My phone is suffering from the bootloop. I don't want to flash the modified boot image yet. I've tried booting several modified boot images over USB using
Code:
fastboot boot boot.img
but they all get stuck at the boot animation. TWRP otherwise works.
Do I have to flash these modified boot images in order for them to work? Or can I boot them using fastboot?
Related
I unlocked my phone's bootloader and immediately flashed TWRP using Google's fastboot after that. I got a size mismatch warning in the fastboot screen but I assumed it was normal. I was planning on installing CM, but the system partition remained empty after "flashing" both the ROM and the GAPPS, even though there were no read/write errors in the recovery's log. As a result, the phone keeps booting into recovery, and the same thing happens with CWM. It's like the recovery thinks it is modifying the system partition but it in reality it is not. Maybe it has to do something with SELinux? Any ideas on how to fix this?
Update: I am able to flash stock and boot into it normally, but trying to flash anything in TWRP (even just SuperSU) will make the phone boot into recovery when turned on or rebooted normally.
Update: Flashing the stock boot.img in mfastboot after flashing anything in TWRP will make the phone boot into the system normally, but this workaround doesn't apply to CM12 installs, as it gets caught in a never-ending boot animation (at least more than 10 minutes), with what appears to be a moving/flickering line on screen (which has been reported before). My suspicion is that somehow the recovery is making a change to the boot partition when it shouldn't. SuperSU can be installed using this workaround, but not CM12.
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
DanielEGVi said:
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
Click to expand...
Click to collapse
Hi,
Running the following command in fastboot should fix the problem.
Code:
fastboot oem fb_mode_clear
I recently tried to install multirom but it kinda messed up, Now I can't either do fastboot boot recovery.img or fastboot flash recovery.img cause none of them works. I also tried to recover stock firmware but it didn't help. any help is appreciated.
I can boot into stock recovery via fastboot boot recovery.img but cannot boot a twrp or cwm.
So I just flashed TWRP to my device but whenever I try to boot into the recovery the screen just hangs. Booting into the regular UI (homescreen) works, the device just doesn't seem to want to work with the custom recovery. TWRP is originally unsupported for my device, I had TWRP built for me by someone from the TWRP builder app. My devices partition format is emmc, and has some kind of recovery.fstab file. I used
Code:
fastboot boot recovery.img
to flash the recovery, because
Code:
fastboot flash recovery recovery.img
didn't work. Can anybody tell me what went wrong and how to fix it?
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool
Just flash this boot image either screen your on. Also a app to flash or save img files while booted in a OS.
fastboot flash boot boot-v9-root24.img.
Or from recovery or by the app.
Also you can flash either boot slot by
Changing the
Fastboot flash boot_a or boot_b then boot-v9-root24.img..
I dual boot so I tried alot of OS12 and 11s out with this file. One this is the kernel is not stock but flash it to what ever you want. Stock kernels are now missing features I use and twrp becomes unstable. Dora kernel is a goodie.