I have a TyTN which I ordered from the States and live in Australia. When I put in my current phones SIM GSM/GPRS card the TyTN starts up by displaying the HTC logo and the following numbers at the bottom of the screen:
M 05
S 04 No GSM
B 05 D 1.18
For a brief second the No GSM pops onto the screen and then the machine boots up. It displays the little aerial at the top of the screen with the exclamation mark. It seems to do that weather there is a sim card in it or not.
I went to Telstra and tried a 3G card but it did the same thing. I also tried an Optus card as well and it also did nothing. After looking through this site I noticed that I do not list a radio or protocol version as everyone else’s does, or is it only listed after the network has been detected?
If I run the phone program and go to menu > options it does nothing but display ‘Unknown SIM status. Only emergency calls can be made without a PIN.’ This message is displayed regardless of weather or not there is a SIM in the machine or weather it requires a PIN. I cannot find any way to ask the machine to detect a network or choose from a number of networks or review status or settings.
Any information or advice would be much appreciated. :roll:
Regards,
Steve
From reading what you have put, it sounds like your device has no Radio Rom, or if it does its corrupt.
If you are in a posistion to return the device to where you got it from I would do that first.
If you cant (aka ebay etc) then I would try reflashing the phone with the appropriate rom and it should overwrite all the rom, radio rom and extended rom leaving you with a working phone.
Put the device in bootloader mode (press POWER and SIDE OK together and at the same reset with stylus), connect to it using mtty and once you see the "USB>" prompt type "checkimage".
You should see the Radio Image CRC checksum there and will be able to diagnose if there's any problem with it. For more info read this wiki page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Thanks guys.
Unfortunately it's not really an option to return the unit. I would rather sort it out myself if possible.
Pof,
I took your advice and put the device in boot loader. The screen came up with a series if coloured bands of red, green, blue and white. In the red band were the following details:
HERM200
IPL-1.00
HERM200
SPL-1.04
I ran the MTTY app. and it came up with the results that you can see in the attachment.
I suppose my next question is “where to from here?” Is it possible to reinstall the ROM of the same version I currently have or is there some other way to turn on the radios ROM?
ACCA001 said:
I ran the MTTY app. and it came up with the results that you can see in the attachment.
I suppose my next question is “where to from here?” Is it possible to reinstall the ROM of the same version I currently have or is there some other way to turn on the radios ROM?
Click to expand...
Click to collapse
I see this error in your attachment:
Radio Image CRC checksum = Checksum: Wait interpreter timeout 0x0
Click to expand...
Click to collapse
Looking at your signature I guess you're using HTC 1.18.255.3 07/22/06 English rom, right? This rom is available on the FTP, check it here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Try to upgrade it, and let us know if you have any problems after the upgrade.
I've had the same problem with one of the earlier units. No GSM. I've reflashed it with shipped ROM and it worked for a day. Then, one of the phone calls got interrupted and after soft reset - NO GSM again. At this point it would not reflash at all - was stuck at 4%. Good luck to you, but I strongly advise to replace this unit ASAP.
Cheers
Thanks Pof and ID64,
I downloaded the ROM and tried to reinstall but had the same problem that ID64 explains. My problem is it stops at 1%. The instructions say this is not a problem just soft reset or pull the battery out. Unfortunately you end up in a vicious circle and it keeps freezing at 1%. I even downloaded a different ROM to see if that would help. Unfortunately it did not.
As mentioned I bought the unit from an online vendor in the States. It’s taken so long to determine that there is a genuine fault rather than a config problem that I do not know if I can return it. I may have to test HTCs ‘worldwide warranty’. Does anyone have any experience with claiming warranty? I wonder if it’s easier to contact Taiwan rather than trying to send it back to the States? If anyone knows the best course of action please let me know.
:?:
Try going into bootloader and typing "set 14 0" to reset the unit to default values before you return it.
If you want to know exactly why the upgrade fails you can sniff the USB port while trying to upgrade using HHD USB Monitor, in the "complete" view you'll see the error message coming from the device. Export it to .txt and attach it here if you want some feedback about the error.
Good luck!
Thanks all,
ID64 I took your advice after trying to load the ROM. It would get to 1% and freeze. I tried the Dopod ROM and it would get to 14% then freeze.
I contacted the supplier (in the States) and he agreed to replace the unit once it was confirmed faulty. I had to send it to Denmark. I have just been informed that the unit is indeed faulty and they will send me a new unit. It is due for dispatch shortly. I will let you know once I have received it and it actually works.
Thanks again all. You were able to provide enough info for me to determine that the unit was genuinely faulty rather than a simple setting or software issue.
Cheers.
Similar error
I have a similar error to the one above with my T-Mobile Vario II. It is intermitant and can be resolved for a time by a soft reset.
The output from running the same test above gives;
IPL CRC checksum = 0x1C4C8E67
SPL CRC checksum = 0x921BC30
CE CRC checksum = 0x3766505C
ExtROM CRC checksum = 0xBC294D4A
Radio Image CRC checksum = 0xF0BF1EF5
Does this indicate that it isnt hardware?
Can anyone offer any suggestions to what may be causing this?
The problem seemed to appear when I changed away from the standard shipped radio ROM.
Thanks
Aidan
Related
There's two type of ROM upgrades: Operating System ROM upgrades and Radio Stack Upgrades.
Radio Stack Upgrades:
Radio Stack upgrades are distributed by the devices resellers. They come in packages with names that may or may not include "Programme B" or "RSU", and they are usually about 2 MB in size. Version numbers are a mess, and lower version numbers do not mean earlier versions. There's at least three different paths of version numbering out there, and the version number on the file doesn't always match the version number displayed at boot and by 'Device Information'.
The official Radio Stack Upgrade process is a mess. We've seen way too many people wreck their devices doing nothing weird or strange. Our advice regarding Radio Stack upgrades is to get them from your own device provider (so you know it's for you type of device: 900/1800 or 900/1900 MHz), and to only upgrade if you know the upgrade will fix known issues that are bothering you.
Operating System Upgrades:
Operating System upgrades are distributed by the resellers in packages whose names may contain "Programme A" or "RUU" (to confuse things, RUU stands for "Radio Unit Upgrade", even though they do not upgrade the Radio part but the PDA part). Operating System upgrades are usually 15 MB in size, and unless you use our utility 'adaptROM', they will only install on phones sold by specific resellers in specific markets.
In this community, the OS is sometimes also distributed as .nb1 file, for use with our XDArit tool. These files are often zipped to about 15 MB, uncompressed they are 32MB (well: 32 MB minus 256 kB actually).
We've seen a number of people doing terrible things to their devices by upgrading their OS ROMs. Here's what we've seen:
- It appears someone is distributing an EXE file for the PPC2003 ROM that contains a part of the OS in the spot where the bootloader needs to be. People that use this EXE to upgrade to 2003 may experience problems immediately or later on, possible making their device unusable.
- We've observed our XDArit tool in the hands of people that should not be using it. If you don't know what a DOS box is, or think you can rename .nb1 files to .nb0, or if you generally do not feel technically proficient, do not use XDArit. It's as simple as that.
(We also blame ourselves for this: XDArit is very counter-intuitive in some parts, and is long-due for an overhaul....)
- Apart from the above, there seem to be problems for people getting back from PPC2003 to earlier versions of the OS. We've been busy doing other things, and we haven't really researched this yet.
- It seems the exe files Jeff makes are OK, and if they aren't, people would know pretty quickly. We advise against running exe-files from others until we've found what causes this 'bootloader mangling' we've observed.
Thanks for your warnings. I just checked my device information. It reads rom version 3;14.06 ENG, Rom date 10/01/02, Radio Version T313. Being not technical at all. Your advice is not to upgrade the Rom or de radio version.
But that leaves me with some problems. F.i. when I try to synchronize with Outlook on my pc. I keep losing mails. The only mails being synchronized at all are those from my inbox. A series of attachments cannot be converted and there is no way to know which mails they are in. I was also hoping that a rom-update would solve my constant memory-lack.
Are there any other solutions?
Upgrade Fails
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Re: Upgrade Fails
scalci said:
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Click to expand...
Click to collapse
:wink: it's same problem that i have but the slution is download the XDA-dev's XDAtools.exe and cook your ROM then save it on your SD-card
for me it's work 100% my Qtek provieder in Saudi Arbia said that you can't downgread ROM after you do upgread but what ?? it's work
:lol:
[email protected]
Upgrade radio fail
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
After upgrad radio from 4.16 to 4.21, My O2 does not reset or hardreset normally. After a long process, I get a blank screen with only input icon on the lowwer right corner. How to fix it now?
problem solved.
inaccess said:
problem solved.
Click to expand...
Click to collapse
How have you done it ?
Re: Upgrade radio fail
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Re: Upgrade radio fail
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Re: Upgrade radio fail
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Re: Upgrade radio fail
droletbe said:
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Re: Upgrade radio fail
Weezer-DC said:
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Click to expand...
Click to collapse
Yes, I got the Wallaby bootloader and it said GSM failed.
Pls show me where about I could get more info on the forum.
ThanX in advance.
Re: Upgrade radio fail
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Re: Upgrade radio fail
droletbe said:
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Click to expand...
Click to collapse
Now everything works ! And this accident "forced" me to buy an SD, so I will not be so limited by the 32Mb limit
Thank you very much
help needed....
i hard reseted my qtek 1010 .... its like 30mins ....and am still gettin 4 bands white red greem blue... is that normal ...that hard reset take this much time... if this si not normal ... what should i do next
Bootloader not recognising sd card image
I am having the same problem. When pressing power and reset, bootloader shows v 5.17 GSM fail.
I have an sd card which has a new bootloader and nb1 file on it. I do a reset with the card in the slot and i get the same screen v517 GSM fail. From what i have read i should be getting an option to upload the new rom.
Can some one help me out please?
If I currently turn the device on normally activesync does not recognise the device.....
The sd card I have was configured using the xdirt programme and it appears to have worked as the sd card is shows not formatted now...
Thanks for all the info and warnings, just got my XDA II today and Im not too hot with it yet so I guess I will be leaving the ROM's alone for the time being
Peter Poelman said:
Radio Stack Upgrades:
Click to expand...
Click to collapse
We have several system where the GSM rom is toast. Is there a way to get a GSM Rom to SD w/o using the PC Monitor program?
The systems will successfully bootup and we have tried loading the GSM rom using RSUpgrade, but it fails after 1%.
Is there any other way to recover the GSM Rom?
You may try speaking to Cgigate on this forum, he has hardware methods of programming the chips directly, whether it works for the radio stack as well as the bootloader and rom you will need to ask him.
Hello all,
well it is not 100% free, you need to earn it.
The price is to allow me to downgrade the RSU to 4.16
I am unable to do this and have tried so many things so far without any success.
I have RSU 3.23 now
ROM wise, I have no problem, I can change it using the SD method and the ismgtool.
Well, I am sure you will ask, what is the guarntee? Tkae my word for it for the time being and try me.
You can send me a private message or e-mail me ([email protected])
If I receive the solution from more than person, I will look at the time I have received the pm/e-mail and the prize will go to the eriler responder.
HURRY :!:
and the winner is: to be updated
and the winner is:
no winner yet!!
Work harder folks
You have "RSU 3.23" and want to **downgrade** to "4.16"? What am I missing :?: :?:
yeah, numbers are meaninless!
Anyway, just solve to me the issue of downgrading 3.23
Hmmm ! i guess you can't
Hello
as far i know and if my memory still works i read something which says you Can not roll back to older version and that was on the 3.23.01 release note.
HTC Advice not to try to downgrade your GSM cause you might distroy your device and lose the GSM capabilities.
also few other issues include
Fixed: SIM unlock code hacked
1. Disable memory dump function.
2. Unlock code encryption.
Fixed: Do not auto-reactivate PDP context when network reject PDP context activation
Fixed: Specific message should store in SIM without affecting the VMI
Solution: Change the DCS of specific OTA message from 0x00 to 0xf2 (Store message to SIM)
Fixed: After dail a wrong number, dail second call with correct number within 30 seconds,
this call will be established for 2 seconds, then be automatically cancelled.
Solution: ACI state is not syncronize to MMI state. Syncronize the state of ACI and MMI.
Fixed: USSD Problem
Fixed: Inter-SGSN Issue
regards
Othman
www.pocketpc4arab.com
Othman,
are you replying to a different topic? :?
What is the relation between what you have written and the downgrading issue?
Place adaptrom.exe in the up or down grade application folder.
run adaptrom, then the up or downgrade application.
This will change the rom as well as the radio stack.
einas_canada said:
Hello all,
well it is not 100% free, you need to earn it.
The price is to allow me to downgrade the RSU to 4.16
I am unable to do this and have tried so many things so far without any success.
I have RSU 3.23 now
ROM wise, I have no problem, I can change it using the SD method and the ismgtool.
Well, I am sure you will ask, what is the guarntee? Tkae my word for it for the time being and try me.
You can send me a private message or e-mail me ([email protected])
If I receive the solution from more than person, I will look at the time I have received the pm/e-mail and the prize will go to the eriler responder.
HURRY :!:
and the winner is: to be updated
Click to expand...
Click to collapse
you can send me the device, i can run over it with my car, get AT&T to replace it with a new one ( I have insurance from them) and BAM! start from scratch
OK, how about this:
1. Obtain the RSUpdate.exe and accompanying files for the radio stack version you want to upgrade/downgrade to.
2. Copy them to the \Windows folder on your device
3. On the device (use File Manager), run RSUpdate.exe. This will manually update the radio stack.
4. Send the free XDA to me, since a winner is me!
JoshB
2JoshB: It is not so easy as you wish.
You may not downgrade 4.21 radio to 3.19 and below in this way (though it is Ok for greater versions). The restriction is by design and appears during actual uploading to radio module due to some kind of _internal_ checking.
I can suggest the following:
-convert RSUpgrade.cp64 you want to upload to binary format. Let it be 3.19 for example
-try to find 03 13 and 13 03 entries (= 3.19 in hex)
-If entries are exists -try to replace them with 04 15 or 15 04 accordingly (= 4.21 in hex).
-convert RSUpgrade.cp64 back to text
-try to flash these files in the usualj way (upload to windows etc...)
But this way is very dangerous. I mean that such a stupid replacement may corrupt radio stack code, so your radio will be broken completely.
More than that: radio stack version checking may be implemented not by number but features available in RSU. So version changes may not be enough to downgrade radio.
the more reliable way is to disassemble radio stack and bypas version checking in more sensible way. But unfortunately my qualification is not enough for doing this.
falconeyez said:
you can send me the device, i can run over it with my car, get AT&T to replace it with a new one ( I have insurance from them) and BAM! start from scratch
Click to expand...
Click to collapse
Can we send you a whole box to drive over ?
Till now, there is no winner
Will there ever be............
Prove the solution is working and there will be.
Soultions that work once like driving the car over it are not acceptable :lol:
Come On guys!
I am hoping someone can either point me to pre-existing plain-language instructions to resolve my issue, or they can walk me through the steps.
(I'll say in advance I'm not a developer, but after scanning through these forums, it seems that other people have had my same problem.)
While upgrading my Siemens SX56 from Pocket PC 2002 to Windows Mobile 2003, the handset rang during the first part of the radio stack upgrade. The upgrade subsequently failed, and now, as you might guess, the unit won't even fully boot.
(Note that bootloader confirms problem with "GSM error" message)
What it WILL do is show the AT&T Wireless welcome screen (with the BIOS version in the bottom corner - A.20.4, I believe), and after a long delay, the letters R and G appear above the A. Then the screen clears and the unit hangs.
Based on what I've read here, I think I need to download something to an SD card and then get the unit to boot off of that card, possibly to restore the radio stack. I have the ability to write info to the SD card using another PDA.
Can anyone help? If at all possible, I'd like to avoid packing the unit up and shipping it off to AT&T or Siemens. Like I said, I'm not a developer, but I'm somewhat application-saavy (if there is such a thing), so I'm appreciative for whatever plain-language help members of this forum can afford
TIA -
Sean
Same here !
I just posted a topic w/ the same problem....
I guess it should be possible to flash the GSM stuff from an SD card?
HELP .. HELP .. HELP ..
I know this subject is old but I could not what I need & how can I fix it
I have bought a pocket pc with phone edition from USA, and when I tried to insert my SIM card it asked me to but my PIN code, then ask me to but the unlock code (SIM code).
Now I am in Saudi Arabia.
WM2003
ROM Versino: 4.01.16 ENG
ROM Date: 02/04/04
Radio Version: 6.25.02
Protocol Version: 324e4
NOTE: I do not have a serial cable.
Thanks,
HFN[/b]
Check this: http://wiki.xda-developers.com/wiki/UnlockWiz
Hope it help you
Edit:
You have a WM 2003, this link work only for PPC2002
SIM Lock
DariusVE
Thank you for your help, I have tried this site, but It did not work because my device using WM2003 and also has no Wireless Modem feature.
Thank you.
Unlocking Quest
Here's my quest to unlock my T-Mobile PPCPE. I think some of this information might be useful to anyone confused about getting this
done.
First I called TMobile to request the unlock code. Since my account was up to date I figured no big deal right? WRong. My IMEI (or TMFT) number was not in their database so they could not give me an unlock code so they said. They told me to call the manufacturer of the device which they said was Microsoft. Knowing full well this was crap I called anyway.
The support guy got a good laugh; MS does not make devices
like this, they only provide the OS. He recommended I call Siemens.
So I did. Real nice guy named Jack had a good laugh as well. Not only could Siemens not tell me who really made my device (a third party made them for T-Mobile) but even if they had unlock codes they could not provide them because of contracts with TMobile. So I go back to TMobile.
The support people felt really bad about the run around and escalated really high up the chain (or so they said). AFter 48 hours I decided to take my own course. Having had good luck unlocking a Treo 600 through 'alternative means' I figured time to tackle the Pocket PC Phone Edition.
This was MUCH different and much harder to figure out.
After a good 12 hours and a whole slew of reading I finally figured out some stuff. Most of this may seem a no-brainer to some of the more educated XDA people out there but for us newbies maybe it will help.
----------------------------------------------------
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM
like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAUnlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the special edition rom and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (xda special edition)
then upgraded bacdk to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDATools
- XDARit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here on xda-developers.com, just
search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SDA backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data. In my case all my data is stored in Domino so I don't
give a hoot about the data on the device. Your mileage may vary!
Second I'm doing ALL of this with no SIM chip in the device. THis may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button
if when you get to the bootloader screen you see nothing more than
some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader.
Bring up xdarit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'wallaby' in the hex codes at the bottom of the XDARit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT).
Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.'
Type 'pnewbootflash_40116 nbl515.nb0' to write the wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0'
you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAUnlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because
some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it.
Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the special edition ROM you might
have some luck using the Installer that comes with it but apparently that
does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have
to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the sim is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 wallaby booting the xda special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 xdaunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use activesync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader
and radio stack if you want but I'm leaving well enough alone for now!
Hi ALL
I did unlock my phone thank you all.
Spicial thanks to "rhodwyn".
Best regards.
Works!!!
Thanks !!! Its working!!!
help in getting all the files needed....
Hi,
I would like to try this.... but where can I get the file pnewbootflash_40116.exe? Or is this a file that I'll create?
rhodwyn,
I would appreciate some help in getting most of the files.
Thanks in advance.
It worked for me too, thanks for the great solution, rhodwyn!
Thank you rhodwyn and everybody... my 2 cents
I love this site and I think that everybody does a great job. I found rhodwyn’s post to be very comprehensive and it is the one that ultimately helped me out this time. I don’t know if anybody is even interested anymore, but since I’ve been helped, I figured that I’ll try and help someone else. I assume that you’ve already read rhodwyn’s post.
I had the same starting configuration. I did everything that he suggested except for changing the bootloader and it worked perfectly. So, as he suspected it was enough to downgrade the radio stack and to load the special edition ROM. I subsequently upgraded my ROM and all is good (although I haven’t upgraded the radio stack and I’m not sure if I will).
I’ve read other posts about problems downgrading and upgrading the RSU and the 1% problem… I had a problem the first time I tried and I became very nervous, but I looked at rhodwyn’s post more closely and placed rsupdate.exe into PPC’s \windows folder and tried it again and was successful.
thanks
rhodwyn
10 minutes and done
Device: Qtek 9000 - straight from Dangaard with no operator personalisation.
Started out with the USB connection problem. Solved that according to descriptions in previous threads.
Flashing stopped due to it not being an O2 device.
Extracted files from the Xda_Exec_Upgrade_v113188.exe.
Tried to download /Uploads/Universal/MaUpgradeUt_noID.exe, but exactly that file could not be downloaded (I can download the other files - ????). Found another file called MaUpgradeUt_noID.exe linked from this forum. It is from 16/3-2005 and illustrates an S100.
Flashing seems to go OK. PC and Qtek says 100% complete after the 3 stages.
Hard reset gives the option of 0 for Factory reset or X for reset
Hard reset results (either 0 or X) in dark screen saying "Serial", "v1.00" (Bootloader?). I have now flashed 4 times with the same results :x
Can the cause of my problems be the "MaUpgradeUt_noID.exe" from March? If so, can someone give a working link for the right version of the file - please :wink:
If not - please help - I am in deep troubles
Best Regards
Steen
You have to upgrade the Radio ROM separately. Look for posts in here or Universal Upgrading for "unbricking your Universal" or something to that effect.
I have been looking and searching, but I’m unable to sort out of the abundance of information what should be done in my situation.
The installation information is blank for all the 3 groups displayed under “From version”, so I guess the device is totally blank – under these circumstances I can’t see why the radio Radio ROM should be updated separately.
Steen
IT'S ALIVE :lol:
Installed the seperate Radio ROM on top of the previous installations. It has now booted and I'm setting it up.
Thank's for the advice BeyondtheTech
... it was worth alot, all though I in my panic could not se the light at the end of the tunnel
Steen