Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
RMseth said:
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
Click to expand...
Click to collapse
I am EXTREMELY unfamiliar with a MAC computer, but I imagine it would have a command prompt like program. I believe it's called "Terminal" on MAC.
Have you tried manually running adb through terminal with a command?
Or is it just a problem within the phones adb?
Tried putting your phone on USB mass storage like mode, such as mount as disk drive?
Just trying to think of some things off the top of my head.
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
RMseth said:
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
Click to expand...
Click to collapse
That's pretty strange. Have you tried flashing to another ROM?
Ya I flashed by to my stock rom and it still didn't want to run... I flashed to an MIUI rom and it didn't want to recognize it ether... so I don't know what's going on... I did unlock my phone using the HTC method, but I did it through my windows side so that might be the reason because it was flashed under windows instead of mac, I don't know if that would really make a difference since it's the same language for fastboot and ADB... what do you guys think? if you think if would make a difference then I'll do it but it just takes a LONG time to run you have to lock the bootloader and then unlock it again, wipes all my data and then I have to reload everything over again... so if you think it would make a difference I'll definitely try it.
Did you get s off before you tried flashing roms? I know that miui is packaged with a custom kernel and you can't flash roms in recovery that have a custom kernel with s on.
Sent from my ADR6400L using Tapatalk 2
no I don't have s off, but I do have an unlocked bootloader and through adb and fastboot I can flash custom kernels, right now I have imoseyon-6.1.AOSP+root and running liquid Gingerbread 3.2 ROM, Android 2.3.7, with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of... I can change everything on my phone except the Radio, but it's through ADB and fastboot you just have to know the codes and what you're doing haha! I've been able to do all that through my windows parellel but I want to get away from that so I can develop everything through my mac OS which is suppose to be easier, from what I read and hear.
Hmmm... I have heard linux is but not mac. I dunno maybe you're right.
Sent from my ADR6400L using Tapatalk 2
Maybe you should try flashing back through windows.
I suppose it wouldn't hurt anything. I'm sure it's worth a shot anyways.
RMseth said:
...with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of...
Click to expand...
Click to collapse
You can S-OFF with the latest update. I have a windows tool that automates most of it.
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
RMseth said:
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
Click to expand...
Click to collapse
Link in my sig. You will have to relock and ruu before it works though because just relocking causes a security warning
Sent from my ADR6400L using Tapatalk 2
What to you mean relock and RUU?
RMseth said:
What to you mean relock and RUU?
Click to expand...
Click to collapse
Relock the boot loader and flash a pg05img to 2.11.605.19. Problem is that it wipes data
Sent from my ADR6400L using Tapatalk 2
1. Make sure parallells is closed so it doesn't steal your connection.
2. cd to the directory platform-tools
3. Type ./adb devices
I didn't see if you confirmed Parallels being closed or not.
OK I FIGURED IT OUT!!!! oh my goodness!!!! this was soo easy and I totally bashed my head in when I finally figured it out!!! oh my goodness!!!!
I had debugging on but I didn't have "unknown sources" marked!!! oh my goodness!!! so when I had both of those marked then it pulled my device right up on my MAC!!!
well for all of those that tried to help me thank you very much!!! I hope you all have a good day!!!
PC: Ubuntu 12.04 with GNOME 3.2 desktop. Phone Galaxy S3 i9300, rooted but running the original stock Samsung.
I have a HTC Desire running Cyanagenmod - it connects to my computer and I have adb access to the command line with no problems at all.
HOWEVER:
Rooted S3: I cannot get it working via adb. I have switched on USB debugging. I've tried rebooting, plugging/unplugging, adb server kill/start to no avail.
As I can't connect, via adb, I tried using an SSH server on the phone and I accessed via the terminal on my PC. That worked but I was surprised to find that I couldn't do anything I wanted via the command line. I tried 'su -' and it was happy with that but whatever I tried to do - including chmod etc, all I got was a response of 'read-only file system' and commands were not effective. On my HTC desire I can do anything on the command line so this was a surprise to me - perhaps it is only possible via adb??
So, in summary, I have two problems:
1. I can't connect via adb when I know it works OK on my HTC Desire.
2. I can't get the root privileges I would expect on the command line.
Any suggestions as to where to go from here will be gratefully received
technoboi2 said:
PC: Ubuntu 12.04 with GNOME 3.2 desktop. Phone Galaxy S3 i9300, rooted but running the original stock Samsung.
I have a HTC Desire running Cyanagenmod - it connects to my computer and I have adb access to the command line with no problems at all.
HOWEVER:
Rooted S3: I cannot get it working via adb. I have switched on USB debugging. I've tried rebooting, plugging/unplugging, adb server kill/start to no avail.
As I can't connect, via adb, I tried using an SSH server on the phone and I accessed via the terminal on my PC. That worked but I was surprised to find that I couldn't do anything I wanted via the command line. I tried 'su -' and it was happy with that but whatever I tried to do - including chmod etc, all I got was a response of 'read-only file system' and commands were not effective. On my HTC desire I can do anything on the command line so this was a surprise to me - perhaps it is only possible via adb??
So, in summary, I have two problems:
1. I can't connect via adb when I know it works OK on my HTC Desire.
2. I can't get the root privileges I would expect on the command line.
Any suggestions as to where to go from here will be gratefully received
Click to expand...
Click to collapse
Did you flash a kernel with adb support?
I always use adb from recovery personally
rootSU said:
Did you flash a kernel with adb support?
I always use adb from recovery personally
Click to expand...
Click to collapse
Ah, in my ignorance - no.
When I first rooted my HTC I put a ROM on it and it worked. I didn't give thought as to the Kernel - I guess I thought it would already be there.
So, it looks as if I need to do some reading and change the kernel. If you have a suggestion for which kernel I will see if I can find how best to install it.
Pretty much any tbh..
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Hello friends at XDA!
I need some help. I have a Tmobile M7 HTC One. I have TWRP 2.7 running just fine. I have been able to flash a few ROM's using just that. I now want to install Kitkat GPe and it seems to require S-Off or else I get stuck in a bootloop. For what it's worth, I have Hboot 1.44. The phone has developer mode turned on. And it has USB debugging turned on.
I made such a mess that I formatted the whole device and had to flash a new ROM via USB OTG. It's back in working order now... but, not with the ROM I want. Currently running the newest stable Cyanogen Mod.
I have attached the phone to a Windows 7 and Windows 8 computer. Neither of them will recognize the phone.
On the Win7 machine, I had HTC Sync installed and closed. I also installed Squabbi's Toolkit and attempted to install the drivers from it. When I click the HTC Drivers button, nothing happens. I have tried connecting to adb through the tooklit and turning S-off... but, they all return some version of the Error: Device Not Found message.
On the Win8 machine, there was no HTC software, so I installed Squabbi's kit. I pressed the HTC Drivers button and it said it had installed new hardware... but, again, ADB won't connect.
I, frankly, don't care about ADB or s-off, as I've never needed them before. I just want to install 4.4 GPe. If I can do that without S-off, please point me in that direction. If I can turn S-off directly from the phone without ADB, please point me in that direction. And if I really need ADB to work, please help!
I'm almost certain this solution is already posted somewhere... and I'm just not able to find it... sorry to be a drag if that's the case. Either way, I'd be happy to reward (paypal) the person/people who help me get this resolved. I'm thinking like $10...
Thanks everyone!