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!
Related
After I flashed TWRP and went to the recovery right after flash, TWRP booted and I did decrypt + allow mods. Once I booted to system and later booted to recovery, TWRP didn't boot and stock recovery booted. Any help?
What I'd try is boot twrp, fastboot boot twrp.img. Then install supersu in twrp. Then boot back into the bootloader and flash twrp.
BearOfXDA said:
After I flashed TWRP and went to the recovery right after flash, TWRP booted and I did decrypt + allow mods. Once I booted to system and later booted to recovery, TWRP didn't boot and stock recovery booted. Any help?
Click to expand...
Click to collapse
I'm guessing you are still on the stock ROM and kernel? Flash a different kernel, or depending on flashing root it might modify the boot.img and stop it from doing that too.
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.
I was a root/rom aficionado back in the day, but laid off for a bit. Last device I messed with was an Essential phone, where you'd fastboot flash TWRP, reboot recovery, and then TWRP flash the stock boot image, then the Magisk zip. Is the process different for the Z2? In the guides I've read through, I don't see any mention of the stock boot image being flashed after the TWRP flash.
I realize flashing the stock boot image replaces TWRP, and I'm ok with that. I'm really only looking for the added Magisk functionality and not root.
For TWRP you would want to follow the guide on TWRP.me for this device.
In short, you want to fastboot boot (not flash) twrp, then install the twrp installer zip, reboot recovery, then install magisk.
After installing magisk, if you start boot looping, you need to go back in and format (not wipe) data.
I updated my phone to open beta 4 and installed twrp.
I flashed latest magisk zip file and no error occurred but the phone doesn't boot up.
Any help?
Thanks
How did you update? TWRP? Which one? Clean install?
What error?
Did you let it boot before install Magisk, or did you install Magisk right after OB4?
If its just dumping you back to TWRP generally a factory reset will make it boot again. (You backed up right?)
OhioYJ said:
How did you update? TWRP? Which one? Clean install?
What error?
Did you let it boot before install Magisk, or did you install Magisk right after OB4?
If its just dumping you back to TWRP generally a factory reset will make it boot again. (You backed up right?)
Click to expand...
Click to collapse
I updated via OTA.
Universal twrp by codeworkx
No. After installing OBA i flashed twrp and then magisk
I just flashed rom in twrp. Reboot to recovery. Flashed magisk and no verity and it booted.
Updated to Android 8.1.0 Oxygen OP5T_O2_Open_4 via OTA. Boots fine. Flashed Magisk-v16.0(1600).zip via TWRP. Bootloop.
Extracted stock kernel from OnePlus5TOxygen_43_OTA_007
Flashed stock kernel in fastboot. Boots fine. Flashed magisk via TWRP. Bootloop.
Flashed stock kernel in fastboot, immediately flashed magisk via TWRP. Bootloop.
Flashed stock kernel in fastboot. Boots fine. Patched stock kernel in magisk, flashed patched in fastboot. Bootloop.
Also tried variations with and without ElementalX, before and after Magisk, with and without cache wipes.
Currently I'm running:
Android 8.0.1
Oxygen OP5T_O2_Open_4
Kernel 4.4.74-ElementalX-OPt-3.00 (kernel extracted from 43_OTA_007 patched via TWRP flash tool)
Build A5010_43_180310
Magisk not installed
Runs fine except lack of root.
Found a fix. https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
Flash Magisk in recovery, then flash the work around, do NOT wipe cache (that's where the fix lives).
I recommend keeping the fix on the phone, not just doing an adb sideload, that way you can recover without a computer if you wipe cache. And of course keeping a working backup of boot.
Same config as my earlier post, but now with working root through Magisk
Hello all If any one can help me ,
I was rooted running rooted stock oxygen os before on my Oneplus 5T
after flashing Oxygen OS 5.1.4 Full Zip my phone is not rooting it gets in initial oneplus logo and freeze there without loading OS
Phone is working fine after Flashing Oxygen OS 5.1.4 Full Zip without any issue its not booting after flashing either SuperSu or Magisk
Steps which I follow are
1 Flash custom recovery I have tried both Codeworkx TWRP | Blu_Spark
2 after flashing recovery boot in to recovery flash Supersu or magisk
3 reboot
when I reboot if i Flash supersu it stuck on oneplus logo, If i flash magisk it reboot itself to fastboot so Os is not loading at all.
I have to flash full Zip again every time to get it working but then I dont have root access.
I have tried at least 10 times with different even old versions of magisk and supersu with out any success.
Is there any particular recovery or different version of magisk or superuse I need to flash?
your help will be really appreciated.
Try a different approach. Instead of installing recovery, just get phone rooted first. There is a way where you can boot into twrp (without installing it), and then flash magisk/supersu zip. If your phone is rooted, then you can install twrp later (or keep oem recovery)
This is how you boot into twrp (or any recovery): fastboot boot recovery recovery.img
Let me know how it goes.
As you said boot to recovery without installing it.
One problem currently I am installing recovery and flashing root. After that phone is not booting up in to OS it stuck on oneplus logo. Then I have to force off phone boot in to recovery and flash full os zip to get it working. I can boot in to TWRP because my os didn't load. Now if I use your method and flash root file and if phone won't boot to os that means I won't be able to boot in to TWRP again to flash full os zip to get phone working atleast without root. Any idea?
Huh, frankly I have no idea why you are facing this menace. I can just give two suggestions.
1. Try with older, more stable versions of TWRP and Magisk
2. Get yourself a custom ROM, most ROM's will work flawlessly after flashing root files
Hope for the best!
I usually switch from OpenBeta to LOS and back again. Here's how I switch back to OpenBeta (steps should work for official OOS):
1) Back everything on internal storage up. This one's important
2) Boot into official OOS recovery
3) Wipe EVERYTHING (this is why you need to follow Step 1)
4) Sideload the version of OOS you want. The instructions will be right there on the recovery screen
5) Boot into Fastboot and flash TWRP
6) Flash Magisk and (optional) Xposed