Develop Bugs

[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] Refurb T999, appears to have been rooted and flashed

UPDATE:
Just thougth I'd update this for anyone who stumbles on this thread in the future.
While everything about the phone from the outside and most of the stuff shown by Device Info indicated it was in fact a T999, apparently it did have an SGH-i747 bootloader. I overwrote that bootloader with an SGH-T999 bootloader, and hardbricked it.
So don't do that.
Talked to a JTAG-er who said that if the download screen says SGH-i747, it has an i747 motherboard.
Word of caution to others who end up with a refurb frankenphone.
I need some help understanding some things here. I'm a bit of a noob when it comes to this android stuff, though I have rooted my Nook once (then unrooted it) and I made an SD card for it with CM7 on it. And I have worked in IT since 1988 and have been a SysAdmin for at least half that time. So I do get most computer-related concepts and I've flashed firmware on everything from disk subsytems to my DSLR.
So here's my story:
I ordered an unlocked, refurbished Galaxy S3 off of Amazon. It's an SGH-T999 from T-Mobile, and T-Mobile is my carrier.
I noted something was awry when it wouldn't register to update. I also notice it doesn't have the wifi calling feature under settings, which it should have if it were stock. And that's a feature I used with my old HTC G2 a lot.
So I've been pouring over this forum for a few days trying to figure out what's up and what I should do to make it do what I want it to.
It has SuperSU on it, and the phone's status is "Modified". It's running 4.1.2, and the build is T999UVMD5-chag-multi-vT (it also lists a baseband version of T999UVDMD5 ... I'm guessing that's the modem version)
I assumed it was rooted because it has SuperSU on it, so I bought Mobile Odin to see if it would even run. It says it wants root (no shock there, but I thought I had it).
SuperSU says the binaries need updating, but it won't update them (it tries and says it failed). There's no SuperUser under "Settings", so I can't enable it.... so I'm starting to think it was rooted, flashed, then unrooted. Though the RootValidator app says I "might" have root since it was denied access. But SuperSu doesn't work right so I can't grant it SU permissions.
So first, I need help with a theory of the state of the phone. Frankly, it works great the way it is except I don't have the T-Mobile WiFi calling feature, which I'd really like. It DOES let me use the hotspot without an extra hotspot plan. Which is very cool (I don't use it much, but I like the option).
I've seen there's a 4.3 build out there based on the T999 that doesn't have Knox ... which I'm assuming is good from what I've read as far as being able to and keep root and control the hotspot feature. But I don't really know.
I've considered going back to an earlier stock version and letting it update OTA or via Kies, but then I'm afraid it might get certain things (like hotspot) disabled by the carrier. I'd really like to keep that feature.
But first ... how do I figure out if I have root on the phone already? I'm getting conflicting info.
Perhaps there is some kind knowledgeable soul who can help me find my way.
Much appreciated if anyone can help.

It was probably rooted and then the root was lost somehow.
Just flash it with the non knox 4.3 rom from mrrobinson.

you can revert back to the latest stock firmware with only root injected\implemented into it. you'll have all the stock features(and bloat, which you can remove, since you'll have root access, using an app like titaniumbackup.
download the firmware in this thread:
http://forum.xda-developers.com/showthread.php?t=1949687
you want the latest official pre-rooted firmware(listed below), where it says T999. make sure it's for T999, and NOT T999L!
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
and you'll need Odin for PC, to flash the firmware:
http://www.androidfilehost.com/?fid=9390275921635705049
follow these instructions on how to flash, starting from "Second"
http://forum.xda-developers.com/showthread.php?t=1771687

Thanks guys.
Got Odin. Watched a good root video. Now to download the ROM I want. 4.3 sounds intriguing, as long as it still has WiFi calling.
I'll go read that thread. I can be taught, but sometimes I need help finding where to start.

flipster64 said:
Thanks guys.
Got Odin. Watched a good root video. Now to download the ROM I want. 4.3 sounds intriguing, as long as it still has WiFi calling.
I'll go read that thread. I can be taught, but sometimes I need help finding where to start.
Click to expand...
Click to collapse
4.3 absolutely has WiFi calling. that's a T-Mobile feature that will always remain on the OTA(over the air) updates, unless they decide to do away with that technology. there were many changes made from 4.1.x to 4.3. by the way, to disable the wi-fi from always scanning in 4.3, you have to turn off\uncheck the option in Settings > Wi-Fi > press "Menu" > Advanced > "Always allow scanning", when you do the update.
4.3 features, as per wiki;
Bluetooth low energy support.[112]
Bluetooth Audio/Video Remote Control Profile (AVRCP) 1.3 support
OpenGL ES 3.0 support, allowing for improved game graphics[112]
Restricted access mode for new user profiles[112]
Filesystem write performance improvement by running fstrim command while device is idle[113]
Dial pad auto-complete in the Phone application[112]
Improvements to Photo Sphere[114]
Reworked camera UI, previously introduced on Google Play edition phones[115]
Addition of "App Ops", a fine-grained application permissions control system (hidden by default)[116]
4K resolution support[117]
Many security enhancements, performance enhancements, and bug fixes[118]
System-level support for geofencing and Wi-Fi scanning APIs
Background Wi-Fi location still runs even when Wi-Fi is turned off
Developer logging and analyzing enhancements
Added support for five more languages
Improved digital rights management (DRM) APIs
Right-to-left (RTL) languages now supported[112]
Clock in the status bar disappears if clock is selected as lockscreen widget
http://en.wikipedia.org/wiki/Jelly_Bean_(operating_system)#Jelly-Bean

Ok, there's one thing holding me back now. I've read a few things about different modem (baseband) flashes, and that I might have to flash a different modem onto my Galaxy S3 SGH-T999 for this to work. I note that my current baseband is T999UVDMD5 which matches the stock image name for 4.1.2 (which is also my current OS version) but the name of the stock image for 4.3 is T999UVUEMJC ... which would suggest to me that this is different modem firmware. Or do I not need to worry because the modem is included in the 4.3 firmware tar file? I have a hunch the latter is the case because it isn't mentioned on that HOWTO page but I really want all my ducks in a row to minimize my chances of bricking or losing data.
T-Mobile Image
November 2013 - 4.3 JellyBean - New!
Note: This is based off of the stock image TMO T999UVUEMJC
Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.
Perm Mirror: Download - root66_TMO_T999UVUEMJC_2.7z
April 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image TMO T999UVDMD5
Perm Mirror: Download - root66_TMO_T999UVDMD5.7z
Incidentally, I've been looking for a good primer page like this ... this is excellent.

Ok... modem is basically firmware, from what I'm reading.
I've tried to download the root66_TMO_T999UVUEMJC.tar to the phone using Odin, but I'm getting a secure check fail sbl2 error when I do. Not finding any information on why that might be.
It is a bit strange to me that when I boot into the recovery mode it's telling me it's an i747, though the sticker and the "about" in the os say SGH-T999... but they may be the same thing for all intents and purposes.
I CAN transfer the file to the SD card using Kies, and I have, but it doesn't show up as an option to load from external storage, and I'm guessing the Odin connection and settings do something special to cause the flash to be available and work in the first place.
So ... have we seen a secure check fail sbl2 before, and do we know what it means? I'm going to keep looking but I've had no luck so far.
Well no good luck anyway.

Here's what Odin is telling me on the PC side
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl2.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Yeah ... this is where I'm stuck. Odin won't flash that de-knoxed 4.3 tar from DocHoliday. It did let me flash Clockwork Mod and I can get into that and back things up, and I was able to add the SuperSU zip (but I don't see the SU program after it boots so I don't think I actually have root.) It's weird.
I read on one forum I might have to flash an alternate recovery onto it to get it to work. I have it downloaded but I'm a little leery of that until I understand the possible implications. I noticed last time I looked at the recovery console it says the counter's up to 3 (after CM... it was at 2 when I bought the thing) and then there's something about Qualcomm Secureboot being set to Enable, but I can't tell if that's good or bad from reading posts on it. My phone didn't come with a warranty so I'm not terribly concerned with tripping the counter (though it would be cool to reset it at some point, it's not a priority at all).
Anyway, I'm still trying to learn more about what all this means before I proceed.
I have visions of bootloaders and img files and tar files and zip files flying around my head. Meantime I'm still on 4.1.2, apparently a de-bloated T-Mobile build with no wifi calling.

It sounds like Odin might be falling due to your phone having an att build.prop. If you are sure it is an sgh-t999, want to keep root, and have the know how, you can make this process a lot easier by updating your firmware to the last one before the 4.3 update (otherwise you will be stuck with Knox). Afterward update your recovery and flash a more current touchwiz ROM.
Make sure to read the entire OP of these threads and flash in recovery.
To update your firmware without having to use Odin, read the following thread:
http://forum.xda-developers.com/showthread.php?t=2282603
There is a few options when it comes to choosing a custom recovery. I'm currently using Philz. If you get Philz, make sure to get the d2lte version. The thread for Philz recovery is below:
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SGH-T999 using Tapatalk

When put the phone in download mode it says product name is SGH-i747 ... but I've never seen another SGH-T999, so for all I know they all say this. Is this why you're thinking it has an ATT build.prop? It does have the T-Mobile logo when starting up and shutting down. I can go read more on that. I wonder if there's an Android OS for dummies book.... I've been working with DOS, Windows, & Linux for decades, it can't be THAT hard to understand.
I need to get comfortable doing CM backup and restore. Yeah, you're right, I don't want Knox -- but there is a de-knoxed 4.3 build out there on the forum which is what I intend to flash when I finally get to a point where Odin will let me flash it. Or I see you've linked some threads that talk about other ways.
I'll go read those threads you linked and see what I can absorb from them. Thanks!

flipster64 said:
When put the phone in download mode it says product name is SGH-i747 ... but I've never seen another SGH-T999, so for all I know they all say this. Is this why you're thinking it has an ATT build.prop? It does have the T-Mobile logo when starting up and shutting down. I can go read more on that. I wonder if there's an Android OS for dummies book.... I've been working with DOS, Windows, & Linux for decades, it can't be THAT hard to understand.
I need to get comfortable doing CM backup and restore. Yeah, you're right, I don't want Knox -- but there is a de-knoxed 4.3 build out there on the forum which is what I intend to flash when I finally get to a point where Odin will let me flash it. Or I see you've linked some threads that talk about other ways.
I'll go read those threads you linked and see what I can absorb from them. Thanks!
Click to expand...
Click to collapse
Most T-Mobile and AT&T s3 ROMs are cross compatible. It sounds like it is a sgh-t999. If it has an AT&T ROM on it, that would make ODIN throw out errors (to prevent bricking your phone) until you have your build.prop identity the device as an sgh-t999.
Sent from my SGH-T999 using Tapatalk

Oh, man. The road blocks. They are legion. And sometimes circular
I've tried updating the bootloader (from CM v6.0.3.1) as described here:
http://forum.xda-developers.com/showthread.php?t=2282603
But CWM aborts the installation:
Finding update package
Opening update package
Installing update
assert failed: getprop(ro.product.device) == "dttmo" || getprop("ro.build.product") == "d2tmo"
error in external/sd/T999_UVDMD5_firmware_v4.zip
(Status 7)
Installation aborted.
Which I figured has something to do with what it's finding in build.prop as mentioned above. Except I just looked in my build prop, and it says it's an SGH-T999 made by samsung.
ro.build.product.model=SGH-T999
ro.product.brand=samsung
But then it says that ro.product.model is obsolete, and to use ro.product.device ... which looks like it's set to ... canada? ro.product.device=d2can
Which certainly doesn't match dttmo or d2tmo.
So ... edit the build.prop file, then?
I downloaded an editor to do it. It does whine about not being able to open /storage/sdcard0/buildprop.tmp, not sure if that's going to be an issue. I "re-rooted" with CWM_SuperUserv3.0.7 so I can now use root explorer again (which is how I looked at the build.prop file) ...
At that point I guess I'd flash the radio/bootloader above, reboot to Odin mode, and try the Knox-Free 4.3 flash again?
Any red flags going up?

flipster64 said:
Oh, man. The road blocks. They are legion. And sometimes circular
I've tried updating the bootloader (from CM v6.0.3.1) as described here:
http://forum.xda-developers.com/showthread.php?t=2282603
But CWM aborts the installation:
Finding update package
Opening update package
Installing update
assert failed: getprop(ro.product.device) == "dttmo" || getprop("ro.build.product") == "d2tmo"
error in external/sd/T999_UVDMD5_firmware_v4.zip
(Status 7)
Installation aborted.
Which I figured has something to do with what it's finding in build.prop as mentioned above. Except I just looked in my build prop, and it says it's an SGH-T999 made by samsung.
ro.build.product.model=SGH-T999
ro.product.brand=samsung
But then it says that ro.product.model is obsolete, and to use ro.product.device ... which looks like it's set to ... canada? ro.product.device=d2can
Which certainly doesn't match dttmo or d2tmo.
So ... edit the build.prop file, then?
I downloaded an editor to do it. It does whine about not being able to open /storage/sdcard0/buildprop.tmp, not sure if that's going to be an issue. I "re-rooted" with CWM_SuperUserv3.0.7 so I can now use root explorer again (which is how I looked at the build.prop file) ...
At that point I guess I'd flash the radio/bootloader above, reboot to Odin mode, and try the Knox-Free 4.3 flash again?
Any red flags going up?
Click to expand...
Click to collapse
I'd highly recommend updating your recovery before doing much. Once you do that, try flashing the bootloader and the 4.3 ROM.The only red flag would be if you plan to use Odin since it is identifying as a different phone due to the build.prop.
Also, it sounds like the previous owner messed up when they modified the build.prop. You really shouldn't need to worry about editing it if you plan to switch ROMs since any new ROM is going to replace it anyways.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

By recovery I think I understand you're saying the latest version of CM ... which I see for my phone is 6.0.4.5 (SGS3 T-Mobile).
I am also reading I can flash a ROM with CM, though all of the ROMs I've seen so far (including the one I want to use) are .tar files and I think CM uses zips.
I don't suppose you can just un-tar the ROM and zip it ... can't be that easy ... can it?

Right, you will need to either update CWM or change to a different recovery such as TWRP or Philz (Philz is based on CWM but has a lot more features.
You're right. Most ROMs are installed/flashed in a custom recovery in ZIP format rather than Odin. Making an Odin package compatible with recovery isn't nearly as simple as unpacking a .tar file and zipping it.
You can find a lot of ROM options that are possible to flash in the development section of this board.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I've updated to Philz CM 6.07.9.
My modem is already T999UVDMD5 ... if I flash the update in this thread (http://forum.xda-developers.com/showthread.php?t=2282603) I'm guessing it will overwrite CM and put the stock recovery back. So I decided to skip that part and try the update again.
I'm getting this here...
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have root ... I can go in and look at build.prop and edit it, but it won't let me save it.
I guess I need to find a different way to flash.

Well, I THOUGHT my bootloader must be locked.
But I'm unsure now ... I mean ... I'm rooted. I can flash stuff with Philz Custom CWTouch ...
It's that FAIL! (Auth) that's getting me.

flipster64 said:
Well, I THOUGHT my bootloader must be locked.
But I'm unsure now ... I mean ... I'm rooted. I can flash stuff with Philz Custom CWTouch ...
It's that FAIL! (Auth) that's getting me.
Click to expand...
Click to collapse
Odin will continue to fail until your build.prop is fixed. Really, all you need to do is pick a custom ROM from these forums and flash using Philz. Afterward, you should be back in order. Just make sure you follow the instructions in the ROM's thread and also make sure the ROM is for the t999
Sent from my SAMSUNG-SGH-T999 using Tapatalk

So there are custom roms that are zips instead of .tars on this forum, then?
Or Can Philz flash a .tar?
I'll look for a custom rom zip out there for my phone.

Problems downgrading to 4.1.1 firmware

I'm having some trouble flashing 4.1.1 on a 4.1.2 phone. I was linked to this site and grabbed the 4.1.1 firmware from there. I've tried both Odin 3.07 and 3.09 but I get a "complete(write) operation failed" error with both.
What's odd is this device is most assuredly an i747, yet on the phone's screen in Download Mode the Device Name field shows T999 for some reason. Might that have something to do with this failure to flash?
I was able to successfully flash a file earlier that rooted the device, successfully from the looks of it. SuperSU seems to be working fine.
Any ideas on how I can get this flashed so I can unlock the phone for use on Smart Talk?
Edit: After doing a factory reset from recovery I now get this from Odin:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Looks like there is a bootloader mismatch that it's causing the write failure.

audit13 said:
Looks like there is a bootloader mismatch that it's causing the write failure.
Click to expand...
Click to collapse
Audit, could it be that it's got the BL for T999 which is what's causing the errors? However, wouldn't that have been likely to cause a soft brick in the first instance unless the rest of the system is compatible? I guess he could check system information under Settings to see if this really has i747 firmware or someone's previously successfully "changed" it to a T-Mob phone. Not sure that's possible but I was just thinking ... perhaps a previous J-Tag operation especially if it was purchased in the secondary market.

Larry2999 said:
Audit, coup as t be that it's got the BL for T999 which is what's causing the errors? However, wouldn't that have been likely to cause a soft brick in the first instance unless the rest of the system is compatible? I guess he could check system information under Settings to see if this really has i747 firmware or someone's previously successfully "changed" it to a T-Mob phone. Not sure that's possible but I was just thinking ... perhaps a previous J-Tag operation especially if it was purchased in the secondary market.
Click to expand...
Click to collapse
It was purchased as a refurb. Everything under System Setting - About Phone shows up as i747. Completely stuck at this point.
Edit: I just installed an app called Info that shows all relevant build information.
Bootloader version shows as T999UVDMD5
Model is SGH-I747
Build ID I747SEMC1
How can I fix this mismatch?

Headcase_Fargone said:
It was purchased as a refurb. Everything under System Setting - About Phone shows up as i747. Completely stuck at this point.
Edit: I just installed an app called Info that shows all relevant build information.
Bootloader version shows as T999UVDMD5
Model is SGH-I747
Build ID I747SEMC1
How can I fix this mismatch?
Click to expand...
Click to collapse
That would explain it then. Thankfully T999UVDMD5 would appear to be the Bootloader for the T-Mob version running Android 4.1.2 (and not the inflexible 4.3). Have you tried flashing the 4.1.2 bootloader via recovery or, if you are feeling adventurous, the 4.1.1 version? You may find both via the links below ...
(http://www.androidfilehost.com/?fid=23269279319197288)
http://www.androidfilehost.com/?fid=23269279319197287
See also previous thread on updating bootloaders (http://forum.xda-developers.com/showthread.php?t=2321310)

Larry2999 said:
That would explain it then. Thankfully T999UVDMD5 would appear to be the Bootloader for the T-Mob version running Android 4.1.2 (and not the inflexible 4.3). Have you tried flashing the 4.1.2 bootloader via recovery or, if you are feeling adventurous, the 4.1.1 version? You may find both via the links below ...
(http://www.androidfilehost.com/?fid=23269279319197288)
http://www.androidfilehost.com/?fid=23269279319197287
See also previous thread on updating bootloaders (http://forum.xda-developers.com/showthread.php?t=2321310)
Click to expand...
Click to collapse
Tried flashing the first one from stock recovery and got:
Verifying update package...
E:signature verification failed
Installation aborted
I read somewhere that this happens when trying to flash a non-signed file in stock recovery so I installed Clockwork recovery and tried flashing both of those files. They both yield this error:
E:Error in (file path and name)
(Status 7)
Installation aborted.
Tried flashing via TWRP and get:
E:Error executing updater binary in zip (file path and name)
Updating partition details...
Failed

So apparently this phone is already unlocked. Never bought a refurbished phone before so didn't even think to try before unlocking it.
So I guess I don't need to downgrade to 4.1.1 afterall. Where does that leave me? I still have this mismatched bootloader (for the T999 model).
Am I okay to just try flashing a recent ROM like AOKP 4.4?

Headcase_Fargone said:
So apparently this phone is already unlocked. Never bought a refurbished phone before so didn't even think to try before unlocking it.
So I guess I don't need to downgrade to 4.1.1 afterall. Where does that leave me? I still have this mismatched bootloader (for the T999 model).
Am I okay to just try flashing a recent ROM like AOKP 4.4?
Click to expand...
Click to collapse
Looks like we learn all the time. I didn't know you could install a bootloader for one system on another system and still get it to work. Thankfully your phone is unlocked. If the phone is working normally, your best option may be to leave it that way for now although, as we've seen, this could seriously limit firmware upgrade possibilities. It's doubtful whether flashing a custom ROM would help because even custom ROMs don't have their own bootloaders and still have to rely on the manufacturer's bootloader to run. A custom ROM would, therefore, probably leave things the way they are with the bootloader. I'm sure there would be a way to get this done. We just have to research a little bit more.
Maybe, now the phone is unlocked and you probably don't need the lower firmware anymore, you may try updating to 4.3 JB. At this stage, you really have nothing to lose so it may be worth trying.

Hello why you want to downgrad maaaaaaaaad
Sent from my GT-S7500 using xda app-developers app

laith al shishani said:
Hello why you want to downgrad maaaaaaaaad
Sent from my GT-S7500 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to downgrade in order to unlock, but it appears to already be unlocked so that's no longer necessary.
Larry2999 said:
Looks like we learn all the time. I didn't know you could install a bootloader for one system on another system and still get it to work. Thankfully your phone is unlocked. If the phone is working normally, your best option may be to leave it that way for now although, as we've seen, this could seriously limit firmware upgrade possibilities. It's doubtful whether flashing a custom ROM would help because even custom ROMs don't have their own bootloaders and still have to rely on the manufacturer's bootloader to run. A custom ROM would, therefore, probably leave things the way they are with the bootloader. I'm sure there would be a way to get this done. We just have to research a little bit more.
Maybe, now the phone is unlocked and you probably don't need the lower firmware anymore, you may try updating to 4.3 JB. At this stage, you really have nothing to lose so it may be worth trying.
Click to expand...
Click to collapse
So just try flashing AOKP or CM or something via TWRP? Don't the newer ROMs require an updated bootloader?
Edit: Got impatient and tried flashing Cyanogenmod. I used the CM Windows installer to minimize any chances of me screwing up the process. Followed the instructions, installer said installation complete, successfully installed, etc. All it did was do a factory reset. Touchwiz 4.1.2 is still on there.

Help me flash stock ROM on M919 which currently has i337 ROM

Hi guys, I'll admit I'm a noob, but I'm trying my best to understand the ins and outs of flashing ROMs. I recently purchased a used S4 SGH-M919. The problem is the phone has i337 AT&T firmware on it. (I'm pretty sure it's a stock ROM and not rooted). I need to find a way to use the Tmobile network on this phone, so I have been trying revert to stock by flashing the stock M919 ROM on the phone using odin. Odin repeatedly fails before the flash begins. Odin dislays "FAIL! (Auth)" and the phone displays message "SECURE CHECK FAILED : aboot". I have tried several different .tar.md5 firmware files from sammobile. I have tried several USB cables and every USB port on my PC. The phone isn't quite bricked, it still boots fine it's just the network unusable with my t-mobile sim and the at&t firmware.
Do I need to wipe the phone and do a kernel flash? I'm lost and any advice would be appreciated
Thanks in advance,
Ryan

pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.

are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website

XeoNoX said:
pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.
Click to expand...
Click to collapse
c_irie said:
are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website
Click to expand...
Click to collapse
Thanks for the replies fellas. I am sure it's a stock SGH-M919. The sticker beneath the battery says so. I've already tried using the most recent firmware from sammobile (ending with OH3) with odin and I receive the same error no matter what. I've even tried multiple versions of odin and have used PDA or AP accordingly.
c_irie, It's not a stock i337, I've read about the bootloader issues and Loki regarding that model. I would really prefer to do a clean M919 flash, but do you think I could use a sim unlock code from at&t with my current situation?

This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled

rkham said:
This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.

XeoNoX said:
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.
Click to expand...
Click to collapse
Thank you for opening up a new realm of possibilities for me. I hadn't thought of that. Why would someone re-brand a i337? Do you think odin is failing because I have the wrong image for a i337?

Problem solved for now. I went ahead and assumed that it's actually an i337. I followed the suggestion above and requested an unlock code from at&t using the imei found in settings. I didn't think it would work, i figured the phone was stolen, but the code from at&t worked and I can use the t mobile network! thanks guys. I'm kind of bummed that it's an i337 since it will be difficult to root if i ever go down that path.

glad we where able to help you out. Sorry to hear that someone kinda scammed you and sold you the wrong phone. To be honest with you tmobile phones have a slightly higher resale value too...i hope you didnt pay the extra premium..esp since it was a fixer upper phone. well anyways glad you got it all figured out. btw: the att s4 on tmo is missing a band but you can possibly unlock it to have all the tmo bands.
http://forum.xda-developers.com/showthread.php?t=2291589

Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.

rkham said:
Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.
Click to expand...
Click to collapse
if you have used a factory ODIN image and flashed it and you have all those problems then im sorry to say it was probably a "fixer upper" phone that wasnt fixed properly. sorry to hear you are having all those problems...that sux. i always thoroughly test new phones IN PERSON before i buy them. i do the sim card test, screen color test, mic test, speaker test, model number test. and a voice and data and wifi test.

installing tmobile on att version
f irst of all you have to have root second you need to install a custom recovery such as TWRP. then you need to download the Wicked V.10 zip.then boot into recovery mode white data cache partition and dalvik cache partition.actually install the zip file you downloaded for the wicked v10 Rom. But make sure download the tmobile version because it willautomatically change your CSC settings

maybes this will help
Ok first things first. You have to be rooted and already have a custom recovery installed like TWRP or CWM. If u aren't rooted then try the king root apk. Once u have root access then you can go to download mode on your phone. Most of the Phones the power button & volume down at the same time will take you to download mode you have to search on Xda for the custom recovery version that is for your phone model it also has to be the Odin compatible ".tar" file. I use Odin 3.9 just because it seems to work better but after u have everything I've listed the install Odin 3.9 on your computer. Once that is done u have to remember where the custom recovery u should have already downloaded is located. Right click on the odin icon and click run as administrator make sure that you click on the BL button because that is where you will place the custom recovery.tar file. when you click on the BL button it will open up a window where you can search for the custom recovery that you downloaded earlier once you find it click on it and it will automatically go to the BL box then you click Start and just let Odin finish doing what it has to do when it says complete unplug your cable from the computer out phone reboot your phone hold volume up that should take you to your custom recovery once you have your custom recovery installed you can backup your whole system install zip files custom roms. things of that nature I hope this helps feel free to msg me if u have problems

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