Database Develop

How to simply root FRF85B

Hi all,
Please how to simply root Nexus One?
This tutorial is to hard "
[Tutorial] Root FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Confirmed) "
No superboot.zip available for FRF85B?

Simply root = unlock bootloader. The second tutorial.
superboot.zip has nothing to do with the way of rooting. Rooting needs to bypass device protection to flash a non-certified update. So you either use exploits, or use the built-in protection override (fastboot oem unlock).

Depends on the status of your bootloader really.
If you want to keep it locked then that tutorial is your only hope.

I have unlocked bootloader but no superuser.apk and no Root privilege
About second Tutorial, we need linux....

If you have unlocked bootloader, what's the problem flashing pre-rooted FRF85B?
http://forum.xda-developers.com/showthread.php?t=714184

I have already flashing my Nexus with Unrooted version because i had signature problem with pre-rooted version.
Now to re-install pre-rooted FRF85 version i need Custom Recovery but I need root to install custom recovery...
No way to have superboot.bat to simply rooted my FRF85?

To install custom recovery you only need to flash it via fastboot, since your bootloader is unlocked.
You can also use ROOT_FRF83 file from the "difficult" thread, if I'm not mistaken.

Jack_R1 said:
To install custom recovery you only need to flash it via fastboot, since your bootloader is unlocked.
Click to expand...
Click to collapse
Thank's for your reply.
I will install custom Recovery to flash with pre-rooted version.
I need wipe before flashing with pre-rooted version?

No wipe needed.

About Custom recovery :
Pre-Requirements :
- unlocked bootloader : How to unlock the bootloader.
- root access : Modaco's superboot.
I have install recovery-RA-nexus-v1.7.0.1.img without rooting my nexus and now I have exclamation mark with a little Android...

Ok, did some search for you. Next time try - search button, "FRF85 root".
Reflash the stock recovery back.
Then use this:
http://htcpedia.com/forum/showthread.php?p=67177#post67177
Under "ROOT".

i have re-flash with stock recovery 2 times but still exclamation mark with a little Android.
Ok i push "Vol+" and "power", stock recoveruy appear
apply sdcard:update.zip (update-nexusone-FRF85-root-sig.zip from HTC EPIA)
--> E:signature verification failed..
Installation aborded

What about ROOT_FRF83.ZIP - did you try?

ROOT_FRF83.zip is for locked bootloader... mine is unlocked.
As i see i need linux and to make this command to root my stock FRF85B..
16) Download the following to the root of your SDcard
- recovery-RA-nexus-v1.7.0.1.img: http://rapidshare.com/files/39326736...s-v1.7.0.1.img
- Note: UnMount your SDcard after copying these files, but keep your phone plugged in
17) In your terminal type "adb shell" and hit Enter
18) In your terminal type "su" and hit Enter
- Tip: At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- Tip: $ should now be replaced with #
19) In your terminal, type "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter
20) In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter
21) In your terminal, type "chmod 775 /system/bin/flash_image" and hit Enter
22) In your terminal, type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" and hit Enter
23) In your terminal, type "rm /system/etc/install-recovery.sh" and hit Enter
24) In your terminal, type "rm /system/recovery-from-boot.p" and hit Enter
Click to expand...
Click to collapse

ROOT_FRF83 is for ANY bootloader. It doesn't care about bootloader.
Download it to your SD card, rename to update.zip and apply. It might not work - in this case, you have nothing to do but to follow the other guide, or wait until someone makes FRF85B superboot for stock ROM and recovery.
The part you've quoted is way past the actual root. Read the thread again, the root ends much earlier.
You need to do steps 1-15, and you need no Linux.

I checked again in Paul's thread, STOCK to CM.
There is NO requirement for root to flash custom recovery through fastboot. Otherwise fastboot wouldn't help any in rooting - think yourself, you need root to flash recovery, and you need recovery to flash root?
Here's a quote from there:
- If you get a Triangle with a ! in the middle alongside an Android for 5+ minutes, you MAY have to remove battery and re-flash recovery (I had to do this once.) (Make absolutely sure that nothing is happening on your phone, as removing the battery when it's doing something can cause a brick.)
So you can try this one and flash AmonRa's recovery again. If it doesn't work, and it turns out that you need Modaco's superboot (which doesn't exist for your version) - then you're back to the second guide.

I have always triangle with a ! after removing batterie, AmonRa's recovery won't appear...
I will wait superboot from paul.

Resolved
Step by Step how to get root from FRF85B stock (with unlocked bootloader) :
- Download AmonRa Custom Recovery and put it where google SDK, Tool folder, is installed.
- Download update-nexusone-FRF85-root-sig.zip and rename it update.zip and put it on the root of your SDCARD
1) Switch off the nexus
2) Hold the Trackball and Power button
3) fastboot devices (to make sure that fastboot "sees" your phone)
4) fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img
5) Don't reboot nexus! just chose "bootloader" from menu, after nexus reboot automaticly, chose recovery
6) AmonRa recovery appear!
7) Apply update.zip
You have root access!

zizouth said:
Resolved
Step by Step how to get root from FRF85B stock (with unlocked bootloader) :
- Download AmonRa Custom Recovery and put it where google SDK, Tool folder, is installed.
- Download update-nexusone-FRF85-root-sig.zip and rename it update.zip and put it on the root of your SDCARD
1) Switch off the nexus
2) Hold the Trackball and Power button
3) fastboot devices (to make sure that fastboot "sees" your phone)
4) fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img
5) Don't reboot nexus! just chose "bootloader" from menu, after nexus reboot automaticly, chose recovery
6) AmonRa recovery appear!
7) Apply update.zip
You have root access!
Click to expand...
Click to collapse
Hey thanks!
I was having the exact same issue & I now have a cyan recovery & root access on the stock FRF85B

[GUIDE] How to get root on the 10.1v

BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.

Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad

FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System

Awesome news! Thanks to everyone who worked on this - I can't wait!

Great, great job you guys! This thing needs root so it can grow

Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App

Thank you guys, it's working great on my 10.1v

I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??

This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition

Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..

gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox

bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..

gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?

Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!

black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.

seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot

Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .

Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge

Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.

I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App

[Q] Can't install any custom recovery Vodafone Nexus One

Hello,
i'm following this forum a long time, now. But at the moment I have a problem rooting my Vodafone Nexus One I can't solve.
It has 2.2.1 (FRG83D) on it. I unlocked the bootloader using fastboot. Now it shows the open lock when booting.
When I try to install a custom recovery using adb or terminal emulator, all looks good. But when i restart and go into recovery menu, always that damn standard menu appears (after putting power on & volume up).
Now I read, that I have to delete the install-recovery.sh in systems/etc and another file, I don't remember right now. I always get an error, when I try to delete or rename them. I tried it using adb, terminal and root explorer.
Does anyone have a clue how I can get rid of them?
Thanks!
Marco

Use fastboot, since you've already gone to the trouble of unlocking your bootloader...
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img

You have to remount the system partition as writable.
You only have to delete the install-recovery.sh file. The other one can be left alone.

hey guys, thanks...
i just did it using the following program and steps:
* - Download Superboot and extract it to a directory on your computer
* - Put your device into bootloader mode. You can either use ADB or turn the phone on whilst holding the trackball to enter the bootloader.
* - If on Windows double click ‘install-superboot-windows.bat’
* - If on a Mac, cd into the directory containing the files and type ‘chmod +x install-superboot-mac.sh && ./install-superboot-mac.sh’
* - If on Linux, cd into the directory containing the files and type ‘chmod +x install-superboot-linux.sh && ./install-superboot-linux.sh’
after that i had to remount it as R/W partition.

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.

[ROOT][TB-X605F/L] Magisk for those who cant use TWRP!

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