Database Users

TMMO US HD2 dead? need help.

hmmm. Sometimes I have a hard time booting up.. I turn on my phone, get to the NRGZ Energizer splash screen... but then the red text does not appear, it just freezes up. sometimes i have to do this 3-4 times before it fully boots up. Other times, i can't boot up with the phone plugged in to either the computer or wall. I get the same problem, freeze at splash. however, after i flash a ROM, it will ONLY boot up with the cord in..
Once i'm fully booted up. I get random freezes and i'm forced to reboot and deal with the aforementioned problems of boot-freeze. i've tried different versions of NRGZ's ROMs, but they all seem to do this.
The above happened in the past month, NOW my HD2 quit responding to all touch commands on the screen. So i figure the ROM was acting up. I flashed a new ROM, same end result. I selected a different dev's ROM, and tried to flash it.. It only flashed 98% and then paused there. After about 20 minutes I decided to pull the plug and try the recovery method, but it didn't. I have, so far, been unsuccessful at flashing a ROM to the device. Everytime I try it stops at 98%.
can someone please help me out? This is my primary phone, and i don't have money for another one.. not even a prepaid. I need to get this guy back up and running.. ANY help is very much appreciated.
-Josh.

josh_prayyforplagues said:
hmmm. Sometimes I have a hard time booting up.. I turn on my phone, get to the NRGZ Energizer splash screen... but then the red text does not appear, it just freezes up. sometimes i have to do this 3-4 times before it fully boots up. Other times, i can't boot up with the phone plugged in to either the computer or wall. I get the same problem, freeze at splash. however, after i flash a ROM, it will ONLY boot up with the cord in..
Once i'm fully booted up. I get random freezes and i'm forced to reboot and deal with the aforementioned problems of boot-freeze. i've tried different versions of NRGZ's ROMs, but they all seem to do this.
The above happened in the past month, NOW my HD2 quit responding to all touch commands on the screen. So i figure the ROM was acting up. I flashed a new ROM, same end result. I selected a different dev's ROM, and tried to flash it.. It only flashed 98% and then paused there. After about 20 minutes I decided to pull the plug and try the recovery method, but it didn't. I have, so far, been unsuccessful at flashing a ROM to the device. Everytime I try it stops at 98%.
can someone please help me out? This is my primary phone, and i don't have money for another one.. not even a prepaid. I need to get this guy back up and running.. ANY help is very much appreciated.
-Josh.
Click to expand...
Click to collapse
It seems more like a hardware fault. Have you tried using a different USB cable or a different USB port (or even a different computer)?
Try flashing the stock T-Mobile ROM, reinstalling the stock SPL, and claiming a warranty swap (say you're experiencing problems that can't be solved by the ROM update or hard resets). Warranty swaps are free, and usually arrive at your doorstep in 3 days.
Good luck.

S4 bootloops on every rom, even after Odin stock flash.

Hello, I am having an issue with my S4.
I was having random reboot issues and my rom was quite old (omega 30 or something) so I decided to update my phone. I flashed stock from odin, then installed TWRP again and tried flashing roms. Roms previously would boot up to the point where I would setup android and then reboot. Now my phone seems to reboot almost directly after the "Samsung Galaxy S4" logo. Some roms have let me boot into the android setup but once the Mobile Network seems to try to connect, the phone reboots right away.
I have tried flashing 3 different stock roms thru ODIN and they all have the same issue. I have tried clearing cache/data in recovery but it hasnt helped.
Does anyone have any suggestions or advice? Thanks!

Might be a power button issue. A friend had a similar problem. The phone would boot and work for some time and then turn off.
At some point it just wouldn't turn on anymore.
It was the power button.

GDReaper said:
Might be a power button issue. A friend had a similar problem. The phone would boot and work for some time and then turn off.
At some point it just wouldn't turn on anymore.
It was the power button.
Click to expand...
Click to collapse
Thank for your reply!
Just curious, if it was the power button, wouldnt my phone also restart in recovery and in download mode? In both of those modes, there is no issue. I'm worried that I flashed a modem incorrectly some time in the past and that could be casuing me issues. If the stock rom passed in odin, shouldnt the modem be working correctly?

BigNaes said:
Thank for your reply!
Just curious, if it was the power button, wouldnt my phone also restart in recovery and in download mode? In both of those modes, there is no issue. I'm worried that I flashed a modem incorrectly some time in the past and that could be casuing me issues. If the stock rom passed in odin, shouldnt the modem be working correctly?
Click to expand...
Click to collapse
Stock roms have modems and bootloaders included. So it must be something else.

GDReaper said:
Stock roms have modems and bootloaders included. So it must be something else.
Click to expand...
Click to collapse
It's very odd. I have no problems getting into recovery or download mode, but absolutely anything I flash will not boot with any reliability and not for more than a few seconds. I was able to flash Omega 42.1 and that worked for about 30 minutes yesterday and then began bootlooping as well.
I have no ideas.

I hate when people solve their problems and don't follow up on their own threads so here I am to post my solution.
Turns out my battery was slightly swollen and causing the battery to disconnect and make the phone restart. I noticed this after a bunch of various testing with the phone plugged in and unplugged. The phone would work fine plugged in but within a minute of being unplugged it would turn off or reboot.
I purchased a new battery and have had no problems at all since, everything works great. When I compare my swollen battery to the new battery, you can see it is slightly swollen but hardly noticeable if they are not side by side.
Anyway, for anyone reading this thread in future, my solution was to replace the battery which had swollen.

Phone still gets stuck in boot loop after flashing stock firmware

I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.

I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?

alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet

Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.

After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.

The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.

alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?

harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.

OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.

Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.

I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.

Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?

harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.

alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..

guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly

Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?

So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.

alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app

My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?

alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.

Nexus 10 bricked, bootloader possibly corrupted: fix?

I just aquired a used Nexus 10 that I wanted to flash with Lineage. Before that, I had successfully flashed every android device I have ever owned, so I thought there'd be no problem. After unlocking the bootloader I tried flashing TWRP recovery (on Linux using fastboot in the terminal), but it took several minutes and when suddenly the sreen started flickering and the flash still wasn't done, I tried to CTRL+C to no avail. I figured that I'd at most corrupt the recovery which would be quite fixable, so I unplugged the cable and tried restarting the tablet. I could still select the options in the bootloader, but when I selected anything, it didn't work (not even shutdown).
Whenever I try to start the tablet now, nothing happens. When it is plugged in to the wall, it shortly shows the "full battery" symbol and the goes black again. No combinations for bootloader or recovery work anymore. I suspect that the unsuccessful flash corrupted the bootloader, so how could I fix that. I do have FTDI and STM32 flashing devices, if that is any help.
P.S.: I already tried removing the battery in case there was anything in volatile memory preventing the boot.

I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.

Atreus said:
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Click to expand...
Click to collapse
Good to hear:good:
Please mark your thread as [SOLVED] if it is, or give us an update on how did you go about the battery perhaps?
Cheers

Nexus 5x will only work while plugged in...

All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real

realkewl said:
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
Click to expand...
Click to collapse
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.

xxJMarian said:
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
Click to expand...
Click to collapse
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real

realkewl said:
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
Click to expand...
Click to collapse
You did it wrong. You have to flash the boot.img that disables 2 of your cores. Search it here on the forum you'll find it