Related
Hello
I've searched on this forum and can't find the answer to my specific question.
I upgraded a while back to MrClean AKU 2.3 and now I need to downgrade because the unit needs to be sent back under warranty due to screen alignment issues.
So I unpacked the i-mate WWE ROM, and replaced the ROMUpdateUtility from that with the ROMUpdateUtility_Wizard_NoID.exe, which I downloaded from the XDA FTP site. (This is because using the standard one supplied gives a ROM upgrade error 296: UPGRADE ONLY error.)
As far as I can make out, the ROMUpdateUtility_Wizard_NoID.exe is just patched to not validate the current version when upgrading.
"Brilliant, this should work", I think.
But I get the following error:
"ERROR [238]: FILE READ... the update utility cannot open the requested file. Please check your update utility"
(see here http://static.flickr.com/111/306871020_8aa37f337e_o.gif)
Please help, anyone, I am coming up to the end of my warranty period and reeeeally want to get this crappy broken screen alignment problem sorted!
Thanks in advance
* bump *
Hope it's not considered rude to bump here, just would love to solve this problem as tis driving me a bit mad
Many thanks in advance
msmobiles.com:
This error message may appear when, for some unknown reason, the ROM image on the phone is corrupt. Download the whole RUU and try again.
Click to expand...
Click to collapse
Hey
Thanks for the tip. You were right, it must have been a corrupt .nbf file.
I tried to downgrade and the progress bar started and finished and all seemed to go well.
But when I boot up again I get the white MrClean ROM splash screen still!
Is it possible the update was done but the splash screen was not replaced?
Or perhaps the update wasn't actually done? Which version number do I look for? I used the .nbf file packaged in with the imate ROM K-JAM_WWE_1010903_106_10110_ship.exe
Please help!
try using this rom to downgrade with... after that you should be able to upgrade to any official rom. Make sure that you pick an official one as the above rom downgrades the ipl/spl as well.
ohh... and make sure that you restore the CID lock as well, they might be get rather cranky otherwise...
Good luck
Hello
Thank you so much for the reply, I really appreciate the advice. I would feel so out-there-on-my-own without it! I bought the imate off contract from expansys and it was really expensive and so really don't want it to end up a brick as I can't afford another right now!
I successfully downgraded to that QTEK custom ROM.
But now when I upgrade again to K-JAM_WWE_216901_2169101_020710_ship (latest).exe from that QTEK ROM, it doesn't work! Upgrade error again [ERROR 296]
Here are the screens I get:
http://static.flickr.com/114/309671629_756dc86b9d_o.gif
http://static.flickr.com/107/309671652_327adfb432_o.gif
Thanks again
Mat
Just to clarify... is the phone CID-locked? You might also want to try flashing it with the K-JAM_WWE_1010903_106_10110_ship.exe ROM before upgrading it... you can also try putting the phone in bootloader mode, press and keep pressed both the keys on the right side and then insert the pen in the resetbutton, before trying the upgrade...
EDIT: msmobiles.com shows the following regarding the particular error:
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
Click to expand...
Click to collapse
Hey Nomad
Thanks again for the advice. This is all really really helpful. Going to try what you suggested a bit later.
I think I CID unlocked the phone - to be honest it was a while ago and I just remember blindly following someone's instructions (I was at a point of desperation at the time for another reason!)
Either way, I am pretty sure it would have to have been CID unlocked because I flashed the ROM from the imate default one to the MrClean one.
I did some initial looking around about CID relocking the device but still not sure how. Does the lockiwiz give the option of locking the CID as well as unlocking it?
Thanks!
Mat
I flashed from the QTEK custom ROM to the K-JAM_WWE_1010903_106_10110_ship.exe after doing that special reset whilst in the bootloader. This flash upgrade worked but again it didn't remove the splash screen from the QTEK custom ROM.
But now whenever I try to flash to the latest imate ROM K-JAM_WWE_216901_2169101_020710_ship.exe using the default RUU I get ERROR [296] UPGRADE ONLY.
And when I try to flash to the same ROM using the noID RUU I get ERROR [238]: FILE READ ERROR.
(On that last one, I have re-downloaded both the noID RUU and the extractable archive K-JAM_WWE_216901_2169101_020710_ship.exe from the XDA FTP.
So, I'm still unable to get my ROM to the imate version! Many thanks for your help!
Mat
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!
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
I am trying to udate my M700 to Hard SPL 1.20. I follow the steps as per the trinity guides. I get to the screen where it says update the ROM Version from 1.23.61.5 to 1.20. I click on next and it says you are ready to update your ROM image. I click on next again and the screen for showing the % of update done when the device resets itself to the screen showing TRIN100 IPL-SSPL by Des and SPL-1.07.ds. However, the update screen changes to error code #246 device not responding and loses activesysnc connection. I also have exactly the same problem when trying to update the Radio as well.
repoman1966 said:
I am trying to udate my M700 to Hard SPL 1.20. I follow the steps as per the trinity guides. I get to the screen where it says update the ROM Version from 1.23.61.5 to 1.20. I click on next and it says you are ready to update your ROM image. I click on next again and the screen for showing the % of update done when the device resets itself to the screen showing TRIN100 IPL-SSPL by Des and SPL-1.07.ds. However, the update screen changes to error code #246 device not responding and loses activesysnc connection. I also have exactly the same problem when trying to update the Radio as well.
Click to expand...
Click to collapse
When you see the error code, DO NOT TOUCH the pda, just restart the Rom update utility program!
Everything will be ok!
Thanks for that, was able to install hard spl 1.2, sim/cid unlock as well as update radio to version 1.5. How can I check that my CID is actually unlocked?
repoman1966 said:
Thanks for that, was able to install hard spl 1.2, sim/cid unlock as well as update radio to version 1.5. How can I check that my CID is actually unlocked?
Click to expand...
Click to collapse
If you have hard-spl, you do not need cid-unlock. Hard spl will ignore CID check during flash....
Thanx guy's. Works!!. started the update again after the error message.
I am stuck onto bootlooder screen and never update
i update my spv m700 to windows 6.1 but it fine. and few day ago i try to windows 6.1 elegent addition but it stops in the middle of screen and i reboot again but it struct onto bootloader screen. can any body help me.
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??