Related
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now
* introduction *
Hello,
before you hate me, please let me to say why I wrote this guide- it is for ultra noob guys, beginners or just for organize almost all files for tweaks and fixes for this phone. Because I noticed myself that it was beginning to make a mess with it, so I decited to write this guide which (what I mensioned) contains tweak and fixes to known bugs that are in the software.
Ready? Staddy? GO!
* warning *
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you.
*
*/
I. Bootloader unlocking
We will start our journey in a beautiful world modified by android with unlocking the bootloader.
What is it?
Bootloader is something like BIOS from computers but in the phone. It let you to boot many software, like recovery. We can't boot directly into recovery without unlocked bootloader because phone has got some closed startup procedure (like POST test in computers). To break it, we must unlock bootloader.
So how to do that?
We must:
1. Download RAR file and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS and go the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Bootloader successfully unlocked.
II. Install TWRP
After unlocking bootloader, we need some recovery to install custom software on our beast.
To do that:
1. Download this TWRP (F2FS support) and place it into unlock folder
2. Reboot into fastboot
3. Connect the phone into PC
4. In unlock folder, run cmd and type "fastboot devices". You should see some device plugged into your PC.
5. Type "fastboot flash recovery XXX.img" when XXX means the name of recovery.
6. When installing process finish, press volume down + power as long as you doesn't see fastboot warning.
7. Phone will get into TWRP.
To get into TWRP just presss volume down + power until you doesn'ts see fastboot warning.
III. Decrypt enrypted data
1. Download the decrypt.zip and copy to SDcard
2. Flash in recovery
3. Format /data
4. Reboot
IV. Flashing custom ROMs
Now the main aim of customization: CUSTOM ROM <3 It let you to do many modifications like style of font in system, theme, newer version of software and many many more.
Just:
1. Copy all your necessary software into SD card
2. Boot your device into TWRP
3. Go to "install", pick firmware which you need and swipe to flash
4. Repeat step 3 with gapps
5. Reboot to system
When you want to install some kernel or NXP or magisk or something else, don't do that after flashing system. Before, flash firmware, system and gapps, reboot and configure. Then go to TWRP and flash 3rd party mods.
V. Unlocking Camera2API
To get GCAM work property, we need to unlock camera2api. If you don't know what's that, go there -> https://www.thegeeksclub.com/camera-2-api-check-smartphone-support/
1. Power off the phone and enter fastboot mode.
2. Fire up fastboot terminal and connect your phone to the pc, enable USB debugging mode from dev. options too.
3. Run the command: fastboot oem enable_camera_hal3 true
4. Type: fastboot reboot
VI. Magisk
Just to get root permissions. If you don't know what it is, go there -> https://www.xda-developers.com/what-is-magisk/
1. Go to TWRP and flash this file
2. Reboot to system
3. Install .apk
VII. Some other useful files
TWRP: https://drive.google.com/open?id=1dhjV0p00AiZ83eF5iUA6o9fdx6zsQYTF
GAPPS: https://opengapps.org
CUSTOMROMS: https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development
FIRMWARES:
339 https://drive.google.com/open?id=1EIRZ1HrJQaOynq48lfhYWaHd9L0fhPU5
Pie https://drive.google.com/open?id=1xwFFadooMD2DJqI9dClcCuojAFwHfdtV
NXP: https://drive.google.com/open?id=1lfRGXlf3q53kLMZDOvLe4jMr3szQPLQd
MAGISK:
.zip https://drive.google.com/open?id=1HrZUdL7ZgVWfuDg7PWOL_DZrwsmNzrRf
.apk https://drive.google.com/open?id=1jFee8Mx0pwCcyE729h33gyfaIfHxNgVI
GCAMS:
Arnova https://drive.google.com/open?id=1R1Sfw0DdKXZxYWDkEvH8ODpWHkUjnkxk
MGC https://drive.google.com/open?id=1YowAmosszfoCJCORjcwE7OQzxOuqY7ql
If you have any observations, remarks - write to me!
Thanks for all XDA community,
~ALYSKY
Reserved
Sir can you plz tell me does this method works on 6gb varient? With firmware version .340
Is this method for XOOT or XOOTD?
My model is XOOTD ....
Dewashish03 said:
Sir can you plz tell me does this method works on 6gb varient? With firmware version .340
Is this method for XOOT or XOOTD?
My model is XOOTD ....
Click to expand...
Click to collapse
I tested it on 4/64 X00TD variant and it worked.
ALYSKY said:
I tested it on 4/64 X00TD variant and it worked.
Click to expand...
Click to collapse
Thax for replay...
Does this twrp can be flashed successful on .340 and pie?
Do we need different versions of twrp to flash on different android version like .239 .240 and pie?
Dewashish03 said:
Thax for replay...
Does this twrp can be flashed successful on .340 and pie?
Do we need different versions of twrp to flash on different android version like .239 .240 and pie?
Click to expand...
Click to collapse
It doesn't matter. You can use the same version of TWRP on different version of firmware.
can this method work on X00TD android pie stock rom. @ALYSKY
unable to install twrp, the drivers are well installed, the bootloader is to unlock I use the original cable usb, I try on several usb port, always the same error message
failed remote requested download size is more than max allowed
my model X00TD
please help me
I have installed twrp recovery and can boot into it but i cant find the magisk or decrypt files to swipe in the recovery. please help
noob858 said:
I have installed twrp recovery and can boot into it but i cant find the magisk or decrypt files to swipe in the recovery. please help
Click to expand...
Click to collapse
U need to put them in your sd card and then you have to select storage (external) and then flash them
lokesh773 said:
U need to put them in your sd card and then you have to select storage (external) and then flash them
Click to expand...
Click to collapse
ok im supernoob at this. nut how do i put it to sd card?? i mean i dont have any sd card inserted.
noob858 said:
ok im supernoob at this. nut how do i put it to sd card?? i mean i dont have any sd card inserted.
Click to expand...
Click to collapse
Use pc to transfer it to sd card....if you dont have sd card you can use pendrive...
Every NKOTB is desperate to post his/her/it's thread / YouTube video for such guide/s, quoting stuff from other's posts / threads and sharing their hard work, without the basic decency to quote and credit the original thread / guy who posted in the first place. Please do so or this thread will be reported for plagiarism.
angixspirit said:
unable to install twrp, the drivers are well installed, the bootloader is to unlock I use the original cable usb, I try on several usb port, always the same error message
failed remote requested download size is more than max allowed
my model X00TD
please help me
Click to expand...
Click to collapse
have you tried to install the driver?
I've updated my phone to latest official pie (.053) . Does these steps still applicable or there is any changes? Please kindly update the guide if there is any changes.
guys i tried to flash recovery but after that.. it does nothing.. i just got blank screen. No TWRP screen
Update 1 : Without TWRP I was able to install Magisk via Manager but after flashing patched image file. I now no longer able to start mobile.. it always gets to recovery screen. somebudy help
Update 2 : I used another boot image and patched it with Magisk and now I am able to boot phone but now it stuck on logo screen
Update 3 : I was using totally differnt boot image .. I extracted it from offical stock rom. Now I booted my phone also did root. Now question is how to install TWRP and dyscript.zip
Update 4 : TWRP or RWRP not working so Now I am not able to decrypt my phone. Help
hi why theres a password in twrp?
ALYSKY said:
* introduction *
1. Download RAR file and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS and go the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Bootloader successfully unlocked.
Click to expand...
Click to collapse
Hi,
First of all, thank you for the detailed steps and instructions.
I downloaded the RAR mentioned in the step 1 above. When I click open after downloading, there's an error preventing me to open. I also tried extracting but I'm unable to do so.
Please provide me the updated link or reupload the file so that I can download it,
Thanks.
unlock.bat file is missing is the unlock folder...what to do?
this is showing when trying to istall twrp
what to do?
@ALYSKY
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
A guide to unlock bootloader, flash a custom recovery and root your Redmi Note 8/8T device :
1. UNLOCKING BOOTLOADER :
Backup your data first. Unlocking will erase your data.
- Enable Developer Options in your phone by tapping the "MIUI Version" 7 times in About Phone.
- Go to Settings > Additional Settings > Developer Options.
- Enable OEM Unlocking, USB Debugging and USB Debugging (Security Settings) .
- Also add account in Mi Unlock Status (Can be found in Developer Options).
- Install the required ADB and Fastboot drivers in your PC from here.
- Download Mi Unlock to PC from here, and sign in with your Mi Account.
- Shut down your phone manually, and hold volume down key and power button to enter Fastboot mode.
- Connect your phone to PC using USB cable and click "Unlock" in Mi Unlock Tool.
- You will be given a specific time (168 hours usually).
- Wait for the given time. Make sure to use your phone and don't log out of your mi account from the phone or reset your device.
- Once waiting time is over, redo Unlock process.
- Your phone will be unlocked successfully.
2. FLASHING TWRP :
- Install the required ADB and Fastboot drivers in your PC if not already in step 1. from here.
- Download TWRP from here.
- Put that TWRP in the ADB and Fastboot installed folder (mostly C:\Program Files (x86)\Minimal ADB and Fastboot).
- Rename that recovery(TWRP file) to "recovery" for convenience (optional).
- Click on Start Menu, type cmd
- Right click and select Run as administrator
- Then type:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type:
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode either manually by shutting down phone and then holding volume down key and power button or by:
Code:
adb reboot bootloader
- Once in Fastboot mode type:
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type(hit ENTER after each line):
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
- Now your phone will boot into TWRP.
OPTIONAL STEPS (Not Recommended): Encryption is always recommended for better security. However if you don't want encryption in your device, follow these steps. Again, not recommended.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your data so make sure your data is backed up]
- Go back to TWRP home and Reboot > Recovery.(Don't reboot system or else you will have to repeat whole process again).
- Done
3. ROOTING :
- Download Magisk zip to PC from here.
- Download Universal DM-Verity and ForceEncrypt disabler from here. (Only required if you followed optional steps.)
- When in TWRP transfer the file(s) to phone and go to Install.
- Here select Magisk zip file and swipe to flash.
- Then select Universal DM-Verity and ForceEncrypt disabler zip and swipe to flash(Make sure to flash this at last or else phone won't boot). (Only required if you followed optional steps.)
- Reboot system.
- Done. Debloat. Enjoy
Links
1. Minimal ADB and Fastboot
2. MI Unlock Tool
3. TWRP
4. Magisk
5. Universal DM-Verity and ForceEncrypt Disabler (OPTIONAL)
If this helped you then hit the Thanks Button. Good Luck.
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
romulocarlos said:
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
Click to expand...
Click to collapse
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
the_weird_aquarian said:
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
Click to expand...
Click to collapse
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
romulocarlos said:
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
Click to expand...
Click to collapse
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
the_weird_aquarian said:
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
Click to expand...
Click to collapse
You're right. Tested right now and worked. Maybe newer Win10 versions are "smarter" than older... who knows...
Well, about the second space, thanks, but you don't need to check with an Google Apps account.
If your phone is decrypted, just open Second Space, configuring it for first time use as you like. Then, on Second Space, go Settings -> Password and security -> privacy. Check if encryption is active.
Thanks again!
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader ?
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you ?
Mozar3lla said:
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you
Click to expand...
Click to collapse
Yes you can root on stock rom. Rooting is not rom specific. You can root on any rom.
Hope it helps.
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
shayanb2004 said:
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
Click to expand...
Click to collapse
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
the_weird_aquarian said:
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
Click to expand...
Click to collapse
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
shayanb2004 said:
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
Click to expand...
Click to collapse
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
the_weird_aquarian said:
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
Click to expand...
Click to collapse
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
shayanb2004 said:
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
Click to expand...
Click to collapse
Make sure to atleast keep your phone turned on.
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
AMJ_Vario said:
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
Click to expand...
Click to collapse
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
romulocarlos said:
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
Click to expand...
Click to collapse
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
AMJ_Vario said:
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
Click to expand...
Click to collapse
In fact, I never used Mi Mover. As each device has its features, I prefer to install apps one by one. My data is on cloud, so for me is easyer.
I suggest you to do the transfer, only for tests, just after you receive your phone. These videos may help you also:
https://www.youtube.com/watch?v=shf-i8z86Ms and https://www.youtube.com/watch?v=ql-f88qllrE
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
shayanb2004 said:
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
Click to expand...
Click to collapse
yes so I have recently flashed orangefox about 2 weeks ago or something. I personally don't use anything other than official twrp, but I flashed orangefox because of it's miui OTA update feature. You can flash if you are planning on staying on stock rom with a decrypted device, as I have dirty flashed stock rom with my decrypted device but it always ends up in bootloop with official twrp. I have to format data everytime. Surprisingly Orangefox solves this issue. Also if you are a fan of theming then it provides a few custom fonts, colors and themes. However if your device is encrypted there's absolutely no reason to switch from official to any other recovery unless you want to customize the looks of your recovery.
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
Links of download at the end of the post.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK WITH WINDOWS
Prerequisites:
A computer with Windows (bruh)
ADB and Fastboot installed
Have installed the device drivers to be detected in fastboot mode.
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.Now it only remains to flash the GSI.
Spoiler: PROCESS OF THE UNLOCK WITH LINUX
Prerequisites:
A computer with Linux (bruh)
ADB and Fastboot installed
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still.
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.Now it only remains to flash the GSI.
If you don't know which GSI to try first, I recommend one from Phhusson, Ermitain or Andy.
NOTE: The system will be encrypted, and in this build of TWRP the encryption is not support so the files of internal storage will appear with numbers and letters random, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
NOTE 3: The GSI architectures for each variant are: A64 AB for 32/2 and ARM64 AB for 64/4.
NOTE 4: If you are going to flash a GSI with GApps you will first have to flash a vanilla Phhusson GSI and start in it, after that you have to flash the GSI with GApps WITHOUT wipes and you can use it normally
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1916 version)
ADB and Fastboot (Windows only): https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/drive/folders/19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-?usp=sharing
Credits:
@eluallen to do the first guide of how to unlock the bootloader and vbmeta file.
@Siddk for the recovery.
@LichtEstarossx for lk file and give some development to pokerp ;-;.
Fastoh said:
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK IN WINDOWS
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI
If you don't know which try first with the GSI of Phhusson or Lineage of Andy
Spoiler: PROCESS OF THE UNLOCK IN LINUX
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI.
if you don't know which try first with the GSI of Phhusson or Lineage of Andy
NOTE: The system will be encrypted, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1924 version)
ADB for Windows: https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/folderview?id=19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-&usp=sharing
Click to expand...
Click to collapse
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
ShotRomsS6edge said:
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
Click to expand...
Click to collapse
Ahí te dice en la imagen, las GSIs compatibles son las que son A64 xd // There it tells you in the image, the compatible GSIs are those that are A64 xd
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
simbanono said:
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
Click to expand...
Click to collapse
What is missing are the drivers, try to download them from this link (is the link that came in the flash tool zip xd): https://androiddatahost.com/276a2
Fixed already ty
.
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
cyanogenmodricky said:
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
Click to expand...
Click to collapse
mmmmm, maybe downgrading to the oldest firmware version you can find
Fastoh said:
mmmmm, maybe downgrading to the oldest firmware version you can find
Click to expand...
Click to collapse
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
cyanogenmodricky said:
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
Click to expand...
Click to collapse
try the version of sp flashtool that uses LMSA
in the log it says which version
Fastoh said:
try the version of sp flashtool that uses LMSA
in the log it says which version
Click to expand...
Click to collapse
ohh ok, i will try it and i tell you if works :3
well i get make downgrade to the lowest version i found, now i can't unlock the bootloader with
fastboot flashing unlock_critical
it gives me "waiting device" :c
edit: i install adb, fastboot and moto drivers, now when i wirte fastboot flashing unlock appears "unknow command"
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Alejandro2810 said:
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Click to expand...
Click to collapse
what SO do you use? windows or linux? because in windows the fastboot mode did not work either ;-;
Fastoh said:
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Click to expand...
Click to collapse
But... How remove battery if this not removable?..
Mortyk said:
But... How remove battery if this not removable?..
Click to expand...
Click to collapse
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Fastoh said:
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Click to expand...
Click to collapse
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Mortyk said:
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Click to expand...
Click to collapse
mmmm, look first trying with lmsa to have as it tells you to do the firmware re-installation, then do the same steps you did in the LMSA but in the flashtool
If you want to downgrade you have to do it with the firmware of the e6s because if you do it with the e6 plus your phone will have birck.
Welcome to my thread. Today I am going to teach you how to install a custom recovery on the device and how to recover the original boot files on the phone to modify them. After modifying those files you will have root on the device. A lot of time and effort has been put into getting this to work. The custom recovery that we will be using is TWRP Recovery.
Note: Modifying your device will void the manufacturer's warranty.
All modifications made to your device are done at your own risk and you claim full
responsibility if the device is damaged or if data is lost.
First, we are going to enable OEM Unlock and USB Debugging. To do so, you will follow the steps below.
1. Sign in to your Mi Cloud Account on your phone.
2. Tap the “Settings” menu on your Mi 11 Ultra, then tap the “About Phone” option.
3. Tap the “MIUI Version” option several times until you see the “You are now a developer” message.
4. Tap the “Additional Settings” Menu, then tap the “Developer options” on your phone.
5. Activate the “OEM Unlock” option, then activate the “USB Debugging” option on your phone.
6. Tap the “Mi Unlock Status” option.
7. Tap “Agree” and then tap the “Add account and device” option on your phone.
8. Turn off your phone, then press the volume down button and the power button simultaneously to put your phone into fastboot mode.
9. Connect your phone to your PC via a USB cable.
10. Download the miflash ZIP file.
11. Extract the miflash unlock tool ZIP file. You will find the Mi USB Driver.exe file and the miflashunlock.exe file after extracting it.
12. Install the Mi USB driver on your PC.
13. Run the miflashunlock.exe file on your PC.
14. Tap the Agree button and then Sign in with your Mi Account after running the miflash_unlock.exe.
15. Click the “Unlock” button, then click the “Unlock anyway” button within the miflash tool to start the process.
16. Click the “Reboot phone” button after you see the “Unlocked successfully” message.
Downloads:
Unlock tool: https://en.miui.com/unlock/download_en.html
Additionally, we will need to have TWRP flashed to the recovery of the phone.
1. We will need to have ADB installed on the computer so download the 15 Second ADB Installer.
2. Run the ADB-Setup.exe.
3. Open a CMD terminal as an Administrator.
4. Type in the command: CD C:/ADB.
5. Type in the command: ADB Devices, make sure that there is a device showing up.
6. Download the TWRP.img to the ADB folder located on C:/ADB.
7. Make sure that you do not have a password or code lock on the device. There can not be any lock on the lock screen.
8. Type the command ADB Reboot Bootloader.
9. Type the command Fastboot Boot TWRP.img.
10. Navigate to the Advanced menu of TWRP and tap on “Install Recovery Ramdisk”.
11. Navigate back to the main menu then tap on Reboot and tap on Recovery.
Downloads:
15 Second ADB Installer: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
TWRP image: https://drive.google.com/drive/folders/1ztP266XjxteVk8pxcD7-sD-IxihmODPV?usp=sharing
Now we will copy the three boot files on the phone and make backups.
1. Navigate to Mount on the root menu or TWRP.
2. Select the System Partition and Data partition then go back to the menu.
3. Navigate to Advanced then Terminal.
4. Type the command dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img.
5. Type the command dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img.
6. Type the command dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/boot_b.img.
7. After all the commands have been entered you can now exit back to the system by rebooting to the system in the Reboot menu.
8. Next, we will install Magisk on the phone to modify the boot files, download the Magisk.apk file on your phone.
9. Open the apk and install the Magisk.apk on the device. You will have to enable Unknown Sources if you have not already.
10. Open Magisk and select install on the Magisk tab.
11. Under Method tap the Select and Patch a File and select the boot.img file.
12. Press the LET'S GO button after you have selected the file. (Make sure to note down the name of the Output file for each file).
13. Repeat steps 11 and 12 for boot file boot_a.img and boot file boot_b.img.
Downloads:
Magisk: https://github.com/topjohnwu/Magisk/releases
Now we will flash the boot files to the phone and we will be rooted!
1. Copy the files you just made from the storage of the phone under /Internal shared storage/Download/(Filenames) to the ADB folder located on C:/ADB
2. Restart the phone and once the phone screen turns off hold the Volume Down button to boot into fastboot.
3. Now this is where it is very crucial to ensure you know what each file corresponds to for the boot files. Type in the command Fastboot flash boot (Modified file name for boot.img).
4. Type in the command Fastboot Flash Boot_a (Modified file name for boot_a.img).
5. Type in the command Fastboot Flash Boot_b (Modified file name for boot_b.img).
6. Then type the command Fastboot reboot
7. Load Magisk and verify that it is indeed installed.
8. Boom rooted!
I don't get this I rooted much easier by simply flashing magisk.
I downloaded magisk zip
I then booted into fastboot connecting my ohone to the pc
I booted into twrp from fastboot with the command "fastboot boot twrp.img"
From twrp I simply flashed magisk.zip wiped dalvik and ART cache and rebooted the phone
Root done!
My question is now how can I update without loosing data.
I was thinking of installing the new rom via miflashtool without wiping data and then reflash magisk. It should work right?
xNAPx said:
I don't get this I rooted much easier by simply flashing magisk.
I downloaded magisk zip
I then booted into fastboot connecting my ohone to the pc
I booted into twrp from fastboot with the command "fastboot boot twrp.img"
From twrp I simply flashed magisk.zip wiped dalvik and ART cache and rebooted the phone
Root done!
My question is now how can I update without loosing data.
I was thinking of installing the new rom via miflashtool without wiping data and then reflash magisk. It should work right?
Click to expand...
Click to collapse
In my testing I couldn't get my phone to root with Magisk. I haven't tested that but it sounds like it should work.
Look it is super simple, it can be done on every rom with an unlocked bootloader (this must be obvious)
Download the latest magisk.zip file on your phone
Download the compatible TWRP for your device on your computer and put it into your ADB and fastboot folder and rename it "twrp.img" (make sure you replace the file extension with the ".img")
Reboot your phone into fastboot
Connect the phone to the PC
Run the check command "fastboot devices" to check if your device is listed
Then run the command "fastboot boot twrp.img"
Your phone will now boot into twrp recovery and there is no need to flash it and overwrite the original recovery
Now give twrp the permissions to look into your folder by unlocking it at boot (password of pattern depends on what you use normally for your phone)
Now since the twrp is chinese you must change your language into english (3rd button on the right then click on the globe on the up right and select the language you want)
Now go into wipe and wipe manually cache and dalvik
Now go into your system and search for magisk.zip, flash it and wipe again dalvik and cache.
Reboot your phone
Now when you boot you must have magisk through your apps, boot magisk and complete the installation process.
Reboot again and enjoy!
xNAPx said:
Look it is super simple, it can be done on every rom with an unlocked bootloader (this must be obvious)
Download the latest magisk.zip file on your phone
Download the compatible TWRP for your device on your computer and put it into your ADB and fastboot folder and rename it "twrp.img" (make sure you replace the file extension with the ".img")
Reboot your phone into fastboot
Connect the phone to the PC
Run the check command "fastboot devices" to check if your device is listed
Then run the command "fastboot boot twrp.img"
Your phone will now boot into twrp recovery and there is no need to flash it and overwrite the original recovery
Now give twrp the permissions to look into your folder by unlocking it at boot (password of pattern depends on what you use normally for your phone)
Now since the twrp is chinese you must change your language into english (3rd button on the right then click on the globe on the up right and select the language you want)
Now go into wipe and wipe manually cache and dalvik
Now go into your system and search for magisk.zip, flash it and wipe again dalvik and cache.
Reboot your phone
Now when you boot you must have magisk through your apps, boot magisk and complete the installation process.
Reboot again and enjoy!
Click to expand...
Click to collapse
is this working with EU ROM?
penyapu79 said:
is this working with EU ROM?
Click to expand...
Click to collapse
On Xiaomi EU is simpler because it inject twrp itself so you don't need to push start via adb
xNAPx said:
On Xiaomi EU is simpler because it inject twrp itself so you don't need to push start via adb
Click to expand...
Click to collapse
Ok thanks. I will try it later
On Xiaomi EU you can straight flash the update, wipe dalvik and cache and flash straight away magisk zip on top, rewipe dalvik and cache and reboot to system
xNAPx said:
On Xiaomi EU you can straight flash the update, wipe dalvik and cache and flash straight away magisk zip on top, rewipe dalvik and cache and reboot to system
Click to expand...
Click to collapse
any problem with bank apps after root?
I'm on official global ROM and I am using revolut with no issues
xNAPx said:
I'm on official global ROM and I am using revolut with no issues
Click to expand...
Click to collapse
I have the Chinese ultra with global rom but if I decide to sale how do I factory reset to do so? thanks ahead and wasn't sure where to post this.
If you want to sell it you must reinstall the original Chinese ROM and relock the bootloader
xNAPx said:
Now give twrp the permissions to look into your folder by unlocking it at boot (password of pattern depends on what you use normally for your phone)
Click to expand...
Click to collapse
Hi, xNAPx !
Thank you for this tuto, but i have a problem :/
At this step, twrp is booting straight on the menu, no password asked, and so, no access to data :/
Do you have an idea please ?
(i'm using xiaomi.eu_multi_MI11Pro_MI11Ultra_21.12.8_v12-12-fastboot)
I believe this is a known issue, there is a problem on some versions of twrp with encryption, to me never happened. What kind of screen security do you have on your phone?
xNAPx said:
I believe this is a known issue, there is a problem on some versions of twrp with encryption, to me never happened. What kind of screen security do you have on your phone?
Click to expand...
Click to collapse
A password
You can try 2 things, remove the screen lock protection or inject a different version of twrp, I never had this problem as I boot twrp via adb
xNAPx said:
You can try 2 things, remove the screen lock protection or inject a different version of twrp, I never had this problem as I boot twrp via adb
Click to expand...
Click to collapse
Thank you
Removal of the screen lock resulted as a failure too (same problem than with the screen lock)
I don't know and can't seem to find another twrp for the mi11 Ultra than this one :
Mi11Ultra(Pro)-twrp3.5.1-recovery-21.5.9-decrypted.img | by Orjon for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Sorry :/
Push it via adb then, in the shell type:
Fastboot boot twrp.img
xNAPx said:
Push it via adb then, in the shell type:
Fastboot boot twrp.img
Click to expand...
Click to collapse
That's what i'm doing from the beginning, but it doesn't work
What does not work in specific? It's a bit too generic