Develop Bugs

[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.

Sprint Samsung Galaxy Note 2 bootlooped not sure what is going on need help ..

<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_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> 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> sboot.bin
ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user _low_ship.tar.md5 is the ROM I am using stocked not sure what firmware was on there before the phone just died normally and was stuck in bootloop the white Note 2 screen first screen I am pretty sure the drivers are installed correctly on the pc Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and generic ones installed as well .. no updates were installed nothing was installed for awhile on it never had no problems I had it for 2 years and it is rooted so no update on battery dying. Battery charge is stuck on grey battery as well, and in recovery mode has the e mount error in red and factory reset restore does not fix the bootloop the phone stays charged good. No custom rom. In Odin 3.09 I put file in AP and on top says set partition just stuck there eventually I think it fails I have tried a few ROMS and says COM4 in blue. Any expert advice needed and phone is in solid shape no abuse. Thank you. Is it a partition problem not sure what is going on?

Hey there,
it's been a while since I had a Samsung smartphone and used odin. Are you sure your USB cable is still ok?
Maybe try another one.
And are you sure you got the correct firmware, bootloader, etc. to flash this file?
Cheers

Ok thanks for replying yea the cable is brand new lil loose on the pc port but good if not moving it around yea this l900 stock rom should work right regardless what firmware version I got I am not sure what version is on there now and it is not the newest.. this a newer rom. I put the rom in the AP checked it ran it not sure what other files or bootloader I need the bootloader is for using older firmware basically rolls back right? I do not think there is any faulty hardware is there has to be programming ..
Follow_and_Feel said:
Hey there,
it's been a while since I had a Samsung smartphone and used odin. Are you sure your USB cable is still ok?
Maybe try another one.
And are you sure you got the correct firmware, bootloader, etc. to flash this file?
Cheers
Click to expand...
Click to collapse

Fixed was faulty cables ..

t700 fails to complete Odin update.

I just acquired a T700 with the stock KitKat 4.4 OS. I want to upgrade it to Lollipop. I have already done this with my Samsung Note 10.1 and with another T700. But this unit always hangs and never completes the download. Com port turns blue when unit is connected. Here is the log from Odin3 v3.09:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF_AutoRoot_Port_T700_BeansTown106.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> SingleDownload.
<ID:0/004> cache.img
Just hangs at this point, no progress shows above the com port window. Previous units completed the download/install within minutes. I let this sit for 1/2 an hour nothing.

ebohatch said:
I just acquired a T700 with the stock KitKat 4.4 OS. I want to upgrade it to Lollipop. I have already done this with my Samsung Note 10.1 and with another T700. But this unit always hangs and never completes the download. Com port turns blue when unit is connected. Here is the log from Odin3 v3.09:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF_AutoRoot_Port_T700_BeansTown106.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> SingleDownload.
<ID:0/004> cache.img
Just hangs at this point, no progress shows above the com port window. Previous units completed the download/install within minutes. I let this sit for 1/2 an hour nothing.
Click to expand...
Click to collapse
Do you actually even realize what you are installing?
The file you are attempting to flash is cf-autoroot which will root your device.
Is that what you want?

ashyx said:
Do you actually even realize what you are installing?
The file you are attempting to flash is cf-autoroot which will root your device.
Is that what you want?
Click to expand...
Click to collapse
Is there another way to upgrade to Lollipop without rooting first?

ebohatch said:
Is there another way to upgrade to Lollipop without rooting first?
Click to expand...
Click to collapse
You don't need root to update the firmware.
Go to Sammobile.com and download the stock firmware.
Follow the instructions on the site to install it.

ashyx said:
You don't need root to update the firmware.
Go to Sammobile.com and download the stock firmware.
Follow the instructions on the site to install it.
Click to expand...
Click to collapse
Then I can also install TWRP using Odin to update to Marshmallow?

ebohatch said:
Then I can also install TWRP using Odin to update to Marshmallow?
Click to expand...
Click to collapse
MM hasn't been released for the Tab S yet.

Can't seem to root via CF-Auto Root w/ new Galaxy Note 4 (SM-N910P)

I run Odin as usual, and it's stuck at Downloadin... Do not turn off target!! with the blue bar not moving and only showing the first little bit.
Odin doesn't do anything either, and only shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltespr-trltespr-smn910p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> recovery.img
After sitting for about 20 minutes.
I've unplugged it and restarted and of course nothing is different. I'm not sure what to do from here. I just want to get rid of all these Sprint apps.

PwnCloud said:
I run Odin as usual, and it's stuck at Downloadin... Do not turn off target!! with the blue bar not moving and only showing the first little bit.
Odin doesn't do anything either, and only shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltespr-trltespr-smn910p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> recovery.img
After sitting for about 20 minutes.
I've unplugged it and restarted and of course nothing is different. I'm not sure what to do from here. I just want to get rid of all these Sprint apps.
Click to expand...
Click to collapse
Samsung driver installed? Do you have any open KIES or Samsung Smart Switch apps open? They should be closed first.
If you're using Windows 10, run as administrator is NOT required. But all other Windows versions SHOULD be ran as administrator with a right click on the Odin .exe file for app launch.
You seem to get to write and fail in Odin. Could be bad USB cable or missing the data lines in it. Original Samsung cable or a Motorola USB cable should work. Try another PC USB port as well. Rear port is often recommended but should be USB 2.0 compatible.
When and if it fails again, check your phone's display for additional information. It's a common failure in our forum for users to flash with reactivation lock enabled. But you could verify in Settings/Security that reactivation lock is disabled.
I prefer a md5 to verify my download but on the case of Chainfire downloads, download twice and check the md5 of both for matching md5. You could have a bad download.
Just typical things to check.
Since you mentioned wanting to remove bloat, have you considered just getting a package disabler from Google Play? I don't use them or know where to get a free one but here's one on sale with 7 day guaranteed refund.
https://play.google.com/store/apps/details?id=com.kunkunsoft.packagedisabler

I think you can get root by odin twrp recovery and then then flash super su
For debloat
http://forum.xda-developers.com/note-4/snapdragon-dev/tool-smartdebloater-v1-t2918623

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.