Ok, talk about it here.
It just installed over my Olipro SPL and before I knew it, it said INVALID VENDOR ID.
Now I can't update to WM6 because of my SPL that is CID locked. I am however able to install an original ROM.
Questions (yet to be answered):
1) Is it possible to run SSPL?
2) Are we able to get Hard-SPL on it again.
If not;
3) Are we able to write a new SSPL that can hack this bootloader.
I don't even know whether it is locked, but I assume they did find out about our SSPL and Hard-SPL.
well i just flashed back to pdaviet's rom from the new WM6 (nothing very impressive about it). I just let the updater push sspl to my phone and it worked. haven't tried loading hard-spl yet.
After flashing to an original rom were you then able to update to WM6?
OK, When I got back in to WM5 i was able to get into SSPL again. It shows SPL-1.07.ds
But we will have to make sure we can rewrite it. I can't test it now, have to go to work. I will check it this afternoon.
OK, i think essentially what this new IPL/SPL does it overwrite your existing, restore any CID locks and vendor ID's as well.
If you have a Dopod branded device from the areas this release is for, you'll have no issues.
I was able to easily update using this rom, then run Olipro's hard SPL after to return to 1.20 Hard SPL
if you unpack D810_SEA_WM6_Upgrade_20070709.exe or RUU_Trinity_DOPODASIA_WWE_3.00.707.16_6275_1.46.30.11_108_Ship.exe with winrar you will see a SPL.nhb file that is the one thats being installed just delete it
TheBlackDragon said:
if you unpack D810_SEA_WM6_Upgrade_20070709.exe or RUU_Trinity_DOPODASIA_WWE_3.00.707.16_6275_1.46.30.11_108_Ship.exe with winrar you will see a SPL.nhb file that is the one thats being installed just delete it
Click to expand...
Click to collapse
already tried it, same stupid problem won't pass through 28%
TheBlackDragon said:
if you unpack D810_SEA_WM6_Upgrade_20070709.exe or RUU_Trinity_DOPODASIA_WWE_3.00.707.16_6275_1.46.30.11_108_Ship.exe with winrar you will see a SPL.nhb file that is the one thats being installed just delete it
Click to expand...
Click to collapse
did that but still same problem with 28%
have you flashed your bootloader back to a hard-spl or kept de original one
TheBlackDragon said:
have you flashed your bootloader back to a hard-spl or kept de original one
Click to expand...
Click to collapse
Tried it with hard-spl and sspl both gave the same result; stuck at 28%
even with "Des SSPL"
Me,too stuck at 28%
if you're putting a new post about getting stuck in the upgrade process (most ppl at 28%), can you please list the steps you took, what bootloader you were using (hard-spl, etc), and what your bootloader shows now...
solved
click here http://forum.xda-developers.com/showpost.php?p=1358479&postcount=132
Works For me
Nice, it worked for me
Still stuck at 28% even after using the CID unlocker
RayEarth said:
Still stuck at 28% even after using the CID unlocker
Click to expand...
Click to collapse
You need SuperCid and SSPL. sorry my engish.
I had the same issue stuck at 28% - I fell back to the last V5 WWE rom and run SSPL (latest Trin) before update to V6 again.
ethos said:
I had the same issue stuck at 28% - I fell back to the last V5 WWE rom and run SSPL (latest Trin) before update to V6 again.
Click to expand...
Click to collapse
You need NEW supercid. Я сам с этими проблемами столкнулся. i dont know this for english.
I had OliPro SPl befor upgrading and have upgraded without any problem. Just run RUU and followed instructions.
I have an idea.
1. RUU flashed SPL 3.03 (so at that moment my phone became cid locked)
2.Probably my phone have the same cid as that ANZ rom. That's why i had no problems.
So all your problems are in new SPL and new logic for flashing device.
for flash new rom you should
1. unpack nbh file
2. use nbhgen to create new nbh with OS/RADIO/EXTROM/IPL only. WITHOUT SPL
3. use SSPL or hardSPL for flash this new nbh
4. enjoy
Related
Hi,
I have the following question. I currently have installed HardSPLv7 (so the device shows IPL-1.04 / SPL-2.20Olipro.
How exactly do I downgrade to my old IPL-1.00 / SPL-1.06 in case I have to hand-in my device for warranty reasons? I already searched through the forum and read that it can be done using sspl somehow but I couldn't find exact instructions.
Can anybody (maybe pof) give detailed instructions on how to downgrade to original ipl/spl from a .nbh with the correct ipl/spl files. I already prepared a .nbh with a spl-1.06 and the corresponding IPL extracted from an original vendor rom and put in my rebuilt dumped rom.
I also have the problem that I don't know where to get IPL-1.00, because on the page where to original roms are listed only the SPL version is noted, but not which ipl is in which rom. Can anybody tell me where I can get an IPL-1.00 .nb file?
Thanks for any help on this. I also think that maybe it could be interesting to put this onto the wiki if I anybody can answer this.
Thanks for any help.
check you PM
It's already pretty much in the Wiki, maybe a 'downgrade' link would be prudent.
Upgrading and cooking: -> MrVanx Hermes upgrade guides -> SPL Downgrade Guide
IPL-1.00 / SPL-1.06? Is this working
Hi,
I just read through the mr vanx downgrade guide and found out that there is a downgrade package with IPL-1.00 and IPL-1.04 and a second one with IPL-1.01 and IPL-1.06.
Now, I have the problem that my device was shipped with IPL-1.00 and SPL-1.06? Apparently this is a strange combination as this is not downloadable at the mr vanx downgrade guide, so my question is. Can I simply extract the IPL-1.00 from one .nbh and SPL-1.06 from the other and recombine them using rombaker, or would a downgrade to this combination screw up my device?
Thanks for letting me know.
I'm on the same boat, I need to downgrade my JasJam to send it in.
I haven't researched at all yet, i've been pretty busy. when I get off work i'll look into it and see if I run into the problem your facing and we can atempt to solve it together.
fone_fanatic said:
I'm on the same boat, I need to downgrade my JasJam to send it in.
I haven't researched at all yet, i've been pretty busy. when I get off work i'll look into it and see if I run into the problem your facing and we can atempt to solve it together.
Click to expand...
Click to collapse
Easiest thing to do is to download your original shipped ROM and extract the NBH file (using dutty's good nbh tool) and grab the IPL or SPL that you need and substitute that for the file from MrVanx. Just be careful what you flash - if you mix up the IPL and SPL file - InstaBrick! Trust me - I know
Do as ToddJG says, download the two files which i refer to in the guide.
Extract the IPLs and SPLs from the two files, mix and match.....BUT BE CAREFULL.......DONT FLASH UNLESS YOUR PREPARED TO DO IT.
ipl 1.00 and spl 1.06 will be fine.
make a single nbh from the mix and match combination then flash with customRUU.
What if i'm trying to flash the original shipped rom.. and i do the first step in your guide, then simply flash the shipped rom, or do i still have to extract the ipl and spl? (they're already extracted just wanting to know if its redundant if i recompile it with the rom i extracted them from.)
Ok, just succesfully downgraded to IPL-1.00 and SPL-1.06. Now i'm gonna flash back to an imate shipped WM5 rom. but one problem with that... clubimate.com is only showing the extroms which are around 6mb when downloaded.. where can i get the full imate rom?
also mrvanx what do u mean by this:
As with other downgrade guides this is NOT intended as a guide for claiming the warranty of the device having flashed components which are not authorised by the manufacturer or carrier.
Click to expand...
Click to collapse
?
fone_fanatic said:
Ok, just succesfully downgraded to IPL-1.00 and SPL-1.06. Now i'm gonna flash back to an imate shipped WM5 rom. but one problem with that... clubimate.com is only showing the extroms which are around 6mb when downloaded.. where can i get the full imate rom?
also mrvanx what do u mean by this:
Click to expand...
Click to collapse
It means that if you flashed unauthroized phone parts (like unofficial WM6 roms, radio upgrades and so on you have void your warranty). Of course if you can downgrade to your old rom nobody will notice that you did that.
But you have to be very careful on downgrading if you have also upgraded your radio I thinkk, cause you can brick your device (means having "NOGSM" after downgrading), see this note from mr. vanx downgrade guide for wm5:
NOTE: If your radio version is currently HIGHER than 1.27.00.00 then it is very likely the radio bootloader is version 0108, this WILL NOT allow the radio to be downgraded to a radio containing BL 0106 and will result in a "NO GSM" error.
Click to expand...
Click to collapse
Maybe you should follow mr. vanx downgrade guide for wm5 to make sure your on the safe side.
I thought he meant that it is still noticeable if you downgrade the IPL and SPL that it would be detected during warranty repairs but thats not the case...
I emailed I-Mate and they gave me an RMA# and had me purchase the $60.00 Diagnostic package from PocketPcTechs.com(They handle imate warranties in the US). So i did that, they emailed me with a form i should fill out and include it with my device when i ship it...
Did that, they sent me an email when they recieved my device, 15min after that i recieved another email that they were working on my devic, then Early the next day i get an email saying repairs are complete and its being ready to get shipped back to me... 15min an email with a tracking number saying its shipped....
Everything worked so smoothly, warranty was accepted, hopefully everything will be good when i get the device back (which should be today) I want to get rid of this ****ty iphone so bad!
todd_jg said:
Easiest thing to do is to download your original shipped ROM and extract the NBH file (using dutty's good nbh tool) and grab the IPL or SPL that you need and substitute that for the file from MrVanx. Just be careful what you flash - if you mix up the IPL and SPL file - InstaBrick! Trust me - I know
Click to expand...
Click to collapse
MrVanx instruction working just fine, however do not put your Hermes into Bootloader Mode. I've been trying the steps with my hermes in BootLoader Mode for many many times and it does not work. Leave it on OS mode. (Today) screen before you run the CustomRUU. Hope this help
why is every one so paranoid about this....
has anyone EVER heard of a warranty being denied because of the software on it?
GldRush98 said:
why is every one so paranoid about this....
has anyone EVER heard of a warranty being denied because of the software on it?
Click to expand...
Click to collapse
Yup cingular/ att will charge you for out of warranty work if its a different rom
Please help
Guys I am having the same issue, I am exchanging my phone and need to downgrade. I followed MrVanx guide and downgraded to 1.10.olipro and now need to flash the original Cingular 8525 SPL back to the phone. The SPL that was shipped was 1.11. Where can I find the file to flash? I have been trying to find it with no luck. Could someone please help me out with this? Thank you very much!
thedude0420 said:
Guys I am having the same issue, I am exchanging my phone and need to downgrade. I followed MrVanx guide and downgraded to 1.10.olipro and now need to flash the original Cingular 8525 SPL back to the phone. The SPL that was shipped was 1.11. Where can I find the file to flash? I have been trying to find it with no luck. Could someone please help me out with this? Thank you very much!
Click to expand...
Click to collapse
Go to the wiki > hermes > original shipped wm5 roms and then decompile the rom with duttys good nbh tool. You will see an spl.nb file. Make that alone into an nbh file using duttys good nbh tool. Then flash to your hermes using the custom ruu.
Since you have successfully followed mrv's guide, you should probably know what all those things are.
todd_jg said:
Go to the wiki > hermes > original shipped wm5 roms and then decompile the rom with duttys good nbh tool. You will see an spl.nb file. Make that alone into an nbh file using duttys good nbh tool. Then flash to your hermes using the custom ruu.
Since you have successfully followed mrv's guide, you should probably know what all those things are.
Click to expand...
Click to collapse
Man thank you so much for the fast reply! Having downgraded to 1.10.olipro and downloading the original rom exe, when I ran it (accidentally) it flashed the 1.11 SPL back to the phone for me. I didn't even have to use duttys tool. THANKS AGAIN!
thedude0420 said:
Man thank you so much for the fast reply! Having downgraded to 1.10.olipro and downloading the original rom exe, when I ran it (accidentally) it flashed the 1.11 SPL back to the phone for me. I didn't even have to use duttys tool. THANKS AGAIN!
Click to expand...
Click to collapse
No problem. I thought you already had the rom you wanted, but just needed to change the spl. Guess I gave the overly complex solution!
marcelser said:
Hi,
I have the following question. I currently have installed HardSPLv7 (so the device shows IPL-1.04 / SPL-2.20Olipro.
How exactly do I downgrade to my old IPL-1.00 / SPL-1.06 in case I have to hand-in my device for warranty reasons? I already searched through the forum and read that it can be done using sspl somehow but I couldn't find exact instructions.
Can anybody (maybe pof) give detailed instructions on how to downgrade to original ipl/spl from a .nbh with the correct ipl/spl files. I already prepared a .nbh with a spl-1.06 and the corresponding IPL extracted from an original vendor rom and put in my rebuilt dumped rom.
I also have the problem that I don't know where to get IPL-1.00, because on the page where to original roms are listed only the SPL version is noted, but not which ipl is in which rom. Can anybody tell me where I can get an IPL-1.00 .nb file?
Thanks for any help on this. I also think that maybe it could be interesting to put this onto the wiki if I anybody can answer this.
Thanks for any help.
Click to expand...
Click to collapse
Hey, maybe i come to late,
I had the same "problem", I had the Screen Aligment Issue. And I really wonderd myself if o2 have problem with my "Schaps ROM Version HardSPL" BUT there was no problem, they solved my Screen Aligment Issue. Afterwards I asked, what actually is bad for warrenty. Upgrading the Bootloader is no problem. But CID (Costumer ID) unlocking will may be evil. Anyway's for myself (the SA-Issue) was a hardware issue which has nothing todo with software facts like upgrading the bootloader...
dont be worried... i guess there will be no prob...
can't seem to get this upgrade to work. the updater stops at about 28 percent for me with an error (286? i think) and after that i'm stuck in bootloader. Every time after that, the updater wont even start.. (a different error).
i can flash successfully a cooked ROM, but can't get the official one to work. Could it be a conflict with Des' crash-proof SPL? That's the only thing i can think of at this point..
To me said invalid device id, and got stuck on the boot loader
try back to any old offical ROM
and then copy SSPL to PDA and run it on PDA
when bootloader appear, run WM6 offical updater
I got same problem too and get fix
good luck
update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?
It installs a new bootloader that can't be hacked by the previous hacks I think.... I'm stuck in it too...
SPL-3.03.0000
racerx_ said:
update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?
Click to expand...
Click to collapse
Hi racerx,
I've encountered the same problem as your, stuck at 28% ERROR [286] while flashing, and couldn't go over it even after recovery process following the instruction.
Could you please explain a bit more details about how to go back to Olipro's hard-spl and enter into bootloader?
Thanks, eager to flash the new ROM...
Well I was able to get out of it by running Pof's CID RUU Unlocker, however, it errors after 7%, and resets. It gets past the bootloader, however, it hardreset the phone...eh.
IT happened to me too - Update Error.
So should i go back to Official WM5 then update to WM6 (i had AX3L installed before and i just had to reflash back to AX3L coz of the error from WM6).
Kinda scared me.....LoL
well, to start with i had Des' Crash-Proof SPL on my phone... so after the updater hung at 28%, i remained in Des' bootloader. I then ran the RUU for pdaviet's ROM, which flashed successfully. After that was on and my trinity was up and running, i flashed Olipro's hard-spl. Then manually put it in bootloader again, and flashed the official ROM.
Let me say this, though. At this point, i think you should be content to get your device out of bootloader mode. This Dopod WM6 doesn't have so much to be desired in it compared to cooked ROM's on this forum, plus your bootloader will be stuck at version 3.xxxx which i don't know if anyone is sure how to deal with yet. I'm regretting flashing mine to official version. Should have waited for a chef to pack it up for me.
what does your bootloader say?
You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.
yeah saw your post on the other thread.. thanks for the tip! talk about a stressful morning haha..
i was waiting for this ROM cause my activesync has mysteriously stopped working for a couple of weeks. so i was going to flash and take it to the service center. The miracle of it, was after my device hung and i reflashed pdaviet's rom, my activesync mysteriously works now even though i reflashed a million times before trying to get it going haha..
new spl is needed for flashing new radio rom with cid locked device.
So that's why RUU reflashes SPL at first.
U could simply reflash HArd spl back by using sspl
mUn, when can we expect your much anticipated "Indigo" rom using this offical WM6 base??
Genius! thanks for the tip mun...
all i can say is one word....
INDIGOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!
I also got Invalid vendor ID when I tried to flash for the first time. But it flashed just fine after I put it into bootloader mode. Give it a try..
Flashed my mine in a breeze from LSVW version 27/05/07.
myppcsg said:
Flashed my mine in a breeze from LSVW version 27/05/07.
Click to expand...
Click to collapse
still same problem
can you post the RUU files plz
mxlaser said:
You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.
Click to expand...
Click to collapse
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....
geoffreyhan said:
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....
Click to expand...
Click to collapse
hehe i did that many time this day maybe hmmm 5 or 6 and im still doing that
try to use another version of RUU (the older one)
ps. plz don't post messages about indigo in other tgreads ) if u want to ask - so ask in mine thread.
I'll flash official rom today and then will make some conclusion ) but i thibk that indigo will be based on oficial release
Stuck at 28% of upgrade
phone is showing 4 colors and does nothing
PLEASE PROVIDE LINK TO BE SAVED
LINKS AND INFO WHAT TO DO IN DETAIL
I AM NOT A COMPUTER GUY
flash official rom back. Then download this rom
http://rapidshare.com/files/42141641/Wm6_Official.zip
and flash that one,
link for official rom ?
i remind you the phone is at the 4 colors mode
this page has all official roms ever made for trinity
http://wiki.xda-developers.com/index.php?pagename=Trinity_Upgrades
pkaza said:
link for official rom ?
i remind you the phone is at the 4 colors mode
Click to expand...
Click to collapse
Don't panic, the phone is not dead. You will get it fixed. Just follow the instructions given, there is a solution.
updated with official rom
hardspl does nothing
other way
?
Help me too!!! I don't even have an official ROM for my Orange m700
ward777 said:
Help me too!!! I don't even have an official ROM for my Orange m700
Click to expand...
Click to collapse
You could try this fix http://forum.xda-developers.com/showthread.php?t=316313&page=5
I don't think so. My Hard-SPL was overwritten and now has the 3.0 version and not SPL version 9.99.
9.99 is NOT Hard-SPL, it's Des's Crashproof spl which is not even trying to prevent itself from being overwritten.
OliPro?
Hello
What about OliPro SPL-1.20.Olipro with IPL-0.5
Can it also be overwritten or wich hard spl do I need first to flash?
Roman
don't worry , simply follow the instruction and reflash it again with the new rom , then it will pass through the 28% ...
Shadowmite said:
9.99 is NOT Hard-SPL, it's Des's Crashproof spl which is not even trying to prevent itself from being overwritten.
Click to expand...
Click to collapse
I know that
But I did have Hard-SPL and now it's gone so it will get overwritten when installing this ROM as well
tony800708 said:
don't worry , simply follow the instruction and reflash it again with the new rom , then it will pass through the 28% ...
Click to expand...
Click to collapse
What instructions?
ward777 said:
What instructions?
Click to expand...
Click to collapse
I guess you're in a pickle. There must be a way around not having an official Orange rom. Have you tried the SD card method from an Orange rom dump? Otherwise, the rom cookers should be able to come up with something. With all of these people trying these roms certainly you must not be the only one with an Orange phone. Good luck .
Hi Guys,
I am also stuck @ bootloader. I have the original rom, but how do I flash this back? It keeps on telling me that it cannot detect the phone. What can I do? Thank you!
You can flash the spl from the bootloader via mtty, but that's not something Ive seen clear instructions on how to do... you might want to log into #xda-devs in freenode IRC and get stepped through it.
If you're stuck at the bootloader, just try running the hard-spl flash right from there...
ward777 said:
I know that
But I did have Hard-SPL and now it's gone so it will get overwritten when installing this ROM as well
Click to expand...
Click to collapse
Yeah, I thought deleting 'SPL.nbh' would prevent the RUU from installing the new SPL but the Hard-SPL got overwritten on flashing.
Kris
there are 2 spl entries in the release... spl.nb and spl.nbh... you have to remove both. also I'd remove the ipl.nb...
These are the files inside the exe:
EnterBootloader.exe
ErrorBattery.fig
ErrorUSB.fig
ModelID.fig
rapitool.exe
README.doc
ROMUpdateUtility.cfg
ROMUpdateUtility.exe
RUUGetInfo.exe
RUUResource.dll
RUU_signed.nbh
SPL.nbh
I suppose you meant to remove the .nb entries inside RUU_signed.nbh
Kris
First of all, I have studied quite some threads about flashing the Diamond in the past days, read the stickies and gone through the pages at modmydiamond.
I now set the following plan, and I would really love to have some confirmation before I break something
If I understand it correctly the procedure is like this:
- flash Hard-SPL signed/unsigned
- optionally update radio ROM
- flash desired operating system ROM.
The following is the case: I have a sim-unlocked (from factory) T-Mobile MDA Compact IV, a DIAM200 with the Dutch 1.37.114.3 ROM, accompanied by the 1.37.0000 SPL. The installed ROM is heavily branded by T-Mobile, and I want to install the non-branded HTC 1.93 Dutch one.
As a preparation I downloaded the signed Hard-SPL 1.30 from this thread, and installed it, and verified it was installed.
Since I wanted to install the non-branded HTC ROM I grabbed RUU_Diamond_HTC_NLD_1.93.404.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe file from here and tried to install it but no success: it got stuck at 0%. (Doesn't that mean that it won't flash unsigned ROM at signed (S)SPL?) What I want to do now is install the 1.40 Hard-SPL unsigned and attempt to install the HTC ROM again.
Now my question is: can I do this safely without transforming my device into an expensive paperweight? Thanks for reading
Hello
I found a simple way for flashing.
Have a look here : http://forum.xda-developers.com/showthread.php?t=423978&page=2
I took the gamble and succeeded. This is how I did it:
- Flashed Hard-SPL 1.40 unsigned using the utility
- Extracted the nbf from the downloaded exe file (Dutch official HTC ROM) using NBHUtil 0.92, see http://forum.xda-developers.com/showthread.php?t=409425
- Joined the OS & Splash together, leaving out the SPL and Radio ROMS, made sure the CID and Model ID were correct (see that thread)
- Flashed it with the RUU the Dutch ROM came with.
...
- Profit.
If you want only the original HTC rom, you can install it by the original update software provided by HTC.
Simply connect your Diamond through USB / active sync and luch the update utility.
You can find last 1.93 here : http://www.files.to/get/342564/gn2jg25lvr
Good luck
Well in my case the combination of Hard-SPL 1.30 and the official HTC 1.93 updater wouldn't let me update the phone's software: I got stuck at 0%. Further inspection of the nbh file showed me it was aimed at DIAM10000. I am not sure if that made the difference or that the Hard-SPL blocked the flash, can't tell.
btw dominique2222, the file you linked in post #4 seems to be a German (GER) file, not Dutch (NLD)
spone1 said:
I took the gamble and succeeded. This is how I did it:
- Flashed Hard-SPL 1.40 unsigned using the utility
- Extracted the nbf from the downloaded exe file (Dutch official HTC ROM) using NBHUtil 0.92, see http://forum.xda-developers.com/showthread.php?t=409425
- Joined the OS & Splash together, leaving out the SPL and Radio ROMS, made sure the CID and Model ID were correct (see that thread)
- Flashed it with the RUU the Dutch ROM came with.
...
- Profit.
Click to expand...
Click to collapse
Finally a guy who persueded me to go and do it
Thanks your hits helped me out and now I have a real Diamond.
BTW how about the hard buttons? I recall that they are swapped between MDA Compact IV and HTC Diamond ?
The hard buttons will work fine, in case you didn't find that out already
spone1 said:
The hard buttons will work fine, in case you didn't find that out already
Click to expand...
Click to collapse
Yep I noticed its all OK and I was actually surprised but the position ( as it looks ) does not care the keyboard matrix address appearently is fixing this
Hi,
My Diamond has no response on the screen, so I think I need to return to factory for repairing. However I have difficulties in falling back to stock ROM and SPL.
From the Wiki:
---------------
STEP BY STEP HOW TO RETURN TO STOCK SPL - FOR WARRANTY REASONS ONLY!
0. be sure to first restore stock OS, and stock radio. stock SPL is always to be done last!!
...
-----------------
I can't flash my ROM to latest HK WWE CSL ROM (2.03) as it just stopped at 0%. I'm using SPL-1.30.OliNex.
Questions:
0) Why? Any step I've missed? I've just copied the .NBH from HTC official ROM download. Should I get the .NBH from the Wiki instead?
1) Should I flash to v1.93 (the very beginning of the ROM)?
2) Must the RADIO be flashed back as well? or the above Stock ROM has included the RADIO already?
3) Anyone can give me a reference on the step-by-step in details...
Thanks!
Please help...
F810
Questions:
f810 said:
0) Why? Any step I've missed? I've just copied the .NBH from HTC official ROM download. Should I get the .NBH from the Wiki instead?
Click to expand...
Click to collapse
If the latest was the offical from the site then you could use that - as you are having issues flashing this with 1.30 HSPL, I would suggest updating that to 1.40
f810 said:
1) Should I flash to v1.93 (the very beginning of the ROM)?
Click to expand...
Click to collapse
This might be a easier option and should work woth the 1.30 HSPL
f810 said:
2) Must the RADIO be flashed back as well? or the above Stock ROM has included the RADIO already?
Click to expand...
Click to collapse
This is recommended
f810 said:
3) Anyone can give me a reference on the step-by-step in details...
Click to expand...
Click to collapse
Its really straight forward like the WiKi suggests
This Thread may help
Thanks a lot.
Re Q3, so do you mean if I extracted the stock NBH, it's only OS but not including RADIO? If so, I will get the RADIO from wiki page later. Would you please clarify for me?
After your information, I think the steps in Wiki are clear. Thanks.
If this is HK ROM is the one you have downloaded from HTC PAGE then it has a radio included
Since my Diamond is totally malfunction in the touch screen, I can't response to all the confirmation & prompts...
I've failed to install Stock ROM and tried your recommendation on upgrading to HSPL 1.40. There was a confirmation on running the program in my Diamond and I can't press YES and now my diamond is just like bricked.
I've also tried pressing VOL DOWN + Reset to connect the Diamond via USB. The ROM Update Utility has "successfully" update the HSPL, but actually when I hard reset it and found it's still running 1.30... Can I just use this approach to fallback to Factory status??
Anyone has good idea on how to fallback to Factory Stock ROM, RADIO and SPL, provided that my screen has totally no response to me?
PLEASE...PLEASE...PLEASE help.
You will not be able to update olipros Hard SPL in bootloader mode as the SPL is protected and the 1.30 will prevent this although show its been done.
What you will need to do then is just load a 1.93 ROM from boot loader. the were some in that link i posted earlier. as to reverting to the default SPL - you may be luck not to need the screen for any confirmation. but running a new SPL to overwrite Oli's you will need to use windows and the RRU
I've tried to load 1.93 ROM to my diamond but failed on OliNex 1.30. The link in modmydiamond.info on OliNex 1.40 Signed seems not correct, as it's still 1.30 after flashed. I've then flashed UNSIGNED 1.40 OliNex SPL (also downloaded from modmydiamond.info) and now flashing the 1.93 ROM in progress from bootloader.
I will flash the Stock SPL through the Bootloader after that...I hope I can successfully fallback and get it repair...
Last question (I hope), the stock SPL should be 1.37 so I want to confirm whether it can boot 1.93 ROM.
Thanks a lot!
Because these Unsigned HARD SPL 's are write protected.....you will fail all the time. Not sure if stock SPL can undue the write protection but if you still get stuck after you try then in order to bypass write protection I know Jump SPL allows for this.
band27 said:
Because these Unsigned HARD SPL 's are write protected.....you will fail all the time. Not sure if stock SPL can undue the write protection but if you still get stuck after you try then in order to bypass write protection I know Jump SPL allows for this.
Click to expand...
Click to collapse
you're right. When I flash the Stock SPL, it is "successful" but actually it doesn't update the SPL (i.e yet running OliNex 1.40). Where can I get the Jump SPL?
Here you go....I did a search
Hi,
Sorry to use this thread but im also trying to install back to my original Diamond ROM and am currently using the rom developed by Diamond Project (1.93.456.2WWE) and i kept flashing it back using Signed V1.93 RUU and apprently the Diamond project words still keep showing out when i start my phone!
How do i completely remove the Diamond Project thing? Thank you!
Read this............Scroll to Post #39
http://forum.xda-developers.com/showthread.php?t=400950&page=4
band27 said:
Here you go....I did a search
Click to expand...
Click to collapse
I also got that but it's not win32 program... I believe it's running on the Diamond. But I've hard reset, and never able to setup as it's screen was not functioning now...
kawatsu said:
Hi,
Sorry to use this thread but im also trying to install back to my original Diamond ROM and am currently using the rom developed by Diamond Project (1.93.456.2WWE) and i kept flashing it back using Signed V1.93 RUU and apprently the Diamond project words still keep showing out when i start my phone!
How do i completely remove the Diamond Project thing? Thank you!
Click to expand...
Click to collapse
That ROM had a different boot image - so you need to replace that by flashing another splash .NBH file using RUU.
Original splash can be found HERE
and if needed CUSTOM RUU HERE
Just un-zip these and put the splash file in the same folder as the Custom RUU and run the RUU - the flash should take a few seconds and viola - bye bye Diamond project splash.
f810 said:
I've tried to load 1.93 ROM to my diamond but failed on OliNex 1.30. The link in modmydiamond.info on OliNex 1.40 Signed seems not correct, as it's still 1.30 after flashed. I've then flashed UNSIGNED 1.40 OliNex SPL (also downloaded from modmydiamond.info) and now flashing the 1.93 ROM in progress from bootloader.
I will flash the Stock SPL through the Bootloader after that...I hope I can successfully fallback and get it repair...
Last question (I hope), the stock SPL should be 1.37 so I want to confirm whether it can boot 1.93 ROM.
Thanks a lot!
Click to expand...
Click to collapse
I think as long as the SPL is changed and the ROM is of the original language the I think it should be OK to send back like that
f810 said:
you're right. When I flash the Stock SPL, it is "successful" but actually it doesn't update the SPL (i.e yet running OliNex 1.40). Where can I get the Jump SPL?
Click to expand...
Click to collapse
As said before; you should be able to successfully run the stock SPL using RUU - if you are trying this via bootloader it will not work.
Which is the original SPL?? 1.23, 1.34 or 1.37? I do recall taking a picture of the original SPL when i 1st got the Diamond for days like that but i just can't find it now
I'm bought it from Malaysia. Anybody can help me confirm this??
R3PUBL1K said:
As said before; you should be able to successfully run the stock SPL using RUU - if you are trying this via bootloader it will not work.
Click to expand...
Click to collapse
I've tried to connect to ActiveSync successfully although the Initial Setup wizard on my Diamond. I've then run the RUU from RUU-SSPL-withoutNBH.zip and put the stock SPL .NBH file into the extracted directory. It can retrieve my device info, and when I confirm the update of ROM, after 3-5 sec it said about connection failure. I can browse the Internal Storage at the moment yet.
I've then tried similar thing using the Custom RUU inside the package diamond-hspl-1.34.zip. This time I can see 100% update. When I press VolDown and reset, the SPL is still v1.40 ONliEx.
What's wrong with my procedures above?
f810 said:
I've tried to connect to ActiveSync successfully although the Initial Setup wizard on my Diamond. I've then run the RUU from RUU-SSPL-withoutNBH.zip and put the stock SPL .NBH file into the extracted directory. It can retrieve my device info, and when I confirm the update of ROM, after 3-5 sec it said about connection failure. I can browse the Internal Storage at the moment yet.
I've then tried similar thing using the Custom RUU inside the package diamond-hspl-1.34.zip. This time I can see 100% update. When I press VolDown and reset, the SPL is still v1.40 ONliEx.
What's wrong with my procedures above?
Click to expand...
Click to collapse
I think I miss the step of running the SSPL-Manual.exe because of my screen is not responding... Anyway for me to put it into the Windows Startup Folder?? When I use ActiveSync I can't see Windows directory.
Please...please...I miss this step only...
f810 said:
I think I miss the step of running the SSPL-Manual.exe because of my screen is not responding... Anyway for me to put it into the Windows Startup Folder?? When I use ActiveSync I can't see Windows directory.
Please...please...I miss this step only...
Click to expand...
Click to collapse
Can anyone help??