Updating to WM6 ROMs on Vista - 8125, K-JAM, P4300, MDA Vario Software Upgrading

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!

Related

unable to revert to O2 rom

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.

Sorry

I posted this for the few people that were awaiting for the Herald kitchen.
So..i know that you must probably hate me till now, but sorry again i have to delay the porting of my Core Kitchen to the Herald.
It has come to my attention that there is still no way of flashing an Terra because there is no RUU and thus no means of flashing. I will see what i can do, meanwhile i got some work and i will leave for about 5 days.
If anybody has any ideas on how to help these people, please put it into action or give me a pm.
Cheers !
you can flash using Aserg's method which is what other cooker's have resorted to!
blackout203 said:
you can flash using Aserg's method which is what other cooker's have resorted to!
Click to expand...
Click to collapse
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Well hopefully they roll out that new RUU for WM6 before the months end. Would love to do some experimenting with it during my vacation next month.
anichillus said:
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Click to expand...
Click to collapse
Yes that´s true. And nothing to say sorry - you had enough trouble with your PC.
But this is what I got as away for falshing from bootloader.
The problem is that the singing of the nbh file doesn´t worfk correctly - i guess.
I've been using his tool from:
http://forum.xda-developers.com/showthread.php?t=311909
He doesn't really show a method, so what I've been doing is:
1. Using NBHExtract to dump an .nbh that's on the Herald Wiki.
2. I rebuild the .nbh using Dark Simpson's little utility using the information I had luckily written down before I bricked the phone. So I plug in my ROM (4.10.531.3) in the Version, HERA110 in Device ID. The only other thing is that I'm not sure about the CID.
3. Place the new .nbh file in a folder with an updater (the ROM Update Utility that comes with the ROMs from the Herald Wiki).
4. Get the phone into Bootloader mode, start the updater.
In this way I've got rid of the Invalid Device ID error (error 243 or something?) and now it goes to 3% and tells me that the image file is corrupt.
I'm very new at this so maybe you can see a flaw in what I'm doing, or maybe with your knowledge we can figure this out. I was *almost* to the point of trying to cook using a couple links you've posted (XIP, dumps, etc) and then put it all together in a signed .nbh, but Rapidshare was holding me back... making me wait 80 minutes between downloads -_-
Anyway... I've only been trying to update the OS.nb portion since I believe I only screwed up my OS, not anything else. I can still get into the bootloader, my IPL/SPL still reads 4.xxxxxx, and by "brick" I mean that the phone just hangs on bootup at the T-Mobile splash screen. Correct? Incorrect?
Click to expand...
Click to collapse
Perhaps we can work with it.
It is not a huge problem for HTC branded devices as there is a RUU to flash with if everything goes wrong. It's just a problem for our T-Mobile Wing and O2 Terra cousins (if they brick their devices). But it's nice to see some proper chefs taking an interest, never liked the pdaviet ROMS ever since they used a whole bunch of Faria's stuff without asking.
im running pdaviet now, but im hoping to see something other soon, its not bad though, just a bit slow..lots of "lagging" on the today plugin, I used the herald dump from tupisdin earlier, and installed my fav progs on that...was pretty dam fast on my phone...only problem was that it occupied more space on the main memory when stuff was not cooked into the rom itself...
trying to learn about cooking myself, not so easy as a thought
But I guess im lucky to have a unbranded htc p4350, If i brick, I just install the official Ruu from HTC
(btw, I DO use Vista for flashing, just changed the usb driver that WMDC uses to connect via USB to the old activesync 4.5 USB driver...)

i-mate KJAM stuck on bootloader

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

Can you bootloader flash rom in vista?

I searched the faq - but couldn't find the answer. I had to use xp on my 8125 for flashing - but the 8925 / kaiser is new to me. Do I still have to use a xp machine to ruu from bootloader for a 6.1 rom?
Possibly
I know that you are looking for a difinitive answer but I have an 8525, My Kaiser just arrived @ the house so I will begin modding it tonight but I haven't had any problems bootloading the 8525 in vista, alot of the threads say that ppl have but it worked eventually. it just takes me a hole lot of time to get a new phone to connect for the first time, after that it's business as usual
I flash and do all sorts of fun stuff using Vista. Just think "Mobile Device Center Connection" instead of "ActiveSync Connection" and you'll be fine.
The absolute best thing you can do is to search for "Flashing with Vista" using the search at the top of the screen. There you will find posts from the Hermes Section that are still relevant. You will rool back the drivers to the Activesync USB drivers & this is good for many reasons. 1. Flashing 2. Using Mtty if something goes wrong.
met3ora said:
I flash and do all sorts of fun stuff using Vista. Just think "Mobile Device Center Connection" instead of "ActiveSync Connection" and you'll be fine.
Click to expand...
Click to collapse
I follow this rule n everythings ran 100% smooth not a single problem!
Gotcha all - but, when i tried to run ruu from the 6.1 rom, nothing happend when I was in bootloader? Is there a special custom rom for the 8925? I had to use a custom one for my old 8125
Ug - XP did it... i tried oli's sim unlocker but couldn't get the whole job done in vista for some reason.... but I didn't uncheck advanced connections first!
new tilt
Ok I got home around 10 & have been trying to get this thing to work for like an hour & a half now, no luck, when I try to hard spl & it goes to bootloader it stays there for a minute then gives me an error
I think it might have something to do with the newer 1.93 spl - I did eventually get it to work with xp, but vista kept hanging and I did resets on the device even though the instructions in the roms said not to.... man, that's nerve wracking! I think the older 1.92 spl version ones work with the ruu better??

Upgrade to 6 stuck on windows loading

Hi,
I got given a couple of Treo 750 phones. Both on the Optus Australian Network so I scratched around for days and found the upgrade software. Shows update 2.27
1st one went perfect.
2nd one on same computer got through copying files and executing update and stalled at the start of completing update.
I got the Windows mobile screen show and it just was not loading for ages. Previous one loaded and then asked for input of Date, touch screen settings etc.
The installer can be re run but says no USB connection at the moment.
I have done a hard reset and get the palm display then locks on the Windows Mobile screen.
I saw procedures to use the Mini SD card but the cards I have won't work in any treo, they are not SDHC type but standard 2G ones.
I next found the recovery tool but holding the left lower button and then hitting reset did not work but does work on my good phone where it shows the coloured bars and SPL....
The left button is a bit dodgy so I suspect it may be faulty. Is there anything else I can try?
EDIT: Ok I pulled apart the phone, looks like it had a hard life as broken case around two screws and they would not unscrew easily. Found the tiny button had dry solder joints. Fixed that up and was able to recover using the reset proceedure.
Phone now working.
could you explain in more detail what you did. thanks man
webafile said:
could you explain in more detail what you did. thanks man
Click to expand...
Click to collapse
What would you like to know?
Once I physicaly repaired the phone as indicated in the edit I was able to hold the left hand button (which was faulty) and the reset at the same time that allowed me to get into the SPL mode and recover the phone.
I understand it very little and most posts on these forums are over my head.
I would like windows 6.1 but there is so much information that seems to conflict that I don't know I am game since it is now working on an official 6.0 Optus version.
I am happy to help but if you can maybe tell me where you are at the moment and what you want to acheive and what you have tried I hope I can fill in the gaps for you.
because im new to this to and i got stuck in the windows screen also. so i would like to know what to download and where from and step by step if you could please.
thanks man
webafile said:
because im new to this to and i got stuck in the windows screen also. so i would like to know what to download and where from and step by step if you could please.
Click to expand...
Click to collapse
Ok to start with what country are you in and what telco were you with eg Vodafone etc as you will need that as a start.
USA and im with AT&A
Try the method describe in the thread below - Mine work
Hi, you might want to try this method
Follow it one by one and do not skip a step
http://forum.xda-developers.com/showthread.php?t=460783
I just did mine last Saturday (it was a Vodafone phone)
AT&T should be easier since the Windows 6 ROM is easier to get
If you'd like to update to WM 6.1, you should upgrade first to WM 6
Something i read about the radio not working to full capacity if you upgrade straight to 6.1
As for the WM 6 ROM, i'm sure you can find it
Good luck
Hi All,
I have a Treo 750 and it WAS running WM 6.0 Professional (OFFICIAL) and I got it onto the phone and then tried to install WM 6.5 and then I downgraded to 5.0 and tried to update back to 6 and it bricked my treo, any of you wonderful xda ppl have any solution?
Also, I have tried installing the ROM again (via SD updater) and it looks like this:
SPLASH1 OK
BOOTLOAD OK
GSM OK
Micro P OK
EXTROM FAIL
OS
Update Terminate
UPDATE FAIL
I cant install the windows installer one as WMDC 6.1 or ActiveSync 4.5 WILL NOT show the device up on the computer. I have Windows Vista Home Basic, and when I tried MTTY, the only ports I get are COM1, COM2, and COM3. I can't get the usb to show up. Even with MTTY 0.01 when I got the USB connection, it would not open. Is it Vista? Or am I not doing it right? ANY HELP WOULD BE APPRECIATED TO GET MY POOR TREO BACK!!!!!!!!!
Thanks
~Mike
Try this?
http://forum.xda-developers.com/showthread.php?t=427519
simunlocktreo said:
Try this?
http://forum.xda-developers.com/showthread.php?t=427519
Click to expand...
Click to collapse
Is this universal (i.e. Hermes/BA/Trinity) or just for the Treo 750. I think what bricked it in the first place was installing a custom rom by veisen (WM 6.5)
~Mike
Didnt Work
That one thing didn't work. It keeps coming up ERROR 226: FLASH WRITE ERROR Anything else???
~Mike

Categories

Resources