Database Info

HELP!

So i was stupid and thought it was done flashing, pushed power cam and com, (hard reset) while it was flashing it doesn't boot past the first screen, i can load bootloader but don't know how to install anything onto it at that stage, i cant use active sync cause well it doesn't run its os... does anyone know how to flash when at boot loader i'm a noob..
ahhhh!

Just run PDAViet Temp at bootloader.

jincongz said:
Just run PDAViet Temp at bootloader.
Click to expand...
Click to collapse
If that doesn't work at once, first uncheck "Allow USB connections" in the setting of ActiveSync before you connect your device.

Snce this has a valid name of "HELP" that is what i need
everyone talks about updating there radio?
what is the radio and do i need to update it
thanks in advance

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

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:
RUUNBH​KAIS 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....

Stuck at HardSpl 3.29 Tri-Color Screen

Okay I got up this morning and my phone was working fine. But then I restarted it and it just booted to the tri-color screen. So i took out the battery and I did a reset and it just keeps comming back.
So I thought that the rom might have went bad, dont know how but I though I would just refalsh it to see if it works. I flashed correctly and said it was complete but just reboot back to the tri-color screen. So the flash will complete fine but cannot get out of boot loader. I tryed flashing original and cooked rom, same result.
So I thought I would try and flash back to an older hard spl, I have hardspl 3.29 right now so I thought I would try hardspl 3.28 just to see if issue would be fixed. So I flash it and it completes, then reboots to tri-color again, but instead of saying 3.28 like it should it still says 3.29. Wierd??
So I through I would give mtty a try and see if I could get past the boot loader. I tryed the boot command which gave me a command error so I did some searching and tryed:
"set 16 0"
"task 8" <- causes phone to restart and goes back to tri-color.
Right now I am stuck at this tri-color screen and I think I am never going to get out. This came up randomly my phone has been working fine for a while now until today.
Can someone please help me on how to make it work????
Thank you to anyone who provides help.

Hi sngskunk, I have a similar problem. After a radio flashing, my phone stopped in tri-color screen, returned to normal after 24h, then returned to hang on tri-color screen. By coincidence it happened after using the camera. I suspect that might be a hardware problem, maybe a short circuit in the camera button, but I will make sure after opening the unit and clean the contacts of the button.

I am going to try and take the phone apart and look at the camera button to see if that is the problem, but is there a command in mtty that will boot the os, after the bootloader.
Because i have tryed the boot command and that doesn't work in Hardspl 3.29, I get a cammand error. I have tryed resetting it but if the camera button is stuck then it is going to go back to the original tri-color screen.

Okay so I toke my phone apart to check the camera button, the button looks fine didnt look dirty or full of dust and I check the micro switch and it seemed okay. While the phone was a part I turned it on to check to see if it would boot to the os, but it didnt it stopped at the spl, and I know that the camera button wasnt pushed.
Going to try and install a new radio just to see if that fixes it, if not, I am all out of ideas.

sngskunk said:
Okay so I toke my phone apart to check the camera button, the button looks fine didnt look dirty or full of dust and I check the micro switch and it seemed okay. While the phone was a part I turned it on to check to see if it would boot to the os, but it didnt it stopped at the spl, and I know that the camera button wasnt pushed.
Going to try and install a new radio just to see if that fixes it, if not, I am all out of ideas.
Click to expand...
Click to collapse
Try flashing a shipped ROM via MicroSD

I tryed installing a radio by itself, didnt fix it.
Installed original shipped rom from microsd, flash when perfect, said it was complete, reset it phone and it came back to the tri-color screen.
There is no "RUU**" i dont know what else is in that string but some people get in at the top of the screen when they are having my problem, but mine does not have it.

I would try going though the FrankenKaiser steps and see if that works? Just an idea

I looked up the post you are talking about and I am confused on it, because if I have the phone connected with the usb cable and use mtty. There is no command named dload.
Code:
cmd>dload
Command error !!!
Ofcouse now that I look at that post again that was in the spl, I cannot get to the radio boot loader the way he says, holding down the green phone and turning on the phone doesnt work just boots into the spl again.
Okay well i found a good post on how to do it but I get errors on the commands becuase in the post he isnt using hardspl 3.29 the cammand is the following:
rtask a <--- gets command error

austinsnyc said:
I would try going though the FrankenKaiser steps and see if that works? Just an idea
Click to expand...
Click to collapse
austinsnyc,
using these steps? -> http://forum.xda-developers.com/showthread.php?t=394584

I tryed those steps, but didnt work it wont go into radio boot loader mode.
I also tryed these steps: http://forum.xda-developers.com/showthread.php?t=393337
But I cannot execute the command: "rtask a", I get a command error.

sngskunk said:
I tryed those steps, but didnt work it wont go into radio boot loader mode.
I also tryed these steps: http://forum.xda-developers.com/showthread.php?t=393337
But I cannot execute the command: "rtask a", I get a command error.
Click to expand...
Click to collapse
I try these steps on saturday, but hardspl 3.* don't suport rtask command . If nothing more resolve, I am putting my chips on this tool (read post 6) ->http://forum.xda-developers.com/showthread.php?t=415839

I've run into the exact same problem.
I just turned off my phone, turned it back on and now it's just stuck.. can't load anything.
2nd time i've had a problem with this phone

Ok so i've also noticed something else with this problem.
Basically, what had happened, I did the same thing as the first post. All I did was reset my phone. I turned it back on, and i'm stuck at bootloader screen
When it is loading, it flashes the screen to a complete white screen that says "Loading. No Image File!"
Then it goes right back to the bootloader screen and that's that.
It seems as though hard resetting, mtty or flashing back to original rom does not work.
Does anyone know what the heck is going on?

@kjb, have you tried the suggestions by AllTheWay and myself in the other thread you posted in. It's very hard to keep up when issues are on going in 2 threads. Please stick to just one, I suggest the other one.
Link here: http://forum.xda-developers.com/showthread.php?t=418692
Thanks
Dave

DaveShaw said:
@kjb, have you tried the suggestions by AllTheWay and myself in the other thread you posted in. It's very hard to keep up when issues are on going in 2 threads. Please stick to just one, I suggest the other one.
Link here: http://forum.xda-developers.com/showthread.php?t=418692
Thanks
Dave
Click to expand...
Click to collapse
Hi Dave,
Yes I have tried flashing the original rom. But unfortunately, i'm still stuck at the bootloader screen and it did nothing.
I am extremely confused now

kjb86 said:
Hi Dave,
Yes I have tried flashing the original rom. But unfortunately, i'm still stuck at the bootloader screen and it did nothing.
I am extremely confused now
Click to expand...
Click to collapse
Tri the link in my sig, There are some suggestions in the Wiki.
Ta
Dave

DaveShaw said:
Tri the link in my sig, There are some suggestions in the Wiki.
Ta
Dave
Click to expand...
Click to collapse
hmmmm, ok for mtty it's not working. There is no USB present and I can't select it.
It won't allow me to do any of the settings just by selecting COM1 or COM2.

kjb86 said:
hmmmm, ok for mtty it's not working. There is no USB present and I can't select it.
It won't allow me to do any of the settings just by selecting COM1 or COM2.
Click to expand...
Click to collapse
Did you disable USB connections first?

AllTheWay said:
Did you disable USB connections first?
Click to expand...
Click to collapse
No. Nothing was disabled. Activesync was not present at all either and nothing was in the task manager.
Few things i've noticed:
a) when flashing to a new rom (or attempting too) there is no image listed in the previous ROM
b) my phone would be off, I'll plug it in to the USB and all of a sudden my phone will turn on right to bootloader.
Don't know if that makes a difference, but it's just some observations for you guys.

kjb86 said:
No. Nothing was disabled. Activesync was not present at all either and nothing was in the task manager.
Few things i've noticed:
a) when flashing to a new rom (or attempting too) there is no image listed in the previous ROM
b) my phone would be off, I'll plug it in to the USB and all of a sudden my phone will turn on right to bootloader.
Don't know if that makes a difference, but it's just some observations for you guys.
Click to expand...
Click to collapse
No you need to disabled USB connections in Activesync for MTTY to work!

Error 260 Update Error

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!

A little help please, guys

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.