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.
Related
Hey Chaps,
Just thought earlier today i'd have a go at upgrading my phone with the new HTC firmware for my Vodafone Kaiser. First i tried it on it's own only to find the 'vendor' had blocked the upgrade, then i ran the HARDSPL software, when it rebooted my phone to the tri-colour screen i stopped pressing enter on the batch file and ran the HTC upgrade again! ... success - sort of; the upgrade got to 15% and stopped with a connection error (my usb's dodgy i think), then when the phone rebooted to the tri-colour boot loader it'd a) no longer accept the HTC Rom (vendor thing again) and b) become irritatingly broken.
Is it possible to flash an older vodafone rom to the device? if so, where can i find such a beast. Or does anyone know of any devilish ways to put the new rom on using the bog standard bootloader?
Thanks in advance big time to any clever phone experts who can de-brick my... er... brick
Dan.
your supposed to install hardspl before upgrading it if you try it on its own it will brick it at least thats what i heard from the stickies
azazelx, he has hardSPL installed, anyway.
@JimmyJangle: flash via microSD card. [url="http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash" URL]Read here.[/url]
You need winrar to extract file nbh from the shipped ROM.exe.
Hmm, i don't think i do have HardSPL actually installed,
When i saw the tricolour screen come up with different version information I stopped that batch file that was installing HARDSPL (impatiently) and started the HTC one (which failed at 15%). So now i (think) i have a phone with no firmware and the bootloader says:
KAIS130
SPL-1.56.0000
CPLD=8
I reckon if i can find a vodafone made rom the bootloader'll let me install it.
Any idea where i could find one?
What is ur orginal shipped ROM?
Your solution now is flash back the orginal ROM by using microSD card method I mentioned above, install HardSPL succesfully, then flash whatever ROM you prefer.
Hey Nghiem,
Thanks for the help, that link doesn't go anywhere though.
Also, wouldn't i need the original rom from somewhere in order to do that?
Thanks,
Dan
where did you buy the phone e.g vodafone, orange, etc...so I can tell you the original ROM? Because you phone CID is not unlock, hence you must flash the back the shippied one.
Get the WM 6.1 Vodaphone official here http://forum.xda-developers.com/showthread.php?t=365058
Hi,
I got the phone from Vodafone in the UK.
It had WM5 on it... erm, that's it.
I've just beem trying to load original voda roms back on to it but it's not happy - i don't know if they really are the originals though, one says 'reconstructed'.
Dan
Actually, that was the rom i tried and it came up with the Vendor ID error.
Dan.
Link on post #6 is the official not reconstructed. How about download directly from Vodafone website? It's strange when you have carrier ID block even with its ROM. Also, try reconstructed ROM listed here http://forum.xda-developers.com/showpost.php?p=1586817&postcount=2
Search for mtty, see if it can help you out.
MTTY saved the day!
Only 3 hours of my life lost!
Thanks,
Dan
Cheers. Don't forget to flash HardSPL and read the wiki before doing anything.
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Before I flashed my first rom, I read wiki.xda-developers.com to make sure I understood what I was doing, and used the search button, instead of risking turning my phone into a paper weight.
Since then, Crackwhore has written a very helpful post at the top of this forum about how to use HSPL and USPL to allow you to flash roms.
yeah i know all that. not my first time flashing a phone but the first time it got stuck loading the bootloader. and specially when i´ve only used the HTC update.
darfor said:
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Click to expand...
Click to collapse
you mean you couldn't get to boot loader page?
So you already have HSPL 1.56 installed (or have SPL1.54 and used USPL)?
If you have HSPL you could try renaming the .nbh file to blacimg.nbh and copying it to the SD card and entering bootloader
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
AFW said:
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
Click to expand...
Click to collapse
try dnloading the rom again amd try.
the file might be corrupt
Have tried that many times. File is not corrupt. I'm getting really worried this is now a brick...
OK, if you can get phone into bootloader, it is not bricked
What does your SPL say in bootloader? Do you get any errors when trying to flash rom? Are you using USPL or HSPL? If USPL, you have to use it before every flash to new rom or radio. If HSPL, are you using correct version?
Was on Dutty's 3.9 XT, but decided to revert to standard WWE 1.56. I flashed the Std 1.56 ROM successfuly, and then tried to restore the ship SPL 1.54 using the card flash method. This failed, and now I'm stuck on the bootlader screen forever.
No matter what I do the THD always goes to bootloader (red-green-blue-white screen), with following text:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
Upgrade ROM code error
Please try again
USB
Click to expand...
Click to collapse
When I start blac_uspl.exe (USPL 2.5), a window flashes (Vista64) for a split second and then nothing else happens. The Vista64 system's USBs work with THD and have been used to sync over past few months.
When I try to run HSPLWrapper_Blackstone_156OliNex.exe and step through the preliminary screens, the Verify that you want to update ROM version screen has the From Image Version as blank and the To Image Version as 1.56.Olinex. When I click to commit the flash the THD screen switches to white with a progress indicator that always stays at 0% until it times out. Recovery does nothing and the same thing always happens. Using Vista64. .Net installed and fine. I can't use the card method (BLACIMG.NBH) - the system also stays on "Loading .... 0%" and nothing else happens.
When I try to flash anything (have tried HSPL1.56, Dutty's 3.9 ROM, stock 1.54 spl) using the card method, the system says "Loading . . ." and hangs there forever without a progress indicator showing.
Your SPL says 1.54.0000. When you try and run USPL.exe have you remembered to disable your antivirus?
Have you tried usb method instead of card for flashing rom?
I know you have said that youi have used usb for syncing, but when in bootloader does it change from 'serial' to 'usb' when you connect HD to PC?
Fallen Spartan - I want to thank you for taking the time to help me resolve this problem. Very much appreciated!
1. Yes, anti-virus disabled and indeed removed from the PC.
2. Yes, have tried the USB method at least 20 times.
3. Yes, the bootloader changes from Serial to USB. It then goes to the progress indicator screen and hangs on 0%. The progress indicator on the RUU on PC also stays at 0% and eventually times out. I've gone through the Recovery routine at least 20 times, with no luck.
When I try to run SSPL-Manual-TouchHD.exe it says "not a valid Win32 application".
I'm a bit perplexed by this.
You have obviously successfully flashed Duttys V3.9 so drivers are fine, you know how to use USPL, both flashing methods (SD card and usb/pc), disabled anti-virus, phone in bootloader.
Have you tried to reflash 1.56 rom or possibly performing a hard reset before trying to use USPL or HSPL. I doubt this would make a difference though.
Have you tried cRaCKwHoRe's USPL GUI v 2.5 Application?
You don't get any code errors?? I'm struggling to find a solution here.
Yes, this is most vexing. I've flashed innumerable times before and never had an issue. I suspect the SPL is fine, but somehow the actual WM ROM image is corrupted. Will now try to load Std 1.56 ROM image again...
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa (though I'm a rugby fan).
AFW said:
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa.
Click to expand...
Click to collapse
No accomodation required, just glad you got it sorted
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
can anybody help me at all
Adamsville: perhaps you're stuck in bootloader mode because the WM ROM image flashed on your system has become corrupted or disabled, ie the only thing the system can boot into is the bootloader.
Try flashing a new compatible WM ROM image and see if that works.
AdamsvillE said:
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
Click to expand...
Click to collapse
a hardreset followed by a 1.54 base rom will solve all ur probs.
or lower spl to 1.14 cos ur stock rom is a 1.14 base as suggested by th name..
cheers
OK. Decided to upload a new ROM as my phone was getting slow and unusable.
It's an O2 XDA (Touch Diamond) with:
Touchflo v3 Build 29946
ROM 1.93.206.6 WWE
09/08/08
Radio 1.00.25.05
Protocol 52.29.25.12H
Boot R1.00.25.05
I downloaded Olinex's unsigned developer Hard SPL and I extracted the NBH file and renamed it DIAMIMG.NBH following the advice here:
http://forum.xda-developers.com/showpost.php?p=2707841&postcount=4035
On soft reset I pushed the vol down and back buttons to get the boot loader stripes, then let go.
I now have a screen which says "Loading..." and has done for 20 minutes. I have now got the phone on charge while I wait for some help to see what to do next, just in case this is a critical stage - don't want to brick it.
Reading through again I am concerned that this was a procedure for rom upgrade not Hard SPL install, can someone tell me please?
Thanks in advance for any help.
Well, I ended up taking the battery off to get it to reboot. It seems to boot fine back into the old ROM.
I still intend to upgrade it (to SwiftBL's v7.5) but have a few questions:
1. Can the HardSPL be run from the internal storage card? If so is it simply running the exe from the unpacked zip from within a folder? ActiveSync is a bit too flaky for me.
2. Do I need the SIM card in the phone at any stage of the ROM upgrade?
3. On the original ROM I get a drop down menu to setup the phone to the UK O2 network settings. If I load a new ROM, will I need to know these settings?
Cheers
1. HardSPL cannot be run from storage. Only Activesync or Bootloader
2. No. You can flash without SIM card
3. You can use connection setup on any new ROM. Usually starts straight after initial setup.
OK here's where I'm at now.
Downloaded jockyw2001's HardSPL 1.24
Ran it and it got as far as prompting me to run on the phone. I said 'Yes' and the HTC screen went black as expected.
Next stage was to run the DiamondCustomRUU.exe file which I did but this is waiting for ActiveSync. ActiveSync will not sync with the phone now, I guess because the phone is not 'on'?
Where do I go from here?
Use the Hard-SPL in my sig with your RUU.
Thanks, will do (it's not the one mentioned in the ROM author's description though).
So how do I recover the phone from the black screen now? Is it safe to remove the battery to reset?
Battery pulled after reading this post:
http://forum.xda-developers.com/archive/index.php/t-427945.html
I'll try the SPL you mentioned now.....
Had a good search but can't find out. This Olinex zip contains just one file RUU_Signed.nbh.
Where do I get the other files from to run this?
use the attached . It has the RUU exe and the nbh.
Thanks. This is a signed version I see, was going to use SwiftBL's ROM which requires unsigned.
May take a look at other roms that use signed unless you think that I can load the SwiftBL rom with this version?
Dear Readers,
I have a few concerns about my recently bought Htc diamond.
The problem is that during bootup it stays frozen on the Touch Diamond bootscreens.
It has HardSPL Olinex v1.93 on it.
First i flashed back to the Stock Rom, worked fine only a couble of unexpected freezes wich made me think into using Mtty(set 14 0, task 29, task 8) to fully clear the phone and than reflash the NLD rom back on it.
Now flashing the rom went al the way 100%, and Congrats me after that.
I rebooted after that but never goes past the bootscreen with the red info lines.
So i thougt that restoring the SPL 1,93 olinex to factory setting might do the trick. But there is no way to do that since i cant get active sync to connect!
My problems is that although i can acces all bootloadmethods ,the phone is being recognized through USB, and all Rom/SPL flashes goes up to 100%. It still doesnt seem to save that rom on its memory.
and when i check the screens of the CustomRUU program it doesnt show any info add the older software version, only shows the info of the rom wich im going to flash.
If i check the USB icon on the task bar while connected to the pc, it says something like ..Qualcomm CDMA.. etc. ! the phone wasnt a CDMA version!
Any ideas?? is it Fixable or do my cats have something new to chew on??
many thanx,
Jeffrey
Copy any ROM you want to your Internal Storage, rename .nbh to diamimg.nbh, Restart your diamond and than immediately press Vol Down and back button, once in a bootloader press power button to flash rom, once finished restart Diamond, and see if ROM will be installed successfully
benko286 said:
Copy any ROM you want to your Internal Storage, rename .nbh to diamimg.nbh, Restart your diamond and than immediately press Vol Down and back button, once in a bootloader press power button to flash rom, once finished restart Diamond, and see if ROM will be installed successfully
Click to expand...
Click to collapse
Dear Benko,
How can i get acces to the internal storage?? Since the phone doesnt boot far enough to get connected in Active sync... are there other methods to acces the internal storage?
The USB trigger mode didn't work either as its not recognizing any flashdrive i connencts to it..
http://forum.xda-developers.com/showthread.php?t=540290
Especially this post:
http://forum.xda-developers.com/showpost.php?p=4194865&postcount=4
divxmaniak said:
http://forum.xda-developers.com/showthread.php?t=540290
Especially this post:
http://forum.xda-developers.com/showpost.php?p=4194865&postcount=4
Click to expand...
Click to collapse
What to do with this link??
I got Mtty running but i cant acces internal storage to copy a rom to it, and flashing by USB went all the way 100% but somehow the phone never boots in to the flashed rom.
Even trying a reflash doesnt show any signs of an older Rom being present on the phone memory..
One question about Mtty, when its said to use the ROM flasher i kinda assumed they ment the CustomRUU program. Am i right, or is there some build-in command to Flash a ROM within MTTY??
jvanzeijst said:
What to do with this link??
I got Mtty running but i cant acces internal storage to copy a rom to it, and flashing by USB went all the way 100% but somehow the phone never boots in to the flashed rom.
Even trying a reflash doesnt show any signs of an older Rom being present on the phone memory..
One question about Mtty, when its said to use the ROM flasher i kinda assumed they ment the CustomRUU program. Am i right, or is there some build-in command to Flash a ROM within MTTY??
Click to expand...
Click to collapse
i had the same problem.... i send it back to repair... had a hardware damage. Luckily i got it for free...
I don´t know if you have exactly the same problem, but it looks like that.
LORDShadowMan said:
i had the same problem.... i send it back to repair... had a hardware damage. Luckily i got it for free...
I don´t know if you have exactly the same problem, but it looks like that.
Click to expand...
Click to collapse
Well lets hope not, because i got mine for 50euro secondhanded, warenty is expired and im really not keen on spending more money on repair than what i paid for.
Have you tried to put another Radion on it?
dravik said:
Have you tried to put another Radion on it?
Click to expand...
Click to collapse
Actually yes i did and it doesnt make any difference.
The weird thing is that even after succesfull flashing both Harspl and Rom never seems to stay on the phone memory but the Radio get updated.
jvanzeijst said:
Actually yes i did and it doesnt make any difference.
The weird thing is that even after succesfull flashing both Harspl and Rom never seems to stay on the phone memory but the Radio get updated.
Click to expand...
Click to collapse
I had a problem with my phone where I did mtty, but forgot to rename the diamimg.nbh file on my phone. So it wouldn't get passed the bootscreen.
My solution was to connect the phone to the usb, hold down the up arrow(I think it was the up arrow) and soft-reset. It came up with those 3/4 color blocks and said "usb" at the bottom. I then used the official htc ruu(also didn't show the current rom on it) to flash the normal htc rom onto it and it worked. Then I just did the normal procedure to get the custom rom on again.
So are you trying to flash the original HTC rom onto it, or a custom rom? Cause if it's a custom ROM, maybe it's just the radio, not the actual OS?
moreph34r said:
I had a problem with my phone where I did mtty, but forgot to rename the diamimg.nbh file on my phone. So it wouldn't get passed the bootscreen.
My solution was to connect the phone to the usb, hold down the up arrow(I think it was the up arrow) and soft-reset. It came up with those 3/4 color blocks and said "usb" at the bottom. I then used the official htc ruu(also didn't show the current rom on it) to flash the normal htc rom onto it and it worked. Then I just did the normal procedure to get the custom rom on again.
So are you trying to flash the original HTC rom onto it, or a custom rom? Cause if it's a custom ROM, maybe it's just the radio, not the actual OS?
Click to expand...
Click to collapse
I tried both custom and Stock Roms several times. After flashing the Stock roms i noticed that the radio version get updated, just no OS to boot!
Since the flashing sequence completes to 100%, i think its strange that the os doent seemed to be copied at all. Is there a possibility that a bad SPL is causing the OS not to be found?? In the Bootloader it still says SPL v1.93 Olinex so i guess its still Hard spl'ed. But when i try connect the phone to pc by usb, it shows up as Qualcamm CDMA device then later changes to HTC...
The Phone is not a CDMA version but i think maybe there is a change that somehow a CDMA SPL accidentlly got uploaded to it. This supposed to cause a phone to brick.
Many thanx for trying to help!
jvanzeijst said:
I tried both custom and Stock Roms several times. After flashing the Stock roms i noticed that the radio version get updated, just no OS to boot!
Since the flashing sequence completes to 100%, i think its strange that the os doent seemed to be copied at all. Is there a possibility that a bad SPL is causing the OS not to be found?? In the Bootloader it still says SPL v1.93 Olinex so i guess its still Hard spl'ed. But when i try connect the phone to pc by usb, it shows up as Qualcamm CDMA device then later changes to HTC...
The Phone is not a CDMA version but i think maybe there is a change that somehow a CDMA SPL accidentlly got uploaded to it. This supposed to cause a phone to brick.
Many thanx for trying to help!
Click to expand...
Click to collapse
Ok, maybe you can try from scratch to re-flash everything?
You should still be able to HardSPL, by doing the soft-reset+vol down thing.
I'd suggest getting the HardSPL from here(I only used it once, but I know it worked for me):
http://forum.xda-developers.com/showthread.php?t=416211
Hopefully that alone is what you need but if it isn't, you should then be able to flash a radio onto the phone(there's a link in that thread too) and then the stock HTC rom(I think the stock would have a better chance than anything else)
All of those flashes should be possible by doing the soft-reset+vol down and then using the RUU. Do you know how to use the RUU to flash a HardSPL, Radio and then OS separately?
you should probably try a full mtty just before you flash the OS(just after you flash the radio) as well, do the set 14 0,task 28 and task 29 and then task 8
And regrading Windows picking up your phone as a CDMA, I can't remember what mine said, but I don't think you should worry much about what Windows thinks the phone is.
*Edit, you should follow the mtty guide here for the most part:
http://forum.xda-developers.com/showthread.php?t=540290
But the second last step(number 7) where you're required to remove the usb cable, soft-reset+vol down+back button to flash from the internal storage, you should keep the phone connected to the usb and soft-reset+vol down and flash the rom using the RUU
message deleted
moreph34r said:
Ok, maybe you can try from scratch to re-flash everything?
You should still be able to HardSPL, by doing the soft-reset+vol down thing.
I'd suggest getting the HardSPL from here(I only used it once, but I know it worked for me):
http://forum.xda-developers.com/showthread.php?t=416211
Hopefully that alone is what you need but if it isn't, you should then be able to flash a radio onto the phone(there's a link in that thread too) and then the stock HTC rom(I think the stock would have a better chance than anything else)
All of those flashes should be possible by doing the soft-reset+vol down and then using the RUU. Do you know how to use the RUU to flash a HardSPL, Radio and then OS separately?
you should probably try a full mtty just before you flash the OS(just after you flash the radio) as well, do the set 14 0,task 28 and task 29 and then task 8
And regrading Windows picking up your phone as a CDMA, I can't remember what mine said, but I don't think you should worry much about what Windows thinks the phone is.
*Edit, you should follow the mtty guide here for the most part:
http://forum.xda-developers.com/showthread.php?t=540290
But the second last step(number 7) where you're required to remove the usb cable, soft-reset+vol down+back button to flash from the internal storage, you should keep the phone connected to the usb and soft-reset+vol down and flash the rom using the RUU
Click to expand...
Click to collapse
Allright i'll give it another try..
keeping my fingers crossed!
moreph34r said:
Ok, maybe you can try from scratch to re-flash everything?......
Click to expand...
Click to collapse
Ok i tried its flashing the Stock HTC NLD rom now aroun 42.. 43%, its slow but atleast still going. This is a big Rom tough.
Two questions:
1. Flashing the hardspl took some time to initiate the progression bar and then suddenly in the blink of an eye from 0 to 100%,
after flashing the hardspl file wich showed in RUU as olinex v 1.40, it still showed SPL.193 olinex on the bootloader.. .. is this common??
2. Is it even possible to downgrade a bootloader?? i would love to have olinex 1.40 back.. i used it before and it worked fine on many roms...i keep thinking my SPL is the problem.
Bye now the Rom flashing finished and it didn't help.. its still frozen.
here is the output from MTTY, may be its usefull:
----------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xFF40, total sector=0xB080
Storage start block=1054, total block=706
Total Bad Block in CE: 0
Erase physical block from 1344 to 2032
si backup: Erase physical block from 2032 to 2048
Format end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>task 8
-------------------------------------
,thanx any way
Did you use the corresponding stockRom (the one with the corresponding spl i mean):
_QMR_RUU_Diamond_HTC_NLD_1.93.404.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
Just in case you didn't, you can find it over here:
http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
Yes i did try, didnt work for me..
i kinda lose hope now.
Losing a phone sucks, first lost my iphone3g then bought this cheap as a replacement for the remaining contract, And now i really regrets that i tried restoring its stock rom,radio,spl since its really did brick the phone for good..
thanks for all the people that tried to help but i'm not sure if its fixable....
So thanx anyway..
yours,
Jeffrey
Mod. edit: not dev related, moved to general
gl though
So my problem is - I put android on my htc tytn II and it worked (well kinda) but anyway I decided to switch back to Windows Mobile...
I installed 1.27.x.x radio , found a Windows Mobile 6 ROM and put (Like in the instructions ) Kaisimg.nbh(renamed from ruu_signed.nbh) and Kaisdiag.nbh to my SD card and then started flashing... It flashed smth,rebooted automatically and started booting android again...
Then I hold again camera button + power+ reset and since then when I put EVERY .nbh file on my sd card and try to flash it it STUCK on "Loading.." If I try to flash it with USB It stays at 0%.
The only exeption is if I try to flash from USB the rom that I tried to flash before from my sd card.. then it starts 0%..1% and reboot the phone...
P.S: Please help me...I think my device is not Broken but I dont know what should I do to fix it...
To flash back to WM from android put your kaiser into bootloader (multi colored screen) Then connect to usb. Download any WM build that is recent (I suggest Phoenix 3 for this, you can flash whatever you want later). After you download it open and run the included RUU that came with it and it will flash it on there.
hmm, I also had experienced the similar problem on my 1st time flashing back to WinMo.
When you are trying to flash via USB cable and the process stopped at 1% I guess there is also a message about "Invalid vender ID" right?
and if the text in your bootloader (tricolor screen) doesn't mention anything about hard such as "3.29.0000" (not "3.29.hard")
then
you've lost your hard SPL that's why you cant flash any .nbh to your phone.
I had managed to solve this problem by flashing stock WM rom for kaiser. The rom also has to be suitable for your phone, I mean if your kaiser is originally from France, then use French kaiser stock rom. Or if you are using AT&T Tilt use kaiser cingular stock rom.
you can find the list of shipped roms for kaiser here :
http://shipped-roms.com/shipped/Kaiser/
If you still have the "invalid vender ID" error message, try another stock ROM.
Thanks man you're my hero! I though I lost my phone.. anyway i bought new one - Nokia 2730 Classic but Ill sell the kaiser...
Thanks Anyway ... you're god!
Have the same problem...
Firstly, I'd like to point that the reason for the hard SPL getting overwritten by an original SPL is NOT HAVING UPDATED HARDSPL to a newer version that prevents accidental overwrite. This is instructed in the previous steps before actually installing Android. That was my mistake (I had HardSPL 1.0 OliPof), and now I can't flash no rom to my Kaiser (which thankfully works quite well in Android).
What happens (please correct me if I'm wrong) is that "KAISDIAG.NBH" is a modified, standalone hardSPL that will flash to the phone the SPL that comes with the "KAISIMG.NBH" you put in your SD card with "KAISDIAG.NBH"). In my case, I used the WinMo 6.1 spanish version 3.29.412.0, which, resulted in my phone being flashed with the original SPL 3.29.
Now, it seems many users have fixed this locating the correct stock rom and flashing it in their Kaisers. But to others, like myself, nothing seems to work. I believe that this is because we not only need a stock rom for our specific Kaiser model, but also it has to be compatible with the SPL that accidentally got installed in the phone. The problem is what if such rom doesn't even exists?
I'm really thankfull for all I learned by reading the forums (and from my mistakes ) and I know I'm in no position to make requests, but here goes what I think could help the users like myself to fix this, if posible:
1) Guide to identify what model of Kaiser we have (maybe it's already there, I just couldn't find it)
2) Complete list (or lists) of stock roms (There are some around, those are easy to find I think, but it doesn't hurt to share different sources)
3) Something like a JumpSPL for Android would be more than awesome...
Thanks in advance to everybody, sorry for my own stupidity . Any idea or help would be much appreciated,
Daniel
hmm, I'm not sure if it has to be compatible with the SPL.
In my case, I was flashing a very old WWE stock rom which has original SPL 1.56.
I also had been very desperate because any stock rom I found seems doesn't work and I even didn't know where originally my kaiser came from because I get it from my uncle. So I tried to flash any WWE stock rom I could found but nothing works. I read from Wikipedia that based on my phone model (Kais100), this model was only sold as AT&T tilt for US. But the problem is my phone is HTC branded, not AT&T tilt. Well, based on this information I also tried to flash some cingular stock rom but the result was just the same.
After contacting HTC Customer care, I know more info about my phone. They told me that based on my phone product ID, my kaiser was originally shipped for US, but unfortunately they can't provide me stock rom for my phone model. So I searched myself but this time I had better objective : to search HTC branded rom but for US.
finally, after days of search. I've found the rom that is suitable for my phone. Its called HTC WWE Brightpoint US which has original SPL 3.29 at the bottom of the list on the website I told you on my previous post.
few weeks ago I also accidentally overwrite my HardSPL again, but this time I did it with the stock ROM which has original SPL 3.29. But this problem also solved by flashing the stock ROM I've found before via USB cable.
So, I guess it has nothing to do with spl version.
Keep tying don't give up.
Update: Step 1 completed! YAY
Using the serial number and some obscure google searching, I came to the conclusion my KAIS130 is australian. Cheers, mate!
I verified this by being able to download stock roms from the australian HTC site with my Kaiser serial number. But at the moment of writing this, have downloaded two roms and no luck yet. 5 minutes remaining for the third one... Wish me luck...
Daniel.
Well... Now what?
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
cuartetoraro said:
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
Click to expand...
Click to collapse
sorry to hear that..
well, extract the .nbh from exe and flash it via sd card is the method that made me overwrite my hard SPL in the first place.
hmm, did your phone comes with operator brand, such as three or something?
-Rif- said:
sorry to hear that..
hmm, did your phone comes with operator brand, such as three or something?
Click to expand...
Click to collapse
No, it's HTC unbranded. Now, something strange here: the label behind the battery has the serial number: HT830GB06075 and the P/N (guess it's part number) :99HCY194-00, but to the left of the camera, another label with the part number: 36H00563-00M and below says DATE:061107(TB02)/US.
I don't know if that's normal, but it caught my atention because my phone seems to have been dissasembled (little label over screw is teared). Maybe my Kaiser isn't Australian after all...