Database Info

New clarified method for rooting the HTC Aria (for those who are having trouble)

Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Note: If you're in Linux, you only need to do Step 4, Step 6, and Step 7.
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe".
If you aren't greeted with a failed to fetch URL error, proceed to Step 3. If you did receive this error, go to Settings in the "Choose Packages to Install" window and check "Force https;//... sources to be fetched using http://..."
Close and re-open "SDK Setup.exe".
Step 3.
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 4.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 5.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 6.
This step is optional, but it may prevent an error later on in the process. If you've never formatted your SD card from a computer, remove it from the phone and format it in Windows or OSX with an external card reader. Then place the formatted card back in your phone, but leave the phone off.
Step 7.
Download the updated Root.zip from eugene373's guide: Root the Slide & Other HTC Devices*6/15/2010* How-To Updated 6/29/2010
Now let's get started...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in Linux) (refer to ice3186's post for Mac instructions)
Note: The loop does nothing but show you the connection status of your phone. It's not technically required, but we'll use it in this guide.
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug the USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please)
Step 10.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
Step 11.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)

I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.

okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.

it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.

gtg465x said:
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe"
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 3.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 4.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 5.
Download Root.zip from eugene373's guide: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
Now let's get into it...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding down the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds, until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug your USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold down the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
step 12.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 13.
If successful, you should see Clockwork Recovery and you now have Su & Superuser.apk installed! You can now reboot your phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Click to expand...
Click to collapse
This isn't complete - this just gets you to clockwork and you haven't installed anything yet. You need to add steps to add root acces or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.

Yes! The secret was formatting the sd card outside of the phone. I am now rooted and liberated! Thanks for plugging along with all the advice guys!

modest_mandroid said:
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
Click to expand...
Click to collapse
Really good tips. I hope you don't mind - I am going to link to this to my original thread.

Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog

Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.

attn1 said:
This isn't complete - this just gets you to clockwork and you having installed anything yet. You need to add steps to root or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Click to expand...
Click to collapse
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.

modest_mandroid said:
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Click to expand...
Click to collapse
Excellent troubleshooting tips. I added a note about formatting your SD card to the prerequisites.
ice3186 said:
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
Click to expand...
Click to collapse
Thanks. Added a reference to your post.
attn1 said:
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
Click to expand...
Click to collapse
Noted in the original post.
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
Thanks. Added the workaround.
attn1 said:
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
Click to expand...
Click to collapse
Thanks. Added a note to the top of the prerequisites.

gtg465x said:
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Click to expand...
Click to collapse
In no way, shape or form are you done after set 12.
You need to do more than just get into Clockwork. That alone doesn't root the phone.

gtg465x said:
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
Click to expand...
Click to collapse
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!

I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?

steezee said:
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
Click to expand...
Click to collapse
Dunno if you can reflash the stock recovery again if you replaced it with clockwork, but you can definitely flash the stock ATT rom again. You can download it from HTC's site: http://member.america.htc.com/download/Web_materials/Manual/HTC_Aria_ATT/HTCAriaOriginalShipROM.exe

Banging my head on the wall. Got it to detect device once on loop. Never again after that. Phone shows up in device manager. Formatted 8gb and 2 gb cards several times.
urge growing. ... want to . . break.. . . .. . .random objects. . .

attn1 said:
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
Click to expand...
Click to collapse
Sorry, I should have mentioned that he updated his update.zip.

You guys are right , there are missing step in the tutorial to fully root Aria.
after i get in to the clockwork from the step above. i have to install the custom rom that can be found in the forum.
when i try to install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . the process goes throught but the recovery is still the same HTC blue color recovery screen.
so before you insert your sd card into the phone after you format the sd card. remember to copy the rooted rom into the sd card so when you successfully get into the clockwork. you want to install the rom then your aria is rooted with superuser icon on the application.
after then you do the "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) step .

There are no steps missing from the first post. I rooted my Aria using that method. Just make sure you have the latest Root.zip from eugene's thread. He updated it the other day and if you try to use the older version of Root.zip with this method it will not work.
What you are doing is installing a custom rom, which is fine, but it's not required to root the Aria.

i was trying to get the clockwork to install and it only work after i load the liberated_aria_b003_signed.zip
before i load liberated_aria_b003_signed.zip , it still give me the default HTC recovery screen.
after i load liberated_aria_b003_signed.zip and install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . i get the clockwork screen as the recovery screen .
i still can't get the side loading to show after i follow the step from here
•COMMON:
•Enable USB debugging (settings > applications > development > USB Debugging)
•adb remount
•adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X:
•echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 settings.db
WINDOWS:
•echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON:
•adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
•Reboot phone and sideloading works. (thanks to fluffyarmada)
.

After rooting, screen looks dead.

I received my transformer today and looked on google for how to root it.
I followed these instructions posted by UBRock on androidforums.com: (as I'm new I cannot post outside links, so I copied the instructions at the end)
After step 4a, my TF booted up like it normally would, with the EE pad screen. Then my screen went to what is shown in the attachment.
I'll turn the screen off, and it will turn on and off by itself.
I've googled and haven't found any issues with rooting this device.
Did I just kill this thing in a few hours? I followed every instruction and had no issues until this.
I bought it off amazon if that matters in case I have to return it. I really hope there's a solution, I got it for a vacation I'm leaving for on Monday.
instructions:
I used this to root my Transformer after the official 3.1 update and it works great. Fast and easy!
The only thing you have to do with ADB is to make sure you have adb installed properly on your computer. Everything is done via scripts.
xda-developers - View Single Post - [ROM] Transformer 3.1 pure root
Quote:
Originally Posted by fone_fanatic View Post
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.
1a. Head over to Asus Support/download page for the transfomer
1b. Select your PC's operating system from the drop down box.
1c. Download and install the USB driver, Asus Sync, and EEE Pad Pc Suite (don't think this one is needed but i installed them all when i first got my tf).
Step 2. Verify that you have adb running properly.
Since adb.exe is included in the download, you really don't need the sdk or adb from elsewhere.
2a. connect your tf via USB to your PC after installing the driver and other apps from step 1.
2b. Open Command prompt on your pc (win key+R) and open (and extract) Tf_rootkit_31 (link at bottom of post).
2c. Navigate to /tf_rootkit_31/root_app/ folder from the downloaded and extracted file, drag "adb.exe file to the open command prompt window.
(it should read something like C:\....\tf_rootkit_31\adb.exe)
2d. After the "adb.exe" press space bar and type "devices" (w/o quotes ofcourse) press enter.
If it says "List of Devices attached" and under that a 15 mixed numbers and letters (serial number) followed by device then adb is working!
If NOT, look at the stickies or search on google on getting adb to work on your OS.
STEP 3. Now the fun begins Here we will put the TF in APX mode and install the APX driver.
3a. Shut your TF off and while plugged into your PC, hold the volume UP and Power button until your PC makes that USB device plugged in sound and there is a notification about installing drivers.
3b. Open up the driver install thing in status bar and press on cancel (or whatever it is to get it to stop searching online for the driver).
3c. Open Device manager, scroll down to "Other Devices" (might be named something else in xp or vista) and you should see APX something with a small exclamation mark in a yellow triangle.
3d. Right click it, select "Update Driver Software..." -> "Browse my computer for driver software" -> "let me pick from list ..." -> click next -> "have disk" -> Browse -> navigate to the downloaded tf_rootkit_31 folder, open usbpcdriver folder and select "NvidiaUsb.inf" -> open, and all it to install, Ignore the unsigned error, let it install anyway.
STEP 4. Get to installing! Now your TF should be in APX Mode (if memory serves me right the screen should turn on.
4a. Go to the downloaded tf_rootkit_31 folder and double click on root.bat (on the TF screen it should say something along the line of "...update successful..."
4b. (OPTIONAL) if you want clockwork mod recovery, then go ahead and double click cwm.bat [Follow STEP 6 to update CWM]
4c. Restart TF, once rebooted make sure USB Debugging is enabled (Settings->Applications->Development)
4d. double click root_app.bat (this installs su and superuser.apk via adb, so command prompt will open up and do its adb thing and reboot your TF)
STEP 5. Confirm completion and CELEBRATE!
5a. Open your app drawer up after reboot and check to see if the Superuser app is there, if so install an app that requires root access (root explorer, adfree, titanium backup etc) and once you open it up, if you get a box requesting super user permission the you got it working!
5b. do a naked/underwear dance!
STEP 6. Update CWM recovery!! You will need a microSD card
6a. Go over to the CWM thread and download latest version of CWM recovery
6b. Place that downloaded .zip (DO NOT UNPACK) on your microSD card
6c. power TF off, then hold voume down + power button, when you see white writing in the top left of the screen press volume up and you should now bee in CWM recovery. Use volume up/down to move through the options and power button to select.
6d. Scroll down to "Install zip from sdcard" press power button then select "Choose zip from sdcard" and now it should list what is on your microsd, Scroll down and select the .zip you downloaded (as of this writing latest version is named recovery-3.1.0.1-solarnz-R3-240511-1908.zip)
6e. Follow instructions on screen, should be straightforward. And now your CWM is updated!
Tf_RootKit_31: Megaupload AND dropbox mirror: Dropbox (thanks tharonald1981)
Click to expand...
Click to collapse

well after running the NVFlash back to stock it went back to what it was when i opened the box and seems to be working with no issues. I'm definitely scared to flash again

MoldyPoldy said:
well after running the NVFlash back to stock it went back to what it was when i opened the box and seems to be working with no issues. I'm definitely scared to flash again
Click to expand...
Click to collapse
how did you do this becuase i followed the same instructions as you and all i was left with the the asus startup splash screen but won't boot further..

gtaguy said:
how did you do this becuase i followed the same instructions as you and all i was left with the the asus startup splash screen but won't boot further..
Click to expand...
Click to collapse
I can't post links, but it's the thread "Asus Transformer NVFlash Stock 3.1 Recovery Roms" on transformerforums.com

You guys extracting the 3 img files and putting it in the NVFlash root folder?

after sweating it for alittle while i was able to do as you guys said above.. downloaded the files placed them in the nvflash folder and recovered the system back to original state. Happy to say that im back to 3.1 now i have to work on trying to get the 3.2 pushed ota.. I do think this rom i just pushed into it is not factory original cuase now i can see the post and the 3.1 rom is rooted.. but im just glad to be back up and running with this amazing tablet..

Rooting Stock 2.2 Guide

I just got my hand on a Captivate and decided to root it. Decided to do this write up since the steps are still fresh in my head. Plus, I can resort to this post should I need to root again sometime in the future, hopefully I won't have too. After several hours of searching and reading XDA, here are the steps I took:
WARNING: I can't guarantee this will work for everyone, but this process works for my AT&T Samsung Captivate running Stock Android Froyo 2.2. All the files are linked from various sources and are works of super smart people, at least smarter than I am.
1. Go into the Captivate's Settings > Applications > Development. Check mark "USB Debugging."
2. Download .NET 4 from HERE and install it. Download the Samsung Driver, choose 32bit or 64bit depending on your OS. Unzip the file, run Setup.exe to install the driver. Connect your phone via USB cable to your PC. This should allow your PC to "talk" to your phone.
3. Download THIS 3e Fixer. Turn off your Anti-Virus if you have any. Unzip the file and the run "install.bat" inside. Press any key to run it. After it's done, select "2" to reboot the phone. This will prevent an error from occurring during the rooting process in the next step.
4. Download the OneClickRoot. Unzip it and right click on the file "Galaxy_One-Click_Root.exe" and select "Run As Administrator". Select "One-Click Root". It will reboot the phone. Once it loads to a menu screen, click volume down and select "Reinstall Packages", then press the Power button. It should root the phone and then reboot.
5. Download OCD. Unzip it and run "OneClickDe-cripple.exe", click on "De-Cripple" and the press any key to run it. It will reboot the device when done. This will allow you to install apps or sideload apps from unknown sources.
That is it. Your captivate should be rooted and sideloading apps should work also.

or you could forego all that and just use SuperOneClick to root and enable sideloading.

Pirateghost said:
or you could forego all that and just use SuperOneClick to root and enable sideloading.
Click to expand...
Click to collapse
yea, i tried the OP's method and was getting file signature errors, reflashed and used superoneclick, worked like a charm

A quick tutorial to ROOT Micromax A50 Ninja

Please charge your phone atleast 50% or above before you follow the guide.
I am not providing any screenshots.
Steps:
1. Download all the attached files to this post.
2. Unzip mt65x3 usb vcom drivers.7z and install the drivers.
3. Create a folder in C drive or anywhere you like and unzip SP Flash Tool v2.1134.00.7z.
4. Copy the files MT6573_Android_scatter.txt and boot.img to the folder you created and unzipped the SP Flash Tool v2.1134.00.7z.
5. Open the folder where you extracted SP Flash Tool v2.1134.00.7z and right click on the Flash_tool.exe and run as Administrator.
6. In the Flash tool window, click on File and Open Scatter-loading File and on the pop-up window, select the file MT6573_Android_scatter.txt and click Open
7. A pop-up might appear, click OK and if you see any kind of error, ignore it.
8. A list on the bottom pane should appear of the flash tool window. Uncheck all excet BOOTIMG and click or double click on the BOOTIMG. On the pop-up window, select the boot.img file that you copied earlier and Open.
9. Click on Options of the Flash tool and click USB Mode if not selected.
10. Now you are ready to flash your phone.
11. Switch off your phone and take out the battery. Put your battery back on the phone. Do not switch on. Connect it to your PC with the USB cable without pressing any button on the phone. Now windows should find the drivers and install it. After drivers are installed, unplug the cable from your phone. Take out the battery from the phone and put it back again. Do not switch on.
12. Now on the Flash Tool window click on the Download button. A message will appear on the bottom right of the window 'Please insert USB cable in 14 seconds', with the counter running. While its running, connect your phone to the PC. If you fail to do it, repeat Step 12.
13. When connected properly, you will see a yellow progress bar, after finishing 100% a pop up window will appear saying BOOTIMG downloaded. You are done.
14. Now unplug your phone, take the battery out, put it back and start the phone normally as you do. Let it fully boot. (Nothing should be wrong, cuz nothing happened to mine. I tested it first. Ashik Anwar second.)
15. Enable USB Debugging on your phone and and connect it to the PC.
16. Installing USB ADB Drivers or USB Debugging Drivers:
Unzip usb_driver.zip.
Open 'Device Manager'.
Right click on 'Micromax A50' and click 'Update Driver Software'.
On the new window, click 'Browse my computer for driver software', then click 'Let me pick from a list of device drivers on my computer'.
Click 'Have Disk'.
On the new Pop-up window, click 'Browse' and go to the folder where you previously unzipped the drivers and open the folder usb_driver.
Now select from the list of files 'android_winusb.inf' and click 'Open', then click 'OK'.
Now from the list of 3 options, select 'Android ADB Interface' and click 'Next'.
An 'Update Driver Warning' will appear, click 'Yes'.
Another Warning will appear asking 'Would you like to install this device software.
Click Install.
Now the drivers should be installed.
17. Now unzip unlockroot23.zip and install the unlockroot23.exe and run the program.
18. Now time to root. On the UnlockRoot window, click ROOT and the program will root it. When finished, it will ask you to restart your phone. So switch it off and switch it on again.
19. Now after you have switched on your phone, browse through the Apps Drawer. You should find an application called Superuser.
You are ROOTED!!!
Still check it by installing an app that needs root permissions, like Root Explorer.
Install BusyBox from PlayStore cuz some programs need it for root access.
Thanx to Varun for providing the modified boot.img and thanx to all the developers for their hard work in cracking and hacking Android for the benefit of the people.
To overclock, Install MTK CPU-Control test from PlayStore. Doesnt need root.
You can overclock upto 806MHz. Enable Set on boot.
Overclock To 754MHz for stability issues.
Enjoy folks!!!
EDIT:
If you are getting error while flashing, repeat the steps.
If you are unable to boot, please flash the original_boot.img
Remember to run the Flash Tool as Administrator
Also the UnlockRoot program as Administrator
I am not responsible for the death of your phone

Rooting the micromax a52 aisha
i have read your post, can you post a tutorial to root micromax a52 aisha, and increase internal memory

can you help us to root micromax a56
http://forum.xda-developers.com/showthread.php?t=1791748
We also got boot.img and other files
http://forum.xda-developers.com/attachment.php?attachmentid=1235489&d=1343837004

Pls can this procedure work with all mt6573 chipset phone. Cause I've tried all the major rooting process like superone and it likes.
The phone is TECNO T1.
Thanks in advance
Sent from my TECNO T1 using xda premium

saheb11123 said:
i have read your post, can you post a tutorial to root micromax a52 aisha, and increase internal memory
Click to expand...
Click to collapse
So sorry
Been busy
Read this whole website for anything related to Mediatek processors for flashing.
http://bm-smartphone-reviews.blogspot.in/2011/10/mt65x3-flashing-tutorial.html
You need to have a linux machine, Ubuntu, to unpack the boot.img, making unsecure to 1 and the repack it. Flash it back.
I dont have a linux machine anymore.
Searh the net for tutorials.
Bootloader unsecure.
I dont have the time and also aint using the A50 anymore.
Dont mind
Goodluck.

aydot360 said:
Pls can this procedure work with all mt6573 chipset phone. Cause I've tried all the major rooting process like superone and it likes.
The phone is TECNO T1.
Thanks in advance
Sent from my TECNO T1 using xda premium
Click to expand...
Click to collapse
Procedure is same, but bootloaders are/must be different.
Read http://bm-smartphone-reviews.blogspot.in/2011/10/mt65x3-flashing-tutorial.html
First dump the boot.img
unsecure it.
Flash it back.
for unsecuring, google
busy
no time
cant help more than this
goodluck

Thanks a lot for a wonderful guide

Can this be done from a linux machine? (Ubuntu for e.g.)

[HOWTO] Root Stock i9505G (any version)

This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"

Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe

:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working

hey thanks!!
will give it a try tonight!

Will this work on 4.3?
Sent from my GT-I9505G using xda premium

Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.

ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.

ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.

Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks

Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0

I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver

warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.

Correct.
Etched in blood by a katana

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")

I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.

Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip

occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4