Kaiser - Cant flash back to WM after flashing Android - Tilt, TyTN II, MDA Vario III General

Hi there, I have a problem with my HTC Kaiser
I've managed to unlock it and flash any rom and radio i wanted, everything worked perfectly, I've had HardSPL 3.34 if i remember correctly
Them, i tried running android, flashed, started booting and... din’t boot. It starts booting but it stops with the following message: [4.2.08726] fake_vsync_int
No problem, i will just reflash back to WM6.1 and get going, BUT... i could not reflash anymore
I noticed that my SPL version has changed, it now shows: KAIS120 - SPL-3.34.0000 - CPLD-8 - USB
I could not flash any roms I've had, searching around i tried many solutions even trying flashing using the MicroSD card without luck
The errors: Either stays at 0% and... ERROR [262] : UPDATE ERROR
or
Gets to 1% and... ERROR [294] : INVALID VENDER ID (When flashing from USB)
Or remains stuck at “loading...” (When trying flashing from MicroSD)
Looking around i found that what i need was to flash the stock rom that came with my Kaiser, my kaiser was WM 6 Portuguese Brazilian, so i got the rom: RUU_Kaiser_HTC_WWE_PTBR_1.88.514.1_PTB_Shipped
Din’t worked
So i tried every rom found here: http://www.shipped-roms.com/index.php?category=windows mobile&model=Kaiser
Din’t worked either
So i tried every other rom i could find, from Chinese roms in support.htc.com to roms found online on file sharing sites, none of them worked
This is a similar problem encountered by Warbyte here, and -Rif- Here, -Rif- managed to find the correct rom, apparently Warbyte din’t have as much luck, to quote him: “Apparently the only solution is to find the matching original ROM which puzzles me as there apparently exists none”
Without other ideas i decided to come here and ask for advice, since i don’t know what else i could try
Any ideas? Thanks for your time.

Related

Hang in bootloader

Hi @ all,
**** happens, yesterday i tried to upgrade my rom on charmer (mda compact 2).
During installation system hangs on and didn´t finish.
So now i have only the startscreen and can reach the bootloader.
Tried now to flash an original rom, the ruu says error 294 invalid vendor id.
Otherwise the ruu (for no id) ended with error 238 file read.
My bootloder shows IPL 1.12, SPL 1.12 and USB connected.
I have read a lot of threads but cant find a answer for that.
Has anyone a good idea?
Thanks a lot for helping.
I wish all users in that great forum a happy new year
ronni
Hi Ronni,
same problem here. Do you found any solution?
Is it right, that your Device not charging and USB is not recognizing too?
Bg
Joy
Are you trying to flash WM6 ROM to your charmer? Because WM6 required IPL and SPL level at least 2.xx.
Did you tried this method to bring charmer back to life?
wow, thank you for your quick response. Hmm, I´m not shure, it´s a PDA from a Collegue, I don´t know, what he do with it. (I know only he try to flash something) Next week he take it to our office, then I try your solution
Thank you again
Joy
Bootloaderhang
Today i tried to update my rom... while the update i had an error.
i had updated the http://forum.xda-developers.com/showthread.php?t=363882
after the hardreset the phone hang by the first screen. I can press everething but nothing happens.
now I tried to flash a nother rom but it is unpossible because it can´t connect with windows mobile center on the pc.
Has anyone a good idea?
Thanks a lot for helping.
I wish all users in that great forum a happy new year
didi500

Corrupt HD?

Hi,
I've just upgraded to a new Dutch rom, but since then I only have trouble.
I get different colours (like drivers are not loaded), it keeps getting stuck or resets itself, and nothing helps.
I've tried to put on a different rom, with succes, but I still have the same problems.
On startup, however, I see the right colours.
I also put back the latest original ROM, but no luck...
Can anybody help me?
guessing you have hspl 1.14 installed
Yeah, I reinstalled that, as one of the latest things I did.
The problem you describe happens when you flash a 1.56 based rom with 1.14 HSPL. First flash a stock 1.56 ROM (a new SPL is then flashed as well) or use the new HSPL. Then you should be fine. So no, it's nor corrupt!
For more info, read crackwhore's guide (sticky)
Well, I'm trying to do so now, but it keeps getting stuck at 0%...
Does it matter I have an NLD-version, and not a WWE?
Update: I cannot get a proper connection via activesync, and through the bootloader it stays at 0%, and after a while the update utility says no.
Update 2: ah, thanks to troubleshooting, it looks fine!
THANKS!

error 226 upgrading vodafone diamond

Hi to everyone.
I've just bought a HTC Diamond on the vodafone network, but need to unlock it as I'm on O2's network.
I've been able to install SPL 1.4 and this shows on the boot loader page.
The problem seems to come when I try and install the 'new' rom. It goes through the whole stage up to 100%. Then on the device it says error code please try again. On my Pc it says error code 226. I've tried it on a windows vista pc, and again on XP. I've also tried it by installing it direct onto the internal storage. This again goes through the installation up to and including 1005, but then come sup with a new screen on the device saying that the update and the radio have both failed to install.
I'd really like to unlock my device and to have a new rom so that I dont have all the vodafone branding.
Like many others, I'm willing to contribute so that research and new software is developed, and I have also read the forums for many hours trying to find a solution to my problem before posting.
Hopefully I can be directed to some help.
Kind regards.
Just to update and incase anyones interested.
I ended up downloading the latest version of the official rom that I could find, then extracted the nbh file using winrar, and installed that from the internal storage which has successfully worked.
Not sure why the other rom image I had wouldn't work, just glad I've got rid of the vodafone bits really.
Regards.

X1 and WinMobile 6.5 (Error 260 with HardSPL)

Hi,
I have some trouble on upgrading my Xperia X1 to Windows Mobile 6.5.
I tried to upgrade some months ago with the same error. Now I finally wanted to upgrade, but it doesnt work.
Ive read several instructions here and on a German board, but unfortunately without any success.
The only thing Ive noticed: HardSPL says, that I am running version 1.05.x on my phone and the new version would be 1.00.x, could this be the reason for the breakdown?
I am also looking for a current German Rom for the X1. The one I tried is from http://forum.xda-developers.com/showthread.php?t=526133
I'm not sure, if there are any newer versions, but it would be nice, if someone could help me.
Here is what I did:
- downloaded the german rom, mentioned above
- unpacked the kovsimg.nbh and put it onto my SD card
- started the HardSPL with the instruction
-> error 260 at 0% (after like 1 minute)
Please help me, I dont know, what I am doing wrong
PCServe said:
Hi,
I have some trouble on upgrading my Xperia X1 to Windows Mobile 6.5.
I tried to upgrade some months ago with the same error. Now I finally wanted to upgrade, but it doesnt work.
Ive read several instructions here and on a German board, but unfortunately without any success.
The only thing Ive noticed: HardSPL says, that I am running version 1.05.x on my phone and the new version would be 1.00.x, could this be the reason for the breakdown?
I am also looking for a current German Rom for the X1. The one I tried is from http://forum.xda-developers.com/showthread.php?t=526133
I'm not sure, if there are any newer versions, but it would be nice, if someone could help me.
Here is what I did:
- downloaded the german rom, mentioned above
- unpacked the kovsimg.nbh and put it onto my SD card
- started the HardSPL with the instruction
-> error 260 at 0% (after like 1 minute)
Please help me, I dont know, what I am doing wrong
Click to expand...
Click to collapse
not many details, but let's see
you successfully flashed h-spl (from olinex thread)? and when trying to flash custom rom you get the error 260? that right?
ensure to use customruu for flashing and not the ruu (hardspl.exe) from h-spl thread
if you use sd for storage of rom image, why not flash using sd-method in the first place?
a newer german rom is here

Back from Android to WM6 problems

Hello everyone!
I recently installed Android Froyo 2.2 (Incubus26Jc's Super FroYo RLS15 All Language), following mainly this thread http://forum.xda-developers.com/newthread.php?do=newthread&f=602, and also reading many others, about hardspl etc.
Everything went perfect! The phone workes just fine, full functioning!
My problem is that, after deciding to go back to windows mobile for selling my phone, I followed these steps :
"Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH.
Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When the flashing is done you should be back to running Windows Mobile."
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Also, when I press the power button+camera button, for a new update flash, after the three colors screen(KAIS130, SPL-3.07.0000, CPLD-8), the message "Loading..." appears and stucks.
I guess, my phone no longer has hardspl, and there is no way to put it back, neither put back the signed rom, if there is no WM os????
Any help/suggestions???
Thank you very much, in advance
I suggest you follow the tutorial switch back to Windows Mobile by Dukenukemx ~ http://forum.xda-developers.com/showpost.php?p=6461906&postcount=1
looks like a really lost hardspl. Maybe this will help you get back to windows http://forum.xda-developers.com/wiki/index.php?title=Kaiser_stuck_at_bootloader
aris0602 said:
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Click to expand...
Click to collapse
One question:
What version radio was on the phone BEFORE attempting a WinMoBlows flash?
It looks like the shipped rom had the 1.27.12.17 radio included in the bundle and, if so, this would explain the error in flashing.
One thing to check would be at the bottom of "Settings" page, touch "About Phone". Towards the bottom you will see "Baseband Version". The numbers at the end are your radio version and should be the original radio numbers. If it says "1.27.12.17", you've found one problem...
I would say follow dukenukem's post and try to reflash HardSPL again.
I haven't run into this problem yet since I will probably never sell either of my Kaisers... lol.
same problem at my place...
installed android, about 2 month ago, wanted to switch back to win and couldnt do it that simple as say "Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. " in Dukenukemx's tutorial.
I have tried everything putting on sd card many ROM's Hardspl's, then i found this on my pc RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88. 07_1.27.12.11_Ship when i try to flash via usb (manually enter bootloader and connect usb cable) it get to 1% and reboots and ond rom update software says ERROR [294] : INVALID VENDER ID and above Exit button says: VER4-KBKV5867-HUEbc568-KBKV58670...
and when i try same rom to flash via sd card it says
Loading...
Checking...
0028002
Not Allow
with any other it stay's at 0% on phone and nothing is showed, then on RUU says ERROR [262] : UPDATE ERROR and down is button Recovery, tried a lot's of times nothing...
Then i saw that you PoXFreak said to check radio in baseband mine is 1.65.17.56
any sugestions please?
Another user with problems...
Tried a return from android to windows mobile because of the random locks that were happening in android (also some other weirdnessess...)
Now when it is put a microSD with kaisimg or kaisdiag it goes into white loading screen and stay there...
(tried flashing Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, that seemed to be the one who came with my phone)
The baseband message somebody talked above shows only "HTC"
When in tricolor bootloader the following is showed:
security unlocked
KAIS***
SPL-3.28.0000
CPLD-8
(Still gonna try updating it connected to the computer, seems like usb and serial dettection are working, for it will dettect the charger connection and start showing USB in the lower part of the screen, battery got very low overnight, still needing to charge it to really do some test)
_____________
Update:
Flashed ok through USB, just entered tricolor bootloaded, connected usb and executed the original rom installer.
hello everyone
I used to have this kind of problem.. my hard spl broke when i tried to flash a stock wm rom from android.
In my opinion, each stock roms comes with specific SPL, radio version, etc. It means that when you are trying to flash stock rom, you also flashing new SPL. the problem is, the new SPL broke your hard SPL so you won't be able to flash anything to your kaiser except your original stock rom which comes with your kaiser.
you can find some stock roms for kaiser here : http://shipped-roms.com
Since I'm only sure that my kaiser originaly comes with WWE version I almost tried all the WWE stock roms there, but my search ended when I flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe, this rom works for my phone and it seems that only this rom didn't give me "invalid vender ID" message.
so, keep trying to find your original stock rom
and after you managed to flash your stock rom, don't forget to flash hard-SPL again if you still want to mess around with your kaiser.
good luck
Another way to do it, albeit a little tougher, would be to use Oli's NBH tool and remove the SPL and radio from a stock rom. That way you get to keep the radio and SPL while flashing a stock rom.
Keep in mind that some WM roms only like certain radio versions, and you may end up having to flash an older (or newer) radio to find what works best.

Categories

Resources