Hi all.
I wanted to flash my original rom from Hungary T-Mobile yesterday and it failed at hidden.img. But I can flash the United Kingdom / Ireland one on the phone.
Is there any way to flash back my original rom ? I downloaded all roms from sammobile.
Device: SM-G925F
Here is the Odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU2POFD_G925FTMH2POFE_G925FXXU2POFD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
1. Extract the md5 file with Winrar
2. Delete the hidden.img
3. Compress it to md5 file using this toolkit.
Link of the toolkit: http://forum.xda-developers.com/gal...lkit-skipsoft-android-toolkit-galaxy-t3101195
The toolkit might look a bit unfamiliar at first but just play with it for a while and you will know how to use it. It's not that hard,I was in your situation too. Cheers
Ryem said:
1. Extract the md5 file with Winrar
2. Delete the hidden.img
3. Compress it to md5 file using this toolkit.
Link of the toolkit: http://forum.xda-developers.com/gal...lkit-skipsoft-android-toolkit-galaxy-t3101195
The toolkit might look a bit unfamiliar at first but just play with it for a while and you will know how to use it. It's not that hard,I was in your situation too. Cheers
Click to expand...
Click to collapse
Thank you for your help worked ! :good:
can someone tell mr how to delete the hidden file? i cant delete it after i extract the MD5..
"Extract" or "Extract to" by using the mouse right-click button, not by double-clicking on the file!
f.
this solved
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
007sahil said:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
This worked for me as well! Thanks!
Hi mate!
i was having this issue on my phone, and what i did is:
Try to install again the firmware on ODIN and you'll get the FAIL message. After that your phone will stay stuck on "Firmware issue... use smart switch..." message on the phone boot.
Ok at this point, install the smart Switch on you PC, the samsung Drivers to Recognize your phone. Done that, plug you phone on the computer e open Smart Switch and wait the software open show your phone. At the top right of the smart switch, there is a button called "MORE", press it and click on the option "Emergency software recovery and initialization" like THIS
After all of this steps, follow the instructions posted on THIS FORUM
I did this steps and Solved the Hidden message when i was trying to install firmwares on Odin. I don't know exactly what smart switch did, i guess it corrected some problems on the partition table that was wrong.
Hope this help you!
Ryem said:
1. Extract the md5 file with Winrar
2. Delete the hidden.img
3. Compress it to md5 file using this toolkit.
Link of the toolkit: http://forum.xda-developers.com/gal...lkit-skipsoft-android-toolkit-galaxy-t3101195
The toolkit might look a bit unfamiliar at first but just play with it for a while and you will know how to use it. It's not that hard,I was in your situation too. Cheers
Click to expand...
Click to collapse
Hi,
How do u delete the hidden.img because its not in the firware folder?
asads89 said:
Hi,
How do u delete the hidden.img because its not in the firware folder?
Click to expand...
Click to collapse
Extract the MD5 file with Winrar and you will see hidden.img file there.
Hi I got the same problem with my SM-G925F from France.
I was in a bootloop with the s6 logo and "recovery is not seandroid enforcing". I trying to flash many different ROMs, they all failed. Finally I tried the G925FXXU3QOK9_G925FBOG3QOK9_G925FXXU3QOJO_HOME.tar and it failed at hidden.img. I renamed it and all but now I'm stuck in another bootloop with the s6 logo and the android in a blue background with galaxy spelt above it. I can't go to the recovery mode. I really don't know what to do now..
oceaneferrari said:
Hi I got the same problem with my SM-G925F from France.
I was in a bootloop with the s6 logo and "recovery is not seandroid enforcing". I trying to flash many different ROMs, they all failed. Finally I tried the G925FXXU3QOK9_G925FBOG3QOK9_G925FXXU3QOJO_HOME.tar and it failed at hidden.img. I renamed it and all but now I'm stuck in another bootloop with the s6 logo and the android in a blue background with galaxy spelt above it. I can't go to the recovery mode. I really don't know what to do now..
Click to expand...
Click to collapse
i am in the same
evox4 said:
i am in the same
Click to expand...
Click to collapse
I kept getting stuck at 'failed at hidden.img' did some google-ing and found out it's to do with my pit files.
Flashed ZEROLTE_EUR_OPEN_HIDDEN240M through the pit option in odin and bingo!
http://forum.xda-developers.com/galaxy-s6-edge/general/g925-pit-files-multi-thread-download-t3171636
(as for the 'recovery is not seandroid enforcing' message that's normal)
beanbean50 said:
I kept getting stuck at 'failed at hidden.img' did some google-ing and found out it's to do with my pit files.
Flashed ZEROLTE_EUR_OPEN_HIDDEN240M through the pit option in odin and bingo!
http://forum.xda-developers.com/galaxy-s6-edge/general/g925-pit-files-multi-thread-download-t3171636
(as for the 'recovery is not seandroid enforcing' message that's normal)
Click to expand...
Click to collapse
I have got one question for you.
Couldnt you enter into recovery mode? That pit save worked?
evox4 said:
I have got one question for you.
Couldnt you enter into recovery mode? That pit save worked?
Click to expand...
Click to collapse
after the pit files flashed the firmware flashed, then I flashed twrp recovery (remembering to uncheck auto reboot in odin before flashing twrp)
beanbean50 said:
after the pit files flashed the firmware flashed, then I flashed twrp recovery (remembering to uncheck auto reboot in odin before flashing twrp)
Click to expand...
Click to collapse
Why did you uncheck auto reboot?
Before you did root?
evox4 said:
Why did you uncheck auto reboot?
Before you did root?
Click to expand...
Click to collapse
it will automatically change back to stock recovery if it auto reboots, root came when I flashed a custom rom
beanbean50 said:
I kept getting stuck at 'failed at hidden.img' did some google-ing and found out it's to do with my pit files.
Flashed ZEROLTE_EUR_OPEN_HIDDEN240M through the pit option in odin and bingo!
http://forum.xda-developers.com/galaxy-s6-edge/general/g925-pit-files-multi-thread-download-t3171636
(as for the 'recovery is not seandroid enforcing' message that's normal)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446269
007sahil said:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
saved my phone thanks a million
glax0 said:
This worked for me as well! Thanks!
Click to expand...
Click to collapse
disculpa no hablo ingles, estoy desesperada porque mi equipo tiene el mismo error pero no entiendo tu explicacion, podrias adjuntar imagenes??
Related
Hi Guys.
I uninstalled some apps on my rooted I9300 and went to bed. When i woke up, the boot logo was stuck.
The only thing i can access is Download-mode (Volume-down + Home + Power).
I think the only way to get my phone up and running again, is through Odin (please correct me if I'm wrong)
What i have tried to resolve the issue:
- Tried downloading stock firmware from Sammobile.com and adding it in Odin v1.85, v3.04 and v3.07: Result: There is no PIT partition. v3.07 stopped at "SetupConnection.."
- Tried downloading rescue firmware here: http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6. The package included Bootloader, PDA, PHONE and CSC files. Tried running them through Odin, first with "Re-Partition" unticked - Failed. Then i tried with "Re-partition" ticked, and got this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
- I tried downloading KIES, to check if my phone connected, but it doesn't.
I just need to access CWM recovery so i can install a ROM, but when I hold Volume Up + Power, it shows the boot logo after a while and it stays there..
Im fairly new to Android, but I hope you guys have some tips for me.
This thread looks like a similar problem
http://forum.xda-developers.com/showthread.php?t=1785481
maatsby said:
This thread looks like a similar problem
http://forum.xda-developers.com/showthread.php?t=1785481
Click to expand...
Click to collapse
I can't find a solution in this thead. The firmware i downloaded from Sammobile.com did not include a .pit file, just one large tar.md5 file.
When using this in Odin i get the "There is no PIT partition" error.
nubz2k said:
I can't find a solution in this thead. The firmware i downloaded from Sammobile.com did not include a .pit file, just one large tar.md5 file.
When using this in Odin i get the "There is no PIT partition" error.
Click to expand...
Click to collapse
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
---------- Post added at 10:44 PM ---------- Previous post was at 10:41 PM ----------
You said you're keen to just get in to recovery, can u flash a recovery in odin and then use adb commands to get there? adb reboot recovery
http://forum.xda-developers.com/showthread.php?t=1796062
maatsby said:
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
You said you're keen to just get in to recovery, can u flash a recovery in odin and then use adb commands to get there? adb reboot recovery
Click to expand...
Click to collapse
Tried flashing Recovery-clockwoork...-i9300.tar now, but it keeps saying that there is no PIT partition
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
As far as I know, there is no point to adb without a recovery to boot?
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
Click to expand...
Click to collapse
Just a bunch of folders. Nothing looks like something i can put in Odin's boxes.
JJEGAN:
Can't extract the PIT file with Heimdall
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
nubz2k said:
Just a bunch of folders. Nothing looks like something i can put in Odin's boxes.
JJEGAN:
Can't extract the PIT file with Heimdall
Click to expand...
Click to collapse
Probably supposed to flash the three parts dont know i steer clear of Pits .
jje
JJEgan said:
Probably supposed to flash the three parts dont know i steer clear of Pits .
jje
Click to expand...
Click to collapse
The rescue firmware i downloaded included 3 parts + PIT file, but when i try to flash just the 3 parts, without the PIT, it fails.
Giving up! I've read through countless forums, and no one has a solution as long as the "Re-Partition operation failed." error shows in Odin.
RMA'ing the phone tomorrow.:crying:
Try firmware initialzation within KIES. You will be prompted for the model and serial number and voilá!!!! New
Flashing going under it's way!!!
Sent from my GT-I9300 using xda premium
worf_1977 said:
Try firmware initialzation within KIES. You will be prompted for the model and serial number and voilá!!!! New
Flashing going under it's way!!!
Click to expand...
Click to collapse
My device isn't recognized by KIES while in downloading mode. Is it supposed to? I've tried downloading the drivers, different cables and pc's.
Got any tips on how to get KIES to detect my phone?
Try re installing USB Drivers for samsung phones...
Sent from my GT-I9300 using xda premium
worf_1977 said:
Try re installing USB Drivers for samsung phones...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Tried it. The drivers are installed. Odin and Heimdall detects it, but KIES doesn't.
Then try to follow firmware initialization steps, and then, and only then, connect the phone... It will look for your terminal in download mode and update it.
Sent from my GT-I9300 using xda premium
worf_1977 said:
Then try to follow firmware initialization steps, and then, and only then, connect the phone... It will look for your terminal in download mode and update it.
Click to expand...
Click to collapse
Tried it. KIES downloads the firmware and fails at apx 69% telling me that "firmware initialization failed".
send it in
Already packed and ready for shipment.
Update:
The service department stated that they had to replace the mainboard on my phone.
I don't know if they noticed that the device was rooted and had a custom ROM, but it was covered by warranty and they are sending it back with no charge
How lucky you are then!!! Congrats and enjoy the new phone, whenever arrives
Sent from my GT-I9300 using xda premium
I own a Orange Samsung S2 i9100 handset. This was working without problem until this morning where it was stuck on bootscreen. Recovery mode does not work.
I tried to update firmware using Odin 3.07 however this does not work. It fails to install.
I am now stuck with the message "Firmware upgrade encountered an error".
I cannot access SD card so rooting etc seems unlikely.
Any ideas?
Win 8 Machine
i9100
ORA-I9100XWLSY-20130606160421
Check out @Hopper8 thread about odin :thumbup:
Thanks.
I assume you are referring to this thread ( [GUIDE][Troubleshoot a failed Odin flash] )?
http://forum.xda-developers.com/showthread.php?t=2345831
I have tried recovering with the two most applicable firmware packages below. I do not know what others to try. I don't think I can use custom packages as I cannot access my SD Card?
http://www.sammobile.com/firmwares/2/
GT-I9100 Galaxy S II
PDA: I9100XWLSY
CSC: I9100ORALS8
MODEM: I9100BVLS4
Added: 2013-06-05
GT-I9100 Galaxy S II
PDA: I9100XWLSW
CSC: I9100XEULS5
MODEM: I9100XXMS2
Added: 2013-05-29
Odin does recognize my phone but each PDA update fails... Kies is installed but not running. Phone still can only go download mode and due to failed Odin update now shows no boot screen (only firmware fail message). I cnanot restore on Kies as did not use this PC before with phone.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSY_I9100BVLS4_I9100ORALS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.. *** At this point I click start
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
andrewwright said:
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
Click to expand...
Click to collapse
I have tried philz recovery steps however this also fails in Odin.
I have tried different usb ports and reinstalling drivers. However Odin can see the phone, so it may not be a USB driver/port issue.
The biggest hurdle is getting Odin to run the flash.
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Original cable used? Have you read and tried all of whats in that thread?
andrewwright said:
Original cable used? Have you read and tried all of whats in that thread?
Click to expand...
Click to collapse
Original Samsung Cable.
Followed instructions in this thread using md5 files for i900?
http://forum.xda-developers.com/showthread.php?t=2201860
Odin packages instructions: Samsung Only
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
to remove yellow triangle, use TriangleAway
Click to expand...
Click to collapse
Whatever I do, Odin still seems to fall over at same place.
What do I need to perform a full factory reset? I take it use Odin to install firmware?
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Sent from a galaxy far, far away
Hopper8 said:
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Click to expand...
Click to collapse
This doesn't work. I have assumed from your suggestion that I use Odin to install firmware via Odin. This fails as well.
I now have a new SD Card I could use to load any software onto the device. However I can not get to the recovery mode screen at all (only download mode). Therefore have no idea what to do now!
I also think my phone is worse now - on download mode screen:
ODIN MODE
PRODUCT NAME: GT-I9100
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: CUSTOM
Click to expand...
Click to collapse
What guide should I use to completely factory reset the phone?
How do I check if the phone memory is correctly partitioned?
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
dmuk said:
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
Click to expand...
Click to collapse
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
niksyspidy said:
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
Click to expand...
Click to collapse
What version? I have tried 1.85, 1.87, 3.04, 3.07 - all fail.
Can I use Kies to repair if I have not previous Kies backups?
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.
[SOLVED]EDIT:
Here is how I solved the problem. I a xda thread I found a similar problem and someone claiming this:
-Downloaded stock firmware and extracted files
-removed .md5 off the end and extracted it again
-inside should be boot.img cache.img recovery.img system.img etc.
-used Unified Android Toolkit to create individual flashable files of each file
-flashed them in the order they came
-everything passed
Click to expand...
Click to collapse
So I tried it, and it worked till the last .tar with the system.img in it. Here I had to switch USB cables from the original Samsung one to my Usb cabel from the Amazon Fire Stick. And then it also worked. For the flashing I used Odin 3.10.6 and the firmware was the G925FXXU2COH2 one. I deactivated Auto-reboot in Odin and after flashing each file I manually restarted the phone to Download mode by holding Vol down + Home + Power.
/[SOLVED]Edit
Hey guys,
this is my current situation: Phone is stuck in cyan screen with "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". I can't use Smart Switch because I was rooted and on "XtreStoLite Deo-Mod Edition 2.3" when the phone bricked. ODIN does recognize the phone. I used Odin3 v3.10.6.
What I did to brick it:
- Downloaded a firmware and tried to flash it to unroot the phone, following that guide
http://forum.xda-developers.com/galaxy-s6/general/how-to-unroot-unbrick-galaxy-s6-t3110608
Model SM-G925F
Model name GALAXY S6 Edge
Country Germany
Version Android 5.1.1
Changelist 5599585
Build date Wed, 12 Aug 2015 08:11:31 +0000
Product code DBT
PDA G925FXXU2COH2
CSC G925FDBT2COH3
Click to expand...
Click to collapse
Since I was on "XtreStoLite Deo-Mod Edition 2.3" the device had the XXU2COH2 BL and stuff (I guessed)
- ODIN failed directly after NAND Write Start!!
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I tried to fix the problem:
- Flashing TWRP form http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866 --> Fails
-Flashing G925FXXU2COH2 stock firmware and G925FXXU2BOGB_G925FDBT2BOG8_DBT (from http://stockroms.net/file/GalaxyS6Edge/SM-G925F/Germany/5.1.1/G925FXXU2BOGB_G925FDBT2BOG8_DBT.zip)
- After finding this http://forum.xda-developers.com/galaxy-s6-edge/help/guide-s6-edge-unbrick-guide-t3187655 and some other threads I removed the hidden.img from both firmwares I already tried, repacked them and flashed with ODIN.
---> modified G925FXXU2BOGB_G925FDBT2BOG8_DBT fails after flashing modem
----> modified G925FXXU2COH2 fails like this:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Sooo.. according to the guide I mentionied I would need to flash pit and Stock firmware at once like this:
1) Get your device to download mode by using this combo "VolumeDown-Home-Power"
2) Open an UP TO DATE ODIN.
3) Find the corresponding .PIT file for your S6 EDGE.
4) Find the corresponding stock rom for your S6 EDGE.
5) Then put them into odin CORRECTLY. Rom to "AP", .pit to PIT
6) Make Sure these are checked: "Re-partition","NAND all erase"
7) Plug your device in and then press start.
Click to expand...
Click to collapse
But I am not sure if this is the right thing to do. Also I don't know which of the provided pits for the SM-G925F I am supposed to use? http://forum.xda-developers.com/gal...925-pit-files-multi-thread-download-t3171636/ Whats the difference between them? Aaaand I'm still not sure which firmware I should be flashing
I would really appriciate your help..
Small update:
Found this suggestion on reddit and tried it
If you've tried to flash firmware off of Sammobile, and had your heart stop when the flash fails, fear no longer.
To fix the soft brick:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
After flashing the hidden.img.tar I was stuck on the Samsung Logo (before the bootanimation) but I could boot into normal Downloading mode. Tried flashing the stock firmware without the hidden.img and got
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And I'm back to the screen saying I should use Smart Switch..
Well I again flashed the hidden.img.tar, then I could get in TWRP. I did restore on old backup and did a factory reset. The phone booted! So I dicided to try the unroot one more time. I was on kind a funny Baseband-Version so I decided to flash COH2 Bootloader and Modem, but Odin right after starting the NAND write and I was stuck on the Error massage from the beginning..
Flashed hidden.img.tar and the phone booted normaly.
What is going on? What do I need to flash or do to get back to stock?
In the device information I now have:
Modell: SM-G925F
Android-Version: 5.1.1
Basebandversion: G925FXXU2BOGE
Kernel-version: 3,10,61-Alex-V_1.2
Buildnumber: XtreStoLite Deo Mod v.2.3 - XXU2COH2
It is really kind of mixed up and I have know idea why I can't just flash with ODIN.
Worked for me but with very minor tweak
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Stuk in bootloop
spencersj said:
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Click to expand...
Click to collapse
After flashing boot.tar my phone is stuck in bootloop and nt coming out despite hard reset also and i m also unable to flash new fw via odin.
plz help.
it states SOLVED.....???
Back in the days I had a emmc problem with a Note 4. I made a image from a working device and booted it up from a sd card. Since s6 edge doen't have a sd slot I wonder how to restore it.
So I can enter Download Mode but not Recovery mode. It's a SM-G925F Belgian model. G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar is what I used with Odin but no luck. Also I tried with SmartSwitch with model and serial number and so but no luck either. After that I tried to flash twrp-3.1.1-0-zerolte.img.tar but still no Recovery Mode. The device turns on, schows the logo and reboots. Always bootloop. This happened after a week of using the new software update.
FYI: Not rooted
dyasten said:
Back in the days I had a emmc problem with a Note 4. I made a image from a working device and booted it up from a sd card. Since s6 edge doen't have a sd slot I wonder how to restore it.
So I can enter Download Mode but not Recovery mode. It's a SM-G925F Belgian model. G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar is what I used with Odin but no luck. Also I tried with SmartSwitch with model and serial number and so but no luck either. After that I tried to flash twrp-3.1.1-0-zerolte.img.tar but still no Recovery Mode. The device turns on, schows the logo and reboots. Always bootloop. This happened after a week of using the new software update.
FYI: Not rooted
Click to expand...
Click to collapse
You can use an OTG flash drive l
Same as you would sd card. What error did you get in odin when flashing the firmware you posted?
dyasten said:
Back in the days I had a emmc problem with a Note 4. I made a image from a working device and booted it up from a sd card. Since s6 edge doen't have a sd slot I wonder how to restore it.
So I can enter Download Mode but not Recovery mode. It's a SM-G925F Belgian model. G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar is what I used with Odin but no luck. Also I tried with SmartSwitch with model and serial number and so but no luck either. After that I tried to flash twrp-3.1.1-0-zerolte.img.tar but still no Recovery Mode. The device turns on, schows the logo and reboots. Always bootloop. This happened after a week of using the new software update.
FYI: Not rooted
Click to expand...
Click to collapse
i had a note 4 do the same thing
as previous poster said u should be able to do the same fix with a otg and flash drive
I already have access to Download Mode but not Recovery Mode. What pit file should I use?
ZEROLTE_EUR_OPEN.pit
ZEROLTE_EUR_OPEN_HIDDEN60M.pit
ZEROLTE_EUR_OPEN_HIDDEN100M.pit
ZEROLTE_EUR_OPEN_HIDDEN150M.pit
ZEROLTE_EUR_OPEN_HIDDEN200M.pit
ZEROLTE_EUR_OPEN_HIDDEN240M.pit
ZEROLTE_EUR_OPEN_HIDDEN300M.pit
Also when I flash with Odin it fails. When I delete Hidden.img from the tar the flash pass but still no Recovery Mode. Phone keeps retarting, showing logo, restarts, bootloop, ...
TheMadScientist420 said:
i had a note 4 do the same thing
as previous poster said u should be able to do the same fix with a otg and flash drive
Click to expand...
Click to collapse
I just remember I had to do the sd card thing because no download mode was working. But here DM works but no Recovery Mode
callumbr1 said:
You can use an OTG flash drive l
Same as you would sd card. What error did you get in odin when flashing the firmware you posted?
Click to expand...
Click to collapse
This error do I get when flashing without deleting Hidden.img
HTML:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dyasten said:
I already have access to Download Mode but not Recovery Mode. What pit file should I use?
ZEROLTE_EUR_OPEN.pit
ZEROLTE_EUR_OPEN_HIDDEN60M.pit
ZEROLTE_EUR_OPEN_HIDDEN100M.pit
ZEROLTE_EUR_OPEN_HIDDEN150M.pit
ZEROLTE_EUR_OPEN_HIDDEN200M.pit
ZEROLTE_EUR_OPEN_HIDDEN240M.pit
ZEROLTE_EUR_OPEN_HIDDEN300M.pit
Also when I flash with Odin it fails. When I delete Hidden.img from the tar the flash pass but still no Recovery Mode. Phone keeps retarting, showing logo, restarts, bootloop, ...
Click to expand...
Click to collapse
What firmware are you trying to flash and what region? Tell me this and I can tell you which PIT file
callumbr1 said:
What firmware are you trying to flash and what region? Tell me this and I can tell you which PIT file
Click to expand...
Click to collapse
G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar
dyasten said:
G925FXXU5EQD4_G925FPRO5EQE1_G925FXXU5EQCD_HOME.tar
Click to expand...
Click to collapse
Before you flash a pit file (as they can be very dangerous) try again to remove hidden.img. extract firmware with 7zip or something similar. Remove hidden.img and then repack. Then flash.
Or
Flash a different firmware
callumbr1 said:
Before you flash a pit file (as they can be very dangerous) try again to remove hidden.img. extract firmware with 7zip or something similar. Remove hidden.img and then repack. Then flash.
Click to expand...
Click to collapse
I did this yesterday and it passes in Odin. I unticked the "restart when done" thing in options. I restarted manually by power + home + volume down. When screen was off I immediately pressed power + home + volume up but it still doesn't go into Recovery Mode
dyasten said:
I did this yesterday and it passes in Odin. I unticked the "restart when done" thing in options. I restarted manually by power + home + volume down. When screen was off I immediately pressed power + home + volume up but it still doesn't go into Recovery Mode
Click to expand...
Click to collapse
Try a different firmware. Firmware is probably corrupted.
callumbr1 said:
Try a different firmware. Firmware is probably corrupted.
Click to expand...
Click to collapse
I downloaded 3 firmwares to test:
7: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU5EQD4/173643
6.0.1: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU4DPGZ/88414
5.1.1: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU3COI9/57688
It stays the same. When I restore with SmartSwitch it also says it's done but still in bootloop...
dyasten said:
I downloaded 3 firmwares to test:
7: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU5EQD4/173643
6.0.1: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU4DPGZ/88414
5.1.1: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/PRO/download/G925FXXU3COI9/57688
It stays the same. When I restore with SmartSwitch it also says it's done but still in bootloop...
Click to expand...
Click to collapse
https://www.sammobile.com/forum/showthread.php?t=30136
Look here for pit. Make sure you only flash the one for your device/firmware
callumbr1 said:
https://www.sammobile.com/forum/showthread.php?t=30136
Look here for pit. Make sure you only flash the one for your device/firmware
Click to expand...
Click to collapse
Thanks for the link. How to know the right model. I only know that's it's a SM-G925F from Belgium (PRO)