Hello.
After upgrading, my Universal dont boot. It's locked at operator start screen.
Hard reset dont unlock it from splash screen.
If I press (ligth + soft reset), select Clean Registry Hive and Format Storage to YES, then reboots and the screen goes to WHITE.
I dont know what is happening...
SOme help please.¡
Try putting it on Boot Loader Mode and flash it back with the old ROM.
Im sorry but the problem it's that i dont have OLD rom :x
see that: http://forum.xda-developers.com/viewtopic.php?t=43592
:wink:
see that: http://forum.xda-developers.com/viewtopic.php?t=43592
:wink:
Any of this post has worked...
Readed from beginning to end.
The Universal upgrade goes well, reboot well, but frezee at logo screen...
Any idea?
jjgarcia said:
Any of this post has worked...
Readed from beginning to end.
The Universal upgrade goes well, reboot well, but frezee at logo screen...
Any idea?
Click to expand...
Click to collapse
Have you tried flashing it back to the OLD ROM or the PREVIOUS ROM you have used and worked on your unit? Try finding another link to download your NEW ROM, sometimes files get corrupted.
I tested with a lot of roms, imate, qtek, t-mob... but nothing works,... i will try to get an original rom and flash from SD card...
get connected :?
bad bad bad, not working...
:evil:
i have the same problem i also, stuck at the splash screen. i have bootloader v1.01 i first unlocked my mda pro with the buzz programm after that i flashed wit the tmobile rom. and it got stuck i reflashed it wit my old qtek rom and it still freezes at the qtek screen.
I think the problem lies on your Boot Loader version. Most of the LATER released ROM is using Boot Loader version 1.00. So anyone who flashed their device with the latest T-Mobile ROM without removing the bl.nbf file got updated to version 1.01. Thus any ROM you try to use won't work.
Try flashing your devices back with Boot Loader version 1.0, then use the old ROMs.
Yes, i have the 1.01 bootloader...
How Can I downgrade to 1.00?
Thanks in advance¡ :wink:
Some idea in downgrade bootloader?
. .. .. .. ... .. .. :roll:
jjgarcia said:
Some idea in downgrade bootloader?
. .. .. .. ... .. .. :roll:
Click to expand...
Click to collapse
Here you go my friend. Just follow the instructions from this thread: http://forum.xda-developers.com/viewtopic.php?t=48590&highlight=boot+loader+1+00
Good Luck Mate!
The solution dindnt worked, because the COUNTRY ID¡¡¡
In the post anybody solved this problem. How can i upgrade? The MaUpgrade_NoID do NOT work.
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
how do you downgrade? no country-id error?
shing said:
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
Click to expand...
Click to collapse
You have to use the Ma_Upgrade_No_ID Tool and I made a short instructions on how to use it in this thread: http://forum.xda-developers.com/viewtopic.php?t=42784&start=50
AND REMEMBER to put your device on Boot Loader Mode before double clicking the Ma_Upgrade_No_ID Tool.
cktlcmd said:
shing said:
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
Click to expand...
Click to collapse
You have to use the Ma_Upgrade_No_ID Tool and I made a short instructions on how to use it in this thread: http://forum.xda-developers.com/viewtopic.php?t=42784&start=50
AND REMEMBER to put your device on Boot Loader Mode before double clicking the Ma_Upgrade_No_ID Tool.
Click to expand...
Click to collapse
yeah, i already did that, but what i wanted to say. it succefully downgraded the bootloader from v1.01 to v1.00. and it also succesully upgraded the Qtek WWE rom. but it is still stuck at the splash screen (the screen shows QTEK wit a sky background and it shows the R 1.09.00 G 42.42.P8 D1.30.77 WWE)
jjgarcia said:
how do you downgrade? no country-id error?
Click to expand...
Click to collapse
i had no country error, i put my mda in bootloader mode and i used the v1.00 bootloader upgrade from the link that the guy posted in this thread.
Related
Hi guys. I have installed loads of ROMs onto my trusty hermes yet today, when trying to flash DuttyThroys Ultra Ultra Lite rom this happened: i downloaded ROM and installed it, it seemed to install fine, got to 100% and then came up with error message stating that Image File was corrupt. Now my hermes is stuck on the multicoloured bootloader screen?!?!?!? I have SPL 2.10. Hard SPL V7 HERM 100 IPL 1.04 (Dont know which of these is relevant to anythin?) .I have read the WIKI on repairing bricks but for my problem it says to reflash any nbh without radio. How is this possible if i cant get my pc to connect to my hermes???
Tried the method of turning off usb connection in active sync, removing battery, reconnecting to usb and running mitty (command SET 14 0) but nothing happens. Mitty says CMD error and active sync doesnt reopen the connection like the guide says! Man i hate this cuz i have now become one of those annoying noobs who has bricked their phone and hassles everyone for help!!!!
Have also tried to flash from sd card but nothing happens, flicks to white screen with LOADING... on it for 2 secons then flicks back to that wonderful multicoloured screen of joy!
Any help will be appreciated guys, cant live without my hermes!!!
Welcome to the fuc... nightmare world of the brick,i'mma in your same situation,now my Tytn is a piece of white stone,and it seems there's no reason to bring it back to live!
I can't stay without my Tytn i do a lot of things with it,Skype,SIP calls,Mail,Messenger,Memo,Internet......i'm in totally despair!!!
you should be able to just reflash a known good rom.
hfam95 said:
you should be able to just reflash a known good rom.
Click to expand...
Click to collapse
Brilliant story! both compelling and rich. But i have already explained that my pc doesnt recognise my hermes so how do you RECOMMEND i flash??
IT could be interesting to make the minimal effort to go and read the wiki.
anyway:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
Better than just cry.
MarcWhittle said:
Brilliant story! both compelling and rich. But i have already explained that my pc doesnt recognise my hermes so how do you RECOMMEND i flash??
Click to expand...
Click to collapse
With the microsd card...
right, its looking good. managed to begin flashing (bar has stopped for ages but having read this is normal im not so scared!) using the SD method. Where my device wasnt superCID i had to use the matching ROM (Orange) to my CID (which incidently i dont know, just downloaded both Orange ROMs).
While im waiting ill try and help you TETSUO! (Im a noob so probably cant!)
Is your device SuperCID??? tell me as much as you can about your device SPL etc
dude, if u read my post u would have seen that i have tried SD method once (sing Black 3.5 not ORANGE ROM), im not crying and im grateful for any help but when i get advice such as 'flash a rom' im gonna be pissed!
And i have read ALL the page on unbricking!!!
It worked!!
One more question, as i have installed a stock Orange ROM do i now need to reinstall HardSPL v7??
Are you on a Win XP or a Vista PC?
XP dude, sorry should have said! and thanks
i went into bootloader, still says 2.10 olipro but when i try to update to new ROM (Black X RC)and pick autodetect it says it says unknown version, use SSPL. it never used to say this so i assume i need to install HardSPL 7 again???
with the tri colour sceen, when you plug the usb cable in does it go from serial to USB ?
what OS have you got ?
just my 2 cents hope it helps.
dude, i have got past that problem and have managed to install an Orange ROM onto it. i only need to know ow whether to install HardSPL v7 again!
sorry slooooooooooooooooow typing
good question hope there an answer,
MarcWhittle said:
dude, i have got past that problem and have managed to install an Orange ROM onto it. i only need to know ow whether to install HardSPL v7 again!
Click to expand...
Click to collapse
just saw your post if ur device is hardspl you just need to supercid your device, If your spl is still showing hardspl and its coming as a error that normally happens to me as well just manually click spl 2.10 and tick (is it hardspl?}
To recap, i have now managed to flash a stock Orange ROM from SD card ( i think the reason it didnt work first time with SD is because device isnt SuperCID and i was trying to flash Black RC, soon as i used Orange ROM (my device is M3100) it worked. I am now back to a fully operational device. I wish to go back to Black but when i AutoDetect what bootloader i have it recommeds SSPL method. Before all my problems it would always automatically pick 2.10?? Does this mean i need to install HardSPL v7 again??
it was HardSPL v7 before all these problems, but im a noob so dont know if it still is?? would installing Orange ROM from SD Card remove HardSPL?? Bootloader still shows SPL as 2.10 oli
MarcWhittle said:
it was HardSPL v7 before all these problems, but im a noob so dont know if it still is?? would installing Orange ROM from SD Card remove HardSPL?? Bootloader still shows SPL as 2.10 oli
Click to expand...
Click to collapse
If you only flash the orange os.nb only then your hardspl wouldnt have changed so its safe to flash your device just manually choose.
If you want to flash hardspl again then do it on a precaution method
Mark,
First of all well done for getting yourself out of a hole. It seems quite difficult to ask for help these days without being shot to pieces even when you have first tried to help yourself by doing all the right things, which is more than can be said for some who come on here asking for help. So well done again.
Re your question, I would reflash Hard SPL anyway to be sure; however before you do that go to the Mr Vanx's guide on hard SPL (forgot the link but type in www.mrvanx.org and you should be taken there) and follow his instructions.
Good luck.
WB
Hallo everbody.
I'd really be glad, if you could help my with my problem:
I currently have bepe's german WM6 ROM v. 0.5 installed on my P3600. Now, the problem is, that I cannot flash anything anymore. When I start any rom update, the device enters boot loader, the progress bar gradually counts to 100% (a little faster, than I remember it doing before). At 100% the device turns off, but doesn't reboot itself. The rom update utility reports a success. When I then restart the device, everything is as before, without any changes.
My installed Hard SPL is SPL-9.99.CP. I tried to flash Olipro's new SPL without any luck. The SPL remains SPL-9.99.CP.
I don't know what to do any more...
have you installed Hard SPL by Oli 1.30????
if yes, downgrade to 1.20 version
psxsnake said:
have you installed Hard SPL by Oli 1.30????
if yes, downgrade to 1.20 version
Click to expand...
Click to collapse
Problem is, I have SPL-9.99.CP installed. It seems, that I even cannot flash to another SPL any more. I just tried to flash Oli 1.30 without any luck.
paranoid2007 said:
Problem is, I have SPL-9.99.CP installed. It seems, that I even cannot flash to another SPL any more. I just tried to flash Oli 1.30 without any luck.
Click to expand...
Click to collapse
SPL 9.99.CP will show with all HARD-SPLs I believe. Try to Flash HARD SPL 1.2 - and then try flashing again.
Lots of people could not flash anything with HARD SPL 1.3 flashed.
nealed said:
SPL 9.99.CP will show with all HARD-SPLs I believe. Try to Flash HARD SPL 1.2 - and then try flashing again.
Lots of people could not flash anything with HARD SPL 1.3 flashed.
Click to expand...
Click to collapse
Could you point me to SPL v. 1.2? I can't find it via the forum search.
nealed said:
SPL 9.99.CP will show with all HARD-SPLs I believe.
Click to expand...
Click to collapse
No you are wrong! SPL 9.99.CP is DES HARD-SPL and CP mean CrashProof.
IPL x.x.50xx is show with every HARD-SPL.
SPL 9.99.CP is okay! Have you tried to flash a original WM5 Rom?
sammy_deluxe said:
No you are wrong! SPL 9.99.CP is DES HARD-SPL and CP mean CrashProof.
IPL x.x.50xx is show with every HARD-SPL.
SPL 9.99.CP is okay! Have you tried to flash a original WM5 Rom?
Click to expand...
Click to collapse
No. If it might help, I'll try. Can you point me to where I can get an original german WM5 Rom?
Ok, found the original ROM Update from the HTC site. Flashed it. This time the device rebooted by itself. Result: I am still stuck with the bepe ROM 0.5. Updating did nothing!
paranoid2007 said:
Ok, found the original ROM Update from the HTC site. Flashed it. This time the device rebooted by itself. Result: I am still stuck with the bepe ROM 0.5. Updating did nothing!
Click to expand...
Click to collapse
try this way! http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
sammy_deluxe said:
try this way! http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
Click to expand...
Click to collapse
Doesn't work. Whenever I try to start Hard SPL, the bootloader shows up for about 5 seconds. Then the screen slowly starts fading to dark grey, so that I can't read anything on the display. Then nothing more happens.
try goin into the bootloader screen on the device first rather that using the update tool first.. this should work
steveecourt said:
try goin into the bootloader screen on the device first rather that using the update tool first.. this should work
Click to expand...
Click to collapse
OMG this worked! Thanks a million. Strangely enough, I tried it this morning without luck.
I also have SPL 9.99 CP and if you put a rom on the flash card it just seems to ignore the file and goes backk into bootloader
steveecourt said:
I also have SPL 9.99 CP and if you put a rom on the flash card it just seems to ignore the file and goes backk into bootloader
Click to expand...
Click to collapse
I have the same SPL but I had never flashed a rom from Flash card.. Could you explain more in the deep how it works? did it once with older Rom's?
I'm a bit confused here I have managed to flash my o2 orbit from the factory o2 wm6 to wm6 premium plus rom, everything worked fine. Then I tried to flash to black & blue 4.3, I got a 302 error, I went through the recovery process and the same happened again. I managed to get the factory rom from the o2 website and it flashes fine every time but whenever I try to flash with any other rom even the premium plus which worked before, I get the 302 error, do I need to CID Unlock it? I'm stuck, Any help would be much appreciated.
lj-_- said:
I'm a bit confused here I have managed to flash my o2 orbit from the factory o2 wm6 to wm6 premium plus rom, everything worked fine. Then I tried to flash to black & blue 4.3, I got a 302 error, I went through the recovery process and the same happened again. I managed to get the factory rom from the o2 website and it flashes fine every time but whenever I try to flash with any other rom even the premium plus which worked before, I get the 302 error, do I need to CID Unlock it? I'm stuck, Any help would be much appreciated.
Click to expand...
Click to collapse
You must run USPL to flash other ROM than your original. If you flash other roms than supplied with your device, you must CID unlock your bootloader and then will be everything fine.
This is why I am confused, how come the wm6 premium plus rom worked first time and now it dosn't . I use the uspl utility first like I did the first time, the spl then changes to 1.11.0000, then I do the rom update. I didn't do a cid unlock the first time but it worked. My brother has the same o2 xda and has also updated to the wm6 premium plus rom from the factory rom, but never did a cid unlock either.
Yes it is a bit strange, but you have to try use the uspl tool again and again, in some version of uspl i hade succes on 5. try. Or look for other version of USPL, maybe you have the old one.
True, I'll try another uspl. How can I tell if it's a new one? I take it I'm doing the procedure correctly ( Run USPL once, then reset, then install rom) ? or run uspl more than once ?
No, run just once, if succesfull the device will reboot, wait untill the activesync will connect to your device and than run romupdate.When possible after the reboot turn to fly mode and wait till activesync will be syncronised with the device and this time run the update.
Thanks for the help mate, I'll keep on trying that
about uspl
hey wat is uspl and from where u can download this utility for wizard ! i m having the same 302 error while flashing a crossbow rom , active sync dont detect my fone now its been bricked n stuked on bootloader screen ! plz help
z0d1ak said:
hey wat is uspl and from where u can download this utility for wizard ! i m having the same 302 error while flashing a crossbow rom , active sync dont detect my fone now its been bricked n stuked on bootloader screen ! plz help
Click to expand...
Click to collapse
Try to search the forum, you will find the uspl tool. If you see the color screen, you can flash just your original rom version.
Hello,
My model ID disappeared from my phone and now I cannot upload anything to it anymore.. It happened while updating to spl 1.40 Olinex... Does anyone have an idea how to upload a Rom without the need of a Device ID? The spl has the right number (I can see that in the Bootloader screen)...
Help?
xanh said:
Hello,
My model ID disappeared from my phone and now I cannot upload anything to it anymore.. It happened while updating to spl 1.40 Olinex... Does anyone have an idea how to upload a Rom without the need of a Device ID? The spl has the right number (I can see that in the Bootloader screen)...
Help?
Click to expand...
Click to collapse
This has happen to my phone as well can you go to bootloader mode and write down all the details here, we might have to contact ccmonex/olinex if its the same which happpen to me,
xanh said:
Hello,
My model ID disappeared from my phone and now I cannot upload anything to it anymore.. It happened while updating to spl 1.40 Olinex... Does anyone have an idea how to upload a Rom without the need of a Device ID? The spl has the right number (I can see that in the Bootloader screen)...
Help?
Click to expand...
Click to collapse
hey. dutty showed me this thread drop me a PM and we can try and fix this.
basically we'll first try to write your modelid back, if that doesn't work, then the last option is flash an SPL that ignores modelid.
cmonex said:
hey. dutty showed me this thread drop me a PM and we can try and fix this.
basically we'll first try to write your modelid back, if that doesn't work, then the last option is flash an SPL that ignores modelid.
Click to expand...
Click to collapse
thanks for responding so fast hope it isnt that bad like it was mines
Thanks for your quick reply's..
Here's my info:
MFG 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
If I take out the battery I can see DIAM100 in the case...
xanh said:
Thanks for your quick reply's..
Here's my info:
MFG 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
If I take out the battery I can see DIAM100 in the case...
Click to expand...
Click to collapse
just pm cmnonex and she will guide you
Another problem is with mtty..
When I start up the program and my phone in boot loader, then mtty crashes immediately when I press a button.. If I disconnect usb and reconnect it again I can type stuff in, but I can type in text without anything happening..
I'm starting to give up on this phone. Maybe I should start seeing it as a expensive pda..
i have the same issue .. me phone is freez then i have to remove battery out .. and restart again ... BUT ... everything is gone ... i cannot doing anything with it ....doesnt matter what kind the rom i upgrade .. still came bootloader ONLY ... i have read many thread about BRICK ... but nothing could help ......please any advise .... HELPP..... please
First of all :
Relax
Got a new diamond today and had the same issues.
What Windows OS are you using ? Do you use WDMC or Activesync ?
What is the driver version of the installed HTC Sync ?
As for mtty :
Next version of QMAT will be fine and will be much more stable than mtty.
As for bootloader :
1. Are you able to connect to mtty, and does it respond to command
"info 2" ?
If yes, fixing it should be no problem.
Contact cmonex, she will be able to help you.
If she isn't able, I and cmonex will figure out what to do next
Cya,
Viper BJK
viperbjk said:
First of all :
Relax
Got a new diamond today and had the same issues.
What Windows OS are you using ? Do you use WDMC or Activesync ?
What is the driver version of the installed HTC Sync ?
As for mtty :
Next version of QMAT will be fine and will be much more stable than mtty.
As for bootloader :
1. Are you able to connect to mtty, and does it respond to command
"info 2" ?
If yes, fixing it should be no problem.
Contact cmonex, she will be able to help you.
If she isn't able, I and cmonex will figure out what to do next
Cya,
Viper BJK
Click to expand...
Click to collapse
Thanks for quick reply VIPER ... my phone run well until i remove the battery ... everything turn out bad ....i use stock rom with is HK version 1.93.871.1
seem to me usb working fine... i can upgrade it ...but ... when is done ...only have bootloader ...First come with ::: DIAMOND TOUCH :: then black out ..when i press power button again .. coming only bootloader screen, no matter what rom i try ... still in bootloader mode.........please help .......
was a double message
viperbjk said:
First of all :
Relax
Got a new diamond today and had the same issues.
What Windows OS are you using ? Do you use WDMC or Activesync ?
What is the driver version of the installed HTC Sync ?
As for mtty :
Next version of QMAT will be fine and will be much more stable than mtty.
As for bootloader :
1. Are you able to connect to mtty, and does it respond to command
"info 2" ?
If yes, fixing it should be no problem.
Contact cmonex, she will be able to help you.
If she isn't able, I and cmonex will figure out what to do next
Cya,
Viper BJK
Click to expand...
Click to collapse
Hi Viper,
Thanks for your reply,
Unfortunately qmat crashes too when I try to send it a command... The version I use here is v395..
I'm using Activesync 4.5.. But this has been disabled...
After a while windows tells me that it finds an unknown device when in bootloader..
The OS is still working and is a HK version 1.93.871.1 as well..
Although I don't know if the OS part is fully ok, since after a hard reset the extra programs get installed and the phone crashes on installing opera...
Could it be that the bootloader itself is not functioning properly making all the tools crash?
My idea is to change the id of the phone to be able to upload a new SPL, and upload a original ROM... At least it should work again then... But I've been trying for more than a week now..
Thanks..
Xanh, which spl is now installed on your device ?
If it is the Hard Spl, try manualspl to reflash spl again. I guess SPL is broken.
Normally, you don't need to change the ID for that.
Changing the ID is only needed when flashing a ROM other than your
original one.
k3vin168 : Also try to reflash SPL. If you've done that and it did work, please contact me via PM. Then either your nand is bad or you need to change the bootmode.
Cya,
Viper BJK
SPL is 1.40.OliNex, but I don't need to change the ID, but it's missing since failing installing 1.40.OliNex SPL.. How does this manual SPL upload work?
No matter which update I try, it will always say that Device ID is wrong... I think NAND is somehow bad, since that's where the device ID is stored right?
xanh,
Could be that nand is bad. There are two regions where the device id is stored.
Memory and NAND. But both can be fixed using Hard SPL (MFG).
PM me, I'll try to help you out of your misery.
k3vin168 said:
Thanks for quick reply VIPER ... my phone run well until i remove the battery ... everything turn out bad ....i use stock rom with is HK version 1.93.871.1
seem to me usb working fine... i can upgrade it ...but ... when is done ...only have bootloader ...First come with ::: DIAMOND TOUCH :: then black out ..when i press power button again .. coming only bootloader screen, no matter what rom i try ... still in bootloader mode.........please help .......
Click to expand...
Click to collapse
Any progress on this one ?
If not, please PM me
xanh said:
SPL is 1.40.OliNex, but I don't need to change the ID, but it's missing since failing installing 1.40.OliNex SPL.. How does this manual SPL upload work?
No matter which update I try, it will always say that Device ID is wrong... I think NAND is somehow bad, since that's where the device ID is stored right?
Click to expand...
Click to collapse
he meant SSPL-Manual.exe from the hardspl thread, but I don't think that would fix mtty.
anyway, have you got my PM. if mtty is hopeless, the other route is what you need (flash SPL without modelid check via special no checking SSPL). I sent you all links and instructions.
(I'd rather not make the files public or all the noobs will start flashing random devices' roms.)
EDIT: I assume your OS is able to boot, but if not, then you need a different set of files, let me know
viperbjk said:
xanh,
Could be that nand is bad. There are two regions where the device id is stored.
Memory and NAND. But both can be fixed using Hard SPL (MFG).
PM me, I'll try to help you out of your misery.
Click to expand...
Click to collapse
for duttythroy, we could not write the modelid back to nand for some reason. lnb said success, then it was still not there in the flash when reading it out afterwards. so I just had him flash a "special" spl
k3vin168 said:
i have the same issue .. me phone is freez then i have to remove battery out .. and restart again ... BUT ... everything is gone ... i cannot doing anything with it ....doesnt matter what kind the rom i upgrade .. still came bootloader ONLY ... i have read many thread about BRICK ... but nothing could help ......please any advise .... HELPP..... please
Click to expand...
Click to collapse
what is your SPL version in tricolour screen?
cmonex said:
what is your SPL version in tricolour screen?
Click to expand...
Click to collapse
i use same as other 1.40 i try all VIPER try to help me out ... but all not working ....just stuck in splash screen ..i try all kind of ROM but still stuck ...i can i do ?? please help
Due to a hardware problem in my Diamond I needed to restore it to manufacturer default. I didn't find a guide to this and since I've done the research anyway I thought I'd put together this little tutorial as the information was somewhat scattered around the forum. I hope this guide will be of use for the community.
My phone was originally branded and sim-locked by 3. After I was through with it, it was SIM-unlocked, security unlocked and had HSPL, custom ROM and a radio ported from another device. The steps below is what I did to restore it to stock. All steps might not be neccessary for you. This procedure might also work for other devices than the Diamond, but of course you need other versions of SPL, ROM etc.
1. Backup everything on your phone to your computer - use activesync, PIMbackup etc and make a copy of your Internal Storage.
2. Make a hard reset (hold vol down + enter and soft reset) and chose to format moviNAND. This step is only neccessary if you want to wipe your Internal Storage before you send the device in for repair, but I recommend it.
3. Go to www.htc.com and download the latest stock ROM (includes stock radio and SPL). You find it under Support and you enter your s/n to get the correct stock ROM for your device, complete with branding for your operator. You can also find stock ROMS here: http://forum.xda-developers.com/showthread.php?t=471699
4. Flash the stock ROM. Now you have stock ROM and Radio on your device. Stock SPL will not be installed until you've replaced HSPL with an older stock SPL and flashed ROM again.
5. Get RUU-SSPL and stock SPL from HERE:
http://forum.xda-developers.com/showpost.php?p=2324829&postcount=39. I used the stock 1.93 SPL. Some instructions and info about restoring stock SPL is in the linked post by cmonex and due credit goes to her. I will repeat some of that info to keep this guide step-by-step. EDIT: Stock SPL 2.03 can be found here: http://forum.xda-developers.com/showpost.php?p=3359191&postcount=390
6. Put the .nbh file from the SPL you downloaded into the same folder as the extracted contents of RUU-SSPL-withoutNBH.zip and run the RUU. This flashes an old stock SPL.
7. Flash your stock ROM from step 3 again. This step is neccessary to get the correct stock SPL on your device, eg. the one that corresponds with the stock ROM you've downloaded in step 3. It was not installed in step 4, because then you still had HSPL. In step 6 you've installed a stock SPL and now the correct stock SPL will flash along with the stock ROM. After this step I got SPL 2.03 on my Diamond.
8. Remove the Security Unlock from your device using the instructions and Security Relocker by Olinex from this post by cmonex: http://forum.xda-developers.com/showpost.php?p=3299516&postcount=492
Now, my Diamond is still SIM-unlocked. I have not managed to find any info about how to restore the SIM-lock, but it is hopefully not neccessary for warranty. As far as I can tell, the unlock doesn't show anywhere, but of course all they need to do is to try a SIM-card from another operator...
If anyone has info about how to restore SIM-lock, then I'll update this guide with that info.
good job...
moderator make this "sticky"
3dward87 said:
good job...
moderator make this "sticky"
Click to expand...
Click to collapse
I second that, it contains links to stock ROMs, that'll hopefully stop a million topics about it lol.
This does not work for me.. However i have a problem. the touch screen of my device is not working.. so i can't get pass the allign screen part .. and for somereason the ruu won't connect to phone when it is at tha part so i can't install the spl.. the only way i can do that i through bootloader and it flashes fine but when i then look in bootloader to see the spl it still shows 1.40 olinex..
Da9L said:
This does not work for me.. However i have a problem. the touch screen of my device is not working.. so i can't get pass the allign screen part .. and for somereason the ruu won't connect to phone when it is at tha part so i can't install the spl.. the only way i can do that i through bootloader and it flashes fine but when i then look in bootloader to see the spl it still shows 1.40 olinex..
Click to expand...
Click to collapse
You're right, I tried it too. Flashing SPL through bootloader doesn't work.
You can try using JumpSPL instead, I've attached it in this post. I don't think JumpSPL will require any screen prompts on your Diamond. You can read instructions.txt in the zip, but it's just really the .bat file so you get an idea of what it's doing. Run the .bat, press enter at the prompts and run the RUU for your stock SPL instead of HSPL when asked. At your own risk, I have not tried this myself.
where can i read more information about jumpspl, how it works and everything?
eranyanay said:
where can i read more information about jumpspl, how it works and everything?
Click to expand...
Click to collapse
Look in the Xda-wiki, search and google, and not just in the Diamond section.
sticky please
this needs to be a sticky topic.
losdrivare said:
You're right, I tried it too. Flashing SPL through bootloader doesn't work.
You can try using JumpSPL instead, I've attached it in this post. I don't think JumpSPL will require any screen prompts on your Diamond. You can read instructions.txt in the zip, but it's just really the .bat file so you get an idea of what it's doing. Run the .bat, press enter at the prompts and run the RUU for your stock SPL instead of HSPL when asked. At your own risk, I have not tried this myself.
Click to expand...
Click to collapse
I have just tried it and it gets stuck where it should run the JumpSPL.exe on the device. After a few minutes it comes with an error:
"ERROR: CreateProcess failed with Errorcode = 30123
- UNKNOWNERROR: 0x000075ab"
This is not good I just think its wierd that because of a broken screen it is impossible for me to get the stock spl flashed back on.
Da9L said:
I have just tried it and it gets stuck where it should run the JumpSPL.exe on the device. After a few minutes it comes with an error:
"ERROR: CreateProcess failed with Errorcode = 30123
- UNKNOWNERROR: 0x000075ab"
This is not good I just think its wierd that because of a broken screen it is impossible for me to get the stock spl flashed back on.
Click to expand...
Click to collapse
Sorry to hear it and I'm afraid I'm out of ideas. After all, my little tutorial is primarily aimed at those whose Diamonds have working screens...
On another note, my Diamond came back from warranty repair and the repair shop had not noticed anything that would void my warranty. In the meantime I got myself a Topaz and now I've sold my Diamond, but I'll be checking this thread from time to time.
Hey thanks bro..!! I need to give mine for reparing..
I have a hardware problem with the reset button.. Do you think I should flash my diamond back to stock? (I don't think they'll check the software right?)
donsalari said:
Hey thanks bro..!! I need to give mine for reparing..
I have a hardware problem with the reset button.. Do you think I should flash my diamond back to stock? (I don't think they'll check the software right?)
Click to expand...
Click to collapse
I would restore it to stock anyway. Some workshops actually look for excuses/reasons why the warranty won't apply so I say you'd definitly be taking a risk if you didn't.
losdrivare said:
I would restore it to stock anyway. Some workshops actually look for excuses/reasons why the warranty won't apply so I say you'd definitly be taking a risk if you didn't.
Click to expand...
Click to collapse
Very true!!! Ok cool... Flashing back to stock!!
Thanks..
Damn.. Hmm anyway then i will have to try the risk and sending it in with hardspl on it.. ! I Hope they won't see it.
Da9L said:
Damn.. Hmm anyway then i will have to try the risk and sending it in with hardspl on it.. ! I Hope they won't see it.
Click to expand...
Click to collapse
Another idea: maybe you can find some a VNC program that also works the "other way" with windows mobile, so that you can get a window on your PC with the screen of your device?
Hi. I'm an orange user and i dont know what SPL i should use to send back to warranty!
DOes anyone can recommend it please?
My Orange ROM is RUU_Diamond_HTC_WWE_1.93.405.1_Radio_Signed_Diamon d_52.29.25.12_1.00.25.05_Ship
UPDATE - i flashed the new rom and i tried to put the original SPL, however it still showing 1.40 Olinex in the bootloader and it still says security unlocked.
Any help please...
Hi I m singapore user i dont know what is the original spl 1.23 ??? i 4get leh can u tell me
bro i try 1.23.000 that version are u sure this is offical stockspl
as i remember it shld be SSPL not SPL somemore when running the tri-boot colour is diffferent from the offical 1
1 . Press volume up restore factory default bla bla bla ..
2 . Press volume down restore factory default and format the internal storage
3 . Press any button to cancel
Where is 2 n 3 ??? gone oridi
herpez said:
Hi. I'm an orange user and i dont know what SPL i should use to send back to warranty!
DOes anyone can recommend it please?
My Orange ROM is RUU_Diamond_HTC_WWE_1.93.405.1_Radio_Signed_Diamon d_52.29.25.12_1.00.25.05_Ship
UPDATE - i flashed the new rom and i tried to put the original SPL, however it still showing 1.40 Olinex in the bootloader and it still says security unlocked.
Any help please...
Click to expand...
Click to collapse
k3nnyboiboi said:
Hi I m singapore user i dont know what is the original spl 1.23 ??? i 4get leh can u tell me
Click to expand...
Click to collapse
If you manage to install ANY stock SPL and then flash the correct ROM for your country and operator then you automatically get the correct SPL too, since stock ROMs include SPL. If you go to htc.com and type in your s/n then you automatically get the latest ROM for your device and operator.
k3nnyboiboi said:
bro i try 1.23.000 that version are u sure this is offical stockspl
as i remember it shld be SSPL not SPL somemore when running the tri-boot colour is diffferent from the offical 1
1 . Press volume up restore factory default bla bla bla ..
2 . Press volume down restore factory default and format the internal storage
3 . Press any button to cancel
Where is 2 n 3 ??? gone oridi
Click to expand...
Click to collapse
I only link to the SPLs provided by olipro and cmonex in the hard-SPL thread. If you need closer info about SPLs I suggest you ask there. I only tried to revert back to stock SPL 1.93 myself and it worked just like described in first post.
Thanks Op
Managed to restore it no problem, but took ages