Develop Bugs

[Q] Help I just BRICKED my Samsung EPIC

I have been using my epic for a little more than a year now and I have used odin and update.zip to update my phone in the past. Also I have rooted my phone multiple times but this time I think I really screwed up. I have the stock EI22 gingerbread installed on my phone and I was trying to root it using ODIN with the ACS recovery. However now I cannot boot into my phone and when I try, I get this symbol of a phone and a computer not connected. I tried using ODIN to go back to EC05 but I get this wierd message from ODIN when I try.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EC05_DXC.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> cache.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried using the victory.pit file and different tar files but that doesn't work either. I tried using the update.zip EI22 file using CLOCKWORK RECOVERY but it keeps saying "Installation Aborted".
Can someone help please???

Try a better cable, try it with the battery and sd card out using the computer as a power source, also try removing the md5 extension from the file. And it is not bricked as long as it has life. Brick is brick. Yours is sponged.

OMGGGGGG THANK YOUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!. I took out the battery and SD card and tried ODIN and it worked. You are awesome my virtual friend.

charlesx123 said:
OMGGGGGG THANK YOUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!. I took out the battery and SD card and tried ODIN and it worked. You are awesome my virtual friend.
Click to expand...
Click to collapse
Glad to help. Odin can be finicky. One phone I have only succeeds if I cradle it in my hand and whisper it will be alright while Odining.

kennyglass123 said:
Glad to help. Odin can be finicky. One phone I have only succeeds if I cradle it in my hand and whisper it will be alright while Odining.
Click to expand...
Click to collapse
I thought I was the only one haha

[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] Soft Brick: NAND write failed, Missing system/build.prop

TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<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> 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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...

Uggo said:
TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<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> 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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Click to expand...
Click to collapse
The exact error I get when I try to flash GAPPS is:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error executing updater binary in zip '/external_sd/pa_gapps-stock-4.4.4-20140916-signed.zip
Error flashing zip '/external_sd/pa_gapps-stock
Updating partition details...
It's also worth noting that flashing the ROM (I'm going with the latest CM nightly) takes way too short of a time to complete

Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks, but it didn't help. I'm still getting the same problems.

Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks for all the help. I'm not sure what the issue was, but I ended up solving it by using the latest CWM recovery to install a flashable version of stock. I'm not a huge fan of stock, but I'm up for an upgrade in January so I'm going to just have to cool it on the ROM front to ensure I have a working phone.

Old Tmo Note 2

When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.

Which file is failing to flash in Odin?

audit13 said:
Which file is failing to flash in Odin?
Click to expand...
Click to collapse
TMB-T889UVUCMK7-20131209151709.tar

Is there one particular file that is not flashing such as system, recovery, etc? It would be shown in the Odin log window.

its just one tar file that I was trying to flash through ODIN.
the 2nd button ( I forgot the name of it, the one that replaces the PDA )
Can you link me the sequences which I should follow to get to the stock ODIN?
Thanks,

Post the Odin log.

filename:
T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5
ODIN LOG:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.

audit13 said:
Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.
Click to expand...
Click to collapse
This is for T889.
I think the most updated one is https://www.sammobile.com/firmwares/download/56160/T889UVUCOH4_T889TMBCOH4_TMB
I am downloading this to try now

here is the new file that I tried to flash.
T889UVUCOH4_T889TMBCOH4_HOME.tar.md5
and here is the log
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Humour me but could you boot the phone into download mode and check the model #?
Have you tried using different USB cables and USB 2.0 ports?

Picture attached

Picture
Picture attached

Okay, the firmware looks good and the phone is running a 4.3 bootloader so the latest ROM from sammobile.com is the only ROM that can be flashed via Odin.
Did you get a chance to try different USB cables and USB 2.0 ports? Might try on a different computer too.

I tried different cables, will try another computer and see

Different computer didn't work either.
What else I can try?

It still fails to flash sboot.bin? The file is the bootloader which could mean the memory is damaged or the original Samsung USB cable needs to be used for flashing.
As a last resort, you could take the phone to a cell repair shop and ask them to flash the phone with a jtag cable or Octopus box.

byteless said:
TMB-T889UVUCMK7-20131209151709.tar
Click to expand...
Click to collapse

byteless said:
When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.
Click to expand...
Click to collapse
Your EMMC is bad probably.

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.