Database Develop

[SOLVED] Latest beta OTA (NPD90G) won't stop booting to recovery

Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?

Same thing for me. I had to run the preview 4 twrp zip
Sent from my Nexus 6 using XDA-Developers mobile app

Gromlakh said:
Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?
Click to expand...
Click to collapse
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).

Good news: got the phone to boot by going to bootloader first, then telling it to boot to system from there. So the phone works again, but the update didn't stick.
Will try flashing stock recovery in a bit. Thanks!
Sent from my Nexus 6 using Tapatalk

mrjiggywiggy said:
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).
Click to expand...
Click to collapse
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.

Gromlakh said:
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.
Click to expand...
Click to collapse
nope

Problem ultimately solved by flashing the zip from here: http://forum.xda-developers.com/nexus-6/general/android-n-preview-5-beta-npd90g-t3421459 (method 1). Everything is working just fine now.

Droid Turbo brick

I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.

LG L90 D415 Constant Recovery

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/

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

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.

Miui 12 ota Update. Fell back to fastboot

Hello. I recently updated my stock miui 11 rom over to miui 12 through the ota update (the phone is unlocked and had twrp installed). Everything seemed to have gone alright. Rom was running great without issues. I restarted the phone after changing the phones region settings and the phone was stuck at the initial miui screen and the restarted itself and went into fastboot. I tried to restart it manually from there and it would just always end up in fastboot. I know from this point, wiping the phone and using miflash to reflash full stock would probably be the next step. I may be mistaken but I recall reading somewhere that there was some anti-rollback thing in place. There doesn't appear to be a rom image or fastboot image I can find to reflash to miui 12 from miflash yet. My concern would be , if i reflash using the miui 11 rom from miflash, would that trip some sort of anti-rollback or would it be ok since it's still android ver 10?

Stll have twrp? Try clearing dalvik\cache or do factory reset from there.
If not have twrp flash it since you have fastboot, try

holymoz said:
Stll have twrp? Try clearing dalvik\cache or do factory reset from there.
If not have twrp flash it since you have fastboot, try
Click to expand...
Click to collapse
Unfortunately, I went another route for the moment and tried the pixel experience rom. Sadly, the phone is constantly freezing and restarting. I do have access to twrp still. Im hoping maybe i can get a stable rom back on this phone because for some reason right now it doesn't seem to want to run anything stable. I'm not sure what to do.
*EDIT* I may have possibly figured out the problem. The first time i had it freeze and crash was when i was using something that involved the sdcard. I've taken the card out of my phone and so far i haven't had any freezes or crashes. yet...

Here the recovery full rom, when I have time will try
https://www.notebookcheck.net/Mi-8-...ade-eligibility-for-the-Mi-9-SE.487980.0.html