so i tried flashing with a new rom and when i restarted the phone it went to the green mytouch3g screen and just hangs there. i tried everything to restore the phone using the android recovery menu by holding the home and power button. but now im left with a phone with no operating system so it wont boot. i dont have a mini SD adapter either so is there any options that i can take to fix it or at least bring it back to stock ROM. thanks
If you have adb you can ums_enable after a format of your card to place an update that way.
how do you do that? im pretty new to this whole thing
Do you have adb installed?
snowmaniac22 said:
how do you do that? im pretty new to this whole thing
Click to expand...
Click to collapse
1. Download the rom you want to flash the phone with.
2. Download androidsdk if you don’t have it installed yet.
3. Copy the rom file to your androidsdk folder to keep things simple.
For example:
C:\androidsdk\tools
Place the rom in the tools folder
4. Once that has been completed, place your phone back into recovery mode.
5. Connect your phone with your usb cable, one side to the phone and the other to your computer usb port.
6. Now go to start/run and type cmd followed by the enter key.
7. Then type c: followed by the enter key.
8. Then type cd androidsdk\tools followed by the enter key. (this will depend on your location of your androidsdk folder.
9. Then type the following to connect to your phone.
10. Type adb devices to start up the services.
11. Type adb remount, followed by the enter key. (This might now work in recovery mode, but I'm use to adding it.
12. Type adb shell, followed by the enter key.
13. While in adb, type mount /sdcard or mount /system, followed by the enter key
14. Now exit from adb
15. Now you should be back in the tools folder of your androidsdk folder.
16. Lets get started with pushing the rom over to your phone.
17. Type adb push rom.zip /sdcard
18. Press the enter key
19. The file should start to copy to your phone.
20. Wait until it completes before moving forward.
21. Once the file has been copied type reboot recovery, followed by the enter key.
22. You should do this to insure that the recovery mode see your new rom.
23. Once back in, simply choose your new rom from the menu options and flash away.
I hope this helps,
*Edit
What he said.
htcclay said:
Boot your phone into recovery and on your command line in adb type
ums_enable
Now your mytouch's sd card should pop up like it normally does when you mount it.
Click to expand...
Click to collapse
lol,
And I've been doing it the long way the entire time.
ttran001 said:
lol,
And I've been doing it the long way the entire time.
Click to expand...
Click to collapse
You know its good to learn your way.
It teaches people rather then the quick fix.
Teach a man to fish....something like that...lol
ok does it make a difference im on a MAC haha i download the tools for MAC but im also using RAv1.2.1G if that makes a difference. i understand the PC side but still on the Mac side so little lost
Not sure on mac. Maybe it's the same?
Sorry
snowmaniac22 said:
ok does it make a difference im on a MAC haha i download the tools for MAC but im also using RAv1.2.1G if that makes a difference. i understand the PC side but still on the Mac side so little lost
Click to expand...
Click to collapse
I only use Linux and windows, but I did find this.
The steps provided in this thread should work once your androidsdk has been setup correctly.
Setup Androidsdk
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)
.
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..
Hi.
i Upgrade my SCH-I800 to CM9. and it works good. and from last week not working. and its stuck it CM logo. so i tired to re installing it.
some how i was tried to boot my Tab back.
so tried below steps
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1. Download the zip and unzip the contents to your Desktop (or where ever you would like). These are stock restore files (DJ11) for Download Mode (Volume down and power) Also download the wpa_supplicant and update.zip. Download all these files to the same directory so they are easy to find. I just use the Desktop.
Step 2. Download Heimdall from Here:
glassechidna.com.au/products/heimdall/
Also just below version 1.1.1 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Step 3. Power off your Tab. With your USB connected to your PC, hold volume down on your Tab, and plug USB into Tab. This will Launch Download Mode. Unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this. At the top you see options. Click “list all devices”, then in the dropdown select Android USB composite device (or whatever it says). Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end. (leaving Tab plugged in and in download mode obviously)
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP!!
Unzip the stock files if you haven’t already.
Now its common sense.
The zImage goes in both the Kernel AND Recovery slot. (they even tell you where things go with little descriptions)
The system.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs
The cache goes in the cache slot.
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED. **Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall-frontend.exe. It will eventually start. Sometimes you just need the right combo of plugging in launching the program…
After you have the files in place click “Start” to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. What this did was return you to STOCK EVERYTHING DJ11. This is necessary to flash the update.zip we downloaded earlier.
After this runs you will more then likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do NOT hold power too long, just long enough to turn it on, then continue holding up volume until you see recovery. WIPE DATA AND CACHE. Tab should boot.
Step 4. You should now be back to 100% stock DJ11, and guess what, you’re still rooted! The next step is to push the wpa_supplicant (For some reason this file makes the update.zip fail) to /system/bin using ADB. If you want, you can get root explorer on your Tab and put the wpa_supplicant on your SDcard. Then, use root explorer to copy this file to /system/bin (its ok to overwrite the one that is already in there). If you don’t want to bother with Root Explorer, do the following. Place wpa_supplicant into your tools folder with ADB.
Tab plugged into PC, with USB Debugging ON from your ADB folder (mine is C:tools) Type:
C:tools: adb push wpa_supplicant /sdcard
C:tools: adb shell
$ su (may need to check the Tab to “allow” permission)
# mount -t rfs -o remount,rw /dev/block/stl9 /system
#cd /system/bin
#cat /sdcard/wpa_supplicant > wpa_supplicant
#exit
$exit
Step 5. Place the update.zip file you downloaded on the root of your sdcard and unplug from PC. Power off your Tab. Boot into recovery. Hold volume up, press and hold power for about 3 seconds then release WHILE still holding up volume until you see stock Android recovery. Apply update.zip from sdcard.
This should start the update process, if it doesn’t reboot on its own, select reboot device from recovery. Once you’ve booted, you will be updated to the newest update from Samsung. Notice Superuser is still in your app drawer. (if it is not don’t panic)
*NOTE If you boot and it requests you to activate and won’t activate, do this to bypass activation. On the screen it asks you to activate use the volume toggle. Press volume up once, volume down twice, volume up three times, and volume down four times. It will then allow you to skip activation.
Step 6. Next we are going to download the Stock rooted images of EC02, and the VOODOO zImage.
We are now going to flash the rooted EC02 files via Heimdall. This will be the same process as Step 3, except we will use the new EC02 files.
Power off your Tab. With your USB connected to your PC, hold volume down on your Tab, and plug USB into Tab. This will Launch Download Mode. Unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this. At the top you see options. Click “list all devices”, then in the dropdown select Android USB composite device (or whatever it says). Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end. (leaving Tab plugged in and in download mode obviously)
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP!!
Unzip the EC02 files if you haven’t already.
Now its common sense.
The zImage (from the zip file, NOT the voodoo zImage you just downloaded) goes in both the Kernel AND Recovery slot. (they even tell you where things go with little descriptions)
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs
The cache goes in the cache slot.
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED. **Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall-frontend.exe. It will eventually start. Sometimes you just need the right combo of plugging in launching the program…
After you have the files in place click “Start” to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. What this did was fix root for EC02.
After this runs you will more then likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do NOT hold power too long, just long enough to turn it on, then continue holding up volume until you see recovery. WIPE DATA AND CACHE. Tab should boot.
*NOTE If you boot and it requests you to activate and won’t activate, do this to bypass activation. On the screen it asks you to activate use the volume toggle. Press volume up once, volume down twice, volume up three times, and volume down four times. It will then allow you to skip activation.
Step 7. This is the final step. Instead of flashing recovery VIA Rom Manager (since the recovery in Rom Manager is not updated to the latest kernel source), we will be flashing @khasmek (aka Boushh from XDA) EC02 VOODOO kernel which will also give us a fully working ClockWorkMod recovery!
Again, we will be using heimdall to flash the zImage we downloaded in step 6 (NOT the stock zImage that was in the zip) Please make sure this file is zImage only on your PC. Flashing anything with an extension (zImage.txt, zImage.zImage, etc) will not take.
Power off Tab and disconnect from PC. Hold volume down and plug into PC to get into download mode. Launch Heimdall-Frontend.exe (drivers should still be installed, if not re-installing the same way from the previous steps will work, but you should not need to do this again). Put your modified zImage in the kernel slot AND recovery and hit start. This will flash a custom kernel AND @khasmek VOODOO recovery! First boot may take a while due to External 4 partition conversion. This is normal. If you bootloop for ANY reason, wipe data and cache. By the way, this kernel is also overclocked to 1.4Ghz. Must use SetCPU otherwise stock speeds of 1Ghz will be default.
*Note: Remember, do not use ROM Manager to flash a recovery or you will have to follow steps 5 on again to restore your Tab (You will have to boot into recovery manually until someone fixes stock ClockworkMod Recovery, I can’t stress enough not to use Rom Manager until you hear otherwise). By the way, these instructions ALSO double as a RESTORATION guide!!! If you get stuck anywhere, past step 5, simply start over at step 5 to recover your Tab. If you get stuck BEFORE step 5, start over at step 1!! Great right?!
-------------------------------------------------------------------------------------------------------------------------------------------------------------
then i sucked step 4.
actually he asked to PUSH wpa_supplicant to /system/bin
first i need to know how it do without booting device. is there way to access Tab internal memory in Download mood or any other way.
Thanks
Purpose: The purpose of this guide is to help collect all information and steps needed to root a Motorola Photon Q 4G LTE and use Clockwork Mod. When I looked for tutorials there were no updated ones that detailed how to do this with the latest android update (as of May 2014) for the Photon. Some steps may have been / were copied from various posts & guides around the internet, again this is just a collection of information.
Goal: A user who just opened his Photon Q 4G LTE and did all the factory updates should be able to get his phone rooted by the end of the guide.
Note: I started this guide but sadly the ribbon cable on my Photon Q 4G LTE broke and I just decided to switch carriers. I never got back to proof reading this guide while it was still fresh in my memory but if anyone sees and issues just let me know.
Unlock the Bootloader:
I unlocked the bootloader because I wanted to install ClockWork Mod and read that you had to. Not sure if you need to do this just for root access. I wanted CWM so that I could create a backup of this phone as is came from the factory so if I want to restore down the road I can. Unlike my Samsung it seems difficult to find the factory software for the Photon Q so this seemed like the best way to get it. Also nice to have the ability to take backups of my phone every so often. Assuming your phone is new I recommend that you also take a factory backup once clockwork mod is on before installing any other apps.
1. Download and install the drivers for the Photon Q from Motorola here ( https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 )
2. Download this ZIP package which contains the tools you need for most of the steps here ( https://od.lk/f/MjRfMjc2MDc1Ml8 )
3. Head over to Motorola’s bootloader unlock site and sign in / register ( https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b )
4. Put your device in fastboot mode by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
5. Unzip and open the folder with the ZIP files from Step 2 and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
6. In the prompt, type “fastboot oem get_unlock_data” without the quotes.
7. You will see 5 or so lines with either “(bootloader)” or “INFO” in front of them. Use notepad or some other basic text editor to paste together the 5 lines of output into one continuous string WITHOUT (bootloader) or ‘INFO’ or white spaces in front of them so your string looks something like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
8. Check if your device can be unlocked by pasting the string in the field on Motorola’s page on their section 6. and click “Can my device be unlocked?” If you have a problem with this most likely the string you pasted in the box has spaces or extra / incorrect characters. Try again.
9. Open the email and get the unlock code. My email ended up in the “Promotion” category inbox instead of my normal inbox so if you don’t see it check in other places such as “Spam”.
10. Put your device in fastboot mode again by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
11. Connect the device to the computer with a USB cable. You'll get a confirmation message on the device to indicate that it's connected.
12. Open the folder with the ZIP files from Step 2 again and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
13. In the prompt, type “fastboot devices” without the quotes and make sure your device shows up.
14. To unlock the bootloader, enter the following in the prompt “fastboot oem unlock UNIQUE_KEY” without quotes where you replace the “UNIQUE_KEY” with the code you received in the email. It is case-sensitive.
15. If the line was entered correctly, you will see a message confirming that your device was unlocked.Install Clockwork Mod:
1. Download the latest ClockWorkMod recovery for the Photon Q from clockworkmod.com/rommanager and place the file in the same folder as the files from Bootloader Step 2. Be careful to select the right image!
2. Connect the Photon Q to the computer via USB.
3. Open the folder with the ZIP files from Bootloader Step 2 again and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
4. Put your device in fastboot mode again by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
5. In the prompt, type “fastboot devices” without the quotes and make sure your device shows
a. If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
b. If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
6. Flash ClockWork Mod recovery onto your device by entering the following command in the prompt “fastboot flash recovery image.img” without the quotes where “image.img” is the full name of the file you downloaded in Step 1.
7. Once the flash completes successfully, reboot the device into recovery to verify the installation by powering off the phone and then holding both “Volume Up” & “Power” simultaneously until you see ClockWork Mod on the screen. From here you can take a backup (recommended) if you want to like I did.
o Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one. Root the device:
1. Boot the Photon Q normally and go to Settings>Developer Options> and enable USB Debugging. You may have to turn on Developer Options as well if they are grayed out.
2. Connect the Photon Q to the computer via USB.
3. Navigate to the folder with the ZIP files from Bootloader Step 2 again open the run.bat file.
4. Press Enter after reading the disclaimer (if you want) and wait for the file to finish running.
5. After it is done you can press enter again to close the prompt and disconnect your phone
6. After the phone reboots automatically you will see a new Super User app in your app list. You are now rooted.
FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.
arrrghhh said:
FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.
Click to expand...
Click to collapse
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!
protivakid said:
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!
Click to expand...
Click to collapse
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .
arrrghhh said:
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .
Click to expand...
Click to collapse
Thanks again! I just used the stock rom but rooted during my brief time with the phone but this will help those who wish to use KK on the Photon.
RISING THIS TREAD FROM THE DEAD!!!
WHO STILL HAS THIS PHONE WORKING??
i blue screened my LG G3 so i pulled this phone off my dash in the bimmer to possibly try to root but it runs so damn slow now. any support will be much appreciated this is by far the most reliable device i ever purchased (400 bucks out the door brand new fml)
i will try to root later this week but big shout out to XDA for all thier threads on android ive been rooting since the
optimus line
cheers!