Hi all,
I have a i777 with stock UCKK6 that I was trying to root with CreepynCrawly's UCKK6 stock with root in his download repository.
I've been spending the past week reading all the posts (Thanks for all the information), and I thought I had everything down, however I wasn't expecting to get the Blue Screen of Death right when I decided to start flashing with Odin. My mistake could've been I installed the USB Drivers from Samsung's website for the i777 which was 1.5.14. I was using Odin 1.85 when it occurred on my Windows 7 x64 machine. When it first occurred, I left the cable in there, and decided to uninstall the drivers, and downgrade to a version that was available from a post on XDA. However, now the problem seems to be that I keep on getting unknown device as the device is still stuck in downloading mode. I was reading some instances where some people were just able to continue after the BSOD, however I'm not so lucky. What should I do now? I'm afraid to do anything to my phone, and I hope I can figure something out before my battery runs out.
Thanks in advance for any help.
The 1.5.14 version of USB Driver for Samsung Phones is fine. Any earlier version is probably fine also, but you will need to reboot the computer after uninstalling, then reinstall and reboot your computer again. Win7 x64 is fine also, and Odin3 v1.85 is preferred.
You didn't say if you got the BSOD on the pc or on the phone. It is usually a term that is associated with windows on the pc. You also didn't say if the Odin flash completed and if you got a pass or fail.
At this point you need to pull the battery to turn the phone off, and start over.
Make sure you have a good install of the usb driver, with reboots as above.
First try to enter recovery mode by holding down all three buttons, vol- vol+ & pwr. If that is successful, do a wipe data/factory reset and then reboot. If the phone boots up normally, then you're back in business.
If you can't get into recovery, or if you get recovery but the phone does not boot up normally, you need to flash again. Enter download mode and do the flash again.
____________________
The following is for reference. How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
Thanks for the quick reply.
In my haste during the initial flash, I forgot to capture the logs, but I'm pretty sure it just started getting to "Nand Write Start". It was pretty early in the process. Then my PC had the Blue Screen of Death, (some PFN error). After realizing that I should still have the bootloader intact, I eventually unplugged the phone and then tried to resume it. I got the same error. Then I tried other versions of the USB driver 1.5.5 (uninstalling then installing with reboots), and I believe it gave me the same error. I then also tried it on another Win XP computer, and one instance I got as far as NAND write start, and then ODIN terminated it this time. Again, I didn't capture the log.
However, I did go back to my Win 7 x64 PC and then installed the latest driver 1.5.25, and I did manage to collect the log for that (I'll be sure to do that from now on):
<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> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004> Complete(Write) operation failed.
Anywyay, I can get download mode again, but I can't seem to get recovery. I instead get a dreaded yellow triangle error message that says Firmware upgrade encoutered an issue, please select recovery mode in Kies & try again. I'm not sure if I'm pressing the correct buttons, but before this process started I was able to get into 3e recover, but it's a tricky sequence to get right sometimes.
Is my problem the image I'm trying to flash? Should I just try to use the one click to UCKH7 since the aborted ODIN flash corrupted my UCKK6?
I was thinking of using Heimdall, but just my luck that their hosting service is doing some maintenance!
Anyway, I'll go through your sequences for ODIN again, but my problem seems to be mostly centered around the driver (especially on the WinXP machine where it won't recognize the device), and on the Win7 x64 I get the Blue screen when any transfer is occurring.
I'll try with your steps outlined above, although I was kind of doing that already sometimes since I seem to recall you posting that somewhere else.
Thanks so much for your help.
Make sure you run Odin in administrator mode..!
Sent from my SGH-I777 using xda app-developers app
If I am understanding you correctly, your computer interrupted the flash during the first time you tried to flash the stock plus root package. This likely happened early in the flash cycle. (By the way, there is no bootloader in that package.)
One possible result is that you now have a partial flash in one partition of the nand, which is essentially nand read/write corruption. I would start with the following to see if it will clear the problem.
1)Assuming your phone operating system is Gingerbread, 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.
Thanks for the detailed instructions. I'll give it a shot. I hope your theory regarding NAND partitions is explaining the weird behavior regarding both my PCs with the USB drivers (x64 Win 7 & XP SP3). If I can't seem to resolve the USB Driver issues and Odin, is it possible to flash the Siyah Kernels with Heimdall? I think their hosting site is back...
Also, as I understand it, if I'm able to successfully flash the kernel it will trip the counter, right? Anyway, it's a moot point since I'm past warranty anyway. I'd be thrilled if I don't have.
Thanks again for all your help!
Yay! I was able to flash the Siyah kernel after lots of experimentation (long story short, I gave up on the Win7 x64 machine, and tried the XP SP3 again, and after cleaning out my registry for Samsung that improved things as well as trying a new USB port on the PC).
Now I have the i9100 screen with the yellow triangle which I assume is because of the Siyah kernel.
Before I move on to the next step, I wanted to make sure I understood things correctly. you want me to next flash the complete UCKH7 binaries linked in your Download Repository from sammobile.com? It also contains the bootloaders, right? I guess for sure I will stay away from the x64 machine since I have that Blue screen problem. I'm assuming the one click and .tar.md5 are the same, right? Since I still am not that confident about my USB drivers, what would be the Heimdall commands in case this doesn't work. I'm also wary of flashing bootloaders.
zebra72 said:
Thanks for the detailed instructions. I'll give it a shot. I hope your theory regarding NAND partitions is explaining the weird behavior regarding both my PCs with the USB drivers (x64 Win 7 & XP SP3). If I can't seem to resolve the USB Driver issues and Odin, is it possible to flash the Siyah Kernels with Heimdall? I think their hosting site is back...
Also, as I understand it, if I'm able to successfully flash the kernel it will trip the counter, right? Anyway, it's a moot point since I'm past warranty anyway. I'd be thrilled if I don't have.
Thanks again for all your help!
Click to expand...
Click to collapse
zebra72 said:
Yay! I was able to flash the Siyah kernel after lots of experimentation (long story short, I gave up on the Win7 x64 machine, and tried the XP SP3 again, and after cleaning out my registry for Samsung that improved things as well as trying a new USB port on the PC).
Now I have the i9100 screen with the yellow triangle which I assume is because of the Siyah kernel.
Before I move on to the next step, I wanted to make sure I understood things correctly. you want me to next flash the complete UCKH7 binaries linked in your Download Repository from sammobile.com? It also contains the bootloaders, right? I guess for sure I will stay away from the x64 machine since I have that Blue screen problem. I'm assuming the one click and .tar.md5 are the same, right? Since I still am not that confident about my USB drivers, what would be the Heimdall commands in case this doesn't work. I'm also wary of flashing bootloaders.
Click to expand...
Click to collapse
I doubt that the phone has anything to do with the pc freezing. It could have something to do with bad flashes if the USB port on the phone is dirty or beginning to fail. Flashing a bootloader is minimally risky. The risk is the flash being interrupted while the bootloader code is actually being transferred, and since the sbl is so small, that transfer happens in a matter of seconds.
If it is nand read/write corruption, you most likely will need to flash the full firmware including sbl and param.lfs. You might first try flashing the package that has the sbl and param.lfs removed, just to see if it will work. But for nand read/write corruption, the sequence I posted is what is needed, afaik. There should be no difference between using the one-click downloader and stand alone Odin. The method is a little different is all.
Thanks for the info as I'll try that. I don't see a ODIN package with UCKH7 stock binaries that have the sbl & params removed. There is one for Heimdall though. I guess I was hoping to test my ODIN setup on the successful PC (running XP) before I run the whole package. Alternatively, I have played around with Heimdall on the original offending Blue Screen PC, but gave up on Win 7 x64 and successfully downloaded the PIT file on the exact same PC booting up in Ubuntu, so I feel good that the connection there is safe. As a general thing with Heimdall, does it matter the order I'm flashing the partitions, or can I even break them up into pieces, taking the UCKH7_noBL image and flashing the factoryfs, and zImage with separate commands?
Entropy512's Original I777 UCKH7 Kernel plus Non-Rooted System Package, which is the second block below the UCKH7 stock binaries is the one that has no sbl or param.
With Ubuntu, you want to use Heimdall command line tool. The code for Heimdall is in the little code boxes in the Download Repository. I don't think the order matters, but there is information in the readme file with the command line tool which suggests an order.
I'm starting to run out of ideas regarding this phone. I went back to ODIN on the Win XP PC that successfully flashed the Siyah Kernel, but after running into problems, cleaning registry entries of Samsung, I can't seem to flash anything past the "SetupConnection" phase of ODIN. It pretty much just hangs there, and I never see any indication that anything is being written to the device (ie no green bar on the phone). I was trying to just flash the Entropy's UCKH7 system files and modem as I'm afraid to just yet flash the bootloaders yet. I guess my question is, are the write problems caused by my hosed NAND partition or am I still having problems with my USB drivers on the Win XP machine. I've installed/deinstalled them many times and spent most of my time rebooting and having ODIN just hang there after SetupConnection.
In parallel, I also tried my Win7 x64 machine (the one that original caused this problem with ODIN), but I only booted up in Ubuntu with Heimdall. I found Ubuntu/Heimdall to be the most reliable as I can reliably get the PIT file at least (I don't always get that far with ODIN on XP). BTW, I think with 1.40 version of Heimdall, he did away with the hard coded names that CreepynCrawly has in the instructions of his download repository, but most of them are just simply in CAPS as opposed to the partition names in the download repository (ie --KERNEL instead of --kernel). You can find out for sure by issuing a print-pit command. With Heimdall, I'm consistently getting the OS to recognize the device in boot mode, but then when it starts writing, I get a libusb error, and I never see the green bar move on the phone.
I still haven't flashed the full stock with bootloaders yet, as I'm hoping that will do the trick. BTW, for the tar.md5 file, what slot do I insert it in since it contains bootloaders and modems? Do I just put it in the PDA slot? With Heimdall, would I issue the commands for the bootloaders first, then the non system images? Or do I just do one Heimdall command for all of them?
Anyway, I'm still not sure if I have a reliable PC that flashes correctly, or my NAND corruption is causing the write errors. If it's the latter, then I'm thinking my phone could really be bricked despite being able to get at the bootloader.
Oh, and 1 more thing. What was the point of flashing the Siyah kernel, and then stock image? I was pretty happy when I got that successfully flashed, but now I'm not sure what purpose it's serving.....
zebra72 said:
Oh, and 1 more thing. What was the point of flashing the Siyah kernel, and then stock image? I was pretty happy when I got that successfully flashed, but now I'm not sure what purpose it's serving.....
Click to expand...
Click to collapse
The purpose is to clear nand read/write corruption. If nand read/write corruption is the problem, then following the sequence I posted exactly should clear it and get your phone back. I don't understand the inner workings of the phone well enough to know why that sequence works. But you havn't tried this sequence yet, since you havn't flashed the full stock image.
zebra72 said:
I'm starting to run out of ideas regarding this phone. I went back to ODIN on the Win XP PC that successfully flashed the Siyah Kernel, but after running into problems, cleaning registry entries of Samsung, I can't seem to flash anything past the "SetupConnection" phase of ODIN. It pretty much just hangs there, and I never see any indication that anything is being written to the device (ie no green bar on the phone). I was trying to just flash the Entropy's UCKH7 system files and modem as I'm afraid to just yet flash the bootloaders yet. I guess my question is, are the write problems caused by my hosed NAND partition or am I still having problems with my USB drivers on the Win XP machine. I've installed/deinstalled them many times and spent most of my time rebooting and having ODIN just hang there after SetupConnection.
In parallel, I also tried my Win7 x64 machine (the one that original caused this problem with ODIN), but I only booted up in Ubuntu with Heimdall. I found Ubuntu/Heimdall to be the most reliable as I can reliably get the PIT file at least (I don't always get that far with ODIN on XP). BTW, I think with 1.40 version of Heimdall, he did away with the hard coded names that CreepynCrawly has in the instructions of his download repository, but most of them are just simply in CAPS as opposed to the partition names in the download repository (ie --KERNEL instead of --kernel). You can find out for sure by issuing a print-pit command. With Heimdall, I'm consistently getting the OS to recognize the device in boot mode, but then when it starts writing, I get a libusb error, and I never see the green bar move on the phone.
I still haven't flashed the full stock with bootloaders yet, as I'm hoping that will do the trick. BTW, for the tar.md5 file, what slot do I insert it in since it contains bootloaders and modems? Do I just put it in the PDA slot? With Heimdall, would I issue the commands for the bootloaders first, then the non system images? Or do I just do one Heimdall command for all of them?
Anyway, I'm still not sure if I have a reliable PC that flashes correctly, or my NAND corruption is causing the write errors. If it's the latter, then I'm thinking my phone could really be bricked despite being able to get at the bootloader.
Click to expand...
Click to collapse
The cause of the failed flashes is most likely in the phone. There is some possibility it is because of the connection between the phone and the computer. It is almost certainly not just because of the computer.
zebra72,
With a quick read of this thread i didn't see it mentioned...but have u tried a different micro usb/usb cable yet ??
Sometimes that cable that u thought was reliable can all of the sudden become not so. Using a different cable has solved heimdall flashes that weren't workin for me in the past...and even odin flashes that were not completing successfully.
Sent from my SAMSUNG-SGH-I747 using xda premium
creepyncrawly said:
The purpose is to clear nand read/write corruption. If nand read/write corruption is the problem, then following the sequence I posted exactly should clear it and get your phone back. I don't understand the inner workings of the phone well enough to know why that sequence works. But you havn't tried this sequence yet, since you havn't flashed the full stock image.
The cause of the failed flashes is most likely in the phone. There is some possibility it is because of the connection between the phone and the computer. It is almost certainly not just because of the computer.
Click to expand...
Click to collapse
Ok, Thanks again for the explanation. Right now, I'm just gun shy given what has happened since the full stock image contains bootloaders. I just don't want it to fail at any of the critical steps, however small that may be. Would I be able to try to flash the Siyah kernel again as a test of my setup, and then if it succeeds flash the full stock?
4-2ndtwin said:
zebra72,
With a quick read of this thread i didn't see it mentioned...but have u tried a different micro usb/usb cable yet ??
Sometimes that cable that u thought was reliable can all of the sudden become not so. Using a different cable has solved heimdall flashes that weren't workin for me in the past...and even odin flashes that were not completing successfully.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I had thought about it, but now hearing creepyncrawly's explanation and your previous experience, it's something I'll have to check. Any recommendations on cables? Should I go with stock Samsung cables? Thanks for the suggestion!
Samsung Oem USB
http://pages.ebay.com/link/?nav=item.view&id=400467800450
Sent from my SGH-I777 using xda app-developers app
Wow, what a difference a USB cable makes! So after more failures today, I decided to pull out the old data cable from my Nexus One and give that a shot. I used both ODIN and Heimdall, and I was able to flash the Siyah kernel again as well as the UCKH7 modem file in Heimdall. With Heimdall, it was telling since I had turned on verbose mode, and with my original OEM cable, I would occasionally get time outs even when retrieving the pit file, but it would recover. However, with flashing, it must not have been able to overcome the errors. In retrospect, the OEM cable has been through a lot (ie chairs rolling over it, pulled and dragged) since it is the same cable as the charger. Props to 4-2ndtwin for pointing this out! And creepyncrawly, it looks like you were right. I kept on thinking it was my computer with the USB ports or drivers!
I also noticed now that I have CWM recovery on it, when I flashed the Siyah kernel a second time. After noticing how fast the ODIN flash was, I'm starting to think the first flash probably didn't fully flash correctly, but I got success after a much longer time than with the good cable. Now I'm wondering if I should risk flashing the bootloaders and instead just try to flash the the UCKH7 with root and go from there. Of course, now that my counter is tripped, can I just flash a ROM that I'm interested in?
Thanks so much for all the help!
zebra72 said:
Wow, what a difference a USB cable makes! So after more failures today, I decided to pull out the old data cable from my Nexus One and give that a shot. I used both ODIN and Heimdall, and I was able to flash the Siyah kernel again as well as the UCKH7 modem file in Heimdall. With Heimdall, it was telling since I had turned on verbose mode, and with my original OEM cable, I would occasionally get time outs even when retrieving the pit file, but it would recover. However, with flashing, it must not have been able to overcome the errors. In retrospect, the OEM cable has been through a lot (ie chairs rolling over it, pulled and dragged) since it is the same cable as the charger. Props to 4-2ndtwin for pointing this out! And creepyncrawly, it looks like you were right. I kept on thinking it was my computer with the USB ports or drivers!
I also noticed now that I have CWM recovery on it, when I flashed the Siyah kernel a second time. After noticing how fast the ODIN flash was, I'm starting to think the first flash probably didn't fully flash correctly, but I got success after a much longer time than with the good cable. Now I'm wondering if I should risk flashing the bootloaders and instead just try to flash the the UCKH7 with root and go from there. Of course, now that my counter is tripped, can I just flash a ROM that I'm interested in?
Thanks so much for all the help!
Click to expand...
Click to collapse
You may be able to flash custom firmware now. It won't do any harm to try. Then if it doesn't flash, you can do the steps I gave for clearing nand r/w corruption.
creepyncrawly said:
You may be able to flash custom firmware now. It won't do any harm to try. Then if it doesn't flash, you can do the steps I gave for clearing nand r/w corruption.
Click to expand...
Click to collapse
That was my thinking exactly, and I tried to flash UCKK6 root (trying to get back my old data), and it failed on the factoryfs partition through Heimdall. Then I just followed your instructions with the stock UCKH7 through Odin and crossed my fingers when it flashed all the important stuff (bootloader, etc), and I let out a huge sigh of relief when it all worked! I'm so excited to have my phone back as I started exploring buying other phones when it looked bleak! Now I'm ready to explore the world of custom ROMs.
Moral of the story is you really have to look at everything even if you think it couldn't be something simple like a cable!
And finally, I want to give a huge thanks to creepyncrawly for helping me out! I'd be SOL without all the prompt help you have provided for me!
Ok, I'll start from the beginning. I wouldn't consider myself a noob, instead a novice power user. I've done my share of flashing and resurrecting my device from a soft brick before. I'd been running 10/21 build of Carbon for a solid week without issues until my phone completely froze while browsing on Dolphin browser. I hadn't restored any system data using TiBu after flashing Carbon running 4.3.1.
So with the device hung, I proceed to restart as always and got stuck on "SAMSUNG" boot logo. I did a battery pull and tried again to no avail. At this point I tried going into recovery and once I got there I had no selections on screen. Simply 6.0.4.4 CWM written at the bottom. Now I really started getting worried. I thought to go back to stock at this point through Odin and this is where things really got mucked up. I tried flashing UCMD8 using Odin 1.85 and it would hang on Sbl.bin and the last message would be "NAND Write Start". I've done a few Odin flashes before and knew this wasn't normal. Few minutes later, no progress so now I'm stuck with the "Device needs to be recovered using Kies" bull**** at power on.
After some research, I came to the conclusion that I have the NAND r/w corruption problem. So I tried flashing creepyncrawly's files from his "download repository" and all the files (stock kernel, UCKH7 system package, bootloader) would get stuck somewhere and last message would read "NAND write start". I just don't know why this happened. Things were smooth sailing and working perfectly and next second I have a semi hard brick on my hand?
Can somebody please guide me through this and try to revive my aging I777 please? Maybe one the senior members, contributors, etc? I'd greatly appreciate any effort. Like I said, I'm not a noob and can work with adb and odin, I just need to be pushed in the right direction with any ideas. :crying:
Did you follow all of these steps in order? If not, go through this sequence again, from 1 through 6.
creepyncrawly said:
Did you follow all of these steps in order? If not, go through this sequence again, from 1 through 6.
Click to expand...
Click to collapse
I knew you'd be the first to come to rescue. So I couldn't complete step 1 because it got stuck at NAND write start. So I first flashed the secondary bootloader and that got me to the Samsung Galaxy SII i9100 boot logo. Proceeded to flash siyah kernel and it's stuck at NAND write start. Maybe I have to put the pit file in for it to remap the emmc?
mpkothari said:
I knew you'd be the first to come to rescue. So I couldn't complete step 1 because it got stuck at NAND write start. So I first flashed the secondary bootloader and that got me to the Samsung Galaxy SII i9100 boot logo. Proceeded to flash siyah kernel and it's stuck at NAND write start. Maybe I have to put the pit file in for it to remap the emmc?
Click to expand...
Click to collapse
I haven't had any personal experience flashing with partitioning checked and using the PIT from the Download Repository. It it were my phone, I would try it though.
Damaged emmc memory is only one possibility. The bad flash could also be due to the connection between the computer and the phone. I would suspect and test everything else first, so use a different good cable, use a different port on the computer, even try a different computer, etc. Also, some have reported that multiple attempts to flash eventually resulted in a pass, so try multiple times.
I do have first hand experience in flashing bad eMMC with repartitioning.
It killed the phone, turning it from a "soft brick" into a "hard brick", and I had to get a new main board.
This is a special case that requires extensive help from you guys (hopefully).
Problem: According to the ATT Samsung specialist the Bootloader I am using is corrupted
Attempted Solution: I have attempted to flash the stock SBL onto my phone but after trying every version of Odin3 (1.83-3.09) it did not work.
**The bar was entirely GREEN but it never finished**
Suggested Solution: Flash the stock ROM back onto the phone using Odin3
Outcome: After trying three different ROMs, all downloaded from Sammobile, using every version of Odin3 (1.83-3.09) only seemed to reach the end then fail at Modem.bin
I was wondering if anyone has any idea how to fix my phone, the original issue was that it never made it past the Samsung logo (not the Galaxy S2 Logo but the actual Samsung logo) the new issue is that it has the Samsung Galaxy SII Logo with the wrong model name (international model) and the small yellow triangle.
If my phone is permanently broken that's fine because I have a temporary phone I just want to get my files off of the phone before using my new one
I have a Jig
I can get it into Odin mode
I cannot get it into Recovery mode
I can get it into Factory mode
Help me please, I have no idea what else to do
Use this version of Odin, or just do more Google fu and find another place to download it from. [ http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 it may be the version of Odin you're using that's messing you up.
The link Phalanx7621 posted was supposed to point to the Download Repository (link is in my signature.)
The preferred version of Odin is 1.85. If you need it, the download link for Odin3 v1.85 at the top of the Download Repository is a working link.
If the boot loader was corrupt, the phone would be a true brick (no sign of life.) If the secondary boot loader was corrupt, the phone would not boot as far as the Samsung logo. It sounds to me like the AT&T Samsung specialist you received that information from was not fully informed.
The I9100 splash screen with the yellow warning triangle is due to flashing a custom kernel, so nothing to worry about. It can be cleared by flashing a stock kernel. Using the following procedure would have put that on your phone anyway by flashing the Siyah kernel, and then will removed it when stock Gingerbread is flashed.
Please note: The link in the Download Repository for the stock Gingerbread that you need to flash is not working, and I have yet to re-upload all these items to a new host. You will have to download this from the sammobile firmware page. It is the I777UCKH7 / I777ATTKH7 dated 2011 August. You'll need to sign in to download it. The registration is free. Edit: sammobile has not uploaded this file to a new host yet either. I will have to upload it and the sbl for you, but since today is Christmas, you may have to wait a day or two. At least you know that there will eventually be something to try.
Edit: The required files are now available with Dev-Host links in the Download Repository.
I think you will probably recover the phone by assuming it has nand read/write corruption and following this sequence:
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of 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. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Attempt #1
When attempting to flash the Kernel in Odin3 v1.85 the bar was fully green but the program never said complete (I left it going for a few hours to no avail)
I tried flashing the SBL and the same issue happened, the bar was fully green but it never said complete (I had previously downloaded the SBL)
When attempting to flash the Gingerbread stock it does not even go past the SBL1 part, the bar does not have any green within it and the program still says NAND Write Start.
I'm not the best with this sort of thing but from observation it seems that my NAND is corrupt and isn't allowing anything to be properly flashed.
By the way: the Custom Binary Download now says: Yes (5 counts) which tells me that the phone recognizes that something is being flashed but it's not working properly
I'm back to being stuck and I think this phone may be truly broken :/
I don't think ur phone is broken.
Try a different usb/micro usb cable. Try a different usb port on ur pc (don't use a usb hub). Make sure the phone's micro usb port is clear of dirt/debris, etc.
Usually when i've had problems with Odin flashes it is something as simple as doing these things that results in a successful flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Same Issue
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
androidrequest said:
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
Click to expand...
Click to collapse
Did you follow exactly the sequence in post #3? If not, please try that.
creepyncrawly said:
Did you follow exactly the sequence in post #3? If not, please try that.
Click to expand...
Click to collapse
Yes, I tried that sequence exactly. It actually won't advance past #1. The green bar loads in Odin under kernel, but stops working at NAND Write Start. And trying the sbl ends with the same result (I believe it's the first download in the Download Repository). All of the flash attempts have failed or frozen, but the Custom Binary Download count is at 3.