I tried flashing US boot loader and I receive 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> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I received the file from this thread. http://forum.xda-developers.com/showthread.php?t=1531850
did you try turning the device on and off again?
Try redownloading the file you're trying to flash, sometimes they get corrupted.
Why are you trying to flash bootloaders anyway? Is your player seriously screwed up?
Ill try that. The player boots straight into recovery, that's my primary issue.
dktfoster said:
Ill try that. The player boots straight into recovery, that's my primary issue.
Click to expand...
Click to collapse
If you're getting recovery your bootloaders should be fine. Probably just need to reflash kernel/rom.
I've done that and it still boots straight into recovery
Are you sure you have the right kernel and rom? Maybe try a different one from the dev section?
I have the 4.0 us, I'm 100% sure I have the right rom. I might just send it back to Samsung. This whole problem started after flashing over to Klins Klassic and doing a factory wipe.
Try a different rom for your device.. it shouldn't be irreversibly screwed up.
Sent from my SGP5
dktfoster said:
I have the 4.0 us, I'm 100% sure I have the right rom. I might just send it back to Samsung. This whole problem started after flashing over to Klins Klassic and doing a factory wipe.
Click to expand...
Click to collapse
Redownload the Us restore pack. Ensure that re-partition is checked.
YP-GP70CWY
Hello,
I just encountered the same problem with my SGP5. It got stuck and reboots to the Android Recovery. I was trying to install a tweak on it after rooting and it just happened. I could go to kies no problem. But the main is, I can't get the OK/Power button to confirm so that I can wipe everything. Vol+- works but no confirmation. What should I do?
It is really hard when someone is on a learning curve. This is totally different for me.
Thank you very much for the devs and help.
....................................
I thought I had bricked it. I made it working again by reinstalling a rom.
thank you anyway.
I had one of my players that kept booting into recovery after resurrection from hard brick. Flashing a different rom fixed it. Flash a rom with CWM and use CWM to factory reset the device and retry. It took me a couple of tries, but I managed to get it to boot correctly.
cvcduty, I have read your little guide to restore the Galaxy Player on AdamOutlers' thread but it still won't work.. If you can please help me out, I'd be very grateful/appreciative. Thanks!
Related
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<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> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<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> 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> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
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
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.
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?