I am creating this post to help p2 community who is stuck on blue led after magisk update on custom rom
I have encountered this issue twice on my phone after a magisk update.
This happens when you patch the update directly from magisk manager.
The first time I was stuck with this issue on custom pie rom, I searched on other threads and got to know that device needs to reset to stock rom by flashing fast boot stock files on download mode, just search it, you will get link with details
However, this was a very complex task , also I lost my data in the process after flashing the data partition. From there , I went on to flash custom rom ,then installed apps , the process took the whole day
The second time when I again stuck with blue led , I was on another pie rom, This time I recovered my device without having to go over flashing all things again.
Please find the detailed step below , as I think it may help someone in such critical issues
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
Please like the post if you had same issue and are able to recover it from mentioned steps
I got into this trouble too, when direct installing magisk from v19.2 to v19.3. The magisk manager shows that it's finished installing v19.3 and reboot. Then the phone shows the white Lenovo screen, then turns dark, and vibrate for a few seconds with blue led lighting up, and finally just freeze. No bootloop, just a dark screen with blue notification led.
What I did was going to twrp (the one recommended in LOS 16.0 thread) by pressing vol up + down + power button until the white Lenovo screen come up, then release. I just reflash my current ROM (RR-P-v7.0.2-20190604-kuntao-Official.zip) using adb sideload. It finished flashing, click reboot, and finally managed to boot into system. No data loss, magisk v19.3 worked, and no magisk uninstaller required.
During the flashing process, I noticed that Magisk v19.3 was being auto flashed, so the magisk manager direct install probably somehow mess up with the boot.img after installing v19.3.
I was not able to go in twrp by any means , so I mentioned steps via download mode
Regarding your way to sideload and dirty flash whole rom , it didnt worked with me previously, so I cannot say about that, it was going back to blue led after reflashing
Regarding magisk installing and removing steps, anyone can ignore this steps and try if it works for them.
Just uninstall the magisk and reinstall it.
I have also faced same error previously and reinstalled magisk and it worked.
Someone please make a video of this and post it here
Rakxx said:
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
I have this issue but I don't know how to do these steps please make a YouTube video and post a link here (I'm new to this)
Click to expand...
Click to collapse
Related
Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks
Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.
Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.
Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy
Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.
You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not
Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?
Wow idk what happened here. Mistakenly replied to this thread. Apologies.
tl;dr
TWRP doesn't encrypt/mount storage,
Magisk kills WiFi.
Before I bricked the phone with a Magisk module, everything was working.
Had to revive my phone with MSM, stuck in qualcomm crashdump.
Now stock firmware is working, but I cannot get phone rooted with working WiFi / working TWRP.
==================================================
This is how I did it before (clean install, unlocked OEM)
1. boot into fastboot/bootloader
2. fastboot > fastboot flash boot twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
3. boot into recovery mode
4. install OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_89e89c225a754eb6.zip
5. install twrp-installer-3.3.1-4-guacamole.zip
6. reboot into recovery
7. Install Magisk-v20.0.zip
8. reboot system
DONE and it worked.
NOW:
1-6 stay the same.
But when I get back into recovery, TWRP doesn't read/mount the storage.
adb push magisk to sdcard/ and try to install leads to following:
Updating partition details...
...done
Unable to mount storage
Failed to mount "/data" (Invalid argument)
Full SELinux is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
- blablabla
- installing
- Done
Updating partition details...
...done
Unable to mount storage
Click to expand...
Click to collapse
...guess what, Magisk is not installed/working
- Repair/change file system doesn't work.
(phone will boot into system instead of recovery, back to recovery still Internal Storage at 0 MB)
- formatting data + Wiping Dalvic / ART Cache, System, Cache doesn't work
(will all lead to stuck in Fastboot -> recovery due to fastboot image)
(installing boot.img (on A & B) and TWRP.zip doesn't help)
- install OOS and then just flash TWRP without flashing stock firmware doesn't change
Alternative
1-6 stay the same.
7. boot into fastboot
8. boot TWRP *-70 again
9. encrypting now works, mounted
10. isntall MAGISK (20.0 or 20.1)
11. reboot system
At this point it seems like everything is working, but with MAGISK now installed, WIFI won't work. Can't activate WiFi it at all.
So, i have no idea what I changed.
Rooting worked before the brick. Now it stopped working.
My friend has that problem after rooting his phone with magisk..
Just flaah the rom and wifi will be back..
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
https://forum.xda-developers.com/on...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Click to expand...
Click to collapse
Thank you, Sir
I should have mentioned that I already flashed a dozen times to stock firmware. Used the package from your link as well when I was stuck in fastboot.
My mistake, I should have been more accurate with my problem.
Getting it back to stock firmware isn't the problem.
Getting it back as a rooted device with working WiFi and working TWRP is the problem.
Stock OOS - without TWRP, without Magisk » ROM working
Stock OOS + TWRP (3.3.1-4) » TWRP not working; ROM working (but this combo worked before)
Stocks OOS + TWRP (3.3.1-70) » TWRP working, ROM working[/b] (but TWRP *-70 should be replaced by *-4 afaik[/U]; correct me if I am wrong)
Stock OOS + Magisk + TWRP *-70/TWRP*-4 » Magisk working, ROM no WiFi. (fixable through reflashing stock firmware and deleting everything)
So maybe any ideas why Magisk/TWRP stopped working now? And how I can get my OP7P rooted and the stable TWRP working?
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
saexcore said:
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
Click to expand...
Click to collapse
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
For me, I never booted into bootloader. I ran fastboot boot /path/to/TWRP.img, while still booted up and that took me to recovery and I used TWRP installer and flashed magisk from there.
I tried almost all the other methods, and kept soft bricking. I didn't patch anything, booting from fastboot soft bricked me.
I just started experiencing connection issues after installing a Magisk modules, but I read a custom kernel solves that.
meleeb4kr said:
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
Click to expand...
Click to collapse
Sure.
The boot image I got from:
https://androidfilehost.com/?w=files&flid=294300
(download the fastboot firmware for your device, for me it was "10.0.1-GM21BA".
open the archive, open the next folder, extract the "boot.img" file to your PC)
Magisk I got from:
https://github.com/topjohnwu/Magisk/releases
(I used 20.1, 19.4/20.0 seems to work more stable for more people)
TWRP I got from:
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
(Download image for Q and twrp-installer.zip)
===================================
1. Boot into fastboot
(developer options > advanced restart > restart bootloader or power device off > HOLD volume down and press power till in fastboot)
2. In fastboot: "fastboot boot twrp70.img"
(#protip: drag & drop file into CMD)
2.1. wait till phone encrypted everything and TWRP started
3. Copy twrp70.zip, boot.img & Magisk-v20.1.zip to your phone
(I put it in the TWRP folder)
no reboots in-between!
3. In twrp homescreen: install > install image > boot.img > choose "boot" > install
4. In twrp homescreen: install > install zip > twrp70.zip > install
4.1 wipe dalvik
5. In twrp homescreen: install > install zip > magisk-v20.1.zip > install
5.1 wipe dalvik
6. In twrp homescreen: reboot > system
Done.
Hope it works for you too.
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk
But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged
What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.
Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain
Fixed!
Now I'll write a guide for those in the same situation.
franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.
Folks,
I wish to update to MIUI 12 but I also want to have ROOT and Magisk functionality.
Is it the same process as before where we:
1) fastboot boot recovery.img (this is twrp)
2) then flash Magisk?
has anyone achieved Root and Magisk functionality on MIUI 12 on Mi Mix 2S ?
I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.
dawidcx3 said:
I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.
Click to expand...
Click to collapse
Thanks bro,
Yea I flashed it the old TWRP/Magisk method and it works.
Placing my personal step by step instructions here in case anyone needs it. You can use Orange Fox in place of TWRP. Your choice.
Get latest Magisk Zip (Magisk-v21.0+) https://github.com/topjohnwu/Magisk/releases/
Copy Magisk-v21.0.zip to Phone Storage
Get latest TWRP (twrp-3.4.0-0-polaris+) https://dl.twrp.me/polaris/
Copy twrp-3.4.0-0-polaris.img to Phone Storage
Rename twrp-3.4.0-0-polaris.img to recovery.img (on local PC)
Go to bootloader mode (Power & Vol - )
CMD the following command: fastboot boot recovery.img
after starting TWRP on the phone flash twrp-3.4.0-0-polaris.img file again in TWRP by clicking Install then Select Image then Recovery Partition.
and after this, do not restart
flash Magisk-v21.0.zip
restart
and TWRP remains and you have root.
Regards..
Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do
25agosto said:
Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do
Click to expand...
Click to collapse
Stock rom has software that checks recovery and replaces it with stock if it detects changes. After you flash recovery in fastboot make sure you power off. Then boot to recovery with button combo and flash the recovery zip (orange fox). After flash it should reboot and automatically edit files to stop stock recovery install.
Is Google Pay working with rooted mi mix 2s?
howpathetic said:
Is Google Pay working with rooted mi mix 2s?
Click to expand...
Click to collapse
Yes it does. You have to use "hide magisk" option.
Hello friends,
Current setup:
Device: OP6
ROM: Stock OOS 9.0.9 stable
Kernel: ElementalX-OP6-3.19
Root status: Rooted with Magisk 23.0
TWRP 3.4.0 | blu_spark v9.115 - Current active slot: A
I wish to wipe the device and clean flash OOS 11 stable then install the latest TWRP, EX Kernel, and root using the latest Magisk. Please help me with the process so that I don't brick the device inadvertently.
The-Droidster said:
Hello friends,
Current setup:
Device: OP6
ROM: Stock OOS 9.0.9 stable
Kernel: ElementalX-OP6-3.19
Root status: Rooted with Magisk 23.0
TWRP 3.4.0 | blu_spark v9.115 - Current active slot: A
I wish to wipe the device and clean flash OOS 11 stable then install the latest TWRP, EX Kernel, and root using the latest Magisk. Please help me with the process so that I don't brick the device inadvertently.
Click to expand...
Click to collapse
Please make sure to take a back up of EVERYTHING ( be it any preferred method you use) . Once you have a backup of your complete phone please proceed to the next step by download the latest OOS 11 Full version( Not the OTA update).
Try updating your phone through Settings -> System Update.
Once the update is complete , Please make sure to reboot your phone to recovery mode once. Which should now be installed with Stock Recovery.
In some cases the stock recovery wipes everything on your phone and reboots.
If not you can wipe using the option Erase Everything including photos in memory.
Once the phone reboots and setup is complete. Reboot your phone once or twice.
The above step may sound weird but it helps you to identify any issue before next step.
MAKE SURE TO FOLLOW THE STEPS AS I HAVE STATED ELSE YOUR PHONE WILL END UP WITH CRASH DUMP MODE.
1.Make sure you have necessary ADB drivers installed on your PC.
2.Reboot your phone to Bootloader mode either by using command prompt or by pressing Volume + and Power key. (CMD : adb reboot bootloader )
3.Use Fastboot command to install the attached recovery file. Please do not use other TWRP files. ( CMD : Fastboot boot boot.img) ( boot.img is the file name attached).
4. The phone should reboot to TWRP recovery mode.
5. Under TWRP menu Navigate to Advanced -> Select Install Current TWRP.
6. The step should install your phone with TWRP on both slots.
7. Once install reboot your phone and check if OOS11 is still intact.
8. To verify if TWRP is installed as your recovery . Reboot your phone to recovery mode.
9. Once in recovery mode you can install the attached Magisk V23 apk using menu Install -> choose Magisk apk.
10. Reboot your phone and install Magisk using the same APK.
Viola you are all good to go if you have installed everything as mentioned.
Hope it helps now.
mm_rajesh said:
Please make sure to take a back up of EVERYTHING ( be it any preferred method you use) . Once you have a backup of your complete phone please proceed to the next step by download the latest OOS 11 Full version( Not the OTA update).
Try updating your phone through Settings -> System Update.
Once the update is complete , Please make sure to reboot your phone to recovery mode once. Which should now be installed with Stock Recovery.
In some cases the stock recovery wipes everything on your phone and reboots.
If not you can wipe using the option Erase Everything including photos in memory.
Once the phone reboots and setup is complete. Reboot your phone once or twice.
The above step may sound weird but it helps you to identify any issue before next step.
MAKE SURE TO FOLLOW THE STEPS AS I HAVE STATED ELSE YOUR PHONE WILL END UP WITH CRASH DUMP MODE.
1.Make sure you have necessary ADB drivers installed on your PC.
2.Reboot your phone to Bootloader mode either by using command prompt or by pressing Volume + and Power key. (CMD : adb reboot bootloader )
3.Use Fastboot command to install the attached recovery file. Please do not use other TWRP files. ( CMD : Fastboot boot boot.img) ( boot.img is the file name attached).
4. The phone should reboot to TWRP recovery mode.
5. Under TWRP menu Navigate to Advanced -> Select Install Current TWRP.
6. The step should install your phone with TWRP on both slots.
7. Once install reboot your phone and check if OOS11 is still intact.
8. To verify if TWRP is installed as your recovery . Reboot your phone to recovery mode.
9. Once in recovery mode you can install the attached Magisk V23 apk using menu Install -> choose Magisk apk.
10. Reboot your phone and install Magisk using the same APK.
Viola you are all good to go if you have installed everything as mentioned.
Hope it helps now.
Click to expand...
Click to collapse
Wow, you've explained it in such great detail. Thank you, I'll try this approach and let you know how it goes.