Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?
When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?
When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.
When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.
Related
I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
I was having terrible GPS reception and I tried the antenna fix- sliding a tiny peace of thick paper under the antenna connectors:
https://www.youtube.com/watch?v=K1-uCIb-t8I
After powering up the phone booted once, then rebooted after couple of seconds and has been bootlooping on Google logo since.
- Takes much more time than normally to power on, then falls into Google logo bootloop,
- Cannot go into bootloader, power + vol buttond doesn't do a thing,
- If I hold vol up + vol down while bootlooping it powers off,
- Plugging in doesn't change anything, no charging indicator when powered off.
Is there anything I can do ?
Did I kill my phone ? If so, how ? What could I have damaged by simply prying the cover open ?
Are all the connections secure?
I checked all the connectors, they're ok.
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Heniuro said:
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Click to expand...
Click to collapse
Might need to wait for 5.1
5.0 is buggy
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
Sadly that is because of a hardware issue. Been happening. A lot lately.
hyelton said:
Sadly that is because of a hardware issue. Been happening. A lot lately.
Click to expand...
Click to collapse
Alright, that's what I had read. Just seemed like a software issue so I was hoping for the best. I went ahead and ordered a new device. Im guessing a full motherboard replacement would be required to fix the device?
Recurring Issue
Hello,
The same problem happened to me a few days ago so this is trully a recurring issue.
I also tried to fix my rom by reinstalling it, then tried to install multiple new rom, and finally flashed the original stock rom. I also am stuck on the bootloop issue.
I'm going to contact LG to see if they can do anything to repaire it but my hope are very low.
I'll try to update this message if I find a solution.
Mine just started bootlooping and no wifi and today it just died. Battery pulls didnt work either no power at all. Probably going to switch to the V30 when its released.
Sent from my One using Tapatalk
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
It's probably to late but theres another method returning to stock KitKat dont know the link off hand in development forums. Sucks you couldnt try no adb methods. Still have the Phone want to sell it i need a cheap screen ?
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!