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
If you want to try [EUI 5.8.016s], then use the instruction below!
[INTRODUCTION]
As you know, this firmware comes with a purchase in the store and if you update your phone, you will not be able to return to the later version. But on the Russian site 4pda.ru, I found a link to this firmware in the form of a backup copy! Well, let's begin!
[INSTRUCTIONS]
1.Download backup mega.nz/#!F0t1UaiJ!vWzUqmzRAmFEYyda0irj_kawevPHA2tM-KrvmlAaqcs [/url] (you may need to register)
2.And so, the archive was downloaded. You open it and there will be a folder under the name (1970-01-01--00-57-22_IMXOSOP5801607291S_release-keys). I advise not to rename!!!
3.Install any TWRP
1)Reboot the phone in Fastboot mode
2)Connect the phone to the computer, open the CMD in the folder where your TWRP
drive.google.com/file/d/0B5wIfEFfXmRbbVlUN2EwdGdRS1k/view [/url]
and write: fastboot oem unlock-go
fastboot flash recovery twrp-3.0.3-20170117-s2-codeworkx.img
4.Copy the backup to /TWRP/BACKUPS/Your Serial Number/
5. After copying the backup , we boot into TWRP
1) Turn off the phone
2) Press the power button and the volume key +.
6.In TWRP click on the item RESTORE and select our backup, select all recovery points and swipe to restore
7.voila. you now have EUI 5.8.016s [official stock].
/
If you have a problem in copying a file larger than 4 gigabytes - follow the instructions below!
1.A file that has a size of 4 gigabytes must be added to the archive using WinPaR
2.Copy the archive to a folder with a backup and in this folder, unpack it into this folder where it is located
3.Delete the archive and leave the file 4 GigaBytes in size and copy to this folder the remaining files
4. As a result, your backup should have a size of 7.29 gigabytes
5.follow step 6!
///////////////////////////////Do not forget to say thank you!\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
So i'm very very new to rooting, soon i'll got my hand on a mi 9t pro and i want to try root it.
I got some gist from reading the guide here and since i want to have OTA updates without the need to flash custom, i thought that rooting with Magisk without TWRP is a good option.
I do have some confusions regarding the method. So unlocking is obviously the first step, which i think is pretty straightforward. Then i need to root Magisk by patching a stock boot image, i assume this is the fastboot stock firmware of my current phone, correct me if i'm wrong.
Does doing it this way risk bricking my device? Usually people suggest to backup the current ROM with TWRP first before doing anything, or can i backup my ROM with other method?
What kind of precaution do i need to pay attention to? And is it actually recommended to do it this way?
yeah, no this has a high hard-brick risk i think. its safer to just flash TWRP and install it trough that, then you can always go back to stock recovery if you wanted to.
dev-DaT said:
yeah, no this has a high hard-brick risk i think. its safer to just flash TWRP and install it trough that, then you can always go back to stock recovery if you wanted to.
Click to expand...
Click to collapse
Could you help point me to any guide thread for flashing MIUI stock recovery back while keeping the root?
thanks for replying
arcwindz said:
So i'm very very new to rooting, soon i'll got my hand on a mi 9t pro and i want to try root it.
I got some gist from reading the guide here and since i want to have OTA updates without the need to flash custom, i thought that rooting with Magisk without TWRP is a good option.
I do have some confusions regarding the method. So unlocking is obviously the first step, which i think is pretty straightforward. Then i need to root Magisk by patching a stock boot image, i assume this is the fastboot stock firmware of my current phone, correct me if i'm wrong.
Does doing it this way risk bricking my device? Usually people suggest to backup the current ROM with TWRP first before doing anything, or can i backup my ROM with other method?
What kind of precaution do i need to pay attention to? And is it actually recommended to do it this way?
Click to expand...
Click to collapse
1. Download the fastboot ROM you currently have installed on your device.
2. Extract the boot image from downloaded zip
3. Keep 1 copy of boot image in your PC (For Backup, in case anything goes wrong)
4. Now copy the boot image in your phone's internal storage.
5. Install Magisk Manager App
6. Open and Tap Install
7. Select "Patch Boot Image"
8. Select the boot image you copied in your phone and follow the on screen instructions.
9. Now there should be a new .img file created in the download folder of your phone. ( I guess named something like magisk_patch.img, not sure of name but you do understand right?)
10. Copy that .img file in your PC.
11. Now connect your phone to your PC in Fastboot mode.
12. Open the folder where you copied it in your PC.
13. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
14. Now type the command "fastboot flash boot filename.img",
let the process complete.
15. Reboot.
16. Profit.
This method should work fine without any issues but if anything goes wrong:
1.Connect your device to your PC in fastboot mode.
2. Open the folder where you kept the boot image (in step 3)
3. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
4. Now type the command "fastboot flash boot boot.img" (without quotes),
5. let the process complete.
6. Reboot
P12AV33N said:
1. Download the fastboot ROM you currently have installed on your device.
2. Extract the boot image from downloaded zip
3. Keep 1 copy of boot image in your PC (For Backup, in case anything goes wrong)
4. Now copy the boot image in your phone's internal storage.
5. Install Magisk Manager App
6. Open and Tap Install
7. Select "Patch Boot Image"
8. Select the boot image you copied in your phone and follow the on screen instructions.
9. Now there should be a new .img file created in the download folder of your phone. ( I guess named something like magisk_patch.img, not sure of name but you do understand right?)
10. Copy that .img file in your PC.
11. Now connect your phone to your PC in Fastboot mode.
12. Open the folder where you copied it in your PC.
13. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
14. Now type the command "fastboot flash boot filename.img",
let the process complete.
15. Reboot.
16. Profit.
This method should work fine without any issues but if anything goes wrong:
1. Connect your device to your PC in fastboot mode.
2. Open the folder where you kept the boot image (in step 3)
3. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
4. Now type the command "fastboot flash boot boot.img" (without quotes),
5. let the process complete.
6. Reboot
Click to expand...
Click to collapse
wow this is worthy of its own thread imo. nice!
P12AV33N said:
1. Download the fastboot ROM you currently have installed on your device.
2. Extract the boot image from downloaded zip
3. Keep 1 copy of boot image in your PC (For Backup, in case anything goes wrong)
4. Now copy the boot image in your phone's internal storage.
5. Install Magisk Manager App
6. Open and Tap Install
7. Select "Patch Boot Image"
8. Select the boot image you copied in your phone and follow the on screen instructions.
9. Now there should be a new .img file created in the download folder of your phone. ( I guess named something like magisk_patch.img, not sure of name but you do understand right?)
10. Copy that .img file in your PC.
11. Now connect your phone to your PC in Fastboot mode.
12. Open the folder where you copied it in your PC.
13. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
14. Now type the command "fastboot flash boot filename.img",
let the process complete.
15. Reboot.
16. Profit.
This method should work fine without any issues but if anything goes wrong:
1.Connect your device to your PC in fastboot mode.
2. Open the folder where you kept the boot image (in step 3)
3. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
4. Now type the command "fastboot flash boot boot.img" (without quotes),
5. let the process complete.
6. Reboot[/QUOTE
target reported max download size of 805306368 bytes
sending 'boot' (40948 KB)...
OKAY [ 0.905s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.920s
Click to expand...
Click to collapse
Unlock the bootloader first
wall.e said:
P12AV33N said:
1. Download the fastboot ROM you currently have installed on your device.
2. Extract the boot image from downloaded zip
3. Keep 1 copy of boot image in your PC (For Backup, in case anything goes wrong)
4. Now copy the boot image in your phone's internal storage.
5. Install Magisk Manager App
6. Open and Tap Install
7. Select "Patch Boot Image"
8. Select the boot image you copied in your phone and follow the on screen instructions.
9. Now there should be a new .img file created in the download folder of your phone. ( I guess named something like magisk_patch.img, not sure of name but you do understand right?)
10. Copy that .img file in your PC.
11. Now connect your phone to your PC in Fastboot mode.
12. Open the folder where you copied it in your PC.
13. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
14. Now type the command "fastboot flash boot filename.img",
let the process complete.
15. Reboot.
16. Profit.
This method should work fine without any issues but if anything goes wrong:
1.Connect your device to your PC in fastboot mode.
2. Open the folder where you kept the boot image (in step 3)
3. Now press and hold shift on you keyboard and right click on empty space in folder and select "Open Command Window Here".
4. Now type the command "fastboot flash boot boot.img" (without quotes),
5. let the process complete.
6. Reboot[/QUOTE
target reported max download size of 805306368 bytes
sending 'boot' (40948 KB)...
OKAY [ 0.905s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.920s
Click to expand...
Click to collapse
You must unlock bootloader first.
Click to expand...
Click to collapse
dev-DaT said:
wow this is worthy of its own thread imo. nice!
Click to expand...
Click to collapse
Does magisk ask for additional installation after u flash patch boot? And can u flash zip module via magick.
deleted
P12AV33N said:
1. Download the fastboot ROM you currently have installed on your device.
[...]
Click to expand...
Click to collapse
where can I download "my" fastboot ROM ?
I have: MIUI-V11.0.5.0.QFJMIXM
Xmaster111 said:
where can I download "my" fastboot ROM ?
I have: MIUI-V11.0.5.0.QFJMIXM
Click to expand...
Click to collapse
Wrong forum, you have a Mi 9T, this is the 9T Pro forum.
Anyway, look here.
https://c.mi.com/oc/miuidownload/detail?guide=2
If viewing on a phone you'll probably need to view the page in desktop mode, otherwise you'll see a blank page.
In step 2 of the guide look for the link
★ Xiaomi Mi 9T Latest Global Stable Version Fastboot File Download
It's not too far down the list.
Hi, I have unlock the boot loader and root my pixel 4a 5g in february update.
I don't understand how update it when new update comes ?
I can update it with Ota when comes in settings/System/Update ?
Or I do flash system image with fastboot and then flash the boot.img with Magisk to flash it in Fastboot mode ?
But I see : Flashing a new system image deletes all user data !!?
Before on Oneplus and later Xiaomi is more easy with Twrp. But now it's very complicated to update my freshly updated Pixel 4a 5g and Root
Please that it is the easiest procedure to update every month with Magisk installed. Previously I stopped all the Mods installed so as not to have a similar bootloop for Substartum .. Thank you
Thanks
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
weissbierdood said:
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
Click to expand...
Click to collapse
Thank you very much.
Have a good day..
I have now the good procedure to update it. Thanks
Just trying to get a confirmation if I wanted to start rooting my device should I wait or is this the model I need to use?
slimjimz81 said:
Just trying to get a confirmation if I wanted to start rooting my device should I wait or is this the model I need to use?
Click to expand...
Click to collapse
You must use the Boot.img corresponding to the rom and the code name of your device (ROSEMARY).
2 methods:
With the TWRP https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/rosemary/
download Magisk app and rename it to Magisk.zip then flash it with TWRP.
or
1. Find or redownload the TGZ file for your current ROM or other rom.
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img(*****command modified if necessary, A/B partitions).
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.