bootloop, adb disabled, fastboot enabled; launch recovery? - Xperia Z3 Compact Q&A, Help & Troubleshooting

tl;dr:
Version: D5803 with SliMM ROM, latest + Xposed +TWRP (maybe not TWRP anymore?)
Problem: bootloop at 2nd boot logo (1st Sony, 2nd Android)
Cause: Xposed Modul installed causig bootloop
Try: Get into recovery to deactivate Xposed via "touch /data/data/de.robv.android.xposed.installer/conf/disabled"
State: recovery not accessible, ADB probably disabled (crashed last time I clicked on developer options), fastboot accessible, locked bootloader
Hi, I have a problem I'm not able to solve by myself. After I installed an Xposed Module, my phone is at boot loop. So I wanted to go to the recovery and deactivate Xposed. But the recovery seems not to be accessible: The LED doesnt go green, so that I can push volume up/down. ADB seems to be disabled in developer options, because it crashed last time I clicked on developer options before the whole error occured. My bootloader is locked, so I'm not quite sure what to do, when accessing fastboot.
I tried fastboot boot twrp.img and to intall it, but - probably of the locked bootloader - an error appears.
So, what can I do to resolve my problem? Any ideas? Unlocking the bootloader without starting the phone?
thanks!
Tray

traydare said:
tl;dr:
Version: D5803 with SliMM ROM, latest + Xposed +TWRP (maybe not TWRP anymore?)
Problem: bootloop at 2nd boot logo (1st Sony, 2nd Android)
Cause: Xposed Modul installed causig bootloop
Try: Get into recovery to deactivate Xposed via "touch /data/data/de.robv.android.xposed.installer/conf/disabled"
State: recovery not accessible, ADB probably disabled (crashed last time I clicked on developer options), fastboot accessible, locked bootloader
Hi, I have a problem I'm not able to solve by myself. After I installed an Xposed Module, my phone is at boot loop. So I wanted to go to the recovery and deactivate Xposed. But the recovery seems not to be accessible: The LED doesnt go green, so that I can push volume up/down. ADB seems to be disabled in developer options, because it crashed last time I clicked on developer options before the whole error occured. My bootloader is locked, so I'm not quite sure what to do, when accessing fastboot.
I tried fastboot boot twrp.img and to intall it, but - probably of the locked bootloader - an error appears.
So, what can I do to resolve my problem? Any ideas? Unlocking the bootloader without starting the phone?
thanks!
Tray
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock ROM but you can also try this:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336

Dinkec27 said:
The only thing I can think of is to reflash the stock ROM but you can also try this:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
Thanks, didn't think of that. When I press a hardware button 5 times the vibration feedback is there, but the phone still gets stuck at the Android boot logo.
Which way do you mean to reflash the stock ROM?

traydare said:
Thanks, didn't think of that. When I press a hardware button 5 times the vibration feedback is there, but the phone still gets stuck at the Android boot logo.
Which way do you mean to reflash the stock ROM?
Click to expand...
Click to collapse
I mean through Flashtool,there are many guides on XDA,but it does wipe all of the data

Dinkec27 said:
I mean through Flashtool,there are many guides on XDA,but it does wipe all of the data
Click to expand...
Click to collapse
Thanks so far - I decided to reflash Stock. Worked.

Related

[Q] Moto X stuck in a boot loop

Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.
Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode
Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!

unable to enter recovery mode

ok this is something very strange, and i'm in a hurry right now. first of all, yes, i installed adb and fastboot mode is enable, yes i'm able to connect to adb (through wireless tho, i don't know what's happening with this stupid xperia), i'm able to connect to fastboot mode when connecting usb and pressing volume up, yes, phone is rooted, yes i know how to enter recovery mode by hardware, that means power button + volumen button a few times (i've done this years ago with this same phone), it should go into recovery mode (different from safe mode), and yet once again, unable to go recovery mode, i'm scared right now, i really don't know what is happening to this phone, i have tried absolutely everything i had on hand and searched every solution possible, yet here i am, desperated to seek for a solution :crying:
edit: i forgot to mention i know how to enter recovery mode from command shell, going through adb and typing adb reboot recovery, but is just passing by and jumping that process and going directly to desktop :'( please help
Maybe recovery somehow deleted from your phone so Try to reinstall the recovery again.This sometime happen if your phone bootloader is locked.
Røbin said:
Maybe recovery somehow deleted from your phone so Try to reinstall the recovery again.This sometime happen if your phone bootloader is locked.
Click to expand...
Click to collapse
and how the hell i reinstall the recovery mode? is that even possible? oh by the way, this is an official rom, not a custom rom, i'm trying to install a custom rom, but without the recovery mode i'm unable to do so :crying:
ps:bootloader is unlocked
NDSA said:
and how the hell i reinstall the recovery mode? is that even possible? oh by the way, this is an official rom, not a custom rom, i'm trying to install a custom rom, but without the recovery mode i'm unable to do so :crying:
ps:bootloader is unlocked
Click to expand...
Click to collapse
Use this XZR recovery installer to install recovery in your phone(need computer).Or use flashify or any other flashing tool from Google play store and download this TWRP 3.0.2 stock recovery img to flash if your phone bootloader is unlocked.
thank you so much, you saved my life dude is not exactly the original recovery mode, but is something :laugh:

Bricked after installing twrp, any ideas?

Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.

Nokia 8 hangs on boot

Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.

Question Redmi Note 10 Pro Bootloop

Using crDroid 7.16 (Android 11) and TWRP 3.6.1_11 (twrp-3.6.1_11-0-sweet), unlocked of course, and rooted with Magisk v25.1, the phone suddenly entered a boot loop.
It will show the Redmi logo, then the CrDroid boot sequence, and then restart.
It is NOT possible to enter recovery, it will show the TWRP screen, and then just do nothing (not even reboot)
It is NOT possible to turn it off, it will just reboot no matter how long the power button is pressed
It IS possible to enter Fastboot
I have tried removing the SIM, no changes. Tried fastboot commands, to boot directly into TWRP (3.6.1, and 3.6.2) or flash a new TWRP - nothing works. Still bootloop, still can't turn it off, still not possible to go into TWRP.
Hoping for any ideas, I'm clueless.
J.PG said:
Using crDroid 7.16 (Android 11) and TWRP 3.6.1_11 (twrp-3.6.1_11-0-sweet), unlocked of course, and rooted with Magisk v25.1, the phone suddenly entered a boot loop.
It will show the Redmi logo, then the CrDroid boot sequence, and then restart.
It is NOT possible to enter recovery, it will show the TWRP screen, and then just do nothing (not even reboot)
It is NOT possible to turn it off, it will just reboot no matter how long the power button is pressed
It IS possible to enter Fastboot
I have tried removing the SIM, no changes. Tried fastboot commands, to boot directly into TWRP (3.6.1, and 3.6.2) or flash a new TWRP - nothing works. Still bootloop, still can't turn it off, still not possible to go into TWRP.
Hoping for any ideas, I'm clueless.
Click to expand...
Click to collapse
Try to flash newest orange fox recovery 12.1 or TWRP via PC again and reboot in it via hardware keys. Then format data with yes and reboot recovery. Flash ROM . Reboot system. Flash magisk after first Boot.
Laptapper said:
Try to flash newest orange fox recovery 12.1 or TWRP via PC again and reboot in it via hardware keys. Then format data with yes and reboot recovery. Flash ROM . Reboot system. Flash magisk after first Boot.
Click to expand...
Click to collapse
Thank you - tried it with Orangefox, directly booting and flashing, but the same issue as with TWRP - it shows the logo screen, and then just stops and does nothing for at least a few minutes.
I feel like the phone is having trouble decrypting or even accessing any of the data?
At this point I think there might not be a way to fix it without losing any data?
And even full wiping and flashing a stock ROM seems difficult, since I can't access recovery at all.
J.PG said:
Thank you - tried it with Orangefox, directly booting and flashing, but the same issue as with TWRP - it shows the logo screen, and then just stops and does nothing for at least a few minutes.
I feel like the phone is having trouble decrypting or even accessing any of the data?
At this point I think there might not be a way to fix it without losing any data?
And even full wiping and flashing a stock ROM seems difficult, since I can't access recovery at all.
Click to expand...
Click to collapse
I've told you to format data with yes. No other way.
Of course you loose every data
just encourage yourself until you execute
fastboot -w
Laptapper said:
I've told you to format data with yes. No other way.
Of course you loose every data
Click to expand...
Click to collapse
Alright. The problem is, that I can't get into the recovery, not with booting into it directly from fastboot, or flashing any other TWRP or Orangefox version and using hardware keys. It just won't load.
So seems like "fastboot -w" is the best option.

Categories

Resources