Hi,
I have spent the last 6 hours trying to downgrade my 2.05 phone to 1.31.
Gold card, hack for legend, etc all works and went by smoothly. The major bump is getting the damn 1.31 to install. I keep getting error 171 and 170 saying there is a USB error; connect cable. I am running 32bit Windows 7.
- I have downloaded the RUU twice, it is the right size and works.
- I have tried the unplug/replug/no unplug and executing the RUU but it fails and gives the 170/171 error again.
- I have downloaded the whole SDK/Eclipse/USB driver and tried using them instead for ADB
- I have tried updating through HBOOT but getting error 170 again
- I have (this is getting repetitive) tried the unRevoked universal HBOOT usb driver but no success
- I tried installing HTCSync drivers but fail once again
- I have done countless reboots of both the computer and phone between drivers, correctly uninstalled them with device manager, etc
I don't know what else to do and noticed a ton of people had the same issue but solved it using with the above steps. None works for me.
Any ideas? I'll donate beer money at some future date if this can be sorted out. I need to root and get Froyo cos its just too slow right now.
Believe it or not, it is upgrading now! To whoever has the same problem, just follow the above steps, spend six hours scratching your head, keep the phone over 30%, and there you go. No idea why it worked! Case closed.
i had to go through similar experience! usb is recognized without any trouble when the rooting is done through linux / mac
Yeah it's weird, doesn't seem to be any logic to it. I got it all working now anyways and running froyo with 767 MHz overclock. After figuring out how yo use rom manager, clockwork flash and getting gapps on there I am never returning to sense. Stock android is just so much more streamlined, fast, and no-frills. I even like the keyboard better. Yay.
Related
i have tryd two different ways to do this from the unlockr way to the unrevoked way. no luck yet. i am a newbie but i am technically savvy. i build computers as a hobby and this is killing me.
the unrevoked way i am getting stopped by the fact i have RUU .6 i have tryd to downgrade to .5 with no luck, usb error 170. yes i have proper drivers installed and my device is findable everywhere it needs to be on my pc..device manager recognizes the htc drivers. i am running win7 x64
i really want to flash this phone so it can be usable performance wise...i am forking out a small fortune to buy the evo4 because this phone is so laggy...please sumone help...
The first time I rooted I used the unlockr method with no issues...what OS version you running on the hero
Sent from my HERO200 using XDA App
boydroid said:
The first time I rooted I used the unlockr method with no issues...what OS version you running on the hero
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
i have 2.1 os, build # 2.27.651.6, so i cant get SU app, and when i try to downgrade via the RUU .5 version i keep getting usb error 171...i have tryed every different thing i can think of to make it work to no avail...
i even tryd the older flashrec way last nite and it wont work either...when i click the back up button it says it cant find....and yes i follow everyone of the tutorials to the letter...i just come to a point in all of them where my phone doesnt take the next step...
another way i have tryd
it never gets to this step either...just kinda stalls out and doesnt ever produce this:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
You can't root this version 2.27.651.6, which you said you have, you must have version 2.27.651.5 to root, so download that build, and reload it first, then you can root easily.
Slovak65 said:
You can't root this version 2.27.651.6, which you said you have, you must have version 2.27.651.5 to root, so download that build, and reload it first, then you can root easily.
Click to expand...
Click to collapse
well i have tryd to do just that...i get a usb 171 error message everytime...the bootload waiting to load gets to about 80 seconds then i get the error message...so its not for lack of trying...nothing else i have tryd works and have no idea how to get my hero back to older version...
Run RUU let the 171 error appear. LEAVE THE PHONE AT THE HTC SCREEN!
Exit the RUU
Run the RUU again while the phone is still at the HTC screen.
It will run the second time.
Ty. I will try that tonite when I get Home. If it works then that info would be a good sticky for others. Will post back with results. Ty again
Yeah, I also have the same problem when trying to RUU, hopefully if I get to try this tonight it'll work.
Kcarpenter said:
Run RUU let the 171 error appear. LEAVE THE PHONE AT THE HTC SCREEN!
Exit the RUU
Run the RUU again while the phone is still at the HTC screen.
It will run the second time.
Click to expand...
Click to collapse
out of curiosity would doing this (running the ruu twice) work with the 1.29 or 1.56 ruu?
I have a similar problem with trying to downgrade 2.27.651.6 to 2.27.651.5. I've tried running the RUU (which takes a LONG time to load, by the way) but it sits at the "Verifying information on you Android phone. Please wait" message for 5-10 minutes then says it can't connect to my phone.
I have Sprint's CDMA HTC Hero with Android 2.1. Every guide I've found about downgrading makes absolutely NO mention of how your phone needs to be setup when you connect it to the PC.
I've tried it in "Charge Battery Only," and "HTC Sync" modes.
I've tried it with and without "USB Debugging" enabled.
Same results. Anyone??
Doormat81 said:
I have a similar problem with trying to downgrade 2.27.651.6 to 2.27.651.5. I've tried running the RUU (which takes a LONG time to load, by the way) but it sits at the "Verifying information on you Android phone. Please wait" message for 5-10 minutes then says it can't connect to my phone.
I have Sprint's CDMA HTC Hero with Android 2.1. Every guide I've found about downgrading makes absolutely NO mention of how your phone needs to be setup when you connect it to the PC.
I've tried it in "Charge Battery Only," and "HTC Sync" modes.
I've tried it with and without "USB Debugging" enabled.
Same results. Anyone??
Click to expand...
Click to collapse
i have the same problem. HELP??
I have a sprint htc hero with build 1.56.651.2
I want to root it for the ultimate goal of using it as a wireless wifi access point. I have read alot about the different versions but don't see much about my build. Is it possible to root this version easily and where exactly are these steps? Sorry to be a noob!! I have JB itouches and phones so I should be ok with this. Any help Thanks!
It looks like I am running an "old" version (1.56...) If I root it what will the new build be that I have?
RUU error 171
I am having the same problem trying to downgrade 2.27.651.6 to 2.27.651.5 I ran RUU and got the error 171 then tried runing it again while in the htc screen as sugested and still got the same result I am getting quite frustrated with this. I have also tried to download differnt ruu's from differnt sources they also dont work. Please help
To all of you need some help with getting the ruu to run try this.
1. Make sure you download all the necessary items found here.
http://forum.xda-developers.com/showthread.php?t=694572
2. Check out the step by step rooting video on Youtube found here.
http://www.youtube.com/watch?v=tAKrIZzXIyA
I used the video rather than try to read all the steps because I felt it was much easier to see everything and takes about 10 mins.
Then make sure that leave your phone on the charging option not "Use as Disk Drive" etc.
I've been rooted for a while but I just rooted my gf's Hero last night and was getting the same errors with her phone that you guys are mentioning so I reinstalled the Htc Sync program and after no luck finally realized I forgot to turn usb debugging on. This is key. MAKE SURE YOU ENABLE USB DEBUGGING. That seemed to solve the error message for me.
im still getting the error 171 saying that my phone is not connected is there some prep work that i need to do besides charge only and usb debugging
i read you cant do it if your running a windows 7 pc
http://forum.xda-developers.com/showthread.php?t=728282
Kcarpenter said:
Run RUU let the 171 error appear. LEAVE THE PHONE AT THE HTC SCREEN!
Exit the RUU
Run the RUU again while the phone is still at the HTC screen.
It will run the second time.
Click to expand...
Click to collapse
It worked for me i left usb debugging on and left it on charge only i ran the ruu and it got stuck at the htc screen i exited the ruu and ran it again and it worked thanks a lot Kcarpenter!
its been a very long while since i updated my phone and used to work fine very slow even when over clocked but fine. the only other thing that happend was very rarely it would restart.
but now the screen wont work all time. it does work some times but not alot. works from reseting the phone. also it may be a loose wire tho because bumping the phone seems to fix it but i think it is just luck that it does.
now the phone is geting calls but nothuing is showing only ringing. i cant even place a call.
what i need to know is what is the latest stable build? and how do i get into the recovery again i cant seem into it again?
im tinking of going back to the original 2.1 but i love the 2.2 only programs ah well i also love haveing a working phone more.
if its a hardware issue simply flashing a new rom wouldnt help i suggest reverting back to stock and take it into a sprint tech store and who knows it could be under warranty still and yes if u flash an ruu theres know way they would ever know it was rooted to begin with.
how do i do this. i can not use adb to push anything to the phone adb wont list the phone in the devices
tutorial i am useing is the stickied one.
how do i revert back to stock
dont see a tutorial but im going to search a bit more
this is old 2.27 official ruu exe when you download it plug your phone into a computer via usb and dont put it in disk mode needs to be charge only im pretty sure then on your computer run the ruu exe and itll update everyhting on your phone and please make sure u have a stable usb cord that wont get disconected easily because all the updates should take around 10-15 min after that youll be on the stock sprint software then u can just update everyhting on your phone by pressing menu settings about phone and software updates but [B]please note that once u runn the ruu you will not be rooted anymore but you can still root easily via z4root after u update everything should u feel the need to[/B] thats all.
http://www.4shared.com/file/2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
thats the download link to the ruu.
thank you the one i was trying wouldnt load in hboot once my phone boots ill try this
yea with this all u need to do is plug your phone into a computer and run the ruu exe and it does everything for you i just couldnt find the right 2.3 ruu but u can still update everything the normal way after this
is there a certain way i connect it because it keeps giving me error 170 usb connection error
edit could it be that i am running 64 bit 7
When it gives you the 170 error with Win7, disconnect and reconnect the usb and re-run the program
Sent from my HERO200 using XDA Premium App
still no go. i did have an error installing sync because i have a 64 bit 7 OS is there a 64 sync install?
one that works because the one that was suppost to work messed up also
I've got 32-bit, sorry I'm not sure if there is a different procedure for 64-bit
Sent from my HERO200 using XDA Premium App
Have you tried a different USB cable? Beyond that, way back when I used HTC sync it was on 64 bit windows 7 fine with no issues. I don't even have it installed now and it ruus fine. If a cable doesn't resolve it, then maybe you just need to delete your USB root hub and force it to redetect USB devices
~maybe I set it too high...
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
This link help me and right now im on the way to updating the phone. thanks everyone who helped ... now hopefully this is going to fix all my problems
have you installed htc hero drivers yet try these out
place them on your desktop then go to devices/printers then click android phone/properties and update drivers dont do an automatic search make sure you choose desktop for the path.
http://handheld.softpedia.com/get/Drivers/HTC-Hero-Drivers-81097.shtml
yea phone so far is now working as it should touch screen and calls thanks again
hi ive searched for a few hours and tried so many different sequences her eon the forums and for some reason i cant get odin3 1.78 to recognize my captivate... otherwise i would have an awesome Cyanogenmod 7 on it.
i rooted it and installed clockwork from the thread "how to install roms" under the dev threads (the big sticky) then attempted to install a custom rom through clockwork and it failed. now my original rom is messed up. i can load into it but android.phone continuously closes...i cant get odin to see my phone thus i cant reflash the original firmware....
yes i have drivers installed.
yes i have the AIO toolbox.
now for some reason i cannot get Odin to recognize my phone AT ALL (download/recovery/loaded). ive literally tried everything i can think of and to be honest i hope someone here can make me look stupid and help me fix it . ive flashed roms before back in the day with my tilt and cliq. but ive been out of the game for a very long time and lemme tell you im completely lost feeling.
im on windows 7 ultimate x86 fully updated.
ill be glad to donate a little bit for some success on just getting odin to recognize because i have everything. its just that stopping me..
in the meantime my phone is just useless
It might be problems with usb port. Try different ports and/or a totally different computer. Make sure you have drivers according to your computer (32-bit /64). I don't really know why it isn't working.
im sure if he got cwm copied to the phone the USB works...
i have never heard of odin3 1.78
only 1.0 1.3 1.5 1.7 1.81 and 1.82
and some odins only work with some phones..
did this odin ever work for you? or never?
try this one...
no i used my laptop MicroSD then transfered into my root folder of my phone.
ive tried it on 4 computers in my house so far all windows 7 32 bit.
installed the drivers from the AIO and even KIE after seeing no results. ive tried different ports as well and thats the exact odin im using ;(
i also attempted XP compatability mode seeing on another thread windows XP worked for another user in a somewhat situation so im debating whether or not to dual boot XP just to fix my phone lol
so your computer doesnt even see it when you mount usb to copy files? not just odin? did it ever work?
i run windows 7 64 bit no probs.
EDIT... i just re-read your first post....
ODIN ONLY sees the phone in download mode. ONLY
no it doesnt see it at all i think im goin to uninstall drivers and reboot.
now it makes the sound that windows found it but i cant access it or visually see it as a mass storage device even when i specify the settings (disabling debug/enabling mass storage) and under download mode it just doesnt see it at all.
i think im going to get organized and correclty reinstall anything i might think may be an issue
also installing xp on a virtual box on my linux machine to my right
virtual machines and odin dont mix well
with linux use heimdall instead of odin. but the machine still needs to see the device.
and try the drivers from samsung.
USE THE ORIGINAL SAMSUNG CABLE!!!!!!!
some cheap cables, like the one for my bluetooth headset are power only usb cables. the other 2 data pins dont connect end to end!!!!!!!!
ahh maybe thats the problem, i happened to pick up my captivate from someone on criraglist just yesterday and it was just phone and charger. how can i tell if i have an original or not? and yea i tried the drivers from samsung for the galaxy S as well. i was so irritated earlier lol i took a break and came back to it
if windows doesnt beep when pluggin in, then the cable is probably no good...
or try the cable with another phone/ usb hard drive / some data device that takes that input....? or go to radio hack and pick up a new cable. if that doesnt work return it to the hack for your$$ back.. if it does work its worth the 15-20$...
or maybe the phone has a dead usb port... that has happened to some people
okay i found a cord that gives me "usb device not recognized" when im loaded into my phone fully and select mass storage. this is after i installed the samsung driver exe 32 bit for my 32 bit windows 7.
looks like windows 7 attempts to install drivers for "mass storage device" and it fails.
my windows will fail on phone boot a few times because the phone cycles thru different modes.. adb and download mode work on different drivers...
remember to mount to see sd card on pc...
but at least you are getting something now... maybe now is the time to try other pcs..
just throwing out some ideas its getting late.... lol
lol yea thanks man ill reinstall android sdk and java se and see if i can get the adb to be seen and try different drivers for now. thanks for helping me ill donate to you in the end even if we cant get it but man my phone is wacked, all the services are force cosing on it. its so useless right now
ConnectionStatus: FailedEnumeration
Current Config Value: 0x00 -> Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!
===>Device Descriptor<===
*!*ERROR: bLength of 0 incorrect, should be 18
bLength: 0x00
bDescriptorType: 0x00
bcdUSB: 0x0000
bDeviceClass: 0x00
*!*ERROR: Device enumeration failure
thats what im getting in every port on my laptop.
okay man i got it.. i rebooted my pc after uninstalling EVERYTHING (java sdk,eclipse, android sdk, AIO Captivate toolbox, all drivers known to man that dealt with the phone) then logged back in, i downloaded and loaded up UVCView.x86 and tried my phone on every single usb port on my laptop while disconnecting ANY other device thats including my mouse and for some reason my captivate only worked on 1 usb port that was on the side of my laptop (left side) and would only make a (ding dong) sound if my external was detached from my laptop (weird) but wouldnt install drivers still. reinstalled the set of drivers needed and installed AIO captivate toolbox, nothing happened. so i put my phone in download mode and i went into the Compatibility options for the AIO toolbox and set to run as windows xp SP3 + checkboxed run in 256 color, Disable visual themes, Disable desktop composition, Disable scaling on high DPI settings and run as Administrator Then doubled clicked/loaded it up. sure looked like utter crap but my phone was seen by windows and sure enough it had 2 drivers it installed. i went into flash to stock and COM 3 came right up i cried with happiness and i flashed faster than my eyes blink while on a cup of sugar. then i went ahead and tested the com 3 detectability under Odin (i set odin with the EXACT same compatibility mode settings as the AIO - i used odin by itself just for testing) and COM 3 was instantly seen. after flashing to stock and making sure eveyrthing was okay, i went ahead and installed the speedmod kernel and yet again windows 7 x86 recgonized the device and it installed about 7 different drivers! i should be okay from here im not totally noobed feeling now.
Thanks for stickin by my side for the information and support TRusselo ill donate to you for that.
PS : i think im going to research for a week or two on getting what i ned for my linux box in the near future lol
congrats!!!!
yep yep, got cyanogenmod 7 running great, sure is a battery killer though, seriously im afraid of leaving the house with this lmao. my next paycheck be sure to see a donate from dahrat
I just wanted to relay my experience for anyone who might run across the same problem. There are so many solutions (some good, some bad) that I thought I'd try and help someone else out that was in one of these situations. Keep in mind, the solutions are all here at XDA, I just had to dig and try a few things.
This Captivate was on a Ginger Clone rom (2.2) from about a year ago and I wanted to go to Cyanogenmod. I personally run Cyanogenmod7 (181), and was trying to replicate that.
[Boot-Loop]
I Attempted to clear caches and go straight to Cyanogenmod. This may have been an inexperienced guess that I might be able to do this, but I know a few other folks that manage to do this. I ended up in a boot loop
[Getting to Download mode]
Can be frustrating, but seems to be if you have the usb unplugged, battery out, sim out, put the sim in, battery in, usb in (phone will turn on, so you have to move fairly quickly) and then hit the up and down volume buttons it will go into download mode.
[Go back to Factory]
I tried using the Odin 1 click solution. I believe there are more than 1 versions of this, but it would just get stuck at "Do not turn off target". I decided to try something else. The Java based Hemidal 1.3 aka "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" seems like it is very well written and very easy. It has you update a driver in the mix and it works fantastically.
[Now I'm at Stock 2.2, rooted]
Need to turn on USB debugging, and I was expecting to be able to put
on the rom manager by copying over a file, naming it update.zip but it won't run due to some signing restriction.
[Unable to run any scripts or update.zip]
http://forum.xda-developers.com/showthread.php?t=833423
Basically, you need to turn off signing
[Went off the tracks, bricked the phone]
I decided I would try and apply the Cyanogenmod rom a different way. I went to their wiki and tried to use their Hemidal 1.1.1 update suite and script. I ended up with a brick. I didn't panic, I used the below url and it worked to get me back into download mode. I then used the previously successful Hemidal one click to fix it.
http://www.traemcneely.com/2011/05/...e-possibly-vibrant-kernel-error-black-screen/
I went back to the 3e recovery installer, ran that script, it worked and let me run unsigned code, I installed rom manager via update.zip, and from rom manager I was able to apply Cyanodenmod 7-v181 and then the Google apps and I was happy. Took about 2 1/2 hours to go through all that. Kind-of a pain... happy now.
Rich
Wish I had your kind of luck
I have a Captivate that isn't "bricked" per say but when I plug it into my computer when it's in download mode I only ever get "unknown device". Forcing a driver install causes a code 10 which makes it unusable as well. I have tried 4 different cables and 3 different computers now and tried all of the USB ports on each of the computers I tried at and always get unknown device even with the correct drivers installed. The 3 button trick doesn't work to put it in download mode but using a jig does. I have tried every operating system combo as well heimdall in OSX and Linux says no device connected, and in Windows 7 32 bit and 64 bit I get the unknown device error, also tried Windows XP and get the same error. I have tried 4 different usb cables now as well in each situation with the same unkown device/no device connected error (2 motorola cables, 1 samsung oem cable, and one no-name cable). I was going to gift this to my Dad because he's been missing Android since he gave his HD2 away and went back to a Blackberry.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.