I recently updated to stock spl 15.000 (from OliNex's spl) to combat the green, fuzzy, screen problem on the new official ROM but nothing will update; I've tried:
-Going back to official ROM's, which results in 'Error: Invalid Vendor ID'
-Going back to OliNex, it just sits at 0% before timing out and going to a recovery console (which is useless)
-Downgrading/Ugrading to official and Dutty's ROM's using USPL
Any help to get back to OliNex would be great.
Thanks
+The phone still works but I can't upgrade it.
Yes i got there too. Drove me nuts...
To install Duttys 2.7 Xtreme Follow points 3 & 4 in this post - works great
http://forum.xda-developers.com/showthread.php?t=503225
or... if you want to get back to OliNex - run USPL then run HSPL to restore back to OliNex
solution
try flashing with sd card loaded the original firmware.
Cheesy95 said:
1. - Going back to official ROM's, which results in 'Error: Invalid Vendor ID'
2. - Going back to OliNex, it just sits at 0% before timing out and going to a recovery console (which is useless)
Click to expand...
Click to collapse
1. - I've encountered the Invalid Vendor ID error too. To work around this, you have to flash the official stockrom in the language you purchased your HD in. That worked for me.
2. - Did you connect your device with Activesync (or WMDC) before you started the HardSPLWrapper? Also you dont need to put the phone into Bootloader mode. Just plug your USB cable in and let it sync. If not sure: follow the instructions in the HardSPL thread.
It has to work, it did with me.
Grtz... Jeat
Thanks everyone. It's working now, I was doing it in bootloader mode 'cos ActiveSync failed me. But now it's up and running again, everything is back to normal, and I can go back to trying new, more awesome, ROM's I installed the latest official ROM and now I'm half-way through flashing Dutty's EXTREME 2.7. I'd still be stuck with the crap official version without your help Thanks again!
Related
Is it possible? I'm stuck on the stock ROM on SPL 1.54 at the moment, USPL not working.
I did a search but nothing came back about this... it's all in the wording
Been there done that...
I had to revert back yesterday after hours and hours of trying to install the new Dutty v3 on mine. I loaded the Hard-SPL back on my phone(panicked a bit when I switched it back on and the colours were all funny) copied a 1.14 blacimg.nbh onto the sd card and 10 minutes later I was back in business. I don't know if this is the "correct" way but it's how I did it.
Thanks - will give that a try.
Hang on - which HardSPL did you use? The one in the sticky post in here does not work with SPL 1.54... (which is true - I just tried)
OliNex - worked for me.
Ah so I flash the old 1.14 stock ROM first to downgrade the SPL.. got it
Thanks!
I first did Hard-SPL. I suppose it doesn't really matter. I love my HD, it's tough as nails and handles just about all the abuse you can throw at it pretty well. Good luck.
I also had problems using USPL to flash any homebrew ROM. Read through the dummy manual and even that did not work. Tried it on a Vista PC and on a XP pc, but it did not work. Eventually I did manage to flash, not using Vista (32-bits) but using XP. Here is how I did it:
1) From command prompt on XP, run black_uspl.exe to put the HD in USPL mode. On the HD, after reboot on the lower part USB should be mentioned.
2) Then from command prompt on XP, run BlackStoneRUUWrapper.exe to start the flashing process.
Thanks I'll definitely try this. But over the weekend - I was up till after midnight fiddling on the pc.
This actually works. Its has for me and i thank you for trying it.
Only thing is, if you do it via SD card, no problems.
If you do it via active sync cable, it is a little tricky.
For me, i flashed HSPL first. As expected, i got the green screen and my data and phone settings wouldnt work. Not so bad i thought, as i will be putting the Stock 1.14 Rom back on and no problems. This is where the fun began. No active sync, and then i got it but wouldnt last long enough to even run Stock Rom flash.
Thats when i reverted back to how Crackwhore mentioned going back to stock SPL.
And that was, goto Active sync Connection settings on PC and untick " Allow USB Connections".
Then put unit into Bootloader as per instructions everywhere here. Bottom of phone will say "Serial" and will show Olinex 1.14 SPL (or however it shows it, sorry)
Plugged in the usb cable and the bottom of phone said "USB"
I then ran the Stock Rom Flashing file ( I used BlackstoneCustom RUU from Dutty's Site, as it has Stock Rom and Stock Radio)
The ROM Downgrade worked perfectly for me.
Im now in the process of re-upgrading my radio and Back to the Rom i was using prior to 1.56 (much more faster and more reliable for me at the moment) I will post up my results when it is done. Hopen this helps others.
NOTE----- I take no responsibility for anyone elses phone. This is you own decision as it was mine- The risk is completely in the beholder of the phone and PC. No Offence intended to anyone.
Frank from Oz Downunder
Well I've managed to do it - back to SPL 1.14.Olinex, running Miri's WM6.5 v8.1 ROM with Manila (the best of both worlds). If anyone's interested, I did it this way:
First flashed the older official HTC ROM (I had the official 1.56 ROM installed before). This put my SPL back down to the stock SPL 1.14. Next I put on the HardSPL, then stuck the new ROM on.
Simples
I can confirm that my downgrade of SPL 1.54 to HSPL olinex 1.14 and Lesser Rom worked ok. Now i have to test it.
If i find anything worth mentioning, i will post it up.
Frank
im having a huge issue here....
i updated my phone to "RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe", that went well.
since the phone is provided with orange UK 'tweaks' i had to use USPL to get around the locks.
ok - so, USPL booted, i then ran the above official update.
sucessful flash - or so i thought.
phone reboots, hard reset, and then allow phone to boot. setup wm6.1 as normal and get to the GPS stage - the hardware com port refuses to stay on the com port i select, and just goes back to 'unselected'.
thus, tomtom will not find any gps devices.
so i try to go back and find another rom that will work correctly - i now cant get ANYTHING to flash - i boot to SPL, attempt to flash rom, and phone/flash utility both get as far as 0%. after a short while, the utility comes back to say no comms with the phone. i cant boot to USPL, flash with another rom or anything.
how do i fix this?
Can you get your HD into bootloader mode ?
Each time a new ROM update
you must perform the procedure again with USPL unlock
Now that makes sense i didnt read the post properly lol
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!
Hi there
I just bought a new Topaz. I have HardSPL and then tried to apply a new ROM. Now it keeps on rebooting - it only gets to the screen where it says TOUCH DIAMOND 2 - and the the red numbers appear in the lower right corner - and then it reboots..
Is it bricked or is there anything I can do??
I tried to hard reset - but it still keeps rebooting
No not bricked.
Must be an incompatible ROM or you didn't HSPL to 2.51.
Just find another ROM, Stock or otherwise (since you are HSPL'd, but check your version first), go into Bootloader Mode and flash with RUU.exe.
Thank you Bruce!!
I'm still having problems though. I have tried to install a few different stock ROM - both 6.1 and 6.5. Everytime the same issue - I get stuck on loading the new ROM and it keeps rebooting.
I have tried to upgrade spl to 2.51 but still the same issue
What else can I do??
What does your SPL show in bootloader mode?
Make sure it has Olinex as a suffix.
Thanks again Bruce,
Yes it says Olinex.. When I first got the phone I tried to install a new ROM and I forgot to do SPL first - could it be that something serious went wrong in that attempt?
Anything else I can try?
niknik76 said:
Thanks again Bruce,
Yes it says Olinex.. When I first got the phone I tried to install a new ROM and I forgot to do SPL first - could it be that something serious went wrong in that attempt?
Anything else I can try?
Click to expand...
Click to collapse
Is it 1.83.Olinex or 2.51.Olinex?
Flashing a ROM w/o HSPL will most certainly mess up your device but it should be recoverable if you can find your stock ROM for your carrier and region.
You symptoms sound as if you are on 1.83 trying to flash 2.51 SPL ROMS.
Hi, im having the same issue as OP, i tried to flash the latest Energy rom (sept 8) onto my td2 and the bootscreen is showing 1.83.Olinex. What do i do to fix this?
You must have HSPL 2.51 for this ROM and for all newest roms.
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.