Trouble with Dopod WM6.. - P3600 ROM Development

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

Related

URGENT help on Hard SPL screen

Hello,
I executed the Hard SPL cab and went into bootloader or some sort of a multi colored screen which says IPL - 0.50 Trin100 and underneath it says SPL 3.03.0000. It connects to my computer and says USB but when I attempt to flash the new WM6 rom which I just downloaded from the rapidshare it resets the machine and continues to remain on this screen of multi colored stuff. I cannot seem to get out of it no matter what I do. What do i need to do to abort the multi colored screen or allow it to flash my HTC trinity with the Dopod WM6 rom?
Thanks,
Gilbert
PS: please don't shoot me if this was discussed elsewhere. i searched and could not fine anyting
happened to me yesterday.
with this screen install AGAIN the hard....
see
http://forum.xda-developers.com/showthread.php?t=316113
and
http://forum.xda-developers.com/showthread.php?t=312499 -page 45
How? I try to execute again the Hard SPL file and it gives me an error and says close window on PC.
Thanks,
Gilbert
it keeps giving me error in connection and i think i bricked my phone i tried to reinstall several times and i get the same results. Poor me.
Same hapen to me, then ive tried to instal over it a another rom and it came to life.
if you're in the bootloader already, try and run the RUU (update program) again on your pc after reconnecting your device.. if that doesn't work, please give details of the error. I don't think you're bricked yet
racerx_ said:
if you're in the bootloader already, try and run the RUU (update program) again on your pc after reconnecting your device.. if that doesn't work, please give details of the error. I don't think you're bricked yet
Click to expand...
Click to collapse
Thanks for your help. I get Error 260:
The update utility cannot connect to your pda. please check usb is connected. click exit to quit.
When I try to run the upgrade alone in XP it starts at 1% then resets the bootloader.
Thanks,
Gilbert
k which upgrade are you running? still trying to get hard spl working, or running the Dopod WM6 upgrade?
*i've been having some troubles upgrading today too, with the WM6.. scary times ha*
racerx_ said:
k which upgrade are you running? still trying to get hard spl working, or running the Dopod WM6 upgrade?
*i've been having some troubles upgrading today too, with the WM6.. scary times ha*
Click to expand...
Click to collapse
I am trying to upgrade the
RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship but i also tried to reflash the 1.23 HTC rom with GPS to see if it would flash since my device is an HTC trinity and not dopod but the same thing keeps happening.
Try to flash PDAVIET version, my came to life doing this
have you tried to flash any other ROM? I was stuck with the same thing, but managed to flash a cooked ROM..
what's your bootloader showing?
if you fail to flash any other ROM, i think you need to try the stack overfow exploit posted here.. http://forum.xda-developers.com/showthread.php?t=308691&highlight=error+206
it's a bit technical, but i think it's your best bet if all else fails.. Pof might be able to help you over there
No matter what i do, what rom i try to flash i get the same damn error message: Error 260 - Connection!!! I am connected so I don't what is wrong with it. I will try some more then decide to take a hammer and break it into 1000 peices.
Thanks.
racerx_ said:
have you tried to flash any other ROM? I was stuck with the same thing, but managed to flash a cooked ROM..
what's your bootloader showing?
if you fail to flash any other ROM, i think you need to try the stack overfow exploit posted here.. http://forum.xda-developers.com/showthread.php?t=308691&highlight=error+206
it's a bit technical, but i think it's your best bet if all else fails.. Pof might be able to help you over there
Click to expand...
Click to collapse
My bootloader is showing the following:
Trin100
IPL-0.50
Trin100
SPL-3.03.0000
Thanks for all your help.
hmmm... i'm not familiar with that SPL number... unless somehow that got halfway updated with the WM6 update.
I think you better head to that thread and try the stack exploit. Did you try loading a cooked ROM to see what happens?
that is it. i give up. i am not experienced in messing with codes. i am going to retire the device for good and use a regular phone. this is crap. thanks for ur help.
oh, that is the SPL version of the new ROM... i guess you weren't using hard spl when you tried to flash it?
ha, well don't give up too quick.. that's one expensive retired device you've got there.
Just keep cool and you should try to install an official Rom to downgrade this SPL !!
Gilbert said:
I will try some more then decide to take a hammer and break it into 1000 peices.
Thanks.
Click to expand...
Click to collapse
Help!
My bootloader is showing the following:
Trin100
IPL-1.00
Trin100
SPL-9.99.CP
When upgrading with the new released WM6 ROM, it keeps failing at 28%
Please help!
best bet for you, is load a different ROM now. Either cooked or official. That will get your device out of crash-proof spl bootloader.
Once the ROM is loaded, if you want to try the official wm6 again, run SSPL first and see if it'll work for you
p.s. i pm'd you my handphone number in case you've got trouble still..
Gilbert said:
My bootloader is showing the following:
Trin100
IPL-0.50
Trin100
SPL-3.03.0000
Thanks for all your help.
Click to expand...
Click to collapse
Hi Gilbert,
Im having exactly the same problem as you. Right now im in the middle of flashing it back down to WM5 (its working at the moment at 17%).
Hopefully after this i will be able to flash back to WM6 (Most probably will go back to AX3L for now).
Hope this helps you out (im quite stressed about it too!)
Edit: I have just finished flashing to Official WM5, now flashing back to AX3L WM6. It works!

The new SPL-3.03.0000 installed by the DOPOD WM6 Installer

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

Stuck In BootLoader After Trying To Install D810 Official ROM

Hi All,
My P3600 is stuck in bootloader after trying to install the official D810 ROM. I used the CID unlock install first, which seemed to work fine, I then tried to install the D810 ROM and it looked like it was working, but stopped at 28% with some kind of communications problem. Recovery does not work... it displays the progress bar, but then goes straight back to the rainbow bootloader screen.
Any help or suggestions appreciated.
Thanks
Rael
Phew... got it working. I removed the battery and replaced, boot loader was still displayed, and then ran the old official WM5 update which seemed to progress from 0 to 100% sucessfully.
Thanks
Rael
Your phone was relocked by the update, and I'm guessing you don't have an actual D810 that's supposed to get this update. The best method to flash this is to follow my post here:
http://forum.xda-developers.com/showthread.php?t=316410
oops, you can use hard SPL in this link:
http://forum.xda-developers.com/showthread.php?t=299659
i got the problem like you when i upgrade my device to wm6 officiel.
After you flash hard SPL Olipro, you can use PC to flash again another rom you like.
(sorry for my worth english)...
People just do NOT know how to read...sigh.

HELP: Cooked ROMS won't flash

I have Orange branded spv m700 and have unlocked and supercid'd the device using pof's tool. I then added HardSpl (Olipro 1.20). All appear to have loaded fine - phone is unlocked and Olipro shows up when put into bootloader.
So, the problem - every time I flash a cooked ROM (Ausdim, NiAx, FiNixNover...?) it won't boot past the first screen. I can rescue the situation by putting device into bootloader and flashing the official WM6 ROM (no radio, no ipl....) and it boots up just fine.
Can anybody help or at least point me in the direction of some good advice?
hmm... odd... can you list step by step what your procedure is for flashing the ROMs
I've done lots of devices - old XDA2i, SPVM600, wifes SPV M700 (unlocked, hard spl etc and flashed away!
This particular device shows IPL 0.50 & SPL 1.20 Olipro. It is unlocked (have o2 sim working in it), and should be SuperCid (I checked the box and radio shows as 1.16.00.00 - pof's patch I believe?). I also re-run HardSpl and Pof's unlock/supercid patch just in case it hadn't flashed properly.
I generally just download ROM and flash via RUU. Occasionally I get the device not responding error so I just re-run RUU from the bootloader screen.
Have tried WM 6.1 and 6.0 cooked roms but all show initial boot screen (numbers along bottom) next screen and then frozen, have waited and waited and nothing. Also, it would not flash back to Mozzers WM5 Orange UK ROM - same symptoms. I thought it was bricked, but the Dopod WM6 flashed perfectly.
Hope that helps - thanks for looking into my problem.
anybody please? por favor........
hmm.. i remember someone having a similar problem but it was some time ago..
two things to try just in case...
1) i'd manually go to bootloader (hard-spl) before flashing
2) Have you tried to flash from SD card? this method seems to provide less problems..
let me know how it goes..
A degree of success - managed to flash WM6 AX3L. All seems to be working. As I recall this is very similar to the official ROM and I used to use it last year because it is very stable. Think I moved on because of the missing email accounts problem. Will happily keep it if I can sort the email problem out. Never really had much fun with the hard reset after loading method - is there another/better way? Just wondering.
Also, now I have a "cooked" rom loaded perhaps it will stop being so sensitive.....!!
How strange! Have just flashed Akeo's new Diamond port ROM and no problems. Not only that, the ROM is FAB!!!

Urgent! My diamond has hardware problem and need to fallback to stock ROM and SPL.

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??

Categories

Resources