Database Info

CM7 boot loop

I'm stuck in a boot loop and I have no idea why, and I've tried wiping cache, wiping data/factory reset, and re-flashing the CM7 rom. Nothing worked. What happned was, my phone died, so I plugged it in, and it went into "charging mode". The phone will boot, but the touchscreen doesnt work, and non of the radios turn on, so that it can just charge I guess? anyway, the phone got to about 20% battery so I decided to reboot it so I could actually use it while charging, but when I did, it started boot looping. I tried everything mentioned above and its still boot looping. Is there anything else I can try?

let phone go all the way dead
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?

fukenbiker said:
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
Click to expand...
Click to collapse
Yea, that non responsive state is what led me to reboot. It only does that when the phone is dead and you plug it in. I assume it's because with cm7 there is no way to charge while the phone is off, at least that's the way it was with my infuse and captivate. So that's not the issue. It's that when I rebooted to get out of that state, it gets to the cm7 boot logo and then reboots. It's never done that before, and I do that a lot. I searched for this issue and I found someone with a nexus on cm7 that had a boot loop, and it was solved by some cwm zip that deleted the partitions, then once you do that, if you flash cm7, all will be well, but I don't know if that's applicable to this situation.
EDIT: I tried the battery pull, I left it out for 20 min and it's still boot looping

How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod

I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod

fukenbiker said:
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I hold the power button until the phone reboots.
fukenbiker said:
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I use the three button combo to get into recovery, and I did wipe data then flash both version 4 and the kernel, and it still loops. I am so confused as to how in the world this happened... anyway, I tried to go back to stock using odin twice and it just got stuck at system.img.ext4.

Oh dear you must take this to the Odin thread.... You belong there until you flash back to stock. Did you try only holding volume down when plugging in to download mode? Your skyrocket is powered down when you try?
Sent from my SGH-I727 using xda premium

I got into download mode fine the first time. then when it got stuck, I changed to a usb port on the back of my pc, but it still got stuck. now it just boots right into download mode.

I don't know what changed.. but since going back to stock wouldn't work, I decided to re flash cwm and try to install cm7 again, and I'm now back up and running just fine. This whole situation was very odd... Thank you for being helpful.

Odin3-v1.85.zip is what you have set up on your computer?
Glad you fixed it.
Sent from my SGH-I727 using CyanogenMod

[Q] Bricked Phone, and T-Mobile Replacement policy

I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?

aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!

Racing19969 said:
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Click to expand...
Click to collapse
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed

aanonymoushuman said:
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
Click to expand...
Click to collapse
what rom were you flashing when this happened?? if it was a stock rom you should have been using odin.. unless it was one of the stock CWM flashable roms... if you can't get it going send me a pm.. I do JTAG repair

aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.

anactoraaron said:
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
Click to expand...
Click to collapse
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)

aanonymoushuman said:
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
Click to expand...
Click to collapse
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...

anactoraaron said:
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
Click to expand...
Click to collapse
I got a replacement going from T-Mobile, they just sent out the new phone today, but I'm confused do I send them my broken one right now? or wait till the new one comes?

They should have explained everything on the phone, they will send you a box to return it in . And if they find out that it has been rooted and modded , you could be charged the full price for the phone. Every time I sent the phone back I've always read it back to stock if yours was bricked hopefully they won't notice
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

boot loop - can't navigate bootloader to get into recovery mode

hi there,
I'm running CM11 nightly late feb. For no apparent reason my phone went into a boot loop this morning (n.b. I didn't flash a new rom or installed a new app). Now it constantly reboots (literally) and doesn't get further than the CM11 boot video or google logo.
If I press volume down and power, it will head into bootloader - but - I can't navigate beyond 'shut down' or 'restart bootloader'. It doesn't execute two consecutive volume up or down commands. In other words, it's impossible to get into recovery mode. Also, because my phone doesn't boot further than the video or logo, I can't make a fastboot or adb connection via my laptop.
Does anybody know how I can fix this issue? I'm clearly running out of luck. Many thx in advance!

reflash recovery?

Try to boot into recovery with cmd: fastboot boot TWRP.img (TWRP or your current custom recovery)
Then restore a nandroid backup or wipe data/system/dalvik
You can still flash the factory images. Fastboot mode is enough. Guide

suikerchiller said:
Now it constantly reboots (literally)
Click to expand...
Click to collapse
Stuck power button. Mash the power button really fast for 20 seconds to unstick whatever is in there.

gd6noob said:
reflash recovery?
Click to expand...
Click to collapse
can't flash anything, because phone is constantly rebooting. Have opened up the phone and took the battery out for 1 minute. Didn't help either. After starting up the phone I get stuck in the boot loop again.
Anyone else an idea?

suikerchiller said:
can't flash anything, because phone is constantly rebooting. Have opened up the phone and took the battery out for 1 minute. Didn't help either. After starting up the phone I get stuck in the boot loop again.
Anyone else an idea?
Click to expand...
Click to collapse
The phone doesn't reboot in the bootloader right?
If it doesn't either do what primokorn said or flash the factory image.
Sent from my Nexus 5

El Daddy said:
The phone doesn't reboot in the bootloader right?
If it doesn't either do what primokorn said or flash the factory image.
Sent from my Nexus 5
Click to expand...
Click to collapse
Well the issue is that it only stays for a fraction of a second in bootloader, which gives it enough time to navigate one step up or down. Not enough time to get into recovery.
How can I do what Primoken said? It doesn't seem to be possible to do a flash when the phone is constantly rebooting?
Thx for helping me out guys, much appreciated!

suikerchiller said:
Well the issue is that it only stays for a fraction of a second in bootloader, which gives it enough time to navigate one step up or down. Not enough time to get into recovery.
How can I do what Primoken said? It doesn't seem to be possible to do a flash when the phone is constantly rebooting?
Thx for helping me out guys, much appreciated!
Click to expand...
Click to collapse
Have you ever kept your phone in narrow pocket? Because it's definitely sounds to me like a stuck power button.

Simonna said:
Have you ever kept your phone in narrow pocket? Because it's definitely sounds to me like a stuck power button.
Click to expand...
Click to collapse
It's not a power issue. Also unscrewed my phone to see if that was what caused it. Nothing in there, mechanism functioned correctly.
UPDATE: For some reason my phone booted up out of nothing. I managed to flash an older ROM via CM Updater (through settings)- which seemed to work. Apps were updated and it was running normally. But after a couple of minutes it restarted out of the blue and now back to square one again.
Guess there's a chance I'll probably get a normal start up soon. Is it a good idea to do a factory whipe restart through the settings menu? Or is Primokorn's method safer?

suikerchiller said:
...Or is Primokorn's method safer?
Click to expand...
Click to collapse
Yes.

Stuck on bootloop

i'm running the arter97 X kernel w/ stock rom on my sm-n920t. i have xposed installed and a few thing disabled through package disabler pro and thats about it. phone worked fine for weeks. went to sleep with it at 9% around 2am this morning with the intention of charging when i woke. got up @ 10am, plugged it up, hit the power button and i've been stuck in bootloop ever since. im able to get to CWM recovery mode but my backups are on my pc, not the sd card. when i plug into the pc the bloody thing doesn't even recognize it (it does kinda, b/c it makes the sound but never shows). i've got the proper drivers installed. not sure what to do or even how this happened. Would greatly appreciate any advice...

newguy15 said:
i'm running the arter97 X kernel w/ stock rom on my sm-n920t. i have xposed installed and a few thing disabled through package disabler pro and thats about it. phone worked fine for weeks. went to sleep with it at 9% around 2am this morning with the intention of charging when i woke. got up @ 10am, plugged it up, hit the power button and i've been stuck in bootloop ever since. im able to get to CWM recovery mode but my backups are on my pc, not the sd card. when i plug into the pc the bloody thing doesn't even recognize it (it does kinda, b/c it makes the sound but never shows). i've got the proper drivers installed. not sure what to do or even how this happened. Would greatly appreciate any advice...
Click to expand...
Click to collapse
Have you tried going into recovery and plugging in USB cable to the phone and AC charger for 30 minutes and then power off the phone in recovery mode then power up the phone using the power button?
If that don't work do a full wipe in recovery including factory reset.
Doing a full wipe in recovery by default will not wipe the internal sdcard unless you select that option.
Good luck,
Have a happy new years.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
Have you tried going into recovery and plugging in USB cable to the phone and AC charger for 30 minutes and then power off the phone in recovery mode then power up the phone using the power button?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
just tried this and nothing. Guess i'll attempt the wipe. By wipe i'm assuming you mean factory reset in CWM?
and if so, am I able to (or is it sensible, rather) restore the phone from the last backup/nandroid that contained Xposed+Arter97 Kernel?

newguy15 said:
just tried this and nothing. Guess i'll attempt the wipe. By wipe i'm assuming you mean factory reset in CWM?
and if so, am I able to (or is it sensible, rather) restore the phone from the last backup/nandroid that contained Xposed+Arter97 Kernel?
Click to expand...
Click to collapse
It's best not to do a restore, start fresh for best results.
I would also suggest that you flash twrp recovery and get rid of philz.
A factory reset in twrp does not wipe internal sdcard unless you select it.
99% of people who have the G928T S6 EDGE+ and the N920T Note 5 all use twrp.
Here is the download link for twrp:
https://www.androidfilehost.com/?fid=24352994023704396
Flash this in recovery.
Good luck,
Happy New Years.
Sent from my SM-G928T using Tapatalk

Tried to restart S7, now it won't boot again. Stuck on Galaxy logo.

Hey,
for the past months my S7 worked as it should. I am using Lineage OS. Today - as I was using WhatsApp - I got "Not responding" errors. I tried to open the settings but even here I got the same error. So I tried to restart it. Held down the power button and selected "restart". But then it just reached the Samsung Galaxy Logo and started again. Over and over. Recovery mode does not work, but the Download mode does. Right now I am trying to stay in the Download mode to drain the battery (it was at 100% when the error occured) to get the S7 to shutdown completly so I can try to get into Recovery mode again. I want to backup my data. Does anybody know what could have caused that behaviour? Or maybe can tell me what to do?
Thank you very much in advance
€dit: After the battery was empty, I connected it to the power cable and it went straight back to the reboot loop.

bibold89 said:
Hey,
for the past months my S7 worked as it should. I am using Lineage OS. Today - as I was using WhatsApp - I got "Not responding" errors. I tried to open the settings but even here I got the same error. So I tried to restart it. Held down the power button and selected "restart". But then it just reached the Samsung Galaxy Logo and started again. Over and over. Recovery mode does not work, but the Download mode does. Right now I am trying to stay in the Download mode to drain the battery (it was at 100% when the error occured) to get the S7 to shutdown completly so I can try to get into Recovery mode again. I want to backup my data. Does anybody know what could have caused that behaviour? Or maybe can tell me what to do?
Thank you very much in advance
€dit: After the battery was empty, I connected it to the power cable and it went straight back to the reboot loop.
Click to expand...
Click to collapse
Do you have twrp installed? If not flash twrp with Odin and reinstall the lineage you were using from the sd card (the exact same version). All your stuff should be saved.

cooltt said:
Do you have twrp installed? If not flash twrp with Odin and reinstall the lineage you were using from the sd card (the exact same version). All your stuff should be saved.
Click to expand...
Click to collapse
TWRP is installed, but I am not able to get there. Just into Download mode. Should I try to reinstall it or could that create other errors?

bibold89 said:
TWRP is installed, but I am not able to get there. Just into Download mode. Should I try to reinstall it or could that create other errors?
Click to expand...
Click to collapse
Problem with lineage is it could be any number of errors. You have a slim chance of rescuing your phone if you can reinstall twrp then the version of lineage you were using.
If this doesn't work then it's back to the start I'm afraid.

cooltt said:
Problem with lineage is it could be any number of errors. You have a slim chance of rescuing your phone if you can reinstall twrp then the version of lineage you were using.
If this doesn't work then it's back to the start I'm afraid.
Click to expand...
Click to collapse
Ok, I'll try it. Thank you very much and merry christmas

Ok, I installed LineAge, it booted and went dark. No lifesign anymore. It won't even Charge.

bibold89 said:
Ok, I installed LineAge, it booted and went dark. No lifesign anymore. It won't even Charge.
Click to expand...
Click to collapse
Plug it in and leave it for at least 15 mins. It doesn't matter if the light doesn't come on just leave it. You need at least 50% charge before flashing and rebooting.