Related
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've read and reread various posts about this. I just want to make sure I have the steps down before I go forward.
What I have now:
Cingular 8525
Rom: 1.34.502.1
Radio version : 1.16
SPL: 1.06
What I would like achieve:
Rom: 2.06.502.3
Radion version: 1.27
SPL: 1.04
Ext Rom: 2.06.502.3
1) Downgrade to SPL 1.04 by flashing the 8525 with file RUU_HER_Cingular_1.30.502.1_1.11.00.00_wwe_cws_ship.exe. This is because it matches my CID CWS__001 and it has SPL 1.04. I guess I simply run it without any other preparations. Is this correct?
2) Super CID and simunlock using HTC_Hermes_SIM_Unlock_v2a.zip
3) I choose the ROM RUU_Hermes_CINGULAR_WWE_2.06.502.3_6275_1.33.31.00_108_Ship.exe
4) Use NBExtract to decompress the above ROM to get files OS.nbf and Extrom.nbf file
5) Flash SPL 1.01MFG using mtty.exe. Is this necessary? Can't I flash OS.nbf with SPL1.04?
6) Flash OS.nbf file extracted using mtty.exe
7) Flash extrom.nbf file extracted using mtty.exe
8) Flash radio from file RUU_Hermes_TMD-TMA_Radiopatch_1.27.00.00_107_GER.exe by simply running it. Is this correct?
Am I missing something in the process?
Lastly, Is this the best COMBINATION of ROM, radio, and ext ROM? And how does RUU_Hermes_CINGULAR_WWE_2[1].06.502.3_6275_1.33.31.00_108_Ship compared to 2.05?
Thanks for any input.
5)
anubus12 said:
...
1) Downgrade to SPL 1.04 by flashing the 8525 with file RUU_HER_Cingular_1.30.502.1_1.11.00.00_wwe_cws_ship.exe. This is because it matches my CID CWS__001 and it has SPL 1.04. I guess I simply run it without any other preparations. Is this correct?
Click to expand...
Click to collapse
I guess there isnt really any need to do that, if you flash SPL 1.01MFG to it then theres no need to do this step.
anubus12 said:
...
2) Super CID and simunlock using HTC_Hermes_SIM_Unlock_v2a.zip
Click to expand...
Click to collapse
I would use the unlocker v3 (i suspect you meant v3 anyway)
anubus12 said:
...
3) I choose the ROM RUU_Hermes_CINGULAR_WWE_2.06.502.3_6275_1.33.31.00_108_Ship.exe
Click to expand...
Click to collapse
The ROM you choose is entirely up to you so yes this should be ok
anubus12 said:
...
4) Use NBExtract to decompress the above ROM to get files OS.nbf and Extrom.nbf file
Click to expand...
Click to collapse
Yep goes without saying ;-)
anubus12 said:
...
5) Flash SPL 1.01MFG using mtty.exe. Is this necessary? Can't I flash OS.nbf with SPL1.04?
Click to expand...
Click to collapse
IF you are doing this then it would be the FIRST step you do
anubus12 said:
...
6) Flash OS.nbf file extracted using mtty.exe
7) Flash extrom.nbf file extracted using mtty.exe
Click to expand...
Click to collapse
Still....yes no problem.
anubus12 said:
...
8) Flash radio from file RUU_Hermes_TMD-TMA_Radiopatch_1.27.00.00_107_GER.exe by simply running it. Is this correct?
Click to expand...
Click to collapse
This part is beyond what i did, my process was that i upgraded to radio ROM 1.27.00.00 using the signed .exe because i originally had SPL 1.09.
anubus12 said:
...
Am I missing something in the process?
Click to expand...
Click to collapse
You seem to have it figured out, but dont go on what i say here, wait for it to be verified by more than just me
My process (having already got superCID and unlocked a while ago) was to upgrade to radio 1.27.00.00 before anything else, then to flash SPL 1.01MFG using mtty, then flash the OS.nb file from the ROM i chose, then to flash ExtROM.nb (again from the ROM i chose). By using radio 1.27 you will have radio loader 107 which is recommended still.
Once some other people have looked over what you posted then you should go ahead (if they all give the "all clear" )
You combination of rom and radio is a good idea (the ROM and ExtROM is entirely up to you but the radio is the highest that doesnt have loader 108?)
It's even easier than that;
get my Custom RUU kit and you can skip the reflash;
take the 3.3AKU and extract the RUU_Signed.
extract the RUU signed with NBHExtract or my GUI tool (make sure it's all in the same directory) then you can create a NEW RUU with SPL 1.04, whatever radio you like (if you want a new one) and the 3.3 OS AKU.
remember: if you do it this way, you can have whatever components you want; ExtROM, OS, mix and match anything.
however... if you don't think you can manage doing this, tell me what you want and I'll happily assemble it for you
1. SuperCid and Unlock with POF VERSION 3
Website:
http://pof.eslack.org/hermes-unlocker/
Install Instructions:
Easy auto-install Instructions:
Unzip unlocker and run AUTO_Unlock_v3.bat
If you don't want to install automatically, or for some reason the process doesn't work for you, here are the manual instructions:
Transfer SSPL/SSPL-HERM.exe to your phone and run it
Tri-color screen will appear
Disable activesync (file -> connection settings -> uncheck "allow USB connections")
Connect your phone to your computer using the USB lead.
Run RUU/ROMUpgradeUt.exe
Follow the flashing process (Check the "I understand..." and "I completed..." boxes and update!)
Allow your phone to reboot.
Transfer HERM_Unlock_v3.exe program to your phone and run it
Click the Unlock Button, select unlock option. Select if you want SIM/CID unlock.
Click "Unlock!" and wait until process finishes.
When done, turn off your phone for 10 seconds and reboot after that.
2. Then Run this cooked ROM (Cooked w/Olipro software)
http://uploadingit.com/files/8194/RUU_CINGULAR_2.06.502.3_1.27.00.00_SPL1.04.zip
Rom: 2.06.502.3
Radion version: 1.27
SPL: 1.04
Ext Rom: 2.06.502.3
I think radio 1.33 or 1.34 is better then 1.27. I do not see a difference between 1.33 or 1.34 though.
You pretty much had the process but this will be easier for you.
just to point out; SuperCID and Unlock (unless using a different SIM) is unnecessary and *could* potentially invalidate your warranty.
SuperCID is pretty much redundant nowadays with the new SSPL; the only real advantage to having your device SuperCID is if there isn't a ROM for your CID with old version stuff to revert to.
Thank you for all the replies! I appreciate it.
@mrvanx and wpbear
The reason stated using unlocker v2a was because, from what I understand, if I use v3 it would put a patched 1.08 Radio BL (which I thought we want to avoid). Which means that I won't be able to "downgrade" to a lower version radio. Am I wrong?
@mrvanx
You said that I didn't need to downgrade to 1.04 BL because I could use 1.01MFG. I thought that I couldn't do that with 1.06 or higher. I had to downgrade to 1.04 first.
@wpbear
I assume in order to use your custom cooked ROM, I have to SuperCID right?
@Olipro
Thanks for the offer of cooking up a ROM. I think wpbear's ROM has everything I wanted. But again, if I wanted to use your ROM, I would have to SuperCID? Also, where can I get your GUI?
But what is the best combination right now of OS, Ext, and radio?
Thanks again!
anubus12 said:
Also, where can I get your GUI?
Click to expand...
Click to collapse
Nevermind, I found your GUI. Thanks!
The only advantage of real SuperCID is being able to write to extrom once you've unlocked it.
You did a real nice v1.0 upgrade set of instructions btw They were perfect. In fact that's exactly what I did to upgrade my 8525.
However, the recent explosion of NBHtools that take advantage of Des' SSPL technique (nicely done Olipro btw )have opened up much better ways to accomplish this now.
anubus12 said:
Thank you for all the replies! I appreciate it.
@Olipro
Thanks for the offer of cooking up a ROM. I think wpbear's ROM has everything I wanted. But again, if I wanted to use your ROM, I would have to SuperCID? Also, where can I get your GUI?
But what is the best combination right now of OS, Ext, and radio?
Thanks again!
Click to expand...
Click to collapse
no, you do *not* have to SuperCID at all with my RUU since it uses SSPL.
if you use the custom RUU (and you can tell, it has the XDA Dev logo on) then your device does not need to be SuperCID
anubus12 said:
@mrvanx
You said that I didn't need to downgrade to 1.04 BL because I could use 1.01MFG. I thought that I couldn't do that with 1.06 or higher. I had to downgrade to 1.04 first.
Click to expand...
Click to collapse
You SHOULD be ok, i downgraded to SPL 1.01MFG from version 1.09 by just flashing it using mtty.exe. I followed the instructions on the How to Flash AKU3.3 Update thread (the first post) to get my new ROM onto my device. I used the HTC AKU3.3 Test ROM and it worked just great.
anubus12 said:
Thank you for all the replies! I appreciate it.
@mrvanx and wpbear
The reason stated using unlocker v2a was because, from what I understand, if I use v3 it would put a patched 1.08 Radio BL (which I thought we want to avoid). Which means that I won't be able to "downgrade" to a lower version radio. Am I wrong?
Click to expand...
Click to collapse
I do not think Pof unlocker put BL 108 on your device, but it doesnt matter anymore since SSPL bypass this and you can now still do radio only changes.
anubus12 said:
@wpbear
I assume in order to use your custom cooked ROM, I have to SuperCID right?
Click to expand...
Click to collapse
No, the bootloader bypasses this now, but as someone else pointed out, if you want to change your Ext_ROM with the hack in the Wiki later, you will need to SuperCID still.
anubus12 said:
But what is the best combination right now of OS, Ext, and radio?
Click to expand...
Click to collapse
OS/Ext ROM: 2.06
Radio 1.34 or 1.27
wpbear said:
Then Run this cooked ROM (Cooked w/Olipro software)
http://uploadingit.com/files/8194/RUU_CINGULAR_2.06.502.3_1.27.00.00_SPL1.04.zip
Rom: 2.06.502.3
Radion version: 1.27
SPL: 1.04
Ext Rom: 2.06.502.3
Click to expand...
Click to collapse
@wpbear
I used the cooked ROM RUU_CINGULAR_2.06.502.3_1.27.00.00_SPL1.04.zip for the upgrade. One question, I have SPL 1.06 before upgrading. Since the cooked ROM has 1.04 in it, I thought it would downgrade to 1.04. Instead, the SPL did not change. Why?
Same result, same question.
Why?
Where can I download this Rom?
Where can I download this Rom?
Download link doesn't work....
anubus12 said:
@wpbear
I used the cooked ROM RUU_CINGULAR_2.06.502.3_1.27.00.00_SPL1.04.zip for the upgrade. One question, I have SPL 1.06 before upgrading. Since the cooked ROM has 1.04 in it, I thought it would downgrade to 1.04. Instead, the SPL did not change. Why?
Click to expand...
Click to collapse
Are you SuperCID with POf unlocker?
SuperCID/unlock yes. POF no.
Wiki and numberous posts indicate if the unit is SuperCID, it is SuperCID period however there is a v2 v2a and v3.
Is there more to SuperCID than just SuperCID?
Sometimes it sticks and sometimes it does not?
Can v3 be run over top of an existing SuperCID/unlocked unit without risk?
True you are either SuperCID or not, but we have seen people loose SuperCID for no apparent reason. Use mtty and check if you are still SuperCID.
Still superCID, still 1.06.
rvc said:
Still superCID, still 1.06.
Click to expand...
Click to collapse
once you have superCID you can downgrade your bootloader by this http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
OK, I've read the wiki and various FAQs on the topic. I am basically looking for confirmation on my plan as I have never done anything like this before. I don't want to see sparks flying out of my 8525 after trying to upgrade.
I have the 1.16 Radio and 1.34 ROM currently and I want to get to 1.34 radio, 2.06 ROM, 3.3 AKU. I think my procedure should be to:
1. perform the CID/SIM unlocker v3 per http://forum.xdadevelopers.com/showthread.php?t=293665
2. Install the latest ROM per:
http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe which should update the ROM and radio.
And I believe all of this is able to be done without downgrading to boot loader 1.04.
Thanks for the help.
pstritt said:
OK, I've read the wiki and various FAQs on the topic. I am basically looking for confirmation on my plan as I have never done anything like this before. I don't want to see sparks flying out of my 8525 after trying to upgrade.
I have the 1.16 Radio and 1.34 ROM currently and I want to get to 1.34 radio, 2.06 ROM, 3.3 AKU. I think my procedure should be to:
1. perform the CID/SIM unlocker v3 per http://forum.xdadevelopers.com/showthread.php?t=293665
2. Install the latest ROM per:
http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe which should update the ROM and radio.
And I believe all of this is able to be done without downgrading to boot loader 1.04.
Thanks for the help.
Click to expand...
Click to collapse
You dont have too SuperCID but I would. That ROM will not downgrade your BL to 1.04. You BL will stay the same or become 1.04 if you happen to have something lower, which I doubt.
wpbear said:
Your BL will stay the same or become 1.04 if you happen to have something lower, which I doubt.
Click to expand...
Click to collapse
Are you saying it won't downgrade the BL regardless of the SuperCID status, or depending on which BL it currently has?
@pstritt: Based on the other info you provided, I'm guessing you must have SPL 1.06. You should be able to flash that ROM without going SuperCID first, as I've done so myself. My SPL remained 1.06 (why it did being contingent upon the answer to the question above).
Really no reason to SuperCID anymore...
Just run the Cingular rom in the wiki as your first step. Second step is to run Oli's 1.10.Oli Bootloader.
So...
1) http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe
2) http://forum.xda-developers.com/showthread.php?t=296722
AND, if you want to be able to edit your ExtRom, see this:
3) http://forum.xda-developers.com/showthread.php?t=297085
Done.
Nothing else needed anymore
LegolasTheElf said:
Really no reason to SuperCID anymore...
Just run the Cingular rom in the wiki as your first step. Second step is to run Oli's 1.10.Oli Bootloader.
So...
1) http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe
2) http://forum.xda-developers.com/showthread.php?t=296722
AND, if you want to be able to edit your ExtRom, see this:
3) http://forum.xda-developers.com/showthread.php?t=297085
Done.
Nothing else needed anymore
Click to expand...
Click to collapse
What if you wanted to go back to an earlier radio, just the radio?
LegolasTheElf said:
Really no reason to SuperCID anymore...
Click to expand...
Click to collapse
Yes, I must agree. Looks like I got my Hermes at just the right time!
PhonePhun said:
What if you wanted to go back to an earlier radio, just the radio?
Click to expand...
Click to collapse
Most of the links for radio only use Des' SSPL, so, SuperCID isn't needed. In fact, you don't even need to worry about having the appropriate BL either as Des' BL uses 1.09 to flash radios, even the 0108...
So, grab the packed RUU and run. Done.
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
LegolasTheElf said:
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
Click to expand...
Click to collapse
Here again, I wholeheartedly agree. Until 1.10.Oli came about the light never went on with me as to the hidden benefits of SuperCID/1.04, despite that fact I had no burning desire to flash cross-CID or "generic" ROMs (...yet!).
Now I understand that it'll give you the ability to manuever in the BL if you happen to hose your radio, etc.
LegolasTheElf said:
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
Click to expand...
Click to collapse
I've been keeping up with that thread, read alot of the wiki, but still can't seem to wrap myself around all the info I've taken in. I think I'm starting to get it some now. All's I've done so far is upgrade my official ROM with AKU 3.3 so now I have bl 1.09 and I'm still not ready to flash with WM6, but in the meantime I do want to upgrade my radio from 1.33 to 1.35 but still have the option to drop back if I wanted to.
PhonePhun said:
I have bl 1.09
Click to expand...
Click to collapse
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE! Unless of course you want to risk a brick?
LegolasTheElf said:
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE! Unless of course you want to risk a brick?
Click to expand...
Click to collapse
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
LegolasTheElf said:
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE!
Click to expand...
Click to collapse
Done deal. Took maybe a minute to load and blam... "SuperCID".
PhonePhun said:
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
Click to expand...
Click to collapse
no, enter the thread, there's only one available; the 1.01 stuff is only available as NB files and you have to know what you're doing to flash those whereas 1.10 is available as an RUU update that you can run on your computer to flash; that's the one you want
PhonePhun said:
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
Click to expand...
Click to collapse
Stick to running the installer (ROMUpgradeUt.exe) to flash the 1.04-based version unless you really know what you're doing. Olipro left his 1.01-based version as .nb's for this very reason.
Show ExtROM Version
Hi, I'm new of the forum, I would want to know how to show the version of the ExtROM in “Device Information” with version 0.20 of XDA Live. Thanks a lot for the answer.
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.
Actually I have already flashed Hard SPL v7 in my device. I have done couple times upgrade (from WM5 to WM6 and changed differenet version of Radio)
But everytime when I run the RUUWrapper.exe, I can't use "autodetect" option, the "next" button doesn't show up and "error" message comes, and ask me to use "force SSPL" instead of "autodetect".
I do click "yes" during the process, when it ask me to allow a file to run on my device.(during click on the "autodetect")
Anyway, using force SSPL method works for me, but I just wondering I fully follow all steps from mrvanx guide already, so what is the problem?
And could anyone tell me what's the difference between follow 3 options:
1. SPL 2.02/2.1 new bootloader
2. Force using SSPL
3. Autodetect
during upgrade process?
Sorry that I post this question, Coz' even I have searched this forum, but still a bit confused abt them.
Appreciated.
with that version of spl auto detect does not work....it is a feature.
check the hard spl forum to find more about it.
faria said:
with that version of spl auto detect does not work....it is a feature.
check the hard spl forum to find more about it.
Click to expand...
Click to collapse
Do u mean if we have flashed hardspl v7 already ,the auto detect will not work?
And must use force SSPL?
Thanks again!
kinghung said:
Do u mean if we have flashed hardspl v7 already ,the auto detect will not work?
And must use force SSPL?
Thanks again!
Click to expand...
Click to collapse
No need,
you could always choose "SPL 2.02/2.1 new bootloader" and check "Is it Hard-SPL?" when you flash a new ROM.
AikonCN said:
No need,
you could always choose "SPL 2.02/2.1 new bootloader" and check "Is it Hard-SPL?" when you flash a new ROM.
Click to expand...
Click to collapse
Thanks, by the way, what is SSPL?
and what if I choose Force SSPL?
Since I have done couple times of upgrades, everytime I choose force using SSPL and this method works.
So I would like to clarify what the difference between them!
kinghung said:
Thanks, by the way, what is SSPL?
and what if I choose Force SSPL?
Since I have done couple times of upgrades, everytime I choose force using SSPL and this method works.
So I would like to clarify what the difference between them!
Click to expand...
Click to collapse
You have to use SSPL When you update a new version Hard-SPL,
Because Hard-SPL can only update by SSPL,
If your new ROM include a SPL but you don't know and you check "Force SSPL" and then your Hard-SPL will be covered with the SPL which include in your new ROM,
It's dangerous for your Hermes to lose Hard-SPL,
That's all.
AikonCN said:
You have to use SSPL When you update a new version Hard-SPL,
Because Hard-SPL can only update by SSPL,
If your new ROM include a SPL but you don't know and you check "Force SSPL" and then your Hard-SPL will be covered with the SPL which include in your new ROM,
It's dangerous for your Hermes to lose Hard-SPL,
That's all.
Click to expand...
Click to collapse
Thanks very much Aikon!
After your explaination and reading lots of articles from web.
I have figured out couple of points, I hope it helps people who are also confused or do not understand what they are doing when flashing radio or ROM.
1. HardSPL v7 could be overwrite when Force using SSPL only. So Force using SSPL only use when u want to flash SPL or new version of HardSPL released. Otherwise, do not use this option
2. Although force using SSPL overwrites IPL/SPL, we do not have IPL/SPL in radio ROM or OS (because we have repackaged the OS). That's why nothing happened even using force using SSPL option
3. Therefore basically after we have HardSPL v7 in our device, we should use "SPL2.02/2.1 new bootloader" and check the "is it hard spl " box everytime when we use RUUWrapper to flash radio or OS ROM
4. That's why using SSPL_HERM.exe method could overwrite SPL, and those people needed to reflash again HardSPL after OS upgrade.
Pls correct me if anything I mislead or wrong.
BTW, I still don't understand why I can't use "Autodetect" option. Since I follow all step from mrvanx guide already.
What I thought is after we have hardspl and using the latest RUUWrapper.exe , everything should be exactly same as what mrvanx guide tells. We should be able to use AUTODETECT instead of "using force SSPL"or "SPL2.02/2.1"
Pls help if anyone knows why!?
Hi kinghung,
I had the same problem and I found out, that you can use "Auto-Detect" when you click first on "is it hard spl". After you activated "is it hard spl" and a click on "Autodetect" you get the right setting marked.
Don't know why it's so, but it works!?
Greets
komodor
kinghung said:
Thanks very much Aikon!
After your explaination and reading lots of articles from web.
I have figured out couple of points, I hope it helps people who are also confused or do not understand what they are doing when flashing radio or ROM.
1. HardSPL v7 could be overwrite when Force using SSPL only. So Force using SSPL only use when u want to flash SPL or new version of HardSPL released. Otherwise, do not use this option
2. Although force using SSPL overwrites IPL/SPL, we do not have IPL/SPL in radio ROM or OS (because we have repackaged the OS). That's why nothing happened even using force using SSPL option
3. Therefore basically after we have HardSPL v7 in our device, we should use "SPL2.02/2.1 new bootloader" and check the "is it hard spl " box everytime when we use RUUWrapper to flash radio or OS ROM
4. That's why using SSPL_HERM.exe method could overwrite SPL, and those people needed to reflash again HardSPL after OS upgrade.
Pls correct me if anything I mislead or wrong.
BTW, I still don't understand why I can't use "Autodetect" option. Since I follow all step from mrvanx guide already.
What I thought is after we have hardspl and using the latest RUUWrapper.exe , everything should be exactly same as what mrvanx guide tells. We should be able to use AUTODETECT instead of "using force SSPL"or "SPL2.02/2.1"
Pls help if anyone knows why!?
Click to expand...
Click to collapse
Yes, your viewpoints from 1 to 4 are right,
I don't know the reason why I can't use "Auto Detect",
I always choose manually.
I have lately found the same issue.
But I checked my device and oli 2.10 was there. So I just went ahead and forced the flash. and all was OK.
Ticking off hard SPL and oli 2.10 also worked fine.
The main thing to do is to ensure that you have oli 2.10 on you device before flashing any RUU file.
komodor86 said:
Hi kinghung,
I had the same problem and I found out, that you can use "Auto-Detect" when you click first on "is it hard spl". After you activated "is it hard spl" and a click on "Autodetect" you get the right setting marked.
Don't know why it's so, but it works!?
Greets
komodor
Click to expand...
Click to collapse
First of all, thanks a lot!
I have just tried your method, but it still doesn't work,the "error" message still comes out and asks me to use force using SSPL.
AikonCN said:
Yes, your viewpoints from 1 to 4 are right,
I don't know the reason why I can't use "Auto Detect",
I always choose manually.
Click to expand...
Click to collapse
Hi Aikom, appreciated!
I still don't understand why the"AUTODECT" doesn't work for me and some other Hermes users.
basilrsa said:
I have lately found the same issue.
But I checked my device and oli 2.10 was there. So I just went ahead and forced the flash. and all was OK.
Ticking off hard SPL and oli 2.10 also worked fine.
The main thing to do is to ensure that you have oli 2.10 on you device before flashing any RUU file.
Click to expand...
Click to collapse
From my understanding, your points are partial correct.
If there is no IPL/SPL inside the ROM u are going to flash, either using force SSPL or pick 2.02/2.1 SPL , both method work and safe!
But if unfortunately someone flashing a ROM with IPL/SPL inside, the current hardSPL would be overwrote if u using force SSPL!!
It's dangerous!
kinghung said:
From my understanding, your points are partial correct.
If there is no IPL/SPL inside the ROM u are going to flash, either using force SSPL or pick 2.02/2.1 SPL , both method work and safe!
But if unfortunately someone flashing a ROM with IPL/SPL inside, the current hardSPL would be overwrote if u using force SSPL!!
It's dangerous!
Click to expand...
Click to collapse
Thanks for your explanation!! Right now I have a much clear concept about flashing!!
And I just notice why the bootloader has changed after I flashed my hermes from WM5 to WM6? Thanks again!!^^
This thread helped me a lot
I was experiencing the same error but thanks to your explanation i could install the rom!!!! Thanks a lot.
kinghung said:
From my understanding, your points are partial correct.
If there is no IPL/SPL inside the ROM u are going to flash, either using force SSPL or pick 2.02/2.1 SPL , both method work and safe!
But if unfortunately someone flashing a ROM with IPL/SPL inside, the current hardSPL would be overwrote if u using force SSPL!!
It's dangerous!
Click to expand...
Click to collapse
That's make much more sense to me.
I had the same problem, chose the "Force" option, and now when I check the bootloader option it says SPL-2.Olipr, meaning it hasn't changed, even though I chose the "Force" option.
Wrong tread - moved
AUTODETECT doesn't work for me too. I have HERM100.
By the way - if I choose "SPL-2.02/2.10 New Bootloader" and tick "Is it Hard-SPL?", after clicking "Next", there is a red text saying that this flasher is intended solely for SPL 1.11 and I must have 1.11 Hard-SPL installed. But I have 2.10... should I ignore this? ;/
mrbabcia said:
AUTODETECT doesn't work for me too. I have HERM100.
Click to expand...
Click to collapse
The same with my HERM300.
If you have correctly checked the options for Bootloader version, then yes, ignore the warning.