Motherboard changed, but various features not working - Galaxy Note II Q&A, Help & Troubleshooting

My phone was working fine and suddenly one day it got stuck on booting screen, then i have tried everything including flashing Rom, but all in vain, finally i ordered a new motherboard from aliexpress.com, the phone got started but everything is in Chinese language, play store was not there and even it is not working when installed from other sources, even whatsapp not working and i am not able to install without google play store. Earlier version installed in the new chinese motherboard was android 4.1.2 and it was asking for software update , when i have updated its software to 4.3 , baseband version N7100ZCUEB1 AND KERNEL VERSION 3.2.31-2859655, BUILD NUMBER JSS15J.N7100CUEOK1.,due to chinese version i am not able to use whatsapp or playstore.After updating the phone, i am not able to make a call and it shows the error "not registered on network" even the apps installed by me are not working, kindly advice what to do, should i use any other version or anything else.This is a chinese motherboard and i want change its software to indian version, what should i do?

Boot into download mode to confirm the model #. If it is a Note 2 made for the Chinese market, the Play store may not function on the phone.

audit13 said:
Boot into download mode to confirm the model #. If it is a Note 2 made for the Chinese market, the Play store may not function on the phone.[/QUOTE
its version is GT-N7100_CHN_CHINEXYNOS4412, can i flash any other ROM in this motherboard?
Click to expand...
Click to collapse

Hmm, looks like it might be the China version of the Note 2 which has limited features. Search XDA for the Note 2 China version and you'll see that many people have problems with flashing ROMs.
Can you send it back and get the international version of the motherboard?

audit13 said:
Hmm, looks like it might be the China version of the Note 2 which has limited features. Search XDA for the Note 2 China version and you'll see that many people have problems with flashing ROMs.
Can you send it back and get the international version of the motherboard?
Click to expand...
Click to collapse
It may be international version because it is shipped for India, is it possible to flash any other ROM and if yes pls guide me how to do, coz i have never done this before. Thanks in advance

If the phone was the international version, it should say "GT-N7100" in Odin mode. See the picture from post number 1: http://forum.xda-developers.com/showthread.php?t=2618261

There's nothing wrong. You need to write the IMEI to the phone memory. By the way you didn't need to buy the entire motherboard. Only the phone memory (16gb eMMC) was corrupt. Samsung produced faulty emmc in the early S3 and Note 2 models (google and you'll see). Mine had same problem I took it to repair shop and they replaced the emmc and wrote the IMEI. Charged me around $40 in local currency. Just tell them you have corrupt IMEI and they'll do it for very little amount of money. After you do that, flash TWRP custom recovery and take back up of your EFS and Modem folder (the IMEI is located here). Then you can upgrade to 4.4.2 and restore EFS and Modem from TWRP.

I don't think it is corrupt or defective chip since 4.3 successfully installed on the phone.

i have changed the CSC code from CHN to INU, after then when i went to recovery mode it shows INU in place of CHN, but i was not able to flash indian ROM in that via odin 3.09, it shows the message "nand write start : failed" and finally failed.
When tried with ODIN 3.07 it shows the error, serial port is not communicating , while USB debugging is allowed in my phone.In recov ery mode it shows the phone detail GT-N7100_CHN_CHINEXYNOS4412 and downside it shows CSC code INU, could any one suggest which ROM to FLASH and how?
CWM recovery is already flashed in it and it is already rooted.
I tried to flash offical 4.4.2 ROM indian version and failed , could anybody pls suggest anything else.

I know of no way to flash a non-Chinese ROM to this phone. I have seen people try to get a ROM onto a Chinese phone. When they do get the ROM installed, The Play store will not run.
The CSC is simply a carrier customization. The problem is the bootloader which prevent the installation of non-authorized ROMs.

audit13 said:
I know of no way to flash a non-Chinese ROM to this phone. I have seen people try to get a ROM onto a Chinese phone. When they do get the ROM installed, The Play store will not run.
The CSC is simply a carrier customization. The problem is the bootloader which prevent the installation of non-authorized ROMs.
Click to expand...
Click to collapse
This ROM is not official, it is a custom ROM as seen in recovery mode.

Based on your first post, the phone looks to be running official 4.3 Chinese rom: http://www.sammobile.com/firmwares/database/GT-N7100/CHN/
All Samsung phones made for mainland China have very tight restrictions on the rom, bootloader, and apps.

audit13 said:
I don't think it is corrupt or defective chip since 4.3 successfully installed on the phone.
Click to expand...
Click to collapse
i think you misunderstood my post...I said his PREVIOUS emmc was faulty. Now that he bought and entirely new motherboard( which has the emmc) he everything is fine. He just needs to write the IMEI to connect to network (not registered on network error).
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Hey if you can't flash other ROMs from odin..
take it to repair shop, they have 3rd party hardware flashing tools, they'll flash the latest 4.4.2 international rom.

I'm not sure if it's possible to flash an international ROM on the phone. Also, the phone may not have the necessary hardware to support the carrier's radio frequencies. If the phone shows the correct imei, not being able to connect to a cell carrier could be a hardware limitation.

audit13 said:
I'm not sure if it's possible to flash an international ROM on the phone. Also, the phone may not have the necessary hardware to support the carrier's radio frequencies. If the phone shows the correct imei, not being able to connect to a cell carrier could be a hardware limitation.
Click to expand...
Click to collapse
before up-gradation of this new chinese rom , network was working fine , so it must be enabled for the frequency range.

The phone may have been running a custom ROM or a hack to allow the phone to work with your carrier? I'm not sure but it does sound like the motherboard is made for mainland China.

Related

[Q] Radio not working in custom ROM I9082

I bought I9082 from China Unicom (which I believe is firmware locked).
I tried to upgrade the firmware manually through ODIN.
But in ODIN it stops at setup connection
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I rooted with CWM and loaded Custom ROM.
Later I upgraded a custom rom - XXAMD6 on baseband ZNMAMB3.
But the problem now is Radio is switched off. So the mobile is not active.
When I try to make a call it says Flight mode is activated. But really flight mode is switched off.
I am able to receive calls and messages
Do you have any solution for this.
Does this mean the firmware is locked?
Any possibility that I can revert back to original stock ROM I9082ZNAMB3
I have this stock ROM downloaded but could not load this through ODIN (seems there is some lock since it stops at setup connection in ODIN).
Any possibility that this stock ROM can loaded through CWM?
My phone is kind of half-bricked since I couldn't make any call also not able to upgrade.
Please give me solution.
mr_coimbatore said:
I bought I9082 from China Unicom (which I believe is firmware locked).
I tried to upgrade the firmware manually through ODIN.
But in ODIN it stops at setup connection
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I rooted with CWM and loaded Custom ROM.
Later I upgraded a custom rom - XXAMD6 on baseband ZNMAMB3.
But the problem now is Radio is switched off. So the mobile is not active.
When I try to make a call it says Flight mode is activated. But really flight mode is switched off.
I am able to receive calls and messages
Do you have any solution for this.
Does this mean the firmware is locked?
Any possibility that I can revert back to original stock ROM I9082ZNAMB3
I have this stock ROM downloaded but could not load this through ODIN (seems there is some lock since it stops at setup connection in ODIN).
Any possibility that this stock ROM can loaded through CWM?
My phone is kind of half-bricked since I couldn't make any call also not able to upgrade.
Please give me solution.
Click to expand...
Click to collapse
you may experience "no service " after rom installation here is what u do to get it back...
its a modem compatibility issue in between different firmwares
download the file from http://www.mediafire.com/?avjo48kvgz517z5 or http://d-h.st/7O8 NEW MODEM LINK
put ur mobile in download mode VOLUME DOWN + MENU + POWER then VOLUME UP to continue
connect to pc
(ur kies should not be runing... proper drivers should be installed)
start odin3 v3.04 . u should see the blue comxx as phone is connected
autoreboot and reset time should be selected.
click in PDA . select the modem.amc8.tar
click start...wait....u get pass confirmation..phone may boot into recovery just reboot.
JUST leave the feedback on this... it worked for me....so it may work for all of u.
Hi, I could not download any file through Odin. I tried pushing the modem file already. Do you think there is any firmware lock?
During setup connection it stays for long time and then it says failed.
Any modem MOD file to push through ClockworkMod I can try.
mr_coimbatore said:
Hi, I could not download any file through Odin. I tried pushing the modem file already. Do you think there is any firmware lock?
During setup connection it stays for long time and then it says failed.
Any modem MOD file to push through ClockworkMod I can try.
Click to expand...
Click to collapse
follow this guide http://forum.xda-developers.com/showthread.php?t=2280248 . make ur own custom rom from ur stock firmware & flash it u will have ur radios back.
or contact @tonylin880806 he is trying to make one rom for ur device.
Hi, Do you know why I could not upgrade firmware or push anything through ODIN?
mr_coimbatore said:
Hi, Do you know why I could not upgrade firmware or push anything through ODIN?
Click to expand...
Click to collapse
it may be carrier locked!!!
unlock carrier lock
k2wl said:
it may be carrier locked!!!
Click to expand...
Click to collapse
Any solution to unlock this carrier locked phone without buying the unlock tools?
mr_coimbatore, I'm having exactly the same problem with a China Unicom I9082 here in Shanghai. Sadly I still haven't been able to find a solution, after weeks of searching.
It's actually a friend's phone, he bought it because he wanted a dual SIM Android handset, though foolishly bought it straight from Unicom rather than from an electronics market. I told him I'd get rid of the China Unicom firmware for him as it is obviously crippled by design like all Chinese Android stock ROMs. I've managed to install k2wl's Ultralite ROM on the handset but I'm facing the same issue as you - the baseband remains untouched from the one that was on the original ROM (I9082ZNAMB3), but it's stuck in flight mode. Can receive calls/texts, cannot make them.
The big clue that there is some kind of lock in place is the fact that one of the original Chinese logos still appears on boot. Flashing a custom ROM should remove all the stock boot logos.
I get exactly the same error when trying to update the baseband with Odin (I tried several basebands and all had exactly the same error as the one you quoted in your first post), so it seems that what we have here is a baseband lock combined with an incompatibility between the existing baseband and the custom ROM (or, more likely, any ROM that isn't the stock ROM provided by China Unicom). If we can remove the baseband lock and update the baseband to one that is compatible with the custom ROM, we should be in business. Sadly, that's as far as I've got.
The annoying thing is that the SIM cards being used on the phone are both China Unicom, so it's not as if I even need the phone to be factory unlocked for use on any network - I simply need it to be able to make outgoing calls/texts on Unicom!
I have seen sites offering an unlock service by IMEI, for example unlocksamsungonline.com, who claim to provide both NCK (network unlock codes) and SPCK (service provider unlock codes), which seem to be what we need in order to unlock the phone without expensive equipment.
However, I have no idea how genuine/reliable these kinds of sites are or if they even work at all (or if they're even legitimate at all), and I'd rather not spend $18.95 USD on an unlock code that doesn't end up working. Also, given that it's a dual SIM phone it's going to have 2 IMEI numbers, so I'm not sure if I'd have to pay double to unlock it or if just one would do the trick!
I've not yet had the time to take the phone to an electronics market in the hope that somebody there understands the issue and has the equipment to remove the baseband lock. In almost all of my previous experiences with electronic markets here in Shanghai, I've found that their hardware knowledge is fantastic (not surprising given that the phones are made in China), but their software knowledge is generally quite poor. I actually spent almost an hour one day explaining to an iPhone engineer that he could in fact upgrade an iPhone's software while preserving an (unlockable) baseband, simply by making a custom ISPW with Pwnagetool or similar that would flash the new firmware without flashing the baseband. He and several of his coworkers claimed that it was impossible, and when I showed them my iPhone that was running the updated iOS while still on an old baseband, until I managed to explain the entire process he thought I had hacked the phone somehow to display a different baseband version... the whole experience was incredibly frustrating and to be honest has left me thinking that I can probably find out more online whenever I've had any kind of software issues with any devices.
Anyway. If you happen to have some success before I do, please let me know! I'll do the same.
Solution
kinggimped said:
mr_coimbatore, I'm having exactly the same problem with a China Unicom I9082 here in Shanghai. Sadly I still haven't been able to find a solution, after weeks of searching.
It's actually a friend's phone, he bought it because he wanted a dual SIM Android handset, though foolishly bought it straight from Unicom rather than from an electronics market. I told him I'd get rid of the China Unicom firmware for him as it is obviously crippled by design like all Chinese Android stock ROMs. I've managed to install k2wl's Ultralite ROM on the handset but I'm facing the same issue as you - the baseband remains untouched from the one that was on the original ROM (I9082ZNAMB3), but it's stuck in flight mode. Can receive calls/texts, cannot make them.
The big clue that there is some kind of lock in place is the fact that one of the original Chinese logos still appears on boot. Flashing a custom ROM should remove all the stock boot logos.
I get exactly the same error when trying to update the baseband with Odin (I tried several basebands and all had exactly the same error as the one you quoted in your first post), so it seems that what we have here is a baseband lock combined with an incompatibility between the existing baseband and the custom ROM (or, more likely, any ROM that isn't the stock ROM provided by China Unicom). If we can remove the baseband lock and update the baseband to one that is compatible with the custom ROM, we should be in business. Sadly, that's as far as I've got.
The annoying thing is that the SIM cards being used on the phone are both China Unicom, so it's not as if I even need the phone to be factory unlocked for use on any network - I simply need it to be able to make outgoing calls/texts on Unicom!
I have seen sites offering an unlock service by IMEI, for example unlocksamsungonline.com, who claim to provide both NCK (network unlock codes) and SPCK (service provider unlock codes), which seem to be what we need in order to unlock the phone without expensive equipment.
However, I have no idea how genuine/reliable these kinds of sites are or if they even work at all (or if they're even legitimate at all), and I'd rather not spend $18.95 USD on an unlock code that doesn't end up working. Also, given that it's a dual SIM phone it's going to have 2 IMEI numbers, so I'm not sure if I'd have to pay double to unlock it or if just one would do the trick!
I've not yet had the time to take the phone to an electronics market in the hope that somebody there understands the issue and has the equipment to remove the baseband lock. In almost all of my previous experiences with electronic markets here in Shanghai, I've found that their hardware knowledge is fantastic (not surprising given that the phones are made in China), but their software knowledge is generally quite poor. I actually spent almost an hour one day explaining to an iPhone engineer that he could in fact upgrade an iPhone's software while preserving an (unlockable) baseband, simply by making a custom ISPW with Pwnagetool or similar that would flash the new firmware without flashing the baseband. He and several of his coworkers claimed that it was impossible, and when I showed them my iPhone that was running the updated iOS while still on an old baseband, until I managed to explain the entire process he thought I had hacked the phone somehow to display a different baseband version... the whole experience was incredibly frustrating and to be honest has left me thinking that I can probably find out more online whenever I've had any kind of software issues with any devices.
Anyway. If you happen to have some success before I do, please let me know! I'll do the same.
Click to expand...
Click to collapse
Hi, Yes I found the solution.
Thanks to tonylin880806 who provided me some links.
I am in Shanghai as well. I took my phone to electronics markets in Xujiahui and Zhangyang Road. In both places, every one said they cannot do anything. The reason may be they don't know or do not want to take any risk or bricking the phone.
Also I went to Samsung service center, they said I have void my warranty. I asked them only to restore the original firmware. But he said the only option is to change the CPU and that will cost more money. I asked for alternate options and he said no.
Then, I re-explored the posts asked if Tony has send me an option
At first, you should upgrade ZNAMB3 to ZNAMD1 with Odin. ZNAMD1 is the office OTA upgrade for ZNAMB3 sent by Samsung.
You can use below link for ZNAMD1 : http://pan.baidu.com/share/link?shar...&uk=3590848074
to download ZNAMD1 which is official and push this through Odin.
So now you will be back with your original firmware without google account.
After this, you can root the phone with CWM.
Then you can load any compatible custom ROMs. But you should note that our handsets cannot load firmwares of all countries. Might be they are firmware locked or modem not compatible for other region firmwares.
I have loaded below custom ROM which is very similar to original firmware with google account. This is really good.
ZNAMD1_rc2 - http://pan.baidu.com/share/link?shareid=517042&uk=2030731697
Also, in this your memory card is swapped with internal memory and have chrome browser. USB OTG is missing.
Only problem I face is, when I install google talk apk there is some problem. Whenever I get an incoming notification from google talk, it hangs and it says process.google.com stopped. So I have installed hangout and its ok with hangout now.
Hope this helps you.........
mr_coimbatore said:
Hi, Yes I found the solution.
Thanks to tonylin880806 who provided me some links.
I am in Shanghai as well. I took my phone to electronics markets in Xujiahui and Zhangyang Road. In both places, every one said they cannot do anything. The reason may be they don't know or do not want to take any risk or bricking the phone.
Also I went to Samsung service center, they said I have void my warranty. I asked them only to restore the original firmware. But he said the only option is to change the CPU and that will cost more money. I asked for alternate options and he said no.
Then, I re-explored the posts asked if Tony has send me an option
At first, you should upgrade ZNAMB3 to ZNAMD1 with Odin. ZNAMD1 is the office OTA upgrade for ZNAMB3 sent by Samsung.
You can use below link for ZNAMD1 : http://pan.baidu.com/share/link?shar...&uk=3590848074
to download ZNAMD1 which is official and push this through Odin.
So now you will be back with your original firmware without google account.
After this, you can root the phone with CWM.
Then you can load any compatible custom ROMs. But you should note that our handsets cannot load firmwares of all countries. Might be they are firmware locked or modem not compatible for other region firmwares.
I have loaded below custom ROM which is very similar to original firmware with google account. This is really good.
ZNAMD1_rc2 - http://pan.baidu.com/share/link?shareid=517042&uk=2030731697
Also, in this your memory card is swapped with internal memory and have chrome browser. USB OTG is missing.
Only problem I face is, when I install google talk apk there is some problem. Whenever I get an incoming notification from google talk, it hangs and it says process.google.com stopped. So I have installed hangout and its ok with hangout now.
Hope this helps you.........
Click to expand...
Click to collapse
Dude thanks so much for the walkthrough, I'm going to try that right now!
However, your first link doesn't work. Can you fix it so I can download the ZNAMD1 firmware please?
kinggimped said:
Dude thanks so much for the walkthrough, I'm going to try that right now!
However, your first link doesn't work. Can you fix it so I can download the ZNAMD1 firmware please?
Click to expand...
Click to collapse
First link is the official firmware ZNAMD1. You can even download the same from samfirmware or anyother websites.
mr_coimbatore said:
First link is the official firmware ZNAMD1. You can even download the same from samfirmware or anyother websites.
Click to expand...
Click to collapse
Yeah, the link you posted has the '...' in it, which ruins the URL. It's the not the complete URL. Do you have the full URL to download it on Baidu? It will be much faster than downloading it from another site, as you know from living in China and having to deal with Chinese internet connections
I just want to make sure I'm downloading the correct version. Is this the right one?
http://pan.baidu.com/share/link?shareid=419656&uk=554171356
---------- Post added at 10:40 PM ---------- Previous post was at 09:54 PM ----------
I got it working. Thanks SO much for your help, my mate will be really happy with it! All he wanted was Google stuff. That updated firmware did the job.
Thanks again!
Google Talk is now replaced by hang out..
Sent from Gt-I9082 stock AMCD firmware
hangout is cool
mr_coimbatore said:
Hi, Yes I found the solution.
Thanks to tonylin880806 who provided me some links.
I am in Shanghai as well. I took my phone to electronics markets in Xujiahui and Zhangyang Road. In both places, every one said they cannot do anything. The reason may be they don't know or do not want to take any risk or bricking the phone.
Also I went to Samsung service center, they said I have void my warranty. I asked them only to restore the original firmware. But he said the only option is to change the CPU and that will cost more money. I asked for alternate options and he said no.
Then, I re-explored the posts asked if Tony has send me an option
At first, you should upgrade ZNAMB3 to ZNAMD1 with Odin. ZNAMD1 is the office OTA upgrade for ZNAMB3 sent by Samsung.
You can use below link for ZNAMD1 : http://pan.baidu.com/share/link?shar...&uk=3590848074
to download ZNAMD1 which is official and push this through Odin.
So now you will be back with your original firmware without google account.
After this, you can root the phone with CWM.
Then you can load any compatible custom ROMs. But you should note that our handsets cannot load firmwares of all countries. Might be they are firmware locked or modem not compatible for other region firmwares.
I have loaded below custom ROM which is very similar to original firmware with google account. This is really good.
ZNAMD1_rc2 - http://pan.baidu.com/share/link?shareid=517042&uk=2030731697
Also, in this your memory card is swapped with internal memory and have chrome browser. USB OTG is missing.
Only problem I face is, when I install google talk apk there is some problem. Whenever I get an incoming notification from google talk, it hangs and it says process.google.com stopped. So I have installed hangout and its ok with hangout now.
Hope this helps you.........
Click to expand...
Click to collapse
isit this rom ZNAMD1_rc2 hhas French in its language list ? I have one to put french language !
Thx advanced !
it also work on a Unicom duos thx you @mr_coimbatore , after ZNAMD1 I flashed this I9082XXAMF7 custom rom and work correctly ...both sim working fine !!
I9082xxamf7
psytr0nic said:
it also work on a Unicom duos thx you @mr_coimbatore , after ZNAMD1 I flashed this I9082XXAMF7 custom rom and work correctly ...both sim working fine !!
Click to expand...
Click to collapse
Hi, Can you please send me the link from where you downloaded I9082XXAMF7 custom rom.
mr_coimbatore said:
Hi, Can you please send me the link from where you downloaded I9082XXAMF7 custom rom.
Click to expand...
Click to collapse
I took it there : #LINK not really customized , just rooted . Roms are 100% samsung stock one according to OP and what I saw too . nothing missing .
psytr0nic said:
I took it there : #LINK not really customized , just rooted . Roms are 100% samsung stock one according to OP and what I saw too . nothing missing .
Click to expand...
Click to collapse
Thanks for the link. It works perfectly.
XXAMF7 got loaded on the baseband version of ZNAM2.
I have the same problem like yours. As soon as it was loaded it said there is a software update, but when say OK to update the software it keeps searching. Have you got any solution for this?
Also, did you try if you upload the stock ROM of XXAMF7 on the unicom Duos? Whether the radio works?
psytr0nic said:
I took it there : #LINK not really customized , just rooted . Roms are 100% samsung stock one according to OP and what I saw too . nothing missing .
Click to expand...
Click to collapse
After update, firmware is still 4.1.2??
Do you have USB on the go (OTG) option. (Means can you connect the USB flash drive to you mobile by means of a adaptor cable??

[Q] T-Mobile branded S3 somehow became AT&T.

When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.

[Q] S3's Model Number changed after installing wrong ROM

I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
SuperGoober said:
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
Click to expand...
Click to collapse
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
lvpre said:
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
Click to expand...
Click to collapse
Thanks it worked.

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!
If you're in Canada then just flash the Canadian firmware.
ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?
Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html
Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.
LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?
Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:
You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.
I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?
OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.
Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!

Odin flash gets: Device:2 Binary:1

Hi Guys,
When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
Or if BL disabled following some recommendations:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
Current version: (got via OTA)
G960FXXU2BRG6
Service provider OXM_XEF_00_0025 ... XEF/XEF, XEO/DBT - but this has probably nothing to do with that.
Returning to:
DBT-G960FXXU1BRE5
History of the phone is that I've received it on Saturday (manufactured on May 21), dual SIM + SD Card was working, got notification about OTA, and did proceed (silly me), got message that "no downgrade" will be possible - thought that it is for normal user, not the one with Odin magic, though have a feeling it has something to do with that. It was unusual message though thought it is something new on S(, but not really blocking me to downgrade with Odin.
Is there any way to downgrade? I really need to do that as thanks to Samsung I cannot use dual SIM + SD Card, described here:
https://forum.xda-developers.com/ga...o-sim-card-t3822368/post77193881#post77193881
Thanks!
When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
same problem, my S9 Plus is AFG cant intall only can update with DBT file but his current AFG no
Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says
*Detection* said:
Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says
Click to expand...
Click to collapse
Many thanks, that makes sense. I do remember message prior OTA apply "you won't be able to downgrade" but thought it was meaning that normal user won't be able to downgrade unless Odin would be used. Tough luck.
The worst part is that this is the first "U2" version for S9, so there's no path for me.
One more question - when "BL" was deselected and I've left only AP, CP, CSC - it resulted in message:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
It is still in effort to downgrade the rest outside of BL, but does it seem I'm stuck on this firmware as the lowest on my phone now?
On technical side, these are all partitions on internal SDcard/memory. Why would it not be possible to overwrite it? Is it re-partitioning thing or something else? I'm trying to understand from where the limitation comes.
p.s. did some reading on bootloader process of Samsung and whilst it is clever and nice for Common Criteria, it should be possible to unlock it as in the past (Superboot tool). The good bootloader lecture is here: https://www.sciencedirect.com/science/article/pii/S1742287618300409 (S7 based).
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
What are risks using that Odin version and pushing AP?
Should I try to push BL too?
Apologies if I'm overly cautious it is that I don't want to brick the phone.
Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5
My Odin screen
batfink1 said:
Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5
Click to expand...
Click to collapse
Well... sometimes it is better to be safe than sorry... (at least this is my take), like with that unfortunate upgrade.
If you're that brave, why don't you upgrade to the latest one and then try to downgrade?
Attached is Download mode screenshot.
batfink1 said:
My Odin screen
Click to expand...
Click to collapse
Interestingly, your model shows 6GB, mine 4GB, but it doesn't matter...
Thanks... I'll debating if to give it a shot with that custom Odin version. Did you try it? Should BL be included?
I said brave, not freaking insane... Mine is rooted and working perfectly
I honestly DON'T want to go through the 17 days of possibly having to wait for the RMM STATE again haha
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
Mines an S9+, they have 6 gig compared to the S9 which only has 4 gig.
I didn't try it, no.. I just know the modded version exists.
I'm having the same problem
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!
Ma5terDevil said:
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!
Click to expand...
Click to collapse
Just a thought - your non-brand might be of an older release than branded software. In worst case you're stuck on working branded soft?
i tried, i doesn't work either with/without BL
batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
i tried, i doesn't work either with/without BL selected. so i guess the modified odin did not fit for the new firmware.
I Tried
Me too being the grab your balls by the hand person that likes to boldly go where no man has gone before, attempted the patch version of Odin on my s9 in an attempt to put the TMO firmware on to get RCS chat. Using BL AP CL and CSC all did not work. I got the same stupid message regarding the downgrade. I then tried AP and CSC alone. Same issue. Finally, I tried just CSC. It gave a similar error but it was difference in the sense that it says [cache]fused 2 > Binary 1.
It's super annoying that you can't move from u1 to u (unlocked to carrier) without having to do all this crap.
Hey all, dunno if you resolved the kernel error but I was getting the same thing on my S8 (SM-G950F) and ended up checking if anyone at the Samsung store could fix it (they could). Have a look at this post I wrote up, hopefully it's somewhat useful.
https://forum.xda-developers.com/showpost.php?p=77580177&postcount=18
Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".
joe535 said:
Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".
Click to expand...
Click to collapse
ODIN is a Samsung INTERNAL tool, you're not even meant to be using it
And you do have the freedom to run whatever OS you want, you have that choice the day you choose to buy a new phone, otherwise read the smallprint, pretty sure you agreed to Samsungs terms when you bought the phone
I don't get why people buy Samsung phones knowing how locked down they can be, knowing they don't run vanilla Android, knowing about KNOX, and then complain when they can't do anything with them.... if I wanted to mod my phone without any problems I wouldn't be buying Samsung
Anyway, honestly I accidentally updated my spare S9 to U2 forgetting it can't be rolled back and I had a little bit of trouble finding a firmware that ran fine with gravity box, but now I'm running a custom BRI3 rooted with magisk running gravity box where 99% of features work including lock screen security.
So unless the U2 bootloader is effecting you in some way... Does it matter if you can't roll back.
Well, the hardware of Samsung I actually do like.. But the software policy I do not.
For sure, never again I will buy Samsung

Categories

Resources