I had fastboot working on my laptop and have used it a number of times. however, when I upgraded to steves 1.5.1 with new baseband, my laptop recognises my streak and vice versa.
But.... when I try to run any commands, it simply wont work.
I was on o2 21-eu, now im on 00-eu but i want to go back to o2 2.1 so i can install official o2 2.2.
Any ideas would be grately appreciated and i apologise if this has already been answerd in another post.
many thanks.
Are you using Win7 64-bit by chance? I had a horrible go of it with Fastboot until I switched to a 32-bit machine. There might be a way to get it to work with x64, but mine kept showing <waiting for device> until I tried a different PC running Win7 x86.
Hope that helps.
-Rob
robroy90 said:
Are you using Win7 64-bit by chance? I had a horrible go of it with Fastboot until I switched to a 32-bit machine. There might be a way to get it to work with x64, but mine kept showing <waiting for device> until I tried a different PC running Win7 x86.
Hope that helps.
-Rob
Click to expand...
Click to collapse
I use win7 with my 1.51 with no issues at all.
Sent from my Dell Streak using XDA App
Thanks for replying.
I am using windows 7 64. I managed to get fastboot working, and downgraded to o2 2.1. As soon as it booted I got the update notification. and after a reboot all is well.
Thanks again.
Related
For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .
chococrazy said:
For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .
Click to expand...
Click to collapse
Try this, it helped me out today.
Forgot OS is Win7 Ultimate 32bit
*Sigh* Did you try it? Im also on Win 7 32bit.
Darkshneider said:
*Sigh* Did you try it? Im also on Win 7 32bit.
Click to expand...
Click to collapse
I copied and pasted everything already... I currently don't ahve a phoen to try it on to see if it works.
I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.
gizmo0681 said:
I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.
Click to expand...
Click to collapse
yup I had that issue a month back...
If you don't have the HTC PC Sync software on your phone anymore (that was one of the first things I deleted when I rooted my phone), then you can't initiate the correct debug mode with the computer... or it may be because adbd runs as root... but going to fastboot usb mode and then running the RUU will work. and yes, it works on Win7.
Hey guys, I originally posted this question in the unrevoked thread, but figured more people might want to know the answer to this question.
Anyway, is there any known way to obtain and reflash the stock recovery image in the event that we wanted to return the phone for warranty or exchange purposes?
Get the original ROM from here: http://www.htc.com/us/support/aria-att/downloads/
What about for the Evo 4G?
I was torn whether to start a new thread in the Evo 4G section, or just reuse this current one. Obviously, you can tell which one I chose.
Atlas15 said:
Get the original ROM from here: http://www.htc.com/us/support/aria-att/downloads/
Click to expand...
Click to collapse
Doesn't seem to work.. Everytime I launch it, it says 'ERROR [170]: USB CONNECTION ERROR' but my device shows up if I do 'adb devices'
I get the same error when I boot into fastboot, as the website suggests. The phone shows up in 'fastboot devices' but I still get the same error 170.
Any suggestions?
edit: read on the hero forum that the ruu's don't work in win7 for some reason, going to try it in vmware with winxp.
edit2: That did the trick. I was able to flash the stock rom under WinXP Pro 32bit from VMWare, which loaded up the stock rom plus stock recovery. Excellent
modest_mandroid said:
Doesn't seem to work.. Everytime I launch it, it says 'ERROR [170]: USB CONNECTION ERROR' but my device shows up if I do 'adb devices'
I get the same error when I boot into fastboot, as the website suggests. The phone shows up in 'fastboot devices' but I still get the same error 170.
Any suggestions?
edit: read on the hero forum that the ruu's don't work in win7 for some reason, going to try it in vmware with winxp.
edit2: That did the trick. I was able to flash the stock rom under WinXP Pro 32bit from VMWare, which loaded up the stock rom plus stock recovery. Excellent
Click to expand...
Click to collapse
Im going to sound like a total nubbie here.... but how did u get it to work and what VWWare program did u use?
EDIT: SCRATCH that I figured it out...
1. I loaded up bootloader
2. left on fastboot
3. made sure it said fastboot usb by unpluging then replugging in usb
4. flashed stock rom
modest_mandroid said:
edit: read on the hero forum that the ruu's don't work in win7 for some reason, going to try it in vmware with winxp.
Click to expand...
Click to collapse
Worked fine for me on Win7 Enterprise 64bit
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
Problem 1: (trying to get fastboot to work)
I downloaded the latest SDk and used the drivers in there. When I goto "update" my Android ADB driver and point it to the the google usb driver, it tell me to go jump off a bridge.. Though I fail to see how that will make my driver install
Anyway that's where i'm stuck, i've tried replacing the .sys files and blew up my XP blue screen at boot which was awsome..
I'm trialing a Streak to replace my iPhone4, This seamed to be the only phone so far that really WOWed me, that was until I used it, with 1.6 it's no iPhone killer..
I am also a previous HTC Advantage user, so i like big phones...
Any Ideas? Maybe i need the old 1.6 SDK Drivers?
This is all to get FastBoot to work, so i can start installing roms.
Problem 2:
Is there anything that I need to be careful of having an ATT phone over an 02?
try dell's drivers.
I found that using XP I had to install the drivers multiple times for it to register the Android 1.0 or whatever.
I simply used the QDL Tool on my locked-to-contract AT&T Streak 1.6. Like I said, I had to install the ADB drivers multiple times (I think that is their name) for it to finally go through. And then on the 4th time or so, it all went smoothly and I'm now running the "official" 2.2
I did nothing special. Just ran the Tool, installed the drivers, if it failed, I installed the drivers again, and ran the Tool again. I think maybe 4th time of installing drivers was the trick. I don't know what I did differently on the last time, but it worked just fine.
subvecto said:
try dell's drivers.
Click to expand...
Click to collapse
Tried that as well, no dice...
stang393 said:
Tried that as well, no dice...
Click to expand...
Click to collapse
That is strange... I was able to get dell recognized by win7 only via drivers that was installed via dell PC sync software...
Sent from my Dell Streak using Tapatalk
Long story short. I had 2 streaks to update today, my friends and a coworkers. I started with my coworkers and used the QDL tool, it went fine. Proceeded with update 318 which also was fine. When I went to do my friends it kept erroring out. (He got it 2 days ago from best buy if that makes any difference.) I tried reinstalling the drivers, using different ports (reinstalled on those ports), didn't work. Went to fastboot let the driver install there, retried the method, nothing. Once his gets to the part where the phone needs to go to fastboot the charging screen that shows battery percentage comes up and the process fails.
I know this doesn't belong on development, but in general it wont get much action....
Any way to fix this issue with QDL not being able to put this device in fastboot? Remember the first streak worked fine.......
Sent from my Sprint Galaxy Tab
Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App
Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck
Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip
slaydog said:
Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Both devices has 1.6 on them. Yeah, my friends just fails with the tool... boots back fine to 1.6 it's not soft bricked.
carhigh said:
Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck
Click to expand...
Click to collapse
I also tried that! I tried 3 different ports! I'm thinking of trying a different PC.. At his work he has a 32-bit XP system, I ran the tool on a Win7 32-bit.
kantras said:
Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip
Click to expand...
Click to collapse
I'll have to try it with the battery removed completely.
If fast boot was damaged would I still be able to get into it? I was able to get to it fine?
I'll have time this weekend to tinker with it, so we'll see!
He was so bummed that he couldn't get Froyo LOL
Maybe it is just me...
When I picked up my streak, i first updated to 2.1 using Modaco's instructions. Then used clockmod for any future flashes.
It was simple and painless. It seems so many people are having problems / bricking their devices with QDL...
If I can't get ny friends to go ill just push clockwork to it and install 318 that way. If its even possible to flash a .pkg file in clockwork?
Sent from my ADR6300 using Tapatalk
still can't get it!!
Ok. I basically tried everything with this White Streak.
This time I jumped on a 32bit XP box.
Installed the Dell Fasboot drivers that are listed on the StreakDroid site
Installed the Qualcomm drivers as described
Still fails when trying to get ADB.
So I found this link that describes how to get ADB installed, so I followed it.
When I enabled USB debugging on the PC it was listed as 'Dell Streak' under the device manager, so per the link I had to 'Update Driver'. From there I chose 'android_winusb.inf' and the device was now listed as (I think) 'Android ADB composite interface' in the device manager.
Proceeded to run the program again and it still fails!
I told my buddy to go return his white one for a black one as because maybe white ones are an issue?
people are only having driver issues with the tool - no one is bricking their devices. The cases of where someone has actually 'bricked' it has been from internal sd card issues (hardware issues). QDL tools is being used to un 'brick' devices. getting the drivers installed is just a pain in the a$$
Not possible to flash .pkg via anything other than stock recovery.
I sent you a PM back on pocketables too but- leaving the phone sitting in waiting for fastboot while you do all of the below, click the driver thats listed as dell streak and uninstall. It should be listed as ADB composite bridge or something to that effect (cant remember off the top of my head). So once you uninstall, don't let it install it automatically, because it will most likely put it back right where it was. It will hopefully show as an 'Android 1.0' device with the yellow triangle. At that point, right click, update driver, and point it to the adb driver that is in the QDL tool folder. This is the only way that worked for me...
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
yeah, thats where he is failing. The fail point is at 'waiting for adb device', meaning the qualcom driver is installed correctly (since it was able to even get that far) but the adb driver is failing - thus not allowing the tool to push files via fastboot.
jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.
shoman24v said:
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.
Click to expand...
Click to collapse
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.
Kohawk09 said:
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.
Click to expand...
Click to collapse
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!
shoman24v said:
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!
Click to expand...
Click to collapse
hmm - could be the fastboot driver possible. Hop on here, meralias is on and he is a master at the tool http://irc.netsplit.de/channels/?net=freenode&chat=#dellstreak
Hey.... well we got it.
I'll just say this.
Doesn't work with the white one
Worked with a black one
I thought you were crazy about the white ones, but I just read this in another post about flashing a new rom:
Kohawk09 said:
Only way to upgrade the white dell streaks is with the qdl tool. Theres something about them... All other methods just leave you in a boot loop.
Click to expand...
Click to collapse
Of course you are using qdl, but I guess ther must be a difference...
Sent from my Dell Streak using XDA App
Yeah there's something with the white ones. Further research proved it. I found a guide for it but we can't try it now. Black ones are the best to do it with.
Sent from my Sprint Galaxy Tab
any idea where I can find instructions for updating my white streak? I can't seem to get it to work following the streakdroid instructions.
Thanks
when its start fastBoot desconect the usb and continue let me know! sent from my Dell Streak using XDA App
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
Click to expand...
Click to collapse
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
jdelano said:
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
Click to expand...
Click to collapse
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Sent from my SPH-D700 using XDA Premium App
iil said:
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Click to expand...
Click to collapse
umm..yeah three complete different computers?...I don't think thats the case.
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
Click to expand...
Click to collapse
I had this exact problem with my Epic also. I tried rooting my fone too, for like 2 months straight, with no luck... Tried every technique, software, and trick in the book and nothing worked...
2 days ago though, I finally rooted it using this solution:
Forget about trying to "root" it.
Instead, flash the "Stock EB13 Deodexed EXT4 + CW 3.0.0.6" to your fone (search the forum, you'll find it and the thread that explains how to do it).
It's pre-rooted too!
It worked fabulous for me. I am now rooted and well on my way to fully customizing my fone.
Odin is finicky though... I had to switch the usb cord around to several different ports before it recognized my fone. Also, it kept locking up at a certain point in the flashing process, but after moving the image from "Phone" to "PDA" (you'll know what these are once you open up Odin), it worked brilliantly.
Try it, it works!
P.S. Just in case this helps anyone; I should note that originally I upgraded from Eclair to the official unrooted straight from Samsung (before they pulled it) stock Froyo. I loved it, but wanted it rooted.
I read somewhere that it was easier to root it if you reverted back to Eclair first. So I did (search forum for uninstalling Froyo).
And from Eclair, I flashed to the above mentioned rooted and deodexed version of Froyo (EB13).
Hope it helps!
syntax_erorr said:
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
Click to expand...
Click to collapse
Might try looking at the usb on the phone to check for something preventing a good connection; I've read where people have found bent connectors and were able to fix it.
Good luck; that has to be extremely frustrating.
I tried everything like you, multiple cables, multiple computers, EVERYTHING!!!
I finally broke down and took it to sprint and they couldnt even get it to connect or fix the problem so i got a new epic. You might just want to take it back and get another one. Im on my 3rd epic now so that should tell you something about these ****TY phones...