Related
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
guys please give me noob friendly instructions for installing magisk latest ver on my lenovo p2 15.1 latest build .
Same
First make sure you have USB debugging enabled on your phone, then install ADB on your PC. Connect the phone to the PC and in the installation folder (ADB > platform-tools) shift right click and choose Open command window here. Type adb devices and authorize your PC on the phone. Download the ROM and extract boot.img from it, transfer it to your phone. On the phone install Magisk Manager and patch the boot.img (Install > Patch boot image). Transfer patched_boot.img back onto the PC (to the ADB > platform-tools folder), then boot your phone into fastboot (VOL down and POWER buttons). Repeat the Open command window here step and type fastboot flash boot patched_boot.img. Reboot your phone (fastboot reboot). You are now rooted on custom ROM.
After installing magisk , do I need to install any module to prevent boot loop like f2fs loop module etc .
Check if you can install modules. If you're facing problems, then you will need to change a few things. The "cannot mount magisk_merge.img" issue for example can be solved by patching and flashing boot image from here https://forum.xda-developers.com/lenovo-p2/development/kernel-f2fs-upstreamed-kernel-twrp-t3845976. I tried tinkering with modules for it and ended up bricking my phone. I would also recommend using TWRP from this thread, it got rid of my second problem (which I now forgot).
Just remember that you will need to flash the patched custom kernel after any ROM update.
I saw a lot of outdated methods of rooting this phone that will cause a lot of bugs to the device, because of the outdate magisk_patched boot image
HERE'S AN UPDATED VERSION
REQUIREMENTS
Unlocked bootloader
Minimal ADB + Fastboot ( I use 1.4.3 PORTABLE) https://forum.xda-developers.com/showthread.php?t=2317790
Pack with required images, including the new magisk_patched.img (required_files.zip, at the bottom of the post)
INSTRUCTIONS
Extract both the minimal adb + fastboot and required_files.zip to a folder
Boot your device in fastboot mode (power if off, then press power button + volume down until you see a bunny working on a Android robot)
Connect the device to the PC via a USB cable (I suggest the one you use of the charger too)
Copy the images from required_files.zip to the folder where you extracted minimal adb + fastboot
Open a cmd/powershell window in minimal adb + fastboot folder (make sure once again that you copied the files from required_files here)
Type these commands:
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
Enjoy! Your phone will reboot (it shouldn't take more than usual btw)
WARNING!
I'm not responsable for any damaaged device, you take the risk
What I basically did is gave you guys an updated magisk_patched image because the the one seen on the internet for now is an old one that caused several problems on some devices, if you're running any other version that the one in the title you should make your own magisk_patched image
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
alpersoft said:
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
Click to expand...
Click to collapse
I removed the erase data line cuz I didn't saw why it would be required since it was working great without it
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
HemanthJabalpuri said:
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
Click to expand...
Click to collapse
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Successfully rooted + edXposed on STOCK rom and GSI roms.
Patched my own boot image (magisk_patched.img) with magisk manager.
To make Netflix & some other apps work, get the liboemcrypto disabler module in Magisk Manager
Also, to pass SafetyNet:
- Enable Magisk Hide
- Install and activate the Riru - Core and Riru - EdXposed (YAHFA or SANDHOOK, both work) modules in magisk manager
- Get EdXposed manager
- Get the HiddenCore Module and activate it
- In EdXposed Manager: Compat List, and tick HiddenCore Module
To avoid issues (Chrome crashes, potential SIM issues, etc..) with HiddenCore:
- In EdXposed Manager, go to Settings > Framework > Enable "App List mode"
- Still in EdXposed Manager, go to Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Play Store, Google Services Framework
- Reboot and enjoy, you're all set and SafetyNet should pass just fine, and you can do whatever you want.
i have question: vbmeta.img above can be used for all versions of miui or only ver 12.0.2
i am using ver 12.0.3 eea
Pls help not working 12.0.3
tanks
I have patched the image with magisk manager
ma259 said:
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Click to expand...
Click to collapse
can i download your vbmeta and work for 12.0.4? maybe? yes? no?
New member here! Will this work also on miui 12.0.5 global?
I have not installed root and the phone is not restored
What is working for MERLIN ?
Take a look: https://forum.xda-developers.com/t/...aomi-redmi-note-9-xiaomi-redmi-10x-4g.4204873
V11.0.5.0:
MAGISK: Working.
MAGISK MANAGER: Working.
TWRP: Working.
RIRU-CORE: Working.
RIRU-EDXPOSED: Working.
EDXPOSED-MANAGER: Working.
XPRIVACYLUA: Working.
MINMINGUARD: Not tested yet.
TITANIUMBACKUP: Not tested yet.
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
accnetdev said:
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
Click to expand...
Click to collapse
same here
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.
Hello
I've just ordered my Pixel 6 Pro, coming from the OnePlus 8 Pro.
I love tinkering with Root/Kernels/Roms.
So my question is, if there is always a way to get back to stock in case of emergency?
The OnePlus phones are considered as "unbreakable", because You can ALWAYS unbrick it via MSM unbrick tool.
Would be nice to know when I start unlocking the bootloader of my Pixel
Thanks!
Sorry that Pixel doesn't have that unbrick tool ...
The only one is a batch commend file - Flash-All extracted from factory full ROM ...
It is possible to hardbrick a Pixel device without hopes of getting it running again, for example if you nuke your recovery.
Most softbricks can be solved by either doing what Kris Chen suggested, or by using
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
After flashing a module that bootloops you can try this:
If it almost boots up but flashes, in a cmd window type:
adb wait-for-device shell magisk --remove-modules
It may grab that and remove all modules. If it doesn't, you can try this:
1. fastboot flash boot boot.img, reboot.
2. long press power button, then long press "power off", click ok to enter safemode.
3. Before your phone boots all the way up, boot to fastboot.
4. fastboot flash boot magisk_patched.img, reboot.
5. In cmd window type: adb wait-for-device shell magisk --remove-modules
6. Your phone will boot up with root and all modules removed.
There's a shortcut to safemode that removes everything but I'm not sure what it is.
Edit: boot.img is taken from the applicable firmware you are on downloaded from Google. Unzip the main zip, go into the folder and unzip the image zip that is inside.
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Lycidias said:
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Click to expand...
Click to collapse
Yes, correct, and yes, safest to do so each time switching kernels.