I was trying to install CM12 on my VS980 LG G2, and in order to do that I installed TWRP 2.8 because that was what they recommended to use with that version. It worked, and I installed it by using the flashable zip from http://blastagator.ddns.net/twrp/2-8-3-1.php
I used this recovery to install the latest build of CM12 from here: http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269 after wiping my data using advanced wipe as the TWRP thread says to. I wiped Dalvik, system, and cache, and then flashed the ROM, GApps, and SU.
When I rebooted, I was bootlooping. Not too abnormal for flashing things on this phone, so I went back into recovery to restore the backup I had made, to find that the backups file list is completely blank. No (Up a folder) or anything. So I panic, and think I wiped more than I have to, so in order to reset everything and start over, I did a format. It says it completes, so I reboot and get back into recovery, and push a new rom to /data/media/0.
Now, when I try to install that zip, it's not there. Nothing gets placed in there. Installing a zip from anywhere else results in bootloops because it can't boot anything, somehow. It's like there's two partitions and it's trying to boot from the one with nothing on it, and that's the same one I'm shown when I go into the restore menu. There are folders like /data/, /sdcard/, etc still visible if I try the install option, but they do not show up when I try to use the file manager in TWRP.
I'm not sure what to do, can I fix the partitions that TWRP is looking at somehow, or is that not even the issue here? I would like my phone to be usable and I feel that having the recovery it shouldn't be this hard to get it back to booting order.
Thanks
I have close to the same issue on my vs980. Except I have twrp 2.7 and I can't flash it 2.8.4 it always fails. But cm12 and gapps were successful on 2.7 version of twrp except it out me in a bootloop. Which my backup and everything was still there for me to restore. Do you have an issues with random reboots after you put twrp on your phone too?
Related
TWRP in general for me has been a mixed bag. I remember using it back when I had my Galaxy S4, and it had problems making nandroids for Touchwiz, but not CM. Typically there was a problem with the kernel. Lately with my Nexus 6 periodically it will either freeze/stall. Tonight I created a nandroid and for whatever reason when I was trying to restore it, it showed it was restored then when I tried to reboot system, the phone rebooted into bootloader mode. I could not reboot the phone it just kept cycling into bootloader mode no matter what I did.
I did not have internet, all I had was a copy of the most recent TWRP and a custom ROM zip. I recommend always keeping a copy of these files. At any rate, there's something wrong with TWRP. Initially I went into fastboot and just re-flashed TWRP. Still had problems. Then I used fastboot to erase recovery, then reflash via fastboot the copy I had then used adb pull to pull in the custom ROM into the sdcard and started up.
Has anyone else encountered this?
flash factory image,flash twrp and restore nandroid backup
Has anyone noticed how TWRP doesn't persist with the latest N dev preview?
I'm not talking about systemless install, either.
I verified that TWRP renames "recovery-from-boot.p" to "recovery-from-boot.bak" before first boot, but on next boot into recovery, it's back to stock.
I even manually renamed "/system/bin/install-recovery.sh" to "system/bin/install-recovery.bak", and "/system/etc/recovery-resource.dat" to "/system/etc/recovery-resource.bak".
Then I deleted all three files; TWRP still gets overwritten with stock recovery.
AFAIK these are all the files associated with creating stock recovery from the boot image, so not sure what else to try.
As it stands, the only way to use TWRP is to fastboot it from pc every time you want to use it.
Btw, I know I can just use a custom rom instead, so please don't provide that as a "solution" lol.
*Edit*
It seems that after deleting these three files and then reflashing TWRP solves the problem.
SuperSU still disappears after a data wipe, but with persistent TWRP, at least it can be reflashed without pc...
Q9Nap said:
Has anyone noticed how TWRP doesn't persist with the latest N dev preview?
I'm not talking about systemless install, either.
I verified that TWRP renames "recovery-from-boot.p" to "recovery-from-boot.bak" before first boot, but on next boot into recovery, it's back to stock.
I even manually renamed "/system/bin/install-recovery.sh" to "system/bin/install-recovery.bak", and "/system/etc/recovery-resource.dat" to "/system/etc/recovery-resource.bak".
Then I deleted all three files; TWRP still gets overwritten with stock recovery.
AFAIK these are all the files associated with creating stock recovery from the boot image, so not sure what else to try.
As it stands, the only way to use TWRP is to fastboot it from pc every time you want to use it.
Btw, I know I can just use a custom rom instead, so please don't provide that as a "solution" lol.
*Edit*
It seems that after deleting these three files and then reflashing TWRP solves the problem.
SuperSU still disappears after a data wipe, but with persistent TWRP, at least it can be reflashed without pc...
Click to expand...
Click to collapse
supersu will always disappear after a data wipe, unless you set it as a system app. and flashing twrp, then deleting that one file upon boot will fix twrp being deleted. and its been that way for years.
simms22 said:
supersu will always disappear after a data wipe, unless you set it as a system app. and flashing twrp, then deleting that one file upon boot will fix twrp being deleted. and its been that way for years.
Click to expand...
Click to collapse
I flash the supersu zip package with twrp rather than downloading from the play store, so supersu is a system app automatically and hasn't historically been erased during a data wipe.
I understand what you're saying though.
The approach you described would be necessary coming from an unrooted device with a stock recovery and no access to a pc, assuming the bootloader was already unlocked.
Hello everyone.
Last night I was trying to root my I8200L flashing the SuperSU with TWRP, so far so good. I installed Chainfire's SuperSU app.
When I opened the app, it said the binaries were outdated, and if I wanted to update them. I accepted ann the phone restarted in Recovery Mode (I'm using TWRP v2.7.0.1). Everything seemed fine, but when the installation finished, the phone rebooted and took me back to the TWRP screen. After a couple of tries I got into a slight desperation, and, without knowing much this recovery (so far always used CWM in my previous devices), decided to do a Wipe, but of course, as I don't know well how this recovery works, I went to Advanced Wipe and tittle all options (Dalvik Cache, System, Cache, Data, Internal Storage and Preload), thinking it would be like a Factory Reset.
Until now I realize that to make a Factory Reset you had to swipe just when you enter to the Wipe section, apparently I erased the entire system, but luckily I have a backup that was done before and also the Stock ROM downloaded from SamMobile.
The problem is, wanting to restore the system with the Restore option, I select the Backup, starts to restore the system, but when appears "Wiping Cache ..." in the console, continues for a few seconds and suddenly appears four purple TWRP screens, and the recovery reboots (I tried to launch the system, but only brings me back to TWRP).
The second thing I tried was flashing the Stock ROM from the Micro SD, but when I try the following appears:
Code:
Installing '/external_sd/I8200LUBUAOC1_I8200LUUBAOC1_ARO.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/I8200LUBUAOC1_I8200LUUBAOC1_ARO.zip'
Updating partiton details...
Finally, I thought the recovery has an error, so I tried to flash PhilzTouch Recovery and get the same thing:
Code:
Installing '/external_sd/PhilzTouch_recovery.tar.md5.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/PhilzTouch_recovery.tar.md5.zip'
Updating partiton details...
I can not access the Download Mode to flash the ROM from the PC via Odin, because when I try to enter (the Download Mode), just send me back to TWRP.
I don't know what to do, the phone is "locked up" in recovery mode. Hopefully someone can help me.
(Sorry for my bad english hope you can understand)รง
EDIT:
I could get into Download Mode and flash the Stock ROM, all done :good:
How?
After 3 years, now i'm passing the similar problem.
How did you acces recovery mode again, after recovery loop?
this is what i've done.
lenovo k3 note with twrp 2.8.7.2_K3_CUOCO92 and rom K3_LOLLIPOP_5.0_ROW_v1.12
i wanted to install one of the latest nougat rom. so i downloaded a twrp 3.1.1.1 made for the k3 note. i flashed the image from my old twrp and replaced choosing the RECOVERY partition.
Flashed ok, i tested a rom, AospExtended-v4.4-aio_otfp-20170708-1051- i flashed it and it worked.
OK BUT.............. i did not wipe the data partition because i received AN ERROR. the new nougat rom was ok but it was a superdirty flash with all the old apps that were crashing. what to do?
i enter into twrp, i REMEMBER that i had the data partition ENCRYPTED so i format it and after doing this i was able to do every wipe i want, included data.
OH PERFECT...... THIS IS WHAT I THOUGHT. i made a full wipe of the rom wiping 4 thinkg : data , internal storage, cache and dalvik cache.
reboot and BOOM. black screen. i press 3 or times the power button and the creen goes on... i am into twrp. from this moment i never returned to see my SYSTEM!
i tested other roms, same problem. i thought it was a twrp problem.... so i installed from the twrp an IMAGE of other twrp... i tested 2 or 3 other twrps specific for my phone k3 note.
I HAD LITTLE BENEFITS with another one.... just because when i press to reboot into system... the phone reboots into twrp AND I CAN SEE IT because the screen is ON, whilst with the "latest" twrp i found...... despites the flashing procedure was ALL CORRECT without errors, at the reboot i always entered into twrp...... BUT INTO A BLACK SCREEN MODE, like if the screen was on...touch enabled, but OFF backligt, and the only way to revive it it is to press power 2 or 3 times, to see the home of the twrp.
i've also found that on MOUNT.......... i always see SYSTEM unflagged, ok i flag it, reboot into system, actually reboot into twrp and system is UNflagged, i try the same thing ALSO flagging READ ONLY...... , idem reboot, twrp.
SEEMS THAT i cannot boot to system anymore. but..... if the twrp was fault, why for the first time let me flash the phone? i really entered into the nougat rom! i found all my old apps and files, but of course it was a DIRTY FLASH, i just wanted to make some wipes.....re flashi the rom.... but oddly i missed the possibility to return anymore to the system.
what could i do at the moment?
how to flash a original image? how to see if this recovery is ok? i donkt 'know where to find my answers......
ah last thing, while into the recovery i was always able to transfer files from pc to phone, but from minutes i am NO MORE ABLE to see the internal memory of the phone.
my computer does not see anything!!! so i am fukked i think....... i did not make anything different.
i only made a lot of wipes... a lot of flashing a lot of testin into recovery. i was able to see it from my pc and put new files through pc. now NO.
solved. i flashed with flash tools an old original firmware android 5.0, then i flased latest twrp with flashtool.... and then flashed the zip of a custom rom.
BL
if u have backup then restore ur stock version or reeboot??
Summary:
1. Flash factory image onto phone successfully
2. Install twrp and make a backup
3. Restore backup after reboot and I'm stuck in a bootloop
I have a new fi Moto x4 running Android 8.1 that I'm attempting to set up. I've reset this phone a bunch of times so here is the standards process:
1. Flash factory firmware as shown in this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I'm using: PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. After flashing, start up the phone and it works fine.
3. Reboot into the bootloader and boot to twrp using: fastboot boot twrp-3.2.3-1-payton.img
4. Copy in the twrp install file using: adb push twrp-installer-payton-3.2.3-1.zip /sdcard
5. Install the zip via the twrp Install function
6. Reboot the phone into the bootloader then start recovery
7. Use the twrp Backup function to create a backup of the Boot, Data and System partitions on Internal Storage (plenty of space).
8. Reboot the phone into the bootloader then start recover
9. Use the twrp Restore function to restore the backup. Finishes fine.
10. Reboot phone to system but the load won't finish. Phone just alternates between the Android One and the Motorola splash screens. Left it for an hour at one point just to be sure. No love.
Things I have tried:
1. Using twrp via fastboot boot and a hard install
2. Making backups to the internal and external memory cards
3. Changing the partitions in the backup
4. Wiping everything except the external sim card before performing a restore
If anyone has any thoughts I would love to here them.
Thank you!
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
I have the same problem as you are. After I finished install all applications, I made a backup with twrp-3.2.3-1-payton. Then next day I restore it from the backup, after finished backup, it goes to bootloop forever. My version is OPWS28.46.21.12, I download stock rom OPW28.46-13 but afraid to flash this rom since it is the lower version might be break the phone if not backward compatible. Then I search the web and found your message and follow this side fund a higher version of the stock rom OPWS28.46-21-14. I download it and flash it. After flashing complete and boot up, it saying new OTA update available, I don't want to update the rom since I want my phone rom version is same as the stock rom I have downloaded into my PC just in case in the future I accidentally doing something wrong I can flash back the stock rom without worrying the backward compatibility problem.
t-bob said:
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
Click to expand...
Click to collapse
I'm a bit slow on the response - but my first thought is manually flash stock rom over your restore without wiping data
I'm able flash the latest stock rom of FI_9.0_PPWS29.69-26-4 and reinstall twrp-3.2.3-1-payton. Then I restore data only that backup from previous rom, I get bootloop again after restore the data only from TWRP. The I reflash FI_9.0_PPWS29.69-26-4 again, install twrp and root it with Magisk. Restore data from cloud google drive automatically. And this time is successfully without bootloop.