I'm facing no SIM card detection after last system update. Does it happened to any of you?
Oxygen OS 10.0.6.GM57BA
GM1900 (red Chinese version)
Magisk and Xposed
Me. Same model and system version here.
After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.
carmeloamg said:
After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.
Click to expand...
Click to collapse
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.
For me it seems to be caused by a Magisk module called OxyMod. After uninstallation everything is back to normal.
For me it was a magisk call recording module that solved this issue.
staenk said:
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.
Click to expand...
Click to collapse
Hi! I've just seen your reply and that you solved it. If you already have magisk installed, unistalling it won't make you loose data I'll explain the process at the end of the post.
tpunkttpunkt said:
For me it was a magisk call recording module that solved this issue.
Click to expand...
Click to collapse
I also had a call recording module for magisk so maybe this was causing the issue and uninstalling magisk solved it but was not necessary. Now the Magisk and that module are installed again causing no problem.
EDIT: I research about oxymod xposed module and find that it has also a call recording patch... everything suggests that enabled call recording was causing the after-update issue.
Now the notes about installing/unistalling magisk for @staenk (hidden to avoid huge post):
In case you have Magisk already installed, you just need to:
Already have adb/fastboot installed in your computer
Download the official Magisk uninstaller .zip from the original developer post.
Save it in your phone memory.
Then find a .img of TWRP that works for our device on android 10 (there's one developed by @mauronofrio )
Power off your phone and boot it into fastboot (volume down + power)
Plug your phone to your computer
Boot twrp using the following terminal command where twrp is the path to the twrp image you downloaded in your computer:
Code:
fastboot boot twrp.img
Click on keep read only when asked.
Use install zip to browse the Magisk uninstall .zip and install it.
You have uninstalled magisk, reboot to system normally.
To install magisk again, just download the latest magisk .zip and repeat the process.
If it is the first time you are installing Magisk the process require to first unlock bootloader, and this process will erase your data. Once unlocked it will remain until you lock it back again. You can relock bootloader after installing Magisk (not recommended from my point of view) and your phone will keep rooted but you won't be able to boot twrp again if something goes wrong, what could lead into you unlocking bootloader again and loosing your data in the process.
If you are too noob to understand the instructions means you should not mess with Magisk or whatever yet and need to read more about.
I also experienced the same issue which I fixed by uninstalling the Magisk Call Recording module.
Related
I recently followed the instructions in this video to root my Pixel 1 (non-XL, Verizon version unlocked bootloader, updated to final version of Pie). I'm not exactly sure what I did wrong, but my phone went into a bootloop and I couldn't get any adb command to work (it said phone not authorized even though it clearly was before the bootloop), so I went ahead and did a factory reset using the Recovery mode.
Now, after the factory reset, I have Magisk Manager appear in my list of apps. When I open it it asks if I want to upgrade to the full Magisk Manager, and if I go ahead with that it finally says "App not installed". I've tried uninstalling the app but it reappears after every reboot.
I'm trying to start afresh with the root now, but I'm not sure if I need to uninstall Magisk first, or just go ahead with following #7 in this XDA guide? Any advice would be helpful.
Thanks!
Run the Magisk uninstaller and reboot, then reinstall Magisk.
post-mortem said:
Run the Magisk uninstaller and reboot, then reinstall Magisk.
Click to expand...
Click to collapse
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!
hassanrashid3 said:
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!
Click to expand...
Click to collapse
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.
post-mortem said:
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.
Click to expand...
Click to collapse
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.
hassanrashid3 said:
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.
Click to expand...
Click to collapse
I've been trying to get rooted all day. It took forever to get TWRP flashed, but when I finally did, I installed Magisk, in accordance with that same video you watched. Installed the Magisk app and it was totally worthless. Nothing but ads. Still not rooted. I'd love to know what you did to finally get root if you have a second.
Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.
hassanrashid3 said:
Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.
Click to expand...
Click to collapse
Yeah, it was a big ol' mess. The Magisk I had installed was from the app store. That was the worthless one. Apparently the real Magisk hadn't been flashed correctly. When I ditched the store app and then re-flashed Magisk, suddenly I was rooted and everything went smoothly. Worst rooting experience ever, but man does it feel good to have control over my phone again. Been kicking bloatware extra hard just because can.
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
By the way, hassanrashid, thanks for the reply and for posting this in the first place. I'm not so sure that I would have gotten rooted at all if I hadn't stumbled upon this thread.
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 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.
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
Did you uninstall Magisk modules First?
null0seven said:
Did you uninstall Magisk modules First?
Click to expand...
Click to collapse
I didn't. The whole point of doing it the way I did was to eliminate the need to uninstall the modules.
Could that be what went wrong?
YES.
null0seven said:
YES.
Click to expand...
Click to collapse
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
JohnsNotHome said:
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
Click to expand...
Click to collapse
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Arden144 said:
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Click to expand...
Click to collapse
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
JohnsNotHome said:
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
Click to expand...
Click to collapse
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Interesting.. I think I'll just follow this method. This was all in the name of saving time.
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Arden144 said:
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Thank you so much for this. I think I understand now.
I hope I haven't caused any problems to the slots thing on magisk with the mistake I made.
1. Uninstal Magisk mods.
2. Flash Oos in System > Update > Local Update. DON'T reboot.
3. Open Magisk > Downloads > TWRP A/B Retention script. Instal it.
4. From Magisk reboot to twrp. Flash Magisk 19.3 stable.
Reboot to system. You should be updated and rooted.
I upgraded to Android 10 using a guide from someone who successfully kept root when upgrading from Android Pie to 10. I followed the steps exactly, but I still lost root. I'm using the latest version of TWRP Guacamole for the OnePlus 7 Pro. I fully understand that it's not fully compatible with my phone so I'm wanting to roll back to Pie. My phone currently does not have an OS on it because another guide I followed said to flash TWRP as the boot in the bootloader in order to reboot into TWRP to then reflash the OTA and then TWRP. I did this because TWRP would not mount my storage and therefore could not install or flash anything because it couldn't access storage. That didn't work. So now when I boot normally or into TWRP, it only boots into the bootloader. I need help fixing this because now I'm out of a very nice phone.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
unrated87 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
BUZzZERBeater00 said:
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
Click to expand...
Click to collapse
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
I tried using the MSMDownloadTool, but the Qualcomm HS-USB QDLoader 9008 (COM3) driver was grayed out in the device manager. When I would open the MSMDownloadTool, it would not recognize my device, and would not download anything. Any suggestions?
BUZzZERBeater00 said:
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
Click to expand...
Click to collapse
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
BUZzZERBeater00 said:
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Click to expand...
Click to collapse
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
blas4me said:
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
Click to expand...
Click to collapse
Sorry. It's too late. I already have Magisk installed and Edxposed.
I just installed Edxposed
blas4me said:
I just installed Edxposed
Click to expand...
Click to collapse
Ya. It worked perfectly as long as I flashed Riru - Core, rebooted, then flashed Riru - Edxposed, rebooted. Then installed the Edxposed apk. Flashing both Riru -Core and Riru - Edxposed back-to-back before rebooting put my OnePlus 7 Pro into a bootloop. I had to boot into TWRP and flash a "Magisk in TWRP" module and then in the terminal type "mm for first time" hit enter, and type "c" which put takingmy phone in Core Only Mode. This disabled the modules it out of the bootloop. But then after it reboots, attempt to uninstall the modules, which won't fully work. So basically you'd just have to flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules. Moral of the story is don't flash both Riru - Core and Riru -Edxposed without rebooting between each install. Also, don't just flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules and then not later flash the "Magisk in TWRP" module and disable Core Only Mode. Or just turn it off in Magisk Manager. Modules will install, but they won't work. And they won't uninstall either.