Hello,
First off, I'd like to apologize for putting this in the "General" section, as I am new, I cannot post in the development related sections.
So, I have compiled a all in one package for rooting your HTC One, this kit includes fastboot, drivers, recoveries, SuperSU, and anything else you will need to root your device (there is a full list below). I have compiled some pretty detailed instructions and will post them in the second post.
INCLUDED FILES:
Fastboot
adb
Clockwork Mod Touch 6.3.something
TWRP 2.5.0
SuperSU (recovery flashable)
Disable Write Protection (recovery flashable)
Drivers (32 and 64 bit)
Stock Boot Image and Recovery
INSTRUCTIONS-
Download Latest:adf . ly/O7zCG
Past Releases:
None Now, this is 1.0!
Notes:
By downloading this you are placing the full responsibility on yourself for anything that happens to your sexy new phone, unless it starts shooting lasers and destroying iDevices, then, the Credit is mine
This works on both Windows and Mac OSX
If you make a video or blog post etc get my permission BEFORE
ENJOY!!!
Instructions
Kwongger's Sprint HTC One All-In-One Pack
1. Create an account at HTC DEV
2. Unlock using the HTC Dev instructions (below) (select "all other supported devices" at start)
3. Flash A recovery using the below instructions
4. Either Flash the SuperSU zip (stock rooted) or the rom of Your Choice (both IN RECOVERY)
NOTE:
I will soon post a detailed YouTube video (in 2 weeks or so when I get my One!)
on youtube com /user/ kwongger
HTC unlock method instructions:
Just So you know, these are directly from htc, all credit to them!
Step 1: Remove and reinsert the battery then proceed to step 2. For devices without a removable battery, long press the power key then select restart. Hold down the volume down key while restarting to start the device in Bootloader mode.
Step 2: Press Volume Down and Power to start the device into Bootloader mode.
Step 3: Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 4: Connect the device to the computer via a usb cable
Step 5: Isn't needed
Step 6: Open a command prompt in the directory by pressing shift, right clicking, and selecting open command prompt window here
Step 7: Navigate to where you unzipped the ZIP file and go to the folder you just created (see step 6 above)
Step 8: Type in Command Prompt: fastboot oem get_identifier_token
Step 9: You will see a long block of text. Copy and paste into the token box on HTC DEV.
You should get this:
Token Submitted Successfully!
You've been sent an email with your unlock key as a file attachment. Please review this email for further instructions and a link to complete the Bootloader process.
Leave your cmd window open you will need it after you get your Unlock_code.bin in the e-mail.
You can place the Unlock_code.bin in your Root folder and follow the instructions from the e-mail.
NOW: boot to the bootloader and select fastboot
Installing TWRP
Now type "fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img" without the quotes and press enter
Now type "fastboot erase cache" without the quotes and press enter
This will install custom TWRP recovery on your phone so you can start flashing custom ROMs.
Installing CWM v6.0.3.1
Turn phone completely off
Boot into HBOOT>Fastboot
Use command "fastboot flash recovery recovery-clockwork-6.0.3.1-m7wls.img" without the quotes or
"fastboot flash recovery recovery-clockwork-touch-6.0.3.1-m7wls.img" also without the quotes
AFTER FLASHING RECOVERY
1. Boot to your recovery and flash the rom of your choice.
~or~
Boot to your recovery and flash the SuperSU zip.
2. Flash the Disable Write Protection zip (will allow you to replace/edit system files)
Frequently Asked Questions
FAQ
Will this work on (insert alternate Htc One carrier here)?
Most likely not, give it a shot though! Remember I am not responsible for anything that happens to your device.
Can I return to stock?
Yeah, just flash the stock stuff through fastboot and relock your boot loader.
Will this void my warranty?
If you really have this question you don't belong on these forums... YES htc even told you themselves when you started the bootloader unlock process
My phone won't boot.
Well you did something wrong, return to stock using the above instructions and then try again.
I am closing this thread because it has information which this thread already has in more detail.
It's best not to have a plethora of the same thread.
Thanks
This is a "re-tread" of a post I previously made, taking an account of the steps I took to successfully update my Nexus 7 from 4.4.4 to 5.0. Note: This is for an unlocked bootloader, if you don't have an unlocked bootloader you will lose your data; consider TiBackup.
My Nexus 7 [WiFi] was rooted on 4.4.4, unlocked bootloader, but stock rom, stock system (as far as I remember). I couldn't find a walkthrough so I'll make one with my experience. This worked for me on my Mac, I hope this helps you.
In the end I didn't lose any data, still have unlocked bootloader and rooted with CWM Recovery & SuperSU (you can replace with TWRP recovery or CWM Touch if desired)
Directions ("./" = file path to platform-tools folder, if you 'cd' to that location the "./" will pull that location in the terminal)
1. You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html.
2. UNZIP and you will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
3. Download the factory images 4.4 (KRT16S) (4.4 required, see HERE, Google broke its own bootloader) and 5.0 (LRX21P) for your Nexus 7: https://developers.google.com/android/nexus/images#nakasi (WARNING: Download the correct images for YOUR device, Nexus 7 Wi-Fi vs Mobile)
4. Unzip the 4.4 image file you downloaded and copy "bootloader-grouper-4.23.img" (img name depends on your build) to your "platform-tools" folder (where adb and fastboot are). (WARNING: the bootloader image in 5.0 is broken see HERE)
5. Unzip the 5.0 image file you downloaded and copy all content, except for "bootloader-grouper-4.23.img," to your "platform-tools" folder (where adb and fastboot are).
6. Plug your Nexus 7 into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate "Developer Options" menu where you will be able to activate "USB debugging")
7. Open terminal and "cd" to the platform-tools folder
8. Verify ADB is working type "./adb devices"
9. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
10. Type:
"./fastboot flash bootloader ./bootloader-grouper-4.23.img" (img name depends on your build)
11. If you have "WiFi Only" skip to step 12; for Mobile flash radio type:
"./fastboot reboot-bootloader"
"./fastboot flash radio ./radio-XXXXXXXX.img" (img name depends on your build)
12. Type:
"./fastboot reboot-bootloader"
"./fastboot update ./image-nakasi-lrx21p.zip" (zip name depends on your build)
It will then reboot (takes a while, 5-10 minutes on boot animation, then it must update App info, another 5-10 miuntes) and then you will be in Android 5.0 with all your data preserved.
Then if you want a custom recovery:
1. On your computer, download CWM, CWM Touch, or TWRP recovery from here: CWM Dwnld or TWRP Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Place the image file you downloaded in your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. In the terminal type:
"./fastboot flash recovery ./FILENAME.img" (replace FILENAME.img by the file name of the CWM/TWRP file you just downloaded)
5. Verify Recovery - Shut down your device and boot it into recovery mode (Once off, push vol- and power together). Choose recovery mode with vol-, then power to select (Note: if you get an Android on his back you still have stock recovery, retry Steps 1-4. I flashed CWM, CWM Touch. and TWRP with no success, plugged my cable into a different USB port and got it first try; try different cables and ports)
Then if you want a root:
Note: If you don't have an unlocked bootloader you will lose data. Already unlocked should be fine, when you boot there should be an open lock at the bottom of the screen below the Google logo. On PC WugFresh Nexus Root Toolkit might be your best option, for me on Mac it is not available so this is what I did.
1. On your computer, download CF-Auto-Root from here: Auto Root Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Unzip the CF-Auto-Root file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. Type: (Note: Step 4 commands need to be run as Admin)
"chmod +x root-mac.sh"
"ls -al"
"./root-mac.sh"
5. Follow on-screen prompt and type your Mac User Account password and ENTER
6. Let the phone go through its thing (Red Android screen), it will reboot when complete.
That is it!
Thanks to Phil Tech: http://youtu.be/IPg_FGbeyq0
Thanks to jipi: http://forum.xda-developers.com/showthread.php?t=2377691
Good luck and happy flashing.
Thanks for the effort.
Thanks ! I did that, more or less adapted. The result was just awefully slow, so I had to do a wipe to start with a clean slate.
Android, the new Windows: reinstall every 6 months....
I've followed the procedure on w8.1 64bit.
All went well but I lost adb after 5.0 finally booted. So I could not install root through NRT (1.9.8).
Adb mode was recognised in windows device manager but adb commands failed with no device found.
Suprisingly fastboot was working.
The solution was to uninstall NRT and adb drivers and reinstall them.
Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.
dg170775 said:
Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.
Click to expand...
Click to collapse
True, I was already on 4.23, but still flashed it anyways. Thanks for the input.
Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.
Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!
Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!
Reserved for Mac instructions.
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.
Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.
Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).
tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...
@tennear
As far as u know TWRP is the same for every A7, sign or not.
DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?
nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.
I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.
The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.
Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti
IMPORTANT NOTE ABOUT ROOTING:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting.
REQUIREMENTS
1- Unlocked Bootloader (search on google if you dont know how to unlock)
2- Drivers and Adb/Fastboot commands knowledge
--------------------------------------------------------------------------------------------------------------------------------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
Bugs:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the serial number folder seems to change (which means that on /TWRP/BACKUPS/serialnumber/backupsinside/ changes every reboot so you have to go get the backup inside the old serialnumber folder and put on the new serialnumber folder).
Im leaving an unsecured boot image because system does not boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
Steps to Install TWRP and root
1. Download and extrct the files: https : // drive. google . com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip ---
Continuation 6. Step by Step of Step 6 since people seem to have been running into issues with it:
After rebooting to TWRP and having SuperSU.zip in the tablet storage. Go on Install tab and press the supersu file and install/flash it then reboot the device.
thanks to yahoo mike for solving the problem with the TWRP not working, you're a saint!
due to the fact that i want to prevent the painful process of trying to find out which twrp works for TB-X605L_S210224_200910_ROW, i will have to point it out to those who have the kind of firmware installed on their Lenovo Tab M10 and try to use TWRP version higher than 4.0 and it doesnt work - TWRP will never work, but there's still a way out for people who want root:
THE MAGISK BOOT.IMG METHOD IN THE FLESH FOR PEOPLE WHOSE TABLETS CANT GET ROOTED THE TWRP WAY!
Disclaimer: the boot.img file which was patched by magisk only works with TB-X605L_S210224_200910_ROW
For other versions you have to use LMSA to snatch the firmware and get the specific files.
This method also works on TB-X605X - same LMSA procedure, same result.
what will you need:
the first and important one - knowledge that i dont care if you couldnt use your 2 brain cells to follow the steps and proceed to brick the device by slapping a boot image on a recovery one and the fact that if you havent started the process yet your data (if theyre not backed up) will be WIPED
Click to expand...
Click to collapse
2 - a tablet, obviously (common sense)
3 - a computer
4 - Android SDK platform tools
5 - boot.img with magisk installed on it
6 (optional) - If you have no ramdisk, LMSA to at least get the recovery.img file
THE STEPS:
if you havent started the rooting process yet:
Spoiler
Code:
1 - Go to device details and tap the serial number 7 times, dev mode should activate
2 - Go to dev settings and activate OEM unlocking and USB debugging
3 - On your computer you should have downloaded SDK platform tools, extract in C:/
4 - Afterwards get into the platform-tools folder, click the path line and type CMD
5 - Type adb devices to see if it installed correctly, your device should appear
6 - Type adb reboot bootloader, wait until the device reboots, you should see FASTBOOT MODE in red text
7 (LAST CHANCE TO BACK UP YOUR FILES, IF YOU PROCEED YOUR UNBACKED DATA WILL BE PERMANENTLY WIPED) - Type this: fastboot oem unlock-go
8 - type fastboot reboot
YOU MAY PROCEED TO THE ROOTING PROCESS PART 2.
If you already unlocked OEM (ROOTING PROCESS PART 2):
1 - Go on your device and download Magisk Manager (Version is 23.0)
2 - install the APK file
3 - open magisk manager and check the ramdisk
We will look at 2 situations:
Yay! Ramdisk is checked as Yes! The process will be hassle free and you wont have to use LMSA to get the firmware!:
Spoiler
Code:
1 - On your computer put the modified boot.img file into the platform-tools folder (Dont worry, it doesnt bite)
2 - Move on to the CMD prompt and enter: adb reboot bootloader
3 - then type in: fastboot flash boot (THE FILE)
4 - after that reboot your device by typing in: fastboot reboot
5 - HURRAH! Now you have installed root using the boot method AND without TWRP! Its best to check it with root checker for best measure though.
OH HELL NAH! IN THIS RARE CIRCUMSTANCE YOUR RAMDISK IS LITERALLY NONEXISTANT AS CONFIRMED BY THE CHECKED NO! HERE'S THE HARD WAY:
Spoiler
Code:
1 - If not already, download LMSA (or just search on the internet lul)
2 - Install LMSA and make sure you have connected your device to the computer
3 - Go to the Rescue tab and download the Firmware
4 - the path should be C:\ProgramData\LMSA\Download\RomFiles\TB-X605L_S210224_200910_ROW, you should see recovery.img
5 - snatch it and then place it into the download folder of your device
6 - use magisk manager to install magisk on the recovery image (MAKE SURE TO CHECK RECOVERY MODE IN MAGISK MANAGER OPTIONS, IT MUST BE CHECKED!!!!)
7 - snatch it by typing the command into the command prompt: adb pull /sdcard/Download/magisk_patched_[random_strings].img
8 - boot your device into bootloader with this: adb reboot bootloader
9 - now flash it into recovery: fastboot flash recovery magisk_patched_[random strings].img
10 - reboot with fastboot reboot
11 - Congrats, you got root! Unfortunately for you and your nonexistant ramdisk you have to boot into recovery to run the system with magisk
12 - use the recovery key combo until you see the splash screen, then release the keys. You will boot into magisk as it hijacks the recovery
13 - and thats how you root without ramdisk! you have gone through the entire pain of having to now use the recovery combo and releasing keys in order to boot into the system with root, but hey, you got root!
if you brick your device and/or meet the device reaper under the name of QUALCOMM USB DIAGNOSTIC, you're pretty much dead and i do not take any responsibility. that was your choice to go with this method.
if you blame me for anything ranging from alarm clock app failing and cant wake you up because it couldnt access the vibration and/or sound to a god forsaken thermonuclear war because the error code of the qualcomm usb diagnostic somehow gave you nuclear access codes, here's the response: COPE AND SEETHE
Click to expand...
Click to collapse