Develop Bugs

Which chip store the Bootloader and the WinCE ?

Dear XDA Developers #... and all other experts,
I had a T-Mobile MDA and I'm affraid that my bootloader had problem with all the buttons. The bootloader V5.15 boots and show GSM OK but none of the action buttons working ? Any Clue ?
Is the Intel #3204C 32MB Flash Memory chip store the bootloader and the WinCE because I had some technical guys who be able to clone the chips using some clonning machine.
Please advice as my MDA had been down for 2 weeks.
Thanks in advance

I would guess you have a hardware problem with the buttons.

Did flashed with SD card but checksum not correct
Dear Peter Poelman,
I did flashed with SD Card 2 weeks ago. Using the XDArit (old ver) and with O2 3.14.13 Rom. I did many restored but everytime it said restored completed but checksum not correct.
I did managed to see the O2 boot screen ( Blue O2) showig 3.14 at the right bottom of the screen but not be able to load the WinCE.
Is there a limit or counter that say number of times SD card restored ?
You think is hardware problem, any solution ? If you think where the fault is, maybe I be able to ask a Technical guy to open the MDA and repair it.
It is not possible to find any T-Mobile support around Asia.
Any respond would be much gratefull

Question: how big was the SD card you flashed with? (It has to be 64 MB minimum if you back up OS and bootloader at the same time.)
I would use XDArit to write an SD card (32 MB card is ok) that contains only the WinCE (OS) part, and try to flash from it. If your card is somehow corrupted, you can use XDArit to read from the OS from the Special Edition nbf-file inside Jeff's exe-file, which you can extract if you open the exe-file with WinZip.
Is there a limit or counter that say number of times SD card restored ?
Click to expand...
Click to collapse
They actually built such a mechanism for bootloader 5.17, but gave up on it (maybe after is was cracked by us?). But this really does not apply to you as you probably do not have this bootloader (or you would not have been able to make a backup).

Bootloader doesn't kick start to restore ?
I am using a 128MB SD Card.
Now even I wrote the SD Card with the new SER 1.1 .nbf files and insert the SD card into the XDA, Bootloader boots up but it doen't show the screen that say press action buttons to start restore ? It only show Wallaby Bootloader v 5.15 and freeze....
I am afraid that the bootloader on the XDA might be corrupted as well. Any tips or solution for these problem.
I remember reading in this forum saying that the XDA be able to lock all buttons accept the Power button. Seems like my case, the Power buttons, soft reset and hard reset buttons working only, the rest are not functioning. The XDA are still be able to charge on the craddle and the power worn off quite fast. Sometimes I even be able to see the Phone Cancel Buttons ( Red one ), the red light are always on...
Any help would be much grateful
suajw

Re: Bootloader doesn't kick start to restore ?
suajw said:
Now even I wrote the SD Card with the new SER 1.1 .nbf files and insert the SD card into the XDA, Bootloader boots up but it doen't show the screen that say press action buttons to start restore ? It only show Wallaby Bootloader v 5.15 and freeze....
Click to expand...
Click to collapse
You used XDArit to write the card, right?
You need to describe in much greater detail what you do for me or anyone to be able to help you.

I'm having a T-Mobile MDA in 3.13.12 GER ( 09/16/02) Radio T310
Bootloader v 5.15 and trying to flash O2 3.14.13 Eng Rom :
1. Using bootloader backup Boot+CE to SD Card.
2. Using XDArit (old ver) Read SD and store to PC ( WinXP )
3. Run RSU-eng of O2 Ireland, sucessfully upgrade, GSM no problem.
4. Run RUU-eng of O2 Ireland, Rom Image not found, error 007.
( forget to patch the NK_wallaby31413wwe_o2Full.nbf )
5. Decided to use XDArit (old ver ) to write Boot+CE ( O2 3.14.13).
6. Insert SD Card into MDA, flash restore compeleted but said checksum not correct
( Repeat many times of writing using XDArit (old ver), sometimes CE only but still checksum not correct )
7. Few occation, manage to see the O2 boot screen showing 3.14 but freeze
8. Left the MDA for few days and try the writing using XDArit again
9. Now soft boots, Bootloader boots show GSM OK, but none of the contact, calender and volume buttons work. If there is a SD card in the MDA, bootloader boots show v 5.15 but not be able to read SD Card.
( some of my posting are on Rom Upgrade forum under suajw)
Just to let you know all the about was done before the release of your SER v1.0 and v1.1 and the new version of XDArit v1.02
The MDA still be able to charge the power but will discharge if leave over night.
Any help will be much gratefull

InitDebugSerial can load bootloader+CE ?
Dear Peter Poelman,
If i boot the bootloader in a serial port from a PC using Hyper Terminal, do you think i be able to load the Bootloader+CE from a SD Card using the comand :
c2r ( from your Wallaby Bootloader Page )
Please advice and many thanks in advance
Notes : have not try using serial port to talk to the XDA

Good idea. Try and see, I guess.

Try hooking up the XDA to the serial com and it still not be able to communicate with XDA, even ? <enter> doesn't show any respond.
What could be the problem ?
By the way Peter Poelman, which is the chip that store the Bootloader+WinCE, I might need to ask someone to clon the chip for me from another XDA.
Thanks for your help and time

Still waiting for reply ????
Dear XDA Developers #.....,
I am still waiting for some replies in this matter....
Any info and advince would be grateful, Thanks.

Re: Still waiting for reply ????
suajw said:
I am still waiting for some replies in this matter....
Click to expand...
Click to collapse
Can't speak for anyone else, but to be honest, I have no idea what your problem could be. It's something odd, and looking at the steps you performed, my first guess would be that it could be hardware related.
Did you try a different SD-card? 64MB or bigger (when doing BOOT+CE, 32 MB or bigger for CE)? A different SD-card reader/writer?
The fact that it first reported checksum error and now doesn't read the card at all is funny. Suppose there's nothing wrong with the bootloader that's in there, but that you have some weird hardware problem that messes up communication with the hardware-buttons and with the SD.
Once you tried a different SD-card: maybe open it up and clean the SD-card contacts? (And don't come complaining if you end up breaking it further, it's just an idea...)
Either way: I spent some time thinking about it and replying to your posts. Until new facts surface, I really have no clue what to do in your case, and unless I happen to come accross the same problem again, chances are I will not have a clue two days, two weeks or two months from now. Sorry....
Maybe you can have it repaired?
Good luck...

Still not working....
Dear XDA Developers #.....,
Tried with new SD Card and also clean up the contacts of the SD reader, still not be able to work????
Another thing I notice my MDA, when I boots in Bootloader Mode, after the GSM OK, the 'Phone Hangs Up' button always lighten up RED, is this normal. Is you XDA the same when in bootloader mode. The battery gets drain off easily, is it because the WinCE is not there as well????
By the ways, thank for all your reply and times. You have been a great help for me and I have learn quite a lots from these wonderful web site and forums. Keep up the good work......
I might not be able to find someone to repair the device but hopefully to look up for a secondhand O2 PCB Board to swap to...

Flashing bootloader with jtag?
Dear XDA Developers #....,
Do you think flashing the bootloader using jtag might solve my MDA problem ?
in your //xda-developers/jtag page you mention a patch do be download here.... I don't see the link to download the patches.
Could you please verify.....
Thanks

Restore the radio rom via sd card dumped from a 6515

Hi everyone,
I have an hw6515 that can not have Rom update via USB cable and Active Sync (error 606 timeout between UBS and bootloader). However, I got roms images like Bigrom or Ipaq disks for SD card that works fine, but having no Radio rom working. I have only PDA functions not Cell phone.
I see the solution from xda-developers for Blueangel xda, but it is not for my model of ipaq. Then I need to know if there is any Rom image for hw 6515 with Radio Rom working that I could get or way to upgrade Rom using USB.
Hence I would be eternally grateful if someone have a radio rom image dumped from a 6515 or is willing to help me out by extracting it from their 6515.
If successful, I will announce my findings and host the radio rom.
Thanks

Radio Stack problems hw651x why cant we get some help with this model Ipaq?
I have the same issue with a Ipaq HW6515a which thinks it's a HW6510a now.
I have been reading the forums for about a month now, and have tried almost everything to fix the Radio Stack misssing on this "HTC Beetles" device.
my best guess is that either a CID lock is preventing it, or seems to be missing the CID all together. When I do a Info 2 .. nothing is returned.
After exentisive logging and analyzing it seems that when I run a offical rom update for my device.. it enters after it enters into the radio flash by external bootloader it does a "rtask 10 1" command, then a "rinfo" command.
the whole proccess seems to stop/lockup and fail at that porint.
I have searched the whole web, many long hours looking for the p10504_BT_HP_PATCH_BETA.EXE file.. not sure what the offical name of the beetle gsm radio fix is called.
I cant seem to locate it, but would love a copy or even a log of the successfull output from running it.
the only other thing I can think of is manualy uploading the RadioOS and RadioFS to the device. which isnt hard to do, but what I lack is the adress location to place them.
Also not sure if I need to erase some areas first of if I can just lnb them up with the correct syntax.
What I have writen here is not all inclusive. I willing to be more detailed about what I have tried and failed and what seems to work, or even what I know I'm missing if anyone wants to know.
In general the HP IPAQ HW561(0,5) users need help fixing a botched radio rom upgrade that an offical HP rom release caused.
Thanks!

Reply
makebillions said:
I have the same issue with a Ipaq HW6515a which thinks it's a HW6510a now.
I have been reading the forums for about a month now, and have tried almost everything to fix the Radio Stack misssing on this "HTC Beetles" device.
my best guess is that either a CID lock is preventing it, or seems to be missing the CID all together. When I do a Info 2 .. nothing is returned.
After exentisive logging and analyzing it seems that when I run a offical rom update for my device.. it enters after it enters into the radio flash by external bootloader it does a "rtask 10 1" command, then a "rinfo" command.
the whole proccess seems to stop/lockup and fail at that porint.
I have searched the whole web, many long hours looking for the p10504_BT_HP_PATCH_BETA.EXE file.. not sure what the offical name of the beetle gsm radio fix is called.
I cant seem to locate it, but would love a copy or even a log of the successfull output from running it.
the only other thing I can think of is manualy uploading the RadioOS and RadioFS to the device. which isnt hard to do, but what I lack is the adress location to place them.
Also not sure if I need to erase some areas first of if I can just lnb them up with the correct syntax.
What I have writen here is not all inclusive. I willing to be more detailed about what I have tried and failed and what seems to work, or even what I know I'm missing if anyone wants to know.
In general the HP IPAQ HW561(0,5) users need help fixing a botched radio rom upgrade that an offical HP rom release caused.
Thanks!
Click to expand...
Click to collapse
Nice that you have much more experience than me. Just few questions:
1 - How can we update manually the Radio Rom and Radio file system?
2 - Do you know the syntax and program to do that?
3 - Is in Windos, DOS or Linux plataform?
4 - Have you tried to execute the process of decrypt the Radio Rom files and tried to map the memory?
I think I´ve ready some thing about this patch in mobility today (http://mobilitytoday.com/forum/showthread.php?t=12702). I´m about to start to analize (hexeditor) my entire rom trying to find what are the address that we should use in this case, of updating manually.

can we update manually the Radio Rom and Radio file system
Nice that you have much more experience than me. Just few questions:
1 - How can we update manually the Radio Rom and Radio file system?
** best I can tell if normaly with the offical Rom upgrade utility, just remove the CeOS and Extrom lines from the .ini file... However that is not working for me. If we knew where the radioOS and RadioFS files where to be placed in rom, we could use mtty to manualy erase the rom address areas and then upload the radio stack to that location and then finalize it by writing it to rom, probably would need to hard boot afterwards.
2 - Do you know the syntax and program to do that?
this is very rough and off the top of my head, dont attempt this.. just an basic example (taken from another thread, which I tried and didnt work for me)
open mtty
USB> password 0000000000000000
USB> set 1e 1
USB> password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> erase a0040000 c80000
HTCST ÚÈÒHTCEUSB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> erase a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> erase a1940000 640000
HTCST ÚÈÒHTCEUSB> set 1e 0
USB>
USB>lnb c:\ipaq651x\RadioOS.nb0
Dont have an example of the output at moment.. but you need to edit the file and remove part of the begining before you are able to upload it with the lnb command. ( used a program do that for me, HX4700_BootLoader) I just used it to exit the files, it does auto try and upload them, but I dont think it places it in the correct place in rom.
USB> password 0000000000000000
USB> set 1e 1
USB> password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> wdata a0040000 c80000
HTCST ÚÈÒHTCEUSB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> wdata a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB> wdata a1940000 640000
HTCST ÚÈÒHTCEUSB> set 1e 0
USB>
Then would have to repeat for the RadioFS...
I know the address above are not correct, and my method is a bit of a guess from what I've seen from how quite a few of the other phones radio upgrade.
I have not seen how to Radio Stack Flash via SD... best I can tell we need a specail SD chip from HTC that has "special" encoding to flash the GSM Radio Rom to the phone.
3 - Is in Windos, DOS or Linux plataform?
windows for most of what I've attempted.. Well alot in the CMD prompt in windows.
Also Active sync 3.8 seems to be alot better with the 6515 then the newer version.
I know you need to have a full battery and be pluggedinto the power, also need a direct connection into the usb.. NO USB HUB in the middle..
I seen a few people who pulled the battery out for a bit.. then placed it back in.. when it got to the aline screen, they placed it into bootloader mode.. (Power-joystickDown-&-Reset) at same time.. just press the reset while holding the other too.. till the logo is in the middle and Serial is on top and .21 on bottem.. .. place it in the charger and run an offical rom upgrade.
Didnt work for me (tried like 150 times) but seems like it should.
4 - Have you tried to execute the process of decrypt the Radio Rom files and tried to map the memory?
you can use mtty to get a memory map.. didnt seem as usefull as it sounds.
I think I´ve ready some thing about this patch in mobility today (http://mobilitytoday.com/forum/showthread.php?t=12702). I´m about to start to analize (hexeditor) my entire rom trying to find what are the address that we should use in this case, of updating manually.
let me know if you figure anything out. I know there are people here who probably have a copy of the HTC Beetles GSM BT HP Radio Patch Beta that was circulating earlier this year, I would love a copy. I wish someone would just write us a patch, cause there are lots of 651x(5,0{a-?}) phone that the cellular part is missing.
Meanwhile I need to go rebuild my laptop.. I downloaded an stupid evil (HTC Atom Unlocker.exe) from the xda ftp site and it trashed the other computer I was working on. didnt get my data, just I'm at game over on that computer.. need to format and start reloading my o/s. almost want to donate my ipaq 6500 to the person who wrote the program that messed up my windows install.. then I know they would be busy for quite a while trying to get the gsm working, and have less time to try and creatively distroy stuff that is not broken.
Hope I helped sorry took a day or so..
Mb

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy

extract everything from the exe and do an upgrade without the radio.nbf

did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry

poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy

Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.

Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1

pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy

1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!

http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4

pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy

Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not

Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help

posted reply to incorrect post - cannot delete post - ignore. Please see next post.

pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy

To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM

leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy

leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.

my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)

pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:

leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it

Radio ROM upgrade FAILED (NO GSM)

i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.

farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.

d_ranade said:
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
Click to expand...
Click to collapse
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani

farehmani said:
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
Click to expand...
Click to collapse
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
I too find that upgrade in Bootloader is more reliable.

To let you into a little secret.. I ALWAYS flash now in Bootloader mode.. I have only had a couple of "bad flashes" but all of them were direct from a running OS...

I have sent you a pm, that should solve your issue. Please check your pm's...
Take care,
-Jwrightmcps
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
yes... i have never tried to flash anything while being in the os. always switch my device to the bootloader first. I have BootLoader 1.01
Please help!!

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
How to put the PPC in Bootloader (Qtek900)?

myname70 said:
How to put the PPC in Bootloader (Qtek900)?
Click to expand...
Click to collapse
Read the wiki - the answers are in there.

apd said:
Read the wiki - the answers are in there.
Click to expand...
Click to collapse
the problem is still there....
i have tried circumvent bootloader password too... and getting error like Win32 Error, Cannot read from the specified device when HEX of password is placed on the memory field of WinDbg.

Tried Another solution for NO GSM but no luck !!
okay here goes; your quoted link had point#5 for no GSM when booting so i followed it as given below.
Pls. see the comments in (( )) for how i conduct these steps and what value is returned.
[[[[--->
Problem 5: Device shows NO GSM when booting (( I'm having this problem ))
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani

farehmani said:
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
Click to expand...
Click to collapse
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.

SpyderTracks said:
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
Click to expand...
Click to collapse
glad to know about my being almost there... still i wonder whats keeping me away from retaining my device...
i have already got BootLoader 1.01...
what other method should i apply to get it working again?????

I have the same problem, but not in Universal, but apache, jwright help me.

i have the same problem can smeone help

Try this
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...

i am having the same problem with exec it shows me no gsm and when i go to the device information it does not shows the radio ver and my phone imei is 0 can someoe please tell me how do i solve the problem i had read this tread but not understand it can someone please explane me how do i solve the problem

shedragon said:
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
Click to expand...
Click to collapse
thanx for your suggestion!
i had tried this already... but the problem is beyon this...
i discussed with pof and he said that somehow i screwed up with the qualcomm chip where the radio bootload resides. so it needs replacement.
anyways... thanx budd... i appreciate your support too...
regards...

my hermes having this problem also ((

[ITA] Artemis Bigix 2.0

Another Rom for Artemis italian user.
This is a new way of install ROM and can be installed ONLY if you have a Micro SD with almost 30 Mb free space.
In Rar archivie there is the nbh file (the Rom) and a file called "Setup".
1. Copy file "Setup" in your SD
2. Flash the rom (remember you must have SPL unlocked).
Don't delete Setup from SD: it's impostant if you make Hard Reset.
Core wm: CE 5.2.1620 (Build 18124.0.4.2) from original HTC WM6 Professional Ita
SplashScreen
SHDC e GPS Photo ready
.........and more.
Italian user can read more on this forums: A1Ktyle - SoloArte
LINK DOWNLOAD RAPIDSHARE

Thanks mate, testing your great work, bye

P3300
My HTC3300 was dead, only can load into Three-color Mode with USB avaliable. I tried all kind of RUUs, including the Original ROMs(English, French, Deustch....)and the newest version , all report ERROR[300]invalid update tool. then the screen of phone stayed in 0% and RUU tool exit only...
IPL 1.27.0001
SPL 1.11.0000 (used the USPL to unlock CID before)
Before Bricked, I successfully updated many versions of ROM, and the last operation is WM6.1.
I'have try this with MTTY:
Cmd> set 32
Cmd> password BsaD5SeoA
Cmd> ruurun 0
Cmd> ResetDevice
But Doesn't work!
because of you!
My phone was perfect before and I have installed your BigiX.
What I have to do? Can U help me?
I can donete some money... pls... help me....

My dear friend,this is an old rom.
But this is not the reason of your problem.
I don't know if MTTY works on this device, but if your screen show 3 colors you are in bootloader mode (and your SPL is 1.11.0000 as you tell, so it is good for flash any rom).
So (in teory) you can connect PPC to PC via USB and run RUU for flashing the rom you want.
In alternative you can flash original rom.
For this operation i suggest Win XP+ AS 4.5 and try to change usb cable (a new one) and usb port (another on your PC)
I hope you can resolve.
No need donate money

Thx, but are 3 days that I'm looking for solution... Lot of people have the same problem. When run RUU flashing after 3 colors bar, the phone start to flashing but is stopping at 0% and the software report ERROR[300]invalid update tool.
I can connect only with MTTY but I'm looking fore some command that can force to send RUU at the fone. For example "send" in telnet. But nobody know how to do this...
If someone have an idea, lot of people will be very very very happy!
And hope gratful

You can try with rom flash from SD card...
Are you italian??
You can found all the info in this website -> Clic here!!!

Yes, I'm Italian.
I'll post this question to that site.
But I think that is possible to force installation of RUU with MTTY.
My problem is that when I have used start_uspl.exe at blank screen was blocked and I have removed battery.
After this my phone is blocked with 3 colors bar and when I try to update, it start but only at 0%
I need to know all MTTY commands

I don't know if MTTY work with P3300, try with the flash from the SD card directly from the device...
This is the link of the discussion...... Click here!!!
Try don't cost anything....

obviously I have try a lot of times... But doesn't work!
I have try to rename in ARTEIMG.nbh and in a lot of different name but when I powe the phone it say Checking SD contents but nothing happen....
I would like to find a command to force reading of SD and writing to the Phone... but I think is not easy...
Thanks whatever....

Do you try with another SD card?
This procedure is the same that the HTC Service use for repair the HTC device...
Try with another SD card... I have a Kingston 2Gbyte and it work very fine!
I hope your Artemis revive very soon!

I have only 2 SanDisk SD cards. One of 128Mb and one of 2GB.
I have tryed with both. With Fat16 and Fat32 but nothing happen...

Sorry for your problems Pinco, I don't have a solution for that but i can strongly recommend another ROM from the great BigX, the one you can see in my signature. OS core seems to be more recent and ROM's almost perfect If you don't have any specific need to use the 2.0, go for Blue-X!

help error 300
what happend any there have solution for this prob