I'm running Android 10 and OOS 10.0.2 GM21AA.
I'v clean flashed the OOS 10.0.2 and rooted the phone by flashing Magisk through TWRP Latest build. Initially the root was going well.
After installing youtube vanced module from magisk, i rebooted the phone and it doesn't rebooted. It got stuck in OEM Unlock Warning screen for a while then automatically shifted to fastboot mode.
Then i flashed the stock boot.img and phone became good to go.
I flashed the stock boot.img patched with magisk. But the phone doesn't get any signal(SIM UNKNOWN) after reboot.
I tried changing magisk and twrp versions also, but it didn't work.
I need help of you guys. Please suggest me.
Use the following thread!
It works fine!
https://forum.xda-developers.com/showthread.php?t=3940368
Gesendet von meinem GM1913 mit Tapatalk
Related
Previsouly, I used TWRP v8 and EU MIUI 8.7.19 and today I updated EU MIUI 8.8.3.
After ROM installation, my system is booted to TWRP mode.
I successfully reinstalled EU MIUI ROM, and worked well until TWRP work.
After using TWRP, my system is booted to TWRP mode..
How can I fix this TWRP loop problem.
Please help me.
Thank you.
Format data and working.
Gesendet von meinem MIX 2S mit Tapatalk
Hi all,
Is anyone rooted on global hardware global ROM 10.3.1.0? I've been getting the update notifications for a while but have been hesitant to update in case I loose root, I've never updated with an OTA on a rooted device before. To update, can I just download the OTA then reflash TWRP and Magisk and be good to go? Has anyone tried this? If so, what version of TWRP and Magisk did you use successfully?
Thanks in advance for any input/advice!
Download the OTA, install it via TWRP, boot into the system and flashing TWRP via ADB again. Boot into the TWRP and flash again magisk. That's how it worked for me. At least with my mix 2 [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I flash magisk 20.1 after every eu update.
First i flash the eu update. After that i boot in recovery again. Then i flash magisk and clean dalvik and cache. Then i boot system.
If you flash into the recovery magisk after the eu update without restarting, it ends in the bootloop.
At least it was with me like that.
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I'm running Magisk 19.4 (the one for Xiaomi devices obviously) on Xiaomi.eu beta 9.12.12. No initial issues or any since
You should always reboot first, otherwise magisk will bootloop
Giuskiller said:
You should always reboot first, otherwise magisk will bootloop
Click to expand...
Click to collapse
A reboot into twrp is enough
Gesendet von meinem MIX 3 mit Tapatalk
I can confirm that magisk 19.3 work fine on lastest eu stable 11.0.1.0 android 10.
i have the last xiaomi.eu beta and the last magisk and all work good
kiwan955 said:
i have the last xiaomi.eu beta and the last magisk and all work good
Click to expand...
Click to collapse
I too [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
From my experience in mix 2s. If i have a MIUI with magisk modules active, then flash new rom, restart, flash magisk, then wipe dalvik, i get bootlooped. The solution was to disable all magisk modules before updating and then flash magisk, wipe dalvik and restart. After getting into the OS, reactivate the modules.
If you have a twrp based recovery that allows you to disable magisk modules from the recovery (like orange fox) that may help you get out of the bootloop.
Give it a try
Hello guys, I have this problem since upgrading to the latest OOS 10.3.2. If I flash Magisk 20.3, device boots without detecting a SIM, so no signal at all. And phone app crashing.
I'm using the latest TWRP (twrp-3.3.1-18-enchilada-Q-mauronofrio).
Anyone experience the same? How to get this to work? I need my Google PAY back
-=zipp=- said:
Hello guys, I have this problem since upgrading to the latest OOS 10.3.2. If I flash Magisk 20.3, device boots without detecting a SIM, so no signal at all. And phone app crashing.
I'm using the latest TWRP (twrp-3.3.1-18-enchilada-Q-mauronofrio).
Anyone experience the same? How to get this to work? I need my Google PAY back
Click to expand...
Click to collapse
bro check ur imei number wheather it is showing or not dial *#06#
Same thing happenned to me. I removed magisk and all modules completely then used local upgrade and reflashed 10.3.2 OTA and flashed twrp img with fastboot. When it booted into twrp recovery I flashed the twrp installer, rebooted to back to recovery and flashed magisk from twrp and rebooted system. Everything was right with the world then. The key was re moving magisk first.
Sent from my ONEPLUS A6013 using Tapatalk
cjcool_123: IMEI is showing correctly because I reflashed ROM back to get networking ability
Hondo71: I'll try that, thanks
Hondo71: I tried that, but unfortunately with the same result.
I re-flashed stock rom to get functionality back, uninstalled magisk app, flashed twrp, rebooted. flashed magisk, booted and nothing :-/
IMEI is not showing when in this state
Might want to stay where you're at until more reports come in with the all clear or maybe there's an issue with the TWRP or the rom itself
I'd try one more time. Make sure magisk and all the modules are uninstalled. Download & Reinstall 10.3.2 full OTA through local upgrade. Then install magisk mamager. Boot to fastboot and boot TWRP recovery img. Then in recovery flash the twrp installer zip, reboot to recovery and install Latest magisk zip. Reboot system. Data and cellular should work. I lost it on both my 6 & 6T but got it back doing it this way on both.
-=zipp=- said:
Hondo71: I tried that, but unfortunately with the same result.
I re-flashed stock rom to get functionality back, uninstalled magisk app, flashed twrp, rebooted. flashed magisk, booted and nothing :-/
IMEI is not showing when in this state
Click to expand...
Click to collapse
Uninstall magisk and modules then reflash 10.3.2 from local upgrade download twrp installer and Magisk zip to internal memory, install magisk manager. reboot to bootloader, then fastboot boot TWRP, in recovery flash twrp installer, reboot recovery and flash Magisk. Reboot system. Just verified it working again on my OP6.
Sent from my ONEPLUS A6013 using Tapatalk
Hondo71: you were right, it is working now. I don't think I needed to do all the procedures you suggested, I figured out there was one module that was causing this - Native OOS call recorder :-/ I feel stupid I haven't thought about this before.
Anyway, all working now. Now I only need to find out new way how to record my calls
-=zipp=- said:
Hondo71: you were right, it is working now. I don't think I needed to do all the procedures you suggested, I figured out there was one module that was causing this - Native OOS call recorder :-/ I feel stupid I haven't thought about this before.
Anyway, all working now. Now I only need to find out new way how to record my calls
Click to expand...
Click to collapse
I reinstalled oos call recorder and it works fine.
Sent from my ONEPLUS A6013 using Tapatalk
How do I root stock os 10.3.2? Which version of TWRP and Magisk I have to use? Please advise. Thanks in advance.
I also lost the function for telephone.
Mobile network ist working, i can recieve calls, but im not able to do calls.
i tried everything...flashes a few times the latest beta...flashed Magisk new...delteted it...i dont know what else can be possible?
yess same problem after got new update > flash twrp > install magisk > NO SIGNAL That because of OOS native call recording delete and reinstall it >DONE Working great.
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again