Good morning everyone, I’m going to show you how to root the Huawei Mate S in last version B361 with the last binaries of SuperSU without get bootloop/brick.
After update to B361, we have to extract the recovery.img from B321 version.
We are going to use the method of Eloy: http://www.htcmania.com/showthread.php?t=1140056
1. We have 3 steps in this method, in the step 3 we have to enter to the folder named “data” and erase the archive “stock”, then we copy the backuped recovery.img from B321 and rename it to “stock”.
2. Then we have to start with the step 1, after flash TWRP we enter to it and BACKUP the partition SYSTEM.
3. After that, we install the SuperSU version of Eloy (2.62).
4. Then we go to BACKUP again and backup the BOOT partition.
5. Finally we install the last version of SuperSU (2.76), then we go to main menu of TWRP and RESTORE the BOOT partition.
6. We restart de Smartphone, it will take a couple of minutes and we have the phone rooted!
NOTE: If we want to remove root, we just have to go to TWRP and RESTORE the SYSTEM partition, then we use de “Step 3” of Eloy Method.
Good luck people, I’ll answer your questions.
Hello, it looks as a good method but I have questions to the description - not clear for me is: 1. We have 3 steps in this method, in the step 3 we have to enter to the folder named “data” .... 2. Then we have to start with the step 1 (which one is step one) , after flash TWRP.... (Which one is the step 2?) It look like beginning with step 3, following with step 1, after flash TWRP and then Point 3.,4.,5.,6 ? - it confuses me. Okay, I see the link to Eloy, but I cannot unterstand Italien. Could you pleas so kind, to descripe also the steps 1-3? Thank you.
Tecalote said:
Hello, it looks as a good method but I have questions to the description - not clear for me is: 1. We have 3 steps in this method, in the step 3 we have to enter to the folder named “data” .... 2. Then we have to start with the step 1 (which one is step one) , after flash TWRP.... (Which one is the step 2?) It look like beginning with step 3, following with step 1, after flash TWRP and then Point 3.,4.,5.,6 ? - it confuses me. Okay, I see the link to Eloy, but I cannot unterstand Italien. Could you pleas so kind, to descripe also the steps 1-3? Thank you.
Click to expand...
Click to collapse
It's spanish, but i will explain you...when i say step 1, 2,3 are the steps from Eloy metod in this link: https://goo.gl/NZ3I8v
the step 1 is TWRP, step 2 is SuperSU (2.62 in Eloy metod), ant step 3 is return to recovery stock (only if you want to remove the root and update your pone).
MY point 1. is replace the recovery in the step 3 in the Eloy method (because that recovery is from the beta and we need the recovery from B321, this is in the file "data" inside the file "PASO 3 RECOVER STOCK")....but this is optional like i said, only if you want to remove root and put recovery stock.
Thank you
sending ´recovery´ (24454 KB)...
OKAY [ 0.522s]
writing ´recovery´...
FAILED (remote: Command not allowed)
finished. total time: 0.523s
CRRUL00C185B360 PHONE UNLOCKED ,FRP UNLOCK .
it show me this trouble
this is for L09, not UL00
Related
Regarding the ROM:
http://forum.xda-developers.com/show....php?t=1867462
I'm a little confused. I was following the flash instructions:
Directions to flash:
1: NANDROID BACKUP
2: Download your ROM to your SD Card
3: Reboot into recovery, wipe data + cache
4: Install the rom
5: If Rom bootloops retry step 4
I was able to successfully get to flashing the ROM. However, I kept on getting a message to find the update.zip file and flash. But I didn't have an update.zip sitting on my phone and was a bit nervous. I pointed back to the miui-bean-beta.zip file. Also the upper right hand corner said slightly different values (93%, 95%). I had to do this a few times before it finally finished. But it wasn't clear to me what "finished" means....
Questions:
a) regarding the directions, just what does step 5 mean???
b) did I need to rename my miui-bean-beta.zip file to update.zip?
RandRMu3ll3r said:
Regarding the ROM:
http://forum.xda-developers.com/show....php?t=1867462
I'm a little confused. I was following the flash instructions:
Directions to flash:
1: NANDROID BACKUP
2: Download your ROM to your SD Card
3: Reboot into recovery, wipe data + cache
4: Install the rom
5: If Rom bootloops retry step 4
I was able to successfully get to flashing the ROM. However, I kept on getting a message to find the update.zip file and flash. But I didn't have an update.zip sitting on my phone and was a bit nervous. I pointed back to the miui-bean-beta.zip file. Also the upper right hand corner said slightly different values (93%, 95%). I had to do this a few times before it finally finished. But it wasn't clear to me what "finished" means....
Questions:
a) regarding the directions, just what does step 5 mean???
b) did I need to rename my miui-bean-beta.zip file to update.zip?
Click to expand...
Click to collapse
A- Bootlooping is when you see the boot animation, phone shuts off and reboots. Rince and repeat. This obviously didn't happen to you
B- The link you provide isn't good so I can't verify what you mean by having to flash update.zip
Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.
Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!
Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!
Reserved for Mac instructions.
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.
Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.
Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).
tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...
@tennear
As far as u know TWRP is the same for every A7, sign or not.
DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?
nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.
I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.
The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.
Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti
So I have a p10, and decided to see what i could do with it. Having little experience, I managed to get somewhere. Unlocked the bootloader, got twrp, installed it with the command fastboot flash recovery recovery.img and got:
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 1.012s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 1.222s
WOOT! Awesome! No problems! Then I issued: fastboot boot recovery.img
And got
downloading 'boot.img'...
OKAY [ 1.020s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.030s
WTF?!
So after a bit, I misread and flashed boot.img with: fastboot flash boot boot.img
I guess I flashed the wrong image. I dunno. But now it boots into the screen that tells me "Your device is unlocked and can'r be trusted" tells me its booting, reboots, goes to the same screen again, says its rebooting again, then brings me to Huawei eRecovery. I connect to my wifi network, telling it to download the latest version and recover, and it says "getting package info failed" So I ma stuck with a device that won't boot.
Oh yes, and down volume and power don't bring me to fastboot anymore.
Begging for help here please.
Do the whole rebranding to unbrick, not sure if you flashed wrong image on boot.
Advice: When flashing recovery boot it by powering off and using key combo. Or adb command. Not from fastboot as IMG.
I did a google search on rebranding to unbrick, and found a guide on the 9. So I assume its similar. It first tests me to boot into twrp. I can't. Twrp never got installed. The next step is to get the offical firmware and put it on the SD card. I can't find it. I am in Canada, and can't find any firmware for canada, nevermind anything north american. It is however possible I have found the wrong guide, as I don't really know what I am doing. As a complete noob, links to guides would be nice when possible and available when making recommendations.
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
okay, i know you are trying to be helpful, but I just can't follow it...
You said "Download Update ZIP. I suggest rebrand to VTR-L29 C432 !" Which one of them? Is the B just a build number, and I should get the latest? please remember, you are talking to a noob.
You talk about 3 files, update.zip, update_data_public.zip and update_all_hw.zip Do I need them all? If so the last one, where I change filelist.xml to all /cn/update_full_all_cn.zip doesn't work. See the following link http://update.hicloud.com:8180/TDS/.../v92067/f2/full/all/cn/update_full_all_cn.zip
Also, rename the file, "Where spcseas is the model of the file you are downoloading" Huh? I know I have to replace the word spcseas with something, but with that?
Now it says to run update.bat Whats the point? I have not been directed to plug the phone into the computer, and even if I did, the computer won't recognize it because I can't get it into any mode... Where do I put these files? They all go in the same directory? I just can't follow this guide as much as I try..
THERE IS GOOD NEWS HOWEVER!
I have been able to get it into TWRP! This means I can get into fastboot, which means I can re-flash the correct boot.img, IF I can get my hands on it (and assuming that's the actual issue It likely is. It was working until I flashed this other boot.img file.). So if I can get direction on how to get it, I should be okay. Double triple and quadruple bonus points for just providing me a direct link to the boot.img file to use without having to play around trying to follow guides I can't seem to understand.
UPDATE!!
Now although I can get into TWRP, its hit and miss, but I can get there eventually, it will no longer boot into fastboot/recovery. When I click reboot, and choose bootloader in TWRP, it just freezes..
This is getting frustrating. Apparently getting into the bootloader is hit and miss, but i can do it.
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
smariob said:
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
Click to expand...
Click to collapse
Thats good to know. I was getting TWRP more often when I did it from off. What was happening was I would holds power and volume up, release power when the logo appeared, and MOST of the time I would boot into TWRP. Sometimes it would just reboot, I would continue to hold up, and it would either reboot, or boot into TWRP. Occasionally I would get the recovery that came with the phone ?!?!
In any event, I managed to get into TWRP, boot into recovery, extract the boot.img, flash it... AND IT WORKED! Phone booted!
So after all this, I backed up EVERYTHING I could using TWRP. The Boot partition, System partition, EVERYTHING! It kept failing on the Data partition, but from my research that wasn't that important anyway. I then installed SuperRoot_noverity_nocrypt.zip, rebooted, installed phh's SuperUser, installed Root Checker, and finally, I have root!!
Thank you so much for the help. About to go "thank clicking" for all the help you provided.
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 29.08.2019] Added new download locations for raw images
[Update 07.01.2019] Added more current raw image for ZS620KL WW 80.30.96.111
[Update 25.10.2018] Added raw image for ZS621KL.
[Update 09.08.2018] Updated for 80.11.37.95 and future versions.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as of 20.07.18 is 80.11.37.86. Newer versions will work too!
This guide is written for firmware 80.11.37.86. If you do not want to upgrade/downgrade to 80.11.37.86 you will need to use the firmware (zip file from ASUS) you are on in all the steps.
If you upgrade your firmware to a newer version AFTER rooting it you will lose root! You will need to patch the boot.img of the new firmware again > follow the rooting guide.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty! Currently there is no method known to relock it!
You will get a warning message about your unlocked bootloader at every boot.
You will no longer receive OTA updates but you can download the new firmwares directly from Asus.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware (ZS620KL WW):
WW 80.10.8.54
https://www.androidfilehost.com/?fid=1899786940962570681
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
WW 80.30.96.111
https://www.androidfilehost.com/?fid=1899786940962570682
https://drive.google.com/file/d/16OgxiPFSDJwhitnqJaITuO-XPOrg_7q9/view
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by amscova.
raw firmware (ZS621KL):
https://addrom.com/raw-rom-unbrick-for-asus-zenfone-5z-zs621kl/
https://www.androidfilehost.com/?fid=1899786940962570680
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by B Nath.
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware from 80.11.37.86 up with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this. There is currently no method know to relock the bootloader.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
flashall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide, GSPD and amscova for providing the ZS620KL raw image links and B Nath for finding the ZS621KL raw image.
Nice Theard
Thank You for your work
Upgrade after rooting
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
Click to expand...
Click to collapse
Process is too long. I am working on unofficial Unlock Tool so that we can retain the warranty.
For downgrading, there is a tool for that. For me, fastboot codes may mess up the system/cache partitions.
If anyone wanna test my unlocking tool, feel free to PM me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
mihaitaiosub said:
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
Click to expand...
Click to collapse
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
isthisadagger said:
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
Click to expand...
Click to collapse
And is not possible to root again whith method described on this thread?
mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
This is why we need TWRP.
mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
It is possible with Magisk Manager 5.8.3.
isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as iof 20.07.18 is 80.11.37.86.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
This guide is written for firmware 80.11.37.86. If you do not want to upgrade to 80.11.37.86 you will need to use the firmware you are on in all the steps.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty!
You will get a warning message about your unlocked bootloader at every boot.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware:
https://drive.google.com/file/d/1ogbQeeNDRPFCb9jl3kpRDK_DmsneQ0xL/view?usp=drivesdk
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware up to 80.11.37.86 with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
patchall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide and GSPD for providing the raw image name.
Click to expand...
Click to collapse
Does unbricking lock the bootloader back since we will be flashing a raw a file.
With Magisk Manager 5.8.3 the whole guide works like a charm
THX
My Zenfone 5z isn't being detected in fastboot mode, kindly help with correct driver softwares, my PC is running on Windows 10
Update : I got my phone to detect in fastboot
How to wipe cache partition
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
chandru.biradar2 said:
Does unbricking lock the bootloader back since we will be flashing a raw a file.
Click to expand...
Click to collapse
No.
kelly66 said:
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
Click to expand...
Click to collapse
Honestly killing the cache rarely helps things.
hi guys how to do this on Macbook pro? Any clues?
shantanudl said:
hi guys how to do this on Macbook pro? Any clues?
Click to expand...
Click to collapse
I do not have any experience with mac os but if you want to root:
Adb/fastboot is available for mac os. All you need to do is find a tool to extract the boot.img from the payload.bin.
If you want to downgrade/unbrick: You would need to convert the bat/cmd files in the full firmware to some shell scripts and exchange the fastboot.exe.
How do I un-root, re-lock bootloader?
ferez said:
How do I un-root, re-lock bootloader?
Click to expand...
Click to collapse
unroot: You press "uninstall" in magisk manager or install an updated firmware without patching boot.img or downgrade.
I have not tried re-locking the bootloader.
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
jens13 said:
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
Click to expand...
Click to collapse
You won't get OTAs + your warranty is voided (due to unlocking Officially)
Yes, you can update your phone by sideloading the zip from ASUS Support Website
Hello,
I see some people are having trouble unlocking Oppo A37f bootloader, for example: Oppo Tools doesn't work.
I made this guide to help you unlock your phone bootloader.
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICE.
BY USING THIS GUIDE YOU UNDERSTAND THE RISK FOR BRICKING YOUR PHONE
REQUIREMENTS:
1) A working brain (must have)
2) A working PC (With Windows Installed)
3) Basic Windows command line knowledge
4) Basic ADB knowledge (Download here)
5) USB Cable (duh)
6) The bootloader unlocker (See attachments)
7) TWRP 3.1.1.0 recovery image made by KoSett (Download here) or
TWRP 3.2.3.0 recovery image made by Yashraj22 (Download here)
8) Zip for disabling dm-verity (Download here, Place it on your phone)
9) Firehose for unlocking (See attachments)
10) Hex editor (HxD Recommended, Download here)
11) Firmware With the version number of Oppo_A37F_EX_11_A.14_161014 otherwise, it will not work (Download the firmware to flash here)
12) Qualcomm USB Driver (Download here)
GUIDE TO UNLOCK YOUR PHONE BOOTLOADER:
Assuming you have extracted all file, Let's start unlocking your phone bootloader!
Step One: Enter download mode using this adb command: adb reboot edl
Step Two: Start "dump_devinfo.bat" and enter your phone COM number *SEE NOTE 1 TO SEE YOUR PHONE COM NUMBER*
Step Three: Enter the ABSOLUTE path to the firehose file
Step Four: After dumping your devinfo.img, open the image using Hex Editor
Step Five: Edit your devinfo.img EXACTLY TO THE IMAGE ATTACHED.
Step Six: Save the edited devinfo image and start "unlock.bat" and enter your phone COM number *SEE NOTE 1 TO SEE YOUR PHONE COM NUMBER*
Step Seven: Enter the ABSOLUTE path to the firehose file
Last Step: Long press the power button to start your phone again, And Voila! Your Phone bootloader has been unlocked!
GUIDE TO INSTALL TWRP AND DISABLE DM-VERITY:
Step One: Enter download mode using this adb command: adb reboot edl
Step Two: Open your command prompt on your working directory and type this command: "emmcdl.exe -p "YOURPORTNUMBER" -f "ABSOLUTEPATHTOFIREHOSE" -b recovery recovery.img" if you are confused see this example: "emmcdl.exe -p COM4 -f C:\WORKING\DIRECTORY\prog_emmc_firehose_8936.mbn -b recovery recovery.img"
Step Three: Long press the power button to start your phone again.
Step Four: Reboot your phone into recovery by using this command: adb reboot recovery
Step Five: Flash the zip you have placed in your phone
Last Step: Reboot to your system and WE'RE DONE!
NOTE:
Note 1: Press Win+R and enter devmgmt.msc and see your phone COM number
CREDITS:
Naveen3Singh at github for his awesome bootloader unlocker tool
KoSett for porting TWRP 3.1.1.0
Yashraj22 for porting TWRP 3.2.3.0
Me for writing this guide
Please hit thanks if this method worked and bye!
EDIT:
Edit 1: Added TWRP 3.2.3.0 by Yashraj22
You can try flashing this rom: here
But i still haven't tested the rom yet.
That worked even with the newer version of the stock ROM still installed (2017-something).
What I did is I dumped the devinfo partition with https://github.com/bkerler/edl, edited it in the hex editor, flashed it back and then TWRP installed, booted and works.
LineageOS 17.1 works as well (except some minor things, like the FM Radio)
Thank you very much.
God it works great. Only the twrp flash step is the most confusing. I don't quite get it yet, but there's a way around it anyway. Root with kingo root then use oppo tools to flash twrp
can anyone help me with step 2
how to enter com number with this cammand dump_devinfo.bat
jron999 said:
God it works great. Only the twrp flash step is the most confusing. I don't quite get it yet, but there's a way around it anyway. Root with kingo root then use oppo tools to flash twrp
Click to expand...
Click to collapse
Yeah, im planning to edit this guide to make it much easier