SPL Myths - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

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.

Related

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

ROM Upgrade Question

OK, I've read the wiki and various FAQs on the topic. I am basically looking for confirmation on my plan as I have never done anything like this before. I don't want to see sparks flying out of my 8525 after trying to upgrade.
I have the 1.16 Radio and 1.34 ROM currently and I want to get to 1.34 radio, 2.06 ROM, 3.3 AKU. I think my procedure should be to:
1. perform the CID/SIM unlocker v3 per http://forum.xdadevelopers.com/showthread.php?t=293665
2. Install the latest ROM per:
http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe which should update the ROM and radio.
And I believe all of this is able to be done without downgrading to boot loader 1.04.
Thanks for the help.
pstritt said:
OK, I've read the wiki and various FAQs on the topic. I am basically looking for confirmation on my plan as I have never done anything like this before. I don't want to see sparks flying out of my 8525 after trying to upgrade.
I have the 1.16 Radio and 1.34 ROM currently and I want to get to 1.34 radio, 2.06 ROM, 3.3 AKU. I think my procedure should be to:
1. perform the CID/SIM unlocker v3 per http://forum.xdadevelopers.com/showthread.php?t=293665
2. Install the latest ROM per:
http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe which should update the ROM and radio.
And I believe all of this is able to be done without downgrading to boot loader 1.04.
Thanks for the help.
Click to expand...
Click to collapse
You dont have too SuperCID but I would. That ROM will not downgrade your BL to 1.04. You BL will stay the same or become 1.04 if you happen to have something lower, which I doubt.
wpbear said:
Your BL will stay the same or become 1.04 if you happen to have something lower, which I doubt.
Click to expand...
Click to collapse
Are you saying it won't downgrade the BL regardless of the SuperCID status, or depending on which BL it currently has?
@pstritt: Based on the other info you provided, I'm guessing you must have SPL 1.06. You should be able to flash that ROM without going SuperCID first, as I've done so myself. My SPL remained 1.06 (why it did being contingent upon the answer to the question above).
Really no reason to SuperCID anymore...
Just run the Cingular rom in the wiki as your first step. Second step is to run Oli's 1.10.Oli Bootloader.
So...
1) http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe
2) http://forum.xda-developers.com/showthread.php?t=296722
AND, if you want to be able to edit your ExtRom, see this:
3) http://forum.xda-developers.com/showthread.php?t=297085
Done.
Nothing else needed anymore
LegolasTheElf said:
Really no reason to SuperCID anymore...
Just run the Cingular rom in the wiki as your first step. Second step is to run Oli's 1.10.Oli Bootloader.
So...
1) http://rapidshare.com/files/18315008/RUU_HER_CINGULAR_2.06.502.3_1.34.00.10_SPL1.04.exe
2) http://forum.xda-developers.com/showthread.php?t=296722
AND, if you want to be able to edit your ExtRom, see this:
3) http://forum.xda-developers.com/showthread.php?t=297085
Done.
Nothing else needed anymore
Click to expand...
Click to collapse
What if you wanted to go back to an earlier radio, just the radio?
LegolasTheElf said:
Really no reason to SuperCID anymore...
Click to expand...
Click to collapse
Yes, I must agree. Looks like I got my Hermes at just the right time!
PhonePhun said:
What if you wanted to go back to an earlier radio, just the radio?
Click to expand...
Click to collapse
Most of the links for radio only use Des' SSPL, so, SuperCID isn't needed. In fact, you don't even need to worry about having the appropriate BL either as Des' BL uses 1.09 to flash radios, even the 0108...
So, grab the packed RUU and run. Done.
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
LegolasTheElf said:
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
Click to expand...
Click to collapse
Here again, I wholeheartedly agree. Until 1.10.Oli came about the light never went on with me as to the hidden benefits of SuperCID/1.04, despite that fact I had no burning desire to flash cross-CID or "generic" ROMs (...yet!).
Now I understand that it'll give you the ability to manuever in the BL if you happen to hose your radio, etc.
LegolasTheElf said:
If you aren't SuperCIDing your device, you **REALLY** should install the Oli BL; reason is that if there is a bad radio flash, it will save you in a VERY big way! Highly recommended to do it before you start mucking around too much with radios/os/etc...
Click to expand...
Click to collapse
I've been keeping up with that thread, read alot of the wiki, but still can't seem to wrap myself around all the info I've taken in. I think I'm starting to get it some now. All's I've done so far is upgrade my official ROM with AKU 3.3 so now I have bl 1.09 and I'm still not ready to flash with WM6, but in the meantime I do want to upgrade my radio from 1.33 to 1.35 but still have the option to drop back if I wanted to.
PhonePhun said:
I have bl 1.09
Click to expand...
Click to collapse
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE! Unless of course you want to risk a brick?
LegolasTheElf said:
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE! Unless of course you want to risk a brick?
Click to expand...
Click to collapse
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
LegolasTheElf said:
Install Oli's BootLoader BEFORE YOU DO ANYTHING ELSE!
Click to expand...
Click to collapse
Done deal. Took maybe a minute to load and blam... "SuperCID".
PhonePhun said:
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
Click to expand...
Click to collapse
no, enter the thread, there's only one available; the 1.01 stuff is only available as NB files and you have to know what you're doing to flash those whereas 1.10 is available as an RUU update that you can run on your computer to flash; that's the one you want
PhonePhun said:
Definitly don't want to brick it. Thanks for the advice, anything else I should know? Do I use Oli's BL in your sig, since there are 2 available?
Click to expand...
Click to collapse
Stick to running the installer (ROMUpgradeUt.exe) to flash the 1.04-based version unless you really know what you're doing. Olipro left his 1.01-based version as .nb's for this very reason.
Show ExtROM Version
Hi, I'm new of the forum, I would want to know how to show the version of the ExtROM in “Device Information” with version 0.20 of XDA Live. Thanks a lot for the answer.

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.

Wiki states instrux for 1.06 but not 1.04 bootloader

My bro has a Titan and is thinking about having me upgrade but I saw that his bootloader version states 1.04 not the 1.06 that mine was when I flashed (and also the one that the wiki says too). Is the process the same? Should I just use unlocker then upgrade to 2.40 then install radio then DCD? A little wary as it is not my phone. Please be specific when answering. I am planning to do the most recent radio and rom.
serfboreds said:
My bro has a Titan and is thinking about having me upgrade but I saw that his bootloader version states 1.04 not the 1.06 that mine was when I flashed (and also the one that the wiki says too). Is the process the same? Should I just use unlocker then upgrade to 2.40 then install radio then DCD? A little wary as it is not my phone. Please be specific when answering. I am planning to do the most recent radio and rom.
Click to expand...
Click to collapse
In order to flash a dcd rom you need 2.40...Go through the same process you would in order to flash a 3.1.x rom.
prepsssuck said:
In order to flash a dcd rom you need 2.40...Go through the same process you would in order to flash a 3.1.x rom.
Click to expand...
Click to collapse
So it still needs unlocker then 2.40 right? or is unlocker unnecessary now?
Who is his carrier? As forthe bootloader question, I'd be asking Ollipro... I've not seen a bootloader 1.04....
azclown said:
Who is his carrier? As forthe bootloader question, I'd be asking Ollipro... I've not seen a bootloader 1.04....
Click to expand...
Click to collapse
bootloader 1.04 is the "stock" verizon bootloader you should still update to the 2.40 if you plan on having any 3.xx.xx radio's
Just to clarify...
When the phone ships it comes with SPL-1.04 which is the stock bootloader, which is why it doesn't say Olipro.
1.06 is also a "stock" bootloader provided by Olipro which allows you to flash stock roms/radios.
Edit: WINGS 1 - PENS 0!!!!!!
gcincotta said:
Just to clarify...
When the phone ships it comes with SPL-1.04 which is the stock bootloader, which is why it doesn't say Olipro.
1.06 is also a "stock" bootloader provided by Olipro which allows you to flash stock roms/radios.
Edit: WINGS 1 - PENS 0!!!!!!
Click to expand...
Click to collapse
Thanks, I have been flashing since the time you needed the old Olipro to flash the radio and when my brother once before flashed going straight to 2.40 it caused problems. I haven't had a new phone since then and wondered if the unlocker was still necessary. I am gathering that it is not and that you can go straight to 2.40, am I correct?
mogul with slight crack along the frame of screen
i've been reading for a while, and someone wrote that it doesn't matter about the bootloader when returning the phone to the store as long as you have the stock rom. i'm using the newer stock rom (3.35), though i did use the unlocker to put olipro 2.40 on it a while ago to mess with other roms.
the work order for the replacement mogul is already in and it (the new or refurbed mogul) should arrive tomorrow or the next day. should i go through the trouble of putting the stock bootloader on there if i already have the newer stock rom from htc/sprint on my phone?
also, i read that sprint has no warranty (or it's only 30 days). i use total equipment protection for $7 per month (which is how i'm getting a new or refurb mogul because of a case fracture). i'm using the newer stock sprint rom (with gps) and my bootloader says olipro 2.40.
does anyone think that i should be worried if i don't do anything before the new one arrives and just give them the cracked one?
i clearly didn't read the terms and conditions closely enough to find anything that tells me not to modify the bootloader or really ANYTHING about the bootloader...is total equipment protection a warranty that i could possibly void by putting olipro 2.40 on it even with the sprint official 3.35 installed?
I wouldn't worry about it. 1.06 is not the official stock bootloader either, 1.04 is, and I've swapped out my xv6800 a couple times with 1.06 on it and the Verizon stock rom. They don't usually check the bootloader. Just make sure the new Sprint stock rom is on there with radio 3.35.04 and you should be fine.
thanks much for your quick reply. i'll rest easier tonight.

Successful Relock and Flash of an XV6800

I had to turn my Titan in for a replacement. Knowing about relocking breaking the usb port, I figured I'd do it anyway and just flash via the SD card. Well to my amazement I was able to relock and flash the OEM Radio and Software without and problems. Once it booted up Activesync connected and charge light came on.
Just figured I'd share since there is so much fear about relocking.
Went from 3.56 based ROM and 3.42.30 Radio back to OEM.
I had to turn my Titan in for a replacement. Knowing about relocking breaking the usb port, I figured I'd do it anyway and just flash via the SD card. Well to my amazement I was able to relock and flash the OEM Radio and Software without and problems. Once it booted up Activesync connected and charge light came on.
Just figured I'd share since there is so much fear about relocking.
Went from 3.56 based ROM and 3.42.30 Radio back to OEM.
Click to expand...
Click to collapse
I'm not sure what you mean about fear of relocking and relocking breaking the usb port.
The story on the street has always been.... DONT go from a GPS to a non-GPS radio. Something about how it will screw up the USB port.
http://forum.ppcgeeks.com/showthread.php?t=21953
Read first post
This is only a small example but I'm sure I could find more than 10 instances of this throughout threads. Including NO2Chem saying not to do it aswell.
The story on the street has always been.... DONT go from a GPS to a non-GPS radio. Something about how it will screw up the USB port.
Click to expand...
Click to collapse
I have never heard that story, nor have I ever had any problems going back and forth between GPS and non GPS radio.
While testing the new Sprint PRI way back when 3.49 came out (I'm on Verizon), and now testing the new Verizon update, I've had to go back to stock more times than I can count and have never ran into any issues.
May I ask where you found these rumors?
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Read the first post in the link I gave you. Then you can do a search on downgrading issues to find more reports.
I know it can be done because I've done it on 2 different Titans now. I made the thread to help prove that it can be done so other arent so scared by the rumors as you call it.
gc14 said:
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Click to expand...
Click to collapse
Exactly... I'm attempting to put the rumor to rest. Atleast as far as Verizon customers are concerned.
What SPL are you using before relocking to 1.06?
yep
Rom 2.09
Radio 1.30
yep
Rom 2.09
Radio 1.30
Click to expand...
Click to collapse
I think you misunderstood me....SPL = bootloader.
What bootloader are you using before relocking?
lllboredlll said:
yep
Rom 2.09
Radio 1.30
Click to expand...
Click to collapse
I am not sure if you answered his question. Which bootloader are you running, nueSPL or other?
I have heard some concern with reverting to non-GPS stock using the no2chem tools, but obviously there is no worry with the relocker and such.
gc14 said:
I think you misunderstood me....SPL = bootloader.
What bootloader are you using before relocking?
Click to expand...
Click to collapse
Sorry I misunderstood you. I was running 2.40 before taking it back to 1.06.
It gets hard to think straight with people flying in and out of my office every 5 seconds. I'll try to read a little more throughly next time.
Sorry I misunderstood you. I was running 2.40 before taking it back to 1.06.
Click to expand...
Click to collapse
In my encounters with going back and forth, this is what I've come up with (for Verizon users):
If using SPL 2.47, steps to relock are as follows:
- Install Olipro 2.40 via USB
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
(DO NOT EVER USE nueSPL Relocker!!!)
To get back to SPL 2.47 from stock, all you need to do is run nueSPL Unlocker and use the microsd card to go from SPL 1.06 right to SPL 2.47, then flash a 3.x.x rom/radio. Going FROM SPL 1.06 TO SPL 2.47, SPL 2.40 is not needed.
If using SPL 2.40, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 2.40 from stock, all you need to do is run Olipro 2.40 via USB, then flash a 3.x.x rom/radio.
If using SPL 1.20, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 1.20 from stock, all you need to do is run TitanUnlocker via USB, then flash a 1.x.x rom/radio.
Now all there is left to do is link this to ppcgeeks and be done with the rumor. Thank you for your input....
gc14 said:
In my encounters with going back and forth, this is what I've come up with (for Verizon users):
If using SPL 2.47, steps to relock are as follows:
- Install Olipro 2.40 via USB
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
(DO NOT EVER USE nueSPL Relocker!!!)
To get back to SPL 2.47 from stock, all you need to do is run nueSPL Unlocker and use the microsd card to go from SPL 1.06 right to SPL 2.47, then flash a 3.x.x rom/radio. Going FROM SPL 1.06 TO SPL 2.47, SPL 2.40 is not needed.
If using SPL 2.40, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 2.40 from stock, all you need to do is run Olipro 2.40 via USB, then flash a 3.x.x rom/radio.
If using SPL 1.20, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 1.20 from stock, all you need to do is run TitanUnlocker via USB, then flash a 1.x.x rom/radio.
Click to expand...
Click to collapse
I vote to have this added to the return to stock wiki. GC will you post?
How about USCC?
Brings me back to my previous question, GC (Previous Thread); How can I back-up the current ("Stock" for USCC) OS ROM and RADIO on my new Titan? It was discussed that it [dumping current ROM and Radio and then using dump to re-flash] couldn't be done. I wanted to do a ROM dump before flashing to DCD's so that I could revert to it if needed; also, so that I could re-flash to "stock" on my old unit before sending it back to USCC... however, I don't how to accomplish this, if at all possible to do so!
If anyone can guide me through this, I could upload the USCC "Stock" (for lack of a better word, since USCC has no actual "Stock" Roms) ROM and RADIO and make it available to other unfortunate USCC customers. I agree w/Serfboreds, and also vote to have this thread added to the "Return to Stock" Wiki.
Thanks, Guys!!
gc14 said:
I have never heard that story, nor have I ever had any problems going back and forth between GPS and non GPS radio.
While testing the new Sprint PRI way back when 3.49 came out (I'm on Verizon), and now testing the new Verizon update, I've had to go back to stock more times than I can count and have never ran into any issues.
May I ask where you found these rumors?
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Click to expand...
Click to collapse
I think the issue lies with Sprint customers..... I personally have reflashed to stock at least 15-20 times.... from a GPS ROM and back.....
That is a very nice summary of steps for re-locking from various spl's and definately needs to be entered into the !iki.... If GC doesn't have time I'll do it when I get done here at the dentist.... booooooo....
I think the real issue was going from bootloader nueSPL 2.47 to a stock GPS rom caused problems. But because verizon customers dont have a stock gps rom to flash back to we go to a non-gps (1.XX) radio which does not cause the problem.
No2chem originally made the advice not to go back to a stock assuming stock included 2.XX or 3.XX radios. Once he was alerted to the fact that going back to stock 1.XX (i.e with verizon) did not cause a problem he modified his warning advice.
Once again, the warning is only valid for bootloader nueSPL 2.47
GC, does going from nueSPL 2.47 to olipro SPL 2.40 prior to relocking negate problems for everyone? I ask that question because I have refrained from moveing to 2.47 for fear of problems in the future. As far as I can see the benefits of 2.47 are marginal at best. But if I have a sure fire escape mechanism I might upgrade my bootloader at some stage
GC, does going from nueSPL 2.47 to olipro SPL 2.40 prior to relocking negate problems for everyone? I ask that question because I have refrained from moveing to 2.47 for fear of problems in the future. As far as I can see the benefits of 2.47 are marginal at best. But if I have a sure fire escape mechanism I might upgrade my bootloader at some stage
Click to expand...
Click to collapse
Yes, it negates the problems.
gc14 said:
Yes, it negates the problems.
Click to expand...
Click to collapse
Thanks dude. And I agree with Serfboreds that you should add this advice to your wiki. Very easy to understand and maps out all (most) of the possible relock escape routes.
Once again gc you are a font of wisdom.
ugh.... i can't keep up with all the misinformation anymore. If it works for you verizon users in your personal experience though good for you. I know for a fact it can cause problems. I'm starting to narrow it down to the original 3.35 leaked rom with GPS radio from sprint, but have no firm proof it's that narrow scope yet . Still have myself a brick from the GPS to pre-gps and I didn't use nueSPL Relocker thats for sure =P
For more info on the problem and others that experienced this "rumor" first hand go to ppcgeeks and search for "download mode"

Categories

Resources