Hi all,
to make story short yes it is possible to revive phone from doctest.
and warning DO NOT RUN DOCTEST on your lovely Typhoon phone...
Problem that I now face with my phone (actually its now too annoying) is that it can not stand more than 24h with one battery charge. Reason for this behavior is that GSMDATA "partition" on that DOC (Disk On Chip) is corrupted so as data that controls gsm radio strength and bla bla....
My question/request for some owner of this small great phone is:
Please use WST (Wizard Service Tool) and backup gsmdiag partiton. About THAT number i will not name , change it before creating backup image with WST (of course make backup with same tool for yourself before).
Other problem with my phone is that CID area is corrupted too but can anyone tell me really if i need it for any reason, as I can flash almost anything onto phone anyway... so if it is really needed please do a backup of it too
And yes it is time consuming to use SD card for repairing your phone so again
DO NOT type doctest in mtty EVER
Thank you in advance
P.S. and no it is not battery that is bad i have 2 spare brand new tested...
Related
Hello there,
I have a MDA from T-Mobile germany PW10A2 with an RUU version which was probably 3-13-12-GER and a RSU which was probably T360.
I dowloaded 2 update files on the site of T-mobile germany:
http://www.t-mobile.de/shop/handy/1,4855,2963-_50-0-99,00.html
- t_mobile_mda_ppc_update_v3_19_03.exe
- t_mobile_mda_gsm_gprs_update_v3_23.exe
Since I wrotte them an Email, no answer, and the page has been cancelled.
What have I done:
- I installed the PPC 3.19.03 through Activesync: no problem
- I then installed the GSM GPRS update: once it started updating on my MDA at 10% it kept stucked. After 20 mn I decided to interrupt.
Since that day I have the white screen with the litle keyboard down right and that's about it.
My boot loader is V5.15. when it runs it displays "WAIT", and then "GSM ERROR"
As suggested in this Forum, I bought an SD Card, and a card reader writter, I wrote the RUU file NK.nbf contained in the downloaded .exe file from T-mobile. I flashed my room (proposed when I cold reseted the Wallaby) and then : NOTHING HAS CHANGED !!!
I tried again with a cooked Rom flashing a NK.nb1 file and... I got the ROMKitchen splash screen and... nothig else.
The display stays all white, you can read "this ROM was cooked in the ROM Kitchen" all on top af the screen and in the lower right side I still have the keyboard Icon.
Now I'm really worried !
Does any one have a suggestion ?...I believe my problem is realy serious.
Pascal
Hate to tell u that mate, but if your device can't be recognized by ActiveSync, then the only action is to get the device to be repaired by a specialized center or replaced.
However, check this topic carefully .. it might help
http://forum.xda-developers.com/viewtopic.php?t=4123
Good luck
Good news bad news
I have an SX56 with att, I had the same problem. rsupgrade failing at 1%, hard reset, and then the device white screned. First, downgrade the rom. Find the old update program, open it with winzip (or winrar) and you should be able to extract the rom image. get http://wiki.xda-developers.com/wiki/XDAtools place the rom on an sd, softboot while holding down the power button. the device will now offer you the option to load the rom from the sd, do so. once this is done the device should display the old roms ID. If this works, format the SD card, create a directory 2577 copy the program RSUpgrade and associated files, rename it as autoexec insert the card in the phone, and you should be able to reflash the RSU, if this fails.... time to break out the jtag header or be ready to send the unit in
My MDA is dead and buried
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
After having flashed a cooked a rom in the kitchen, I still had the same problem, so in the perspective to bring it back to a T-mobile store, I reflashed the faulty file I had downloaded on the T-mobile Web site.
I hoppe they won't find out and make any trouble.
I like this MDA so much, I don't remember how it was without it !
All the best
Pascal
Re: My MDA is dead and buried
Pewinski said:
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
Pascal
Click to expand...
Click to collapse
send the phone to me, I could repair for you!
Thank's but it's under guarantee and I get it repaired or a new one for nothing.
Best regards
Hello,
i do something wrong,
i start the HimaClearJumpCode.exe on my XDAII, and now
the XDA always in the USB/Serial V1.01 mode and any
reset or remove battery don't restart.
could someone have a idea how to reset it?
Regards
Markus
Why do you start this file ????
AFAIK this file is used during the update-process by the
HimalayUpgrade and should never be used manually.
And AFAIK it definitly thrashes your as it jumps into the bootloader.
Try to describe what you want to do !!!
Alex
you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.
itsme said:
you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.
Click to expand...
Click to collapse
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.
upol said:
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.
Click to expand...
Click to collapse
extROM is different part. You can update without extROM
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
Hi to everybody.
I would want to set you a very strange problem that has happened to one friend of mine. He has installed the original ROM wm5 and he wants to pass to wm6, once connected the pda to the computer activesync unfortunately it tries to syncronize him but remains to syncronize to the endless (1° strangeness) one.
Later starting the official updating htc downloaded by the site, continuing with the instructions and reaching the prophetic moment in which the pda is disconnected by activesync and puts on in formality bootloader to adjourn from the prophetic error 260 that I have documented and I bring here you him:
Me being a little hacker and almost all knowing the methods to upgrade the ROM I have recommended him to try to put in formality bootloader to extract the content of the original file and to make to depart the file ROMUpdateUtility, but also them error 260. Not giving me for defeated I have tried the last method from me known, the updating from micro sd card.I have dictated him footstep footstep what had to do but not even this time of it to wanted to know to adjourn him (2° strangeness, doesn't know however if has correctly done all finding himself him in the Marche and me in Sicily ). I think that can treat more specifically him of the pc of the operating system, even if he has told me that it has the xp.
Now I put me in your hands, aspect suggestions on as to resolve.
I thank you in advance
And excuse me for mine bad bad..... English
To get your P3300 back to live
Don't worry if things goes wrong sometimes.
1.What you can do is maybe a good option if you have a P3300 without a
provider then you can better going
to the website of Htc register yourself (its free!) Then register
your model of your Htc Product.
Go to the Htc club. you will find your originale udate rom!!! This is also
to find it here.
2. There is a nother option.
copy your RUU_singned img to a sd card and put the sd card bac to
your P3300.
Start the bootloader by pressing the both key rec. and power
and hold em when your do a reset.
You will see a 3 color line on your screen then you will see
the install progres from your img.
wait and follow the instruction on that display.
I had also a problem a month ago but and this option by the sd card
did working fine for me.
Now I update the software and also the dial pad to vista look. That is
realy awesome!
It's working fine and do its job what this model has to do!
Succes and good luck!
PLEASE I need help! I have an htc p3300 and when I try to update it goes up to 3% and turns off. There isn't any rom that I haven't tried but noone worked . Is there anything I can do ? Thanks in advance
...
takes sd card out..
you done uspl.. if not.. click it in my signature..
I don't know what happened with my kaiser after backup. When reboot, device require a password, in fact I can't forget mine but it's still wrong
Anyone can help me fix it? (up rom is impossible because my device can't connect via USB with ActiveSync when device is locked) The software is Sprite Backup.
(Maybe something I wrote really difficult to know because I'm not good in English)
Did you really get a backup into SD card or PC ? - then maybe you have a bachup of everything and have no problems...
Do you have your documents in the SD card ? (not in the main memory) - then maybe you won't have to complain about them if you erase main memory
And, did you sync with your PC ? - then you'll have no problem to put them again into your Kaiser
If you answered "properly" the above question, then your best choice is, following this order:
1) Take your SD card and copy everything from it into another device, hard disk, pendrive, etc. so you'll be able to have another copy of it. Better if you get 2 copies.
2) The device OFF, plug it in the battery charger till the light will be green (this is, charge the battery)
3) Hard-reset the device ( press together both buttons which are used for the lower menu bar and then switch on your device - follow the steps in the screen when advised "you'll loose all your information")
4) Once the device will be accessed, switch it off, plug your SD card inside, switch it on, and try to use your Backup created with Sprite.
4.1) This maybe locks again your device with the wrong password. Then you must repeat steps 1-3 and loose what you got in backup with Sprite, so you'll have to customize everything and reinstall everything by yourself. (In fact this will allow you to reorganize things in a better way; do you remember that time you thought to yourself "I'ld better do it in another way" - this happens to everybody!).
Please, go to the Wiki to read more about hard-reset. Even, do a search about avoiding soft-reset when Sprite runs. Hope this helps.
Good luck !