Database Users

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.

Need urget assistance

Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop

Nortonic said:
Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop
Click to expand...
Click to collapse
Whats the error displayed in odin mode

kpwnApps said:
Whats the error displayed in odin mode
Click to expand...
Click to collapse
No error other than saying (Successful: 0 / Failed: 1)

Nortonic said:
No error other than saying (Successful: 0 / Failed: 1)
Click to expand...
Click to collapse
Try different cable. Sometimes its cable fault

kpwnApps said:
Try different cable. Sometimes its cable fault
Click to expand...
Click to collapse
Tried 5 different cables, OEM, and off-brand.
I've contacted samsung again.

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

Can the bootloader get corrupted? I feel like mine did.

A couple of days ago. I wanted to check my phone in the morning and it started boot looping when I pressed the power button. Then, after a couple of boots it went into the TWRP recovery. I wiped cache/dalvik in hopes of a quick fix but still boots into recovery.
I can also go into the bootloader but the bootloader is completely unresponsive. It just gets stuck on the "barcodes" option, the volume keys do nothing and adb doesn't see my device when it's in the bootloader. I also tried re-flashing the same ROM I'm using(within recovery) to no avail.
I still intended on using this thing for a couple more years (I have a couple of spare OEM batteries and a spare chasis). Really appreciate any help.

Recovery.log from TWRP

Any flash drive can become corrupted.
Boot loops are commonly caused by poorly coded apps like launchers and power management apps.
Rootkits are always suspect with abnormal boot ups and unstable operation when no other cause can be found.
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
*a drop, water exposure or a ESD event when repairing a phone can cause this... sometimes not immediately.

blackhawk said:
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
Click to expand...
Click to collapse
Can I reflash firmware without the download mode working properly?

Sorry, way beyond my skillset...

troubleshooting, bricked overnight

Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.

PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/

I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?

PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.

I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.

PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look

That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...