Related
I did upgrade in my O2 Neo, but after upgrade rom i´ts don´t turn on
What i cam do ?
O2 Neo is not a Magician, it is a Prophet (I think)
Anyway, we need more infor. What you do use to upgrade, where did you get it from, how do you perform your upgrade, any error message during upgrade, what's the sign now, all dark, hang on a particular screen, etc.
My Pocket is PM300 HTC
I did upgrade, and this show 100% and reset the pocket after upgrade, by this dont work, the screen splash blink only and turn off.
The led Red and Blue is blinks.
I used RomUpdateUtility HTC and the rom image i used Xda_Minis_Upgrade_v2.21.4.101
You used the ROM of a XDA-miniS (aka `Wizard`) to upgrade your `Prophet`. You are seriously screwed. You may have made yourself the most expensive paper weight you ever had.
Anyway, try see if you can boot into bootloader mode (3 colour screen). If you can do that, there are still hope.
My Pocket is PM300 HTC died
This show
IPL 2.21.0001
SPL 2.21.0001
and turn off i can´t update the rom.
What can i do ?
gmarcel said:
This show
IPL 2.21.0001
SPL 2.21.0001
and turn off i can´t update the rom.
What can i do ?
Click to expand...
Click to collapse
I need more details. That do you mean by `This show`? Where is these information shown? in the bootloader (3 colour screen) or the initial screen where your phone freeze. If you were able to get into the bootloader, you might able to get your Prophet ROM into it. Just start on bootloader mode, and plug in the USB. Activesync will not tell you anything, but you ought to able to still upgrade/refresh a Prophet ROM into it (eg running those ROM with EXE).
Can someone confirm if the ROM he used has IPL/SPL in or not?
Mod, can you move this to Prophet section.
More detail
These information shown in the bootloader (3 colour screen)
the initial screen show only O2.
i cant get bootloader, the Prophet only flashes.
The Activesync not tell anything.
I need move this for Prophet ?
gmarcel said:
These information shown in the bootloader (3 colour screen)
the initial screen show only O2.
i cant get bootloader, the Prophet only flashes.
The Activesync not tell anything.
I need move this for Prophet ?
Click to expand...
Click to collapse
Your statements are contradicting. You said you get these information from bootloader screen but you said you can get bootloader?
Anyway, if can get the bootloader screen. Just stay there. Connect it to your PC. And choose a *Prophet* ROM with EXE extension to run on your PC. It works most of the time. For step by step instruction, do a search here. I bet there are lots of similiar cases.
I can´t get bootloader
The screen with three coulours show about 3 seconds and this turn off.
I hope I'm wrong, but if your bootloader is gone, you device is gone. Hope others can help.
i think i have brick my dopod 818pro
have follow the step 1 and install without any error.
then installed the Cert_SPCS.cab and EnableRapi.cab.
then installed the Prophet_4.0.0.0.1_PV rom by running Upgrade_ROM.bat from the computer.
after that restat the device.
AND the phone boot after the HTC Innovation screen and stay at the loader screen.
NOw my screen only showing :
IPL 2.15.0001
spl 2.15.0001
gsm 02.69.21
os 4.0.0.0
and wouldn't boot in ???
anyone here please help
tq
finnally manage to boot in.
redo the step 1 in boot loader mode.
then installed the pdaviet 4.0.0.0.1 from pc
and it is done.
very nice screen
will try it out n c .
tq very much
Hi, how did you manage to solve the issue?
My situation is a little different.
-Load Step 1... ok Successful
-Load Upgrade_Rom.bat... completed
But when I reboot the PDA I just get this screen!!!
Nothing is responding.
PC cant detect the device.
Hard reset also get back to the same screen.
Please help
reboot your device into the bios screen (reset while holding camera button)
at that point i usually just put on the default WM5 comming from QTEK to reestablish operations.
i am using the prophet touch series from gullum and for that i do the following steps after having reestablished the WM5.
Put on PDAViet_TEMP
wait until phone restarts and shows 'Touch to get started'
Put on the Prohvet Touch (VIII or IX Beta)
Hard Reset (Com and Cam button, wait for the message asking to confirm afetr you release the reset button but hold on to com and cam buttons until message pops up) Confirm Hard Reset
So far i repeated this process about 6 times and it works every time
best of luck
need explanation
im planning to buy a dead prophet.....as the seller states...when he posted the pic, it still enters bootloader mode...but it shows
IPL: 1.00
SPL: 2.20.0001
Can this still be repaired? and is this possible? how can i repair it...it is being sold at a very cheap price
I've had similar issues and by just putting the original rom or the WM5 if you can enter bootloader mode thenit comes back to live. Once WM5 which is very stable is loaded, you can upgrade to the WM6 roms. Has always worked for me but it is a bit nerve racking to see the thing frozen. The key when upgrading is to use than WM5 rom and upgrade from there.
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....
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!
Hi,
I have a Qtec S200. G3
Now the problem is that I cannot flash it:
a) Using Softspl: the device screen sometimes turns bright white as it should, but when I start a RomUpdateUtility_NV_G3 it does not find my PDA
It tells to check my USB connections, which are ok.
b) Using Hardspl G3 found here, also at first produced the White screen, and when it came to the rom updating part, next, next, update-> the PDA screen turned black and eventually it could not connect to the PDA, displayed the same USB connection error.
c) Prophet Tools 2.8.3
Hardspl & Softspl are practically unusable, the same thing happens as above, softspl shows promise by entering into the "Bright white screen" state, but even then, when trying to "put" or "update" a rom to the pda in that bright white screen state, it still turns the screen black and does nothing, same connection error as before.
What could be the cause of this?
Any help would be appreciated
Details:
IPL 2.09
SPL 2.09.0000
GSM 02.07.20
OS 2.9.7.24
Help, anyone?
Help.. i have the same exact type of phone and the same error.. Can't get into SoftSPL and HardSPL doesnt work either. Really tired of WM5, nomatter how good it is
Today i tried to upgrade the IPL from 2.09 to 2.10 but still nothing. When i start the upgrade the phone turns off and wont start again until i pull the batter...
Any if all help would be welcome!
After a year i'm still stuck with this old ROM and the same problem as before.
Bump... Really could use some help on this
Same problem here
My S200 has the same issues.
But today when i tried to upgrade the IPL/SPL to 2.20 it worked and i was even able to hard spl .
I think the problem might be with the battery.Have you guys checked that out?
As for me,i am able to start flashing roms but the phone gets disconnected automatically in between.
I am going to try a whole night recharging and then flashing.
lets see if battery is the villain
my qtek s200 is mad
i tried to upgrade my rom from w to w6,and because i don't know how to do?my s200 has become unusable without charger,when hard reset it doesn't complete install process and it blocked,restarting it works unproperly,bud comands no sound no ...unpluging charger it turns off,battery is full "i'm sure ",but it indicate it empty 0% ???,
how can i syncronise it to pc and it is off
ipl 1.01
spl 2.20.0000
gsm 01.12.10
os 1.5.4.2
pleeeeeeeeeeeeeaaaaaaaaaaase heeeeeeeeeeeeeelp
Tomorrow i will try with my new battery..
Sofar, i know it boots into the 3 colour stripe menu when using RUU program and that's it, program crashes and phone stays the same..
Really hope battery is the solution..
BAttery change didnt do anything, still the same old ... cant upgrade.. anyone know if there is some upgrade block on some models?
BUmp.. the only phone i have been unable to flash is the S200.. ANY advice left in anybody?