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.
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
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
Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.
Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?
Hi,
I am looking how to fix my friend's Realme 8 5G (RMX3241) phone.
Here is the story:
1) My friend downgraded his firmware but by an accident installed ROM for India region, the result was he had no GSM signal on the phone (he lives in EU).
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
3) The phone booted, but no GSM.
What I did:
1) Managed to boot into recovery using "adb reboot recovery".
2) Then I pressed 'reboot' in recovery (I wanted to load a proper region ROM) and since then I am watching "realme" logo for like 10 minutes straight, so I assume it went into bootloop.
What I can do now:
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
2) Pressing vol up + power doesn't boot into recovery, just normally boots the system but it goes into bootloop.
3) The orange state is still there.
So assume I am now left with bootlooped system with no access to ADB.
Can anyone help me with this? Are there any solutions to this?
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Well, I have a solution for that.
It seems that the system is bricked, so you need to download a proper firmware version for your phone, and flash the stock ROM via fastboot (platform-tools) by erasing super and vbmeta partitions, and flashing every single IMG file of the firmware stock ROM.
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
Click to expand...
Click to collapse
Orange state is normal also as far as i know there is not a button combination to boot into recovery on this phone
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
Click to expand...
Click to collapse
This is fastboot mode and you have to use fastboot which is bundled with adb, in this state you can: unlock bootloader, flash partitions or you can reboot to recovery
Taracair said:
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Click to expand...
Click to collapse
SP_Flash_Tool_v5.2124 works for me
You have to:
Have proper VCOM MTK drivers installed
Boot the phone by pressing vol up + vol down while connected to pc via usb
Use MTKAuthBypass v7 before flashing in order to bypass auth protection system.
UPDATE:
mtkclient it's perfect and on the github everything is explained on how to use it