Related
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
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
It's normal. Remove the phone, reboot it and run Revo again. It'll fail each time it tries to reboot but running it again does the stages one at a time. It'll eventually say you have root and do you want to install CWM
It happened with me many time....(NOTE: Do "DISABLE Fastboot" & "ENABLE Debuggin").
Try it again. When it boots into bootloader, you will eventually see on top "S-OFF" and the name "Revolutionary" as well. My Hboot version was totally different from the one mentioned on the "Guide to S-Off,Root,Flash CWM Recovery", But I did Root and flashed few ROM's till now. As soon as you instal CWM, install ROM Manager, Update the CWM and reboot into recovery and make a BACKUP(To be on safeside,as it was useful for me)
Good Luck.
Thanks. Ill keep trying and hopefully itll work eventually like you guys said.
First upgrade to Windows 7 But yeah, like the other 2 two guys said, just keep trying
Sent from my HTC Sensation Z710e using Tapatalk
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
HTC sync was the only way it worked for me, on the the third loss of communication it worked, s off. As others stated, keep trying, it works.
Sent from my HTC Sensation 4G using Tapatalk
Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
Did you check the Post #2 of http://forum.xda-developers.com/showthread.php?t=1192300
icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
Try putting it to charge only, fastboot off and debugging on.
Try it 2-3 times.. eventually it gives s-off. Then you can install recovery by booting the phone & putting PGxx.zip on your sdcard. Then turn off the phone and boot to bootloader (Vol - and power) press vol + when it asks for update.
I had the same problem on the 3VO. When I disabled the fastboot option it worked!!
I was having this problem, USB debug on and fast boot off. No number of resets would cure it.
This is how I solved it, in case anyone is having the same problem:
The application reset the phone a second time, at which point it would get the error, I was left in the boot menu with S-On and a sad expression on my face.
During the first reboot into the boot menu, I quickly selected 'FASTBOOT USB' (I think it was vol down once, then power button). It then started processing the ZIP file before the application could reboot it a second time.
The application will still get the same error, however on your phone, you will now have S-Off.
Disclaimer: I have no idea what I'm doing, as evidenced by my post count of 1. It seems to work fine, but my phone may explode in 30 minutes time, I have no idea.
press power key
when it asks for the fastboot second time, just press the power key once and u will get the s-off
after s-off...how can we push recovery and flash su zip...for root...
sorry guys, but I just can't get this to work. I'm having the exact same issue
as, well a lot of people. "Communications with phone unexpectedly interrupted"
I got a brand spanking new Sensation. (if that could be part of the problem)
I've scowered the internet for a solution and tried just about anything I can find.
- Phone is set to USB debugging.
- fastboot is off
- set to charge only
- sync is uninstalled
- all drivers are installed
I've tried every possible combination of the above as well.
I've tried "when it asks for the fastboot second time, just press the power key once and u will get the s-off"
for the "Try it 2-3 times.. eventually it gives s-off" I just completed my 25th try,
and still no luck.
What the f**k is going on here? I'm no noble prize winner, but I've done
way trickier stuff than this.
any ideas?
Thanks guys,
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Hello Guys,
I solved this issue when I rooted my HTC desire using Unrevoked..
every time the desire rebooted, then the unrevoked said that " Communications with phone unexpectedly interrupted "
What I did is that,
- Phone is set to USB debugging.
- I couldn't find (fastboot) in my mobile, I just forgot about it.
- set the mobile to sync only when connected with usb cable.
- HTC sync is uninstalled from my computer.
- my computer recognize the device when it connected with usb cable otherwise you need to download some drivers (google it).
- then I connected my desire to the computer using the usb cable and start the unrevoked software.
- the unrevoked works and download some files then said that waiting for device to reboot. my device is rebooted.. when the logo of HTC started to appear in my mobile and just before the mobile completely works after rebooting, I have unplugged the usb cable from the desire..
- the unrevoked software still saying that "waiting for the device to reboot and it may take few mintues" !!
- when the desire is completely works and ready to use I have plugged it again to the computer and choose sync mode in very fast way before the unrevoked software detect it.
- then the unrevoked software start to download some files on the deasire and reboot it again for the second time and said that " waiting for device to reboot" .. in same way in have unplugged the usb cable after the HTC logo appears before it completely start and plug it again when the desire is completely working and ready to use and to respond.
- then the unrevoked software downloaded more files and said that " Done successfully" .
When I used this method, I have rooted and flashed my htc desire mobile and It is working fine. I just installed some custom roms on my mobile from the sd card using ClockworkMod Recovery v2.5.0.7 and it is working great..
I hope this will help somebody getting same problem.
Greeting from Saudi Arabia.
Mkman
AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
Thanks alot.I was same problem and done that way....
AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
It applies to Hboot 1:18.0000 as well. However in my case, no amount of plugging and unplugging will fix the problem...
Edit: Solved by running on Win 7, outside of the VM where I usually do my phone stuff with adb installed ect... So not sure if adb was the issue or that the VM is WinXP. Anyway, seems clean install of drivers without adb installed fixed it.
try to install adb, it works
When I was rooting and s-off an htc desire on linux using revolution. It fails every time on "waiting for fastboot...", then exit with "communication with phone unexpe...".
I have adb installed with android sdk. however, i haven't started the daemon. The last time I use "adb devices" to check the connected device, this also enables the adb daemon. Then everything just goes well and i get s-off.
Remember to install adb and start it by executing "adb devices"
icepikk said:
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
Click to expand...
Click to collapse
i had same issue when i was using a VM windows machine, once i tried with a physical win machine it worked like a charm.
I looked through quite a few threads with the "stuck at samsung logo" problem, but none seems to be the same as mine...
I tried several roms (Vegabond, Zeus ZTR for ~2 months, Aeon, Legend 3 for ~2 weeks), and then tried to flash MIUI (specifically MIUI.us.Aries_v4_2.7.20_Eng_Deo_ZipA_Signed_TMT.zip). After installing the zip, I thought I tried reflashing it again for good measure, so I went into advanced / reboot recovery in CWM, and that's when the phone get stuck at the samsung logo.
This seems a bit different than others in that it won't turn off. Holding the power button will shut down, then get back to the same place one second later. Nothing I did can get the phone to anything but the Samsung logo. I decided to just leave the phone plugged in last night, at least to charge the battery. This morning it looks like I can finally get the phone into download mode, but neither Odin nor the Heimdall one-click recognizes the phone (I did install Kies). I start with the battery out, phone unplugged. Then press and hold the v+/v-, plug in USB (the PC blips the "USB sound" a couple of times, but shows the "device not recognized" message), and then insert the battery. As soon as I do that, the phone gets into download mode (ask to press v+ to download or v- to reboot) but the PC then blips the "USB disconnect" sound, and neither Odin nor Heimdall one-click can see the phone. The phone just shows the yellow triangle with andoid shoveling, and on top it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)"
I'd really appreciate any pointers...
fishline said:
I looked through quite a few threads with the "stuck at samsung logo" problem, but none seems to be the same as mine...
I tried several roms (Vegabond, Zeus ZTR for ~2 months, Aeon, Legend 3 for ~2 weeks), and then tried to flash MIUI (specifically MIUI.us.Aries_v4_2.7.20_Eng_Deo_ZipA_Signed_TMT.zip). After installing the zip, I thought I tried reflashing it again for good measure, so I went into advanced / reboot recovery in CWM, and that's when the phone get stuck at the samsung logo.
This seems a bit different than others in that it won't turn off. Holding the power button will shut down, then get back to the same place one second later. Nothing I did can get the phone to anything but the Samsung logo. I decided to just leave the phone plugged in last night, at least to charge the battery. This morning it looks like I can finally get the phone into download mode, but neither Odin nor the Heimdall one-click recognizes the phone (I did install Kies). I start with the battery out, phone unplugged. Then press and hold the v+/v-, plug in USB (the PC blips the "USB sound" a couple of times, but shows the "device not recognized" message), and then insert the battery. As soon as I do that, the phone gets into download mode (ask to press v+ to download or v- to reboot) but the PC then blips the "USB disconnect" sound, and neither Odin nor Heimdall one-click can see the phone. The phone just shows the yellow triangle with andoid shoveling, and on top it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)"
I'd really appreciate any pointers...
Click to expand...
Click to collapse
First thing I suggest is to uninstall Kies, it has been known to cause issues. Second get the drivers back on the computer, you will find them here http://forum.xda-developers.com/showthread.php?t=1610374
thanks to bigjoe2675.
From this point,there is more than one way to do this, my choice is this, because it always works for me http://forum.xda-developers.com/showthread.php?t=1524081 all credit to qkster and Entropy512.
Should you wish to give MIUI another try please post in that thread and I will help.
BTW, it is normal to get stuck on the Samsung screen when you go from GB to ICS. There are instructions posted in the OP of the ICS rom for proper way to flash.
I un-installed Kies and all the other samsung drivers from win7, rebooted win7, re-installed the Infuse driver from ISET thread, rebooted win7 again, then tried connecting the Infuse (battery out, hold v+/v-, plug in USB, then insert battery). Infuse will ask whether to go into download mode, and win7 complained about unrecognized USB device. If I press v+ to go into download mode on the infuse (shows the yellow triangle and "Downloading... Do not turn off Target!!!" message), win7 blips the USB disconnect sound. The Heimdall one-click 1.3.1 shows "Device state: Disconnected" the whole time. Tried it several times with the same result. Any more ideas/suggestions?
Can u get to CWM?
Pony Express said:
Can u get to CWM?
Click to expand...
Click to collapse
Like pony said, ur supposed to get stuck at Samsung logo after flashing ics ROM from GB. Try to hold both volume keys and power button to turn on ur phone. Hopefully this will get u back to recovery, then u just need to flash miui again.
I'm thinking this might b ur problem bc the previous ROMs u mentioned were GB.
Sent from my SGH-I997 using xda app-developers app
fishline said:
I un-installed Kies and all the other samsung drivers from win7, rebooted win7, re-installed the Infuse driver from ISET thread, rebooted win7 again, then tried connecting the Infuse (battery out, hold v+/v-, plug in USB, then insert battery). Infuse will ask whether to go into download mode, and win7 complained about unrecognized USB device. If I press v+ to go into download mode on the infuse (shows the yellow triangle and "Downloading... Do not turn off Target!!!" message), win7 blips the USB disconnect sound. The Heimdall one-click 1.3.1 shows "Device state: Disconnected" the whole time. Tried it several times with the same result. Any more ideas/suggestions?
Click to expand...
Click to collapse
Once you install Kies or any Samsung driver to a port, Heimdall previous device recognition is erased.
If you want to use Heimdall in that specific usb port again, you need to reinstall heimdall drivers.
You can also move the usb cord to a different usb port or try a different usb DATA cord and reinstall the Heimdall drivers
benbos_06 said:
Like pony said, ur supposed to get stuck at Samsung logo after flashing ics ROM from GB. Try to hold both volume keys and power button to turn on ur phone. Hopefully this will get u back to recovery, then u just need to flash miui again.
I'm thinking this might b ur problem bc the previous ROMs u mentioned were GB.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
@Pony_Express: No CWM. Can only get into download mode.
@Benbos_06: I did try volume up & volume down (that's what I meant by v+/v-). If I add the power button to the mix I only get the Samsung logo. If I do any button combo without plugging in the USB, I also get only the Samsung logo. I have to do exactly v+/v-, plug in USB, then insert the battery, to get anything other than the Samsung logo.
@qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
fishline said:
@Pony_Express: No CWM. Can only get into download mode.
@Benbos_06: I did try volume up & volume down (that's what I meant by v+/v-). If I add the power button to the mix I only get the Samsung logo. If I do any button combo without plugging in the USB, I also get only the Samsung logo. I have to do exactly v+/v-, plug in USB, then insert the battery, to get anything other than the Samsung logo.
@qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
Click to expand...
Click to collapse
Okay, I wasn't sure if it was soft bricked or if u still had recovery but were looping.
The device is supposed to b recognized by Heimdall/Odin while it is in download mode. I don't even think my computer showed it being recognized until I started Heimdall then Heimdall recognized it.
I would keep trying with different Heimdall/Odin versions and different combinations of cords and ports or a different computer if that's an option. Even if the computer doesn't show it as recognized try to open the Heimdall one click or Odin to see if it shows the device. For me, it took like afew hours of messing around with different combos of these to finally get it recognized.
The last option is to get a usb jig (believe that's what it is called). They r cheap and r supposed to give u a much better chance of having ur phone recognized. But I would keep trying different ports, cords, computers (if that's an option) first.
Sent from my SGH-I997 using xda app-developers app
qkster is offline but will most likely be back soon. To answer your question @qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? - he is actually talking about the latest Java drivers, you will find his link right under How To Install. After installing, it would be a good idea to restart your computer and then follow the rest of his install instructions. You are in a good place, be patient, you are doing great.
Edit: Just re-read your post - qkster can correct me if this is incorrect- In order for your computer to recognize your phone after you have the drivers installed, you should power the phone on and let it display the Samsung screen. At that point connect your usb cable but do not press volume keys to enter download mode at this time. Once your computer recognizes your phone then you can proceed.
fishline said:
u mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
Click to expand...
Click to collapse
As long as you can get into download mode, you don't really need a jig. It is a handy tool, though. No battery pull. Just plug in the jig.
http://forum.xda-developers.com/showthread.php?t=1524081
Here is the heimdall 1 click uclb3. Read the op a few times. You will need to flash it 2 times...the second time with boot loader checked.
the drivers you mentioned is for odin or samsung..not for heimdall..it has it's own self contained drivers.
Try a different pc or a usb port with a known good usb data cord.
After you run the jar file, look thru the options. you should see option to install drivers - via zadig
Okay man i had the exact same problem
And your right no one has the answer but after a week off research i noticed that its easier to go to an at&t store and get a new one. I was worried that they would find out but they didn't and just gave me a new one
Sent from my SGH-I997 using xda app-developers app
OK. I un-installed the Samsung drivers and reboot the PC. Re-download the Heimdall one-click back to stock jar. Ran it, clicked on "install Heimdall 1.3.1" from the Help menu. It first complained that I have a newer VC++ redistributable than what it tried to install. Closed that dialog, then it ran zadig. With the phone connected and in d/l mode, the "list all devices" option does not find the phone. Tried a different cable and port to no avail.
Moved to another PC (WinXP instead of Win7). The VC++ redistributable installs. Zadig finds an unknown device (which I'm quite sure is the phone), but driver install fails. I guess it really needs to find the SAMSUNG USB composite device? Would I be able to use the "create a new device" menu to force it? If so I guess I need to put in the usb id?
Yoshiikim said:
Okay man i had the exact same problem
And your right no one has the answer but after a week off research i noticed that its easier to go to an at&t store and get a new one. I was worried that they would find out but they didn't and just gave me a new one
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I don't think I have that luxury: I bought the phone used off craigslist about 2-3 months ago. I doubt AT&T would exchange the phone w/o receipt.
fishline said:
OK. I un-installed the Samsung drivers and reboot the PC. Re-download the Heimdall one-click back to stock jar. Ran it, clicked on "install Heimdall 1.3.1" from the Help menu. It first complained that I have a newer VC++ redistributable than what it tried to install. Closed that dialog, then it ran zadig. With the phone connected and in d/l mode, the "list all devices" option does not find the phone. Tried a different cable and port to no avail.
Moved to another PC (WinXP instead of Win7). The VC++ redistributable installs. Zadig finds an unknown device (which I'm quite sure is the phone), but driver install fails. I guess it really needs to find the SAMSUNG USB composite device? Would I be able to use the "create a new device" menu to force it? If so I guess I need to put in the usb id?
Click to expand...
Click to collapse
It's been a while for me but try to install the samsung usb composite device to see it it makes any difference.
The other thing you can try is a newer usb hub (if you have one) between your pc and the phone.
qkster said:
It's been a while for me but try to install the samsung usb composite device to see it it makes any difference.
The other thing you can try is a newer usb hub (if you have one) between your pc and the phone.
Click to expand...
Click to collapse
I've tried it on all USB ports of a third PC with the same result. Tried both USB cable I have (one stock Infuse, the other stock SGS2, look identical). Does it matter exactly when I put the phone into d/l mode? If I leave the phone on the "warning" screen, zadig can see the "Unknown device" but can't install driver. As soon as I press volume + on the phone to go into d/l mode, the "Unknown device" disappear from the list. If I put the phone into d/l mode first before zadig starts, it doesn't even see the "unknown device".
Does anyone know if there's a way to force zadig to install the correct driver? Would that help?
fishline said:
I've tried it on all USB ports of a third PC with the same result. Tried both USB cable I have (one stock Infuse, the other stock SGS2, look identical). Does it matter exactly when I put the phone into d/l mode? If I leave the phone on the "warning" screen, zadig can see the "Unknown device" but can't install driver. As soon as I press volume + on the phone to go into d/l mode, the "Unknown device" disappear from the list. If I put the phone into d/l mode first before zadig starts, it doesn't even see the "unknown device".
Does anyone know if there's a way to force zadig to install the correct driver? Would that help?
Click to expand...
Click to collapse
It has been a while since I had to install heimdall. I keep that specific pc, that usb port and that usb cord sacred.
I install nothing else as I treat this as my infuse life line.
I found a few links that may help:
http://www.thegalaxytabforum.com/index.php?/topic/4757-how-to-use-heimdall/
http://forum.xda-developers.com/showthread.php?t=1113195
http://www.glassechidna.com.au/products/heimdall/
All I can say is persistence pays off.
If not, try Odin...if you use Odin, just remember to reinstall samsung kies device drivers and use a different usb port.
gl
qkster said:
It has been a while since I had to install heimdall. I keep that specific pc, that usb port and that usb cord sacred.
I install nothing else as I treat this as my infuse life line.
I found a few links that may help:
http://www.thegalaxytabforum.com/index.php?/topic/4757-how-to-use-heimdall/
http://forum.xda-developers.com/showthread.php?t=1113195
http://www.glassechidna.com.au/products/heimdall/
All I can say is persistence pays off.
If not, try Odin...if you use Odin, just remember to reinstall samsung kies device drivers and use a different usb port.
gl
Click to expand...
Click to collapse
Thanks very much. I really appreciate your help!
All three links talk about the step where the phone is put into d/l mode and then zadig would find the SAMSUNG USB Composite device for driver installation. That's the step that's not happening for me. If I boot the phone into the download mode warning screen (i.e., before pressing volume up), zadig shows an "Unknown device", and as soon as I press volume up to go into download mode, it disappears from the list altogether.
Tried Odin: doesn't recognize the phone either.
Will keep trying though, and report back if I ever get any where with it.
Having the same exact issue as fishline
I'm glad I could find this thread, because I'm having the exact same trouble as fishline regarding multiple PCs (and multiple USB cables) not allowing me to mount USB storage, and each PC giving me a "USB Device Not Recognized" message. My girlfriend originally had this phone on stock AT&T 2.2 (Froyo). I rooted it, installed CWM Recovery (red), and installed the Serendipity VII rom (I believe this is a GB rom). I had never used Odin or Heimdall, so no rom has ever been "flashed" to this phone. My gf didn't have any trouble with this ROM for some time, including mounting the USB on several occasions.
She then bought an HTC One X, and I got this phone. I immediately upgraded the rom to Dark Knight (Android 4.0.4, ICS?) which screwed up the recovery screen (adding static-y rainbow artifacts and changing the recovery to blue instead of red). To correct the recovery issue, I reverted to AT&T Froyo by using a recovery ZIP. This rom now runs OK, but USB mounting has completely disappeared. I have tried 2 Windows XP desktops and 2 Windows 7 laptops, and 4 different USB cables (including 2 verified data cables) with no success. I have installed Kies, Kies Mini, and just the Samsung drivers by themselves. I even installed Samsung PC Studio due to a suggestion in another thread. No luck at all. Every time I connect the phone to the PC (whether in D/L mode or just from the home screen) I get a "USB Device Not Recognized" message. When I originally flashed Dark Knight, I noticed there was some issue with the naming of the external SD card. I'm wondering, could this issue be related to a bad partition of some kind in the internal memory? And is there any way to fix this without the use of Heimdall or Odin (which I cannot get to work)? I can flash through CWM Recovery just fine (since it's fully fixed now).
If there is still anyone that can give me some suggestions, I would reaIly appreciate it. I can use the phone as is until February, when we're due for another upgrade, but the lack of USB mounting is extremely inconvenient. Thanks to fishline for originally starting this thread, and to everyone that has offered suggestions.
Maybe try this... Good luck !!
http://forum.xda-developers.com/showthread.php?t=1389375
It has worked on various Infuse roms.
Thanks
Pony Express said:
Maybe try this... Good luck !!
http://forum.xda-developers.com/showthread.php?t=1389375
It has worked on various Infuse roms.
Click to expand...
Click to collapse
Thank you for the suggestion. Unfortunately, I am currently on the AT&T stock Froyo rom (rooted with recovery, of course), so I don't think it's allowing me to install the APKs in your link. It says "there was a problem parsing the file" or something similar. I appreciate the help.
Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher
melkhaldi said:
Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher
Click to expand...
Click to collapse
It seems to work fine now... I honestly kept tinkering around, it seems to work now. I wish I could offer a better answer. But I am not sure I am able to remember what I did exactly... it was a bunch of plugging and unplugging, restarts, and lots of prayers.
I had a same problem and similar solution
I believe i had found the solution when I change the USB port from my notebook where I had plug my the USB cable from my smartphone.
Same issue here.. I think it is because of USB 3.0. My laptop don't have USB 2.0 hence fastboot or adb wont detect my device, I was using a USB extender which works as USB hub (2.0) it worked many times before now again facing same reboot on usb connection issue.
hi i have a Samsung galaxy S 4G (SGH-T959V) it has the rom slimsaber
i want to install the stock rom but i cant access the download mode
also doesnt charge while its turn off , but charges fine while its turn on
Vongolazer0 said:
hi i have a Samsung galaxy S 4G (SGH-T959V) it has the rom slimsaber
i want to install the stock rom but i cant access the download mode
also doesnt charge while its turn off , but charges fine while its turn on
Click to expand...
Click to collapse
The charging not being fully functional is not a surprise as SlimSaber is based on Android 4.4 which has problem with the charging for our phones.
The next question is, how are you trying to access download mode?
From what I've heard, a download jig is the way to go. However, I don't have one so I turn off my phone, push both volume buttons in, and, with the other end of the USB cable already in the computer, plug in the USB. Sometimes it doesn't go first time so try it a few times (also can take a couple of seconds). It should bring up yellow warning screen asking if you want to continue. Flash away (assuming you have the right files)!
well i have tried with the button combination like you said , but nothing appears and my computer only says ¨unknown usb device¨ and when i try from the recovery it just reboot.
Vongolazer0 said:
well i have tried with the button combination like you said , but nothing appears and my computer only says ¨unknown usb device¨ and when i try from the recovery it just reboot.
Click to expand...
Click to collapse
Yes, the download mode reboot from recovery not working is a known issue. Fixing it would have probably involved messing with the bootloaders so it wasn't done (if i recall correctly).
Since I'm assuming you're on Windows, have you installed the USB drivers? Also, it would be worth trying a different USB cable and a different USB port if you haven't already. Typically the ones on the back of a desktop are the best. If you have a laptop, trying ports on the other side is recommended.
Can you transfer files from the phone as a mass storage device? Does the phone act as if its plugged in when it is (ie is there a notification to connect storage to your pc?). In Device Manager on your computer, could you please list off any unknown devices. If you have linux, the output of the command "lsusb" would be great (if not, don't worry).