I couldn't find any guide for rooting the V40, so I thought I'd write down the steps I took to root my new EUR V40 - LMV405EBW. Maybe it will help others. Sorry if this is somewhat confusing, I didn't have time to make a polished version. It's basically made from my notes during the process with the commands copied from bash history.
-First, unlock the bootloader following LG's instructions here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
There's no TWRP for the V40 and the one made for G7 doesn't work. I don't have the time and knowledge to even attempt to compile TWRP for the V40, so I proceeded with just patching an original boot image with Magisk.
You can get the patched boot images that I used from here:
Oreo 10e: boot_a_magisk_patched_10e.img
Oreo 20f: boot_a_magisk_patched_10f.img
Pie 20a: boot_a_magisk_patched_20a.img
Pie 20b: boot_a_magisk_patched_20b.img
Pie 20f: boot_a_magisk_patched_20f.img
Pie 20g: boot_a_magisk_patched_20g.img
Q 30b: boot_a_magisk_patched_30b.img (this requires flashing to the active boot partition).
Q 30c: boot_a_magisk_patched_30c.img (this requires flashing to the active boot partition)
Q 30d: boot_a_magisk_patched_30d.image (this may or may not work with "fastboot boot" and could require flashing to the active boot partition. I haven't tested if live boot still works. I just did fastboot flash boot_x img_file).
You can try to boot it with with fastboot if you have a LNV405EBW and skip the KDZ extraction part.
Installing Magisk:
Flashing this image isn't necessary, just straight boot should be sufficient and safe.
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
Code:
adb reboot bootloader
fastboot boot boot_a_magisk_patched_10e.img
After the phone boots the OS with the external boot image, open Magisk Manager and tap on Install. Select the option to Direct install to the active slot. I played it safe and decided to NOT flash also on the inactive slot. I've left it alone so I can use it in case of need of recovery.
You'll probably notice that you don't have a connection to the carrier. Just ignore it, it will back once the phone is booted normally.
Reboot and you will have permanent root until you switch the A/B slots.
In case my patched boot image doesn't work, you can just make your own.
Tools needed:
Magisk Manager 7.0.0 installed on the phone
LG Bridge installed on a Windows machine.
a Linux machine or VM (I used the latest ubuntu desktop), python3 with the zstandard module installed and kdztools from steadfasterX's repo. Maybe kdztools would work on Windows too, I haven't tried it.
adb, fastboot
You need to procure an original ROM file for your phone model. It can be downloaded easily with LG Bridge. Just connect the phone to a Windows PC, start LG bridge, go to the Software update tab and click on Update error recovery. Wait for the download to start and disconnect the phone. Ignore LG Bridge complains about not being able to flash after the downloading stage is completed. Don't click anything in Bridge and before closing it go to C:\Users\<your_username>\AppData\Local\LG Electronics\LG Bridge\SWUpgrade and copy your KDZ somewhere else. Preferably send it to the Linux VM to the LG work folder, it'll be needed there.
On Linux open a terminal:
Code:
cd ~/Documents
mkdir LG
cd LG
git clone https://github.com/steadfasterX/kdztools.git
cd kdztools
nano undz.py -c
For kdztools to be able to extract the V40 images, I needed to edit undz.py and comment the lines 88-90. So, this block should all be commented or undz will fail to extract the boot partitions.
Code:
#if len(dz_item['pad']) != 0:
# print("[!] Error: pad is not empty", file=sys.stderr)
# sys.exit(1)
To extract, with the KDZ copied to ~/Documents/LG/
Code:
cd ~/Documents/LG/kdztools
./unkdz.py -f ../V405EBW10e_00_OPEN_EU_DS_OP_0109.kdz -x
cd kdzextracted/
List the partitions contents and look for the IDs of boot_a and/or boot_b. In my case they were 44 for boot_a and 63 for boot_b
Code:
../undz.py -f V40510e_00.dz -l
Extract boot_a or boot_b or both, they're identical:
Code:
../undz.py -f V40510e_00.dz -s 44
../undz.py -f V40510e_00.dz -s 63
You can find the extracted boot images in the dzextracted subfolder. Get boot_a.image or boot_b.image or both from there and send them to the phone in a location accessible by Magisk Manager. The Download folder should do fine.
Open Magisk Manager and tap Install, select Patch Boot Image file and patch the image file(s) you extracted. Get the patched_boot.img that Magisk Manager saves in the Download folder and send it to a PC where you have adb and fastboot.
Go to the beginning of the post to the Installing Magisk section.
Damned tempting, but I'll wait until after Pie drops.
Sent from my LM-V405 using Tapatalk
Glad to see this, hopefully it's a start for all of us.
If anything, at least a way to unlock the bootloader via legitimate channels! Gonna be generating that string, next chance I get, to be ready.
Sent from my LM-V405 using Tapatalk
Once runningnak3d gets a hold of this, we should be good with the v40. Cool beans.
Hey do the unlock codes online work for $ 12-15 on sprint? I used to flash phones back in the day and got a great deal on a bad IMEI sprint lg v40, but so far I can see there isn’t a way yet. On top off all that I m in Europe and don’t want to get the error message that I m out of the Region. I would have to go to USA just to unlock the phone.
@runningnak3d
Can't I install the firmware on a different device?
V version can not unlock BL, so envious
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
LameMonster82 said:
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
Click to expand...
Click to collapse
Or I could find you stupid for not noticing the patched image is in my first post.
DLS123 said:
I find you stupid for not noticing the patched images are in my first post.
Click to expand...
Click to collapse
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
LameMonster82 said:
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
Click to expand...
Click to collapse
I mentioned in the description 1 line below the link that it's for 10e. There was no other update in a long time. I don't think there can be any confusion for now. I can edit and label the file when there's will be another fw update.
It looks like unlocking the bootloader breaks Widevine L1 on the V40 and downgrades is to L3. No more HD or UHD Netflix.
I couldn't find any other solution than to re-lock the bootloader to restore L1.
This doesn't happen on the V30.
@DLS123
Thank you for all!
I ask you for more details; i'm stuck at flashing first image in adb; it returns an error; have LMV405EBW with 10f. unlocked bootloader of course
Thx again for your support!
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
i suppose is something wrong in this instructions.
daphix said:
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
Anyway; understand now what to do;
Steps are below:
- first install magisk manager
- download magisk zip from magisk site or from magisk manager himself on phone
- download patched_boot_a.img to phone from our good contributor
- use magisk manager and select inslall image of patched_boot_a.img from phone
- magisk manager will generate a magisk patched image
- transfer this magisk patched image (not patched_boot_a.img) to pc in ADB folder
- flash with Adb this magisk patched image from pc to phone.
Thx to our friend!
---------- Post added at 09:53 AM ---------- Previous post was at 09:21 AM ----------
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Hi;
using Magisk mamanger and your file was generated a file: magisk_patched.img
pls support; trying to flash that image from PC with adb not work:
fastboot flash partition_a magisk_patched.img
Click to expand...
Click to collapse
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
DLS123 said:
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
Click to expand...
Click to collapse
Hi , thank you for reply;
I tried many combinations of your commands;
maybe due that am noob, but succesion below simply is not working:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
Related
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813
Thanks. Looks like I have plans for NYE
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.
Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.
Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.
Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.
Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.
I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please
andienchancer said:
I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please
Click to expand...
Click to collapse
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
It gives me bootloop, can I do it flashing twrp and the zip file?
reserved
Moto E5 XT1944-3 Nora solution
andienchancer said:
It gives me bootloop, can I do it flashing twrp and the zip file?
Click to expand...
Click to collapse
i can find solution in this post, just install twrp until, password encryption dont show.
LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
I can confirm that the procedure works for Moto E5 Play XT1920-18.
Anyone noticed that can't root with magisk the p20 pro or it just me?
Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!
sarichter said:
Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!
Click to expand...
Click to collapse
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
Thank you so much! Do you have any idea where I can get the OTA or at least figure out in specificity which OTA on Firmware Finder is correct? It sounds like it needs to be 100% exact to avoid issues / bricking.
---------- Post added at 03:12 PM ---------- Previous post was at 02:18 PM ----------
purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
OK... so I was able to extract the RAMDISK.IMG file but I can't patch it because Magisk Manager hangs after I install it. Is there a way to patch the RAMDISK.IMG file manually or via PC?
OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
sarichter said:
OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
Click to expand...
Click to collapse
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.
purple patch said:
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.
Click to expand...
Click to collapse
People struggle because the firmware is from 100 different regions, all with different release dates, there is no official TWRP that works 100% correctly with encryption, and Magisk changed the standard install method. I'm not surprised that people are having a tough time figuring out what to do so they don't brick their phone. This thing isn't cheap!
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...
maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks
I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!
By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)
So, if like me, you ended up buying the Redmi Note 10S because it was very cheap (it's something like 200$ for a really good phone) and then just hopped on to xda forums for the latest roms and stuff, you'll find that not much development is going on regarding this phone, understandably because of "better" alternatives within the same line-up.
As a consequence, we don't yet have TWRP or CWM or any such custom recoveries built for this specific device (Redmi Note 10S) nor do I think they're coming any time soon, which is unfortunate since that would have made the process a tad bit more convenient. We don't have any custom roms built specifically for our device either (although we can probably use GSI roms)
So we'll now try to do the process ourselves.
Now, for the disclaimer:
DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....knowledgeable to weigh in his/her opinions. If you end up bricking your phone or if things go wrong, I'm not responsible, that's on you.
Also, please read the entire guide first and then begin.
Alright, with the appetizers out of the way, let's just crack on to the main course:
STEP-0: Requirements:
Redmi Note 10S
Install OEM fastboot drivers
Obtain android platform-tools along with knowledge about how to use it
Your Bootloader should be unlocked (wait for 1 week after first attempt at unlocking after which you'll receive your "permission")
Fastboot rom from here
Magisk apk
Being ready to lose your data (in short, don't personalize your phone just yet (....and also take a backup of everything)) and accept that you'll have SafetyNet related issues until you do some other special stuff
Enable Developer mode and USB debugging
STEP-1: Obtain boot.img (and vbmeta.img)
What we need is a boot.img that we can patch using magisk. We can do some code-fu to pull it from the phone but we don't need to do that. We can instead obtain the fastboot rom from here (I don't think region matters but take accordingly just to stay safe). While downloading, you'll see that what you're downloading a zip. This is intended because the boot.img (and the vbmeta.img) is within this zip file.
Anyways, once you download it, unzip all of the contents into a folder and move on to the next step.
STEP-2: Patch the obtained boot.img:
Take the boot.img from the zip file you obtained earlier and move it into the internal storage of your phone. Install the Magisk Manager apk from here. Install the apk and then after opening, go straight to installing Magisk, then select "Select and Patch a File" and then select the boot.img that you moved into the internal storage. It will then start patching the boot.img after which it will generate a patched boot.img, the directory of which is mentioned at the end of the patching process.
Move the patched boot.img back into your computer and move on to the next step.
STEP-3: Flash the patched boot.img:
Alright, this is the final leg of the journey (or should I say, desserts?).
Keep the vbmeta.img and the patched boot.img handy as you will be needing them here. You can find the vbmeta.img in the zip file you extracted earlier in the guide.
NOTE: The vbmeta.img is especially important because if you don't flash this while disabling verity and verification, you'll be stuck in a bootloop until you flash the stock boot.img (the boot.img before you patched it) back because this.
Alright, with all of that at hand, boot your phone into fastboot mode.
Now disable what is equivalent to the windows version of secure boot:
Code:
fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
And then the following command that will finish it off:
Code:
fastboot.exe flash boot patched_boot.img
If you get stuck in a bootloop (perhaps because incorrectly flashing vbmeta.img or anything else), flash the stock boot.img with the same command and try the process again
And then finally for the cherry on top:
Code:
fastboot.exe reboot
After all that is done, hopefully you will see the setup for MIUI. Complete it as you normally would, and after the setup, you will find the magisk manager preinstalled but it will have the placeholder android app logo. Open that and it will prompt you to complete the download and installation of magisk manager. Do that and then open magisk manager (at this point it will have the familiar logo), go straight to installing Magisk and then select Direct Install (Recommended) and then let it do its thing.
After that, it will prompt you to restart your device to complete some stuff at which point you have successfully rooted your phone.
Aftermath:
I would like to remind you that SafetyNet will fail, even if you enable MagiskHide. You will have to do some other stuff to fix that if you want to use stuff like Google Pay so if that is a deal breaker, I suggest you don't follow this guide yet until some recommendations regarding SafetyNet pop up in this thread (or if you find some stuff elsewhere (please do let me know)).
Weirdly the Widevine rating is still at L1 according to DRM Info so I guess Netflix and other stuff will work fine(?). I don't use netflix or prime video so I can't help you there.
Concluding:
If there is anything step I have missed out or some issues you're facing, please let me know within this thread. I'll be happy to resolve the issue. If there are any recommendations regarding SafetyNet or any recommendations in general, I'll be happy to listen.
EDIT 1: You can't use Netflix because you won't be able to find it in Google Play Store.
EDIT 2: You can use Netflix and other DRM protected applications by installing the following Magisk Modules:
Riru (This is required by the next one)
Universal SafetyNet Fix (To pass SafetyNet ctsProfile evaluation)
MagiskHide Props Config (!!MOST IMPORTANT!!) (To get fingerprint certificates and pass other authentication related stuff)
Of course, as is with software, this stuff may eventually be patched by google or netflix so you should still refrain from using this guide (or rooting in general) if you don't want to deal with the hiccups down the road.
Certification is still L1 (weirdly) after installation of the modules and you will now be able to find Netflix in the store.
EDIT 3: Edited the guide after @murigny64 's reply (Thanks!)
Hello
No need to flash both A and B,
you can use "fastboot flash boot patched_boot.img", it will flash active system branch
because "boot" is a "partition_by_name" and symlinked to active partition (boot_a or boot_b)
I can flash Boot & VBmeta without issues but "--disable-verity --disable-verification flash vbmeta vbmeta.img" command just does not work. I got vbmeta.img from original device image & i have tried all kind of versions of command "fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img". Flasching VBmeta vorks but then i guess i would need spesific modified image file where it is disabled already. Any advice?
flashing vbmeta does result in an error and boot loop.
Error: unknown option -- diable-verity
Okay it seems like my phone has been sort of rooted but not completely. When I tried to edit my build.prop (to disable MiraVision), it resulted in the entire build.prop being wiped completely.
Thanks for sharing
Anyone got Google Pay working after installing Magisk and Universal Safety Net Fix ?
Exb22 said:
I can flash Boot & VBmeta without issues but "--disable-verity --disable-verification flash vbmeta vbmeta.img" command just does not work. I got vbmeta.img from original device image & i have tried all kind of versions of command "fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img". Flasching VBmeta vorks but then i guess i would need spesific modified image file where it is disabled already. Any advice?
Click to expand...
Click to collapse
sengottuvel said:
flashing vbmeta does result in an error and boot loop.
Error: unknown option -- diable-verity
Click to expand...
Click to collapse
Use a command prompt, not windows powershell.
stuntdouble said:
Use a command prompt, not windows powershell.
Click to expand...
Click to collapse
I shall try what you said. And get back to you.
sengottuvel said:
I shall try what you said. And get back to you.
Click to expand...
Click to collapse
same issue. Even cmd did not work. what am I doing wrong?
Can you please outline the steps? perhaps I am missing something by mistake.
You haven't followed the guide above, you've sent the commands in the wrong order. If you have done it in the right order previously then your adb version is maybe out of date so follow this guide and try again:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
stuntdouble said:
You haven't followed the guide above, you've sent the commands in the wrong order. If you have done it in the right order previously then your adb version is maybe out of date so follow this guide and try again:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
Could you please tell me the right order in which the two command lines have to be entered?
I was able to successfully entered the two lines in the below order,
fastboot flash boot path to patched boot image
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
I am now seeing MIUI logo for more than 10 minutes. I am not sure if this waiting time is normal?
Could I try replacing the second line with fastboot flash vbmeta path to vbmeta image?
Your help will be highly appreciated.
In the exact same order as RandomAccessVemuri has kindly posted for us all in their guide above. The vbmeta file first then the boot.img. If everything is done to the letter then there's no reason it shouldn't work on your device.
It looks like you're trying to format one of the partitions after modifying the boot.img, that's the wrong way around, so yeah that's going to stop it from booting. And when the commands take it should take seconds, then on rebooting using the fastboot command it should load up in a normal time.
RandomAccessVemuri said:
By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)
So, if like me, you ended up buying the Redmi Note 10S because it was very cheap (it's something like 200$ for a really good phone) and then just hopped on to xda forums for the latest roms and stuff, you'll find that not much development is going on regarding this phone, understandably because of "better" alternatives within the same line-up.
As a consequence, we don't yet have TWRP or CWM or any such custom recoveries built for this specific device (Redmi Note 10S) nor do I think they're coming any time soon, which is unfortunate since that would have made the process a tad bit more convenient. We don't have any custom roms built specifically for our device either (although we can probably use GSI roms)
So we'll now try to do the process ourselves.
Now, for the disclaimer:
DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....knowledgeable to weigh in his/her opinions. If you end up bricking your phone or if things go wrong, I'm not responsible, that's on you.
Also, please read the entire guide first and then begin.
Alright, with the appetizers out of the way, let's just crack on to the main course:
STEP-0: Requirements:
Redmi Note 10S
Install OEM fastboot drivers
Obtain android platform-tools along with knowledge about how to use it
Your Bootloader should be unlocked (wait for 1 week after first attempt at unlocking after which you'll receive your "permission")
Fastboot rom from here
Magisk apk
Being ready to lose your data (in short, don't personalize your phone just yet (....and also take a backup of everything)) and accept that you'll have SafetyNet related issues until you do some other special stuff
Enable Developer mode and USB debugging
STEP-1: Obtain boot.img (and vbmeta.img)
What we need is a boot.img that we can patch using magisk. We can do some code-fu to pull it from the phone but we don't need to do that. We can instead obtain the fastboot rom from here (I don't think region matters but take accordingly just to stay safe). While downloading, you'll see that what you're downloading a zip. This is intended because the boot.img (and the vbmeta.img) is within this zip file.
Anyways, once you download it, unzip all of the contents into a folder and move on to the next step.
STEP-2: Patch the obtained boot.img:
Take the boot.img from the zip file you obtained earlier and move it into the internal storage of your phone. Install the Magisk Manager apk from here. Install the apk and then after opening, go straight to installing Magisk, then select "Select and Patch a File" and then select the boot.img that you moved into the internal storage. It will then start patching the boot.img after which it will generate a patched boot.img, the directory of which is mentioned at the end of the patching process.
Move the patched boot.img back into your computer and move on to the next step.
STEP-3: Flash the patched boot.img:
Alright, this is the final leg of the journey (or should I say, desserts?).
Keep the vbmeta.img and the patched boot.img handy as you will be needing them here. You can find the vbmeta.img in the zip file you extracted earlier in the guide.
NOTE: The vbmeta.img is especially important because if you don't flash this while disabling verity and verification, you'll be stuck in a bootloop until you flash the stock boot.img (the boot.img before you patched it) back because this.
Alright, with all of that at hand, boot your phone into fastboot mode.
Now disable what is equivalent to the windows version of secure boot:
Code:
fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
And then the following command that will finish it off:
Code:
fastboot.exe flash boot patched_boot.img
If you get stuck in a bootloop (perhaps because incorrectly flashing vbmeta.img or anything else), flash the stock boot.img with the same command and try the process again
And then finally for the cherry on top:
Code:
fastboot.exe reboot
After all that is done, hopefully you will see the setup for MIUI. Complete it as you normally would, and after the setup, you will find the magisk manager preinstalled but it will have the placeholder android app logo. Open that and it will prompt you to complete the download and installation of magisk manager. Do that and then open magisk manager (at this point it will have the familiar logo), go straight to installing Magisk and then select Direct Install (Recommended) and then let it do its thing.
After that, it will prompt you to restart your device to complete some stuff at which point you have successfully rooted your phone.
Aftermath:
I would like to remind you that SafetyNet will fail, even if you enable MagiskHide. You will have to do some other stuff to fix that if you want to use stuff like Google Pay so if that is a deal breaker, I suggest you don't follow this guide yet until some recommendations regarding SafetyNet pop up in this thread (or if you find some stuff elsewhere (please do let me know)).
Weirdly the Widevine rating is still at L1 according to DRM Info so I guess Netflix and other stuff will work fine(?). I don't use netflix or prime video so I can't help you there.
Concluding:
If there is anything step I have missed out or some issues you're facing, please let me know within this thread. I'll be happy to resolve the issue. If there are any recommendations regarding SafetyNet or any recommendations in general, I'll be happy to listen.
EDIT 1: You can't use Netflix because you won't be able to find it in Google Play Store.
EDIT 2: You can use Netflix and other DRM protected applications by installing the following Magisk Modules:
Riru (This is required by the next one)
Universal SafetyNet Fix (To pass SafetyNet ctsProfile evaluation)
MagiskHide Props Config (!!MOST IMPORTANT!!) (To get fingerprint certificates and pass other authentication related stuff)
Of course, as is with software, this stuff may eventually be patched by google or netflix so you should still refrain from using this guide (or rooting in general) if you don't want to deal with the hiccups down the road.
Certification is still L1 (weirdly) after installation of the modules and you will now be able to find Netflix in the store.
EDIT 3: Edited the guide after @murigny64 's reply (Thanks!)
Click to expand...
Click to collapse
Hello,
I have done a factory reset to my phone and I lost something very important so is it possible to get back to the previous version of the phone before the reset or should I give up
And thanks for your answer
Hello, I have the same phone as u. I wanted to unlock my bootloader and I tried like every tutorial on Youtube and other websites i could found but none of them worked out for me. this ****ty outdatet program of xiaomi just dont recognize my phone. Pleaaase tell me how u did it
Is it possible to don't wipe userdata ? Maybe using flash_all_except_data_storage.bat ?
There is some options to set before root ? On some other tutorials they tell to turn off MIUI optimization for example
Gg
I want to root my phone but I am scared I hard brick it because I did it before but I was still under warranty and I somehow locked the bootloader so should I give it another shot or just forget it?
Flameagle2021 said:
I want to root my phone but I am scared I hard brick it because I did it before but I was still under warranty and I somehow locked the bootloader so should I give it another shot or just forget it?
Click to expand...
Click to collapse
if you read all the instrucctions you wont hard brick your device
Does it work using an different android version than the boot.img file i extracted it from, since i often switch android versions with gsis and so on. (e.g android 11 boot.img with android 13 gsi?)