Every time a new image comes out I wipe the device and flash the new release image using the flash-all.bat. However, this time I'm running into the issue of just trying to install Magisk beta 15.2 because it won't let the device boot. I've tried two methods:
Without Installing TWRP
1.) Wipe phone (factory data reset), flash-all.bat, and set-up device to get pin and fingerprint setup
2.) Reboot to fastboot and fastboot flash boot twrp-3.2.1-0-marlin.img
3.) Boot from fastboot screen into recovery and flash Magisk beta 15.2 (1520)
4.) Reboot to system and won't pass G logo
Installing TWRP
1.) Wipe phone (factory data reset), flash-all.bat, and set-up device to get pin and fingerprint setup
2.) Reboot to fastboot and fastboot flash boot twrp-3.2.1-0-marlin.img
3.) Boot from fastboot screen into recovery and flash TWRP-installer-3.2.1-0.zip
4.) Reboot to full TWRP recovery
5.) Flash Magisk 15.2 (1520)
6.) Reboot to system and will not boot past G Logo
The only thing I am trying to accomplish is get Magisk working with the stock kernel; I don't care if TWRP is installed or not. Someone else has to have tried this or has to have seen this issue because nothing I do short of restoring stock boot will allow it to boot up. Anyone have this issue and know how to get around it using the Jan 18 software?
i think the problem is that you're flashing the twrp image with fastboot instead of booting it. in #2 for either method that you tried, you ran fastboot flash boot twrp-3.2.1-0-marlin.img. try it without the word flash. fastboot flash boot twrp-3.2.1-0-marlin.img. the twrp web page for the pixel xl recommends this as the way to initially run twrp. fastboot flash boot changes the boot image. fastboot boot doesn't. when you flash the magisk zip or twrp zip from recovery, they're expecting the stock boot image. but since you ran fastboot flash boot, the boot image was modified and no longer stock. that's about all i understand about the pixel's partitioning and the boot image. there are others who can explain it better than me.
altwu said:
i think the problem is that you're flashing the twrp image with fastboot instead of booting it. in #2 for either method that you tried, you ran fastboot flash boot twrp-3.2.1-0-marlin.img. try it without the word flash. fastboot flash boot twrp-3.2.1-0-marlin.img. the twrp web page for the pixel xl recommends this as the way to initially run twrp. fastboot flash boot changes the boot image. fastboot boot doesn't. when you flash the magisk zip or twrp zip from recovery, they're expecting the stock boot image. but since you ran fastboot flash boot, the boot image was modified and no longer stock. that's about all i understand about the pixel's partitioning and the boot image. there are others who can explain it better than me.
Click to expand...
Click to collapse
I definitely missed that and I actually know exactly what you mean by not using the "flash" term. I'm going to give this another shot, thank you for pointing out my mistake I definitely see the issue now. :good:
Edit: That was exactly it. Booting directly to twrp fixed my issue because I was modifying my boot partition every time I flashed twrp. My own worst enemy. Thanks for helping me out @altwu
no problem. glad to hear that you're up and running.
Related
I recently bought an Oneplus 3 and wanted to root it, I succesfully unlocked my bootloader but when I try to flash TWRP and then load into the recovery mode the phone shows the oneplus logo for a few seconds and then turns itself off (even though ADB said it was succesfully flashed), when I reboot and go into recovery in brings me to the stock recovery.
Does anyone know how to fix this?
EDIT:
I previously had TWRP running on my Oneplus 3, at the first boot of TWRP I selected 'Read Only' because I saw that in a video, I couldn't flash a certain rom thats why I tought I had to update my TWRP, does this have something to do with it?
Anyone?
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Stock
krabman said:
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Click to expand...
Click to collapse
Can this be apply on other devices? Because I am having the same problem
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
This is universal: After flashing OEM ROM, don't boot into system. Boot into recovery, you will get into TWRP and from there boot into system. Or after flashing OEM ROM, flash Magisk and then boot into system.
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
Yeah, what he said. You can reboot recovery from TWRP and TWRP will patch it or you can flash magisk and it will do the work. What you can't do is flash TWRP and then boot directly to system because the stock recovery will be restored. Realistically do both, reboot recovery and then flash magisk for the win. I congratulate you on searching BTW, this thread is more than 2 years old. You may want to consider perusing the appropriate section for your other device. If it's a newer device with AB you will have some specific procedures to follow relating to that.
I apologize if this is the wrong place to ask, but when I try to boot my phone (Mi 6) normally I end up seeing TWRP's OpenRecoveryScript running briefly before the phone shuts off and boots again. My phone started doing this last night without any apparent prompt while I had it charging and plugged into my computer. I think it might be because of the MIUI update I installed earlier that day. I can still boot the phone into the TWRP recovery screen with all its options, and into fastboot, but I can't boot it normally. How can I fix this without encrypting/deleting or otherwise messing up the data currently on my phone?
I was able to fix this problem by downloading the stock recovery .img file posted in this thread ( en.miui.com/thread-639221-1-1.html ) and flashing the recovery section using TWRP. I hope whatever caused my problem is fixed in future updates of TWRP.
If you want a advice, no worry about use TWRP for root or any other feature you can need, but don't flash it, only boot it. If you replace the Recovery, you will have problem with otas and other stuff. Instead:
fastboot flash recovery twrp.img
use
fastboot boot recovery twrp.img
Yes, you must use it everytime you want enter on twrp, but it by far, less problematic
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Alcolawl said:
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Click to expand...
Click to collapse
I had the same problem, then I got a twrp boot loop, ended up having to boot into slot b and reflash stock img through adb, beware...
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
NYYFan325 said:
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
Click to expand...
Click to collapse
I was on RC1 also
Anyone got some insight to this? Can't be that uncommon of a problem...
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
noidea24 said:
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
Click to expand...
Click to collapse
I never had TWRP stick unless I added another step to your instructions --boot completely into the rom once, go back into the bootloader, open temp TWRP and flash the TWRP zip again. If I didn't do this my recovery would always revert to stock but, strangely, even though I was running a custom rom the combination of the custom rom and stock recovery never bootlooped my phone and I was able to boot from the stock recovery to the custom rom with no problems. The only reason not being able to boot into TWRP was even an issue was that you can't flash any zips in recovery without it. Otherwise the phone ran so perfectly I didn't even realize at first that TWRP wasn't still the installed recovery.
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Also pointing out flashing rooms and certain zips here in the forums WILL revert you back to a stock recovery. Just my last bit of helpful information, hope someone gets it figured out, flashing is already a chore for those of us who like to experiment.
pcriz said:
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Click to expand...
Click to collapse
I was able to boot into recovery after doing this. Got a bootloop booting into system though, but flashing the ROM (and TWRP) fixed it.
Hello,
Try booting to TWRP 3.0.2 RC1 then flash TWRP 3.0.2 RC1 + SR1-SU v2.82SR1 + SU Pixel Fix (from Chains beta thread) one right after the other in the same TWRP session then reboot. Should fix your issue, give you recovery+root without ram dump.
Cheers
Everytime you flash a rom you need to flash twrp before rebooting or you'll lose twrp recovery.
Unfortunately I've had to get my Pixel XL replaced due to a defect and received a Verizon edition XL running 7.1.1. This is what I get for buying it from Best Buy Therefore I cannot unlock the bootloader and this problem no longer applies to me.
I'll keep this thread open for a bit in case it's useful for anyone else. I'll just sit here in all of my Stock-ness.
I couldn't get this to work. Tried flashing stock boot.img, then booting off of the TWRP images but I keep getting TWRP boot loop. Any suggestions? Tried flashing the entire stock image as well and no dice...
Okay, so I had to give lineage a try and have now switched back to stock rom.
On Feb update
Twrp img is 3.2.1.0
No matter what I try I am getting a bootloop when trying to install magisk.
My current steps:
Completed a stock room flash with wipe
Fastboot flash boot --slot all boot.img. ( Stock boot image)
Phone is on slot_a
Fastboot boot twrp.img
In twrp I have tried to just flash magisk 16.0
Restart system
I'll get to the Google splash and it will just sit there forever.
If I manually restart I get a brief Google splash then cycles to bootloader.
Where am I failing?!?!
You don't have to flash any boot.img after installing the stock with flash-all. You can also try to flash the stock to both slots and flashing the twrp after fastbooting it, rebooting and then flashing the Magisk.
FIXED**
So i again did a complete wipe with the most recent feb OTA via flash-all with the -w included.
Afterwards booted, setup completed
restarted to bootloader
fasbooted twrp
flashed elemental x kernel
rebooted system
fastbooted back into twrp
flashed magisk 16.0
rebooted system
Works perfectly now.
Hopefully this can help someone out in the future!
Hello, need your help guys.
So my Whyred bootlooping now. What I did previously was wiping System, Cache, Dalvik & Data before flashing custom ROM -- I know, this shouldn't be an issue. But since I can do fastboot, I tried to flashes recovery. I tried a few (TWRP, RedWolf & Batik), for each the steps were all the same: Via fastboot flash the dummy image to manipulate ARB check, then flash Recovery and finish with boot into recovery.
The phone booting into recovery, I can see the screen of recoveries for few second, then phone bootlooping again.
What should I do?
And for additional information, my phone was unlocked bootloader -- it still unlocked because I can see the Unlocked sign on bootloop screen. I also tried to flash official MIUI rom via fastboot (whyred_global_images_V10.0.6.0.OEIMIFH_20181127) but it was failed because anti roll back -- I also don't understand this because the ARB was supposed not allowing me to downgrade, but why is it also not allowing me to flash the latest ROM too?
I am now stucked in bootloop -- still can do fastbooting, but really have no idea how to flash any rom and get into the system. Really need help help help please
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Rush-er said:
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Click to expand...
Click to collapse
Yes, for redwolf it was the command -- I was short typing but thats the idea.