Develop Bugs

[UPG]Hard-SPL Unlocker or how I learned to stop worrying and love the MPU

[size=+1]Greetings From the Diamond Elite Project Team (currently only Olipro and Cmonex, so, any other skilled devs wanted - please PM Olipro and/or Cmonex, don't PM this account, we rarely check it)[/size]
We are proud to announce the release of Hard-SPL for *ALL* Diamond devices, overcoming the new MPU protection on the device.
[size=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/size]
As an added feature, the Hard-SPL requires signed code even after flashing... we chose to do this for several reasons.
1) safety... we will begin releasing all available Diamond resources re-signed with our certificate, this means you don't need to worry about flashing something incompatible, if it's something bad, we won't sign it.
2) reliability; If you want something signed, just ask, we will be able to verify that it's not going to be something that breaks the device, as has been the case with the Elf ROM disaster.
We'll be releasing a developer edition in the future; we will continue to maintain the signed SPL as this is quite nice for total and utter noobs afraid of bricking their device.
Flash this now, [size=+2]Go to our separate thread listing Supported ROMs for ROMs you can flash[/size]
[size=+2]Installation Instructions:[/size]
1) Download, extract to an empty folder.
2) Run RomUpdateUtility.exe, Have Phone Synced with PC in Windows Mobile
3) follow steps, check device for prompts after PC shows loading bar.
4) SPL flashes, job done.
Anyone having problems with the device entering SSPL automatically, please copy SSPLManual.exe to the device and run it. then once the screen is black, run RUU manually.
IMPORTANT NOTES:
1. do not try to use this SSPL to flash anything else other than an SPL file. it explicitly blocks other flashes anyway. SSPL is *never* a good way to flash OS images
2. INSTALLING THIS WILL HARD-RESET THE DEVICE
Thanks to Walshieau for a **** load of testing!
All Project Donations gratefully accepted
INSTALLING THIS WILL HARD-RESET THE DEVICE
TROUBLESHOOTING TIPS:
- read the instructions.
- read the instructions.
- read the instructions.
- Anyone having problems with the device entering SSPL automatically (your device doesn't even go to black screen), please copy SSPLManual.exe to the device and run it. then once the screen is black, run RUU manually (you run the RUU on the PC, if it isn't obvious).
- if you get connection error in RUU after the device goes to black screen, then try a different USB port, also do not use USB hub, you can also try rebooting your PC, and can try using another PC. read the thread for even more tips that I don't remember now. also you can try unticking advanced network functionality in start menu / settings / connections / usbtopc applet.
- if SSPL-Manual.exe or enterbootloader.exe fails to run (says missing component or similar), try a hard reset of the device.
- CDMA (Sprint or Telus) diamonds need my other hardspl:, head over to: CDMA (not GSM) diamond hardspl - ONLY use this if your diamond does not use GSM protocol for radio!!! otherwise you will brick the device!!!
UPDATE: 1.37 Hard-SPL
for those who need 1.37 due to some screen fuzziness issues on some newer diamonds, here it is with hardspl patches:
- Developer Edition: can flash unsigned code. Version: 1.37.OliNex
- Signed Edition: can only flash preapproved signed code. Version: 1.38.OliNex (of course still based on 1.37).
please see Attachment below for Signed Edition!!
for Developer Edition, see the developer hardspl thread of course.
(use attachment Hard-SPL-Diamond-OliNex.zip to get the RUU package to flash the 1.38 NBH from HardSPL_OliNex138_Signed.zip. just overwrite the NBH file with 1.38 NBH)
I recommend you flash the original HardSPL, as that one is MFG. only flash the 1.37/1.38 if you experience the fuzzy display issue.
UPDATE 2: 1.93 Hard-SPL
(placeholder for now, but you can already download unsigned version in the Developer HardSPL thread!)
if someone's diamond came with 1.93 SPL originally, maybe this HardSPL based on 1.93 will work better than the olders. I have a report that someone has black screen with older SPL's.
but even if your diamond didn't come with 1.93 stock, but 1.37/1.38 doesn't fix screen problems (fuzzy screen, flickering, etc.), it is recommended to try this 1.93 HardSPL.
if your diamond works fine with original HardSPL, no need to flash this one.
IMPORTANT: all in all, I recommend you flash the original HardSPL, as that one is MFG and easier to deal with if there is some problem. only flash the 1.37/1.38 or 1.93 if you have screen issues.
if it was some other version and you still have issues after trying 1.37/1.38 and 1.93, then please let us know.
Stock SPL's for warranty reasons:
visit the http://forum.xda-developers.com/showthread.php?t=400411 (Signed ROMs) thread, see post #20.
(or visit Developer HardSPL thread post #39, same thing.)

Thank you. I am going to flash..

panosha said:
Thank you. I am going to flash..
Click to expand...
Click to collapse
enjoy! you won't imagine how much work it was for me to get this ****er (SSPL) working
anyway, this has been tested on radio versions 0.91 and 0.93, I don't think it is radio specific, but if you have some newer radio version (haven't seen any yet) and have trouble with running SSPL or flashing it, let us know.
also, the SSPL screen is black, not tricolour, that's just the way it is. only preproduction diamond had it tricolour.
last note: do not try to use this SSPL to flash anything else other than an SPL file. it explicitly blocks other flashes anyway. SSPL is *never* a good way to flash OS images.

Thanx a lot guys, awesome work.

Thanks Olinex
i agree to the idea of olipro, it is good to the community ...especially for new comer who had not muc experience in rom flashing
but i think for developer and some experienced user , a unsigned version is neccessary for daily testing like :
1) if i am cooking a rom and wanna flash into the device to had a real test , i need to wait u guys to sign..u guys may busy and wasting unneccessary time for signing some "beta" rom ...example I made a hermes rom before ..which had chinese build in support, i had made more than 5 nbh for my own testing ....:S .. u can imagine if need signed .. i need to bother "olinex" tooo many time
look forward for a developer unsigned ver

@leofungwai.
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
also, it should allow for flasing genuine firmwares signed by vendors, meaning hardware vendor's certificate is still must be valid.
And if it doesn't then, what happens if device is stucked in bootloader or doesn't boot into OS anymore? that would make difficult for reverting back to original SPL.

SecureGSM said:
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
Click to expand...
Click to collapse
Surely you're not THAT stupid?

testing now
hi all testing now updating soon

First of all great work guys!
I am trying to flash my Diamond from a Windows XP machine. I start the RUU and when the progress bar appears it halts at 0% and after some time starts about a connection problem, my diamond is not going in bootloader mode. So I started my Diamond mannualy in 3 color mode and started the RUU again. Again it halts at 0% and is there now for about 5 mins. Can you help me out guys?
RvBCrS

Great!
And thanks for the TEAM!!!
Just installed it.
Worked.
this makes a Hard Reset on the Device.
Now will try to update with a different rom.
Nadavi.

what is that suppposed to mean? calling someone stupid is already bad but that was my question.
The way I understood, if your SPL code is checking for presence of your certificate "attached" to the NBH, then if the certificate in your SPL code is patched to different certificate, then SPL will not complain about code is not being signed by your certificate anymore. call this stupidity, but I am not going to put something on my device I would not be able to remove with out third party *permission* to do so.
again, I can be wrong. I am not a programmer, but then your explanation is confusing.

Very strange, if I start the RUU updater with my phone booted in Windows Mobile, it try's to start EnterBootloader.exe but that crashes with an exception window!?!

just reset the device and try again. it MUST be done from windows

Olipro said:
just reset the device and try again. it MUST be done from windows
Click to expand...
Click to collapse
Thanks olipro for you response, I rebooted my device and did it again with windows mobile booted, waited for device center connection, and again got the exception on "Enterbootloader.exe" very strange it looks like a .NET exception window.. I have a Dutch Mobile edition, don't know if that matters..

SecureGSM said:
what is that suppposed to mean? calling someone stupid is already bad but that was my question.
The way I understood, if your SPL code is checking for presence of your certificate "attached" to the NBH, then if the certificate in your SPL code is patched to different certificate, then SPL will not complain about code is not being signed by your certificate anymore. call this stupidity, but I am not going to put something on my device I would not be able to remove with out third party *permission* to do so.
again, I can be wrong. I am not a programmer, but then your explanation is confusing.
Click to expand...
Click to collapse
yes... patched to a different certificate, therefore, requiring files that you flash to be signed with it.
If you want to get rid of it, you can have a stock HTC SPL signed with it.
Personally I like this because our released ROMs have no SPL in and a dedicated rollback desired for warranty purposes can be used with no chance of mistake

SecureGSM said:
@leofungwai.
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
also, it should allow for flasing genuine firmwares signed by vendors, meaning hardware vendor's certificate is still must be valid.
And if it doesn't then, what happens if device is stucked in bootloader or doesn't boot into OS anymore? that would make difficult for reverting back to original SPL.
Click to expand...
Click to collapse
you can't, because the SSPL also requires this custom signing to flash the HSPL...
your point is very good about allowing for stock ROMs.
we actually can have a way to do that
though hopefully this won't last long and the unsigned "developer version" will be available to everyone soon. I strongly disagree with the original idea anyway.

same
same here stuck in 0 %

motin said:
same here stuck in 0 %
Click to expand...
Click to collapse
did the screen actually go black (i.e. into bootloader)

WooooooT great job guys!!!!

when you run the new rom from europe then it will boot to the 3 bootolader mode you can see your spl installed and then not mov any more from 0%

Unable to flash Diamond with new ROM

I cannot flash my Diamond with a new ROM. I have tried using HardSPL versions 1.23, 1.24, and 1.34,and various ROM's but with no joy.
I have done a hard reset on my phone and setup an active sync connection with my PC. I then run HardSPL, which I get the screen with 4 colours on my phone and then get the progress bar displaying 0% on my phone, but doesn't get past that, the program times out with a communication error.
When I take out and replace my battery my phone still works fine.
Please can anyone give me advice.
Thanks

same here.
ROM 1.37.401.3
radio 1.00.25.03
WWE

paul_32 said:
same here.
ROM 1.37.401.3
radio 1.00.25.03
WWE
Click to expand...
Click to collapse
Dito for me!

Saw this coming
Indeed, not a surprise to see another thread opened by newbies.
Partly (small part though) we might point the finger at the HARD SPL creators and the Chefs.
Too many ROMS with sometimes confusing "signed" or "non-signed" versions (and this is for you newbies) WHICH NEED A DIFFERENT HARD SPL.
Unsigned and Signed ROMS can not be flashed with same SPL guys .
So, start readin these threads about the ROM you want to flash profondly and use SEARCH.
In a few weeks, you'll have to write this message to newer Newbies again.
Maybe I better ask a MOD to close this thread though

Look here ! The solution is near
Just an example how you will feel in a few minutes
http://forum.xda-developers.com/showpost.php?p=2420277&postcount=125

ceevee369 said:
Indeed, not a surprise to see another thread opened by newbies.
So, start readin these threads about the ROM you want to flash profondly and use SEARCH.
In a few weeks, you'll have to write this message to newer Newbies again.
:
Click to expand...
Click to collapse
The problem is: We get a connection error a while after the black screen during the hardSPL procedure. And the SPL is not updated...
So if you know what the reason is that the device wouldn't enter SSPL automatically (JumpSPL.exe 0x800000 sspl-1.01-reloc-mod.nb)? Mine didn't respond! I try to used another USB port but …same problem!
I tried to run " JumpSPL.exe " directly from the diamond... then the screen turned black (backlight still working good but the whole screen is black)
Thx for your answer!

Well, I had the same problem, and managed to work around it! First of all, I have NO idea why all of a sudden my Diamond would stop going into bootloader mode by itself - instead, all I get when trying to flash is a screen which fades to black, and then eventually the comm error after 5 minutes, with the option to go into recovery mode.
This is what works for me: first of all, make sure you have the right HardSPL for what yoyu need to do. Either flash the one for the signed roms (and the only try to flash signed roms) or flash the one for unsigned roms (and then only flash unsigned roms). But how to flash if the screen goes black and you do not get a connection?
Well, what works for me (and it may not work for you - try at your own risk!), is to put the phone in bootloader mode by holding the -Volume button and doing a soft reset, and then connecting it to the USB cable of the PC. When the lettering in the white part changes from Serial to USB, you are ready to go, and - at least for me - the flashing works.
Don't ask me why, but this is what I did last night to put the .05 radio on my Diamond.

ceevee369 said:
Indeed, not a surprise to see another thread opened by newbies.
Partly (small part though) we might point the finger at the HARD SPL creators and the Chefs.
Too many ROMS with sometimes confusing "signed" or "non-signed" versions (and this is for you newbies) WHICH NEED A DIFFERENT HARD SPL.
Unsigned and Signed ROMS can not be flashed with same SPL guys .
So, start readin these threads about the ROM you want to flash profondly and use SEARCH.
In a few weeks, you'll have to write this message to newer Newbies again.
Maybe I better ask a MOD to close this thread though
Click to expand...
Click to collapse
Thanks ceevee369 it works fine for me now

I still cannot get a new ROM on my diamond. When I said it worked above that was only getting HARD SPL on my phone.
When I try to update the ROM it gets to 100% and then says the ROM is corrupt. I have tried with different ROM's and I get the same error

creation said:
I still cannot get a new ROM on my diamond. When I said it worked above that was only getting HARD SPL on my phone.
When I try to update the ROM it gets to 100% and then says the ROM is corrupt. I have tried with different ROM's and I get the same error
Click to expand...
Click to collapse
Could you please give the UNSIGNED developers SPL a try?
You only used he Signed version ones as you wrote in 1st thread, and as far as I can feel, you try to flash unsigned ROM's maybe?
Hope you're not bricking your device soon.
Did you posted in the specific ROM thread a specific question on the hard SPL you use vs. The ROM you intend to flash?
Yes, bootlader will always start, but no, it won't go further than giving you an error if no compliant Rom is used.

ceevee369 said:
Indeed, not a surprise to see another thread opened by newbies.
Partly (small part though) we might point the finger at the HARD SPL creators and the Chefs.
Too many ROMS with sometimes confusing "signed" or "non-signed" versions (and this is for you newbies) WHICH NEED A DIFFERENT HARD SPL.
Unsigned and Signed ROMS can not be flashed with same SPL guys.
So, start readin these threads about the ROM you want to flash profondly and use SEARCH.
In a few weeks, you'll have to write this message to newer Newbies again.
Maybe I better ask a MOD to close this thread though
Click to expand...
Click to collapse
The majority of these "help me" posts wouldn't be necessary if the information on this forum was a little more accessible - and seriously, the search engine returns so much dross that it takes an age to gather all the relevant info about roms, spls, flashing, cooking etc, etc. And yes, modmydiamond.info is a cool site but the info there is basic at best.
I'm not knocking the work being done here as it's seriously good - I'm a techie from way, way back, so I can appreciate the amount of effort involved - however, you guys make a rod for your own back by not producing documentation that is more explanatory (or just there) to start with.
And yes, I can also appreciate that you're a bunch of dudes doing this for free and for the love of it and not a bunch of technical writers getting paid for your work but you have to try to understand what a newbie is faced with when they arrive at this site looking to upgrade their pride and joy. Confusing and contradictory are two words I'd use.
Peace.
Ade
PS. ceevee369, the "you"s above weren't necessarily directed at you.

Everytime I'm trying to Hard-SPL my phone disconnects and tryies to install a device called "Qualcomm CDMA Technologies MSM" but doesn't find a driver for that. So there is no connection left between the Phone and the PC and it doesn't work anymore...
Can anyone look if that device is installed on his PC? And if possible upload a driver for that?

Found a way to solve the problem:
Go into bootloader-mode (volume-down + reset) and then connect to the PC. If Win is looking for the drivers you will find them in the folder where ActiveSync was installed. Afterwards you should see "usb" instead of "serial" in the screen on your XDA.
Now soft-reset and proceed as told everywhere...
So my problem was that Win Didn't finde the drivers automatically and i didn't know where to look for them.

ceevee369 said:
Could you please give the UNSIGNED developers SPL a try?
You only used he Signed version ones as you wrote in 1st thread, and as far as I can feel, you try to flash unsigned ROM's maybe?
Hope you're not bricking your device soon.
Did you posted in the specific ROM thread a specific question on the hard SPL you use vs. The ROM you intend to flash?
Yes, bootlader will always start, but no, it won't go further than giving you an error if no compliant Rom is used.
Click to expand...
Click to collapse
Its working now, I used the unsigned SPL. Although when I was using the signed SPL I was trying to Flash ROMs that had been sigened.

Question on newbie with rom update

okay, guys, I have a few question that I am hoping it can be answered before I advernture ito flashing my rom.
First of all, I relaly appreaciate all of the people who work so hard getting the rom updated. You guys rocks.
Now, this is the first time I am going to flash to my tilt 2. As I have read the flashing the GSM phone guide (which I am hoping that's the guide I should be following to flash). I am just a bit confused as to how to do it.
It appears to me that I must flash the SPL unlocker in order to flash to the any rom am I correct? Just curious what exactly does it do? If I flash it, would tehre be any issue if I decided to go back to the original rom. I saw that at HTC's site, they have stock rom for ATT phone (http://www.htc.com/us/support/tilt-2-att/downloads/)so if I want to go back, can I just use that file and flash it back? Or I need to flash to a diff HardSPL? before I can use it?
Also, i am curious as to are there any program that will let me keep all of the settings and stuff up to date. in my past where I have the hp's ipaq. I had a tool where after I flash teh rom or do a hardreset, I can run that tool to revert all of the program and configurations (of course, I had a backup file first).
Let me just double check:
basically
1-hardspl
2-rom
3-all set
again, my phone is ATT tilt 2, I would really appreciate any information.

The SPL is kind of similar to the BIOS in your computer; it performs very low-level functions, and functions as a bootloader, among other things. The SPL is responsible for flashing new ROMs to the device, and the SPL that comes on your device won't let you flash ROMs not signed by HTC. HardSPL is a patched SPL that removes this ROM signature check, allowing any ROM, official or custom, to be flashed. The way HardSPL is designed also makes it more difficult (though not impossible!) to brick your device.
If you ever want to restore your original SPL (for warranty purposes,etc.) there are a few threads which explain how to do this, and the HardSPL thread has all the SPLs available for download. If you flash the package from AT&T, your ROM will be the original ROM, but the SPL will still be HardSPL, which isn't okay if you're returning the device for warranty purposes since they check for that. As I said, there are a few threads which have full tutorials for restoring your AT&T Tilt2 to stock.
For backup, there are tons of solutions out there such as the User Customization types (XDA User Customization and Sashami), as well as the full backup and restore suites (Sprite backup, SPB backup). I've automated everything on my device with XDA User Customization, so I don't know much about the full backup and restore suites, though a backup and restore suite might be more what you're looking for based on your description.
Lastly, you have the order of flashing correct. Optionally, you can flash a radio ROM later on, but if this is your first time flashing, you might want to wait awhile until you're more comfortable with flashing.
OMGHAX 900th post!

Quick Advice Needed: I going from stock OEM WM6.0>Android

I have flashed phones before, (my TP2 runs android)
Sorry for the extra post, but I know someone has tried this.
I've read the stickies, there is ALOT of outdated info, dead links, etc..
***Whats the easiest upgrade route to get a stock WM6.0 Kaiser on Android?***
WM6.0>OEM HTC WM6.1 ROM>Android
OR
WM6.0>Custom WM6.5 ROM>Android
Which is the easiest/quickest way to get Android?
NAND or run Haret off the SD card?
I don't need a walkthrough just anyone's quick advice. Espicially, any trip-ups I might encounter regarding the radios and SPL versions.
Thanks

Sucessfully bricked the phone trying using Atools!

congratulations for not thoroughly reading the sticky topic about HOW TO COMPLETELY REPLACE WINDOWS MOBILE WITH ANDROID.
It Requires Radio version 1.65 or higher (which is only compatible with WM6.1 or 6.5)
It Requires HARD SPL Version 3.29 or higher (which is compatible with WM6.1 or 6.5) for the case you wanna flash on NAND
So either way, you gotta upgrade to WM6.1, HardSPL, Radio, then Go to ANDROID. Impatience often hurts. Android is blazing fast when installed on NAND (sys + Data)
So tell me,
Your phone is bricked in what sense? flashing using Atools is risky. I suggest go with RUU utility or SD Card. And I suggest you must consider a lil bit of reading first

Atools isn't a flash tool...

Thanks for the help, and I can sense your frustration. I make my living doing IT work. And, I'm not technically a newbie to the flash game. I've owned the PPC6700, Mogul, Touch Pro, and TP2. I've flashed them all. I've even contributed a sticky or two.
I admit I was rushed. And like a small child with a gun, I took a shot without fully understanding Atools.
Yes, I can only blame myself for my Kaiser's demise. To answer your question, the Kaiser is toast. It can't get bootloader and only has a blackscreen and one green light. Atools wins this round. But I'm not too concerened, I'm in a position where I have a nice stock of Kaiser's to fry before I need to peruse The DEFINITIVE MTTY thread.
Dark_prince, please don't blame my impatience entirely for the phone's death. Don't you think some of the blame definitely falls on me not being a bit smarter than 'ye old sticky thread (How to replace Windows Mobile with Android). Following that sticky verbatim will lead a WM6.0 user to HARDSPL first, and then update WM6.1. Ignoring that, the sticky also instructs users to use Atools, which requires it's own sticky.
In the passing year and a half since that sticky was updated, haven't newer versions of Android appeared with newer methods of installation that aren't covered in the sticky? Specifically, it's not clear to me where to find a newer Android installation tutorial that doesn't include Atools.
I'm comfortable that I could complete an Android-Haret setup running off the SD card, but I don't think performance would be acceptable. I want what you and others have
Android is blazing fast when installed on NAND (sys + Data)
Click to expand...
Click to collapse
and I'm not above begging for your help to get it.
Now that I've burned one attempt, I need someone's input about how to proceed. Any help is appreciated....
In my usage case, I'm starting with an AT&T 8925 (Tilt) (KAISER100) w/ WM6.0 Professional. Here's where I stand on attempt #2
1. Cleared the storage on the phone.
2. In order to get the correct usb drivers on my Windows 7 PC, I downloaded and installed WMDC 6.1 UPDATE: WMDC 6.1 Does not install ALL the correct drivers, you'll need to force some by reading this thread.
3. A few toggles of "Advanced Network Functionality" later, the phone was Syncing nicely.
4. I then downloaded and flashed the Official HTC AT&T Tilt WM6.1 Upgrade ROM Success.
I now have stock WM6.1 and radio version 1.65.21.18
Next up, I'm trying to decide which HardSPL to use, and which radio will provide me with the best options from the Android Chefs. I don't anticipate any trouble flashing these. But, which combination of HardSPL and radio offer the best base package for an upgrade to Android? I'd love your advice.
Speaking that, after I upgrade the SPL and radio, how the hell do I get Android on my phone if I'm not suppossed to use Atools? Don't I need Atools in order to create a custom .nbh and Android install package for my Kaiser? If not, where can I find these files, especially if I don't know my panel type?

UPDATE: A Little bit closer.
I successfully updated the SPL / Radio(1.70.Olinex) / SIM Unlocked using KaiserUnlocker.exe
Updated the bootloader to 3.56 Hard SPL nostuckinSPL / Force USB via SD card
Updated the radio from 170.0linex to 1.70.19.09 via SD CARD
For any Windows 7 x64 users attempting to Flash their Kaiser, be sure to have a look at [TUT] Dummies guide: updating HTC USB Sync Drivers.
I should have made a bigger mental note when after I installed WMDC 6.1, Windows FAILED to install the correct driver the first time I connected my phone to the PC in bootloader mode. The above thread explains the process of booting Windows 7 in a special mode, in order to force customized drivers to be installed on your machine, the hard way. I followed the steps until about step 12 (my device manager never yellow flagged anything). According to the thread, it looked like it failed, so I resorted to the next best thing. Keep the phone in bootloader and unplug and replug to different usb ports praying that my "forced-on" drivers would finally recognize the damn thing. Success, it finally did and Windows started loading the Qualcomm CDMA Technologies MSM Windows driver. Launching KaiserUnlocker.exe took it from there, albiet with one confusing caveat... IN the first part of step 1, KaiserUnlocker will tell you that you need to unplug and replug your usb during the second-half of step one. Okay, no problem. It fails to tell you that you're going to do this "uplug and replug" at the same time you'll be staring at text in red saying DO NOT UNPLUG OR LAUNCH ANY PROGRAMS!
However, unplugging and replugging is necessary in order to trigger Windows to use the bootloader drivers to communicate.

SPL 5.xx all downgrading ways summary

Hi guys. Becouse much people in thread [DFT][Updated!#2] HSPL / RSPL for HTC WP7 First Generation do not know, how to downgrade SPL to be able HSPL using, we can resume all known ways here. But, I have no all devices, post confirmations, please. I have got >=1 confirmations from all next mehods, but, use it carefully, it is on your own risc. For any devices no JTAG/XTC method is possible to restore factory state!
1. Two-stage way (worked for any devices only, but for all SPL states including "small" and "big" halfbrick).
Using official update parts.
Description .. in progress.
Links:
http://forum.xda-developers.com/showthread.php?t=1361577,
Google Translated Unbrick Manual.
2. ROMUpdateUtility way (worked for any devices only, for equal brand/region only, not for halfbricked, but PC USB connection is needed only).
EDIT: ATTENTION: DO NOT TRY METHOD NR. 2. It is really, that this method can work only on any device, but more devices may be fullbricked!
Using original ROM parts (Thanks to Ansar).
Description .. in progress.
Links:
Google translated from WMMania.cz
EDIT> Better way seems original SPL downgrading RUU only - see http://forum.xda-developers.com/showthread.php?t=1411904
3. Full GoldCard (worked for all devices, all brand/region, for intacted SPL and "small" halfbrick only, but not for "big" halfbrick). You need Y-Cable (may be simplified - see picture - you nedd 2,5'' external disc usual additional power cable and very chip USB A/F-A/F junction only).
Using original ROM parts.
Description .. in progress.
One way only, which is for Trophy device fully confirmed.
Links:
http://forum.xda-developers.com/showthread.php?t=1359498
4. Simplified "like" GoldCard (worked for any devices, equal brand/region only, for intacted SPL and "small" halfbrick only, but not for "big" halfbrick). You need Y-Cable (may be simplified too), but you do not need second WM/Android/Linux device for CID reading.
Using original ROM parts.
Description .. in progress.
Links:
Google Translated Unbrick Manual.,
http://forum.xda-developers.com/showthread.php?t=1371073

Nice idea all in one thread. If you want, you can use my movie about that.
http://www.youtube.com/watch?v=uctenG08Fj8

Please clear up my mixed head.
I have a O2 Branded Htc 7 Pro. I am stuck on 7720.68
I cant restore any of my premango states and I cant boot to usb host mode anymore. (800b010a or 8018004D or...)
So there is no way to fix my bootloader at the moment right? Official Updates from Zune (HTC Updates or 7740) dont work either. However I have the possibility to use the cab sender togo to 7740, but that is the only cab that works this way.
Help me please what can I do?

After Mango halfbrick
Hi kaemen. Have you tried http://htc7pro.howto.cz/O2ODEHTGoldHTCOEMUpdate2011.cab posting by cab sender? If success, you can downgrade SPL by GoldCard. But, it is for your risc, cca 1% of flashing results fullbrick.
Google translate page http://htc7pro.howto.cz/Unbrick/UnbrickCesky.htm or see all my posts in HSPL XDA thread. Martin

this is seriously bugging me now.
I dont have backup before 7720,
i dont have y cable or anything
spl is at 5.1
now can anyone simplify what needs to be done?

I dont understand why this is so complicated for everyone. I have a HTC Mozart on DFT 7720 and i can easily downgrade by restoring to a stock Pre-Mango ROM. Just plug in the device while holding the volume key to get the multi color screen and then run the RRU Rom .exe and there you go.
Im probably missing something here arnt I?

I get an error 80180048

Too danger
fahdriyami said:
I dont understand why this is so complicated for everyone. I have a HTC Mozart on DFT 7720 and i can easily downgrade by restoring to a stock Pre-Mango ROM. Just plug in the device while holding the volume key to get the multi color screen and then run the RRU Rom .exe and there you go.
Im probably missing something here arnt I?
Click to expand...
Click to collapse
It is not so simply. This method can work, see point 2 from my first post. But, 1. it is not working on halfbricked device, 2. it can fullbrick phone in any combination of RUU-Device-Brand-SPL5.x.
Better way seems original SPL downgrading RUU only - see http://forum.xda-developers.com/showthread.php?t=1411904

the post written by OP is seriously confusing. "any device only"?? what does that even mean? if it were to say "some device" or "certain devices ony" it would have made more sense. right now im just to baffled by the sentences to even try any of the listed solutions.

bevoc said:
the post written by OP is seriously confusing. "any device only"?? what does that even mean? if it were to say "some device" or "certain devices ony" it would have made more sense. right now im just to baffled by the sentences to even try any of the listed solutions.
Click to expand...
Click to collapse
This article is a year old, from the time of the first WP7 generation. Also, several people promised linguistic correction and no one did it. I am not able to write english right myself, this is translated with Google help. But, enough people used it successfully last year. Many recent articles is there now on XDA. I writed here first posts about halfbrick solution possibility without special hardware and about SPL downgrade too. But, they are very old, you can find many recent and better posts here.