usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Ra dio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
good luck to you and your phone. i was afraid of these things too, so before i started to do anything, i saved some roms onto my virtual sd card, just to be sure if i get stuck without a operation OS, i still have some roms on my memory. and before starting with anything, i charged my phone up to 95%.
sorry, i can not help you and i guess you have to wait for a solution.
Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.
rattfink said:
Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.
Click to expand...
Click to collapse
Okay, so I had this problem and at the end of the day I had to turn it in to Samsung for warranty purposes because the phone would automatically turn off when on and then restart the boot process and turn off again. However, I found a temporary fix, if you pull out the battery wait for a while (like an hour) and put it back in, the phone should stay on longer so you can flash through Odin. The phone will no longer turn on normally because once you start the flash with Odin the boot.img has been flashed but it's a broken flash due to the fact that the phone turned off in the process.
Here are simple steps:
Take out the battery and leave it out for an hour or so (longer won't hurt)
Get the USB plug and make sure it's in the computer and Odin is started with the correct tar file already selected so that you can flash it quicker
Put the battery back in and start the phone in download mode
Connect the phone and just let it sit for a couple second to make sure it stays on
If it does stay on for more than 15-20 seconds then you can begin the flashing process
If it turns off while in download mode you can take out the battery and put it back in (you don't need to wait)
It's really all just a matter of patience because eventually, the phone should turn on for long enough
Once flashed, the phone should work for a while
So after following that process, I got the phone to work for about 2 months but the issue reoccurred. I was eventually able to flash the stock rom but the problem persisted. So I called in to Samsung to turn it in for the warranty. So far, they have "Replaced a component" in my phone. I SHOULD have it back by Monday. :fingers-crossed:
Thanks, for the response. Battery is out now so I'll try later this evening after it sits for awhile.
I hope it works for you. Just as an update, Samsung has fixed the problem and my phone has shipped as of today! So I guess it's an error on their part.
No luck yet.. Going to leave battery out overnight and try again in morning.
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.
I just recently Odin the NJ3 tar over my ND8 stock deodexd debloated ROM a couple of weeks ago. Then I started experiencing that the phone will randomly shuts off automatically and the only way to turn it back on is to plug it into a power source.
So I decided to flash the Stock+NJ2+Deodex.zip using Philz after doing a wipe to install a new ROM. This caused the phone to only boot to the Sprint Logo and then it shuts down. So I decided to wipe and install Wicked S5 Xperience V2.2. Now I am at where the phone will only boot and runs if it is plugged into a power source.
Can someone suggest a solution or steps to get my phone back to stock (including all the needed downloads)?
Can I restore a backup I made prior to updating to NJ2 (while still on ND8)?
Can I install the ND8_STOCK_DEODEXED_ROOTED.zip after upgrading to NJ3?
Note: The phone runs fine when I boot into Philz and so it cannot be a bad battery?
Installing an ND8 Stock ROM on NJ2 disables Wifi. So I managed to install the Stock+NJ2+Deodex.zip and get the phone running just as long as it is plugged in.
When I unplug to run on battery, the phone turns off. When I try to turn it on, it gets to the Sprint Logo and then turns off.
I can boot into Philz recovery mode on battery and it works fine in recovery mode without turning off.
Does anyone have any suggestions as to what could be wrong?
[Solved] New Battery
Thanks for all the help.
The Sprint store tested the battery and it failed. Installed new battery and phone is now working again. What's the chance the battery gave out at the same time I flashed a ROM?
So i was flashing a new rom with twrp bootloader unlocked everything went well and then when i went out of twrp it just would't turn on anymore just off but the screen was still on so the phone too but then i thought just to wait till the battery dies and so it did i put my phone to charge and i didn't say anything so i just let it there came back about an hour later still nothing and it wont turn on, nothing at all i don't know what to do i hope it ain't hard bricked
Try booting into download mode(odin mode), you'll have the confirmation page on it DO NOT GO PAST IT, let your phone on there for a few a hours so it can get enough juice to flash your stock firmware.
From my experience one hour should be enough to flash but you have to be quick after you take it out of the charger and put putting it to the pc. I also recomend to have every firmware file preloaded on odin.