As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.
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
Guys, first of all, if there's an answer for my q in previous posts I apologize and thank beforehand for the directions.
This is the deal, i flashed this rom in my gs3 intl version over mobile odin.
Everything went well, loaded fine and all, and the phone overall is working fine, the issue is, as i tried to inject root over odin on my pc, odin returned me the error "no pit partition" and failed.
Same thing happened as i tried to flash again my previous oficial rom.
Is there any solution for this? Can i get root? How do i go back to my ofw?
Thanks Thanks thanks and sorry again for my inexhaustible search.
Andrew_spiegel said:
Guys, first of all, if there's an answer for my q in previous posts I apologize and thank beforehand for the directions.
This is the deal, i flashed this rom in my gs3 intl version over mobile odin.
Everything went well, loaded fine and all, and the phone overall is working fine, the issue is, as i tried to inject root over odin on my pc, odin returned me the error "no pit partition" and failed.
Same thing happened as i tried to flash again my previous oficial rom.
Is there any solution for this? Can i get root? How do i go back to my ofw?
Thanks Thanks thanks and sorry again for my inexhaustible search.
Click to expand...
Click to collapse
Sounds like you flashed the wrong cfroot. Whats the filename of cfroot you flashed.
Also maybe a screenshot of the failed odin message.
Sent from my GT-I9300 using xda premium
I'll post a screen shot as soon as i get home, all i remember is it says something about the pit partition and it fails.
Its smt like this (got it from a post with a similar error)
<ID:0/007> Added!!
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
I tried both odin 1.8 and 3, same result.
Andrew_spiegel said:
I'll post a screen shot as soon as i get home, all i remember is it says something about the pit partition and it fails.
Its smt like this (got it from a post with a similar error)
Added!!
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Re-Partition operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!
I tried both odin 1.8 and 3, same result.
Click to expand...
Click to collapse
Post the filename of the cfroot you flashed as well.
Sent from my GT-I9300 using xda premium
I dlded it from the zedomax website,
http://galaxys3root.com/galaxy-s3-r...4-2-1-leaked-rom-root-for-galaxy-s3-gt-i9300/
I9300XXUFMB3_I9300OJKFMB3_ILO.zip
Stock leaked fw for s3 i9300
Andrew_spiegel said:
I dlded it from the zedomax website,
http://galaxys3root.com/galaxy-s3-r...4-2-1-leaked-rom-root-for-galaxy-s3-gt-i9300/
I9300XXUFMB3_I9300OJKFMB3_ILO.zip
Stock leaked fw for s3 i9300
Click to expand...
Click to collapse
Hi
you are trying to root 4.2.1. so check if your cfroot version is correct. (CF-Root-SGS3-v6.4.tar)
And how are u flashing official rom? which files are u using?
i'm using that root file you mentioned.
I also tried flashing another stock rom, 4.1.2 but didn't work.
ficti0n851 said:
Post the filename of the cfroot you flashed as well.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Tried odin today with the CF-Root-SGS3-v6.4.tar
this is what i got
<ID:0/007> Added!!
<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> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Restarted phone, and as usual everything is fine, phone works normally other than some bugs i imagine the rom has.
http://forum.xda-developers.com/showthread.php?t=2214684
Sent from my GT-I9300 using xda app-developers app
lefttobleed said:
http://forum.xda-developers.com/showthread.php?t=2214684
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I tried that already, odin won't let me flash either a root or another rom even if its stock.
NO1 else haves a remote idea of what is happening to me?
i need to flash again cuz that damn JB leak is draining all my battery in 2/3 of my day....
Yeah, now my phone is softbricked with the Firmware upgrade encountered an issue message. Lucky me!
Andrew_spiegel said:
Yeah, now my phone is softbricked with the Firmware upgrade encountered an issue message. Lucky me!
Click to expand...
Click to collapse
Are you saying softbricked not booting or just that Kies no longer recognizes firmware due to conflicting firmware codes ??
jje
JJEgan said:
Are you saying softbricked not booting or just that Kies no longer recognizes firmware due to conflicting firmware codes ??
jje
Click to expand...
Click to collapse
Not booting, stuck at the "Firmware update has encountered an issue..." screen.
Can get into download mode only, not recovery. Cant flash cuz NAND write error fails on odin.
Thread reads as Nand damaged probably due to partition information table part of the nand faults .
jje
Hello.
I usually don't post on forums but, I'm having a heck of a time trying to get this resolved. I don't know if this has already been addressed in a thread but I am having a hard time getting my phone to root with Odin.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I attempted following the root steps provided here: http://forum.xda-developers.com/showthread.php?t=2143479 and have run into a roadblock. The code I get when I run the PDA file through Odin is this:
<OSM> CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried doing a factory data reset, clearing the cache partition/wipe, and am still getting a fail. I have not rooted this device previously and notice while I had the device in Downloader mode that the system status says 'custom'. I tried downloading and installing the PIT file for my device and also attempted running No triangle (which will not start up properly).
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
jaycue said:
Hello.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
Click to expand...
Click to collapse
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Thanks for the response
It's 4.3 OTA. I'll try that other program and see what happens.
Thank you
Another way than Kingo
jcollier said:
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Click to expand...
Click to collapse
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
TX_Jax said:
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
Click to expand...
Click to collapse
I hadn't seen your previous response before I responded on this thread. That said, it sounds like your thread might help the OP.
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.
Hello!
I'm attempting to root my S4 and eventually flash it with a custom ROM. However, I'm having a lot of trouble getting it to root. I'm using an online guide which flashes another kernel (NC5) using Odin then roots using towelroot and finally flashing back to my original kernel (NK1). The problem is that when I originally try to flash the NC5 kernel using Odin, I get an error. I've tried looking online for a solution but have found nothing so hopefully someone on here can assist me.
I'm running 4.4.2 on a SCH-I545VRUFNK1 and using Odin v3.09 but have also tried v3.04 to no avail. I've taken the battery out and waited 10 minutes, but that didn't work. Here is the output from Odin:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Thank you to all in advance!
Niotic said:
Hello!
I'm attempting to root my S4 and eventually flash it with a custom ROM. However, I'm having a lot of trouble getting it to root. I'm using an online guide which flashes another kernel (NC5) using Odin then roots using towelroot and finally flashing back to my original kernel (NK1). The problem is that when I originally try to flash the NC5 kernel using Odin, I get an error. I've tried looking online for a solution but have found nothing so hopefully someone on here can assist me.
I'm running 4.4.2 on a SCH-I545VRUFNK1 and using Odin v3.09 but have also tried v3.04 to no avail. I've taken the battery out and waited 10 minutes, but that didn't work. Here is the output from Odin:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Thank you to all in advance!
Click to expand...
Click to collapse
Have you tried using a different USB cable? Sometimes I have had this happen, I switched cables and it worked fine after, but this may not be your specific issue.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Also, are you using the Kernel or full image? Look at file size as the Kernel is fairly small compared.
Yea, I did try that! I tried it with two different cables and two different USB ports but didn't change anything unfortunately.
Niotic said:
Yea, I did try that! I tried it with two different cables and two different USB ports but didn't change anything unfortunately.
Click to expand...
Click to collapse
I would say maybe try another PC if available.
What if there isn't another pc available?
What is the file size of the image you are trying to flash?
Flash a stock nc5 image, then use towelroot. Odin may not be liking the image... Also, sometimes the phone has to be flat. That helps me A LOT in my constant Odin Flashes.
XxD34THxX said:
Flash a stock nc5 image, then use towelroot. Odin may not be liking the image... Also, sometimes the phone has to be flat. That helps me A LOT in my constant Odin Flashes.
Click to expand...
Click to collapse
Can't flash a stock image of NC5 as he is on NK1. He CAN flash the NC5 kernel, use towelroot to root, and then flash the NK1 kernel again.
I had this same problem. I am pretty sure I had the phone flat on my table instead of on my PC... That didn't help in your case... Use Odin 3.07
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Niotic said:
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Click to expand...
Click to collapse
Just tried Odin 3.07 with no luck, my phone is flat and I tried two different USB ports with two different chords. What's my next option?
Niotic said:
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Click to expand...
Click to collapse
Its no problem man. I actually jump on XDA when I am at work, in between selling phones and monthly renewals. I recently had the same issue and changing my cable solved it for me.
Thanks for understanding! Yea I've tried two different cables as stated before but no luck. I'm starting to get the feeling this root isn't going to work -_-
Niotic said:
Thanks for understanding! Yea I've tried two different cables as stated before but no luck. I'm starting to get the feeling this root isn't going to work -_-
Click to expand...
Click to collapse
What, if you don't mind my asking, do you use root for?
Sent from my SCH-I545 using XDA Free mobile app
Well recently my battery life has been atrocious to say the least so I was hoping on using a root to improve that further controlling the resources that some apps use even while not in use. For example facebook is constantly pulling a massive amount of resources which I believe is partially related to my bad battery life.
I also am a bit obsessed with my UI and love changing it around in order to get better funtionality as well as increasing it's visual appel. I feel that touchwiz is ugly and would like to flash something over it in order to get rid of it and allow further customization of my UI.
Have you tried unchecking Auto Reboot in Odin options?
Another way, I've got this rooting problem on my Samsung E5:
...
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Luckily I found a thread in AndroidForums (I can't post the link here because of XDA's rules). Not totally the same but I think it could help. Belong to it, maybe your reactivation lock is on. Turn it off (Menu > Settings > General > Security > Reactivation lock, uncheck) and retry.
Thanks for the suggestion zhaona; unfortunately, it did not work. Does anyone else have some suggestions?