Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Hellstorm32 said:
Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Click to expand...
Click to collapse
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Hellstorm32 said:
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Click to expand...
Click to collapse
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Hellstorm32 said:
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Click to expand...
Click to collapse
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Well, I hope I didn't jump the gun. I did use the .pit file in Odin 3.07, I just saw your message about Odin 3.12. I loaded the PIT in the PIT slot, loaded my ROM in the PDAslot, and it seems to be taking a while on the <ID:0/003> Get PITfor mapping..
Droidriven said:
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Hellstorm32 said:
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Click to expand...
Click to collapse
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Text in Odin so far..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Hellstorm32 said:
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Click to expand...
Click to collapse
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Hellstorm32 said:
Text in Odin so far..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Click to expand...
Click to collapse
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, I've closed Odin. I've disconnected my device. I've checked and yes, I can still enter download mode (phew, I don't have much hardmod skills to get it running if it's hard bricked).
I'm going to bring it in to Best Buy today and see if the Samsung staff can flash it there. I was running stock when this happened. It's crazy, I was driving my car and I had my phone in my mount on the dash. I just happened to look over and it was stuck on the boot screen. No warning. It just restarted and froze on it's own.
Thanks for the help, I'm going to keep working on it today and see if I can get things moving.
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Hellstorm32 said:
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Click to expand...
Click to collapse
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Hellstorm32 said:
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Click to expand...
Click to collapse
If you did NAND erase all its dead. I started to warn you when you first mentioned NAND to leave it alone and don't mess with NAND in Odin. You can send it in for JTAG service, its usually $50 and they send it back to you fixed. Cheaper than replacing the motherboard. JTAG is the last ditch effort.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
If you did NAND erase all its dead. You can send it in for JTAG service, its usually $50 and they send it back to you fixed.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Hellstorm32 said:
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Click to expand...
Click to collapse
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Great help. Thanks man. I think I'm going to look at new models and see about upgrading. I believe with all the battery problems on the Note 7 that Verizon is offering 0$ down as incentive to purchase one. I'll have to do my research, but it's listed as 36$ a month and I may be able to afford that. After I get a new phone, I'll do my best to get the old one working again (new mobo) and probably look to unload it on Ebay after it's up and running no problems. Either that or let my wife take tthe Note 2 over (She has an S3).
I'm bummed. Especially because this happened out of the blue. I was running stock ROM and phone rebooted out of the blue to the splash screen and BAM...dead. I've been able to recover devices before (I bricked a Stealth Trio 7 before and had to write .sh files to get the touch screen to work again), this is the first time I've been unable to fix an android device. Had to happen sometime.
Thanks again for your efforts.:highfive:
Related
Hi,
Today I bought a galaxy note 2 off someone and its stuck in a bootloop.
It starts up and goes the Verizon 4G LTE screen and that's it.
I tried going into recovery and it says E:failed to mount /efs (Invalid argument)
I've tried using Odin and the phone to flash a stock file but they just dont work. Odin stopped working when the top thing said flashing recovery then it changed to "fail" in a red box. On the bottom it said Complete (write) operation failed.
Any ideas. Worst case its a parts phone but I really think/hope its fixable.
Thanks
I should add that when Odin fails the device says something about a firmware error and to use the Kies software. The Kies software just hangs at "connecting" so I was able to exit out of that message by going back to Odin and JUST using the 16gb PIT file. Then after that, I'm back to step 1 where it hangs at the 4G LTE bootloop.
Thanks
Use Odin, flash the alternate restore package with PIT file and repartition selected.
imnuts said:
Use Odin, flash the alternate restore package with PIT file and repartition selected.
Click to expand...
Click to collapse
I googled the alternate restore package and I downloaded one from a thread that you made. It downloads as a tar.md5.xz file and then Odin can't recognize it. Any ideas? Also whats the difference between VRAM and VRAL in the files since I found two files with those names in that thread.
Thanks
enferrari said:
I googled the alternate restore package and I downloaded one from a thread that you made. It downloads as a tar.md5.xz file and then Odin can't recognize it. Any ideas? Also whats the difference between VRAM and VRAL in the files since I found two files with those names in that thread.
Thanks
Click to expand...
Click to collapse
Alright, After making a folder I got the 7z file to extract into a tar.md5 and restored my note 2 with the PIT file as well. It went through successfully and Odin said it was successful. Upon restart the phone was still in a boot loop. I went into recovery and it says "failed to mount /efs" again Any more tips
enferrari said:
Alright, After making a folder I got the 7z file to extract into a tar.md5 and restored my note 2 with the PIT file as well. It went through successfully and Odin said it was successful. Upon restart the phone was still in a boot loop. I went into recovery and it says "failed to mount /efs" again Any more tips
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34891181
In section 1b, use the vramc3 file and pit file. If that doesnt work, try it with both files and reparation checked. As a note, this vramc3 is the actual stock software and will relock the phone so if it works and boots, you will need to use casual to unlock it again.
Sent From My Sticky Note, Too?
I had the exact same issue recently. Failed to mount EFS partition (If you see this in your stock recovery, you have a HUGE issue on your hands)... Stuck in a bootloop no matter if Odin is successful or not. Nothing I did booted it back up. So I thought I was screwed.
Now if none of the above methods work for you, I HIGHLY suggest you check out mobiletechvideos.com. They take care of bricks, which sounds like that's where you're at.. They fix EFS issues, and everything you can think of. They have great reviews. And I actually took the plunge and went to them to fix my phone at the time.. I paid for the unbrick service, a new USB cord, and rush processing. Cost around $100. Which costs me a lot less than buying another phone and/or using my upgrade.
Once my phone returned, I factory resetted the phone, and all was perfect. I suggest you trying that if these methods don't work for you. I can thank @ForeverSupra for sending me to them.
Mobiletechvideos.com
Try the VRALJB alternate restore package. It has an xz extension, but 7zip can extract it. There may be an issue with the VRAMC3 package, but I haven't had a chance to look into it to confirm and/or fix it.
imnuts said:
Try the VRALJB alternate restore package. It has an xz extension, but 7zip can extract it. There may be an issue with the VRAMC3 package, but I haven't had a chance to look into it to confirm and/or fix it.
Click to expand...
Click to collapse
Ok I'll try that. I tried the VRAMC3 and it said it was successful but it was still stuck in a boot loop . Will download the VRALJB and keep you guys updated. Worst case I'll just list it for parts on eBay - I only paid $60 for it since the guy said it was stuck in this boot loop and I thought it would be an easy fix. I appreciate you guys helping me.
Ohh_Trenton said:
I had the exact same issue recently. Failed to mount EFS partition (If you see this in your stock recovery, you have a HUGE issue on your hands)... Stuck in a bootloop no matter if Odin is successful or not. Nothing I did booted it back up. So I thought I was screwed.
Now if none of the above methods work for you, I HIGHLY suggest you check out mobiletechvideos.com. They take care of bricks, which sounds like that's where you're at.. They fix EFS issues, and everything you can think of. They have great reviews. And I actually took the plunge and went to them to fix my phone at the time.. I paid for the unbrick service, a new USB cord, and rush processing. Cost around $100. Which costs me a lot less than buying another phone and/or using my upgrade.
Once my phone returned, I factory resetted the phone, and all was perfect. I suggest you trying that if these methods don't work for you. I can thank @ForeverSupra for sending me to them.
Mobiletechvideos.com
Click to expand...
Click to collapse
Looks like I'm in the same position as you. One last try and Im probably gonna list it for parts.
If it doesn't work, and you're interested in selling it, let me know as I may be interested in picking it up to try and fool around with, if the price is right.
Here we go:
I was trying to install a custom rom today (done it about 20 times before on different devices including this one).
Had rooted stock & CWM custom bootloader (unlocked using Casual months ago I think).
Flashed custom rom and (unfortunately) downloaded and flashed a file for the international version (GT-N7100).
Basically, I accidentally flashed the MJ5 custom bootloader by accident (again, it's for international version, which I have SCH-i605).
It's from here under the SPECIAL INSTRUCTIONS FOR 3.6 AND ABOVE heading
(don't ask why, I'm an idiot. Was trying to install this rom and just totally blew past the fact it was for international version)
I've tried using odin to flash "KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5" (stock rom) and "sch-i605-16gb.pit" as outlined in the countless 'Restore to stock rom/bootloader from bricked state' articles out there on the webs but it keeps failing. (Part 1b from here)
Current symptoms:
Boot loop almost instant at samsung logo with new N7100 line. Will not boot into bootloader but I can get it into odin download mode.
Using Odin3 v 3.07 (on multiple computers with the right drivers I'm pretty sure) I go into download mode and this is listed:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
WARRANTY BIT: 0
Odin hangs at 'Get PIT for mapping' if re-partition is checked, outputs the following if re-partition is unchecked (only auto-reboot and F. Reset Time checked)
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
After this point, it's like the phone stops responding to odin, because if I try to flash again or flash something else, odin just outputs:
<OSM> All threads completed. (succeed 0 / failed 0)
I've been at it for about 8 hours now and I know I'm getting desperate, so I'm hoping you all can help me out before I resort to new phone/sending in for factory reset
Thanks!
- John
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
nikhil.kdhand said:
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Click to expand...
Click to collapse
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Re: JTAG
Hälftebyte said:
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
he1calledbubba said:
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
Click to expand...
Click to collapse
Yeah many people use him. He's also here on XDA.
Let us know how it turns out. :good:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Numzi said:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Click to expand...
Click to collapse
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Numzi said:
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Numzi said:
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Click to expand...
Click to collapse
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Hälftebyte said:
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Click to expand...
Click to collapse
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Numzi said:
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Click to expand...
Click to collapse
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Hälftebyte said:
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Click to expand...
Click to collapse
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Numzi said:
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Click to expand...
Click to collapse
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Hälftebyte said:
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Click to expand...
Click to collapse
So Heimdall didn't work - it failed repartitioning and when I tried unchecking that, failed at bootloader, then at cache, etc. Do you think it's wiser for me to first try flashing the modem then do the SD Swap? or to just do the SD Swap thing on Jedi?
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Numzi said:
...
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Click to expand...
Click to collapse
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Hälftebyte said:
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Click to expand...
Click to collapse
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Numzi said:
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Click to expand...
Click to collapse
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Hälftebyte said:
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Click to expand...
Click to collapse
I decided to just get the JTag service now and just paid for it. I'll let you know if it really goes back to perfect.
Hello, well i have SGH-I777 and about a week ago the phone frezee so i turn it off and when i turned it on its just stuck on "Samsung galaxy" logo and i can not go in recovery mode.
Because i can go just into Download mode i tried to flash rom with Odin but idk what went worng now i have this message:
firmware upgrade encountered an issue. please select recovery mode in kies & try again.
I still can go to Download mode and use Odin but i tried to flash 4 (!) diffrenet "stock rom" but everyone of them wont work and the proccess stoped in the middle(factoryfs.img or sbl.bin or setupconnection or NAND Write Start!!)
So i give up and ask for help here! please what should i do and what im doing worng?
I download the stock rom from here and galaxys2root and some other places and nothing work everything stuck at some point..
HELP PLEASE! How can i fix this problem? and which rom i shold have after this (i had CM 10.1.3 and he have some problems and crash from time to time) is there any other better rom?
Thank you so much!
Amo5 said:
Hello, well i have SGH-I777 and about a week ago the phone frezee so i turn it off and when i turned it on its just stuck on "Samsung galaxy" logo and i can not go in recovery mode.
Because i can go just into Download mode i tried to flash rom with Odin but idk what went worng now i have this message:
firmware upgrade encountered an issue. please select recovery mode in kies & try again.
I still can go to Download mode and use Odin but i tried to flash 4 (!) diffrenet "stock rom" but everyone of them wont work and the proccess stoped in the middle(factoryfs.img or sbl.bin or setupconnection or NAND Write Start!!)
So i give up and ask for help here! please what should i do and what im doing worng?
I download the stock rom from here and galaxys2root and some other places and nothing work everything stuck at some point..
HELP PLEASE! How can i fix this problem? and which rom i shold have after this (i had CM 10.1.3 and he have some problems and crash from time to time) is there any other better rom?
Thank you so much!
Click to expand...
Click to collapse
Your phone seems to be soft bricked. Are the stock roms you downloaded .tar files or .md5 files? If they are .zip files or .rar files, uncompress them with 7zip. Did you put them in the PDA slot in ODIN?
@Amo5,
Sorry to be so late to answer your question, but I have been traveling out of town for the holiday.
Go to the Download Repository and get the latest stock distribution, I777UCMD8 Stock Binaries (Android 4.1.2 Jelly Bean). Enter download mode and flash that, and see if the flash will complete. If the flash completes, but the phone does not boot past the splash screen, enter recovery and perform a wipe data/factory reset.
If the flash is not successful, your phone may have nand read/write corruption, so post back here with the results of the above, and I will post the instructions for clearing nand r/w corruption.
StoneyJSG said:
Your phone seems to be soft bricked. Are the stock roms you downloaded .tar files or .md5 files? If they are .zip files or .rar files, uncompress them with 7zip. Did you put them in the PDA slot in ODIN?
Click to expand...
Click to collapse
Thank you for your answer, I already understood this soft brick and I downloaded of coruse the .tar files and I put them in the PDA slot in ODIN.
creepyncrawly said:
@Amo5,
Sorry to be so late to answer your question, but I have been traveling out of town for the holiday.
Go to the Download Repository and get the latest stock distribution, I777UCMD8 Stock Binaries (Android 4.1.2 Jelly Bean). Enter download mode and flash that, and see if the flash will complete. If the flash completes, but the phone does not boot past the splash screen, enter recovery and perform a wipe data/factory reset.
If the flash is not successful, your phone may have nand read/write corruption, so post back here with the results of the above, and I will post the instructions for clearing nand r/w corruption.
Click to expand...
Click to collapse
Thank you so much for your answer, you have nothing to be sorry about
I download the file from here like you said and the flash stuck again at SBL1.bin , anyway i can't go in recovery mode.
So it is nand read/write corruption like you said? what should i do now?
Thanks again both!
Amo5 said:
So it is nand read/write corruption like you said? what should i do now?
Thanks again both!
Click to expand...
Click to collapse
The problem MAY be NAND read/write corruption. It is also possible that you have a bad or flaky connection between the phone and the computer. Sometimes failed flash is due to USB cable or micro USB connector on the phone, or you may need to use a different USB port on the computer, or even another computer. If the problem is NAND read/write corruption, then the following should clear it.
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
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.
creepyncrawly said:
The problem MAY be NAND read/write corruption. It is also possible that you have a bad or flaky connection between the phone and the computer. Sometimes failed flash is due to USB cable or micro USB connector on the phone, or you may need to use a different USB port on the computer, or even another computer. If the problem is NAND read/write corruption, then the following should clear it.
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
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.
Click to expand...
Click to collapse
Thank you again, the Siyah 2.6.14 Kernel doesnt work, its stuck also at NAND Write Start!!
I tried also the full stock and its doesnt work also, about the SBL Bootloader i cant find the download there colud you give me the direct link? i get confused with all the links and descriptions there.
Amo5 said:
Thank you again, the Siyah 2.6.14 Kernel doesnt work, its stuck also at NAND Write Start!!
I tried also the full stock and its doesnt work also, about the SBL Bootloader i cant find the download there colud you give me the direct link? i get confused with all the links and descriptions there.
Click to expand...
Click to collapse
The I777 SBL is the very first item in the Download Repository.
creepyncrawly said:
The I777 SBL is the very first item in the Download Repository.
Click to expand...
Click to collapse
Its also stuck at NAND Write Start!! part, why nothing is working?
Amo5 said:
Its also stuck at NAND Write Start!! part, why nothing is working?
Click to expand...
Click to collapse
I would first suspect a problem with the connection. As I wrote previously:
The problem MAY be NAND read/write corruption. It is also possible that you have a bad or flaky connection between the phone and the computer. Sometimes failed flash is due to USB cable or micro USB connector on the phone, or you may need to use a different USB port on the computer, or even another computer. If the problem is NAND read/write corruption, then the following should clear it.
Click to expand...
Click to collapse
Try different cables. Try different USB port on the computer. If you can get access to a different computer, try flashing from that. That will be a good start to troubleshooting this issue.
creepyncrawly said:
I would first suspect a problem with the connection. As I wrote previously:
Try different cables. Try different USB port on the computer. If you can get access to a different computer, try flashing from that. That will be a good start to troubleshooting this issue.
Click to expand...
Click to collapse
I tried a diffrenets USB cables and USB port, next setp is another computer? and what if it doesnt work?
TY again for all the help!
Amo5 said:
I tried a diffrenets USB cables and USB port, next setp is another computer? and what if it doesnt work?
TY again for all the help!
Click to expand...
Click to collapse
In 99.9% of cases (I'm not going to say it's an absolute, but nearly so), when the phone can go into download mode it can be flashed. I'm not sure I know all the possible factors that would interfere with a flash, but the connection between the phone and the computer probably accounts for the vast majority of cases.
Have you ever had any problems with the USB port on the phone? You might try cleaning it with alcohol, not 80% as it has too much water in it, at least 90% or better.
Another thing you could try is flashing it using Heimdall from the command line instead of using Odin.
creepyncrawly said:
In 99.9% of cases (I'm not going to say it's an absolute, but nearly so), when the phone can go into download mode it can be flashed. I'm not sure I know all the possible factors that would interfere with a flash, but the connection between the phone and the computer probably accounts for the vast majority of cases.
Have you ever had any problems with the USB port on the phone? You might try cleaning it with alcohol, not 80% as it has too much water in it, at least 90% or better.
Another thing you could try is flashing it using Heimdall from the command line instead of using Odin.
Click to expand...
Click to collapse
sorry for my late answer, i have been away for the last week.
I just tried diffrenet latptop and again with my PC and same result still stuck at NAND Write Start or SBL1 its depened at the file im trying to flash(stock/kernel/sbl)
of coruse I tried different USB cables and even micro USB.
what next?
Amo5 said:
sorry for my late answer, i have been away for the last week.
I just tried diffrenet latptop and again with my PC and same result still stuck at NAND Write Start or SBL1 its depened at the file im trying to flash(stock/kernel/sbl)
of coruse I tried different USB cables and even micro USB.
what next?
Click to expand...
Click to collapse
There is little else I can add to help find a solution to your issue. I've already covered pretty much what I know about the SGH-I777 with respect to your issues.
Even though you have been unable to flash with the things you have tried so far, it still may flash for you if you keep working with it. I have seen users report in the forums here that they were able to get a successful flash on the xth try (I don't remember, 5th, 10th, 15th?)
It could possibly be an issue with your micro usb port on the phone? What have you done to trouble shoot that?
There are some things that could cause the reported behavior that are not related to the connection between the phone and the computer. I have seen one or two reports of actual memory module damage that would allow the phone to boot, but not to function correctly. In such a case, the damage is in a non-critical area of the memory.
If you live near an AT&T service center (not a store), you might take the phone in to the technicians there and ask if they can help you out. I know the phone is rather old and out of warranty, but they still might help.
You could send the phone to Samsung for repair. There will be a charge. I think you could determine how much by calling them ahead of time.
creepyncrawly said:
There is little else I can add to help find a solution to your issue. I've already covered pretty much what I know about the SGH-I777 with respect to your issues.
Even though you have been unable to flash with the things you have tried so far, it still may flash for you if you keep working with it. I have seen users report in the forums here that they were able to get a successful flash on the xth try (I don't remember, 5th, 10th, 15th?)
It could possibly be an issue with your micro usb port on the phone? What have you done to trouble shoot that?
There are some things that could cause the reported behavior that are not related to the connection between the phone and the computer. I have seen one or two reports of actual memory module damage that would allow the phone to boot, but not to function correctly. In such a case, the damage is in a non-critical area of the memory.
If you live near an AT&T service center (not a store), you might take the phone in to the technicians there and ask if they can help you out. I know the phone is rather old and out of warranty, but they still might help.
You could send the phone to Samsung for repair. There will be a charge. I think you could determine how much by calling them ahead of time.
Click to expand...
Click to collapse
Well my counter is about 25 now and many times the flash isnt count..
I living in country without AT&T service so i guess i send the phone to some lab or something..
About the connection between the phone and the computer i had troubles with it in the past so i just move to "Wifi file transfer" so i dont know if the problem still relavent, anyway i checked it in 2 differents computers and many USB cables.
SO what you saying is keep trying OR send it to some lab?
thanks again for all your help buddy
Hello gentlemen, here I am asking for help.
After trying different ROMs, I decided to go back to stock because of the frequent reboots. Today, after a few days since stock, all of a sudden the phone reboots itself and gets stuck on the Galaxy S3 logo (not bootloop). Opening recovery leads to a list of errors similar to this post, if not identical. Alas, being the d***head I am, i didn't backup EFS or system, or at least I don't know where did i put them lol
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
rp158 said:
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
Click to expand...
Click to collapse
Failed, here's the log
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Btw, the firmware I tried to flash was the one Kies gave me, then I downloaded it from sammobile. But since it didn't work out, could you explain me the second method, or link me a guide? Thank you
OP, your eMMC (your phone's, actually) might be on its way to the garbage - and might not. The problem is that if it is - it takes the whole phone with it.
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
After that, repartition FW + PIT, and if it fails - try working from a different PC. If it fails from any PC when trying to write eMMC - well, then you probably need to buy a new phone.
Repartitioning FW:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
or
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Hey @Jack_R1, thanks for your answer. Before I proceed with one of those guides, what do you mean with:
Jack_R1 said:
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
Click to expand...
Click to collapse
because I think I don't get what you mean
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
boomboomer said:
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
Click to expand...
Click to collapse
@boomboomer so is this to save files like pictures, music, videos, etc...? Because if that's the case, it doesn't matter really that much, the important matter is to make this phone work again. So, is there anything else I need to know before going with those guides?
Other that you'll probably need to buy a new phone, no.
boomboomer said:
Other that you'll probably need to buy a new phone, no.
Click to expand...
Click to collapse
Well, that's encouraging lol just out of curiosity, is there a reason becuase it stopped working all of a sudden and ****ed itself up so badly?
Nand memory wear.
Flash an official cwm or stock recovery.
Sent from a stolen phone!
When I try to install stock rom over odin (or custom recovery) always apear text NAND WRITE START FAILD! I trying to install PIT file but same message apear!Any advice on that problem!Thx
Post the Odin log because this log will help diagnose the problem.
Make sure you're using a USB port on the motherboard that isn't a shared port (must be on the motherboard for pc and the single port on a laptop (not the side with 2 ports)).
Use the original Samsung cable that came with the phone or another high quality cable from another device manufacturer.
Use the correct drivers. You can usually install kies and uninstall on the it keeping the drivers.
Put the phone in download mode BEFORE connecting the phone to the pc to ensure the correct drivers are loaded.
Check the md5 hash of the firmware you are using. It must match the original.
Load the firmware into AP/PDA field of odin. If you need to use a .pit file you must load the pit file AND the firmware file into odin and select the "repartition" check box.
If you still encounter issues you can call time on it as it will be dead.
If you feel like investigating you can flash a firmware in sections and see which one fails and that will give you some idea of which part of the nand is corrupt.
shivadow said:
If you still encounter issues you can call time on it as it will be dead.
Click to expand...
Click to collapse
Hi Man! I read something similar from you in another thread. could you elaborate a bit more, why do you think these phones are dead? Im starting to think that too, but I trying to find confirmation...
My phone started to do weird things 2 months ago. I install a stable rom, 5 file stock ROM in odin (AP, BL, CP, CSC, PIT), or debloated stock etc. Everthing is OK for a few days or weeks.
Then my apps stop responding, or force close, even base apps. then the phone basically "falls apart", and bootloops
all i could do is keep flashing clean roms in odin so I can use it for a few weeks (or days).
but today I couldnt do it anymore.
only DL mode and TWRP started but TWRP doesnt see most partitions, cant even mount the external SD card.
Code:
blah-blah
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
odin says this, basically always some repartiton fail or write operation fail message
tried a lot of combinations, 1 and 5 file roms, with or without PIT, even tried nand erase, bootloader update and efs clear options as a last ditch effort...
are you saying too, that this is the eMMC dying? and what could cause it?
---------- Post added at 01:26 AM ---------- Previous post was at 01:10 AM ----------
shivadow said:
the nand is corrupt.
Click to expand...
Click to collapse
sorry in the meantime I found you in another thread
would you say this too to my phone?
https://forum.xda-developers.com/showpost.php?p=76148578&postcount=6
Flash the latest stock as a single tar file in Odin, not separate files.
I don't recommend a pit file until you have tried all different USB cables and USB ports.
The reason the phones die is because solid state memory is flawed, android is flawed and the software that is produced on a daily basis is flawed because android itself is flawed..
Since when has "losing all your personal belongings" been an acceptable fix because from what I remember there were days gone by that if you encountered such issues where the only remedy is to have a full on clean out of your history you were entitled to compensation.
Would you throw away all your photographs because you wanted to change the album cover?.
So the moral of the story is clear. Don't have your life stored in digital format if you want to keep it safe as one day, for definite, your phone, tablet, pc or whatever else will definitely crap out on you and leave you in the lurch. We live in a consumer world so electronics are cheaply built with components becoming exponentially cheaper and poorer quality with the people becoming ever greedier for a bigger profit margin and will wring every penny out of a total failure.
I hope that explains the situation a tad..
audit13 said:
Flash the latest stock as a single tar file in Odin, not separate files.
I don't recommend a pit file until you have tried all different USB cables and USB ports.
Click to expand...
Click to collapse
man i tried that, many ways...
like 40 different combinations.
but of course it doesnt help that theres no rescue firmware for the 9305, only the 9300
at least i couldt find one that is meaningfully recent.
so i could only try my providers 2015 and 16 or so 1 file firmware.
yes i waited for pit or nand erase options until i exhausted the more mild options...
but FYI odin tick the repartition option automatically if you add the 4file+pit firmware so i kinda feel it meant to be done that way.
ill do 1 more run in the weekend and post if magically something happens beyond fail.
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
shivadow said:
Don't have your life stored in digital format if you want to keep it safe
I hope that explains the situation a tad..
Click to expand...
Click to collapse
i didnt do that i keep a very clean phone.
everything is in the cloud or on the ext sd.
i just want a working phone so I can call people lol
or a verdict that my phones dead.
kbuss said:
man i tried that, many ways...
like 40 different combinations.
but of course it doesnt help that theres no rescue firmware for the 9305, only the 9300
at least i couldt find one that is meaningfully recent.
so i could only try my providers 2015 and 16 or so 1 file firmware.
yes i waited for pit or nand erase options until i exhausted the more mild options...
but FYI odin tick the repartition option automatically if you add the 4file+pit firmware so i kinda feel it meant to be done that way.
ill do 1 more run in the weekend and post if magically something happens beyond fail.
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
i didnt do that i keep a very clean phone.
everything is in the cloud or on the ext sd.
i just want a working phone so I can call people lol
or a verdict that my phones dead.
Click to expand...
Click to collapse
Hang on a sec.. You say its a i9305.. You can't flash i9300 firmware to a i9305 as they are totally different phones. It is probably the reason you're getting pit errors.
You MUST try a stock i9305 firmware.
shivadow said:
Hang on a sec.. You say its a i9305.. You can't flash i9300 firmware to a i9305 as they are totally different phones. It is probably the reason you're getting pit errors.
You MUST try a stock i9305 firmware.
Click to expand...
Click to collapse
man please no.
of course I flash the correct FW
its just the 9305 forum section is dead in this thematic, theres no information there about these problems.
I always flash 9305 FW
BTW one of the problems that theres no "rescue FW" for it, so I cant really try that.
its easier for normal s3 owners.
basically I adressed You because I saw you wrote several posts in this eMMC matter.
but thx anyway.
im enroute for s7 or oneplus 5t now
maybe in the future i try to revive my 9305 w a donored motherboard just for fun.
but based on what you say, its possible that most of these phones will get a faulty memory in the future, so there will be no donors either.
or you change the motherboard for a donored one and that dies too in a few months...
opinions?
kbuss said:
man please no.
of course I flash the correct FW
its just the 9305 forum section is dead in this thematic, theres no information there about these problems.
I always flash 9305 FW
BTW one of the problems that theres no "rescue FW" for it, so I cant really try that.
its easier for normal s3 owners.
basically I adressed You because I saw you wrote several posts in this eMMC matter.
but thx anyway.
im enroute for s7 or oneplus 5t now
maybe in the future i try to revive my 9305 w a donored motherboard just for fun.
but based on what you say, its possible that most of these phones will get a faulty memory in the future, so there will be no donors either.
or you change the motherboard for a donored one and that dies too in a few months...
opinions?
Click to expand...
Click to collapse
The problem isn't emmc. Android is buggered from basic. I recently found out that android is flawed and that is most likely the reason that all phones right across the board fail.