Related
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)
.
So completely randomly my gTab gets stuck in CM7 boot loop when I turn it on. I'm on 1.1BL with CWM recovery running craig gomez's repack ROM. Everything was going great, but then yesterday it just stopped booting and stuck @ boot loop. I just tried to restore an an CWM backup of just "boot" because I didn't want to lose my data, I also tried reflashing the ROM without wiping, same thing, stuck @ CM7 boot animation forever.
When I try to back up the ROM in CWM it says "failed to dump boot" or something and won't back the ROM up.
I don't want to do other stuff to fix this because I REALLY don't want to lose my data for some apps. If I could just get the damn thing to boot once I could run titanium or mybackup but I can't back up the ROM in CWM and can't boot past CM7 animation.
Is there any way I could back up my stuff thru adb without being fully booted or do something in CWM to back it up or somehow get it to boot?
You can see if running a filesystem check on /data and /mnt/sdcard fixes things.
If it does not, then looking at the logs may help identify the cause of the boot loop. Collect logs like this:
1. Power off gTab.
2. Connect USB cable.
3. Run "adb logcat -v time > log.txt" in a cmd.exe window and leave it running to collect logs.
4. Power on gTab.
5. Wait until the system has gone into a couple of boot loops, then kill the running adb logcat to stop log collection.
Post the log.txt here.
rajeevvp said:
You can see if running a filesystem check on /data and /mnt/sdcard fixes things.
If it does not, then looking at the logs may help identify the cause of the boot loop. Collect logs like this:
1. Power off gTab.
2. Connect USB cable.
3. Run "adb logcat -v time > log.txt" in a cmd.exe window and leave it running to collect logs.
4. Power on gTab.
5. Wait until the system has gone into a couple of boot loops, then kill the running adb logcat to stop log collection.
Post the log.txt here.
Click to expand...
Click to collapse
Got it fixed!
I think my SD card was funky, I put a new one in, backed up the whole ROM, did full wipes on everything, reflashed the ROM, then restore only data from advanced restore in CWM and now everything works and I got my apps back!
Thx for your help
So I have the issue where my CWM version is boot looping. I know how to fix it by flashing the CWM roach fix but my SD card directory is not visible either. It's only showing the internal sd card. I unfortunately can not get my transformer driver to install on my pc. The driver that is provided from the asus website isn't working. That and the driver should be showing "APX" i believe, and it's showing "Transformer".
I've done a lot of searching for help and all the recommendations are saying connect it to the computer and use adb to push the file or to create a micro sdcaard directory. Or use nvflash.
Suggestions are appreciated.
And for info, i've used a pc with windows xp, and 2 laptops one with windows 7 and one with windows 8. No luck with the drivers.
same problem, I can't ADB either.
Brand New said:
same problem, I can't ADB either.
Click to expand...
Click to collapse
I'm still actively looking for a fix. I'm trying to see if I boot in linux if I can get the tablet recognized. I'll report back. If you find a fix yourself please share.
I wonder if we flash a new update.zip and just return to complete stock if it'll work?
No, the recovery (if you have the same one I have) is that it is a bug in the recovery that continually boot loops. I have nand and tried to install fresh and it doesn't fix. If you can read your sdcard not your internal memory you can easily just install the fixed roach recovery that doesn't boot loop and that will fix it for you.
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
This helped. Step one was slightly pointless due to the fact that the CWM recovery doesn't read the SD card but the internal storage. But after doing the cold reboot, I loaded the new one, and then followed the steps 1-3 without the exit and it applied with no issue. I'm now on the new touch recovery with no boot loops. Thanks very much for your help.
Yeah I should have pointed out to cold boot first and put the files needed on the internal sd.
Edit above post to show that
How do you coldboot?
Brand New said:
How do you coldboot?
Click to expand...
Click to collapse
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
baseballfanz said:
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
Click to expand...
Click to collapse
Thanks buddy I owe you one.
Thank you guys
thanks
Hi guys, I just registered today, I have been using XDA for a while now, and hadn't created an account. I rooted my asus tf and Flashed CWM and ended up getting the recovery bootloop. Within 10 minutes I had found this post and used baseballfanz suggestion to use terminal emulator, and Flashed the touch Recovery and got out of the bootloop. Now running AOKP on my TF-101 and its smooth as butter. I felt i needed to make an account today just to thank baseballfanz. You guys rock, thanks again.
**EDIT** stryke504, i neglected to thank you as well in my earlier post.
This is what this place is all about. I created an account back in 2007 and just started posting last year for the same reason.
Sick!!!! It worked!!!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
same issue and nothing seems to work.....help
I was caught in a bootloop with CWM 3.2....something or other...couldnt adb. Couldn't cold boot...just clicked and stayed on screen...now I have lost the recovery I did have and feel like I am royally screwed....I am on tf101 b90....so nvflash doesn't work so I read....exactly how screwed am I?
What do you mean? You don't know what recovery you are using anymore?? Have you tried NVflash? Does your computer recognize the tablet?
Sent from my PG86100 using xda premium
thank you
helped fix my problem i was having but i was caught in the terminal and it kept denying root access the way i solved this was to
cold boot
re root using vipermod 4.5 and using option 1
http://bit.ly/Ac63pA
then following the steps with the terminal commands
fully working transformer
baseballfanz said:
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
Click to expand...
Click to collapse
hum, sorry, i don't mean to be slow but im not understanding how i can install from zip (sdcard) if my bad cwm can't read it.
i can cold boot, i can use terminal but how can i flash the files if i need to be in recovery to do it and that recovery won't read the sd?
is it possible to flash from terminal?
thanks,
Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer
Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.
Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed
Sorry,
I posted before your edit showed up--
Glad to hear.
steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.
I've spent 4-6 hours researching and trying things and have become quite familiar with rooting, fastboot, adb, sideload, and various other tools and have many installed & working, so if I make a noob comment or mistake, go easy on me. I did my best to do my own due diligence.
Here's the situation:
Nexus S 4G - stock from Sprint
Android 4.1 as pushed from Sprint
Not Rooted
Debugging Mode not enabled
Launcher, UI, Settings, Apps, etc fail ("has stopped") if they use the UI
Things not requiring UI do start and run
Android boots up normally to the lock screen (I have pattern lock). Apps start up in background fine (Locale, Alarm Clock Extreme, etc). Upon unlocking, I get "Unfortunately, Launcher has stopped." Repeatedly. It won't let me click any apps. I can, however, bring down the notification window. Selecting anything in the notification window fails, with "____ has stopped," including Settings, Messaging, Google Play, etc. When I plug in USB, I see the green Android with the "Turn on USB storage" button, but I can't click it before "System UI has stopped."
Unfortunately, most solutions warn "this will wipe all user data," and I don't have backups of a hundred or more photos and videos of my daughter's first year. So wiping data will be my LAST resort...and even then I may try forensic recovery from a dd image (I work in Computing Security, so have a fairly good technical background).
What I've tried, and result:
Reboot into recovery - I get dead Android with red exclamation
Wipe cache & reboot - no improvement (tried 5-10 times)
Reboot into Safe Mode - no improvement
Push 3rd party launcher - installs, but upon unlocking and selecting Launcher / Go Launcher (.e.g), I get "Go Launcher has stopped."
Fastboot - I get device listed/connected, but most commands cause wipe, so I haven't ventured much further
Calling Sprint and having Jellybean re-pushed to my device - it appeared to push (I saw update status message), but when I rebooted, no apparent difference (maybe it didn't push?)
Add/Remove apps via Play Store - works fine. I can remove apps (and have removed nearly all) and add apps, and they uninstall or install successfully (notification window confirms). But I can't access any newly installed apps due to the "stopped working" window.
Suggestions I can't try:
adb backup/shell/pull etc - my debugging mode is not on and I can't turn it on.
USB backup - can't enable USB Mode, and I don't have an automount capability
fastboot oem unlock - wipes phone
I want to try adb sideload <image>, but I haven't been able to confirm whether this truly wipes the user partition or not. If anyone can confirm, let me know. My phone enters sideload mode via:
1) boot to fastboot (power + vol up from OFF)
2) select recovery
3) at dead android with red exclamation, again press power + vol up and release. Menu appears only after you release.
4) 2nd option is "Apply update from ADB" which puts phone into special adb mode where the ONLY command accepted from your PC is "adb sideload."
Any suggestions on how I may be able to retrieve my photos and videos given this completely borked OS?
Thanks.
You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906
jayjay3333 said:
You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906
Click to expand...
Click to collapse
Thanks for the suggestion, but that requires Debugging Mode enabled. It's essentially a GUI for "adb backup." Unfortunately, I can't get debugging mode enabled in any way known to me yet.
Is anyone out there familiar with the adb sideload command? I'm really curious if sideloading an image into user partition in any way wipes data.
SOLVED - how I saved the baby photos
I thought I'd give a quick post on how I actually was able to recover my baby's photos. I was at my last resort and decided I'd just try to do a dd image of the card after I did a "wipe and factory reset." My hope was that a "wipe" did not actually write 0s over the entire internal SD card, but just erased the FAT. In that case, I figured, if I took a dd image, I could use a tool like Forensic Toolkit or similar file carving tool to carve out .MP4, .3GP and .JPG files.
So I selected the wipe and factory reset, but had my Linux system ready to do the dd IMMEDIATELY upon reboot. I had ALREADY plugged my USB connector into the Linux system. When the factory reset completed, the system booted directly to the "Enable USB Mode?" prompt. I enabled it, and performed a ~14 GB dump. I know this only catches the user partition, but I didn't care about the system partition, and hoped it would be re-allocated in roughly same location as previously (not stomping on my user data). After the dd was complete (about 3 hrs or so), I bit the bullet and just signed into my Google account and had Google Backup "restore settings."
Later, I was using ES File Explorer and noticed all JPGs were still in my DCIM folder. When I browsed with Gallery ALL PHOTOS AND MOVIES were still present! :victory:
I did not have any backup/recovery software installed to the best of my knowledge, except for Google's "settings backup." So my best explanation is that the wipe & factory reset DID NOT wipe my user data. This may be a fluke, or due to me having USB connected during the wipe & reset. Not sure.
Just to be sure we're all talking about the same "Factory Reset," on my stock Nexus S 4G running Android 4.1.1:
- power off phone
- press Vol Up and Power at same time -- you'll get the Bootloader
- select Recovery -- you'll get dead android with red exclamation after a few seconds
- press Vol Up and Power at same time again -- you'll get a secondary menu
- select "wipe data/factory reset"
- select "Yes" from a long list of "No" with one randomly-placed "Yes"
Hope this helps someone down the road...
I also wanted to note about the "ADB sideload" command. It can only be used to push incremental updates to the device--not full images needed to recover from a corrupted OS. I successfully sideloaded the 4.1.1 update (re-applied the 4.1.1 that I was currently running), which included "launcher2.apk" and a couple other launcher components that gave me hope. But when the 4.1.1 sideload completed successfully and I rebooted, launcher was still hosed. The 4.1.2 incremental update hasn't been released by Sprint yet.
That was hell of a read. The Samsung toolbox program you can do a temp boot and mount your SD card. But I'm too late to tell you now sorry.
Sent from my Nexus S using xda app-developers app
A few minutes googling would have told you that adb is set in the build.prop
Code:
persist.sys.usb.config=adb
OR adb with mount external
persist.sys.usb.config=mass_storage,adb
OR adb with mtp, but you need a kernel
persist.sys.usb.config=mtp,adb
Hi Can you tell us the dd command that you have used to dump the data?
My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone
Pavankumarvijapur said:
My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone
Click to expand...
Click to collapse
I wonder if this will work with a Nexus 7 on 4.3-4.4 ota soft brick
This is why rooting unlocking and a custom recovery is so important.
Sent from my XT897 using XDA Premium 4 mobile app