After being stock on 10.0.19 forever, I finally decided to use the msm tool and update to 10.0.31 but I was wondering where I can find the stock boot image so that I can patch with magisk and root again.
I tried rooting using the magisk_patched from the 10.0.25 reserve restore tool but I lost access to wifi.
aryehzev said:
After being stock on 10.0.19 forever, I finally decided to use the msm tool and update to 10.0.31 but I was wondering where I can find the stock boot image so that I can patch with magisk and root again.
I tried rooting using the magisk_patched from the 10.0.25 reserve restore tool but I lost access to wifi.
Click to expand...
Click to collapse
Just extract it via adb using either the patched stock recovery or TWRP. Very simple and quick to do.
Related
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update
I have recently rooted my A3(2016) and have been using SuperSU, since i heard about Magisk i wanted to try and install it with TWRP but I have been getting error to restore Stock Boot Image. I've tried Fully Unrooting in SuperSU app but it says it can't restore Stock Boot Image. Is there anyway to acquire Stock boot image without flashing new firmware, since I don't want to lose data.
HisBrain said:
I have recently rooted my A3(2016) and have been using SuperSU, since i heard about Magisk i wanted to try and install it with TWRP but I have been getting error to restore Stock Boot Image. I've tried Fully Unrooting in SuperSU app but it says it can't restore Stock Boot Image. Is there anyway to acquire Stock boot image without flashing new firmware, since I don't want to lose data.
Click to expand...
Click to collapse
hi , extrat boot.img from your firmware and flash with twrp also magisk v14.0>>> reboot and wait .... good luck
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
Click to expand...
Click to collapse
SuperSU should have a uninstall file, try flashing that in twrp
Sent from my validus_athene using Tapatalk
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.[/Q
Flash a temporary rom and then install a stock recovery, and then boot back into stock rom by flashing stock image on pc
through fastboot mode
Click to expand...
Click to collapse
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
siddhesh9146 said:
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
Click to expand...
Click to collapse
Thank you so much. You saved my life right there.
Hi all
I am wondering if anyone knows how I can get my hands on OOS 9.0.11 Patched Boot Image.
I have honestly looked everywhere and the only one I could find was for OOS 9.0.7
I would like to use the boot image to install Magisk for root without a custom bootloader.
Thanks
anasbourini said:
Hi all
I am wondering if anyone knows how I can get my hands on OOS 9.0.11 Patched Boot Image.
I have honestly looked everywhere and the only one I could find was for OOS 9.0.7
I would like to use the boot image to install Magisk for root without a custom bootloader.
Thanks
Click to expand...
Click to collapse
You can temporarily boot TWRP and flash magisk. It's that simple..
anasbourini said:
Hi all
I am wondering if anyone knows how I can get my hands on OOS 9.0.11 Patched Boot Image.
I have honestly looked everywhere and the only one I could find was for OOS 9.0.7
I would like to use the boot image to install Magisk for root without a custom bootloader.
Thanks
Click to expand...
Click to collapse
Above method by @indian84 is using twrp boot image
1. fastboot boot twrp_boot_image
2. Download Magisk then sideload or install
or
Without twrp you need to patch stock boot.img yourself
1.Install MagiskManager
2. Dowload stock boot.img
https://drive.google.com/file/d/1U8LD1C84CVmv8CVQJgdwmZUsQqSE2m3s/view?usp=drivesdk
3. Patch stock boot.img with MagiskManager and you will get patch_boot.img then transfer it to your pc
5. phone - start fastboot mode
6. pc - fastboot flash boot patch_boot.img
7. pc - fastboot reboot
8. done
Thank you. Exactly what I was looking for.
If you use this method to convert TMobile to international software, could you them download the full international firmware and reflash and have OTA working then?
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..