Related
i'm dumb as a brick cause that's what i have...a brick. honestly, i'm not sure how i managed this. it was late at night and i've done so many things trying to fix. here's my current situation:
i followed a guide somewhere on what to do if you think you've bricked your phone. it involves a pit file, a system.tar.md5, a kernel.tar.md5, and a recovery.tar.md5.
using odin, i can successfully flash the system.tar.md5 and the kernel.tar.md5.
...but the recovery.tar.md5 fails almost immediately. i have also tried using odin to flash clockworkrecovery. it too fails almost immediately.
my phone will not power on. however, if i plug the usb cable to my computer and the phone, i get the big battery picture (like it's recharging) but the little flower-like 'busy' indicator in the middle is not moving.
Remove the battery. Hold volume down and plug the phone into your computer. It should enter download mode, enabling you to Odin back to stock.
i've already tried that. it fails at the end of the flash when odin gets to 'recovery.bin'
have you restored back to stock before with those files?
you might have a bad download. Try re-downloading your files and try with the new files.
yes, all the roms? i have on hand i have previously used before and they worked. now everything i throw at it fails when it gets to recovery.bin and the phone won't power on. when i press the power button, nothing happens. however, if i plug into my computer, i get the previously mentioned battery screen.
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
for example, i have a DL09.tar.md5 file that i have used to successfully flash before. now, this is what i get in odin:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> factoryfs.rfs
<ID:0/007> modem.bin
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i also have a EB01_DXC.tar.md5 file that i have successfully used before. now, i get:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> zImage
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ok... i had weird things happen to me not too long ago and it turned out to be my USB cable.
It charges my phone but anything dealing with pc connection it bugged out
i bought a replacement online for about $3 on amazon from OEM store or something like that.
but first try to get your hands on another cable, or at the least try different USB ports on your PC, preferably the ones closest to the power supply and see if that makes a difference
djlim4 said:
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
Click to expand...
Click to collapse
thanks. i already had the ci500_vzw_eb01_froyo_rel.tar.md5 file. it never worked for me. odin on win7 32-bit would stop working at the end. however, i never had that particular pit file. i'm redownloading the tar.md5 just to make sure. however, the link to the pit file in that article is no longer working. none of those 'dropbox' links have ever worked for me. i'm trying to google that specific atlas pit filename but i keep getting broken links. any pointers?
http://dl.dropbox.com/u/19519343/atlas_v2.2.pit
i just uploaded it to my db... hope it works for you
ok. i found that particular pit file somewhere else (atlas_v2.2.pit).
i'm a little confused about what you meant about the recovery files in the article you linked to. are you saying don't use the recovery files in that article?
yea, that's an old CWR
if you're just trying to get your phone up and running, that last step is not necessary... if your phone boots up initially after the first odin flash, you can proceed however you want from there
i'm going to try the first stuff first and see how that goes...but if i'm still in the same situation then, i'm tempted to go ahead and try that old odin recovery file since recovery seems to be where my issues are. doesn't seem like it could make it any worse. however, the link there doesn't work for that either. any chance you could spot me a link for that too?
p.s. really really thank you for the help!
yea no prob... i'll check back in later when i get home from work and see if you need anything else. Good luck.
http://forum.xda-developers.com/showthread.php?t=1046905
the CWR situation got kinda confusing at one point and i didnt keep up with all the little details until it sort of got ironed out... i know that the most current one is 3.x and that thread i believe has a few options to get that on. If not, look up GizmoDroid. He wrote up a very detailed post on Clockwork and the whole confusion behind it and cleared up some stuff, sorry gotta get back to work, dun have time to look for that thread.
http://dl.dropbox.com/u/19519343/cwm-recovery-ALL.tar
ok... that is the OLD CWR, but it worked for all the stuff pre-eb01 i think...
def not for comm rom or official froyo released stuff, but that's the recovery file that's in the link i first sent you.
if you want the updated clockwork, check post # 5 of this thread
http://forum.xda-developers.com/showthread.php?t=1082726
was kind of bored waiting for the ci500_eb01_froyo_rel.tar.md5 file to download. i plugged my data cable into the back of the computer and tried flashing this 'CWMRecovery_DJ05_DL09.tar.md5' file i had laying around. didn't work at first. then i tried doing it with the atlas pit file you so kindly provided. it worked! the very first time in 24hrs and 100s of tries that i've actually been able to flash anything having to do with recovery...
...but phone still wouldn't power on. i plugged it into my wall charger and tried to power on. no go. well, i left it there plugged in. about 5 minutes later, i turn around and the stock recovery screen is up! yay! even tho it was barking about being unable to mount /dev/block/st111 and /dev/block/mmcblk0p1 ...i'm still pretty excited...some kind of progress i guess
i'm beginning to think all my problems are coming from the mad-crazy flashing i was doing last night with a very low battery. intuition told me that was a bad thing but i was already having problems and my OCD wouldn't let me go to sleep without getting my phone back in working order. OCD bad. Sleep good. low battery bad. charged battery good.
hey that's good news, at least there's some progress.
Will be offline for a while, but i hope there are enough links there for you to tinker with and hopefully get everything fixed.
i'm just glad my "bricked" folder of my dropbox finally got some use
YES! using that atlas pit file, the froyo rom linked there, and somewhat charged battery i am up and running!!!!
thank you thank you thank you!
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
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<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> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
MistahBungle said:
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
Click to expand...
Click to collapse
Yeah thanks. I've looked over and found a whole list on here such as try different computer, different ports, run as admin etc etc and they didn't work after trying them over and over. They seemed quite generic :crying: I thought it might have been a problem with the fact that PhilZ is on there. Or should that not make a difference?
JackJack94 said:
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<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> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
Click to expand...
Click to collapse
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Many40 said:
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Click to expand...
Click to collapse
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
MistahBungle said:
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Click to expand...
Click to collapse
Okay thanks for that. I'll check that out. And thanks for clearing up about the current firmware to. Makes me feel a bit more relieved :fingers-crossed:
JackJack94 said:
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
Click to expand...
Click to collapse
OK, then just follow the advice given already by MistahBungle (you must have missed something)
BTW what is exactly firmware you are trying to flash, is it made for your device, might be bad download ....
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Auth means you are using the wrong tar fille. Make sure you use the MI1 file if you took the latest update
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Ablac said:
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Did you get it to work? I made the same mistake with SafeStrap, and now I can only boot to the download screen.
I'm downloading the ROM you linked, but it will take another two hours.
EDIT:
Download finished. How do I install it? I was expecting a .tar or .md5 to use with ODIN, but the link contains a zipped .img
Did it work?
Ablac said:
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
alexbmex1 said:
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
dlist said:
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Click to expand...
Click to collapse
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
All done
artjef said:
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
Click to expand...
Click to collapse
Beautiful ROOT! It is back. Thank you very much for the link. Worked like a charm.
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?