Related
Hello,
I tried to upgrade my SPV M1000 to WM5. I followed the procedure and ran the device in bootloader mode. I put the device on the cradle and it displayed USB and V1.06. Ok sounded good.
I started then the HimaUpgradeUt.exe program on the PC. The problem is HimaUpgradeUt.exe didn't find the mobile device at all. After maybe 1 minute looking to it displayed an error 101 message.
I tried different things : install ActiveSync 3.8, 4.2, 4.5 (no change)
I tried to connect the device with mty and it worked !
I tried to run HimaUpgradeUt.exe with the SPV running WM2003 and it found the device. I didn't try to upgrade in this mode anyway.
Any help is very welcome.
is your machine with win vista also?
as you said that you tryed to install ActiveSync 3.8, 4.2, 4.5, guess its WinXP. if its 2000/WinXP/win2003 then use only 4.2 version of ActiveSync. don't know why but i can only have sucess with that version. check for any security software that may block COM. with ActiveSync-Pocketpc.
that HimaUpgradeUt.exe you use is for your model? as im not an expert on this matter, don't know if your precise phone is a himalaya, maybe thats the prob. ehehhe then maybe not as im not aware of all the brands this peace of tech can became!
do right click on my computer and select manage, goto device manager and see for a mobile entry there, while your pocket is connected in serial/usb boot mode. there must be a windows ce device there for this to happen, and you should, not a must, but try to shut activesynch down while doing this detection with HimaUpgradeUt
Yes I'm running Windows XP Pro SP2. I installed activesync 4.2 again and disabled the firewall. I can see windows detecting the device when I put it on the cradle. But there is still the 101 error message when I try to run the update.
Vista and upgrade
Firstly thanks to marcjero for guiding me to this thread...
secondly... I had no probs at all, syncing my device with vista's WMDC(Windows mobile device center), apparently I tried to flash my device... and yes its an i-mate XDA II, currently running on C_ShekharAKU3.5.R40.P24_public_ROM and want to update to the latest one... apparently, connected my device to my system in bootloader mode... and well since then my system has a prob detecting my device... and I cannot even sync now... when i try to run HimaUpgrade, get the same 101 error code... :-(
any ideas how to get this thing working again?
PS: its seriously frustrating for me
use the "HimaUpgradeUt_noID.exe " instead the "HimaUpgradeUt.exe"
download it HERE!
install the latest Active Sync...version 4.5
Syncing in Vista is no problem but as i said from other thread...i tried but not working...you cannot flash the device except in winxp...
Regards!
jojo
syncing not working either...
xda2jojo said:
you cannot flash the device except in winxp...
jojo
Click to expand...
Click to collapse
The prob is that now a normal sync does not work either... so I cannot synchronize my device with my system at all :-(, any ideas at all... on how to get it to work?
xda2jojo said:
use the "HimaUpgradeUt_noID.exe " instead the "HimaUpgradeUt.exe"
download it HERE!
install the latest Active Sync...version 4.5
Syncing in Vista is no problem but as i said from other thread...i tried but not working...you cannot flash the device except in winxp...
Regards!
jojo
Click to expand...
Click to collapse
I tried both (as 4.5) and HimaUpgradeUt_noID.exe without any success.
daWidoW said:
The prob is that now a normal sync does not work either... so I cannot synchronize my device with my system at all :-(, any ideas at all... on how to get it to work?
Click to expand...
Click to collapse
marcjero said:
I tried both (as 4.5) and HimaUpgradeUt_noID.exe without any success.
Click to expand...
Click to collapse
what OS you are using while flashing and synching? xp? vista?
I'm running XP SP2
About Vista...
Read this thread
Could worth to try.
I tried to flash using my work laptop and it's working now
44% processed, finger are crossed...
hi
guys i am newbie in upgrading and tried to run athena wraper and it died and after searching forums i still cant find cure ok so here it is i can do hard reset but it dosent help no boot up it still gives me ring round joystick good news is i can get it to bootloader screen (or at least thats what i think ) its red green blue and white screen with usb or serial (depending on cable )
screen reads
ATHE100
IPL-V0.90
ATHE100
SLP-V1.20.Olipro
now can any one help me ??
how can i upgrade rom with out device being detected by active sync every time i run upgrade utility it just comes up with connection error
still no luck
hi
still no luck
do i need special drivres to detect device if its in bootloader ?
it dosent show any thing in device manager when i connect it while its in boot loader
on running upgrade utility it comes back with error 260 connection error saying cannot find device (i am stuck in bootloader)
any advices ??
please help !!!!
The fact that you can still enter the bootloader means that it is not bricked, so first advice would be, as is so well presented in the Hitchhicker's Guide to the Galaxy, "Don't Panic".
Enter bootloader without any SD Card or SIM left in the Athena.
Then, plug it to the USB port, and see if it goes from "serial" to "usb".
Then try to flash first the Black Dual PK ROM available on the forum (in the WM6 section), or an official ROM available from the Wiki, for instance.
hi
tried to flash it with both and came out with same error
260 connection cant find device
and i cant even see any changes in devicemanager but it dose goes serial to usb when i connect
and my pc is not detecting the device (just like that depressed robot from hich hikers guide to galaxy )
Do you have Windows XP or Vista ?
Ecraseur said:
Do you have Windows XP or Vista ?
Click to expand...
Click to collapse
xp (pc i am trying to upgrade i also have vista on other pc which i havent tried yet should i try that ?)
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
vijay5264 said:
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
Click to expand...
Click to collapse
Hi
Try a hard reset ( Volume down+reset) and then get into the boot loader(Camera+reset~10seconds) then flash the PK dual rom. Don't panic, Your athena is hard spl patched therefore not bricked. If that not works down load the exact official rom for your device flash that then flash the PK dual rom. try Redownload the rom again.
Good luck
HeartOfDarkness said:
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
Click to expand...
Click to collapse
hi
thankes i think u understood the problem it is utility which fails before even starting beacouse of no connection see if u can find any thing
and yes i tryed hard reset and then tryed to flash with project black rom and i have downloaded latest t mobile rom from oficeal website but as i said before it fails with connection error it starts up and box says ''verifying information on your pda fone please wait'' and minut later it comes up with error 260 connection error '' please check following
1 your pdafone is connected to usb cable /cradle
2 usb cable connected to pc
(wich is basicly same if you try to nrun upgrade with out connectind pda )
(and yes i have tryed it with 2 different cables and it dose change from serial to usb)
some ting intrestin i foun in orignal update utility faq
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
is possible because device is in bootloader ?
or am i doing some ting wrong?
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Pantaloonie said:
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Click to expand...
Click to collapse
good idea but dident work after 4 on board ports and 2 hub ports no joy at all
by looks of it upgrade utility is trying to read info from my device and could be failing for 2 reasons
1 it is not detecting device
2 info in pda is corrupted and could not get any info from device
well thats my theory but not really sure any suggestions??
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
eaglesteve said:
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
Click to expand...
Click to collapse
it is running xp the one i am working on now (i do have 2nd pc running vista 64 bit )
but i am doing unlocking in xp
all i want to find out is dose device needs any drivers or dose it gets detected if device is in bootloader ?
if thats the the case i dont see any new devices in xp devicemanager
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
HeartOfDarkness said:
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
Click to expand...
Click to collapse
i found this in wiki and first three posts are empty but followed the procedure and downloaded all three roms and still no joy error
''Problems using the Athena Unlocker - the Black Screen of Death
Using The Athena Unlocker tool (developed by Olipro) is a 3-stage process. Most users get through the first stage but as they start stage 2, get a black screen where their device becomes unresponsive and so cannot proceed with the unlocking. See these posts
http://forum.xda-developers.com/show...&postcount=169 or http://forum.xda-developers.com/show...&postcount=176 or http://forum.xda-developers.com/show...&postcount=226
It is always recommended that you first take out your MiniSD card. You can then follow the instructions below.
* Get one of the ROMs in this link and extract it http://forum.xda-developers.com/showthread.php?t=314672
* Get your device into bootloader (the three-colour screen; You can get there by pressing the Camera key + Volume key + Soft Reset at the same time)
* Connect your device to your PC (even if the PC shows no sign of recognising it, it does) and the SERIAL shown on the screen of your device will change to USB)
* Hit the ROM Upgrade Utility and upgrade your device.
* Once the upgrade is completed, configure your device (Calibrate screen, set time zone, etc).
* Now continue with the Unlocker, to the end.
It is important to complete the unlocker to the end or else you will miss out on flashing your radio, with a common symptom of your gps not working.
Good Luck and enjoy your improved device!
''
now i am still stuck will it make any difference if i try it in different xp pc other then the one i started the process ?(and screwed it up)
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
lpsi2000 said:
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
Click to expand...
Click to collapse
good idea
i have already tryed with firewalls and virus protection off but doing it in fresh xp might just work small question do i need to install active sync or is it not needed (any way ill try both first without and then with )
ill report back in about 3 hours (i know i am sad and havent got a life but its worth a try )
Yes, the wiki confirms what I thought but didn't voice out loud as yet (I was sure about it for the Universal, but not for the Athena): the upgrade utility doesn't *require* that it be Activesynced. That's, as I'd said, te whole point of the bootloader.
If you still have problems uploading the new ROM to your Athena after following the wiki thing, then it *does* mean that there is some external factor playing dirty, so the firewall to check (and some anti-virus software also scan network connections) indeed is a good idea.
Keep us posted, and I'm keeping my fingers crossed.
i posted this in the hard spl sticky thread but got no responses so i thought i would create a new thread.
Been reading through the forums for 3 hrs. i read the entire unlocker thread. cant find any info on this.
i own a htc x7501. i performed a hard reset, connected device to windows xp pc. synced with active sync 4.5. everything connected, i can browse files on the device. device definitely connected.
i took out the sd card, sim card remains. windows xp computer has all updates and service packs and antivirus disabled.
i ran athena unlocker version 3, downloaded today from unlocker thread. click step 1, it loads the RUU, i follow the steps, says upgrading from image version 2.19 to Hard-spl. i click next, says now upgrading and shows the status bar at 0%. after about 10 - 15 secs, windows pops up on computer screen and says "error 202: connection. please make sure your device is connected to your computer, check the cable, blah blah"
tried mulitple times, each time restarting pc and device. device still works as before, nothing changed at all.
any ideas?
come on guys, anything?
someone has to have a clue
what do you see when you get into the bootloader screen. Get into the boot loader by pressing down and holding on the camera button while sticking your stylus into the reset hole for a good 5 seconds.
it says:
athe100
ipl-v2.02
ATHE100
SPL-v1.10.0000
i followed the tutorial video in the unlocker thread, and on the video when the guy done step 1, it asks to install something on the phone, enablerapi.cab by the look of the video. i never get this, just says "connection error"
thx for your reply Eaglesteve, appreciate it
This mean your flashing was not successful yet.
I think you should first reflash your original ROM back to restore it back to working condition again first. Then repeat the step and keep the finger cross this time.
You do this by first going into the boot loader mode, then connect up the usb cable, and run the RUU (RomUpdateUtility) program of your ORIGINAL stock ROM.
Edit: Sorry, did you say that your device is actually still working? Then you don't need to reflash the original ROM.
Do you have .net Framework 2.0 installed with the services packs on your XP machine?
i think there might be a misunderstanding.
the rom is untouched. i cant complete anything. here is what i did from the beginning. new stock phone. performed hard reset. went through customisations as per normal. stock rom installed.
plugged device into pc running xp. active sync, connected and synced. ran unlocker tool version 3. press step one, unlocker minimises and open RUU. says checking device for version details, finds them, says image version 2.19. great, that shows it can communicate with device. i click next a couple times, eventually it gets to the status screen that shows percentage of flashing and a warning at the bottom that says, "be aware this might take 10 mins" or something like that. about 15 secs, nothing happens, then new window appears saying "error 202: connection, please ensure device is connected, check cable/cradle"
i click ok, RUU exits, unlocker reappears, and says step 1 complete.
make sense?
PashaK said:
i think there might be a misunderstanding.
the rom is untouched. i cant complete anything. here is what i did from the beginning. new stock phone. performed hard reset. went through customisations as per normal. stock rom installed.
plugged device into pc running xp. active sync, connected and synced. ran unlocker tool version 3. press step one, unlocker minimises and open RUU. says checking device for version details, finds them, says image version 2.19. great, that shows it can communicate with device. i click next a couple times, eventually it gets to the status screen that shows percentage of flashing and a warning at the bottom that says, "be aware this might take 10 mins" or something like that. about 15 secs, nothing happens, then new window appears saying "error 202: connection, please ensure device is connected, check cable/cradle"
i click ok, RUU exits, unlocker reappears, and says step 1 complete.
make sense?
Click to expand...
Click to collapse
Yes, indeed I misunderstood. Please see my revised post above.
yes .net framework 2 and 3 installed plus all service packs.
PashaK said:
yes .net framework 2 and 3 installed plus all service packs.
Click to expand...
Click to collapse
I wish I could be of more assistance, but I'm not sure why your connection does not stay firm throughout the process. Perhaps you could PM Olipro for assistance?
yeah i might have to. i was thinking about trying it from a server 2003 machine, in case it is something wrong with my xp pc. i also have a vista pc but i dont trust vista enought to do it.
you think server 2003 would be ok to do it from?
thanx for helping a fellow aussie out
PashaK said:
yeah i might have to. i was thinking about trying it from a server 2003 machine, in case it is something wrong with my xp pc. i also have a vista pc but i dont trust vista enought to do it.
you think server 2003 would be ok to do it from?
thanx for helping a fellow aussie out
Click to expand...
Click to collapse
No worries mate.
Perpahs you want to try a newly installed XP machine? You know what it is with older machine. After a while all kinds of stuff goes in to corrupt it. I vaguely remember a post where someone who did not succeed with an XP machine later got it workign with another XP machine.
I think it is not possible for Olipro to anticipate all the possible conditions which might affect the program.
So, give it another go with a different, cleaner XP machine.
Good luck.
thanx, i might try that tomorrow if olipro has no other ideas. this is a newly formatted pc. i format quite regularly, being a network administrator, i keep all my pc's very clean.
i will report back my results when i get this solved.
thanx again
PashaK said:
thanx, i might try that tomorrow if olipro has no other ideas. this is a newly formatted pc. i format quite regularly, being a network administrator, i keep all my pc's very clean.
i will report back my results when i get this solved.
thanx again
Click to expand...
Click to collapse
Your cable has no problem I assume? Do you have problem doing ActiveSync in normal use?
the cable is the same one i got with the device. hardly used. everything in activesync works fine. i can browse files. install programs, everything works as it should, except the unlocker
I had a very similar problem when i tried to make the WM6 upgrade...
The reason for the connection failure:i had my Ameo connected via an external USB-hub.Which worked perfectly when i just wanted to synchronise or browse files...but when i wanted to make the upgrade i got the same connection error at exactly the same point.
Sticking the cable DIRECTLY into one of the PCs USB-ports solved the problem.
Ok,last night i tried the unlocker myself.
I put the cable directly into one of the ports of my PC...and got that connection error!
Tried to reinstall WM6-which,as mentioned in my post above had worked...still connection error.
Disconnectedt the USB from my pc,and simply put it back in a different port.
WM6 installation worked,and unlocking the phone afterwards worked,too.
No connectin errors anymore.
So this definitely is some sort of USB connection error.
Just try different ports.
i tried updating the rom, which i have done a few times before, but this time i tried to update it in windows 7, i did not secceed and eventually i got the tree color screen, then i moved to my xp machine and i tried upgrading there, everything was going fine, and just when i the upgrade process was about to finish i got the tree color screen again. i read the vista rome upgrade tutorial and my win7 had the proper vista drivers installed. could i consider my device bricked????
dddnnnggg said:
i tried updating the rom, which i have done a few times before, but this time i tried to update it in windows 7, i did not secceed and eventually i got the tree color screen, then i moved to my xp machine and i tried upgrading there, everything was going fine, and just when i the upgrade process was about to finish i got the tree color screen again. i read the vista rome upgrade tutorial and my win7 had the proper vista drivers installed. could i consider my device bricked????
Click to expand...
Click to collapse
I don't think your device is bricked you need to install those vista drivers properly a Flash failing at 90 - 95% is common if those drivers have not installed correctly
Follow this guide here it has pictures and works for most users (you need to connect to USB in bootloader to install the drivers on win 7)
http://forum.xda-developers.com/showthread.php?t=485293
When you have done that try to flash the nvid recovery ROM to restore your prophet to factory win5 (Then you will need to Unlock and hardspl again if you want to upgrade)
I can not enter bootloader, and i can not establish connection with the pc. I installed the drivers, no change, my screen still stays with the tree colors, i still can not manage to get any of the RUUs wirking.
dddnnnggg said:
I can not enter bootloader, and i can not establish connection with the pc. I installed the drivers, no change, my screen still stays with the tree colors, i still can not manage to get any of the RUUs wirking.
Click to expand...
Click to collapse
The three colour screen is bootloader
The problem is loading the drivers in vista i have found a different tutorial try this one
Please note that you are the only person having trouble flashing on win 7 follow the tutorials or we will get bored with your post
Only follow this thread for driver install the rest is not for your device
http://forum.xda-developers.com/showpost.php?p=4194862&postcount=2
When the drivers are installed correctly follow my recovery post above
Thanks for the support, i followed the abovegiven instructions (http://forum.xda-developers.com/showpost.php?p=4194862&postcount=2). 10a did not appear and the date in 12 was 2004 not 2003. Strange new thing happened, the phone restarts itself automatically, so i removed the battery now.
Anyways, i belive that it was time for my prophet to retire. Thank you all for all of the support and all different roms, great job, great community, the greatest of ots kind. Unfortunately i will not be able to participate here with my new phone, i got Sony Ericsson Satio.
Wishing the best of luck for all the forum members,
With kind regards,
dddnnnggg
P.S. Please inform me if you create a Symbian subforum Thanks once again
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.