Related
Here is another new ROM from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular.
ROM Version: 1.34.502.1
ROM Date: 09/22/06
Radio: 1.16.00.00
Bootloader: 1.06
As always, download link on the wiki upgrading page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
If you have questions be sure to read the Hermes wiki first, specially the Upgrading FAQs.
Notes on this ROM:
* See the threads on the previous Cingular ROMs for upgrading issues such as enabling video calls, band selection tab, ExtROM customizations, PTT button, etc...
-v1.30
-v1.31
-Downgrading instructions
UPGRADING INSTRUCTIONS:
* People with bootloader <= 1.04 just follow the normal procedure (run RUU twice after invalid vender ID error).
* People with bootloader 1.06 (those who have flashed the cingular 1.31 rom) need to downgrade to bootloader 1.04 first:
1) Put your device in bootloader mode by holding the side Ok button and the power button and at the same time reset with the stylus.
2) Upgrade to a ROM matching your CID, that is a ROM from your vendor (TyTN owners use the TyTN rom, dopod owners the dopod rom, jasjam owners the imate rom, etc...). This will get you back to bootloader 1.04
3) Flash the new 1.34 ROM as usual (run RUU twice after invalid vender ID error).
Enjoy
Guys, i'm at work and still haven't had time to flash it on my Hermes, so the first flashing it please update the OS build and protocol version on the wiki. Thanks
Any chance that we have release notes for this ROM uploaded as well?
Thanks.
cant run the rom file, it said file corrupted. i downloaded twice, both time it said rom file is corrupted. please re upload the rom
Tried to flash from 1.31 to 1.34 - but I get error message ERROR [294] INVALID VENDER ID
Anyone had any luck flashing 1.34
Doesnt upgrade from 1.31 - just get an invalid vender id error...
EDIT: can't downgrade either using the bootloader method - seems like we are now stuck on this rom until a solution is found!
Have you tried to restart the falshing SW without touching the hermes and without disconnecting the USB?
You are supposed to do this a second time when you get this error
Eric
Eric Duprat said:
Have you tried to restart the falshing SW without touching the hermes and without disconnecting the USB?
You are supposed to do this a second time when you get this error
Eric
Click to expand...
Click to collapse
Yep - tried this with Dopod, Cingular 1.30, and HTC ROMs - all get the same invalid vender ID error...
tried that, but it is no help
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
netboy said:
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
Click to expand...
Click to collapse
ROM file is fine. Runs OK here - just cannot flash to a 1.31 device...
netboy said:
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
Click to expand...
Click to collapse
Clear your cache, rom file is OK, I checked the md5sum of it.
Same here - Invlid vendor ID.
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
It makes sense that a direct upgrade from 1.31 -> 1.34 will fail. However, a downgrade to the original TyTN ROM for users having a real TyTN (CID QTEK_001) followed by an upgrade to 1.34 should work. I believe TyTN owners have been reporting success at downgrading from 1.31 although this is mystifying too as one would expect that the bootloader version downgrade should prevent this also....
Sleuth255 said:
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
Click to expand...
Click to collapse
Its a Orange M3100 SIM unlocked (HERM100)
let me REBOOT my pc and try again.
i cleared my cache. still got erros. and said can not unpack, file is corrupted..
@people getting invalid vendor ID:
Please report:
- which device do you have: TyTN, Vario II, SPVM3100, DOPOD 838pro, etc...
- Your device CID: QTEK_001, CDL__001, O2___102, etc... can be checked by "info 2" bootloader command, leave blank if you don't know it.
- Current ROM on your device before trying to upgrade
- Bootloader version
Sleuth255 said:
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
It makes sense that a direct upgrade from 1.31 -> 1.34 will fail. However, a downgrade to the original TyTN ROM for users having a real TyTN (CID QTEK_001) followed by an upgrade to 1.34 should work. I believe TyTN owners have been reporting success at downgrading from 1.31 although this is mystifying too as one would expect that the bootloader version downgrade should prevent this also....
Click to expand...
Click to collapse
True - thinks this makes sense. As Orange haven't released an upgrade yet I can't test this out. Need someone that has a Dopod or TyTN to experiment...
I'm trying this now. I got the same invalid vendor ID (HTC TyTN, running 1.31), and now I'm flashing back to 1.18. This seems to be working, albeit very slowly. I'll keep you updated if I can upgrade from 1.18 - 1.34; the flash to 1.18 should take about 25 minutes.
For people on Cingular, does push to talk work on this rom? If not, then this is not the final rom.
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.
Trying to upgrade my hermes,
but after checking my device, I got error message, something
like this:
error 260, check your usb cable, device is not properly connected
(but it yes, because of successfuly syncing etc.)
I already have netcf 2.0 i 3.0 installed, I restarted
laptop and device...
what to do??
thx
gervasius said:
Trying to upgrade my hermes,
but after checking my device, I got error message, something
like this:
error 260, check your usb cable, device is not properly connected
(but it yes, because of successfuly syncing etc.)
I already have netcf 2.0 i 3.0 installed, I restarted
laptop and device...
what to do??
thx
Click to expand...
Click to collapse
try to flash a different rom
post your question here. Of course after you search for the answer in that thread.
You are using an old RUU with a new bootloader. Extract the NBH and use custom RUU.
but it happened when I tried to flash HardSPL... according to mrvanx guide.
I didn't brick my tytn, just cannot run upgrade. any upgrade...
if somebody has similar problem, pls what to do...
so... let the RUU push SSPL on your phone, do not put it manually in bootloader mode.
which RUU, pls? I'm trying to flash hardSPL according to mr.Vanx guide, with RUUwrapper, I have spl 1.04
I have rom 1.18.255.3 07/22/06 , and radio 1.03.03.10
gervasius said:
which RUU, pls? I'm trying to flash hardSPL according to mr.Vanx guide, with RUUwrapper, I have spl 1.04
I have rom 1.18.255.3 07/22/06 , and radio 1.03.03.10
Click to expand...
Click to collapse
Are you using the RUU at this link?
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 ?
I'm running vp3G latest ROM and wanted to install a radio. I thought I could install the latest 1.54 but when I do it locks up at 0% and then gives me the 262 error message. The wiki says I should have bootloader 1.04 or HARDSPL. I thought I did. Can someone help me out as to what radio will work and what are the steps to upgrading?
Thank You
Read my specs. I have the same rom you do. should work
1.54.07.00 works
1.54.07.00 works well with vp3g's roms
If you can't be past error 262, here's an option:
Copy "SSPL-HERM.exe" to your miniSD then run it from the phone.
Your phone will reboot into the BL (tri-color screen)
Connect your phone via USB to your computer
When AS finally pops up, click cancel
Run RUUWrapper.exe and force SSPL
That should do it.
MontyV77 said:
I'm running vp3G latest ROM and wanted to install a radio. I thought I could install the latest 1.54 but when I do it locks up at 0% and then gives me the 262 error message. The wiki says I should have bootloader 1.04 or HARDSPL. I thought I did. Can someone help me out as to what radio will work and what are the steps to upgrading?
Thank You
Click to expand...
Click to collapse
1.48.00.00