Database Develop

[HOW-TO]Unlock, Root and install CWM step by step

This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.

4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.

I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?

Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.

Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5

so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.

ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.

igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA

cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...

Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.

I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?

Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.

Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.

Recovery Mode/Boot Screen Loop

Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB

fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.

TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB

BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB

teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck

fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!

How To Guide How to install Omnirom - the complete guide

Install OmniRom 12 / 13 on Asus Zenfone 8​FOLLOWING THIS GUIDE WILL VOID YOUR PHONES WARRANTY, ERASE ALL YOUR DATA ON THE PHONE AND IN SOME RARE CASES POSSIBLY BRICK YOUR PHONE.
THE AUTHOR OF THIS GUIDE IS NOT RESPONSIBLE FOR ANY CONSEQUENCES IF YOU USE THIS GUIDE. YOU DECIDED TO DO THIS AND YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Prerequisites:​Downloads:
- vendor_boot.img
- LOS_recovery.img => Recovery image
- Omnirom.zip
Place them all in the same folder on your computer
Install and setup ADB and Fastboot
How to install Omnirom​
BACK UP ALL YOUR DATA ON THE PHONE, THEY WILL BE DELETED IN THE PROCESS!!!!!!!!!!!!!!!!!!
Update your phone to the same android version as the rom you want to install. And yes you have to install all updates until you reach the desired android version.
Install the Asus-Unlock-App from the asus website
Use the unlock app to unlock the device. Reboot. Your device will perform a factory reset,
Set up the phone, skip what you can and enable the developer options:
Settings => System => About Phone => Software-Version => Tap on Build-Nr. until the message "You are now a developer" appears.
Go to the developer options: Settings => System => Developer Options and enable "USB-Debugging".
Install ADB and Fastboot, for Windows install additionally the drivers from the asus website.
Plug your phone to your computer with the original cable. Accept USB-Debugging and allow it permanently.
Open a terminal/command window and navigate to the directory where your rom and LOS_recovery are stored. Type:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF device", if that is the case type:
adb reboot bootloader
Once the phone is in Bootloader mode type:
fastboot devices
It should show something like "ALOTOFCRYPTICSTUFF fastboot", if your device shows up, type:
fastboot flash vendor_boot vendor_boot.img
Wait until it is finished and then:
fastboot flash boot LOS_recovery.img
Wait until it is finished and then:
fastboot reboot recovery
Factory reset => Format data
Select apply update => ADB Sideload
On your computer (still in the directory with all the files) type the following:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF sideload", if that is the case type:
adb sideload name-of-your-omnirom-image.zip
Wait until its finished, check the screen on the phone. If it says "Signature verification failed" on the phonde display just click yes.
On your computer it may get stuck at 47%, but it keeps on going, be patient and wait until it shows on the phone display that sideloading is finished.
When its finished you can go back to main screen and reboot your phone. Be patient, it will reboot once or twice and take some time. If it didn't boot your rom within a few minutes something in wrong.
If all went well, you will be presented with the start screen of your newly flashed rom.
If all goes perscheid: How to recover your phone:​Prerequisites:​You have to decide if you want go back to or restore Android 12, then take the image from download A, if you want to stay on or upgrade to Android 13 then download B.
Download:
A. A13 to A12 raw image from the asus site
B. A13 Beta raw image
Recover your device​
Unpack the downloaded zip files and navigate your terminal/command window into the unpacked folder
If your phone bootloops or is stuck at the asus logo:
Press Volume down and power button until the screen gets black and then immediatly press volume up and power button until the you see the bootloader screen then release the buttons
Check if ADB can see the device by typing:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF device", if that is the case go to the next step
In the folder from step 1:
On linux: sudo sh update_image.sh
On windows: commands-to-use-a-batch-file update_image.bat
and wait until the the script is finished and you have to press any key (only enter works)
Boot the stock rom, set up your phone and start again but you can skip step 2 & 3 (unlock the bootloader). Don't forget to enable USB-Debugging before you start to do anything.

[GUIDE] Installing Lineage 18.1 (& more) [X00H] [X00I]

In this guide, i'm going to be a bit straightforward on how to install LOS 18.1 on your X00H/X00I device.
For the process, you need:
Your X00H/X00I device;
The following must be unlocked (if you didn't, you can follow the howto over my post);
A rooted phone/tablet with Magisk (any ADB & Fastboot tool is fine, but i suggest using this for simplicity);
In case you have none of the above, even a PC or Laptop with ADB and Fastboot binaries installed will suffice;
If you're on Windows, you can get the installer over GitHub;
If you're on Linux, hop into your package manager and install them via terminal (the following example will be for Debian/Deb-based/Ubuntu/Ubuntu-based distros. If you're on Arch, Fedora, etc.: just search for "fastboot" by using the respective pkg manager's search flag, then install it basing from the name it's repo gives):
Code:
sudo apt install fastboot
An USB cable (should come into the device's box, also must be capable of data transfering);
If you're going to do the process via a rooted device, the Asus device should come in it's packaging with an OTG adapter (be sure to attach the following to the rooted device);
PBRP (Pitch Black Recovery Project) for the device- OG post can be checked here;
Latest version for X00H;
Latest version for X00I;
If your device is an X00I, you can alternatively get TWRP instead;
The Android 9 Beta update (you MUST have the device updated to that version, else you'll risk the device to be bricked- for more info, check the OG post by Seba);
If you want to flash it via stock recovery, you can get the file over ASUS' site on the device;
Download for the X00H;
Download for the X00I;
If you have already flashed a custom recovery on your device, you can get the "custom recovery flashable zip"over SebaUbuntu's site;
.zip file for the X00H;
.zip file for the X00I;
Tiny discalimer on the flashable .zip above: once installed, your device's recovery will be replaced to stock (in other words, you'll lose the custom recovery);
The Lineage OS 18.1 rom and recovery (credits to @miya0405 for finding the site);
ROM and LOS Recovery for the X00H;
ROM and LOS Recovery for the X00I;
If you have all of the things required in the list, let's go!
--------------------------------------------------------------
Installing the Android 9 Beta​Stock Recovery method:​
Download the Android 9 Beta over ASUS' site (any device is fine, even using the phone itself);
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery (do Power + Vol.up combo- if your device's unlocked, tap on the volume button and select "Recovery" by pressing on the power button to confirm);
Select "Update from sd card";
Select the .zip file you've downloaded;
Wait for the update to install;
After updated, go back and select "Power off";
Custom Recovery Method:​
Download the Android 9 Beta flashable .zip over SebaUbuntu's site;
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery;
Select "Install";
Select the "External Memory" storage;
Search for the .zip file inside the SDCard;
Tap on it and install it, unchecking everything;
Swipe to continue and let the .zip file install;
The recovery will print you text on the progress (also gives advice on what to do after install);
Reboot to system;
Power off the device;
----------------------------------------------------------------
Unlocking the device:​Just a tiny reminder if you haven't yet, check my guide about it: then, resume from this point and proceed;
----------------------------------------------------------------
!!A word of advice!!​Don't install PBRP recovery just yet!
If you'll pick PBRP instead of the LOS recovery as the custom recovery of choice, flashing LOS 18.4 with it should make Lineage 100% unbootable and stuck in a bootloop!
Don't reboot back to PBRP if bootloops happen:
neither don't fix the "Cache" partiton with it, else it'll cripple more Lineage and redirect the boot to recovery or fastboot/bootloader!
TL;DR: Don't do my same mistake and flash the recovery partition with the wrong recovery (on the bright side, the device will still be salvageable).
----------------------------------------------------------------
Flashing Lineage Recovery:​Before proceeding, do the following firsthand:
Be sure to have the ADB & Fastboot binaries installed;
Your device rebooted to fastboot/bootloader mode (any method is acceptable);
Must have downloaded the recovery for your specific model (links are on the "required" list);
The device must be connected to the host machine (if you're using a rooted phone, be sure to have the OTG adapter connected to it first);
Rooted Android Device Method:​
Open the "ADB & Fastboot"tools of your choice;
Whether it is a terminal or the app i've suggested earlier: this portion will purely give instructions if you have the app;
If you're going to do the process via terminal, then jump to the "Linux Method" instead;
If it is the first time you open the tool, it should ask for root perms.- allow them;
Tap on the top right corner of the UI;
Tap on "Fastboot";
Tap on "Refresh";
Go to the "Partition" title, next to it you should see a dropdown menu;
Select "recovery";
Tap on the "Flash" button;
A file manager should open: search where the lineage recovery is (typically you can find it in the "Download" folder. The file should be called "recovery.img");
After selected, the app will automatically flash the recovery for you;
Disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Linux Method:​
Open the terminal (use the shortcut CTRL+ALT+T to open it, preferrably);
Do the following:
Code:
lsusb
# This checks if your asus device is connected proper to the machine
# If it is, lsusb should output something around a "Google" or "Qualcomm" device on the ID Bus
cd Downloads
# If you have put a different language locale, cd into the Downloads folder with it's localized name
ls
# List for the files inside the folder. You should see a file called 'recovery.img' inside
fastboot devices
# Tell fastboot to check if any device on bootloader/fastboot mode is connected
fastboot flash recovery recovery.img
# Gives fastboot the instruction to flash the .img file to the desired device's partition, which is the recovery in this case
After done flashing, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Windows Method:​GUI Method:​
Simply use the "Latest ADB Launcher"executable located on the desktop of your PC;
Just make sure to flash the recovery partition with the "recovery.img" file;
Terminal Method:​
Navigate with the File Explorer;
Go to your Downloads folder and find for a file called "recovery.img";
Cut and paste it to where the ADB and Fastboot tools are installed at;
Click on your mouse's right button;
Select "Open terminal here" over the contextual menu;
A terminal should pop-up (Command Prompt, that is);
Type in the following:
Code:
fastboot devices
fastboot flash recovery recovery.img
Wait for the recovery to flash on the device;
After done so, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
------------------------------------------------------------
Installing Lineage OS 18.1:​Before proceeding, do the following firsthand:
Your device must be turned off;
Must have deleted the Android 9 Beta .zip file from the SDCard, for avoiding accidents;
Download the Lineage file off of the "required" list's links for your specific model;
Put the downloaded .zip file on an SDCard;
Insert the SDCard inside the device's slot;
Boot up into recovery mode;
Select with the volume keys "Apply Update" > "Apply from sdcard" and confirm with the power button;
Select the LineageOS .zip file;
Confirm with the power button;
Let the rom install by the recovery;
After install, navigate to the back button with the volume keys;
Select "Factory reset" > "Format cache partition";
The recovery will ask you the following:
Code:
Format Cache?
THIS CAN'T BE UNDONE!
Select "Yes";
Go back;
Select "Reboot system now";
First bootup will take some while, but you'll be greeted by the setup screen in no time.
Congratz, now your device has Lineage OS installed!
-------------------------------------------------------------------
Extras/FAQ Section:​Q: Is it possible to get root priviledges on the device?​A: Sure! There are different ways to apply root on the ROM, but feel free to pick whichever method you like:​
Rooting your device by picking it's 'boot.img' (exactly located on the folder of the respective model) over SebaUbuntu's Lineage site and patch it with an already-rooted device that has the Magisk companion app installed (requires no recovery patching, but it is required to boot the asus device in fastboot mode and patch the boot partition);​
Downloading the Magisk companion app over it's GitHub page, rename the .apk file by replacing '.apk' to '.zip' via file manager, patch PBRP over the recovery partition (with one of the methods listed over 2 titles above this one), and install the 'magisk.zip' file like you could usually do on any other device with custom recovery;​
If you use an X00I device, you can preferrably install TWRP from here instead of PBRP;​
After applied root on the device, patch back on the device the Lineage recovery- just for avoiding any inconvenience if you want to factory reset the device;​
Q: My device has Lineage installed, but the bottom buttons don't work. Is there a way to enable a virtual navbar?​A: Yep, but it's a bit of a tricky process. You must have either apps like Terminal Emulator or Termux installed for making this work- as an extra, you could get other keyboards like BeHe Keyboard or Hacker's Keyboard: but that is only if you've picked Terminal Emulator as your choice.​For direct instructions, follow this (you must be inside the terminal app of your choice and already gave storage perms to it firsthand):​
Code:
su
mount -o rw,remount /
vi /system/build.prop
# After come this far, go to the bottom of the build.prop file by scrolling with the touch screen
# On your keyboard, press the I key. This should make vi enter into INSERT mode
# When done so, add the following line on the build.prop file
qemu.hw.mainkeys=0
# For getting out of INSERT mode, find on your keyboard or terminal UI the ESC button
# For quitting and saving the file on vi, type the following
:wq!
# This should make vi quit and save the modifications to the build.prop file
# For rebooting the device straight from the terminal, just type in
reboot
# The device should immediately reboot, and upon unlocking: the virtual navbar should appear
Q: Can it be possible installing MicroG on the device?​A: You can! Every method for installing MicroG perfectly works on this ROM;​
Q: I have MicroG installed on my device, but i want to apply signature spoofing for extra functionality. Is this possible?​A: Sadly, due to the tinkering i've done on my side: the ROM gets a meltdown when modifying the 'services.jar' file is involved (root or non-root). If you follow some guides online (despite being few), the ROM, regardless of what you do or which method you follow: ​it will end up in a bootloop (or, to be more specific, the SystemUI starts to become picky);​
------------------------------------------------------------------
Credits:
miya0405 (for the lineage site)
SebaUbuntu (for the LOS rom, recovery, and PBRP recovery)
Erwin Abs (PBRP Recovery)
aaaaaaziskurnia (TWRP recovery for the X00I)
You, for dedicating your time on reading this long guide!

[GUIDE][ROOT] Unlocking and Improving Your Lenovo ThinkSmart View (CD-18781Y)

Improving Your Lenovo ThinkSmart View (Custom Recovery, Root, Play Store, Custom Webview)​Huge credit to @deadman96385 on how to flash your Lenovo Thinksmart View device and providing access to the firmware files! Credit to @WhyPartyPizza on reddit for the adb enable steps. And also, credit to @Xi07 on providing a way to install TWRP and demonstrating that it is possible to get the Play Store working. And also credit to @garnir4ik on showing us that we can root the device.
The point of this guide is to organize all the information we have on the device and provide a way to make the device more usable (especially since some of the software on the device is outdated).
The guide covers how to:
Install TWRP (optional) and Magisk (recommended) on the device
Install microG and the newest version of the Google Play Store (Magisk required)
Update Webview (needed for Home Assistant)
I'm still trying to figure out how exactly to do certain things on this device so feel free to leave any new information you find!
Installing TWRP (optional) and Magisk (required for Play Store)​Quick Blurb:​To install TWRP, you will need to flash new firmware onto your tablet. However, since there's currently no way to use the device with the bootloader unlocked, a lot of the features used in TWRP are unusable. It might still be good to install TWRP in case someone finds a way to modify the device to better utilize TWRP.​​To install Magisk, it will be much easier to do it by flashing new firmware. However, it is also possible to install Magisk without flashing new firmware. I will include the steps to do this below these.​Steps:​
Download and install the Qualcomm drivers from here
Download and install QPST from here
Download the firmware from this thread (Credit to @deadman96385). I used the 200628.084 version for reference.
Extract the firmware to a folder that you can easily access, like on your desktop.
If you want to install TWRP, download the recovery.img file attached to this post. (Credit to @Xi07)
Open the folder that you extracted the firmware to. In the image folder, replace the recovery.img file with the one you downloaded.
If you want to install Magisk, download the boot.img file attached to this post.
Open the folder that you extracted the firmware to. In the image folder replace the boot.img file with the one you downloaded.
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
If you get the dreaded "Sahara" error when flashing your device, you may be waiting too long to flash. The device must be flashed moments after it is booted into EDL mode (powering on with Vol + and Vol - held down). Once you plug in your device, hit download the moment the port is recognized at the top of QFIL.
You can also try disabling driver signing (I'm not sure if this makes a difference). To do so:
Spoiler: Expand Here
Open a command prompt as an Administrator.
Run
Code:
bcdedit /set testsigning on
and restart your device
Your computer should say it's in Test Mode (bottom right corner). To disable driver signing, follow the same steps but run
Code:
bcdedit /set testsigning off
instead.
Thanks to HowToGeek's article for the information.
From here, you can go ahead and follow the original method from @deadman96385 for breaking into the device.
Spoiler: Expand Here
When it boots up select Teams (Others seems to try and network boot/download files and fails)
Go through the setup wizard until you get to the Microsoft Teams (Language > Wifi > Bluetooth > Teams)
Select the Gear Icon in the top right of the teams page
Select the "About" settings option
Tap on "CD-18781Y.200628.084" under firmware version a bunch of times rapidly until a prompt comes up saying developer unlocked.
If your usb c cable is plugged, in unplug and replug it in.
You will now have ADB access.
Download your desired Launcher and use the following command to install it:
Code:
adb install APK_FILE_NAME.apk
You will then need to send this adb command to select a new default launcher:
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
I would recommend getting a navigation bar app. I've attached the one I used to this post.
You can also technically install Magisk without reflashing your device.
Spoiler: Expand Here
Install the Magisk app (use the Magisk APK)
Enable OEM unlocking in Developer Settings
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, execute
Code:
fastboot devices
to make sure the device is discovered. If a device is not listed, you may need to go into Device Manager > Other Devices > Android device with question mark. Right click > Update Drivers > Browse My Local Drivers > Let me pick from a list > Change to Fastboot Drivers.
Code:
fastboot oem unlock-go
This will unlock your bootloader.
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, navgiate to the directory where your Magisk boot.img is downloaded. Run
Code:
fastboot flash boot boot.img
After the boot.img is flashed, you need to lock your bootloader to be able to boot back into the device. If you're not in fastboot mode, you can once again unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
Run either of the 2 commands to lock the bootloader. You can restart the device and boot into the device once you are finished.
Code:
fastboot oem lockfastboot flashing lock
Steps for Google Play Store and Custom Webview will be in the next post (to reduce clutter).

Installing MicroG and the Newest Version of the Google Play Store (Magisk Required)​
Download and install the MicroG Services Core and Services Framework Proxy from the MicroG site.
Install the Magisk app (use the Magisk APK). When you open the app, it should say the version of Magisk installed next to "Installed."
On your Android Device go to Settings > Connected Devices > USB > File Transferring Mode.
Download the NanoDroid-patcher.zip file, BusyBox.zip, and terminal_systemizer.zip. Do not unzip these files. Drag and drop these devices onto your Android device.
In Magisk > Modules > Install from storage, find the .zip files and install all 3 Modules. The NanoDroid-patcher module in particular may take awhile so be patient.
Install the apk of Google Play Store of your choice.
Install Termux. In Termux, issue the command
Code:
su
A superuser popup should show up. Make sure to allow Termux Superuser access. If you miss clicking on it, you can allow access in the Magisk App > Superuser.
Code:
systemize
Follow the dialog prompts to systemize Google Play Store to /system/priv-app
Restart the device.
Open the microG settings app. Register the device in Google device registration. In Self-Check, click on each setting (the words, not the checkboxes) and enable them all. Pay particular attention to System spoofs signature being checked off.
Restart the device again if you want. Google Play Store should be working fine now (may need to clear it's App Data first if it's not working).
Installing Custom Webview (Magisk Required)​Some apps such as HomeAssistant won't function without an up to date System Webview. As this tablet is running a quite old version Webview version, this causes these apps to not work. Luckily, there's a Magisk Module to fix that.
Download the Webview_Manager zip file and drag and drop it onto your device. Install it using Magisk. You will need to watch it install as it requires some input on which Webviews you want to install.
After restarting the device, navigate into Settings > System > Developer options > Webview implementation. You should now be able to change your Webview to a updated version.
Note, you may need to unplug and replug in the device after the first restart of installing Webview.

Reserved 2

Chewie610 said:
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
Click to expand...
Click to collapse
A slightly easier way that may work I haven't validated on the thinksmart specifically is using qfil's partition manager tool. It allows you to dump, erase, flash individual partitions, that way you can flash just the one you want without having to deal with a full qfil flash. Finish all original steps up to 10. Instead of clicking download do the following instead:
Navigate to the top menu: Tools -> Partition Manager -> OK. If all goes well, you will be greeted with a dialog listing all partitions in ~5s. If this is not the case even after a full minute, try re-entering EDL/9008 mode.
Once the partition list is loaded, you can perform the following actions on partitions by right clicking a partition and then clicking 'Manage Partition Data'.
'Erase' (Clear the partition)
'Read Data...' (Dump the partition)
'Load Image...' (Flash the partition)
Click to expand...
Click to collapse
This is also a great way of backing up partitions from your device. The dumped partition can be found in C:\Users\%USERNAME%\AppData\Roaming\Qualcomm\QFIL\COMPORT_##. Note that the name of the file is the raw file locations so you will need to rename the imgs as you go.