Database Info

No download mode, no recovery, detected by odin, not kies

Hi,
I rooted my brandnew GT-P3110 with cf, flashed pacman and cwm recovery. I do not blame anybody alse for my issues but myself. I guess I messed up the restoring of NON-system-apps:
After a day of troublefree use the tablet randomly rebooted and came back with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". No booting into recovery possible, no booting into download mode, no regular boot. Just the same message over and over again. Battery is unremovable.
I installed Kies, updated it, it downloaded drivers but under "emergency recovery" my tablet didn't appear. I then followed the "Firmware Upgrade and Initialization" procedure wich downloaded the necessary files but aborted with a korean text shown in the attachment after replugging the tablet. I tried this with 2 different USB-cables on several USB-ports. Kies btw asked me to remove the battery (not possible) after entering device number and serial-number. I turned off by pressing the off button instead and it turned on again.
I uninstalled Kies, rebooted, installed the samsung drivers manually, rebooted. I installed odin 1.85 (and later 1.3) and downloaded my contry's stock firmware (and later a newer version of the same firmware and another country's stock) from sammobile. I tried to flash them first without "repartition" ticked, later with it ticked but without a pit file (i can't find it!). I got four different errors, two are attached, the third was somethign like "cant write (line 1876)" and "cant write (line 1440)".I tried three stock firmwares with two version of odin with two USB cords on everal ports on ONE computer. I remove the tablet every time, exited odin every time, run it as admin, disabled firewall, xp-antispy and antivirus. I'm on Windows 7.
Besides a million other threads I found this one, but I wasn't able to solve my issue with it: http://forum.xda-developers.com/showthread.php?t=1652398
For 48 hours i tried to solve this problem by myself. Now I hope to find out if there's a point in continuing or if I can give up and throw away the piece of samsung.
Cheers,
404

android404 said:
Hi,
I rooted my brandnew GT-P3110
404
Click to expand...
Click to collapse
Try odin 1.61 1.85 sometimes itll jar it loose

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
Thanks but it didn't work.
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Mine is still bricked. Good luck.

facing same problem in my samsung tab 2 p3100 after root

wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.

novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
Click to expand...
Click to collapse
Thanks. Well, I understand the theory. I have had trouble finding a PIT file that I am sure is for my device. I did save a PIT file but I think it is corrupt because using it requires me to let the battery die afterwards to get back to download mode. Same for the bootloader. I have a few things I've tried, but not sure I have one that is exactly for the GT-P5113 (in fact, I never did find a JB for the 5113 just the 5110 and it never would load).

Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.

I can do each thing you mentioned, but my device is not getting detected by my PC. When I insert USB it says USB not recognized and it is not detected by Odin, adb and anything else. I am stuck on Boot Logo for my P3100 and when I go into recovery, it says USB not recognized. Fully messed up. Can you help me out here.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
Click to expand...
Click to collapse

2 years later .... did you ever unbrick this? I'm dealing with a P5113 now that's stuck at the "Firmware upgrade encountered an issue" screen. <sigh>
wd5gnr said:
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
Click to expand...
Click to collapse

No. I finally sent it to one of these ebay guys who will JTAG it since I was too lazy to wire up one of my JTAG probes. They worked on it and said it was simply dead and the only alternative would be to replace the flash chips.
Bought a Nexus 7.

I've got the pit files for P311x and P3100 on my website https://sites.google.com/site/jrc2swebsite/downloads/samsung-galaxy-tab-2-70-p31xx

[Q] Am I bricked err?

I got my GNP 12.2 (SM-P900) a few weeks ago and just tried to root it using Odin and download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
However it paused at cache.img and after 10 minutes or so it just failed.
I've tried it a few times, but same thing, and on start up all I get is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried Kies 3 and Kies 2.6 but they both say my device is not supported, even if I try to go into Tools and do it it says the model name is incorrect and doesn't even give me an option to enter the serial number :-\
I looked around for a stock ROM but the closest I could find was the P901 and P905 (But I am the P900)
I don't really know what to do, so any advice would be much appreciated :angel:

Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that

jns20 said:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
Click to expand...
Click to collapse
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?

ChampagneFerret said:
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
Click to expand...
Click to collapse
IIRC you need to reflash recovery and you should be able to boot up again.

muzzy996 said:
IIRC you need to reflash recovery and you should be able to boot up again.
Click to expand...
Click to collapse
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.

ChampagneFerret said:
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
Click to expand...
Click to collapse
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:

icem237 said:
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
Click to expand...
Click to collapse
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.

ChampagneFerret said:
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
Did you use Odin 3.0.7 or 3.0.9? 3.0.7 is included with CF and MUST be used even though 3.0.9 is the latest. If odin was already installed on your PC and you used 3.0.9 bad things are going to happen.

ChampagneFerret said:
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.

icem237 said:
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
Click to expand...
Click to collapse
I tried both as well, and that's exactly what happened to me. During the process, my screen went all screwy and that's when it told me the process had failed.

I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?

Flash Stock Recovery
davschm said:
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Click to expand...
Click to collapse
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1

Russbad said:
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Click to expand...
Click to collapse
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?

davschm said:
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
Click to expand...
Click to collapse
Stock recovery is what your device originally comes with. CWM recovery is a modified version of that and it allows you more functionality.
When I messed up my update and root, my device would not boot up at all. I flashed the stock recovery and that enabled me to successfully root. No data was lost, no factory reset was needed and all my apps and settings were unchanged.

Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.

bioncorp said:
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
Click to expand...
Click to collapse
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!

Russbad said:
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Click to expand...
Click to collapse
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.

bioncorp said:
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
Click to expand...
Click to collapse
I finally got mine rooted by simply trying over and over. I re-downloaded the CF flash tool and used 7zip to extract it several times, and used a different usb port at least once. Not that I really thought there was a problem with my extraction or the download or my USB port. But from what i have seen posted, you just have to try it 3 or 4 (maybe even 10) times until you get lucky and it works.
I did at one point try to recover my Note 12.2 with the "recovery.img" instead of flashing it with a full factory re-image (which causes data loss) but that didn't work for me ether. But I later had good luck with using Odin 3.09 to flash TWRP. So at least I now have a good custom recovery and backup tool.

okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:

ChampagneFerret said:
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
Click to expand...
Click to collapse
FINALLY! :laugh: I got it to root!
I ended up using a different computer in the end and used Kies 2.6 for the drivers. I tried this a total of maybe 8 or 9 times, and it worked on the second attempt on the second attempt.
For the record, I left "md5" in the file when rooting, and that's when it worked.

[Q] GT-P5113 Only booting to: Firmware upgrade encountered an issue.

Tablet is a Samsung Galaxy GT-P5113TS 16GB version.
The initial problem with the tablet was that the Galaxy Tab logo appear but would just hang. It would boot into the firmware download menu with the buttons but not the recovery mode.
Attempted to flash a CWM and/or a Philz Recovery. After the attempted flash (via Odin 1.85) which failed. The tablet could no longer be recognized by Odin. Rebooted the tablet and it now comes up with the error: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The computer and Odin 1.85, and 3.09 all recognize it is there connects to it but fails to install a recovery file, a PIT file, a full firmware (P5113UEUCMK3_HOME.tar.md5)
Kies detects there is a device but fails to recognize it.
Attempting to use Kies says it cannot upgrade or initialize the GT-P5113 after the model number and serial number are entered.
Odin 3.07 is presently the only Odin that goes through the entire process of flashing the Stock ROM.
However, when it completes, there is nothing on the screen. If I leave it for 10 minutes, the screen still remains black.
If I then shut it down, it reboot with the same error message. After trying that and another stock ROM,
Odin is now failing at system.img with the error Xmit Write fail XmitData Fail.
Now it is caught in a boot loop which reboots the tablet constantly (known only by the sound of a USB device disconnecting and reconnecting) and will eventually stop after a random time at the "firmware upgrade encountered an issue". Then I can try it again. I have tried it with the only two 4.2.2 firmwares that I can find on samsung-updates.
I have tried this on two different computers with the same firmware. It just seems to get worse the more I try.
I am not even sure what firmware was on it before as it belongs to a neighbour who asked me to help getting working for him.
Holding down the power button for 10 seconds or more does not shut down or stop the boot loop.
Any suggestions at all would be appreciated it.
Is there anything else I can try that I haven't tried already like a bootable micro SD card? I have searched and I can't find one or the correct information to make my own.
EDIT: Tried it with a PIT file (signed_espresso_20120220_16G.pit) but it fails to upload the PIT file with the error "There is no PIT partition"
Thanks for any help.

Um... do you know if odin was ever run with "repartition" checked but no pit file?
Sent from my SGH-T999 using Tapatalk

Not sure at this point but it is in the realm of possibility.
If it was, is there any way to repartition it? Like with Heimdall or something?
EDIT: This is what was done since posting the above.
OK, I left the tablet charging overnight (well I slept 4 hours or so) and this time it installed the firmware without any errors.
I figure it was that the battery was dead. However, even though it installs the firmware, it still fails if I use the .pit file with the same error of no PIT partition.
Upon reboot, it comes back to the "Firmware upgrade encountered an issue" message again.

tokenpoke said:
Um... do you know if odin was ever run with "repartition" checked but no pit file?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes I tried to re-partition a couple of times using the 16GB PIT file as it is a 16GB Tab 2. But it never completed any attempt to do the re-partition.
It installs the firmware every time now but after when it is finished to do the reboot. The screen remains black until I hold down the power button to shut it down and then it reboots and presents me with the firmware encountered an issue message.

dechronic said:
Yes I tried to re-partition a couple of times using the 16GB PIT file as it is a 16GB Tab 2. But it never completed any attempt to do the re-partition.
It installs the firmware every time now but after when it is finished to do the reboot. The screen remains black until I hold down the power button to shut it down and then it reboots and presents me with the firmware encountered an issue message.
Click to expand...
Click to collapse
I think I wasn't clear enough.
Repartitioning without using a pit file can wipe the whole system into one or two partitions.
As far as I know that is an irreparable condition.
Sent from my SGH-T999 using Tapatalk

Is there a way to create a bootable Micro SD card that has a recovery image CWM/TWRP that will allow me to repartition?
I got a heimdall print-pit output from somewhere with the partition block sizes, etc.

Thanks for the help. I think the eMMC was bad to begin with because it was not booting into recovery or even flashing recovery images or booting any of them.
I was hoping there was a way I could make a bootable micro SD that I could format the eMMC, booting to a bootloader from the micro SD card and flashing the stock rom back on.

Hi Dechronic, and hi all xda-dev members here,
I think I am experiencing some problem with yours.
My friend asked me to fix his Galaxy Tab P5100. It shows yellow triangle with message "Firmware upgrade encountered an issue......"
I did try to enter recovery/download mode by hold power+vol up/down -> Display went blank, then back to yellow triangle.
I did try to flash stock ROM that downloaded from samsung website using Odin 3.10.7, 3.10.6 -> Failed
I did try to flash stock ROM that downloaded from samsung website using Odin 3.07 -> PASS. Then device went blank again. There was no sign of life , then I pushed the power button -> Back to yellow triangle, again.
I tried another flashing -> still same result.
I tried to install CWM from odin -> PASS -> screen went blank again
Did you successfully "wake" your device up? If yes then please share the steps here
Many thanks in advance.

haniefhusna said:
Hi Dechronic, and hi all xda-dev members here,
I think I am experiencing some problem with yours.
My friend asked me to fix his Galaxy Tab P5100. It shows yellow triangle with message "Firmware upgrade encountered an issue......"
I did try to enter recovery/download mode by hold power+vol up/down -> Display went blank, then back to yellow triangle.
I did try to flash stock ROM that downloaded from samsung website using Odin 3.10.7, 3.10.6 -> Failed
I did try to flash stock ROM that downloaded from samsung website using Odin 3.07 -> PASS. Then device went blank again. There was no sign of life , then I pushed the power button -> Back to yellow triangle, again.
I tried another flashing -> still same result.
I tried to install CWM from odin -> PASS -> screen went blank again
Did you successfully "wake" your device up? If yes then please share the steps here
Many thanks in advance.
Click to expand...
Click to collapse
Let me guess, you have KIES installed?
Uninstall KIES if you use Odin or Heimdall to flash via download mode.
Don't use USB-Hubs - use i direct port on your PC/Laptop.
Good luck!

I have the exact same error on my tab 2 P3100, I tried upgrading through Kies, after entering the Model and serial no it says does not support Initializing.
I downloaded the Stock Rom and flashed using Odin, it shows a successful flash only in Odin 3.07 (other versions of Odin it shows FAIL), but when it reboots it shows the same message "Firmware upgrade encountered an issue"
I un-installed Kies and flashed through Odin, yet again the same error message, its just stuck on this screen. Any help like what should I do next?

Same problem!! Any help?

Urgent help needed odin fail

Hi all I will keep it brief.
I have tried to flash with Odin 3.10.6, 3.10.7, 3.09, 3.10 root, twrp, stock firmware G920F but everything fails at "Nand Write Start" its driving me crazy. I've tried different versions of Odin, Twrp, and even Smart switch multiple times but nothing will write to the phone. ODIN ALWAYS FAILS AT NAND WRITE START.
My phone will only boot into download and NOTHING else not even recovery.
Any help welcome......

Try different firmware revisions. You flashing stock? What was the last fw successfully flashed?
Sent from my SM-G920F using Tapatalk

It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.

Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.

cooltt said:
It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.
Click to expand...
Click to collapse
Reactivation lockn as seen in download mode?.
Sent from my SM-G925F
---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
johnnyblaze1977 said:
Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.
Click to expand...
Click to collapse
Try to flash latest fw. Probably you've upgraded the bootloader to which cannot be downgraded.
Sent from my SM-G925F

What i've noticed with the S6 (and S7 i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the screen just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
NB: Tried latest BTU firmware, won't flash same problem "Nand Write Fail"
NB; Reactivation lock is OFF

cooltt said:
What i've noticed with the S6 (and S& i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the scree just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
Click to expand...
Click to collapse
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F

Rosli59564 said:
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F
Click to expand...
Click to collapse
Smart Switch is useless! I put in the model SM-G920F then the serial number and SS tells me the correct firmware is (EVR), downloads it, prepares it for installing, starts to install, gets to 1% then says "an error has occurred please use the Emergency code below to recover your phone" BUT there is no code! It says Emergency recovery code: .......nothing.
The main issue i'm experiencing is ODIN will not flash anything of any version, always fails at "Nand Write Start".
I've tried multiple versions of Odin, Stock Firmwares, TWRP, Root. Nothing will flash until the battery is dead, then when i try with a little charge for the first time Odin will usually flash the 1st file i give it (no matter what it is) then thats it, back to failing after "Nand Write Start".
Driving me crazy.

Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers

johnnyblaze1977 said:
Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers
Click to expand...
Click to collapse
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.

cooltt said:
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.
Click to expand...
Click to collapse
Already tried that. Flashing the EVR just doesnt work, ODIN Fails every time. Smart Switch says it should be EVR based on S/N but i just cant get it flashed.
Dont know what else to try.
Cheers

You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk

DarryDoo said:
You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Its WIN7 im using on both the work and personal laptop, neither of which have had any issues in the past.
IF i flash EVR, it fails, i then flash TWRP to reboot into Recovery, but i see there alot of unable to mount / error messages, possibly the partitions are damaged? I dont know.
cheers

Need help with potential softbrick with G955F

Hi guys,
I need help with my G955F. I was on Carotid's ROM and attempted to flash the AQL5 (BTU) firmware downloaded from Samfirm to go back to stock. The flash failed during writing the system.img and now it is stuck on the "Error has occurred while updating the device software" screen.
I can get into Download mode and I can boot into TWRP using ODIN.
Each attempt to flash a firmware in ODIN throws up a "FAIL" during the system.img write portion.
Each attempt to reflash a ROM from my external SD card in TWRP throws up an error while writing to system. /System is unmounted when I start up TWRP and I have to manually mount it each time.
The phone is "not supported" in Samsung Smart Switch.
Anyone have any ideas?

Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.

ianrobbie said:
Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.
Click to expand...
Click to collapse
Good observations.
You are correct, if the first flash fails, immediately re-enter download mode and flash again.

JeffDC said:
Yes, if the first flash fails, immediately re-enter download mode and flash again.
Click to expand...
Click to collapse
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.

ianrobbie said:
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.
Click to expand...
Click to collapse
Have not heard of that before - new to me, interesting find.
So the way to replicate is . . .

The way I got there was to have a screwed up install. I tried to flash a stock firmware and it generated a FAIL in Odin during the /system.img write.
The phone then rebooted to a pale green screen with a large triangle and exclamation mark advising me that the phone was in Emergency Recovery Mode and I should restore it by plugging it into a PC with Smart Switch installed.
Interestingly, Smart Switch refused to recognise my phone, saying it was an "unsupported device".
After numerous attempts to flash new firmware through Odin and TWRP (even using the two-step method of getting into Download mode) and using different cables/ports I was planning on getting it professionally repaired until I noticed that when Odin was running and I plugged the phone in, with the emergency screen on, it was "added" as it would be during Download Mode.
I loaded up the AQL5 firmware, and tried to flash. A progress bar appeared under the text on screen and it got about halfway through flashing /system when it failed again, but this time it has progressed much further than any other attempt.
I then reset everything, used an official Samsung cable and a port directly connected to the motherboard on my PC (I had been using a USB extension cable before) and attempted another flash and it worked!
I don't know how you would go about replicating those circumstances without risking your phone but if you find yourself stuck in the same situation, give it a try.
It worked for me.

Thanks, ianrobbie.