Related
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Splooshie said:
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Click to expand...
Click to collapse
Some G4's can't be flashed with the ROM on the HTC site, but can be flashed with the Wizard Love ROM. I'd try that. It's saved me several times.
Or try a hard reset before flashing another rom. See if it fixes the problem
If your phone makes it to the boot screen it isn't bricked.
It isn't bricked. It shouldn't be. If he flashed the Core 2.0n it's impossible that a OS only ROM would brick it because it doesn't touch the bootloader or the extended rom. Plus, from what i understand the ShellTool flashes OS only and that means even if the ROM he was trying to flash contained an IPL/SPL , then only OS would be flashed.
The fact that it even gets to the bootloader screen is proof enough it isnt bricked.... reinstall the carrier update and try something else.
Oh Sorry, he tried to reinstall the carrier ROM .. disregard.
I tried the love rom, but it errors out with error 300, invalid argument ( I think it looks like italian) =/
I've rebooted my pc, did a couple hard resets on the phone and verified the phone is being detected. The USB sync driver is loading. Seems every flash utility cant see the phone even when in the boot loader.
BTW it fails at the point where it tries to verifiy the information on my phone. if that helps.
Is your PC XP or Vista? If its Vista, it can't talk to a phone in bootloader mode. If you are XP then you should be fine but then I'm not sure why you can't flash the Wizard Love rom...
I'm using xp.
When you put it into boot loader mode, is USB in the lower left corner?
Splooshie said:
I'm using xp.
Click to expand...
Click to collapse
Have you tryed a hard reset ?
yes twice the second time when it rebooted I forced it to boot the boot loader before it tried to boot the OS.
And you have tryed taking out your SD card, and flashing the Wizard Love rom directly from the RUU (not with ShellTool) ?
You have enough battery ?
I have been using the flash utility, I don't know how to use shell tool without the scripts, and I can't install any of the cabs since it wont boot into the OS. I just tried on another xp machine and both the cingular rom utility and the love rom failed to communicate with the phone.
any other ideas?
edit: oh and I should have near if not 100% battery ( been plugged into a pc since the problem started and it was 100% when I started this mess. =) SD card has always been removed.
FYI, even though it has been plugged into the computer, it may not have enough battery. From my experiences, it drains the battery even if it is plugged in. Luckily, I have a second wizard so when my first battery drained (and wouldnt recharge even when plugged into the wall) I just popped the second battery in and i could flash it again. See if you can find a charger or something for the battery, and then once it is charged, let me know and I will give you a ROM i have that saved my other wizard (which is a G4 and no it isnt wizard love)
-Nstefanelli-
it seems to be charging, the orange light is on and the phone is off.
ok in a few i'll PM u a link to the ROM.. i havent used it in a while so i might have to gather it up..
-Nstefanelli-
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Splooshie said:
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Click to expand...
Click to collapse
Are you sure you don't have a G3 ? Hmm, I think you have a G3 and that's why it doesn't work. Try and flash the Tmobile 2.26
If your ipl 2.25, spl 2.25, then you defenively have a G3 CID UNLOCKED
Go back to Button's 1.05 ROM, CID UNLOCK it and then flash the Tmobile 2.26 and then flash Core 2.0n
Don't use ShellTool !
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....
OK
I've always had troubles flashing radios for some reason, I've managed to just not do it but now with Duttys 6.1 out I really need some help
- I've flashed Duttys latest successfully
- I've flashed HardSPL
- But whenever I flash the radio (1.64.08.21) I get a connection error at 99%!!
Now I can still get into the phone using mtty and the boot command.
Am I doing something stupid -- Any help gratefully received!
Alex
ps - I have a UK o2 XDA Stellar
I'm a newbie been here with a AT&T Tilt less than a week and I promise I'm reading, but I'm having the exact same problem. Flashed Duttys dual V4 as my first try last Tuesday without a problem and of course be a crazy new guy I wanted his newest work. So I flashed Duttys 6.1 today and I guess I just can't figure out how to flash radios, because I've tried 2 now and both error out at 99% and I too have to use mtty to get back into the phone. I'll keep reading, but if someone could tell us new guys what the heck we are doing wrong that would be great.
PS I'm glad to be here and this looks like a lot on fun thanks for having me and look forward to helping out someday.
JMan
Hey Alex! I figured it out Brother! Do this and you should be able to upgrade your radio. I was using JumpSPL1.56-KAIS run from my device and I was running into the same problem everytime I tried to upgrade my radio. Would get to 99% and then would error out. So I followed these steps taken from a number of different post and put together until it worked!
1) Make sure you have JumpSPL1.56-KAIS somewhere on your device the file for me is in "my docs" on my Tilt.
2) Run kaiser-HardSPL from your PC with your device hooked up via usb with the green act sync icon. Once you get to the white screen of death on you device, stop unplug you device and soft boot it via your stylus and the reset button. Leave your pc alone right where it stopped in the kaiser-hardspl screen. "should be to the point where it says unplug and replug in your usb you should have the tri color screen press enter to proceed"
3) Now set your connection settings in active sync to not allow usb connections.
4) Now plug you device by in via usb and run Jumpspl1.56-kais on your device. When it has the tri color screen and says usb, unplug usb and plug back in.
5) Now back in the kaiser-hardspl window, continue on with the on screen directions. This should now install hardspl just like the rom or roms that you might have already installed and will say finished.
6) The device should reboot.
7) close the kaiser-hardspl window and let you device fully reboot.
8) Once it is fully rebooted follow these directions: Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up
9)Now run your radio update and it should go through without erroring out at 99%. It will stay at 99% for a bit then jump to 100% success!
My Tilt is working great now with sound and everything. Have not tested anything else yet, came right here and started to let you know what I did to get radio installed.
So now I'm running Duttys WM6.1 newest release with radio 1.64.06.
Call me crazy and sure I know I might have taken more steps than I needed to, but I got it working.
Hope this helps you.
Take care,
JMan
First, are you using a 6.0 rom or a 6.1 rom? If you are using a 6.0 rom you cannot flash any of the 6.1 radios and vice versa. Also, if you have hardspl installed, why would you need to use jumpspl. I have never used jumpspl and I promise I have flashed 50+ times counting, roms, radios and splash screens.
I believe that was my problem, I was never able to get Hard-spl installed and I was using jumpspl to install the 2 roms that I have installed since I got my tilt a week ago. The method I used above allowed me to get hard-spl installed and then I was able to install the radio rom. I am using Duttys WM6.1 rom.
JMan I want your babies!!!
Ok I had actually done everything upto the final step (holding the camera button after a soft reset) but that made it possible to flash the radio just as you described.
So many thanks for sharing your solution!!
Alex
jmandss said:
Hey Alex! I figured it out Brother! Do this and you should be able to upgrade your radio. I was using JumpSPL1.56-KAIS run from my device and I was running into the same problem everytime I tried to upgrade my radio. Would get to 99% and then would error out. So I followed these steps taken from a number of different post and put together until it worked!
1) Make sure you have JumpSPL1.56-KAIS somewhere on your device the file for me is in "my docs" on my Tilt.
2) Run kaiser-HardSPL from your PC with your device hooked up via usb with the green act sync icon. Once you get to the white screen of death on you device, stop unplug you device and soft boot it via your stylus and the reset button. Leave your pc alone right where it stopped in the kaiser-hardspl screen. "should be to the point where it says unplug and replug in your usb you should have the tri color screen press enter to proceed"
3) Now set your connection settings in active sync to not allow usb connections.
4) Now plug you device by in via usb and run Jumpspl1.56-kais on your device. When it has the tri color screen and says usb, unplug usb and plug back in.
5) Now back in the kaiser-hardspl window, continue on with the on screen directions. This should now install hardspl just like the rom or roms that you might have already installed and will say finished.
6) The device should reboot.
7) close the kaiser-hardspl window and let you device fully reboot.
8) Once it is fully rebooted follow these directions: Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up
9)Now run your radio update and it should go through without erroring out at 99%. It will stay at 99% for a bit then jump to 100% success!
My Tilt is working great now with sound and everything. Have not tested anything else yet, came right here and started to let you know what I did to get radio installed.
So now I'm running Duttys WM6.1 newest release with radio 1.64.06.
Call me crazy and sure I know I might have taken more steps than I needed to, but I got it working.
Hope this helps you.
Take care,
JMan
Click to expand...
Click to collapse
You are the STAR! Trillions of thanks. Solve my problem!!!
I love it when when the new guy can help out! Glad it worked guys, and thanks to all the old pros around here for allowing us to read so we can try and help ourselves out.
Take care,
JMan
I think I have fallen in love with this thread. This is truly nice to see guys. Keep up the great work.
i've the same problem, but when reboot Appear immediately hardspl, but i can't re-install nothing !
please help me
I don't want to miss mi tytn
pedro_se_rooot said:
i've the same problem, but when reboot Appear immediately hardspl, but i can't re-install nothing !
Click to expand...
Click to collapse
You need to use MTTY to get things going for you again, here is the thread to get mtty:
http://forum.xda-developers.com/showthread.php?t=371154&highlight=mtty
Search around and see if you can find the step by step to use it, might even be a how to text file in the zip file not sure. This should get you back on your way.
Can someone locate the step by step to use mtty for this man and put it in this post?
Have a good one,
JMan
Not a good day for the Wolfpack, Damn Tarheels!!
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!