Flashing stock rom with odin, "stuck" at system - T-Mobile, Samsung Galaxy SIII

The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?

Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.

Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.

You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?

Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.

Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??

Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard

Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.

Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1

griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.

Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that

In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.

Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.

griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.

Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference

Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe

Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png

Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.

Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?

Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.

Related

[q] please help!!!bricked!!!

please help me someone i had the stock el29 system and tried to root it with this
http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root
but it froze at factoryfs.im so im waited 25 mins then tried doing the odin manually by putting the file in myself then it went all the way to rqt_close then nothing it stuck.
i need to get rooted cause i want this rom but i will take anything now rooted non rooted i just want my phone fixed.
http://forum.xda-developers.com/showthread.php?t=1512419&highlight=fd24
it (auto root) made my phone say "firmware upgrade encountered and issue. please select recovery mode in kies & try again.
my first device. i couldnt connect to odin and computer wouldnt recognize device so i took it to sprint and they gave me a replacement.
i figured it was a bad download or something so i downloaded it again today and it messed this phone up to only this phone connects to pc and is recognized but when i try to upload the rom on the regular odin and not the one click it stuck at rqt_close and im confused as to what to do now. i dont even have to be rooted anymore i just want a rom on this phone i was out of a phone for 5 days for that Rom and its messed me over again.
1st time it stuck at factoryfs.img then i got replacement and it stuck at modem and then i took out battery after it was froze for like 25 mins. please help me!!!
Have you tried a different USB cable and/or computer?
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
TamiaSky said:
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
Click to expand...
Click to collapse
Can you get into recovery mode?
no i cant get into recovery just that dreadful notice but i can get into download mode, so thats a good thing im guessing.
i get all the way to the end to rqt_close then it says my device has been removed like odin is kicking me out or something. i dont unplug my phone or anything but it gets all the way to the end then says removed then failed
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
sfhub said:
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
Click to expand...
Click to collapse
ive tried the auto packages and doing it manually and when i did it manually i made sure tat it was the pda slot and i unchecked the re-partition when it popped up as well then after looking around on the internet still i used one of the 7-zip packages and used the pit file with it and checked re-partition and still nothing. odin gets all the way to the end right after modem and then sticks on rqt_close then says removed now it just did this
<ID:0/006> 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/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> recovery.bin
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
i really hope you guys can help me. im so serious if i get this fixed ill never try to root this phone again. i dont wanna have to get another replacement phone.
MeWarning said:
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
Click to expand...
Click to collapse
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
TamiaSky said:
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Click to expand...
Click to collapse
Well first if you look in the reference section B in the one you've been trying to Odin(http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root) there's separate tar files for the modem, kernel, and rom. Why don't you try doing each one one at a time to see if anything will succeed.
And if that doesn't work try to Odin one of the leaked stock ICS builds sfhub has also.
This is what happens when I do it manually without the auto package.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
then it freezes
sfhub said:
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
Click to expand...
Click to collapse
its the full, and ive never been on ics
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
now i will try the no data and see what happens.
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
TamiaSky said:
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
Click to expand...
Click to collapse
No problem, just let us know how it goes.
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery. This will increment your ODIN flash count, but it is better than a phone not working.
sfhub said:
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery.
Click to expand...
Click to collapse
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
TamiaSky said:
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
Click to expand...
Click to collapse
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
sfhub said:
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
Click to expand...
Click to collapse
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
MeWarning said:
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
Click to expand...
Click to collapse
When you package a modem.bin inside of a .tar.md5 it can flash in both the PDA and Phone slot. It is simpler for the instructions to ask people to always use the PDA slot.
If you flash a modem.bin file itself, then it must go in the Phone slot. If you flash the wrong file in the Phone slot, your phone won't boot. That is why I package things so people always use the PDA slot.

[Q] "Firmware Upgrade Encountered and Issue"

Hi. I tried following a simple guide to rooting my S3, but it failed horribly. I followed the steps (download Odin+this file, load the file into Odin, hit Start and bam your phone's rooted) but it failed. Here's the log from Odin.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.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
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Now my phone won't run properly, it says to run Kies in recovery mode or something but I don't understand. In retrospect I should've downloaded Kies onto my computer first, as well as SU onto my phone, and I probably should've found out my model number, but here I am.
I'm not trying to install a custom OS, I just want root access so I can use root-only apps. Can anyone tell me how to save my phone?
if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward
You may just have bricked your phone, because that package was for the international variant.
relieved
jdelano said:
if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward
Click to expand...
Click to collapse
Wow, thanks a lot man! I will be sure to!
seb0910 said:
Wow, thanks a lot man! I will be sure to!
Click to expand...
Click to collapse
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171
jdelano said:
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
If it's a true brick then that won't work, because in a real brick the phone doesn't even turn on. When that thread refers to a brick, it's really referring to a soft brick which is easy to recover from.
yes, I am assuming soft because the OP said "Now my phone won't run properly", not it won't turn on. I know its bad to assume but I took the leap any way

[Q] Stock note 2 bootloop

Hi, so my cousin gave me her note 2 and told me to fix it! its basically on a bootloop so first thing i thought of was to flash stock firmware,
So i did that and the Samsung logo just flashes for eternity :| she hasn't done anything like rooting etc.
So i downloaded the UK stock firmware(her note 2 is the THR) but it's still in bootloop!
I can't get into recovery to wipe data! when i hold the key combos, it just keeps rebooting (samsung note II - n7100 black and white one)
(I actually needed help flashing the rom but not its fixed i need help with this and i didn't want to make another thread)
should i try to use put and re-partition?!
kamranhaghighi said:
Hi, so my cousin gave me her note 2 and told me to fix it! its basically on a boot loop so first thing i thought of was to flash stock firmware
so i downloaded the UK firmware (although i have no idea what country it is, but it doesn't make difference right?!)
and it gave me this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should i do ?
i have windows 8 and odin 3.09
Edit: I got the firmware from here :
http://www.cnet.com/how-to/how-to-restore-a-galaxy-note-2-from-rooted-to-factory-settings/
My country's firmware is not available anywhere
Click to expand...
Click to collapse
Hello ,
many months ago I had a problem to install a Samsung rom. For me the solution was :
Download firmware from sammobile
Use Odin PC 3.07 (It doesn't work with 3.09 version I don't know why )
I hope that can help you.
gb61 said:
Hello ,
many months ago I had a problem to install a Samsung rom. For me the solution was :
Download firmware from sammobile
Use Odin PC 3.07 (It doesn't work with 3.09 version I don't know why )
I hope that can help you.
Click to expand...
Click to collapse
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it might be because i'm using UK firmware.
Iran's firmware isn't available!
(i used 3.04 but its old anyway !)
I'm driven crazy i will just wait for an answer :|
kamranhaghighi said:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it might be because i'm using UK firmware.
Iran's firmware isn't available!
(i used 3.04 but its old anyway !)
I'm driven crazy i will just wait for an answer :|
Click to expand...
Click to collapse
It should be good to try with Odin more recent if you can.
Iran firmware on the image .
How did you find it i saw that website too but i couldn't find the firmware!
I will try odin 3.07 and post results
gb61 said:
It should be good to try with Odin more recent if you can.
Iran firmware on the image .
Click to expand...
Click to collapse
YEAH! it worked ! thanks so much but i'm afraid it will not work, im still on samsung lighting up and down but i only waited like 1min, it had this problem expect it would not boot at all!
EDIT: ok flashing stock didn't help. i still got bootloop, any idea how to fix this?!
i also can't get into recovery, it only gives me a red led when i hold volUp+Home+power!
i did a few things now i can't even flash the old one with 3.0.7, gives the same error it did on 3.09 , i give uP! somebody help me :|
gb61 said:
It should be good to try with Odin more recent if you can.
Iran firmware on the image .
Click to expand...
Click to collapse
flashing the one i got from sammobile gives me this:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100OJVDMC1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
edit: sounds like it is because its an old firmware!
now i can't even flash the UK with 3.07!
should i make a new thread for my bootloop? (i still got bootloop after going stock)
kamranhaghighi said:
should i make a new thread for my bootloop? (i still got bootloop after going stock)
Click to expand...
Click to collapse
Hello,
have you try to install a custom rom ?
gb61 said:
Hello,
have you try to install a custom rom ?
Click to expand...
Click to collapse
No!
kamranhaghighi said:
No!
Click to expand...
Click to collapse
Have you see in the link in the edit of my last post ?
At this moment you can't acces to recovery ?
gb61 said:
Have you see in the link in the edit of my last post ?
At this moment you can't acces to recovery ?
Click to expand...
Click to collapse
I just saw it now, and no i can't get into recovery, i will read the link you gave me tomorrow, im super tired today! and also have an exam
my guess is the eMMC chip has failed, or the partition is corrupted. Yoiu might try and flash the PIT but i suspect that wont work. This type of failure is unfortunately quite common from my experience. My Note 2 had the same problem and still cant find a fix.
grwalker said:
my guess is the eMMC chip has failed, or the partition is corrupted. Yoiu might try and flash the PIT but i suspect that wont work. This type of failure is unfortunately quite common from my experience. My Note 2 had the same problem and still cant find a fix.
Click to expand...
Click to collapse
sorry for your note 2!
hope its no longer like that in note 3 and 4 :! (i got the note 4!)
kamranhaghighi said:
sorry for your note 2!
hope its no longer like that in note 3 and 4 :! (i got the note 4!)
Click to expand...
Click to collapse
Hello,
try that :
Install a recovery with Odin PC
download original CWM note 2 :https://mega.co.nz/#!rY1DmZ7J!JzeUWnC-X1_0jO42aoydRAYakgPQMo9RgHqAHyRGWyI
download TWRP : https://mega.co.nz/#!jNdQwaib!BdXte5RXjPVg7YLVjHS6WjbMZzfS-DJk6IPW6jPvyWs
Download a custom rom for Note 2 :
copy and paste CWM ,TWRP and custom rom on your SdCard
Install CWM with Odin PC , if doesn't work try with TWRP.
If it works , install the rom with recovery
I hope that will help you.
gb61 said:
Hello,
try that :
Install a recovery with Odin PC
download original CWM note 2 :https://mega.co.nz/#!rY1DmZ7J!JzeUWnC-X1_0jO42aoydRAYakgPQMo9RgHqAHyRGWyI
download TWRP : https://mega.co.nz/#!jNdQwaib!BdXte5RXjPVg7YLVjHS6WjbMZzfS-DJk6IPW6jPvyWs
Download a custom rom for Note 2 :
copy and paste CWM ,TWRP and custom rom on your SdCard
Install CWM with Odin PC , if doesn't work try with TWRP.
If it works , install the rom with recovery
I hope that will help you.
Click to expand...
Click to collapse
i'm also going to check re-partition and use pit file. is that a good idea?
i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!
kamranhaghighi said:
i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!
Click to expand...
Click to collapse
Have you follow this steps ?
How to Install ClockworkMod Recovery 6.0.4.4 on Galaxy Note 2 N7100
Download Odin v3.09.
Extract Odin zip file and you will get Odin3 v3.09.exe along with few other files.
Power off your Android device. Wait 5-6 seconds for vibration to confirm complete switch off.
Now, put the Galaxy Note 2 N7100 in Download Mode by pressing and holding down the Volume Down, Home and the Power button together. A warning screen will come up; press Volume Up button to enter Download Mode.
Now run Odin3 v3.09.exe (see Step 3) as an Administrator because Admin privileges is required to complete the process smoothly (only applicable Windows Vista and higher).
Now connect your device to your PC using USB cable. An “Added!!” massage will appear in Odin’s message box. If you don’t get the same then you should try another USB port (try USB port located in back in your desktop PC). If that too don’t work then you should reinstall the driver. If you successfully see the “Added!!” message in Odin then you are ready to go in next step. You should also see COM port with a number in Yellow if you successfully added your device.
Click the AP Button, and select that .tar.md5 file that you downloaded earlier. If you are using old Odin then add the file to PDA button.
In Odin window, make sure only Auto Reboot and F. Reset Time checkboxes are selected.
Double check everything that we mentioned in Step 7 & Step 8 above. Now, once satisfied hit the START button to begin the flashing process.
Once flashing completed, your Galaxy Note 2 N7100 will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect your device from computer.
kamranhaghighi said:
i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!
Click to expand...
Click to collapse
Ok,
we try to install a full wipe rom :
Download this zip : https://mega.co.nz/#!KN1QiZyJ!tKkqdUSYOtuLI4_4TRe8ZpXsHb3G608KsJd5XNf6EhU
Extract the files = 4 .tar and 1 .pit
Put this file in odin like in the picture = FLASH WITH PIT (RE-PARTITION)
gb61 said:
Ok,
we try to install a full wipe rom :
Download this zip : https://mega.co.nz/#!KN1QiZyJ!tKkqdUSYOtuLI4_4TRe8ZpXsHb3G608KsJd5XNf6EhU
Extract the files = 4 .tar and 1 .pit
Put this file in odin like in the picture = FLASH WITH PIT (RE-PARTITION)
Click to expand...
Click to collapse
ok thanks! btw in the process of doing this i gave myself a nice electric shock 0_0 it came from 2 connectors from back of the device ! i got pass anyway
edit: it will take an hour~ i will post results when its done!

HELP! Galaxy S6 (SM-G920P) (SOLVED)

I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om
x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)
Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_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.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...
Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.
x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_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.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?
1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting
1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<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> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode
Updated main
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
I am having a very similar issue, can't seem to figure out how to fix it.
x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...
x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<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> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?

Samsung tab 3 lite SM-T110 bootlooping and nothing helps so far

My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.
ccsrichman said:
My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.
Click to expand...
Click to collapse
what version of Odin are you using?
Give THIS version a try.
If it fails, post a screenshot of Odin.
I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ccsrichman said:
I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.
Anybody else has any ideas ?
gr8nole said:
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.
Click to expand...
Click to collapse
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there
ccsrichman said:
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there
Click to expand...
Click to collapse
And the text there is:
ODIN MODE
PRODUCT NAME: SM-T110
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
nothing else
Also a newbie with the Tab TM-110
Hi there
Since we are not many here with our device i thought i should send you a message.
Unfortunately i do not have a solution for your problem but maybe it helps if you take a look at what i experienced so far.
I hope you can find my Thread by my profile.
Have you tried to use a different PC yet for flashing with Odin? Would be interesting to know if it helped.
So. Don`t give up. There will be a solution. :good:
Naturestone
I'm having the same issue, anyone can help?
same error GT-I8200 2ND partition error

Categories

Resources