Database Info

Method for 100% factory restore, unrooted.

This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.

thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...

thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.

I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.

this is great info to have. great work.

???
has anyone actually tried this? because my pc dosent recognize phone when i try

bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first

??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks

i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process

I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.

theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.

Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App

I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.

The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.

OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.

If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App

farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx

If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App

Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.

SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here

[Q] Can anyone help me with sbf_flash in a virtual box using ubuntu?

So I made a huge mistake and I tried flash the new Gingerbread for D2 on my D2G. Now everytime I start up my phone it goes right to Bootloader D0.11. I have done as much research as possible in the last few days and the only successful recovery I've read of is by flashing the stock D2G Rom with sbf_flash in ubuntu (RSD lite 4.7 and 4.9 both wouldn't successfully flash. It also gave the bootloader a code corrupt error when it turns on now). So anyways, I used virtualbox to make an ubuntu 10.10 VM so I could sbf_flash my D2G. I installed Ubuntu, installed guest additions, added myself to the vboxsf user group so I could get USB access in my VM, ran sbf_flash in the terminal, the ROM loads up on the computer but then tells me that it's "waiting for phone." I've tried everything that I can think of but I can't get ubuntu to recognize that my phone is hooked up to the USB drive in Bootloader mode. I don't know if there's a Linux driver for the D2G that I couldn't find, I don't know what to do. If anyone could help out it would be a life saver, thanks

not sure about d2g but try this
"Remove battery, reinsert.
Open keyboard and hold the X.
Then while holding x turn the phone on and let go of the power button but keep holding the X
You should get a little green android. Now let go of everything.
Now push the volume up and down at the same time. A blue menu should come up allowing you to clear cache and wipe/restore. "
for anyone who has trouble getting through bootloop problems

Nothing is going to help him except flashing an actual D2G sbf to the phone!
You can't flash an SBF for a D2 to a D2G no more than you would flash a microwave firmware into a Refrigerator!
He screwed up his radio because the SBF expects a CDMA radio and the D2G has a Hybrid CDMA/GSM
Impatience sometimes leads people to do very dumb things!

Registered just to reply.
gdfnr123 said:
not sure about d2g but try this
"Remove battery, reinsert.
Open keyboard and hold the X.
Then while holding x turn the phone on and let go of the power button but keep holding the X
You should get a little green android. Now let go of everything.
Now push the volume up and down at the same time. A blue menu should come up allowing you to clear cache and wipe/restore. "
for anyone who has trouble getting through bootloop problems
Click to expand...
Click to collapse
Yeah, doesn't work.
The phone boots straight to the bootloader and due to failed gingerbread install, well, it removes a lot of the core pieces of the D2G's boot process(aka, it has no more recovery mode available).
RSD-lite also fails at BP passthrough.
Anyway, to the OP;
After going through the past, ehhh, 4 hours or so trying to get this to work, I'm going to just say that you're not going to get it to work via virtualbox. Whenever I tried to connect the phone via USB and have it recognised in the virtual machine, virtualbox would either 1. Outright crash or 2. Give an error on connecting it.
You're going to need to burn the ubuntu .ISO to a disc and use it as a livecd and do everything off of it. Which, honestly, isn't that bad.
I used directions off of here, replacing with the .sbf from here.
For whatever reason I couldn't completely copy over the .sbf via USB, so I just downloaded while on the livecd.
In any case, I can confirm it works, which is great.

Boygloyd said:
So I made a huge mistake and I tried flash the new Gingerbread for D2 on my D2G. Now everytime I start up my phone it goes right to Bootloader D0.11. I have done as much research as possible in the last few days and the only successful recovery I've read of is by flashing the stock D2G Rom with sbf_flash in ubuntu (RSD lite 4.7 and 4.9 both wouldn't successfully flash. It also gave the bootloader a code corrupt error when it turns on now). So anyways, I used virtualbox to make an ubuntu 10.10 VM so I could sbf_flash my D2G. I installed Ubuntu, installed guest additions, added myself to the vboxsf user group so I could get USB access in my VM, ran sbf_flash in the terminal, the ROM loads up on the computer but then tells me that it's "waiting for phone." I've tried everything that I can think of but I can't get ubuntu to recognize that my phone is hooked up to the USB drive in Bootloader mode. I don't know if there's a Linux driver for the D2G that I couldn't find, I don't know what to do. If anyone could help out it would be a life saver, thanks
Click to expand...
Click to collapse
The free version of Virtualbox does not support usb. VMware Player-free and supports usb (and better than Virtualbox imo). I can't post the link do a search for VMware Player 3.0.

[Q] Help with Recovery/Reboot Problem

Hi Guys,
I have the TF101 tablet and anytime I try to reboot it just stays at the first boot screen with the "Eee...." screen. Forever. If I hold down power and vol-down then hit vol up, it just stays there saying its booting recovery image but never changes. If I hold down volume long enough it comes to the factory reset/cold boot screen, if I choose cold boot it will boot.
I have rooted the tablet and had no problems previously, was able to flash roms and whatever else I wanted to do. Also, when I plug the tablet into my Windows XP machine, it does not detect the tablet in any way.
Tablet info:
Android Version: 4.0.3
with 2.6.39.4 kernel
I don't remember what rom its running exactly but I know its a version of ICS

Did you use ROM manager to update your CWM version? This sounds exactly like that, you can try running the bootloop-fix in my PERI tool (link in my signature) to fix, or manually run roach2010's fix found in his latest recovery thread. You definitely need ADB working, otherwise you'll need to Nvflash. (Nvflash Wheelie link is in my signature as well)

You are probably right i very well could have done so in rom manager. Im on vacation and dont have access to a pc right now but am going to try ur tool when i get back. Thx for the info
Sent from my Transformer TF101 using xda premium

Wait. I just realized. My pc doesnt even respond when i plug my tab in. How do i run PERI?
Sent from my Transformer TF101 using xda premium

Cold boot and install the drivers.

Ok Thing o Doom, you've been great pointing me in the correct direction, however I need some more guidance.
I have installed ADB, and when I cold boot the device and run adb devices I get nothing.
HOWEVER, if I just reboot the tablet, when it's stuck on the EEE screen, I do adb devices and it shows 123456789ABCDEFG.....
My computer doesn't see the tablet when it's plugged in otherwise, nor does any other windows PC in the house. Do you have any guidance as to what I can do? Please help, I need to get this thing running right.

You just need to get to a state where adb is recognized, and 'adb shell' command works.
From that point PERI should work.
Reboot when it prompts you to if it doesn't automatically (Probably won't being stuck on logo)

I can't seem to get anywhere else. My pc recognizes the tablet at the first boot screen but adb shows it as inactive. When I cold-boot the tablet it boots and loads fine but ADB nor any PC recognizes that it's plugged in. I'm lost.

Is "Enable USB Debugging" Checked in Developer Options?

Won't boot, won't connect to windows.

So I've been running Vegan-TAb GingerEdition 7.0.0 (using clockworkmod I don't remember the version) for a year or so and decided I was going to upgrade. I plugged the USB into my Win7 64bit PC and it told me it was unsupported please format. I of course wasn't going to let Windows format it and since I had upgraded ton Win7 since I had last connected the tablet I figured that was the issue. I started searching the forums on how to fix this and the tablet died. I figured I had just forgot to plug it in so I did and let it charge. When I went to turn it back on later, I got past the birds then to the Vegan-Tab loading screen. It would come on, flash, then go blank, come on again flash and repeat a total of 9 times, then just go blank. The PC recognizes it as there but when I try to open the drive it says "Please insert a disk into removable disk H:". I've tried installing the usb drivers through the SDK, it seemed successful, but I still get the Please insert disk. I then tried the USB drivers suggested by the nVflash thread and still nothing.
Any suggestions? Should I try a Linux machine? I've searched around and haven't found anyone else with this same problem.

GreenMan1976 said:
So I've been running Vegan-TAb GingerEdition 7.0.0 (using clockworkmod I don't remember the version) for a year or so and decided I was going to upgrade. I plugged the USB into my Win7 64bit PC and it told me it was unsupported please format. I of course wasn't going to let Windows format it and since I had upgraded ton Win7 since I had last connected the tablet I figured that was the issue. I started searching the forums on how to fix this and the tablet died. I figured I had just forgot to plug it in so I did and let it charge. When I went to turn it back on later, I got past the birds then to the Vegan-Tab loading screen. It would come on, flash, then go blank, come on again flash and repeat a total of 9 times, then just go blank. The PC recognizes it as there but when I try to open the drive it says "Please insert a disk into removable disk H:". I've tried installing the usb drivers through the SDK, it seemed successful, but I still get the Please insert disk. I then tried the USB drivers suggested by the nVflash thread and still nothing.
Any suggestions? Should I try a Linux machine? I've searched around and haven't found anyone else with this same problem.
Click to expand...
Click to collapse
You might have to nvflash the tablet back to factory stock ROM for BL 1.2 and then upgrade the rom to VeganTAB 7.1 from their site.
When you set your tablet in apt mode ( power and the + volumn buttom, the 3 birds will display and then screen goes blank, that is
normal) and plug it to the PC, the PC should make a sound then you are ready to do a nvflash.
http://viewsonic-gtablet-for-dummies.webs.com

tsukaza said:
You might have to nvflash the tablet back to factory stock ROM for BL 1.2 and then upgrade the rom to VeganTAB 7.1 from their site.
When you set your tablet in apt mode ( power and the + volumn buttom, the 3 birds will display and then screen goes blank, that is
normal) and plug it to the PC, the PC should make a sound then you are ready to do a nvflash.
Click to expand...
Click to collapse
I've already tried that, it didn't work.

Clockwork mod is still working. I've been holding power and vol - not vol+ I feel dumb. Hopefully I don't have to factory reset.

[Q] Hard Bricked my Nexus, possibly?

After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.

sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.

Yeah, it's strange. Did you find a solution yet, by chance?

sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.

Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.