[Q] "Firmware Upgrade Encountered and Issue" - Sprint Samsung Galaxy S III

Hi. I tried following a simple guide to rooting my S3, but it failed horribly. I followed the steps (download Odin+this file, load the file into Odin, hit Start and bam your phone's rooted) but it failed. Here's the log from Odin.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Now my phone won't run properly, it says to run Kies in recovery mode or something but I don't understand. In retrospect I should've downloaded Kies onto my computer first, as well as SU onto my phone, and I probably should've found out my model number, but here I am.
I'm not trying to install a custom OS, I just want root access so I can use root-only apps. Can anyone tell me how to save my phone?

if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward

You may just have bricked your phone, because that package was for the international variant.

relieved
jdelano said:
if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward
Click to expand...
Click to collapse
Wow, thanks a lot man! I will be sure to!

seb0910 said:
Wow, thanks a lot man! I will be sure to!
Click to expand...
Click to collapse
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171

jdelano said:
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
If it's a true brick then that won't work, because in a real brick the phone doesn't even turn on. When that thread refers to a brick, it's really referring to a soft brick which is easy to recover from.

yes, I am assuming soft because the OP said "Now my phone won't run properly", not it won't turn on. I know its bad to assume but I took the leap any way

Related

[Q] i317 at&t soft bricked, please help!

Ok, I know someone is going to yell at me. I have searched for 24 hours on this site before deciding to post. Please don't verbally assault me too badly. Here is what happened, overnight, the phone must have gotten an OTA update. It is now frozen at the Samsung Galaxy screen.
I cannot get to CWM which I did have on 4.1.1
I can only get to download / ODIN mode (vol down, home, power.) So I downloaded Odin 3.07 (the newest i think)
I downloaded KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 (AFTER A LOT OF SEARCHING!)
I can get Odin to see my phone, com4, I put the above file in PDA and eventually get this....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong? Is it the wrong file I am trying to flash? Is there any way to get CWM back? Because I do have semi recent backups. ANY help would be appreciated. I'm pretty much willing to pay somebody at this point.
Thanks and sorry if I missed the thread on this. I REALLY tried via google and internal XDA searches
- Keith
AT&T Galaxt note 2
Hoping those keywords garner more attention. I am still stuck with a non working phone and my SIM is in an iPhone 4s..... yuck
Also I have a PIT issue?
keithh85 said:
Ok, I know someone is going to yell at me. I have searched for 24 hours on this site before deciding to post. Please don't verbally assault me too badly. Here is what happened, overnight, the phone must have gotten an OTA update. It is now frozen at the Samsung Galaxy screen.
I cannot get to CWM which I did have on 4.1.1
I can only get to download / ODIN mode (vol down, home, power.) So I downloaded Odin 3.07 (the newest i think)
I downloaded KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 (AFTER A LOT OF SEARCHING!)
I can get Odin to see my phone, com4, I put the above file in PDA and eventually get this....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong? Is it the wrong file I am trying to flash? Is there any way to get CWM back? Because I do have semi recent backups. ANY help would be appreciated. I'm pretty much willing to pay somebody at this point.
Thanks and sorry if I missed the thread on this. I REALLY tried via google and internal XDA searches
- Keith
Click to expand...
Click to collapse
At least with the MD5 file I am trying to load, It says I need a PIT file. Which I have downloaded, but it just sits there for what seems like forever then gives me this error....
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
keithh85 said:
At least with the MD5 file I am trying to load, It says I need a PIT file. Which I have downloaded, but it just sits there for what seems like forever then gives me this error....
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey, I used to flash my phone like 3-4x a week and the I bricked it, this video helped me get back on my feet, hope it helps. Just go from there as a base and then you flash whatever you need to install on your phone. Good luck!
http://www.youtube.com/watch?v=WwNOAgopXvc
Pit file? I have found 2 PIT files. neither work
Looks like my phone needs to be re-partitioned also? I am completely lost. Reading some of the threads that might mean my internal memory went dead. Anyone?
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
keithh85 said:
Looks like my phone needs to be re-partitioned also? I am completely lost. Reading some of the threads that might mean my internal memory went dead. Anyone?
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Try different USB port.
2) did you put your md5 file in a folder? If so check folder name.
3) Run odin as admin
reply
A_youu said:
1) Try different USB port.
2) did you put your md5 file in a folder? If so check folder name.
3) Run odin as admin
Click to expand...
Click to collapse
Yes to all 3.... I read something about SDS (Sudden death syndyronme) on galaxy phones. I think that's what happened. I really don't know but I cannot flash anything without needing pit file.
keithh85 said:
Yes to all 3.... I read something about SDS (Sudden death syndyronme) on galaxy phones. I think that's what happened. I really don't know but I cannot flash anything without needing pit file.
Click to expand...
Click to collapse
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Thanks for the reply, I will try a 4.3 rom
A_youu said:
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Click to expand...
Click to collapse
ODIN MODE (red)
Product name:
Current Binary: Samsung Official
System Status: Custom
Android guy
Downloading...
Do not turn off target!!
your other question...
A_youu said:
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Click to expand...
Click to collapse
Yes, AT&T kept telling me I needed to update. I would try to kill the screen but it would keep popping up over and over. So I finally let it download with the intention never installing it. I guess it did it without my knowledge.
PIT file....
I finally got ODIN to make some progress... But I do not know what to do from here. Picture attached.
keithh85 said:
I finally got ODIN to make some progress... But I do not know what to do from here. Picture attached.
Click to expand...
Click to collapse
Ok, Can you try to flash new stock rom? You can follow here - http://forum.xda-developers.com/showthread.php?t=2589891
Also, make sure that you don't flash "AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)" bootloader as this bootloader is only for 4.3 leaded version.
Failed
A_youu said:
Ok, Can you try to flash new stock rom? You can follow here - http://forum.xda-developers.com/showthread.php?t=2589891
Also, make sure that you don't flash "AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)" bootloader as this bootloader is only for 4.3 leaded version.
Click to expand...
Click to collapse
Same result... Here is the screenshot.
keithh85 said:
Same result... Here is the screenshot.
Click to expand...
Click to collapse
When Odin fails, are you getting any message on the phone itself? If you look in the top left corner it should display some information. Mine will usually give me a message when Odin fails.
phone screen
cameron213 said:
When Odin fails, are you getting any message on the phone itself? If you look in the top left corner it should display some information. Mine will usually give me a message when Odin fails.
Click to expand...
Click to collapse
No the phone never changes.
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
flymacs said:
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
Click to expand...
Click to collapse
I will give it a shot. I have nothing to lose at this point. I've been on an iPhone for 3 days now
flymacs said:
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
Click to expand...
Click to collapse
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
keithh85 said:
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
Click to expand...
Click to collapse
Do you have pit file? If so try to give all files together in Odin -
pit file in "PIT" & select re-partition checkbox
ROM in "PDA"
and try to flash.
keithh85 said:
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
Click to expand...
Click to collapse
Had posted a possible solution for you over on general then saw this thread...
http://forum.xda-developers.com/showpost.php?p=49378159&postcount=62
Includes link to the pit file

Flashing stock rom with odin, "stuck" at system

The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1
griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.
Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.
griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.
Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?
Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.

[Q] SGS3 - Problems trying to return to stock

Hello All,
I have a white Samsung Galaxy S3 (SGH-i747m) The Canadian Rogers version.
Previously was running cyanogenmod and cwm recovery. This phone has been headaches since I bought it, with frequent crashes, freezing, overheating, etc. even before I ever rooted or changed roms, but that's another story.
I'm hoping to return to stock and get rid of it. I used odin 3.0.7 to flash a rom I downloaded from sammobile.com. Everything seemed fine, then last night it crashed, and hangs on reboot. Trying to boot to recovery gives kernel panic.
Now im trying to flash again. it starts to work, I see the progress bar on the phone, and then it fails every time:
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Write)
phone says ODIN: flash write failure
I have tried several roms now and am not 100% sure I have the right one even though it worked once. can someone point me in the right direction so I can at least be totally sure I'm flashing the right thing? Having the canadian version seems to make it difficult.
perhaps I need to repartition but I understand that it's super dangerous and I have no idea where to find the proper pit file anyway.
any help? thank you.
Today I tried the firmware I downloaded from here: http://forum.xda-developers.com/showthread.php?t=1968625
same issue. Also tried two other computers last night. If anyone could help it would be much appreciated. Kinda desperate here as this is my only phone. thanks!
Try different USB cables as well as every USB port on the computer.
Can you copy the entire Odin text from its message box?
Also, what is your current firmware build, and which ones have you tried flashing?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks DocHoliday,
I've tried multiple cables, ports, and computers. I wish I could remember exactly what I flashed, but I've got firmware downloads all over my desktop. Here's my output from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYAEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
the firmware I'm trying to flash now is "I747MVLUEMK5_I747MOYAEMK5_I747MVLUEMK5_HOME.tar.md5" The one I had flashed previously was one of these:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
I747M_RWC_I747MVLUFNE6_I747MOYAFNE6_Original
KIES_HOME_I747MVLALE8_I747MOYAALE8_20120523.225040_REV04_user_low_ship.tar
Whichever it was, I know it was stock samsung and was kitkat. I hope that answers your question. I was playing around with Heimdall today and was able to extract a pit file, if that could be of any help.
OK, just fyi, the only kk one listed there is the NE6 pkg.
You can try using the pit file if you like, shouldn't hurt to try it. I've got an I747 one here: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=6471
Don't know if it'll work on yours or not, but the partitions are the same so it shouldn't matter.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Ok. I'm getting access denied while trying to follow your link. How can I get permission?
Try this one
https://www.androidfilehost.com/?fid=23060877489996938
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I think my phone is bricked

Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out
gfp11289 said:
Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out
Click to expand...
Click to collapse
You have a dev edition or retail?
Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point
gfp11289 said:
Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point
Click to expand...
Click to collapse
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.
jcip17 said:
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.
Click to expand...
Click to collapse
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo
gfp11289 said:
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo
Click to expand...
Click to collapse
You can't flash stock roms (.zip files)in ODIN. They need to be .tar files
First check under your battery it should say developer device. If not you have a retail version. If you do have developer edition try to go through these steps and hopefully you will be okay. .
http://forum.xda-developers.com/note-4-verizon/development/how-to-custom-recovery-root-t2923340
If you have a retail version try this.
http://forum.xda-developers.com/not...nt/verizon-note-4-firmware-odin-file-t2926827
You said you accepted the lollipop update when you were on Kit Kat?
I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P
gfp11289 said:
I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P
Click to expand...
Click to collapse
Woh don't do anything I said. You're in the wrong forum
Try to seek help here
http://forum.xda-developers.com/note-4-sprint​
Oh shoot I didn't even realize I was in the Verizon forum. Sorry
gfp11289 said:
Oh shoot I didn't even realize I was in the Verizon forum. Sorry
Click to expand...
Click to collapse
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !
jcip17 said:
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !
Click to expand...
Click to collapse
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?
gfp11289 said:
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?
Click to expand...
Click to collapse
Yes definitely just do an advance wipe and wipe data, system, cache, and dalvik cache before. But don't confuse TWRP with the stock recovery. TWRP is a custom recovery.

Galaxy Note 2 T889 stuck with the logo

I have a Galaxy Note 2 SGH-T889. I have spent the past week reading and trying suggestions on this forum. I downloaded kies but it gets stuck connecting to the phone. I have tried several versions of odin. It gets to sboot.bin and write fails. I have tried the original firmware which took 2 hours to download. I refuse to pay for the upgrade in download speed for something I only need one time. I have tried the pit and firmware combination. The only thing that seem to register anything on the phone was when I tried the modem.bin.....it had a blue progress line but then it failed. I am starting to think it is a hardware problem.
How did it start? The phone was sitting on the desk when it came on and restarted. Then it stop when it got to the Galaxy Note II logo. I can get it into Download Custom OS mode but it will not go into recovery mode. Prior to that I had to data wipe and factory reset because it was having the logs process stopped and other processes popups. I had to wipe and reset about 3 times prior to the failure.
I was using the plain old firmware. I think the phone auto updated to the 4.3. I did not install any custom os. I just use the phone as a phone, the calendar and the camera pretty boring stuff. Did not know anything about odin, kies, soft brick, hard brick, jtag, emmc or sds prior to the failure. Not sure exactly what the difference is between t889, n7100, n7105 or n7108. I have downloaded the android toolkit and tried several of those options but it says to enable debugging but I have no access to the settings on the phone to enable debugging.
The way the phone crashed makes me think it had a hardware failure. If there is anything else I can try, I am willing to try anything.
Eva
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
andytiedye said:
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I am wondering if the phone was doing an auto update and got stuck in the process. I had my phone set to auto update. Maybe that is a mistake...I guess I should have made it ask before it updated at least then I would know what cause the problem.
Eva
Note 2 sgh-t889 boot.bin error
audit13 said:
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
zevacat said:
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
Click to expand...
Click to collapse
Ok it finished downloading. I ran it with odin 3.12. This is the results.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
audit13 said:
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
Click to expand...
Click to collapse
That try was with the odin 3.12 using the ap slot. I did try 3.07 pda and the 1.87. Yes it is a a tar.md5 file.
Had an interesting occurrence. I restarted the laptop while the phone was connected to the laptop and the laptop went into an infinite start loop. At first I thought, oh great now the laptop is broken....:crying: But then I unplug the phone and the usb cable. The laptop started normal. I plugged the cable in and it still restarted without problem so whatever black hole the phone is in....it will pull in all connected device into the abyss.
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
audit13 said:
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
Click to expand...
Click to collapse
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
I recommend flashing the most recently released stock rom, not earlier releases.
zevacat said:
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
Click to expand...
Click to collapse
I can't seem to find an earlier versions all the 4.1. All the links come back as file not found. They did have a gt n7100 unbranded 4.4.2 kit kat N7100_ITV_N7100XXUFOE1_N7100ITVFOF1.zip so I am waiting for it to download. It says it will take about 2 hours. Or is there some other version that would be better? and where can I find it. Rapid Gator really stinks as far as downloads.
Eva
Flash the latest 4.4. Try updato.com.
audit13 said:
Flash the latest 4.4. Try updato.com.
Click to expand...
Click to collapse
They don't have a 4.4 for the sgh-t889 so which one would work best out of the other options 7100, 7105 or 7108?
Eva
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
audit13 said:
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
Click to expand...
Click to collapse
4.3 gets stuck after the sboot.bin. audit13 said "the bootloader in the ROM is not compatible with the phone "....so if the bootloader in the sgh-t889 is not compatible then I need a different bootloader don't I? Not sure where to find a different bootloader.
Eva
The only thing I can suggest is taking it to a cell shop that can flash it via jtag.

Categories

Resources