Database Info

Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac

For Droid 2's on Gingerbread, click link below to find info to Root your phone
http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
One Click Root Version for Linux and Works for Mac, too!
This is still a work in progress! Gonna call it 3.3 (I went through 3 previous versions). It takes the 2.2.1 version and adds a user interface. Nice, easy, clean. In order to run this script, you need to chmod (change permission) of the .sh file, and then execute it.
Download the file here: http://kimete.com/droid/beta/dorootv3.sh
It is good for both Linux and Mac. All you have to do is execute it and the script will download all the appropriate files for you!
How to run this in Ubuntu/Linux
How-to video here: http://www.youtube.com/watch?v=gvlB3e_UE8I
Note: General idea. You no longer need to update android-sdk, though.
1. Download the file.
2. Right-click the file, choose properties, choose the permission tab, and check executing file as program, close window
3. Double-click the file, choose Run in Terminal, and it'll start.
4. Choose 1 for install and root. Choose 2 for root process only. Only good if you've rooted using this method before, or you need to reroot your phone. Choose 3 to unroot. Choose 4 for credits/donation information. Choose 5 to exit. Choosing other numbers...
How-to for Mac
How-to video here: http://www.youtube.com/watch?v=d7s8dtfYyHI
Note: General idea. You no longer need to download and install android-sdk anymore.
1. Download dorootv3.sh. Best to put it on your desktop.
2. Open a terminal. Go to the magnifying glass and type in terminal, and then select it.
3. Next, you need to change permissions. Type in the terminal chmod 0755 followed with a single space. Then drag the dorootv3.sh into terminal.
You should see something like this chmod 0755 /user/(file path)/dorootv3.sh. Press enter.
4. Now run your file by dragging the file into the terminal again and pressing enter!
5. Now choose and option...
New version of rooting for Linux and Mac! Version 2.2.1!
Linux 2.2.1: http://www.kimete.com/droid/beta/DoRootLinux_221.zip
Mac 2.2.1: http://www.kimete.com/droid/beta/DoRootMac_221.zip
General Instructions:
1. Extract the files.
2. Change the permissions on the doroot.sh file
3. Run doroot.sh file.
Instructions for Linux and Mac
1. Extract the respective files to somewhere accessible. Your home directory or desktop is idea. The file comes in a .zip file. Just open it up and drag and drop the DoRootMac or DoRootLinux folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the folder in terminal.
example: [cd /DoRootMac or cd /DoRootLinux]
4. enter [chmod 0755 doroot.sh] then run it [./doroot.sh]
5. Let it run.
6. That's it, you are done.
One Click Root for Windows
Here's the Windows version. Facelessuser pushed this through and worked his magic. Give it a try. Very exciting stuff. I haven't used it yet, but according to him, it should work!
Download here, Ver. 2.1.4:
http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
Instruction for Windows:
How-to video here: http://www.youtube.com/watch?v=B7RGVikpQ8o
1. Extract the folder from the DORoot zip file to your desktop. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom righ, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot.bat
5. Let it run.
6. That's it, you are done.
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Many thanks to facelessuser for working his magic!
====
====
How-to Videos
Video of the Rooting Process for D2 and DX by [email protected]
For Windows/Mac/Linux
http://www.youtube.com/watch?v=u5l3MDomDSc
Video of the Rooting Process for D2 and DX by DarkOnion
For Windows
New: http://www.youtube.com/watch?v=B7RGVikpQ8o
Old: http://www.youtube.com/watch?v=gzlg9a-H42w
How to use the ADBDL.sh file by DarkOnion
For Mac and Linux
http://www.youtube.com/watch?v=9cHpGXfEudM
=====
=====
Frequently Asked Questions
Why does my anti-virus tell me that the files contain Trojan's?
The files are exploits and hack your phone. Don't worry, they are clean. However, to be safe, do not download from any other source than the ones linked in this post.
I've gotten countless hate mail and comments on Youtube users about rageagainstthecage-arm5.bin being detected as a trojan. It is an EXPLOIT. If you are scared that the files I hosted are going to give your computer a virus. Look else where, like Z4Root, though, my understanding is that Z4Root also uses rage.
http://forum.xda-developers.com/showthread.php?t=853704
What is do these files/programs/scripts do?
These scripts will root your Droid 2 or Droid X phone with the least amount of user input as possible.
Why should we use this method and not another method?
All the methods are based off the same process/procedure. If you feel like doing MORE work, we can't stop you. The reason why we wrote all these scripts is to expedite the process, make the procedure easier, and to reduce human input which reduces the chance of human error.
Is there anything I need to know in order to successfully root my phone?
Yes. READ THE DIRECTIONS. Read the directions first. A lot of people make errors because they don't read the directions. I've also provided links to my video and another video which outlines the root process. Both are only a few minutes long.
Root failed! What do I do?
Run the script again! Most people succeed on the first or second try. Usually the rest by the third try.
Do I have to install Android SDK and update it?
It depends. The new Linux/Mac version does not require you to. The windows one, we are still working on.
Does this work on other phones?
I can't answer that. I know it works for Droid 2 and Droid X.
Wait a minute, this isn't really one-click! What's the deal?
Deal with it. Don't like it, try the 25+ step process.
When I open up the Superuser app, I get a blank screen.
That is NORMAL. Superuser lists the processes/applications that you've allowed superuser access to. If you haven't allowed anything, then it will be blank.
How do I test if I have root or not?
Try downloading an app like Wireless Tether (published by Google), and running it.
What USB connection mode do I set my phone to?
PC Mode or Charge Only. Choose the one that comes up with USB Debugging.
I am not very good with computers. Is this something I can do?
Oh yes! The key to success is following the directions.
How do I update Android SDK?
On Windows, you just need to double click the SDK Manager.exe. On Linux/Mac, you need to go into terminal, navigate to the tools folder in the android sdk folder, and run this command ./android update sdk. More information can be found in the SDK Readme text file. On Windows, double-click and run the SDK Manager.
I am getting stuck at the "daemon not found/daemon is starting" part. What do I do?
You need to fumble with the settings on your phone. You don't need to close the terminal. Change between PC Mode and Charge Only mode until it starts to continue. If that still doesn't work, also try disabling then enabling USB debugging for each mode.
=====
=====
Reporting an Error or a Problem
You can report errors right here in this thread. Make sure you give us as much information as possible. List what operating system you are on, what phone you have, at what part of the script you had errors, and anything else you may have tried or done. The more information you provide us, the better we understand situations. Posting up pics or logs of the terminal is extremely helpful.
=====
=====
Change log for 1-2-3 Root
Version 0.0 - 25+ step tutorial on how to root D2 on Windows and Mac
Version 1.0 - Initial scripts to streamline processes and reduce user error in Ver. 0.0.
Version 2.0 - Streamline of multiple scripts into 1 script. Minimal commands. Minimal work. With error checking and reporting.
Version 2.1 - addressed issue where remnants of a previous root would not allow root to complete
Version 2.1.1 -
-Cleanup code.
-Address issue where I thought I was killing a hanging rage, but I wasn't (It was a syntax thing)
-Fix for ERROR6 or ERROR5 (this was drastically different than what I did in windows. I wasn't returning exactly a string in format I thought when doing the check, so I had to do some ridiculous stuff to process it.)
-Better error resolution. (more error checking)
-Refined unroot.
-Reboot if you had files from a previous root
-Now the script will automagically download needed root files if they are not in your folder. (If you are behind a proxy, make sure your mac or linux has curl or wget configured for proxies respectively)
-Longer wait before remount (I had it not remount because it was busy once)
Version 2.1.2 -
Linux and Mac
Contains everything windows 2.1.1
Unroots non bootstrapped phones too
All
Contains option to unroot
Version 2.1.3 - Added dounroot.bat
Vesion 2.1.4 -
-Fix bug where people were getting a false ERROR5 because they already had Superuser.apk
-Hide killing of busybox before unroot
Version 2.1.4 - Files are standalone. No need to download Android SDK anymore.
Version 2.2.0 -
-adb included, no SDK needed
-abort if cannot find adb
-remove alternate busybox at /system/xbin and /system/bin when unrooting
-remove alternate busybox at /system/xbin when rooting and installing busybox at /system/bin
-No more hang in exploit...I hope
-Clean up code
Version 2.2.1 - minor revision to code (curl related)
DarkOnion's DoRootv3
Version 3.0 - set-up menu's, added error checking, will detect which OS you are on
Version 3.1 - fixed issues with ADB SDK User interfaces
Version 3.2 - adapted to DoRoot 2.2.1
Version 3.3 - edited code for easier understanding and modifications
=====
=====
References:
Original procedure produced by Sebastian Krahmer
http://forum.xda-developers.com/showpost.php?p=7838000&postcount=1
Tutorial/How-to Root Droid 2 on Windows by DarkOnion
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
Tutorial/How-to Root Droid 2 on Linux/Mac by DarkOnion
http://forum.xda-developers.com/showpost.php?p=8103311&postcount=340
====
====
Appreciate my work and/or help, feel free to send donations my way! Poor college student here who just got a speeding ticket! Doh!

This is outdated information and should be used as a reference only! All updated versions have moved to POST #1.
Hi all. Made it to the front page of XDA Developers.
http://www.xda-developers.com/android/easy-rooting-method-for-droid-2/
I just want to make sure credit is given where due. First of all, the original procedure was produced Sebastian Krahmer. From there I wrote an indepth tutorial to root the Droid 2. I took a vague instruction set and help it grown into something that the average person could understand. Understanding the need to simplify the process, I decided to write scripts to further streamline the process. What started out as a 3 part script that involved 8 or 9 commands eventually became a two part script that involved 3 or 4 commands. I have no programming background, by the way. Having trouble getting the process down into one part, facelessuser volunteered to take my work, and put a bunch of neat things into it to get it to work as one thing with error checking! So, with that said, I'd like to thank everyone that had a part in the project, especially facelessuser for his dark magic arts that made the script run, matt4542 for constantly testing my various scripts, and everyone who directly or indirectly ran the scripts!
We are moving forward!
===
Hi all.
We (me), facelessuser, and a few others are working furiously to get an easy one step program out for you guys. In the mean-time, I have a pretty safe, and clean, and easy 2 step method for Windows, Mac, and Linux. I am still cleaning stuff up, but for the most part, it all runs well.
What you need:
Android-SDK for your operating system which can be found here:
http://developer.android.com/sdk/index.html
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
And the files/scripts/programs to root for your OS:
Want to try the one step process, go down to post #2!
Windows [1.0]: http://www.kimete.com/droid/DORootforD2Windows.zip
Mac/Linux [1.0]: http://www.kimete.com/droid/DORootforD2Linux.zip
Instruction for Windows:
GO DOWN TO POST #2 AND DOWNLOAD THE ONE STEP
1. Extract and Update Android SDK package to your computer. The file comes in a zip file. Just open it up and drag and drop the android-sdk-windows folder to your C drive. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom right, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot1.bat
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to DOS, enter or double click doroot2.bat
8. That's it, you are done.
Instruction for Linux and Mac:
GO DOWN TO POST #2 AND DOWNLOAD THE 1-STEP!
1. Extract and Update Android SDK package to your computer. The file comes in a .tar.gz file. Just open it up and drag and drop the android-sdk-linux folder to your home directory or desktop. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the tools folder of your android-sdk
[cd /android-sdk-linux_x86/tools]
4. enter [chmod 0755 doroot1.sh] then run it [./doroot1.sh]
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthe cage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to command prompt, [./doroot2.sh]
8. That's it, you are done.
Enjoy my works? Want to show your gratitude? Just want to help a poor college student out, donate via PayPal to: [email protected]. All donations are greatly appreciated. Money will be spent on escorts, food, adult beverages, higher education and its bs fees, paying off my phone, and the wonderful speeding ticket I got this week!

Hey Thanks alot for writing this! I just tried it out and ran until completion.
A few things I found.
In the dos prompt, part2 the program asks user to input a few commands. Commands 2 and 3 should end in .sh. The program dosent mention this.
Thanks again

Typo in the 3rd step. You forgot to add '.sh'.

lockdownx1x said:
Typo in the 3rd step. You forgot to add '.sh'.
Click to expand...
Click to collapse
Doh. Good catch y'all. I will take care of that now!

Problem
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!

The " ./ " before doroot.sh tells linux to look in the current directory for the file to run. Make sure you in the tools directory of the sdk and that the script is there as well.
Sent from my DROID2 using XDA App

Yep i definitaly made sure of that but same error. It doesnt matter though i have rooted my droid 2 through the manual proccess

NiteSite said:
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
Click to expand...
Click to collapse
Did you do cd data/local/tmp in adb shell before doing the chmod and ./doroot2.sh?

Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App

NiteSite said:
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Weird. I am going to send you a PM. Hit me up on Google Talk.
-Kevin

Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?

mjones1052 said:
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
Click to expand...
Click to collapse
I am working on it. Hahaha. I don't have any programming background. So I am learning on the fly, but progress is being made.
Though, I have to say that the process is much much much easier than what it originally began as. So... moving in the right direction.

I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?

Kenny Strife said:
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Click to expand...
Click to collapse
Just follow the instructions. Launch the doroot1.bat file. The .bat file will launch you into ADB shell. chmod the doroot2.sh file, then run it. adb shell again. chmod the doroot3.sh file and run that. Hope that helps. I am on google talk if you need help.

I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.

please help!
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??

chrismouro said:
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
Click to expand...
Click to collapse
You are okay. Superuser lists the program you've allowed superuser access to. You haven't given any apps access, therefore blank!

Kenny Strife said:
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
Click to expand...
Click to collapse
Kenny, did you get this resolved? I am experiencing the same issue.

I'm getting kicked the ./doroot2.sh: not found as well. Anyone get past this point?

[mod] Clockwork recovery 3.0.2.8 [easy install] v3

I have put together a little program to allow me to install recovery quicker because I got fed up of it taking so long.
Its dead easy to use!
instructions
download file
unzip
connect vega and make sure usb debugging in enabled
click windows_install, mac_install, or linux_install to flash depending on what your running (u should know that )
wait for that to finish
to boot into recovery click the recovery icon in your app draw
Download v3 clicky - mirror 1
another v3 - mirror 2
For those of you that are having an "error: device not found"
It means that you dont have the adb drivers installed correctly
To check right click on the windows folder and click command prompt here. then type adb devices
If nothing shows up then it means the drivers arent installed
To install them correctly follow this guide
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
Click to expand...
Click to collapse
v1 - windows only
v2 - added mac and linux
v3 - updated to CW 3.0.2.8
thanks go to @mad murdock for making the image and now for fast mirrors
also thanks to @bob1369 who has made a mac and Linux version

i have created mac and linux versions
linux; http://www.megaupload.com/?d=JNEP1GJ5
mac; http://www.megaupload.com/?d=O73B61F0
i suggest creating a small automator app on the mac to further speed installation of clockworkmod just drag run shell script into a work flow and write in the box below the code you would usually use to run the script from terminal e.g.
cd /route/to/script
./install.sh

This worked a treat for me.
I used it to update cwm to the latest version.
Thanks very much for a time saving app.

bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
ahh nice work! i will add to the first post and mention you
i will test linux some time

bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
I have tested the linux version. It works. Same thing with the chmod... I guess you cannot chmod something that is not there.. Just remove the trailing slash. It should work then....

help
my computer cant detect my advent vega
i try xp win7 and vista
help

device no find
after i use install
the word"device no find"
anyone help

fung58745 said:
after i use install
the word"device no find"
anyone help
Click to expand...
Click to collapse
on the vega or pc?

on pc and my vega is in usb debug

same ad "add.thebad " devices not find
my i hav been setup up adb

well done! pretty userfriendly - will link to this post

i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
hope that helps...
mirror1: clockwork_recovery_3.0.2.4_vega_noflash.zip size: 73M (76109336 bytes)
mirror2: clockwork_recovery_3.0.2.4_vega_noflash.zip md5sum: 4d8cf9aa85331e8e2673b3406646fbc5

fung58745 said:
on pc and my vega is in usb debug
Click to expand...
Click to collapse
fung58745 said:
same ad "add.thebad " devices not find
my i hav been setup up adb
Click to expand...
Click to collapse
odd, does the vega show up if you do "adb devices"?

mad-murdock said:
i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
Click to expand...
Click to collapse
o yeah, that speedy download is nice i will put in first post thanks.
i have merged mac and linux as well attatched to first post
i will pm

same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.

fused#1 said:
same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.
Click to expand...
Click to collapse
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7

fused#1 said:
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7
Click to expand...
Click to collapse
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list

add.thebad said:
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list
Click to expand...
Click to collapse
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)

fused#1 said:
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)
Click to expand...
Click to collapse
hmmm, a little confused by this one. mines works correctly and shows up under adb devices but mine shows up as android composite adb interface
try an install like this
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
i think that should set it up right
have you used the vega and adb before?

Thank you. I will try that right now. Used adb with a desire until today.

[Q] JB Rooting Issues

Okay so basically all I'm wanting to do is get root access. I'm on the latest JB build thanks to my dad "making sure everything was up to date" before he gave me my infinity for my birthday. Tried the Debugfs method already with no luck at all on 2 PCs. Apparently unlocking my bootloader isn't an option either as I'm stuck with the dreaded "network error" message. Bootloader isn't really an issue though, as I wasn't needing any custom roms/kernels/etc, just wanting to use a PS3 controller. Anyways, short version of my question, whats the quickest way for me to downgrade to ics, root, and upgrade back to JB (if thats even needed?). Or for me to get root access on my current build? Any help is appreciated!

AsusInfinity said:
Okay so basically all I'm wanting to do is get root access.
Click to expand...
Click to collapse
Well,
You'll have to go back to ICS .30 if you want to root with debugfs.
If the Asus unlock servers aren't working it's the only way to get rooted.
Below is a cut and paste from here:http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
_______________________________________________________________________________
*This method works only with ICS roms
Note: Rooting will NOT void your Warranty!!!
Before you start make sure that:
* USB Debugging is activated (on your device go to Settings/Developer Options/USB debugging)
* Unknown Sources is activated ( on your device go to Settings/Security/Unknown sources )
* Make sure no other Android device is connected to your PC
* Make sure Asus Sync Tool is not running on your PC
========= Rooting procedure =========
1) Create a folder on your desktop an name it " TF700 Rooting " (you can use a different name but i will use this name in this guide)
2) Download Asus USB drivers and Debugfs automated root from here
3) Extract the downloaded files to TF700 Rooting folder
4) Power ON your device and connect it to a USB port on your PC
5) If Windows is asking for the drivers point the driver installer to the Asus USB drivers in the TF700 Rooting folder ... if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)
6) Open the TF700 Rooting folder and run RootDebugfs.bat (right click --> Run As Administrator)
7) Select option "1" and press "Enter"
8) Follow the instructions on-screen
DONE, if you did everything right your device will be rooted.

Rooting the rko3066/rockchip 3066 device

I'm a newbie to Android, but I fumbled around with a rooting tool and found a method that works to root two flavours of rko3066, rockchip 3066 devices. As it only roots the device, I see no reason why it should not root any android device, as long as the correct device drivers are used.
USE AT YOUR OWN RISK.
As always with any routine that flashes the eprom of any
cpu, no responsibility is assumed or implied by the author
for any damage that following these instructions may cause
to your phone, tablet, pc or device.
USE AT YOUR OWN RISK.
Rooting u30gt-h
On tablet
1.In U30gt-h Settings->Display open sleep setting.
2.Set sleep to at least ten minutes.
3.In U30gt-h Settings->storage->click on Three dots in upper
right of Settings window title field
4 Select USB computer connection Dropdown menu .
5. Select "Mass Storage" check box
6. <-- backout of storage settings
7. Browse down in Settings and select Security
8.In Security Settings, Select Unknown sources, to give the
Android device permission to install software from sources
not specifically sanctioned by Google and the Android
Consortium. This ensures that the Root utility,
Tp-Sparky-Root.bat will have the necessary access rights to
root the u30gt. If you have any qualms about unsanctioned
files on your tablet or device, you will want to uncheck
this selection after the rooting process is complete.
Whether any of the rooted utilities and programs you will
want to use are sanctioned, is anybody's guess. As always,
be careful when Dling or intalling Any software. I trust
everyone has and uses anti-virus software on all your
devices.
8.scroll down in settings and select {} Developer
Options, if not there, go to (i)about tablet and touch and
hold the Build field and it will bring up developer Options
in the left hand main menu.
9. In Developer Options, select USB debugging.
10. Close settings, and any other open apps.
11. Goto U30gt main android desktop, to ensure good clean
reboots.
12. Using a Known good micro USB to std USB cable,
connect U30gt tablet to PC, you'll get a "connecting to usb"
in notifications area in Android, and a usb icon in the
notification area. You Do Not want to select "Connect to Pc
to Transfer Files", in the notification menu, just plug in the
cable and let it be.
USE AT YOUR OWN RISK.
On PC
1. Search in a web browser for RKBatchTool_u30.zip, the 1.5
version, DL and unzip in the default zip file subdirs.
Rk-batch-tool 1.5 has u30gt drivers, browse the Rk-batch
tool's dir for the u30 drivers for your PC OS. Right click
on the rockusb.inf and chose Install, to install the driver.
2. Verify that you have a rockchip_usb USB Device under disk
drives in Device Manager. Control Panel->System->Hardware->
Device Manager->Disk Drives->rockchip_usb USB Device.
3. Dl TPSarky-VonDroid-Root.rar from
*"mediafire.com/?vd3y1rld2amdxq5"*
as a newbie I cannot post links, so search mediafire.com for TPSarky-VonDroid-Root.rar
4. Unarchive TPSarky-VonDroid-Root.rar, using an archive, or
zip utility: Winzip, alzip, etc. It may require the password
"geekbuying.com" to unrar the archive.
5. Mouse into TPSarky-VonDroid-Root directory created by the
rar file, until you get to TPsparkyRoot.bat and adb.exe
files, a couple of sudirs inside TpSarky unzipped file
directories.
6. Run, double click on, adb.exe first. It opens up a dos
command window, runs a dos executable that launches adb
server and connects to the U30gt. It opens and closes so
fast you won't hardly see it. If you Do Not run adb.exe.
first, Tp-Sparky-Root.bat will not communicate with the
U30gt, and your root will fail.
7. Now run, double click on, Tp-Sparky-Root.bat
Tp-Sparky-Root.bat will Immediately reboot the u30gt.
8. When the u30gt reboots, hit space key as instructed.
Tp-Sparky-Root.bat will reboot the u30gt, again.
9. Press the space key as instructed, again. The command line
will show
uid=0<root> gid=0<root>
if you have a successful root.
10. Press the space key as instructed, again.
The command informs you the U30gt root has been remounted,
there are a couple of errors relating to SuperSU, I presume
SuperSu was Not included in the tpsarky zip file, or is in
the wrong place for the batch file to find it, but you can
DL SuperSU from GooglePlayStore, nhnf. The Utility notifies
you that Tp-Sparky-Root.bat is completing the root.
11. The u30gt will reboot one last time.
12. DL Titanium Backup Root, Rootchecker, or Avast Android to the tablet,
and they will confirm a rooted tablet.
**As this method only Roots the device, and since it worked
on both my u30gt and an Imito-Mx1 mini android, I think it
should work on nearly any RKO3066 droid device.
As always with any routine that flashes the eprom of any
cpu,
USE AT YOUR OWN RISK.
Thanks to the people who initially posted the original root
routine for the IMITO-MX1 on Youtube, and to geekbuying for
this procedure, as well as the files for rooting the IMITO-
MX1 and ultimately the u30gt. A big thanks to Tp-Sarky or
Tp-Sparky, whoever they may be, for writing the batch file
that does all the work. I also want to thank 900Supersport,
kastycube and the good folks at alldocube for their various
flavours of the u30gt firmware and utilities, as well as
flashmyandroid.com
I have tried all flavours of android 4.1 firmware, 900
supersport, kastycube, to the generic cube-tablet.com
versions from 1.07 to the latest greatest build 1.11, and
None of them gives me access to the microsd card. I bought
two of these puppies for Christmas, IPS version, and neither
the original out of the box or my reconfigured one reads
microsd. It is possible that both got bad sd card readers,
but unlikely. As my imito-mx1 miniandroid reads the microsd
cards, as does the adapter in my pc, it is most probably an
U30gt flavour android system software issue. Anybody got any
clues how to resolve microsd issues in android?

works great
533online said:
I'm a newbie to Android, but I fumbled around with a rooting tool and found a method that works to root two flavours of rko3066, rockchip 3066 devices. As it only roots the device, I see no reason why it should not root any android device, as long as the correct device drivers are used.
USE AT YOUR OWN RISK.
As always with any routine that flashes the eprom of any
cpu, no responsibility is assumed or implied by the author
for any damage that following these instructions may cause
to your phone, tablet, pc or device.
USE AT YOUR OWN RISK.
Rooting u30gt-h
On tablet
1.In U30gt-h Settings->Display open sleep setting.
2.Set sleep to at least ten minutes.
3.In U30gt-h Settings->storage->click on Three dots in upper
right of Settings window title field
4 Select USB computer connection Dropdown menu .
5. Select "Mass Storage" check box
6. <-- backout of storage settings
7. Browse down in Settings and select Security
8.In Security Settings, Select Unknown sources, to give the
Android device permission to install software from sources
not specifically sanctioned by Google and the Android
Consortium. This ensures that the Root utility,
Tp-Sparky-Root.bat will have the necessary access rights to
root the u30gt. If you have any qualms about unsanctioned
files on your tablet or device, you will want to uncheck
this selection after the rooting process is complete.
Whether any of the rooted utilities and programs you will
want to use are sanctioned, is anybody's guess. As always,
be careful when Dling or intalling Any software. I trust
everyone has and uses anti-virus software on all your
devices.
8.scroll down in settings and select {} Developer
Options, if not there, go to (i)about tablet and touch and
hold the Build field and it will bring up developer Options
in the left hand main menu.
9. In Developer Options, select USB debugging.
10. Close settings, and any other open apps.
11. Goto U30gt main android desktop, to ensure good clean
reboots.
12. Using a Known good micro USB to std USB cable,
connect U30gt tablet to PC, you'll get a "connecting to usb"
in notifications area in Android, and a usb icon in the
notification area. You Do Not want to select "Connect to Pc
to Transfer Files", in the notification menu, just plug in the
cable and let it be.
USE AT YOUR OWN RISK.
On PC
1. Search in a web browser for RKBatchTool_u30.zip, the 1.5
version, DL and unzip in the default zip file subdirs.
Rk-batch-tool 1.5 has u30gt drivers, browse the Rk-batch
tool's dir for the u30 drivers for your PC OS. Right click
on the rockusb.inf and chose Install, to install the driver.
2. Verify that you have a rockchip_usb USB Device under disk
drives in Device Manager. Control Panel->System->Hardware->
Device Manager->Disk Drives->rockchip_usb USB Device.
3. Dl TPSarky-VonDroid-Root.rar from
*"mediafire.com/?vd3y1rld2amdxq5"*
as a newbie I cannot post links, so search mediafire.com for TPSarky-VonDroid-Root.rar
4. Unarchive TPSarky-VonDroid-Root.rar, using an archive, or
zip utility: Winzip, alzip, etc. It may require the password
"geekbuying.com" to unrar the archive.
5. Mouse into TPSarky-VonDroid-Root directory created by the
rar file, until you get to TPsparkyRoot.bat and adb.exe
files, a couple of sudirs inside TpSarky unzipped file
directories.
6. Run, double click on, adb.exe first. It opens up a dos
command window, runs a dos executable that launches adb
server and connects to the U30gt. It opens and closes so
fast you won't hardly see it. If you Do Not run adb.exe.
first, Tp-Sparky-Root.bat will not communicate with the
U30gt, and your root will fail.
7. Now run, double click on, Tp-Sparky-Root.bat
Tp-Sparky-Root.bat will Immediately reboot the u30gt.
8. When the u30gt reboots, hit space key as instructed.
Tp-Sparky-Root.bat will reboot the u30gt, again.
9. Press the space key as instructed, again. The command line
will show
uid=0<root> gid=0<root>
if you have a successful root.
10. Press the space key as instructed, again.
The command informs you the U30gt root has been remounted,
there are a couple of errors relating to SuperSU, I presume
SuperSu was Not included in the tpsarky zip file, or is in
the wrong place for the batch file to find it, but you can
DL SuperSU from GooglePlayStore, nhnf. The Utility notifies
you that Tp-Sparky-Root.bat is completing the root.
11. The u30gt will reboot one last time.
12. DL Titanium Backup Root, Rootchecker, or Avast Android to the tablet,
and they will confirm a rooted tablet.
**As this method only Roots the device, and since it worked
on both my u30gt and an Imito-Mx1 mini android, I think it
should work on nearly any RKO3066 droid device.
As always with any routine that flashes the eprom of any
cpu,
USE AT YOUR OWN RISK.
Thanks to the people who initially posted the original root
routine for the IMITO-MX1 on Youtube, and to geekbuying for
this procedure, as well as the files for rooting the IMITO-
MX1 and ultimately the u30gt. A big thanks to Tp-Sarky or
Tp-Sparky, whoever they may be, for writing the batch file
that does all the work. I also want to thank 900Supersport,
kastycube and the good folks at alldocube for their various
flavours of the u30gt firmware and utilities, as well as
flashmyandroid.com
I have tried all flavours of android 4.1 firmware, 900
supersport, kastycube, to the generic cube-tablet.com
versions from 1.07 to the latest greatest build 1.11, and
None of them gives me access to the microsd card. I bought
two of these puppies for Christmas, IPS version, and neither
the original out of the box or my reconfigured one reads
microsd. It is possible that both got bad sd card readers,
but unlikely. As my imito-mx1 miniandroid reads the microsd
cards, as does the adapter in my pc, it is most probably an
U30gt flavour android system software issue. Anybody got any
clues how to resolve microsd issues in android?
Click to expand...
Click to collapse
works great full root on sk30sdk android 4.1.1 2013 rockchip tablet follow instructions and all is well

do you have any idea; f this process works on
Next book 7 premium se
s/n: YFG121******* ?
Sent from my Next7P12 using Tapatalk 4 Beta

Just rooted PIPO M9 which is a RK3188 using this method.
Althought I can everything that a rooted device does, including executing the apps and changing syste files, I don't see SU app anywhere?
Is this normal?

cool, I think I'm gonna try this method tonight after work.
I'll let you know how it goes
Hacking my Own Next7P12-GP, PM me if you can help

Thanks .. it works for RK30_ICS :good::good:

Djuganight said:
Just rooted PIPO M9 which is a RK3188 using this method.
Althought I can everything that a rooted device does, including executing the apps and changing syste files, I don't see SU app anywhere?
Is this normal?
Click to expand...
Click to collapse
Yep, but for security reasons it's better to install some su governor, because now every app can have root access without your permission.

http://forum.xda-developers.com/showthread.php?p=43584766#post43584766
Check this for simple 4 steps root for this device. Easy and without any risks and even with an unroot tool.

Hi Guys, I Need Help to Root my Alcatel One Touch Tab 7HD with
Chipset: Rockchip RK3066
Android 4.1.1
Kernel Version: 3.0.8+
Build Number: 100_ASPPH_000
I cannot enter too Stock Android Recovery Mode ;(
I already Install the adb driver, usb driver of this device and Rockchip Driver ;(
I'll try many Rooting Procedures but Opportunetly it doesnt work ;(
The ff. the i will use to ROOT this Alcatel One Touch Tab 7 HD are
Application Status
1. UnlockRoot Failed
2. SuperOneClick v.1.9.1.0 Failed
3. Root_with_Restore_by_Bin4ry_v31 Failed
4. Srsroot Failed
5. Zuodashi Failed
i'll Try also this Method but its doesn't work too ;(
Rooting the rko3066/rockchip 3066 device
http://forum.xda-developers.com/show....php?t=2127573
[GUIDE] Fix ADB USB driver for Rockchip RK3066
http://forum.xda-developers.com/show....php?t=2061063
I hope any can Help me. ;(

Thank you very much, I have just rooted my Cube U18GT-S

Works also on Kiano Core 10.1 Dual 3G...
after installing Samsung Android ADB driver for Win 7. Thank you very much.....:fingers-crossed: :good:

Search in a web browser for RKBatchTool_u30.zip, the 1.5
version, DL and unzip in the default zip file subdirs.
Rk-batch-tool 1.5 has u30gt drivers, browse the Rk-batch
tool's dir for the u30 drivers for your PC OS. Right click
on the rockusb.inf and chose Install, to install the driver.
Click to expand...
Click to collapse
I'm trying to root my Andi-7 tablet with Android 4.1.1 and the RK30sdk.
I searched as instructed and found this zip file.
Extracted the file, found rockusb.inf and right clicked and chose install.
Every time, I get the error message.
Any help?

Thanks
Works on Xelio P717A

You can try this method found here http://forum.xda-developers.com/showthread.php?t=1987280&page=2. It's the method I used on my IdeaUSA CT705 it's just repetative having to keeping pushing the"enter" button as it also states in the thread.

Working on iRulu AX105
Thank you, working on iRulu AX105 Tablet, 10.1"

Permission denied
As ichiyamato said, this method not working for sk3066 device. Scrips are not working because there are no permission to copy necessary files into device.
All scripts gave,
Code:
*---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
--- Plug in your device, make sure debugging is enabled in Developer Options
--- This script will now copy files over to your N101 II
failed on '/data/local/tmp' - Permission denied
link failed File exists
I think we should open write permission on device. But i dont know how.
Thanks.

Work on Touchmate TM-MID940
I have successfully root my Touchmate TM-MID940 with TPSarky Android rooting method
Thanks

Confirmed working on an Energy System i8 tablet.
The micro SD card on my device does not stay in properly, so this method was needed.
I had to manually fiddle with adb a little (I had been trying other methods to root), so personally I would change the instructions to explain how to open a command prompt and execute:
adb kill-server
adb start-server
(Check it says starting server)
adb get-state
(check it says device)
then run the batch file

Rooted Cube U30GT-H firmware original v1.11 Rockchip 3066 with Kingo Root. Easy, easy. :good:

rootmaster
ichiyamato said:
Hi Guys, I Need Help to Root my Alcatel One Touch Tab 7HD with
Chipset: Rockchip RK3066
Android 4.1.1
Kernel Version: 3.0.8+
Build Number: 100_ASPPH_000
I cannot enter too Stock Android Recovery Mode ;(
I already Install the adb driver, usb driver of this device and Rockchip Driver ;(
I'll try many Rooting Procedures but Opportunetly it doesnt work ;(
The ff. the i will use to ROOT this Alcatel One Touch Tab 7 HD are
Application Status
1. UnlockRoot Failed
2. SuperOneClick v.1.9.1.0 Failed
3. Root_with_Restore_by_Bin4ry_v31 Failed
4. Srsroot Failed
5. Zuodashi Failed
i'll Try also this Method but its doesn't work too ;(
Rooting the rko3066/rockchip 3066 device
http://forum.xda-developers.com/show....php?t=2127573
[GUIDE] Fix ADB USB driver for Rockchip RK3066
http://forum.xda-developers.com/show....php?t=2061063
I hope any can Help me. ;(
Click to expand...
Click to collapse
I think u should try rootmaster . Search it on google . Its an chieneese app but u shall understand how to use when u will install it . It can root many of the rk3066 devices

[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux

[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux
Ciao xda users, I'm here to introduce a new tool of mine, MiUnlockTool.
MiUnlockTool is an unofficial tool used to unlock bootloader on Xiaomi devices. This tool is copied from the original windows MiFlashUnlock tool and works the same way. The main feature of this tool is compatibility with linux and mac operating system (and windows too).
If you want more information about the tool and the story behind you can read below, if you just want the download link, here it is:
DOWNLOAD LINK
Requirements: java (javafx for gui if not included in your jdk/jre)
Usage:
- Download and extract the zip file
- If you don't have it, install java
- On windows:
-- open MiFlashUnlock.bat for graphical interface or:
-- open a cmd windows and cd into extracted dir and use "MiUnlockTool.bat username password" command for command-line usage
- On linux:
-- open a terminal window and cd into extracted dir and use "sudo ./MiUnlockTool.sh" command for gui interface or "sudo ./MiUnlockTool.sh username password" for command-line
- On mac:
-- open (double click) MiFlashUnlock.command for graphical interface or
-- open a terminal window and cd into extracted dir and use "./MiFlashUnlock.command username password" for command-line
- Attach your locked device in fastboot mode.
- If you are using gui just follow what you see on your screen
- If you are using command line version remember that there is no confirmation request before unlock and no check if the bootloader is already unlocked.
Possible errors:
- If you get a permission related error on linux or mac when launching the tool, open a terminal and cd into extracted dir and use "chmod 777 MiUnlockTool.sh" (or MiUnlockTool.command on mac) to set the executable permission.
- If your device isn't recognized:
-- On windows: install adb drivers
-- On linux/mac trying launching the tool with sudo (sudo ./MiUnlockTool.sh on linux or sudo ./MiUnlockTool.command on mac)
- Other problems launching the tool: try running "java -jar bin/MiUnlockTool.jar" command
- If you get some errors with javafx class not found stuff when you try to launch the gui, then you are missing javafx library. See openjfx package on linux.
- Any other problem: provide feedback in the comments.
Additional info: original MiFlashUnlock tool is just a bridge between fastboot, you (and your account login credentials) and xiaomi server: the tool gets device info from the device and send them to the server together with the account login token, the server checks wherever you satisfy all their requirements (account authorized, account associated with device in developer settings etc) and if everything is okay the server reply with the unlock key for your device instance (every time you reboot your phone you need a new key). Then the tool send the key to the device with a custom build of fastboot and if the key is right then the device is unlocked, else it reboots. After I discovered all the process behind the original unlock tool (and all the security encryption techniques) I decided to replicate it with a java (cross-platform) tool which embeds a custom fastboot version and replicates what the original tool does. That's a simple explaination of how my tool works (obviously it's more complicated than that).
This tool requires all of what is required by the original tool (an authorized xiaomi account binded to the device through developer options for three days if I remember correctly).
FAQs:
- Is this tool safe to use?
Yes, the main part is communication between tool and server, a safe thing. Also the unlock procedure itself is safe: or the key is correct or it is not. In both cases the device will not be damage.
- How did you find out how to replicate the original tool?
Thank you for your question. It's been a bit difficult since the original tool has been obfuscated and virtualized (protected against reverse engeneering) with a powerful protector: VMProtect. I've spent some time to reverse it (and custom fastboot too) and I finally did it. I will not explain in details how I did it.
- Is this tool more powerful than the original on? why should I use it on Windows?
Absolutely not, my tool is worst than the original one (it will have more bugs and on windows it doesn't manage drivers for example), that's why you should NOT use it on Windows. I made it work even with Windows because it was very simple to do. You can use it one Windows just to test it if you like, but I recommend using the better original tool MiFlashUnlock.
- Wow, you did a tool already done by developers paid by xiaomi, who is paying for the effort you put into this?
No one, I try to help people and getting appreciation for my work is a bit of a reward to me, but if you want to show your gratitude even more and support me as a developer you can make a donation, I will appreciate that even more (donation link below)
- I have to put my xiaomi account credentials, should I trust this?
I'm the developer of XiaoMiTool, I hope that a little bit of my reputation together with the hopefully good early feedback of reckless users on this tool is enough. If you are more a geek you can track the traffic and see that the only server connected are xiaomi and miui.
- I wanted too see the source of this tool but I see it is a bit obfuscated, why?
Xiaomi clearly doesn't wanted people to see how MiFlashUnlock works (since they obfuscated it a lot), I don't want to disrespect xiaomi decision by releasing the source plain, so I decided to obfuscated it a bit just to make it a bit harder to see (even if my tool is 100 times easier to reverse than the original)
- Can I share this tool?
Of course yes, but I would like you to share it using the xiaomitool.com link (not mega.nz one) so that if I release an update new people will get that and not the old version (there is no tool update enginge built in).
- You're english is not wonderful...
I know, hopefully it is understandable enough
Feedback.
I love feedback, feedback is the best you can do to help me improving this tool. I have not time to answer everybody's questions but I generally read feedback and do my best to make the tool work. If the tool worked or if the tool didn't worked you can write it in the comments, adding additional information like what error you get, what screen you see when the tool get stuck or even what you tried to solve the problem are precious to me. I have not all of xiaomi devices, I fully ested my tool only with two devices (a redmi 4x and a mi note 2) and only on two operating systems (linux and windows), so any new combination could lead to new errors or problems. Please include also your operating system when leaving feedback. Sometimes there are problems on gui which are not on command-line version, so if the tools fails launching or when using gui I suggest trying the command-line version.
Donation: free software is great from users prospective, but developers who spend hours of their time and don't get money for it are more unhappy to develop further free tools, so if you liked the tools and it saved you from the need to do 5000 kilometers to get a windows pc, or from the need to download a virtual machine image with your 32kB internet connection, you can show your gratitude by offering me a tasty, cold beer by clicking the link below
DONATION LINK
Download: you missed the download link at the top? Here it is again:
DOWNLOAD LINK

Fully obfuscated tool. Maybe bloatware or password hijacker

Problems with mi unlock on ubuntu system
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo

The program does not find the phone connected. But "sudo fastboot reboot" work
---------- Post added at 12:03 PM ---------- Previous post was at 11:51 AM ----------
dpvalverde said:
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo
Click to expand...
Click to collapse
Reinstall certs

disconnects phone on checking bootloader status with an error message on top left corner of phone "press any key to shutdown"
and stays stuck after reconnecting in fastboot mode when reading device info.

How to install it on manjaro arch Linux. did u keep it in AUR.?

Status : Success unlock bootloader
Device : Redmi 4X
Waiting Time : 72hours
Thx for the tool . love3 ??????

worked a treat.
had been struggling to use the mi tool for windows and my device was not being detected.
this took me barely a minute to unlock.

Waiting for a fastboot device...
Well, the communication with the 'net seems to work as intended but that is where it stops:
Code:
[18:01:15][INFO ] Starting login procedure
[18:01:24][INFO ] Login procedure succeeded
[18:01:25][INFO ] Checking account unlock permission
[18:01:27][INFO ] Unlock permission confirmed
[18:01:27][INFO ] Waiting for a fastboot device
Using the fastboot command line works for the same user account so this won't be solved by running the tool as root. The device reports itself as 18d1:d00d Google Inc. and shows up clearly when using the fastboot command line tool:
Code:
$ fastboot devices
deadbeef fastboot
(no, my device ID is not deadbeef)
Tried OpenJDK 10 and 9, Oracle JRE 8, no difference.
Digging deeper using strace shows the problem: the 'special' fastboot command you include (in bin/MiUnlockTool_res) is a 64-bit executable while I'm running the tool on a 32-bit machine. Substituting the provided tool for a link to the version already present on this machine makes the command progress to the error:
Code:
$ java -jar bin/MiUnlockTool.jar '[email protected]' 'mysupersecretpassword'
[18:19:25][INFO ] Starting login procedure
[18:19:36][INFO ] Login procedure succeeded
[18:19:36][INFO ] Checking account unlock permission
[18:19:39][INFO ] Unlock permission confirmed
[18:19:39][INFO ] Waiting for a fastboot device
[18:19:39][INFO ] Device connected: deadbeef
[18:19:39][INFO ] Obtaining device info...
[18:19:40][INFO ] Device info obtained
[18:19:40][INFO ] Checking if unlock will erase data and server message
[18:19:42][INFO ] Unlock procedure will erase userdata
[18:19:42][INFO ] Server message: An unlocked device is an easy target for malware which may damage your device or cause financial loss.
[18:19:42][INFO ] Querying unlock server for unlock key
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Anyway, you might want to add a 32-bit fastboot command or just tell users to install a native version and use that.

@YetAnotherForumUser
I see the same error message when I tried to unlock MI 8 (global version bought yesterday in official Xiaomi store in Poland). I tried official Xiaomi tools on Windows 10, but without any success (verify failed at 50%).

I'm using it on a Linux laptop, I get "buffer overflow detected" after "starting final unlock procedure" and then it fails

i have this 2 errors on linux tring to unlocking my redmi note 5 [20:59:38][ERROR ] Unlock request replied with error code 20036
[20:59:38][ERROR ] Error meaning: After %d hours of trying to unlock the device

After waiting 360 hours I was able to unlock my Mi 8 with this tool on my Ubuntu! With official MiFlashUnlock tool I wasn't able to unlock this device on Windows 10. Thanks a lot!

YetAnotherForumUser said:
Code:
...
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Click to expand...
Click to collapse
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.

YetAnotherForumUser said:
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.
Click to expand...
Click to collapse
I also used 64-bit OS -> Ubuntu 18.04 x64. It would be nice to see amount hours instead of %d, however it's just a minor bug. This tool is the best choice for Linux, MacOS and event Windows 10 users.

Hey guys,
Although I've unlocked & rooted other Android's in the past, this is my first time with a Xiaomi device. I've tried running the tool, and appear to get the "Error meaning: After %d hours of trying to unlock the device" error. Am I right in thinking this is just a bug in terms of the hours displayed, and that I will just need to wait the 15 or so days before I can unlock the device? At what point does that 15 days begin?
Also, once unlocked, what is the best way to flash a ROM? ADB via Terminal?
Looking to flash the Global MIUI over the Chinese one I currrently have.
Thanks!

Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected

huynhkhoa said:
Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected
Click to expand...
Click to collapse
Windows or linux ?

naik2902 said:
Windows or linux ?
Click to expand...
Click to collapse
window bro, please help me :crying:

huynhkhoa said:
window bro, please help me :crying:
Click to expand...
Click to collapse
Why r u not using original miunlock tool for windows ?
Did u enable oem unlock, usb debugging?
Installed fastboot drivers
Use fastboot devices command to check if u r device connected to pc.
Did u bind ur account to miunlock status in developer option?