(Not a Q&A) While doing some stuff to my phone I messed something up. My phone boots to TWRP instead of the system. I have to boot my phone into bootloader to boot the system. How do I fix this?
Related
Hello XDA Developers
I fear I am currently in a state of denial, but I still hope you fine folks can help me (even if it's only to get to the final state of grief... acceptance)
My problem in a nutshell:
- system image is fine
- recovery image is broken
- device is stuck in a recovery bootloop
- apx is working but i have no NvFlash backup image available
Here's what happened:
1. I have accidentally flashed the wrong version of TWRP (JB instead of ICS, even though i still have the 9.4.2.21 Bootloader) with fastboot.
(reason for this was because i kept getting the stupid boot loop with CWM that you can fix with)
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
2. The device booted fine after the flashing process but i could (for now obvious reasons) not enter recovery mode, so I booted all the way, powered down the device and selected restart -> recovery
Now i am in what appears to be the good old boot loop:
The prime wants to boot up recovery, fails, reboots.
Holding vol-Down does not give me the option to start fastboot - it just states the Bootloader Version and says "Bootin recovery kernel image"
Holding Vol-Up brings me to APX and NVFlash should work, but i cannot for the life of me find my blob.img - i think it is still on my internal sd card. :crying:
Is there any hope left for me? Is there any method i am unaware of to skip the recovery boot or at least get to fastboot?
This just feels so unreal because the working system is "right there" hidden behind the recovery partition, i just cannot get to it because i'm stuck in the blasted bootloop again.
Thanks a bunch
Christoph
I'm not an expert in Android, nor am I an expert with computers, just an average joe in the Android world. Since the time I got myself into this community I never stopped learning something small. I was able to root my phone, install custom firmwares, unroot my device, do a NANDroid back up. All of this done with the help I got from an online source. Now, I'm looking forward to do further tweaks in my device's system. It might sound risky, but I'm enticed by how far an android device can be further improved. But before I do any of this, I'd like to know the appropriate steps to do when something goes wrong like what if device ends up on boot loop.
Questions:
1) What is boot loop?
2) What causes boot loop?
3) Is it the same with a bricked phone?
4) Can the phone be recovered from it (boot loop / brick)?
5) What should be done when a phone is on boot loop?
I humbly ask everone to share a bit of your knowledge about this.
Thank you.
1 - Is kinda of obvious. Bootloop is when your device is stuck at some of bootscreens (model screen, Samsung logo screen) and it doesn't boot properly. Even if you remove the battery and insert it again to turn it on, it doesn't turn on.
2 - There are various reasons: incompatible kernel, incompatible rom, edits on build.prop, rom poorly flashed. And, for our device, if you try to reboot into recovery directly and it has CWM installed, it may enter on recovery bootloop.
3 - I''d say it is a "soft bricked phone". If you has access to recovery or download mode, congrats, you can undo the mess. But if you can't, you got a hard brick. So, it will need repairs.
4 - As I said before, if you has access to recovery or download mode, it is possible to recover it.
5 - It depends. First I would undo my last actions. If I don't have success, I would reflash stock rom, it's almost guaranteed.
So, it happened to my phone when I attempted to do a "Recovery Back Up" using "[ROOT] Rashr" app. I had a Recovery Boot Loop, which boots only into Recovery Mode. But it's fixed now. Here's the thread: http://forum.xda-developers.com/grand-quattro/help/s-o-s-device-boots-cwm-t2981980
This is a reference for those who have the same problem.
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Arsalanzahoor said:
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Click to expand...
Click to collapse
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Arsalanzahoor said:
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Click to expand...
Click to collapse
Glad you got your phone working--your persistence paid off.
Be sure to make a backup before flashing other ROM's.
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode. I can use a command to delete all my data. As they're Magisk modules, clearing the data might not unbrick my phone (I'm not sure).
Is there any way I can reboot my phone into TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
SGoraiCS said:
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode.
As they're Magisk modules, clearing the data might not save my phone. My phone's not going to turn on (I'm not sure).
Is there any way I can reboot my phone to TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
Click to expand...
Click to collapse
Two Methods.
1- Some phones actually respond to fastboot reboot recovery. This is quite natural given adb reboot recovery, but unfortunately is non-standard. I found lots of people suggesting this method so I offer it here in the hopes that it works for some, but it didn't for me.
2- Some phones will actually let you book into an image via fastboot without flashing it. This will allow you to load a recovery image without needing to reboot the phone at all. You need a copy of the recovery image on your computer, but running fastboot boot image.img should do the trick. I was able to load up TWRP using this method.
Sent from my Pixel 3 XL using Tapatalk
Hello,
short background story:
I have a KIW-L21 which is running Android 7.0.1 Resurrection Remix CustomROM. Recently, my battery and power button died, so when I plugged in the phone to charge it, it would immediately power-cycle (button defective and constrantly forced the phone to reboot).
I got both replaced by now, but the phone does not boot anymore (I guess due to the continuous power-cycling maybe some files got corrupted). It will show up the initial RR logo and then the boot animation, but it will not get past that anymore. I haven't flashed or changed anything on the phone for ages.
Bootloader is unlocked and TWRP 3.4.0-0 is installed. I can access the bootloader, TWRP and even the eRecovery by physical button combinations.
Before loading a backup, I'd like to know if there's anything I can try in order to get the phone back running (something similar to chdsk on Windows or the like )?
dmesg.log and recovery.log attached, in case this is of any use. What I can see is that the time and date is totally ****ed up, I highly doubt this would prevent the phone from booting though.....
If nothing else helps and I have to restore a backup, which partitions exactly should I restore? Only boot, data and system as described on the TWRP FAQ? Does it really hurt if I restore further partitions? After all, they're created using TWRP on my own phone, not downloaded somewhere.
Thanks in advance