I have a Galaxy note 10.1 running kitkat 4.4.2 (GT-N8000)
Yesterday i was browsing the internet when suddenly the device decided to shut down and went on a restart boot loop where it would show the "Samsung galaxy note 10.1" screen for a while and then reboot and re-show the same screen
i have tried entering recovery mode but the tablet keeps restarting without end the only thing i can access is download mode
So recently i tried flashing using Odin but when ever i try to flash any file it shows this error
Code:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried flashing a stock recovery so i can try and wipe the current data
I have tried to download multiple stock roms from jelly bean to kitkat which all ended up failing
I have tried flashing the tablet with a "Repair rom" which contains the BL AP CSC and Modem files
i think that if i can still access the download mode that there is some hope to recover?
Any solutions?
Thanks in advance.
If i posted this in the wrong section forgive me i have just started out
Related
I'm new here and I couldnt find a thread which had the same problem as me solved so here we go!
I tried manually installing the official jellybean firmware on my N7000 following the steps exactly (usb debugging on, download mode etc) Once I started to run Odin everything was fine until a massive FAIL occured. This is what Odin said
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000ZSLM5_N7000OZSLM5_N7000XXLSO_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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.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)"
Anyway now my phone won't start, it will turn on and but it gets stuck on the Samsung Logo, I booted it into recovery mode, wiped cache, user data and rebooted but it was still stuck on the Samsung logo. How do I fix my phone from here??
Have you installed the drivers on your pc?
64 bit - http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32 bit - http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Install the driver and then try again
Sent from my GT-N7000 using Tapatalk 2
check if kies is running.. close it from task manager... run odin as admin.. aslo before flashing again.. you need to power off and reboot into download mode
Thank you!!
Thanks, that's what I hadn't done, install the drivers. All working good now and have to say its great to finally have jellybean on it!
I've come across various other threads concerning this topic with other devices, but none are exactly like my issue.
I rooted originally with Odin and CF autoroot with no issues. Now me being the noob that I am, I un-rooted with Kies to check for any updates. The process went fine, however my device status still says "custom" and I'm unable to re-root using the same method that I did before. I get a "fail" in Odin after the cache.img process and have to remove the battery to reboot device.
Has anyone had this issue or am I the only idiot to unroot this beast of a phone?
Best bet. Odin back to stock and then reroot and forget about updates.
BAD ASS NOTE 4 + BAD ASS GEAR S
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
I'd try a different version of Odin.
Razorfengraul said:
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
Click to expand...
Click to collapse
As said diff version or bad cf autoroot download. It can be many things. Try a fresh download of everything. Also when u Odin back to stock it went fine so it is something after. Bad download
BAD ASS NOTE 4 + BAD ASS GEAR S
Recently I installed Clockwork Mod on my sisters Samasung Galaxy I8190N and attempted to flash lollipop on it. Much to my disappointment somewhere in the process I failed. Now when the phone boots I see the lollipop loading animation, but it goes no further during the boot. I can no longer access the Clockwork Mod recovery with up+power+home button. But can still access the download mode. So I tried to reinstall the 4.1.2 using odin, however with odin I get the following error when trying to flash using the PDA/AP:
Code:
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone (in download mode) it says Custom Modem Binary installed.
Any help in getting my sisters phone back to how it was before she gave it to me (default 4.1.2) would be greatly appreciated!
Edit: I realise after posting that this would of been better in the troubleshooting forum, apologies for that.
Factory reset or flash original firmware from sammobile
I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Hi.
I've been given a bricked(?) SIII galaxy mini, which boots into Android system recovery <3e> mode.
I'm trying to revive it, but I'm not having much luck.
I have tried the following:
-wipe data/factory reset
-wipe cache partition
-enable download mode and flash using various odin versions.
-changed usb cables
-use different pc's windows 10/7/vista
-reinstall usb drivers
-start odin elavated
Odin does recognize the phone (<ID:0/004> Added!!)
But flashing fails
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200NXXUAOL1_I8200NVDPAOD1_I8200NXXUAPB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> obm.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Any suggestions ?
*bump*
Anyone ? Could anything be done using ADB ? The phone is not rooted.
Do your solve your problem?I am also having same problem. http://forum.xda-developers.com/showpost.php?p=68542525&postcount=2270