Okay, I really need help. I'm so spoiled with my Nexus 6 and flashing **** I'm at a loss on how to properly update all this ****.
I need to flash the stock dtbo.img which is fastboot flash dtbo dtbo.img, then after that, i need to fastboot boot twrp.img, flash the latest twrp to update it, then flash the new kernel and then magisk last. Correct? Do I need to worry about setting slot a or b as primary and all that extra stuff when I first rooted?
Hey did you ever get any answers?
What are you trying to do? Why are you flashing dtbo? If you're doing a monthly update then there are a couple different ways.
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.
Hey ^^'
I stupidly decided to flash TWRP on the boot image. (fastboot flash boot_b TWRP.img)
The problem is that I now logically always boot on TWRP and not on the system.
Who has an idea how to delete TWRP again from the boot image? ,
Use new flasher to flash unpacked firmware from FTF file, there are many tutorials how to do this.
So I flashed TWRP on my 7t before I realized it doesn't work on the stock OS. I want the factory recovery back. Can somebody point me to the best way to do this. (Also I want to keep root and magisk)
Just extract payload.bin of stock os and flash the recovery.img with fastboot
Hello,
In all of the steps to install Magisk on a phone, I never liked the step in which you have to flash the patched boot image on the boot partition. I always thought it is pruned to errors, especially if you do that at every update, an oversight maybe when you download the ROM or maybe you use an older version of the patched image and your device is soft-bricked. So, I always wondered if there are other, safer, solutions to do that step. When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image. I know that the result is pretty much the same, but if you screw up with the patched boot image, the result is just a temporary bootloop that you can resolve by just restarting your device. But in all the guides I've read, only one suggested this alternative solution, so I was wondering why this solution isn't suggested or, at least, mentioned, for those who are afraid to do the blind flash. There are possible issues with using this method or what?
I already used this method two times for installing Magisk on a Oneplus 9 and a Pixel 6, and now I'm here with a brand new Pixel 6 Pro and I've to decide what method to use.
Because you're essentially doing the same thing. Even if you flash the incorrect boot image, just flash the correct one afterwards and problem resolved. You can do either way, the alternative just takes a step longer.
Now that restore images/flash to inactive slot after ota is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
shoey63 said:
Now that restore images/flash to the inactive slot after OTA is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so the next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
Click to expand...
Click to collapse
Thanks for the answer, this is really helpful. So, should I use the canary version for the first installation or can I use the stable and update to the canary when I have to OTA update? This is just to be sure, I don't know how "stable" is the canary since I never used it.
And since I'm, I'll take the opportunity to ask another related question: how bad can I screw up with the boot image? For example, if I flash a boot image of another device (oriole for example), should I still be able to boot into fastboot and flash the original, or this will prevent me to boot in the fastboot mode at all?
Because I'm still not sure if the initial bootloader phase (the one that boots up the fastboot) is included in the boot image or not, since the recovery has been included in the ramdisk of the boot image since the introduction of the A/B devices (or, at least, I think so).
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
shoey63 said:
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
Click to expand...
Click to collapse
Awesome, thank you! You clarified a lot of my concerns.
fuji97 said:
When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image.
Click to expand...
Click to collapse
I do this exact procedure for every OTA. It's just easier for me and I've had numerous problems trying to "keep" root versus just booting to a patched image and reinstalling.