Database Info

[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on

If you would like to S-OFF, Install ClockWork Recovery, permanently Root & obtain SuperCID. Follow Steps 1 to 4!
To Debrand or flash an official stock ROM only: follow Steps 1 & 4 only (you may skip step 3 & 4 is you do not need them)
To Root: follow steps 1-3
To install a custom ROM for the first time: Steps 1 & 2 then follow the guide below on how to install a custom Rom (step 3 isn't needed as customs roms are already rooted)
CLICK HERE FOR [GUIDE] TO UNLOCK YOUR SENSATION FREE - WORKING FOR EVERY SENSATION (noobproof) Steps 1-3 Needed! or Steps 1 & 2 plus custom ROM
UPDATE: NEW Recovery 5.0.0.8 - Follow Step 2 below to download and install. you do not need to follow the rest of the steps if you are just updating CWM
For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root
FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION
Whether your a noob or not, it nice to see a step by step guide as S-off is developer preview only and doesn't come with much instructions. I have simply Collaborated what is out there into one easy thread. Nothing complex.
here is my very small simple detailed guide. I have put a lot of Time and effort to make sure everyone can benefit so Just push Thanks if it helped
Click here for TROUBLESHOOTING OR FAQ
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit http://revolutionary.io/
download the application for your operating System. AND EXTRACT IT TO A FOLDER
YOU MAY NEED TO DISABLE YOUR ANTIVIRUS PROGRAM- Norton is flagging up Revolutionary as a Virus when it isn't
IMPORTANT
Fill out the form under the download links with your OS, Device, Hboot Version and Serial number. This will give your beta key to enable you to S - OFF. Make a note of this.
How To get your Hboot Version - 3 methods below
1. Run the revolutionary Utility you just downloaded from http://revolutionary.io/ and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
4. With the phone switched on (not in HBOOT, just the regular home screen), plug in your USB cable and select HTC sync mode.(IGNORE any warning messages on your phone telling you it cannot find HTC Sync )
5. Launch revolutionary.exe. It should detect the phone and ask for your beta key. Type it (BE CAREFUL, as its case sensitive) or copy and paste it in.
If Revolutionary fails to find your phone verify you have all the drivers installed, try disk drive mode or charging mode (Linux users can use disk drive mode. Confirmed to be working by others)
6. Once you have entered your beta key correctly, follow any on screen prompts or actions from revolutionary and wait for it to S-Off,
7. You're done. Your Device will Successfully have S-OFF....if it hangs on method 3 and doesn't S-Off. See post 2 below for solutions.
IF REVOLUTIONARY SAYS FAILED YOUR PHONE IS NOT SUPPORTED. Go back and check hboot using the methods above. some users are told its failed and they still have S off now. If you have S-off your hboot will now be 1.17.1011 and revolutionary will tell you now your device is not supported
8. Revolutionary will now ask you to Install clockwork recovery mod after S OFF. Type N and install it manually below (the recovery provided is v4.0.1.4 doesn't charge when device is switched off, the one below v5.0.0.1 does charge)
9. Your Device now is S-off.
To install clockwork recovery for the sensation. Follow step 2!
STEP 2. To INSTALL Recovery - v5.0.0.8
1. Download recovery v5.0.0.8 for the Sensation [URL="http://forum.xda-developers.com/showthread.php?t=1277975"]HERE:[/URL] or Multiupload
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
6. Delete PG58IMG from your memory card and you can now root using step 3 below or install a custom ROM using CWM (Customs Roms are already rooted)
7. OPTIONAL: Boot into recovery or Completely switch off (Fastboot disabled or remove and reinsert battery)
Follow STEP 4 SUPER CID sub steps 1-6 to get adb running
8. Enter the command "adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status" Phone will confirm it is "CHARGING"
Charging issues fixed with new clockwork recovery. writing is now BLUE not purple or orange
Step 3. To permanently root your Sensation - (This means you will NOT LOSE ROOT on rebooting)
1. Download the file su-2.3.6.3-ef-signed.zip from here: DOWNLOAD
2. Copy su-2.3.6.3-ef-signed.zip to your SD card root folder (main folder of your memory card)
3. Start clockworkmod recovery (instructions below. See To Start Clockwork recovery)
4. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT!
5. Navigate to "Backup & Restore" using the Volume Down button and press select (power button to select) then select "Backup"
6. Select "install zip from sdcard" after backing up
7. Then select "Choose zip from sdcard"
8. Then select "su-2.3.6.3-efgh-signed.zip"
9. Then select "Yes - install su-2.3.6.3-efgh-signed.zip" to confirm
10. Then go back
11. Then reboot.
12. You're rooted!
If you are getting error messages regarding S-OFF, Rooting or installation - Troubleshoot below in post 2
See POST 2(HERE):
STEP 4. WRITE SUPER CID [YOU ONLY NEED TO DO THIS ONCE]- (continue from step 11 below if you have already done this)
(allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE)
1. Download adb tools here: download for WINDOWS or download for LINUX or from the attachments below
2. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
{
"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"
}
4. open command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
5. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings)
6. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
7. enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
IF it doesn't you can Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
8. enter the command "fastboot oem writecid 11111111"
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
11. enter the command "fastboot reboot"
12. You can now flash any ROM you like.
To reinstall any stock ROM after this or De-brand or reinstall a different type of Rom (European, Asian, US).
Just click here to download an Official Rom,
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
TO DE-BRAND OR REINSTALL STOCK ROM (Changes to Stock S-off, Removes Root and clockwork)
Reinstall your original stock ROM you had (e.g Vodafone, Tmous, Asian, European unbranded etc. if you are changing back to S-ON)
1. Backup all User Data and Apps (Titanium backup Recommended) SKIP THIS STEP IF YOU WANT TO WIPE EVERYTHING
2. Use the SUPERCID method above. (Confirmed to work)
3. If you cannot get superCID to work. Follow this by Alexp999. HERE: any problems PM ME and i will help
Your phone bootloader will read "PYRAMID PVT SHIP S-OFF RL" after this, Root and clockwork will have been removed now
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
You should now have S-on back and you can return your device or do whatever it is covered again under warranty.
10. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
11. Run RUU_Pyramid_***.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
The above method works successfully. So do not under any circumstances try this without going back to stock first using Ruu.exe. and Follow the instructions correctly if you want S-on WITHOUT problems Any doubts or questions PM me and i will get back to you and help you.
Donations welcome as i had a very shaky night experimenting and bricking my device (and having a panic attack over it) to find a safe method for successfully getting S-on back for all you out there complaining about warranty.
To Start Clockwork recovery
1. EITHER make sure fastboot is disabled in settings and shut down your phone
This can be done via Settings > Power> Untick "FAST BOOT" at the bottom.
OR take out your battery and put it back in. (this is easier)
2. Keep hold of the volume down button and switch your phone on.
3. Hboot will start. Navigate to recovery with the vol down button. Press power button to select and enter recovery.
To install a Custom ROM - you will not lose data or apps with this method!
1. Download your chosen ROM by other developers in the development threads and copy the ZIP file to your SD Card ROOT directory
2. Start clockworkmod recovery (instructions above)
3. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT! (skip this step if you have already made a backup previously)
4. Navigate to "install zip from sdcard" using the Volume Down button and press select (power button to select)
5. Then select "Choose zip from sdcard"
6. Then select "your_chosen_rom.zip"
7. Then select "Yes - install your_chosen_rom.zip" to confirm
8. Then go back
9. Then reboot.
10. First boot will take quite some time -This is normal, i know you want touch your nice shiny phone but BE PATIENT - ENJOY!
Special Thanks to AlphaRev, unrEVOked Team, Bin4ry & to everyone else that helped with this GUIDE and with S-off and Dazweeja with S-on

TroubleShooting!
signature verification failed in CLOCKWORK
Make sure you have installed Clockwork From Step 2 Above. V 4.0.1.4 specifically for AlphaRevX
1. Load up Clockwork Recovery (See post 1)
2. Navigate and Select "install Zip from SD Card"
3. Select "Toggle Signature Verification". Press it once or twice till you see the message. "Signature Check: DISABLED"
Installation aborted in Clockwork
E:Error in /sdcard/su-2.3.6.3-efgh-signed.zip
(status 0)
Installation Aborted
1. First Try the above method of repeating it 3 times to achieve root. some users are getting installation aborted. but on third attempt rooted successfully
2. Failing that: Download su-2.3.6.1-ef-signed.zip AND su-2.3.6.3-efgh-signed.zip.
3. Place both of them on the root (main folder) of your sd card and flash su-2.3.6.1-ef-signed.zip using Step 3 from post 1. it is likely it may repeat the error above. INSTALLATION ABORTED
4. Flash su-2.3.6.3-efgh-signed.zip now using step 3 in post 1. YOU SHOULD BE NOW ROOTED!
Stuck on White Screen with Green HTC Letters for over 15 minutes or continuously rebooting without starting up
You are not bricked, Whatever you flashed in clockwork didn't flash correctly. Most likely a Rom
This could be due to a bad file, or download error or powering off or pulling the battery part way through. no need to worry
1. Re-download the Rom or file or theme you were trying to flash in clockwork
2. Install again using clockwork. wait till its finished and reboot. you should be cured
3. MAKE sure whatever you are flashing is compatible with the Sensation or made for the Sensation
Revolutionary Hanging on "Method 3"
1. Make sure you have installed all the drivers from above.
2. Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
3. Install These Drivers HERE:
4. Basically anything and everything that will allow your phone or other phones to automatically connect or sync to your computer has to be uninstalled
5. Try another Computer or Factory Reset your device as a last resort.
If you are getting root error messages
Some Users acheived root by repeating Step 3 a few times Try this
1. Repeat step 3 at least 3 times or until it installs completely .
2. Download busy box from the market , open it and install the app.
3. Reboot and that should do it , root should be working and WiFi with s off
4. You may get messages telling you it failed to root or installation aborted but reboot and check it with root checker. Many users are told its failed but are actually rooted now
If u want to verify if u have root download the app called root checker it checks for root and for busy box to b installed correctly... if that fails
Try Installing/REINSTALLING SuperUSER and Busybox (or busybox installer) from the market. if it still doesn't work then
Flash a custom Rom as they come Pre-Rooted
Many Tmous users are acheiving root while a few are not. please try all of the above mentioned methods.
Titanium Backup Crashing (when restoring backup)
1. Uninstall and reinstall Titanium backup
2. If that fails reinstall your ROM (Full wipe recommended in clockwork before reflashing rom. Unless you have already made a backup with titanium before. you will lose apps + data)
Titanium Backup not working
The likely Cause of this could there are some files left behind from your temp root. You need to delete the files in /data/bin/ you can do this by
Download Terminal Emulator from the market
open terminal emulator and type:
su
rm -r /data/bin/*
or if you are familiar with using adb: (you can use the adb exe supplied by revolutionary in his tools pack)
adb shell su
adb shell rm -r /data/bin/*
Then reboot into recovery and reapply the su-2.3.6.3-efgh-signed.zip installation. Another User posted this fix as it worked for them
WIFI PROBLEMS (ISOLATED INCIDENTs)
IF YOU ARE EXPERIENCING WIFI ERROR.
Currently the only way to fix this is to flash Stock Rom again or Custom Rom.
1. Follow step 4 above in post 1
2. OR You can flash a custom Rom from Clockwork. LeeDroids Rom is close to Stock and confirmed to be working on a Tmous Sensation
Any problems or fixes PM me please

[GUIDE] TO UNLOCK YOUR SENSATION FREE - WORKING FOR EVERY SENSATION (noobproof)
Method 1 was discovered by a noob - Dav22. Dazweeja came up with a simple ADB command. Skygear for working it in Terminal Emulator
Method 2 was discovered by sieempi (Links at the bottom), STRING: NOT FOUND workaround found by jackmonter5
Big thanks to xplod4202. Risked his Sensation to see if Methd 2 was safe for us all.
And The simple guide : xl Viper lx : I am simply doing what i do best. getting you a noobproof guide and also simplifying the adb/terminal code
All of us will take credit for the collaborating and making of this thread to help everyone unlock with no cost. What???.....Yes thats right......We broke the FTSE index by providing free unlocks! lol
Also 9 people who voted no in the poll, ad voted before we found method 2 which unlocks every sensation
METHOD 1 - USE THIS FIRST
The SIM-Unlock code location for some sensation's (NOT ALL) has been found and confirmed to work for the few users who tested it. Use method 1 below to find your unlock code
(Method 1 ADB guide in post 2 if you don't want to use Terminal Emulator or you just want to use ADB)
Requirements:
-Rooted simlocked Sensation - Enable USB debugging in Settings > Application ->Development
-Terminal Emulator (Download free from the market) or click here to download and install into your phone
Your IMEI Number (Dial "*#06#" in phone keypad to get it)
GUIDE - Method 1
1. Download Terminal Emulator from the market if you havent already done so and Run it. This should bring you a blue screen. Full screen.
2. enter the command "SU".
3. Click allow when Super user pop up appears to give it root access. (If your keyboard disappears, keep hold of menu button to bring it back up)
4. enter the command "strings -n 8 /dev/block/mmcblk0p6"
5. This should give Output a bunch of numbers like in the screenshot! IF IT SAYS STRING: NOT FOUND MOVE TO POST 2 AND USE ADB!
6. The 8 digit number above your IMEI number is your unlock code. See post 2 on how to enter it.
IF it only brings you a date above your IMEI. Then the unlock code is not present in your device. Move to Method 2
GUIDE - Method 2 - USE IF METHOD 1 FAILED!
Revolutionary achieved radio S-OFF for Sensation (among other devices) which means you can practically do whatever you want with your phone (like actually owning it). This means it makes it vulnerable to all sorts of schemes including sim-unlock. The following method is quite efficient and easy to do and can be done with the need for a computer!
Requirements:
-Rooted simlocked Sensation!
-Clockwork Recovery or Revolutionary Recovery - NEEDED FOR NANDROID BACKUP
-Titanium Backup (Download from the market if you don't have it) - YOU ONLY NEED THIS IF YOU DONT WANT TO OR CAN'T NANDROID BACKUP
WARNING!!!
Backup all your settings/apps/sms/network/APN/Data etc.
Using this method to unlock will wipe your data and apps too! (Factory Resets in other words)
But it's this method that actually resets some other things including your sim-lock status.
Guide - Method 2
1. MAKE A NANDROID BACKUP USING RECOVERY - (Completely switch off your phone, Press Volume down + Power button to get into bootloader, Volume down to recovery then press power button to get into Recovery. Volume down to "Backup and Restore" in recovery. Press Power to backup and your done!
(Make a backup in Titanium backup if you don't want to or can't nandroid backup. Menu > BAtch >Backup systems data + Apps with data)
2. Download PG58DIAG for the Sensation HERE or FROM MULTIUPLOAD
3. Copy the PG58DIAG file into the Root folder of your SD card (The main Folder of your Memory Card)
4. Turn off your phone Fully and reboot into the Bootloader/HBOOT screen (see post 2 on how to get to bootloader screen)
5. Press Volume Down to Enter DIAG - Place the phone horizontally when it asks you too. (Flat)
6. Press power button to select "Clean S58 Data
7. Press power again to "clean S58 Data".
8. POW - your unlocked! Try a SIM card from a different provider!
9. Delete the file from your SD Card (Delete PG58DIAG) and REBOOT!!
Your phone Will set up for the first time, go through it all till you get to your home screen
10. Go back into recovery and restore nandroid backup. same method as step 1 above. but instead of backup, you use restore feature
(Use Titanium Backup to restore if you used it to backup instead of Nandroid backup)(Menu > Batch > Restore System Data + Apps with user data)
Now you’re free to go! Bear in mind, though, in certain circumstances you will lose your data connectivity or network signal. You’ll just need to check your APN, network type etc. and re-enter them; Just run the nandroid restore to get everything back
Thanks to Dav22. for discovery of method 1
Dazweeja for his simple Code to find the unlock
sieempi for Method 2.
Thanks to Team Revolutionary for PG58DIAG and S-off
Don't forget to CLICK THANKS, VOTE and RATE if this guide worked for you.
don't forget to thank the above users too by clicking the links

Method 1 ADB GUIDE
METHOD 1 - ADB GUIDE- Skip steps 1 to 5! if you already have already got ADB and can get to the ADB folder through command prompt/Terminal. If your not sure follow all the steps
1. Download adb tools here: download for Windows or Linux or from attachments in the Sensation S-off guide
2. On your PC click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
4. open command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
5.a Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings) OR!!!!
[ IF YOU GOT THE STRING:NOT FOUND ERROR IN METHOD 1 (terminal Emulator) REBOOT INTO RECOVERY AND CONNECT YOUR USB AND CONTINUE (Turn off your phone completely, volume down + power button, then select recovery to get into it!) ]
6. enter the command "adb shell". Your phone should display a hash sign [#] (if it doesn't then you are not rooted! - GO ROOT)
7. enter the command "SU".
8. enter the command "strings -n 8 /dev/block/mmcblk0p6"
9. This should output a bunch of details as shown in the screenshot below
10. The 8 digit number above your IMEI is your unlock code. See post 2 on how to enter it. IF it only brings you a date and your IMEI. Then the unlock code is not present in your device. Move to Method 2 in Post 1
To unlock your GSM phone with the unlock code follow these simple steps:
1. Power on your Sensation with a SIM card from an unsupported network/carrier/provider.
2. If asked, enter the PIN code of your SIM Card.
3. Enter unlock code when prompted!
FOR DUAL CDMA
How to enter the code in dual CDMA - GSM/LTE HTC Phones
1. Power on your Sensation with a SIM card from an unsupported network/carrier/provider.
2. Phone will tell you to insert an allowed SIM card and that the phone will switch back to CDMA mode.
3. Click OK.
4. Click green button to get to the main screen of the phone.
5. Click on settings.
6. Click on all settings.
7. In the personal tab click on security.
8. The phone will ask you to enter the unlock code. Enter it. Done

FAQ - Frequently Asked Questions
Recovery Charging Issue
Clockwork recovery v4.0.1.4 with the purple writing suplied by revolutionary and 4.1.0.5 from rom manager both have an issue with charging. Your phone will not charge if you turn it off.
So if you flashed it via revolutionary.exe or in post one before i before i uploaded the new updated one.
Post one is now updated with the new clockwork recovery 4.0.1.4 with the blue writing that does not have charging issues.
Just follow Step 2 above to flash the new clockwork Recovery v4.0.1.4 and this will fix your charging issues.
the new recovery is orange while the old one was purple
What is a noob?
A noob is someone new to XDA or new to the device and its methods of rooting/customizing. Its not bad being a noob. we we're all their at one stage. i was a noob for winmo in July 2009. I was a noob for Android in October 2010. you tend to learn everything pretty fast. easy to work with android is.
What is S-OFF?
S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC devices is S-ON (write protected), which means that neither can you access certain areas of the system nor can you guarantee a permanent root
Do i need Rooting?
An unrooted device is like logging onto the guest account of windows, you can do many things, just not everything
Think of Acquiring root as having Administrator Access on the device, so you can install/modify/fix/break anything you want.
What does clockwork Recovery do?
Clockwork allows you to flash Unofficial Roms and Themes via zip files on your SD card, also you can make backups of your current rom and wipe certain types of memory. (User data, system, boot, cache, dalvik cache)
What is flashing? (showing your bits off in public?) NO!
Flashing refers to Downloading themes or apps or Roms onto your SD Card and then installing them using clockwork or any other utility where the phones Operating System is modified

the program sees my phone but my beta key isn't working.

leyvatron said:
the program sees my phone but my beta key isn't working.
Click to expand...
Click to collapse
Fill out the form again correctly and copy paste doesnt work so you gotta make sure you type it letter for letter, it is case sensitive

leyvatron said:
the program sees my phone but my beta key isn't working.
Click to expand...
Click to collapse
its Case-Sensitive

thanks a lot for the guide. i was confused about one thing. you say, "To get your Hboot Version, make sure fastboot is disabled". where exactly do we make sure that fastboot is disabled? is that a setting in android? i thought it had to do with recovery... thanks again!

greves1 said:
thanks a lot for the guide. i was confused about one thing. you say, "To get your Hboot Version, make sure fastboot is disabled". where exactly do we make sure that fastboot is disabled? is that a setting in android? i thought it had to do with recovery... thanks again!
Click to expand...
Click to collapse
its when your turn off your phone and turn it back on, its comes on within seconds,
i have fastboot enabled but the easiest way possible mate is just take out the battery and put it back in, that way you will know definitely its off, not on hibernated

Thanks for the guide!
Just got S-OFF on my phone and installed ClockworkMod

Psyed said:
Thanks for the guide!
Just got S-OFF on my phone and installed ClockworkMod
Click to expand...
Click to collapse
Me too. going to try and flash Leedroid in half an hour
Glad it helped you too, orignally i booted into fastboot and was wondering why it wouldnt recognise my phone till i saw instructions buried in the long thread, rather than people sifting through it, i thought its better if i make it into its own thread

sundar_amn said:
Will this work on T-Mobile US Sensation?
Click to expand...
Click to collapse

ikhzter said:
Me too. going to try and flash Leedroid in half an hour
Glad it helped you too. dont know what Mgormans problem was, orignally i booted into fastboot and was wondering why it wouldnt recognise my phone till i saw instructions buried in the long thread, rather than people sifting through it, i thought its better if i make it into its own thread
Click to expand...
Click to collapse
Too late to flash a rom right now. I'll fix then after waking up... whenever later on today

I had no problem using copy paste ind the command prompt.
My windows is not in english but I think it is something like this in a english windows:
push the cmd icon at the top on the cmd running, edit > paste
/henrik

henhoy said:
I had no problem using copy paste ind the command prompt.
My windows is not in english but I think it is something like this in a english windows:
push the cmd icon at the top on the cmd running, edit > paste
/henrik
Click to expand...
Click to collapse
oh yeh i forgot you could do that, what can i say, too excited about S-OFF

AWESOME !!!!!!!!!!!!!!!!!!!
Yessssssssssssssssssssssssssssssssssssssssssssssssssssss !!!!!!!!!!!!!!!!!! I love youuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

my revolutionary.exe is stuck on: acquiring root (method 3)...
This comes up after i put in the beta key, it says accepted.
i do have usb debugging on, on put it on htc sync
i have an .0011 hboot so it supported, whats the problem?

shatred said:
my revolutionary.exe is stuck on: acquiring root (method 3)...
This comes up after i put in the beta key, it says accepted.
i do have usb debugging on, on put it on htc sync
i have an .0011 hboot so it supported, whats the problem?
Click to expand...
Click to collapse
you have usb debuging enabled???
i have the same version of bootloader and for me it stucks at "waiting for fastboot"
undplug and plug phone, while in fastboot doesnt help, driver is also installed correctly! Anybody knows a solution for that?

Phily757 said:
you have usb debuging enabled???
i have the same version of bootloader and for me it stucks at "waiting for fastboot"
undplug and plug phone, while in fastboot doesnt help, driver is also installed correctly! Anybody knows a solution for that?
Click to expand...
Click to collapse
but when i select it seeks my computer for htc sync, but i uninstalled it like the first post said it needed to. so after about 20 seconds it says that htc sync cannot be found on my computer. is this a good sign?..

Xoom root and bootloader unlock

I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).

wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?

Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.

RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.

Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?

llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted

TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)

llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?

TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me

I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?

madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.

Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!

Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?

do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.

factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!

madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5

sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).

madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge

Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!

madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"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"
}

Nextbook Ares 8A with Android 6.0.1 root solutions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Pioneer XDP-300R Digital Audio Player - Root, TWRP Recovery, and Mods

{
"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've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true

Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)

HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?

A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.

Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.

Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.

HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel

gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?

I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel

Grazie mille per il tuo lavoro

gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP

Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?

Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model

Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help