I am very frustrated with my HTC Touch Diamond as I am trying to update it to Hard-SPL yet when it's plugged into the computer (with active sync running) and I follow all the directions very closely, I go to update the phone and it doesn't show any activity on the phone, the progress bar on my computer screen shows 0%, then it eventually pops up with a message saying Error 202. This is a connection error, yet I am positive that the phone is plugged into the computer. Please HELP!
Hello, Did you run SSPL first? You can only flash hard spl when sspl is active it is a black screen.
I have a Telus HTC Touch, does that make a difference on whether or not this will work?
your diamond is cdma. these only work with gsm.
so by the word 'these' in the last post, you mean that the Rom updates won't work?
I don't think SPL has to do anything with CDMA or GSM. Some ROMs have an option in the phone settings to choose either GSM or CDMA.
ryanseyz: Make sure you have a factory ROM ready before trying the cooked ones here so when things happen unexpectedly, you always have a choice. Next, there are 2 versions of SPL here, try both. Make sure you install EnableRAPI.cab and CertSPCS.cab installed on your device.
Regards,
Carty..
anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax
Phyrax said:
anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax
Click to expand...
Click to collapse
The same here with my mda compact iv. I've tried all versions of the RUU of hardSPL with no result (error 202). When I update the official rom of t-mobile (1.93) with the RUU, there isn't a connection problem and everything goes well.
My device is not simlocked, but i suspect it has a security lock or something like that.
Hello, I have the same problem with a HTC Diamond : error 202 and everything is connected, hotsynched, etc.
Did anyone find a solution ?
anyone??? im having the same problem..
I'm having this issue as well, any solutions?
The same problem
I have a HTC Touch Diamond and have the same problem.
I don't know what i have to do to fix this problem.
I have got the same problem. Add I have problem with align screen, so I can't run any cab on device. Looking for any advice..
i have a htc mda basic ....same problem...any solution...please help....
I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.
Dudubai said:
I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.
Click to expand...
Click to collapse
Thank's..., this solution work for me...!!!
For me too !!! working now !
Thanks it work!
Thanks !!! It works !!!
Related
I tried to flash unsuccessfully an 8525 that I have (from work) that has never been used.
The device is locked. I tried several times to flash it from my Vista machine but no go.
It detect the SPL 1.04, click next a few times, start the update process, the 8525 reboots and gets in USB mode ready to start the flash, then nothing.
It sits there for 30 seconds or so then display error code 260.
I checked the codes but didn't find it in the list.
Tried flashing from the microSD card but same thing. Reboot and it goes in the serial mode (with the screen RGB blocks) then does nothing else.
Haven't ever had a problem flashing my TyTN so I'm wonder what gives.
check if the image is OK, download it once again and change the USB port or machine is possible, i have an 8525 that works fine with VP3G so is something locally
mine works fine with that ROM.
did you use pof's unlock and install HARD-SPL 2.10 first?
Thats what I did. Worked like a champ.
haven't unlocked nor installed HardSPL first.
Do you think that might be the issue?
The device is completely stock, locked to AT&T.
Yes that is the issue. All the roms you find here are not vendor specific. You must install HardSPL first, then you can flash these ROMS..
Read Mr Van's guides too they are most helpful and easy to understand...
cool... will give that a shot. i figured i must have missed something since my TyTN had never had any issues being flashed (god knows how many times).
Hello all.
I have just bought an o2 Xda Ignito (aka HTC TOUCH DIAMOND).
I want to flash it to a cooked rom. And after reading up about it on this site, it would seem that I would need to install HSPL onto my device.
Well that is where the problem lies. I get the 262 error when trying to flash it with HSPL. I have even tried to do it the manual way (placing the SSPL onto the device, run it, then install it via my computer.
I still have no luck. I have tried this more than enough times with no joy...
I've read up on a few threads with the 262 error with no joy.
It just sticks on 0% and then the above error comes up. I can't understand why it wont work.
If you need any information let me know.
Cheers.
Hi,
What version of HardSPL are you trying to install?
R3PUBL1K said:
Hi,
What version of HardSPL are you trying to install?
Click to expand...
Click to collapse
I'm using this one
http://forum.xda-developers.com/showthread.php?t=416211
But I have tried 2 different HSPL versions.
One of them gave me the white loading screen and then it just froze
The other just gives me a black screen and stays black, although one time i did get the phone to show the % bar on the screen, but that froze on 0% too :\.
Thank you for the response.
So I presume then you tried the most common 1.4? What were the other two.
You could try this 1.93 (HERE) if not done so already.
Run this from your PC - during the process a message appears on you device screen asking to run an .exe (select yes) the the process should start. You may find that nothing appears to happen for a while, which is not the case.
Please do not do anything until you see the processed completely finished or the system error out.
R3PUBL1K said:
So I presume then you tried the most common 1.4? What were the other two.
You could try this 1.93 (HERE) if not done so already.
Run this from your PC - during the process a message appears on you device screen asking to run an .exe (select yes) the the process should start. You may find that nothing appears to happen for a while, which is not the case.
Please do not do anything until you see the processed completely finished or the system error out.
Click to expand...
Click to collapse
That is very strange, I used the 1.93 version before with no avil, this time it worked with this version! cheers
Glad it worked for you.
Happy flashing
DanMc07 said:
Hello all.
I have just bought an o2 Xda Ignito (aka HTC TOUCH DIAMOND).
I want to flash it to a cooked rom. And after reading up about it on this site, it would seem that I would need to install HSPL onto my device.
Well that is where the problem lies. I get the 262 error when trying to flash it with HSPL. I have even tried to do it the manual way (placing the SSPL onto the device, run it, then install it via my computer.
I still have no luck. I have tried this more than enough times with no joy...
I've read up on a few threads with the 262 error with no joy.
It just sticks on 0% and then the above error comes up. I can't understand why it wont work.
If you need any information let me know.
Cheers.
Click to expand...
Click to collapse
Bro you have a Diamond 2, this is your problem the Tutorial is for first Diamond.
AlexisRoj said:
Bro you have a Diamond 2, this is your problem the Tutorial is for first Diamond.
Click to expand...
Click to collapse
Where did you get the idea that he had the Diamond 2? he does not...
If you care to read the thread, you should notice that, and the issue is resolved.
R3PUBL1K said:
Where did you get the idea that he had the Diamond 2? he does not...
If you care to read the thread, you should notice that, and the issue is resolved.
Click to expand...
Click to collapse
Search in google "aka HTC TOUCH DIAMOND" and you find your answer
AlexisRoj said:
Search in google "aka HTC TOUCH DIAMOND" and you find your answer
Click to expand...
Click to collapse
There is no need for me to search - HE DOES NOT HAVE A TOUCH DIAMOND 2 - What he owns is a carrier customised Diamond (1st diamond) FFS.
See Here
and for your information this is the diamond 2 HERE
Please no more silly comments about it being a TD2
i own a htc diamond indian version. it has rom version 1.37.720.2.wwe. i downloaded the upgrade from official site. but it stops at 0‰ and gives error 262. what should i do
Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!
I have the same Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU value and i was able to restore my phone to working status with the following ROM
http://www.megaupload.com/?d=IJIVTIMF
Hope this help
10507
Thank you very much 10507! I'll download it now and see if it works.
Thanks for the file but it appears that it is for the SDA. It dit not work
luisro said:
Thanks for the file but it appears that it is for the SDA. It dit not work
Click to expand...
Click to collapse
That's odd, I was able to restore my Excalibur/Dash after flashing the corrupted EnergyRom.
Hope you will find a way to resolve your problem.
10507
But how did you do it? Flashing it through USB or through the memory card? The weird thing is that when I run the EXE the cellphone that appears in the picture of the program is an SDA. But well I will try it again and thank you for the help!
I used bootloader method and connected my phone through USB for flashing. Remember to remove your memory card when flashing.
well, I've been in your situation for almost 3 days now, and still no solution for it, maybe it's time to put it in the box and purchase a new one , all thanks to the broken EnergyROM ...
Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.
ookba said:
Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.
Click to expand...
Click to collapse
Thanks ookba for cheering us up. I'm having the same problem like many, many people in this forum hopeless seeing our dash not responding to every solution proposed in this forum and the only thing that we have right now is keep trying to flash and see if it works. I will try again in different PC and see what happens. I'll let all of you know if I finally resurrect my s621.
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
This problem is ridiculously weird to why some members are able to restore their phone to original factory condition, and others are not able. Therefore, I have search from trustworthy sites and from friends for difference made ROM. Hopefully, one of these ROMs with help out anyone...........
1.33.422.1 (Worldwide English, WM6)
http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
1.27.405.1 (Worldwide English, WM6)
http://rapidshare.com/files/100235639/HTC_S620_WWE_1.27.405.1.exe
1.22.531.6 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?z4vjgzxisrz
1.22.531.4 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?yygkw1d5xmc
1.11.531.1 (T-Mobile USA, WM5)
http://rapidshare.com/files/104641948/T-Mobile_DASH_WM5_V_1.11.531.1.exe.html
Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_ 02.98.90_Ship
http://www.mediafire.com/?9gbwdzd2omg
Thanks 105507 but no success at all, I even found 2 more factory roms in the web and also they don't work. I own an unbranded international version s621 manufactured by Brightstar corporation (I tried to flash Brightstar's stock rom but it didn't work) and I noticed this because in the warranty docs it says brigthstar corporation and originally the phone came with WM5.
not that this will help. but this is one of the reasons why people should be really installing the hardspl so if you have a bad flash, you dont have to install a stock rom. any rom whether be it cooked or not will work. but this hardspl must be done prior to installing ANY rom. the hard spl is done by jockyw2001. send him a pm to see if theres anyway to get that on the phone, even in its current state.
edit: here's the link to the hardspl: http://forum.xda-developers.com/showthread.php?t=329605
luisro said:
Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!
Click to expand...
Click to collapse
My phone is the same your phone but ONBL 1.33.0000 and SPL 1.33.0000
I'm trying to find the original rom of this line but not found. Please help me!
Have you done a reset? My friend fixed his by trying reset a few times. He reset it, walked away...., it took long time to see whether it booted over; if not, do it again...
By the way, he leave the sim card in; and, you need to remove your micro sd card.
On an official site it is possible download ROM for your phone. It is flashing from bootloder mode. It some times helped me, while I have not flashed hard SPL.
luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
Hi my friend, I wish you lucky!!!
by the way, where country you're from, I have some Shipped Roms here for brazilian Excalibur (S621), maybe it could help, if the answer is yes, let me know to made this one come to you
http://wiki.xda-developers.com/index.php?pagename=Elf_GoldCard
Furious Girlfriend (oh My beloved Helloween died with my ROM's)
Boy oh Boy...
My ROM's are now in heaven
Girlfriend deleted they (I'm so sorry...)
But, pay attention in this thread
http://forum.xda-developers.com/showthread.php?t=381726
In there have a sort of shipped ROM's and maybe coud help you
Good luck my friends
A friend from XDA have some Shipped Rom's and will upload it for you, shortly he'll post something here
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
same problemm
Same problem. Any help?
tekata said:
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
Click to expand...
Click to collapse
Any chance to MTTY? Might help, just guessing...
Or try to flash a new radio ROM as the wifi hardware might be stuck in a state that is unknown to the drivers. Flashing a radio is supposed to reset hardware but I may be wrong.
Really guessing here but symptoms shows relation to radio hardware.
Cheers,
Cina.
sspl
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Hello, my solution to this was conductive interconnect of metalic parts as you can see here
://i.ytimg.com/vi/UUnH8O-1jII/0.jpg
(of course with http on the beginning, i'm not allowed to post links)
on the left with aluminium tape (sorry for image quality, found it on web).
It also seems that the sim card reader has to be conductively connected with the above em shielding.
Hope it will help
it´s a battery problem ... get a different one and your phone should be fine
Dreamtheater2003 said:
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Click to expand...
Click to collapse
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
@edefux
Do you already had such a case? I am not sure, if buying a new battery is economical enough only in order to try, if it works. I admit, it could be the battery. But running the phone with the charger switched on, should show if its the battery or not. I tried with charger on, but obviously this didn't solve the problem. Or do you mean, that in the battery there is some sort of "short circuit", that's confusing the Diamond no matter if the charger is on or not?
@DiamondFlower
Thanks for the suggestion. I'll give it a try, when I tried everything else
This will be the final try before burrying the precious Diamond.
Cheerz
MTTY.
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
...
Cheerz
Click to expand...
Click to collapse
See this post for MTTY. This is the second post on Diamond ROM thread pinned for easy access anyway. Please search before you post!
If you can enter bootloader mode with VolDown pressed while reboot you're off to go. You can plug in USB cable and you can flash SPL, Radio or any new ROM. I assumed this based on your first post:
tekata said:
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
Click to expand...
Click to collapse
Cheers,
Cina.
it is a battery problem i´m 99,9% sure of it - i had the same case ... it was driving me crazy ... different roms, radios, but the problem persisted - luckily at that time i was working at a cell phone provider and could try different hardware, which finally brought me to the solution to switch the battery.
edefux said:
it is a battery problem i´m 99,9% sure of it...
Click to expand...
Click to collapse
Maybe I'm a bit unlucky, but I've got the 0,1%. Took a new battery, this didn't solve the problem though.
i´m sorry it didn´t work for you ... !
it's ok! it didn't work - actually I could have thought about it wont work: beforehand I sent the item to the mobile operator guarantee team and they returned it back - no warranty of course (due to olinex bootloader which I wasn't able to remove) and stating: Fremdeinwirkung/ Totalschaden (total loss). And because I sent it without battery and they obviously checked it ... suppose with a fresh or "good" battery. And it still didn't work for them, so...
I'll try to open it and see if there is some short circuit around the metal shielding. Maybe I'm lucky then.
Anyway thanks guys about the hints and suggestions!
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
Click to expand...
Click to collapse
I'm not sure if its called sspl but you can run it from boot loader and it will black out your phone. after that you need flash the new bootloader.
I'm thinking its not a bootloader problem though...
hello everyone..
this morning I was intended to revert my kaiser back to WM 6.1,
I followed the instruction to put the ROM to my SD card along with KAISDIAG.nbh.
but maybe I chose a wrong rom, as the process goes, I just realize that the process was deleting my hard SPL..
now the text my 3 color display only says "SPL-1.56.0000"
but the android is still working....
so now my phone run on android without hard SPL...
could anyone help me? is it possible to install a hard SPL from android?
flashing from SD card doesn't works because I don't have any hard SPL installed..
There is no way at present to install hardspl from android, since we cannot run jumpspl, however you should still be able to flash a stock 6.1 rom using usb method.
Sent from my HTC Dream using Tapatalk
I have tried, but the process always failed with connection notification.It says that update utility cannot connect with my pda phone.
Well the problem is, flashing with usb method needs activesync connection with the computer. since microsoft activesync doesn't applicable anymore, I have no idea how to build connection with my phone. Besides, nothing seems happened every time I connect my phone with usb cable. Its just like my pc couldn't detect the device.
Should I install some kind of programs first on my pc? or am I miss some steps to make my phone detected by my computer?
I'm using windows xp by the way..
The CustomRUU still works for me if you boot the phone into SPL first (reset and camera+power buttons) then plug it into the computer and run the RUU (no activesync connection), so you should be able to flash a WM ROM, then you can sort out the HardSPL later
EDIT: Or does that only work for me because I have already got HardSPL?
yes it works..
the process goes, but only for 1 % . my phone reset itself and the notification on my pc says about invalid vender ID "this update utility cannot be used for your PDA phone, please check your update utility."
since the only stock rom that I found is .exe which is extract itself, I couldn't use The CustomRUU. Could this be the problem? or do I choose a wrong rom?
edit : I'm trying to install Factory Shipped ROM form HTC
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
Do you know where to find stock rom for kaiser? most of the post about stock rom leads me to wiki xda, which is not available anymore.
thanks.
Not sure if these will work, but there are links to original HTC and ATT ROMs here
Also at the bottom of that post is a link to some reconstructed original ROMs
I have no idea if these will work any better than the one you've already tried, but it's probably worth having a go
thanks for the link..
I have visited that thread before, actually the 1st ROM that I tried to flash is also from that page. Both original ROMs for HTCor ATT doesn't works for my phone. But thanks to you I just realize the link about some reconstructed original ROMs.
Well, My phone is KAIS-100 which is made in Taiwan.
I guess I'll try Chinesse HTC 1.56.708.3.
I hope this one will make a progress.
-----------------------------------------
aww... still not working..
with reconstructed ROM, the process stuck at 0%, give me error [262] notification : update error. The manual said that if this kind of error occurred, I just need to do soft reset and run RUU again. I have tried several times even restart my pc first, but still not working.. any suggestion?
Try to flash radio. If you can't do it i think that you have messed up the bootloader
I can't...
the result is same, I'm trying to flash KAIS_Radinly_1701909 or KAIS_RADIO_ONLY_1710901_Custom, I got stuck in 0% with error [262]
The text in my bootloader says
KAIS-100
SPL-1.56.0000
CPLD-8
So, is there nothing else I could do if I have broke my bootloader?
No one can help me anymore? T-T
(running to the middle of the street and shout "why God, why??")
So, the lesson is :
If you are trying to flash back to windows mobile, DO NOT use factory shipped rom. Because it will modify your hard SPL and downgrade your radio version.
If the process failed and your hard SPL gone, you will get stuck in half working android without being able to flash anything, including correct your radio version, or reflash your kernel to fix your panel setting.
correct me if I'm wrong..
well, I hope my experience could be useful for you.
Thanks.
You can extract the exe file with winrar and you'll have all the files including RUU_signed.nbh
Rename it to kaisimg.nbh and copy to sdcard
Don't know if you can install from sdcard but since it's the shipped rom it might let you.
thank you salac..
I also have tried that method, using winrar to extract exe files.
but still, no luck for me..
Flashing via SD card got me stuck at loading screen, and I also tried to use custom RUU to flash the files via usb but my phone reset itself at 1% of the process and gives me error message [294] : invalid vender ID.
SOLVED
Finally
after days of yearning..
I found a suitable WM 6.1 ROM for my kaiser.
My phone is KAIS 100 HTC P4551. Usually, KAIS 100 model is for AT&T but mine is HTC branded, so that's why AT&T stock ROM won't works and my phone was originally shipped for US, that's why most of WWE stock ROMs always give me error 294.
So, basically I have to use HTC WWE ROM for US and this is really gives me hard time since HTC US website only provide ROM for AT&T.
In case you have same problem with me, I have uploaded the ROM at rapidshare
and you could find it here.
Now, I can flash a hardSPL, fix my radio version....
and flash back to android..