Related
I found a Method how to root the OT-995.
1. Activate the Developer Options
2. Connect the OT-995 via USB to your Computer
3. Install the Driver (if you haven't it )
4. Copy the root file (e.g. Update.zip) to your the folder of your SD-Card
5. Boot your OT via ADB in Fastboot (Adb reboot fastboot)
6. Download the newst ClockworkMod.img and flash it via Fastboot (fastboot flash recovery *the folder of the recovery.img*
7. Try "fastboot recovery"
8. Now ure in the Recovery Mode. Flash the root file (update.zip)
9. Reboot
10. Finish.
Sorry for my bad english, i'm only 16
Sent from my HTC Desire using XDA Free mobile app
Lenovo Phab PB1-750M 6.0.1 Marshmallow
Before anything else, make backup.
*UPDATED "Drivers" link: (June 17, 2023)
What's in the guide?
(A) Rooting
(B) Installing TWRP custom recovery
(C) Installing Xposed framework
Firmware:
These are full OTA. Install via recovery. Latest is PB1-750M_S000675_170107_ROW. Links from this forum.
PB1-750M_S000675_170107_ROW
PB1-750M_S000660_160930_ROW
***Some users (including me) had encountered an error ("Permission denied") on OTA update PB1-750M_S000660_160930_ROW_TO_PB1-750M_S000675_170107_ROW. If you can't update to the latest, just install the PB1-750M_S000675_170107_ROW full OTA.
Requirements:
(a) Driver. This should be installed by your device and can be found on CD Drive when you connect your device. Install "LenovoUsbDriver_autorun_1.1.30_user.exe" found on the link.
(b) Latest ADB and Fastboot (I recommend Minimal ADB and Fastboot).
(c) Download SevenMaxx TWRP image. Thanks estanenmi for the link.
(d) Download SuperSU binaries. This is v2.68. You could try the latest or just update it after successful install.
(e) Unlock the bootloader. On your device, go to Settings > Developer Options > Allow OEM Unlocking. Then reboot into bootloader via terminal/cmd: adb reboot bootloader. When in fastboot mode, type in terminal/cmd: fastboot oem unlock-go.
***fastboot oem unlock-go will restore the device to factory settings.
Rooting:
(a) Place the TWRP image on the root directory of Minimal ADB and Fastboot (or where your adb and fastboot is located)
(b) Copy the SuperSU zip file on your device
(c) Go to terminal/cmd: adb reboot bootloader
****You can also go to fastboot via "volume down + power" buttons.
(d) Go to terminal/cmd: fastboot boot twrp.img
****If you have flashed a custom recovery, you can install via recovery. The code above just temporarily boot the TWRP image.
(e) Then: fastboot reboot
(f) Navigate the TWRP. I strongly suggest to make a "backup" first.
(g) In TWRP, go to "Install" > locate and select the SuperSU.zip. Swipe to confirm.
(h) Reboot after installation. Your device may reboot a few times.
(i) Download root checker to verify.
*SuperSU app may update and may require to update su binaries.
*If SuperSU installation fails, boot the TWRP.img again and restore (if you have created a backup ).
*You could try installing the SuperSU listed above if your device is on bootloop due to unsuccessful rooting (worked for me).
*I haven't looked for possible problems pre and post rooting - always do backup.
Screenshot
Installing TWRP (custom recovery):
I haven't found any official custom recovery for this device. The custom recovery TWRP by SevenMaxx (from a russian forum) works. (install at your own risk). You can install the custom recovery via fastboot.
****If you only need root access, I suggest that you temporarily boot the TWRP to install SuperSU. It's better to wait for the official custom recovery for the device.
(a) First, the device's bootloader must be unlocked. Check the requirements on how to unlock bootloader.
(b) Configure your device again and enable USB debugging and OEM unlocking.
(d) Go to terminal/cmd: adb reboot bootloader
(e) Then: fastboot flash recovery twrp.img
(f) Device will reboot.
(g) Check the new recovery options via (1) Volume Up + Power button; or (2) adb reboot recovery
Installing Xposed framework (manual):
Please check the official thread for xposed on LL/MM. The device has an ARM architecture and is running on android 6.0.1 (sdk23). Download the latest xposed framework (.zip) here (current latest v87) and xposed installer (.apk) here.
(a) Your device must have root access. Follow the guide on how to root the device.
(b) Install the Xposed (.apk). ***You can install the framework via the Xposed app.
(c) Copy the *.zip file on your device.
(d) Boot your device into recovery (im using the TWRP used in this guide) and install the xposed *.zip.
(e) Reboot. On startup ("Android is starting" message), the device will "optimize applications" and could take a long time.
(f) Check the xposed app download some modules.
step d failed
at cmd after entering the command, its say failed remote, unlock the device first to use this command.
yumark said:
at cmd after entering the command, its say failed remote, unlock the device first to use this command.
Click to expand...
Click to collapse
Hello there. You need to unlock the bootloader first. On your device, go to settings > developer options > Allow OEM unlocking. Reboot your device into fastboot, then on terminal/cmd: fastboot oem unlock-go. Just follow the steps (a) to (b) in Installing TWRP.
thanks sir
rolland.arriza said:
Hello there. You need to unlock the bootloader first. On your device, go to settings > developer options > Allow OEM unlocking. Reboot your device into fastboot, then on terminal/cmd: fastboot oem unlock-go. Just follow the steps (a) to (b) in Installing TWRP.
Click to expand...
Click to collapse
done installing twrp.img , now rooting method?
yumark said:
done installing twrp.img , now rooting method?
Click to expand...
Click to collapse
Just follow the rooting guide after you have unlocked the bootloader. Goodluck.
wow, done rooting thanks a lot, keep it up all the goo wrok XDA i salute this site.
yumark said:
done installing twrp.img , now rooting method?
Click to expand...
Click to collapse
thank you very much now i can increased my 1 gb ram sorry for the misspelled XDA,
How about xposed?
thanks for the guide! worked right away.
yep, better wait for the official custom recovery, all i have to do now is also wait for an official custom rom to come out
Please somebody helps me!
Please someone can upload a "backup image" from TWRP so i can use it for "restore" mi device.
My device now is blicked and i can not use QFIL for restore because in the "restoration procces" of QFIL always says:
"Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode"
I hope someone can helpme uploading this file
Thanks
thank you
rolland.arriza said:
Rooting Lenovo Phab PB1-750M (Android 6.0.1)
Before anything else, make backup.
Requirements:
(a) Driver. This should be installed by your device and can be found on CD Drive when you connect your device. Install "LenovoUsbDriver_autorun_1.1.30_user.exe" found on the link.
(b) Latest ADB and Fastboot (I recommend Minimal ADB and Fastboot).
(c) Download SevenMaxx TWRP image. Thanks estanenmi for the link.
(d) Download SuperSU binaries. This is v2.68. You could try the latest or just update it after successful install.
(e) Unlock the bootloader. On your device, go to Settings > Developer Options > Allow OEM Unlocking. Then reboot into bootloader via terminal/cmd: adb reboot bootloader. When in fastboot mode, type in terminal/cmd: fastboot oem unlock-go.
***fastboot oem unlock-go will restore the device to factory settings.
Rooting:
(a) Place the TWRP image on the root directory of Minimal ADB and Fastboot (or where your adb and fastboot is located)
(b) Copy the SuperSU zip file on your device
(c) Go to terminal/cmd: adb reboot bootloader
****You can also go to fastboot via "volume down + power" buttons.
(d) Go to terminal/cmd: fastboot boot twrp.img
****If you have flashed a custom recovery, you can install via recovery. The code above just temporarily boot the TWRP image.
(e) Then: fastboot reboot
(f) Navigate the TWRP. I strongly suggest to make a "backup" first.
(g) In TWRP, go to "Install" > locate and select the SuperSU.zip. Swipe to confirm.
(h) Reboot after installation. Your device may reboot a few times.
(i) Download root checker to verify.
*SuperSU app may update and may require to update su binaries.
*If SuperSU installation fails, boot the TWRP.img again and restore (if you have created a backup ).
*You could try installing the SuperSU listed above if your device is on bootloop due to unsuccessful rooting (worked for me).
*I haven't looked for possible problems pre and post rooting - always do backup.
Screenshot
Installing TWRP (custom recovery)
I haven't found any official custom recovery for this device. The custom recovery TWRP by SevenMaxx (from a russian forum) works. (install at your own risk). You can install the custom recovery via fastboot.
****If you only need root access, I suggest that you temporarily boot the TWRP to install SuperSU. It's better to wait for the official custom recovery for the device.
(a) First, the device's bootloader must be unlocked. Check the requirements on how to unlock bootloader.
(b) Configure your device again and enable USB debugging and OEM unlocking.
(d) Go to terminal/cmd: adb reboot bootloader
(e) Then: fastboot flash recovery twrp.img
(f) Device will reboot.
(g) Check the new recovery options via (1) Volume Up + Power button; or (2) adb reboot recovery
Click to expand...
Click to collapse
:good::good::good::good::good:
rolland.arriza said:
Rooting Lenovo Phab PB1-750M (Android 6.0.1)
Before anything else, make backup.
Requirements:
(a) Driver. This should be installed by your device and can be found on CD Drive when you connect your device. Install "LenovoUsbDriver_autorun_1.1.30_user.exe" found on the link.
(b) Latest ADB and Fastboot (I recommend Minimal ADB and Fastboot).
(c) Download SevenMaxx TWRP image. Thanks estanenmi for the link.
(d) Download SuperSU binaries. This is v2.68. You could try the latest or just update it after successful install.
(e) Unlock the bootloader. On your device, go to Settings > Developer Options > Allow OEM Unlocking. Then reboot into bootloader via terminal/cmd: adb reboot bootloader. When in fastboot mode, type in terminal/cmd: fastboot oem unlock-go.
***fastboot oem unlock-go will restore the device to factory settings.
Rooting:
(a) Place the TWRP image on the root directory of Minimal ADB and Fastboot (or where your adb and fastboot is located)
(b) Copy the SuperSU zip file on your device
(c) Go to terminal/cmd: adb reboot bootloader
****You can also go to fastboot via "volume down + power" buttons.
(d) Go to terminal/cmd: fastboot boot twrp.img
****If you have flashed a custom recovery, you can install via recovery. The code above just temporarily boot the TWRP image.
(e) Then: fastboot reboot
(f) Navigate the TWRP. I strongly suggest to make a "backup" first.
(g) In TWRP, go to "Install" > locate and select the SuperSU.zip. Swipe to confirm.
(h) Reboot after installation. Your device may reboot a few times.
(i) Download root checker to verify.
*SuperSU app may update and may require to update su binaries.
*If SuperSU installation fails, boot the TWRP.img again and restore (if you have created a backup ).
*You could try installing the SuperSU listed above if your device is on bootloop due to unsuccessful rooting (worked for me).
*I haven't looked for possible problems pre and post rooting - always do backup.
Screenshot
Installing TWRP (custom recovery)
I haven't found any official custom recovery for this device. The custom recovery TWRP by SevenMaxx (from a russian forum) works. (install at your own risk). You can install the custom recovery via fastboot.
****If you only need root access, I suggest that you temporarily boot the TWRP to install SuperSU. It's better to wait for the official custom recovery for the device.
(a) First, the device's bootloader must be unlocked. Check the requirements on how to unlock bootloader.
(b) Configure your device again and enable USB debugging and OEM unlocking.
(d) Go to terminal/cmd: adb reboot bootloader
(e) Then: fastboot flash recovery twrp.img
(f) Device will reboot.
(g) Check the new recovery options via (1) Volume Up + Power button; or (2) adb reboot recovery
Click to expand...
Click to collapse
CyanogenMod 13 for Lenovo phab pb1 750m available on this Russian site
Lenovoforum.ru
Here is link to custom ROM>> http://lenovo-forums.ru/topic/21986-lenovo-phab-cm-13-android-60-custom-rom/
There is some problem with WiFi.On some phone it's working and on some it's not working.Plaese somebody fix it.
rolland.arriza said:
Rooting Lenovo Phab PB1-750M (Android 6.0.1)
Before anything else, make backup.
Requirements:
(a) Driver. This should be installed by your device and can be found on CD Drive when you connect your device. Install "LenovoUsbDriver_autorun_1.1.30_user.exe" found on the link.
(b) Latest ADB and Fastboot (I recommend Minimal ADB and Fastboot).
(c) Download SevenMaxx TWRP image. Thanks estanenmi for the link.
(d) Download SuperSU binaries. This is v2.68. You could try the latest or just update it after successful install.
(e) Unlock the bootloader. On your device, go to Settings > Developer Options > Allow OEM Unlocking. Then reboot into bootloader via terminal/cmd: adb reboot bootloader. When in fastboot mode, type in terminal/cmd: fastboot oem unlock-go.
***fastboot oem unlock-go will restore the device to factory settings.
Rooting:
(a) Place the TWRP image on the root directory of Minimal ADB and Fastboot (or where your adb and fastboot is located)
(b) Copy the SuperSU zip file on your device
(c) Go to terminal/cmd: adb reboot bootloader
****You can also go to fastboot via "volume down + power" buttons.
(d) Go to terminal/cmd: fastboot boot twrp.img
****If you have flashed a custom recovery, you can install via recovery. The code above just temporarily boot the TWRP image.
(e) Then: fastboot reboot
(f) Navigate the TWRP. I strongly suggest to make a "backup" first.
(g) In TWRP, go to "Install" > locate and select the SuperSU.zip. Swipe to confirm.
(h) Reboot after installation. Your device may reboot a few times.
(i) Download root checker to verify.
*SuperSU app may update and may require to update su binaries.
*If SuperSU installation fails, boot the TWRP.img again and restore (if you have created a backup ).
*You could try installing the SuperSU listed above if your device is on bootloop due to unsuccessful rooting (worked for me).
*I haven't looked for possible problems pre and post rooting - always do backup.
Screenshot
Installing TWRP (custom recovery)
I haven't found any official custom recovery for this device. The custom recovery TWRP by SevenMaxx (from a russian forum) works. (install at your own risk). You can install the custom recovery via fastboot.
****If you only need root access, I suggest that you temporarily boot the TWRP to install SuperSU. It's better to wait for the official custom recovery for the device.
(a) First, the device's bootloader must be unlocked. Check the requirements on how to unlock bootloader.
(b) Configure your device again and enable USB debugging and OEM unlocking.
(d) Go to terminal/cmd: adb reboot bootloader
(e) Then: fastboot flash recovery twrp.img
(f) Device will reboot.
(g) Check the new recovery options via (1) Volume Up + Power button; or (2) adb reboot recovery
Click to expand...
Click to collapse
Gabom88 send me your email ID
Successfully rooted my Lenovo PB1-750M. Thanks.
dzoanhuy said:
How about xposed?
Click to expand...
Click to collapse
Hello there. Have you installed Xposed? I've successfully installed Xposed Framework. I'll put a guide if you need it.
gabom88 said:
Please somebody helps me!
Please someone can upload a "backup image" from TWRP so i can use it for "restore" mi device.
My device now is blicked and i can not use QFIL for restore because in the "restoration procces" of QFIL always says:
"Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode"
Click to expand...
Click to collapse
Hi. If you can still use the recovery (stock/TWRP), download the Firmware and install via recovery. Links are provided in the post.
Pb1-750p
Hi guys will this work on phab Pb1-750p
Can't see anything about this model
What is the difference between
PB1-750P and PB1-750P
Please reply
---------- Post added 25-07-2017 at 12:00 AM ---------- Previous post was 24-07-2017 at 11:57 PM ----------
PB1-750P and PB1-750M sorry predicted text
Pb1-750p
Hi will this work on phab Pb1-750p can someone let me know please be well appreciated
Tony0985 said:
Hi will this work on phab Pb1-750p can someone let me know please be well appreciated
Click to expand...
Click to collapse
Hi there. This method works for PB1-750M. There is currently no custom recovery ported for your device. You need to have a working custom recovery before you can root. If you want, you can try booting the custom recovery above and see if it works (the two phab models looks the same). But before anything else, makebackup (and make sure you know how to restore it).
Tony0985 said:
Hi will this work on phab Pb1-750p can someone let me know please be well appreciated
Click to expand...
Click to collapse
Hi there. This method works for PB1-750M. There is currently no custom recovery ported for your device. You need to have a working custom recovery before you can root. If you want, you can try booting (not flash) the custom recovery above and see if it works (the two phab models looks the same). But before anything else, makebackup (and make sure you know how to restore it).
Pb1-750p
Hi I was able to root it but not sure how to back it up only reason is I brought it and phone is full of trojans factory reset did not resolve it if you know of a method please can you guide me thanks for your response
Tony0985 said:
Hi I was able to root it but not sure how to back it up only reason is I brought it and phone is full of trojans factory reset did not resolve it if you know of a method please can you guide me thanks for your response
Click to expand...
Click to collapse
You need to have a rom/firmware of your device. Go to lenovo forum and try to find you rom.
How did you root your device? Using the TWRP i posted? Make backup from the TWRP recovery.
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11, which reportedly does not wipe your user data), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.img
Find your MIUI version in Settings -> About phone -> MIUI Version and look for the version number (e.g. 13.0.6.0(RKEEUXM))
Visit the MIUI Updates Tracker and download the matching Stable Fastboot update (if you can't find it scroll down to Extracting boot.img from Payload)
Unzip the TGZ and the TAR that it contains then navigate to the images directory and find the boot.img file
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode (you cannot use fastbootd for this or you'll bootloop)
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Extract boot.img from PayloadIf you can't find a fastboot image (boot.img) for your version then you might be able to extract it from the full firmware package. This will require the use of a third party tool such as payload-dumper (python) or payload-dumper-go. Note that you may be better off just waiting for the fastboot image to be released to the public.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Updating Magisk
You cannot update Magisk via the Magisk app, as this device does not allow writing to the boot partition at runtime.
Instead, update the Magisk app, then use it to patch your stock boot.img and flash it manually using fastboot, as if you were installing it from scratch (as above). This will not wipe your user data, but be sure to backup first in case something goes wrong.
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img (using payload_dumper)
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderThis can be done using the official tool from MIUI or using mtkclient. I went for the mtkclient option as I don't want to send more of my personal data to MIUI than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
python mtk reset
Disconnect USB cable and reboot phone
When it boots a message is displayed saying it is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgThe boot.img needs to be extracted from the official MIUI firmware package using payload_dumper.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO)
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
Wow, Thank you very much!
Very details!
Will try it in my spare time.
MarkLev said:
Wow, Thank you very much!
Very details!
Will try it in my spare time.
Click to expand...
Click to collapse
Good luck, let us know how it goes and what you do with your root! So far I've installed AdAway and De-Bloater
aricooperdavis. hi!I buy phone Poco M4 Pro (4G) (fleur). Please help me get ROOT rights for this phone.
I do not have PYTHON, but I have mtkclient - the bootloader is unlocked, and there is an Android SDK for fastboot firmware.
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
After unlocking the bootloader, using the mtkclient method, a new notification appeared
- dm-verity coruption
You device is corrupt/
It can't be trusted and may not work properly
Press power button to contime
Or, device will power off in 5 sec. Always need PRESS POWER for contime again How to fix it?
It sounds like you've done everything right so far.
Lark5 said:
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
Click to expand...
Click to collapse
Sorry, I have the EEA firmware; RKEEUXM.
If you want to extract the boot.img and vbmeta.img from your firmware package you will have to install python. This is worth doing as installing updates in the future may require you to do this extraction process again.
Alternatively you may be able to use mtk to dump these images directly from the phone, but I don't have any experience with this. To perform updates this way you would have to completely unroot and relock the bootloader, update the firmware, then re-dump the new boot and vbmeta images and root again. I think just installing python is probably easier...
The error message you're seeing is dm-verity, and we disable this when flashing the vbmeta.img in step 4, which I've edited to clarify. You can see that we disable it in the final fastboot command:
aricooperdavis said:
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Click to expand...
Click to collapse
Good luck with your rooting!
Unlock Bootloade and Root and RECOVERY for Poco M4 Pro (4G) with out Pyton (on Windows 10\11):
Unlock Bootloader:
1.Download the MediatekBootloaderUnlock archive. Unpack the archive ZIP.
2. Open the Driver folder and right-click the cdc-acm.inf file, select "Install"
3.Now go back to the main folder and install the USBDK (x64 for 64-bit OS, x86 for 32-bit OS) on your PC (also right click - install).
4. Reboot the PC.
5.Turn off the phone.
6.Run the UnlockBootloader.bat file to start the bootloader unlock process. We keep it on, it is in a state of response from the phone, if the firewood, the cable is connected, then everything is ok, I’ll tell you right away that it turned out 3 times.
7.Now connect the phone to the computer with a cable by holding down the volume up + down + power button. (If the volume up button doesn't work, try using volume up or volume up + volume down or all three hardware buttons) while the UnlockBootloader.bat file is open.
8.Once the phone is detected, some commands will be run in the UnlockBootloader.bat file. Let the commands finish and as soon as the window closes. Your bootloader will be unlocked.
BY THE WAY! - You can lock the bootloader again by following the same steps without clearing. Just use LockBootloader.bat with the same steps.
Root:
Downloading the official firmware for the phone, I took fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global (approximately 5.6GB in weight)
Unpacked it ZIP, pulled out 2 files from there fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global\images
boot.img and vbmeta.img
Downloaded Magisk STABLE Version: 24.3 - download on telephone, setup APP
Launch Magisk Manager. When a pop-up window appears asking you to install Magisk, select INSTALL and select install again.
Click on "Fix Boot Image File".
Connect your device to PC via USB cable. Make sure USB debugging is enabled.
Download ADB \ fastoot (I took tools_r29.0.6-windows)
Run CMD as Administrator
We write -
adb devices - the phone must be determined (QX ********* device - so all drivers are correct)
adb reboot bootloader - The phone reboots into fastboot mode - an inscription on the screen if dm-verity corruption messages appear - press POWER to continue
fastboot flash boot boot_PATCH.img (file name how to change)
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img - will remove the inscription dm-verity corruption
OrangeFox-R11 RECOVERY:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download, and Run CMD as Administrator
We write -
fastboot flash boot XXXXNAMEXXXX.img
Flash !boot! not fastboot flash recovery XXXXNAMEXXXX.img
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox [not yet officially supported]) at the end. I tend not to bother with custom recoveries as I stick with the stock MIUI ROM and a custom recovery would complicate applying OTA updates. However, if you wish to install a custom ROM (anything other than a stock MIUI signed boot.img) then a custom recovery would be necessary, and they can also facilitate taking device backups etc.
aricooperdavis said:
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox). I tend not to bother, but it can be convenient.
Click to expand...
Click to collapse
2. Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Fastboot Download V13.0.7.0.RKEMIXM
Explanations:
For fastboot (~5.6Gb) - firmware version, just unzip the ZIP, inside there is boot.img and vbmeta
For recovery (-2.5Gb) needed to extract boot.img Through Pyton for example
thanks for the help aricooperdavis
Lark5 said:
Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Click to expand...
Click to collapse
That's a great resource - the files it links to seem to be hosted on MIUIs servers too, so they're verifiably official
The more general link for all regions (not just global) for this phone would be: https://mirom.ezbox.idv.tw/en/phone/fleur/
I've updated the instructions to reflect your experience, thanks @Lark5!
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgNote: if your MIUI version (Available at: Settings -> About phone -> MIUI version) has a "Fastboot" file listed here then you can download that file and unzip it to find the boot.img and vbmeta.img, then skip to step 3.
Otherwise you'll have to extract them from the official MIUI firmware package using payload_dumper as follows.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO))
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Daafafagsgsgs said:
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Click to expand...
Click to collapse
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Daafafagsgsgs said:
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Click to expand...
Click to collapse
Go to this link, scroll to the downloads section, and select the right download for your OS, then follow the instructions.
This video shows the process, but has very annoying music!
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
I installed and tried everything this error comes
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Can i flash it with my phone ??
Adb otg app??
I don't know, I can't help you with that.
aricooperdavis said:
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Click to expand...
Click to collapse
Fastboot version
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
aricooperdavis said:
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
Click to expand...
Click to collapse
After many tries i found that the command given is wrong
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This is given
It will be
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
I is Missing Now i have flashed vb meta and problem is solved with the fastboot version i have
By the way thanks
I. Link to download rom
- Global version: https://help.redmagic.gg/hc/en-us/articles/5110059449113-REDMAGIC-7
- China version: https://ui.nubia.cn/rom/detail/72
II. File need to work (google for it pls)
1. Driver for adb and fastboot and install it on pc
2. Platform tool
3. Payload dumper
4. Magisk mask APK
III. Unpack rom to get require file
1. Download rom same with your version (CN or Global)
2. Using winrar or 7zip to unpack file rom to get payload.bin file
3. Using Payload dumper to dump payload.bin
4. After dumping u will get boot.img; recovery.img
IV.Unlock bootloader
1. Unlock developer mode on phone
2. Settings -> Developer Options -> OEM unlocking
3. Connect phone to PC
4. On PC using platform tool -> open CMD on folder platform tool
5. Using command:
adb reboot bootloader
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
V. Root
1. Require boot.img from step III and unlock bootloader from step IV
2. Copy boot.img file to phone
3. Install Magisk mask APK
4. Using Magisk mask to path boot.img file
5. After path u will get file path in download folder on your phone
6. Copy that path file from phone to pc paste it on platform tool folder
7. Rename file to boot.img
8. Open CMD on folder platform tool and using following command:
adb reboot bootloader
fastboot flash boot boot.img
VI. Convert rom from CN to Global or Global to CN
From Cn to Global should using Global version Asia (EU not testted)
U should wipe data before doing this
0. Connect phone to PC
1. Open CMD on adb folder
2. Command 1 by 1:
adb reboot bootloader
fastboot flash recovery recovery.img
( Flash recovery.img file unpack from rom
* if you want convert from CN to Global then flash recovery.img file of Global version rom
* if you want convert from Global to CN then flash recovery.img file of CN version rom)
3. After done command:
Fastboot reboot
*wait reboot done
adb reboot sideload
4. Copy rom file (*.zip) to platform tool folder rename it to rom.zip file (Copy version u want to flash)
adb sideload rom.zip
Waiting it done and reboot
VII. Unbrick phone
It only work if u can get fastboot mode
1. Flash recovery.img unpack from same version rom factory rom u phone using (CN using CN; Global using Global)
2. Go to recovery mode
3. Go to adb sideload mode
4. Flash rom with adb sideload (read step VI)
Waiting it done and pray it back to life again
VIII. Fix FingerPrint after root
1. Buy any calibrate tool u can get on your country (im using relife RL-071 tool)
2. On dial using code *#9959#
3. Press START
4. Then follow video
After recalibrate done u should reboot phone and check
I prefer u should wipe data to it work correct
It works! I have successfully rooted and recalibrated the fingerprint reader.