HTC Aria Cyanogen Mod 7 Installation Problem - HTC Aria Q&A, Help & Troubleshooting

I just got hold of a HTC Gratia and wanted to install Cyanogen Mod 7 nightly.
First of all i cant get S-OFF because the revolutionary.io website is down so i cant get a beta key.
Secondly, I am running Windows 10 and was only able to install the ADB driver. When I connect it in fastboot/hboot Windows says "USB device not recognized" it does not even allow me to search for drivers. For this I got hold of a ubuntu live cd and after hours of trying was able to get fastboot to work. Then again the bootloader is LOCKED. At htcdevs website i downloaded the RUU (exe) which does not work on linux. I could use the open RUU tool here at xda but that would be too difficult for me. The drivers link in the HTC ARIA SUPETHREAD is also offline. I dont think they would work in this case either.
What are the possibilities ?

Related

T-mobile uk Hero goldcard but can't run RUU, USB error - help!

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.

G2 Touch ROM update?????

Hey guys, as you can see im new to this forum, i have a G2 touch that isn't rooted or anything like that and decided to update to the new ROM on HTC site so i could get OTA upates for 2.1
So i've got all the right drivers for HTC sync (comes up as "ADB Interface - My HTC" in device manager) so that it stays connected when i launch the RUU on my laptop (running Win 7 64-bit), but then when it goes into the first part of the update where my phone is in the bootloader?? part HTC Sync decides to disconnect and the update says its not plugged in an cancels the RUU and im stuck with my phone in what i think is bootloader (it says RUU USB on the screen when plugged in then changes to RUU when i take the cable out)
Anyway, can somebody please shed some light onto what is happening and give me a hand on how to successfully install the ROM update or point me in the direction of a good how to guide
Cheers!
it's a driver issue, update your drivers AND make sure you have the latest version of the htc sync software.
If possible use a machine that isn't using Windows 7 as it's known to cause issues...
Windows 7 has no real issues, just does it differently. Just reinstall the drivers when in the fastboot bootloader mode. Fixed.

revolutionary method stuck at 'zerging root'

i wanna get s-off and root on my wife's phone using the revolutionary method so she doesn't lose any data, problem is that I can't get the HTCDriver3.0.0.007 on my windows 7 machine to open up, i get a windows popup that asks is it ok to run this file, i hit 'ok', then that's it, setup never starts. so when i try to run revolutionary, i get stuck at the 'zerging root' step. apparently it won't get past that step until after i get that htcdriver to install.
i've made sure the phone was in usb debugging, updated windows, tried to download that same exe from other sites, and still nothin.
anybody have an idea of what to do
There's no point bothering to run Revolutionary until you get the driver installed....
Are you logged in with admin privileges on Windows ? Is a User Access Control window popping up that you don't see and aren't responding to ?
You could use HTC sync to get the drivers that's what u did...
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
the only window i get is the one asking if i'm sure i wanna run the file, i hit yes and nothin else happens. i'm the admin, i even ran hit 'run as admin' and it still nothing happened. i've tried other exe files that i have on my computer to see if they would run and they ran. it's just this one
i thought htc sync had to be disabled in order to use revo though
Sync does have to be disabled, but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Stratejaket said:
...but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Click to expand...
Click to collapse
Don't the instructions at revolutionary.io say exactly that ?
how could i uninstall sync and not uninstall the driver with it
The installer from HTC includes multiple pieces that show up individually in Add/Remove Programs. Easiest thing is to try it...
Sent from my ADR6400L using XDA App
i FINALLY got it! i reinstalled htc sync, it was over 100 mb. then deleted it. after that, i plugged the phone in and mounted it as a disk drive, so it installed whatever drivers it needed. then mounted it as htc sync; windows installed more drivers. then i set it to charge only, enabled usb debugging and ran revolution again, and it finally worked. she's rooted!! thanks!!!
Same thing was happening to me when I was tryin to root my mom's Thunderbolt. Couldn't get past the "Zerging Root..."
So contrary to what all the guides say, I installed HTC Sync, it installed all it's pre-requisites during the install, UPDATED HTC Sync to latest version, it updated all the pre-reqs again, mounted phone to computer as a disk drive, waited for drivers to install, mounted phone to HTC Sync, waited for all drivers to install, confirmed that HTC Sync was communicating the phone, set phone as Charge Only, waited for drivers to install, unistalled HTC Sync, ran Revolutionary, waited a minute, it FINALLY got past Zerging Root!
Hope this helps anyone else who has been tearing their hair out over this issue...
Alternate solution for rooting with latest ota...if you have locked bootloader
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING THIS PROBLEM
Thunderbolt Tool
I was able to S-OFF and ROOT my Thunderbolt by using the Thunderbolt Tool located at this link... rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
This app does it all for you, just follow the instructions.

Can't find correct Windows 8 64-bit drivers.

Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.

[Q] ADB won't connect, cannot S-off, and want Kitkat

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!

Categories

Resources