Windows Vista VS Flashing Firmware or Radio ROMs! - JAMin, XDA Neo, S200 Software Upgrading

Upgrade OS pocket pc (RUU file problem how to solve ) in Windows Vista
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
http://mahmood1.com/Documents/USBAS.rar
http://mahmood1.com/Documents/64bit.rar
Best reguards to mahmood

NetrunnerAT said:
First of all, connect your device when it`s in bootloader.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
Click to expand...
Click to collapse
they were already running
NetrunnerAT said:
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
Click to expand...
Click to collapse
in the 64bit.rar there are drivers in the ruu-work-64bit folder and in the wce.zip. i tried both for my vista x64 system.
NetrunnerAT said:
then, kill wmdc.exe with any taskmanager
Click to expand...
Click to collapse
i also killed the mobsync.exe
NetrunnerAT said:
You are Ready. run ruu or connect MTTY.
Click to expand...
Click to collapse
the ruu simply crashes while trying to connect to the device. luckily the flash didn't start yet.

Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.

Yeah I live in New Zealand and I think the 700wx here are different somehow. For example I don't think mine has a bootloader period.. I tried all 400 ways of getting it into bootloader and all I get is a reset back to normal screen no tricolour.
Weird but unless I can get it into bootloader first I don't think its going to get anywhere. Which my palm 700wx just doesn't have I think.

i managed to do it with vmware on vista. tried all these methods but the programs crashes all the time, luckily not frying my 818pro as well!

I have the same experience. The NVID RUU works, but al others don't. By the way, the NVID also work with only the "old" drivers installed, not dis-allowing USB connection, not starting in bootloader and not killing wmdc.exe.
I don't know for sure, I noticed the RUU Utility version is newer. But when I just switch the nb.nsk file, I get an error, or it crashes just like before. Can it has something to do with the fact that the NVID RUU updates the SPL as well?

floepie said:
Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.
Click to expand...
Click to collapse
Try running command prompt as Admin and type
bcdedit /set nointegritychecks on
Then try again to install the 64 bit driver. It should work

I have just found the answer for Prime2007, i have a telecom treo 700wx and the previous codes for the bootloader didnt work for me either however if you go into your dailpad and press ##8778# your phone will reboot into bootloader also there is not colored strips just the treo logo with some numbers at the top.
If you want to exit without making changes you will have to pull out your battery

Unfortunally this doesn't work, as mentioned, with things such as Radio ROM update only...
If anyone finds out how to make it work for those I'd be greatly appreciative.

hey guys .. i follows all your step . but i still cant run the ruu sucessfull .. help please.. thanks

completed the tutorial exactly, and continued taking the same problem.
I get the same error. Help please.

Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)

l3v5y said:
Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)
Click to expand...
Click to collapse
Is G4 my prophet.
No have a solution?a new utility updater for Vista is posible?
Thanks.

Related

Vista Flash . . .

Hi Guys, Does any one knows if we still have the same problem flashing from Vista...I can not wait to flash my Universal from my Vista PC...but everytime I get a error message...
Any ideas?
At moment is not POSSIBLE to flash directely with MS Vista.
It's possible via a virtual PC or if you change drivers of activesync or PDA, I don't know exactely, i've read this in a forum but i forgot.
Via WINDows XP only at time
Via WINDOWS XP only at times.
moeaboelela said:
Hi Guys, Does any one knows if we still have the same problem flashing from Vista...I can not wait to flash my Universal from my Vista PC...but everytime I get a error message...
Any ideas?
Click to expand...
Click to collapse
Yeah I think you can, just install Activesync 4.5 to use its drivers instead of the Windows Mobile Device Center thingy..
and hey teddybear.. you're spamming.
nearly..
actually I have managed to flash under Vista using a solution founs somewhere on the Internet but it's the same I saw suggested here on xda. basically, you have to install activesync connection drivers (only them, not the whole AS program!) to Vista so it'll will recognize your device in bootloader mode. You can continue to use the mobile device centre afterwards.
This is just a preview of the procedure you have to go through, now use the search function or google to find the whole thing and do it, it requires not more than 15 mins (if you're quite a dummy), probably less.
greetings
The solution!
Check my info for flashing in Vista...
http://forum.xda-developers.com/showthread.php?t=313001
DaVince said:
Yeah I think you can, just install Activesync 4.5 to use its drivers instead of the Windows Mobile Device Center thingy..
and hey teddybear.. you're spamming.
Click to expand...
Click to collapse
Sorry...
i've see when is not possible to flash PPc with vista.
if now it's possible, ...it's very good!!!
As far as I know it's not possible to install active sync. The only way is the one I posted....
I confirm, 100%
cyberpunk627 said:
I confirm, 100%
Click to expand...
Click to collapse
Thanx!..........
i still cant get it working under vista
i tried what daunes has posted, but under dev mgmt i dont have "Mobile devices" at all!
any straightforward way of doing it?
@ dreamtheater39
Wich version of Vista are you running?
I hope it's not a beta version?!
And also what is very important is that you have to put your device in bootloader mode.
Please let me know!
duanes said:
@ dreamtheater39
Wich version of Vista are you running?
I hope it's not a beta version?!
And also what is very important is that you have to put your device in bootloader mode.
Please let me know!
Click to expand...
Click to collapse
Hey daunes,
I got it to work eventually! I hadnt put it to bootloader mode, so my device used to appear as "HTC Universal" in device manager under "Portable devices" which i tried to upgrade (driver update). In bootloader mode it showed up differently as you've mentioned and everything worked fine! A big thanks for this, i'm now finally able to flash and monkey around with different roms, something i quite missed ever since i moved over to vista!
Cheers!
San
No thanx glad to help

please help i beg you!!!

i JUST BOUGHT A NEW O2 EXEC, AND TRIED MY BEST TO UNLOCK cid AND SIM, O2 APPARENTLY SHIP THEM UNLOCKED, SO I TRIED AND IT WAS. TRIED TO cid UNLOCK BUT NO LUCK KEPT GIVING ERRORS. SO I BEGUN THE INSTALL CROSSBOW LATEST, AND IT THEN WAS STUCK ON O2 SPLASH SCREEN, TRIED TO REFLASH WITH THINGONASTRING, NOW ITS STUCK ON BOOTLOADER, SAYING V2.01 AT BOTTOM AND SERIAL OR USB (WHEN CONNECTED), I HAVE LOOKED AND TRIED ALL OPTIONS, I TRIED UNI_EXTBOOTLOADER, AND THE OTHER ONE WHEN I WAS STUCK IN SPLASH SCREEN. NOTHING IS WORKING, THEN I TRIED TO SEE IF I COULD INSTALL OFF CD WITH O2 EXEC, BUT CANNOT FIND RUU. THE ONLY WAY I CAN NOW GET INTO BOOTLOADER IS FIRAT ATTACHING THE USB CABLE THEN BOOTLOADING, I CANNOT DO IT WIHOUT USB CONNECTED, BUT IF I TOOK THE USB OUT AFTER I HAVE GOT IT INTO BOOTLOADER, IT STILL STAYS ON. WHEN I ALSO PRESS THE RESET WHILST USB CONNECTED, THE LIGHT ON O2 EXEC FLASHES RED EACH TIME PRESSED?
ANY HELP WOULD BE GRATEFULL.... COULD THIS BE VISTA??? AS THATS THE OS I USE.
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
vistar said:
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
Click to expand...
Click to collapse
Hi vistar,
Hopefully, you will have it sorted out by Christmas!
Yes, it is Vista problem and you need to change the USB Vista driver in your PC to XP driver.
I don't mean changing the Windows Mobile Device Center to Active Sync 4.5!
But the USB drivers. Look here:
http://forum.xda-developers.com/showthread.php?t=313001
http://forum.xda-developers.com/showthread.php?t=291723
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
I believe that the first post should solve your problem. If not try the others. Basically, in Device Manager of your PC, the USB driver should be the old XP driver dated 2004!
Any other year won't do you good!
Merry Christmas!
Happy New Year!
KOR!
It is highly recommended NOT to use Vista ... even with the proposed driver patch.
I have developed a Radio ROM issue because of this: http://forum.xda-developers.com/showthread.php?t=347375
If you are using Vista, it is highly recommended for you to use Virtualisation and install XP.
I have been using XP under VMware forever without problems as far as flashing my Qtek is concerned ... until my Vista mis-adventure that is. I know that VMWare is not free, but you may want to give http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx a try.
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
will try the threads above thanks, i have tried in vista, and also i use vmware too, with xp pro spâ. which seems to work better but get error ăđă, radio update error, i think i have wiped the radio??? as when the first screen comes up it says:
from,
Radio:
EXT Rom:
Bla bla:
to:
Radio: 2.?.??
EXT Rom: 2.2.??
Bla bla: 2.2.??
I cant remember what numbers came up, but it was blank at top and version numbers at bottom.
any help would be grateful
ok i got it to work , through vmware, i ran PsiDOC_WM5_20041_Taster, which worked think its WM̀ still but its back on, I want WM̉ though, i'll try again.. some advice wouldn't go a miss. thanks.
Note: If anyone has problems blame vista..... Good OS, Bad PDA Partner...
ok every rom i try fails with the following: Error 114, Radio Rom Upgrade error.
why is this??? i have looked through the wiki and forum, people have had this problem before, but no answers.
I have this when WM5 loads up,
1.09.00
42.42.p8
2.00.41 WWE
and bootloader v2.01 (G4)
just incase this info is needed.
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
vistar said:
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
Click to expand...
Click to collapse
If you have tried all the links I have given, you could have easily upgraded the ROM to Windows Mobile 6.
Read carefully, my above post #3.
Did you know that you could just flash the CE ROM (Main ROM), if the Radio is not flashing.
KOR!
KOR support center !!!
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
vistar said:
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
Click to expand...
Click to collapse
Read the four links, I have given you.
1. nk.nbf (CE ROM - Main ROM)
2. ms_.nbf (Extended ROM - Storage ROM)
3. radio_.nbf (Radio ROM)
If the ROM is in .exe format, than excute the ROM without hooking your universal to the PC. In the temporary folder, you will find all the files.
Read,
KOR!
sorry what i meant was how do i flash the files to the device??? i have all the files ready..
do i remove radio from folder then execute RRU? or do i use a different way?
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
vistar said:
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
Click to expand...
Click to collapse
Hi Vistar,
You are welcome. If you download the drivers from the first link in post #3, then you can use Vista without any problems to flash your device.
Just make sure that the driver is dated 2004 before flashing the device. Check the driver for the Portable Devices ->USB Disk in the Device Manager of your PC.
Best Regards,
KOR!
BTW, I did reply to your PM.
King of Rapture™ said:
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
Click to expand...
Click to collapse
Perhaps that's because both your Unis are G3 - and mine is a G4.

Stuck on the "boot" screen

Hi,
I tried to upgrade the ROM, unfortunately we had a power cut (sod's law haha) and my PC cut out. Now when I try to turn my XDA on (o2 exec) all I get is a dark screen with USB at the top and V1.01, I've tried the recovery tool included in the update but obviously didn't work because windows doesn't recognise the device.
Any ideas would be MASSIVELY appreciated.
btw I've tried doing a hard reset and pressing 0 but it just resets the device to the above screen =/
Thanks,
Lee
Just Re-Run The Rom Upgrade Utility And Reflash The Rom.
Regards,
OllieD
Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail
Ive Never Flashed With Vista And Never Will.
I Read There Was Issues And Didnt Think It Was Worth The Risk.
Its Never Wise To Run Flashing Software In An OS It Wasnt Designed For.
Anyway Flash With XP And Your Problems Will Be Gone.
I Dont Think XP Even Recognises The Device When Its In Bootloader The Flashing Software Just Knows What To Do, Although The Software Wasnt Designed With Vista In Mind.
Regards,
OllieD
leedavid said:
Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail
Click to expand...
Click to collapse
There are some year 2004 XP drivers available for Vista. Do a search and you will find it.
It is too late and I am tired. If you can't find it then I will try to help you later.
Good luck and don't worry as nothing is wrong with your device. Wrong drivers for PC.
KOR!
If nothing else works, try using mtty to erase the device, and reflash!
Oh, and word of advice: Never flash with Vista, it f.cks your device! Always do your falshing with XP, that's the most stable out there...
mzalan said:
If nothing else works, try using mtty to erase the device, and reflash!
Oh, and word of advice: Never flash with Vista, it f.cks your device! Always do your falshing with XP, that's the most stable out there...
Click to expand...
Click to collapse
I always flash my devices on Vista, and never had any problems. Though, you have to have proper XP 2004 year driver installed.
KOR!
leedavid said:
Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail
Click to expand...
Click to collapse
Do you try to flash via a hub connection? Because it's recommended to connect the device directly to the PC!
brother go to this link your problem is fixed
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
or this
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
respectfully
King of Rapture™ said:
I always flash my devices on Vista, and never had any problems. Though, you have to have proper XP 2004 year driver installed.
KOR!
Click to expand...
Click to collapse
well, yeah. but in that case, I could argue that the driver, which counts, is from XP
But anyway, most people here would recommend against flashing in Vista, unless you must. XP is just a lot more stable, and causes fewer problems. but let's not get into which is better, shall we?
help!!!!!
hey guys, ive been stuck in this bootloader thing for ages now its been a day ive had no luck so far im using vista myself and there is no XP computer available to me unfortunately. the mtty utility says cannot open ports, im not using a hub either and the unit_exitbootloader.exe does not help either i need some serious help please. the screen is stuck at USB on the top (whe i take out the usb cable it says Serial on top) and v1.00 on the bottom. please help, ive got vodafone v1640 version of universal. thanks in advance

Frustrations with RUU

I just got my brother's MDA (mine got worn out), and he had upgraded to a TNT WM6 build (not sure which one). I would like to either downgrade back to OEM T-mobile, or try another of the WM6 builds.
The problem comes when I try to run RUU, with the T-mobile version, it gives me an error and wants me to start over, with the SNN 3.1 upgrade, it just shuts down RUU and with both errors it give me the tri colored screen. When I remove the battery and restart, it loads normally.
I have a G3 wizard, IPL/SPL: 2.26, I'm running Vista on my pc, and I have the latest Windows Mobile Device Center. Also the phone is cid unlocked from when my brother upgraded. This is driving me nuts. I am relatively new to the whole rom flashing world, so any thoughts would be appreciated.
As a side note, I also can't get Wizard Service Tools to work, it won't detect my phone, so if that's part of whatever suggestion might be made, I can't really use that.
Thanks.
have you tried flashing from bootloader?
Camera/reset combinaion?
the idea is that you put it into bootloader first, then run the ruu.
Simple answer to all of your problems is Vista,its still not compatible and has many problems.Do it on WinXP,there won't be any problems and its highly recommended.
Secondly,WST_4.2.2 will not work in Bootloaders,it must be run on a working OS.
Agian...
And again, And again, and again...
Why is a thread saying that is a proved method to flash by vista?
Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469
Hey ather!!!
ather90 said:
Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469
Click to expand...
Click to collapse
Is there a special version for vista that works? maybe changing the thread name especifying the Version could helps? wich is it? home basic? Bussines? Ultimate?
lol, i meant which Bit do you have, is it a 32-Bit version or a 64-Bit version ?, if its 64, the above tutorial will work...but you have to find the 64-bit version drivers
hi, I've updated a rom before but never on vista 64 where can I find this driver?
64-Bit Drivers :
http://mahmood1.com/Documents/64bit.rar
Notes :
1. YOUR DEVICE MUST BE IN BOOTLOADER BEFORE CONNECTING IT TO THE PC
2. If you are running Windows Vista 64-bit, then driver signing verification is on. In order to turn it off, and, thus, load this driver, you have to reboot the machine and turn driver signing verification off.
When the OS starts to load, hit the F8 key. That will bring up the boot options screen. The "Disable Driver Signing Verification" choice is towards the bottom of the list.
3. if you are running SP1 on your system...updating these drivers will cause RUU to crash when you try to do an upgrade.
4. If you get access denied, try closing your AV and disabling your Firewall
Hope this helps

HTC Snap 511 (Willow): SSPL, HardSPL and original SPL by JockyW

Attached you find all you need to flash cooked ROMs on your HTC Snap 511 (Willow).
The sspl/hardspl are confirmed to work fine on the HTC Willow platform (HTC Snap 511).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC CEDAR platform (Ozone) is not supported. For the Dash3G and Ozone I have already developed a sspl/hardspl.
The packages contains a SSPL, HardSPL, patched ROM updater and the original Snap S511 SPL. The package is based on SPL v0.34
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Snap S511 HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.34.Hard")
5. to test the sspl and the hardspl you can flash a splash screen
Once the HardSPL is installed on your device you can flash any cooked or original ROM.
A donation for my work would be highly appreciated
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Donation
Donation has been sent. Thank you for this.
Good work!!!!
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
dougmwpsu said:
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
Click to expand...
Click to collapse
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Black_V!per said:
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Click to expand...
Click to collapse
Anyone care to donate their S511 to me for a week or so?
ookba said:
Anyone care to donate their S511 to me for a week or so?
Click to expand...
Click to collapse
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
dougmwpsu said:
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
Click to expand...
Click to collapse
Sure it can. Where are you though?
ookba said:
Sure it can. Where are you though?
Click to expand...
Click to collapse
Raleigh, NC. My next vacation isn't till the week of Christmas though, so maybe someone else can step up in the meantime. I'll also be out of the office again for a week in the spring.
first off, thanks so much to Jocky and Ookba for all the work you guys do! but i'm having some issues. i've dont a lot of searching on here and i can't find a solution hopefully someone can help me. i can't get the hardspl to run successfully.
my bootloader screen shows this:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
i'm using windows 7 (through VMWare on my iMac), everything seems fine until the pop up on the phone, i click the button (the not really a trackball button) and the screen goes black, i lose all connectivity through WMDC and the Rom Utility gets error 266.
If i don't click when the pop up shows on the phone, the Rom Utility will show and then the phone will go into the bootloader with USB written in the white area then i get the error 266 again.
of course there's no sim because it's a Sprint s511, and the sd card is always removed.
what can i do? i'd really love to get 6.5 on there, but i'm at a loss.
The fact that your running on a MAC with VMWare makes me think the issue could be in the connection...
Im not even sure if Win7 works, i could be wrong however. You wouldnt happen to know of anyone that has a WinXP machine would you?
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
I applied the HardSPL to my snap using Windows 7 and everything went well
robconway said:
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
Click to expand...
Click to collapse
Thats what it sounds like... Good to know it works on Win7 though SPIK3.
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
robconway said:
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
Click to expand...
Click to collapse
Must have corrupted during the download... Havent seen that since my 56k-days.
Glad to hear that!
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Jaymoon said:
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Click to expand...
Click to collapse
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
SPIK3 said:
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
Click to expand...
Click to collapse
How would I go about checking this?
I remember on my Samsung Ace, before the 6.1 update, I had to install an "application unlocker" that allowed unsigned programs to install. Is this the same thing with the Snap? Also this is the Sprint version, so I don't have a Sim card, or anyway to typically "unlock" this phone.
EDIT: Ah, now I know what you mean. I found the SDA Application Unlock here: http://forum.xda-developers.com/showthread.php?t=563761
The Rom Update Utility finished successfully! Now to move on to the next step... Thank you SPIK3
No problem, glad I can help.

Categories

Resources