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)
.
The OTA Update:
Your phone will download the OTA update as a zip file in the Download folder.
------------------------------------
The Problem:
------- quote by jackdowsan -------
I downloaded the file, placed it in my zip, went to cwm recovery and tried intall zip from sd card, it failed saying something about signature verification....
What are my options? I am on stock with root and custom recovery..
------------------------------------
The Solution:
I was in the same situation and I've resolved it by extracting the original OTA recovery.img from the OTA Update zip and flashed it through fastboot. Then I've updated the system software successfully and flashed back the ClockworkMod recovery.
If somebody needs a step by step guide, please see below:
WARNING! You may loose your root access after this procedure. Do not worry. You can root it again the same way you did before, or much easily by using the application Voodoo OTA RootKeeper (free, no ads, on the market). Just install it before you start and then again after the process to restore your root access.
1. Send the system software update archive located in your phone's download folder to your PC. Open it and inside you'll find another archive - firmware.zip. Open it and extract the original OTA recovery.img. Put it in the same folder with the fastboot.exe file.
2. On your HTC One X, enable USB debugging by going to Menu>>Settings>>Applications>>Development>>USB debugging and check-mark the box.
3. Turn OFF your smartphone using the Power button.
4. Press and hold Volume DOWN button and then immediately press Power button. Select Fastboot mode from the menu that appears on the screen.
5. Connect your phone to your PC using the USB cable that came with it.
6. Open a Command Prompt Window on your Desktop, go to the folder with your fastboot.exe and then type in the following commands. It will flash recovery on your phone.
fastboot flash recovery recovery.img
7. When the flashing is done, simply enter the following command into Command Prompt Window to reboot your phone.
fastboot reboot
8. You have successfully installed the original OTA Recovery on your HTC One X. Start the phone update again and it'll successfully update to 1.29.401.11. Your job is done!
9. Once everything is completed you can put ClockworkMod Recovery again by following the steps above but instead of using the OTA recovery.img file use the ClockworkMod recovery.img.
Cheers,
P.S. Sorry if this thread is not in the right place. Please move it if it's necessary. I'm still new here
Thanks a ton, would try this today
Just tried it, something did not go right, firtly, I had a little different update file then yours, I had
OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6
which is like 34.5mb or something....
I extracted it and got recovery.img from firmware.zip and followed your guide, but after fastboot reboot, when I entered my phone, I still see it on 1.28.401.9
what could be wrong? I saw the fastboot recovery command executed just fine...what else can it be?
Thanks!
This solution should work on any OTA phone with custom recovery and root access.
So you flashed the OTA recovery.img, restarted the phone and in the normal mode you started the System Software update, right? My phone installed the update with no problems and it was showing the new version. The thing I lost was the root access but I explained how to gain it back.
If an experienced developer is reading this thread they may be able to advise us why the solution did not work with your phone.
Ok, so I used this method to root, http://forum.xda-developers.com/show...&postcount=310
I then took a nandroid immediately after rooting. I then installed the latest version of CWM 6.0.1.3 (I used Rom Manager to install it which may have been my mistake).
I was then going to be in the process of installing a custom ROM so I went to wipe data / factory reset, but it just sat there and did nothing. I then tried to boot and I got stuck at the ASUS screen (second screen after the EEPC pad page thingy). It just sits there.
CWM doesn't recognize anything (can't mount SD card so I can't restore whatsoever.. When I try to restore it says:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
I'm not quite sure what to do next. I obviously messed up somewhere. I'm guessing ROM manager didn't flash CWM correctly. I'm newer to Android and this is only my second device that I'm attempting to flash... not sure what to do. Please help if you can, if not, guess I'll be buying the new google tablet... shouldn't have done this before my trip to hong kong heh.
-----
EDIT: I can't cold boot either
So I can get into APX mode, I downloaded nvflash and ran the download.bat, but still nothing, it just sits at the eee pad screen and does nothing.
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
patmann03 said:
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
I'm guessing this means my version is too new for AXP recovery... darn that's no good. I can't tell what version my transformer is, the sticker on the back is too hard to read (maybe because it's really late), and all of the other stickers I pealed off today... heh.
I tried getting adb to work, but I'm not quite sure how. I believe I have the drivers installed, but I have a feeling I messed up the SD card on my device so much that even adb can't recocgnize it.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ I followed this guide..
Ok, I can get into adb mode and can push items to my device, anyway to restore this way?
Ok, flashed a new recovery. I'm able to access my sd card (external). I found my restore, however, when I went to restore my backup it restored the system, but got an error formatting data...
Used this tool to install new recovery. http://www.androidauthority.com/tra...-3-root-custom-recovery-one-click-tool-97173/
trying to use the same too to unroot...
Get this..
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
3889240415f5497 recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.512550 seconds, 3.9MB/s
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1328 KB/s (4599884 bytes in 3.380s)
Running wolf's exploit...
mv: can't rename '/data/local/tmp': No such file or directory
Going...
ln: /data/local/tmp: No such file or directory
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Ok, this saved my ass. http://forum.xda-developers.com/showthread.php?t=1688012
I had a first generation Galaxy S and was fairly involved in XDA until I traded it in for an iPhone. A few days ago I bought the One X and I noticed there weren't any guides tailored to Mac users on how to flash custom ROMs from a brand new stock device. So here I go. If I have time and get the permission of the developers of the root exploit I might eventually create a mac program that automates the process. Over time I will also try to improve this with screenshots and better instructions. I take no liability if your phone blows up or if it doesn't work for you.
This is just a rough draft, use at your own risk.
Overview
Root the Device
Install Custom Recovery
Install Custom ROM
Directions
Assuming you are on the latest firmware, 2.20, you have to use the X-Factor root exploit. It should be in the downloads folder that you will download below. I did not come up with this expliot so if it works you should donate to its creator. For convenience I bundled the tools you will need into a single zip file. You can download it here. Place the unzipped folder on your desktop. You will also need a custom ROM downloaded from the Android Dev portion of this forum.
Rooting
Back up all data that you would miss if lost.
Open up settings > Developer Options > USB Debugging
Plug your phone into your computer. Do not mount the drive; just leave it in charging mode.
Move the folder you downloaded earlier onto your mac's desktop. Now open a terminal window and type "cd desktop/htconexmac" and press enter.
Now type "sh run.sh" and press enter.
Press enter again when the disclaimer pops up.
If it works, on your phones screen a message should pop up asking for backup restorations as well as a prompt for passwords. Ignore the password spaces and autorize it. It should prompt you twice.
The phone should restart into "bootloader mode." Press the enter button on your computer once this loads and it should confirm that your new CID is "11111111" if it worked. If it doesn't say that then try again from scratch.
Press enter again and you should get a big block of text copy the whole block including the tags on either side of it. You will need this to unlock the bootloader.
Go to htcdev.com and make an account. Now go to htcdev.com/bootloader and in the drop down box select All Other Supported Models press enter and follow their directions.
Recovery
Close terminal entirely (not really necessary, it just makes things go smoother) and reopen it. Now type "cd desktop/htconexmac" and press enter.
Now turn your phone off entirely and turn it back on by pressing the power and volume down buttons at the same time. You should boot back into recovery mode. This time, use the volume keys to select fastboot
With your phone plugged in and USB Debugging still enabled, type "./fastboot.osx flash recovery twrp.img" This will install the TWRP Custom Recovery. I did not make this, if it works for you I would suggest donating to its developer.
When it is done installing you can turn off your phone and then boot back into the bootloader by holding the power button and volume down button at the same time.
Now scroll to recovery and press the power key. You should boot to a screen with lots of buttons.
Flashing the ROM
Press the button that says "Mount" and then press the button that says "Mount USB Storage." In a moment you should see your phone appear mounted as a disk on your computer. Drag the .zip file of whatever ROM you downloaded to this disk as well as the file titled "gaaps.zip." Once they finish copying press "unmount."
Press the back button to return to the main screen and then press the button titled "Wipe"
Do a factory reset. Press back. Wipe the cache. Press back. Wipe the Dalvik cache. Press back twice to get to the main menu.
Press "Install" and then select the zip file on the ROM you want to install. Press "add more zips" and select "gapps.zip." Finally slide to confirm the flash.
When it is done flashing go back to the main menu and press "reboot" and then "bootloader"
Make sure it says "FASTBOOT USB" in red. On your computer find the folder where you kept your ROM and extract the zip file. Find the file called "boot.img" and copy it into the htconexmac file on your desktop.
In terminal type "./fastboot.osx flash boot boot.img"
When it is completed type "./fastbook.osx reboot"
Your phone should boot with its ROM!
nice one bro
BreatheHT said:
nice one bro
Click to expand...
Click to collapse
Thanks. I don't think many people around here use mac though.
Very useful. Before I got my Win8 I felt like Mac users were left out. Still prefer to do things on my Mac when possible. Thanks for posting this
I am glad for the instructions. I just inherited my wife's old Mac Book and it's great to get intro to fastboot with OSX.
Sent from my HTC One X using Tapatalk 2
Thanks bro. I got a Mac and I've been waiting for clear instructions. Ill will give this a shot later today!
HtcOneXda-developers app
azd9 said:
Thanks. I don't think many people around here use mac though.
Click to expand...
Click to collapse
good job, on a mac 2
Very valuable!
Sent from my One X using Tapatalk 2
azd9 said:
I had a first generation Galaxy S and was fairly involved in XDA until I traded it in for an iPhone. A few days ago I bought the One X and I noticed there weren't any guides tailored to Mac users on how to flash custom ROMs from a brand new stock device. So here I go. If I have time and get the permission of the developers of the root exploit I might eventually create a mac program that automates the process. Over time I will also try to improve this with screenshots and better instructions. I take no liability if your phone blows up or if it doesn't work for you.
This is just a rough draft, use at your own risk.
Overview
Root the Device
Install Custom Recovery
Install Custom ROM
Directions
Assuming you are on the latest firmware, 2.20, you have to use the X-Factor root exploit. It should be in the downloads folder that you will download below. I did not come up with this expliot so if it works you should donate to its creator. For convenience I bundled the tools you will need into a single zip file. You can download it here. Place the unzipped folder on your desktop. You will also need a custom ROM downloaded from the Android Dev portion of this forum.
Rooting
Back up all data that you would miss if lost.
Open up settings > Developer Options > USB Debugging
Plug your phone into your computer. Do not mount the drive; just leave it in charging mode.
Move the folder you downloaded earlier onto your mac's desktop. Now open a terminal window and type "cd desktop/htconexmac" and press enter.
Now type "sh run.sh" and press enter.
Press enter again when the disclaimer pops up.
If it works, on your phones screen a message should pop up asking for backup restorations as well as a prompt for passwords. Ignore the password spaces and autorize it. It should prompt you twice.
The phone should restart into "bootloader mode." Press the enter button on your computer once this loads and it should confirm that your new CID is "11111111" if it worked. If it doesn't say that then try again from scratch.
Press enter again and you should get a big block of text copy the whole block including the tags on either side of it. You will need this to unlock the bootloader.
Go to htcdev.com and make an account. Now go to htcdev.com/bootloader and in the drop down box select All Other Supported Models press enter and follow their directions.
Recovery
Close terminal entirely (not really necessary, it just makes things go smoother) and reopen it. Now type "cd desktop/htconexmac" and press enter.
Now turn your phone off entirely and turn it back on by pressing the power and volume down buttons at the same time. You should boot back into recovery mode. This time, use the volume keys to select fastboot
With your phone plugged in and USB Debugging still enabled, type "./fastboot.osx flash recovery twrp.img" This will install the TWRP Custom Recovery. I did not make this, if it works for you I would suggest donating to its developer.
When it is done installing you can turn off your phone and then boot back into the bootloader by holding the power button and volume down button at the same time.
Now scroll to recovery and press the power key. You should boot to a screen with lots of buttons.
Flashing the ROM
Press the button that says "Mount" and then press the button that says "Mount USB Storage." In a moment you should see your phone appear mounted as a disk on your computer. Drag the .zip file of whatever ROM you downloaded to this disk as well as the file titled "gaaps.zip." Once they finish copying press "unmount."
Press the back button to return to the main screen and then press the button titled "Wipe"
Do a factory reset. Press back. Wipe the cache. Press back. Wipe the Dalvik cache. Press back twice to get to the main menu.
Press "Install" and then select the zip file on the ROM you want to install. Press "add more zips" and select "gapps.zip." Finally slide to confirm the flash.
When it is done flashing go back to the main menu and press "reboot" and then "bootloader"
Make sure it says "FASTBOOT USB" in red. On your computer find the folder where you kept your ROM and extract the zip file. Find the file called "boot.img" and copy it into the htconexmac file on your desktop.
In terminal type "./fastboot.osx flash boot boot.img"
When it is completed type "./fastbook.osx reboot"
Your phone should boot with its ROM!
Click to expand...
Click to collapse
it keeps saying my "CID is not 11111111".......
Forget that last post from me.. Lol I got it.
HtcOneXda-developers app
Thanks for this. Was waiting for some clear mac directions before rooting/unlocking!
Awesome. Thank you!
mikeeygee said:
Awesome. Thank you!
Click to expand...
Click to collapse
Excellent write up.
One question, is the XFactor Exploit used on Rogers phones? I seem to remember this was for AT&T models.
Thanks again.
David
dkonkin said:
One question, is the XFactor Exploit used on Rogers phones?
Click to expand...
Click to collapse
It's not needed. Rogers phones can go straight to unlocking via htcdev.
Thanks again.
Plan to put HTC One X back in order tonight.
Numerous lessons learned, thanks to all for the assist.
David
dead link
the 'You can download it here' link is dead, could someone post another please?
so I can use this guide for my s2?
Unlocking the Bootloader is Required! This will erase all data and void your warranty!
Since all data will be wiped it's best to do this immediately after getting the phone. At least unlocking the bootloader.
I won't add a disclaimer, because if you trust some guide from some guy on the internet you should know what that means without being told explicitly.
For me the bootimage method posted on Modaco does not work and apparently others seem to have trouble as well (see the poll at Modaco). And since I couldn't find any guide here on XDA I thought I'd write one. XDA helped me a lot when I got my DHD, so maybe now I can help back.
This is based on soyd's guide at swedroid.se which I used to finally get my phone rooted after some unsuccessful attempts.
The guide is for Windows, but could probably be easily adapted to Linux/Mac by using the appropriate drivers/tools. I followed these steps to successfully root my Moto G (16 GB, german retail, Android 4.4.2, OTA 176.44.1).
Here're the neccessary steps:
Install Motorola and ADB Drivers
Unlock Bootloader
Flash Recovery
Flash SuperSU
Enjoy
Install Motorola and ADB Drivers
Do not connect your phone to your PC just yet.
If you already have ADB drivers and Motorola drivers installed, just skip this step.
Download these files:
Motorola Drivers
ADB Tools (thx to androidpit.info)
mfastboot.exe (only download that file from the G-Drive folder - thx to whoever uploaded it)
Run the MotorolaDeviceManager_2.4.5.exe you just downloaded and install it
Extract the two folders from adb-tools_treiber.zip
Open ADB-Treiber folder and run UniversalAdbDriverSetup.msi
Copy mfastboot.exe to ADB-Tools folder
Now this next part might be optional, but some things might not work without it and there's no real harm so:
Enable USB-Debugging
On your phone, open Preferences
Scroll all the way down to About this phone
Scroll all the way down to Build-Number
Tap 7 times on that entry
You'll get a message "You're a developer now"
Go back and open the new item Developer options
Check USB-Debugging
Connect your phone to the PC
Drivers will be installed and the phone will ask you to confirm USB debugging from that computer
Unlock Bootloader
There are probably lots of guides around, but to have it all in one place, here's yet another one:
!YOU WILL LOOSE YOUR WARRANTY AND ALL DATA BY UNLOCKING THE BOOTLOADER!
Switch off your phone
Hold Volume-Down and press and release Power to boot into Fastboot
A text screen should appear
Connect the phone via USB to the PC
Open a command prompt and browse to the ADB-tools folder you just created
Type:
Code:
fastboot oem get_unlock_data
You'll get five lines of characters, all beginning with (bootloader):
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy all lines into one long string without the (bootloader) part!
You want something like 0A40040192024205#4C4D355631323030373731363031303332323239#BD00 and so on.
Open Motorola Unlocker Site (you need to sign-in)
Copy the string in the box at 6. and press Can my device be unlocked?
A Request my Unlock Key button should appear. Check I Agree to the legal stuff and press that button
Check your mail for the unlock key
In the ADB-tools folder type:
Code:
fastboot oem unlock [I]paste_your_key_here[/I]
The phone should reboot and greet you with a nice warning about you having lost your warranty.
Flash Recovery
Now that the booloader is unlocked you have to flash a custom recovery to be able to flash SuperSU.
Download the CWM image from this post. The file should be named something like recovery-clockwork-6.0.4.7-falcon.img. Copy the file to the ADB-Tools folder you created earlier and rename it to CWM.img
Your phone should still be connected to your PC and have finished rebooting and be in stock ROM.
In the ADB-Tools folder type:
Code:
adb reboot bootloader
The phone should reboot and the bootloader will come up again
To make sure all's working as expected type:
Code:
fastboot devices
You should get a response similar to:
Code:
List of devices attached
TA93005M6V device
To flash the custom recovery, type:
Code:
mfastboot flash recovery CWM.img
On the phone you might get a message about size mismatch, just ignore it. Now you have to enter the newly flashed CWM recovery. Take your phone and:
Press Volume-Down to scroll to the Recovery menu item
Press Volume-Up to select that item (yes, Vol-Up selects)
The phone will boot into recovery
Now is a good time to backup your system.
Press Volume-Down to scroll to Backup and Restore
Press Power to select that item
Press Volume-Down to scroll to Backup to /sdcard
Press Power to select that item
Backup will commence, once it's finished go back to the main menu and select Reboot, then confirm with YES
You phone will reboot into the stock ROM.
Flash SuperSU
Now you can finally flash SuperSU and be done with the whole business.
Download the newest SuperSU and save the file to your phone's SD-Card's root directory. The phone should show up as an MTP device in Windows file explorer.
In ADB-Tools folder type:
Code:
adb reboot recovery
The phone will reboot and once CWM Recovery has come up, use the Vol-Up/Down keys to scroll and Power to select
Select Install zip
Select zip from /sdcard
Select /0
You should find a file like UPDATE-SuperSU-v1.94.zip there.
Select that file, confirm YES and wait for the flashing to finish
Go back to the Main menu and select Reboot, confirm YES
The phone should once again reboot into normal stock ROM operation. To check if all went well, open the app drawer, tap on SuperSU and if no error message comes up... You're done!
I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people...
Please comment if some things should be changed or improved.
Already guide is there general section..
http://forum.xda-developers.com/showthread.php?t=2585755
But you guide is simple and understandable.. So better stick this thread in this section..
Sent from my XT1032 using XDA Premium 4 mobile app
cdma moto g...?
Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked??
unlocking the bootloader worked great but it wont let me flash the recovery
keifus.rahn said:
unlocking the bootloader worked great but it wont let me flash the recovery
Click to expand...
Click to collapse
How you flashed it? Explain the steps you tried..
Sent from my XT1032 using XDA Premium 4 mobile app
bondisback said:
Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked??
Click to expand...
Click to collapse
I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img
keifus.rahn said:
I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img
Click to expand...
Click to collapse
Has anyone found success with a boost mobile variant please?
This was the easiest way for me and I used ROM manager to flash my recovery http://www.theandroidcop.com/how-to-root-motorola-moto-g/
Sent from my XT1031 using XDA Premium 4 mobile app
Remove the Spaces
bur2000 said:
I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people...
Please comment if some things should be changed or improved.
Click to expand...
Click to collapse
I had the same problem at first. When you copy and paste the code on the website it put spaces between the code. There cant be any spaces then it will work. Hoped this helps XD
Thanks
Great guide, I used it to root my Moto G I got today but I had problems with flashing the Clockworld recovery. It simply would not work, said error. But I tried TWRP and it worked. But I also named it recovery.img and used your command but replaced CVM.img with recovery.img. Got rid of ALL of the bloatware. I was stuck at first because I didn't start the command promt inside of the adb tools folder.
Recovery issue
Guys I had a similar issue while flashing the cwm.
When I flash it in the first boot it works, I can enter in the interface and can create a backup or flash one, but after a reboot it do not enter again. I tried entering via fastboot -> Recovery and received the dead android icon with the "No command" message.
Tried installing via PlayStore and had the same result, even with the TWRP.
Any ideas ?