Database Develop

Recovery problems with TWRP 2.8

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?

Can't install TWRP on S3 mini (GT-i8190N)

Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?

Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.

adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...

Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.

ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now

Okay happy to hear that everything is fine now. Happy playing with custom roms

Stock Recovery

Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help

EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.

Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?

Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...

always booting into TWRP, unable to enter into system. (solved!)

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??

Fastboot loop

Think i have rally buggered up and update, was going to try out the havoc rom, when i went to flash it i was told i needed to update vendor to v12 so i flashed the official miui vendor v12 rom, rebooted and now im stuck in a fastboot loop. i think my mistake was following the instructions on the havoc rom and wiping system, data, dalvik and cache without the havoc rom flashed.

this worked for me:
from https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
Full credits to @ SivSomRao (telegram handle, since no xda)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery[/QUOTE]
I was OverJoyed when this worked. However, every time I entered recovery, I was met with the fastboot logo again, Therefore, I just repeated the process I did when I first unlocked my bootloader via twrp in the tutorial above, which was, I went to manage partitions and formatted my data, wiped my rom, and did the same steps as in the tutorial when I first got my orange fox.
Now use twrp interface, copy orangefox.zip to my phone via PC, then flash that zip. Then go to settings > manage partitions > data > format data > type 'yes'. Then quickly flash a vendor, then a flash ROM (normal clean flash, tutorial given above) and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right so I tried LR-twrp (it's in Chinese, but I can change the language to English) . PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did. .
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.

The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.

Robbo.5000 said:
The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.
Click to expand...
Click to collapse
Thank you for this type of answer. I was trying use all the instructions to wipe, but all the time I got brick (fastboot loop) in my Mi 9 SE. Not problem when usign the first page of the wipe.