Related
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
gecafe said:
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
In download mode you can install the last stock 4.1.2 Jelly Bean UCMD8 firmware using the program Odin follow this complete tutorial :
http://www.android.gs/flash-android...d8-update-for-the-att-samsung-galaxy-s2-i777/
After installing the stock ROM root your phone in this way:
1-Download Framaroot apk file into your device.
2-Go to Menu—>Download, locate the Frameroot apk file.
3-Press on Frameroot apk file in the Download folder. A pop-out windows ask for confirmation, press confirm/yes to proceed with Framaroot installation.
4-Once Framaroot successfully installed on your device, you shall find Framaroot icon in the Menu.
5-Press on Framaroot icon in Menu to launch the app.
6-In Framaroot user interface, choose Aragorn exploits within the list of exploits.
7-You shall now receive a exploit results: “Success… Superuser and su binary installed. You have to reboot your device”
Sent from my SGH-I777 using xda app-developers app
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gecafe said:
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
pepe100 said:
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
That's what i used, but im gonna install it again
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
gecafe said:
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
Click to expand...
Click to collapse
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
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.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
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:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
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.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
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
Thanks mate im gonna try it, but how do i get recovery mode, i tried to do it but it didn't work, i tried this:
Press volume+ and volume- at the same time 5 seconds and later press power button, i always get to the download mode.
OK guys, i have not solved my problem but i could investigate something thanks to my friend's i777 phone, and this is:
I noticed he had Rom manager, and he said he uses it lot of times and his phone have not gotten a problem, so i tried the rom magager recovery mode (what i tried and f***** my phone), the phone worked great and did not have any problem, after trying lot of things i decided to use the NQ antivirus, and it detected the rom manager as a virus and dangerous app i had to uninstall, actually just tried it in a i777 phone, tomorow i'll try on a different phone to see if this is normal.
Im gonna keep investigating about what rom manager does after solving my problem.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
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.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
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
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
gecafe said:
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Click to expand...
Click to collapse
You need to try a different known good usb cable, or different ports on the computer, or even a different computer to see if you can get Odin to complete. If you are absolutely sure that the reason Odin does not complete is not due to the above, then you may have a firmware problem that is beyond my ability to help you, or you may have some kind of hardware issue.
If it were my phone, I would probably send it to Mobile Tech Videos, since they are reliable and very good, but if you are not willing to spend money, then I don't have anything else to suggest.
Edit: It occurred to me that you may not have followed the full sequence. Did you get to step 4, and if not you need to try to flash the sbl.tar by itself in the pda slot and then go back to step 1.
I have been there...
This has happened to me a couple of times. You can either do a complete flash of a stock rom and go from there, OR, you can flash a recovery kernel. There is an old Sylah image floating around. You can flash this with the Odin tool. I believe Odin 3.07 worked best for me.
SteveMurphy said:
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
Click to expand...
Click to collapse
First of all is im a newbie in XDA i saw the warning when i joined, it seems u got mad, if u cant be patient with a noob, dude just let others help me.
Thanks im gonna try another pc and cable.
I tried to flash a new ROM today, and have had some really bad things happen just one after the other. I'll try to give the rundown as complete as possible:
I downloaded this ROM: http://forum.xda-developers.com/showthread.php?t=2565674
Threw it on my SDCard. Used TitaniumBackup, Booted into Recovery to create a save of the ROM I was using (way outdated Jelly'Beans'), cleared all the necessary settings, and loaded the new ROM. It completed successfully, but upon reboot would hang at the Samsung loading screen.
I dug into the FAQ of the above ROM, located here: http://forum.xda-developers.com/showpost.php?p=47597316&postcount=4056&nocache=1&z=2785911354639757
it says: If you didn't update the bootloader since Android 4.1.2 flash MJ5 bootloader or newer --> ND3 is latest available bootloader - find download link below
So I load back into recovery and use my restore point. I hit the link, download the BL, and use ODIN to load it up. Reboot the phone.. now it constantly flashed the boot screen, but I notice the Samsung boot now has GT-N7100 beneath the logo. What the hell. Back on the FAQ I realize it links to a BL for a completely different version of the Note 2.
I can still hold down volume/home/power and access the downloader.
Using http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1 ODIN v3.07, root66_VZW_stock_system.tar.md5, and sch-i605-16gb.pit I am attempting to return to stock. ODIN is returning these errors:
Occasionally, it will hang at Get Pit for Mapping, and never move, forcing me to unplug the device, remove the battery completely ( or else my PC will fail the software install when plugging back in) or if I turn Re-Partition off I get this error:
<OSM> Please wait..
<OSM> root66_VZW_stock_system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any way to salvage?
Thank you in advance for advice.
UPDATE 1: Removed and reinstalled Samsung USB drivers, restarted PC.
Is it possible that I need flash to a previous bootloader to get back to the stock version outlined in the ODIN thread I linked? If so, can anyone direct me toward a filename?
jenkemdealer said:
I tried to flash a new ROM today, and have had some really bad things happen just one after the other. I'll try to give the rundown as complete as possible:
I downloaded this ROM: http://forum.xda-developers.com/showthread.php?t=2565674
Threw it on my SDCard. Used TitaniumBackup, Booted into Recovery to create a save of the ROM I was using (way outdated Jelly'Beans'), cleared all the necessary settings, and loaded the new ROM. It completed successfully, but upon reboot would hang at the Samsung loading screen.
I dug into the FAQ of the above ROM, located here: http://forum.xda-developers.com/showpost.php?p=47597316&postcount=4056&nocache=1&z=2785911354639757
it says: If you didn't update the bootloader since Android 4.1.2 flash MJ5 bootloader or newer --> ND3 is latest available bootloader - find download link below
So I load back into recovery and use my restore point. I hit the link, download the BL, and use ODIN to load it up. Reboot the phone.. now it constantly flashed the boot screen, but I notice the Samsung boot now has GT-N7100 beneath the logo. What the hell. Back on the FAQ I realize it links to a BL for a completely different version of the Note 2.
I can still hold down volume/home/power and access the downloader.
Using http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1 ODIN v3.07, root66_VZW_stock_system.tar.md5, and sch-i605-16gb.pit I am attempting to return to stock. ODIN is returning these errors:
Occasionally, it will hang at Get Pit for Mapping, and never move, forcing me to unplug the device, remove the battery completely ( or else my PC will fail the software install when plugging back in) or if I turn Re-Partition off I get this error:
<OSM> Please wait..
<OSM> root66_VZW_stock_system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any way to salvage?
Thank you in advance for advice.
UPDATE 1: Removed and reinstalled Samsung USB drivers, restarted PC.
Is it possible that I need flash to a previous bootloader to get back to the stock version outlined in the ODIN thread I linked? If so, can anyone direct me toward a filename?
Click to expand...
Click to collapse
Well hate to tell you this but you need JTAG service. There is NO way to recover from flashing a different phones bootloader.. That is why it is a GREAT idea to read before flashing random things unto your phone
UPDATED NAND FIX 2015
First of all I saw Some people saying Nand Write Fail And No Fix
Can Do it....!
Cygwin For Windows
NotePad++
7Zip
AABox
Odiin
your brick (i mean phone)
Stock Firmware or any TAR with 4file better
USB Drivers and all SAmsung Drivers
Getting Ready
Please Dont use Aabox Vit Packet 1 or SupperSS Nand if you are doing this Method
Cygwin - use as Linux Shell
Cygwin For windows
NotePad++ - for Editing All CodesNote Pad ++ Download
7 Zip for Open zipAnd Extracting Tar Md 5 and zips download here
AABOx for Verify and Sum CodingAA-box is need for coding rom for tar and its download link is not available at because of Under Maintenance and update. Its Ok i will guide you the coding manually
OdinWe Need Odin .85 or 65 if you have " AAbox 2 " its solved. odin3 1.85 download
UPDATING WAIT...!
//----------------------------------Below is old Post 1---------------------------------------------//nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Note- Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Press thanks if you done.
Mod Edit:- : Links Removed & Thread Closed.
ErickNoz said:
nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Press thanks if you done.
Click to expand...
Click to collapse
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Updated
eniac0 said:
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Click to expand...
Click to collapse
Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
ErickNoz said:
Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Click to expand...
Click to collapse
wow, i would not have figured that out, but it certainly explains why that error has started appearing so often in different threads and sites now.
I had stopped trying various ways to flash my phone to avoid doing something stupid but i think I'll give your method a try now that i understand where it comes from. I am not super eager to mess with pit files but i believe to have found the right one so I'll give it a try.
Thx.
eniac0 said:
wow, i would not have figured that out, but it certainly explains why that error has started appearing so often in different threads and sites now.
I had stopped trying various ways to flash my phone to avoid doing something stupid but i think I'll give your method a try now that i understand where it comes from. I am not super eager to mess with pit files but i believe to have found the right one so I'll give it a try.
Thx.
Click to expand...
Click to collapse
You are welcm... keep in mind friend don't us bad or different pit files u will be bricked.
Always keep in mind to have a breathing phone... if its dead .....you will have to use it as a paperweight.
So use correct pit
Use correct sbl and other bin files to flash
Ur bootloader or download mode is for wake up from sleep.. not done if dead.
If you press thanks button that my secret
ErickNoz said:
nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Note- Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Press thanks if you done.
Click to expand...
Click to collapse
Hi
Thank you for your possible solution. Unfortunately, I have never used Cygwin before, and I am not sure how to follow your steps. Is there any chance you could write the procedure in a little more detail?
I have been ROM Flashing for a while, but I have not tried this method for solving the NAND write problem. I have been trying to deal with this, since the KitKat release came out, but now, becaue I cannot upgrade, some of my apps have stopped working.
Thank you!
msl said:
Hi
Thank you for your possible solution. Unfortunately, I have never used Cygwin before, and I am not sure how to follow your steps. Is there any chance you could write the procedure in a little more detail?
I have been ROM Flashing for a while, but I have not tried this method for solving the NAND write problem. I have been trying to deal with this, since the KitKat release came out, but now, becaue I cannot upgrade, some of my apps have stopped working.
Thank you!
Click to expand...
Click to collapse
Can I know you device history before nand write
ErickNoz said:
Can I know you device history before nand write
Click to expand...
Click to collapse
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<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)
Woooow Nand write
msl said:
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<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)
Click to expand...
Click to collapse
Wooow this is the correct nand write fail caused by md5 or tar prob.
Only Use odin1.87 or 1.3 version
And untar ur md5 or tar firmware
Then tar back with the given order by me above 1st post.
It will be ok. Realy...
ErickNoz said:
Wooow this is the correct nand write fail caused by md5 or tar prob.
Only Use odin1.87 or 1.3 version
And untar ur md5 or tar firmware
Then tar back with the given order by me above 1st post.
It will be ok. Realy...
Click to expand...
Click to collapse
Hi
But, if it was a problem with the md5 or tar file, wouldn't everyone else also have the same problem? This md5 is from sammobile, it should be an official Samsung release, and I am sure thousands of others are using it.
Secondly,
How do I untar the file exactly, I have never done this before, I am not familiar with the software you describe in the original post.
Do you know where I can find instructions on doing this, or would you have time to write a very quick instruction ?
It sounds like I have to take the file apart and put it back together again.
Update
msl said:
Hi
But, if it was a problem with the md5 or tar file, wouldn't everyone else also have the same problem? This md5 is from sammobile, it should be an official Samsung release, and I am sure thousands of others are using it.
Secondly,
How do I untar the file exactly, I have never done this before, I am not familiar with the software you describe in the original post.
Do you know where I can find instructions on doing this, or would you have time to write a very quick instruction ?
It sounds like I have to take the file apart and put it back together again.
Click to expand...
Click to collapse
Use Cygwin for tar and untar
Install cygwin first google it
Or
Use Tar box by AFx
Hi, I downloaded a ROM from sammobile and I don't have all those files.
My files are:
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
sbl.bin
zImage
Should I do like you said until the 4 (because I have the first 4 files from the tar command) and then write the others or I need to find one ROM that have system and recovery?
I hope my pit files is right too.
And another question:
I don't understand everything from this:
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Click to expand...
Click to collapse
1- Tick repartition
2- Update bootloader
3- Click reset
4- tick Auto reboot
5- Choose the downloaded pit file
6- Choose the created tar into PDA
Is it right? If yes, could you explain the "update bootloader" ?
Thanks
[Query] to same problem
eniac0 said:
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Click to expand...
Click to collapse
Hi There,
I have been struggling with same problem.. NAND WRITE FAIL
I had initiated a thread too in this context.
Want to know, if your attempt on device solved the problem ?
Thanks
Hi, ultimately no, i was able to depackage the rom but not fix it. It didn't have all the same components mentionned by erick and i wasn't sure how to compensate for the missing ones, were they mandatory, missing because obsolete, i don't know.
It gave me hope but it ended nowhere. Also all experts i contacted were not able to fix it and samsung won't even touch it because it was rooted.
I am thinking about putting a bounty on xda here to hire some help.
didnt fix n7100
Hi I couldnt find the boot.bin on extracrting 3 different md5 files. However, i did the steps as told but didnt work i make the repair.tar with cygwin .
vmware fusion for macos
Had the same issue using a virtual machine via vmware fusion for macosx. I switched for parallel desktop then flashed the last stock firmware and right pit file (repartition thicked).
At first boot possible boot loop on Samsung logo but resolved by wipe data / factory reset with stock cwm.
My phone's issue ended up being the eMMC chip busted. Had the phone repaired for about 150$, which i thought was cheaper than a new Note 2.
Solution
msl said:
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<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)
Click to expand...
Click to collapse
I had the same problem until 5 minutes ago and you can solve it by:
Going to
-Developer options-
Allow "USB debugging"
Uncheck the "Veify apps via USB" box
Let me know if it works
Kind regards
SM-N910C
4.4.4
Odin3 v3.07
CF-Auto-Root-trelte-treltexx-smn910c.tar.md5
Svenarchy said:
I had the same problem until 5 minutes ago and you can solve it by:
Going to
-Developer options-
Allow "USB debugging"
Uncheck the "Veify apps via USB" box
Let me know if it works
Kind regards
SM-N910C
4.4.4
Odin3 v3.07
CF-Auto-Root-trelte-treltexx-smn910c.tar.md5
Click to expand...
Click to collapse
I can't acces developers options because my device is soft bricked. I downloaded the jelly bean firmware because that what firmware the device was on (I believe) a year ago when I rooted the device for a co worker the link is here http://galaxynote3root.com/galaxy-note-3-stock-firmware/ any help would be marvelous so I can unbrick this darn phone TIA
I dont understand these instructions they are too advanced. The title of this post looks very promising as I am basically in an emergency to get my phone fix due to the NAND write fail issue but the OP does not state any helpful information including download links, where to get the files from, which files they are, what to do rather than one word instructions :S - We come on here expecting to get help (and to help others) so please somebody reply to me on what I have to do to get this fixed. (ask me for details if you are kind enough to help)
Thank you.
So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
es0tericcha0s said:
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
Click to expand...
Click to collapse
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nynten said:
So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
Click to expand...
Click to collapse
If Odin fails to work when you try to flash the firmware, then try to flash the ROM again, but without closing Odin. Sometimes we have to try like 5 times for it to work.
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
es0tericcha0s said:
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
Click to expand...
Click to collapse
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Nynten said:
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Click to expand...
Click to collapse
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
es0tericcha0s said:
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
Click to expand...
Click to collapse
Thanks, worked perfectly.
:good::highfive::victory: