<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUCMB2_N8010O2UCMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should i do?
rawarauf said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUCMB2_N8010O2UCMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should i do?
Click to expand...
Click to collapse
Unplug
restart Odin
Reboot tab to download mode
plug in tablet
run Odin again
Happens from time to time
Also may want to redownload the file if it happens again just to be sure
Also, do you own an 8010? Just checking since you're flashing an 8010 file
What's that bit about "Get PIT for Mapping"
That shouldn't be there. You might have to give us some more info
ODIN always runs "get pit for mapping"... Don"t scare the poor guy...
If you don't know something don't answer, you could be the cause of another person's brick...
You don't need to worry about that.
Most bad flashes through ODIN are done because of user error. A lot of times the rom being flashed is corrupt. If it has an MD5 sum, you should get an MD5 checker and make sure the rom file isn't corrupt..... Try a different edition of ODIN, I've used 3.07 where 3.03 didn't work, same file, same cable and same tab... Worked fine...
Unless you've checked re-partition when you flashed, it looks like a bad sector on your NAND. You may need a pit file to correct but be VERY careful if you flash one of these as this is a definate brick if it is corrupt or for the wrong device....
I dont know how to add a pit file
ultramag69 said:
ODIN always runs "get pit for mapping"... Don"t scare the poor guy...
If you don't know something don't answer, you could be the cause of another person's brick...
You don't need to worry about that.
Most bad flashes through ODIN are done because of user error. A lot of times the rom being flashed is corrupt. If it has an MD5 sum, you should get an MD5 checker and make sure the rom file isn't corrupt..... Try a different edition of ODIN, I've used 3.07 where 3.03 didn't work, same file, same cable and same tab... Worked fine...
Unless you've checked re-partition when you flashed, it looks like a bad sector on your NAND. You may need a pit file to correct but be VERY careful if you flash one of these as this is a definate brick if it is corrupt or for the wrong device....
Click to expand...
Click to collapse
I downloaded the firmware 2 times it give the same error for both of them
I tried two version of Odin 3.04 and 3.07
i didnt try MD5 checker but i will try it if it is needed
I want to try a pit file but I don't know how to do it ,
Also I own a GT-N8013 which is the US version of Galaxy Note 10.1 i think this shouldnt be a problem to Flash United Kingdom Version since they are same device .
Thanks a lot for your help
Honestly, you DON'T want to try a pit file... Fastest way to brick your device...
Did you try using Mobile ODIN?
This means you do need to root your device but I found it seems to work a hell of a lot better than PC ODIN....
What I would do is restock original firmware then root device. This will raise the flash counter but then run triangleaway....
Load the rom file you are trying to flash onto an sd card and put it into the Note.
Make sure you use Mobile ODIN PRO as you can now flash the new OS and remove root if you want to going back to stock UK rom...
Flash away...
You should be "Official" in all statuses, both bootloader and settings with no flash count...
And trust me, if you start playing around with a pit file you are going to regret it....
Related
Hi everybody, I tried to upgrade my GT-P5100 to 4.2.2 but something went wrong and now I have a black screen with this message:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably I have selected Re-Partition but I didn't have a PIT file
The tablet had the stock rom and was not rooted.
I have Odin 3.07 and this PDA file but the procedure fails:
P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5
Code:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can't start Recovery or Download mode.
Can you help me?
Please if I need some more files write me all the links to download them, because many of them were hosted by hotfile and are no more downloadable...
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
That´s the Black-Screen of Death! Downloadmode is on in this window Connect to your PC, Odin will get your device
There should be no Problem with the file itself "<OSM> Checking MD5 finished Sucessfully.." - bad download will give another output because the MD5 is not valid if it´s broken.
Make sure you uninstall KIES before using Odin and run Odin as Administrator !!!
Kies in installed and Odin is executed as administrator
So what should I do?
GT-P5100 restore stock rom firmware odin
SOLVED using this guide and this file
dylan6662 said:
SOLVED using this guide and this file
Click to expand...
Click to collapse
Hello, i have the same your prblem with my galaxy tab 2 10.1 !!!...
do you remember how you managed to solve?
Do you remember what was the file of "this link" (http://www.bergfiles.com/i/bf5bdebbf2hci0) that is no longer active?...
I have absoluty need !!
THANKS !!!
Still on trouble
I still can find the right link to download the necessary file to flash on my gt-p5100 like this case , my screen just still say "Firmware upgrade encountered......"
cant log into download mode
but still detect on odin
please help me.
Hi all. I have the same problem. A message "Firmware .... an issue" Tried different Odin versions. With 3.07 and 3.10 versions looks like flashing is ok, Odin shows no errors. But nothing on the tablet, there's not status bar. And when flashing finished, Odin shows no errors. But tablet really not flashed. What the problem can be? Who can help?
HELP HELP
andrezerotwo said:
HELP HELP
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...opment/odin-gt-p5100-4-2-2-stock-rom-t3022183
try this link, it is stock firmware.
further if it can't solve by just flashing firmware, you can try pit file. but be careful before flashing this with odin, be sure of what it will do, there are guides to explain the proper process.
http://forum.xda-developers.com/showthread.php?t=2552155
I have the exact same problem, tried different odin versions, flashed the stock firmware, also tried different pc's, but no solution.
this is the error I keep getting on odin, Tried Kies it says P3100 does not support initializing. A friend says maybe its a motherboard issue, is that possible or just a firmware problem? What should I do next?
This is the error I get in ODIN.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100DDCNA3_P3100ODDCNB1_P3100DDCLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
v1v14n said:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi! With my tablet the same. I understand that eMMC has died, need a replacement and reflashing of the programmer.
GT-P5100 Firmware upgrade encountered an issu
Hi All,
I have the exact same problem with GT P5100, I cannot update my 5100,Itried different odin (1.85,307,309,1,7) versions, flashed different firmwares, but no solution.
this is the error I keep getting on odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMD1_P5100DBTDMD1_P5100XXDLL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Many thanks in advance,
So i recently rooted my i925 with this universal method...
http://forum.xda-developers.com/showthread.php?t=2403230
https://www.youtube.com/watch?v=QCBLOhWavT0
Then I decided to try and run the casuall "Jailbreak" software to get a custom recovery and unlocked bootloader and i just checked "I did it" during the root portion since I already was... and now I'm soft bricked. I can only get into the download mode and tried flashing with odin but no luck might be doing something wrong... Also tried following the cyanogen instructions which involve flashing a cwm recovery in download mode but still no luck. Any help would be greatly appreciated!!! If I hold power the screen will just flash the download mode screen on and off. I pulled the back off and pulled power. No difference.
Any ideas guys? This is the first time I've bricked anything since I've been here and it's got me pretty worried...
Still stuck is anyone has any ideas.
2rz_taco_sr5 said:
Still stuck is anyone has any ideas.
Click to expand...
Click to collapse
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
tselling said:
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
Click to expand...
Click to collapse
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
2rz_taco_sr5 said:
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
Click to expand...
Click to collapse
Maybe try Heimdall commandline. You can flash individual pieces.
tselling said:
Maybe try Heimdall commandline. You can flash individual pieces.
Click to expand...
Click to collapse
I'm just going to warranty it out with verizon. Ive warrantied phones before with no issue. usually for amoled screens that get shadows before the year warranty is up. Hoping all goes well.
im having this same issue, device keeps starting and then fails out, is there a solution to this?
Just tried to flash my SM-G920X It's a demo version of the S6.
( No calling. I'm ok with this it's not my problem)
Because it had the retail mode software installed that is a nuisance. I tried to flash over it many times. The retail mode locks the bootloader and can't be removed, its an administrator. wiping with android device manager just returns to stock+retailmode. retailmode documentation now says it can never be removed.
recovery mode wipe is forbidden.
cfautoroot and twrp both fail - its the retailmode lock
I tried flashing with G920FXXU1AOE3_G920FXEU1AODQ_XEU.zip with the *Phone bootloader update* ticked. It's a full unbranded rom from sammobile. It should have a bootloader?
It replaced the bootloader!!!!
Then hung. reboot phone.
"An error has occurred while updating device software. Use Emergency recovery function in Smart Switch PC software."
I can't. it demands a code from the programs last try when the update failed. Or you can try to use the sim registration serial number online check. But I no have sim! It's not registered. (it is not stolen I've already had a back and forth with samsung email serial number check. I got it from ebay)
Cannot power off! stuck on either download mode or emergency warning. Both bright blue/green whole screen. left it plugged in last night so it didn't drain the battery flat. Was very very hot this morning. I put it in the freezer for half an hour.
Think I can still use odin. It says added. I can still get it into download mode.
Just need to totally reflash the thing. But with what???
when I try to reflash bootloader I get...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOE3_G920FXEU1AODQ_G920FXXU1AOE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when I try normal odin whole flash of the ....XEU It just hangs here...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOE3_G920FXEU1AODQ_G920FXXU1AOE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
Holy ****! There is something very wrong with the way odin deals with these things.
I just copied out the recovery.img file from the stock rom I've been trying to flash. Copied it over the one in here twrp-2.8.6.0-zeroflte.img.tar as suggested by this post. http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736/page2
I have recovery back!
This is an odin **** up as he says.
reboot. exactly where I was retailmode still there account still there.
quatzar said:
Holy ****! There is something very wrong with the way odin deals with these things.
I just copied out the recovery.img file from the stock rom I've been trying to flash. Copied it over the one in here twrp-2.8.6.0-zeroflte.img.tar as suggested by this post. http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736/page2
I have recovery back!
This is an odin **** up as he says.
reboot. exactly where I was retailmode still there account still there.
Click to expand...
Click to collapse
me facing almost same situation, I want to remove demo crap from it, so I just root it as my first step but now phone is hang on Galaxy S6 live demo unit, I try to flash your recovery but I was not much lucky so please can you give some tips to solve issue, thanks
Any Possible Solution for my GT-P3100 "firmware upgrade encountered an issue"?
My P3100 gave up on me about a month ago. It was just stuck with "Samsung galaxy tab 2" on the screen. I tried rebooting many times with no success. I read so many threads and tried many alternatives using Odin but my tablet is still not responsive. Currently, it will just have the "firmware upgrade encountered an issue" message until the battery runs out. Pressing buttons won't get to download mode.
I was so disappointed for not finding any solution that I gave up searching for 2 weeks. Now I am giving it one last shot with proper guides before I throw it to the trash.
If anyone can spare me some time, this is roughly what I had been doing:
- Odin3 (versions 07, 09, 1.85, 10.6, 10.7)
- Firmwares from Sammobile (India, China versions)
- universal roots for galaxy tab2
- CWM_ROOT_P3100.tar.md5
- CF-Auto-Root-espressorf-espressorfxx-gtp3100
- I tried through Kies but it won't recognize the device, and "firmware upgrade and initialization" returns "GT-P3100" does not support initialization"
- Remove Kies, block antivirus, switch usb cables and usb ports!
All of this was done desperately, randomly, and with lot of frustration.
Now I am hoping that someone can guide me for one last chance. And I am willing to try anything regardless of the outcome.
Thanks in Advance!
Sibson
Will I ever get any attention? I am still struggling alone in the darkness, stumbling from here to there, but I still believe there gotta be someone out there who will have a bit of care for my concerns. I randomly got that far with my p3100:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100_JB_SBL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> Sbl.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But even though it renders a success, the screen still shows the "firmware upgrade encountered an issue..." message. So I tried again with another tar file and got the same thing:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espressorf-espressorfxx-gtp3100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"Firmware upgrade encountered an issue..." message still comes back.
Can you tell me anything about this? Please? Really begging now? :crying: ?
Don't run KIES or any KIES service in background while using Odin.
Android-Andi said:
Don't run KIES or any KIES service in background while using Odin.
Click to expand...
Click to collapse
Thanks for the reply. I have killed all Kies processes in the background but there is no change.
Uninstall KIES and reboot. Make sure keeping the drivers.
Start odin as administrator.
Connect your tab being on the issue screen ("Black Screen of death" - in case you like to search some more). On this screen, dlmode is running in background automatically.
Now make sure using the right rom for your device and use odin to flash it.
Good luck!
Android-Andi said:
Uninstall KIES and reboot. Make sure keeping the drivers.
Start odin as administrator.
Connect your tab being on the issue screen ("Black Screen of death" - in case you like to search some more). On this screen, dlmode is running in background automatically.
Now make sure using the right rom for your device and use odin to flash it.
Good luck!
Click to expand...
Click to collapse
I have followed the procedure but I still get no change:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100DDCNA3_P3100ODDCNB1_P3100DDCLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The tablet turns off after <ID:0/005> RES OK. I wait but it does not reboot. When I press the power button, the same "Firmware upgrade encountered an issue" shows up. I tried with 3 other rooms but ends the same.
I want to point out that my P3100 is the international version. Is there any specific recommendations?
Bad emmc? Could be the reason for bootloop too...
Android-Andi said:
Bad emmc? Could be the reason for bootloop too...
Click to expand...
Click to collapse
Thanks for that point. I was hoping to find a way to troubleshoot the emmc but couldn't find any. And if the emmc is at fault I guess there is nothing I can do.
The only update is that when I start Odin flash, the tab screen shows a bue progress bar but doesn't go all the way even though Odin says " PASS". I have attached a pic, in case any other possibility comes in mind.
https://www.dropbox.com/sh/oyq71eb1rqcbak4/AAArGKrWaWh5l7_4zILRIHCRa?dl=0
Thanks for your time. I will just keep surfing for possibilities and will update you if I get any solution.
You could try flashing an older stock rom, maybe 4.1 or 4.0.3
Hi Android-Andi,
I haven't gotten any solution but I got few changes. Thought I should share them in case it can bring some leads.
After all the failures I tried things randomly and I decided to flash the PIT. I used 3 pits from different sources but all failed with "there is no PIT partition".
Then I decided to use files from other models to flash. I downloaded a PIT file for Tab3 7.0 3G.
This also failed, but strangely the device was able to boot to "Samsung Galaxy Tab2 7.0" and nothing else (Pic. 1). I tried the buttons and was able to get real download mode for the first time (Pic. 2 &3).
Link to the pictures: https://www.dropbox.com/sh/oyq71eb1rqcbak4/AAArGKrWaWh5l7_4zILRIHCRa?dl=0
Even though I already flashed many times with odin "PASS", I noticed that the download mode screen says this:
PRODUCT NAME: GT-P3100
CUSTOM BINARY: NO
CURRENT BINARY: SAMSUNG_OFFICIAL
I tried to flash again with "PASS" but still the same.
So I guess that the old system is still inside with no change, and probably blocking the flashing procedure.
Now, my question is whether there is an option in odin to force and wipe everything before I flash.
sibson said:
I tried to flash again with "PASS" but still the same.
So I guess that the old system is still inside with no change, and probably blocking the flashing procedure.
Now, my question is whether there is an option in odin to force and wipe everything before I flash.
Click to expand...
Click to collapse
This (and your other symptoms) is consistent with a bricked emmc.
However, if that is not the case, you could try flashing it from linux using heimdall. I believe that has a wipe option.
I think you can go to recovery mode and do a factory reset and wipe cache. If nt there are ways in which you can flash a custom rom through odin and try going to stock firmware using odin now.
Hey all
I've got a soft bricked Samsung Galaxy S6 where I can boot to the boot loader but not the Android OS. After trying lots of different things and reading a lot of the forum posts on here I'd come to a dead end so thought I'd start my own tread as I can't seem to see a solution for this issue currently.
Here's what I originally tried
So I've downloaded and installed Odin 3.10.6 and set that up on my computer just fine, it's a Vodafone Galaxy S6 so I downloaded appropriate firmware from here - http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387.
I then put the phone in to the 'Download mode' by pressing Volume Down, Center Home, and Power buttons and then connected the phone via USB to my computer. Then I start up Odin which seems to realise that the phone is there, in the top left I get '0:[COM5]' and in the log I get '<ID:0/005> Added!!'.
After this I press on the 'AP' button and navigated to the upziped .tar.md5 file which I stated I downloaded earlier. Odin takes a few moments to do it's thing and load the file. After about 30 seconds in the log I now have this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Now I press the 'Start' button and the process fails, here's what my log says;
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I've tried so far to fix the problem
Downloaded and installed the Samsung Galaxy USB drivers, restarted the computer and repeated the whole process - no change
Downloaded and installed an older version of Odin (Odin 1.85) and repeated the whole process, same problem
I've then tried this whole process again on the three different USB ports (two USB 2, one USB 3) on my computer but have the same problem
Repeated the whole process on my girlfriends laptop - same problem
So that's where I've got to currently and I've run out of ideas, can anyone point me in a new direction to try here or maybe I've missed something stupid?
Better, closer warmer
So I've gotten a bit closer with this one but still not solved the problem.
So I was trying to think of new ideas to try and resolve my problem - when the phone is in 'download mode' it a few facts and figures on the screen ... namely the model number which is 'SM-G920F' and also a few other interesting details such as 'Reactivation lock' is off. So there's another thing I can eliminate from my list.
Anyway I Googled the model number and found another Firmware to download from Sammobile .com
So I downloaded this Firmware and gave this a try and got a lot further - this time it seems to start to install actually almost all the way to the end before failing. Here's what my log says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPB8_G920FVFG3DPB8_G920FXXU3DPB8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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)
The fact it's got this far to me means I'm cross USB drivers off the list too as surely the computer seems to know the phone is there right? ... So I'm not there yet but I seem to be much closer (I hope).
What I've done to try and fix it this time
After this first fail I've tried running Odin as Administrator, thought it may have been an permissions issue but I ran in to the same errors.
I thought I'd give it a try changing some settings in Odin and tick 'Flash lock' ... I know earlier it seems to have stated that reactivation lock was off but right now I thought I'd try anything - This completely stopped Odin in it's tracks when it got to 'Send lock information..' so this totally doesn't feel like the solution to me ...
So I'm stuck again until I think of something else to try ... If any of you lovely people out there have any clues or suggestions for something else I could try I'd love to hear from you ...
And I'm out of ideas!
Alrighty then!
I've tried this whole process with about 5 different firmware downloads now and I'm stuck simply because I'm out of places to download and try different firmware versions from.
Does anyone here have any suggestions for different firmware versions I could try or locations I could download and try different firmware versions from?
Any advice welcome!
N
try the CF- Boot for that phone, flash it with Odin
Richie G said:
try the CF- Boot for that phone, flash it with Odin
Click to expand...
Click to collapse
That's done it! Thank you!
And for all you future people reading this who might bump in to this post with the same problem here's what I did.
I found a 'CF Auto root' file for the version of my phone - CF stands for Chain Fire and you can get them from a quick google or from somewhere like www autoroot chainfire eu
This file is simply a tar.md5 file and you treat it like any other firmware file - In Odin click on 'AP' select the file and just hit start, as simple as that really.
N
hazardous_waster said:
So I've gotten a bit closer with this one but still not solved the problem.
So I was trying to think of new ideas to try and resolve my problem - when the phone is in 'download mode' it a few facts and figures on the screen ... namely the model number which is 'SM-G920F' and also a few other interesting details such as 'Reactivation lock' is off. So there's another thing I can eliminate from my list.
Anyway I Googled the model number and found another Firmware to download from Sammobile .com
So I downloaded this Firmware and gave this a try and got a lot further - this time it seems to start to install actually almost all the way to the end before failing. Here's what my log says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPB8_G920FVFG3DPB8_G920FXXU3DPB8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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)
The fact it's got this far to me means I'm cross USB drivers off the list too as surely the computer seems to know the phone is there right? ... So I'm not there yet but I seem to be much closer (I hope).
What I've done to try and fix it this time
After this first fail I've tried running Odin as Administrator, thought it may have been an permissions issue but I ran in to the same errors.
I thought I'd give it a try changing some settings in Odin and tick 'Flash lock' ... I know earlier it seems to have stated that reactivation lock was off but right now I thought I'd try anything - This completely stopped Odin in it's tracks when it got to 'Send lock information..' so this totally doesn't feel like the solution to me ...
So I'm stuck again until I think of something else to try ... If any of you lovely people out there have any clues or suggestions for something else I could try I'd love to hear from you ...
Click to expand...
Click to collapse
solved ? if not do let me know
Bhargav Hegde said:
solved ? if not do let me know
Click to expand...
Click to collapse
Yes this is now solved thank you Bhargav