Develop Bugs

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.

Updated phone, hung and can't power off

I was running stock Marshmallow rooted and updated to the official Nougat stock. After restarting I then ran fastboot flash recovery and installed TWRP 3.1.0-0. After doing so I booted to recovery using the "fastboot boot twrp-3.1.0-0-ether.img" and the phone rebooted to TWRP. So far so good, I exited TWRP and the phone restarted to the warning screen:
"Your device has been unlocked..." and it's now been sitting at that screen for over 20 minutes. The phone doesn't show up as a fastboot or ADB device, but it does show up in windows device manager. I've held the power button down for over 2 minutes and it won't power off, it doesn't respond to volume buttons.
Steps:
1. Updated rooted stock Marshmallow with official Nougat Image downloaded from forums
2. Reboot and flash TWRP 3.1
3. Boot to TWRP (Made no changes)
4. Reboot phone
5. Completely unresponsive, but still powered on
Did I brick my phone? Is there a way to force it to restart or power off?

Update: Eventually I started mashing buttons, holding down Vol - and Power would allow the device to power off. Then I could turn it on while holding Power and Vol +. This allowed me to get into Fastboot. I tried just flashing the recovery image from the Nougat update, but that didn't fix it so I reflashed the entire Nougat image using the Flash-All.bat that came with it and that appears to have fixed it.
Sorry for panicking, carry on

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

Phone not turning on anymore from TWRP install

I had a stable running device with Magisk and TWRP. Yesterday evening I successfully updated to the latest OxygenOS 5.0.3. The update as expected and as usual restored the stock recovery so this morning I downloaded the latest TWRP .img, went with the usual routine of enabling USB debugging, rebooted to fastboot and flashed the TWRP recovery.
The phone rebooted and I forgot to do the combo to immediately enter TWRP to patch the boot image and avoid the stock recovery being rewritten. So during the oneplus boot animation I forced a shutdown by holding the power button, re went to fastboot and re flashed TWRP, then I tried to reboot with the combo to enter recovery and here starts the issue.
The phone shutdown and never turned on. Also attaching it to the charger doesn't show the usual charging animation. I've read the Mega unbrick guide but holding the Volume Up doesn't show my device on the pc so I can't proceed with any of the suggested methods.

Maxiride said:
I had a stable running device with Magisk and TWRP. Yesterday evening I successfully updated to the latest OxygenOS 5.0.3. The update as expected and as usual restored the stock recovery so this morning I downloaded the latest TWRP .img, went with the usual routine of enabling USB debugging, rebooted to fastboot and flashed the TWRP recovery.
The phone rebooted and I forgot to do the combo to immediately enter TWRP to patch the boot image and avoid the stock recovery being rewritten. So during the oneplus boot animation I forced a shutdown by holding the power button, re went to fastboot and re flashed TWRP, then I tried to reboot with the combo to enter recovery and here starts the issue.
The phone shutdown and never turned on. Also attaching it to the charger doesn't show the usual charging animation. I've read the Mega unbrick guide but holding the Volume Up doesn't show my device on the pc so I can't proceed with any of the suggested methods.
Click to expand...
Click to collapse
Try holding down the power button for >40 sec and if the phone powers on, reflash OS, TWRP and Magisk before booting again.
If not successful, hold down the power+vol up/down buttons for >40 sec and see if it powers on.
If all else fail, disable signature verification in your PC, install the OnePlus drivers and try to connect.

Hold volume down and connect to the pc download the unbrick tool and start it

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.