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
Related
Install Drivers:
Download required files HERE
1: Plug in Aria with supplied data cable to install standard drivers
2: Install HTC Sync (we only need this to get appropriate .adb drivers)
3: Install H Boot Driver - Detailed Guide HERE
a: Power down Aria
b: Hold Volume Down button and press Power (this brings you to bootloader)
c: Wait for SD Card diagnostic (about twenty seconds)
d: Plug in Data cable - at this point Windows will say driver didnt install properly
e: Navigate to Device Manager and update driver for Android 1.0
f: Select "Browse Computer for Driver" and open "Android USB Driver" folder and click next
You now have all the Necessary drivers for your new Android!!
Rooting Your Phone
Credit goes to all the great devs at XDA Developers, including Attn1 and shad0wf0x for their great work
With all the Drivers installed you can now Root the phone!!
1: Go into Menu/Settings/Applications/Development and check the box for "USB Debugging"
2: Plug in phone and choose Charge Only, check box for "Dont ask again" and DONE
3: Download and Run unrEVOked Recovery Tool as Administrator(Windows users)
(as per unrEVOked instructions uninstall any s/w that communicates with the phone(ie: HTC Sync, Doubletwist, etc.)
---Follow any on-screen instructions
**It may take a few tries(unrEVOked hates Windows)
**if all else fails, try shad0wf0xs' Ubuntu Live CD method HERE
Congrats!! you have Rooted your phone
Un-Rooting(Restore to factory)
All drivers from above must be installed
1: Official ATT 2.2 Update(NOW Rootable!!! Click ME) or ATT 2.1 Update Download
2: Make sure USB Debugging is checked in Applications/Development(if fail, then uncheck debugging)
3: Run Aria Shipping ROM.exe as Administrator
---Follow on screen instructions, may take up to ten minutes
Install Custom ROM's
Once youre Rooted you can install custom ROM's from Clockwork Recovery;
1: Copy a custom ROM to the SD card
2: Power down phone
3: Hold Volume down key and press Power to enter bootloader mode
4: After diagnostics run, choose "Recovery" from the list and press power button to select it
5: In Recovery menu choose "install zip from SD card"
6: now select "Choose zip from SD card"
7: navigate to the custom ROM and install
**NOTE: Before flashing a custom ROM it is highly recommended you Wipe Data/Factory Reset in Recovery first
it is also good practice to make a Nandroid backup before flashing any custom ROM
Install Custom Font
Credit goes to churapa. Nice work Bro!! Original Guide HERE
**ROOT Is Required for this
**ALWAYS make a Nandroid Backup before attempting any Mods
-Things you will need:
-True Type Fonts(both Normal and Bold .ttf)
-ADB Tool and knowlege of use
-Required Drivers for proper communication between PC and Android
1: Copy both fonts (normal and bold) into folder named Androidfonts
2: Rename fonts to DroidSans and DroidSans-Bold
3: With the phone off Enter Recovery mode by holding Volume Down key and press Power, select Recovery from the list
4: Once in Clockwork Recovery choose "Partitions" and select "mount system"
5: Connect Phone using Data Cable and run ADB Tools in CMD (c:\Android\Tools)
6: now in CMD window enter the following command:
adb push c:\androidfonts\DroidSans.ttf /system/fonts/DroidSans.ttf ENTER
adb push c:\androidfonts\DroidSans-Bold.ttf /system/fonts/DroidSans-Bold.ttf ENTER
7: Now exit CMD, unmount phone in Partitions menu, Go Back, Reboot Phone, Disconnect USB cable
Enjoy your new font!!
NOTE: Respectively you can backup your current fonts by entering the following in ADB:
adb pull /system/fonts/DroidSans.ttf c:\androidfonts\backup
adb pull /system/fonts/DroidSans-Bold.ttf c:\androidfonts\backup
How to Sideload 3rd Party Apps:
(Rooting NOT required for this)
Download SDK Tool HERE
1: Un-RAR Android folder to root directory on PC (ie: C:\ )
2: Open CMD Prompt and type CD\ and hit Enter
3: Now type cd\android\tools Enter
4: Plug in Data cable and choose "Charge Only" on phone (always choose this)
5: Now in CMD prompt enter this command: adb install barcodescanner3.4.apk and press Enter
The SDK tool should install the Barcode Scanner app on the phone. Yay!! Success!!
**You can use this method to install .apk downloads onto the phone. For this demo i had already inserted
the Barcode Scanner app into SDK tools folder. the actual command should read as follows:
adb install c:\path to .apk file (ie: adb install c:\apps\filename.apk)
**I chose this app because you can use it to install other apps by scanning the barcode
found on many HTC App sites.
How to apply ringtones over 300kb limit:
Short story first
I wanted a nice free app to manage files, so i installed Astro File Manager using Barcode app from above.
While moving some files around i discovered the option to set mp3's to ringtone... and it worked!!
This is good because i was not happy to see there was a 300kb limit to ringtones. There may be another
or better way, but this is how i did it
1: Go to Astro app website HERE
2: Scan the Barcode with Barcode scanner app to install Astro Direct link HERE
3: Open Astro, navigate to SD Card\Mobile\Music
4: find the music file you want set to ringtone, Hold on it until menu pops up
5: Select "Music Options", select "Apply as Ringtone"
or if you dont wanna go through all that hassle, install Rings Extended App. Direct Download HERE
How to remove unwanted Stock Apps using SDK:
1: Once your phone has been rooted with Clockwork, boot into Recovery(hold volume down/press power)
2: Open CMD prompt, get to the "android\tools" directory
3: In recovery window highlight "Mount System"
4: Plug in data cable, in CMD type adb remount
5: Now enter adb shell
*you can view the list of apps stored in the phone by entering ls
6: To remove an app enter the following: rm whateverapp.apk, then enter rm whateverapp.odex
(example: rm HtcFacebook.apk ENTER then rm HtcFacebook.odex ENTER)
7: Type ls again to confirn they have been removed, reboot phone.
*NOTE: you may get 0.0dip listed in Widgets menu. simply go into Manage Apps and locate HTC Sense. Open it and "clear data". your display settings will be reset to factory, but it gets rid of the false data.
Stay tuned!! More to come
Nice tut I could easily follow it
Sent from my Liberty using XDA App
Nice post man... way overdue. Hopefully the mods will sticky it and head off a lot of frustrated searches! =)
Nice guide man...you should sticky this and continue to add stuff to it.
works on htc gratia a6380 with hboot 1.00 ? ? ?
thanks
kiko85 said:
works on htc gratia a6380 with hboot 1.00 ? ? ?
thanks
Click to expand...
Click to collapse
Sorry, there has not been any procedure documented for rooting the Gratia with hboot 1.00. If you search this forum you will find some posts and references for things to try, but nothing concrete has been published yet.
Really good post. Very helpful
Sent from my HTC Liberty using Tapatalk
happy you guys like it. the idea is to be very simple and straight forward.
most of the info comes from XDA guides here. i hope an Admin will sticky this so it will be handy for others to use
i recommend to add the guide to Changing the default font of your Aria
http://forum.xda-developers.com/showthread.php?t=869302
Well, that was quick and easy. Thanks!
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Javi97100 said:
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
CMD = command
CMD is the command you type into run (Start - Run) to open a command prompt.
Javi97100 said:
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
If you are using Windows Vista or Windows 7, this is the black command window that allows you to enter commands such as "COPY", "DIR", "XCOPY", etc.
Cool can I get a link to download and install this?
Sent from my Liberty using XDA App
Oops never mind its on the first page
Sent from my Liberty using XDA App
kevina90 said:
i recommend to add the guide to Changing the default font of your Aria
http://forum.xda-developers.com/showthread.php?t=869302
Click to expand...
Click to collapse
done Bro, added a revised version to the main guide
tested it out on my Aria first, everything worked perfectly.
Hey Zed,
You might want to add to the Font section that you can change your LockScreen font using exactly the same method, but the font for the LockScreen is named Clockopia.ttf -- I'm sure anyone who changes their fonts will want that one changed too.
Also, on the pull command to back up your fonts, you need to add a \ after backup. I did it your way and it wrote the fonts into a file called backup. Then each time I entered it again to back up another font, it overwrote the previous one. Maybe the pull commands should also be moved up into the actual instructions instead of a footnote too, in case someone doesn't read all the way through before starting the process. It will be too late if they have already followed the instructions in their current form.
These are just suggestions, not criticism. Love the thread, thanks a lot for creating and updating it!
Thank you so much for this thread. It made rooting my Aria and putting on the latest liberated froyo ROM super easy. I was a root/custom rom virgin before yesterday!
I'd also add a rom list so people can stay updated.
911jason said:
Hey Zed,
You might want to add to the Font section that you can change your LockScreen font using exactly the same method, but the font for the LockScreen is named Clockopia.ttf -- I'm sure anyone who changes their fonts will want that one changed too.
Also, on the pull command to back up your fonts, you need to add a \ after backup. I did it your way and it wrote the fonts into a file called backup. Then each time I entered it again to back up another font, it overwrote the previous one. Maybe the pull commands should also be moved up into the actual instructions instead of a footnote too, in case someone doesn't read all the way through before starting the process. It will be too late if they have already followed the instructions in their current form.
These are just suggestions, not criticism. Love the thread, thanks a lot for creating and updating it!
Click to expand...
Click to collapse
all suggestions are appeciated. good thoughts bro, soon as i have time it will be done
FIRST OF ALL, I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICE! PROCEED AT YOUR OWN RISK!!!
Now that we got that out of the way...
I have noticed that some people`s Marketplaces simply refuse to update by themselves (exactly what happened in my case) and as most of the people visiting this forums are not tech-savvy and simply want a step-by-step guide to get things working, I decided no harm can be done by me posting this info.
Installing Android SDK revision 8
First of all, you will need to have Android SDK (and ADB of course) installed with the drivers ready to go. In order to get the SDK installed go to the official Android website and download the latest revision (r08 at the time I posted this). You can download any of those files, but I prefer using the executable installer so I can make sure everything is at its place. Now, there are two major flaws with this whole process which have almost made me quit the whole process several times, but I got them sorted out and will help you solve them aswell.
FLAW #1: After beginning the installation process, the installer will prompt you to download a JDK (Java Developer Kit) in order to continue installation. Hit the "Visit sun.java.com" button and download the latest Java SE (currently this one). But before proceeding be sure to download the 32 bit one, as the Android SDK only recognises this version. I know it`s not a big deal, but I spent about two hours trying to figure out what the heck went wrong and it became quite frustrating.
Install the JDK, then the SDK. Once Android SDK is done, simply go ahead and launch SDK Manager (you can find it in Program Files\Android\android-sdk-windows\) and when you get to choose the packages to install, simply check "Accept All" and click "Install". Once it`s done, it`s time to download the drivers. Click "Available packages", tick "Third party Add-ons" and under "Google Inc. add-ons" you should find "Google Usb Driver package". Tick it and click "Install". IF YOU GET AN ERROR SAYING THAT PERMISSION WAS DENIED AND YOU ARE UNDER WINDOWS 7, COPY THE WHOLE "Android" FOLDER CONTAINING THE SDK TO YOUR DESKTOP (OR ANY OTHER PLACE) AND REPEAT THE STEPS ABOVE. I know it`s quite rudimentary, but it does its job. Once it`s done, a folder named "google-usb_driver" will be created under Android. Be sure to correctly copy it to the original location in case you had permission issues.
FLAW #2: Ever since Android SDK r08, Google decided to remove the ADB files so now they have to be manually placed in the folder. I have uploaded them for you, so click here to download them. Once downloaded, extract the archive to the "Android\android-sdk-windows\tools" folder.
OPTIONAL: Go to Start Menu, right click on Computer, click Properties. The System window will appear, where you need to go to "Advanced system settings". Once there, click on "Environment variables" and where it says "System variables", look for PATH. Once found, highlight it and click "Edit..." then add the line "C:\Program Files\Android\android-sdk-windows\tools;" at the end. Click "Ok", "Ok" and "Ok", then restart your computer.
Right now everything should be working as expected. Connect your HD2 to the PC via USB and hope for the best. If the drivers are working and it is recognized as a HTC device, open a command prompt and type "adb devices". If you get anything such as "List of devices attached" followed by some code such as "0123456789ABCDEF device", everything is working well. Good job, you just correctly and completely installed Android SDK on your PC!
If not...
Check your device manager and if you see any devices related to your HD2 having problems, simply right click on them and update the drivers with the ones downloaded earlier in the "google-usb_driver" folder then reboot your computer.
We`re all set! ...What now?
The whole process is actually quite simple. First of all, download the new 2.2.6 Marketplace and put it somewhere accessible, such as your desktop. Open a command prompt and enter the following:
Code:
adb remount
adb shell
rm /system/app/Vending.apk
This will basically delete the old Marketplace from your device.
Now go to the folder where you placed the new Marketplace, hold down Shift, right-click and select "Open command window here". A command prompt should pop up at the exact location. Now execute the following command:
Code:
adb push Vending.apk /system/app
And that is it! Now restart your device and try to run your Marketplace, it will load for half a minute or so then it will start normally. Enjoy!
I know this is rather a tutorial for installing the SDK, but I figured it would be useful to let everyone know how I managed to solve my problem. In case I skipped any steps or you notice anything wrong/wish to add anything, please feel free to do so!
If you feel my post has helped you in any way, do not hesitate to hit the "Thank" button!
Reserved post for further mini-tutorials.
At least on my r08 install if you install the platform tools component then adb will be available under the platform-tools directory (moved from the tools directory).
@OP
Did you test this on a non sense build?
This procedure will most likely not work with Cyanogenmod ROMs. That and I'd suggest you give the newest market version (2.2.7) instead. I'm not willing to destroy my ROM again by trying it on CM.
***
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.
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).
[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions
Nice work sub
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list
@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?
slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?
GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command
you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!
No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.
Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
This fixed it! That was a stupid mistake
kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.
I've had several Android devices. That was the easiest root I've ever done.
bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.