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.
Related
Hello,
I have a question that I have wanted to ask for ages and have never found the answer:
Is there a way I can 'safeguard' my phone so if something goes wrong in the flashing process I can re-flash any ROM onto it and not the original device ROM?
I mean, could I put some special bootloader on first before flashing or something?
I ask this because for my device there is currently no original ROM (XDA Cosmo) - and I would like to test out some ROMs but am concerned I'll brick my device. I haven't had a problem yet doing it, but who knows - it does seem to happen to people even when they do everything right. And I don't think I'm the only person with this problem.
Any advice from more experienced members?
Thanks
A Bricked Device, Or Temporary You Cannot Reboot Your Mobile Device
uccellino said:
Hello,
I have a question that I have wanted to ask for ages and have never found the answer:
Is there a way I can 'safeguard' my phone so if something goes wrong in the flashing process I can re-flash any ROM onto it and not the original device ROM?
I mean, could I put some special bootloader on first before flashing or something?
I ask this because for my device there is currently no original ROM (XDA Cosmo) - and I would like to test out some ROMs but am concerned I'll brick my device. I haven't had a problem yet doing it, but who knows - it does seem to happen to people even when they do everything right. And I don't think I'm the only person with this problem.
Any advice from more experienced members?
Thanks
Click to expand...
Click to collapse
I have so called bricked my test device more than 100 times and each time I have unbricked it each time. So never panic if you brick your mobile device. I have even bricked the wifi several time, I just unbricked the wifi also, have fun with the new 6.1 ROM'S with out worry............!
Technology said:
I have so called bricked my test device more than 100 times and each time I have unbricked it each time. So never panic if you brick your mobile device. I have even bricked the wifi several time, I just unbricked the wifi also, have fun with the new 6.1 ROM'S with out worry............!
Click to expand...
Click to collapse
I like your idea and your optimistic view
The problem is, I've read so often: "solve this error by reflashing with your original ROM", just I don't have one... and sofar I've haven't been able to recreate one. I did however hear about downgrading the bootloader before doing a real ROM flash and thought maybe this could be a solution...
Just re-read this: Excalibur Update SPL (USPL) 1.11
http://forum.xda-developers.com/showthread.php?t=329605&highlight=wm6+excalibur+S620
And read this:
EDIT:
You can now also flash the USPL allowing you to flash any unsigned (cooked ROM or ROM module, e.g. radio or OS) or signed ROM with any model/vendor ID. The USPL substitutes your SPL until you perform a full ROM update. Consider it as an extra insurance in case something goes wrong with flashing cooked ROMs or any other ROM update !
Instructions:
1. Run the USPL (Excalibur USPL- CID BYPASS.zip)
2. Run the ROMUpdateUtility.exe (Excalibur-USPL-RUU.zip)
Click to expand...
Click to collapse
Does this mean even if something goes wrong flashing, I can still flash something else back (not the original ROM)?
I suppose another question I have is: Is a CID unlock, eg. from IMEI-check, permament?
Check this link to see if your official ROM is listed.
Official ROM Collection
Mikey1022 said:
Check this link to see if your official ROM is listed.
Official ROM Collection
Click to expand...
Click to collapse
Unfortunately not There seems to be no XDA Cosmo ROM image anywhere.
[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%
Hi all
please dont flame the n00b. I have recently acquired my first smartphone the diamond and am very pleased with it. I have read through the threads and have developed my understanding of the considerations to make in flashing the ROM on my phone
I have an early version of the ROM as I received one of the first stock into the UK, which turned out to be grey imports from hong kong :S . I would like to realise some of the speed / battery / bugfix benefits of the newest ROM
however many of these threads are quite long , so i was wondering if someone could do me a favour by succintcly summarising the steps i would need :
my phone is runnning :
1.34.831.1 WWE - the unit is from hong kong i beleive, i have registered on HTC HK e-club
I would like to upgrage this is the latest signed UK ROM ?
If this is not possible can advice be given on going to the latest HK WWE ?
I understand this will involve changing the HARD SPL ?
Additionally can any method provided be confirmed as a reversible process should i need to invoke the warranty ?
thanks in advance for your help.
please let me know if you need any further information form me in order to help.
thanks
1: install hardspl (unsigned)
2: search the threads for the newer HK stock roms, they've been posted by tudispin I think.
3: flash
4: should need arise, you can revert to stock spl, search the threads for spls by htchackers.
you should be able to flash back for warranty purposes.. safest thing is still to dump your current ROM (search the forums and wiki for how-to), but i think you'll be alright. You can check out my site for step-by-step instructions on how to upgrade your ROM
thanks so far
just for help so far
your guide looks great racerx_
so i should be able to do the following tonight
1: install hardspl (unsigned)
2: search the threads for the newer UK? stock roms,
3: flash
4: and should the need arise, you can revert to stock spl, search the threads for spls by htchackers.
once the hardspl is loaded am i correct in thinking any ROM can be loaded ?
oh but
dump my current ROM before proceeding .. just in case
porkmince said:
just for help so far
your guide looks great racerx_
so i should be able to do the following tonight
1: install hardspl (unsigned)
2: search the threads for the newer UK? stock roms,
3: flash
4: and should the need arise, you can revert to stock spl, search the threads for spls by htchackers.
once the hardspl is loaded am i correct in thinking any ROM can be loaded ?
Click to expand...
Click to collapse
yeah you should technically be able to load any ROM... if signed Hard-SPL, then only any signed ROM of course
hit a slight problem
So i am tryiong to HARD SPL. have gone through all the instructions but :
when installint the HARD SPL . the phone screen switches off the progress bar on PC sits at )% for about 20 sec it then accelerates to 100% very quickly within around 2 mins. It say that is is installed correctly
however the phone restarts and i can still see the d: as 1.34.00.00
so the loinex 1.3 has not installed
the windows is hard reset as i then have to go through the screen calibration
any help appreciated
HardSPL is not the ROM, just software to enable the update
once you installed HardSPL you should now be able to install a ROM
hi
yes sorry for the confusion in my past previous description. It is the HARD SPL software update which says that it is installed but isnt
i have not attempted to load another ROM until this is done first
any further advice ?
in essence when installing the olinex 1.30 i get no errors
bit it doesnt install and all i get is a hard reset ?
If it goes through OK, it has installed You don't see anything different in the splash screen- that just lists the basics
To confirm, go into Bootloader mode by holding down the Volume Down Key and at the same time pressing the red reset button at the mouth of the stylus silo. It can take a few goes, but will show a rainbow screen listing the SPL etc, which ought to say 1.30 Olinex, confirming the correct SPL flash.
Once confirmed press the reset button to restart.
ok thanks for step by step advice there
the HARD SPL is loaded version 1.30 I will try a new ROM now
i am trying the :
RUU_Diamond_hTC_Asia_WWE_1.37.707.1_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship
which is signed so should work
mmm even though the phone is synced up I get error
"262" when i try to install new ROM
it basically stalls on 0% for about 4 to 5 mins before it aborts with this error message.
i have searched the forums but cannot see a succinct plausible answer
hmm.. i thought that error was usually encountered with unsigned ROMs...
1) are you flashing with xp or vista
2) are you connected through a USB hub?
3) what EXACTLY are your steps for flashing this ROM
hi there
yeas flashing through vista 64 bit
and not using USB hub but direct connection
I downloaded the signed 1.37.401.3 Europe ROM linked from this forum and this installed fine
the improvement over the old ROM is immense. so far i am delighted by the results.
I am still perplexed as to why the asian ROM did not install still :S
only difference so far is that this EUROP ROM does not have the remote desktop app
thanks for all your help. I am going to test this ROM over the coming week, but unless there is a compelling reason to another ROM i will stick with this
Why HARDSPL when flashing HTC rom?
When using the newer 1.37 roms, you download the installer from e-club, make activesync conn en go for it?
A noob's point of view
I got my Diamond about two weeks ago, and since I'm new to PDAs and WM, I've done a lot of reading on the forums, wiki etc. At first things were quite murky for me and I know what my fellow noob here is feeling. So I thought I should share my experience (or lack there of) for the use of other noobs.
What I Know
HardSPL is needed in order to flash a cooked (non original HTC) ROM. As I understand, it is the equivalent of BIOS for PCs, mixed with a bootloader flavor. You need to first change this section of software first in order for the cooked roms to be accepted.
HardSPL comes in two flavours:
- the developer edition with which you can flash any type of roms (signed, unsigned, original) link: HardSPL dev ed
- the signed edition with which you can flash signed roms (original HTC, and cooked signed). The signed ROM versions give an added sense of reliability since they are tested. link: HardSPL signed the topic name was confusing for me at first
A list of signed ROMs: here
There are more than one "cooks" out there working in teams or otherwise. And more than one ROM you can flash. I did a lot of reading before I chose the one to use, I find user feedback the best measuring tool for quality .
Now for the flashing part
After you downloaded the HardSPL and the chosen ROM, you need to install ActiveSync. This is found on the CDs that come with the device, or downloadable fromo the M$ ****e aaaa site ActiveSync is a tool used for transferring contacts, e-mails and other outlook stuff if you use it, files, AND is needed for the flashing process. When installing, if you do not use outlook and do not like "syncronisation folders" on your desktop uncheck every "folder" option, you will be better off.
This site was very useful to me since it gave a detailed description flashing with visual documentation which (a bit uncomfortable to admit) was very helpful for me.
The HardSPL flash takes little time to complete and unless going into bootloader mode (vol down + soft reset) is completely transparent to the user.
The ROM flash takes longer 10 mins - they go by pretty slowly .
For safety reasons, I also downloaded an original HTC ROM just in case.
Because the flashing process once started SHOULD NOT be stopped there are a few things to consider:
- charge the battery
- firmly and directly (no hubs) plug the USB cable into computer and device.
- if you live in an area where power cuts are often consider doing the flashing on an UPS-enabled computer.
When the flashing finishes, the device will reboot and you will have to set-up again. If using TLRs ROM do not panic if you have to align the screen 6 times or so as I did. You will eventually get to the next step
What I don't know or am not sure of:
- when using signed HardSPL can I load an original HTC signed ROM? if so, is this enough in case of RMA issues?
- when reflashing with a newer/different ROM can I restore a back-up made with the previous ROM? I'm using sprite and I backed up everything, including what registry stuff it offered to. In this case, do i need to reapply the registry tweaks? dunno if sprite backs-up all the registry or just some of it.
Im must thank guys for this thread, i am minutes from going to the postal office to get my Diamond and this weekend has been full of information reading and program downloading, but the only thing i was a bit hung up on was this flashig buisness. Of course i know a lot about flashing ( Right about everything there is to flash ) but almost nothing about Phone Flashing
But i think i will try the version i get now first to see if i feel the need to update to anything else...
Hence my question is rather simple... How tha fack do i see what version i already have? >_< is it that (vol down + soft reset) thing? or am i way out of place?
thx.
Reb0rn said:
How tha fack do i see what version i already have? >_< is it that (vol down + soft reset) thing? or am i way out of place?
thx.
Click to expand...
Click to collapse
No, that is for HardSPL info. To see the ROM version, go to settings - device info and you'll see both ROM and radio.
Hi I have recently tried to flash my Touch Diamond ROM, messed the hell out of it and, the only way to fix it is to flash it with the original stock ROM that it came with. Could anyone please help me with this.
HTC Touch Diamond P3700
Rom SPL 1.93
CID HTC_017
The phone was not branded straight from the manufacturer.
The problem is that I tried to flash the phone without doing hard SPL
Cleaned the whole phone and the only thing working now is the connection to the computer Trough mtty. I tried using other ROMS but they stop at 1% and gave me a vendor incorect error or something.
just download it from htc site
I tried but when I select the Serial number it says that the update is not for my phone and doesn't let me download it. and the ones that they have are only updates.
Does anyone have a valid Serial Number that i can use to download update ROM from HTC?
Have you tried any official roms posted around here? like this one: http://forum.xda-developers.com/showthread.php?t=410720
I did that but it started to load the roam into the phone and crashed at 1%,
it gave "Invalid Vendor Id" error and it turns off. Is there like a unversal HTC rom that at very least gets me access to the NANd Memory
I just want to HArd_spl the phone and install a new ROm
Dont even care about the original ROM any more
ekirakosyan said:
I did that but it started to load the roam into the phone and crashed at 1%,
it gave "Invalid Vendor Id" error and it turns off. Is there like a unversal HTC rom that at very least gets me access to the NANd Memory
I just want to HArd_spl the phone and install a new ROm
Dont even care about the original ROM any more
Click to expand...
Click to collapse
Try that one HT828GN27034 and let me know the result.
Oh very nice, thank U very much, I'll try it right now.
All of the Upgrade ROMs just give me invalid Vender ID error message
Doesn't make sense to me though, i tried flashing the Phone With Hard-SPL but for some odd reason it hangs at 0%.
Is my phone dead for good or there might be a way to fix this issue
did u installed OLINEX first?
If ur phone is in 3 color screen try to install Olinex 1.4 and after that flash it with stock ROM.
No thats the thing, I Just Cleaned the phone with Mtty and tried to flash it with WM6.5. but after the cleaning nothing really work out. and i cant even go back to the the old Rom cose I did not back it up.
ekirakosyan said:
No thats the thing, I Just Cleaned the phone with Mtty and tried to flash it with WM6.5. but after the cleaning nothing really work out. and i cant even go back to the the old Rom cose I did not back it up.
Click to expand...
Click to collapse
not even hard reset? did u tried?
yeah man i tried hard reset too, that was no go, I wish there was a way to remove the CID Lock
ekirakosyan said:
yeah man i tried hard reset too, that was no go, I wish there was a way to remove the CID Lock
Click to expand...
Click to collapse
What windows are you using?
I am using windows 7, but i tried the same process on vista and XP, same result, the phone connects to the pc, and right as i try to load one of the ROMs from HTC's website, the thing crashes at 1% and says invalid vendor ID error.
IS there a universal ROM that can be loaded, or my phone is bricked for good?
Perhaps you want to have a look here: http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
Succes!
Oh wow this place has every ROM type but mine, so not fare, u think if i download and try every one of these other ones I might have some sort of luck?
I used HTC's MTTY and figuered that My CID is HTC__017, and the 1.93 Spl
and mine is not listed there.
Hey, I have the EXACT same problem. My diamond is the US 3G Unbranded phone (DIAM110, CID=HTC__017). I've both called and emailed HTC asking for the ROM, but they say that they do not have it. The only way to get it would be to request it from the vendor you bought it from. I got mine as a gift so I can't really do that. Oh, and if you want them to flash it for you, you have to pay like $160. Not cheap. And you know HTC, they'll make up that your main board's fried, and ask you to pay $300. If you have WARRANTY, send ASAP. Mine expired a week ago.
As for flashing random ROMs, most likely this will not work (although you can try). The way your phone determines if it's allowed to install the ROM is by looking at the beginning of the file. If you open up the NBH with an editor, you can see and even change the ID. The problem is, HTC "signs" the file with a 2048 RSA key (2^2048), and if you even change one digit then the signature will be invalid.
So yes, I have the exact same problem, my thread is at: http://forum.xda-developers.com/showthread.php?t=623320, so if you have any luck, or I do, check out that thread.
At this point, the only things that are left to do are to beg HTC or a vendor for the ROM update (I might find HTC developer's mailing address and ask them); find a way to get into Soft SPL, or in other words load into memory a bootloader that would allow flashing of unsigned code; or find a vulnerability that would allow flashing unsigned code (has been done with Trinity).
Also you can try contacting Olipro, cmonex, and pof, but I so far have had no luck.
Hopefully we'll find something.
~codeslicer
Hey man, thanks for the reply, we are pretty much on the same exact boat, am gonna try to contact HTC see if my warranty is still up, and the phone i got it as a gift, I don't have a recipt of a proof of purchase, what do u think i should tell them. And if that doesn't work, I think I am going to try every single 1.93 ROM
in this site.
http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
And also what is your CID. if its HTC_017 then its not here, but there are a lot of them in here so u might get some luck.
let me know how it goes man.
I think i have the solution
can u please confirm clearly as what has happened , hope i have the specific solution .
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.