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] D2G won't SBF

okay guys here's my issue. I was flashing over to liberty and I forgot to wipe everything so as liberty was going through its stuff through bootstrap I pulled the battery hoping to stop the process.
HOWEVER, I am not stuck at the "liberty" logo. I have tried to sbf and I am getting....
failed flashing process: Phone (0000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E) phone was disconnected.
Can someone please help me?

I've seen people have sucess with SBF errors by renaming the SBF file, trying a diff comp, and if ya vista or win7 ya have to be running as Admin. Give any of those a try that ya can while I'm looking over google to see if I can find anything more directly relevant to the errors you are getting.

Luckily I still have my x sitting around. I'm using macbook pro with vmware running windows 7. I have sbfed successfully on my x using the same setup.
Sent from my DROIDX using Tapatalk

I should also note that I tried booting into recovery and wiping data and cache still didn't help.
I do have a backup of stock from that I made. However, I just don't think its possible for me to access that backup to restore?
Sent from my DROIDX using Tapatalk

I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.

-Gilgamesh- said:
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
Click to expand...
Click to collapse
I am using rsd 4.9. I tried everything you stated except a new computer.
I have droid 2 bootstrapper installed and clockwork. However, whenever I boot into recovery it keeps bringing me to the stock one so I can't restore. If I can figure out how to restore maybe I would be good?
Sent from my DROIDX using Tapatalk

Likely you got far enough into SBF to erase clockwork. Though you can try pulling you battery during boot while its on the moto logo, and if clockwork is still installed it will then boot directly to it.

Yupp nothing. Stuck at the liberty boot logo where it says "liberty"
Sent from my DROIDX using Tapatalk

I donno then. I would try a diff comp and see if that helps. Or maybe someone else will see this thread and have some other ideas. You may could also try posting directly in the SBF thread, maybe someone with more experance with it will see it there? Just a thought.

Thanks for the help.
If anyone else can help I am all ears!
Sent from my DROIDX using Tapatalk

Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.

OK so im not sure about the Liberty ROM however I have had to SBF when I tried installing Fission 2.4.3 on my D2G.
My process was turning the phone on boot mode. This is done but holding the +- Volume button and then hitting the power button.
Next I got RSDLite 4.9 and lastest drivers from motorola. Next is restart computer! This was important as RSD wasn't finding my phone until I did. Once I restarted ran RSD hooked up the phone in boot mode found the sbf file and hit start. Took about 15 min to finish.
Not sure if this helps.

Rsd is finding my phone no problem right away. I suppose I should try it on a different computer though, one that's running xp.
Sent from my DROIDX using Tapatalk

buryboi said:
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
Click to expand...
Click to collapse
Do you know what driver your talking about or where to find it?

Okay guys I tried doing it on Windows XP and I am still getting the same exact message it wont' re-enumerate.
I am scared beyond belief right now and don't know what to do. If someone can suggest something I would really appreciate it.

Not sure if this helps, but this is what "my device" info says while in rsd lite...
IMEI/ESN/MEID:
N / A
Technology:
N / A
Software Version:
N / A
Flex Version:
N / A
Bootloader Version:
v0x00D011
DRM Version:
N / A
AP Die ID:
14b0001391953a0a0000d8ff0100
BP Die ID:
0000000000000000cd6932890485
AP Public ID:
6df40c77da38d6f01bc27cc2f40c041ee4491ae2
BP Public ID:
040000000500000002000000ffff0000ed153289

If you are on Win7 64 then try the drivers in the attached zip file.
It is the BP passthrough mode that fails at the end of the flash because it needs to load a separate interface to flash the baseband radio partition.
That interface is a Motorola Flash device MDM6600 and not the S-Flash OMAP3460 device.
If you are having trouble with the drivers loading during the flash cycle re enumeration then you can try this trick to get them to load.
Turn off the phone and then power on holding the Volume Up + Power.
The phone will boot to the M Logo and just stay there like it is hung.
It is now in BP passthrough mode and will enumerate as a Motorola MDM6600 flash device and Windows will attempt to load those drivers when you connect the USB cable. Point the New Hardware Found wizard to the folder where you extracted the zip and it should load them. If not, you may have to manually force it to load them in the Have Disk dialog.
Now pull the battery and reboot the phone normally and try flashing in RSD Lite again. You will already have the BP passthrough interface drivers loaded now and it should re enumerate and complete the flash of the baseband(CG5) and reboot the phone at the end. Wait at least a minute after it reboots for all the post boot initializations to complete and RSD Lite should eventually say Pass and allow you to disconnect without the error warning about damaging the attached device.
If none of this works, get an XP box and it will all work without any issues 99% of the time.
Good luck!

Okay... So I downloaded the drivers, connected via USB and it did show up as what you said it would. However, I then ran the sbf and it says "The Motorola AP flash interface could not be found and kept failing.
What do I do?

Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not

nickb2005 said:
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
Click to expand...
Click to collapse
It won't charge in the bootloader until you have software on your phone you need to use another D1 or D2 to charge. Or use an external charger.
If windows isn't working there are ways to flash in linux that usually yield better results.
Sent from my DROID2 using XDA App

[Q] Another Brick Thread - Not recognized by ODIN/ADB??

Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.

I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem

You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.

I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.

I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.

sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.

That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!

Glad to hear it.

[Q] [HELP] Stuck on CWM screen, frozen!

Hey everyone!
So I flashed a ji6 tar through SGS kernel flasher to get 2e recovery. I think it managed to do so successfully because now I have CWM when I boot into recovery. HOWEVER, when recovery pops up it goes to the CWM screen and FREEZES! I cannot select any options including reboot system. I also now cannot startup my phone normally! What can I do? I have ODIN but it won't detect my phone when it's connected (tried this about 20 times). I'm running a mac so I guess there aren't very many options. The only way out of anything int his mess is to pull the battery. SOMEONE PLEASE HELP! My phoen is now useless for all purposes. I tried factory reset, etc. On normal bootup my phone is stuck on the startup screen and never progresses past. Help please!

well odin doesnt run on mac.
search for heimdall. (same thing but for all OS) [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite ...
heimdall / odin use download mode not recovery, you know that right? hard to tell by your message.
Instructions for download mode:
plug USB cable into computer
have phone shut off
hold both volume buttons
plug USB into phone
let go of buttons when you see an android digging "down"
Click to expand...
Click to collapse
or get VMware or another virtual machine and install windows. http://www.utorrent.com http://torrentz.eu/search?f=vmware http://torrentz.eu/search?f=windows+7

THanks for the tips.
I've been using (or trying to) Odin in Download mode but it will not detect my device. Recovery in CWM freezes, 2e recovery leading to the CWM screen is fine but when I hit'reboot now' or startup regularly using the power button, it's stuck on the boot up logo page. But I'm investigating Heimdall hopefully that helps or I am totally at my wit's end! Been working on this for a couple hours using everything I can think of! (And Google and XDA forums of course!)

Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!

NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
Any chance you have access to a Windows based system? I've never used Heimdall, so I can't help you there.
Are you 100% sure you're in Download mode? Yellow shovel guy. Were you using Odin with VMware Fusion or something similar? Try different USB ports if it's a G5 or something, doesn't apply if a Macbook.

Heimdall is open source and it works on all platforms...
It's BETTER!

studacris said:
Heimdall is open source and it works on all platforms...
It's BETTER!
Click to expand...
Click to collapse
I don't doubt that at all. I flash to stock so seldom now that using Odin once ever 3 or 4 months doesn't bother me.

NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
unfortunately i know nothing about heimdall, even though im the one that suggested it. studa! help a man out! i gave you your 900

here is a link to a 1 click heimdall package, which also has a prerooted version i suggest you get that as this a transitory os and rooting is part of the process of getting 2e recovery WITHOUT flashiing a stock kernel that will make your phone unbootable.
if you have connection issues refer to THIS THREAD
once that is completed, refer to THIS THREAD to MANUALLY replace 2recovery.
then to make sure it wasn't a wonky cwm file you had that made it freeze(actually now that i think about it you could use adb to push this to the root of /mnt/sdcard FIRST to see if its the cwm file. adb should work in recovery) grab the attached update.zip

Had a similar situation and had to order the USB jig to get out of it. It is pretty easy to make or if you want an easy (and clean) option, order one. Once you have that, remove the battery, SIM and SD. Reinsert the battery and then insert the USB jig. It will go right into download mode and then from there use Odin to flash it back to stock.

[Q] Nexus S 4G stuck at lock screen

I am working on my husband's phone which is a Sprint Nexus S 4G. Although I have a lot of experience with rooting, flashing custom ROMs and recoveries with my 3D Evo, and previous HTC phones, I haven't worked on his Nexus at all. It is stuck at the "Google" screen with the unlocked icon at the bottom. I can't move the unlock icon, no buttons work, either the capacitive or hard buttons. The only thing I can do is pull the battery. However, I am able to boot into fastboot by using the volume up + power keys. In fastboot, I have the following info:
Product name - HERRING
HW version - REV 34
Bootloader version - D720SPRKE1
Baseband version - D720SPRKE1
Lock state - UNLOCKED
My choices for operations:
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
At the bottom of the screen is says:
USB Control Init
USB Control Init End
If I reboot into recovery, I get the Android with arrow and box, which then goes to a triangle with ! inside.
Also, I didn't unlock his phone, though it shows as unlocked. It is a refurbed, though.
If I plug the phone into any computer, it is sort of recognized, but the data isn't able to be read. I have a netbook with XP Pro and an old version of Android-sdk, a newer netbook with Windows 7 64-bit, and an iMac running Snow Leopard. One of my netbooks is running Ubuntu maybe 10.x. My other netbook has a hosed installation of LINUX Mint 12. In Windows 7, the device drivers downloaded, but my netbook never saw the phone. When I booted it into fastboot on Win 7, it needed Android 1.0 drivers, which were not found on Windows Update. In XP, it saw the drive as empty, ie, gave it a letter, but said to insert a disk. On the old Ubuntu, it shows UMT, but won't see any data on the phone. I can't boot into Mint.
I have talked to 2 Sprint techs. One suggested that the touch screen isn't working. My husband does say that it hasn't been recognizing his touches sometimes, recently. The other tech suggested a hard reset, which I believe would wipe the 16GB onboard flash memory. Am I correct in believing this?
Basically I'd like to get the photos off of this phone. I'm willing to try through adb, even install a newer version of Android sdk on the Win 7 netbook. I'm also going to try using a live LINUX DVD, as well as install an updated version of LINUX onto my newer netbook, replacing the non-working Mint. I'd be willing to flash a custom recovery and ROM, too, if I could do it without losing the photos.
I have spent the last 5 hours on this, searching XDA as well as using Google. If anyone can give me any ideas, I'm willing to try them. Thanks.

Have you tried installing pdanet on your PC? That should give you the drivers.
Sent from my Nexus S 4G using XDA

chappy824 said:
Have you tried installing pdanet on your PC? That should give you the drivers.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
Thanks, I'll try it.
I tried the Win 7 64-bit drivers on my netbook. I installed themuntil it said to plug in the phone. Here's what happened:
After plugging in phone, still had the google screen w/unlock icon.
Pulled battery. Booted to fastboot while connected. @ bottom of screen on phone:
below USB control, STANDARD_SET_CONFIGURATION
@ very bottom of screen:
FASTBOOT STATUS - FAILInvalid Command
On netback: stopped @ installing PdaNet to your phone and hung.
I rebooted the laptop and phone. No new screens or options.

Hmmm.. have you tried flashing a recovery.img? Maybe that's why you can't go into the recovery . I'm not to advanced on these kinda things, just trying to help