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...
Related
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
just to dispel the myth;
SPL 1.01MFG Flashing via mtty is NOT faster than using the RUU; HTC do not deliberately slow down the process, that's just bloody stupid; the reason it can take longer is if you include a Radio ROM, because flashing a radio takes sodding ages, but can people please learn that using a proper NBH is a smarter and safer way to flash their Hermes.
I second that. this myth appeared because 1.01MFG was the first bootloader that allowed us to flash unsigned, but it didn't allow to flash a radio. So there was the general "feeling" that signature checking was slowing down the process, but it was not: the slowness is caused by flashing the radio.
True, but from strictly a ROM cooker perspective, its not faster. It takes time to build/run the RUU & when you're testing cooked roms, its just far easier to fire up the sspl 1.01MFG and lnb the new os.nb directly.
I understand safety to be the presence of BL v1.10.Oli at location 50020000.
Consequently, I keep this version flashed and test out cooked ideas (currently I'm working on the ATI video issue so I've been flashing a lot of test roms) using your 1.01MFG sspl bootloader.
Expanding on this, I believe that production cooked ROMs should include your 1.10.Oli SPL bootloader from a safety perspective based on my understanding that the BL is flashed first in the RUU under the control of the 1.09Des SSPL loader. This will guarantee a safety net should something go wrong during the OS and/or Radio flashing portion of the process. I would also imagine that this is why you state that RUU flashing is safer too.
Maybe this should be SOP whenever a new production ROM is released by Operators too: Repackage everything into a sspl that also loads 1.10.Oli. Of course, when HTC takes their inevitable next steps in this "spy vs. spy" battle, all this may be invalidated...
Here's an interesting thought: Your bootloader advancements have actually helped Operators since using this technique should result in far fewer bricks being returned for new devices. Now the question is this: does this cost HTC I wonder? Or to put it differently: who sucks up the cost of a bricked Hermes that is replaced in warranty. Whomever this is is very happy with you Olipro and likely to offer you a job as a top developer . Conversely, whomever sucks up the cost is gonna put a contract out on you....
JK: The fact is this: both have a contract on you b/c you've invalidated CID
When I run the RUU, I'll open the Windows Media Player to play the MP3 files, and the update process will be finished in 2-3 minutes.
I guess my major question is this:
At what time during the RUU flashing process is the bootloader flashed? If its the first thing to be flashed then my points above are valid. If not, then everybody who flashes needs to insure that they have 1.10.Oli in flash before stripping the bl out of any ROM they wish to flash. Perhaps we could begin to go through production ROMs and designate those that have had this done with another column on the Wiki.
Sleuth255 said:
At what time during the RUU flashing process is the bootloader flashed?
Click to expand...
Click to collapse
In the order it is placed on the NBH file, generally IPL & SPL are the first.
Sleuth255 said:
If its the first thing to be flashed then my points above are valid.
Click to expand...
Click to collapse
Yes they are: the HardSPL is flashed but the process continues with the current bootloader on device... but after the flashing process ends (or fails) HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
pof said:
HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
Click to expand...
Click to collapse
But there isn't a 1.09 hardSPl yet, no?
VivaErBetis said:
But there isn't a 1.09 hardSPl yet, no?
Click to expand...
Click to collapse
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
politby said:
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
Click to expand...
Click to collapse
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Olipro said:
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Click to expand...
Click to collapse
that's what I thought. Any forecast on when (if) you'll have one available?
politby said:
that's what I thought. Any forecast on when (if) you'll have one available?
Click to expand...
Click to collapse
no... I mean you either need to have flashed on a Hard-SPL before you buggered it up, or you need to be able to still get into Windows after buggering it
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
VivaErBetis said:
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
Click to expand...
Click to collapse
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Olipro said:
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Click to expand...
Click to collapse
Ok. Fortunately I don't need it ***yet***. Thanks Olipro.
BTW: I got your 1.10 version installed and it works very well. Thanks.
new custom RUU is complete;
ROM Cookers, the good news is that this is now a single file, simply provide it with an NBH and you have compatibility with all SPL versions.
Fifth edition... with detection of all SPL versions, plus a very special selection of two soft-load options, including an "Unsafe" SPL which can be used to flash your device back to any SPL you desire.
5.2 is a small patch to fix an error with the unsafe SSPL not allowing you to overwrite the bootloader
Good Work Olipro One Question When Will It Be Available?
Cheers
fantastic Oli,
Great work, guy! (as usual )
Great works.
ok, Custom RUU is released, enjoy
uhm... minor bug in the old release... replaced
Thanks. You make life a lot easier....
Olipro, I can't flash using your new RUU and Hard 1.11SPL.
I got installed your Hard SPL 1.11. Start the RUU and selected "SPL-1.11 Bootloader" and mark "Is it Hard-SPL?", Everithing goes well but, when it tries to start the upgrade, the machine hibernates and, after some seconds an error 260 appears.
IMHO the RUU can't start the Hard-SPL 1.11.
Any clue?
EDIT: It doesn't leave a RUU.log in C:\ like previous version (?)
Thanks and best regards.
@VivaErBetis: put your phone in bootloader mode manually, then start the upgrade.
@VivaErBetis
Do you realy have SPL 1.11 on your phone? I think it means "Olipro SPL 1.11" is not SPL 1.11.
"Olipro SPL 1.11" can also be "SPL 1.04" and "Is it Hard-SPL"
So you must choose your original SPL and "Is it Hard-SPL".
brmm0016 said:
@VivaErBetis
Do you realy have SPL 1.11 on your phone? I think it means "Olipro SPL 1.11" is not SPL 1.11.
"Olipro SPL 1.11" can also be "SPL 1.04" and "Is it Hard-SPL"
So you must choose your original SPL and "Is it Hard-SPL".
Click to expand...
Click to collapse
no, you're horribly wrong.
1.11.Oli is based on SPL-1.11, 1.10.Oli is based on SPL-1.04
pof said:
@VivaErBetis: put your phone in bootloader mode manually, then start the upgrade.
Click to expand...
Click to collapse
Ok, done and it runs well. Thanks pof.
OK, sorry my mistake.
Now i read a lot of more thread, and the most is clear.
Thanks
ok, Custom RUU 3.5 released, enjoy
Olipro said:
ok, Custom RUU 3.5 released, enjoy
Click to expand...
Click to collapse
Thanks mate! This is how I wanted it
Olipro said:
ok, Custom RUU 3.5 released, enjoy
Click to expand...
Click to collapse
So quickly, thanks.....
Great stuff Oli
So, let me get this straight: just stick an nbh in the same location as this and run yeah?
Genius and simple!
So, do I run this instead of romupgradeut.exe that comes with, for example, the WM6 roms, if I have hard-spl 1.11 installed?
petes said:
So, do I run this instead of romupgradeut.exe that comes with, for example, the WM6 roms, if I have hard-spl 1.11 installed?
Click to expand...
Click to collapse
yes, put it in an empty folder along with the NBH you want to flash, that's all.
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.
well... that current NBH will brick any Hard-SPL device since it will overwrite the IPL. I have 1.50 which I have given to ToddJG; this new version prevents the IPL being overwritten, so as long as you don't flash using SSPL, you would be safe.
is there any actual demand for it?
Oli are you refering to the NBH on "Full WM6 Pro. from Dopod (Test rom)"?
I am using SPL 1.50 Olipro - it works great.
Whether there is demand or not, I think you should disable IPL flashing in the flasher and then (assuming you feel like it) release an expert version (or maybe just an expert mode?) that will allow you to flash IPL. Even that I guess isn't even needed because we could just SSPL an upgraded IPL if we ever need to (right?)
To my (limited) knowledge, there is currently not any real reason to upgrade your IPL and if there are NBH's out there that are going to brick devices, I think it would be best to limit newbies abilitys to brick their devices (which hopefully means less aggrevation for you!)
Package HardSPL-1.50 with IPL-1.03 on a single NBH and publish it
I actually got stuck in BL mode when I tried to flash IPL 1.03 with SPL 1.40.Olipro installed and using Hard-SPL to flash. set 14 0 doesn't work anymore. I had to re-flash the OS to get it to work again.. A real ****ter as I had just finished setting it up nicely and didn't have a backup
Anyways, just to let you know....
I think that bocking IPL flashing would be a good thing. Like it was said earlier I would release it if it could stop users from bricking devices. I have been very happy with your contribution. It has saved me twice now. My little rug rats have pulled out the usb cable on my laptop to pda connection twice. If it had not been for you tool I would have a great paper wieght.
Thanks again.
Erik
LegolasTheElf said:
I actually got stuck in BL mode when I tried to flash IPL 1.03 with SPL 1.40.Olipro installed and using Hard-SPL to flash. set 14 0 doesn't work anymore. I had to re-flash the OS to get it to work again..
Click to expand...
Click to collapse
when this happens, you can just flash a splash screen to get it working again
pof said:
when this happens, you can just flash a splash screen to get it working again
Click to expand...
Click to collapse
Actually, I tried that.. It refused to work. Flashing the OS was the ONLY thing it would do.. It was odd. I tried to flash SPL again, it failed with a communication error. IPL again, the same. Splash screen, ditto. OS worked.
LegolasTheElf said:
Actually, I tried that.. It refused to work. Flashing the OS was the ONLY thing it would do.. It was odd. I tried to flash SPL again, it failed with a communication error. IPL again, the same. Splash screen, ditto. OS worked.
Click to expand...
Click to collapse
OK, A NEW SPL WILL BE RELEASED SHORTLY: SPL-2.10 - BASED ON A NEW HTC SPL, 2.02