Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
alfmetal said:
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
Click to expand...
Click to collapse
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
BigJayDogg3 said:
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
Click to expand...
Click to collapse
yeah, i think thats the difference, i was using a tmobile MDA with WM 5 like 2 years ago, and used to install custom roms but back in the time i had dsl so i never had a problem doing it.
so, BTW, how fast is the Energy rom?
the one i have looks nice but i feel is very slow
paperWastage said:
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Click to expand...
Click to collapse
i wonder if there is an offline mode to do this?, without an internet connection.
Daniehabazin said:
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
Click to expand...
Click to collapse
not that i know, but i have win7 32 bits version, so maybe its has something to do with the 64 version
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Just to add, windows 7 64bit here and haven't noticed one difference or problem with anything.
player911 said:
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Click to expand...
Click to collapse
Nah, had my raphael a long time, have flashed a couple of roms before, i'll try to put it in bootloader mode and let it install the driver, i'll keep searching for a customruu that works for 7 x64, Thanks for the reply
i got syncing working, uninstalled the driver for the mobile remote adapter, and let it download a new one from windows uppdate, and now it works, stange since it's the same driver as before...
I was having the same problem with windows 7 x64 and the fuze... found my solution elsewhere so i thought i'd post it here in case someone checks here first like me... I needed to install Windows Mobile Device Center to get the driver to work correctly with an active sync connection =)
I have W7 ultimate x64 and I can't flash either. But I don't mind. I just put the .nbh on the memory card, start up customRUU and it puts my phone in boot loader itself then installs the ROM off th ememory card.
even there's already a WMDC on win7, I tried to download it again from brothersoft, then it's update the driver..... done!
btw I'm using win7 x86, so I haven't tried on x64...
img707.imageshack.us/img707/3830/51947559.jpg
I can't post a pic or link...
Related
Just curious if this is working for anyone. It didn't seem to work for changing the splash screen to the black HTC on my aku 2.3.1 ROM. I don't think I would try this on a complete ROM upgrade.
I'm wondering if this is due to Vista or the aku...
Well, it seems these attempts should be avoided as related by others....
I could not install Jesterz AKU2.2 on Vista yesterday. Kept giving me Error [260], i.e. the upgrade tool was losing connection with the device. Worked fine on XP pro this morning.
It could be related to the Mobile Device Center that replaces Activesync.
tried a downgrade yesterday evening on vista and it smashed my phone.
so i don't recommend it you can't get a "good enough" connection in bootloader from windows vista to the phone and active sync is not working anyway so that crap will be away by this evening. It seems to me vista is not yet ready. Good enough means that it shows on the phone that USB sign in the bootloader but the flash utility can't get a connection
cr0ssy, that's exactly what happened to me. In the bootloader I get the USB sign but the upgrade tool won't recognise the device. What I noticed was that Vista uses a different driver than XP. This new driver is what could be causing the problem.
hm maybe the old driver works on windows vista, too if just don't let it install automatically.
did you get the phone back to work?
I wonder if this has something to do with a move from NDIS- to a serial-based connection in Vista....
When in bootloader Vista recognises the device as Generic NDIS.
is yours back working kta? if, did you just put xp back on your computer and reflashed it in the bootloader? (or other computer)
cr0ssy said:
is yours back working kta? if, did you just put xp back on your computer and reflashed it in the bootloader? (or other computer)
Click to expand...
Click to collapse
Yes I then managed to flash the ROM from bootloader on another PC running windows xp.
mh did you flash then with the usual boot utility? is it possible to flash these customized roms which have a upgraderom.bat or something like that in bootloader mode? (don't want to expermient now that its not really working anymore)
sorry for getting a little bit offtopic
managed to upgrade without a problem on vista
which rom did you use and did you manage to install active sync?
phone is back working :> thanks kta
Yesterday I tried flashing my friend's Magician ROM on his Vista and had the same problem and had to use an XP laptop to flash. The upgrade utility program and others based on it (MaUpgradeUTNoID, etc.) seem to have a problem working with the new vista drivers.
without the beta Mobile Device Center, which you should downlad from MS, you can just access in explorer mode to your device, but you can not install anything to you device from vista. Just download the Mobile Device Center for Vista from the MS Page.
Mentes said:
without the beta Mobile Device Center, which you should downlad from MS, you can just access in explorer mode to your device, but you can not install anything to you device from vista. Just download the Mobile Device Center for Vista from the MS Page.
Click to expand...
Click to collapse
I have the Mobile Device Center installed and still have this problem.
the ROM upgrade tools do NOT work on vista (yet) there are several calls open with Microsoft to get this fixed, however I don't think it will be fixed in a few days seeing the speed of Microsoft......
For now, only update using windows xp
does the upgrade tools work on WinXP X64 edition?
liuyang said:
does the upgrade tools work on WinXP X64 edition?
Click to expand...
Click to collapse
They should as it has 32bit comp. however I havent tested it, so I'm not fully sure.
Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
GWD said:
Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
Click to expand...
Click to collapse
"Windows Vista"..... uh huh
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
XP in Vista??
So, can you explain exactly how you installed the XP drivers into Vista... My Uni is pretty much the only reason I'm running a multi-boot system anymore!!
Any problems caused??
I tried to fight the Vista urge, but after having Ultimate installed on all the systems at work, I could fight no longer!!
GWD said:
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
Click to expand...
Click to collapse
i'll resist the urge to call you a "fool", but had you not put your foot in your mouth...i.e SEARCHED BEFORE WRITING...some one would have come to your help...
read this for upgrading in vista
http://forum.xda-developers.com/showthread.php?t=292631
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file. In the meantime . . .
I think I did everything right. HardSPL worked fine, but then, when I tried to flash Dutty's Dual v4 ROM, it stopped at 6% and told me there was a communication error. I tried it a few more times, tried Dutty's Touchflo Rom (that got to 4%) . . . still no luck. Same error. In between each try, I reset using the stylus and sometimes the stylus while holding down power and camera.
Am I doing something wrong, or was my mistake trying to do this via parellels?
Current screen says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
USB
Thanks, guys.
I can confirm that if you install xp via boot camp then you can flash fine on a mac. I haven't tried going through an emulator such as parallels though. It should work fine though as long as parallels has taken over the usb ports.
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
By the way
It is error 262 that I'm getting . . .
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
drewcopeland said:
It is error 262 that I'm getting . . .
Click to expand...
Click to collapse
I might have to look into that. My "solution" didn't work. I'm going to try to find the original ROM somewhere . . .
zenrandom said:
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
Click to expand...
Click to collapse
I am using Fusion instead of Parallels but this is what I do. I only have 1 copy of xp installed via bootcamp but I can also access it through Fusion.
I also have fusion on my MacBook Pro, and it failed when tried to flash. So I bootcamp and started XP and it flashed flowlessly
If you own original XP CD (like me) you can always call microsoft to activate, and since it is installed in 1 PC then fine (you'll have 1 license for parallel & another for Bootcamp)
drewcopeland said:
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file.
Click to expand...
Click to collapse
Which version of parallels do you have? In version 5160 the usb flashing works fine, in 5582 it is broken, as is in version 5584. They had an special build 5582.5 which allowed me to flash my phone correctly and according to parallels, the "next" version will include those usb fixes.
I'm using the latest version 5584 and when I need to flash my phone, first i shut down windows vm, install parallels 5160 over the current version and then boot up windows. I ignore the installation of parallels tools and just flash my phone. Then shut down windows again, re-install parallels 5584 and all is fine again.
Hope this helps you...
that does. Do you mean the most recent update will work?
edit: never mind. the most recent is 5583. I'll try to find 5160
drewcopeland said:
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
Click to expand...
Click to collapse
If you have a valid license for parallels, then you have a valid license to use bootcamp...
That said, I have flashed through parallels and vmware fusion TONS of times (about to do it again, in fact). So long as you've routed the "HIGH GENERIC RNDIS" device to the virtual machine it should work fine.
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
http://forum.xda-developers.com/showthread.php?t=1056847
And if you have a P990, you're in the wrong forum (this forum is for the P999).
omerika.emir said:
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
Click to expand...
Click to collapse
The Roms for the p999 and the p990 are not inter changeable. Different frame work.
jrfaulkin said:
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
Click to expand...
Click to collapse
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Erocks said:
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Click to expand...
Click to collapse
VMware with XP on it/Google how to bypass limitation?
Found this to get Xp Mode on home edition idk if it works I just use VMware personally
http://m.tomshardware.com/news/windows-xp-mode-windows-7-win7,10213.html
Sent from my LG-P999
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
rs70 said:
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Click to expand...
Click to collapse
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
DreamerTKM said:
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
Click to expand...
Click to collapse
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
rs70 said:
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
Click to expand...
Click to collapse
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
DreamerTKM said:
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
Click to expand...
Click to collapse
Well, my primary PC is my laptop with 8.1, but I've got desktop as well with dual-booting Vista and 8.1 and it is way faster to do it on vista, than to partition HDD and install Windows 8. Also I'm not dev or some tinkerer, so I don't need to use fastboot that often.
To answer the second question, I closed all tabs regarding the drivers on 8.1 as soon as I did what I needed on Vista, so I'm afraid I don't have the link. I could probably find it somehow using my internet history, but I spent several hours browsing various forums, so it would take me an eternity...