Hi people,
Yesterday my 10.1 was slow as something very slow again, its internal memory was nearly full (frkn Rayman is 5 gig by now) so I deleted some little games through the aps-manager. And also "google text to speech" which surprised me a little bit, i thought that woud be one of the million apps i dont use but have to keep, but he led me deinstall it. Happy, i went to bed.
This morning I took the thing and started Animation Throwdown, which is in part on a micro-sd ( I recently put some apps on the sd, again with the app-manager. Didnt work before kit-kat, but works now i guess.
During some loading screen it suddenly rebooted and halted at the glowing SAMSUNG logo.
I turned it of by pushing the power button 10 secs some times, Then i took out the mini-sd. I think after that it didnt really power down anymore, when i tried it always rebooted.(This is solved by attaching the power..why???)
I cant enter recovery mode, just download-mode.
So I got Kies and Odin and a stock os. I just recently updated to kitkat, so i took this one.
Installed kies, shut it down, shut down the single kies process, start odin in admin-mode (every odin version i found tested), add firmware, connect tab in download-mode. It gets detected. But all the time:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE4_N8000OXADNE4_N8000XXUDNE1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed
I googled and found a gazillion threads on stuff like this, most times not solved but rather old. According to this either something broke, my computers usb suck (possible) or its a general problem with odin and note 10.1 and .tar files. There seems to be a chance that making my own .tars could help, but i dont know i i will be able to learn that stuff...
Ah, installing twrp doesnt work either, its another error though.
Any tips? Something broke? Should i try another firmware (will have to wait for this, sammobile stuff is down for non-premium members. There is an eplus (carrier) version, but the tab was unbranded bought from german retail "Saturn". Would trying out lolipop be a good idea?
I know this stuff is old, but i would really like to get at least my data back ;(
NAND write fail .
See multiple identical posts .
Its failing to write to memory block as possible damaged Nand or wrong files flashed .
Related
Hey all,
So yesterday I rooted using PingPong root, went fine, didn't trip Knox etc etc.
Installed Lucky Patcher, ended up getting the "out of space" error when trying to install apps so done a factory reset.
Get up to the point when setting the phone up and it just hung at "Just a sec...", no matter what I done, nothing changed. So I downloaded official Samsung firmware from sammobile and that's where I'm stuck now. Odin has been sitting at "NAND write start!!" for about ten minutes, nothing is happening.
Any advice at all? Pulling my hair out, the phone is only a week old.
Odin log;
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCY_G920FEVR1AOC1_G920FXXU1AOCW_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
Got the same problem 2 daya earlier. Just downloaded smart switch from samsung and restored my phone using emergency bla bla
AskinSavascisi said:
Got the same problem 2 daya earlier. Just downloaded smart switch from samsung and restored my phone using emergency bla bla
Click to expand...
Click to collapse
I forgot to mention, did try that briefly earlier but the download got stuck on 0%, left it maybe 5 mins. Any way I can use the downloaded firmware with smart switch?
Also, phone is now stuck at the downloading screen lol, how the hell do I turn the thing off?!
EDIT: NVM, got it turned off, will try smart switch again.
EDIT 2: Smart switch is actually downloading the firmware this time, panic over! Cheers for your help.
Ur welcome
Ive just found the reason why...
i forgot to turn off reactivation lock... when i disabled it, flashing was succesfull afterwards
Heyy XDA,
Writing this post as I'm completely stumped on this one
Basically when I first got my S6 I rooted it and all, and everything was fine, I then unrooted it in order to update the OS to 5.1.1 which again all went fine.
This was about 4 days ago. Since this there hasn't been any issues what so ever, until this morning when the phone died. After charging it back up to 100% I switched it on and it just chilled in a bootloop.
From here I tried soft resetting the phone, but it stayed in the loop. I then tried clearing the cache, which again had no effect. I've also tried wiping the phone entirely and putting it back to factory which again did nothing to help and safemode didn't boot as it restarted as soon as the display lit up (baring in mind that the OS is completely stock and the phone is unrooted.)
After no avail with the phone, I decided to try rooting the phone, hoping that it would 'kick' it back to life as that's what Apple devices do... :good: , however after attempting to root the phone it just stayed on the samsung screen with the error 'recovery is not seandroid enforcing'.
Then I thought ... F*** ... and downloaded the 5.1.1 firmware for my current model (G920F, UK model, EE network) which I then tried to flash through ODIN v3.10.7, however I got the error of:
'<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)'
I've checked that this is the correct version, as well as checked the MD5 to ensure its not corrupted. Also I've tried restarting my PC and tried all 5 USB ports.
Anyone have any other ideas other than start moaning to Samsung and trick them into giving me a new phone??
Thanks in advance,
Dark :highfive:
If you don't have tripped knox, you definitively should bring it to warranty.
But I think, by installing root you tripped it already.
Now you have two options. The first is to bring it to warranty and 'pray' that they doen't discover the altered KNOX state.
The second is, you can search for a complete firmware with PIT file and everything.
I see that you understand how to flash phones, but I will again alert you an others that have the same problem and read that post: Be sure to select the PIT file which corresponds to your phone's size (32, 64, 128GB)
However, bring it first to warranty. If they doesn't want to repair, take second option which is PIT flashing. If that doesn't take efect either, you must bring it to repair, and unfortunately, pay to repair this phone.
Tried a different cable?
Heyy XDA,
Writing this post as I'm completely stumped on this one
Basically when I first got my S6 I rooted it and all, and everything was fine, I then unrooted it in order to update the OS to 5.1.1 which again all went fine.
This was about 4 days ago. Since this there hasn't been any issues what so ever, until this morning when the phone died. After charging it back up to 100% I switched it on and it just chilled in a bootloop.
From here I tried soft resetting the phone, but it stayed in the loop. I then tried clearing the cache, which again had no effect. I've also tried wiping the phone entirely and putting it back to factory which again did nothing to help and safemode didn't boot as it restarted as soon as the display lit up (baring in mind that the OS is completely stock and the phone is unrooted.)
After no avail with the phone, I decided to try rooting the phone, hoping that it would 'kick' it back to life as that's what Apple devices do... :good: , however after attempting to root the phone it just stayed on the samsung screen with the error 'recovery is not seandroid enforcing'.
Then I thought ... F*** ... and downloaded the 5.1.1 firmware for my current model (G920F, UK model, EE network) which I then tried to flash through ODIN v3.10.7, however I got the error of:
'<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)'
I've checked that this is the correct version, as well as checked the MD5 to ensure its not corrupted. Also I've tried restarting my PC and tried all 5 USB ports.
Anyone have any other ideas other than start moaning to Samsung and trick them into giving me a new phone?? :silly:
Thanks in advance,
Dark
Hi,
You may try again by using this guide: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
A PIT file could help to re-partition your device: http://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
For any queries feel free to post in th Q&A forum of your device: http://forum.xda-developers.com/galaxy-s6/help
Hope it help & good luck!
Thank you for using XDA Assist.
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.
Hi all,
I have a Galaxy Note 10.1 (2012) which worked fine until one night I switched it off before bed. The next morning it doesn't boot up. It just shows the Samsung logo.
The machine won't go into recovery but starts to show the TWRP initial screen before going back to rebooting.
The machine will go into download mode and I have tried flashing stock a stock ROM and TWRP again but each time, ODIN reports a fail.
This is the log from ODIN when I try to flash the stock ROM:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/SIZE]
I have very often flashed ROMs in the past without a problem. I had TAB Sensation on the Note and had been using this for quite a while, then this just happens without any obvious reason.
Any help would be so gratefully received.
Thank you.
Jason
Download again.
Sent from my SM-N920C using XDA-Developers mobile app
Thanks for this but what should I download again?
stock ROM # for your model .
Same problem, but with unrooted model on stock 4.4.2. Happened once before, when under guarantee, and Samsung fixed it. Issue in detail:
Switch on - stuck at 10.1 logo
Will restart into download mode
Won't restart into recovery
Windows 10 computers won't recognise it when attached ('unknown USB device'), so ODIN doesn't see it.
So I'm stuck - any suggestions? Thanks in advance.
Attempted remedies so far:
uninstalled Kies
installed Samsung drivers (various versions)
reinstalled Kies
Skipsoft Toolkit
I've got the exact same problem with mine, it started several months ago. I was about to toss it but figured I'd give it another shot after a coworker told me of this forum. He suggested loading a new firmware/OS via the micro SD card, although since it won't even really boot I'm not sure how I'm going to do that.
http://forum.xda-developers.com/showthread.php?t=2080366