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 could hack Radio rom from Cinglar,and make Flashable file.
2 of them,,Version 1.10 and 1.16 were tested on my VarioII.
i tried to upload them onto xda-FTP many times but fialed.
so i uploaded to my FTP for you guys.
instruction of upgrade also there.
Please got to get them if you interested in.
http://asukal.net/blog/2006/09/radio_upgrade_hermes_form_cing.html
Good luck
Asukaly yours!
WTF! This is _VERY_ good news!! :shock:
How did you manage to cook the type 2 radio rom??
Is Ma_Upgrade_NoID working with the hermes bootloader?? AFAIK the bootloader lacks wdata command... (replaced by 'wdatah')
Is it that you need only rwdata but not wdata to flash radio?
An explanation of the process to create the working nbf out of the extracted .nb files would be very useful!
Thanks!!
EDIT: I uploaded the files to xda-dev FTP and make a new wiki page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Thanks for the new Radio update. Just updated my MDA Vario II. Will test if there's any improvements!
Seems to work like a charm!
ROM 1.18.255.3
ROM date: 07/22/06
Protocol version: 32.53.7018.01H
Ext ROM 1.18.255.106
Radio 1.16.00.00
And my Bootloader remains at V1.04 :!:
(I'd have pasted a bitmap, but I couldn't figure out how!).
Major kudos to Asukal!!!!!!!
Now if we could only find a new TyTN System ROM to go along with this spiffy new radio...
super Asukal, great news!!!
about the screen alignment problem, if you have some free time, could you please translate whats is the problem and how they do to fix the screen alignment problem please
http://inuchanbt.blog54.fc2.com/blog-entry-86.html
thanks you so much Asukal!
I am receiving country id error : 120 while attempting to upgrade the radio from Cingular 1.31 ( radio 1.13). Even when i ran the upgrade second time device seems to go into radio update screen but just sits there and doing nothing.
then the radio updare error comes up. following the soft reset I have checked device information and radio version is still: 1.13
device is HTC TyTN, originally shipped with Italian ROM.
any ideas?
@superduper: I guess you need a 1.04 bootloader to perform the radio only rom upgrade from Asukal, but your current rom has bootloader 1.06
Let's see if anyone else with Cingular 1.31 rom can do the radio only upgrade or has the same problem you reported...
@Asukal: please give us details on how you did to extract the "radio_.nbf" from shipped Hermimg Cingular NBH file
this is super excellent. Now all we need is a rom image update then we can make our own aku 3.2 version.
Good job Asukal.
vua777 said:
super Asukal, great news!!!
about the screen alignment problem, if you have some free time, could you please translate whats is the problem and how they do to fix the screen alignment problem please
http://inuchanbt.blog54.fc2.com/blog-entry-86.html
thanks you so much Asukal!
Click to expand...
Click to collapse
he did ...pls see a picture
Summary to extract and convert nbh, pls wait a while.
i will make report after finish all my project of this,
now i am trying to flash Only Splash, and only OS, only Extrom separately.
PLS patient!
and thanks report guys!.
if no_id_upgrade can not work on Bootloader 1.06,
can u try with Hermes Upgrade.exe with this nbf?
(you must remove nbh before that, i didnt try that so i am not sure it work or not) :?
thanks a lot Asukal!!!
no luck. file open error : 240 :?
Asukal said:
if no_id_upgrade can not work on Bootloader 1.06,
can u try with Hermes Upgrade.exe with this nbf?
(you must remove nbh before that, i didnt try that so i am not sure it work or not) :?
Click to expand...
Click to collapse
Is it any better?
So, a question for those of you who've done the upgrade - does it make any difference you can notice? Just wondering if it's worth doing the upgrade at the moment, or waiting for new HTC rom when it finally appears.
Tried this on a Orange M3100 with the 1.31 Cingular ROM, but it doesn work. Just sites at 0% and then you eventually get an error. Seems like you need bootloader 1.04 for this to work...
are there any improvements using these new radio roms? also, what's the difference between 1.10 and 1.16?
thanks
I wasn't having any radio problems previously, and so far, I haven't seen any issues with 1.16, either.
Bluetooth works fine, UMTS/GSM calls work fine, WLAN works fine, and UMTS data works fine...
If I see any strange behaviors, I'll be sure to point them out...
Asukal said:
Summary to extract and convert nbh, pls wait a while.
i will make report after finish all my project of this,
now i am trying to flash Only Splash, and only OS, only Extrom separately.
PLS patient!
Click to expand...
Click to collapse
Aaaaghhh! I can't wait
Please tell me if this process is correct to create the radio_.nbf:
Code:
nbh2dbh.pl HERMIMG.nbh HERMIMG.dbh
dbhdecode.pl HERMIMG.dbh
alpinenbfdecode.pl -e ./GSM.nb radio_.nbf
My radio_.nbf and yours differ, is it because of headers?
Thanks!
Just tried the procedure on mine.
Hardware = Dopod 838Pro
ROM = imate
Upgraded to radio version 1.16, the procedure worked fine! Except that after the flashing was complete the PC displayed "upgrade failed" but after a soft reset of the PDA, it worked.
You did a great job, Asukal!!!
I can see some improvement that I can see more wireless bar on my title bar after I upgrade radio ROM.
Thsi is cingular ROM, so I don't know somebody who lives outside US can see this improvement, but I can see it in my rural US state.
In addition, as you said, I can see OS runs smoothly than my original ROM.
I was usually stuck when I run "menu" or "button" applet in control panet. But after I upgrade to Radio 1.16, I don't have it.
I don't know why, but it is real.
I appreciate your effot!!
works great, thanks..
guys who can not flash Radio
One of my friends try to flash 1.16.and faild in that.
But could flash 1.11.
then tried 1.16 again, finally he could flash 1.16.
Please try this step.<this is not to guarantee can do, just a possibility>
And i will prepare 1.13 also soon.
Hello all,
I'm creating this poll to try and figure out why some of us can't unlock our Extended ROM / extrom.
By the way, I'd like to thank all the developers on this forum who contribute software for our Hermes... this thread is in no way a complaint or cut down to their software and guides. All I'm trying to do is just figure out why some of us can't unlock our Extended ROM. Do not Flame or Complain about any developer's software in this thread!!!!!
If you have questions on how to unlock your Extended Rom go to the following links:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
http://forum.xda-developers.com/showthread.php?t=283750
Here's my situation:
- I had a stock Cingular 8525 with a 1.06 bootloader and 1.34 ROM
- I then did an unlock sim and super cid and had no problems
- I then used HTweaC 2.1b to Unhide and Unlock my Extended ROM and was successful.
- I then followed Mr.Vanx's guide to upgrade to LVSW WM6
http://www.mrvanx.myzen.co.uk/hermes_guide/lvsw/
- Following the guide, I upgraded my Bootloader to Olipro HardSPL 1.40, upgraded my Radio ROM to 1.38.00.10, and then successfully installed LVSW WM6
At this point, my Extended ROM was unhidden but locked. I've read posts saying that it was because WM6 doesn't allow you to write to the Extended ROM so I assumed it was a limitation of WM6.
I then installed Black 2.0 WM6 and again, my Extended ROM was unhidden but locked.... again assuming it's a WM6 issue....
After tinkering around WM6, I decided to revert back to my Cingular stock 1.34 ROM since I was having trouble using WM6's Internet Sharing to tether my laptop to my 8525.... I find it easier using WM5's DUN since I don't have to muck around with proxy server settings on my laptop when using WM6's Internet Sharing.
Anyways, after using:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeGuide
I stripped out the OS.nb of the stock Cingular 1.34 ROM, created a new .nbh and then used ruuwrapper.exe to load the stock Cingular 1.34 ROM.
So now, I'm back at the Cingular 1.34 ROM but after using all the methods I used previously to unhide and unlock my Extended ROM, I'm only able to unhide my Extended ROM but not unlock it. I hope this is not permanent . I really liked having the additional 10MB
Anyways... I hope some of us can figure out a solution to how to unlock our Extended ROM
By the way, I did try to reformat my extended rom using this post but was unsuccessful since the Extended ROM is write protected.
http://forum.xda-developers.com/showthread.php?t=290132
For those of you who can't unlock, can you post what you tried to use to Unhide and Unlock your Extended ROM to try to find a pattern on our problem?
joel32137 said:
Hello all,
I'm creating this poll to try and figure out why some of us can't unlock our Extended ROM / extrom.
By the way, I'd like to thank all the developers on this forum who contribute software for our Hermes... this thread is in no way a complaint or cut down to their software and guides. All I'm trying to do is just figure out why some of us can't unlock our Extended ROM. Do not Flame or Complain about any developer's software in this thread!!!!!
If you have questions on how to unlock your Extended Rom go to the following links:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
http://forum.xda-developers.com/showthread.php?t=283750
Here's my situation:
- I had a stock Cingular 8525 with a 1.06 bootloader and 1.34 ROM
- I then did an unlock sim and super cid and had no problems
- I then used HTweaC 2.1b to Unhide and Unlock my Extended ROM and was successful.
- I then followed Mr.Vanx's guide to upgrade to LVSW WM6
http://www.mrvanx.myzen.co.uk/hermes_guide/lvsw/
- Following the guide, I upgraded my Bootloader to Olipro HardSPL 1.40, upgraded my Radio ROM to 1.38.00.10, and then successfully installed LVSW WM6
At this point, my Extended ROM was unhidden but locked. I've read posts saying that it was because WM6 doesn't allow you to write to the Extended ROM so I assumed it was a limitation of WM6.
I then installed Black 2.0 WM6 and again, my Extended ROM was unhidden but locked.... again assuming it's a WM6 issue....
After tinkering around WM6, I decided to revert back to my Cingular stock 1.34 ROM since I was having trouble using WM6's Internet Sharing to tether my laptop to my 8525.... I find it easier using WM5's DUN since I don't have to muck around with proxy server settings on my laptop when using WM6's Internet Sharing.
Anyways, after using:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeGuide
I stripped out the OS.nb of the stock Cingular 1.34 ROM, created a new .nbh and then used ruuwrapper.exe to load the stock Cingular 1.34 ROM.
So now, I'm back at the Cingular 1.34 ROM but after using all the methods I used previously to unhide and unlock my Extended ROM, I'm only able to unhide my Extended ROM but not unlock it. I hope this is not permanent . I really liked having the additional 10MB
Anyways... I hope some of us can figure out a solution to how to unlock our Extended ROM
By the way, I did try to reformat my extended rom using this post but was unsuccessful since the Extended ROM is write protected.
http://forum.xda-developers.com/showthread.php?t=290132
For those of you who can't unlock, can you post what you tried to use to Unhide and Unlock your Extended ROM to try to find a pattern on our problem?
Click to expand...
Click to collapse
I created a patch for the ExtROM for those who aren't SuperCID, you need the developer certificates for it to work, and it's only proven (by me) to be working under WM6, technically it should work with WM5 but we've found that WM5 could possibly have extra security that prevents the dll running, although I don't see how personally.
Hmmm ... I followed the guide except I installed the latest Oli and radio, then reflashed to Black 2.0, and then ran the SuperCID/SIM unlocker doing both.
Able to unlock the extrom and clear it no probs.
Thanks Olipro and Chachi for your input, I'll give it a whirl and hope to unlock my Extended ROM and post my results.
By the way, here's a link to Olipro's patch mentioned above:
http://forum.xda-developers.com/showthread.php?t=297085
Just read the Olipro Unlocking ExtRom method / thread from the link below, then ran the ExtROMPatcher.exe on my 8525. Patch ran successfully. After a soft reset, I couldn't see the Extended ROM partition. So, I then installed the sdkcerts.cab as well as installed the Security Configuration Manager (for the noobs: downloaded from M$ ... it's a Powertoy for WM5) and made sure Security was turned off for my 8525. I then did a soft reset..... however..... like many others from the thread below, I was unsuccessful. I have to say... Olipro was more than patient trying to help everyone in the thread
joel32137 said:
Thanks Olipro and Chachi for your input, I'll give it a whirl and hope to unlock my Extended ROM and post my results.
By the way, here's a link to Olipro's patch mentioned above:
http://forum.xda-developers.com/showthread.php?t=297085
Click to expand...
Click to collapse
joel32137 said:
Just read the Olipro Unlocking ExtRom method / thread from the link below, then ran the ExtROMPatcher.exe on my 8525. Patch ran successfully. After a soft reset, I couldn't see the Extended ROM partition. So, I then installed the sdkcerts.cab as well as installed the Security Configuration Manager (for the noobs: downloaded from M$ ... it's a Powertoy for WM5) and made sure Security was turned off for my 8525. I then did a soft reset..... however..... like many others from the thread below, I was unsuccessful. I have to say... Olipro was more than patient trying to help everyone in the thread
Click to expand...
Click to collapse
you could try renaming OEM_FLASHDRV.dll to something else (like OEM_FLASHDRV2.dll) and then changing the registry to use the new OEM driver.
currently I'm using WM6 with the patch with no problems. since you're on the WM5 ROM it might not work; but as I say, try the above suggestion and see if you get any joy.
After each ROM upgrade I run 2 files... First I run MountExtROM_v2.cab then ExtROMPatcher.exe In that order. The ExtROMPatcher resets the device and my Ext ROM is visible and I can write to it.
This has worked for every WM6 ROM and also some of the WM5 ROMS (but can't remember which except one of the Dopods).
Hi Olipro, thanks for the tip but I tried renaming OEM_FLASHDRV.dll to OEM_FLASHDRV2.dll and updated the corresponding registry key but still no luck.
Hi ach2, thanks for the tip as well but I've definitely ran MountExtROM_v2.cab and then ExtROMPatcher.exe In that order but still no luck....
What's interesting is that only 2 people are not able to unlock their Extended ROM but from reading all the posts related to this issue, it would seem there was more people encountering this problem....
joel32137 said:
Hi Olipro, thanks for the tip but I tried renaming OEM_FLASHDRV.dll to OEM_FLASHDRV2.dll and updated the corresponding registry key but still no luck.
Hi ach2, thanks for the tip as well but I've definitely ran MountExtROM_v2.cab and then ExtROMPatcher.exe In that order but still no luck....
What's interesting is that only 2 people are not able to unlock their Extended ROM but from reading all the posts related to this issue, it would seem there was more people encountering this problem....
Click to expand...
Click to collapse
you also installed the SDK certificates?
Definitely installed the SDK certificates you attached from the previous thread.
I followed everything you suggested from the previous thread.
Could I have in someway screwed up the Extended ROM partition during my WM6 flashing?
What's odd is that whenever I flash a new ROM (with an Extended ROM), the Extended ROM gets overwritten so I know it is able to be unlocked.
Olipro said:
you also installed the SDK certificates?
Click to expand...
Click to collapse
I think I figured out a solution to this problem.
I was able to unlock my Extended ROM by re-doing pof's SIM & CID Unlocker
http://forum.xda-developers.com/showthread.php?t=293665
You'll have to do the entire procedure again using the Instructions.txt
That means going through the process of copying the SSPL-HERM.exe to your Hermes and running from your Hermes. Then run the ROMUpgradeUt.exe from your computer. After the upgrade completes (around 20 min), copy the Herm_Unlock_v3.exe to your PDA and run it. That's what I did to unlock my Ext. Rom.
Please note that I did run a previous version of pof's unlocker and was successful in unlocking my Ext. Rom. It was only after I upgraded to HardSPL V5 and installed WM6 is when I lost write access to my Extended ROM. I'm still not sure if it was the install of HardSPL v5 or WM6 that locked my Extended ROM but I'm just happy it's now unlocked.
Hope this thread helps some noobs.
I installed Olipro Hard SPL and am now able to try any wm6 ROM without SPL.
After having tried many of them, I would like to downgrade and try the last Qtek shipped ROM for wizard: QT_FR_9100_2170706_21707106_20710_180406.
But no matter how I try, I'm now unable to install that wm5 ROM.
Even my former SPV M3000 shipped ROM refuse to re-install.
I guess it's either a problem of RUU, or more probably a problem of SPL on those ROM.
I'd like to remove their SPL, but I don't know how to do.
Any tutorial, advice, or special no ID RUU that fits well those wm5 ROM?
The actual problem with this Rom is the RUU.
It won't let you downgrade.
However it is wise to get rid of the IPL/SPL, for safety and for keeping the hard SPL.
You can use typho5.exe to disassemble the ROM in parts, and use nbftool to re-assemble it without using the IPL/SPL.
They are available in the ROM kitchens.
Use the ruu in the hard spl thread for flashing.
Thanks for the reply, Equinoxe.
Actually I've already tried many RUU, not only the Ruu already included in the official ROM.
Mun RUU etc. But no luck, all kind of error occured but the the flashing remains impossible.
I'll try to find the tools you told me about and see whether removing IPL/SPL makes it easier to flash those ROM.
If you know any special RUU suitable for such a downgrade, please, let me know.
riri22 said:
Thanks for the reply, Equinoxe.
Actually I've already tried many RUU, not only the Ruu already included in the official ROM.
Mun RUU etc. But no luck, all kind of error occured but the the flashing remains impossible.
I'll try to find the tools you told me about and see whether removing IPL/SPL makes it easier to flash those ROM.
If you know any special RUU suitable for such a downgrade, please, let me know.
Click to expand...
Click to collapse
If Mun's RUU didn't do the trick, you better use the CORE pro kitchen.
You can extract the parts with typho5.exe
usage:
typho5.exe -x nk.nbf
all the parts will be created/extracted
Delete all the IPL_1 IPL_2 SPL_1 and SPL_2 parts
use nbftool to reassemble the ROM. (read the PDf to see the starting addresses, although nbftool should be patched to show the right addresses)
Good luck
EquinoXe
the-equinoxe said:
If Mun's RUU didn't do the trick, you better use the CORE pro kitchen.
You can extract the parts with typho5.exe
usage:
typho5.exe -x nk.nbf
all the parts will be created/extracted
Delete all the IPL_1 IPL_2 SPL_1 and SPL_2 parts
use nbftool to reassemble the ROM. (read the PDf to see the starting addresses, although nbftool should be patched to show the right addresses)
Good luck
EquinoXe
Click to expand...
Click to collapse
Hi Equinox, thanks for the reply.
I started trying to get typho working, but all I could see was a brief command prompt and nothing else.
Finally, I ended up using Molski DevPack, which already includes those tools, in quite an ergonomic way.
After finding a guide about using those tools, It took me, no kidding about 10 mn for the whole process and 5 more to do the flashing.
I used nb2nbf_wizard to reassemble the ROM with only the parts I wanted to keep, including the extended ROM.
Regarding the address, it did it automatically, except for the HTC logo that I did manually, and also for the name of the Extended and Logo I renamed according to the sample jpeg showing that soft in action.
Since I kept the extended ROM and the original splash and logo screen, and I now have an authentic Qtek Wizard, just for fun.
But the most important is the feeling of building one's own ROM, according to your own taste and choice. Wonderful.
You were right: after having removed SPL/IPL and rebuilt the ROM, the Mun RUU worked flawlessly to flash my so called Qtek ROM onto my wizard.
In the meantime, It got rid of the pile of miscellanous splash screens and logos that were left since the install of all previous wm6 ROM.
Thanks again for the tips.
P.S.: the guide I used to understand how to use the Molski DevPack:
http://forum.xda-developers.com/showthread.php?t=320910&highlight=RUU_2001
Can't update rom anymore
Info about phone
WIZA200
IPL 2.21.0001
SPL 2.21.olip
GSM 02.19.11
OS 6.0.0.0
TNT_5.0_Wizard_TouchFLO
Windows XP
Active Sync 4.5 (Works Fine)
When i try to install another ROM i get communication error[224] : DEVICE NOT RESPONDING
When i try to install Cert_SPCS.cab or EnableRapi.cab or TomTom i get installation of xxxx.cab was unsuccessful.
Please help
Hi,
i was trying to upgrade my Hermes to WM6 and i was doing it according to mrvnx guide. First i tried the WM6 guide. Ipl was 1.01 and SPL was 1.11. Evrything went fine up until the part where the actual ROM was supposed to be flashed. The update pocess started, and i went for a smoke somewhere at 2%. When i came back, there was a message saying image file was corrupted, and Hermes was up and running. So, my first instinct was that i missunderstood something and that that guide was for phones already having WM6, so i decided to do the WM5 guide. I flashed the SPL, skipped the radio upgrade (cause i didn't know whether to use that version or the later one) and skipped to the next page. And, low and behold, there it says "Firstly download the WM5 ROM you wish to upgrade to"
And now i'm stuck and i don't know what to do. Should i get some WM5 ROM and first upgrade to it and then to WM6? Or should i go straight for WM6 ROM? If so, do i just follow the WM5 guide only using WM6 ROM or do i just flash it by the WM6 guide?
The phone still works with no problems at all. The desired WM6 ROM is Pays Full. Is it really corupted (got it from the "download full" link in the first post here), or was it my mistake?
Sim unlock and cid unlock your device then - http://pof.eslack.org/hermes-unlocker/
Download your carriers Rom (wm5 or wm6 - o2,orange,at&t etc)
then flash that.
then HARDSPL your device - http://forum.xda-developers.com/showthread.php?t=296722
then use modified updater to flash your device with the wm6/6.1 rom of your choice.. works fine for me.
2.10 bootloader with the "is it hardspl" checked and wa'la its updated
hope this helps.
Thanx for the answer. I doubt i'll find my carrier's rom, since i'm from Croatia, and i think it hasn't been posted here, and certainly hasn't been posted on my provider's site. I did make a backup before upgrading, and i have the three raw files made with itsutils. Will this do?
Also, could you please explain why i need to sim/cid unlock it? The device itself is not branded at all, i believe it's only locked to the provider's sim, and that's all. Does sim /cid unlocking cover that or is it about something else?
Thanx!
Sim unlocking = you can use other sims
CID unlocking = you can use other roms (maybe why your update is crashing)
HARDSPL = One less chance of bricking your device
as your device is still currently up and running im guessing you can do it all via that rom.
Ok, just so i don't missunderstand you, can i do what you suggested, but without flashing the carrier's rom?
you can, however you may encounter problems with wm6.1 in the future (hard resets etc)
OK to clear this thread up....
...make sure you have flashed HardSPL before continuing then...
...redownload the ROM it sounds like it has become corrupted whilst being downloaded so make sure you unzip the whole thing to a folder first then try it.
did everything like kingsizeriz told me, except i did it on the existing rom. uploaded the same rom i tried before and it worked like a charm. me and mates have been fiddling with it the whole evening and noticed no problems so far. Thanx for the help, much appreciated
Btw, one last question, is NK.EXE supposed to be 0 bytes?