Database Info

[GUIDE] Unlock/Root/Flash for Moto X Style/Pure

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
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 issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.

Nextbook Ares 8A with Android 6.0.1 root solutions

UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks

@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks

Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks

Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.

How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.

adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"

Would love to see some break throughs with this device aswell. Cheers to any one working in it.

Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en

Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.

martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:

This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk

vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???

cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk

vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?

cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk

Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it

OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!

OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available
Thank You all for your support :highfive:
Never Settle :fingers-crossed:​

Introduction​​
Rooting OnePlus 6 would give you additional benefits like you can install special apps, Flash Custom ROMs & Custom Mods, you can streamline your phone performance and many extra features. The real performance of an Android smartphone can only be unlocked once it is rooted.
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: ​
1. Unlocking the Bootloader
2. Installing a Custom Recovery
3. Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking Bootloader​​Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.​
Installing a Custom Recovery​​A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root Access​​You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.​

Setup, Preparation & Prerequisites​​
Basic tasks that may be referred to throughout this guide:​​Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Drivers Installation​1. Download & Update OnePlus 6 Drivers From Here
2. Download & Update Fastboot and ADB Binaries/Drivers from Here
3. Run the .exe file downloaded from above as Administrator.
4. Press 'Y' every time the installer asks for.
5. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To Remember​Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional)
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Unlocking Bootloader​
Turn the phone off. Then boot it into fastboot mode by holding volume up + 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:
Code:
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
Code:
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.
Please continue and follow the next post to install Custom Recovery

Flashing TWRP Recovery​
Downloads:
Official TWRP Image & Installer Zip
Blu_Spark TWRP
Root
Magisk​
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation.
Download all the files, place Magisk & TWRP installer zip on Device Internal Memory and TWRP img on your PC
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
You will temporarily boot into TWRP
Now in TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed.
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST

Gaining Root Access​
This is a continued post from the above post...
1. Boot into TWRP Recovery
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk to root.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and might reboot a few times.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted !!
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:

Making a Nandroid Backup​
Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back.
You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 5 to 7 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS

Restoring a Nandroid Backup​
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 5 to 7 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.

Making an EFS Backup​All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...

Restoring an EFS Backup​If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:

Full Stock Rom:
OOS 5.1.3:
AFH
Changelog:
* Updated Android Security Patch To May
* Preloaded OnePlus Switch Application
* Added Configuration for Notch Show/Hide
* Camera - Support Super Slow Motion (720p at 480fps and 1080p at 240fps)
* Camera - Support Quick Capture in Portrait Mode
* Gallery - Support more actions for recently deleted files

Thread Opened for Users to Unlock the device for now, TWRP will be updated as soon as its available.
Thank you for your consideration.

Funk Wizard said:
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
Click to expand...
Click to collapse
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?

KnifeFed said:
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?
Click to expand...
Click to collapse
Yes you are right, you can still flash Magisk and get root access if you don't allow modifications. Also there should be no difference between the TWRP EFS backup or the Terminal Emulator EFS backup.
I would still recommend both as backup if you mess up TWRP/OS due to encryption issues, besides that the official twrp for the 6 would still take time so for just wanted to keep both options at your disposal :good:

Funk Wizard said:
Flashing TWRP Recovery​
Click to expand...
Click to collapse
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?

Titokhan said:
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?
Click to expand...
Click to collapse
The initial build was 5.1.0 which was a test build

Funk Wizard said:
The initial build was 5.1.0 which was a test build
Click to expand...
Click to collapse
Thanks for the confirming my initial speculation.
:highfive:

Funk Wizard said:
Gaining Root Access​
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Click to expand...
Click to collapse
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
You can just take the partial OTAs with unlocked bootloader..
But if you install custom recovery ( twrp) ..then you have to flash the full rom zip anytime that you want to upgrade..

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
As and when you get the device follow the below:
1. Boot up the device and check for system updates
2. Update to the latest available 5.1.3 as of today or whatever latest at the time you have the device.
3. Unlock the bootloader
4. Continue with TWRP flash & Root (Magisk) as by next week TWRP will be available
4. Set up the device the way you want now like installing you preferred apps and setup your device.
5. There on whenever an update comes download the full zip and flash it via twrp instead of partial OTA's
I will make a separate thread for instruction on how to update just like my threads on 5T & 5, links on my signature.
Those will be self explanatory and tested instructions as I happen to have the device with me.
For anything else you are free to discuss here, I may not be available all the time due to work schedule however I will answer all your concerns once I have access to xda.
Thank you for your patience :highfive:

[GUIDE] Xiaomi Qin F21 Pro Custom Firmware, Root, Playstore Certified

I bought a cracked version of the 4/64 version of Xiaomi Qin F21 Pro unlocked bootloader, rooted, and with preinstalled fully working Google Playstore and Play services running on the official firmware 2.0.8.
But lately there's a very nice update development from 4PDA website for the device! It took me a while before I made it work and a lot of trial and error.
I will make a full detailed easy to follow step by step tutorials on how to do it with all the links for the files required.
The results will be:
A fully converted v1.1.1 custom firmware without the chinese apps
TWRP Recovery
fully rooted
certified playstore and google services fully working
THE PROCESS COULD ALSO UNBRICKED THE PHONE
Requirements:
PC
UNLOCKED BOOTLOADER Xiaomi Qin F21 Pro (MTK soc) V1.0+ V2.0+ (4/64gb ONLY)
Files (will be provided)
working brain
CREDITS:
4PDA FORUMS device thread
Telegram Group
DEVS for the unlock bootloader tool
DEVS for the Custom Firmware
DEVS for porting TWRP
testers
many more I probably forgot
...........TUTORIALS SOON

TUTORIAL UPDATE!
MY DEVICE IS 4/64 with unlocked bootloader
Unofficial Qin F21 Pro (MTK chipset) firmware, version 1.1.1 multilanguage.
Thanks to @redsat, @gaguga and the whole 4pda community.
Install at your own risk and responsibility.
For testing purposes only, will be updated or changed if necessary.
Use SP flash tool for flashing, bootloader should be unlocked on the phone (via @mlgmxyysd tool or Ubuntu boot image). Having the full own ROM dump is highly recommended in advance.
Changes:
-Removed chinese applications
-Decrypted data partition
-APK installer with no restrictions
-System partitions are writable
TWRP recovery 3.6.0_11-0 is added
(In TWRP the phone memory is accessible via path: /data/media/0)
WARNING: FLASHING THE FIRMWARE WILL WIPE EVERYTHING! I SUGGEST BACKUP IMPORTANT FILES BEFORE DOING THIS. I WILL NOT BE HELD RESPONSIBLE IF YOUR PHONE DONT BOOT, SOFT/HARD BRICKED! THIS TUTORIAL IS TO DO AT YOUR OWN RISK!
ALL FILES REQUIRED FOR WINDOWS https://www.mediafire.com/file/tl8hv77gl0vo6sd/qin_f21_pro_mtk.zip/file
download and extract zip
extract "F21PRO_1.1.1 (2).zip" (the firmware)
extract "SP_Flash_Tool_V5.zip" (flash tool)
install drivers
open "flash_tool.exe"
select scatter file from the firmware folder
click download
turn phone off
hold back button then plug usb cable to pc. It should start flashing
after download complete, unplug then boot to TWRP then reset factory
Congrats! You now have chinese free apps firmware with TWRP Installed
If it wont boot "DEVICE ENCRYPTED", just go to TWRP and FORMAT DATA then reboot (it should boot to system now)
transfer "boot_2.img" phone or transfer it to a USB Flashdrive (more easier to locate) (FOR 3/32 VARIANTS TRY TO USE THIS BOOT IMAGE BOOT.IMG 3/32)
boot to TWRP once again
go to device path /data/media/0 or USB storage path using OTG
FLASH IMAGE "boot_2.img" to boot partition to fix the device twrp path to /sdcard (IMPORTANT! boot is an IMAGE FILE not ZIP FILE. by default, TWRP is set to check for zip file and will n0t se IMAGE FILES in the directories. YOU NEED TO TAP THE INSTAL IMAGE BUTTON so image files will appear)
reboot and proceed to installing ROOT and Google services
HOW TO BOOT TWRP:
* + heart button (upper left) + power on. once douqin logo appears press up button + power on immediately. TWRP first boot is in Russian language. just change it to english change twrp language
HOW TO ROOT + GAPPS with playstore certified + fix keypad annoying issue
transfer all the app APK from the "APK" folder youve download
install everything (QinPad be a more stable keypad input)
open gboard and enabled both gboard and QinPad (this should give you a quick switch of input in the notification bar everytime you will type something)
open MAgisk app and update the apps to 22.1. phone reboots (DO NOT UPDATE TO VERSION 24.3)
Open magisk again then Install Magisk > Select a patch file > choose "boot_2.img" in your directory (path where you transfer it)
transfer "open_gapps-arm64-11.0-pico-20211217.zip" to device
boot to TWRP
FLASH IMAGE "boot_2.img_patch" IN THE BOOT PARTITION. then reboot. should be found in download path in TWRP
go TWRP again and flash "open_gapps-arm64-11.0-pico-20211217.zip"
reboot > SYSTEM
you will see playstore. you will have an annoying message "device isnt playstore certified" just ignore it
open MAGISK app go to settings and enable MAGISK HIDE, search module and install "Busybox for NDK" then reboot
open MAGISK app, search module and install "MagiskHide Props Config" then reboot
open Terminal emulator app
type "su" enter (grant permission)
type "props" enter
type "1" enter
type "F" enter
type "30" enter
type "25" enter
type "2" enter
type "y" enter
type "y" enter (phone reboots)
after reboot wait gapps to update (around 5-10 mins) then sign in to playstore
you've now enter Playstore
go to playstore settings > about > click update playstore
wait for it to update the version and keep checking in playstore settings > about > IF DEVICE IS CERTIFIED
If the updated playstore still said " DEVICE IS NOT CERTIFIED", proceed to manual
install device id apps from playstore and copy your GSF ID
register it manually here > https://www.google.com/android/uncertified/?pli=1
go settings ~ apps and look for playstore and play services and clear data. reboot phone and Playstore should be certified!
Congats! your phone now is rooted with twrp, no more chinese apps, and with fully working google services. I suggest perform a TWRP backup and store it somewhere safe for future use.
HOW TO FIX NO/DELAYED INSTALLED APPS NOTIFICATIONS
Thanks for JawadEly for the info, it works!
1. Install all your apps
2. Install terminal emulator app and system app remover app from playstore (this will give you the apk path you want to systemize)
3. open magisk, search and intall "APP SYSTEMIZER" module then reboot.
4. open terminal emulator app
6. type "su" and grant the permission
7. type "systemize"
8. You need to set Selinux = TRUE by choosing "s"
9. once its set to TRUE, you can now systemize any app provided you know the apk path of the apps installed.
10. enter "3", here is where you put the apk path of the app you want to systemize
11. to get the apk path of installed app open the "system app remover" app you installed.
12. go to user apps and LONG PRESS an app you wish to systemize.
13. copy the apk path then go to terminal emulator and paste it. Type "1" to confirm.
14. Go to settings > apps list > clear storage of that app you transfer as system app
15. done! just repeat the proceedure for each app you wish to fix the notifications.
BEWARE! Be careful using system app remover. Don't uninstall system apps required for the android system. You might end up in a bootloop. This app is also used to remove bloatwares of OEM firmwares.
I made this tutorial as DETAILED and as EASY TO FOLLOW as posible. Credits to 4pda community group and for individuals who contributed that made all this posible. Sorry if my English bad. Not my native language. If you lke the tutorial, you can buy me a beer.
paypal > [email protected]
gcash > 09912293147
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, I have an F21PRO I am looking for a custom firmware, saw your tutorial, but only saw the directory, there is no specific tutorial, so when you update, please notify me. Thank you，I am using a translator to talk to you, please understand

keep us posted, looking forward to this!

really looking forward to this, mostly about having custom recovery for this phone!

Any updates for that? It's been 2 months since this was posted.

sorry just got too busy but here it is now! enjoy

Can I change qinpad language? or duoqin IME language? I want to change Korean, but I can't find the way.

Thanks a bunch bro, Followed all the steps and somehow I managed to get it working. M a d
Cheers!

thank you, will this recognise uk area codes?

please help I can not install qinpad, it says app not installed?

Jbazt_katuforzs said:
UPDATE! MY DEVICE IS 4/64 with unlocked bootloader (must)
Unofficial Qin F21 Pro (MTK chipset) firmware, version 1.1.1 multilanguage.
Thanks to @redsat, @gaguga and the whole 4pda community.
Install at your own risk and responsibility.
For testing purposes only, will be updated or changed if necessary.
Use SP flash tool for flashing, bootloader should be unlocked on the phone (via @mlgmxyysd tool or Ubuntu boot image). Having the full own ROM dump is highly recommended in advance.
Changes:
-Removed chinese applications
-Decrypted data partition
-APK installer with no restrictions
-System partitions are writable
TWRP recovery 3.6.0_11-0 is added
(In TWRP the phone memory is accessible via path: /data/media/0)
Separate TWRP as boot.img attached as well (thanks to 4pda comrade @yurxxl)
Also you can install Magisk and GAPPS as zip packages via TWRP.
WARNING: FLASHING THE FIRMWARE WILL WIPE EVERYTHING! I SUGGEST BACKUP IMPORTANT FILES BEFORE DOING THIS
ALL FILES NEEDED for WINDOWS https://www.mediafire.com/file/tl8hv77gl0vo6sd/qin_f21_pro_mtk.zip/file
download and extract zip
extract "F21PRO_1.1.1 (2).zip" (the firmware)
extract "SP_Flash_Tool_V5.zip" (flash tool)
install drivers
open "flash_tool.exe"
select scatter file from the firmware folder
click download
turn phone off
hold back button then plug usb cable to pc. It should start flashing
after download complete, unplug then boot to TWRP then reset factory
Congrats! You now have chinese free apps firmware with TWRP Installed
If it wont boot "DEVICE ENCRYPTED", just go to TWRP and FORMAT DATA then reboot (it should boot to system now)
transfer "boot_2.img" phone or transfer it to a USB Flashdrive (more easier to locate)
boot to TWRP once again
go to device path /data/media/0 or USB storage path using OTG
FLASH IMAGE "boot_2.img" to boot partition to fix the device twrp path to /sdcard
reboot and proceed to installing ROOT and Google services
HOW TO BOOT TWRP:
* + heart button (upper left) + power on. once douqin logo appears press up button + power on immediately. TWRP first boot is in Russian language. just change it to english change twrp language
HOW TO ROOT + GAPPS with playstore certified + fix keypad annoying issue
transfer all the app APK from the "APK" folder youve download
install everything (QinPad be a more stable keypad input)
open gboard and enabled both gboard and QinPad (this should give you a quick switch of input in the notification bar everytime you will type something)
open MAgisk app and update the apps to 22.1. phone reboots (DO NOT UPDATE TO VERSION 24.3)
Open magisk again then Install Magisk > Select a patch file > choose "boot_2.img" in your directory
transfer "open_gapps-arm64-11.0-pico-20211217.zip" to device
boot to TWRP
FLASH IMAGE "boot_2.img_patch" should be in download path
flash "open_gapps-arm64-11.0-pico-20211217.zip"
reboot THE CURRENT SLOT
you will see playstore. you will have an annoying message "device isnt playstore certified" just ignore it
open MAGISK app go to settings and enable MAGISK HIDE, search module and install "Busybox for NDK" then reboot
open MAGISK app, search module and install "MagiskHide Props Config" then reboot
open Terminal emulator app
type "su" enter (grant permission)
type "props" enter
type "1" enter
type "F" enter
type "30"
type "25"
type "2"
type "y" enter
type "y" enter (phone reboots)
after reboot wait gapps to update (around 5-10 mins) then sign in to playstore
you've now enter Playstore
go to playstore settings > about > click update playstore
wait for it to update the version and keep checking in playstore settings > about > IF DEVICE IS CERTIFIED
If the updated playstore still said " DEVICE IS NOT CERTIFIED", proceed to manual
install device id apps from playstore and copy you GSF ID
manual register it here > https://www.google.com/android/uncertified/?pli=1
go settings ~ apps and look for playstore and play services and clear data. reboot phone and Playstore should be certified!
Congats! your phone now is rooted with twrp, no more chinese apps, and with fully working google services. I suggest perform a TWRP backup and store it somewhere safe for future use.
I made this tutorial as DETAILED and as EASY TO FOLLOW as posible. Credits to 4pda community group and for individuals who contributed to made this posible. Sorry if my English bad. Not my native language. If you lke the tutorial, you can buy me a beer. paypal > [email protected]
Click to expand...
Click to collapse
Thank you for this! I managed to get everything installed and running. Will be testing it out in the meantime! Thanks again bro! No more bloatware!

If you have a 32GB model, when using Flash Tool, uncheck the tickbox saying "userdata" as leaving this on will completely brick your device.

jason24589 said:
If you have a 32GB model, when using Flash Tool, uncheck the tickbox saying "userdata" as leaving this on will completely brick your device.
Click to expand...
Click to collapse
thanks for the heads up. but can you confirm too that it can still be re-flash again by holding back button if it got bricked?

Jbazt_katuforzs said:
thanks for the heads up. but can you confirm too that it can still be re-flash again by holding back button if it got bricked?
Click to expand...
Click to collapse
I'm not sure. I found that warning from a Telegram group 3 days ago as someone already bricked their 32GB model when they flashed it with userdata option left being checked

harahaum1 said:
Can I change qinpad language? or duoqin IME language? I want to change Korean, but I can't find the way.
Click to expand...
Click to collapse
I'd suggest to use Traditional T9 IME app. Not sure if this supports Korean as most of the languages supports English, French, Russian, etc.

jason24589 said:
I'm not sure. I found that warning from a Telegram group 3 days ago as someone already bricked their 32GB model when they flashed it with userdata option left being checked
Click to expand...
Click to collapse
i think its in the buildprop. anyways 3/32gb variants, DONT TRY THIS TO YOUR PHONE. TUTORIAL ONLY FOR 4/64.

Pixel launcher. Nice alternative launcher i confirmed works! Install using magisk
https://forum.xda-developers.com/t/magisk-pixel-launcher-for-android-11.4213619/

hello, I can't extract "F21PRO_1.1.1 (2).zip" (the firmware). the zip is corrupted. can you re-upload the firmware please?
thanx

Chabanda said:
hello, I can't extract "F21PRO_1.1.1 (2).zip" (the firmware). the zip is corrupted. can you re-upload the firmware please?
thanx
Click to expand...
Click to collapse
Try to use 7zip

[GUIDE] Xiaomi Qin F21 Pro mt6761 Global — Rooted with Play store

This is intended to be a guide on how to root and add play store to a Qin F21 PRO with a MTK6761 processor and 4GB/64GB. The phone I bought came with android 11 and firmware version 1.0.3 (I was dumb enough to not buy the cracked version). I will come back to this to improve the guide as I have more time, but wanted to share some broad strokes here as a way to thank all of you for the help I got from this forum, from 4pda and from various devs that did great work with tools and modules I used.
-------------------------
DISCLAIMER: I have no f****** idea of what I'm doing. My experience with Android rooting is only 2 days (REALLY!), so take this into consideration and proceed with caution.
-------------------------
I'm running a MAC (Big Sur 11.6), so I can't say for the validity of these steps on other OS, but Linux should be quite similar, and Windows too given that all tools have versions for them.
-------------------------
REQUIREMENTS
A factory reset Qin f21 pro on firmware 1.0.3 — Can't say that I recommend doing this without wiping it clean, but you could try
Python 3.9+ — I used homebrew to install (Python 3.9.12), but google is your friend here
MTK client — I used this tool to flash magisk patched boot image and to revert my bricked phone
Android Debug Bridge (adb) — I installed android-platform-tools via homebrew, but you probably already have this
Magisk 24.2 — would probably work with 24.3 but again, I DON'T KNOW WHAT I AM DOING
Android Developer options enabled and USB debugging enabled — if this is what stops you, big red flag
A Brain — goes without saying, things will go wrong and you will probably have to be creative
Magisk modules I used
MagiskHide Props Config — used to "pass as" a OnePlus N10 on google's eyes
Magisk Gapps Core — this is what installs google play store and services
Universal SafetyNet Fix (ended up not using because had to disable Zygisk, but it's worth knowing about it)
-------------------------
WHAT YOU WILL PROBABLY GET IF THINGS GO RIGHT
Rooted ROM
Play store
Happiness (this one is tricky though)
-------------------------
1. Install everything you need on you machine
Go to MTK client github page and follow the instructions to install it on your machine, do the same for android debug bridge. Downlaod Magisk apk and the modules from the links above too.
2. Backup your phone
First, we are going to backup the current state of the phone. CD into the MTK client folder and with your phone OFF and disconnected from the USB run this command
Bash:
python3 mtk_gui
This will open a GUI and prompt you to connect your phone. You should hold the OWL and RETURN keys on the keyboard while connecting it to the USB. The app will now detect your phone and do its magic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that your phone is connected you should be able to dump all the partitions you need to recover it if things go wrong. I did it by selecting all partitions except "userdata" and then clicked "Read partitions". It should take a while, and when it's done you should see various .bin files for all partitions saved somewhere in your computer. Make sure you keep them safe. You can also read the readme from MTKClient on other ways to back your phone (specially for what the "Flash tools" tab is supposed to mean, but this is what worked for me).
Tip: Make sure you don't move the usb cable too much, as I noticed this may cause it to disconnect mid-way and you will need to try again.
3. PUSH THE ZIPS TO YOUR PHONE DOWNLOADS FOLDER
With that out of the way, grab all the zips and move them to your phone.
Open your terminal tool on your computer, cd to where you downloaded Magisk.apk and the 3 modules, and push the files to your phone via ADB USB with this command
Bash:
adb push /path/to/magsik.apk /sdcard/Download
Bash:
adb push /path/to/module.zip /sdcard/Download
You should have all files now on your Downloads folder — you can check by using the native files app.
4. PUSH A BOOT.img TO YOUR PHONE DOWNLOADS FOLDER
Make a copy of the boot_a.bin you just dumped, rename it to boot.img, and push it to your Downloads folder (we will use magisk on it to patch and root your device).
Bash:
adb push path/to/boot.img /sdcard/Download
5. INSTALL MAGISK AND PATCH THE BOOT.IMG
Now, on your phone, go to the Downloads folder and install magisk by clicking the apk, go through all the steps to get it running.
Open the magisk app and on the first card click the install button. On the next screen select the method "Select and patch a file". Magisk will ask you to find the boot.img file. Now you just have to wait for it to finish patching the img.
On the log you will see that Magisk has a path to where it saved the patched img. On your computer run
Bash:
adb pull path/to/magisk/patched/boot.img
This will move the patched boot to your computer which will be helpful in the next step.
6. UNLOCK AND ROOT PHONE
Before we do this, we will need to create an empty vbmeta bin file. On a mac you can do this on your terminal by running
Bash:
touch vbmeta.bin
Now, turn off your phone and disconnect from USB, run this command, and then connect the phone to the USB clicking the buttons from step 2 (this is needed everytime you connect to mtk client, so I won't repeat going forward).
Bash:
python3 mtk da seccfg unlock
Then, after you unlock it, reset the phone by running
Bash:
python3 mtk reset
Now run
Bash:
python3 mtk_gui
With the phone connected to the MTK Client GUI, you will go to the "write partitions" tab:
Find boot_a and set it to the patched boot bin file magisk generated
Find vbmeta_a and set it to the empty vbmeta.bin file you create
Click "write partitions" and wait for it to do its thing.
Bash:
python3 mtk reset
You should now be able to disconnect from USB, start your phone and see "orange state" message on top of the duoqin logo on boot.
Note about partitions: I have little understanding of how the partitions structure are supposed to work on android 11 with MTK processor, but that being said, I had to touch these partitions along the way: seccfg, boot_a, vbmeta_a, vbmeta_b, and super (these last 2, because I bricked my phone). Proceed with caution when writing to them, and with even more caution when writing to other partitions.
7. HIDE MAGISK AND DISABLE ZYGISK (BETA)
Open magisk and hide it by going to settings and click "Hide the Magisk app" — I called mine Houdini, but you can call it whatever you want.
Also, make sure you disable Zygisk on the settings (Reboot if needed).
8. Install MagiskHide Props config
Open magisk again, go to the modules tab and click "install from storage". Find the MagiskHide props config .zip file and install it. Reboot the device.
Now, on your computer, and with USB debugging connected, run:
Bash:
adb shell
This will give you access to your phones shell. Make sure you have internet access on your phone, you can then run:
Bash:
props
(su might be needed here, if so, you can allow it via magisk superuser tab)
Follow the steps from the tool to get your phone fingerprint to be OnePlus N10 5G Global BE2026. This means you will need to navigate the tool on menu options 1 and 2 to do this. Menu option 4 is defined as active by default. You will probably have to reboot a few of times along the way. Just follow what the tool says and check its docs if needed.
Docs: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf
Here is what I have:
9. Install Magisk GApps Core and hope for the best
Open magisk again, go to the modules folder and click "install from storage". Find the magisk gapps core.zip module and install it. Reboot. That's it.
Your browser is not able to display this video.
Tip: If play store keeps crashing try clearing its cache and storage by going to settings > apps > play store and clear storage
If it doesn't work, play around a bit, try different settings, maybe install Universal SafetyNet Fix, add google play store and services to Magisk's denylist and enable Zygisk, google stuff, poke around. What I described above is what worked for me.

reserved for updates — probably will never happen

wow thanks worked great.

Thank you so much for your hard work!! This works perfectly, I appreciate it!

I followed your guide through step 6, but now when I try to turn on my phone it says:
"dm-verity corruption
Your device is corrupt.
It can't be trusted and may not work properly
Press power button to continue.
Or, device will power off in 5s"
It powers off after 5 seconds, even when I press the power button.
I tried flashing the original firmware, and I'm still getting the same message.

The solution to "dm-verity corruption" on the F21 Pro is: (after following the tutorial through step 6)
1. boot into fastboot by running "python mtk payload --metamode FASTBOOT"
2. using fastboot, flash vbmeta_a.bin with the --disable-verity flag and the --disable-verification flag:
"fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.bin"
3. wait until it finishes (it should be pretty quick), and then hold down the power button to reboot.
4. the device should now boot without the "dm-verity corruption" message
Sources:
I used part of method 2 from this tutorial: https://www.droidwin.com/disable-dm-verity-without-twrp/
Instructions to get to fastboot are from the README.md from https://github.com/bkerler/mtkclient

Note: In the guide, the link to download Magisk is from magiskmanager.com. This is not the official website of Magisk. The official place to download it is from https://github.com/topjohnwu/Magisk.
Edit: The link in the guide was fixed.
As per https://www.xda-developers.com/psa-magiskmanager-com-not-official-website-magisk/

Information on how to do this stuff is scarce it seems with the exception of you and some Russian website. Hopefully someone can help (I am a complete Android novice) - My device is the 3gb/32gb version and I'm not entirely sure which configuration I purchased. It was from eBay and the description gave no information other than storage and RAM. If it helps, when turned on it had Amazon App Store installed and I have the ability to download apps from browser and install directly on the phone. It shows version 1.1.1. Any chance you could advise if this ticks the boxes as it were so that I'm not walking in to bricking my phone with no knowledge or skill of how to fix it? Appreciate the help
Should also mention - It doesn't seem to have any root apps or anything like that and no google play store/services etc.

thanks for this

Hi! If anyone has the backup with partitions and doesn't mind sharing it, let me know. Thank you!

Hello, there has been an update. Now the company Duoqin itself provides its devices with official Google Play Services. Could someone who has this updated device help us get such an update?

I was also stuck after the 6th step. What solved it for me was using the `vbmeta_a` partition from this post. Thanks to @Jbazt_katuforzs

my phone bricked

I have MagiskHide Props Config, Universal SafetyNet Fix, and Magisk Gapps Core installed, but it's saying "This device isn't Play Protect Certified". Any ideas?