i tried install the wm5 rom from sd, but stuck in "Reset to factory default."
use pc install, but it detect wrong model id as "HP ipaq" instead of "HP iPAQ rw6828". Is there a rom having a correct model id?
i start in bootloader, but the connection was not detect in windows 7. Is it i must use windows XP?
Related
hi to everyone,
about a year ago, i patched thr spl...now is 2.13.0000. Yesterday i tried to install to my imate jamin (s200) the new qtek s200 italian rom. The process start successfully and cheked the version. When the phone reboot itself and shows the bootscreen, he program said that there was error 260 and cannot continue; on the phone screen reamin the boot section. When i try to rebbot, it works, but in this way i cannot update my phone. How i can solve this??
i use windows vista and windows mobile device center 1.0 version; also, i used on innotek virtual machine, windows xp with activesync 4.5I would like to inform you, if you can help, theat about a month ago i sent my phone to the assistence because the audio didn't work (is it possible that the assistence did something that block the update??
thanks and please help!!
on the bootscreen, compares RUU on the right-up side,ipl 2.13,spl 2.13 and (all writes are in the red section) and usb on the left-bottom side (on white background)! that's all, i think i've said everything...please HELP!!!
THE PROBLEM IS THAT PROPHET CANNOT CONNECT AT USB IN BOOTLOADER
i've tried, also, to use camera + softreset and when reboot the writes RUU disappear, but still not recognize on usb when in bootloader.
Someone can solve this problem? please....
your problem is vista!
use native windows xp and not VMWare or some Virtual Computer!
have the same strange errors if i flash with vista.
how you have flash your ipl to 2.13??
i used the pdamobiz...i think my ipl was 2.15.0000, and after downgrade, it becomes 2.13.0000. Sound strange? So, do you think the problem is vista and the VM? but i read in this forum that lots of people flash hos phone using xp on virtual machine....but you mean that in vista if you plug the phone (botloader) in to computer, windows doesn't recognize it?
i havent test "win xp vm" on a "vista host". my work laptop has vista and i cant update any rom/firmware. vmware use the host system and his driver to route the usb device. possible the usb-subsystem in vista is changed to much ;-)
test it ... if work ... ok ... we can debug it!
SOLVED
SOLVED! I flashed the prophet on "real" xp. Now my spl changed to 2.20.000 and ipl remain at 2.13.0000. I have another question: if i flashthe phone with one rom of wm6 (which is better?or which is the rom with less bugs?), can i reflash with a wm5 rom without problem?
thanks in advance and thanks for your advice!!
I have a long fight with USPL and vista, but finally yesterday I won.
All you need to do is:
1. Remove your SD card
2. Do a hard reset or clean storage (some programs like battery status block full access to your device)
3. Connect your mobile to PC and make sure that activsync connection is established
4. Start to flash your device with USPL, when DOS part end and your mobile switch to bootloader mode vista will find new device and start instaling new drivers.
5. Wait till vista finish installing new drivers and unplug your device, do a soft reset
6. Next step is to change vista drivers to xp, to do this you need to fallow this instruction:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)
8. When USPL instalation will finish you can flash any rom you want to your arte
Succesfully tested on my T-Mobile MDA UK now I've got WM6 WWE.
Thanks pof for your great release
grabson79 said:
I have a long fight with USPL and vista, but finally yesterday I won.
All you need to do is:
1. Remove your SD card
2. Do a hard reset or clean storage (some programs like battery status block full access to your device)
3. Connect your mobile to PC and make sure that activsync connection is established
4. Start to flash your device with USPL, when DOS part end and your mobile switch to bootloader mode vista will find new device and start instaling new drivers.
5. Wait till vista finish installing new drivers and unplug your device, do a soft reset
6. Next step is to change vista drivers to xp, to do this you need to fallow this instruction:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)
8. When USPL instalation will finish you can flash any rom you want to your arte
Succesfully tested on my T-Mobile MDA UK now I've got WM6 WWE.
Thanks pof for your great release
Click to expand...
Click to collapse
Thanks for news about it..!
Worked for me.
Works Great !
One more notch on WM6 belt!!
Working great!!!
Used it to upgrade to WM6 (bepe's) and later, GSM (2.93.90)!!
Big
Thank you, this helped me USPL my orbit on vista.
Oh...My...God! That is so cool of you! Many thanks!!!
at step 4: do i stop after the DOS part? Or do i continue with the screen with the big picture of a mobile?
Because after the DOS part vista installs the drivers but i'm not yet in the bootloader screen on my mobile (but i've got a white screen).
at step 6: When i untick "allow USB connections" in the WMDC, my mobile is no longer in the Device Manager list so how can i then change te drivers to the XP drivers?
Sharkey1802 said:
at step 4: do i stop after the DOS part? Or do i continue with the screen with the big picture of a mobile?
Because after the DOS part vista installs the drivers but i'm not yet in the bootloader screen on my mobile (but i've got a white screen).
at step 6: When i untick "allow USB connections" in the WMDC, my mobile is no longer in the Device Manager list so how can i then change te drivers to the XP drivers?
Click to expand...
Click to collapse
First put your Artemis into bootloader then connect to your PC. Vista will install a driver for a PDA but this driver is not correct. You can find the correct drivers in the posts above this. After installing the NEW drivers you can reset your artemis and disconnect it from your pc. Restart it and just run USPL again. Has to work now.
Good luck!
ok what am i doing wrong...?
have followed all the steps above... but still get a 270?
am on official O2 uk WM6 rom but want to upgrade radio as performance / batt life have become dire since moving from the HTC WM6 rom to the offical O2 one....
device now syncs without drop out having changed driver to the old 2004 one... but still cant upgrade radio or USPL or anything ......
HELP!
the odd thing is the O2 wm6 rom updates fine within vista. but nothing will go over the top of it?
o21 exchanged my orbit... new one updates fine.. woohooo
first thanks for the news now we know the uspl works on vista
second 2. Do a hard reset or clean storage (some programs like battery status block full access to your device) is interesting to know this
grabson79 said:
I have a long fight with USPL and vista, but finally yesterday I won.
All you need to do is:
1. Remove your SD card
2. Do a hard reset or clean storage (some programs like battery status block full access to your device)
3. Connect your mobile to PC and make sure that activsync connection is established
4. Start to flash your device with USPL, when DOS part end and your mobile switch to bootloader mode vista will find new device and start instaling new drivers.
5. Wait till vista finish installing new drivers and unplug your device, do a soft reset
6. Next step is to change vista drivers to xp, to do this you need to fallow this instruction:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)
8. When USPL instalation will finish you can flash any rom you want to your arte
Succesfully tested on my T-Mobile MDA UK now I've got WM6 WWE.
Thanks pof for your great release
Click to expand...
Click to collapse
Second time flashing, help!
I succesfully flashed my Artemis (after using USPL)... At the moment, I'm tired of my cooked ROM and I would like to install a new ROM. Do I have to use USPL a second time?
Bootloader screen says: SPL 1.11.100 (or something like that...)
Many thanx...
Doesn't work, because Vista says that it is not a Vista driver. How did you all installed the drivers under vista???
cmon uspl gives error code 260
Though I am not new to these ROM upgrading things, I am always receiving error code 260 while trying to update the SPL by cmon uspl. I have already successfully updated by uspl, long ago. I have flashed several ROMs and tried most of them.
Why only cmon uspl is giving me such error?
Yesterday i tried to upgrade rom of my Qtek S200 device. I uploader temp rom after that when it comes to installation of wm6 rom my device could not connect to my pc via ActiveSync. I have Windows XP. When i plug the device to my pc it shows an error message : ""There was a problem installing this hardware Windows Mobile-based Device" What can i do please help me...
Put the device in bootloader, and flash a new WM5 NVID ROM.
http://wiki.xda-developers.com/index.php?pagename=Prophet_recovery
but i cannont connect my device with activesync when i try that it tries to find a driver. finds a driver and installs that but after that "There was a problem installing this hardware Windows Mobile-based Device" message appears and i can not connect my device to pc.
can i upgrade roms with Windows Vista?
Uninstall active sync. Restart. Re install activesync. Restart. Then put your device into bootloader. Disable connect through USB in active sync and then connect the device and PC and then try to flash a WM5 ROM.
Vista won't work with upgrading because of the drivers.
I had just write a post in my thread about this. I have the same problem intalling the device in PC.
Before I had put the actual ROM in my phone, I went to bootloader and inserted another ROM in this case an official one... right now I cannot go to bootloader . Do I have to do a HardSPL!? probably this is the solution for quaschi!
We wait for the opinion of more experienced members!
my hermes turns on, gets to the boot screen, and doesnt do anything.
I've hard reset it and it still wont work.
it has the WM 6.5 on it from http://forum.xda-developers.com/showthread.php?t=495280
it started messing up when i opened a rar with a rar tool.
so how will i fix it if i cant get it recognized on windows mobile device center for activesync?
Have you tried flashing a new ROM using the SD card method?
i dont have a SD card
If you have Hard SPL V7 installed I suspect it would be very similar to using XP with activesync... Open up windows mobile device center and go to connection settings... Untick "Allow USB Connections". Put Hermes into bootloader and run the RUU_Wrapper.exe file. Should work...
Cheers...
on the hardSPL it says update error 260 cannot connect to pda phone
Google translation from Russian.
1.When you try to include shows such a query:
2. Hard reset does not bring results, everything remains the same. When loading writes that operating system 6.5.
3. Activesync (winXP) and Windows Mobile Device Center (win7) offer before using the device to unlock it. Code is unknown to me, the computer device is not synchronized.
4. Flash the rom does not work. The reason - they do not see it (as it were). But in Device Manager device determines a driver on a well-established.
___________
I can not find the official windose mobile of 2003. I read somewhere that it can help.
Help please.
Photo for step 1.