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
Related
it just vibes 3 times and nothing? I can get into Rom Manager recovery but why can't I using regular method???
Rooted today using unrevoked....then load Rom manager 3.0.0.8 made recovery from that and now I can't even boot in the Vol up or down + power?
If you pressed vol + and pwr you put it into debug mode. Pull the battery and then do vol - and pwr, it should boot into the bootloader.
Same issue as the O.P.
I press PWR+VOL DOWN and get it to the screen that shows hboot, recovery, fastboot, etc.... BUT I can't access Recovery AT ALL. The VOL UP & VOL DOWN keys do absolutely nothing.
Any and all help is appreciated.
Thanks.
Found the fix... had to remove the p5 img from the sdcard that was used to root the HTC TB. If you don't remove it, the phone automatically tries to load it.
I'm having this problem too only I can't boot into my phone at all. I loaded nerozehl's latest kernel and can't get back into my phone. It just comes up saying "Process system is not responding." I have the radio on the root of the sdcard but don't know of any way of getting it off.
Any suggestions?
EDIT: And I just remembered that I could do adb reboot recovery. Whoops...
Last night I started my Phone in recovery mode and strangely it was taking a long time to move from Fastboot window to TWRP recovery window. When it reached the recovery window it just hung up (below video)
What did I do to get it working back again?
Held the power button expecting the phone to switch off - It did no good. Kept on blinking.
Left the phone as is so that it drains the battery.
When the battery drained connected the charger and restarted the phone in Fastboot mode (Power+Volume Down). Phone booted successfully.
Navigated to the TWRP Website and downloaded the latest Version TWRP 2.8.5.0 for M8.
Connected the phone to the laptop and ran the command fastboot flash recovery twrp-2.8.5.0-m8.img - Recovery installed successfully :angel:
The phone rebooted back in recovery without and issues. :victory:
Thank You
It's already known that you need the latest version of TWRP if you update your bootloader otherwise it won't load
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 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
Hi,
I have a global variant of S20 with Exynos chipset running rooted stock Android 10 with G980FXXS2ATE7 firmware.
Root was done with Magisk and it was properly working.
I installed a Magisk extension that caused the initial boot loop, but Recovery and Download mode was working. I was trying to install TWRP but that failed to load with some DTBO related problems. So I restored the stock recovery for Android 10 and then choose to flash the Android 11 version of dtbo alone without any additional files from that package, because I was hoping that it would make TWRP work. So I have a combination of stock files for Android 10 + corresponding rooted bootloader and stock recovery + Android 11 version of DTBO.
This was a big mistake, as since the device is rebooting every 30 sec. It only shows that the bootloader was unlocked and afterwards the "Samsung Galaxy S20 secured by Knox" screen. It stays here for a while and then reboots automatically.
Download mode and recovery are inaccessible. They simply do not appear, not with any key combination via which they worked earlier.
If I plug the phone into my laptop, there is absolutely no USB traffic, it is not recognized as a device.
Odin does not see the device either (as there is no USB device recognized by the OS).
The only thing I can do else is if I hold the Vol down + power button for a while and then plug in the charger when the screen goes dark, then the charging logo appears without showing the percentage of the battery. I stays there even if the unplug the charger. When touching the buttons, it goes back to the boot loop.
I have not found a way to power down the phone, even pressing and holding any combination of Vol up, Vol down and Power buttons.
I think the problem is that neither Recover nor Download mode can boot and this is because of the wrong DTBO file that I flashed.
Do you have any idea how I could repair and reflash the working DTBO file matching the firmware on the device under these circumstances?
Is there any trick for Exynos to boot from the SD Card like there is something for Qualcomm based phones?
Or any other way via which I could trigger some activity on USB?
Thanks for any suggestion
Try launching fastboot devices while holding fastboot keys.
Thanks for the suggestion!
I solved the problem finally.
It is strange, but recovery and download mode started to work with the hardware buttons after I removed the SD Card from the phone. I do not know how this is related, but afterwards I could flash with Odin and after reflashing the original firmware and the the usual vbmeta zip, the phone booted up properly.
Afterwards, I could reflash the magisk patched bootloader and regained root access as well.