Hi guys,
New to flashing custom ROMS. Good news - flashed CM12, then LiquidSmooth and I'm learning a lot after having soft bricked my phone a few times. Bad news - After trying to get back to Stock I'm not able to get out of this LG Logo bootloop. The LG logo will flash, screen will go black and the whole process starts again. It doesn’t progress past that. I'm unable to get to TWRP recovery or download mode.
My idiotic move:
Iffy stability with camera and mobile data with CM and LiquidSmooth. Decided to go back to Stock.
I flashed my nandroid backup, which I believe led to a bootloop (can’t remember). Was able to boot to TWRP and get back to CM12. Then I had the genius idea of using AutoREC and selecting the “Go Back to Stock” option. Yes, it’s already sounding like a bad, and nonsensical idea as I say it now. Can't remember exactly what I did next - I either flashed my nandroid backup or did a factory reset through CM settings. Threw me into this bootloop.
The details:
Model - D800 - Am sure of this.
Stock software before flashing CM12 was Lollipop 5.0.2 via OTA.
TWRP Recovery 2.8x something or other. Used AutoRec to flash.
I can interrupt the bootloop and access Factory Hard Reset through Power + Volume Down
Had to go to JB Bootloader in order to Flash ROMs. Errors returned otherwise.
Roadblocks:
No download mode. Holding Volume Up & Inserting USB cable doesn't work. Although am able to get bootloop to include a blank screen with red flashing LED through this method from time to time.
Phone boots up, and goes directly into bootloop when plugging USB cable into phone. This happens both when plugging into a wall charger or into a computer. I think this is probably the biggest pain and is holding up things from progressing. Can turn off phone by holding down power for a few seconds, BUT if the phone is plugged in it will continue to boot on its own.
Phone not recognized by computer & ADB However, was at times able to get Device Manager to recognize the phone as an "Unknown Device" after going to the Factory Hard Reset screen. This is no longer working after trying different drivers. I’ve went through LG Mobile Universal Driver as well as the Koush driver.
Going through Factory Hard Reset via hardware buttons only throws phone back into BootLoop
Can’t boot into TWRP
Any insight or help guys? Thanks in advance. I think getting into Download Mode will be a quiet victory. I’d like to try to use Supersports guide once I get there to go back to stock.
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.
Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.
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
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.
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.