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.
Related
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.
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
uedam said:
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
Click to expand...
Click to collapse
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
01015 said:
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
Click to expand...
Click to collapse
In addition I tried this rom with bootloader 1.09 and radio 1.18.00.10.
ftp://xda:[email protected][1].35.255.2_1.35.255.102_1.08.00.10_SHIP.EXE
The radio rom was not upgraded to 1.18, it remains 1.14.
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
pof, see http://forum.xda-developers.com/showpost.php?p=1068511&postcount=35
might be due to the new SoftBank ROM sold since December?
Even they http://www.imei-check.co.uk/m3100unlock.php couldn't do it:
The Unlocker it will NOT WORK with Japanase Softbank devices with SPL1.09 and radio 1.14.00.10 sold after 1st December 2006. To check your spl just put the phone in bootloader :hold the [OK] button (from the left side of the phone where the volume button is) and the [power on] button and in same time press the [reset] hole (near to the charger connector -- use stylus to press it!) and you can see IPL and SPL
Radio version can be checked from Start->Settings->System->Device Information:Radio Version.
If you buy the unlocker and claim that your phone is a 1.09 we will NOT refund you. We don't know when we will release a new update or IF we will release one!!!
Click to expand...
Click to collapse
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
pof said:
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
Click to expand...
Click to collapse
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
pof said:
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
Click to expand...
Click to collapse
pof,
I installed usbmon and tried radio rom 1.20 upgrade again (it also failed...)
Here is the log files exported from usbmon. I hope it will help to solve the problem.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/usbmonlog.zip
Sorry, the file was too large to attach to this post.
p.s. If you need further information, please let me know.
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
sn00x said:
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
Click to expand...
Click to collapse
Yes, before upgrade I unlocked my X01HT and used with DoCoMo rom. The radio version was 1.06.00.10.
I uploaded the USB traffic log and please view the file. Does the same thing occur when writing another rom? or this is the first case?
pof said:
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
Click to expand...
Click to collapse
Hmmm, would it make sense to have him log the full-upgrade process - presumably the "locking" happened when he did the RUU_X01HT_1.33.761.4_1.14.00.10.exe
and hopefully it would happen even if Radio 1.14 were already on the system when he re-did the full upgrade.....
Richard
Yes, this will be at least worth looking at
pof said:
Yes, this will be at least worth looking at
Click to expand...
Click to collapse
I did full rom upgrade again and got log to the file.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/fullupgradelog.zip
It's beyond my comprehension.
p.s. It's very large (about 400MB text file, the zip is about 120MB)
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
pof said:
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
pof, it sounds quite interesting. Softbank built the special version of 1.14.00.10 radio?
So, if possible, we cook new rom which includes radio rom same as HTC 1.18.416.1 rom then the person who has 1st version of X01HT can upgrade it safely?
uedam said:
So, if possible, we cook new rom
Click to expand...
Click to collapse
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
pof said:
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
Oooh, that *IS* an interesting (and unpleasant) development. Sounds like imei-check has annoyed some people with good connections to HTC
Richard
rsolomon said:
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
Click to expand...
Click to collapse
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
uedam said:
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
Click to expand...
Click to collapse
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
chainbolt said:
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
Click to expand...
Click to collapse
Sorry, my explanation was not correct. You are right. Thanks.
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 used HardSPL successfully on a Wizard that was formerly:
IPL 2.21.0001
SPL 2.21.0001
GSM 02.19.11
OS 2.21.2.8 GER
It's showing SPL 2.21.Olip, yet all my attempts to flash the phone with the Original T-Mobile USA Rom (RUU_TMobile_US_226102_22610105_022511_WWE_Ship) end up with errors.
If I use the RUU provided with the above ROM, it ends up with an Error 300 (Invalid Update Tool). Using SoftSPL or RUU MUN with the .nbf-file from that package both ends up with an Error 238 (File Read).
I just want to turn this T-Mobile Germany phone into one with the Original T-Mobile USA Rom so if anyone knows how to do this, solving the above problems, any help would be greatly appreciated.
Just to make sure, with an Original shipped Rom such as the T-Mobile USA one, I don't have to make sure to extract the provided IPL/SPL-files it contains before flashing on my G4, do I?
Scotty_73
try this:
Scotty_73 said:
I used HardSPL successfully on a Wizard that was formerly:
IPL 2.21.0001
SPL 2.21.0001
GSM 02.19.11
OS 2.21.2.8 GER
It's showing SPL 2.21.Olip, yet all my attempts to flash the phone with the Original T-Mobile USA Rom (RUU_TMobile_US_226102_22610105_022511_WWE_Ship) end up with errors.
If I use the RUU provided with the above ROM, it ends up with an Error 300 (Invalid Update Tool). Using SoftSPL or RUU MUN with the .nbf-file from that package both ends up with an Error 238 (File Read).
I just want to turn this T-Mobile Germany phone into one with the Original T-Mobile USA Rom so if anyone knows how to do this, solving the above problems, any help would be greatly appreciated.
Just to make sure, with an Original shipped Rom such as the T-Mobile USA one, I don't have to make sure to extract the provided IPL/SPL-files it contains before flashing on my G4, do I?
Scotty_73
Click to expand...
Click to collapse
hello, sometimes the RUU is old, and is not possible to flash roms (because is ooold tool ok)
try downloading a newer RUU and copy the .NBF file in to the RUU folder, now you should be able to flash the ROM you have choosen to your WIZARD
GOOD LUCK!!!
tigrisimo said:
hello, sometimes the RUU is old, and is not possible to flash roms (because is ooold tool ok)
try downloading a newer RUU and copy the .NBF file in to the RUU folder, now you should be able to flash the ROM you have choosen to your WIZARD
GOOD LUCK!!!
Click to expand...
Click to collapse
Thanks for your advice but how could the RUU included in a rom package be outdated if it's specifically meant to be used to flash that rom? I did however follow your suggestion and tried several other RUU's as well, unsuccessfully unfortunately. I would expect the newest available T-Mobile USA Rom would have included the newest available RUU.
So, are there any other suggestions?
if you have a G4 use my setting... i used softspl & romupdatutility_noid...
i´ve uploadet it for you...
just copy in the nk.nbf in the folder and run START-sSPL.exe !
Hi
My HD2 is original unmofidied one. Has stock ROM and I didn't install anything on it yet. I went to update the ROM version to 1.66 from the link posted on the first thread on this forum.
My phone is HD2 with these versions:
ROM 1.48.707.2 (71294) WWE
ROM date 11/09/09
Radio version 2.05.51.05_2
Protocol version 15.28.50.07U
Tried to run the file RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
Program starts working, changes the display on my HD2 to the reb/blue/green HTC preboot screen and then displays the gauge. Going into about 2% of the process of updating the ROM I get the following error message:
ERROR [294] : INVALID VENDER ID
This Update Utility cannot be used for your PDA Phone. Please check your Update Utility.
Why is that? I thought that ROM above is stock rom unmofidied and that should flash just fine without any tweakings at all on my HD2. I don't want to mess around with my HD2, just wanted to update the ROM.
hi
you must apply HSPL before upgrading your rom ,the subject have been treated in another topic .
every hd2 is cid locked... so you can only install rom that you download from htc website using your serial number.
however you can use
1. goldcard method http://forum.xda-developers.com/showthread.php?t=572683 to flash any original rom regardless of language/region
2. use uspl , http://forum.xda-developers.com/showthread.php?t=606713
it flashes any ROM using the original SPL to your device (no warranty void)
3. use hspl http://forum.xda-developers.com/showthread.php?t=611433
you can also return to your original spl if you need it for warranty , everything is explained in that threead