Related
I have done the upgrade and everything went fine. After the upgrade it ran to extended rom configs and they went fine. My phone is no longer showing that it is connecting to 3G. All I have is the E logo on top. I am in my office and it is a 3g area, I was connecting 3G before the upgrade.
I have reinstalled the PTT .cab, and Hard Reset after it etc... Still the same.
I was going to upgrade my radio from 1.33 to 1.34 this morning, but when I ran that installer it told me that it was the wrong country??? Should I keep my radio 1.33? anyone know whats going on with this?
Thanks.
Gromet said:
I have done the upgrade and everything went fine. After the upgrade it ran to extended rom configs and they went fine. My phone is no longer showing that it is connecting to 3G. All I have is the E logo on top. I am in my office and it is a 3g area, I was connecting 3G before the upgrade.
I have reinstalled the PTT .cab, and Hard Reset after it etc... Still the same.
I was going to upgrade my radio from 1.33 to 1.34 this morning, but when I ran that installer it told me that it was the wrong country??? Should I keep my radio 1.33? anyone know whats going on with this?
Thanks.
Click to expand...
Click to collapse
Maybe try putting SPL 1.09 on it then running the RUU Shipped Radio ROM 1.27 from Germany.
OK< I tried what you said. My phone is SPL 1.09. So I ran the 1.27 RUU. I got the same kind of error.
ERROR 120: COUNTRY ID ERROR
The ROM image that you are trying to use is not designed to work with your device. Please check the vendor website and download the correct ROM update.
??????????????????????????????????????????????????????????????????????
Before loading another radio on it. just make sure it's the icon that is just not showing the correct connection, as some radios do... Check mspeed from your phone's browser for your actual connection speed... http://www.dslreports.com/mspeed
Gromet said:
OK< I tried what you said. My phone is SPL 1.09. So I ran the 1.27 RUU. I got the same kind of error.
ERROR 120: COUNTRY ID ERROR
The ROM image that you are trying to use is not designed to work with your device. Please check the vendor website and download the correct ROM update.
??????????????????????????????????????????????????????????????????????
Click to expand...
Click to collapse
Sounds like you are not SUPERCID. Run Pof v3 Unlocker, verify supercid, then try again.
Bimboy said:
Before loading another radio on it. just make sure it's the icon that is just not showing the correct connection, as some radios do... Check mspeed from your phone's browser for your actual connection speed... http://www.dslreports.com/mspeed
Click to expand...
Click to collapse
Good point. MT_PC_Hermes_PTT_REG_070129.CAB fixes the icon settings in the new Cing ROM.
Just ran a speed test... 207kbit/sec...
You might also just go to the \extended_rom via totalcommander or other filemanager and execute autorun.exe or at least the cab that corrects the 3g/u/e icons MT_PC_Hermes_PTT_REG_070129.CAB
A lot of people have found that for some reason after upgrading via mfg package to the 2.06 cingular rom, that the entire entended_rom did not run; even if they did not stop it after the upgrade. It looked like it loaded to most people, but they did not have the useless icons like telenav, mobiTV, etc..
OK, so something strange happened... I went to run POF's unlocker again. I ran it, but all of a sudden a ROM image begins to load? It looked like it was reloading the cingular image I loaded yesterday. Just than I get called into a meeting, when I get back, my phone is sitting there, looking the same as I left it before doing anything EXCEPT I have a G Icon now. Great, so I just checked the settings...
ROM Version 2.06.502.3
RADIO Version 1.16.00.00 ?????????????????????
Should I keep this radio or uupgrade it to a newer one, and if you think a newoer one than which should I try?
Gromet
Gromet said:
OK, so something strange happened... I went to run POF's unlocker again. I ran it, but all of a sudden a ROM image begins to load? It looked like it was reloading the cingular image I loaded yesterday. Just than I get called into a meeting, when I get back, my phone is sitting there, looking the same as I left it before doing anything EXCEPT I have a G Icon now. Great, so I just checked the settings...
ROM Version 2.06.502.3
RADIO Version 1.16.00.00 ?????????????????????
Should I keep this radio or uupgrade it to a newer one, and if you think a newoer one than which should I try?
Gromet
Click to expand...
Click to collapse
I think the consensus is that 1.27 is best until/if GPS ever works.
WAIT!, Lat time I checked your sig, did you not have Radio 1.34? Now I see you are on 1.27. Did you downgrade for a reason? I started the 1.34 upgrade just before you posted. What are the differences between 1.27 and 1.34?
Gromet
More strangeness...
So I started the 1.34 radio upgrade, click update, phone reloads into blotloader, goes to upgrading radio stack please wait... PC shows Stage 1: Upgrading Radio, BUT it just sits there at 0% than errors out.
SO
I ran the 1.27 Upgrade, SAME THING>???????????????????
Whats goin on?
BTW, I'm on SPL 1.09 and I ran Pof's Unlocker again successfully....
Gromet said:
More strangeness...
So I started the 1.34 radio upgrade, click update, phone reloads into blotloader, goes to upgrading radio stack please wait... PC shows Stage 1: Upgrading Radio, BUT it just sits there at 0% than errors out.
SO
I ran the 1.27 Upgrade, SAME THING>???????????????????
Whats goin on?
BTW, I'm on SPL 1.09 and I ran Pof's Unlocker again successfully....
Click to expand...
Click to collapse
What is you Radio BL 107 or 108?
I had access to two separate 8525's. One had 1.34 and the other had 1.27 (BL0107). The 8525 I keep and use daily is on 1.27 with BL 0107. I am waiting for further NBH flashing directions before changing both devices to BL 0108.
When it goes into Botloader mode, it sais SPL 1.09, Where else do I find the bootloader version?
Gromet said:
When it goes into Botloader mode, it sais SPL 1.09, Where else do I find the bootloader version?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=289173&highlight=hermes+rversion
mtty
To access the radio bootloader for that, but the command to do this (rtask a) has been removed in SPL-1.09.
If you downgrade the SPL to 1.04, you can see it using radio bootloader command "rversion":
Code:
USB>rtask a
Enter Radio Bootloader
rversion
Gromet said:
OK, so something strange happened... I went to run POF's unlocker again. I ran it, but all of a sudden a ROM image begins to load? It looked like it was reloading the cingular image I loaded yesterday. Just than I get called into a meeting, when I get back, my phone is sitting there, looking the same as I left it before doing anything EXCEPT I have a G Icon now. Great, so I just checked the settings...
ROM Version 2.06.502.3
RADIO Version 1.16.00.00 ?????????????????????
Gromet
Click to expand...
Click to collapse
Gromet, this is normal behavour. Pofs unlocker flashes a hacked radio rom (1.16.00.00). Once device restarts, you need to copy the unlocker exe file (included in pof's unlocker zip) to your device, and then execute it on the device. I guess the exe that you run on the device interacts with the hacked radio to unlock the device somehow.
Once thats done, you'll get a 'success' message. Now you can download the shipped rom 1.27.00.00. Since your device is now superCID you can just exec the exe in the shipped rom directly to upgrade the radio from 1.16 to 1.27
Just make sure that you kill activesync before playing about with any rom flashing - it gets in the way.
Nigel
So yeah....
I did everything for PoF's Unlocker, and I GOT the SUCCESS message... but now I cant get any version of a radio upgrade to run. If activesync is on, It starts the upgrade and never gets past 0%, if activesync is off, i error out even before it ever starts the upgrade.
Gromet
Gromet said:
So yeah....
I did everything for PoF's Unlocker, and I GOT the SUCCESS message... but now I cant get any version of a radio upgrade to run. If activesync is on, It starts the upgrade and never gets past 0%, if activesync is off, i error out even before it ever starts the upgrade.
Gromet
Click to expand...
Click to collapse
I don't have much to add other than, 'me too'--but eventually the upgrade worked. I Ran POF's unlocker and chose supercid as well. But couldn't get past that 0% with the 1.27.00.00 radio upgrade.
I'm at:
IPL - 1.00
SPL - 1.04
While typing up this message I decided to try again and type up the error verbosely.
Sure enough the sixth try was the charm.
-g
Gromet said:
WAIT!, Lat time I checked your sig, did you not have Radio 1.34? Now I see you are on 1.27. Did you downgrade for a reason? I started the 1.34 upgrade just before you posted. What are the differences between 1.27 and 1.34?
Gromet
Click to expand...
Click to collapse
I am back to 1.34 and I created the NBH standalone Radio ROM since the new tools are available now.
You can easily go between Radio ROM again YEAH!
Here are Radio ROMs:
1.27 http://uploadingit.com/files/8194/NBH Radio Only 1.27.00.00.zip
1.33 http://uploadingit.com/files/8194/NBH Radio Only 1.33.31.00.zip
1.34 http://uploadingit.com/files/8194/NBH Radio Only 1.34.00.10.zip
wpbear said:
I am back to 1.34 and I created the NBH standalone Radio ROM since the new tools are available now.
You can easily go between Radio ROM again YEAH!
Here are Radio ROMs:
1.27 http://uploadingit.com/files/8194/NBH Radio Only 1.27.00.00.zip
1.33 http://uploadingit.com/files/8194/NBH Radio Only 1.33.31.00.zip
1.34 http://uploadingit.com/files/8194/NBH Radio Only 1.34.00.10.zip
Click to expand...
Click to collapse
So, excuse my ignorance, but are we now saying that we can upgrade the radio roms listed without ending up with the 1.08 bootloader, or alternatively that 1.08 no longer causes a problem?
Rob
I got this phone a few days ago and I'm already on a modding spree.
Today, I upgraded to SPL-1.40.01ipro and also upgraded the radio to 1.38.00.10.
To continue my modding spree, I wanted to update to the new Cingular ROM (2.06.502.3). I downloaded the package and launced it. I went through the usual ROM upgrading steps (checkboxes, etc.). Finally, at the last screen (before the status bar) I clicked ok, and it popped up a message saying "Verifying PDA information, etc." The phone disconnected from ActiveSync (even quit the program), Windows made the disconnecting sound, and then it made the connecting sound, and my phone went into bootloader mode. It then stayed there until a window popped up on my monitor saying "Error [260]: Update Error".
I searched about Error 260 and all I came up with was program conflicts. I rebooted the computer and tried to exit pretty much every program. Do I not have enough space on the phone?
Anyone have any idea how I can fix this? I searched alot. Thanks
Edit: I am using WinXP Pro, so the Vista issue has no concern.
If it is a standard RUU updater provided by Cingular you need to disable USB connections in activesync first.
Using the customRUU updates provided here (all the WM6 builds and HardSPL...and radio) its the opposite, but try unticking "allow usb connections" in connection settings (in activesync on your pc).
I assume it's the standard RUU, as it does not say CustomRUU on the file.
Edit:
I am using this one:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Cingular English CWS__001 2.06.502.3 02/02/07 ?? 1.33.31.00 32.66.7020.10H 15671.3.3.0 3.3 1.09 108
Should I just do the Ext. ROM ones?
Also, wouldn't disabling the USB connection result in a connection error (since it's not "connected")?
By the way, your upgrade guides are excellent! They really helped with the radio and SPL update.
A few minutes ago, I tried the the SIM unlock/CID unlock .v3 and it does the same thing. Error [206].
justsignbythex said:
I assume it's the standard RUU, as it does not say CustomRUU on the file.
Edit:
I am using this one:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Cingular English CWS__001 2.06.502.3 02/02/07 ?? 1.33.31.00 32.66.7020.10H 15671.3.3.0 3.3 1.09 108
Should I just do the Ext. ROM ones?
Also, wouldn't disabling the USB connection result in a connection error (since it's not "connected")?
By the way, your upgrade guides are excellent! They really helped with the radio and SPL update.
Click to expand...
Click to collapse
I think i might have been confused with using the mtty program, never mind.
The reason your RUU will not work is because you have an upgraded SPL (HardSPL) on your device and it is not recognised by the operator RUU.
The procedure to flash the cingular ROM to your device is the same as in my WM5 Downgrade Guide.
(you might not understand this until youve read the guide)
Just package the OS,Extrom and splashscreens as in the guide and flash with the CustomRUU tool, you will be fine. (follow the guide its all in there). Just to add to that when you come to flashing the repackaged ROM (at the end of the guide) select the 'Autodetect' option when the flashing utility asks what SPL you have.
Thanks for the help so far!
I read another thread: http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
that if I update the ROM a certain way, I will not be able to upgrade the radio afterwards. Is this true for your WM5 downgrading guide? (I am upgrading to AKU3.3 by the way)
Just want to make sure before I do it.
justsignbythex said:
Thanks for the help so far!
I read another thread: http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
that if I update the ROM a certain way, I will not be able to upgrade the radio afterwards. Is this true for your WM5 downgrading guide? (I am upgrading to AKU3.3 by the way)
Just want to make sure before I do it.
Click to expand...
Click to collapse
You can change the radio without issue dude. Aslong as you have HardSPLv6 (1.40.olipro) then we will have no problem sorting you out.
The guide is awesome!
But when it comes to this window:
Follow the RUU instructions as usual to flash the WM5 ROM. Select 'Autodetect' when the RUU asks which SPL version you have.
when I select Autodetect it says it cannot query the device and it advises me to pick SSPL. Should I just do that? Activesync is running and connected.
justsignbythex said:
The guide is awesome!
But when it comes to this window:
Follow the RUU instructions as usual to flash the WM5 ROM. Select 'Autodetect' when the RUU asks which SPL version you have.
when I select Autodetect it says it cannot query the device and it advises me to pick SSPL. Should I just do that? Activesync is running and connected.
Click to expand...
Click to collapse
select the third option down, then tick hardspl. sometimes it doesnt detect correctly
Thanks alot! Your help has been indisposable.
It's currently flashing as we speak. Will update you as it's done.
It works great, thanks!
justsignbythex said:
It works great, thanks!
Click to expand...
Click to collapse
No probs dude
Might wanna give the threads on HardSPL, CustomRUU and maybe the (hermes) rom koch???
The info there is great for future releases of ROM (and also for the techniques used in my guide)
I have same problem, error 260. At same time, after final check. I have made my .nbh with this guide (from Original ROM 2.11.255.1 03/07/07 and 2.05.255.1 01/17/07 ).
I have tryed to update with that guide that I mentioned before on two different computers Win XP sp2 and Win 2000. I have ActiveSync 4.2 on PC and the phone is Vodafone v1605 (with only rom that it has) and I have updated bootloader to 1.40.olipro.
Does this RUUWrapper.exe work with this .nbh allso? I want to upgrade everything to newest, or should I? I didn't find userguide for RUUWrapper or when it should be used.
I also tryed to flash ROM with "ModifiedRUUUpdater-V2", it went little bit further, but it hanged in 0% with error 244
Error 260 continuted
hello
I had the same issue, Error: 260. I have a hermes TyTn, WM6. I have tried to follow the steps on the downgrade to WM5 but have some issues. There is a warning to do the HardSPL first because this would prevent the unit from being bricked, but i am doing this because I can't do the Hard SPL. Secondly the Hermes RomKoch by dutty can not be found at the link provided. please help!
Try this method:
First go to this mode:
http://rt002nf0.eresmas.net/TodoPDAs200/bootloader01.jpg
And finally run ruuwrapper. This helps me.
error 260
I am getting the same error 260 message when I try to upgrade as well. I read several threads with different solutions and none of them worked for me. The link in this forum pointing to the downgrade guide does not work. I've tried on 2 different Vista Ultimate machines with no success. The funny thing is, I upgraded one of my 8525s on one of these machines with no problem, but this new 8525 I received today isn't playing nice. Any suggestions would be greatly appreciated.
Thanks
Install Hard SPL V7, then use sd card method to install ROM.
Go to page 116, post 1160 on this thread - http://forum.xda-developers.com/showthread.php?t=296722
for sd card method for Hard SPL.
Just drop the steps using sspl.exe when flashing roms as you would now have Hard SPL installed.
You need a 2Gb or less sd card formatted FAT32 and make no spelling mistakes when renaming .nbh file to hermimg.nbh..
Cheers...
But how do I get the Hard SPL V7 installed. That is the version I was trying to install. I go through the steps and once my phone gets to the bootloader, it disconnects from the WMDC and then the error message. So I need to get past the Hard SPL V7 install first. Any ideas on that?
Thanks ultramag69
ultramag69 said:
Install Hard SPL V7.
Go to page 116, post 1160 on this thread - http://forum.xda-developers.com/showthread.php?t=296722
for sd card method for Hard SPL.
You need a 2Gb or less sd card formatted FAT32 and make no spelling mistakes when renaming .nbh file to hermimg.nbh..
Cheers...
Click to expand...
Click to collapse
As I said before
Thanks ultramag69 it worked. I appreciate your help. Do you also have a good link for the Windows Mobile 6 download?
Thanks again.
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Then I followed this guide
And updated to Hard-SPL v7 fine
Then I got to the Radio update step, I tried the radio it said (1.43)
It got to 7% and failed,
Then I tried 1.48 and 1.50
The same happened.
Why can't I update my Radio? Is there a trick or something you guys use?/
I tried it the SD card way and Its the Same.
Thanks.
Can a pro please explain how and what they used to get their PDA from its original state to having a cooked OS and a working Radio?
Korpse said:
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Then I followed this guide
And updated to Hard-SPL v7 fine
Then I got to the Radio update step, I tried the radio it said (1.43)
It got to 7% and failed,
Then I tried 1.48 and 1.50
The same happened.
Why can't I update my Radio? Is there a trick or something you guys use?/
I tried it the SD card way and Its the Same.
Thanks.
Can a pro please explain how and what they used to get their PDA from its original state to having a cooked OS and a working Radio?
Click to expand...
Click to collapse
That guide works 99% of the time. There is really only a small handful of possibilities:
1) You did not follow the guide exactly
2) The file you got for radio is corrupt (unlikely since you tried multiple files)
3) Your connection is unstable (unlikely since SD card method fails)
Hmm... Try the bricked hermes thread - is a sticky in the Hermes forum. It is long, but you may find something. It seems to me that the 7% hang on radio happens from time to time - but I am not sure if there is a standard fix. Maybe try the google search in my signature - use terms like hermes radio 7% brick or something. I am sure it is fixable. You got HardSPL to load properly, right? So your bootloader screen shows SPL version 2.10 Olipro or something like that?
The interesting thing is that you got it back to oringinal ROM & radio... You are using the latest Custom_RUU to do all the work. Makes me wonder if it is a CID problem, although I don't think you would even get to 7%, you would just get an immediate failure.
You could use MTTY to restore the radio back to factory I beleive..
You might also need to make sure your device is CID unlocked..
Thanks for the help guys
I updated to HardSPL-v7 and that went fine, it read IPL-1.04 and SPL-2.10.Olipro afterwards,
Then I attempted to update the radio and it failed, I followed the guide exactly.
Then I tried the SD way, the same.
Now. I'm doing the SIM and CID unlocker v3a by pof (Did it the SD way) and the IPL update completed with OK, The SPL went OK to, but the radio failed so i did a reset now I going to run that unlocker program and see if it succeeds,
then I will run the Factory ROM and restore it to how it was, then I will update to the Black Satin Cooked ROM, and I'll just have to stick with the old radio until I find a new method that might work.
Whats the go with the downgrading to bootloader 1.04 like it says in the wiki everywhere, what will that do that will help the radio update that the newest bootloader can't?
Korpse said:
Thanks for the help guys
I updated to HardSPL-v7 and that went fine, it read IPL-1.04 and SPL-2.10.Olipro afterwards,
Then I attempted to update the radio and it failed, I followed the guide exactly.
Then I tried the SD way, the same.
Now. I'm doing the SIM and CID unlocker v3a by pof (Did it the SD way) and the IPL update completed with OK, The SPL went OK to, but the radio failed so i did a reset now I going to run that unlocker program and see if it succeeds,
then I will run the Factory ROM and restore it to how it was, then I will update to the Black Satin Cooked ROM, and I'll just have to stick with the old radio until I find a new method that might work.
Whats the go with the downgrading to bootloader 1.04 like it says in the wiki everywhere, what will that do that will help the radio update that the newest bootloader can't?
Click to expand...
Click to collapse
If the CID unlocker runs fine, try the radio again. There is no reason that a new one would not work, if the older one works routinely.
The downgrade stuff is for people who want to return it to it's near-exact shipped condition - usually for warranty or sale purposes.
So, I ran the original factory rom
I did it via the SD card, as it is a lot more useful this way.
Heres the Results:
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS-
Click to expand...
Click to collapse
please mind the ranting....
WTF WHY THE F##K DID IT STOP AT GSM AGAIN FFS!
you can obviosly see why I'm pissed, its acting up like the radio is a BANK VAULT with 8" STEEL. I just can't flash it at all, but for some reason I have ran this ROM a while back and had no problems, so there must be a way
Did you run the CID unlocker successfully?
Have you used MTTY before? You may want to do that.
Had you successfully flashed back to the old ROM before?
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Click to expand...
Click to collapse
It seems like it - so the SAME ROM will not work now either?
I ran the newest dopod wm6 rom which was only the OS, some splash screens and the EXTROM, and to my amazement the GSM worked, the Radio and IMEI reappeared in the device information, but after a soft reset its gone again. it seems the GSM is still there but I can't touch it at all.
When I did the SIM and SuperCID unlocker it gets to the hacked GSM and fails,
but after a reset, I ran the tool and ticked bot options. then it said Success!
How can I check to see if it worked.
My bootloader is 1.40.Olipro (the one the SIM and CID unlocker downgraded me to)
Korpse said:
I ran the newest dopod wm6 rom which was only the OS, some splash screens and the EXTROM, and to my amazement the GSM worked, the Radio and IMEI reappeared in the device information, but after a soft reset its gone again. it seems the GSM is still there but I can't touch it at all.
When I did the SIM and SuperCID unlocker it gets to the hacked GSM and fails,
but after a reset, I ran the tool and ticked bot options. then it said Success!
How can I check to see if it worked.
My bootloader is 1.40.Olipro (the one the SIM and CID unlocker downgraded me to)
Click to expand...
Click to collapse
You can use mtty to see if the supercid process worked. The Hermes Wiki - in particular THIS SECION will be very helpful.
Yep its definitely SuperCID,
still reading through pages looking
I spent HOURS messing with **** on my phone, downgrading bootloaders, trying different ROMs, Stuffing with every command I could find for MTTY and anything else imaginable.
I got the radio to update, but its still stuffed
I added this to the Wiki because it works:
METHOD 2
Also, Ive found that Hard-Reseting the device restores GSM.
1. Remove the battery
2. wait 10 second
3. Re-insert Battery
4. Turn the device on
5. Watch for "NO GSM" on boot
6. if you see it. Return to step 1. (sometimes you have to do it up to 20 times)
If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.
This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.
Click to expand...
Click to collapse
I did what the last post said, had it booted with my radio working, and then I ran the RUU for the GSM 1.50.00.00 radio upgrade. and THIS IS UNBELIEVEABLE, AFTER ALL THAT STUPID STALLING ON 0 and 7%, it UPGRADED!!!!!
I have exactly teh same situation here.... my device is SUPERCID and its stalls on GSM upgrade every time
I already tried like 10 different versions of radio bootloader updates and none of them worked for me !!! It always stalls at 11% or 7%
MMTY output
Cmd>checkimage
IPL CRC checksum = 0x830E7601
SPL CRC checksum = 0x921BC30
CE CRC checksum = 0x26BC961C
ExtROM CRC checksum = 0xE7056FB7
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Can somebody help ? I am sure there is a way to flash the new radio version !!!
There is a defenitite fault in RADIO ROM and I wish I should have never tried to upgrade to 1.50.0 . Last coule of days have been a nightmare for me. I read the entire foruma and stil could not find a solution to my problem.
METHOD 2
Also, Ive found that Hard-Reseting the device restores GSM.
1. Remove the battery
2. wait 10 second
3. Re-insert Battery
4. Turn the device on
5. Watch for "NO GSM" on boot
6. if you see it. Return to step 1. (sometimes you have to do it up to 20 times)
If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.
This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.
Click to expand...
Click to collapse
sure i've done it too many times, atleast after the 7nth time i've stopped counting but still i have no GSM .
any help is much appreciated folks .
WBR
Also whatever ROM i install after it starts for the first time it starts to customize and install oem apps it stops while customizing at the theme part i don't know why but it did .
do a "checkimage" in MTTY, if your radio is corrupt then that method wont work, also about the updates stalling, do task 28 in MTTY, then reboot
MMTY output
Cmd>checkimage
IPL CRC checksum = 0x830E7601
SPL CRC checksum = 0x921BC30
CE CRC checksum = 0x26BC961C
ExtROM CRC checksum = 0xE7056FB7
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
So is the radio corrupt ?
What is task 28 ? WIKI SAYS - Format DOC - What is DOC ? Is it related to RADIO ROM ?
Hi there, I have very minimal experience with this stuff so I will provide as much detail as possible...
I had previously successfully programmed my HTC6800 back in March by unlocking with Olipro 2.4, then I flashed the radio with 3.27 and used dcd 2.3.2 for Bell on it. Now my memory is a little foggy as that was several months ago however I made it through the process fine. This encouraged my to try to update again today. I tried following the steps in the wiki as I could not find the guide I had used previously. I already had Olipro 2.4 so I was good at that step. I then tried running the newest radio update and it would not take. It gave me an error. I reset the phone and tried several times but to no avail. I then tried putting on dcd3.2.0 which went fine. THe phone rebooted and I made a test call and everything was fine. I however wanted the new radio update still so I thought I'd take another crack at it... it still would not update. In the wiki it said about relocking the phone and putting it back to the factory ROM and starting again. So I did this, I downloaded the relocking util and followed the instructions to relock the phone. That went fine... Olipro is gone and is shows the 1.06 like it's supposed too... next it said to put the factory ROM back on... well, I am will Bell and the link for the factory ROM is dead! I can't get it anywhere!!!
So currently my 6800 sits as the 3 colour screen with 1.06 relock on it and does nothing else. It has radio 3.27 on it and dcd 3.2.0.
Is there any way to fix this?????
Run this first to exit the bootloader and get into windows mobile. Then check out which rom you are on (I think you were on dcds rom). Then load radio via sd card method listed in the wiki. Then reload dcd if you are not already on the version that you want.
P.S. I have heard things about that ROM that it caused problems. You may want to read up on that here.
Nope
Well, I downloaded the file and tried running it but to no avail. It just comes up saying that the application failed to start because RAPI.DLL is missing.
Also
I tried running that app on a Vista machine as well and it just says that it can't open the USB port. However, windows found the device and installed a driver for it when plugged in AND it shows USB on the bootloader screen when plugged in.
ok..,. let me see...
try installing olipro 2.40 again, it seemes that your phone is locked (olipro 1.06) so it can't run the dcd custom rom... reset and see if you can enter windows...
then if you enter windows normally, downgrade to olipro 1.20 and install the new radio, then, once again upgrade to olipro 2.40 so it can enter windows...
let me know if it worked for you...
Evo69 said:
well, I am will Bell and the link for the factory ROM is dead! I can't get it anywhere!!!
Click to expand...
Click to collapse
Install another carrier's stock ROM (though to keep things easier avoid the Telus one as it doesn not include a radio ROM) and avoid letting it run any customisations after boot/screen calibration.
You are fine.
Here's the problem
OK. Here's the problem. I obviously misread the instructions on setting the unit back to stock as I just read them again and I realize my mistake. I did not load the stock ROM on first. I used the Re-lock program and re-locked my unit before putting the stock ROM back on. So I sitting at the 3 colour screen with SPL 1.06 and I have radio 3.27 on the unit and dcd's latest ROM on it. I can't get it past the 1.06 bootloader. I have tried a hard reset, I have tried the program above to exit the boot loader and it does not work. Is there any way I can get Olipro 2.4 back on or exit this bootloader???
just connect your phone to the computer (it's ok to be on the tri color screen) and install olipro 2.40 from the computer...
you just need to be sure that when you connect the phone in the tri color screen it says USB...
i'm attaching Olipro 2.40
No Dice
Nope. I had tried that already. I just tried again. When I run Olipro 2.40 the command prompt comes up and then come up with a window saying "Cannot Find Device" (or something VERY close to that). It then asks if you'd like to retry, clicking retry just keeps bringing up the same message. If you click "No" on retrying it will eventually move on to the next step and load up the flash program. It will then attempt to flash the unit (Grey screen with the status bar comes up) but it just sits at 0% and eventually comes up with a 242 communication error.
i had a similar problem yesterday when i tried to upgrade the radio form 3.42.02 to 3.42.30 and taht solved my problem...
so you basically cannot exit the bootloader mode?? even when you hard reset your device??
Can the unlocker be flashed from a memory card? Has anybody ever tried?
Evo69 said:
Nope. I had tried that already. I just tried again. When I run Olipro 2.40 the command prompt comes up and then come up with a window saying "Cannot Find Device" (or something VERY close to that). It then asks if you'd like to retry, clicking retry just keeps bringing up the same message. If you click "No" on retrying it will eventually move on to the next step and load up the flash program. It will then attempt to flash the unit (Grey screen with the status bar comes up) but it just sits at 0% and eventually comes up with a 242 communication error.
Click to expand...
Click to collapse
I have the Bell ROM if you're looking for it.
TS
I didn’t think it was possible to flash back to a stock Bell (non-GPS) rom/radio after flashing to a GPS radio.
Does anyone know if it’s possible to flash the SPL (bootloader) from an SD card?
No2chem over at ppc geeks has a new SPL that loads from the device, but it needs be running.
http://forum.ppcgeeks.com/showthread.php?t=30561
jhamilton said:
I didn’t think it was possible to flash back to a stock Bell (non-GPS) rom/radio after flashing to a GPS radio.
Does anyone know if it’s possible to flash the SPL (bootloader) from an SD card?
No2chem over at ppc geeks has a new SPL that loads from the device, but it needs be running.
http://forum.ppcgeeks.com/showthread.php?t=30561
Click to expand...
Click to collapse
I haven't tried to do it yet, but I did develop a theoretical how to before I first flashed my phone as I wanted to make sure I had a way out. You can find it here:
http://forum.xda-developers.com/showthread.php?p=2017265&highlight=bell#post2017265
YES
Timeshell said:
I have the Bell ROM if you're looking for it.
TS
Click to expand...
Click to collapse
Ya, if you can post attach that file to a posting on here I would appreciate it. If you need an alternative method of send the file to me just PM me and I will figure something out.
Keystone said:
Install another carrier's stock ROM (though to keep things easier avoid the Telus one as it doesn not include a radio ROM) and avoid letting it run any customisations after boot/screen calibration.
You are fine.
Click to expand...
Click to collapse
I tried using a Sprint one... it would not work.
Timeshell said:
I haven't tried to do it yet, but I did develop a theoretical how to before I first flashed my phone as I wanted to make sure I had a way out. You can find it here:
http://forum.xda-developers.com/showthread.php?p=2017265&highlight=bell#post2017265
Click to expand...
Click to collapse
Yeah I've heard some horror stories when it came to downgrading, including a few bricked devices.
http://forum.ppcgeeks.com/showthread.php?t=26082
I would be interested to know if anyone on Bell has managed to successfully downgrade a 6800 to stock.
i thought dcd's new 3.2.0 needed a radio of 3.35 or higher to run and does not flash the radio when u flash his rom. Another problem with the phone not coming out of the bootloader is that you have to disable usb connections in active sync or windows mobile device center for the exit bootloader app to work. Try disabling the usb connection in whichever one applies for you and run the app again. If you can get out of the bootloader try to go back to ollipro 2.40 or use one of no2chems bootloaders as they work from the device and an sd card no need for a pc to flash the bootloader. once bootloader is unlocked again run a full radio/rom update like the sprint stock 3.35 easily found on htc's website under the titan (us version of the site). Don't let the carrier custimizations run ... the file that runs after u calibrate screen and set timezone just pull the battery. Then grab whatever rom / radio you want to or were trying to flash 2 before and name it put it on the root of an sd card (thats under 2gb and formatted to fat32) and rename the ruu_sighned.nbh file to TITAIMG.nbh hold power + camera and hit your soft reset button. The tri color screen will come up and should say loading then promt to hit the power button to flash and show u what u r flashing. cdma (radio). os (radio rom) or splash screen, or whatever you r trying to flash hit power button to start once done it will sit with update complete on the screen pull the battery out for about 30 sec and put it back in reboot and enjoy the custom rom or radio.
kdj67f said:
Can the unlocker be flashed from a memory card? Has anybody ever tried?
Click to expand...
Click to collapse
You can use nueSPL 2.47 to load the locker/relocker but you need to be booted into WM6 to do so. You need to reload another rom that uses the bootloader you have currently loaded and then you can move forward or backward.
Evo69 said:
Ya, if you can post attach that file to a posting on here I would appreciate it. If you need an alternative method of send the file to me just PM me and I will figure something out.
Click to expand...
Click to collapse
Uploaded to Rapidshare
http://rapidshare.com/files/1271390...3.666.1_RS_1.37.30_BM_1.27_0604_SHIP.zip.html
TS
I'm trying to flash my RADIO to 3.42.50 using the ROM Update Utility that came with the latest kitchen.
It starts to upload (8%), then gives me the follow error:
ERROR[328]: INVALID COMMAND
This update utility cannot be used for your PDA Phone. Please check your update utility.
Any ideas what might be causing this?
ROM: DCD 2.1.0
Radio: 3.27.00
See the Radio thread. It details this etc.
ookami007 said:
I'm trying to flash my RADIO to 3.42.50 using the ROM Update Utility that came with the latest kitchen.
It starts to upload (8%), then gives me the follow error:
ERROR[328]: INVALID COMMAND
This update utility cannot be used for your PDA Phone. Please check your update utility.
Any ideas what might be causing this?
ROM: DCD 2.1.0
Radio: 3.27.00
Click to expand...
Click to collapse
What Bootloader are you using?
I was using 2.40, like the DCD FAQ says but I see the radio requires 1.20... which I'm having trouble finding.
Anyone with a link to TitanUnlocker to install 1.20?
ookami007 said:
I was using 2.40, like the DCD FAQ says but I see the radio requires 1.20... which I'm having trouble finding.
Anyone with a link to TitanUnlocker to install 1.20?
Click to expand...
Click to collapse
Here you go...
TitanUnlocker
Tried that... it puts 1.10 on and kills communication to my phone. Now I'm stuck at a 2.40 bootloader screen and unable to flash it.
Thank God for titan_exitbl.exe!!!
So... I need a copy of TitanUnlocker that will upgrade me to 1.20
So... I need a copy of TitanUnlocker that will upgrade me to 1.20
Click to expand...
Click to collapse
You're not following the instructions correctly. Do EVERYTHING it says and it will install right.
gc.. why you usin radio 3.37.71?
kflipproductions said:
gc.. why you usin radio 3.37.71?
Click to expand...
Click to collapse
I always wondered that... LOL
I tried it again... same thing. Basically, as soon as the SPL-1.10 screen comes up, ActiveSync grays out, so I can't establish an activesync connection.
ookami007 said:
I tried it again... same thing. Basically, as soon as the SPL-1.10 screen comes up, ActiveSync grays out, so I can't establish an activesync connection.
Click to expand...
Click to collapse
That's correct. after you get the initial connection... it will not get an accurate ActiveSync connection. Don't worry. if you follow the instructions to a T... you'll be able to flash properly.
Ok... being as I LOVE beating my head against the wall... I tried it... for the third time... this time... it worked!
So... I am happily using my phone with the Radio 3.42.50 and the latest DCD ROM!
Thanks to all who helped!