Hello guys,
I've just updated the device with Dec OTA file (and Root with Magisk Patched file) like so many other times and suddenly Wi-Fi doesn't work.
Any suggestion? It sounds to me that there were other people who had the same issue in previous updates.
Ok, I fixed it. Repeat the process resolved the issue...
Darkside1984 said:
Ok, I fixed it. Repeat the process resolved the issue...
Click to expand...
Click to collapse
What did you do? What process exactly did you repeat?
reverenddak said:
What did you do? What process exactly did you repeat?
Click to expand...
Click to collapse
So basically what worked for me was flash the OTA, flash Magisk and TWRP installer.
I rebooted, noticed it didn't actually switch what slot I was on (I was on B before installing and still on B afterwards) and I had no root.
Rebooted to recovery and switched to slot A, flashed the OTA again as well as Magisk and the TWRP installer, rebooted.
This time the system booted up with root but no longer had WiFi, it wouldn't turn on at all.
Rebooted a third time into TWRP and switched the slot back to B and now it's working correctly with root and WiFi.
Related
So, i just updated Magisk to 14.0. After rebooting, my phone gets stuck just before the lockscreen appears, then it automatically reboots to the recovery menu. Here i can only download a new stock rom, reboot (which goes the same way), and shutdown. Now, i would like to boot in TWRP and uninstall Magisk, but i have USB debugging disabled, so i don't know if i can access TWRP and run the uninstaller from SD.
Is there anyway i can get out of this situation without the dload method and therefore wiping my internal memory ? I have most of it backupped, but some important files i spent weeks getting are still there.
Ok, i resolved it. To fix this you can go into TWRP (pressing Power+Volume Up before the screen turns on and Up until you enter recovery) and apply the Magisk Uninstaller (it does not need a boot image to work). Hopefully this will help anyone who had this problem.
The best version of magisk yet is v13.3
mine just updated to 14.0 without any problem , i use direct update from app.
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Magisk 14, no issues here either. Stock rooted L04.
stuckoutside said:
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Click to expand...
Click to collapse
Glad it was fixed.sometimes same things work for few but not for others. Thats wiered but still fact remains the same
stuckoutside said:
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Click to expand...
Click to collapse
Try magisk 14.0 directly not from 13.3 , but mine is smoothly worked from 13.3.
venugopalu007 said:
Try magisk 14.0 directly not from 13.3 , but mine is smoothly worked from 13.3.
Click to expand...
Click to collapse
These are weird issues. Works for one but not for others.
Strange
You can report this to the Magisk support thread.
Sent from my DUK-L09 using XDA Labs
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Just in case, I successfully got on the fastboot and then used "fastboot" command to boot on TWRP. I am now making a backup of "/sdcard".
But I would really like to not have to make a factory reset... Is there a solution to avoid this?
Flash ROM and flash Twrp
Reboot
Shutdown
Boot on twrp
Flash magisk
Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake [emoji6]
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
I succeeded in fixing it by installing twrp and doing... I don't really remember what lol, but I was able to uninstall Magisk and reinstall it with twrp, now everything works again!
"Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake"
Yeah, I thought it was the most safe way to update but it seems that I was clearly mistaken.
Thank you anyway!
I've updated like that a couple of times now and it always work. Most likely you had modules that made you not being able to boot.
hey, the error is that you need START the update using the standard OTA interface (don't reboot), and then go to magisk, and install to second slot. Afterwards it will reboot. What you did is configure your phone to boot from the second slot but the update wasn't ready or something like that. I don't know the technical details but I did the exact same thing on the last update, and I've learned from my mistake
In that case, you can change the slot using fastboot, I think that's what I ended up doing. It took me like a whole afternoon to figure out the mistake. I'm hoping this warning is useful for future updates.
It will be useful yes, thank you for the clear explanation!
noom4_5 said:
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Click to expand...
Click to collapse
Flashing magisk uninstaller fixes this.
*system error* said:
Flashing magisk uninstaller fixes this.
Click to expand...
Click to collapse
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
tamamma said:
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213/page5
If you are on Android 10 beta 1
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.
I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?
I'm not rooted but From my experience you have to delete modules folder in twrp
RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update
RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though
For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Is this a bug of Magisk?
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:
If you have TWRP you can remove modules if you have a bootloop.
So I updated my phone to the newest firmware (international version) but I didn't look up how to do it properly because I thought it would be like the op8pro I was wrong
I disabled my xXx module, ran the update and with magisk 20.1 I installed to the inactive slot and it rebooted with no problem. but then not researching what to do next I just switched my module back on and it is now stuck on a boot loop
So my question is, is it going to be possible to restore the phone and keep intact the data or I'm just gonna end up swiping it clean in the process.
Thanks
Ar3olaa said:
So I updated my phone to the newest firmware (international version) but I didn't look up how to do it properly because I thought it would be like the op8pro I was wrong
I disabled my xXx module, ran the update and with magisk 20.1 I installed to the inactive slot and it rebooted with no problem. but then not researching what to do next I just switched my module back on and it is now stuck on a boot loop
So my question is, is it going to be possible to restore the phone and keep intact the data or I'm just gonna end up swiping it clean in the process.
Thanks
Click to expand...
Click to collapse
Delete the magisk modules in root/data/ADB/modules .... Using TWRP
@soka said:
Delete the magisk modules in root/data/ADB/modules .... Using TWRP
Click to expand...
Click to collapse
My twrp is gone do I install it with the one click root app ?
Ar3olaa said:
My twrp is gone do I install it with the one click root app ?
Click to expand...
Click to collapse
Hopefully you have an unlocked bootloader.
Flash TWRP.img using fastboot
fastboot boot TWRP.img