Hi
I get this problem too often and I dont know why and what I did do when I dont get it. This is the case.
Now I have flashed the g3 wizard with one of the wm6-manilla roms. I have succeded with this once so I have followed the guides with the unlocking and downgrading etc. Now I have downloaded a new cook and try to install it by starting the rom update utility wizard.
Problem is that the installation ALWAYS fails now. It starts, the device disconnects from activesynk, waits another 30 seconds then fails to restart the device so I get the dreadful Error 260 update error and the phone is dead. I remove the battery, restart the device and try again and my hair turns grey.
I figure I need to downgrade first so I try all the differens RUU's that are pointed out in the guides (CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe, Xda_MiniS_LaunchROM_v154102.exe) but always the same problem.
What am I missing?
WinXP
AS4.5
IPL 2.26
SPL 2.26
Once downgraded and CID unlocked,a G3 device will remain CID unlocked forever,there's no need to downgrade everytime you flash a new rom.Just simply flash a new rom whenever you desire.So don't reflash Button's Rom 1.05 before every flash,its just required to flash once to get IPL/SPL 1.xx for CID unlocking,after which there's no need to reflash it again.
Error 260 is due to open port,so reboot your pc and Soft Reset the phone,hope it'll work fine.If you have reflashed Button's Rom 1.05 and downgraded,it wud be better if you perform the CID unlocking procedure again through lokiwiz02b or WST_4.2.2,after that upgrade to IPL/SPL 2.xx by either flashing T_mobile 2.26 or any official aku 2 rom,then upgrade to any wm6.1 rom.
You can even take out the battery and leave it for 30 minutes,after that put it back and try to flash.
Hmm.. now I have rebooted the pc and disconnected the battery for 30 mins. No luck. Still the same error.
There must be something I have missed. I have flashed with several roms before w/o any trouble.
I am connected to activesync as a guest on usb-cable.
Oh i didnt downgrade because it failed that too. So right now im on a wm6 manilla pretty good rom but the wifi's gone
Try flashing from bootloader:
* Hold down the camera button and then softrest without letting go of the camera button.
You should se a pretty tri color screen with IPL/SPL Information.
* Connect Wizard to PC using usb and wait for windows to detect the drivers if they are not already installed.
* Start your RUU and follow the steps.
Normally this error occurs when trying to flash under vista, if this is the case visit a friend who has XP and take some coffee
It gets worse im afraid.. and I am under XP.
Now the phone wont pass the t-mobile bootscreen. It gets stuck when showing the IPL/SPL information.
I fail to enter the bootloader. Hopefully im doing something wrong.
I have tried this:
1) Holding down cam-button and pressing soft-reset. The phone boots as normal but stucks at same place.
2) soft-reset and when sceen goes black, hold cambutton. Doing this makes the boot halt totaly and the screen remains black. Looks like it turns off cause the softreset wont work and I have to press the powerbutton to get life signs again.
How (exactly) do I get it into bootloader?
Evolution... i managed to do a hard-reset and got the phone to boot up again. So back to square one with not being able to use the ubs+ruu
hmm very strange.. in a desperate attemt to get into bootmode i held down the voice-button instead of the cam-button and then power-on. Not it worked! Mystic....
***
update! problem solved
In case anyone else reads this. I rebooted the pc for the 10th time, rebooted the phone at the same time and (a dramatic paus here) i pulled the usb-cable and placed it in another slot in the pc. And there it goes...
I dont work with computers... i work against them!
Related
ok so I previously had NBD 7.6 on my phone and it was running fine. then I decided it was time to upgrade to 8.3 I went through the flash process using the shell tool straight from 7.6 to 8.3. however the hard reset did not work right away and my phone did what I think was a soft reset. where it gets stuck in the splash screen with the IPL SPL GSM and OS numbers. my phone is a G4 and I have heard that you can't use the RUU to flash new roms you have to use the shelltool. however I am trying to flash back to the original love rom and am having no luck because my computer does not recognize my phone and nothing comes up in my computer however it is connected because it makes the noise when I plug it in. so how can I flash back to the t-mobile love rom without putting Cert_SPCS.cab and EnableRapi.cab files on my phone?
Wizardlove should work. Perhaps you could elaborate on why wizardlove doesnt work.
Another suggestion is that you could flash back to the rom that your device was shipped with.
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
squishymax said:
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
Click to expand...
Click to collapse
You havent mentioned bootloader mode so i suspect your flashing wizard love with shelltool? correct me if im wrong. Put the phone in bootloader mode and flash wizard love using the RUU.
The original rom that was supplied with your device can in most cases be downloaded from their website. For example my device is branded I-mate so I obtained the latest rom from I-mate's website.
yeah my device is CID Locked and whenever I try to flash using the RUU the program loads up and I click next for like 2 screens and then when the mini screen that says verifying the information on your pda phone pops up vista kills it and says it has stopped working. so I have never been able to use the RUU when flashing to a new rom. and I have the lastest RUU as well. and yes my phone is in bootloader screen when I try to flash it.
I figured it out. It was easy. Vista can lick my balls! I went to a comp with XP and everything went smooth. after 5 hours of sweating and searching. @$%#%!
Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBHKAIS 1*0
SPL-1.56.0000
CPLD-8
USB
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....
Alright so for some reason my phone would not flash roms fully they would always stop at like 89 percent or somthing...
So i thought maybe i should update my hard spl...
So i flash a new hard spl on my phone and now for some reason a htc pocket bios screen comes up and i cant even attempt to flash anything now...
Someone help?
Go get the official rom for your phone. Make sure your phone is in the bootloader screen (tri color) and it shows USB. Activesync will NOT connect (thats fine). Now run the RUU for the official rom (ignore where it says to make sure activesync is working. As long as the phone shows USB you are fine). Once you flash to the official rom, you should have a working device again.
At that point you need to verify if you have any type of hardspl installed (post what your phone says on the boot loader screen. You can get back to it by holding the camera button and doing a soft reset. Then just do a soft reset again to get the phone to reboot).
Good luck
I'm new in the world of flashing cooked ROMs
and i need to do it but i can't
Everytime i try to Flash HARDSPL 3.xx, it stops at the percentage screen and gives me an error on my pc.
And i tried to flash the ROM directly, and same problem.
I'm getting nervous of this stupid mobile, please i need Help.
I read all posts on how to install everything but nothing completed to the end.
bebo833 said:
I'm new in the world of flashing cooked ROMs
and i need to do it but i can't
Everytime i try to Flash HARDSPL 3.xx, it stops at the percentage screen and gives me an error on my pc.
And i tried to flash the ROM directly, and same problem.
I'm getting nervous of this stupid mobile, please i need Help.
I read all posts on how to install everything but nothing completed to the end.
Click to expand...
Click to collapse
you should go here ...
I had a problem when I first did mine. at the tri-color screen my phone never said USB on it and my computer showed an unknown usb device. Here's what worked for me but remember you only need to do this the first time, Once you have HardSPL flashed your phone will work like normal.
after your phone gives you a warning that a program is going to reboot it. You get a tri-color screen. As soon as you see this screen hold the camera and power button and press the reset button, don't disconnect the usb cable.
In other words the program that causes your phone to reboot doesn't allow the usb to work properly but a manual reboot into the SPL using the camera/power button does. I have not tried the "Forced USB" version of HardSPL because this problem goes away once you get HardSPL installed.
This would be better posted in the HardSPL thread.
Flash an official stock ROM, then follow ALL the instructions in the link deepthroat gave you to the T.
Ok. I've had problems up and down and tried and tried to do this and finally got it. So now I'm going to share it with all of you.
1. Download and Unzip the Files in the thread for the Ozone Verizon (HardSPL) posted by JockyW.
http://forum.xda-developers.com/showthread.php?t=551458
2. Connect your phone via ActiveSync, let it sync, and then start the auto.bat.
3. First, the JumpSPL will copy over. Press enter on the computer. Then the SSPL will copy over. Press Enter on the computer. Then it will prompt to start the JumpSPL. Press Enter. JumpSPL should pop up on your phone. Press the silver center button to start JumpSPL. The screen goes black. Then the DOS window will ask you if you have USB Connectivity. DO NOT PRESS ENTER YET!!!!
4. THIS IS VERY IMPORTANT!!! Wait for your phone to disconnect from ActiveSync. Once it does, unplug your phone from the USB. Go into ActiveSync's Connection Settings, and uncheck the box that says ALLOW USB CONNECTIONS. Reconnect your phone to the USB, and it should install the HTC USB Sync driver. NOW PRESS ENTER IN THE DOS WINDOW.
5. The RomUpdateUtility will start up, run it. And it should do the HardSPL on your phone. Your phone will restart when it's finished. If you want to check, before you do any of the above steps, copy the EnterBootloader.exe over to your phone. When you're done with the RomUpdateUtility and the phone has restarted, run the Bootloader and see what the tricolor screen says. It should be 0.39 Hard. Pull the battery, put it back in, restart the phone, and you should be good to go for flashing custom roms!
WOOHOO!
Thanks guys! I'll be donating soon. I'm about to flash the custom 3VO ROM right now! I'll let you know how it goes!
::EDIT:: The 3VO ROM is beautiful and runs like a charm! You guys put so much work into this.
Let it be known that this method for flashing the HardSPL can also be used for flashing the 3VO ROM.
NOTE: I WILL NOT TAKE RESPONSIBILITY FOR BRICKING YOUR PHONE.... seeing as I was scared I almost bricked mine once, and was VERY LUCKY that I did not. Please, follow all directions carefully. Phones are expensive.
ActiveSyn Doesn't disconnect
I got to the step where JumpSPL runs and my screen goes black. However, my phone never disconnects from ActiveSync. I tried unplugging it and disabling USB in activesync, but then my phone comes up as Not Recognized. If I try to run JumpSPL at this point I get, "Error (260): Connection." Any ideas?
How long are you waiting for ActiveSync to disconnect? It takes awhile. I know for me, it took about 5-10 minutes for it to disconnect.
Try waiting a little bit longer, and let us know what happens.
I waited long enough for activesync to stop. I unplugged my phone, disabled USB in activesync, and reconnected my phone. Every time I get a error saying "USB Device Not Recognized." If I try to run the update utility I get a connection error.
In all fairness I bricked my phone initially and had to recover it using a "stock" ROM someone posted for the CEDAR. My phone might just be hosed.
wm 6.5
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
I flashed the HardSPL on the Verizon 6.5 Update. So I guess the answer would be Yes.
I'm really lovin' this 3VO ROM. It's fast and the battery last a lot longer.
i tried your method and i'm still coming up with SPL-0.39.0000
i've tried other peoples guides as well and cant get it to hardspl, any ideas?
I followed all of these steps a few different times and my Bootloader still says .44. I tried varying the steps a little based on what users said on the thread about putting the HardSPL on the .39 and it still didn't help. I'm going to keep trying various configurations, but if anyone else is able to get their Official 6.5 ROM over to the 3VO, I'd love to hear how.
Thanks
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
recoshaa said:
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
Click to expand...
Click to collapse
You can find the hardspl definition here http://forum.xda-developers.com/wiki/index.php?title=Glossary
If you want to install a custom rom you will need to hardspl your device.
I hope that helps
I ran auto.bat, when the updater failed I disconnected USB from phone, reconnected, then ran updater manually and it all worked. Had to do this on both the HSPL and the ROM.
Also, make sure you don't uncompress both to same folder as it creates a .nbh file and if you have both on same folder you might be trying to install the ROM instead of the HSPL or vice-versa.
Another note. If you are HSPL already you can turn off device, turn it back on pressing DOWN VOLUME and POWER, leave both pressed until you get to rainbow screen, you can then run the updater and it won't bug you with battery being less than 1/2
I had problem that after screen goes blank, the phone will not connect. Some time "HTC USb Sync" will show, some time not. ROM Update will always complain that phone was not connected.
This is what I did to solve.
1. Power Off.
2. Hold vol dn and send with one hand. Then power with other hand.
3. Choose restore default configuration.
4. Let it boot
5. connect to ActiveSync.
6. Now run auto.bat
7. It runs fine and HArd SPL is loaded.
Enjoy.
schoenkn2 said:
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
Click to expand...
Click to collapse
Hi there, not sure if this belongs here. If you're planning on putting a custom ROM on the Verizon Ozone, do not use the HTC/Verizon wm6.5 update! "!! DO NOT !!" With the original stock wm6.1, you have a .39 Bootloader. After flashing the HTC/Verizon wm6.5 Stock Rom, you have a .44 Bootloader. And you can forget about putting a Custom/3rd Party ROMS. If somebody knows how to fix this, please tell me.
Thanks, and enjoy your HTC!
JD