Develop Bugs

[Q] Stuck on Samsung Boot Logo, ODIN says no PIT partition

Hi everybody,
I didn't download or flash anything recently, and was on 4.1.1 stock firmware. My phone was working perfectly last night. I woke up this morning, and it was stuck on the Samsung boot logo and very hot from the charger.
I was panicking, and quickly loaded up ODIN and tried to download the same firmware I had before. I can't get a yellow bar in ODIN no what I try. I never had this issue before. I have been reading and trying different things for the past 4 hours. I am using the original USB cable, tried all the different USB ports, a different PC, re-installing the drivers, re-installing Kies, re-installing ODIN, and nothing seems to give me the yellow bar in ODIN.
I cannot boot into recovery mode, only download mode. Please help, I'm very worried my phone could be bricked somehow
Seems there is no PIT partition??
If it matters, here is what I get when I try to load firmware without the Yellow bar in ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I have just downloaded the toolkit and trying it. It keeps saying "waiting for usb debugging mode to be enabled"

cheetahpro said:
Hi everybody,
I didn't download or flash anything recently, and was on 4.1.1 stock firmware. My phone was working perfectly last night. I woke up this morning, and it was stuck on the Samsung boot logo and very hot from the charger.
I was panicking, and quickly loaded up ODIN and tried to download the same firmware I had before. I can't get a yellow bar in ODIN no what I try. I never had this issue before. I have been reading and trying different things for the past 4 hours. I am using the original USB cable, tried all the different USB ports, a different PC, re-installing the drivers, re-installing Kies, re-installing ODIN, and nothing seems to give me the yellow bar in ODIN.
I cannot boot into recovery mode, only download mode. Please help, I'm very worried my phone could be bricked somehow
Seems there is no PIT partition??
If it matters, here is what I get when I try to load firmware without the Yellow bar in ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I have just downloaded the toolkit and trying it. It keeps saying "waiting for usb debugging mode to be enabled"
Click to expand...
Click to collapse
I have the exact same problem right now with my phone.
have you found any solution?

Anti_virus_abdo said:
I have the exact same problem right now with my phone.
have you found any solution?
Click to expand...
Click to collapse
Download and flash pit file, then flash stock, or if you have custom recovery then download recovery flashable stock rom and flash using sideload.

Mufrad said:
Download and flash pit file, then flash stock, or if you have custom recovery then download recovery flashable stock rom and flash using sideload.
Click to expand...
Click to collapse
i'm struggling same problem during laast 5 days and tried almost everything for solve this problem.
i tried to flash stock recovery but phone didnt react and odin failed with "there is no pit partition". i dont want to use pit for reparttion and erase all my personel stuff on my phone but give up lastly and used pit file with stock recovery.but beside odin worked at start but stopped the screen that "setting parttion"
please helppp???.i dont want to send my phone to guarantee service because of they eraase all my personel stuff c
@dr.ketan

cagriekim said:
i'm struggling same problem during laast 5 days and tried almost everything for solve this problem.
i tried to flash stock recovery but phone didnt react and odin failed with "there is no pit partition". i dont want to use pit for reparttion and erase all my personel stuff on my phone but give up lastly and used pit file with stock recovery.but beside odin worked at start but stopped the screen that "setting parttion"
please helppp???.i dont want to send my phone to guarantee service because of they eraase all my personel stuff crying:
Click to expand...
Click to collapse
unfortunately you have to, it's not an option.

Anti_virus_abdo said:
unfortunately you have to, it's not an option.
Click to expand...
Click to collapse
could u solve the problem????

cagriekim said:
could u solve the problem????
Click to expand...
Click to collapse
No, it's not a software problem, it's SDS :/
so i am going to replace the motherboard, and i am out of warranty because i bought it from more than a year, so i am going to pay 220$ for the replacement.
I'll NEVER EVER buy a crappy Samsung device again.

[Q] N7100 ODIN error, stuck on logo or Firmware upgrade encountered an issue...

Hi everyone,
I read various similar problems for N2, but also for S2 and S3, and did not manage to solve my problem
I got my N2 with 4.1.1 and I wanted to upgrade it immediately to 4.1.2 because of the SDS etc.
This is what happened:
0. Antivirus disabled, usb drivers installed, run as admin, different USB ports and 2 Samsung cables
1. Downloaded and unpacked N7100XXDMB2_N7100OXXDMB2_BTU.zip
2. Entered download mode (vol down+power...)
3. Opened odin 307 and connected the phone
4. PDA button, file select
5. Start and after few seconds ERROR:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
6. After restarting the phone, I got and error: Firmware upgrade encountered an issue... No possibility to enter the recovery!
7. Tried to work this out via KIES. Installed it, but it doesn't recognize the device at all
8. Downloaded rom again, different versions, same result
9. Tried to flash bootloader only but got the same result
10 Tried to flash everything again but with PIT file this time, and got the same result - ERROR
THAN I FOUND TWO STRANGE THINGS:
10. I flashed ONLY PIT file (re-partition) and had success, but phone than just displays starting screen - GALAXY N7100... and does nothing else! Also no possibility to enter the recovery!
11. I flashed CWM recovery with success, but can not enter it and phone displays starting screen - GALAXY N7100... and does nothing else!
12. When I try to flash rom again, I get Firmware upgrade encountered an issue screen again!
Is there something else I could try to do to fix my bricked phone and if not, what do you thing is the solution (new motherboard)?
Thanks for everything!

After whole day of trying and reading, I got several different USB cables, started testing and... VOILA! One of them simply did the job! I can't believe that two original Samsung cables were faulty, so that the third one was OK If anyone encounters the similar issue, my recommendation is to get several cables and at least give it a try!

soft bricked ATT SIII??? was using CM 10.

I had was running CyanogenMod 10 or 11 on my unlocked Samsung Galaxy S III - I747. I think before CyanogenMod, I had Android 4.3 OTA. I wanted to go back to stock At &T and downloaded original firmware from sammobile. tried to use different versions of Odin but no success. Everytime I used to get this kind of error.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and KIES was of no use as it did not recognize my I747 on cyanogenMod. Today someone told me that I could get it restored on KIES from tools menu.
-Turned phone off, pulled battery out.
-On Kies, tools> Restore and initialization (?) then input model and serial no. Gave me firmware....... proceeded. After sometime booted phone on download mode but kies failed and gave me message saying emergency recovery code but there was no code. Code space was blank. Now my phone screen show
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again,"
every time I press power button it goes to same screen. I can get to download mode but can do nothing as ODIN is not working or giving me same error. Booting onto recovery mode gives me same "Firmware upgrade encountered an issue" error.
What can I do to get my phone back on working condition. Stupid me, I am expecting to get some job interview calls tomorrow and do not have extra phone o put sim on.
Please help me, My external SD card on phone has recovery image (?) of CyanogenMod if I can get to custom recovery but can not. I would take it in Cyanogenmod if not to stock as long as it gets on working condition.
Thank you

Your phone has the the stock 4.3 bootloader and using Odin to flash a stock ROM could have bricked your phone. Do not use Odin unless the 4.3 ROM has been compiled for use with Odin.
I recommend using Odin to flash the latest d2lte tar recovery. Then copy a custom KK ROM to your SD card and flash that instead of trying to flash a stock ROM.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte

Out of desperation, i flashed cf autoroot md5 by chainfire using odin that brought my phone back to life ie cyanogenmod 10.
Now when i try to update cyanogenmode i get signature verification fail message. I dont know what is the issue here.
Thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Are you trying to upgrade to CM11? All Kit Kat ROMs require a up-to-date recovery.

[Q] Soft Bricked Note 2 - Odin Failsn - Kies won't detect my phone - Help?!

I soft bricked my phone somehow, no clue. My phone was fine, battery died with no downloads, or anything running, went to turn it back on after plugging it in to find it bricked at the Samsung start screen.
I've tried restoring it with Kies, which won't recognize my phone is plugged in(??).
I've tried restoring it in Odin with Kies uninstalled, it keeps failing though.
Here's a copy of Odin's log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVBMD1_T889TMBBMD1_935627_REV04_user_low_ship.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Note 2 has never been rooted, and I'm completely at a loss as to what has happened. I've tried different USB cords and slots around my laptop, but don't have another computer I can try it on currently.
Also, After trying Kies and Odin I noticed in the top left corner of my Note's screen, KNOX WARRANTY VOID changed from 0 to 1, not sure what that means either!
Any suggestions? I'm lost without my phone!
Edit:
After ODIN fails, my phone says unsupported version also in the top left corner. I've tried 3 different stock ROMs.
Edit 2:
And now I can't get into the boot menu, just the download menu.
Kies also won't recognize that my phone is connected now.

Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.

I've tried at least 4 different firmware versions, and am having no luck with any of them. Should I be looking for one that includes the OTA update from back in the winter?
Androidwizzard said:
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
Click to expand...
Click to collapse

I have the same problem. any other sugestions?

Not yet, I've yet to find a firmware that works. :/
Jotapoggi said:
I have the same problem. any other sugestions?
Click to expand...
Click to collapse

FIX
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
Kittylee, take a look at this video " youtube . com / watch?v=GbAJH_mL6N4" I've downloaded the rar version of the clockwork recovery for my GT-N7100 from this site "galaxynote2root . com / cwm-recovery /" you have to choose the "RAR" version since it's thhe one odin uses.
OBS.: Remove the spaces from the links
It worked for me. try it.
:laugh:

Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse

kittylee said:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
Click to expand...
Click to collapse
Which version of andriod is it?

Galaxy Note 2 T889 stuck with the logo

I have a Galaxy Note 2 SGH-T889. I have spent the past week reading and trying suggestions on this forum. I downloaded kies but it gets stuck connecting to the phone. I have tried several versions of odin. It gets to sboot.bin and write fails. I have tried the original firmware which took 2 hours to download. I refuse to pay for the upgrade in download speed for something I only need one time. I have tried the pit and firmware combination. The only thing that seem to register anything on the phone was when I tried the modem.bin.....it had a blue progress line but then it failed. I am starting to think it is a hardware problem.
How did it start? The phone was sitting on the desk when it came on and restarted. Then it stop when it got to the Galaxy Note II logo. I can get it into Download Custom OS mode but it will not go into recovery mode. Prior to that I had to data wipe and factory reset because it was having the logs process stopped and other processes popups. I had to wipe and reset about 3 times prior to the failure.
I was using the plain old firmware. I think the phone auto updated to the 4.3. I did not install any custom os. I just use the phone as a phone, the calendar and the camera pretty boring stuff. Did not know anything about odin, kies, soft brick, hard brick, jtag, emmc or sds prior to the failure. Not sure exactly what the difference is between t889, n7100, n7105 or n7108. I have downloaded the android toolkit and tried several of those options but it says to enable debugging but I have no access to the settings on the phone to enable debugging.
The way the phone crashed makes me think it had a hardware failure. If there is anything else I can try, I am willing to try anything.
Eva

Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk

Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?

andytiedye said:
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I am wondering if the phone was doing an auto update and got stuck in the process. I had my phone set to auto update. Maybe that is a mistake...I guess I should have made it ask before it updated at least then I would know what cause the problem.
Eva

Note 2 sgh-t889 boot.bin error
audit13 said:
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva

zevacat said:
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
Click to expand...
Click to collapse
Ok it finished downloading. I ran it with odin 3.12. This is the results.
<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)

You are flashing a tar.md5 file in the PDA slot of Odin 3.07?

audit13 said:
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
Click to expand...
Click to collapse
That try was with the odin 3.12 using the ap slot. I did try 3.07 pda and the 1.87. Yes it is a a tar.md5 file.
Had an interesting occurrence. I restarted the laptop while the phone was connected to the laptop and the laptop went into an infinite start loop. At first I thought, oh great now the laptop is broken....:crying: But then I unplug the phone and the usb cable. The laptop started normal. I plugged the cable in and it still restarted without problem so whatever black hole the phone is in....it will pull in all connected device into the abyss.

Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.

audit13 said:
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
Click to expand...
Click to collapse
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva

I recommend flashing the most recently released stock rom, not earlier releases.

zevacat said:
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
Click to expand...
Click to collapse
I can't seem to find an earlier versions all the 4.1. All the links come back as file not found. They did have a gt n7100 unbranded 4.4.2 kit kat N7100_ITV_N7100XXUFOE1_N7100ITVFOF1.zip so I am waiting for it to download. It says it will take about 2 hours. Or is there some other version that would be better? and where can I find it. Rapid Gator really stinks as far as downloads.
Eva

Flash the latest 4.4. Try updato.com.

audit13 said:
Flash the latest 4.4. Try updato.com.
Click to expand...
Click to collapse
They don't have a 4.4 for the sgh-t889 so which one would work best out of the other options 7100, 7105 or 7108?
Eva

I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.

audit13 said:
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
Click to expand...
Click to collapse
4.3 gets stuck after the sboot.bin. audit13 said "the bootloader in the ROM is not compatible with the phone "....so if the bootloader in the sgh-t889 is not compatible then I need a different bootloader don't I? Not sure where to find a different bootloader.
Eva

The only thing I can suggest is taking it to a cell shop that can flash it via jtag.