Has anyone found a way to upgrade to any WM6 ROMs on Windows Vista? I'm sorta at my wits end here!
In the Wizard Upgrading forum there is a thread "Upgrading your phone on Windows Vista". The driver instructions (which are really well written) work perfectly, but the RUU version fails with an "out of date" error.
There have been a number of other RUU versions suggested, but they all crash on Vista.
Shelltool works on Vista only about 25% of the time. Usually it just starts the flash process and hangs indefinitely. I was able to successfully flash XM6r4, but since then nothing else I've tried has worked. I did go back to the latest AT&T ROM afterwards, but haven't been able to get back to WM6 since. One of the things I tried was extracting the RUU from Cingular's update, but that one didn't work either, which confuses me even more!
All of the RUU Wrapper versions I've used to flash my Hermes work great on Vista, yet none of the RUU versions seem to be able to do so on my G4 Wizard (Cingular 8125).
Please, if anyone has any suggestions, I'd really appreciate them! I've searched and searched through the forums for different methods and versions, but have come up empty handed.
FWIW, I don't have access to an XP machine, and dual booting is not an option for me.
Thanks!
Dual Boot!
I just ended up dual booting XP, I noticed you said it was not an option, but did you know you can do it without reformatting through computer management in Vista?
Vista RUU
dktech said:
I just ended up dual booting XP, I noticed you said it was not an option, but did you know you can do it without reformatting through computer management in Vista?
Click to expand...
Click to collapse
Yep! Unfortunately that's not an option either. It's a matter of resources. I'm stuck with Vista, on which, I should point out, I can upgrade my Hermes successfully 100% of the time!
The RUU versions used to flash .nbh format ROMs to my Hermes all work, yet the older versions which take the .nbf format ROMs used by the Wizard don't!
There's got to be some solution. Using Shelltool usually works, but that only flashes the OS, not the ExtROM, splash screen, etc, so it's really only part of the solution.
Hmm i myself had some problems with flashing using Windows Vista. here are some observations i had
1) i first flashed using the origional tmobile rom (3.08 spl/ipl with 2.69 radio) i flashed it without doing anything special besides putting it in bootloader mode
2) next when i tried flashing it with a cooked rom it wouldnt work ( again i just tried to flash from bootloader mode without following any of the instructions givin in the Upgrading with Windows Vista thread)i found the RUUupdater version to be 2.0?? ( im sorry i forget the exact version numbers)
3) On checking the RUUupdater of the Tmobile that worked i found it to be 2.5???( again i forget teh exact version but suffice it to say it was newer)
4) i copyed the cooked rom nbk files to the Tmobile origional rom folder ( the one that worked on updating) but unfortunatly it wouldnt work
5) i then went to the thread and downloaded the drivers and installed them as the instructions said i should
6) i then downloaded the VistaRUU file they had there and then copyed the nbk files to that folder and VIOLA i flashed it and it worked like a charm ( again i flashed in bootloader mode)
This was just my experiance hopefully someone can figure out what i did right and why it worked for me and hopefully make it work for everyone else having problems
I thought there was a thread somewhere here about how to use Vista...if I remember, it may have even been stickied.
There was a stiki but it seems to have been unstikied and has since gone outta sight
Was this the thread??
It is still stickied if it is the thread.
I don't use Vista, so I haven't really read through it.
http://forum.xda-developers.com/showthread.php?t=338473
docnas said:
Hmm i myself had some problems with flashing using Windows Vista. here are some observations i had
1) i first flashed using the origional tmobile rom (3.08 spl/ipl with 2.69 radio) i flashed it without doing anything special besides putting it in bootloader mode
2) next when i tried flashing it with a cooked rom it wouldnt work ( again i just tried to flash from bootloader mode without following any of the instructions givin in the Upgrading with Windows Vista thread)i found the RUUupdater version to be 2.0?? ( im sorry i forget the exact version numbers)
3) On checking the RUUupdater of the Tmobile that worked i found it to be 2.5???( again i forget teh exact version but suffice it to say it was newer)
4) i copyed the cooked rom nbk files to the Tmobile origional rom folder ( the one that worked on updating) but unfortunatly it wouldnt work
5) i then went to the thread and downloaded the drivers and installed them as the instructions said i should
6) i then downloaded the VistaRUU file they had there and then copyed the nbk files to that folder and VIOLA i flashed it and it worked like a charm ( again i flashed in bootloader mode)
This was just my experiance hopefully someone can figure out what i did right and why it worked for me and hopefully make it work for everyone else having problems
Click to expand...
Click to collapse
What do you mean by putting the phone in bootloader mode first? In my experience, the phone has to be booted fully in order for the RUUs to work. Is there a way to get it to recognize the phone if it's already in bootloader mode?
If I put the phone in bootloader mode and then run RUU, the RUU just comes back and says it can't talk to the phone.
FWIW, I did the same as you, as far as flashing the original (Cingular) ROM and trying to use the RUU that came with that update. It seems that those RUUs won't work with any other ROMs.
Thanks for any help!
akashastrega said:
Was this the thread??
It is still stickied if it is the thread.
I don't use Vista, so I haven't really read through it.
http://forum.xda-developers.com/showthread.php?t=338473
Click to expand...
Click to collapse
Yep, that's the one! Been through it. As I mentioned above, the driver instructions in that thread are required when using Vista, but the RUU doesn't work.
Other than docnas here, everyone else has had the same problem as me. The Vista RUU comes back and complains that it's out of date.
I'd like to figure out what docnas did differently to get it to work. BTW, what version of Vista were you using? 32 or 64 bit? Mine is 64.
I'd also like to find out how it worked with the phone already in bootloader mode, since everyone says (and my experience has shown) that the phone needs to be booted and synced before the RUU will talk to the phone.
This may all be too late for me anyway. I'm giving my old Cingular 8125 to a friend, which is why I've been updating it. Unfortunately (or fortunately? ), once she has it, I'll only be working with my ATT 8525, which I can update and work with without any of the problems I've had with the Wizard.
Related
Hey All-
I'd appreciate any help anyone can offer. I am having problems updating to any of the WM6 ROMs out there (up here). One of a few things is happening:
1) Either RUU crashes just after it successfully sends my PDA in to bootloader mode, or
2) RUU is able to stay up, but for some reason, does not like the update file:
I either get an error: "This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.", or
it suggests the nbf file is "corrupted", I think indicating the RUU util I am running is out of synch with what the PDA is expecting.
I'm using a T-Mobile MDA (Vario?) and Vista.
I've tried all of the solutions I have been able to find:
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
* various flavors of the update utility to get around the crash, which do not let me upgrade to the ROM of choice!
* hard reset of the device
* I even tried pulling down one of the ROM upgrades from the T-Mobile dowloads site and dropping that in with a WM6 ROM nbf file. That was a huge flop.
I know people have done this! I've seen it over and over again. So what in the world stupid thing am I doing to not make this work?
Thanks.
Joel Niemeyer
Seattle
RUU doesnt work on Vista. Use shelltool.
Thanks for the advice. I'm sure it was good advice, but I am three hours in to it running now, and I don't have a good feeling about it. I think it says it would take at least 15 minutes. Not 180! Ugh, now I wonder what I should do?
Joel
jniemeyer said:
Hey All-
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
Click to expand...
Click to collapse
How do you do that? Thank you because when i try to downgrade my ROM or w/e so that i can unlock it when i gots to bootloader the fred green blue thingy it doesnt reconnect to active sync and maybe thats my probelm...=[
chaos, just look around for the RUU with Vista instructions- they are everywhere!
hey mate,
just follow this instructions http://www.modaco.com/index.php?showtopic=252977 to falsh every official ROM under MS Vista. Surely, when it comes to WM6 you gotta use the Shelltool.
regards
irm
Answer for Vista
My question is why don't people just dual boot vista with xp or 2000/etc...that would solve a lot of issues about the problems with vista.. just boot to xp..
I figure if you have the $Funds$ to spend on a $250+ phone you could shell out $50 for a 150gb 16mb cache HDD for your pc and dual/tri/quad/etc... sheeet son i've been doing this for years with linux/m$/mac.
Gotta face it, some software just runs better on one OS over another. peace out.
can someone confirm shell tool work
ANTC said:
can someone confirm shell tool work
Click to expand...
Click to collapse
I tried it, took like 6 minutes then it was completed, knowingly it wasnt flashed right, but did the hard reset on the phone and was stuck at the SPL screen, so just loaded up VMWare to reflash.
It worked for me...
I flashed one of the WM6 ROMs using my Vista Ultimate computer. One of the main parts in making the thing work is remembering to put your computer in bootloader before doing it. On post #7 in the MoDaCo thread, it says this.
Once more, here is the link: http://www.modaco.com/RUU-on-Vista-It-can-be-done-the-ultimate-guide-t252977.html
so your saying witht hat tut you flash a custom rom??
Yes
Yes I was able to. I don't remember which, but I think i was Core 2.0
Yeah, I was able to use shelltool to make this happen. Thanks for the feedback, folks. Only hang up was that it had appeared to have seized up (was seemingly stuck before the "End" portion). I waited for like 3 hours before I finally threw up my hands and hard reset the unit. Low and behold my wizard booted up in to the new ROM and I have been good to do since!
Hi Guys,
i consider myself relatively experienced at flashing HTC devices having been using and upgrading for a few years but i've run into an issue on my CID locked G4. i upgraded to WM6 without issue and i tried to revert back to my O2 rom, the flash failed and i'm now stuck at the splash screen. I've tried to flash the original ROM from boot loader but i get a 101 error unable to connect(can see it in device manager). as i'm using vista i did a search and found some instructions and driver files but i get the same result. the only thing i can think of now is to CID unlock but i'm not sure it will help (unless it allows me to do the SD card restore). any ideas guys?
IPL:2.21.001
SPL:2.21.001
GSM:02.25.11
OS:10.1.0.811
OK., what you need to do is use a PC with XP, because i have read that vista PC's can get you into a lot of trouble. When you are at an XP PC, follow the instructions in my previous post
( http://forum.xda-developers.com/showthread.php?t=313354 ).
When you flashed the original ROM, and you succeeded in doing so, think real hard if you still want to upgrade to a new ROM.
If you still want to do that, stick to a PC with XP installed (no vista!).
If you did reflash a good ROM into your HTC you'll be one step closer to upgrading your ROM.
Read this post thourougly :
http://forum.xda-developers.com/showthread.php?t=298613
as this will help you in case you didn't CID unlock your device.
(thanks vippie; this is the clearest walktrough i could find!)
If you are really sure you CID unlocked your device, you can flash your device to any ROM you think is useful to you.
If your device is really CID unlocked, you should be able to flash any ROM that is posted on this forum.
I know that it is that easy, because i have tried every WM6 ROM that is posted on this forum
good luck, and i hope in the end you will have the ROM that you want....
thanks. my device IS CID LOCKED and i've tried to flash it from 2 XP machines so it is looking like its a brick thanks anyway.
for sale wizard with pretty 3 colour screen - sold as seen!!!
One thing you can try is use another USB to mini USB cable, i have had one cable that didn't connect really well.
Sometimes it worked but if i moved my phone the connection went down.
I just thought of that because it was a while ago that this happened - I threw away the faulty cable and had no problems after that.
tried 3 different cables too
knownuser said:
tried 3 different cables too
Click to expand...
Click to collapse
How much do you want for it? I need a new screen and body shell!
jabreu203 said:
How much do you want for it? I need a new screen and body shell!
Click to expand...
Click to collapse
was actually kidding i'd like to fix it but i'm open to offers PM me.
ok .....HELP
i've paid for the CID unlock which went well i then tried to flash the O2 default rom failed error 101 (connection) i then tried wizard love failed error (300) in italian.
so stage 2 was to use the sd card recovery i ran the utility and then followed the instructions r2sd all etc..all seemed fine i restored the image to the wizard and rebooted it still won't go past the splash screen i've tried re-flashing and hard reset still no go....please guys any help???
If you have a memory card take it out. Right click on ActiveSync and go to connection settings. Uncheck allow usb connections then try to flash. With windows XP...
tried to flash on a win2K machine (4 pc's thats the only one thats not vista) still get error 101 on the original O2 rom and 300 on the wizard love rom.
still no joy anyone have any ideas???
http://www.t-mobile.hr/mdasw/RUU_Pro...R_WWE_Ship.zip fixed i'm on a tmobile rom i'll try downgrading again.
Hello everyone,
First - I'm really happy to have found this resource. I had no idea about all the cool things I could do to my phone. Thanks to everybody for all your hard work.
I spent a lot of time reading up with the goal of upgrading to a Windows Mobile 6 ROM. But now I need some help please, because I can't get my phone back!
I determined that my phone is a G4 (IPL/SPL of 2.16.0001). I attempted to load various WM6 Roms (TNT 4.0 Official and XDA Mobile 6), without success (error 300). Eventually, I succeeded in loading Wizard Love 2.26.10.2, and booted into Windows successfully. I then tried to load TNT 4.0 on. It got up to 100%, rebooted - and now I am stuck on the RGB / bootloader screen. Plugging in USB cable gives me the USB txt in the bottom left, but no response from the computer. The various RUU utilities I have tried to restore the phone back to Wizard Love or official iMate ROMs all fail - they can't seem to find the phone.
I would greatly appreciate any help. Thanks you in advance.
Regards,
Nick
Progress!
More research led me to find that WinXP should be able to install a new ROM without ActiveSync - in fact, you need to disable ActiveSync USB connections and end wscecomm.exe via task manager.
These steps allowed me to attempt flashing of a new ROM:
1. Uninstall device from device manager
2. Turn off device completely
3. Disable USB in ActiveSync
4. End process "wscecomm.exe" via Task Manager
5. Plug in phone, windows will detect and install as a Windows CE. This will make wscecomm.exe load again. End this before running the RUU tool
6. Run RUU. When detecting your phone, it will run wscecomm.exe. I kept ending it and crashing the RUU . RUU stops it itself.
7. Finally my phone was detected and I was able to proceed to flashing without an RUU error. Previously, i was getting error 260, 264, 300...
I was greedy and attempted to load XDA Mobile 6. It got to 99% and crashed. I will try and get back to Wizard Love.
If somebody could tell me what I am missing / doing wrong that would be great. To summarise:
- I have been able to install Wizard Love
- I have a G4 i-mate KJAM
- TNT 4.0 has reached 100%. On reboot, I only got boatloader.
- After many hours trying to fix, I finally was able to attempt to flash XDA 6 r2. It reached 99% before crashing
I will now try to put Wizard Love back on, but I really want to run WM 6.0 and am not very concerned about which flavour. Thanks for your help
No...You shouldn't use RUU for upgrading to WM6 because your G4 is not unlocked (You need to pay to unlock a G4, however it is not required if you don't use RUU).
Flash to Wizard Love, then get a copy of ShellTool and use it to flash the nk.nbf inside WM6 RUU.
no worries. I have the same phone and running XDA r2a, so it can be done!
Simply get hold of G4_step_by_step_install_wm6 I think theres a link to rapidshare on this forum, try search. (I will try get the link later on.) Follow the steps and it has shelltool which will extract th OS for and you can then install. Make sure you get the splash screens from XDA thread so you get the full package.
Good luck
G4_step_by_step_install: http://rapidshare.com/files/22275022/G4_step_by_step_install_wm6.rar.html
link: http://www.megaupload.com/?d=VRYOZ4GO
Read this: http://forum.xda-developers.com/showthread.php?t=293480
You need this: ftp://xda:[email protected]/Uploads/WIZARD/Unlocking/ShellTool_bugfixed.zip
G4_step_by_step_install_wm6 will give u step by step guide on what to do.
Thank you
Hey guys - thanks so much, I can't wait to get stuck into it.
You know I spent my whole weekend getting into this stuff and I'm sure I have only just scratched the surface!
I think it's fantastic that so many of you put so much work into this, and then also have time to guide people through the process.
Regarding the FTP links throughout these forums - They never seem to work for me. I get an error 550 - failed to change directory. These are links with usernameassword of xda:xda. The only link that worked had something different, along the lines of xdaupload:xda, can't remember for sure.
What am I doing wrong?
Just get the G4_step_by_step, forget everything else. Its on rapidshare. It has even a WM6 Rom in it so you can even that on your Wizard. But you can install XDA R2a also by following the step by step guide and knowing what to replace. Have you downloaded it? Its about 75MB but well worth every bit of it! You wont need anything else after that.
We learn from each other! Thats why we help others so they help us too
cochumbo said:
Regarding the FTP links throughout these forums - They never seem to work for me. I get an error 550 - failed to change directory. These are links with usernameassword of xda:xda. The only link that worked had something different, along the lines of xdaupload:xda, can't remember for sure.
What am I doing wrong?
Click to expand...
Click to collapse
The forum carried many ROMs before. Micro$oft had some opinion on this and hence the ROMs were all removed. Most of the 550 errors would be due to this.
kernelguy
Hi,
I've recently rooted my phone and moved from WM to Myn's Donut NAND build. I like it a like except for a couple things. The most annoying is that my phone reboots every time it enters sleep mode, either from timing out or from me sending it into sleep manually.
I've reflashed the ROM a number of times with different builds, and even some of the other ROMs. Same problem.
I tried flashing back to one of the custom WM builds and that was even worse, it rebooted soon after coming up to the WM desktop. I never had problems prior to unlocking and doing the initial ROM flash.
It seems odd that I would have picked up a hardware problem right as I did the unlock and first ROM flash. Does anyone have any ideas?
Thanks
what unlocker did you use?
I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
First and foremost, make sure you have unlocked your phone with the "2.31 CoKe" HardSPL. If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely have already done this. If not, perform the steps HERE first, before continuing.
Click to expand...
Click to collapse
tsrich said:
I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
Click to expand...
Click to collapse
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..
mssmison said:
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..
Click to expand...
Click to collapse
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.
mrono said:
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.
Click to expand...
Click to collapse
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...
JM-PDA said:
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...
Click to expand...
Click to collapse
just use the unlocker v.40 then flash stock rom, then unlock again with the .31
as for the url, just google vogue unlocker .40
How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?
tsrich said:
How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?
Click to expand...
Click to collapse
flash it via sdcard or through bootloader
cp0020 said:
flash it via sdcard or through bootloader
Click to expand...
Click to collapse
Maybe I'm doing it wrong then.
I opened up the vogue_unlocker.exe and extracted all the files to a dir. I changed into that dir and copied the VOGUIMG.NBH file to RUU_signed.nbh. I've had to do that for other ROMs, so I did it just to be safe. I then put the phone in bootloader mode, and connected it via USB. Then I ran the ROMUpdateUtility.exe from that dir.
It wanted to update from image ver ' <blanks>' to image ver ' 1.00.000.0'
It runs through the install, but doesn't seem to update the ROM. The bootloader still shows SPL-0.41.CoKE
I ended up flashing to a custom WM ROM, which let me establish an Activesync connection, so then I could run the full .40 install from windows, which worked.
I am trying to flash the ROM on my Touch Pro 2 before I sell it. I am running windows XP on a mac using Parallels 5.0. I have tried running the ROM update when active sync is connected and all starts ok then I get error 226 saying cannot connect. I then tried flashing straight from a newly FAT32 formatted microSD card and that jsut stocks on with a Loading message. So I tried flashing Hardspl, although I think that I have done this before when I still had a pc, but that failed with a connection error too. Any tips/advice anyone?
You need to provide more information. Are you trying to flash a custom ROM, and which one? What ROM are you running now? What version of the phone do you have/what carrier?
If you are still HardSPLed, the second line of text on the bootloader (tri-color) screen will say "OliNex", probably saying "SPL-0.85.Olinex". If it doesn't say this, the SPL is locked, and you won't be able to flash a custom ROM.
If you are trying to flash the stock ROM, I think some people have been having trouble doing so with the phone HardSPLed. But it may depend on what stock ROM. I am able to flash the Euro stock ROM just fine on my HardSPLed phone.
ok, i'll try to answer your request for more info:
trying to flash Energy Rom build 23699.
Existing ROM version is listed as 2.07.401.1 (80303) WME dated 2/4/10.
Phone is an unbadged HTC Touch Pro 2 as sold by Tmobile etc in UK.
Can't see any mention of OliNex on bootloader screen, so perhaps I didn't unlock= it after all. Certainly no T mobile stuff left on the phone now.
??
jbevan said:
ok, i'll try to answer your request for more info:
trying to flash Energy Rom build 23699.
Existing ROM version is listed as 2.07.401.1 (80303) WME dated 2/4/10.
Phone is an unbadged HTC Touch Pro 2 as sold by Tmobile etc in UK.
Can't see any mention of OliNex on bootloader screen, so perhaps I didn't unlock= it after all. Certainly no T mobile stuff left on the phone now.
??
Click to expand...
Click to collapse
Don't know off hand what ROM that you have installed right now. What do the boot screens look like when you start the phone? Also, what does the bottom row of red letters say, when you startup the phone?
If it doesn't say Olinex on the bootloader screen, you are not HardSPLed. Either you never did it, or you relocked it.
Run HardSPL, and you should be able to flash from the SD card no problem.
Redpoint. Thanks for your replies and interest. I have tried to run HardSpl but this fails with a 260 connection error, even though Activsync is synced and connected. Id this to do with running a virtual pc on a mac perhaps?
Your welcome, hope my advice is helpful.
HardSPL is pretty finicky, even on Windows Vista and Windows 7 systems. I think running it on a Mac is difficult or even impossible. You can search the HardSPL thread and see if anyone was able to get it to run on Mac. I'm pretty sure I read different users on that thread mentioning issues with running HardSPL on Mac.
My best advice would be to run HardSPL on a friend's Windows XP system, if possible. It usually runs smoothly on XP, and only takes a couple minutes.
Yes, that confirms my suspicions. I will try it frommy partners windows XP netbook whenshe gets home. Fingers crossed.
Will let you know how I get on and if I need any more help!