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

Stuck on Boot after Update

I have never installed another Rom before.
However I checked for software updates for my phone, and apparently I needed to update my phone.
After I updated it, it looked great and very fresh.
However when my battery died, I tried turning it back on...and it's just stuck on the whole boot loader sequence. How do I fix this??

Take out the battery, wait a minute, put it back in, check to see what happens.
Sent from a dream.

elijahwhite said:
I have never installed another Rom before.
However I checked for software updates for my phone, and apparently I needed to update my phone.
After I updated it, it looked great and very fresh.
However when my battery died, I tried turning it back on...and it's just stuck on the whole boot loader sequence. How do I fix this??
Click to expand...
Click to collapse
Teichopsia said:
Take out the battery, wait a minute, put it back in, check to see what happens.
Sent from a dream.
Click to expand...
Click to collapse
Do that ^^^^, and if you still are in bootloop, then do a wipe cache...if not contact HTC support. Just for curiosity, was your phone rooted?

Hmm
Unfortunately it wasn't that easy.
I even did a factory reset...and it continues to loop. I tried connecting it to my PC and manually install the software again...no luck.
I called HTC and they have made an "escalated tech ticket" for my current situation. There didn't seem to be any problems during the installation of the software from the update via phone. And the new software was working perfectly for a couple hours...until it's battery died.
I have never modded or rooted or flashed my phone. So I'm just confused as to how this can randomly happen with no cure.

Since you've never done any of those things, let htc handle it. If you have any issues after that, come back and we will see what we can do to help.
Sent from a dream.

[Q] What is wrong with my HTC Sensation? :(

Hello everyone,
First of all sorry if what am about posting had already been discussed, I just couldn't find it. My device has been behaving weirdly recently. It all started by it turning off randomly when I flashed the JellyBean 4.2 custom ROM by albinoman. And each time I turned it back on it showed a battery percentage that was either smaller or bigger than what was there before. I decided to move back to Revolution theme but the same issue persisted. Now, my phone can't go pass the Beats Audio logo when it turns on, but stops and goes off. If I try turning it on again it wount untill I remove the battery, wait like 15secs and put it back again. When I plug in the charger, the LED comes on, goes off and comes on again after 5secs or so...just assuming that. Please if anyone out there could help me out I'll be absolutely grateful , please...

Frubots said:
Hello everyone,
First of all sorry if what am about posting had already been discussed, I just couldn't find it. My device has been behaving weirdly recently. It all started by it turning off randomly when I flashed the JellyBean 4.2 custom ROM by albinoman. And each time I turned it back on it showed a battery percentage that was either smaller or bigger than what was there before. I decided to move back to Revolution theme but the same issue persisted. Now, my phone can't go pass the Beats Audio logo when it turns on, but stops and goes off. If I try turning it on again it wount untill I remove the battery, wait like 15secs and put it back again. When I plug in the charger, the LED comes on, goes off and comes on again after 5secs or so...just assuming that. Please if anyone out there could help me out I'll be absolutely grateful , please...
Click to expand...
Click to collapse
post your bootloader details
and what recovery do you have?

rzr86 said:
post your bootloader details
and what recovery do you have?
Click to expand...
Click to collapse
My bootloader is unlocked but I can't get the exact details cuz my phone wount turn on anymore. The recovery is 4ext touch V1.0 and I'm pretty sure my firmware is "universal"

Frubots said:
My bootloader is unlocked but I can't get the exact details cuz my phone wount turn on anymore. The recovery is 4ext touch V1.0 and I'm pretty sure my firmware is "universal"
Click to expand...
Click to collapse
if you have universal firmware as you said then you are on S-OFF
follow this
format all partitoins except sdcard from 4ext
flash the rom
if it doesn't boot then flash the boot.img of the rom via fastboot command
the command is fastboot flash boot boot.img

rzr86 said:
if you have universal firmware as you said then you are on S-OFF
follow this
format all partitoins except sdcard from 4ext
flash the rom
if it doesn't boot then flash the boot.img of the rom via fastboot command
the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Little issue is, its getting worse everyday. A couple of days ago I could still turn on the phone and get to the recovery but now it wount even turn on or charge anymore. Could it be my battery is dead?. Cuz it started behaving weirdly recently...like when the phone rebooted it showed a far different battery percentage either lower or upper. Then one day it showed grey with an exclamation sign on it. Then when I plugged in the charger, the LED turned on, then off and then on again and went straight to green, like it charged faster. Thanks for your help, I just hope my phone aint just good for the trash

Try with a new battery.

Constant rebooting

I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.

it looks like motherboard is gone. I hope you can return it when you have custom rom installed.

DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.

turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk

DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.

carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.

DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.

carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.

DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol

Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.

LG G3 Bootloop

Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!

acmilandroid said:
Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!
Click to expand...
Click to collapse
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk

hyelton said:
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Not yet, but I definitely will. What difference does it make? Thanks for helping!

acmilandroid said:
Not yet, but I definitely will. What difference does it make? Thanks for helping!
Click to expand...
Click to collapse
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk

hyelton said:
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?

acmilandroid said:
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?
Click to expand...
Click to collapse
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk

hyelton said:
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk
Click to expand...
Click to collapse
Yes. However, I'm not sure if I was able to manually boot into download mode or the phone automatically did it. I did pull the battery before connecting the phone, and I did hold volume up. I just don't know if I physically put it into download mode myself.

New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.

acmilandroid said:
New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.
Click to expand...
Click to collapse
Were you able to solve the issue and progress any further???