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

Oukitel K6000 Plus Twrp, Root

Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
{
"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"
}
BTW Sorry for my bad English XD

@Cheese-ass
Greetings and welcome to xda. All posts on xda must be in English, I have translated this one for you but please use google translate for all future post's
Regards
Sawdoctor
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted

There is a way to connect a lan usb adapter?

fantastic work like a charm, but used recovery download from the german one and worked rooted oukitel k6000 plus yea

i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???

Worked fine. I had to download files from other websites, but this procedure was good.
After reboot, su was working fine in /system. I wanted to reset the device completely, and typed "fastboot oem unlock"; I thought it would wipe data. Now, phone only boots on TWRP, and it seems like the /data partition is broken. TWRP can mount /system, but not /data. Either the device node is missig, or the partition is not formated properly.
Code:
# cat /etc/fstab
/dev/block/mmcblk0p6 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p8 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p9 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p26 /system ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/external_sd auto rw 0 0
/usbotg auto rw 0 0
Losetup-a gives nothing.
I tried all possible commands (adb reboot to everything), and press volume up or down ... always get back in TWRP. Can not even reach the factory menu (the one where there are tests).
After reformating /data i can reboot to bootloader (fastboot), but still not /system.
Stock ROM was looking fine; I would like to be able to keep it. I would like to avoid flashing to an other ROM.

In short, I have TWRP and flashboot, but /system launches TWRP.
I don't know how to get a working system. SPFlashTool does not seem to work with TWRP installed. TWRP does not like OUKITEL_K6000_Plus_V6.0_20170519.rar. I can't find any ZIP ROM for TWRP. And when I try individual .img files from the RAR, TWRP can install them, but it does notproduce a working phone.
I fear something could be wrong with the partition table, or at least /data. /system contains many files and this looks good.
---------- Post added at 01:30 PM ---------- Previous post was at 12:40 PM ----------
How I fixed it:
fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img (EDIT: this MUST be wrong, should be fastboot flash recovery /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img or fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/boot-verified.img )
then, perform again https://fvknl.pro/k6000-plus-v6-0-upgrade/
and now I have a working phone.

* Can't apply Android updates because of TWRP+SuperSU ?
Now that my phone works, and is rooted (i use the stock ROM version 6), may 19th, the system is telling me there are system updates to do. I have downloaded them (200MB), but after reboot, update fails, for obvious reasons: the update is designed to be installed by the stock recovery firmware; and that partition is overwritten by TWRP.
I was given a tip to work around this (wherer the img file is taken from the .rar archive of the stock ROM):
# fastboot boot /tmp/recovery-verified.img
and it worked: fastboot uploaded the recovery image to the phone, ran it, and that recovery firmware started to apply the update.
Started ... but failed before half of it ... PROBABLY because /system was HEAVILY modified while I asked TWRP to install UPDATE-SuperSU-v2.82-20170528234214.zip (read the installation log of SuperSU ... it alters many things).
How can I apply my android updates without erasing the whole phone each time I want to apply them ?
A: how to get the installation log, to see the failure point, and fix it manually
or
B: install the update manually without running the recovery, but extract the update file, and manually copy the new files at due place, one by one
or
C: how to undo installation of SuperSU, so that /system is in a state where the update can be applied.
I want to do this without erasing /data, or /system. I had this issue on my previous phone; since december 2014 I could not apply any Android update; so my phone is stuck to Android 4 from december 2014. There have been many changes and updates during 2015 and I could not apply them. After installing su, i had been able to perform two Android updates; updates broke after installing Xposed. I do not want my new K6000 to have the same issue; I want to find a way to apply updates. And I would like to keep the stock flavour because there are many features I would like to use (don't want to install misc ROMs).

Xposed for oukitel 6000plus root
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio

no xposed for k6000 plus
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
sorry latest xposed is for sdk 25 and the latest firmware for this device is android 7.0 (Sdk 24)

patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
I have tried many random things; I forgot the details of it. The versions are not a problem; there are links around to download old installers. Even if latest Xposed is for Android 25, archives will let you download v24.
It also depends when you rooted your phone, and which updates you did on your ROM before rooting. Depends if you are using ROM v6, v9, or v18 ...
Also, even if Xposed is installed, it's not working properly; in particular, I wanted Xposed to NotifyClean, and this plugin could not be installed on the Xposed I have (download goes fine, but plugin complains I need reboot to activate it). So, in short, Xposed is useless for me for now. Some other plugins have installed correctly (Taskbar).
The Xposed I have NOW is version 87 by PurifyOS. ATM, Android API 24.
But I said I tried many random things, so, maybe having tried to installed other variations of Xposed by other people was important to have this one installed. I remember that at some point, trying to install this one (purify) failed, and then, worked later ... forgot why.

Error
When you try to upload a TWRP, a message pops up:
"error: cannot load 'recovery-twrp31jemini.img'"
Bootloader should be unlocked. I see a buzz when switching on "yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds"
Phone has a ROM v18
Application procedure on W10.
Does anyone find any solution?

You don't need to burn TWRP in FLASH to be able to use it. You just need to load and run it, this way:
fastboot boot recovery_TWRP-3.1.0.img
This way, if you have backup your whole phone, or downloaded and extracted a ROM, you can boot a stock recovery image:
fastboot boot /tmp/recovery-verified.img
According to your name jemini ... I thjink you have downlaoded the wrong TWRP. Boot and flash may fail if you grabbed a file for an other phone.
This should be ROM independant.
Since I rarely use TWRP, I now keep the stock recovery, and run TWRP from fastboot only when I need it; this way, stock recovery is available for Android updates.
Do you have links to ROM v18, so that I can download and install it directly, instead of having to burn v6, then update to v9 and v18 via update process ? I have issues with updates, and would like to flash directly using v18; but could not find a download link.

I got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) Start unlock flow
OKAY [ 14.791s]
finished. total time: 14.792s
Problem is now:
Orange state
Your device has been unlocked and can't be trust
Your device will boot in 5 seconds.
But it's not booting, just stuck at this screen.
Any help very much appreciated!
EDIT:
I was on V23 ROM which came per OTA.
EDIT-2:
I was able to flash it back to V23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.

rom
"Custom Rom Doogee Shot (FreemeOS) :
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!""""
What do you say that this rom picks up on the oukitel k6000 plus ??

I need someone to help me my k6000 plus did not call any more after this procedure.
when I install the rom stock by flash sp this error appears
https://drive.google.com/file/d/0ByEkRDgYmbWtOXdpbngtcGJxQk0/view?usp=sharing

What do you want to do?
Flash the Stock ROM back with flashtool?
You should switch to "Download Only" and not "Firmware Upgrade".
Also the Download Agent was different when I flashed it, it was DA_PL.bin.

cojo11 said:
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Click to expand...
Click to collapse
SIVAKUMAR: yes my mobile also same problem ...boot loop please help me oukitel k6000 plus MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
sivakumarindia said:
SIVAKUMAR: yes my mobile also same problem ...MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
Click to expand...
Click to collapse
SIVAKUMAR: I THINK THIS ROM DIFFERENT MT6750 AND MT6750T:crying:
---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------
rolex0815 said:
i got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) start unlock flow
okay [ 14.791s]
finished. Total time: 14.792s
problem is now:
orange state
your device has been unlocked and can't be trust
your device will boot in 5 seconds.
but it's not booting, just stuck at this screen.
Any help very much appreciated!
Edit:
I was on v23 rom which came per ota.
Edit-2:
I was able to flash it back to v23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
Click to expand...
Click to collapse
sivakumar: My mobile also same condition boot loop

I got the same and this help me :
For this case, leave SP tool setting as normal. Before connect USB to device:
1. Press and hold vol +
2. Connect USB to device and hold vol + button.
3. Just release the button until you see the download process start working.
with this solution i have Flaht the v6 rom

Boot loop try this Back to STOCK ROM
Cheese-ass said:
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
BTW Sorry for my bad English XD
Click to expand...
Click to collapse
SIVAKUMAR INDIA: BOOT LOOP TRY THIS BACK TO STOCK ROM OUKITEL K6000 PLUS MT6750T
----------------------------ERROR BOOT LOOP -------------------------------------------
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
---------------------------TRY THIS STEPS RECOVERED STOCK ROM--------------------------
step1: Vcom+SPD+and+adb+driver+Installer+Windows+8_10
INSTALL DRIVERS
step2; SP_MDT_v3.1732 (DOWNLOAD )
EXTRACT AND RUN SP-MDT FLASH ,
SCAN ---------CONNECT MOBILE------FLASH SUCCEED----
step3: OUKITEL_K6000_Plus_V23_20170726
THIS LINK AVAILABLE OLD VERSION SP_MDT ONELY SEARCH AND DOWNLOAD NEW VERSION SP_MDT_v3.1732
LINKS: https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html

[Guide] Root Pixel 3 XL Android 10.0 (Q)

[Guide] Root Pixel 3 XL Android 11 (R) Unlock/Lock Bootloader + Install Stock Images/Systemless Root2021
Android Security Bulletin—June 2021
Pixel Update Bulletin—June 2021​
Introduction
This Guide is for Pixel 3 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 3 XL'.
This Guide also works for Pixel 3 owners: If, they download the Pixel 3 files.
New
Android 12 Developer Preview - Beta 2
Factory Images: Downloads for Google Pixel 06/09
OTA Images: Apply a device OTA image 06/09
CalyxOS
GrapheneOS
Update(s)
Factory/OTA Images - 06/07
Magisk Stable - Magisk-23.0 05/12
Magisk Beta - Magisk-23.0 05/12
Magisk Canary - Magisk-23xxx
TWRP - Waiting for Android 11 (Q) TWRP
SafetyNet - SafetyNetFix v1.1.1 01/16
SDK Platform-tools - r31.0.2 April
Custom Kernels
ElementalX (Check his Kernel Manager for latest update.)
Kirisakura v3.0.8_R 06/11
Custom ROMs
[ROM][11][OFFICIAL] lineage-18.1 for Pixel 3/XL (blueline/crosshatch) - Nightly by razorloves
[OFFICIAL][11]ScorpionROM v4.x 05/04
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 3 XL phone with an unlocked bootloader.
The latest Android 11 (R) Factory or OTA Image: "crosshatch" for Pixel 3 XL
Factory Image
11.0.0 (RQ3A.210605.005, Jun 2021)
Which one should I use?
OTA Image
11.0.0 (RQ3A.210605.005, Jun 2021)
Which one should I use?
Computer - With the latest SDK Platform-Tools: r31.0.2 installed.
Important: Update Platform Tools, regularly, for optimal performance.
Other Pixel XL Guides
[Guide] Pixel 4 XL Android 11 (R)
Credits/Thanks/Recognitions
@topjohnwu - Magisk Canary
@sliding_billy - His help editing this thread.
Those I may have, inadvertently, forgotten.
Index
(NOTE: Numbers 1-11 are not steps, they are individual sets of instructions).
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, Add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
After unlocking your bootloader, every time you reboot you'll see a warning: You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Do not lock the bootloader until you have returned the phone to stock. Failure to do so causes bricked phones.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep or wipe data
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file with the -w (Wipe Data).
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3 XL - crosshatch.
If your phone was rooted, and you want to 'Keep Data'. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images prior flashing the Factory image. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
If you get an error:when flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 3 XL - crosshatch to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder with the extracted the Factory Image and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove -wfrom this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
Note: If you do not remove the -w your Internal Storage will be wiped.
Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
At the Command Promp type: flash-all and press enter.
System will reboot when flashing is complete.
Do #7 to root/reroot.
Flash Factory Image Wipe Data
This will wipe your Internal Storage.
Open the folder with the extracted the Factory Image.
Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
Open a Command Prompt on your computer in the Platform-tools folder.
At the Command Prompt type: flash-all and press enter.
System will reboot when flashing is complete.
Do #7 to root/reroot.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery - TWRP
Important notes:
Charge your device.
Enable USB Debugging on your phone.
Install the latest version of SDK Platform-tools on your computer.
Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
Connect your device to your computer using a USB cable.
Boot T.W.R.P.
T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
When T.W.R.P boots tap Advanced ==> ADB Sideload.
✓ the wipe Dalvik cache box
Swipe to start
On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
You will see the progress of the sideloaded file.
When the file finishes sidloading, reboot your device.
Done!
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (crosshatch-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
At the Command Prompt type: fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Important Notes:
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R). I recommend doing a clean install. What is a clean install?
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
If your phone was rooted. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
Download files:
Magisk App - Download to your phone
Magisk Beta/Stable App
Magisk Canary App
Custom Kernels - Download to your phone - install with Kernel Manager
Important: Unless otherwise directed by Kernel Developer, Flash the Kernel after Magisk.
[Kernel][11.06.2021][4.9.272] Kirisakura_R 3.0.8 for Pixel 3/XL aka Bluecross by Freak07
Kernel Manager - Download to your phone
EX Kernel Manager
Patch the boot.img
Do #6 - Extract boot.img
Install Magisk (Beta, Canary or Stable) App
Open Magisk App
Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode (#1)
Connect the phone to the Computer with USB cord.
Open a Command Prompt (#1) in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important:If your phone boot loops try one of the following options.
Flash the stock boot.img to both slots. fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok == > wait for it to boot ==> Reboot.
Pass SafetyNet: MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Download SafetyNetFix from the link above.
Open Magisk Canary App
Tap Modules icon.
Tap Install from storage
navigate to the SafetyNetFix file
Hightlight the file (tap it)
Tap the check mark (✓) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Open Magisk Canary App
Tap the Setup icon.
Scroll down to Magisk - MagiskHide and enable it.
Tap back arrow => tap Superuser icon => tap MagiskHide => Scroll to the bottom of the page => Tap Search icon => Tap Show system apps (Under Filters) => check (✓): Google play services (com.google.android.gms).
Close Magisk Manager.
Open Settings
Tap Apps & notifications
Tap see all 999 apps
Tap the three dot menu
Tap Show system
Scroll down to Google Play Store
Tap it
Tap Storage & cache
Tap Clear cache
Tap Clear storage
Exit settings
reboot
Open Google Play Store app
Tap Menu
Tap Settings
Scroll down to Play protect certification
check for Device certification.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_
Tap, Reboot
Done
Custom ROMs
Need help with a Custom ROM?
Read and follow the Installation Instructions. The installation instructions are in the OP.
If you have a problem Installing the ROM, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
[ROM][OFFICIAL][Android 11]ScorpionROM v4.x[Google Pixel 3/XL][Blueline/Crosshatch] by NepoRood
ROM][11][OFFICIAL] lineage-18.0 for Pixel 3/XL (blueline/crosshatch) by razorloves
Unofficial
None
Mods/Scripts/Themes
Tulsadiver's Mods
Android 10 ADB Installer-Zip Installer, creates magisk module by Tulsadiver
Android 10 Accents Mod by Tulsadiver
Others
[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.3.6 by Didgeridoohan
[Substratum][Magisk]Pixel Launcher Editor for P3XL by eg1122
[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 3 XL Thread
T.W.R.P. Backup/T.W.R.P Update
Waiting for Android 11 (R) T.W.R.P.

Why on earth would anyone go through all these steps AND lock their bootloader when just using flashall.bat with -w intact also wipes your entire phone?!

@Homeboy76 did this work for you? Was getting ready to do a clean install and while researching what the delta of 19 and 20 was, I see talk of sensors not working?

I always appreciate using your guide(s). Thanks a lot!

guide works, thanks for helping me root android 10 on first day of official release

I've Magisk patched the boot.img using the Canary build and flashed.... it's been stuck on the bootscreen for about 20 minutes. Is this normal? How long should I leave it?

Has anyone gotten Adaway working?

Hi,
Great guide, appreciate it.
I'm on Android 9 rooted with magisk. when I try to install Android 10 I get an error below. Latest platform tools, Bonito .20 Any ideas what is wrong? Flashed multiple time through the Pie security updates etc and never had an issue.
_________________________________________________________________________________
F:\platform-tools>flash-all
Sending 'bootloader_a' (8349 KB) OKAY [ 0.298s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) xbl signature verify fail
FAILED (remote: 'Validate packed image fail')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (73196 KB) OKAY [ 1.798s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_a
OKAY [ 0.298s]
Finished. Total time: 2.376s
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 8A5Y0F91G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'crosshatch'.
Update requires 'bonito' or 'sargo'.
fastboot: error: requirements not met!
Press any key to exit...
_________________________________________________________________

Looks like I screwed it up. Now it boots to the spinning G than back to Fastboot - "no valid slot to boot". Now what?
Reflashed Pie, all set -phone boots up. Now to figure out how to get to Android 10.

ginfest said:
Hi,
Great guide, appreciate it.
I'm on Android 9 rooted with magisk. when I try to install Android 10 I get an error below. Latest platform tools, Bonito .20 Any ideas what is wrong? Flashed multiple time through the Pie security updates etc and never had an issue.
........
Device product is 'crosshatch'.
Update requires 'bonito' or 'sargo'.
Click to expand...
Click to collapse
You've downloaded the wrong image. Are you on a 3a XL (Bonito) or regular 3 XL (Crosshatch)??
Download the correct image from here: https://developers.google.com/android/images

krs360 said:
You've downloaded the wrong image. Are you on a 3a XL (Bonito) or regular 3 XL (Crosshatch)??
Download the correct image from here: https://developers.google.com/android/images
Click to expand...
Click to collapse
Oh **** what a dummy I am! I'm on a Pixel 3XL not 3a XL. Sorry, I'll try again
---------- Post added at 08:49 AM ---------- Previous post was at 08:17 AM ----------
Ok, reflashed the correct Crosshatch 0.20, flashed the Magisk patched .img et viola, Android 10 rooted and no loss of data!
Thanks for all the help.

not to be that guy who asks for ETAs but any idea how long TWRP takes for a new version of android to come out? never really been around for a version release like this and just curious. waiting for TWRP to come out before i go through this process.

Homeboy76 said:
OP
Click to expand...
Click to collapse
Great write up! Thank you! I would suggest adding "--slot all" command to the magisk instructions. Root wasn't appearing to be working for me until I added that in.

pr0adam said:
not to be that guy who asks for ETAs but any idea how long TWRP takes for a new version of android to come out? never really been around for a version release like this and just curious. waiting for TWRP to come out before i go through this process.
Click to expand...
Click to collapse
This twrp works
https://forum.xda-developers.com/showpost.php?p=80017781&postcount=1152
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
Has anyone been able to edit build.prop? I have root, but cannot mount the build.prop w/r.

lawtalking said:
This twrp works
https://forum.xda-developers.com/showpost.php?p=80017781&postcount=1152
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
Has anyone been able to edit build.prop? I have root, but cannot mount the build.prop w/r.
Click to expand...
Click to collapse
even though it says its for blueline(pixel 3) and we are on crosshatch(pixel 3xl)?

I'm not able to flash the 10 factory image. I can flash pie just fine, but it always gives an error when trying to push the system image. I can flash Pie just fine. Anyone else have this issue?

jmartin72 said:
I'm not able to flash the 10 factory image. I can flash pie just fine, but it always gives an error when trying to push the system image. I can flash Pie just fine. Anyone else have this issue?
Click to expand...
Click to collapse
Are you getting an error saying that you need to use fastbootd?

airmaxx23 said:
Are you getting an error saying that you need to use fastbootd?
Click to expand...
Click to collapse
No it doesn't say that. I'd have to do it again to get the exact wording, but it makes my phone boot to some screen that says fastboot up at the top

pr0adam said:
even though it says its for blueline(pixel 3) and we are on crosshatch(pixel 3xl)?
Click to expand...
Click to collapse
Yes. The code paths are the same, so it works. Used it myself.

lawtalking said:
Yes. The code paths are the same, so it works. Used it myself.
Click to expand...
Click to collapse
Are you using just the .img each time or flashing an installer after?

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"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"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition