ZTE Blade A7 - Telstra Evoke Plus Bootloader Unlock - Blade General

Hey XDA, i recently purchased a Telstra Evoke Plus - my ISP's rebranded version of the ZTE Blade A7 2019-T.
Here's the bootloader unlock instructions i have created a few nights ago.
WARNING,
ALL BOOTLOADER UNLOCKING will erase you DATA partition and therefore remove your user data.
Please backup your device data if you don't want this to happen.
Open Settings Application
Tap System
Tap Advanced
Tap About Phone
Tap Build-Number 7 Times
Go Back Once
Open Developer Options
Tap Enable USB Debugging
Toggle OEM Unlocking to Allow
Install Device Driver on Your PC
Start a Terminal Window on your PC with ADB
Plug-in the ZTE Blade A7 Now
Run Commands
Code:
adb reboot bootloader
fastboot flashing unlock_critical
Accept the Dialogue on your ZTE Blade A7 by pressing Volume UP key
Now do a Full Unlock with,
Code:
fastboot flashing unlock
Accept the Dialogue Again.
You will now have unlocked both Critical Flash Partitions and Other Partitions.

Related

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

[GUIDE] OnePlus X: How to Unlock Bootloader and Backup EFS

Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU/Motherboard by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Click to expand...
Click to collapse
Code:
Index
1. Set Up Fastboot & ADB
2. Unlock OPX Bootloader
3. Enable USB Debugging & Activate OEM Unlock
4. How to backup EFS & Other Partitions
Lets get started
1. Set Up Fastboot & ADB Drivers:
What’s ADB?
ADB stands for Android Debug Bridge. It works when the device is powered on and booted into OS or Recovery. The tool helps in sending basic linux commands, and a variety Android specific commands from PC to connected Android devices.
What’s Fastboot?
Fastboot works only in bootloader/fastboot mode. It allows you to re-flash system partitions on your Android device and requires a device with an unlocked bootloader. It’s particularly useful when you want to update your device manually or in a rare situation when you accidentally soft-brick your device and need to install a clean stock system image.
Download and run adb-setup-1.3.exe
2. Unlock OPX Bootloader:
Backup important files stored on your OnePlus X before proceeding with the steps below, as unlocking the OnePlus X Bootloader will completely wipe/delete all files on the device.
After the installation of drivers (OnePlus X, Fastboot & ADB drivers) follow the below to proceed with Unlocking the Bootloader of your Oneplus X
3. Enable USB Debugging & Activate OEM Unlock:
* Go to Settings > About phone, and then tap ‘Build number’ 7 times or until you get the message ‘You’re now a developer!’.
* Go back to Settings, choose ‘Developer options’. Find the ‘USB debugging’ option and use this toggle button to enable it. Accept warning by tapping on OK button.
Also in the ‘Developer options’. Find the ‘OEM Unlocking’ option and use its toggle button to enable it. It asks for your PIN/Screen unlock code, type it. Then accept the warning by tapping on OK button.
Connect your OnePlus X to windows now. You will get a pop-up on your phone when you connect for the first time after enabling USB debugging. Select ‘Always allow from this computer’ checkbox and then tap on OK button. (You may or may not get this prompt so don’t bother if you dont)
Boot your OnePlus X into Bootloader/Fastboot mode. (Make sure you have backed up all important data as you’ll lose everything on phone in the steps below.)
Connect your OnePlus X — in Bootloader mode — to PC. Let the driver install.
Open a command window on your PC.
For this:
>>Open the adb folder on your PC.
>>Hold shift key, right click on empty white space.
>>Choose Open command window here option from that.
Power off your phone then boot into fastboot mode (power + volume up).
Connect your phone to your windows via usb cable.
Confirm whether fastboot is working. With OnePlus X connected to PC, run the following command in command window.
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection to unlock the bootloader use
Code:
fastboot oem unlock
The device will now go through the automated unlocking process, just let it do its thing and it'll boot up into Android.
You’ll see a new screen on your device. Choose Yes and confirm it.
That’s it. The device will reboot automatically.
To confirm unlock status, reboot into bootloader and type the following command:
Code:
fastboot oem device-info
Code:
Device unlocked: true
Other lines are not that important
4. How to Backup EFS & Other Partitions (Root Needed)
* Download Partitions Backup And Restore App from Here
* Open the app and grant it root access.
* Click on the Settings icon above and select preference to .img
* Select the partitions marked in yellow and backup them by clicking on the download like button at the bottom right.
* Go to the storage and search for the Partitions Backup folder there you will three .img files (modem,modemst1,modemst2) . Save them to your cloud and as many places as you want as they are very important files.
This way you can back up all other partitions too. (I would recommend backing up all those that are not found in a factory image.)
Is it different from TWRP somehow?
Caraparbor said:
Is it different from TWRP somehow?
Click to expand...
Click to collapse
It is quite different from TWRP, though it is not mandatory to perform a EFS backup.
Hi folks, i unlocked the boot loader (see attached file) but i can't start TWRP or Partitions Backup and Restore, any ideas?

[Guide] how to root and install TWRP on redmi note 6 pro

First of all at the time there is no official way to root redmi note 6 pro
This guide is suitable for the global version and mybe Indian version need to check because in India redmi note 6 pro not available
I'm not responsible if anything happens to your device. If you execute this procedure properly then you shouldn't face any problems. I tried this procedure on Redmi Note 6 pro and it worked flawlessly. I used a computer with Windows 10 insider .
Before you proceed please back up all your important data and make sure that your phone battery is charged >60%
A .Prerequisites
1. Disable driver signature enforcement in Windows
How to do this pls read here: http://en.miui.com/thread-237673-1-1.html
2. Install ADB and Fastboot tools with drivers on Windows
How to do this pls read here: https://forum.xda-developers.com/sho....php?t=2588979
3. Enable "OEM unlocking" and "USB debugging" in your device
a. Enable Developer Options in: Settings/About Phone/MIUI version. Click on MIUI version seven times
b. Now go to: Settings/Additional Settings/Developer Options and check "OEM unlocking" and "USB debugging"
4. Check if your bootloader is locked
a. After successful installation of "ADB and Fastboot" enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable).
b. Go to the folder where you have put the "ADB and Fastboot" and open a command window inside that folder. To do that hold together "Shift + Right Click" on any empty white space inside the folder and then select "Open PowerShell Window Here" or "Open Command Window Here"
c. Enter the terminal command in command line: >>fastboot devices<<
If you don't see your device it means that the drivers weren't installed properly or the device wasn't connected properly. If this happens please reinstall your drivers from Point A. 2. or try these drivers here:
http://xiaomiadvices.com/download-xiaomi-usb-drivers/
d. If you see your device then enter the terminal command in command line: >>fastboot oem device-info<<
If your bootloader is locked, you'll get the following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
finished. total time: 0.063s
………………………………………………………………………
If your bootloader is unlocked, you'll get following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.053s]
finished. total time: 0.055s
………………………………………………………………………
5. Request Permission from Xiaomi to Unlock the Bootloader
a. Create a Mi Account: https://global.account.xiaomi.com/pass/register
b. Sign to Xiaomi and apply for unlocking http://en.miui.com/unlock
You have to give a reason for requesting to unlock the bootloader.
c. Wait for permission. however very few users are reporting a waiting time of up to 7 days . If your request is approved then you should receive a message with following content:
"You've been granted the permission to unlock your device (Mi Account xxxx). Donload Mi Unlock Tool At http://en.miui.com/unlock"
6. Connect your Mi Account to your Device
Go to: Settings/Additional Settings/Developer Options/Mi Unlock status and check "Add account and device"
B . UNLOCKING BOOTLOADER
Attention: Unlocking the bootloader will erase all your data! So please back up your data before you unlock the bootloader
1. You must enable "OEM unlocking" and "USB debugging" as per point A. 3.
2. You must connect your Mi Account with your device as per point A. 6.
3. Download Mi Unlock Tool here: http://en.miui.com/unlock
4. Enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable)
5. Start the Mi Unlock Tool
6. Enter your eMail and your password of your Mi Account
7. Connect you device to your computer and start the unlock procedure
8. Follow the unlock tool instructions until the unlock procedure is finished
9. Reboot your device
In case you get the message, that the unlocking can be done after 360h or 720h then you have to wait for that time to pass
C . INSTALL THE TWRP RECOVERY
your boot loader must be unlocked
1. Download the file https://drive.google.com/file/d/1pgcTalz8rAFWYwP8xYNmNB8uTk-OlAn4/view?usp=drivesdk
2. Extract to your computer desktop or adb folder
View attachment 4651279
3. Reboot your phone to fastboot
4. Go to your computer and connect the phone with computer
5. Open a command prompt and type
6. Fastboot devices if you phone detected in command prompt window it will show numbers of device like in picture
View attachment 4651278
7. now type [ fastboot flash recovery recovery.img] or you can do like this ( fastboot flash recovery and drag recovery file to command prompt) and hit enter
View attachment 4651277
8. now press volume+ and power at the same time until your device boot to TWRP
9. After successfully booted TWRP now flash View attachment 4651280 and wipe data
10. Enjoy your flashing
D . ROOT YOUR PHONE
1 .Donwload latest Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Put Magisk into external sd card because decryption is not for now
2 .Flash Magisk
3 .Restart your smartpphone
4 .Now set up you phone
5 .Done enjoy
telegram :- https://t.me/tulipofficial
I have read about some problems with ported (from whyred ?) twrp and MIUI 10 on RN6 pro,
but I could not remember where
so there are no problems ??
Perfect
perfect with MIUI 10 ?
phonepete said:
perfect with MIUI 10 ?
Click to expand...
Click to collapse
Yes
...
Great wanna try it..?
twrp is ok now
are there any possibility to re-lock?
hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks
I have problems with this twrp.
When i enter in recovery it ask for a password to decrypt the data storage. I tried everything but i don't know how to decrypt, So i can't mount Internal and SD Partition and neither root my phone
I tried to wipe data, but even in this case i can't navigate into internal storage.
Should i wait for an official TWRP?
raexan said:
hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks
Click to expand...
Click to collapse
You have to apply for unlock and then wait for 14 days.
Has anyone successfully unlock other LTE bands after root? I have the global version but it does not have LTE band 12 & 17 which are critical for AT&T
Can you please tell me if this TWRP edition can see the SD card ?
Thanks
Password required in mount operation
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks
toni.pace said:
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks
Click to expand...
Click to collapse
in that menu I think that you can press cancel and enter in the menu of recovery
Enviado desde mi Redmi Note 6 Pro mediante Tapatalk
same thing happened to me .. as I enter to the TWRP, I have being asked for the pin unlock password, which is not the one I have previously set on the miui. I rebooted to system, removed the pin protection and yet again it didn't helped with the TWRP asking the pass .. if I hit the cancel, I enter to the TWRP yet no any storage is mounted and can't do nothing further. So for a lot of us this guide is not 100% good.
clemenza011 said:
same thing happened to me .. …..
Click to expand...
Click to collapse
I was finally able to root the phone, but i don't know exacly how.
BTW
My TWRP is V.3.2.3 v3 Special Edition mod by Mr-r00t
In TWRP just click "Cancel" to password request, then you should be able to see the content of the Sdcard.
From there i flashed "Disable_Dm-Verity_ForceEncrypt_09.02.2018.zip" and "Magisk-v18.0(18000).zip"
Rebooted in system and did some setup in Magisk app
I did install also "Root checker basic"," Root Browser" , "Titanium Backup" from PlayStore.
In "Root checker basic" installed BusyBox too.
Finally root is working, and i was able to copy a new "Hosts" file in \system\etc, just to get rid of annoying ads .
Good luck
Right, I managed the same last eve *with the other recovery to be honest) .. root after magisk works, and tapatalk is clean after adaway was installed .. yet my data is encrypted and I cannot for instance do the full backup from the twrp. I am concerning format data, as I understood that it should remove the encryption, yet I am not sure would I have to flash something (ROM?) after I format the data, or I could just reboot to the system, as is?
magisk manager shows ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', I suppose that such situation corresponds to the fact that I am encrypted, and I have flashed disable_dm_verity, just like being said.
also, our (RN6PRO) devices have activated anti-roll-back (mine arb index is 4) so there should be no much space for mistakes.
clemenza011 said:
Right, I managed the same last eve *with the other recovery to be honest) .. .
Click to expand...
Click to collapse
Sorry i cannot help with that question about format DATA , my skills are limited.
My Magix manager shows the same " ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', "
I am ok with my phone now, and don't want the risk to loose everything or to be forced reinstall all.
I hope someone else could answer this question.
Have a nice day.

Unicorn Unlocker & TWRP for Telstra Evoke Plus - A.K.A ZTE Blade A7 2019-T

ZTE Blade A7 2019-T Bootloader Unlock and TWRP Install Guide
I have recently ported a similar MT6761 devices TWRP 3 to suit our needs on the ZTE Blade A7 2019-T.
It has take a few solid days messing around, but here's everything I've got on the Telstra Evoke Plus Variation.
You MUST UPDATE to M01 Version First !!! Important !!!
- WokeWorld
Click to expand...
Click to collapse
Specifications,
Android 9.0
Firmware Update M01
CPU MT6761
RAM 2GB
KERNEL 4.9.117+
I was going to make a complete BATCH Script for Windows PC's however I gave up after a while.
Everything is compiled into a ZIP folder called Unicorn
First, Extract the Unicorn ZIP.
If you want to do everything manually, then open Assets Folder and copy out the Files needed.
recovery.img
vbmeta.img
twrp.img
Once you've got your files, Skip past the Automatic Instructions if you're planning to go manually.
Auto Instructions
Open Auto Install TWRP.bat
Follow on-screen instructions
Manual Instructions
Enable USB Debugging and OEM Unlocking;
Open Settings
Open System
Open Advanced
Tap Build-Number 7 Times to Unlock Dev Options
Go Back Once
Open Development Options
Find USB Debugging and Enable it
Find OEM Unlocking and Enable It
Plug Device Into Computer
Start the Unlocking and Installation,
Enter following commands
Code:
adb reboot bootloader
Code:
fastboot flashing unlock_critical
Press Volume UP to Accept on Device
Code:
fastboot flashing unlock
Press Volume Up to Accept on Device
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Code:
fastboot flash recovery twrp.img
Now the Tricky Part is Rebooting without Automatically Replacing the Recovery with Stock.
Hold Power until Screen Turns OFF
Immediately Release Power and Press Volume UP + Power Again for 5 seconds
Release after 5 seconds and wait until TWRP boots Up for First Time.
STOPPING THE STOCK RECOVERY REPLACEMENT,
Open TWRP
Open MOUNT
Mount the System
Go back to File Manager
Open System > System >
Delete `recovery-from-boot.p` or Rename It
FILES
all files are packed in the zip "Unicorn.zip" on my Google Drive - Sorry can't post links yet, you have to copy paste it
Google Drive Folder
https://drive.google.com/folderview?id=11XmE_hg6sC6JLAL6qK6E9PJ9kwbUo49j
• A newer Port of TWRP is available in the folder until I can upload here, hopefully soon.
WHAT'S NEW ?
• Fixed Prop.default with correct Device information from TECNO KB8 to Blade A7
• Added NV RAM & NV DATA to Backup Section, not Sure about Restore Section yet.
TWRP REQUIRES YOU ERASE YOUR DATA PARTITION INSIDE TWRP TO FIX ENCRYPTION PASSWORD.
Please do a backup of your data first, Unlocking the bootloader will Erase the DATA Partition with all your precious files on it.
So .. where's the file
so this would work for the a7 prime?
Hey buddy
Do u have stock rom for this to flash via Sp FlashTool? I get mine A7 zte on bootloop

Possible to get on Stock OOS11 with Root?

I just bought a carrier unlocked T-Mobile 7t pro McLaren 5g on ebay and I've spent several hours reading up on the unlocking and rooting processes for this phone.
I can't seem to figure out if it's possible to get it up and running on the stock OOS11 rom with root (and hopefully TWRP), and if so, what the entire process will be.
I've had my OnePlus 6 for several years now and have had it unlocked/rooted since I got it, so I'm fairly familiar with these sorts of things, just not on this phone specifically. Thanks
This is exactly what happened to me. I just bought unlocked T-Mobile 7t pro McLaren 5g. Coming from 6T McLaren (had 1,2,3,5 and as mentioned 6T McL). I had them all rooted and all other phones that I used before these. But reading around here I feel like I never rooted phone in my life. So much confusing information and also outdated. Not one proper post step by step how to do it. Unlocking tokens? OTA not working etc. Honestly I don't know where to start. lol
Yes, what do you need help with?
Just finished unlocking Bootloader and made steps.
Going to do root and twrp. But first I want to extract my current boot image, as I am at latest update 11.0.1.6.HD61CB
XxBigBuckxX said:
Yes, what do you need help with?
Click to expand...
Click to collapse
One thing I am wondering if is it possible to change T mobile logo animation to McLaren Edition Boot Animation
astracd said:
One thing I am wondering if is it possible to change T mobile logo animation to McLaren Edition Boot Animation
Click to expand...
Click to collapse
McLaren-BootAnimations-OP7T_Pro_5G-A11.zip
drive.google.com
Magisk Flash
Thank you!
Enable USB Debugging and OEM Unlocking
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > System > Developer options > Enable USB debugging and OEM Unlocking. I also enable Advanced reboot.
Fastboot mode and Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + and down - and power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
type:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS (It will take some time to get boot – just leave it to do its thing).
Congratulations you've now successfully unlocked bootloader!
Flashing TWRP Recovery and Magisk root
https://twrp.me/oneplus/oneplus7tpro.html
fastboot flash recovery twrp-3.6.0_11-0-hotdog.img
Do not reboot to OS
Boot into TWRP Recovery
Now in TWRP, tap on Install and browse to the TWRP.zip and install it. TWRP will now be installed to both slots. TWRP is now installed. Reboot into TWRP Recovery.
Now in TWRP, tap on Install and browse to the Magisk-23.0(23000).apk and install it. Reboot to system.
Congratulations you've now successfully rooted your phone!
XxBigBuckxX said:
Yes, what do you need help with?
Click to expand...
Click to collapse
I am trying to find if anyone managed to convert McLaren 5G from T-mobile to International version?
Cannot make VoLTE and Wifi Calling work. It seems it doesn't work on T-mobile version with some of other carriers.

Categories

Resources