Specifics first -
Device: VS980 (VZW LG G2)
Recovery: TWRP 2.6.3.2
ROM: CM 10.2 12/6 Nightly
I had a random reboot while trying to answer a phone call today. Its happened before. So I figured I would reflash the nightly to see if it would correct itself. I entered recovery from the power button menu. I tried to flash the nightly from the CyanDelta folder (tinkering around earlier, downloaded it, detected rom, and deleted from cmupdater file). For some reason I decided to wipe cache and dalvik after installing. The phone never rebooted after that. I proceeded to try and power up only to be faced with a constant CM boot screen (I knew something was wrong when I notice how long it took to get to the CM screen). I was able to get back into recovery to try and flash the 11/30 nightly, which I hadn't touched. After flashing, I noticed the "Unable to mount /cache". So instead of trying to fight with my phone to get back into recovery, I flashed a backup. It also displayed the "Unable to mount /cache". My phone was in recovery where I performed a factory reset. ADB was recognizing it and receiving commands. I unplugged it to see if I could get into download mode. Now I cant get it back into recovery. When I do "adb devices" it shows up as "unauthorized". Where do I go from here? I have very limited adb experience.
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??
Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app
Same Problem here! Exact Same
Also having this issue, stuck in the secure boot loop, can't get to download mode.
Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!
Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.
I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.
So I bricked my N4 somehow (I don't know if it is soft or hardbricked).
I was running latest N5X AOSP 6.0 Lollipop and everything was fine, when i decided to try the AICP 0.1 experimental LP. I made a clean install but it the first boot ended in a black screen. Then i rebooted into recovery and made a factory reset and since then Im stuck in an infinite bootloop.
So here is what i tried so far:
Flashed newest Factory Image via Fastboot and ADB. Result: Bootloop
(Flashed with flash-all.bat and every img by myself, i even tried without flashing cache.img and userdata.img, but everytime i ended in a bootloop that goes longer than 30 minutes)
I tried several Toolkits but nothing helps everytime I reboot its a bootloop.
But somehow when i flash the N5X AOSP 6.0 and let it boot for some minutes and then just shut it down and boot again i can see its optimizing my apps but when it comes to start them i just stays there...
I also tried to format my /cache with TWRP into FAT and back to Ext4 (that was one solution i found) but that doesnt seem to work too..
I am very frustrated and hope someone can help me
Hi, I just tried Modding on Android for the first time. I went about this using adb commands in Ubuntu Terminal. I unlocked my bootloader then (I think) I flashed twrp recovery onto my Nexus 4 (Build Number LMY470.) When I went to check if my flashing of twrp was successful, it brought me stock recovery. I saw online that someone was in the same situation and they used the
Code:
fastboot erase cache
so I tried the same. In the terminal it looked like it was successful but as soon as I went to recovery mode it brought me to stock recovery again. In the recovery menu it said something about failing unmount or something. After this I tried turning my phone on and it has been stuck in the boot animation for the past 50 minutes. What should I do? Thanks!
EDIT: I factory reset my device after an hour and a half of not knowing you could get out of the boot animation. Now my recovery works. No replies needed.
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
I would flash TWRP and try wiping all including internal. Sounds like one of the partions is corrupted. You could do it with fastboot in bootloader mode but not sure of the commands.
teunnk said:
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
Click to expand...
Click to collapse
You're probably not used to the stock recovery. The no command droid is normal. Watch this video, and see if you can get to recovery or bootloader.