Hello
I have a G2 VS98026A running 4.4.4 BlissStalk.
I wanted to try and flash the crdroid 5.0 Rom, went to recovery to take a backup,
the process started and after a while the screen went black. I rebooted and tried to
enter recovery mode again, but nothing, black screen. I had TWRP 2.6.3.2.
Since then i tried reflashing all vs980 versions of both TWRP and CWM
with loki_tool and with Flashify and FreeGee, no luck.
I want to save reverting back to stock as a last resort, so I am wondering if anybody has a solution for this.
I am having a similar issue however mine was caused slightly differently.
I have jackpotcalvin unofficial cm11 and few weeks backs updated to bootstack 26a no issues. However that also updated recovery at the time.
Didn't bother me, however earlier I went into flashify and realized there was an updated twrp version. So I said why not update. So using flashify I downloaded the most recent twrp available (2.8.3.0) and then selected extract and flash directly from flashify. Chose to reboot into recovery and now nothing. There is some sort of command that appears on the LG screen when it first boots but it shows it for too short of a time for me to be able to read what it says and then I just get a black screen and that's it. Nothing else.
I am able to boot into cm11 no problems and everything else works just fine. Just don't have the option to boot into recovery.
I would also prefer not to have to do a clean wipe or anything of that nature.
Sent from my LG-VS980
Related
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
ifizik said:
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
Click to expand...
Click to collapse
Did you update your firmware also? Can't directly flash a recovery on 24A. There's some extra steps involved, AutoRec listed in the LG G2 section is the easiest way around that.
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
ifizik said:
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
Click to expand...
Click to collapse
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
So the AutoRec method worked beautifully. I have a recovery once again and was able to make a back-up so i can flash kernels
Thanks for the help.
JRJ442 said:
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
Click to expand...
Click to collapse
If you scroll down on page 2 of the document in the FAQ section it tells you how to install a recovery.
I currently have PacMan rom 4.4.4 KitKat installed on my Moto X and when I went to update to a new rom I found that TWRP didn't work. I can boot into recovery mode, but the splash screen just displays and never actually enters the recovery. I have to hold the power button down until the phone reboots to get out of it. I currently have TWRP v2.8.7.0 installed. I tried some of the older versions of TWRP and none worked. I also tried updating to the unoffical TWRP 3.0.2 and that behaved the same. Lastly, I tried Philz CWM recovery v6.57.9. That loaded and I was able to navigate the menu but once I selected a option that performed a task, it would freeze. If anyone can help me out it'd be greatly appreciated. Thanks
frew415 said:
I currently have PacMan rom 4.4.4 KitKat installed on my Moto X and when I went to update to a new rom I found that TWRP didn't work. I can boot into recovery mode, but the splash screen just displays and never actually enters the recovery. I have to hold the power button down until the phone reboots to get out of it. I currently have TWRP v2.8.7.0 installed. I tried some of the older versions of TWRP and none worked. I also tried updating to the unoffical TWRP 3.0.2 and that behaved the same. Lastly, I tried Philz CWM recovery v6.57.9. That loaded and I was able to navigate the menu but once I selected a option that performed a task, it would freeze. If anyone can help me out it'd be greatly appreciated. Thanks
Click to expand...
Click to collapse
Had a similar problem on my XT1060 Dev Ed., lost all my data coz of it. Only method which worked was to flash a stock firmware via RSDlite or manually through mfastboot.
Try option 5 from here with complete data wipe.
Try to go to bootloader first and load it from there. Already saw this working some times.
Sent from my XT1052 using XDA Free mobile app
varunpilankar said:
Had a similar problem on my XT1060 Dev Ed., lost all my data coz of it. Only method which worked was to flash a stock firmware via RSDlite or manually through mfastboot.
Try option 5 from here with complete data wipe.
Click to expand...
Click to collapse
This worked perfectly, thanks.
Hi, I updated my rooted OnePlus 3t with an OTA update (dumb, I know, I wasn't thinking). It failed and the device needed to be wiped. I've since tried to go through the process to reinstall twrp and supersu and I can no longer get it to boot when TWRP and superSU are installed. The weird thing is, I AM able to use it with the stock recovery and non-root, but any subsequent flashes fail, despite it appearing as if everything has been installed properly.
One last wrench to throw into this: I cannot access recovery (whether TWRP or stock) without running
Code:
fastboot boot recovery.img
. When I run that, I'm able to get into recovery, however if I go through the phone itself on the main menu after unlocking the phone, it just reboots and brings me right back to where I was.
Any ideas on what I may have done wrong and how to fix it? I've been following the guide from the oneplus forums, I've run that process about 5 or 6 times over the past day to no avail.
P.S. Have flashed the newest version of dm-verity
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
I also just realized that I can't really do anything about flashing the stock rom manually because the download mode is registered as fastboot and it doesn't seem to properly register in the Device Manager at all...
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Fivavoa said:
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Click to expand...
Click to collapse
In twrp there is a terminal so you might be able to get access to fastboot by removing download mode.
Look at the thread below.
https://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Hi :3
Fivavoa said:
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
Click to expand...
Click to collapse
Hello, look at this page, this would solve the problem:
https://www.androidsis.com/solucionar-problema-bootloop-recovery-actualizacion-ota-linageos/
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.