Related
my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!
when it auto reboot to recovery, formate data
When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...
I dont know if you can boot it w/o root
redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.
jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos
SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!
It gets stuck on the white screen with the letter G and moving progress bar under it after rebooting. I ended up just flashing the stock boot.img and it works again but just rootless for now.
I successfully rooted with Magisk a few days ago but after getting a bootloop from trying to install Xposed I restored to 8.0 stock. I probably should've made a backup of the patched_boot.img from back then When I try making patched_boot.img again with Magisk it is only ~26 mb but the factory boot.img is ~41 mb. I don't remember exactly how big my first patched one was, but I feel like it shouldn't be this small.
potatoesryum said:
It gets stuck on the white screen with the letter G and moving progress bar under it after rebooting. I ended up just flashing the stock boot.img and it works again but just rootless for now.
I successfully rooted with Magisk a few days ago but after getting a bootloop from trying to install Xposed I restored to 8.0 stock. I probably should've made a backup of the patched_boot.img from back then When I try making patched_boot.img again with Magisk it is only ~26 mb but the factory boot.img is ~41 mb. I don't remember exactly how big my first patched one was, but I feel like it shouldn't be this small.
Click to expand...
Click to collapse
Have you tried flashing the Magisk.zip instead? I had some troubles myself recently but flashing the Magisk zip worked like a charm. You don't need to flash TWRP recovery, you can just one-time boot to TWRP and flash the Magisk zip that way.
EDIT:
To do so, I'm taking snippets from THIS post, but basically:
Download TWRP.img, place in platform-tools folder.
Download Latest Magisk v14.x Zip file, place on device "SDCard"
Reboot phone to bootloader/fastboot
Command: fastboot boot <twrp filename.img>
Once TWRP loads, flash the Magisk Zip file you downloaded and reboot your phone, you should be all set.
Tried flashing Magisk 14.4 and the most recent 15.3 with twrp but still stuck at same boot up screen. If it matters I'm running 8.0 with November update (opd1.170816.025). I'll probably do a clean install of 8.1 later and try again, just waiting for a few apps get updates for 8.1
potatoesryum said:
Tried flashing Magisk 14.4 and the most recent 15.3 with twrp but still stuck at same boot up screen. If it matters I'm running 8.0 with November update (opd1.170816.025). I'll probably do a clean install of 8.1 later and try again, just waiting for a few apps get updates for 8.1
Click to expand...
Click to collapse
Just to be clear, you are telling Magisk to patch the November BOOT.IMG, correct?
You could also try dirty flashing the January full ROM (remove the -w from the flashall script), then flashing Magisk via TWRP...
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
Hello Everyone
I felt this section will be more appropriate for this query as it can also help many others who might be seeking an answer to the same question after Pie OOS (Community Beta) came out. This can also act as a guide for all future queries regarding force encryption. So, I have a really simple query, for which I have searched before posting but no concrete information came up.
Query:
How to prevent OOS from force-encrypting my internal data on first boot after a fresh ROM flash? I have tried flashing Magisk before first boot but that doesn't prevent force encryption. I am also using a custom kernel so patching stock boot image and flashing it won't be a viable option too.
Does anyone know of any zip or method which would prevent OOS from triggering force encryption (both Pie open beta and Oreo 5.0.8)?
I have tried to flash Oreo on an decrypted partition as follows but it still encrypted it.
1. Factory Reset
2. Flash OOS 5.0.8 zip on decrypted storage
3. Flash TWRP
4. Reboot to recovery
5. Flash Magisk
6. Flash custom kernel
7. Reboot
8. Rom takes 10 minutes to boot and storage is encrypted when booted up.
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
jeffrey268 said:
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
The doubt i have is for the patched boot image. I always flash a custom kernel and i assume it will replace the bootimage as well.
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.