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
Related
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.
Hi ,
while I had upgrading only radio to 1.38 the process has interrupted
I had removed the battery and the tytn start but at boot no gms appears instead the radio version then it freezes on windows startup.
I need to reflash the radio firmware but I can do that from active sync.
i have bl 1.04 can anyone help me?
thank you very much
have you install Hard-SPL ?
Ah the curse strikes again... get reading here.... http://forum.xda-developers.com/showthread.php?t=286755
Though post #467 may be of particular interest to you.
sorry for the delay in my response.
i have tried to read all the post about bricked tytn.
Then I have tried to use the kilt methid but my device show a blank screen after the attach. I wait more than 30 minutes after that but without result, so I think this way is not good for me.
Anyway I have use the hard spl 1,10 for the radio upgrade.
I can boot in bootloader spl 1.04 so I hope this a good thing
any ideas?
Thanks
juggero said:
sorry for the delay in my response.
i have tried to read all the post about bricked tytn.
Then I have tried to use the kilt methid but my device show a blank screen after the attach. I wait more than 30 minutes after that but without result, so I think this way is not good for me.
Anyway I have use the hard spl 1,10 for the radio upgrade.
I can boot in bootloader spl 1.04 so I hope this a good thing
any ideas?
Thanks
Click to expand...
Click to collapse
yeah, get a regular RUU for your device, an *official* one and update with it.
if you have SPL 1.10.Oli already flashed on the phone, there is something better we can do... but clearly it sounds like you haven't
Olipro said:
yeah, get a regular RUU for your device, an *official* one and update with it.
Click to expand...
Click to collapse
will not work, 'cos he has SPL 1.04 and htc_boot 0108 (as he was flashing 1.38 radio), so he needs 1.09 to reflash the radio.
I'm closing this thread, as I see juggero has already posted in the right place.
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...
Does anyone experience the same difficulties with the new spl 2.03 like I do?
- I can't use the 'old' upgrade tools anymore. I keep getting an error 260 which is very frustrating as the new upgrade program does actually work, but gives me a CID error. Yep I don't have SuperCID.
- Any custom build rom with all Hermes rom cookers I tried will give me an 'image is corrupt' error when I use the new upgrade tools.
So it seems to me the spl password algorythm has been changed and the hashcalculation for the rom too
Now I'm left to debugging the new upgrade, in which I'm not to good at. Why am I doing this? I broke my Hermes during the upgrade and for warranty I really like to have the origal splash screens showing. Even updating the splash is't possible now. The SD method doesn't work either, apperently (and luckily for not bricking purposes) the bootloader seems to check that image too.
Any help is welcome in this.
Cheers, M
oltp said:
- I can't use the 'old' upgrade tools anymore. I keep getting an error 260 which is very frustrating as the new upgrade program does actually work, but gives me a CID error. Yep I don't have SuperCID.
Click to expand...
Click to collapse
You need to use the new RUU since SPL-1.11. Both old and new RUU are packaged in CustomRUU, which will unpack either one or other depending on the SPL version you have.
oltp said:
- Any custom build rom with all Hermes rom cookers I tried will give me an 'image is corrupt' error when I use the new upgrade tools.
Click to expand...
Click to collapse
You need a patched SPL in order to flash unsigned code. All custom builds are not properly signed with a valid HTC certificate.
oltp said:
So it seems to me the spl password algorythm has been changed and the hashcalculation for the rom too
Click to expand...
Click to collapse
Before the password was dynamic, algorithm explained in the wiki. In SPL versions 1.11 or newer the password is always: BsaD5SeoA
Don't know what you mean by "hashcalculation"... the CRC algorithm is still the same, in all bootloader versions.
oltp said:
I broke my Hermes during the upgrade and for warranty I really like to have the origal splash screens showing. Even updating the splash is't possible now. The SD method doesn't work either, apperently (and luckily for not bricking purposes) the bootloader seems to check that image too.
Click to expand...
Click to collapse
With a non-patched SPL you won't be able to flash anything that is not signed.
If your CID is ok (info 2 bootloader command shows a valid CID), you can unbrick it by flashing a signed (shipped / official) rom matching your device's CID.
If your CID/radio is br0ken (shows "No GSM" when booting), you won't be able to flash anything on it, your only hope is having a KITL enabled OS image.
i have problem i have tmobile vario 2 after trying upgrade the rom to wm6 phone stop on 17% and now is stock on the bootloader mode spl 2.03 and i can to anything i try flashing with difrend wersion of the software and nothing.help
@pof: thanks for your instant reply and pointing me to my black-outs. The password does work, but still the lnbs command gives me back: invalid command. Maybe that's because the device isn't unlocked. Just like to flash the spl 1.01MFG so I can at least try to work my way out of the bricked situation. Since KITL isn't enabled there isn't much hope, I know. I really tried all the wiki solutions.
Guess there are only two options left: repair centre and IMEI-check for JTAG flash.
Anyone knowing an other alternative, pls let me know
Cheers,
M
same problem here.. need help
Hi,
I have a touch dual running 6.1 which I unlocked but installed the incorrect radio back onto so now it doesn't ring.
After unlocking I upgraded sspl 1.16.exe and now have spl 1.16 hard which won't let me install the radio version I need 1.58.16.27 (this version is running on another phone with the same set up but is locked.)
I have seen with on these pages instructions like run uspl then spl1.15 but these don't seem to work for me. I flashed the rom but still have spl 1.16 hard although I am informed that the device is "Test only not for sale" on boot up.
Is there a sure fire way of downgrading or is there a way of reinstalling the correct radio in spl 1.16.
Am I doing something completely wrong. Thanks for any and all information.
b1968 said:
Hi,
I have a touch dual running 6.1 which I unlocked but installed the incorrect radio back onto so now it doesn't ring.
After unlocking I upgraded sspl 1.16.exe and now have spl 1.16 hard which won't let me install the radio version I need 1.58.16.27 (this version is running on another phone with the same set up but is locked.)
I have seen with on these pages instructions like run uspl then spl1.15 but these don't seem to work for me. I flashed the rom but still have spl 1.16 hard although I am informed that the device is "Test only not for sale" on boot up.
Is there a sure fire way of downgrading or is there a way of reinstalling the correct radio in spl 1.16.
Am I doing something completely wrong. Thanks for any and all information.
Click to expand...
Click to collapse
Don't worry buddy, just flash a rom with a radio, or flash another radio and your device will ring again, for Niki roms with radio take a look HERE
Goodluck,
Worked a charm
Thanks for taking the time.
Ben