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.
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.
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 upgrade from the wwe aku 3.3 rom to swe rom
and go back to the wwe version
every thing was ok
but when i flash the extrom i forgot in mitty to write
after the name of the extrom.nb to put the number 57500000
then i made reset task 8
and my phone turn off no on never
i did all proccess again with the number but when i do task 8 to reset the phone turn off
and i cant make it on again plz your help plz
Will the phone enter bootloader mode? Is it the 1.01 MFG bootloader? If so, look at the wiki and use the codes there to check your nand status, cid, etc. If everything checks out as OK then this might work: use mtty to reflash the os, reset, then use mtty to reflash the ext rom. DO NOT FORGET THE ADDRESS when you flash with mtty! As you have found it can cause all sorts of headaches.
If you can't get it into bootloader mode you're in trouble. If your bootloader no longer reads as 1.01 you will have to reflash that as well (might be a good idea to reflash it anyway, no telling where your previous flash attempts ended up)
YMMV. Do this at your own risk.
Ninja1
thanks friend
its ok now i just upgrade again the rom then the extrom and
its on again woww i was shaking
but now again with my aku 3.3 wwe
i have jasjam it work very good with it
very fast
and i dont know what need to be diffrent but it looks ok
like the other versions
maybe cause i dont know what need to be change with the aku 3.3
thanks
Glad to hear that it is OK. If I might suggest, leave the flashing alone for a bit and just enjoy your resurrected toy...
Ninja1
i made a mistake to when i updated from swe rom to wwe rom there was no OS i all most cried when the phone did not turn on but everything is ok now 1.01 MFG bootloader is the best
hahaha happened to me as well in the EXACT situation. Yeah for me I was doing it at work. next time i will make sure I am solely focused on the one task.
fyi upon review yes the swedish one is faster
Yeah, when you forget the offset, you flash the extrom over the top of the os
at least this doesn't trash the bl so you can get out of it again....
I have the same problem...but i did it according what they had post....but then now..my phone can't even on at all...can't go into BOOTLOADER at all.....sad..n scare...
nelsonlye said:
...but i did it according what they had post...
Click to expand...
Click to collapse
What does this mean? Try explaining exactly what you did (or forgot to do), and maybe we can help you.
Ninja1
Follow the way to flash it to AKU 3.3...ord did it.....
I already change to Bootloader 1.01 MFG....then flash according....
I just didn't flash the EXT.ROM only..
And the problem was/is?
Only one short question! -Only one short answer! ;-)
I´ve flashed my hermes to the 1.35 radio rom. Now iam getting these ****ty
radio waves signals out of the hermes´s earspeaker . And it is possible that i have to send in my device, because i have several problems with sending sms. Because of these things it would be very nice if it is possible to flash back to the shipped version of the Radio Rom(1.27.00.00)
I tried to flash back with
RUU_Hermes_TMD-TMA_Radiopatch_1.27.00.00_107_GER.exe
and it completed succesfully but on the hermes is still the 1.35 Version of the radio rom.
THX
You will need the sspl version of the installer. It can be downloaded here.
hmm, so i took the wrong radio ROm version?
on this site:
http://forum.xda-developers.com/showthread.php?t=291827
i took the first one because i have a herm300 from t-mobile.
So i only have to flash with the version you gave me, and thats all?
Update radio without Activesync connetion
Can I update this rom version without any activesycn connection. My HTC TYTN is hang out after rom dwwongrading and now it start unitl windows loading screen. I think that only alternative is download new rom with help of three colour screen usb connetion or with help of mtty program. My bootloader version is 1.09
Please let me know your opinions,
Juha
@Miliano: you are correct. The sspl download for v1.27 was created by wpbear.
Unbelievably, I found the link for you by looking in the Hermes WiKi....
@frontpage: sspl based flashing won't work unless windows mobile can load
What I have now:
OS: Black 2.0 Cingular edition
Boot Loader: 1.01
Radio BL: 108
Radio: 1.38.10
what I want:
OS: WM 5 from the 1.34 cingular release
Boot Loader: Loader from the 1.34 cingular release
Radio BL: AFAIK you can't downgrade these so staying at 108
Radio: 1.16.00.00
How I plan to get there:
take the .nbh form the 1.34 cingular package and use RUU to flash the device.
Questions and concersion:
I'm looking for input on possible incompatabilities and hang-ups with varios BL versions and what not.
comments / feedback on my plan would be greatly appreciated and I will build a monument in your name if you help .
This has been covered before...
But, since you're well on your way to brick-ville, I'll buy your phone off you for, say, $100? It'll be worth less after you brick it...
Read up on the W*I*K*I and Oli's 1.40.Olipro bootloader before you do something dumb.
I did read it.
And thats the plan I came up with.
I was looking more for a confirmation.
The wiki has a ton of great info but its laid out reall crappy and not very cohesive. So I figured I'd post what I've came up with after reading it to see if I missed something. And from there maybe get more specific input on where the issues/dependencies are..... or maybe not.
spicer said:
I did read it.
And thats the plan I came up with.
I was looking more for a confirmation.
The wiki has a ton of great info but its laid out reall crappy and not very cohesive. So I figured I'd post what I've came up with after reading it to see if I missed something. And from there maybe get more specific input on where the issues/dependencies are..... or maybe not.
Click to expand...
Click to collapse
From your plan it is obvious that, even IF you read the wiki, you didn't understand it. Re-read the THREADS about 1.40 SPL and also search for MRVANX and read his TUTORIALS...
---New plan
What I have now:
OS: Black 2.0 Cingular edition
Boot Loader: 1.01
Radio BL: 108
Radio: 1.38.10
what I want:
OS: WM 5 from the 1.34 cingular release
Boot Loader: Loader from the 1.34 cingular release
Radio BL: AFAIK you can't downgrade these so staying at 108
Radio: 1.16.00.00
How I plan to get there:
Flash to hardSPL-v6
Fash Radio to 1.16
flash OS i get out of the 1.134 package. (the os.nb file i believe it is named)
last flash the boot loader.
Questions and concersion:
I'm looking for input on possible incompatabilities and hang-ups with varios BL versions and what not.
comments / feedback on my plan would be greatly appreciated and I will build a monument in your name if you help .
LegolasTheElf said:
From your plan it is obvious that, even IF you read the wiki, you didn't understand it. Re-read the THREADS about 1.40 SPL and also search for MRVANX and read his TUTORIALS...
Click to expand...
Click to collapse
I really appreciate the feedback. At least you're letting me know my plan wont work. Which will prevent me from trying it. But it would be kick ass if you could be more specific about what in the wiki i missed like :
-you can't flash the entire .nbh file cause it will try to replace your boot load and break it.
or
- Re-read the THREADS about 1.40 SPL because *something useful here*
Either way I'm still thankful cause I know my plan is a **** sandwich.
Very good.. You're getting there! It's nice to see someone read some directions..
You have it mostly right.. Flash the HardSPLv6 first. Then, grab the .nbh from the cingular rom and combine it with CustomRUU. Choose 'Autodetect' (we're looking for a hard-spl flash)..
Then, once that's done, you'll have the right radio, OS, splash, etc.. The only thing left would be to down-grade the bootloader, which I would advise against.. But, you can do it.. There is a seperate thread on HOW to do that, as it isn't just a one-step process.. Search and ye shall find.
Thank MAn!!! That kicks ass.
I need to send my phone back because the radio dies every 5 mintes.
So I want to get it as close to factory as possible.
So after I downgrade the BL i won't be doing anymore flashing to that phone.
Sometimes when I soft reset the phone is says "No GSM" even when sim is there. Soft reset it again and the radio is detected.
Very irritating.
Check out:
http://www.mrvanx.org/hermes_guide/
Flash HardSPL-1.40
Create NBH containing your provider's 2xSplashScreen + ExtROM + OS & flash it
Flash 1.16 radio
Flash-HardSPL-1.10
Flash your original IPL & SPL versions.
F-ya! That last part about down grading the BL is the part I was having trouble pinning down.
One last question:
Can I use the cingular NBH or will it try to flash the RBL and crash because you can't down grade the RBL
the the new mrvanx page is dope. found the donwgrade guide.
Bricked using this method
pof said:
Flash HardSPL-1.40
Create NBH containing your provider's 2xSplashScreen + ExtROM + OS & flash it
Flash 1.16 radio
Flash-HardSPL-1.10
Flash your original IPL & SPL versions.
Click to expand...
Click to collapse
Pof,
I did it this way but after flashing the radio rom I get no GSM and then I'm stuck in the Windows Mobile Screen.
I have looked in the Wiki but how can I actually unbrick?
My SPL is still 1.40 Oli. But I can't get activesync to work.
Should I flash the new radio via SD card or any other way (mtty?)
I would be very gratefull for any help,
Cheers,
HJ
P.S. Found a solution; http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
I will try to do this trick.
Thanks
@hellejoep: Try flashing your latest working radio again in NBH format.
pof said:
@hellejoep: Try flashing your latest working radio again in NBH format.
Click to expand...
Click to collapse
Pof,
One question, Can I upgrade radio rom via mtty?
Or otherwise?
Cheers,
HJ
P.S. How can I Flash any radio in NBH format? While stuck in bootloader?
hellejoep said:
Can I upgrade radio rom via mtty?
Click to expand...
Click to collapse
no
hellejoep said:
How can I Flash any radio in NBH format? While stuck in bootloader?
Click to expand...
Click to collapse
Disable activesync, and use CustomRUU.
pof said:
Disable activesync, and use CustomRUU.
Click to expand...
Click to collapse
Done that but then I get a Error 260.....
Any suggestions?
Or is there a way to bypass this? I have IPL 1.01 and SPL 1.40 Olipro.
I now got a Connection Error 264 but the bootloader gives usb and I can reach the hermes bij MTTY.exe.....
What is going wrong?
@hellejoep: close all programs including mtty before u run ruuwraper. Make sure you're using the latest version (v4.2) and activesync is not enabled.
pof said:
@hellejoep: close all programs including mtty before u run ruuwraper. Make sure you're using the latest version (v4.2) and activesync is not enabled.
Click to expand...
Click to collapse
It worked, cheers!!!!!
LegolasTheElf said:
Very good.. You're getting there! It's nice to see someone read some directions..
You have it mostly right.. Flash the HardSPLv6 first. Then, grab the .nbh from the cingular rom and combine it with CustomRUU. Choose 'Autodetect' (we're looking for a hard-spl flash)..
Then, once that's done, you'll have the right radio, OS, splash, etc.. The only thing left would be to down-grade the bootloader, which I would advise against.. But, you can do it.. There is a seperate thread on HOW to do that, as it isn't just a one-step process.. Search and ye shall find.
Click to expand...
Click to collapse
@LegolasTheElf,
This was great example on how to get people to read the wiki. I like your approach and I will try to use it in the future.