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 ....
Related
Disclaimer: if this topic has been handled somewhere else already, i'm sorry, but the search sure didn't come up with it.
Hi guys,
I'm currently facing a strange behavior of my P7500. This device was bought 2 days ago, and appears to have an unlocked bootloader. However i'm not too sure about this, since i only checked if there's a lock-symbol during boot (there isn't).
When trying to root the device using the nvflash method however, i was facing the 0x4 error.
Also, Odin v1.85 fails to flash any rom whatsoever. Neither stock roms nor Broodcomb seemed to work thru Odin.
Odin fails with the following output:
Code:
<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> Firmware update start..
<ID:0/007> bootloader.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> modem.bin
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The device IS rooted however, with the method described here. Thus, i also have CWM 4.0.0.4.
Another strange thing, that seems to point in the same direction though, is that installing Busybox fails (unless its supposed to take longer than 30 minutes).
To me that seems like its not possible to write to NAND.
Has anyone any idea how to fix/workaround this?
The firmware currently installed is the stock XWKG9.
Thanks for listening
Edit: With a different Busybox installer i was at least able to install BB. For the rest - still no success.
Edit 2: I stumbled across some other forum's post mentioning interferences by active KIES components in the system. Thus i rebooted, and the flashing process now fails later than in the original log. But it still fails.
Now i'm going to try a clean 32bit-VM (instead of a heavily used 64bit one) with nothing but the drivers installed in the system. Trying to flash stock KI1...
Final edit: I think i solved it AND found the reason why it actually happens: Timing issues in the system (in my case because of using a VM). It seems that when the system the operation(s) is/are performed on is relatively prone to lagging of any kind, the Odin flashing will fail, and most likely also any nvflash attempts.
How to fix
Can you show me how to fix this error ? Please
han.tvk said:
Can you show me how to fix this error ? Please
Click to expand...
Click to collapse
Yeah, would e great to know how you did it. I´ve the same prob.
Thanks in advance.
dvb127 said:
Yeah, would e great to know how you did it. I´ve the same prob.
Thanks in advance.
Click to expand...
Click to collapse
His final edit explains what he did: run ODIN on a clean system, not on a virtual machine. Running virtualized apparently introduces enough delays to cause the flashing process to fail.
yes i noticed other people post similar threads. but i could not find any answer to my issue, so i post another one. if i missed something, please pointed it out for me by all means.
My SGS2 is with Vodafone Australia.
i already upgraded it to ICS. but i do remember what rom i used when i upgraded it, the Kies cant recognise my phone. So last night, i downloaded another rom and planned to reflash the phone with a stock rom. it turned out all mess!
the flashing failed with boot.bin
<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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005>
<ID:0/005> Receive Response form LOKE
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
then i did some research and reckoned i might use the wrong rom, so just finished downloading another version: I9100TDULP9_I9100TVAULP7_I9100TDULP4_HOME.tar
but the issue is exactly same.
i use the rom for PDA, PHONE and CSC, didnt select repartition and not touch PIT either.
the phone is GT-I9100T.
Guys, please help me. i am a noob.
restart pc
kill kies
download the file again preferable from checkfus (builtin curruption check)
put the phone in download mode, connect the cable
put the file in pda.
all the new files i see are one file tar.md5 unless its different fro T
so just put in pda and flash.
edit: do not forget to wipe before nd after for optimal working
alwayseric said:
the phone is GT-I9100T.
Guys, please help me. i am a noob.
Click to expand...
Click to collapse
well heres all the firmwares for your phone hopefully u may spot the one you had if not just go with the lastest one.
FIRMWARE FOR GT-I9100T
the problem was fixed.
it seems i had to put both odin.exe and odin.ill into one folder (i extracted them on the desktop at first) or i should not load the rom file into PDA, CSC and PHONE. as there was only one file, i only needed to load it in PDA.
atifsh said:
restart pc
all the new files i see are one file tar.md5 unless its different fro T
so just put in pda and flash.
edit: do not forget to wipe before nd after for optimal working
Click to expand...
Click to collapse
i wish i had read your reply earlier. yes, only need to put the file into pda. i hope my lesson will be useful to some other newbies in the future.
thanks.
DJBoxer said:
well heres all the firmwares for your phone hopefully u may spot the one you had if not just go with the lastest one.
Click to expand...
Click to collapse
yes, it is where i downloaded the roms. i guess the first one i got was wrong, the second should be good. thanks.
but now, i have another issue with Kies. even though i used the "official" voda's rom, Kies still reckon "Your device does not support software update via Kies"
any clue?
Kies should work now that you've flashed the Voda ICS rom, however, for some reason (I have no idea why it doesn't work sometimes, perhaps someone else on here does ?), you'll find Kies still doesn't work even tho the stock rom contains the correct CSC, etc.
You could muck around for ages trying to find a solution to this, or you could simply do what most people on here who have found themselves in your situation do & that is to use Odin to flash future stock rom 'updates'.
Regardless of whether Kies works or not now, you do have the most up to date stock rom available for Voda, so you won't need to flash another stock rom until Voda issue another update (last one before recent ICS was in November).
Get the PC version of Checkfus, and when Voda do issue another update, you'll be able to easily download same & flash it via Odin.
alwayseric said:
i wish i had read your reply earlier. yes, only need to put the file into pda. i hope my lesson will be useful to some other newbies in the future.
thanks.
Click to expand...
Click to collapse
THANK YOU FOR POSTING THIS ADVICE! Odin failed for me after several attempts, which scared the crap out of me as it was my first time flashing a ROM on my SGS2...
Since there's only one file in the downloaded ROM, you only need to specify the file in the PDA section!!! That's it so simple... the guides need to be updated!!
I had a S2 i777, then I got a S3 so I gave the S2 to my mother. I just installed fresh ShoStock because I thought that would work well. It worked ok, but after about a month I came home and she said it wasnt working.
It appeared to be bootlooping at the ShoStock logo. I downloaded a new rom for it on my phone the put the SD card in her phone, booted into clockwork and tried flashing it. Trying to wipe or flash at all results in hanging for a few minutes then rebooting and getting stuck at the Samsung S2 logo now. Since then I've tried various odin methods for flashing to unbrick around xda. Every time I try to flash with odin, it either says error or it just hangs until I manually stop it after 30+ minutes. I've even got as desperate as to have Kies revert it to stock, it also hangs at 2%.
At this moment, you can see the screen its stuck it in the attached screenshot, its probably worth noting its been at this screen ever since the first Odin flash failed.
I do have a microUSB jig so I can kick it into download mode if I have to. Anyone got any ideas :f
Try the following procedure exactly as written. In case the problem is nand read/write corruption, this should clear it and get the phone working again.
1) Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
When I try and flash Siyah in Odin for step 1, it just hangs.
<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> zImage
<ID:0/004> NAND Write Start!!
Click to expand...
Click to collapse
The box at the top says kernel and the progress bar goes all the way across, it will never get past this.
Since it won't flash the kernel, the next thing to suspect and try to find out if the cable is faulty. Or anything in the path from the computer to the phone. So...
Try a different cable, or as many different cables as you can put your hands on.
Try different ports on the computer, and use the ones attached directly to the motherboard if it is a desktop.
Try a different computer.
In some cases where there is a connection problem, just flashing repeatedly may eventually result in a pass, as some have reported.
Tried it on two different laptops, with three different microUSB cables on each, no dice.
I tried flashing the kernel from step one you gave, I also tried the I777UCKH7-CL503881 FULL Odin3 One-click from the Download Repository and it hangs at:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
Click to expand...
Click to collapse
I don't have any additional suggestions for trying to fix it yourself. The problem could be one of several things. It doesn't seem like a simple soft brick. Maybe it could be damaged memory or some other hardware failure. Or maybe not.
If you are close to an AT&T service center, maybe you could take it by and ask them to flash it back to stock for you. If that fails, then at least you are pretty sure the problem is in the phone, not the connection. I realize it is not under warranty any longer, but they should at least try that for you.
You could send it to Samsung repair center to be worked on. They would probably fix it, but it won't be free, and it will also take two to three weeks. If it were me, I would call them first and discuss the issue with them.
Give these guys a call or message them and tell them your problem and they can most likely fix it. I have had work done by them in the past there quick and there professional...
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t/
Sent from my SGH-I777 using xda app-developers app
Could I get some help with my Samsung Ace? I am at a loss as to what to do next.
Early last year, I got a Samsung Galaxy Ace S5839i from Three in the UK. Like everyone with this model, I had problems with the limited storage space and bloatware, even after moving apps to the SD card. After some research, I downloaded Titanium and used it to remove the bloatware. Unfortunately, I wasn't careful enough and I must have deleted one or more core files, because now I get the 'android.process.acore' error message very frequently and I am unable to receive/make calls or receive/send text messages.
I have been looking on several android forums, but I have to say I find all the terminology confusing: ROMS, kernels, Odin, SplitFus, flashing – help!
After trying many things suggested on various threads in the forums (all unsuccessfully), I really just want to go back to the way the phone was originally, and then try again with Titanium (more carefully this time!). Is that even possible?
One potentially useful thing that I have learned from the forums is that I could use firmware for the 5830i, even though my phone is the 5839i. The Three firmware for the model 5839i is available on Sammobile, so I would prefer to use that.
However, when I tried to load the 5839i firmware file using Odin 3.09, this happened:
<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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone guide me through this? I just want to get back to how my phone was before I started using Titanium (so I can try Titanium again, but more carefully this time!). NB For some reason, I cannot use KIES.
What should I do?
OhHowWeLaughed said:
Could I get some help with my Samsung Ace? I am at a loss as to what to do next.
Early last year, I got a Samsung Galaxy Ace S5839i from Three in the UK. Like everyone with this model, I had problems with the limited storage space and bloatware, even after moving apps to the SD card. After some research, I downloaded Titanium and used it to remove the bloatware. Unfortunately, I wasn't careful enough and I must have deleted one or more core files, because now I get the 'android.process.acore' error message very frequently and I am unable to receive/receive calls or receive/send text messages.
I have been looking on several android forums, but I have to say I find all the terminology confusing: ROMS, kernels, Odin, SplitFus, flashing – help!
After trying many things suggested on various threads in the forums (all unsuccessfully), I really just want to go back to the way the phone was originally, and then try again with Titanium (more carefully this time!). Is that even possible?
One potentially useful thing that I have learned from the forums is that I could use firmware for the 5830i, even though my phone is the 5839i. The Three firmware for the model 5839i is available on Sammobile, so I would prefer to use that.
However, when I tried to load the 5839i firmware file using Odin 3.09, this happened:
<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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone guide me through this? I just want to get back to how my phone was before I started using Titanium (so I can try Titanium again, but more carefully this time!). NB For some reason, I cannot use KIES.
What should I do?
Click to expand...
Click to collapse
go search your odin problem on google.
after successful went into the originally rom i recommend you to flash simplicity v4 as it only take 4 MB on Internal Memory and you will have a lot of free memory and you will not need to risk with that titanium
go here for unbrick your device .
http://forum.xda-developers.com/showthread.php?t=2283926
ѕєηт ƒяσм αcє-ι-cσσρєяνє
amolgosavi said:
go here for unbrick your device .
http://forum.xda-developers.com/showthread.php?t=2283926
ѕєηт ƒяσм αcє-ι-cσσρєяνє
Click to expand...
Click to collapse
I followed all of the instructions in that thread, but no luck. I used firmware for both the S5839i (single file) and the S5830i (multi files) in each of Odin 1.85, 3.07, and 3.09 (so, six attempts in total) but each combination either failed or, in the case of Odin 1.85, did not move out of Setup Connection.
What is going wrong? Is there something really obvious that I am failing to do? I have the USB Debugging mode enabled on my phone. What else am I doing wrong?
OhHowWeLaughed said:
I followed all of the instructions in that thread, but no luck. I used firmware for both the S5839i I(single file) and the 5830i (multi files) in each of Odin 1.85, 3.07, and 3.09 (so, six attempts in total) but each combination either failed or, in the case of Odin 1.85, did not move out of Setup Connection.
What is going wrong? Is there something really obvious that I am failing to do? I have the USB Debugging mode enabled on my phone. What else am I doing wrong?
Click to expand...
Click to collapse
Follow this.
http://forum.xda-developers.com/showthread.php?t=1840645
Watch the video, do it exactly as he does but use open Australia.
OhHowWeLaughed said:
I followed all of the instructions in that thread, but no luck. I used firmware for both the S5839i (single file) and the S5830i (multi files) in each of Odin 1.85, 3.07, and 3.09 (so, six attempts in total) but each combination either failed or, in the case of Odin 1.85, did not move out of Setup Connection.
What is going wrong? Is there something really obvious that I am failing to do? I have the USB Debugging mode enabled on my phone. What else am I doing wrong?
Click to expand...
Click to collapse
i think you dont understand correctly..just go to this link and follow the instruction..i think this time it will work..
www.firealby.blogspot.in/2013/05/how-to-flash-stock-rom-on-samsung.html?m=1
ѕєηт ƒяσм αcє-ι-cσσρєяνє
amolgosavi said:
i think you dont understand correctly..just go to this link and follow the instruction..i think this time it will work..
ѕєηт ƒяσм αcє-ι-cσσρєяνє
Click to expand...
Click to collapse
I followed your instructions completely, and it worked! THANK YOU VERY MUCH!
Of all the times I have done this, this was the first time I used a bootloader file. Is that what made the difference? Or perhaps it was something else. Right now, I don't care, because I can finally use my phone again! )
Thank you very much for your help on this thread, and for your easy-to-follow videos.
OhHowWeLaughed said:
I followed your instructions completely, and it worked! THANK YOU VERY MUCH!
Of all the times I have done this, this was the first time I used a bootloader file. Is that what made the difference? Or perhaps it was something else. Right now, I don't care, because I can finally use my phone again! )
Thank you very much for your help on this thread, and for your easy-to-follow videos.
Click to expand...
Click to collapse
sooo finally you unbricked your device.. :thumbup:
ѕєηт ƒяσм αcє-ι-cσσρєяνє
Envy-X said:
Follow this.
Watch the video, do it exactly as he does but use open Australia.
Click to expand...
Click to collapse
I did, and it worked! Thank you!
amolgosavi said:
sooo finally you unbricked your device.. :thumbup:
ѕєηт ƒяσм αcє-ι-cσσρєяνє
Click to expand...
Click to collapse
Aaaaaaaand, the S5830i firmware seems to have a lot less of the ridiculous bloatware that came with the original S5839i firmware, so I'm even more happy...
OhHowWeLaughed said:
Aaaaaaaand, the S5830i firmware seems to have a lot less of the ridiculous bloatware that came with the original S5839i firmware, so I'm even more happy...
Click to expand...
Click to collapse
you can flash custom roms also of s5830i
ѕєηт ƒяσм αcє-ι-cσσρєяνє
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?