Database Users

No instant root for Hero under 2.1?

There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?

rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.

Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.

Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!

Ok. I'll try later as the villainrom web site is not reachable now.

rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735

rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.

pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse

Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.

Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?

Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?

If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.

You are the best. Thank you.

Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598

[GUIDE] Root 2.3.3 On a Mac WITH OEM Unlock!

***
If you're looking for a guide on how to root on Windows, there is a fantastic guide here written by W0lv3r1n3!!
***
I know there is a stickied guide for this but it hasn't been updated since 2.3.1 so I decided to update it a little bit just to make things easier for people. Credit for this goes to Amin Sabet and DistortedLoop with a few changes/additions by me.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download this file (http://dl.dropbox.com/u/22368847/adb-fastboot.zip) and unzip it to your desktop (Inside you'll find all the files you need to proceed including "adb", "fastboot", "recovery-clockwork-3.0.0.5-crespo.img", and "su-2.3.6.1-ef-signed.zip").
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery-clockwork-3.0.0.5-crespo.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Some people with new Nexus S' are finding that the file discussed in the following steps does not exist. If you cannot find it but can still reboot into Clock Work Recovery Mod then don't worry, you're still rooted and fine!
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
~~~~~~~~~~~~~~~~~~~~~​
Updated for ICS and included instructions in the zip!
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .

Mods any chance we can get this stickied to replace the old one? There seems to be some confusion about using the old version to root.

Nicely done.

any guides to root 2.3.3 for windows?

J__ said:
any guides to root 2.3.3 for windows?
Click to expand...
Click to collapse
Honestly, its a very similar process. Just download a different version of the SDK and make sure you put the recovery image in the folder of the installed SDK called tools. Then when you get to executing the commands do this:
Code:
cd *remove the asterisks and type the file path to the directory for the tools folder of your SDK folder in program files*
Then remove the
Code:
desktop/adb-fastboot/
and just type the other parts.

jlevy73 said:
Nicely done.
Click to expand...
Click to collapse
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?

im getting this error message "cannot load 'recovery-clockwork-3.0.0.5-crespo.img'"
so stuck on step 6. any advice?
thanks
Also, curious because now I have an unlocked bootloader but nothing else has been done. This shouldn't be an issue I assume.....

I've never heard of someone having that issue. Try the command fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img
Sent from my MattedBlues CM7 Google Nexus S!

kenvan19 said:
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
Click to expand...
Click to collapse
I don't think it's enough but it would make a great add-on to the original rooting for mac thread.

-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.

owlmatt said:
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
Click to expand...
Click to collapse
Did you install the android SDK? I'm a little lost, I'm not sure what could be going wrong...I used this method to root both my and my wife's phones with no issues.

This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.

owlmatt said:
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
Click to expand...
Click to collapse
Oh no! I see where I screwed up in my guide...I'm sorry I see it clearly now...don't know how I missed it before.
instead of
Code:
~/Desktop/androidsdk/tools/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
type
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img

Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.

owlmatt said:
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
Click to expand...
Click to collapse
Okay I have one last idea...I'll grab the link then edit this with the stuff...brb
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.

I AM ROOTED!!! How do I buy you a beer?

owlmatt said:
I AM ROOTED!!! How do I buy you a beer?
Click to expand...
Click to collapse
Haha don't worry about it man! Just glad you're rooted now

Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.

owlmatt said:
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
Click to expand...
Click to collapse
If you really want to do something, I'd suggest buying the XDA Premium app from the market and help support XDA as a whole.

Consider it done.

Android SDK issues

Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files

UntamedDeviance said:
Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files
Click to expand...
Click to collapse
I'm not sure why you'd be running the android.bat file? It's not really required to get things working. I have no idea why the SDK Manager would be hanging, but if you really want to have that, then I'd do a full uninstall of everything, reboot, and then try again. Did you download the SDK from here?
Technically you don't HAVE to install the SDK to get access to the Kindle Fire. You only really need fastboot.exe, and adb.exe, and the Android drivers. All of these are available in a single download via the following post. You also don't have to use the actual utility if you don't want to, although it is actually quite cool and recommended if you are new to this.

sl0ttedpig said:
I'm not sure why you'd be running the android.bat file? It's not really required to get things working. I have no idea why the SDK Manager would be hanging, but if you really want to have that, then I'd do a full uninstall of everything, reboot, and then try again. Did you download the SDK from here?
Technically you don't HAVE to install the SDK to get access to the Kindle Fire. You only really need fastboot.exe, and adb.exe, and the Android drivers. All of these are available in a single download via the following post. You also don't have to use the actual utility if you don't want to, although it is actually quite cool and recommended if you are new to this.
Click to expand...
Click to collapse
Thanks, I appreciate that... I was only trying to run android.bat because it is what SDK Manager first runs when it first boots and that is why SDK won't boot... I have tried a full uninstall, reboot, install, reboot... But I have done this for a while, so I am really comfortable with adb, so I will just get the files there... Thank you for those links.. I will do it that way, something to make it easier for always helps
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha

Rooting Gingerbread 2.3.6 (4.5.141) - The Complete Guide

Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
This may look complicated, but is super easy. If you don't feel comfortable using this method, you can use this automated tool (yes, it works on 4.5.141). It won't be as satisfying, or even feel good. You won't learn anything, but you will be rooted. Download tool here (link in OP is broken).
Pre-work:
1) Read the xda Atrix Beginners Guide (then read it again)! (Link)
2) Download and install 7zip. (Link)
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. (Link)
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
You can simply copy each command and paste in to the command prompt.
If you encounter any errors after entering a command, just ignore and keep going (assuming you entered the command properly).
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down until you see "fastboot".
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
17) Open a terminal emulator, then type "su" and hit enter. You should see "#" if you are rooted. Or, download Root Checker from the Play Store.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Note: If you experience problems with updating superuser after rooting, try going in to Manage Applications and clear Superuser data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Downloads:
My Atrix AFH Folder
*****

Thanksssss
Just want to show my appreciation. Your guide followed step by step worked flawlessly on my atrix. Ive been trying to root this darn thing for about a week and a half with no luck. found your guide and worked perfect first time around. Thanks..
David

Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
upndwn4par said:
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
Remember to click THANKS if this guide helped you!
Pre-work:
1) Read the xda Atrix Noob Guide (then read it again)! Link
2) Download and install 7zip. Link
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. Link.
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down.
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Click to expand...
Click to collapse

RE super user pkg.
aksma said:
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
Click to expand...
Click to collapse
Well for me what happen is down at the bottom he has two links for two of the files you need to zip. in one of those, there is a superuser file. When doing the cmd commands at the end you will end up installing the superuser. The best thing to do which really helped me was to download the command prompt text file, that way you can mimic exactly what you see. Hope this helps.
-David

Thanks David, I just started doing the same. Lets see how it goes.

good luck
aksma said:
Thanks David, I just started doing the same. Lets see how it goes.
Click to expand...
Click to collapse
no problem. Believe me i was in the same position. I must of tried rooting mine like 15 times to no avail ,then i found this thread and it worked.

Worked like a Champ!! Thanks David... Was quick and easy.. ..

excellent
aksma said:
Worked like a Champ!! Thanks David... Was quick and easy.. ..
Click to expand...
Click to collapse
Good deal. So glad i found this thread haha.

Glad I could help!

good one.

Thanks a lot
was so expected that this guide

Going to give it a try
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac

Thanks!
Rooted phone

dmacdog said:
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Click to expand...
Click to collapse
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!

thanks
that was cool!

very usefull!! thank you!

very useful
Sent from my MB860 using xda premium

condor7272 said:
that was cool!
Click to expand...
Click to collapse
Yes it is. Awesome feeling to look in your app drawer and see this:

THANKS!!
upndwn4par said:
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
Click to expand...
Click to collapse
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions

1iJakk said:
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
Click to expand...
Click to collapse
Don't unlock your bootloader if you think you will want official Moto ICS update (major hard brick risk).

Razer Phone 2 Unroot Step by step.

Unroot Razer Phone 2
This is the method that I used, I bought a phone that was rooted (little did I know) custom recovery was not installed on my device, but bootloader was unlocked and the phone was rooted. Disclaimer:I am no expert, i just used this method last night (2/2/2019) the Razer guides weren't the best at step by step so I am compiling what I learned from doing this. I am not responsible if you brick or bootloop your phone. You should also do independent research on XDA etc before you attempt this process so you understand the risks. I invite others that know more than me to correct what I may have missed and I will updated the OP.
Step 1
You need a USB C to A cord similar to the one that came with the phone, but Razer says that they don't recommend you use that one because it is designed for quick charge not data transfer so I used one that I bought on Amazon years Ago.
Step 2 you need to download 3 things:
The stock image that can be found here:https://developer.razer.com/razer-phone-dev-tools/factory-images/
You need to download Android SDK
https://developer.android.com/studio/releases/platform-tools.html
You need to download the drivers:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Also open this https://developer.razer.com/razer-p...02.1384856067.1549140743-333350818.1549140743
Unzip all of these files to a new folder on your desktop call it Razer Phone 2 or whatever.
I also went into the phone tapped build number repeatedly to enable developer options and turned on USB debugging.
On the device, go to Settings > About <device>.
Tap the Build number seven times to make Settings > Developer options available.
Then enable the USB Debugging option.
Step 3 you need to Open this PDF courtesy of Razer:
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
This document loosely tells you how to install the drivers follow through all of the steps they give you
It should be noted you see a reference to “Download Mode” there is no such thing also the easiest way to get to this screen is to turn the phone off plug the USB into the computer with the phone not plugged in then hold volume down and plug the phone into the computer and press the power button holding volume down you should be taken to a screen that looks like this (aka download mode): see the image I attached.
I had an issue when I got to the Have Disk portion once I got to the step I had to drill all the way down to the android_winusb.inf file located inside the usb_driver folder. Once i got that it finally showed me the Android ADB Interface and the following dialogue screens. (if you are scrolling through a screen of Manufacturer -Models looking for something then you are doing it wrong) Once it is installed the device Should not have the Android with a ? on the device manager screen it should now say Android ADB Interface. (this part took me almost 2 hours I got frustrated and had to walk away for a bit so dont give up)
You can test that the drivers have been installed correctly like they say in the document but they left a step out for the not as tech savvy people. The way to do it is to open up a command prompt. You will see the directory that is is pointing to is likely C:\Users\[Insert user Name]. We need to change the directory it is looking at by typing.
Cd C:\Users\[insertusername]\Desktop\razer phone 2\platform-tools
(the command cd changes the directory)
You should see the directory change to be looking specifically at that folder now. Now simply type fastboot devices. The command should run and you should see the serial number of your device in the command prompt. If it does not return this then the drivers are not installed correctly.
(some other guides said you should also run the command adb devices, but I never got that to return anything all it ever told me when i ran it was “List of devices attached” with nothing else.
Step 4
Setting the Environment
Once i got to this step I was a little scared because I have never dealt with this before this allows you to call the ADB commands from the command prompt without having to specify the specific folder these ADB commands are located.
Follow the document referenced above until you get to the step that says click New
Instead we are going to look in the section titled “User Variables for [InsertUsername]
Under this section you will see a variable called PATH click on PATH and click edit. A box should pop up and on the right side it should say New, Edit, Browse, Delete, Move Up, Move Down.
Click on New and specify the folder called platform-tools mine looked like this
C:\Users\[username]\Desktop\razer phone 2\platform-tools
Click on ok the box will close and then click on ok again all the boxes pertaining to the environment variables will close.
Step 5
Test that the environment is set up correctly.
You might remember in step 4 we had to open a command prompt and tell it to look specifically at the platform-tools folder to run the ADB commands. With the environment now set we no longer have to specify the folder to run these commands, we can call them from any directory. To test this open a new command prompt it will likely be pointing to
C:\Users\[Insert user Name]
With the phone still plugged in and in “download mode” and without changing the directory, type
fastboot devices it should return the serial number of the phone if the environment has been properly setup if it has not been properly setup then it will return this error.
fastboot' is not recognized as an internal or external command,
operable program or batch file.
Step 6 (im not sure if this is necessary)
Because I bought my phone used I used rootchecker app to ensure the phone was indeed rooted and “download mode” told me the bootloader was unlocked. I wasnt sure if I needed to unlock the critical partitions, but you will notice in the razer instructions right above flash system image they call for them to be unlocked. I simply opened a command prompt and typed:
fastboot flashing unlock_critical
It said they were already unlocked so I moved forward with flashing the system image.
Step 7
Install the system image
From here I followed the razer instructions when i got to the step:
“Navigate to the unzipped system image directory” you open a command prompt and type
Cd C:\Users\[insertusername]\Desktop\razer phone 2\aura-o-global-2009
What this allows you to do is run the flash_all script.
The flash all script uses the command fastboot which if you remember is in the platform-tools folder this is why we had to add the environment in the previous steps so that once we got to this step the flash_all script could find and run that command. I ran this and had no issues the phone will continue to restart and in the command prompt you will see it pushing all the files to the phone. After about 3-4 minutes the phone was at the Wizard. I continued following the guide to lock the bootloader

Reserved

Duplicate post

my phone is not detected in bootloader mode now. i just want to relock my bootloader and i am stuck now

thank you so much! I was almost giving up trying to fix my phone till i saw your post

LordCandyAndy said:
thank you so much! I was almost giving up trying to fix my phone till i saw your post
Click to expand...
Click to collapse
Same here this post was a god send.

The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.

Thanks for the guide.
flash_all kept failing for me because it wouldn't allow fastboot from the ROM's folder. Copying the contents of my platform-tools (adb) folder into the ROM's folder fixed this issue for me. I'm assuming this is because I didn't set up the environment variables correctly.

Darkann said:
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Click to expand...
Click to collapse
I am having the same issue any help