Nextbook Ares 8A with Android 6.0.1 root solutions - Miscellaneous Android Development

Nextbook Ares 8A with Android 6.0.1 root solutions - Miscellaneous Android Development

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

Related

Beginners Guide to root and flashing a custom ROM on the TF700T

Last edit: Jan 2, 2018
The information here can be found in many places on the web and several forums. But when I started flashing custom ROMs about two years ago, I got frustrated many times because I found that information to be scattered, fragmented and in many cases outdated.
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF700 involves three steps:1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recoveryRooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step since any custom ROM you flash will be rooted anyway.
But if you want to root the TF700 on stock firmware there are three ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK).
And then there is Towelroot, a one-click-root exploit. It's an apk, so no PC necessary. Only Towelroot v1 works for the TF700 and it's hard to find. My dog ate the copy I had..
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Download the Asus Unlock Tool v7 from here: https://www.androidfilehost.com/?fid=817550096634776735
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
If you get an unspecified "network error" you could be in for some major headaches. Many tablet's serial number and/or the mac address of the mainboard seem to be registered incorrectly in Asus database. This problem is widely discussed on several forums, just google: "cannot unlock TF700" or similar and read the threads. Too many variables to discuss this here...
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
To determine if you need to update your bootloader read post #3
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8.+ you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
TROUBLE WITH ADB FASTBOOT DRIVERS? SALVATION IS NEAR!! (May 2017 edit)
And it is called FWUL (F-orget(?) Windows Use Linux) a great Arch Linux distro that you can boot off a USB stick or CD with simple adb fastboot all setup for you. Follow the instructions, set your boot sequence to boot from USB or SD drive first and disable Secure Boot in your BIOS Security settings. I have fought with Windows driver problems as long as I have been using Android devices and some stuff I never got to work. With this baby I was able to connect to 4 different Android devices with no problems at all. A beauty! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Inside that folder Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
If all of the above fails follow these instructions: https://www.michaelcrump.net/power-tip-for-windows-users-open-command-prompt-here/
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://twrp.me/devices/asustransformerinfinityTF700T.html
Download the latest version of TWRP. Version 2.8.0 or later is ready for KitKat and Lollipop custom roms as well as backward compatible with JB ROMs.
FYI ONLY: If you for whatever reason want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Formatting data is only necessary in cases of data corruption.
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
This will flash the recovery to the recovery partition
Example:
If the file is named TWRP_2.8.6.2_TF700_recovery.img, the fastboot command is:
Code:
fastboot -i 0x0B05 flash recovery TWRP_2.8.6.2_TF700_recovery.img
You can rename the file to something easier to type, but file name and fastboot command have to match.
So if you renamed the file to twrp.img:
Code:
fastboot -i 0x0B05 flash recovery twrp.img
If your recovery comes as a blob:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock rom you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers or check out post #2. There's a description of the most popular roms for this tablet.
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you

ROMs for the TF700
Update June 2017:
Time moves on and this tablet is till alive....
Most of the roms below are ancient by now. One dev, the legendary timduru, is still working for this tablet and currently supporting Nougatella, Android 7.1.2 for this tablet.
Skip to here if you are thinking about a current rom: https://forum.xda-developers.com/showpost.php?p=72540013&postcount=346
Click to expand...
Click to collapse
KatKiss-KatshMallow by timduru (MM on the TF700 - who would have thought?) is still under intermittent but active development and it is a beauty. Multi-window support anyone?
http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements, but since there have been no further Asus updates, development on this rom has stopped. This rom would give you the most Asus-like experience on this tablet.
http://forum.xda-developers.com/showthread.php?t=2425383
And here is the recent incarnation of this rom: CROMi-X Resurrected: http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
@LetMeKnow still releases a new teak here and there, so keep following the thread.
Development on all of the following roms has stopped. The devs have moved on to other devices
CROMBi-KK is based on CM11 and tweaked for this tablet but a little buggy. The later LP based roms from the same team are definitely better.
http://forum.xda-developers.com/showthread.php?t=2672751
CyanogenMod is build from the ground up, CM10.x emulating JB 4.3, CM11 emulating KitKat (JB 4.4). CM was not build with a transformer (keyboard) in mind, but the dev has ironed out most of those bugs.
http://forum.xda-developers.com/showthread.php?t=1957660
ZOMBi-X: From the same team that developed CROMi-X and CROMBi-KK. Based on OMNI rom with multi-window support.
http://forum.xda-developers.com/transformer-tf700/development/rom-t2857931
ZOMBi-POP The (almost last) project from the CROMI/CROMBi/ZOMBi team. It's Omni based Lollipop for the TF700
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
A note: This rom will run with data formatted to ext4, which is the OEM default. But it benefits from /data on F2FS, the new file system developed by Samsung, more than any other rom before it. Changing the file system for /data to F2FS has become very easy since the TWRP team build support for it into their recovery. I wrote a guide for converting your data partition to F2FS here:
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
That same team took one final stab at a 6.0 rom for this tablet: http://forum.xda-developers.com/showpost.php?p=65968239&postcount=3719
But I would call this definitely an unfinished product with a doubtful future.
CM12 I don't run CM roms - try it for yourself
http://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
OmniROM by lj50036 who's on the ZOMBi team
http://forum.xda-developers.com/transformer-tf700/development/rom-omnirom-tf700t-t3056438
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
AND IF YOU LIKE YOUR NEW ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Alternative methods to install TWRP
Edit February 2015
In this section I originally explained how to flash TWRP to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work sometimes (and if you have root), but I will not recommend or promote them any longer.
Why?
Because I'v read too many stories about these apps failing, even flashing to the wrong partition - you name it.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
I have spent quite a few hours helping users who got themselves into a situation where the only thing they could access on their tablet was recovery, but they did not know anything about adb/fastboot and did not set it up when the tablet was still working. To get it to work with a soft bricked tablet is much, much harder!!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.

HOW TO UPDATE YOUR BOOTLOADER
The last official Asus firmware update to JB 4.2.1 brought us to the 10.6.1.14.10 bootloader - and it will be the last one we ever get since there will not be any Asus firmware updates anymore.
If you are on an older bootloader and want to run a KK or Lollipop ROM, you should update your bootloader to this version.
Determining which bootloader you currently have
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.14.10-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.14.10 is your bootloader version
20130801 is the build date (and immaterial in most cases).
Updating your bootloader
Still on stock with stock recovery:
Just OTA update to the last Asus firmware or flash it manually.
Custom ROM with custom recovery
Either:
1. Flash Asus stock firmware in your custom recovery
Download the official Asus firmware, unzip it once, flash that second zip in TWRP or CWM.
The distinct disadvantage of this method is that you will loose your custom ROM and your custom recovery and you will have to reflash them, but it works to get you onto the latest bootloader - or the latest stock rom if you desire to return to stockOr:
2. Flash only the bootloader in recovery
This is what I would recommend you do.
Go here for a collection of flashable bootloader/recovery packages: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
If all you need is the latest US bootloader, go to post #3.
The packages (bootloader + recovery) will replace not only your bootloader, but also your current recovery with whatever the TWRP version in the package is.To flash a KK or Lollipop ROM afterwards you need TWRP 2.8.+.
If you choose a bootloader package with an older recovery, you need to flash the latest TWRP version after you flashed the above bootloader package. In between you have to reboot (do not skip this step!)

sbdags said:
@moderator could we sticky this please.
Brilliant post Bernd
Click to expand...
Click to collapse
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.

berndblb said:
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
Click to expand...
Click to collapse
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Mod edit: I deleted your previous post to give the third post to OP. I will copy paste it here.
@stamatis could we sticky this please.
Brilliant post Bernd :good:

sbdags said:
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Click to expand...
Click to collapse
No problem. You "jumping the gun" is an honor to me.
Thanks

Well written and very informative post. Thread stuck.

please help
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported. So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh.. So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks

blackc3 said:
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported.
Click to expand...
Click to collapse
I think you mean v8, v7 for the Asus Unlock tool?
You have to extract it. On the tablet you can use the app ES File Explorer from the Play Store. It downloads as a .rar file, the result has to be an apk
So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh..
Click to expand...
Click to collapse
You have to get the drivers working - no excuses
Without working drivers you cannot push a recovery to your tablet. What Windows version do you have?
Try installing the Asus PC Sync Utility, try the Google Naked Drivers, try the ones attached to this post (note: I have not tested these myself) - you will have to find the correct combination for your PC yourself.
Here are a few links that may be helpful.
http://www.addictivetips.com/window...-or-device-drivers-manually-in-windows-vista/
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
Click to expand...
Click to collapse
No. You just got started!
Here are a couple of different approaches if you cannot unlock:
http://www.transformerforums.com/fo...discussion/42587-my-unlocking-experience.html
http://forum.xda-developers.com/showpost.php?p=51210808&postcount=6

Thanks for the guide,
everything went smooth until this step:
fastboot -i 0x05B0 flash recovery twrp.blob
Now my cmd just hangs there (been like 10 mins), not sure if i should restart tablet or cmd? Tablet still in fastboot screen. Thanks.

What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk

berndblb said:
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
It recognizing it correctly (atleast from what I understood from the guide). If it matters, I installed twrp 2.7 instead since it indicated 2.6.3.2+
I get:
015d2bbce9141e18 fastboot
Can I safely reboot/close cmd and try again?

Yes. Ctrl C will cancel the command, you should get the command prompt back.
Strange... twrp.blob is in the same folder as your fastboot.exe, right?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
OP updated
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!

droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
A question for @_that as I always thought you needed the ID. Maybe not?

sbdags said:
A question for @_that as I always thought you needed the ID. Maybe not?
Click to expand...
Click to collapse
Apparently there was an older fastboot version that needed it. I've not used the ID for a long time.
It doesn't matter if you use 0x0B05 or 0xb05, it's the same number.

Great tut.
Thanks for posting. Good info, very concise.
berndblb said:
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here or if my instructions are dead wrong. I may be a fiend who's going for the world record in tablets bricked. Do your own research, read thrice, ask twice, flash once.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using the custom recovery
Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step. However - as of today, Feb 27, 2014, another path to installing a custom recovery opened up (again) and that method (using GooManager to install TWRP - see below) requires you to be rooted.
So if you want to root the TF700 on stock firmware there are two ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK). There was some controversy around Kingo. Late last year their threads on XDA got closed because they used the vroot method which had a sniffer component that collected information and sent it to servers in China. The developers of Kingo removed vroot and worked it out with XDA. Their threads got re-opened in December. So I believe Kingo is safe to use - but you be the judge of that....
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: ASUSTeK Computer Inc. -Support-
Select your device, choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v8 (I assume you are on JB 4.2 firmware)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you or use ES File Explorer on the tablet
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. For now I assume it goes ok.
To check if you are unlocked, boot the tablet and read the tiny script. It should say: This device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up.
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows 7/8:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
This is not confirmed to work on Win 8.1, but that may be due to the driver signature verification in Win8. Google how to turn it off.
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for the adb folder) and the corresponding drivers. Takes about 15 seconds
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Linux and iOS: Check out this site https://code.google.com/p/adb-fastboot-install/ or this [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers
The fun begins
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
In Win XP select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
All Windows versions: In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers.
Let's assume everything is good:
On your computer go here: Techerrata Downloads - Browsing tf700t
Download the correct TWRP version for the ROM you intend to flash (see list below)
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock ROM you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom ROM and they are rooted anyway.
Alternative methods to installing TWRP
A) The app GooManager, free in the Play Store, downloads and installs TWRP (currently version 2.6.3.1) on the TF700. But GooManager requires root AND the bootloader to be unlocked. For users who are rooted already or those who cannot get ADB and fastboot to work on their PC, rooting with Motochopper or Kingo and then using GooManger to install TWRP may be a good alternative.
B) sbdags, the developer of CROMi-X (probably the most popular ROM for this tablet) provided a tool that automates the fastboot commands necessary to install a recovery..
I personally believe it is essential to have a working fastboot connection from PC to tablet and becoming familiar with basic fastboot commands when you develop a flashing habit, but if you want to take a shortcut his tool is here: http://forum.xda-developers.com/showthread.php?t=2646279
ROM – Recovery combinations
I assume you are on the 10.6.1.14.10 bootloader
CROMi-X – TWRP 2.6.1 or later http://forum.xda-developers.com/showthread.php?t=2425383
CROMBi-KK – TWRP 2.7.0 http://forum.xda-developers.com/showthread.php?t=2672751
NOTE: Formatting data in TWRP 2.7 takes a lot longer than in previous versions (up to 90 minutes). DO NOT INTERRUPT THE PROCESS if you format /data (usually only necessary with data corruption)
CM11 – CWM 6.0.4.6+ http://forum.xda-developers.com/showthread.php?t=1926286
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Installing a custom ROM
The most popular custom ROMs for the TF700 are CROMi-X, CROMBi-KK and CyanogenMod (CM).
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements.
CROMBi-KK is a mix of CM11 and CROMi-X and at this point still in beta.
CM11 is build from the ground up, emulating KitKat (JB 4.4).
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
Note: Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers
Note: It is recommended (mandatory if you go for CM) to do a Factory Wipe in TWRP before installing a custom ROM.
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
From here on out it's as easy as downloading the installation file of your custom ROM, booting into recovery, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you go for CROMi-X and TWRP as your recovery, make sure you check "verify zip signature" under the Install menu. sbdags signs his ROM zips - a better way to ensure file integrity than md5 sum.
For a general overview and comparison of ROMs check out Gtanner00's thread, post 2 + 3. Note that he describes roms for the TF300, but since the framework for the TF300 and TF700 is very similar there is usually an equivalent rom for the TF700 at the XDA Developers forum.
http://www.transformerforums.com/forum/showthread.php?t=41508
Do not follow or download from any of the links he provides! I only link to his thread for general information!
Any questions - please ask.
AND IF YOU LIKE THE ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Click to expand...
Click to collapse

droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
Same thing happened to me. Fastboot recovery command did not return after over 10 minutes. I did Ctrl-C. Ran the command again and got the invalid argument error. Tried a couple times with same result. Unplugged and replugged USB cable (to same USB port). Ran the command again and it worked. When it worked, it took 11 seconds to flash recovery.
Also probably worth noting in the guide is that the Asus boot unlocker requires Google sign-in. If you have 2-step verification setup on your Google account, you need to use a one-time app password to sign-in.
Code:
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
^C
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
OKAY [ 2.704s]
writing 'recovery'...
OKAY [ 8.026s]
finished. total time: 10.731s

[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.

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

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

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

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

Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Step by step guide for lg v20 h918 unlocking, downgrading, rooting and twrp

STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY)
DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES BRICKING OR DAMAGING YOUR MOBILE IF THE PROCEDURE IS NOT FOLLOWED CORRECTLY. I'M JUST SHARING THE WHOLE PROCESS WHICH I HAVE FOLLOWED TO ROOT AND INSTALL TWRP IN MY LGV20 H918 UNLOCKED T MOBILE.
AND I HAVE TESTED THIS IN MY OWN DEVICE AND WAS ABLE TO ROOT AND ACHIEVE TWRP.
THIS IS ONLY FOR LGV20 H918 VERSION
ENSURE INTERNET IS UP AND RUNNING IN YOUR PC
EDIT: THE WHOLE PROCESS HAS NOW BEEN AUTOMATED IN TWO SIMPLE STEPS TO PREVENT ANY POTENTIAL DAMAGE TO YOUR DEVICE. THANKS TO THE LAFSPLOIT CREATOR BRIAN @runningnak3d.
JUST FOLLOW THE PROCEDURE BELOW AND YOU SHOULD HAVE YOUR DEVICE ROOTED IN NO TIME
1. BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING.
2.MAKE SURE YOU HAVE CHARGED YOUR PHONE TO AT LEAST 90 PERCENT
CHECK YOUR PHONE SOFTWARE VERSION IN SETTINGS---ABOUT PHONE----SOFTWARE INFO
IF IT IS ANYTHING BETWEEN H91810P TO H91810U MEANS IT IS ARB1 (ANTI ROLL BACK 1) AND YOU NEED TO USE LAFSPLOIT METHOD TO ROOT AND INSTALL TWRP,
IF YOUR VERSION IS H91810O OR BELOW (ARB0), YOU CAN EITHER USE DIRTYCOW OR LAFSPLOIT METHOD FOR THE SAME.
IF YOU ARE ON ARB1, PLEASE FOLLOW THE METHOD BELOW,
PART 1: DOWNGRADING
IF YOUR VERSION IS H91810 (Q, R, S, T, U) YOU NEED TO DOWNGRADE TO A LOWER VERSION ( H91810P) TO EXECUTE LAFSPLOIT.
IF YOU ARE ALREADY ON H91810P, YOU STILL NEED TO RE FLASH THE H91810P KDZ AGAIN FOR THE LAFSPLOIT SCRIPT TO WORK CORRECTLY.
DOWNLOAD H91810P KDZ FILE FROM BELOW
https://androidfilehost.com/?w=files&flid=282709
DOWNLOAD AND INSTALL ALL THE FILES BELOW IN YOUR PC
UPPERCUT AND LGUP----
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LG DRIVERS---
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
CONNECT YOUR MOBILE TO YOUR PC IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
RUN UPPERCUT.EXE WHICH WOULD OPEN LG'S UPDATER TOOL AUTOMATICALLY.
INSIDE THE LG UPDATER TOOL, CLICK ON BIN AND SELECT THE H91810P KDZ FILE DOWNLOADED EARLIER.
NOW SELECT UPGRADE AND FLASH
ENSURE THE USB CABLE IS CONNECTED THROUGH THE FLASHING PROCESS AND WAIT FOR YOUR PHONE TO REBOOT AND THEN REMOVE THE USB CABLE.
CHECK THE SOFTWARE VERSION AND ENSURE IT IS H91810P
PART 2: UNLOCKING BOOTLOADER
HEAD TO SETTINGS---ABOUT PHONE----SOFTWARE INFO (ENSURE IT IS H91810P)
ENABLE DEVELOPER OPTION IN YOUR PHONE BY CLICKING ON THE BUILD NUMBER MULTIPLE TIMES
NOW HEAD TO SETTINGS---DEVELOPER OPTIONS
TURN ON OEM UNLOCKING, ENABLE USB DEBUGGING AND DISABLE 'VERIFY APPS OVER USB'
NOW CONNECT YOUR PHONE TO PC AND OPEN ADB COMMAND CENTER PROMPT IN YOUR PC
adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
fastboot oem unlock---->THIS COMMAND WOULD UNLOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
fastboot oem device-info OR fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN UNLOCKED OR NOT.
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
IF THE BOOTLOADER HAS BEEN SUCCESSFULLY UNLOCKED, THE DEVICE WILL SHOW AN UNLOCKED BOOTLOADER WARNING MESSAGE WHILE BOOTING (THIS CAN BE IGNORED OF COURSE)
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
PART 4: INSTALLING TWRP AND ROOTING USING LAFSPLOIT
BEFORE PROCEEDING ENSURE YOU BOOT YOUR PHONE AND DONE ALL THE BASIC SETTINGS
NOW HEAD TO THE DEVELOPER OPTIONS IN YOUR DEVICE AND ENSURE OEM UNLOCKING AND USB DEBUGGING ARE SWITCHED ON.
NOW CONNECT YOUR DEVICE TO THE PC (RUNNING LINUX OS FROM PENDRIVE) IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
DOUBLE CLICK ON THE LG FOLDER INSIDE FWUL DESKTOP
INSIDE THAT, DOUBLE CLICK ON LGLAF(RUNNINGNAK3D) ICON WHICH WILL OPEN A TERMINAL
ENTER THE BELOW COMMANDS
git pull
git checkout h918-miscwrte
./step1.sh
THE ABOVE COMMAND FLASHES TWRP RECOVERY ONTO YOUR DEVICE.
WAIT AND PULL OUT YOUR DEVICE WHEN IT ASKS TO.
RECOMMENDED: NOW THAT TWRP HAS SUCCESSFULLY INSTALLED, YOU CAN MANUALLY FORMAT,FLASH LATEST TWRP RECOVERY AND USE ANY METHOD LIKE MAGISK OR SU FOR ROOTING.
INSIDE TWRP RECOVERY. FIRST FORMAT USING WIPE--ADVANCED FORMAT--TYPE yes AND FULL DO A FULL FORMAT, THEN FLASH MAGISK AND THE LATEST TWRP RECOVERY BELOW.
MAGISK ZIP DOWNLOAD:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
LATEST TWRP BY PHOENIX(H918):
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
OR
IF YOU ARE UNSURE ABOUT FORMATTING AND FLASHING, JUST USE THE BELOW COMMAND TO DO ALL THE WORK AUTOMATICALLY
CONNECT YOUR DEVICE AGAIN IN DOWNLOAD MODE AND ENTER THE FOLLOWING COMMAND
./step2.sh
THE ABOVE COMMAND FORMATS YOUR DEVICE AND FLASHES MAGISK TO ACQUIRE ROOT.
TIP : IF YOU FACE ANY ENCRYPTION ERROR AFTER USING STEP2. SH, DO A ADVANCED FORMAT WITHIN TWRP AND FLASH MAGISK AND LATEST TWRP BY PHOENIX MANUALLY.
YOU ARE NOW ROOTED WITH TWRP RECOVERY INSTALLED.
REMEMBER TO BACK UP THE CURRENT ROM BEFORE FLASHING ANYTHING..... DO CHECK POST #2 FOR OTHER TWEAKS
IF YOU WISH TO UPDATE TO LATEST STOCK (10U) AND KEEP ROOT AND TWRP, JUST FOLLOW THIS LINK AND DO REMEMBER TO ROOT USING MAGISK AFTER FLASHING THE ROM BEFORE YOU BOOT.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I WOULD LIKE TO THANK ALL THE DEVOLEPERS WHO HAVE CREATED THE ABOVE SOFTWARES WITHOUT WHICH THIS ISNT POSSIBLE.
CREDITS:
@autoprime FOR HIS UPPERCUT TOOL
@steadfasterX FOR HIS FWUL TOOL
@Phoenix591 FOR HIS WORKS ON TWRP RECOVERY
AND FINALLY, @runningnak3d FOR HIS EXCELLENT WORK IN ROOTING OUR DEVICE :good:

WHAT NEXT?
NOW THAT YOU HAVE ROOTED YOUR MOBILE, I WOULD RECOMMEND DOING THE BELOW TWEAKS FOR FURTHER ENHANCED EXPERIENCE....
1.THERMAL THROTTLING
IF YOUR ARE STILL ON A STOCK BASED ROM , I WOULD STRONGLY RECOMMEND TO RECONFIGURE YOUR THERMAL FILE TO PREVENT ANY POSSIBLE LAG WHEN USING EXTENSIVELY...
FIRST DOWNLOAD THE FILE BELOW:
https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view
USE A ROOT EXPLORER (PREFERABLY ES EXPLORER) AND GO TO ROOT/SYSTEM/ETC.
YOU SHOULD HAVE A FILE NAMED thermal-engine-8996.conf
RENAME IT TO thermal-engine-8996.conf.bak (JUST FOR A BACKUP IF ANYTHING GOES WRONG)
ENSURE THE ABOVE DOWNLOADED FILE IS IN .conf FORMAT
IF IT ISN'T , RENAME TO thermal-engine-8996.conf
NOW SAVE THE FILE TO THE SAME DIRECTORY VIZ ROOT/SYSTEM/ETC
GIVE PERMISSION TO THIS FILE TO rw-r--r-- USING THE ROOT EXPLORER ( SELECT FILE--->PERMISSION--->READ WRITE, READ, READ)
FINALLY SAVE AND REBOOT.
THIS WOULD OVERWRITE THE THERMAL LINKED PERFORMANCE OF THE CPU TO AVOID ANY LAG WHEN USING EXTENSIVELY.
2. RCTD REMOVER
ALSO I WOULD STRONGLY RECOMMEND TO REMOVE THE LG'S RCTD CCMD AND TRITON MONITORS AS THESE WOULD RUN CONTINUOUSLY IN A ROOTED LG PHONE AND CONSUME LOT OF RESOURCES...
JUST INSTALL THE RCTD REMOVER APP FROM BELOW LINK:
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
GRANT SU PERMISSION AND CHECK THE DESIRED FILES (I CHOSE ALL THREE FILES) AND CLICK ON PATCH, FLASH IMAGE AND REBOOT (THIS WOULD PATCH THE BOOT FILE, SO AGAIN IT IS ADVISABLE TO CREATE A BACKUP OF THE CURRENT BOOT IMAGE USING TWRP OR WITHIN THIS APP ITSELF)
3. SCREEN CALIBRATION:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
INSTALL KERNAL AUDITOR APP FROM PLAY STORE AND GRANT SU ACCESS
CHANGE THE BELOW VALUES WITHIN THIS APP (SCREEN SETTINGS)
Minimum RGB value = 35
Saturation Intensity = 27
Screen Hue = 1520
Screen Value = 112
Screen Contrast = 132
THIS WOULD SOMEWHAT REDUCE THE BLUE TINGE AND GHOST APPEARANCES OF THE SCREEN
CREDITS: @Holyman007 for his thermal tweak @Zacharee1 for his rctd remover app

I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?

turdbait said:
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
Click to expand...
Click to collapse
this would end up with a stock rooted phone with twrp recovery if all the methods are correctly followed..
......final result would be.... you would end up with a rooted stock rom with a twrp recovery....
your second screen will work perfectly.....
please let me know if you need a different thread for installing custom rom, and to reduce the lag., install sound mod to get maximum sound output and customize second screen... i will create a noob friendly thread for these as well......

Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443

kish9046 said:
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
Click to expand...
Click to collapse
Thank you, I've been reading up on the main lafsploit thread for awhile but I was still not sure about the whole flashing KDZ file and stuff so when you posted this thread it was a motivator to try it out. Got a day off from work tomorrow so gonna try it then so I don't got to worry about the time.
I'm interested in the max sound output and second screen customization if you got the time and its not to much to ask. If you want to wait till either someone else comes along thats interested or till I root just so you don't waste your time I shall update hopefully sometime tomorrow. Thanks again.

kish9046 said:
sha256sum h918-twrp.img ----> THIS WOULD AGAIN THROW A HASH, CHECK IF BOTH THE HASHES ARE ABSOLUTELY SIMILAR
Click to expand...
Click to collapse
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.

onlineaces said:
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
Click to expand...
Click to collapse
Thanks for the heads up.... Changed to EXACT...

I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.

turdbait said:
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
Click to expand...
Click to collapse
great to hear that u have root now.... will post soon on other mods including a step-by-step process on removing rct soon....

All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs

cnjax said:
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....

Glad someone actually laid it out step by step.

kish9046 said:
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Click to expand...
Click to collapse
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.

BROKEN1981 said:
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
Click to expand...
Click to collapse
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1

kish9046 said:
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
Click to expand...
Click to collapse
Abr1 yes I am rooted with twrp.
As I said, the commands to push magisk and twrp to sd did not work. I used usb otg in twrp to push magisk, but forgot to put twrp to flash as well.
I forgot that twrp had replaced download mode, so I was going a bit nuts trying to figure out how to get twrp to recovery. Lolol
Now I'm on latest update with rtcd removed thanks to the op who hosted it on xda as a flashable zip.

Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?

tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
As you are in twrp, you can manually flash magisk zip and twrp recovery.....

tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.

tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.

[GUIDE] Unlocking, rooting & Pixel OS install guide for Pocophone F1

There are already many guides explaining how to unlock, root and install a custom ROM on your Pocophone F1.
But even following the guides, I met multiple issues (access denied to data partitions, boot loops, ADB recovery stopped working ...).
Here is the full procedure that worked for me.
You will need a computer running under Windows for unlocking your phone because Xiaomi only provides a Windows version of its unlocking tool.
I performed the Fastboot and ADB steps under Linux (Ubuntu) because the installation of the tools under Linux is straightforward whereas I had hard times installing ADB under Windows. Moreover, my ADB client sometimes fails to connect under Windows whereas I have no issues under Linux.
Windows steps
-------------------
1/ backup all your personal information (pictures, videos, docs ...) because unlocking will erase all your data.
2/ you have to create a MIUI account from the stock ROM:
- fill in your email address
- set your phone number otherwise Xiaomi won't let you unlock your phone
3/ Xiaomi constrains you to wait for 72 hours after your MIUI account is created before you're able to unlock.
You have no choice but waiting (users reported that the classical fastboot oem unlock does not work).
The delay may differ from one user to another. Some users even reported a ridiculously long unlocking delay of 720 hours (~ 30 days).
It may depend on your country, phone operator etc ...
4/ download the official Xiaomi unlock tool:
miflash_unlock-en-3.3.827.31.zip
MD5: 8812104e1f6859087f1a9d66481ce9e5
SHA256: 4644878fcaa794d8c0bee67900df80efb28b0d8bd63669d943c043412b06790d
5/ run miflash_unlock.exe while connected to Internet.
The Internet connection is required because the tool performs a user permission checking before allowing you to unlock your phone.
- fill in again your email address & password
- accept all the annoying Xiaomi disclaimers
6/ finally you will get a screen with 3 green checkboxes telling you that your phone was successfully unlocked:
{
"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"
}
Linux steps
--------------
7/ install ADB and Fastboot on your Ubuntu system as superuser:
$ sudo apt-get install android-tools-adb android-tools-fastboot
This simple command is enough for installing all the ADB stuff. Unlike with Windows, you don't need to spend time installing multiple drivers and waste time trying to understand why it doesn't work.
I recommend that all the 'adb' commands are launched as superuser using 'sudo'.
Indeed, some ADB commands will only work as superuser.
Most likely, the ADB path is not set in the superuser environment.
Consequently, you will have to locate the 'adb' path with the 'which' command then launch 'adb' with its absolute file path:
Example with ADB installed under /usr/share/android-sdk/platform-tools
Find 'adb' location:
$ which adb
/usr/share/android-sdk/platform-tools/adbLaunch 'adb' using the found path:
$ sudo /usr/share/android-sdk/platform-tools/adb devices

8/ download the following packages and store them all in a new directory called 'adb':
twrp-3.2.3-2-beryllium.img
This is the latest TWRP recovery for the Pocophone F1.
MD5: 3fbf82042f5ea4e332c24cffc6ac1a4b
SHA256: 71a2fb92813fc7c77e7caf2e4b6716dda6cd688d175c56ec6dcdf34a458223b5
beryllium-9.1.24-9.0-vendor-firmware.zip
Under recent versions of Android, the vendor now provides a unified hardware abstraction layer.
Android now relies on this HAL so it can now be released independently from the hardware layer. This new architecture is also called 'Trebble'. The PixelExperience 9.0 released by jhenrique09 on 05/02/2019 relies on the Pocophone Pie 9.1 vendor firmware which must be installed first.
MD5: e931fb719c86f54b12ab4b91857335af
SHA256: 35cd48bab31755287a742ce7dfba4b75343daece2dcf31a27e1a650851e46ae9
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip
This version requires that the Pie 9.1 vendor firmware is installed on the phone.
If you don't, you won't be able to go further and will get the Updater process ended with ERROR: 7 error when trying to flash.
MD5: 804305f334dcb6c1a41b9b2ab91a0ce6
SHA256: 0b8ae9f849971ea14d12065d82fa86fe0051d9570ad08e1008c095757b1fab55
DisableForceEncryption_Treble.zip
This tool will disable automatic encryption which occurs at first OS initialization.
This package includes Magisk 16.7 which will be installed by the script.
This is not the latest Magisk version so we will upgrade it later with the latest Magisk 18.1.
MD5: bb2b91c92aa9d441f41a325438d4a081
SHA256: ba0d9de4474594f01837eebf06edac1daa38775cfa78840cd885c28c5032fae2
Magisk-v18.1.zip
Magisk will allow applications to gain root access to your phone. It does quite the same as SuperSU but it does it better. Magisk pass the SafetyNet test whereas SuperSU generally doesn't. It can also hide itself from apps so they will run as on a stock phone.
MD5: 3ab4d455e6f27f0098c1a723705c6ea1
SHA256: eb06176ea1a2a564a82167902e8159fab13af330f3224c725f04b653232bb527
Magisk-uninstaller-20190204.zip
We will use the uninstaller later to uninstall Magisk 16.7 properly before installing Magisk 18.1.
MD5: 34745c7f3c0d13dbeb5f4223ad887b7b
SHA256: ac80eb0131983c8810fab23d092342e07d1b69b2d91035c027cb7a34ed18f9eb
Personally, I chose the PixelExperience ROM because it is surprisingly stable and fast for one of the first custom Pocophone F1 ROM.
Moreover and specially if you disable auto-encryption, the phone runs much faster than the stock ROM.
The basic Google Apps are included in the ROM so you don't have to install them separately like you have to do with LineageOS.
Finally, the Pixel interface is very ergonomic and much pleasant to use than MIUI.
Before this, I tried LineageOS 15 then 16 but none of them worked for me. I got some boot loops and it even corrupted my bootloader (look at the troubleshooting section here if you meet the same issue).
9/ if present, remove the SD Card because the system can mess up between the apps installed on the internal storage vs external sdcard.
10/ open a terminal shell
11/ change directory to your 'adb' directory created for storing your packages
12/ with phone unplugged, power off then hold Volume Down & Power to enter FASTBOOT mode
13/ connect your phone to computer using your USB cable
14/ run fastboot devices as superuser to check if your phone is correctly connected:
$ sudo fastboot devices
ad5e3f6 fastboot
If you see your device listed like here then everything worked fine.
15/ flash the TWRP 3.2.3-2 bootloader:
$ sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
target reported max download size of 536870912 bytes
sending 'recovery' (31004 KB)...
OKAY [ *1.251s]
writing 'recovery'...
OKAY [ *0.312s]
finished. total time: 1.563s
The flash command will reply 'OKAY' twice if flashing is successful.
16/ you now have to reboot to recovery directly from FASTBOOT mode otherwise your recovery will be overwritten by stock ROM if you reboot to system. This is performed by invoking fastboot with the boot argument.
$ sudo fastboot boot twrp-3.2.3-2-beryllium.img
downloading 'boot.img'...
OKAY [ *1.216s]
booting...
OKAY [ *0.064s]
finished. total time: 1.280s
The TWRP splash screen should now show up.
17/ TWRP 3.2.3-2 handles decryption but I chose to work without encryption for several reasons:
- you might be unable to use your external SD card outside your phone because of encryption,
- your phone will run faster,
- certificates could probably be revoked remotely by manufacturers or Google so you can lose access to your phone and data.
If your partitions are encrypted (which is the case if you're coming from MIUI), you should format your data partition to restart from an unencrypted partition. Formatting will erase all your data so check you're backed up before doing it.
18/ you now have to reset your phone to perform a clean install.
As far as I am concerned, I advise wiping everything to start from a fresh brand new system.
To do so, tap Wipe, tap Advanced Wipe then check:
* Dalvik / ART Cache
* Cache
* System
* Data
* Internal StorageFinally, swipe to wipe.
19/ tap Back arrow then Reboot and finally Recovery
20/ plug your phone with USB cable to your computer.
21/ first of all, kill any running ADB daemon. We do it to be sure ADB daemon is started as superuser.
Indeed, some ADB commands won't work if not superuser.
$ sudo adb kill-server
Then check that ADB is working from recovery by typing the command:
$ sudo adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ad5e3f6 recovery
The 'daemon started successfully' output notifies you that ADB daemon just started.
If your device is listed then everything is fine.
22/ go to your 'adb' directory then type the following command to copy all the packages to the /sdcard phone directory:
$ sudo adb push beryllium-9.1.24-9.0-vendor-firmware.zip /sdcard
beryllium-9.1.24-9.0-vendor-firmware.zip: 1 file pushed. 21.5 MB/s (442907715 bytes in 19.651s)
$ sudo adb push PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip /sdcard
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip: 1 file pushed. 21.4 MB/s (1065939977 bytes in 47.478s)
$ sudo adb push DisableForceEncryption_Treble.zip /sdcard
DisableForceEncryption_Treble.zip: 1 file pushed. 21.3 MB/s (4447302 bytes in 0.199s)
$ sudo adb push Magisk-v18.1.zip /sdcard
Magisk-v18.1.zip: 1 file pushed. 21.4 MB/s (4362466 bytes in 0.194s)
$ sudo adb push Magisk-uninstaller-20190204.zip /sdcard
Magisk-uninstaller-20190204.zip: 1 file pushed. 21.2 MB/s (2290127 bytes in 0.103s)23/ go to main TWRP main menu then tap Install then tap beryllium-9.1.24-9.0-vendor-firmware.zip to install.
The vendor firmware must be installed prior to the ROM which relies on it.
If you forget this step, you will get a Updater process ended with ERROR: 7 error when trying to flash the ROM.
24/ go to main TWRP main menu then tap Install then tap PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip to install.
25/ go to main TWRP menu then tap Install then tap DisableForceEncryption_Treble.zip to install.
DisableForceEncryption_Treble will prevent the ROM from auto encrypting your phone upon first initialization. It also install Magisk which will give you root access.
Note that you can skip this step if you want to keep your phone encrypted.
26/ go to main TWRP menu then tap Install then tap Magisk-uninstaller-20190204.zip to uninstall any existing version of Magisk. The DisableForceEncryption_Treble also installs Magisk 16.7 so this step is required for a proper removal.
27/ go to main TWRP menu then tap Install then tap Magisk-v18.1.zip to install.
28/ now, boot to System.
29/ If you installed DisableForceEncryption_Treble then your phone will initialize without encryption.
30/ you now have to link your Pixel OS phone to your Google account and install your apps.
YOU ARE ALL DONE
Congratulations !!! you now have a Pixel OS and rooted system installed on your Pocophone F1.
TROUBLESHOOTING
-------------------------
Before installing Pixel OS, I had hard times trying to flash LineageOS on my Pocophone F1.
For a reason, it corrupted the bootloader and ADB server stopped communicating with my computer.
I thought I bricked my phone but I successfully restored everything by following those steps:
1/ boot to TWRP by holding Volume Up & Power
2/ tap Wipe
3/ tap Advanced wipe
4/ check everything except USB-OTG then swipe to wipe all.
5/ hold Power button for a long time, the phone will then try to boot to System but fall back to FASTBOOT because we just erased the system partition at the previous step.
I advise that you follow exactly this procedure. I can't explain why but I first reboot to FASTBOOT from the TWRP menu but doing like this did not fix the ADB recovery server which still kept unresponsive after reflash.
6/ reflash TWRP by running again sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
7/ hold Volume Up & Power buttons to boot again to TWRP recovery.
8/ connect your phone to computer with USB cable.
9/ type adb devices and you will see your device again.

Cristobal2018 said:
$ adb push beryllium-8.11.7-9.0-vendor-firmware.zip /sdcard
beryllium-8.11.7-9.0-vendor-firmware.zip: 1 file pushed. 22.3 MB/s (402068528 bytes in 17.164s)
Click to expand...
Click to collapse
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?

kousarali said:
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?
Click to expand...
Click to collapse
You're absolutely right.
If you forget flashing the vendor firmware before PE, you'll get a system error 7 when trying to flash the PE ROM.
Many people encountered this error when this ROM was released.
I updated the tutorial.
Thanks!

Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
The other way to find the link is searching Google for the MD5 or SHA256 signature.

Cristobal2018 said:
The other way to find the link is searching Google for the MD5 or SHA256 signature.
Click to expand...
Click to collapse
akashkyh said:
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy
Click to expand...
Click to collapse
Thanks a lot guys.

I updated the guide with the official links to the packages.
The package names are now all clickable.

if i already installed disable force encryption zip during rooting procedure do i need to flash it again in step 27

Hi, even though i have flashed the vendor firmware, i got error 7 for pixel rom. I dont know what is the problem. I do wipe for all and flash vendor zip. But got error7 in pe Rom

Question
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance

Antidote03 said:
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance
Click to expand...
Click to collapse
I just tried to flash the latest PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL and it raises a system error 7 complaining for the missing vendor 9.1 firmware.
According to the https://downloads.akhilnarang.me/MIUI/beryllium/ download page, you will notice that akhilnarang released vendor beryllium V10.1.3.0-9.0 vendor firmware a long time ago (december 2018).
Consequently, for flashing the latest PixelExperience ROM (20190205), I would advise to first flash vendor 9.1 available here: beryllium-9.1.24-9.0-vendor-firmware.zip

Is it really necessary to flash DFE (step 27)? Thank you.

Thank you so much for the comprehensive guide. I got my Poco F1 yesterday and I have a good idea what I need to do, but there's always some uncertainty.
DFE being the one question I have, but you explained it etc, so it looks like at this point it is recommended, but not necessary as such - if I understand.
Vendor firmware is another question mark for me, but it makes a bit more sense.
Right now, I am just going to look at rooting my phone, once I'm done with that I will start looking at custom ROMS.
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
I almost think that if it's just rooting via magisk you don't need to swipe right. since I don't think magisk touches system (but not sure).
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).

autisticarvin said:
Is it really necessary to flash DFE (step 27)? Thank you.
Click to expand...
Click to collapse
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.

Cristobal2018 said:
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.
Click to expand...
Click to collapse
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.

autisticarvin said:
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.
Click to expand...
Click to collapse
Of course, I should have written 'flash' instead of 'root'

d.casper.b said:
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
Click to expand...
Click to collapse
Rooting allows the applications to run as root so the only requirements for doing it is having the root permissions. In recovery mode, TWRP already has the root permission so it should be enough.
I can't tell for sure because I did not test it but I would say as long as you don't require to write to the system partition, you don't have to swipe right. Magisk is not installed on the system partition so swiping should not be required.
d.casper.b said:
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).
Click to expand...
Click to collapse
Installing TWRP while leaving the stock ROM installed is not a good idea.
Indeed, the stock MIUI performs an integrity test at boot time and it restores the stock ROM if a different one is found (like TWRP). At reboot, your TWRP will be overwritten with the stock one.

Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!

CobraStrike said:
Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!
Click to expand...
Click to collapse
You can do this by using the ADB tools for Windows

Database Info

welcome