I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.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> 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)
Click to expand...
Click to collapse
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Fuzz21 said:
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Click to expand...
Click to collapse
Yeah, I'm reading this now. I just did what it said, but still no dice.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
I had a problem with mine where Odin wasn't doing anything at all. It would start but never finished. I changed the USB port and was good after that. Weird because my sgs2 and sgs3 international were fine using the one USB port. Just a thought to try a different port if it stops or fails
Sent from my SGH-I747M using xda app-developers app
brfield said:
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
Click to expand...
Click to collapse
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Problem solved!
JibbsIsMe said:
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Click to expand...
Click to collapse
OK, I got it. First, I followed this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I stopped right after step 8. I then put my Ext SD into my old phone, formatted it, and put on this: http://forum.xda-developers.com/showthread.php?t=1732191
Then I went into recovery, and flashed that ROM. Then rebooted, and I'm fine now! YAY!
I almost wasted $730....
--Jeremy
Awesome stuff !!
Mine is still a 500$ paper weight, LOL hopefully I can fix it :S
Good luck, I would hate to lose my phone on it's first day...
JibbsIsMe said:
Good luck, I would hate to lose my phone on it's first day...
Click to expand...
Click to collapse
Thanks budd
I really hope I can resurrect it from the Dead.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
I hate to threadjack, but this is the only thread I can find mention of this error with the sgs3 with.
mine did the same thing last night, thought I bricked.. but it didnt brick, used the phone all day today with no problems, tried to root again today with at&t method with odin, and I keep getting the same error. Its a bell i747m using odin 3.0.7
Any ideas?
Edit: Also I have tried several usb ports and a couple different cables.
Related
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Sent from my GT-I9100 using xda premium
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
alexkno said:
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
Click to expand...
Click to collapse
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
UltimateAnas said:
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Click to expand...
Click to collapse
pilgrim011 said:
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
Click to expand...
Click to collapse
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So the binary counter is not stuck as I had mentioned earlier. But it still got stuck at the NAND write step.
From what I understand, the kernel does change from "Samsung official" when I flash stock ROM to "Custom ROM" when I flashed Siyah and back to "Samsung official" when I re-flashed it. But it gets stuck after that. Any ideas why?
Thanks
insat3d said:
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So it is not stuck as I had mentioned earlier.
Any other ideas guys?
Thanks
Click to expand...
Click to collapse
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Click to expand...
Click to collapse
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
insat3d said:
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
Click to expand...
Click to collapse
have you tried everything there?
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
have you tried everything there?
Click to expand...
Click to collapse
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
I don't think so. You might have to replace your motherboard.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
if I am not mistaken JTAG will give access to core, but I guess (but I am not a technician) that if the internal storage is corrupted and not even repartition helps, then I guess only replacing it might help.
I'd advise to watch out for a repaircenter near you and ask
Ok...so the phone is 2 months old.....
Purchased in India but being used in the US?.......
I don't care what Samsung says.....it sounds to me like they are trying to 'fob you off'. I personally would take this further. ....contact Samsung HO, contact your local trading standards department (or whatever it's called).
No warranty. ....that's just corporate bulls**t.......the age of the phone (if it can be proved) is what's important.....I think you have a very strong case here.....go with it.
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Similar problem i9100T
I have the same problem in that the phone stops at nand write when attempting to install package. I can only get into download but it will flash a bootloader but that is all. I believe that it may be necessary to reload the .pit file but I cannot find where this would be found. I presume if this were included it would reinstall this and would fix the internal storage. Any advise on this would be gratefully received.
Galaxy S2 stuck at NAND WRITE START
MODS.... please delete this post.
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
'<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Baraa01 said:
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
' Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Heya!
Your SIII looks bad with this stripes!
Have you flashed your StockROM via Odin while you were in DownloadMode? If it don't be in DownloadMode, it also can't be flashed.
Try to download a firmware from samfirmware.com and to flash it via Odin in the PDA field while your device is in DownloadMode!
And when you have finished, go to Recovery and Wipe your Data&Cache!
Greetings...
Sent from my GT-I9300 using xda app-developers app
Of course I used ODIN to flash stock rom, it didn't work.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Of course I used ODIN to flash stock rom, it didn't work.
Click to expand...
Click to collapse
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
TheRealFelix0212 said:
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you read my first post, yes, I did flash it in Download Mode via ODIN.
Well, it obviously had a problem writing the rom into the phone (nand write failed). You may have a hardware fault. Do you have the nand chip that suffers from sds?
Sent from my GT-I9300 using xda premium
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
ratatattata said:
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
Click to expand...
Click to collapse
Still failed in ODIN. You reckon the eMMC chip is damaged?
Baraa01 said:
Still failed in ODIN. You reckon the eMMC chip is damaged?
Click to expand...
Click to collapse
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
jmpmjmpm said:
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Same isssue here, same screen and everything.... I tried for over a month and nothing... got an expensive door steep. If you have any lights about this... let me know!!
try flashing recovery only and then flash 3.8 again through recovery.
try flashing the resurrection rom from the checkrom site through odin in download mode..
galaxys3lover said:
try flashing the resurrection rom from the checkrom site through odin in download mode..
Click to expand...
Click to collapse
Been there, done that. Nothing happens. Same error, Re-Partition failed.
please help?
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
I hope I've not ended up with this phone mentioned in this thread....purchased a phone from ebay and the seller said its stuck on Android SIII logo...I can get into download mode but before I attempt anything can someone tell me if this is a UK phone so I can apply the correct ROM (if it works!).
Also, currently the phone does not charge, battery is fine as i've tried the battery from own s3 and vice versa...both batteries are fine but the phone does not appear to charge...I'm hoping this is ROM related....
Any help will be much appreciated otherwise its an expensive gamble!
BTW...In the download mode the product bit is blank and does not say Samsung galaxy s3 like my own working phone does...
Hello,
I have a problem unrooting/unbricking my Galaxy S4 for Verizon. I followed step-by-step processes and it seems to not work properly for me. I downloaded "Odin3 v.1.85" and the stock firmware, "GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip" and "SCH-I545_MDK_562219_Stock_Restore.tar.md5" for Verizon. I put my phone into the Download Mode and began the process of unrooting using Odin. I made sure that my device was connected. I clicked PDA and chose the stock firmware for my phone. I clicked Start and it begins. As soon is it begins, it says it is not responding, but I wait a few seconds and it responds. After that, it continues where it left off for the unrooting process. The process turned out to be a fail. Here's the message:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It has failed and when I attempt to reboot my phone, it gives me a message that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I attempted the Kies process, and it would not connect my device to Kies. Please help. I feel as if I were the only user with this problem. Thank you.
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Seems like it's tough luck for me. What do you suggest I do? Did you resolve any of your similar issues?
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
goosedaddy said:
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
Click to expand...
Click to collapse
Alright. I'll follow these steps and I'll get back to here and let you know. Thank you.
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
MattLife said:
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
Click to expand...
Click to collapse
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
goosedaddy said:
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
Click to expand...
Click to collapse
This really helped me! Thank you so much! It's been fixed.
MattLife said:
This really helped me! Thank you so much! It's been fixed.
Click to expand...
Click to collapse
Awesome! Glad it all worked out.
help
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
gregorykbrownjr said:
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
Click to expand...
Click to collapse
if you can't get the usb port (charging port) to work with communicating to your computer then there really isn't much you can do. Have you tried cleaning the contacts off inside the port? Are you sure its NOT the cable?
This has been talked about somewhere else here in this forum
Same problem
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Hey I have the exact same issue but with the international LTE galaxy s4 do you have any idea what i can do i have put the GPE rom on this and i found that flashing TWRP when it gave me the kies error bought me back to my GPE rom i'm going to sell this phone and i need to return to stock firmware should i try a new computer or something else please help me i've been really scared, i would appreciate it if you can help me in any way.
Okay, A little background quick! I just signed up for XDA because I have been lurking all day, and everyone seems to have their problems solved fairly quickly. Unfortunately none of the fixes here have helped me.
I was running KitKat for a while on my Verizon Galaxy Note 2 SCH-I605. I started having trouble with my SD card and it seemed my only route to fixing it was to root. Initially I was ignorant and used some one click solution. It certainly rooted my device, but it did not unlock my bootloader and when I tried accessing CWM Recovery my phone soft bricked. I proceeded to download ODIN and my phone's stock firmware. I flashed it and fixed my phone.
At this point I should have said goodbye to rooting, but I am a stupid stupid man. I flashed a rooted stock for my phone and it worked, but once again running CWM soft bricked me. I tried a few different things, rooting and trying to get things to work - flashing stock whenever I soft bricked again. Eventually, for whatever reason, ODIN froze when flashing STOCK. This was right around where I was giving up on the whole escapade. I an Install Firmware error and a message for KIES to repair it. I looked online, but none of the methods seemed to fix it. VZW Upgrade Assistant didn't help, and KIES won't either.
The Crux of the Problem:
I managed to get my phone in download mode and in a state of relief flashed stock to fix my phone and leave this all behind. Odin flashed, it all went well. I was very careful to follow the proper steps to ensure a proper flash of stock. Odin went through all its steps, my phone went to reboot. This time odin said PASS! before my phone finished rebooting. Now my phone is just sitting on the screen that says "Samsung GALAXY Note II". I can get to the download screen still, but I can not get to recovery to factory reset.
I know I screwed up on this, please don't tell me everything I should and shouldn't have done. I know i shouldn't have done any of this. I just want some help putting this behind me, whatever the cost. Please help me out guys!
Guys
Please help! I absolutely need my phone, and my only alternative is buying a new one. My older phones have batteries that last 5 minutes tops. Please help me here! I don't have Almost a grand for a new phone!
OMG
I got it! Fixed! After 7 hours of deep searching and experimentation I found the cure for my phone! All the things I was doing! It was so simple! Unfortunately it landed me back with KitKat Stock (Whatever, I'll deal with it), but it saved me. I flashed 4.3 Stock that I got from SamFirmware!
This is a newer firmware than I had before, but so be it! I'm so estatic!
Thank you guys! A lot of the info I found tonight was throughout the forums. No one thing here fixed my issue, but a combination of the threads here brought me to this conclusion! You guys are the bomb! Have a wonderful day!
Good job man
Sent from my SCH-I605 using Tapatalk
And your method was???? lol... I was helping my friend unroot from stock rooted with twrp, and my method was to start fresh with a stock 4.3 i found at samsfirmware. I used odin 3.09 and all went well until it finished and was boot looping (more of a flash). I tried the normal go to recovery and wipe davlik and factory reset but i cant get into recovery. So next i tried to re flash and once that didnt work i made sure my note 2 drivers were up to date. And here I am still cant flash and cant figure anything out and still cant flash. Below is what it shows for me, but yea if you could share what you did it would be so helpful!
:<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)