Hi,
Today I tried to flash my recovery using the latest twrp:
twrp-3.2.2-0-zl1.img
I used the fastboot tool following these steps:
https://www.google.com/amp/s/forum....pro3/how-to/leeco-le-pro-3-root-t3476560/amp/
After doing that, my phone seemed bricked, there is no way to enter to the recovery non to the bootloader mode.
Pressing the power bottom for 1 minute, I could boot the system, which the only thing that is working as normally.
All the methods to install a recovery I've seen requerie to switch to the bootloader mode, what can I do to reinstall a twrp recovery?
Thank you.
Dioniso said:
Hi,
Today I tried to flash my recovery using the latest twrp:
twrp-3.2.2-0-zl1.img
I used the fastboot tool following these steps:
https://www.google.com/amp/s/forum....pro3/how-to/leeco-le-pro-3-root-t3476560/amp/
After doing that, my phone seemed bricked, there is no way to enter to the recovery non to the bootloader mode.
Pressing the power bottom for 1 minute, I could boot the system, which the only thing that is working as normally.
All the methods to install a recovery I've seen requerie to switch to the bootloader mode, what can I do to reinstall a twrp recovery?
Thank you.
Click to expand...
Click to collapse
Had the same issue. I just flashed TWRP img through AIO tool
And all works now
Deleted,
I thought you were bricked. Use the AIO tool
Easy Way to do this with one tool
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great,
After you install it, make sure to check for updates.
Get it here: https://forum.xda-developers.com/le...auronofrio-t3580611/post71627491#post71627491
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Install TWRP,
* Fast your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Problem solved, thank you
Related
******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!
I *just bought Mi A1, and I want the Night Light feature. And the blue accents (I love it).
I enabled OEM unlocking, enabled USB debugging. adb recognized my phone, and I rebooted it to bootloader (fastboot).
HOWEVER, fastboot devices brought up no devices - the phone is not being recognized.
I used the AIO tool here, and I'm getting the same results. Interestingly, when I reboot to the bootloader, the phone switches off after 30 seconds or so, and instead starts charging (cuz it's connected to my laptop) but it stays in fastboot if I use Vol - and power button.
I could be missing USB drivers, I supposed. I had installed drivers from the AIO tool, am I missing something?
Help appreciated, thanks!
If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.
_mysiak_ said:
If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.
Click to expand...
Click to collapse
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?
kvn95ss said:
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?
Click to expand...
Click to collapse
For example here and just follow the video guide in the post for both ADB and Fastboot drivers installation.
With your phone in fastboot mode, look in device manager, there is probably a device that does not have drivers. If you have already installed them, you can try having Windows search for them. Then you would validate by doing a fastboot devices command from command prompt.
I have managed to get it working, I've flashed TWRP, however it goes into a bootloop with linux penguin, then a white background with Google colors and an open lock at the bottom, reading "Unlocked".
Strangely, if I flash TWRP with the AIO tool, the phone boots into system rather than loading into TWRP ?
Any reason for the peculiarity!?
Also, I can't reboot the phone.
And for some reason, my phone is encrypted!
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk..
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure
_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
Oohh.. okay. Right now I'm downloading the Dec. update. I'll flash that with MiFlash tool (saving the user data) and then install Magisk with TWRP.
Before that, should I try flashing stock recovery?
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure
Click to expand...
Click to collapse
Well... I thought that the encryption is preventing my phone from booting. Strangely, flashing TWRP 3.2 using the AIO boots my phone to system, so at least I can use my phone.
_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
ALSO, do I have to install magisk on both the slots?
I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.
_mysiak_ said:
I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.
Click to expand...
Click to collapse
So, I flashed the December fastboot ROM, unlocked my bootloader, booted to TWRP and installed Magisk v14 (latest). It installed without issues, but when I try to boot, it goes into a boot loop.
Also, when I boot using TWRP (no modifications) my hotspot doesn't seem to work, I have to restart my phone to fix it.
Well, I guess I'll try it once more...
Damn, it worked! Magisk installed and phone boots well. The phone gives a warning before booting, that it can't be checked for corruption (probably because of the unlocking I guess).
Now, onto installing the Magisk module which gives me to use GCAM (HAL3) and nightlight.
Just a note, Magisk v14 doesn't work well with dual partitions, this might explain strange behavior. Use official Magisk beta v 14.4 or 14.5.
Hi, I'm trying to get TWRP on my J530F (to install LineageOS and Gapps). Adb reboot bootloader results in rebooting Android. I've managed to get into recovery or download mode by holding buttons, but it's useless. Found something with heimdal, but dnf manager refuses to install it to my computer. How can I setup the TWRP? I use Fedora 64b.
Any advice appreciated.
sjiamnocna said:
Hi, I'm trying to get TWRP on my J530F (to install LineageOS and Gapps). Adb reboot bootloader results in rebooting Android. I've managed to get into recovery or download mode by holding buttons, but it's useless. Found something with heimdal, but dnf manager refuses to install it to my computer. How can I setup the TWRP? I use Fedora 64b.
Any advice appreciated.
Click to expand...
Click to collapse
I have tried a similar thing with adb and fastboot using Debian, I was trying to oem unlock.
adb reboot bootloader on my J530G results in rebooting to Download Mode but fastboot never recognizes the device. I don't know if fastboot is compatible with galaxy phones.
scroll-lock said:
I have tried a similar thing with adb and fastboot using Debian, I was trying to oem unlock.
adb reboot bootloader on my J530G results in rebooting to Download Mode but fastboot never recognizes the device. I don't know if fastboot is compatible with galaxy phones.
Click to expand...
Click to collapse
I guess, switching the OEM unlock option in developers section may do the bootloader unlock. Had some luck with adb reboot download, which resulted in rebooting to download mode saying sth like "ODIN mode". I did some research, found more info about ODIN, heimdal etc., but after some time I gave up, cos dnf package manager keep refusing to install Heimdal, saying
Code:
Problem: conflicting requests - nothing provides libusb1.0 >= 1.0.8
(already installed libusb-1, libusb-devel-1)
Anyone have advice? Thanks
Follow the instruction here to install twrp https://forum.xda-developers.com/ga...msung-j5-pro-twrp-3-1-10-v2-0-t3728233/page10
Then from twrp flash magisk from here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
That's how to properly root without bricking your device or losing your imei
Hi i have a ZTE Blade A5 2020 and i want to unlock it's bootloader and install a custom recovery. If i want to boot it to recovery i can do it with the adb command and everything works but it doesn't boot to bootloader and i cant unlock it.
I tried adb reboot bootloader, adb reboot fastboot, adb reboot download and also reboot edl it only boot to system again
I tried using the volume buttons (with and without charger connected to the computer) same thing except the recovery
I tried the recovery option "reboot to bootloader" it boot system
The only thing I can do is to reboot it to recovery or system can someone help me
I have enabled the OEM unlocking in the developer options
Help me
Help
You need a recovery.img with this function, think the russian version has that function, can be flash this with spd research tool. It has to be the research since because allows You to choose what install an what not.
But how i use that tool
makuca said:
You need a recovery.img with this function, think the russian version has that function, can be flash this with spd research tool. It has to be the research since because allows You to choose what install an what not.
Click to expand...
Click to collapse
.