Related
**** 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
i have a galaxy s 4 verizon i have mdk and i have tried unrooting it because my friend tried rooting it while i was gone and messed up the process but im using odin3.07 and im getting this.
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
my phone says start [224,1440]
sw rev. check fail : fused 5, binary 1
and ive tried 2 other stock files and i still get the same thing i even tried a Me7 to please help
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_u ser_low_ship_MULTI_CERT.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> 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/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> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im using Odin v1.85
this what i get from trying mdk and me7
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
he said he followed this youtube video https://www.youtube.com/watch?v=uii_mYm8IGE
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
A1C_Malone said:
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
Click to expand...
Click to collapse
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
scryan said:
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
Click to expand...
Click to collapse
where can i download mj7 or mk2 stock i have a verizon s4
Sounds like you may want to follow this... If a newer firmware was attempted to be flashed..http://forum.xda-developers.com/showthread.php?t=2579278. IF NO LONGER MDK AVAILABLE FOLLOW THOSE STEPS.
A1C_Malone said:
where can i download mj7 or mk2 stock i have a verizon s4
Click to expand...
Click to collapse
use Kies and get a factory clean install
Ok so i rooted my phone a bit back but i keep getting firmware upgrade notifications so i just wanted to unroot and be vanilla firmware. well i tried with Odin and it didnt work so im stuck in Odin mode and i cant get back to using the phone. Please HELP!
Here is my guide.
http://www.androidfilehost.com/?fid=23501681358538464
This does not seem to be working...
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
techguy2002 said:
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i read at it and did what it said. Instructions werent super clear. Is that for the ME7?
not for ME7 but how to get from nc5 to mk2 and back rooted to nc5. I dont know how you would get back to ME7. I saw the post and made the comment and couldnt delete it.
@Radllik
There is no reason to open two threads on the same subject. This thread since it has replies has been moved to the Q&A section where all questions and request for assistance belong.
Your other thread will be locked, please pay attention to the rules in the future.
EFM
Have a great day!
Same, stuck in odin/download mode
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<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> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I'm pretty sure you couldn't reinstall me7 as its no longer signed? Might want to look for full wipe tars for Odin and try that.
Sent from my SCH-I545 using XDA Free mobile app
Vidanl said:
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<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> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
That link does not work on the page you sent. Also i live in Michigan.
the link isn't working
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Vidanl said:
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Click to expand...
Click to collapse
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
they wont pass in odin
k1mu said:
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
Click to expand...
Click to collapse
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Vidanl said:
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Click to expand...
Click to collapse
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
got it working
k1mu said:
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
Click to expand...
Click to collapse
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Same exact problem!
Vidanl said:
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Click to expand...
Click to collapse
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
cashmoneysalad said:
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
Click to expand...
Click to collapse
Verizon S4 16Gb PIT can be downloaded from here http://www.androidfilehost.com/?fid=23269279319199111
Sent from my SCH-I545 using Tapatalk
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
cashmoneysalad said:
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
Click to expand...
Click to collapse
Fused:6 - your phone has the NC5 bootloader.
Binary:5 but you're trying to flash MJ7/MK2.
At this point you can follow Surge1223's directions to back down to MK2 then upgrade to NC5 rooted. http://forum.xda-developers.com/showthread.php?t=2726868
Or, do the same thing using techguy2002's directions: http://forum.xda-developers.com/showthread.php?t=2763834
Working from this thread: http://forum.xda-developers.com/showthread.php?t=2578209
Started with a phone that had the OTA Kitkat update. Tryed this from Surge1223 http://forum.xda-developers.com/showthread.php?t=2726868, didn't work. ended up downgrading (trying) to back MK2 and ended up with phone with no sound.
Came to the " [ODIN][TAR] VRUEMK2 Emergency and No-Wipe Odin tars" thread and tried that. Odin failed on the tar.md5 full wipe file "ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5" as shown in the log below. Tried the pit file too "JFLTE_USA_VZW_16G.pit" just to get the phone to reboot.
At this point I just want a unrooted stock phone. Kitkat would be fine with me, wanted to root for some stuff, but it's not that important right now. Waited for the PASS in ODIN, phone boots fine, still no sound.
Looking for help, thanks.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Sorry, I linked to the wrong original thread. I was trying to get back to MK2. I corrected the title and link to the thread I was using.
The phone is now on MK2, but with no sound.
Surge1223 said "Flash the NC2 hlos for sound to work and use bypasslkm for wifi" in this thread http://forum.xda-developers.com/showthread.php?t=2726868, but I've not found a real clear (for me) description on how to do those. I was hoping to ODIN back to stock and get the sound back.
thanks.
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
montejw360 said:
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
Click to expand...
Click to collapse
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
montejw360 said:
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
Click to expand...
Click to collapse
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
k1mu said:
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
Click to expand...
Click to collapse
saw that come up many times, just never looked at it. good to know, thanks.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Ovreel said:
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Click to expand...
Click to collapse
It's a "desperation move" because it wipes everything on the phone, downloads a factory stock image, then flashes it. Basically, it's a emergency recovery tool that shouldn't be used if you care about what's on your phone.
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_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> Initialzation..
<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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> 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)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> 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)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!