Related
Hello everyone.
I have just bought my Hermes (AT&T 8525) after one year of planing so. It came with WM5. I downloaded some of the ROMSs, radio and bootloaders commented here. I tried reading all the vast infromation in this forum and the wiki, but still having a problem.
THE PROBLEM IS AS FOLLOW:
When I start the flashing process, using HTC_TyTN_WWE_3[1].54.255.3_6275_1.48.00.10_108.exe or RUU_Hermes_CINGULAR_WWE_3.1.57.502.1_6275_1.48.00.00_108
... everything goes well, until the progress bar appears in my PC. When it appears, ActiveSync in my PC closes and my Hermes goes to stand by (the lcd goes off) so I cannot complete the installation process.
The phone works pretty well and I'm really amazed for all its capabilities. But still, I'm stucked with wm5.
Why do you think this happened?
PS: I flashed the radio (1.51.00.10) and bootloader (HARD SPL v7). My ROM version is 2.15.502.3. I use "ActiveStink" to sync my files without problems.
Any advice will be more than welcome!!
I'm no expert but that appears to be normal behaviour!
ActiveSync is only used at the start of the process. After a few files have been transfered, Activesync is closed and a different link is established. If you just leave it for a short while longer, a progress bar should appear on the Hermes too.
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
todd_jg said:
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
Click to expand...
Click to collapse
I'm having the same problem - always have. The message tells me that I'm disconnected and that I should check my USB connect etc. I left that box up there for about 15 minutes. Now I've closed the box and have waited several minutes with no activity. This is pretty aggravating. Thanks for any help.
try turning off your antivirus aplication. thats work for me flashing my tytn to wm6.
I've done everything.... I guess
Hi...
Yes, I consulted the www.mrvanx.org, excellent tutorials.
I flashed without problem the radio and bootloader. The progress bar started to "progress" and everything was fine. The only problem I have is flashing the WM6.
I don't remember where, but I readed that flashing the bootloader "Hard SLP v7" causes my HTC not to accept any Oficial WM6 ROM. The article said that I only had the chance to flash a coocked or modified ROMs. Is this true?
If not... what else can it be? I also closed all my applicacations including the antivirus, goback, disabled the internet connection, the logictec mouse center, etc. and nothing, the same as Chicoh happens to me.
"Error 260: Connection... check the USB cable bla bla bla."
Should I restart in safe mode to do the flashing?
Should I try to install a modified ROM?
Have in mind I've tried three different official ROMs: WWE, Cingular and spanish.
Thanks to all the comunity!!!
Saludos desde México!!
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
liquidsilver said:
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
Click to expand...
Click to collapse
I'm trying that as we speak. I have a good feeling about this. I'm a little concerned that I didn't think of it though. Makes perfect sense - Skip the middle man.
UPDATE: Crap. No luck. Thanks all the same though. I'm not giving up.
What OS are you using, xp or vista? My vista 'top had the same problem wouldnt flash for the longest time and i had to use my xp.
However, it does work now. Not entirely sure why.
Now I had success!!!
Hello my friends.
It seems that the article I readed days ago detailing that after flashing the Hard SPL v7, I could only install a modified ROM, not an official one from HTC or Cingular.
I downloaded Black Satin and installed it without any troubles. The entire process lasted only 3 minutes!!!
I wanted to have an official ROM, don't ask me why, and never tried the "other" ROMs that are actually excellent!!! some apps that were on WM5 are not in WM6, which is kind of sad, but if there's something that I love of WM Smartphones is that I can download and install whatever I want or develop it if it doesn't exist!!!
By the way, I use Windows XP Pro.
Thanks for all the support!!!
PS: Before flashing the Hard SPL v7, I tried installing the cingular WM6, but didn't make it. That's why I readed almost all the pages and threads here in xda-developers and found that flashing a new bootloader was a very good idea. The rest of the story is known by you.
i dont know what's wrong, ive owned this dash since march. updated to wm6 when it came out, then stopped giving a hoot after finding out that SNappunlock wont work on my dash.
i noticed people here found a very nice dash rom that i want to flash to so badly, but i learned that this requires appunlock in order to get the CID bypass to work
after searching around for wm5 (took about an hour) so i can flash back just so i can appunlock, then flash to the better rom. i found it! all thanks to BGNiko
you think i'm done with my problems, right? well i go to flash to wm5, and during the flashing session, the screen brings me to that RGB before the rom change happens, but no go! it tells me my usb cable isnt hooked up even though it is. ive had no problems re-flashing to the wm6, so the cable isnt the problem.
anyone ever have problems reverting to wm5? is there a solution?
thanks in advance
ps: i have us tmobile
uhh... did you try again?
i had the same thing happen to me. tried again, same thing (same message that you got). restarted the computer, tried again... presto. worked fine.
so long as the flash process doesn't start, your phone should be fine. it's just a matter of getting the computer to talk to the phone. it might be as simple as a computer restart... or trying a differnt usb port or something.
well, took your advise.. didnt work, but thats because i have vista (go figure). did it on my other comp and it worked
though i'm still faced with the appunlock problem
appunlock didnt work, and every time i go to execute sda unlock it tells me that its "not a certified windows CE edition"? or something to that matter
any help would be greatly appreciated
edit: wow, so i am an idiot. i thought the apps had to be excecuted from the phone.
anyway, did the uspl cid unlock. turned my screen white instead of black, but i'll take it
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 !!!
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
I had what sound like the same problem yesterday.
my post is over at ppcgeeks.
"I disconnected but I did not see the phone exit bootloader mode and reset itself.
....
What should I do from here?
Reboot phone, soft reset, hard reset? - go have fun?
....
I did a couple soft resets and have been playing around with it,
I guess I upgraded right... but it was weird there at the end, instructions not the clearest to me, i guess."
mine seems to be working fine, except the weather thing.
shows
in the About section my phone reads
WM 6.1 Pro
CE OS 5.2.21041
Device Information reads
ROM version 1.05.Alltel
Radio version 3.42.30
PRL Version 30008
PRI version 2.02_011
I was kinda scared to do another hard reset b/c I had already changed a bunch of settings.
Sorry if this doesn't help you too much,
but it is nice to know I'm not the only one with this issue
.
Hmm sounds like a similar problem. But I thought it wasn't unlocked unless we saw 2.31.coke somewhere in the device information.
As far as I know, hard reset did not hurt the phone. I tried installing that unlocker 4 times then went with the original HTC rom and it still turned out just like before. It installed the rom fine
Yeah I am still concerned about how it wont go through the exitbl step...
moonwoo said:
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
Click to expand...
Click to collapse
Yeah, the directions can be a bit confusing over there on that thread
Basically here are the steps
Download the 2.31 unlocker
Download the ROM you want to use (my personal preference is this one for a TF2D style or this one for a WinMO 6.5 style interface that has TF2D included to switch back and for - both very stable, fast and clean and the thread is very active for help (especially if your on Verizon or Bell which can have issues)
from there, use WinRAR to extract each file into separate folders
then Put your phone in bootloader mode (press and hold power+camera+stylus in reset until 3-color screen comes up)
At this point at the bottom of the screen it will say Serial, plug it into the USB cable or cradle and it should change to USB
Start the exe in the 2.31 and follow the directions (you may get some errors about sleep4.exe just click on OK as it keeps occuring its a XP/Windows7 64 bit issue if that is what your using)
At the point where it tell you to disconect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
once complete, reboot, allow it to do its thing then reboot and go back into bootloader again during reboot you should see coke 2.31 in the upper left if so your ready to go
plug it into your USB/Cradle again and then go into the ROM folder you extracted the ROM into
Once the screen on your phone says USB again go to the folder and double click on the RomUpdateUtility.exe file and follow the directions again, it may take some time so be paitent
once the phone flashes and reboots, let it run and do its thing to the and reboot itself then (and here is an important step for stability) once it starts up do a hard reset (red+green+stylus in reset hole) hit the enter button (center of D-Pad) it will reflash the phone and then red key (send) when prompted
then go thought the setup again, this time you can actually set things up as your keeping them this time and once things are done and your at the start screen on your phone power off (not reset) the phone and then start it up again - seems doing it this way takes care of alot of little issues that will come up before they can happen
Depending on your carrier be sure to have one of the DCD Carrier Cabs as well especially for the 6.5 ROM as it is a generic ROM and some have reported needing to run the DCD Carrier Cab for the service they use to get on the internet and use GPS and the like
Hope that clears up things a bit LOL
Detroit Doug
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
moonwoo said:
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
Click to expand...
Click to collapse
Your all set to flash if in bootloader it says as your phone does SPL-2.31.CoKe
you all unlocked and ready to go ... just put your phone in bootloader mode then connect the phone to your PC "serial" will change to "USB" and then run the RomUpdateUtility.exe file and follow along with the bouncing ball, do the watusi, wipe hands on pants - whatever helps you pass the time
but follow the steps as outlined above with the hard-resets and power-offs and the like, believe me its better to solve the issues before they occur than wait and have to start over
Detroit Doug
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
moonwoo said:
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
Click to expand...
Click to collapse
Glad it worked, and Ill try to answer you concerns
1 -Now that it is unlocked go ahead and swap ROMs all you want to, the tricky part is the stock ROM, flashing back to stock can and will revert your radio (if youve upgraded it) and ca cause issues with the unlocker, but a simple run of the unlocker 2.31 again can correct it
2 - NFSFAN like other Chefs have ways of moving data/programs around when they cook up these ROMs utilizing whatever kitchen program they personally prefer that being the case how they data/programs get pushed about can create the speediness you now see in your phone by freeing up the RAM for apps and the like and pushing programs off to the side optimizing how the device should have been setup from the start
As for that, Ive been using his ROMs as well as some others for quite some time and have had little to no issues with how he places the progs and data so I wouldnt worry about it
Yeah, Live in Las Vegas now - but Michigan will ALWAYS be home Go Red Wings !!!!
Detroit Doug
Thanks Doug, for all your information. Your answers were great! Hopefully I wont need too much more help in the future. i'm learning~
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
hibbiejibbie3 said:
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=20370
Detroit Doug
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
Check your PM over at PPCGeeks
Detroit Doug
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
From Detroit_Doug
At the point where it tell you to disconnect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
Maybe wait longer if you can,
I reckon some pc take longer to fully recognize[process] the disconnect and reconnect procedure.
example: disconnect > wait 20-30 seconds > reconnect > wait 20-30 seconds > then continue
I had that same issue and waiting longer during this process helped
.
I can't even get to that point. With active sync on as soon as I start the unlocker RUU it gets the info from my phone and shows the current rom 3.14.605.1 ....I click update and it shows 2.31 unlocker I hit next and then the install status bar comes up on my desktop and my phone goes into bootloader mode and the active sync connection drops and I get the 262 connection error. If I start the RUU with my phone in bootloader usb mode already it does not detect my current rom and I click next. click next to 2.31 unlocker, and it goes through the same steps and I get the same error. Is there anything I have to do to my phone prior to running the RUU. My phone is a verizon xv6900 running wm 6.1 rom 3.14.605.1 with radio 3.37.78
I have the same problem with my new sprint touch. I get error 262 at 0%, did they change something in these new phone that won't allow us to unlock?
Rom is 3.03.651.4
radio 3.42.30
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
I ended up having to re-run the .041 unlocker and then the 2.31 unlocker and it ended up working for me. I'm not sure why I had to because I Had the same bootloader info prior to running the 2.31 unlocker in the first place. The 6.5 rom and gps rom has been working flawlessly for a week now, the only thing I had to do was call up VZW (*8889) the guy answered "account investigations" LOL I told him I had to hard reset and my phone wouldn't authenticate and he asked me to call back from another line. I told him that I had no landline and he said thats fine I can override it just call back right away whenever you get to another phone. That was on friday and I have not called back but I've been able to text, make and receive calls so I don't think I will unless I have to.
gooney said:
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
Click to expand...
Click to collapse
thank you! i did that and it worked for me.
yeah, it says right in the directions over there to just run the exe it will create a temp folder and run the RUU itself from there
Extracting it and running it will always cause issues
also - Ignore the sleep4.exe or whatever if you encounter it - it is a legacy exe that is called that isnt used anymore, wont affect the unlocking just hit OK through it
Detroit Doug
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..