Related
Please i need help to upgrade to the new radio rom. i have a siemens sx66 from cingular. i tried to upgrade it but i always get an error.
Hi aih1977,
Please read the wiki. Cheers ^^
Hi khngaroo
i did but i still get an error
Same issue here
Hi guys,
Actually, I have the same issue. As far as I could see, the Wiki doesn't address the "123: Radio file checksum error" that I receive when following the directions. I follow the directions for using the downloads which doesn't go, then I use the files from the Siemens SX66 Upgrade as suggested.
Any thoughts? Thanks.
ever thought about reading the other threads ?
http://forum.xda-developers.com/viewtopic.php?t=23814
Hum
Lets see the wiki 1.40 upgrade is in the first place a TPYE II upgrade.
Now if you spend sometime and READ the page you will see that there are 2 ways of doing a 1.40 upgrade. One is the whole rom in its type II format the other is just the CE and the radio Type I.
How ever if you don't read the page and think you are got it all worked out then you use the fast option, thats the MA_noID tool (Type II), then download the radio 1.13 which Is a type I but who cares about that any way....then you run the bugger and get a checksum error what the hell have I done now error.
Please correct me if I am wrong so that I can correct the wiki page.
MDAIIIUser,
Yes, I have thought about reading the other threads. What was not obvious to me was that I need to upgrade to the 1.40 ROM to be able to upgrade to the 1.13 Radio. Forgive me if I missed this.
Thanks for pointing this out. I'll start over and review all the 1.40 ROM threads.
lungbutter
You dont need to upgrade to CE 1.40 for the radio 1.13.
Just go to wiki and follow the radio upgrade page. It worked for me and many others.
Now if you want to upgrade to 1.40 then do that also on the wiki page, this will however give you the radio 1.12. (unless you read the whole of the page and understand the getting started section of wiki as in how to use fix.bat)
i tried everything can someone set up the files and link it so i can download it. i think im doing something wrong.
Can you click on the link in my signature?
Arg! Lost my post twice.
Anyhow, MDAIIIUser,
Ok. So the 1.40 ROM is not needed. That was my initial impression. I thought you were referring to reading the 1.40 ROM threads.
I also saw that many users were able to upgrade with no problems. That's why I was suprised when I received the checksum error after reading the 1.13 Radio threads and exactly following the Wiki several times before I gave up. I must have missed something because it seemed like the Wiki steps should've worked no problem.
I haven't found anyone posting that has upgraded the radio on a Siemens SX66 yet. I'm wondering if it's Siemens-related which is why I jumped on aih1977's thread (sorry ).
I'll start over and review the threads and directions, etc.
Thanks for your reponses.
lb
so you are saying that
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.13_Upgrade
does not work for you as you have a SX66.
This could be due to the fact that your device has no camera and the header of the rom is for a camera.
I have never read about having to fix the header for a radio upgrade, its a first for me but I can learn.
Please confirm
1) By following the link above I get an error
2) the error I get is the following
3) My rom at the moment is.
The new Radio ROM does work on a SX66 if you folloe the directions. If you have an issue use the upgrade files that you used to upgrade 1.40. Your going to get an error the 1st go around but then it will run smoothly the 2nd try.
MDA,
I'm running 1.13.00 radio on my SX66...
-Chris
Dear MDAIIIUser,
Correct me if I am wrong. All this while, from what I've read through the forum, my understanding is that MA_NoID can only be used to upgrade type II ROMs. If so, I must confess that I've upgraded my radio to 1.13 (type I) with MA_NoID... And it worked... Any clue?
Cheers ^^
Ok i just want someone to help me with upgrading the radio and if someone out there upgraded the radio please link it or pm me with the files that you used to do it.
Thank you.
MDAIIIUser,
Okay, I was able to get the radio stack upgraded to 1.12. Here's what I did. I'm sure it's pretty ugly and probably not the easiest way but:
Followed the Wiki again with errors as follows:
After step 7, running BaUpgradeUt I received the "Error 100: Model ID Error".
After step 5 of the second set of instructions, I received: "Error 123: Radio Image File Checksum Error". No joy.
So I then took the iMate 1.40 ROM image and extracted the files, deleted the ms_.nbf and nb_.nbf and ran MaUpgradeUt_noID.exe. It errored with Error 120: Country ID Error. The phone was still in USB mode so I reran MaUpgradeUt_noID.exe again and it successfully updated the Radio to 1.12. I tested the phone calling my voicemal with no problems.
I then replaced version 1.12 with the 1.13 version. I ran BaUpgradeUt.exe and recieved the "Error 123: Radio Image File Checksum Error" (this is using the files from the 1.40 ROM with the 1.13 radio file). I then tried running MaUpgradeUt_noID.exe again. The device software update utility showed no information in the from or to sections of the dialog box. It doesn't throw the phone into USB mode and after a minute or so it offers congratulations thinking it upgraded the phone.
I then went back to the 1.13 Radio files I downloaded and ran MaUpgradeUt_noID.exe. I received the Error 100: Model ID Error".
I reran MaUpgradeUt_noID.exe and received an error that it coundn;t find the ruu.conf file so I renamed the htcruu.conf and htcruu.dll ruu.conf and ruu.dll. I reran it and it would attempt to update the radio, then timeout. I received a communications error (which I didn't record) then tried to soft reset the phone. It was stuck in USB or Serial mode. Cold boot no worky either.
I then reflashed back to 1.12 successfully. I will try to update to 1.13 later tonight or tomorrow.
Here is my phone info. before the update:
Siemens SX66 Cingular
Model No: PH20B1
ROM Date: 01/21/05
Radio Version: 1.02.10
Protocol Version: 1337.35
Ext. ROM Version: 1.33.110 WWE
Thanks for the responses. I'm sure that there's an easier way but I'm happy to be at least 1.12.
lb
Edited: Type on filenames.
God are we having fun.
And Boy am I lost.
This is what I can work out.
You flashed the i-mate rom 1.40 radio 1.12 got errors and re ran it it was fine. Thus you have a 1.40 with radio 1.12
Now you are stuck. you want to flash the radio 1.13 (Type I) using the wiki info and you get error that tells me that you have the wrong device. The file is for a device with a camera you dont have that.
You try the MA_tool which wont work as its for type 2 and gives you a checksum and your stuffed again.
You seem to be the first person that has come up agaisnt this thus we need to upddate wiki with new info.
I have a problem with this as the 1.12 was a type II to Type I convert that I made, nobody had a problem with that before.
So as I asked you to confirm what you have and you have not done that I will ask again.
Please confirm
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.13_Upgrade
1) By following the link above I get an error
2) the error I get is the following
3) My rom at the moment is.
OK i did everything i just want the files that someone used to successful upgraded there siemens sx66 from cingular to the new radio 1.13 rom. so i can upgrade my siemens sx66.
SO PLLEASE CAN SOMEONE HELP!!!
MDAIIIUser said:
So as I asked you to confirm what you have and you have not done that I will ask again.
Please confirm
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.13_Upgrade
1) By following the link above I get an error
2) the error I get is the following
3) My rom at the moment is.
Click to expand...
Click to collapse
MDAIIIUser,
Sorry for the confusing post. I wanted to provide some detail. Answers are as follows:
1) Yes.
2) ..."Followed the Wiki again with errors as follows:
After step 7, running BaUpgradeUt I received the "Error 100: Model ID Error". After step 5 of the second set of instructions, I received: "Error 123: Radio Image File Checksum Error".
3) Siemens SX66 Cingular
Model No: PH20B1
ROM version: 1.33.10 WWE
ROM date: 01/21/05
Radio version: 1.12.00
Protocol version: 1337.42
ExtROM version: 1.33.110 WWE
I believe that I don't actually have the 1.40 ROM. From the directory in whcih I decompressed the iMate 1.40 ROM (PDA2k_WWE_14000_176_11200.exe) I removed the ms_nbf and nb_.nbf files and left the radio_.nbf file, which I believe will only flash the radio, then updated.
Is that less confusing?
Thanks,
lb
aih1977,
We are actually trying to determine what the issue may be to update your radio on the SX66. Hang in there!
I tried to upgrade mine xda with ivan's rom but something went wrong so now i cand upgrade it at all.
Allways i get some country or model id error.
I tried to restore image(which i got from another XDA) but says when i enter bootloader & when i should be asked for rom dump it says:
SD Download
Sections=3
Not allow update
I checked ExtROM version but it says 0.0
Please if u have any solution i would be gratefull
stop complaining and start searching for solution.
hint: use MaUpgradeUt_noID.exe to bypass the country code error.
helmi_c has packed this kinda utility in this latest rom (in the folder PH20B1).
good luck.
also read the upgrading wiki. what does it say your meant to do before you upgrade? get ur device data. then what does it say to do with that data?
input it into the upgrade file. helmi's newest rom pretty much does this for u if u follow the wiki and the readme that comes with it.
always follow guides TO THE LETTER, or you're gonna screw up your device.
[writing from work in a hurry, so excuse me for not having all my details in front of me]
I'm a long-time avid user/flasher of the Wizard who recently bought an old BA on eBay for my wife. First thing I did was download the xplode WM5 ROM and flash the sucker. Very nice and now up-to-date.
Call volumes sucked, so I checked her Radio version, and it was 1.02 or something ridiculously old. I tried to flash the newer 1.15 Radio Rom using the bootloader app that came with it (MAUUpdate something). I got a country code error, so I added the special line to the config file to cheat.
Now it starts the process and never gets past 0% on radio flash. Just hangs. And then some strange 114 error when it finally dies.
I've tried with the newest MaUpgradeUt_noID files I could find. I even tried the 1.13 Radio ROM with no change.
I even re-flashed to WM2003 and tried to flash just the Radio from there. Kept getting "wrong device" message or connection error or something. I tried multiple times in a row (one post suggested the first time will error but second time will work).
I did SIM unlock just in case (Cingular on Cingular so shouldn't have been a problem).
Any suggestions out there? I think I've tried everything!
And yes, I've read all posts and wiki's. (Usually I read only Wizard, but have extended my reading to cover the BA).
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
xummy111 said:
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
Click to expand...
Click to collapse
yes, I did. mentioned that above.
I get either country code error (or after correcting that per the wiki advice, I get long period of hang followed by an odd error 113. I think.
does device origin matter? my BA is from ebay and the getdeviceinfo.cab leaves me a blank result except model number and a few random numbers...
I take it that when everyone else flashed to WM5, they followed the simple Wiki instructions and everything went fine? I think I got some odd-ball sub-model that is resistant to Radio flash.
Downgrade Your BA to the WM2003SE, then unlock it with xda3_all_unlock-v1.6_138.exe tool (You can find it in the BA forum here with description how to use it) then try to flash the Radio ROM You want....And then You might upgrade to WM 5.x again if only You wish.
I've tried one of the other sim unlock apps already (successfully) without solving the problem (was tried on WM5). I'll try the order of downgrade, unlock, then upgrade and see if it works.
Thanks for the suggestion.
Jeremy how did it go? are you able to upgrade to the latest radio rom? I also have the same problem as you do. Do you mind telling me the steps if you somehow able to upgrade to latest rom?
this worked for me. after you flash to a new rom (like xplode's), do not take out the BA yet. flash to the new 1.15 radio rom. then you can do the no/yes/yes routine.
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.
Shortly after flashing to the niki radio, 1.65.29.22, I saw on the bootup screen, an 'H' in the corner. Having gained not much of a positive experience from this radio, I decided to try and flash to a different radio, a radio I had liked. While doing so, it always failed at 99% whether flashing to two other radios or trying to flash to a different rom.
Long ago, when I had first visited this forum, I remember there was a problem with the radio locking but can't seem to remember what exactly to search for to fix this. Any ideas?
[Edit] Change the title to better describe the issue.
[Edit] Additional Info: Does it help that the error I'm getting at the end is
[going to 1.64.21.18] - 262: Update Error
[going to 1.64.21.14] - 270: Update Date Error (Image file is corrupt) [freshly downloaded from 4shared]
Oh, I put in hardSpl 3.56. Would it matter to try the earlier versions?
[Final Edit] Thanks to everyone who helped. Here's the pattern: [In order of execution]
Changed SPL from 1.1 -> 3.56
Changed Radios from 1.65.29.22 -> 1.64.08.21 -> 1.65.21.18
in the kaiser forums as well as the kaiser ultimate radio thread, search for "radio from hell" and make sure (and pray!) that the version you currently have is NOT the radio from hell.
I changed the title of the thread to better describe the issue at hand. I just noticed that after installing Niki radio as listed above, I keep getting flashing issues that fail at 99% whether radio or new rom.
DarkCloudInc said:
I changed the title of the thread to better describe the issue at hand. I just noticed that after installing Niki radio as listed above, I keep getting flashing issues that fail at 99% whether radio or new rom.
Click to expand...
Click to collapse
Have you read ASCIIker's answer above?
Well, the radio I had listed wasn't found in the thread. So, before I proceed to go through the steps, I would like to know if this is really a symptom that would require going through the steps.
DarkCloudInc said:
Well, the radio I had listed wasn't found in the thread. So, before I proceed to go through the steps, I would like to know if this is really a symptom that would require going through the steps.
Click to expand...
Click to collapse
Try another combination of hardslp (change your actual) and try to flash the radios again. Let's see if that works.
Does it help that the error I'm getting at the end is
[going to 1.64.21.18] - 262: Update Error
[going to 1.64.21.14] - 270: Update Date Error (Image file is corrupt) [freshly downloaded from 4shared]
Oh, I put in hardSpl 3.56. Would it matter to try the earlier versions?
[Edit] Fixed? I think. I got a new radio on my thing after finally jumping to:1.64.08.21. Will try to flash it to one of the above radios. This one's camera doesn't seem to work.
[Edit2] Finally! Back to a radio that I really thought was great! I will now fix the title.
DarkCloudInc said:
Does it help that the error I'm getting at the end is
[going to 1.64.21.18] - 262: Update Error
[going to 1.64.21.14] - 270: Update Date Error (Image file is corrupt) [freshly downloaded from 4shared]
Oh, I put in hardSpl 3.56. Would it matter to try the earlier versions?
[Edit] Fixed? I think. I got a new radio on my thing after finally jumping to:1.64.08.21. Will try to flash it to one of the above radios. This one's camera doesn't seem to work.
[Edit2] Finally! Back to a radio that I really thought was great! I will now fix the title.
Click to expand...
Click to collapse
Good to know that you solved your problem.