Related
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.
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.
Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.
BoJo963 said:
Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.
Click to expand...
Click to collapse
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.
sasank360 said:
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.
Click to expand...
Click to collapse
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.
BoJo963 said:
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.
Click to expand...
Click to collapse
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
BTW can you remember the fail message on your phone when odin failed....??
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.
sasank360 said:
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.
Click to expand...
Click to collapse
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.
BoJo963 said:
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.
Click to expand...
Click to collapse
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.
sasank360 said:
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.
Click to expand...
Click to collapse
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.
BoJo963 said:
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.
Click to expand...
Click to collapse
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
http://www.sammobile.com/firmwares/1/?model=SGH-I257M&pcode=0 --- This is the list of latest firmwares for I257M. Use these firmwares, not I9195 firmwares.
sasank360 said:
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
Click to expand...
Click to collapse
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.
BoJo963 said:
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.
Click to expand...
Click to collapse
No mention. It is essential to learn from little mistakes.
It seems that after the November AT&T OS upgrade that my wife was unable to get into the Settings App (Settings Failed Error). :crying:
1. Got on with Samsung support, they took me through several reboot sequences, etc.
2. Finally they said we need to Factory Reset. We backed up data with Kies and proceeded.
3. While rebooting from the factory reset, OP Sys fails on the language selection screen (Settings Failed Error)
4. Samsung took us too Kies and tried to flash the Op Sys.
5. Now getting "Firmware upgrade encountered an issue".
6. Tried Kies again but does not find my device.
7. Downloaded the I747 AT&T Rom and using Odin
8. Am able to get the "Downloading" screen to work
8. Odin sees the Com but when trying to flash, it Fails every single time.
HERE IS THE SEQUENCE:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I am stuck as to what to do next. PLEASE HELP :crying:
Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk
Sachitoge said:
Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
Sachitoge, thanks for your reply!
So what your saying is that my Wife's phone is as good as being Hard Bricked?
Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
For now it seems its hard bricked, but if u never got root on it or if your knox trigger is 0x0, and u got this far with brick, then your operator or samsung is responsible to fix it no matter what, stay on what you say and push them saying you didnt do anything and that you enabled knox protection thus Odin flash fails. Say to them with a more serious speech and deeper speech like you its kinda feeling that you seem like you are angry. Tell them you need asap phone and replace it asap. You can even say to diagnose the phone and see that you didnt do anything illegal (root proccess) or dropped phone.
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
EDIT: This knox protection is additional optional protection, and is not must, so u know. Its impossible to turn it off without getting into your Settings app and disable it manually.
Skickat från min SM-G900F via Tapatalk
Sachitoge said:
Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
. . .
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
I talked to the voice tech support and they said that i should first try to image the operating system at the BestBuy store. If I can't get it to work then to send it into them and they will do a "free" evaluation. However since i started with a good phone, they are liable. Although they may try and get me to pay for fixing it
As it is, should i really send it to them? Or is there any other software solution, or a JTAG??? (not sure all that would involve)
Thanks!
Look, that knox protection is as good as Apple's remote iCloud lock function. It is encrypted, and it requires decryption of the system partition (i may be wrong, i just say what i believe is/can be). The Knox is a type of a Encryption, it's really secure and safe and is used widely worldwide, the decryption is hard because it must be protected with your samsung account and password, because it required that during enabling it. This indicates it is encrypted according to your specified Samsung account. I may be wrong, but try to find on internet whether it's possible to disable it remotely. Try to boot phone normally, then go on PC/Laptop and search to login to Samsung account and by any chance, look to remotely unlock this Knox security.
Other than that, without access to "Settings" app, you wont be able to disable it. Simply impossible. It is encrypted.
Same for iOS Devices that got locked with remotely iCloud lock app, it is locked and encrypted remotely and requires remotely decryption to system partition and this is why almost nobody can bypass it. There are ways but sadly are private from public to prevent Apple team patch the exploit. I do believe they use this exploit for iDevice that is stolen to afterward sell to another end-user the stolen phone, or possibly they could be unlocking devices in exchange of money. Easy money from my view, however, it is encrypted and is no way possible. MAYBE samsung can do it from their end without saying "we decrypted it and did clean install rom" instead of that, they will speak in a manner speech like "We did put the phone into a developer-only software from our end on our PC and did a full disk-clean which also killed all files, and had to re-attempt to install rom and reconfigure IMEI". Maybe not exactly like this but something close this. From what i know, whenever you do full clean, your IMEI mostly stays, this is because you mostly cant really navigate it manually or delete it, usually it is protected lol.
I hope you're not tired with this long message, you shouldn't be charged for such a mess they caused to you, so like i said, dont let your guard down and hesitate, stay behind your phrase/word! I promise, it will work!
You mentioned Voice Tech Support, talk serious, talk that you are not tech heavy, (for ur wife). Play a bit stupid-role about technology and that it happened while OS Upgrade.
Remember, they will be after your money, don't let them do it and get cash into their pocket for free, it's not worth and not your fault to cause you being charged!
Please, try my method and you will see it really saved you a couple 10 dollars. As of sending the phone, im not sure, they wont however pay the shipping fee, other than that any other cost is unacceptable so beware, dont get phished from IT experts.
Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.
I recommend not using Odin to flash any ROMs at this point.
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
audit13 said:
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
You are right, it could be, i dont know how things really work in USA as i always bought unlocked phones and living in europe, so it was good to point that out. The error do happen while knox protection is on too, same type of message so its a bit tricky...
Skickat från min SM-G900F via Tapatalk
I have never seen Knox protection cause that error. I don't think it is not Knox that is stopping the flash, it is the bootloader security.
The only protection that I have seen that would have an effect in download mode would be re-activation lock.
Sachitoge said:
. . . other than that any other cost is unacceptable so beware, dont get phished from IT experts. . . Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.
Click to expand...
Click to collapse
Thanks for your long reply! and in helping me with this issue. I will be firm with them. My wife is not tech savvy and I don't know how my wife's phone got encrypted, or if there was someone remotely hacking her phone from our PC or over the wireless. She always complained to me that someone was listening in on her conversations and interfering with her text messages. And we had some evidence this was taking place. She does not know how to encrypt her phone, so she didn't enable knox encryption. So perhaps her phone was hacked somehow.
On the download screen of the phone this is what I am getting:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECURE BOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Downloading.......
Does this mean anything to you that could possible help knowing what the problem is?
I see nothing to indicate that the phone is encrypted.
The existence of the warranty bit line tells me the phone has at least a 4.3 bootloader which caused the Odin flash to fail: the ROM being flashed has an older (probably 4.1.1) bootloader.
Knox and encryption are not the same thing. Encryption can take place in the absence of Knox and Knox can be present on a non-encrypted phone.
Whether the phone is or is not sim-locked isn't relevant to this situation as it can happen regardless of a phone's sim-lock status.
audit13 said:
I recommend not using Odin to flash any ROMs at this point. . . The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file. . . There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates. . . I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
Thank you for your suggested solution! I have an Identical phone to my wife's phone. Is there anything else useful i can grab from my phone? The info App states:
Model: SAMSUNG-SGH-I747
Device Type: d2att
Product Name: d2uc
Country origin: MADE IN CHINA
Manuf. Date: 2012.08.31
Knox Warranty Void: 0x0
Storage: 16 GB
Product Code: SGH-I747RWBATT
Orig CSC Code: ATT
Firmware CSC Code: ATT
Active CSC Code: ATT
CSC Country: USA/US
Mobile Operator: AT&T / 310410
Bootloader Version: I747UCUFNJ2
PDA Version: I747ATTFNJ2
Baseband Version: I747UCUFNJ2
Latest Firmware: Not Found
Kernel Version:
3.4.0-1514807
[email protected] #1
32-bit
Java Virtual Machine: Dalvik 1.6.0
Root Existence: No
Android Version: 4.4.2
Build Number: KOT49H.I747UCUFNJ2
Build Fingerprint: samsung/d2uc/d2att:4.4.2/KOT49H/i747UCUFNJ2:user/release-keys
Build Description: d2uc-user 4.4.2 KOT49H I747UCUFNJ2 release-keys
Build Date: Mon Aug 10 14:43:43 KST 2015
Changelist: 1514807
Hardware / Board: qcom / MSM8960 [32-bit]
Platform / Chip: MSM8960
GPU: Qualcomm Adreno 225
Modem Board: MSM8960
Hardware Revision: REV0.4
Firmware: KIES SYMBOL --- I747UCDLK3 --- date: 2012-11-01 ---- USA (ATandT) ---- Version: 4.1.1 --- CSC: I747ATTDLK3
Your phone is running the latest ROM as indicated by the nj2.
The line about kies, where did that come from?
audit13 said:
Your phone is running the latest ROM as indicated by the nj2.. . . The line about kies, where did that come from?
Click to expand...
Click to collapse
That line came from the Firmware Browser page of the Phone INFO *Samsung* App.
Is it possible to extract all the files I need from my phone and burn them over to my Wife's semi-bricked phone?
Nope, that won't work.
If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed.
Flashing the wrong bootloader and modem file could hard brick the phone.
audit13 said:
Nope, that won't work. . . .If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed. . . .Flashing the wrong bootloader and modem file could hard brick the phone.
Click to expand...
Click to collapse
I am still new here, and although I am a computer programmer, a lot of the terms are foreign to me.... i understood the custom recover and the custom ROM but what is the "baseband" that needs to be determined? Can i get the baseband information from my identical phone?
The baseband or modem is software installed on the phone to control its functionality. The last 4 characters of the baseband/modem should match the last 4 characters of the bootloader.
From your post above, notice the fnj2:
Bootloader Version: I747UCUFNJ2
Baseband Version: I747UCUFNJ2
The bootloader and baseband/modem will change as you upgrade the phone's ROM.
If the soft-bricked phone has the mjb bootloader and you try to flash an lk3 bootloader, this will probably hard-brick the phone because the lk3 bootloader is an older bootloader. The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.
audit13 said:
.......The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.
Click to expand...
Click to collapse
So why not just flash her phone with the newest bootloader available?
If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. Also, I am not sure if the modem and bootloader need to be upgraded in release order. I wouldn't think so since I have flashed the Canadian version of the s3 (i.e. i747m) from 4.1.2 to 4.4.2 with no problem.
Always flash the bootloader and modem in the same session before rebooting. Don't flash a modem, reboot, and flash a bootloader as this could also cause a brick.
NOTE: flashing a custom recovery will change the warranty bit from 0 to 1 which will tell a Samsung tech that non-official software was installed on the phone and you may wind up with no recourse against Samsung.
I recommend this if you will not be pursuing the matter further with Samsung: install a custom recovery, boot into recovery, wipe cache, and reboot the phone. Hopefully, clearing the cache will allow the phone to boot as I think it is still stuck in a boot loop.
If the phone still will not boot and you have not back up all of the data, boot to recovery, mount the data partition, connect the phone to a computer, copy off what you need, wipe/format the data and cache, then reboot.
audit13 said:
If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. ... ... ...
Click to expand...
Click to collapse
I am willing to try it. Do you know a thread i can follow or how i can get some instruction on creating and flashing a custom recovery? Also..... i still have the option to bring the phone over to BestBuy store who is a Samsung tech center. I am not sure if they can do anything other that what I have already tried
I just picked up an unlocked Snapdragon S9 and it immediately updated to Android 10, One UI 2.0, which is cool, but it's got a bunch of Sprint bloatware included that's just annoying. If it matters, I'm planning on using Google Fi but haven't activated it yet.
Is there a debloated version available anywhere?
Either debloat yourself or perhaps flashing xaa firmware (u to u1)
longebane said:
Either debloat yourself or perhaps flashing xaa firmware (u to u1)
Click to expand...
Click to collapse
Interesting idea, going from U to U1 is a factory wipe, right? So this would be the time to do it before I start setting up my new phone. I might just check that out, thank you.
thinksnow said:
Interesting idea, going from U to U1 is a factory wipe, right? So this would be the time to do it before I start setting up my new phone. I might just check that out, thank you.
Click to expand...
Click to collapse
no factory wipre required at all man. When flashing there are 4 files that Odin needs, the firmware set supplies 5 files. 2 of them are CSC files. CSC and HOME_CSC. Flashing CSC will wipe it clean, flashing HOME_CSC wont wipe anything, itll just install the firmware behind the scenes and voila! You have a "unlocked" S9
Youdoofus said:
no factory wipre required at all man. When flashing there are 4 files that Odin needs, the firmware set supplies 5 files. 2 of them are CSC files. CSC and HOME_CSC. Flashing CSC will wipe it clean, flashing HOME_CSC wont wipe anything, itll just install the firmware behind the scenes and voila! You have a "unlocked" S9
Click to expand...
Click to collapse
Well skibidi do-da, that's good news. I don't recall where Id' read that it was no problem to flash a U1 on a U device, but that doing so would wipe your phone. Again, it's not an issue for me since I knew I was going to be putzing with the ROM anyway and haven't set anything up, but in the future, that's handy information.
thinksnow said:
Well skibidi do-da, that's good news. I don't recall where Id' read that it was no problem to flash a U1 on a U device, but that doing so would wipe your phone. Again, it's not an issue for me since I knew I was going to be putzing with the ROM anyway and haven't set anything up, but in the future, that's handy information.
Click to expand...
Click to collapse
yup. its absolutely possible. I flashed the U1 on my G960U with the HOME_CSC about 7 months ago, no issues since then. Also, no factory reset since i flashed that either. I was gonna flash the regular CSC this weekend, but i ended up replacing the front door windows in the younger kiddos sedan. LoL. It was a blast, i promis
Attempting to flash G960U1UES7DTB2_G960U1OYM7DTB2_XAA (using Home, not CSC) over G960USQU7DTA8 and ODIN is showing this:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 6926 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You might want to hold off on flashing this update - it's causing weird problems on my T-Mo S9. I knew Samsung/Android was going to start going after how many apps need the Accessibility Service to work, but it seems like this update just took out a whole slew of my apps at their knees. I'm still researching...
https://www.gottabemobile.com/samsung-galaxy-s9-android-10-problems-5-things-to-know/
Help me understand thisplease, guys.
Youdoofus said:
no factory wipre required at all man. When flashing there are 4 files that Odin needs, the firmware set supplies 5 files. 2 of them are CSC files. CSC and HOME_CSC. Flashing CSC will wipe it clean, flashing HOME_CSC wont wipe anything, itll just install the firmware behind the scenes and voila! You have a "unlocked" S9
Click to expand...
Click to collapse
So, I have my S9 (SM-G960U) - AT&T phone, I want to use it on my T-mobile account. This Odin process will unlock the sim option?? This is what I need if so.
And if this is the process, which thread will be the best to follow here?
Thanks,
Rita
IntellaGeek said:
So, I have my S9 (SM-G960U) - AT&T phone, I want to use it on my T-mobile account. This Odin process will unlock the sim option?? This is what I need if so.
And if this is the process, which thread will be the best to follow here?
Thanks,
Rita
Click to expand...
Click to collapse
No it will not unlock he sim. Either ask att or find a paid service which we dont talk about or provide here