Develop Bugs

Trying to install TWRP but the phone keeps overwriting it

Trying to install TWRP v3. Phone is unlocked (not rooted yet as not necessary atm). I'm able to sucesfully push the .img to the sdcard via adb and install via "fastboot flash recover twrp.img" but the moment I reboot the phone and try to access recovery to get into TWRP, all I get is a little icon of an android mascot lying down with his belly open. No TWRP.
I know the phone will auto-overwrite custom recovery's if the correct combination of hardware buttons are not pressed after the first TWRP install (as TWRP needs to patch the default recovery the first time to stop the phone from constantly trying to overwrite TWRP every time) but so far i've not been able to find out what it is (i.e. not the usual vol +- and power all at the same time. Its gotta be something else?).
Edit: Delete his post. I figured it out. Turns out it isn't a good idea to execute "fastboot reboot" immediately after TWRP installation

Don't restart the Phone!
Flash Recovery and the do the following:
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

RIP Phone

So basically I was trying to get OmniRom set up, and here's what I did:
(was on beta 108 btw)
Unlock the bootloader (worked!)
Then the phone rebooted by itself, and I saw a glimpse of "encrypting phone..."
I turned on USB debugging, then I authed the phone and rebooted into fastboot once again.
Flashed recovery, worked, and then was greeted by "Enter your encryption password" in TWRP.
Clicked the back key, then wiped data (normal settings). Later I mounted usb. Saw that there was nothing in phone, but for some reason, TWRP Files showed that there were.
So I turned off my phone, and I can't get it past the black boot up screen. Can't even turn off the phone.
Help is greatly appreciated. Thanks!

Can you get to twrp? if yes, mount mtp n copy rom n flash.
try various combinations to reboot. All 3 buttons etc for 10plus sec or 2 button combos.
Or let it drain the battery down and boot to twrp after connecting to charger.
long press power button then along with vol down on power down for fastboot... recovery.

sorry double-post.

lolrepeatlol said:
So basically I was trying to get OmniRom set up, and here's what I did:
(was on beta 108 btw)
Unlock the bootloader (worked!)
Then the phone rebooted by itself, and I saw a glimpse of "encrypting phone..."
I turned on USB debugging, then I authed the phone and rebooted into fastboot once again.
Flashed recovery, worked, and then was greeted by "Enter your encryption password" in TWRP.
Clicked the back key, then wiped data (normal settings). Later I mounted usb. Saw that there was nothing in phone, but for some reason, TWRP Files showed that there were.
So I turned off my phone, and I can't get it past the black boot up screen. Can't even turn off the phone.
Help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
hold volume down and power button for up to 15 seconds and you should reach fast-boot mode. Once in fast-boot mode flash the stock ROM using the latest Stock Tool provided by razer https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/ or if you choose to keep TWRP and use stock OS without trouble I recommend @crians new flash-able stock ROM: https://forum.xda-developers.com/ne...tbit-robin-ether-flashable-stock-rom-t3627060
For omni ROM (once in TWRP)
1. Hit advanced wipe in TWRP and wipe everything it lists.
2. Back out and go to format data and type yes.
3. Plug phone into pc and transfer G-Apps and ROM.zip
4. Flash ROM and G-Apps then reboot

refurbed and still bootlooping

LG refurb updated the ROM to 20x, and (supposedly) replaced MB & RF.
Now I can't get into bootloader, with either ADB or power/vol down combo. Bootloops instead and takes 15 mins to become a working phone again.
I've factory reset 2x today.
Perhaps factory reset and don't restore from Google?
Perhaps 20x is corrupt?
I have no idea what to do next other than deal with the apparent idiots at LG Texas. This is the 2nd "refurb" in a month and 3rd since I've had the G4.
HTC M7 is saving my sanity as backup.

finally got out of bootloop. OEM unlock was the issue in Developer options.
But now having problem getting it to boot into twrp.
fastboot flash recovery twrp.img - went ok, as per past experience.
but - fastboot boot twrp.img - is a no go.
I get this back - cannot load 'twrp.img': No such file or directory.
Can't power down with power button held for 10secs.
Only fastboot reboot works.

What happens if you try to boot into recovery with the key combo (power and vol down until lg logo appears, then release power briefly whilst still holding vol down and then press power again whilst still holding vol down - should bring you to "factory reset page" but once factory reset is confirmed should go to TWRP)

nope, goes to factory reset. tried that twice.

Ok so even after you have flashed twrp, when you enter that factory reset page and click yes twice, it actually factory resets it (that screen is there for everyone but it normally goes to twrp afterwards). Did you boot into your phones OS inbetween flashing twrp and booting to it? LG software replaces twrp with stock recovery if you don't patch the os.
The way to permanently install twrp is:
1) reboot to bootloader and perform "fastboot flash recovery twrp.img"
2) fastboot reboot
3) AS SOON AS IT REBOOTS (<-- that is important) - use key combo and click yes twice - do NOT let it boot back into the main android system inbetween, or you will need to start again

k, I'll give that a go tonite after work. Don't recall the issue with the earlier OS, 20v (before "refurb"), but I'll do oit.

What model of phone is it?
In terms of flashing twrp, that has always been the process (I have a G4 on v20g firmware and it took me a while to work out why twrp kept being wiped)

it's a G40 w/20x. Never had this issue before 20x.
still actually having an issue on reboot. Takes about 7 mins now as it optimizes 1 unknown app.

used this method from fastboot:
fastboot boot twrp.img and pointed (d&d) to twrp on my drive.
then installed twrp from memory as described on twrp page/Fastboot Installation Method.
Ding Ding Ding!
thanks.

Possible fix for Pixel XL Bootloop Issue

I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.