Database Develop

[Q] So I wiped System in TWRP...

Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891

So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.

hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?

dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.

hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...

I followed what you suggested and got the phone back up and working. Thanks again.

How to encrypt with TWRP recovery installed

I realised I haven't re-encrypted my Titan yet since wiping it to correct some issues but when I tried, it just reboots. I've run into this issue before, which is caused by having a custom recovery (in my case TWRP) installed as Android uses the stock recovery to do the encryption. I don't particularly want to mess around flashing back the stock recovery and then back to TWRP, so is there a way to encrypt the phone without doing that, perhaps using ADB?

Bump. If the only way to encrypt it is to flash back the stock Recovery, could someone point me to where I can find some instructions on doing this and a download link please?
EDIT: Never mind, I found this now http://forum.xda-developers.com/showthread.php?t=2635706 so I'll use that to flash stock recovery.

I have failed at flashing

Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!

mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again

mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628

Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!

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.