Develop Bugs

[Q] OMG..!!! Help Soft Bricked Epic..Odin FAIL.!!

OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.

jclould1911 said:
OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.
Click to expand...
Click to collapse
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.

OK I tried using Htc cable...Odin still FAILS.

you probably do need to buy a new cord as he says if odin isnt recognizing or is continuing to soft brick then new cord re install drivers for odin

Since it is a COM error it may be the drivers. Heimdall I believe loads it's own drivers so that may work for you. Go to Development and at the top in the stickies check out post 2 of How to fix a semi-bricked Epic.
Sent from my SPH-D700 using XDA App

ok thanks... and heres the odin prob.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.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> param.lfs
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and im going to try Heimdall now.

Try downloading a new Odin even if its the same one, and the tar file again
Sent from my SPH-D700 using xda premium

I had problems with different versions of odin and cable combinations. I thought mine was shot too. I finally found a working combination with Odin 1.7 and an aftermarket cable. I've had no problems with this combination on multiple flashes. Don't worry, as long as you can get into Download mode, you are not bricked.

Thanks tried using different combinations of Odin and cables and v1.7 is working but is failing at the end.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.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> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> boot.bin
<ID:0/004> recovery.bin
<ID:0/004> zImage
<ID:0/004> factoryfs.rfs
<ID:0/004> datafs.rfs
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help.

It appears you are getting further everytime which is usually an indication of a flaky cable or port. Did you also try it with the battery out?
Sent from my SPH-D700 using XDA App

I also found that it finally worked with the SD card out. I don't know if that's related. It worked first time and every time on 1.7 to flash anything I wanted, but I did have the SD card removed.

The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.

jclould1911 said:
The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.
Click to expand...
Click to collapse
No. EC05 kernels are not compatible with GB leaks.

Odin fail? Remove battery
kennyglass123 said:
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.
Click to expand...
Click to collapse
Thank you for this. I was softbricked and tried 3 different computers and four different cables and kept getting fails. It turned out that Odin just didn't want to run until I left the battery out. Back up and running!

[Q] GT-N7100 ROM and PIT failure feedback

I've just lost my Samsung note, after a hard reboot when the phone locked I got a dead system. Tried to boot into the reset menu but got the Odin menu by mistake, after which I hard reset the phone again, but this time it won't boot past the SGN2 Boot screen. I've gone through all the stuff of trying to re-install the phone with a ROM but it moan I had no PIT, so I found one. Still though it won't go past in setting of the partition... it might need a long time to set-up, but I have no idea as after a hour its still leaving the same message. I'm going to leave it overnight, but I would love some feed back to those that have done this before.
Last status in Odin3 -
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..

Well I left it running over night and still nothing... So far I have tried it with PIT_N7100_16GB_20121102 and it just never gets any further. So I can only assume that I'm making a mistake getting this on the system. Going to have another search later to see if their are any other methods of restoring the phone.

It's really bad sign and I suspect SDS
Can you give more details what exactly happened, how the issue started?
You are on which rom, when this happened?
Sent from my GT-N7100 using xda premium

dr.ketan said:
It's really bad sign and I suspect SDS
Can you give more details what exactly happened, how the issue started?
You are on which rom, when this happened?
Click to expand...
Click to collapse
The phone is completely stock, which it why this has rather confused me. All I know is that it was working all OK, hun and wouldn't respond, so I reset it with a battery pull. On starting it up the phone wouldn't move past the 'Samsung' boot screen. So I tried to boot into the recover to reset the system and end up in the Odin mode by mistake, but since then the phone now won't move past the SNGT-7100 Screen. Plugging it into Odin and trying to install the stock ROM again it told me I had no PIT, so I have tried to apply a number but they all fail.
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012>
<ID:0/012> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried the PIT_N7100_16GB_20121102.pit and sch-i605-16gb.pit
I'm rather stuck as to whether there is another method I can try or should just give up and take it back to Phones4u to get it replace via the warrenty as I've only had it since just before Xmas.

It seems SDS purely, don't do anything, particularly which raise flash counter and just submit to service centre.
Sorry man but it's seems nothing but SDS, you may not have updated to latest 4.1.2,which believed to have fixed for it
Goodluck
Sent from my GT-N7100 using xda premium

I'm just reading up on SDS... thats rather annoying. Well off to Phone4u then. Thanks for your help.

On which rom were you before all this happened?
Sent from my GT-N7100 using xda app-developers app

I have the same problem on stock rooted rom. Phone was working perfectly. Retarted and now nothing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_XEF_N7100OXADLJ2_422394_REV00_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Sds
Sent from my GT-N7100 using xda premium

[Q] My note II won't boot

Hi Every body:
That is really a bad day, just woke up this morning to find my device (was plugged for charging over night) to find it stuck at (GALAXY NOTE II N-7100)
tried several times to pull the battery and put it back hopefully to get it boot...but nothing happened.
I can access only the download mood and NO access to the custom recovery!!
I was running Android 4.1.1 WITH ROOT!
As advised in many other posts, tried to update to 4.1.2 using odin but the whole process failed with the following log:
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas and suggestions will be really appreciated.
Samsung maintenance in my place may take forever to get it fixed (almost 2 weeks!!)

Use odin 1.85 , check samsung usb drivers installed , exit kies, disable antivirus and firewall and try..

"<ID:0/004> Can't open the serial(COM) port." And try another usb port.
" Android 4.1.1" ?... Be careful about sudden death...

Primokorn said:
"<ID:0/004> Can't open the serial(COM) port." And try another usb port.
" Android 4.1.1" ?... Be careful about sudden death...
Click to expand...
Click to collapse
Thanks for the reply, really appreciate it..
I changed the USB port and got the following log from odin:
<OSM> N7100XXDMC3_N7100OJVDMC1_N7100XXDLK7_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>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?

drsayed_958 said:
Any ideas?
Click to expand...
Click to collapse
Did u try another Odin version? 1.85 or 3.04

Primokorn said:
Did u try another Odin version? 1.85 or 3.04
Click to expand...
Click to collapse
Tried both, got the same result.:crying:

You can flash with pit in Odin, it should work. The pit file can be found around here somewhere, can't find it for you right now.
Sent from my GT-N7100 using Tapatalk 2

http://forum.xda-developers.com/showpost.php?p=32273406
Not sure that it solves your issue.

same problem can anyone help ? no pit partition , or Can't open the serial(COM) port. , all drivers are installed i installed kies for driver the uninstalled without drivers

[Q] Stuck in boot loop, nothing I try works. Is my phone a lost cause?

Model: SGH-T999V (Wind Mobile)
Firmware Rom: Cyanogenmod 10.1.3 (IIRC, might have been 10.1.2)
So, last night I plugged my phone in to my computer to charge. I walked away to do some other things, and when I came back a few minutes later I found it rebooting, or at least trying to. It seemed to be stuck in a loop. It would vibrate and show the Samsung logo, and then show the model logo (in my case "Samsung Galaxy SIII" with the cyanogenmod logo on the bottom half of the screen). After this, it would vibrate twice with around a two second delay between each vibration. Then it would show the Samsung logo, the model logo, and vibrate twice again, repeating indefinitely. The only thing that stops the loop is pulling the battery.
At this point I'm thinking that there's a problem with the battery. I kept it plugged in to my computer for a little while while it tried to boot, hoping that it just needed to be charged. After this didn't work, I tried charging it with a portable battery pack I had and used a different cable. Still nothing. Then, I found a spare battery that I had and replaced the one I had been using. That didn't work either, the phone continued doing the same boot loop.
I don't believe that the problem is a faulty power button, since it doesn't start trying to boot until I either plug it in to charge or I press the power button myself. I can't seem to enter recovery mode. Whenever I try, it shows the initial Samsung logo screen with "Recovery Booting...." in small blue text in the top left corner of the screen, but then proceeds to reboot again.
I am, however, able to enter download mode. I decided to try and flash my stock firmware, hoping that would fix the problem. I put my phone in download mode, opened odin, and it seemed to recognize my phone. I loaded the .md5 file and hit start, but almost immediately it showed 'FAIL'. This is what it said in the message box:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
At this point I have no idea what else I can do. I hope it's not a hardware failure, but it's starting to look like that's the case. Is there anything else I can try, or is my phone just dead? And, if it is dead, does anyone know the exact cause?

CM is your rom, not your firmware. The firmware is what we generally refer to as everything but system, kernel and recovery. Do you know what your current firmware build is?
Are you certain you downloaded the Wind version of the firmware?
I could be wrong but from the Odin output it looks like you have pre 4.3 firmware. If so, try using any other build and see if it flashes.
Judging from the symptoms you described, it is possible you could be looking at a hardware failure. Possibly the SoC, but more likely the memory. If you cant get Odin to flash anything the possibility of this becomes greater.
Try other firmware with Odin. Try with and without re-partition checked. (This will wipe all your data)
Try flashing TWRP via Odin. If that makes recovery work you may then be able to factory reset and flash a rom again.
Try different usb cables and ports. Try another computer as well if nothing else is helping.
Beyond all of that, im not sure theres gonna be much you can do.

Argh, I always seem to get ROM and firmware mixed up. Anyway, If I'm understanding this correctly I'm pretty sure that my firmware was 4.2.2. I definitely downloaded the wind version of my stock firmware. I also found on my computer 4.0 firmware that I'd downloaded a couple years ago. I tried flashing that with odin and got the same result. Then I tried it with re-partition checked and it failed again with this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I guess that's that then. Luckily I had backed up all my photos last week on a whim.

Out of curiosity, did you use a PIT file when repartitioning, or did it use the one in the device? Whichever it is, try the other as well. I believe the pit files are in the General section.

I used the PIT file on my device when I first tried to repartition. I downloaded the PIT file that you were talking about and tried again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Did you try flashing recovery only? And does odin see the devices COM port in the top left?
Did you try different ports and cables?

Odin does see the COM port. I just tried flashing TWRP and odin said that it passed, but I'm still not able to boot into recovery mode. I have tried using another port but I don't have another cable on me.

Well if it said it passed the recovery flash, the cable and port are probably ok.
Im not really sure there is much else you can do tbh. Its sounding more like a hardware problem at this point.
Sorry I dont have anything better to tell you, but if I think of anything else you could try ill let you know.

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