Related
By this you will be able to Unlock bootloader, Flash TWRP, and Root while maintaining possibility of applying future OTA's
I've researched many topics and forums for this and compiled all those things in this single step by step topic.
WARNING
Follow if you understand every word written in the topic name only and at your own risk.
I am not responsible for your doing. Follow every step as mentioned, you can skip parts if you understand what you are doing. Read it again to understand clearly, don't do it if you have any doubt and ask before rather asking later.
Credits to xda miui forums and all their ops for this kind info. Thank You.
Divided in 5 parts:
Main Topic-Introduction, Download links
Post two-Short Instructions-Rooting and Flashing OTA's
Post three-Unlocking bootloader, Flashing TWRP, Flashing 7.2.3 OTA, Rooting
Post four-How to flash Future OTA and Root after that
Post five-Troubleshooting- Drivers installation, Patching boot.img, Re-locking Bootloader, Fixing error 0x80070002 in MI Tool, VOLTE fix for marshmallow roms, Debloat MIUI 8, Under Test Methods
Things needed:
1. Redmi Note 3
2. PC with windows x64 (I did it on Windows 10 x64)
3. MiFlash_2016.03.30.exe
4. Fastboot 7.1.8 rom
Note: Fastboot 7.2.5 Rom is now available, you can use that and skip ota modifying and flashing part:Fastboot 7.2.5 rom
5. i) Miui 7.2.3 OTA
ii) Miui 7.2.5 OTA
6. twrp-3.0.2-2-kenzo.img
Twrp-3.0.2-2 Complete backup version
7. unlocked_emmc_appsboot.mbn Recovery flashable
8. Boot.img patcher (extracted from alka recovery, credits to the dev)
Patching method on pc is also given in the guide
9. Volte Fix for Marshmallow Roms: Here
10. MIUI 8 Debloating:Here
Some patched boot.img:
i) 7.2.3 patched boot.img
ii) 7.2.5 patched boot.img
iii) 7.3.2 patched boot.img
9. Android Image Kitchen OP-Android Image Kitchen - Unpack/Repack Kernel Ramdisk
10. Minimal adb and fastboot OP-[TOOL]Minimal ADB and Fastboot
11. SuperSU zip OP-SuperSU v2.65
12. i) Edited updater-script for OTA 7.2.3
ii) Edited updater-script for OTA 7.2.5
Now follow post 3 if you are not clear about this 'thing' or try looking at post 2 for simple and short instructions.
Short Instructions-Rooting and Flashing OTA's
Divided in two parts:
PART 1
How to root?
1. Falsh complete 7.1.8 with unlocked emmc_appsboot.mbn instead of the one in the rom .tgz and unlock using fastboot- After this our bootloader is unlocked.
2. We will now flash the twrp recovery using fastboot (with help of minimal adb and fastboot)- we have a custom recovery to apply modified ota zip (all future ota zips need to be modify before flashing) and also to flash supersu and patched boot.img
3. We will make a backup of 7.1.8 system+boot in TWRP.
4. We will now modify the ota zip (replace emmc_appsboot.mbn and updater-script) and flash in the recovery (system mounted as read only on first TWRP boot) but will NOT flash supersu.- updated to 7.2.5 now
5. We will now make a backup of 7.2.5 system+boot with NO compression in TWRP.- we got 7.2.5 boot.img (boot.emmc.win is the name )to patch it (#8 in things needed)
6. We will take this backed up boot.emmc.win in Android Image Kitchen in pc and patch it.- we now have patched 7.2.5 boot.img and a way to patch all future boot.img's
7. We will now mount system as read/write and flash supersu and this patched boot.img in twrp.- we have successfully rooted the phone.
PART 2
Future OTA's will fail as they will verify system and boot too before flashing. We have altered both here. But we have a recovery and a backup to restore before flashing ota.
So, how to apply future updates?
1. Download the ota but DO NOT flash it.
2. Modify the OTA zip as we did for 7.2.3 and 7.2.5
3. Restore unrooted system and not patched boot.img (the 7.2.5 TWRP backup)
4. Mount system and read only
5. Patch the OTA zip by replacing emmc_appsboot.mbn and updater-script. Flash the OTA
6. Make a new boot+system backup.
7. Patch the new boot.img.
8. Mount system as read/write
9. Flash patched boot.img along with supersu.
Follow up post three for detailed Rooting guide if things are not clear for you.
Unlocking bootloader, Flashing TWRP, Flashing 7.2.5 OTA, Rooting
It is particularly focused on rooting latest (at writing this) version of Miui i.e. 7.2.3
How to Root?
For rooting we have to flash SuperSu from custom recovery i.e. TWRP. So, obviously we need to flash TWRP first in Redmi Note 3.
But, to flash TWRP we need to unlock bootloader first
Unlocking Bootloader:
Downloads from post one:
1. Download and Install Mi Flash Tool
2. Download and Extract 7.1.8 Fastboot Rom (You can also use latest fastboot rom, just skip OTA part from this guide)
3. Download, Extract and Replace unlocked_emmc_appsboot.mbn in the extracted rom folder
4. Download and Install Minimal ADB and Fasboot Tools
Instructions:
1. Turn Your Phone On and Connect USB Cable to the phone and the Computer
2. Go to settings-about phone and tap Miui versoin five times.
3. Go back and go to Additional settings-Developer Options and enable USB debugging (if disabled) and Enable OEM Unlock (if disabled)
4. Open Device Manager in PC and check to find your phone Installed as ADB Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. See if there is any pop up in phone asking to Authorization (Allow USB debugging). Check Always allow from this Computer and tap ok.
6. Run the Minimal ADB and Fastboot From the Start Menu
7. Check if your Device is Detected in ADB by typing this command
Code:
adb devices
You should see the output like this
If not, then you have to install drivers. Go to topic #5. Then try again.
8. Type the following command to Reboot the Phone to EDL mode
Code:
adb reboot edl
9. Check the Device Manager you should see the Phone as shown in the Screenshot below
NOTE: The Driver can be Either the one Shown in the Image (which is a default driver loaded by windows)
or
can be from Qualcomm which will read as
Qualccomm HS-USB QLoader 9008
Click to expand...
Click to collapse
Note that there is a possibility that You might End up in
Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
But Don't Panic and Follow the Steps from Step No. 1 again
10. Now Start the MI Flash Tool and Browse to the Location Where you have Extracted the Fastboot ROM
11. Go to Advanced (arrow in front of browse) and Select:
Flash Programmer, Raw XML File and Patch XML File
from the Fastboot ROM\Images folder and press enter on keyboard
12. Press Refresh in MI tool and You should see you phone in the MI Flash tool With the same COM# as in the Device Manager
13. Press Flash and wait. It would take some time to flash about 170-250 seconds or more ( if Miflash shows a error on clicking Flash , please restart Miflash and try again)
14. After the Miflash fastboot is completed successfully, hard boot phone to Fastboot mode by pressing and holding Volume Down+Power On. You will see mi bunny on screen.
15. Again run Minimal ADB and Fastboot from start menu (as Administrator)
16. Type:
Code:
fastboot oem device-info
It will show you the current Bootloader Status .
17. Now again Type:
Code:
fastboot oem unlock-go
Optional: Type in the previous command again to check if the status of Bootloader had changed or not.
18. Type:
Code:
fastboot reboot
to reboot the phone.
Bootloader is unlocked now but do not disconnect the phone from pc yet.
Credits:
http://en.miui.com/thread-253680-1-1.html
http://en.miui.com/thread-261019-1-1.html
Flashing TWRP:
Downloads from post one:
1. TWRP recovery
Instructions:
1. Once done with bootloader unlock guide, without disconnecting the phone, restart phone in fastboot mode (use steps 1-8 from unlocking guide and replace edl command with fastboot, i.e. write fastboot instead of edl in cmd) or Press and hold volume down+power to hard boot it to fastboot.
2. Go to Minimal ADB and Fastboot directory
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
and copy/move downloaded twrp-3.0.2-2-kenzo.img here.
3. Type following in cmd once the phone is in fastboot mode.
fastboot flash recovery twrp-3.0.2-2-kenzo.img
4. Once done, hard boot phone to recovery by Pressing and holding Volume Up+Power On. TWRP should boot.
Note: When asked to mount system as read only or as read/write select read only in TWRP. This step is important otherwise you will face bootloop after flashing ota.
Flashing 7.2.3 OTA and then 7.2.5 OTA:
Downloads from post one:
1. Miui 7.2.3 OTA and Miui 7.2.5 OTA
2. unlocked_emmc_appsboot.mbn
Downloads from internet
1. 7zip Or WinRAR
Instructions:
1. Download the OTA in your PC or move it in your pc from phone after downloading.
2. Open the OTA file in Windows with Winrar/7zip
3. Locate the emmc_appsboot.mbn in firmware-update folder and delete from the zip (it will take a while for the deletion please be patient)
4. Drag and drop the (unlocked)emmc_appsboot.mbn to the firmware-update folder of the OTA
5. Navigate to "META_INF/com/google/android/" and extract the updater-script file and then delete it from the zip.(make sure to keep a backup of the zip)
6. Open the file in a text editor, (I prefer Notepad++) and delete the following lines and save the file
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys" ||
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys" ||
abort("Package expects build fingerprint of Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys or Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f320640385976fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeedd9a0") || abort(""EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f320640385976fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeedd9a0" has unexpected contents.");
if block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") then
ui_print("Verified system image...");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "e04e9788c17630b4088243d8b3ee29509568b793") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "3b8aeee76a291f2b1647c9bbcbece5be948a83fc") || abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates");
(range_sha1("/dev/block/bootdevice/by-name/system", "80,0,32770,32929,32931,33439,65535,65536,65538,66046,98303,98304,98306,98465,98467,98975,131071,131072,131074,131582,163839,163840,163842,164001,164003,164511,196607,196608,196610,197118,229375,229376,229378,229537,229539,230047,262143,262144,262146,262654,294911,294912,294914,295073,295075,295583,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,476353,491520,491522,524288,524290,557056,557058,589824,589826,622592,622594,623102,650190,650191,655320") == "a75d23fa6067c58c166603cfac0b3d0df9b81919") ||
abort("system partition has unexpected contents");
endif;
Click to expand...
Click to collapse
(Edit the 7.2.5 OTA the same way or use updater-scripts provided for both OTA's from post 1)
7. Now again navigate to "META_INF/com/google/android/" and drag and drop the modified updater-script file inside the folder
8. Move this modified OTA zip to your (internal/external sd) and flash using TWRP.
9. Once done, make a system+boot bakcup in twrp, name it "7.1.8 stock"
10. Apply future updates like this and make backup with naming. Delete old backups.
Example: Make a backup named "7.2.5 stock" just after flashing 7.2.3 and 7.2.5 updates. Then root it and flash patched boot.img. If the phone starts up normal, reboot to recovery and delete 7.1.8 stock backup and keep 7.2.5 stock backup to use it for flashing future OTA.
Rooting:
Downloads from post one:
1. SuperSU zip
2. 7.2.5 boot patched.img
Instructions:
Note: Now change the mode to read/write for system partition from mount option in TWRP. Otherwise these zips will not flash.
1. Copy/Move/Download SuperSU zip and patched boot.img in your phone.
2. Extract the .rar containing the patched boot.img.
3. Reboot to recovery and Tap on Install in the TWRP main screen.
4. Select SuperSu.zip
5. To flash boot.img, the default mode is to flash zip files, you will need to toggle the mode to images.
6. To do so, tap on the Images… button on the bottom-right of the screen
7. The recovery will now only see the image files, select the patched boot.img
8. Once you select, you will be prompted to select the type of image it is, select Boot or Recovery. Select Boot.
9. Finally, swipe the button on the bottom of the screen to start the flashing process.
10. Once complete, you can go to Reboot > System.
How to flash Future OTA and Root after that
You got a Unlocked, Rooted phone with custom TWRP recovery. The OTA will check the system and will fail to flash as you have flashed SuperSu and Boot.img.
What you may do when a new OTA arrives??
Flashing any OTA and rooting it
Downloads from post one:
1. SuperSU zip
2. Unlocked boot img (will be updated when ota will arrive)
3. Unlocked_emmc_appsboot.mbn
Downloads from internet:
1. WinRAR/7zip
Preparing OTA:
1. Download the OTA in your PC or move it in your pc from phone after downloading.
2. Open the OTA file in Windows with Winrar/7zip
3. Locate the emmc_appsboot.mbn in firmware-update folder and delete from the zip (it will take a while for the deletion please be patient)
4. Drag and drop the (unlocked)emmc_appsboot.mbn to the firmware-update folder of the OTA
5. Navigate to "META_INF/com/google/android/" and extract the updater-script file and then delete it from the zip.(make sure to keep a backup of the zip)
6. Open the file in a text editor, (I prefer Notepad++) and delete the following lines and save the file
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys" ||
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys" ||
abort("Package expects build fingerprint of Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys or Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f3206403859 76fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeed d9a0") || abort(""EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f3206403859 76fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeed d9a0" has unexpected contents.");
if block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") then
ui_print("Verified system image...");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "e04e9788c17630b4088243d8b3ee29509568b793") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "3b8aeee76a291f2b1647c9bbcbece5be948a83fc") || abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates");
(range_sha1("/dev/block/bootdevice/by-name/system", "80,0,32770,32929,32931,33439,65535,65536,65538,66 046,98303,98304,98306,98465,98467,98975,131071,131 072,131074,131582,163839,163840,163842,164001,1640 03,164511,196607,196608,196610,197118,229375,22937 6,229378,229537,229539,230047,262143,262144,262146 ,262654,294911,294912,294914,295073,295075,295583, 327679,327680,327682,328190,360447,360448,360450,3 60958,393215,393216,393218,393726,425983,425984,42 5986,426494,458751,458752,458754,459262,476353,491 520,491522,524288,524290,557056,557058,589824,5898 26,622592,622594,623102,650190,650191,655320") == "a75d23fa6067c58c166603cfac0b3d0df9b81919") ||
abort("system partition has unexpected contents");
endif;
Click to expand...
Click to collapse
NOTES:
a. If this is not working for you, getting error while flashing, then use the updater script added in post one, i have edited that my self for my use and worked perfectly.
b. Allow TWRP to read/write system (asked on first time when recovery boots) as flashing ota to system is a write process.
7. Now again navigate to "META_INF/com/google/android/" and drag and drop the modified updater-script file inside the folder
8. Move this modified OTA zip to your (internal/external sd) and flash using TWRP.
9. Once done, make a system+boot bakcup in twrp, name it "7.2.3 stock"
Flashing and making new Backup:
1. Reboot to TWRP (Volume Up+Power on)
2. Restore 7.2.3 stock backup from backup and restore options
3. Flash the modified OTA.
4. Make a new backup of system+boot and name it "version" stock. Like "7.2.3 stock"
Rooting:
1. Copy/Move/Download SuperSU zip and patched boot.img in your phone.
2. Extract the .rar containing the patched boot.img.
3. Reboot to recovery and Tap on Install in the TWRP main screen.
4. Select SuperSu.zip
5. To flash boot.img, the default mode is to flash zip files, you will need to toggle the mode to images.
6. To do so, tap on the Images… button on the bottom-right of the screen
7. The recovery will now only see the image files, select the patched boot.img
8. Once you select, you will be prompted to select the type of image it is, select Boot or Recovery. Select Boot.
9. Finally, swipe the button on the bottom of the screen to start the flashing process.
10. Once complete, you can go to Reboot > System.
Troubleshooting
Installing Drivers
1. Disable Windows Drivers Signature on your computer: you can do that by pressing Windows button + i on keyboard to reveal the Settings page. From there you can choose Update & Security >> Recovery >> Advanced startup >> Restart now. Wait a moment for your computer to restart. Next, go to Troubleshoot >> Advanced options >> Startup settings >> Restart. Once your computer restarts, now choose Disable driver signature enforcement which is option number 7. See the video below:
Disable Windows Drivers Signature
:credits to the owner i have not made it.
2. Hold Vol - and Vol + and plug Usb , you will enter adb Mode.
3. Now Phone is Connected as ADB. Check Device Manager for Below:-
4. Run Minimal adb (search adb in start)
5. Type these Commands:
Code:
adb devices
adb reboot edl
Phone will enter in download Mode with Red Led.
6. Open Device Manager and Phone will be detected as QHUSB_BULK.
Right Click and choose Update Drivers.
7. Choose Browse My Computer for Driver Software
8. Choose the Path of Xiaomi Folder. Most of users will find it like this.
Note:- If Folder does not exist , Install MI Flash (post #1) first.
Win 64 bit C: \ Program Files (x86) \ Xiaomi \ MiPhone \ Qualcomm \ Driver
Win 32 bit C: \ Program Files \ Xiaomi \ MiPhone \ Qualcomm \ Driver
9. Choose Install this Driver Software anyway.
10. The driver will be installed Sucessfully and you can see added in Ports as Qualcomm HS-USB.
Credits:http://en.miui.com/thread-235865-1-1.html
Patching Boot.img
1. Download the Android Image Kitchen Tool from post #1 and extract it.
2. Download the fastboot room and extract to locate the boot.img (or any other source you would like) and move it to the Android Image Kitchen folder, as shown below:-
3. Right click & hold, on the "Boot.img" file and move & place it onto unpackimg.bat file and proceed with the on-screen message to "Run", as shown below:-
4. Next go to ramdisk directory and locate fstab.qcom file, as shown below:-
5. Use any text editor (notepad++ preferred) to open fstab.qcom file, then use the Find function to find any value containing "Verify" and delete with care, and save it accordingly, as shown below:-
Code:
,verify
:delete verify also the , in from of it.
6. Now we need to repack the modded boot.img file, double-click to execute "repackimg.bat" hence it will generate a new boot file as "image-new.img" as shown below:-
7. Done..
Credits:http://en.miui.com/thread-249666-1-1.html
Relocking Bootloader: (DO AT YOUR OWN RISK AND ONLY IF YOU KNOW WHAT YOU ARE DOING)
1. Get the fastboot rom image from topic #1 or the locked emmc_appsboot.mbn from post #1 (version 7.1.8)
2. Download (from post #1) and Install Minimal adb and fastboot
3. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and copy/move the downloaded emmc_appsboot.mbn here.
4. Run MAF32.exe (it is in this folder too)
5. Type following commands
Code:
fastboot Flash aboot emmc_appsboot.mbn
fastboot Flash abootbak emmc_appsboot.mbn
fastboot Reboot
6. Done.
Fixing The system cannot find the file specified.(0x80070002):
* Make sure you have downloaded correct rom.
* Make sure there is no space in you path of images.
Eg:
NOT E:\MI TOOLS\rn3\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global_9706e12561UNLOCK\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global\images
BUT E:\MI_TOOLS\rn3\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global_9706e12561UNLOCK\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global\images
IF STILL THE ERROR IS THERE (ONLY TRY IF ALL ABOVE METHODS FAIL)
1. Download this Rar and replace both files in your fastboot rom. (flash_all.bat in rom folder and rawpragram0.xml in images folder)
2. Try to flash now.
What about the fingerprint error while flashing OTA?
OP, you need to really give detailed steps... Else this thread is gonna be filled with more questions than answers....
For example the ota zip does not contain the boot.img file but contains a patch file boot.img.p , so do we need to replace modded full boot.img in ota- will it get flashed or will the flashing fail as the instructions in ota will be for patch boot file...
Dropbox link for patched bot image of 7.2.3 is not working... gives error
7.2.3.0 boot.img
use this link to downloadwww.dropbox.com/s/k5w16gotzz7zge0/7.2.3 boot patched.rar?dl=0
Sudeep Duhoon said:
reserved 4
Click to expand...
Click to collapse
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
pvp16 said:
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
Click to expand...
Click to collapse
to flash modified boot.img you have to do all the steps till that part first.
Error from dropbox
Downloaded file of boot .rar has been corrupted
root 7.2.3.0
if i am on 7.2.3.0 (bootloader locked) is it neccessary to flash 7.1.8 ie downgrade to unlock bootloader... or i can skip some of ur steps plzzz help
---------- Post added at 09:29 AM ---------- Previous post was at 09:15 AM ----------
what we are doing (deleting) in script..... it is for to get rid from finger print error
Deevit said:
Downloaded file of boot .rar has been corrupted
Click to expand...
Click to collapse
Downloading in phone? Try uc browser.
vivekjha said:
if i am on 7.2.3.0 (bootloader locked) is it neccessary to flash 7.1.8 ie downgrade to unlock bootloader... or i can skip some of ur steps plzzz help
---------- Post added at 09:29 AM ---------- Previous post was at 09:15 AM ----------
what we are doing (deleting) in script..... it is for to get rid from finger print error
Click to expand...
Click to collapse
Yes necessary.
I was following the process to install the OTA after making changes to the zip file with the emmcxx and update-script.
TWRP threw me this error
Failed to apply patch " patch/boot.img.p"
Updater process ended with ERROR:7
Pls help. Thanks
Tried
Sudeep Duhoon said:
Downloading in phone? Try uc browser.
Click to expand...
Click to collapse
In UC I had tried but it has been corrupted
Unlocking Bootloader Error
When I try to flash fastboot oem unlock-go it returns: FAILED (remote: Token verification failed, reboot the device)
.HOW TO FIX
pvp16 said:
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
Click to expand...
Click to collapse
Not without unlocking the bootloader, you cant
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
fylim said:
I was following the process to install the OTA after making changes to the zip file with the emmcxx and update-script.
TWRP threw me this error
Failed to apply patch " patch/boot.img.p"
Updater process ended with ERROR:7
Pls help. Thanks
Click to expand...
Click to collapse
I guess you need to remove the patch boot file and replace it with modified boot image file.
Deevit said:
Downloaded file of boot .rar has been corrupted
Click to expand...
Click to collapse
link has been updated but file working fine. it is 10.64mb
If you're one of the lucky few to receive Oreo (EMUI 8) on your Nova 2 Plus, then you can rejoice knowing you can finally run custom ROMs. Here's how.
I'm not responsible if you somehow ruin your device. Bear in mind, Treble ROMs are still largely in development, and there are many bugs and there isn't a single ROM that passes SafetyNet - so apps like Snapchat don't work. Read the instructions for reverting to EMUI before you proceed with installing a custom ROM.
First off, check if you're on Oreo and your phone have Project Treble.
Open Settings, About Phone
Make sure that your Android version is 8.0 or 8.1
Follow this guide
If your phone supports Treble, continue
Next, you have to unlock your bootloader. Follow this guide, under "Unlocking Bootloader". FYI: You can reboot into your bootloader by holding down the Power Button and Volume Down. When you reboot it will say "FRP unlocked and bootloader unlocked". If it doesn't, you messed up.
Go to this thread and go window shopping for a cool ROM under the title "Generic System Images (GSI) Projects & Complete ROM". I don't recommend you choose phh's AOSP, as that has the least support. Personally, I chose Resurrection Remix Official. You're also looking for an arm64 A-only GSI.
If you're like me, you won't have a TWRP image installed, because there isn't one that works 100%. Choose a GSI that has gapps installed for this reason.
Grab the GSI and drop it along with your adb.exe on your PC. Reboot back into your bootloader (remember: Power Button and Volume Down).
Execute
Code:
fastboot erase system
in your cmd/terminal/powershell window. This will erase your system partition. Don't worry, you can get this back from Firmware Finder.
Execute
Code:
fastboot -u flash system [B]GSI_File_Name[/B].img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
You have successfully flashed a custom ROM. Congratulations.
---
Read on for rooting and reverting back to EMUI.
The beginning steps are the same for both. You'll need Firmware Finder and Huawei Update Extractor , which is sadly only for Windows.
Open Firmware Finder and search for your model number (BAC-L21, BAC-AL00, etc)
Sort by date to find the latest Oreo release, download it
To revert to EMUI 8
Extract UPDATE.APP and place in Huawei Extractor's root
Open Huawei Update Extractor
Go to Settings, uncheck everything that begins with "Verify..."
Go back to Extract, and open the UPDATE.APP
Extract SYSTEM.img, and save it in some place. If you rooted using the method below, get your RAMDISK.img out as well.
Place it in the folder where you have adb.exe
Reboot phone into fastboot
Execute
Code:
fastboot erase system
in your cmd/terminal/powershell window. This will erase your system partition.
Execute
Code:
fastboot -u flash system SYSTEM.img
If you rooted, then flash the original RAMDISK.img as well
Allow the images to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
Grats, you are now back to EMUI 8.
---
To root your phone using Magisk
Extract UPDATE.APP and place in Huawei Extractor's root
Open Huawei Update Extractor
Go to Settings, uncheck everything that begins with "Verify..."
Go back to Extract, and open the UPDATE.APP
Extract RAMDISK.img, and save it in some place - have a backup copy saved to your PC in case you want to unroot
Move it to your phone using MTP, and remember where you saved it
Download Magisk apk
Install it on your phone
Open the app, go to Settings and change the Update Channel to beta
Go back to the opening page, make sure it's installing Magisk 16.6, then press Install, then press Patch Boot Image
Select the RAMDISK.img you just saved, let it do its thing. It won't show you any progress bars, but trust me, it's working.
Once it's finished, move the patched_boot.img from the MagiskManager folder to your PC
Place it in the folder where you have adb.exe
Reboot phone into fastboot
Execute
Code:
fastboot erase ramdisk
in your cmd/terminal/powershell window.
Execute
Code:
fastboot flash ramdisk patched_boot.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
Grats, you got Magisk root.
Once you have root, you can also fix a fingerprint gesture issue with Treble ROMs by following this guide.
---
Thanks for reading and enjoy your Oreo custom ROM.
Can u make a detailed tut how to root bac L21 running oreo? And how to flash a stock firmware if messed up.. Coz i screwed up my phone before and tried sd card method but could not flash a stock firmware.
Deleted
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?
Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?
İ don't now
İ need answer to to trying this method
But my phone C185
And the update file in Firmware finder 2 file not 3
use Hrupdater
CouCouFR34 said:
Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?
Click to expand...
Click to collapse
You would have to modify hwota script as Pie only uses 2 zips.
aureliomilitao said:
use Hrupdater
Click to expand...
Click to collapse
that's not recommended as Pie uses System as root.
ante0 said:
You would have to modify hwota script as Pie only uses 2 zips.
that's not recommended as Pie uses System as root.
Click to expand...
Click to collapse
how modify hwota script as Pie only uses 2 zips?>
same steps with 2 file works??
please my account HCU is block
need help for fix my IMEI with acount HCU via TeamViewer
Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?
CouCouFR34 said:
Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?
Click to expand...
Click to collapse
Remove the following line from update-binary in hwota8_update.zip and repack.
echo --update_package=/sdcard/HWOTA8/update_data_public.zip >> /cache/recovery/command
Or check out this post: https://forum.xda-developers.com/showpost.php?p=78962795&postcount=171
I want to patch new updates of emui 9 with latest google security patches so which no check recovery i use on emui 9.
OK it works very well and EMUI9 is definitely better than version 8; on the other hand how to reinstall TWRP?
I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?
CouCouFR34 said:
I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?
Click to expand...
Click to collapse
You don't need TWRP to install Magisk; for that matter, they can't be installed simultaneously on EMUI 9 together anyway.
The EMUI 9 method for Magisk is to patch recovery_ramdisk.img extracted from update.app, flash the patched image, and boot to recovery from then on. (Huawei made it impossible to load a custom ramdisk on Pie otherwise.)
Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?
CouCouFR34 said:
Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?
Click to expand...
Click to collapse
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Thank you irony_delerium ; very clear tutorial ; on the other hand, in UPDATE.APP there are 2 RECOVERY files : RECOVERY_RAMDIS.img and ERECOVERY_RAMDI.img which do the same weight; patching MAGISK with RECOVERY_RAMDIS.img I arrived at a system error and a dialogue asking me to either erase the data, or a factory restore; on the other hand with ERECOVERY_RAMDI.img it was installed alone? does it seem normal to you?
irony_delerium said:
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Click to expand...
Click to collapse
Hello
If you wouldn't mind confirming a few things from your post, as I'm trying to do this.
Is the sole purpose of extracting the big file to extract the recovery_ramdis ? You don't mention if anything is done with the big file.
The ADB commands didn't work for me, (error: push requires an argument).
But, I sent the recovery_ramdis via magisk manager, and it worked, then advised me that it put the image in /storage/emulated/0/Download/patched_boot.img but I can't find that location.
OK, edit ... I found the file and flashed it, rebooted into recovery and I get the message software installation failed.
I've had a whole lot of failures, phone won't root despite magisk giving no errors, dload won't work, superSU won't work.
Update .... root decided to work out the blue so I tried EMUI flasher and it looked like it was going to work ... but failed the update at about 10%.
Update - Bricked.
Hello guys , [ UPDATE ROOT for EMUI 9.1.0.210 .. at bottom ... there are some minor changes]
been reading here and there for a working root but didn't work and my worries to get phone locked / bricked / bootloop
was increasing at any failed test !
THIS method WILL WORK i tested it today and worked ! I'm gonna upload also my magisk recovery_ramdisk PATCHED (read later) so you can skip few steps !
let's start
(steps are copied by Athanatos81 post here in XDA that's basically what i applied with some minor changes )
I. Rooting your device
1. be sure ADB / fasboot are working on your pc(drivers) and smartphone - INSTALL magisk manager Magisk Manager
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
( you can use my magisk recovery_ramdisk PATCHED it's created by using update.app from update.zip file of EMUI BUILD 9.0.1.175(C432E3R1P5)
that means IF you are on emui 9.0.1 with THAT BUILD NUMBER you can use it ... if you are on a different build DO NOT use it, I take no responsabilities !!!
link to magisk recovery_ramdisk PATCHED magisk recovery_ramdisk PATCHED magisk_patched_9_0_1_175.img
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC. ( you can NOT enter fastboot? read in next section)
4. Open a Powershell and check if your honor 8 pro is listed by writing :
Code:
fastboot devices
you should see something like BYJDU17803000088 fastboot
that means your phone in correctly in fastboot/connected
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk magisk_patched.img
(in this case MY ALREADY MADE magisk recovery_ramdisk patched is named like that IF you choose a different name that CHANGE it also in the command)
when the process is complete (you'll get something like this
OKAY [ 0.184s]
finished. total time: 0.879s)
you need to REBOOT follow these next steps as i describe them or it won't work :
6. from your pc command window write
Code:
fastboot reboot
as soon as phone reboot
- remove usb cable
- PRESS and HOLD DOWN " volume up " VOL+ , keep it pressed until you see HONOR text (blue screen)
doing this will INSTALL MAGISK
7. your phone boot regularly(hopefully) now open Magisk Manager
you will see MAGISK 19.x.x.
and MAGISK 7.3.2
click on INSTALL (magisk 19.3) --- INSTALL ---- DIRECT INSTALL
when it's done it'll ask you to reboot , click reboot
phone is rooted !!!!!
i hope it helps for any references have a look at these pages which helped me :
root emui 9
magisk download
Magisk info
ROOT EMUI 9.1.0.210
first of all thank you to @OldDroid and @Athanatos81 for support ...
DOWNLOAD my patched magisk: PATCHED Magisk recovery 9.1.0.210
I'll descrive here the process how to update and root from 9.0.1.175 to 9.1.0.210
in my case i was on emui 9.0.1.175 rooted and i couldn't enter recovery or fastboot or simply update through system update !
so before starting it go in system settings -> update and DOWNLOAD your update
when you end your download don't restart and update BUT enter in fastboot:
to enter fastboot i had to restart honor 8 pro (while connected to usb)
and keep pressing VOL DOWN
now in fastboot you'll do following steps
(to install official update YOU FIRST NEED to install stock recovery so in this case 9.0.1.175 stock recovery .. while if you just need root on your actual rom you can just use the patched magisk recovery)
check if your smartphone is seen
fastboot devices
now
fastboot flash recovery_ramdisk magisk_patched_9_1_0_210.img ( in this case is the one i already patched for you )
fastboot reboot
let system start and than use ADB
adb reboot recovery
system will restart now open magisk manager
INSTALL MAGISK( in my case v20.1 )
INSTALL direct
reboot when asked
congratulations your Emui 9.1 is rooted !!!
Work with 9.1 ?
probably... I still didn't uodst though (going soon in holidays I don't wanna mess up with it lol)
Kyouck said:
Work with 9.1 ?
Click to expand...
Click to collapse
Sent from my DUK-L09 using Tapatalk
Kyouck said:
Work with 9.1 ?
Click to expand...
Click to collapse
IT WORKS !!!!!!!!! just tried it ! there are some minor changes .. i'm gonna explain what to do
IF you have problem with ADAWAY ( not enough space or something similar )
OPEN MAGISK manager
SETTINGS
click over SYSTEMLESS HOSTS
and now reboot
open again Adaway and it'll be working
IF YOU HAVE PROBLEMS with SMS app crashing ( you can't receive/send sms ) follow this and it'll work again
https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964#post80777289
just another important update :
if you have got (probably you did "system settings update") read this:
I've got that "system update settings" on my honor 8 Pro and guess what? I've lost magisk root... so I need to do procedure again.. unbelievable but that is it! I found out cause I started to see annoying advertising and I checked adaway and "no root"
Sent from my DUK-L09 using Tapatalk
simika said:
IT WORKS !!!!!!!!! just tried it ! there are some minor changes .. i'm gonna explain what to do
Click to expand...
Click to collapse
Code: fastbood devices is not work in my phone. im not can start fastboot mode
StaBar said:
Code: fastbood devices is not work in my phone. im not can start fastboot mode
Click to expand...
Click to collapse
connect the phone to pc, keep "vol-" pressed directly after pressing restart on the phone, it should enter fastboot now.
I had same problem.. doing that it'll enter fastboot
Sent from my DUK-L09 using Tapatalk
I need the patched files
I need the patched magisk files guys please the links provided on top aren't working
Hello this will work without unlocking bootloader? Also the links above are not working. I am on 9.1.0.212, can I use your 9.1.0.210 patch file? Thanks.
I'm on 9.1.0.212.. Please tell me how to root this.. Plzzz
Updated magisk_patched_9_1_0_210.img - Magisk v20.4 included , added also the original RECOVERY_RAMDISK extracted from 9.1.0.210.
magisk_patched_9_1_0_210.img md5sum = fa2b59807eac66e128653eaebc433aa3
RECOVERY_RAMDISK_9_1_0_210.img md5sum = c62ac7fdc55cb535d1b627b8f17f1842
Will the steps for flashing be same as given in OP?
Thanks...
panijsr said:
Will the steps for flashing be same as given in OP?
Thanks...
Click to expand...
Click to collapse
yes and take the latest magisk manager from the official magisk page
nanortemis said:
Updated magisk_patched_9_1_0_210.img - Magisk v20.4 included , added also the original RECOVERY_RAMDISK extracted from 9.1.0.210.
magisk_patched_9_1_0_210.img md5sum = fa2b59807eac66e128653eaebc433aa3
RECOVERY_RAMDISK_9_1_0_210.img md5sum = c62ac7fdc55cb535d1b627b8f17f1842
Click to expand...
Click to collapse
Bro which file to flash from this two.. actually I flashed magisk patched file and it worked fine with magisk installed but then I tried custom rom and it didn't work so flashed stock rom again and lost root access so I did same step but this time magisk isn't installing and not giving root access.. idk what's wrong can you please help?
Please help me root this version
RECOVERY_RAMDISK_9_1_0_230.img & magisk_patched_9_1_0_230.img ?? Where can be found ?
gazon9 said:
Please help me root this version
RECOVERY_RAMDISK_9_1_0_230.img & magisk_patched_9_1_0_230.img ?? Where can be found ?
Click to expand...
Click to collapse
Honor V9 Guides, News, & Discussion
Use this forum to find the best how-to guides for the Honor V9 and discover the latest news. General discussion also goes here.
forum.xda-developers.com
your screenshot shows honor v9 not honor 8 pro
simika said:
Hello guys , [ UPDATE ROOT for EMUI 9.1.0.210 .. at bottom ... there are some minor changes]
been reading here and there for a working root but didn't work and my worries to get phone locked / bricked / bootloop
was increasing at any failed test !
THIS method WILL WORK i tested it today and worked ! I'm gonna upload also my magisk recovery_ramdisk PATCHED (read later) so you can skip few steps !
let's start
(steps are copied by Athanatos81 post here in XDA that's basically what i applied with some minor changes )
I. Rooting your device
1. be sure ADB / fasboot are working on your pc(drivers) and smartphone - INSTALL magisk manager Magisk Manager
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
( you can use my magisk recovery_ramdisk PATCHED it's created by using update.app from update.zip file of EMUI BUILD 9.0.1.175(C432E3R1P5)
that means IF you are on emui 9.0.1 with THAT BUILD NUMBER you can use it ... if you are on a different build DO NOT use it, I take no responsabilities !!!
link to magisk recovery_ramdisk PATCHED magisk recovery_ramdisk PATCHED magisk_patched_9_0_1_175.img
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC. ( you can NOT enter fastboot? read in next section)
4. Open a Powershell and check if your honor 8 pro is listed by writing :
Code:
fastboot devices
you should see something like BYJDU17803000088 fastboot
that means your phone in correctly in fastboot/connected
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk magisk_patched.img
(in this case MY ALREADY MADE magisk recovery_ramdisk patched is named like that IF you choose a different name that CHANGE it also in the command)
when the process is complete (you'll get something like this
OKAY [ 0.184s]
finished. total time: 0.879s)
you need to REBOOT follow these next steps as i describe them or it won't work :
6. from your pc command window write
Code:
fastboot reboot
as soon as phone reboot
- remove usb cable
- PRESS and HOLD DOWN " volume up " VOL+ , keep it pressed until you see HONOR text (blue screen)
doing this will INSTALL MAGISK
7. your phone boot regularly(hopefully) now open Magisk Manager
you will see MAGISK 19.x.x.
and MAGISK 7.3.2
click on INSTALL (magisk 19.3) --- INSTALL ---- DIRECT INSTALL
when it's done it'll ask you to reboot , click reboot
phone is rooted !!!!!
i hope it helps for any references have a look at these pages which helped me :
root emui 9
magisk download
Magisk info
ROOT EMUI 9.1.0.210
first of all thank you to @OldDroid and @Athanatos81 for support ...
DOWNLOAD my patched magisk: PATCHED Magisk recovery 9.1.0.210
I'll descrive here the process how to update and root from 9.0.1.175 to 9.1.0.210
in my case i was on emui 9.0.1.175 rooted and i couldn't enter recovery or fastboot or simply update through system update !
so before starting it go in system settings -> update and DOWNLOAD your update
when you end your download don't restart and update BUT enter in fastboot:
to enter fastboot i had to restart honor 8 pro (while connected to usb)
and keep pressing VOL DOWN
now in fastboot you'll do following steps
(to install official update YOU FIRST NEED to install stock recovery so in this case 9.0.1.175 stock recovery .. while if you just need root on your actual rom you can just use the patched magisk recovery)
check if your smartphone is seen
fastboot devices
now
fastboot flash recovery_ramdisk magisk_patched_9_1_0_210.img ( in this case is the one i already patched for you )
fastboot reboot
let system start and than use ADB
adb reboot recovery
system will restart now open magisk manager
INSTALL MAGISK( in my case v20.1 )
INSTALL direct
reboot when asked
congratulations your Emui 9.1 is rooted !!!
Click to expand...
Click to collapse
please upload again the patched 9.1.0.212 .img file, thank you!
currently I'm trying to download stock firmware Indian variant 9.1.0.212(C675E7R1P6) so that I can extract update zip and pick stock recovery_ramdisk.img file to patch with Magisk and use fastboot flash method after it is patched. please let me know if there is something I'm missing or doing wrong. I urgently need some lost files last month. very urgent matter. plz help me if you can
Thankk you....!!! I can not explain how happy I am. God Bless you
nanortemis said:
Updated magisk_patched_9_1_0_210.img - Magisk v20.4 included , added also the original RECOVERY_RAMDISK extracted from 9.1.0.210.
magisk_patched_9_1_0_210.img md5sum = fa2b59807eac66e128653eaebc433aa3
RECOVERY_RAMDISK_9_1_0_210.img md5sum = c62ac7fdc55cb535d1b627b8f17f1842
Click to expand...
Click to collapse
It still works on my EMUI 9.1.0.210 C636.
Follow the instruction on the second half of the original post, and then download these files from the link by nanortemis.
1. Put the device into fastboot mode by connecting the USB cable to the PC and long press "Vol -" button
2. Install adb, and run
fastboot flash recovery_ramdisk magisk_patched_9_1_0_210.img
fasboot reboot
3. boot into the device, and then open the magisk app, you shall see a pop-up asking for reboot again, click on ok.
4. reboot... and yeap... you're rooted.