Probs upgrading Qtek2020 - MDA II, XDA II, 2060 ROM Development

I run Vista and have "upgraded" the USB Drivers and followed the guide that should enable you to upgrade your devise in Vista as described elsewhere on this forum.
I put my Qtek in BootLoader Mode, put it in the crade and checked that the writing changes from Serial to USB and execute the HimaUpgradeUT_noID.exe from the [titipan.net]Hima - Helmi AKU3.5 ROM SP2.
After a while I get a "Cant Connect " error.
Now heres the "fun" part. If I just execute the file without going into Bootloader I get as far as the "Upgrading your Device" Screen. After a couple of minuts without anything happening I get the "Error 101".
Am I doing something wrong here or do I need additional Upgrading of Vista to be able to upgrade my device from WM2003 to WM5?

you can search around the forum for upgrading using vista as things with vista seem to work differently then xp
or you can try and get access to an xp pc to upgrade with

Related

Upgrading the Radio HELP

http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=18&Itemid=27
Quote "Follow the next instructions EXACTLY"
after following the instructions fully "now i'm stuck" . im installing the radio OS is MINI XP HOME, by pressing autodect the activeSync box apairs, click yes.
Then the folloing boxes apair, ERROR "could'nt query the device" and Error "Unknown version! Should pick SSPL"
i have installed HardSPL Version 6 (1.40.Olipro)
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=19&Itemid=27
That's funny -- i'm getting the same -- the only difference I noticed from mrvanx's screenshot was that mine says "IPL-1.00" on the 2nd line.
I sent him a PM.
1.) Do you have Windows Vista or XP?
There's a seperate guide for upgrading under Vista. Whats Mini XP Home?
2.) Do you have .Net 2.0 installed on your desktop? If not please make an upgrade.
Try the radio upgrade again, don't use autodedect and mark the boxes
.) SPL-1.11/1.13/1.30/1.35/1.40 New Bootloader
AND
.) is it a Hard SPL?
DO NOT MARK "Force Using SSPL"
I did it exactly this way some days ago without any problems.
My guide is only intended for genuine XP users, i cannot guarantee that this "copy" of windows is fully functional...sorry!
vista
In vista i get a Error Box "Unknown version! Should pick SSPL"
Once again:
Try the radio upgrade again, don't use autodedect and mark the boxes
.) SPL-1.11/1.13/1.30/1.35/1.40 New Bootloader
AND
.) is it a Hard SPL?
DO NOT MARK "Force Using SSPL"
As you are now using Vista have a look at mrvanx vista guide first.
If the box says, you should choose SSPL....do it ffs!!!
Im not sure if your doing this stuff correctly but like the post above this says you need to config vista first.
Ive got this error on XP SP2 and on Vista on two different computers and two different cables.
Just used the boxes above instead, no big deal.
Schooleydoo, did you try either of the above conflicting suggestions? I've got the same problem. Legitimate XP with .NET 2 and all current updates. SPL-1.40.Olipro loaded on JAs Jam no problems. Now NEITHER the radio upgrade, (1.40.30) nor the WM6 (Pro_Black_2.0) RUU's correctly detect the SPL version in the first step. Which boxes to manually check is in doubt and not helped by conflicting posts above. Did you persue this Schooleydoo? Did you take the risk and try one?
tomcroft said:
Schooleydoo, did you try either of the above conflicting suggestions? I've got the same problem. Legitimate XP with .NET 2 and all current updates. SPL-1.40.Olipro loaded on JAs Jam no problems. Now NEITHER the radio upgrade, (1.40.30) nor the WM6 (Pro_Black_2.0) RUU's correctly detect the SPL version in the first step. Which boxes to manually check is in doubt and not helped by conflicting posts above. Did you persue this Schooleydoo? Did you take the risk and try one?
Click to expand...
Click to collapse
If you have SPL 1.40, select the third option (which has 1.40 mentioned) and tick "is it hard-spl?".
How is this confusing!?
MrVanx -- i think i know what the problem here is..
it's that "unsigned blah blah blah error"
ppl stare at the screen of the machine, not the device. right before it "fails" to find and auto detect, a warning shows up on the device asking permission to run.
i have custel's 1.3 and used htweakc to allow unsigned in security tab (WM5 ppl can find this in the wiki and just about everywhere else on this site). This should enable auto detect to work.
I'm having a similar issue. When I click autodetect it asks if my device is sync'd and I click yes. It then says it can't detect it. I've done everything the guide tells me to do up 'til this point and I can't figure it out. I might try to check the boxes like you said above.
Update: I have version SPL:2.10 on mine and I accidentally clicked the 3rd option with 1.41 on it and it worked fine. I'm upgraded and am running w/o problems. No on to the WM6 black install.
I have had this problem too. I continued through the errors and everything worked. I posted my problem here.
http://forum.xda-developers.com/showthread.php?t=303436&highlight=errors
Someone noted that most the devs are using the most recent .net framework. I only upgraded to 2.0, not sure if theres anything more recent than that.
People having autodetect problems, please check this thread for the latest RUU. It will autodetect past version 1.4. As Donnyuga noted, it is also fine to just click the third option, that works too. Updating and using autodetect is just a little more error proof.

Problems with upgrading the SPV M3100

I recently purchased a SPV M3100 after reading many great reviews on this device.
I have just unlocked it using the HTC Hermes SIM & CID unlocker v3a using my old Windows XP laptop and it works great (I've tried using my Vista ultimate 64 computer earlier it didn't work).
I am now interested in upgrading my SPV M3100 to latest software available from Orange or the WM6 roms available on this site like Black Dymond, really keen in seeing its potential.
I have read through the Hermes upgrading forums carefully and made sure all is done properly. I have even read through the Mr Vanx step guides in upgrading.
First I decided to use the Orange update from their website.
After making sure the USB cables are connected correctly and allowing the WMDC to sync I proceeded to run the update.
I followed each step and tick the boxes. The phone goes into the tricolour mode or bootloader screen with the following on the screen:
Herm100
IPL-1.01
Herm100
SPL-1.40
On the computer, the window 'verifying your device' is on for few minutes, after this a new window appears indicating: ERROR 260 - update error
This happens again and again, day after day, I have soft reset the device, rebooted the computer, tried both the XP and vista computers, check the usb cable and connections, did everything that is said in the forums, but nothing....
I have even attempted to use the HardSPL program and followed the process to load the black dymond, but same message appears.
Must note that after soft resetting the device the phone returns to its original state, so no harm done. but no upgrade....... Damm...
Help... Any ideas ...... Please....
Many thanks
Danny
UK
Orange SPV M3100 / Hermes 100
Operator 14.123.1.614
ROM 1.23.61.4
Radio 1.16.00.0
IPL 1.01
SPL 1.40 Olipro
Update your WMDC to the latest version.
Then try again
Thanks for your prompt reply...
I thought when I originally installed the WMDC was the latest version as I have downloaded it from the Microsoft windows mobile website....
I have downloaded the appropiate Vista 64 version for my vista machine and the appropiate xp version for my xp laptop...
Did you download the latest version...are you sure??
http://www.microsoft.com/windowsmobile/devicecenter.mspx
Same problem -> Error 260 if I try to upgade.
Hi
I hve the same issue. Tried on Windows XP and Vista.
Also downlaoded the latest WMDC.
Could that be something with the area code?
I'm in Norway.
For XP should you not be using ActiveSync 4.5?
I re-flahed my M3100. The first attempt it failed, it then recovered itself and the second attemp was successful.
Im sure I have, just downloaded the other day, anyway I have downloaded it again just now, installed it, connected my phone and allowed the sync process to complete. I run the orange update again and still the same message..... Error 260: update error
What SPL version do you have?
To check press and hold BOTH the side ok button and the power button, then insert the stylus into the hole in the bottom of the device.
I have SPL 1.40 Olipro
So i take it you havent read or searched on this error, the orange RUU cannot recognise your device because you have anewer SPL version (HardSPL)...ffs dude had you told us that fact it would have saved you PLENTY of time. You posted you had SPL version 1.40...................you SHOULD have said you have already updated to HArdSPL (1.40.olipro)
follow my Safe WM5 Flashing Guide to get it done.
Sorry if I have wasted your time. I thought that I included the my phone details (SPL and rom etc) on my original message.
I have searched for this error, but I gather I wasn't getting anywhere...
So I thought I would ask for some help and advice....
Anyway thanks for replying with your help. I will check your link straight away.
If I still have problems, I hope it would be ok to ask in this thread.
Thankx Mr Vanx for all your help.
It is now working. I've loaded the WM6 Black IV Shadow rom.
Do you know when there will be a 3G / video dialer for this rom.
Many thanks
Hi MRVANX, i also have the same SPL and my radio is not working. I tried to open the link that you have pasted but the link is broken. Can you please share the info here or on my email address "[email protected]"

hardspl install problem (noob here) [vista x64, no sync w/ bootloader]

This is my first post, though I've been pouring over the forums everyday for a few weeks to try to get up to speed. You may notice that my join date is quite recent, but I only recently signed up! I finally replaced the broken usb port last night and then flashed wm6 from htc onto my hermes. This morning I've been trying to install Hard-SPL-V7, which failed, then I successfully ran the SIM/CID unlocker, and finally tried to run HERM-SSPL which failed. What seems to be happening is that after syncing and running RUUWrapper.exe the device goes to the bootloader screen:
Code:
HERM100
IPL-1.04
HERM100
SPL-2.03
But doesn't do anything else, and then the PC reports a disconnect error. I think that the device is supposed to reboot after going to the bootloader, but it doesn't. I have noticed that shortly after going to the bootloader, it flashes a white screen with red text, and then returns. It's so fast I can't read the text. After the error prompt on the pc (vista), I soft-restart the device and it returns to the today screen where everything appears to be normal.
What am I doing wrong? I read the guide for installing the hard-spl. RUU_signed.nbh is in the same directory on the pac as RUUWrapper.exe. The device isn't bricked. I'm stumped.
I appreciate any and all help. I know it's painful to keep answering the same questions over and over again, so I promise that I've been searching for an answer in the wiki and on the forums.
Also, thank you for these utilities, roms, forums, etc. It's amazing that so much is being accomplished by apparently so few.
***UPDATE***
More information is always better...
After wmdc is connected I run RUUWrapper.exe
I check Force using SSPL and go through the prompts...
Code:
From:
Image Version : 3.62.502.3
To:
Hard-SPL-2.10
The device goes to the SSPL as opposed to the SPL, I think, and displays this:
Code:
HERM100
IPL-SSPL
HERM100
SPL-1.09.ds
Then the pc prompts 'Verifying ...'
The device stays one the bootloader screen, and then the pc prompts:
Code:
ERROR[260] UPDATE ERROR
When I soft reset the device, it comes up to the today screen, and going to the bootloader displays this:
Code:
HERM100
IPL-1.04
HERM100
SPL-2.03
OK, I think I know what's going on.
I thought that I had gone through installing the vista x64 drivers from the guide but I hadn't. It doesn't matter much though as vista x64 really doesn't like unsigned drivers. I've not been able to get past that. So the issue was that vista x64 can't sync with hermes in bootloader mode. OK, fine, I guess that I'll be working with XP. Why oh why did I decide to try vista x64...
Has anyone else found a solution to this?
mangiaculo said:
OK, I think I know what's going on.
I thought that I had gone through installing the vista x64 drivers from the guide but I hadn't. It doesn't matter much though as vista x64 really doesn't like unsigned drivers. I've not been able to get past that. So the issue was that vista x64 can't sync with hermes in bootloader mode. OK, fine, I guess that I'll be working with XP. Why oh why did I decide to try vista x64...
Has anyone else found a solution to this?
Click to expand...
Click to collapse
Id stay clear of vista when trying to do flashing stuff....it REALLY just messes with all aspects of the process, regardless of if the WMDC is up to date.
Best thing to do is to get 32bit XP fired up and use that its just so much easier and everything else you use wont have to be patched/tweaked to behave on XP. LOL my vista config guide should really be a sly 'Uninstall vista, format and install XP SP2......guide'.
when you ran the SIM/CID unlocker, did you run it from your Storage card or did you use your usb to install? i think i had a similar issue. it would always give me the error 260. First, i sim/cid unlock my phone via storage card and it said unlocked and everything, but it still gave me the error 260. then i decided to just try to SIM/CID unlock via USB and when i did that, i didn't get the error 260 but instead it updated to Hardspl v7. hope that makes sense.
mrvanx said:
Id stay clear of vista when trying to do flashing stuff....it REALLY just messes with all aspects of the process, regardless of if the WMDC is up to date.
Best thing to do is to get 32bit XP fired up and use that its just so much easier and everything else you use wont have to be patched/tweaked to behave on XP. LOL my vista config guide should really be a sly 'Uninstall vista, format and install XP SP2......guide'.
Click to expand...
Click to collapse
Thank you both for the responses. I ended up going home and flashing on my xp machine. Our new work machines are 64bit and I had several options for os, and silly me, I thought vista x64 sounded like a good idea. It's been a challenge.
Anywho, hardspl is installed! I also flashed the black 3.0 wm6 rom, though my keymapping is strange for the additional key functions. I'm off to research an answer on that. Thanks!
Would it be possible to install virutal PC on vista 64-bit and just run a virtual instance of 32-bit xp? I guess my real question is whether it is possible to flash the phone from a virtual pc.
-thanks.
hi,
Yes, it is possivel , i do it, i recomend you using VMware soft, because virtual pc doen't have USB support.

Cingular 8524, upgrade to 3.12.3.7, in Vista, getting 294 error

Alright so I am so frustrated with this...and I am sure there is a simple solution for it. The screen on my old 8525 got messed up and since it was under waranty they sent me a replacement...the screen is ok on the replacement, but the phone isn't working (shows exclamation point next to "wine glass" rather than signal strength bars).... after hours and several phone calls to tech support, High End Devices waranty dept and who knows where else, it was determined that the current ROM version is incompatible with the AT&T network, I have to upgrade. So the version of the ROM on the replacement is 2.15.502.3 which makes wonder why in the world would AT&T send me a phone that would not work on their network? (I'm really trying not to vent here...) Anyways so I go to the HTC website as directed by the Tech. Support person download the stuff and after another hour on the phone with HTC and every possible sollution that they know is tried still can't install. I am running a Vista 64 machine and after getting around all the Vista quirks I am finally able to get to the Bootloader screen (button combination is: Side button [Ok] + [Power] Then push [Reset]...if done correctly your phone goes to the 4 bar boot loader screen, if not your phone soft resets and you have to try it again...) anyways in the bootloader screen it goes to the installation bar on both phone and PC and goes to 1%, then durring that one percent I get the horrible "ERROR 294 : INVALID VENDOR ID" on the PC and the Phone resets.....No matter how we have tried it it is always the same thing...redownloaded the file 3 times, restarted the phone about a gazillion times and the PC about 2 or 3 times. What can I do? I would love to have Ms Windows Mobile 6, but all I really want is a working phone....can anyone please help?
Some more info for those of you that can help:
On "Device Information" screen here is what I have:
ROM version: 2.15.502.3
ROM Date: 04/09/07
Radio version: {blank}
Protocol version: {blank}
On Bootloader screen:
In the top (red) section:
(in white)
HERM100
IPL-1.03
(in yellow)
HERM100
SPL-1.11
and then at the bottom (white) section:
(in black)
USB
(it says Serial when I unplug the USB cable)
I am trying to install the ROM titled:
RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
downloaded from:
http://216.139.227.230/download/Sof...502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
found by going to http://www.htc.com, Support, AT&T 8525, Software Download.
Thank you for any help you can give.
u cant be serious......you got an invalid model ID from an 8525 while trying to install an update from at&t itself.
well the solution would simply be to install hardspl (see the sticky) and then install the update. although there are many other easier and faster solutions i think this is the *safest* way. but then the fact that your radio version shows nothing makes me wonder......maybe a corrupted radio or something, which may or may not be related to the invalid model ID error.......anywho, search the forums for error 294 its probably been discussed many times
First of all thanks for your help. So I tried installing the 2.10 - Hard-SPL-V7 and it wont finish the install. I connect the device follow through the installation and when I get to the point where I push Yes on the 8525 the screen goes to the red/green/blue/white bars screen shows
HERM100
IPL-SSPL by Des
HERM100
SPL-1.09.ds
then the Computer shows ERROR [260]: UPDATE ERROR and the installation stops....
error 260 is an open port error, reboot your computer, and try again, if it doesnt work, try a different usb port, also disable watever firewalls or antivirus software you have
Okay so I diabled both the firewall (Windows Firewall) and the antivirus (AVG) and restarted the computer...tried 3 different USB ports...still the same problem....You don't think it could have anything to do with Windows Vista 64 and Windows Mobile Device Center. BEcause as soon as I go into the new Bootloader screen, the WMDC shows that the 8525 is diconnected now...even though it's not. I saw a post on here about installing drivers to get Active Sync on a Vista machine, but the drivers it provides are unsigned and Vista won't let me load them....so what's the next step? And again thank you so much for your help.
Is there any use in putting more effort into this or should I just have AT&T send me a new one?
whether there's any use left is ur decision, dont ask me to help you make your decision.
i know you can install unsigned drivers on vista, i dont know how, use the search. i have also heard that updating wmdc to the latest version helps too.
or you can either try and install hardspl using the microsd card, again use the search.

Error [262]: Update Error

Hi Friends:
Today, I tried to run my HTC MOGUL PPC-6800 in Bootloader Mode (SPL-1.07.0000) and then I run ROMUpdateUtility (Hard-SPL-MFG) to update the SPL to 2.40-olipro and I got the following:
- only 0%
- and finally ERROR [262]: UPDATE ERROR
I needed to do the recovery procedure and tired again and got the same results.
Can you help me?
Thanks
TecMan
Sprint HTC MOGUL PPC-6800
Windows Mobile Device Center 6.1.6965
Windows Vista 64-bits
You must establish a Activesync connection first and not be in Bootloader mode then execute Hard-SPL-MFG.exe. Checkout the updated Wiki:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
search is your frined
I recently did the update with 2.40 and DCD's ROM, I had the same issue. I don't know what I did to make it magically work agian. I tried three different times. Anywho, sorry I can't be more help.
Hi Friends:
I solved the Error [262]: Update Error, it was very simple...
1. I run the Microsoft ActiveSync 4.5 with Windows XP-SP2 and then run Hard-SPL-MFG.exe and my NEW SPRINT HTC MOGUL PPC-6800 got a Bootloader Mode with 2.4.Olipro
2. I run RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship.exe and I had the following:
Windows Mobile 6 Professional
CE OS 5.2.1629 (Build 18136.0.4.8)
ROM version: 3.35.651.2
ROM date: 02/22/08
Radio version: 3.35.04
3. in Bootloader Mode, I run DCD_3.0.1_Sprint and I had the following:
Windows Mobile 6.1 Professional
CE OS 5.2.19199 (Build 19199.1.0.0)
ROM version: dcd 3.0.1
ROM date: 02/22/08
Radio version: 3.35.04
Thank you for your support and now my NEW SPRINT HTC MOGUL PPC-6800 is working great!!!
TecMan
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
mrfantastic said:
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
Click to expand...
Click to collapse
Run this to exit the bootloader.
Sorry run what?
Sorry that was the problem i have that the titan_exitbl.exe
and it wont work and gives me the error msg i mentioned
mrfantastic said:
Sorry that was the problem i have that the titan_exitbl.exe
and it wont work and gives me the error msg i mentioned
Click to expand...
Click to collapse
Oops, sorry I misread that the first time.
If you did uncheck the allow usb connections, you may to try killing the device center process. I've had issues with that before (I use Vista as well).
Look for wmdc.exe in the Process list and try killing that. It should work if you then reconnect your phone. I've had success going that route on Vista anyway.
Tried that too didnt work
Weird because i kno my computer realizes something is connected but I try the titan_exitbl.exe and get that error
is it because im running on vista?

Categories

Resources