Upgrade an nb0 file with MTTY: problems - JASJAR, XDA Exec, MDA Pro Software Upgrading

Hello everyone, i hope someone knows what the hell my JasJar bootloader have, since i'm trying to flash my device without success.
I've searched everywhere in the forum but found just a message with no reply.
First of all, i've unlocked my jasjar, it's now a superCID device. Or well, i guess so, since i can exec lnb commands.
Here you are the "log" from mtty:
-------------------------------------------------------
USB>task 32
Level = 0
USB>info 2
HTCS00000000 î¢-HTCE
USB>lnb c:\image.nb0
:F=c:\image.nb0
:A=70100000
:O=00000000
:L=FFFFFFFF
start NB image download
Fail to synchronize with the host (1)
USB>
-------------------------------------------------------
Using the "l" command jasjar hangs and MTTY claims a timeout in \\\wcehUSB1 or something after 5 minutes.
Any idea? I've tried with USB2 and USB1.2, tried differend PC models and differend baud but nothing change.
The "info 2" returns a strange SuperCID message. 2 bad.
Any advice is appreciated!
----------Refresh------------------------
I've also tried to upgrade bootloader to v1.1 but still have same issues...

Related

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

Help with mtty / BL, installing OS

Hey y'all,
Thanks for taking out the time to help me
So, thanks to a friend, I got a beta release of WM flashed on my Hermes a few months ago. I didn't realize that it was a time-limited beta, and I can't use my device anymore.
Current Status --
1. ActiveSync can't connect to the device, so can't use RUU directly.
2. Similarly, I can't use the CID unlock utility, because it requires an AS connection
3. I can access the BL and connect to it from mtty. I see the USB> prompt.
4. Dump of the BL tri-color screen --
HERM200
IPL-1.00
SPL-1.10
5. Dump of "task 32" command in mtty
Level = FF (i.e. CID locked)
Hence, I can't flash BL 1.01 MPG and install an OS. (nor can I install CID unlocker, see #2 above)
6. Dump of "info 7" command in mtty
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a S024
Device Name: H, Bootloader Version : 1.10
.....
Question --
I want to get a working OS on the device. (With that, AS should connect and I will be able to CID unlock the device.) Any ideas?

Another bricked Universal

Seems to have been a run on these!
I have an SPV M5000 that was happily-ish running WM6 (as in my sig), and decided to pass it on to someone and put it back to Orange WM5 firmware.
Well, something went wrong, and now it's stuck with no Radio ROM; I've done the MTTY/Task 28 stuff, I've tried every ROM I can lay my hands on, and I'm having a couple of basic issues:
If I use the generic RUU update, it doesn't want to write the ROM. It just sits there at 0% with the device presumably waiting to get something. Eventually it times out with error 114. Then goes into recovery, and crashes.
If I try any others, including the Orange ROM, it complains that it has an invalid country code. Since this WAS a UK M5000, I used Jwright's M5000 ROM, and I have no idea why this would be changed or broken.
Obviously the bootloader appears to be working, but I don't seem to be able to get a Radio ROM onto it. I'm using an iMac booted into Windows XP since my Vista machine is, well, running Vista.
I really don't want to throw this unit away (and trust me, if I can't make it work by the time I give up it WILL be hurled into the nearest solid object then beaten to a pulp with my iPhone).
Well, I've tried everything on the forum; it's refusing to accept a Radio ROM, even though I've flashed the other parts with success. The only thing I haven't tried is SD-card upload since no-one has actually said "how" this works - how to prepare the SD card for use, for example, what the file should be - so I assume nobody knows this.
I've even tried the MTTY "erase" commands as suggested by Pof, and pretty much the only thing left is trying to update with the Linux tool that won't really help me much as I don't have a Linux setup.
I must admit that with the level of expertise on these forums, I can't find a solution to this, but with all of that - and no doubt if anyone was awake to read this I'd have been told to search (which is, of course, what I've been doing for the past 5 hours, along with flashing, rebooting, trying different cables, etc) - and still no working machine, I can only assume my M5000 is scrap due to some weird bug. Not worth spending money on to repair.
So, how shall I destroy it? Run over it with the car? Switch it on (obviously everything APART from GSM is working fine, with the lovely extended battery) and then set fire too it and see how long it'll run for? Freeze it? Smack it with a large hammer? Drive to Dover and see if I can get a strong enough catapult to send it to France, where it will HAVE to unlock itself by law?
(Edit: Tried it with the FlipStart; clean install of ActiveSync 4.5 - still nothing).
What's that stuff about "device ID not compatible"?
01:56:49:905 [msg] : Version : [2.11].
01:56:49:905 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
01:56:49:968 [msg] : MSystemFile Not Exist !
01:56:49:968 [msg] : CEFile Not Exist !
01:56:49:999 [msg] : Current in CE Mode.
01:56:54:280 [msg] : Device BL VER : [] [].
01:56:54:280 [err] : Device CID Error.
01:56:54:280 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
01:56:59:046 [msg] : Check Ac in CE mode. AC : [1]
01:56:59:046 [msg] : IsBL. BL : [0]
01:57:03:280 [msg] : Enter BL OK.
01:57:07:296 [msg] : Disconnect ActiveSync .... [2]
01:57:07:296 [msg] : Start Get Connect Port.
01:57:07:468 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
01:57:29:187 [msg] : Get Device Backup ID.
01:57:29:187 [msg] : Device BL VER : [1.01 ] [].
01:57:29:187 [msg] : Device ID Is Incompatible.
01:57:31:187 [msg] : =============================================
01:57:31:187 [msg] : START UpdateRadio !
01:57:40:077 [msg] : Check Radio Level 0 [704].
01:57:41:655 [msg] : RUpgrade 0 : 0 Start.
02:02:22:952 [err] : RWipe Data Error.
02:02:23:421 [err] : BL UpdateRadio Error.
02:02:23:421 [msg] : START UnInitialization !
02:02:23:437 [msg] : END UnInitialization !
02:02:28:812 [msg] : START UnInitialization !
02:02:28:812 [msg] : END UnInitialization !
Click to expand...
Click to collapse
Was the device unlocked before flashing to wm6? You could also try flashing on a Windows XP machine..hope this works for you.
Or try this..Got it from Laurentius
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 ))
<---]]]]
clemsyn said:
Was the device unlocked before flashing to wm6? You could also try flashing on a Windows XP machine..hope this works for you.
Click to expand...
Click to collapse
Um...
I'm using an iMac booted into Windows XP
The FlipStart is also running Windows XP.
And it was SIM-unlocked by Orange; it wasn't SuperCID, and I flashed the "Orange M5000" version of Jwright's Crossbow ROM with no issues (apart from the Crossbow bugs).
clemsyn said:
Or try this..Got it from Laurentius
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
<snip>
Your phone should be alive again (( Its Not ))
<---]]]]
Click to expand...
Click to collapse
Tried that, one of the first ones I found. Now IIRC the bits in brackets are his results as he tried it. The last line says it didn't work. Which is precisely what happened for me, too!
At present the ROM update won't progress at all. Before it would reach 99% then fail. I'm wondering if the battery, despite showing 100%, is actually not charging correctly and it needs more power to erase the Flash.
Well, let it charge all night in case it was a power issue (it has a high-capacity battery), tried the Radio ROM, tried the 'task 28' path, tried Universal_SIM_Unlock with MaUpgradeIt - wiped the ROM, no problem reflashing with CE/ExtROM, but no Radio. Just cannot install it period.
Task 32 gives me FF - CID is corrupted, basically. Can't flash Radio 0.00.00, can't flash any radio at all.
Is there any way around this, or is it (as it seems from extensive forum searches including Buzzdev) scrap now? Is there a way to flash an ID to it, and if so, is there any way that the IMEI is damaged, or if so restorable, or will the phone be useless even if I can get a ROM onto it?
I don't get it, as I did nothing stupid with this; I've flashed loads of devices, I even flashed (and risked bricking in a BIG way) a brand new iPhone without headaches. Seems to be a lot of Universals suffering this lately - what is causing it?
Have u tried task 28 55aa
clemsyn said:
Have u tried task 28 55aa
Click to expand...
Click to collapse
Again, from the first post in the thread:
"Well, something went wrong, and now it's stuck with no Radio ROM; I've done the MTTY/Task 28 stuff, I've tried every ROM I can lay my hands on, and I'm having a couple of basic issues:"
I appreciate the attempts to help, but what I am looking for is some insight into what has gone wrong, not blind attempts to try any solution - I've tried it all already in the hope something would work. I think that the issue is very low-level, and I don't know how it becomes corrupted - but I have a suspicion that many Unis have been bricked in the same way and the reason no-one has posted a definitive solution is that there isn't one.
you did not mention if you were flashing with the SD card inserted into the unit (or have you but I failed to read it).
there is one flashing problem here somewhere and the issue was solved when the SD card was removed from the Uni before flashing.
Good question, and no - no SD card, no SIM card; I think I remembered this from the original Uni_Unlocker stuff which I'd been going to try before finding out Orange would unlock it for me anyway.
In fact, I'd like to try flashing FROM SIM card if anyone could provide a dump, but no-one seems to have been able to in the threads I have read - since the information about how the SD-Flash works is somewhat scarce, the service manual says "you can", but not what format the data should be in, or how the process works. Merely, how it can be initiated.
And I also suspect that with corrupted CID, I couldn't access the flash routines anyway, since all the radio flash tools appear to depend on this Sec level being "open". Some sort of direct hardware flash - maybe via JTAG - may be the only way around it, though I noticed the Hermes solution which runs under Linux would appear to work by "forcing" the data somehow.
I have the same problem. And confirm, can not upgrade...
... by SDCard, because I get and error :
"Update not allowed!"
The situation is:
- All ROms WinCE updated run OK! and function correctly: Wifi, Bluetooth...
- All Extended updated ROMS run OK!
- But any Radio Rom cannot ben updated, include the special Rom of Buzz.
I have the same error 114. Device Display "NO GSM", and not have IMEI, not have Protocol.... The phone is OUT of Service.
The problem is the CID is scratched or the Radio bootloader is broken. After 2 years there is still no solution For the Universal devices, But for devices Hermes If there is solution:
http://forum.xda-developers.com/showthread.php?t=286755
please guys, pof, buzzz, HEEELP for The Universal's brickeds Devices
¡¡pleasee....!!
p.d.: (sorry for my bad english)

someone can help me with mtty???

hi all,
I am trying to make the radio work again using this procedure:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
but I got a problem and I'd like if someone can help me.
The problem is that I start mtty, I connect the phone in bootloader, I put USB and the I hit twice enter, but the prompt is always CMD>, doesn't change in USB>; I tried many times hitting enter twice, but nothing changes.
How can I do it?
thankyou
Mick
Don't work that's not a problem its just the version of mtty you are using, it should still work.
i am going crazy...I am tring the guide step by step, but when I try tu update radio,it get stuck.
I am with NO GSM and NO IMEI in this moment.
please
help me
(maybe on msn messenger or skype this way I can tell my problems directly)
in Mtty try typing:
task 32
you should get level = 0 to say your device is SuperCID if not you could try the SDcard Method http://forum.xda-developers.com/showthread.php?t=293651&highlight=task+32
thank you markafreeman,
I followed your instruction and I vas able to get level = 0,
but the problem is still that I have Cmd> prompt instead USB.
(can it be a driver problems??)
anyway, I wrote as the guide says:
Cmd> password BsaD5SeoA
Cmd> set 1e 1
Cmd> erase a0040000 c80000
Cmd> erase a0cc0000 c80000
Cmd> erase a1940000 640000
Cmd> set 1e 0
I closed the mtty, restart the PDA on the bootloader again (HERM100, IPL-1.04 Spl-2.10.Olipro) and I sent the official old ROM RUU_Hermes_QTEK_ITA_2.11.258.1_102_6275_1.38.00.10_108_Ship, it starts but get stuck at 13% and then I got on the pc error 262, upgrading error!
I tried twice and it stops always at 13%
UP!!please...somebody give me hope !
I'd probably try the SDcard method I posted earlier at that point.
On some versions of MTTY it shows CMD on some it shows USB, nothing to worry about.
thank you markafreeman:
I tried to do that, but when it start to write radio,it just stops.
thank you drummer10630:
I didn't see any changes in the phones,also if I try with Cmd> prompt
when I go to install RADIO,it stops
Hmmm the other thing I've seen people suggesting with connection problems is on the hermes go to settings and usb to pc and untick the advanceed netowrk option.
mickscores said:
hi all,
I am trying to make the radio work again using this procedure:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
but I got a problem and I'd like if someone can help me.
The problem is that I start mtty, I connect the phone in bootloader, I put USB and the I hit twice enter, but the prompt is always CMD>, doesn't change in USB>; I tried many times hitting enter twice, but nothing changes.
How can I do it?
thankyou
Mick
Click to expand...
Click to collapse
task 28 55aa
then flash again!
Thank you yyyuanye,
I tried your command, it told me that something was formatted, then I tried to re-flash form SD card, but it stops when it's flashing the RADIO.
if you got any idea form me...please...I will be waiting for it.
the Mtty communicate with my Herm because it replies with the coomands Cmd> info, so now it's not a mtty problem anymore.
I don't know, but maybe, in mtty there is a command that erase everything on the radio and make it ready for a new installation.

Categories

Resources