Related
I currently have AKU3.2-1.0RC1.
What do I have to do to install RUU_Molski.Biz_AKU2.3-226102_22610105_024711_WWE-30MB-CF2?
Also, Molski mentioned I need an Extended ROM - how do I install that?
Thanks guys.
Tried RomUpgradeUtility_noID .....there was an Error 240 =(
Error 300:
Error message will appear when you use the incorrect RUU version to upgrade.
Error 240:
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
_Nomad_ said:
Error 300:
Error message will appear when you use the incorrect RUU version to upgrade.
Error 240:
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
Click to expand...
Click to collapse
O i got that. that's from the Readme file.....
But what does that mean?....like.can you suggest the next step? =)
Well... I'd suggest that you use this ROM to downgrade with. You should be aware that this ROM also downgrades the ipl/spl so make sure that after flashing it upgrade to an official ROM that also upgrades your bootloader.
NOTE: You have to make sure that your device is CID-unlocked before flashing a custom ROM. If you don't know how, look here...
After these steps you shouldn't have a problem upgrading to the latest molski.biz ROM.
Oh, and the extended_rom is, in the case of molskis rom, already included in the download. As it is in almost every ROM available, so you really don't have to worry about that...
Good luck and give us a shout if you run in to any problems not answered in the above mentioned thread
_Nomad_ said:
Well... I'd suggest that you use this ROM to downgrade with. You should be aware that this ROM also downgrades the ipl/spl so make sure that after flashing it upgrade to an official ROM that also upgrades your bootloader.
NOTE: You have to make sure that your device is CID-unlocked before flashing a custom ROM. If you don't know how, look here...
After these steps you shouldn't have a problem upgrading to the latest molski.biz ROM.
Oh, and the extended_rom is, in the case of molskis rom, already included in the download. As it is in almost every ROM available, so you really don't have to worry about that...
Good luck and give us a shout if you run in to any problems not answered in the above mentioned thread
Click to expand...
Click to collapse
I had my CID unlocked using lokiwiz. Very happy - first time everything just went as described in the thread....!
However I wasn't able to use __RUU_Wizard_1050412_WWE_101_11210_WWE.exe - It gives me an Error 300 again. (My Wizard is newly hard-resetted so I guess I don't mind hard-resetting it again if needed)
hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
If i were you I'd use this one =)
futureshock said:
ok i found it i didn't read further the 1st page on sspl thread
edit:
have repacked it with runme.bat and 77.7er SSPL ...
Radinly_1.54.30.10
Click to expand...
Click to collapse
At least I did and it worked =)
and then I'll highly recommend this WIM6.1 release by FutureShock: http://forum.xda-developers.com/showthread.php?p=2094056#post2094056
GL =)
I've GOT IT!!! using various mix and match method, im flashing the phone now!!! fingers crossed it'll boot later
UPDATE: DOESNT WORK! PLEASE HELP
It sure will.. Even I got it to work really fine
crap!. doesnt work. it's still SPL 1.09 and stuck at 2nd boot screen.
is there a ROM editor that works for meteor? can someone please suggest one that can be used to sign the nbh file.
jerpelea, or futureshock, please help
not good news
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
PiGeonCZ said:
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
Click to expand...
Click to collapse
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
alexnvidia said:
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
Click to expand...
Click to collapse
why did you format ?
try to reflash 1.09 spl
and after this wwe one of 1.34 roms to get 1.10 spl
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
Click to expand...
Click to collapse
jerpelea: First of all I will say thank you for taking all that time you do spend on the ROM cooking/building/making/what-ever-is-the-right-name and I/we really appreciate it!
jerpelea said:
but i dont know if you have the knowledge
Click to expand...
Click to collapse
I think that comment was really unnecessary!
As a n00b I know how hard it is to understand what’s happening. I did read the wiki’s and still I didn’t get HOW TO upgrade a ROM until I found a great post in FutureShock’s thread
darkDirk said:
First of all:
It's fantastic what you are doing with wm6.1 and the Breeze, Futureshock !
I am new and trying to upgrade it myself, but at first I didn't have any luck.
Here is a simple newby step-by-step manual:
- Download and extract a MTeoR-FutureShock-WM61-xxxx.x.rar
- Check your Mteor battery in more then 50 % full
- connect the Mteor to the computer via usb and check if Activesync works
- go with DOS (cmd line) to the directory and start runme.bat
- On the Mteor press camera and powerbutton at the same time.
- then immediately press any key on the computer to continue the batch script.
- now you should see the 3-color bootscreen
- press any key to start the rom-update program and follow its directions.
When the update is finished (in less then 5 minutes), then wait untill the first boot is complete.
If you don't get the 3-color bootscreen or you the update on the Mteor stays on 0 % and the rom-updater displays an error, try testing this:
On the Mteor start the explorer and in the root directory (press UP once) find SSPL.EXE en start it.
If the Mteor won't start the program and there is an error like "insufficient trustlevel".
You need to remove the application lock on your Mteor.
Run SDA_ApplicationUnlock.exe on your PC with Activesync working and then install SP_AllowCertificateInstall.cab on the Mteor.
You will find those two in the .rar in ".\opt Software\Unlock Tools"
Then redo from the start.
Then, Have fun !! (Futureshock & DarkDirk)
P.S. works on a BREE100 with IPL-0.90 and SPL-2.05.
Click to expand...
Click to collapse
But I still do not know what SSPL, SPL, IPL or whatever there is does to me or/and the phone.
Anyway. Thanks for all the work.
if someone has a corrupt CID just send me an pm...
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
with all the respect what you do for this community, isn't taht you who advice us to update the SPL before trying your images?
in this thread http://forum.xda-developers.com/showthread.php?t=384398 you should probably higlight that the update should be done only on WWE devices.
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
alexnvidia said:
hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
Click to expand...
Click to collapse
run terratem
type info2
if it sais A07 then just flash rusian 1.34 rom and enerithing will be fine
application unlock it
run sspl 77.7
flash wm6.1
if it says enithing else you need to locate your original rom
till now i found that it sais a07 in most cases
BR
alexnvidia said:
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
Click to expand...
Click to collapse
it depends on the info displayed on terraterm
for A07 you can use the russian rom to recover
this is what i got from terraterm. same as mtty.
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
Cmd>
i did flashed back to my original ROM after the first stuck in WM screen incident. and amazingly the flashing process works after several mix and match. after the original (WM5) ROM completed flashing, my IPL is downgraded back to 0.9 and SPL is still 1.09, and im still stuck at the WM logo screen (this time WM5 logo).
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
futureshock said:
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
Click to expand...
Click to collapse
i tried SD card flashing too yesterday. it says not allowed. i have already flashed over the original dopod 595 ROM and my phone is now WM5. the flashing is 100% successful, but it is still stuck at the second boot WM screen.
i think im in a really screw up position now. i have SPL 1.09 and IPL 0.9. i dont know what is corrupted now. is it the CID? SPL?
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
futureshock said:
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
Click to expand...
Click to collapse
both mtty and terraterm give me the same msg when i type info 2. it says time out (refer above for exact error message).
the original dopod 595 rom has SPL2.05. and it was successfully flashed into the phone. when the phone reboots, it is still stuck at 2nd boot screen (WM logo). i checked, the SPL is still 1.09, but IPL has been downgraded to 0.9.
OK, so, here it is.
Download, extract, Donate!
your device *MUST MUST MUST* be synced with ACTIVESYNC and in WINDOWS MOBILE before starting the procedure.
All of you kind folks who pledged to the fund... please feel free to use my donate link </shameless_whore>
Cheers!
Olipro.
Hey Olipro
Nice to see this is up and running.
One Question....does it need to be in XP or can it be done in Vista as well?
try Vista and report back.
Vista worked for me
Vista worked for me
goes through alright (once drives are fixed up) however flashing any other rom still fails - even when manually going into the hard spl, and then running flash utility, it says the rom is corrupt.
Just the start?
ajajaj said:
Vista worked for me
goes through alright (once drives are fixed up) however flashing any other rom still fails - even when manually going into the hard spl, and then running flash utility, it says the rom is corrupt.
Click to expand...
Click to collapse
I guess that this means we need to now roll our own, or wait for someone to release a p3600i rom which uses this spl?
ajajaj said:
I guess that this means we need to now roll our own, or wait for someone to release a p3600i rom which uses this spl?
Click to expand...
Click to collapse
Did you try flashing a new radio ROM as well. Previously we could not flash anything other than the HTC Official ROMs including radios.
Radio Upgrade successfull
Andyc46 said:
Did you try flashing a new radio ROM as well. Previously we could not flash anything other than the HTC Official ROMs including radios.
Click to expand...
Click to collapse
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....
ajajaj said:
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....
Click to expand...
Click to collapse
I have an nbh from an existing rom, I want to change the 400 to 401 as referred to in other thread - can anyone offer context (where do i find the 400 specifically referred to?)
if I search, is it hex I am searching for, or ascii?
TIA
ajajaj said:
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....
Click to expand...
Click to collapse
Well that is a good start.....which ROM did you try that came back as corrupt?
Andyc46 said:
Well that is a good start.....which ROM did you try that came back as corrupt?
Click to expand...
Click to collapse
I have tried the Trinity_WM6.1.Black_Edition.OS_Version_CE_5.2.19701_Build_19701.1.0.2_by_Akeo rom - this reports as corrupt.
Also, RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite - this one complains that the rom is for 128, not 256 MB.
等待中国高手的简体ROM
waiting 4 the writer 's CHS ROM
experiments in flashing
I modified the first instance i could find of 0x0400 the RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite rom to 0x0401 and got a different error message saying:
Error [226] : FLASH WRITE
Flash write error happened. please check your PDA phone.
now the phone is now stuck in SPL
changed it back, and re-flashed, flash failed with "type error (128 vs 256)" however the phone now boots again.
tonychou said:
等待中国高手的简体ROM
waiting 4 the writer 's CHS ROM
Click to expand...
Click to collapse
No good to me...I am after WWE
ajajaj said:
I have tried the Trinity_WM6.1.Black_Edition.OS_Version_CE_5.2.19701_Build_19701.1.0.2_by_Akeo rom - this reports as corrupt.
Also, RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite - this one complains that the rom is for 128, not 256 MB.
Click to expand...
Click to collapse
That seems strange as the basic ROM for D810 (Standard Trinity) is the same for P3600i.....you would think both phones should accept cooked ROMs (now we have Hard SPL).
sigh. problem is that none of the roms I try will load...
By changing first 0x0400 in mary nbh to 0x0401, it flashes as far as 11% and fails with communication error, then when booting changes the inital start screen of the phone, (flashed to phone) but no further. saying the rom is corrupt.
SUCCESS
fully flashed the P3600i to WM6.1 - writing new thread to show how.
I had tried a few times one 2 mechine
one on winxp and one on win2k3
but both mechine show the same error when i do the step 1
the phone go to 3 color but in pc side it shows the ERROR [260] message
don't know how to do ><
after reset the phone
nothing happened
What happened to me exactly the same as you!
money donated!
Thanks both olipro & ajajaj!
ok so i tried to do hard-spl. but i got a 260 error.. reset my phone, windows came back up.
this was from a xp sp2 machine :/
the crap thing is now i cant run any cab files on the wm device.. i've definately done something to do.
Hi,
I've just upgraded to a new Dutch rom, but since then I only have trouble.
I get different colours (like drivers are not loaded), it keeps getting stuck or resets itself, and nothing helps.
I've tried to put on a different rom, with succes, but I still have the same problems.
On startup, however, I see the right colours.
I also put back the latest original ROM, but no luck...
Can anybody help me?
guessing you have hspl 1.14 installed
Yeah, I reinstalled that, as one of the latest things I did.
The problem you describe happens when you flash a 1.56 based rom with 1.14 HSPL. First flash a stock 1.56 ROM (a new SPL is then flashed as well) or use the new HSPL. Then you should be fine. So no, it's nor corrupt!
For more info, read crackwhore's guide (sticky)
Well, I'm trying to do so now, but it keeps getting stuck at 0%...
Does it matter I have an NLD-version, and not a WWE?
Update: I cannot get a proper connection via activesync, and through the bootloader it stays at 0%, and after a while the update utility says no.
Update 2: ah, thanks to troubleshooting, it looks fine!
THANKS!
Guys,
My HD has an issues, it appears to only go to the RGB screen/bootloader. The error says:
"Upgrade ROM code error
Please try again"
It appeared after trying to downgrade from HardSPL after my screen kept being miss aligned and I was onable to use the phone properly.
O and O said:
Guys,
My HD has an issues, it appears to only go to the RGB screen/bootloader. The error says:
"Upgrade ROM code error
Please try again"
It appeared after trying to downgrade from HardSPL after my screen kept being miss aligned and I was onable to use the phone properly.
Click to expand...
Click to collapse
hello,
you should provide more information of what you're doing, or what you've done.
For example, telling us which rom are you using now and what rom you want to flash to.
Also, 'trying to downgrade from HSPL' to what?
And maybe some other relevant infos so that we all can help you
O and O said:
Guys,
My HD has an issues, it appears to only go to the RGB screen/bootloader. The error says:
"Upgrade ROM code error
Please try again"
It appeared after trying to downgrade from HardSPL after my screen kept being miss aligned and I was onable to use the phone properly.
Click to expand...
Click to collapse
Does it still show hspl as being loaded? If so, just flash the rom again, as it says. That error usually happens when the rom update process is interrupted.
I presume you are trying to flash back to a stock rom to correct some issues you are having. If so, follow the steps at the end of this post.
It was from a stock ROM - I was on Miri's v35 before then. I wanted to change SPL to stock so I sued the stock 1.15 file and when through the process and for some reason it didn't complete and now I get the error.
Bump - I kinda want my phone BACK!
O and O said:
It was from a stock ROM - I was on Miri's v35 before then. I wanted to change SPL to stock so I sued the stock 1.15 file and when through the process and for some reason it didn't complete and now I get the error.
Click to expand...
Click to collapse
Okay, let us all make things clear again, shall we?
You were with Miri's v35, then you decide to go back to stock. So you flashed back a stock rom, and now you want the spl back to stock spl.
So did you restored your radio too?
3. run the hardspl exe but do not click anything in RUU yet. just let the hardspl EXE extract the files for flashing.
4. the SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
Click to expand...
Click to collapse
Now the other question: Did you overwrite the .nbh file as mentioned?