flashing radiorom from bootloader - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

pof, whats the address i need to flash a radiorom from bootloader mode?
I collected those from the wiki, but its missing the info for the radiorom.
First Splash:
lnb finalsplash.nb 500e0000
Second splash screen (SubSplash):
lnb finalsplash.nb 50140000
Extrom:
lnb ExtROM.nb 57500000
OS:
lnb OS.nb
ok after enormous searching i've found this:
lnb radio_.nbf 0x80000000
the address is correct, but the file has to be GSM.nb extracted from NBH file, not a .nbf which includes also the NBF header.
And AFAIK no one tried to flash radio using this method yet, you'll be the first if you do it and if it doesn't work you can brick your phone.
If you do it, please report the results
Click to expand...
Click to collapse
okay i have tried it.. it does not brick the phone, but it also doesnt change anything.. radio version remains the same even though it flashes it properly.
USB>lnb gsm.nb 80000000
:F=gsm.nb
:A=80000000
:O=00000000
:L=FFFFFFFF
start NB image downloadS
Load ADDR: 80000000 Length: D80000
H***************************************
****************************************
*****************************Code entry point at 0x80D60000
Click to expand...
Click to collapse
i have updated the wiki with this
USB> task 32
USB> lnb gsm.nb 80000000
USB> task 8,
this seems to flash the radio but the radio version reported by the os remains the same. so this is not working properly
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG

dutty said:
pof, whats the address i need to flash a radiorom from bootloader mode?
I collected those from the wiki, but its missing the info for the radiorom.
First Splash:
lnb finalsplash.nb 500e0000
Second splash screen (SubSplash):
lnb finalsplash.nb 50140000
Extrom:
lnb ExtROM.nb 57500000
OS:
lnb OS.nb
ok after enormous searching i've found this:
okay i have tried it.. it does not brick the phone, but it also doesnt change anything.. radio version remains the same even though it flashes it properly.
i have updated the wiki with this
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Click to expand...
Click to collapse
are you sure it's actually writing a new radio? try flashing a Non-GPS one when you have a GPS (or vice versa) and testing [email protected]

Olipro said:
are you sure it's actually writing a new radio? try flashing a Non-GPS one when you have a GPS (or vice versa) and testing [email protected]
Click to expand...
Click to collapse
yep.. it is downloading and writing the blocks..at least thats what the mtty output tells me... i've tried flashing a non-gps radio and it still reports the gps radio and startgps works.. weird..
the thing for me is i've flashed the 108radio boot loader which prevents me from flashing only radioroms.. so i've tried doing this from the bl..
i think the only possibility that is left for the 108rbl is to create a full os image using typhoonnbf decode (including splashscreens, os and everything else) and then flash this image.

dutty said:
yep.. it is downloading and writing the blocks..at least thats what the mtty output tells me... i've tried flashing a non-gps radio and it still reports the gps radio and startgps works.. weird..
the thing for me is i've flashed the 108radio boot loader which prevents me from flashing only radioroms.. so i've tried doing this from the bl..
i think the only possibility that is left for the 108rbl is to create a full os image using typhoonnbf decode (including splashscreens, os and everything else) and then flash this image.
Click to expand...
Click to collapse
no, not weird... it's just not flashing; now here's a thought; is it possible to rtask, authenticate with the radio then exit out of rtask mode again... perhaps it protects the memory address till you do this

Olipro said:
no, not weird... it's just not flashing; now here's a thought; is it possible to rtask, authenticate with the radio then exit out of rtask mode again... perhaps it protects the memory address till you do this
Click to expand...
Click to collapse
yeah, not weird
btw.. i've also tried to do a radio rom upgrade from an official provider.. tmobile germany released a radiorom only upgrade.. but i couldnt use that to downgrade too..
how do you mean? authenticate? simply entering the radioloader and exiting?
i.e.
rtask a
retuoR
another thought.. what would happen if we just "rerase" the region of the radiorom and then try to reflash.. have to admit i lack the balls to try it
edit: tried the rtask a , rversion, retuoR and then flashing.. but it didn't work

okay.. the last and maybe the best idea is this:
since we can dump parts of the rom using the bootloader how about dumping a radiobootloader < 108 and then "lnb" it into a 109 device..
http://forum.xda-developers.com/showpost.php?p=1092471&postcount=1
i have tried this:
USB> task 32
USB> set 1e 1
USB> rbmc spl 50020000 40000
Click to expand...
Click to collapse
but it doesnt seem to work..
Code:
USB>rbmc spl 50020000 40000
GetExtRomData+(): *pszPathName=spl, dwStartAddress=50020000, dwLength=40000
:F=spl
:A=50020000
:L=00040000
:rbmc=
how can i recieve the file? i have enabled automatic downloads in mtty.. pof?

The radio code is actually flashed into the Qualcomm chipset under the control of the radio bootloader. that's why nbf radio flashing can only be done with bl1.04. In subsequent bootloaders, the required radio bl commands aren't available.
I believe the chipset itself may be mapped into the addresses you mention, but the flashing method is different thus the reason why nothing happens.

Sleuth255 said:
The radio code is actually flashed into the Qualcomm chipset under the control of the radio bootloader. that's why nbf radio flashing can only be done with bl1.04. In subsequent bootloaders, the required radio bl commands aren't available.
I believe the chipset itself may be mapped into the addresses you mention, but the flashing method is different thus the reason why nothing happens.
Click to expand...
Click to collapse
interesting..
but if we're using 1.01mfg and flashing into the mapped/virtual memory area we might be able to overwrite the 1.08 radio bootloader..
according to http://wiki.xda-developers.com/index.php?pagename=HermesMemoryMap
the radiobootloader sits right behind the radio at 0x80100000
i would give it a try but i dont know how i can dump files from the bootloader onto my pc.. rbmc seems to send the file, but mtty doesnt know how to recieve it. i guess i'll have to use usbmonitor?

Or is the bootloader itself in the Qualcomm chipset as well? All the normal bootloader does is transfer control (in bl1.04 with rtask 4 in subsequent bl's using a mechanism that is only revealed during the nbh flashing process) to the radio bootloader. Then data flows....

Sleuth255 said:
Or is the bootloader itself in the Qualcomm chipset as well? All the normal bootloader does is transfer control (in bl1.04 with rtask 4 in subsequent bl's using a mechanism that is only revealed during the nbh flashing process) to the radio bootloader. Then data flows....
Click to expand...
Click to collapse
i don't know. but i know that we need to find a way to deal with rb 108 as it will be packed into any radio rom thats released.
there must be a way to dump and flash it using the bootloader as it gets flashed when updating a radiorom using lnb or maupgrade.
unfortunately i really don't know how to deal with the remote dump command, even with usbmonitor the output is useless, as mtty only recieves a couple of bytes then stops. after terminating the connection and restarting mtty it recieves a couple more bytes and so on and so on..

I think the key here is to figure what goes on during nbh flashing since we know the radio bootloader can be changed then. This also holds the key to simple RUU flashing of cooked roms on the hermes btw. We have to get here too eventually if we ever want to package up a cool GPS enabled hermes rom that even Noobs can install Right now, hermes upgrading is a nightmare....

Sleuth255 said:
I think the key here is to figure what goes on during nbh flashing since we know the radio bootloader can be changed then. This also holds the key to simple RUU flashing of cooked roms on the hermes btw. We have to get here too eventually if we ever want to package up a cool GPS enabled hermes rom that even Noobs can install Right now, hermes upgrading is a nightmare....
Click to expand...
Click to collapse
i'll do a full ruu upgrade now and track the whole thing with usb monitor.. maybe something useful comes out of that

sorry i have been away for the last 2 days.
Radio can't be flashed with lnb, it must be flashed from radio bootloader using rwdata.
Now we can use Des SSPL to flash radios in NBH, so radio bootloader 0108 is not a problem anymore
I will provide a reimplemented flashing tool for hermes in a few days (need two more long nights to finish fixing minor bugs), it allows to dump the radio and do some "extra" stuff... at the moment it only works in linux, but I'm sure some of you will be able to port it to windoze

yep... the holy grail of nbh flashing is possible Des "got 'er done"!

Related

Radio 1.35.00.11

Does anyone know how to upgrade Radio 1.27 to 1.35 without getting BL 1.07 changed to BL 1.08??
There is no way. But then, why do you care what radio BL you have?
I just like having all possibilities of upgrading Hermes components back and forth. I am aware of Des's SSPL tool, but you need to be in Windows Mobile to use it.
However, I saw an interesting post where Izzard-UK managed to burn the OS.nbh from the Micro SD, it is probably possible to do the Radio and ExtrRom using some sort of file that will tell it which location to start Writing.
It looks like soon we will have have cleverer and more powerful tools.
Well, the technique for microSD loading of an nbh image is not new. I would say that if you can get bl 1.01MFG loaded then you're pretty much good to go with the sspl solution.
My Radio 1.35.00.11 upgrade failed with 114 Error and now Hermes starts in Bootloader mode.
What could go wrong and what to do?
I'm now running update again to see if it fails again or not.
I had XDA Live 0.10 + Radio 1.18, Bootloader 1.01 MFG as far as I remember.
@schriss: you need to go into bl with mtty & issue the following commands:
set 14 0
task 8
the first command sets the boot flag from "boot to BL" back to "Boot to OS"
the second command resets your hermes
This is the problem you would see if you were using a .nbf upgrader instead of an sppl upgrader. Bl 1.01MFG is missing commands and causes an abort.
However, sspl executes its own bl which is v1.09.
When you were doing the upgrade, when the RUU put your device in tri-color mode, what bl version was displayed?
Sleuth255 said:
@schriss: you need to go into bl with mtty & issue the following commands:
set 14 0
task 8
the first command sets the boot flag from "boot to BL" back to "Boot to OS"
the second command resets your hermes
This is the problem you would see if you were using a .nbf upgrader instead of an sppl upgrader. Bl 1.01MFG is missing commands and causes an abort.
However, sspl executes its own bl which is v1.09.
When you were doing the upgrade, when the RUU put your device in tri-color mode, what bl version was displayed?
Click to expand...
Click to collapse
I don't remember what was displayed, but you are right, I didn't use sppl upgrader because the link was broken and there was only one upgrade on FTP.
I've taken time and read WiKi and almost started flashing BL 1.04 hoping that it could let me run the upgrade again successfully - would that work?
I'm on mtty now trying your commands...
EDIT: That's the link that didn't work: ftp://xda:[email protected](GPS-Enabled)Trinity2Hermes-SSPL-comp.zip it's on GPS Driver first page.
EDIT2: Set 14 0 command helped, THANKS!
All radio-only links are still in the Wiki. The 1.35.00.11 link is still good there in the shipped radio only upgrades section. I'll check the GPS page & fix... The valid wiki link points to this file.
BL1.04 won't work if your radio is already using bl0108. Best to just use sspl and not worry about it.
Sleuth255 said:
There is no way. But then, why do you care what radio BL you have?
Click to expand...
Click to collapse
You mean even if we flash radio 1.27..00 with the newest 1.35.11 using sspl method, radiobootloader bl0107 will change to bl0108.
if this true why we should upgrade 1.27.00 to 1.35.11 and loose the ability to flash extracted radios in nbf format?
IIRC, you will loose the ability to enter some radio bootloader commands if you go to bl0108 with sspl. OTOH, you will gain the ability to use the latest radio ROMs for your device if you go the sspl route (since they are all bl0108 from 1.27 on). Those are the tradeoffs IMO.
I was in the Wiki looking around for various "task" commands when you are the in bootloader using TTY but I don't see anything outline the list of commands (e.g. task 32, task 8, etc...).
I thought may be there will be specific command to get the version of the Radio Bootloader from TTY.
Nevermind, I needed to dig deeper
I was in the same dilemma whether to use radio v1.27 or v1.35.
After much thinking, I decide to stick to radio v1.27 with HTC boot 0107.
I've done a bit of digging and it seems there really isn't much difference between the radio bootloader commands available in 0108 and 0107. I was mistaken. I was thinking about the Trinity Bootloader that was missing the commands that got you into the Radio bootloader AT interface...
So, bottom line IMO is there is no good reason to stick with an 0107 Radio bootloader. All the most current radios have the 0108 bl and with sspl, it's trivial to switch to any radio you want.
Sleuth,
Since this radio rom is GPS enabled, have you found that it uses more battery power compared to the 1.34 version? Or are the GPS chips always on anyway?
It doesn't use any more power unless an "[email protected]" command is issued to turn on the GPS radio. The only program that can do this on a hermes is superdave's VRSerial driver which you must install seperately.
How is the radio 1.35.00.11 compare with Radio 1.34.00.10??
Will it be better?
Sleuth255 said:
I've done a bit of digging and it seems there really isn't much difference between the radio bootloader commands available in 0108 and 0107. I was mistaken. I was thinking about the Trinity Bootloader that was missing the commands that got you into the Radio bootloader AT interface...
So, bottom line IMO is there is no good reason to stick with an 0107 Radio bootloader. All the most current radios have the 0108 bl and with sspl, it's trivial to switch to any radio you want.
Click to expand...
Click to collapse
my only concern is if the 1.35 rom is not as reliable/stable as the 1.20 rom i am using now, i am unable to go back since there is no SSPL radio for 1.20. The only versions i see in the wiki is 1.27, 1.34, 1.35
I updated my TyTN with the AKU 3.3 full update (OS, ExtROM, Radio 1.34 and the works).
Now I want to upgrade the radio to 1.35, since I have some connection problems, but wasn't it so that you couldn't do radio extracted rom only upgrades due to some reason?
Or can it be done with Des's SSPL bootloader?
[edit]
Never mind, found the answer and now running 1.35 Radio
[/edit]
@joej: its easy enough to make one for yourself from any Full NBH that has that radio. Table in Wiki will tell you which.
Welp, after one day with 1.35 radio I've decided to revert it back to 1.27. I've found that this 1.35 version is even worse than 1.34. The line has dropped (voice) 4-6 times / 1 hour talk.
I drive by car 2h/day the same route so there shouldn't be much difference between the signal quality along the way.

Really safe way to flash Post Dec2nd X01HT!

EDIT (Apr 4th 2007):
The following is OLD info, use pof's unlocker v3a for automatic SIM unlock, reported to work good with Post Dec2nd X01HT...
Read further ONLY if you want ot unlock your phone manually.
NOTE: Radio flashing doesn't seems to work with newest X01HT ("white" or "March batch") because radio-bootloader version had changed! This also means that you can't SIM-unlock this phone version just yet...
* * * MANUAL SIM UNLOCK * * *
Basically it is very safe to flash Hermes phones using Olipro's Hard-SSPL 1.40 bootloader, especially with new devices with 0108 radio-bootloaders, like our precious X01HT! Also, it's time to elaborate this in more details...
WARNING: You are doing this on your own risk!
The procedure for unlocking and flashing:
Prevent bricking. Flash Olipro's Hard-SSPL 1.40!
This is most important step. By doing this you prevent many bricking scenarios!
1a. On new X01HT (or any other working phone), download and run Des's SSPL 1.09. Copy SSPL.exe on the phone or SD card and just run it from phone's file explorer. When you enter bootloader, you'll see 'rainbow' screen and something like "SPL-1.09Des" is displayed.
1b. Download Olipro's Hard-SSPL-V6. Make sure you disabled USB connection in ActiveSync before you continue. Plug your phone in USB port and run RomUpgrade.exe and follow the steps. Also you can choose 'Force SSPL' option in wich case you can skip step 1a, but then you have to keep ActiveSyncce USB connection on. After you finish, phone will reset itself. It you enter bootloader you should see something like "SPL-1.40.Olipro".
SIM unlock. Flashing pof's 1.18 radio only & manual unlock!
2a. Download pof's unlocker v3, NBHTool and CustomRUU_V4. Use NBHTool to extract pof's modified radio (NBH to NB option) from HERM_unlocker_v3.nbh (you will find that file in v3 unlocker archive). After extracting, delete IPL and SPL files, leave only radio. Now use NBHTool again to create signed radio file (NB to NBH), and save it to same folder as RUUWrapper.exe.
2b. Now run RUUWrapper and flash pof's radio. Enter bootloader on the phone, disable USB connection on ActiveSync. Radio should flash in 5-6 minutes and phone will reset.
2c. Insert SIM card other than SoftBank and enter unlock code: 22051978. Now your phone should be unlocked! If you want to stay with SoftBank's ROM, you'll need welcome.exe tweak to prevent idiotic SoftBank's OS SIM lock.
(Optional) Flashing other ROMs and RADIOs.
Use nbhtool and CustomRUU_V4 to upgrade. First extract ROM, ExtROM and radio files you want to flash form Shipped RUUs. If you really want SuperCID (it is not needed anymore because ExtROM can be unlocked other way) you can run pof's v3 unlocker from the phone. I do not advise doing that because it might void your warranty!
It is also wise to flash new radios separately form OS flashing.
Good luck!
I am intrested in your post.
Is it safe to flash 1.01mfg to my 1.09 bootloader?and can i do it with SSPL?
You can flash bootloader 1.01 on CID locked phone ONLY by using SSPL.
Zgembo said:
You can flash bootloader 1.01 on CID locked phone ONLY by using SSPL.
Click to expand...
Click to collapse
Thank you for the reply.you said CID locked,is that mean a phone which did not have superCID?Sorry about the question,because the word:CID lockedis not usually used.Or what you mean is CID unlocked?
And I think your method mainly differ from the other is that you think we should flash the bootloader 1.01 first.And if something goes wrong,we can use the lnb command in bootloader mode to fix it,which bootloader 1.09 have not that command support.
And if you do not superCID your device,how could the OS rom HTC 2.05.255.1 you said ran in x01ht?it is not the right cid...
Am I right?thank you very much.
seems to work...
Zgembo said:
I tried with other SIM card, it works, but I can't determine if I have No-GSM problem, because here in Japan there is no GSM at all...
Click to expand...
Click to collapse
i tried using my brother's sim card from the philippines and it can read it, the Sim Menu appears. i'm still in japan so i can't be sure if i can get a gsm signal when i go to the philippines.
confirm please
can anyone confirm if Zgembo's procedure will work on GSM Networks? it will be a great help!
SSPL
qvik123 said:
And if you do not superCID your device,how could the OS rom HTC 2.05.255.1 you said ran in x01ht?it is not the right cid...
Am I right?thank you very much.
Click to expand...
Click to collapse
that's what SSPL.exe does for us, it allows us to flash any rom we want without worrying about the bootloader version. it makes the upgrader think that the hermes is SuperCID.
@jello_e:
I did not flash HTC 2.05 OS using SSPL, but I was using bootloader 1.01, lnb commands to be precise. I flashed extracted ExtROM and OS ROM from HTC 2.05 ROM, ExtROM first! Here is the log:
Code:
USB>
USB>task 32
Level = 0
USB>lnb 04_ExtROM.nb 57500000
:F=04_ExtROM.nb
:A=57500000
:O=00000000
:L=FFFFFFFF
start NB image downloadS
Load ADDR: 57500000 Length: AAA000
H***************************************
****************************************
*******LAST BLOCK, dwBytesCollected=0x16000
Code entry point at 0x57FA0000
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 491
Storage Total block: 445
Total Bad Block in CE: 0
NeedToEraseBlockStart: 504
Storage format success
USB>lnb 06_OS.nb
:F=06_OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image downloadSH
Load ADDR: 501A0000 Length: 39E4000
***************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
*************************LAST BLOCK, dwBytesCollected=0x1C000
Code entry point at 0x53B80000
Write Nand Success
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 473
Storage Total block: 463
Total Bad Block in CE: 0
NeedToEraseBlockStart: 486
Storage format success
USB>task 8
qvik123 said:
Thank you for the reply.you said CID locked,is that mean a phone which did not have superCID?Sorry about the question,because the word:CID lockedis not usually used.Or what you mean is CID unlocked?
And I think your method mainly differ from the other is that you think we should flash the bootloader 1.01 first.And if something goes wrong,we can use the lnb command in bootloader mode to fix it,which bootloader 1.09 have not that command support.
And if you do not superCID your device,how could the OS rom HTC 2.05.255.1 you said ran in x01ht?it is not the right cid...
Am I right?thank you very much.
Click to expand...
Click to collapse
Bootloader 1.01 allows us to flash any ROM, no previous SuperCID unlocking is necessary... But to get 1.01 bootloader you need "virtual" SuperCID status, and we can accomplish that using SSPL...
Zgembo said:
:
Bootloader 1.01 allows us to flash any ROM, no previous SuperCID unlocking is necessary... But to get 1.01 bootloader you need "virtual" SuperCID status, and we can accomplish that using SSPL...
Click to expand...
Click to collapse
Thank you for the reply.I just successfully flashed 1.01mfg with sspl.Then I pressed OK & PWR to activate it,it shows
HERM200
IPL-1.01
HERM200 MFG
SPL-1.01
on device,and when I use mtty to test,here is the result
USB>
USB>task 32
Level = FF
USB>info 2
HTCSVODAK801彌?HTCEUSB>
USB>lnb
Command error !!!
USB>
so I guess I still can not flash a os rom by using 1.01mfg,
But to get 1.01 bootloader you need "virtual" SuperCID status, and we can accomplish that using SSPL..., do you mean I still need to run sspl to flash ext rom and os rom?How do sspl create a virtual SuperCID for 1.01mfg?
And,I still had not flashed the customed radio,will that a reason for the command response above instead of level = 0 like you?
Thank you!
please elaborate
Zgembo said:
Ok, I made some minor risk and tried to flash my Post Dec2nd X01HT in a non-standard way. Here is the procedure or what I've done:
0. PREPARED by Hard-reseting Hermes, and not allowing Extended ROM to run. (Soft reset right after hard reset, when "Customizing device..." started)
1. Run SSPL-HERM from the phone http://forum.xda-developers.com/showthread.php?t=293651
2. Flashed Hermes bootloader 1.01 http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
3. Restart Hermes and used SSPL-HERM again to flash pof's custom radio 1.18 manually (run RUU/ROMUpgradeUt.exe) http://pof.eslack.org/hermes-unlocker/
4. Restart Hermes and flash HTC 2.05.255.1 Shipped Extended ROM and OS ROM using bootloader 1.01 ONLY! (I flashed Extended ROM first, and then, without restarting, OS ROM) http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
5. Inserted non-SoftBank SIM and restarted. Input manually SIM unlock code: 22051978
That's it. I only tried with 2.05 HTC test ROM but there is no reason for this procedure not to work with other ROMs...
I tried with other SIM card, it works, but I can't determine if I have No-GSM problem, because here in Japan there is no GSM at all...
Good luck!
Click to expand...
Click to collapse
Zgembo, thanks for this new technique! More will appreciate it if you elaborate on the steps a little bit more. This is the stuff most of us in Japan are waiting for. I hope Pof comments on this thread as most people trust his opinions, and if the Masters here, including Zgembo, could back these steps up and confirm then we'll have a happier Hermes world!
superCID
@Zgembo:hmmm i think this is a little off topic but i was trying to follow your procedure step by step but before going to step no 1, i tried info 2 using mtty and it says my device is SuperCID. maybe the SuperCID option in pof's unlocker v3 did stick.
note:
- i was on HTC 1.35 rom from S.Africa... (locked 1.09 X01HT)
- used pof's unlocker v3, successfully unlocked and SuperCID'ed.
- re-Flashed Softbank ROM bl 1.09 using SD Card.
jello_e said:
Zgembo, thanks for this new technique! More will appreciate it if you elaborate on the steps a little bit more. This is the stuff most of us in Japan are waiting for. I hope Pof comments on this thread as most people trust his opinions, and if the Masters here, including Zgembo, could back these steps up and confirm then we'll have a happier Hermes world!
Click to expand...
Click to collapse
I have the same idea,thank a lot for this.And waiting further comments from senior profs.This is really a SAFE way to flash X01HT,and even other phones.
Finally I successfully flashed WM6 XDA live os rom with this method.Here is the mtty log and hope it will be helpful for the others.
Note the 02_OS.nb is the file which extracted from the xda-live 0.10 rom.
Code:
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 491
Storage Total block: 445
Total Bad Block in CE: 0
NeedToEraseBlockStart: 504
Storage format success
USB>lnb 02_OS.nb
:F=02_OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image downloadS
Load ADDR: 501A0000 Length: 43CB000
H***************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
****************************************
************************LAST BLOCK, dwBytesCollected=0x15000
Code entry point at 0x54560000
Write Nand Success
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 534
Storage Total block: 402
Total Bad Block in CE: 0
NeedToEraseBlockStart: 547
Storage format success
USB>task 8
qvik123 said:
Thank you for the reply.I just successfully flashed 1.01mfg with sspl.Then I pressed OK & PWR to activate it,it shows
HERM200
IPL-1.01
HERM200 MFG
SPL-1.01
on device,and when I use mtty to test,here is the result
USB>
USB>task 32
Level = FF
USB>info 2
HTCSVODAK801彌?HTCEUSB>
USB>lnb
Command error !!!
USB>
so I guess I still can not flash a os rom by using 1.01mfg,
But to get 1.01 bootloader you need "virtual" SuperCID status, and we can accomplish that using SSPL..., do you mean I still need to run sspl to flash ext rom and os rom?How do sspl create a virtual SuperCID for 1.01mfg?
And,I still had not flashed the customed radio,will that a reason for the command response above instead of level = 0 like you?
Thank you!
Click to expand...
Click to collapse
It seems you should had flashed pof's unlocker radio prior to flashing from bootloader 1.01... Anybody to confirm this?
jello_e said:
Zgembo, thanks for this new technique! More will appreciate it if you elaborate on the steps a little bit more. This is the stuff most of us in Japan are waiting for. I hope Pof comments on this thread as most people trust his opinions, and if the Masters here, including Zgembo, could back these steps up and confirm then we'll have a happier Hermes world!
Click to expand...
Click to collapse
I will elaborate in details later... I understand it could be language problem for japanese users too, unfortunately my Japanese is not good enough to provide detailed info... Someone could help?
Zgembo said:
It seems you should had flashed pof's unlocker radio prior to flashing from bootloader 1.01... Anybody to confirm this?
Click to expand...
Click to collapse
Yes that is right.Finally,I flashed the pof's radio and then the radio level becomes 0 and I can use lnb as well.
i think as long as you have the hermimg.nbh and an sd card, you can always recover from the "No GSM" or "stuck on bootloader/white screen" error.
i did a do or die thing with my hermes and i think the risk paid off...
i flashed the HTC 2.05.255.1 test rom after using pof's unlocker v3 and i never had the "no GSM" error.
popped in a Docomo sim and it works...
popped in a GSM sim and the STK Menu appeared, sim manager can read the sim card... although i have no way of testing the GSM signal. the phone doesn't reject the simcard it just simply says "No Service" which is an obvious fact. now all i have to do now is go back home to the philippines and test if GSM works... or if a good soul can do what i did and is in a GSM country now, a confirmation would be nice.
wooohoooo
qvik123 said:
I have the same idea,thank a lot for this.And waiting further comments from senior profs.This is really a SAFE way to flash X01HT,and even other phones.
Click to expand...
Click to collapse
not just a SAFE way to flash but a SAFE way to Unlock our darn S-ftbank phones.
how does the X01HT react to the XDA Live rom? any bugs so far?
jello_e said:
not just a SAFE way to flash but a SAFE way to Unlock our darn S-ftbank phones.
how does the X01HT react to the XDA Live rom? any bugs so far?
Click to expand...
Click to collapse
The only "bug" I have is when the screen is locked sometimes the soft buttons dont change to "unlock"
Also, no way to access flat-rate after April 1st.
same old prob...
jokinawa said:
Also, no way to access flat-rate after April 1st.
Click to expand...
Click to collapse
same old problem huh... i can't believe softbank... really... off topic, but hell, it is so frustrating!!!

Hard-SPL, Or How to Not Brick Your PDA Ever Again And Fix Bad Blocks!

OK, well... I'd like to introduce Hard-SPL; available in 3 flavours:
SPL 2.10 based on 2.02 will be released shortly at £5 per person... only kidding... it's free, and out now, but do consider a donation
1) 2.10 - Hard-SPL-V7 - see Changelog for further details
(at the bottom)
2) 1.10 - Olipro SPL - based on 1.04 and unlocked - use for rtask commands.
View attachment Hard-SPL.zip
3) 1.01 - Olipro MFG - based on 1.01, and really for testing only.
View attachment Spl-Olipro-MFG.zip
TO FLASH THE NEW Hard-SPL, Select Force-SPL, you should only choose otherwise when recovering your device from an old Hard-SPL version!
RUU now forces SSPL every time... do not use this RUU for anything else.
For older CustomRUU users; pick the 1.40 option, autodetect will not work... or download and use the new CustomRUU
1.01 is provided as SSPL and SPL; SPL is intended for flashing, SSPL is intended to be loaded by SSPL, neither of these are packaged as an NBH since if you intend to play with it, you should know how to make your own package for it.
Bad Blocks SPL Available! - Hard-SPL-V6.zip - fixed RUU bug for those using 1.11/1.13/1.30
Code:
[b]CURRENT FEATURES[/b]
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.10.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
[b]ChangeLog[/b]
[b]Hard-SPL-2.10[/b]
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
[b]Hard-SPL-1.40[/b]
-repairs a bug that affected SPL being replaced by retail ones.
[b]Hard-SPL-1.35[/b]
-addresses an issue for those with Real Bad Blocks to prevent whitescreens.
[b]Hard-SPL-1.30[/b]
- removed password for wdata commands and rbmc etc.
- activated "task 2a" to allow recovering bad blocks as well as flashing valid OS.
- Disabled SPL flashing; this SPL protects you from writing over it by accident.
- Bad Blocks "info 8" command works now allowing you to check for bad blocks.
[b]Hard-SPL-1.13[/b]
- Patched NAND check; bad NAND ignored, valid OS can be flashed to recover bad blocks.
[b]Hard-SPL-1.11[/b]
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
[b]Hard-SPL-1.10[/b]
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
Looking for other SPL Files? scroll back up! they're at the top underneath each version heading!
please remember that 1.35 and 1.40 are the same as 1.30, so when using CustomRUU, either select that, or download the NEW customRUU and overwrite.
Olipro said:
ROM's not available yet; I'm sending them to pof for testing before anybody is allowed to flash this... there's still a chance you could brick your phone
Click to expand...
Click to collapse
great stuff... i'll report in a while
Damn... a lot of people are sure gonna like this! How about doing 1.01MFG too so we can still flash os.nb in < 5 mins with lnb?
Sleuth255 said:
Damn... a lot of people are sure gonna like this! How about doing 1.01MFG too so we can still flash os.nb in < 5 mins with lnb?
Click to expand...
Click to collapse
if someone sent me it as a .nb then certainly... a proper nb... unsigned.
Current Status: Pof has successfully flashed his device, unsigned ROM seems to be flashing fine, if all is well, then I'll get a package ready within the next 10 minutes.
man it works!! That's the safest thing to put on an hermes
Thanks Olipro
Fantastic work! This will definitely be a big help to everyone.
not to sound stupid or anything, but what does this enable your phone to do exactly??
Its the holy grail of hermes flashing! As long as there's no bad blocks in NAND, bricking due to corrupted CID can now be now be avoided.
Olipro said:
if someone sent me it as a .nb then certainly... a proper nb... unsigned.
Click to expand...
Click to collapse
only 1.01MFG I've ever seen is .nbs
koolhand79 said:
not to sound stupid or anything, but what does this enable your phone to do exactly??
Click to expand...
Click to collapse
Same features as SSPL, but flashed on the phone and with bootloader version 1.04 (hex edited to be shown as 1.10.Oli), that is:
Ability to bypass signature in NBH files (friendly for cooked roms)
Ability to access radio bootloader (no more corrupted CID bricks)
Shows itself as SuperCID when doing a rom upgrade (but it internally isn't)
Can be uninstalled by just reflashing a shipped SPL, so no warranty is lost
Sleuth255 said:
only 1.01MFG I've ever seen is .nbs
Click to expand...
Click to collapse
yeah, but it's just the .nb with the NBH headers on... I'm a lazy sod and was hoping someone had already made it an nb to save me the time
also... in a few seconds, a flash package for my SPL will be available!
When? When? When? Waiting... Yahooo. Good news to us all as cooking and flashing going to be as safe as possible.
Okay it is my time to sound like a moron.
Alright I get the general idea of what this does, not could someone point, no need to show the link, just mention where in the documentation I can find more real info on this.
Probably Des or Olipro can answer that:
Can we also patch the SPL to always write 0xFF on the "disastrous 517th byte" of each physical NAND page? (or not overwrite the existing value, whichever is better), this way even when the flashed OS.nb contains a value != than 0xFF on that byte, will not produce a bad block and this would make flashing cooked images _really_ fool proof.
For those willing to go deeply, read Des comment here.
pof said:
Same features as SSPL, but flashed on the phone and with bootloader version 1.04 (hex edited to be shown as 1.10.Oli), that is:
Ability to bypass signature in NBH files (friendly for cooked roms)
Ability to access radio bootloader (no more corrupted CID bricks)
Shows itself as SuperCID when doing a rom upgrade (but it internally isn't)
Can be uninstalled by just reflashing a shipped SPL, so no warranty is lost
Click to expand...
Click to collapse
Not that there's a heck of a lot of reason for doing it any more but does that mean we can now downgrade radio bl versions? Also will it help recover from bad bootloader flashes? I am constantly in awe of the brilliant people in this forum!
chymmylt said:
does that mean we can now downgrade radio bl versions?
Click to expand...
Click to collapse
No, if you have 0108, will keep 0108.
chymmylt said:
Also will it help recover from bad bootloader flashes?
Click to expand...
Click to collapse
No... a bad flash in bootloader means a bricked device, but this is not common on hermes, the most common is bad flash in radio which can only be fixed if the bootloader is 1.04 or the rom has KITL enabled.
pof said:
No, if you have 0108, will keep 0108.
No... a bad flash in bootloader means a bricked device, but this is not common on hermes, the most common is bad flash in radio which can only be fixed if the bootloader is 1.04 or the rom has KITL enabled.
Click to expand...
Click to collapse
that means you've overwritten the bootloader I have made... so obviously not.
however, the bootloader does have built-in recovery functions (HTC's work) and generally you need to be doing something funky to bugger the SPL up.
pof said:
No, if you have 0108, will keep 0108.
No... a bad flash in bootloader means a bricked device, but this is not common on hermes, the most common is bad flash in radio which can only be fixed if the bootloader is 1.04 or the rom has KITL enabled.
Click to expand...
Click to collapse
Still very exciting! Y'all da man! (Men?)
Thanks again!
For those with 1.01MFG or 1.04 SuperCID, will this new BL give any new benefits? I understand those with 1.09 will benefit, but, is it worth flashing if I already have 1.01MFG on the device?
with this will i be able to upgrade and downgrade to any radio i want regardless of nbh or nbf, since no one is answering me in the thread i created about this. lol

Hermes SPL-1.11

The new AKU3.3 htc rom installs SPL-1.11 on your hermes.
This SPL has "Common Base Version : 1.51d" and some of the bootloader commands have changed, this is now more similar to Trinity bootloader.
The prompt is now shown as "Cmd>" instead of "USB>".
New commands:
getdevinfo - shows "Get CID Ok" and modelID encapsulated in HTCS + HTCE.
ResetDevice - resets the device
progress - shows a progress bar
wdata - now flashes NBH files (instead of wdatah)
password - now takes "BsaD5Se0A" as static password (info 3 and old method still works)
There's not much to worry as if you flash it on your device, it can be easily downgraded using SSPL.
It probably has other things we don't know yet, so if you find anything interesting about it, please post it here
Some new notes:
- The new RUU compatible with SPL-1.11 does a 'task 28' after flashing a NBH file, even if the NBH file doesn't contain OS. This hard-resets the device every time you use this RUU with 1.11 SPL.
- 'shmsg' command no longer exists.
pof said:
Some new notes:
- The new RUU compatible with SPL-1.11 does a 'task 28' after flashing a NBH file, even if the NBH file doesn't contain OS. This hard-resets the device every time you use this RUU with 1.11 SPL.
- 'shmsg' command no longer exists.
Click to expand...
Click to collapse
Okay then the best SPL is the 1.09, with this we can upgrade the radio and still keep all our settings.
Thanx for the info!
No, the best is 1.11 with a hacked RUU that doesn't send the 'task 28' , so you can update the radio in 10 min instead of 20
pof said:
No, the best is 1.11 with a hacked RUU that doesn't send the 'task 28' , so you can update the radio in 10 min instead of 20
Click to expand...
Click to collapse
You mean the ModifiedRUUUpdater-V2.rar from the Wiki?
Regards,
Primoz
Pc78 said:
You mean the ModifiedRUUUpdater-V2.rar from the Wiki?
Click to expand...
Click to collapse
No, this RUU is only compatible with SPL <=1.09.
I mean the RUU found in RUUInside.exe on the new AKU 3.3 rom from HTC.
Olipro integrated both old & new RUUs, making it compatible with all bootloader versions on Custom RUU V3, but it has yet to be modified to avoid the 'task 28' command after flashing a NBH. We still have to check if this will have any impact when flashing OS and not formating NAND after.
I'm planning to implement support for 1.11 on HERMflasher too.
pof said:
No, the best is 1.11 with a hacked RUU that doesn't send the 'task 28' , so you can update the radio in 10 min instead of 20
Click to expand...
Click to collapse
We'll, if there's no negatives with this method then that's got to be the way forward. How come 1.11 can flash twice as quickly? Is it just optimisation?
pof said:
Some new notes:
- The new RUU compatible with SPL-1.11 does a 'task 28' after flashing a NBH file, even if the NBH file doesn't contain OS. This hard-resets the device every time you use this RUU with 1.11 SPL.
- 'shmsg' command no longer exists.
Click to expand...
Click to collapse
As I assume this mean that avter ONLY Radio ROM upgrade follows a hard reset...so the settings and the APPS on the device is gone? I have installed the Hard-SPL 1.11Oli and now I want to upgrade the OS ROM only...that means I need a new RUU or the one with SSPL will be ok?
Regards,
Primoz
randomelements said:
How come 1.11 can flash twice as quickly? Is it just optimisation?
Click to expand...
Click to collapse
No idea
Pc78 said:
As I assume this mean that after ONLY Radio ROM upgrade follows a hard reset...
Click to expand...
Click to collapse
Yes... but it's the newer RUU version which does it, so it's easy to avoid it.
Pc78 said:
I have installed the Hard-SPL 1.11Oli and now I want to upgrade the OS ROM only...that means I need a new RUU or the one with SSPL will be ok?
Click to expand...
Click to collapse
The one pushing SSPL is OK if you start upgrade from OS with activesync enabled.
Tried Oli's 1.11 bootloader today and it is really fester. Radio flashes in less than 5 min! Also, you can flash any radio to radio-bootloader 0108 phones...
It is true that task 28 is executed after any flash, even if you only flash the splash screen. Needs to be fixed.
Zgembo said:
Tried Oli's 1.11 bootloader today and it is really fester. Radio flashes in less than 5 min! Also, you can flash any radio to radio-bootloader 0108 phones...
It is true that task 28 is executed after any flash, even if you only flash the splash screen. Needs to be fixed.
Click to expand...
Click to collapse
it is, I've patched the RUU and pof will test it... hopefully it works fine but it might cause issues if you are flashing a proper OS ROM, so I might have to implement a checker in my RUU in case 2 versions of RUU are needed.
Zgembo said:
Tried Oli's 1.11 bootloader today and it is really fester. Radio flashes in less than 5 min! Also, you can flash any radio to radio-bootloader 0108 phones...
It is true that task 28 is executed after any flash, even if you only flash the splash screen. Needs to be fixed.
Click to expand...
Click to collapse
Yes, very quick flashing but the hard reset issue is really a bad thing
Does SPL-1.11 restore/change the "boot screen", I'm stuck with the "Bring back the ROM archive" on my boot screen and I hate it, SPL-1.10 Oli didn't bring back the standard boot screen..
Zulee said:
Does SPL-1.11 restore/change the "boot screen", I'm stuck with the "Bring back the ROM archive" on my boot screen and I hate it, SPL-1.10 Oli didn't bring back the standard boot screen..
Click to expand...
Click to collapse
the SPL is the bootloader... not the bootscreen, flash your own splash screen from whatever ROM you like, it's nothing to do with me.
Olipro said:
the SPL is the bootloader... not the bootscreen, flash your own splash screen from whatever ROM you like, it's nothing to do with me.
Click to expand...
Click to collapse
Sorry, I thought that the boot screen could be changed by flashing a bootloader that did in fact contain a boot screen (I thought that some did and some didn't implement boot screens)..
Hello.
Is there ANYWAY to get this spl 1.11 WITHOUT having to do this flash? I did it and STILL can't get the actual rom I want flashed to work. It keeps saying something about it not being able to open the utility or something. And not only that, on top of that, the device won't read any of my sd nor sdhc micro cards. I even tried formatting my 8gb which had a tom tom navi program on it for install and lost all of that info for nothing. Please help.
You can't use an sdhc card to flash an os. You need a 2gb or less sd card. Once an os is on it may be able to read the sdhc card through the software but we couldn't get sdhc cards (or if we could they were too expensive) when the Hermes was released so they didn't bother allowing the bootloader to recognise this.... Unfortunately you wiped tomtom needlessly...
You can put back on though.
You also need Hard SPL ver7 to flash from the sd card.
Cheers...

My Downgrade plan. Looking for input from the pros

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.

Categories

Resources