I have read through endless posts and stickies.. I still can't figure out what the correct procedure is for updating my TYTN II from WM6.0 to WM6.1
I would greatly appreciate it, if someone would lay it out step my step
I tried to flash with the WM6.1 update, it said there was a vender error.
I tried flashing with HardSPL 3.28 and it stops at 0% and says there is there is a communication error, and to click next to perform the recovery. I perform the recovery, after removing the battery and putting it back in, the phone starts up normal.
I tried the white screen solution.. it reaches the three coloured display with USB and just sits there.. i eventually reboot the phone.. and it starts back up normally..
but none of the flashing procedures have worked yet..
I used the files found Here for the white screen problem.
I don't know what else to try..
Direct update - Invalid Vendor ID
HardSPL 3.28 - Communication Error
JumpSPL - Does nothing...
What am i missing?
Puff1911 said:
What am i missing?
Click to expand...
Click to collapse
Interpreation and sense of what you are reading.
http://hpcmonex.net/olipro/KaiserUnlocker.zip
That is the link to the Kaiser Unlocker by Olipro. It Hard-SPL's and SIM Unlocks. If you do not need the sim unlock simply flash to a different ROM after the first step.
Thanks socalkevin21 for providing a usable response
Not a problem, let me know if you have any issues.
The software says to unplug the USB connection as soon as the screen turns to the three coloured screen.
when i plug back in, the progress bar waits a couple seconds then jumps directly to 100%.. is that correct?
The phone reboots, and starts back up as normal.. but the same version ROM is still there..
Puff1911 said:
The software says to unplug the USB connection as soon as the screen turns to the three coloured screen.
when i plug back in, the progress bar waits a couple seconds then jumps directly to 100%.. is that correct?
The phone reboots, and starts back up as normal.. but the same version ROM is still there..
Click to expand...
Click to collapse
enter bootloader (press and hold the camera button all the way while pushing the stylus into the reset hole)
you should now be at a tri-color screen
what does this screen say?
KAIS130 MFG
SPL-1.0.OliPof
CPLD-8
when I click on Unlock Radio, it says "incompatible device"
Is that also normal?
Do i need to patch the radio as well?
wooooo!!! got it! i eventually got it to update the radio by clicking the button over and over..
I didn't get to unlock the phone (step 3).. but after i tried to update to windows mobile 6.1.. and it worked!
Thanks socalkevin21 and mbarvian!!
Well my device runs a lot faster.. but also sticks a helluva lot more!
Also my camera doesn't show anything, it takes pictures fine.. but there is no live display.. anyone having that problem?
And i also lost Voice Commander.. anyone have the install files for that?
**Fixed the camera problem. I had installed the HTC camera patch... Problem solved after removing it.**
Puff1911 said:
Well my device runs a lot faster.. but also sticks a helluva lot more!
Also my camera doesn't show anything, it takes pictures fine.. but there is no live display.. anyone having that problem?
And i also lost Voice Commander.. anyone have the install files for that?
**Fixed the camera problem. I had installed the HTC camera patch... Problem solved after removing it.**
Click to expand...
Click to collapse
Try a new HardSPL.
WM6.1 freezes sometimes with the OliPof 1.0 Hard SPL.
All the latest Hard SPL's are here: http://forum.xda-developers.com/showthread.php?t=396922
There are no other differences between 1 and 3.* other than the version number - they both work the same (oh and no MFG in 3.*, but you won't notice that)
Ta
Dave
Related
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....
i tried flashing a non-factory rom to my tilt. the steps i took are listed below.
tried the hardspl utility. got a white screen.
tried the hardspl utility for white screen devices. got the tri-color screen. yay.
ran the custom flasher that came with the custom rom i wanted to try.
got to 27% and stopped. it asked for a restart.
all subsequent flashes get to 0%.
went to the "how to revert" thread and grabbed the att factory rom.
ran the utility. utility returns "invalid vendor id" error.
my tilt shipped with 1.62.00, but the utility tries to install 1.57.502.2. does this matter?
how do i unbrick my phone?
--RC
rafadavidc said:
i tried flashing a non-factory rom to my tilt. the steps i took are listed below.
tried the hardspl utility. got a white screen.
tried the hardspl utility for white screen devices. got the tri-color screen. yay.
ran the custom flasher that came with the custom rom i wanted to try.
got to 27% and stopped. it asked for a restart.
all subsequent flashes get to 0%.
went to the "how to revert" thread and grabbed the att factory rom.
ran the utility. utility returns "invalid vendor id" error.
my tilt shipped with 1.62.00, but the utility tries to install 1.57.502.2. does this matter?
how do i unbrick my phone?
--RC
Click to expand...
Click to collapse
is your phone stuck at tricolor screen? If so tell me what it says.
{red band upper right corner}
RUUNBH
{red band lower left corner}
KAIS1*0
SPL-1.93.0000
CPLD-8
{green band}
{blue band}
{white band top center}
USB
--RC
rafadavidc said:
{red band upper right corner}
RUUNBH
{red band lower left corner}
KAIS1*0
SPL-1.93.0000
CPLD-8
{green band}
{blue band}
{white band top center}
USB
--RC
Click to expand...
Click to collapse
Looks like hardspl was never installed. Is your device stuck on that screen?
redbandana said:
Looks like hardspl was never installed. Is your device stuck on that screen?
Click to expand...
Click to collapse
I'd say Hardspl wasnt installed properly. Did you have enough battery life when you started the install of the rom? After a bad install of hardspl, I would ahve tried to reinstall it from the beginning again just to make sure you didnt have any problems. For now, try to pull up hardspl by holding in the power button/camera button (pressed really hard), and pressing the soft reset button in. If you do it right, the tri-color screen should come up. Then try reflashing hardspl if you can, or trying the rom again.
If that doesnt work, if you have At&t you can always connect it to a car battery and let it fry. Just don't cause any damage to the phone physically or with water. Otherwise, it doesnt matter.. you can warranty exchange it.
i followed the instructions for white-screeners.
copy 1.56, see if it white-screens. if it does, copy 1.93 and try again.
got the color bands? good. make the connection and flash away.
right?
--RC
rafadavidc said:
i followed the instructions for white-screeners.
copy 1.56, see if it white-screens. if it does, copy 1.93 and try again.
got the color bands? good. make the connection and flash away.
right?
--RC
Click to expand...
Click to collapse
you still need to install hardspl.
nimda0 said:
I'd say Hardspl wasnt installed properly. Did you have enough battery life when you started the install of the rom?
Click to expand...
Click to collapse
yes.
After a bad install of hardspl, I would ahve tried to reinstall it from the beginning again just to make sure you didnt have any problems. For now, try to pull up hardspl by holding in the power button/camera button (pressed really hard), and pressing the soft reset button in. If you do it right, the tri-color screen should come up.
Click to expand...
Click to collapse
doing this does exactly the same thing as simply applying power.
Then try reflashing hardspl if you can, or trying the rom again.
Click to expand...
Click to collapse
ok, this is probably where i'm not clear. i was under the impression that installing hardspl is as simple as getting to the tri-color screen without white-screening with one of the jumpspl files.
If that doesnt work, if you have At&t you can always connect it to a car battery and let it fry. Just don't cause any damage to the phone physically or with water. Otherwise, it doesnt matter.. you can warranty exchange it.
Click to expand...
Click to collapse
connect what to the car battery? the +/- contacts as illustrated on the phone battery?
--RC
redbandana said:
you still need to install hardspl.
Click to expand...
Click to collapse
as i stated, the thread isn't very clear on this. i tried running the hardspl utility, but it whitescreened. i ran the alternate one for white-screeners and it got me to the tri-color screen. what else is there?
i tried resetting the phone and rerunning the hardspl utility after successfully getting the tri-color screen, but it just whitescreened again.
--RC
rafadavidc said:
yes.
doing this does exactly the same thing as simply applying power.
ok, this is probably where i'm not clear. i was under the impression that installing hardspl is as simple as getting to the tri-color screen without white-screening with one of the jumpspl files.
connect what to the car battery? the +/- contacts as illustrated on the phone battery?
--RC
Click to expand...
Click to collapse
dude your phone isn't broken. you need to stop focusing on what is stated there and listen to what I am saying. You need to install hardspl. 1.93 is only if you were receiving a white screen. Install hardspl let me know what happens. I'll be up for another 1/2 hour customizing a rom.
The new SPL should work. I also got white screen with HardSPL and SPL. But the new one worked on my 2 new dievices.
xmoo said:
The new SPL should work. I also got white screen with HardSPL and SPL. But the new one worked on my 2 new dievices.
Click to expand...
Click to collapse
he can't flash with 1.93 it stalls at 0%. I was under the impression 1.93 is one of the original ATT spl's.
i'm sorry, i didn't mean i'm ready to run out and fry my phone right now, i'd rather fix it.
i guess i'm unclear on what it means to install hardspl. running the .exe from here just does nothing. is there something i'm missing?
--RC
rafadavidc said:
i'm sorry, i didn't mean i'm ready to run out and fry my phone right now, i'd rather fix it.
i guess i'm unclear on what it means to install hardspl. running the .exe from here just does nothing. is there something i'm missing?
--RC
Click to expand...
Click to collapse
Probably not Pof writes clear instructions. Follow his instructions to a T. Since you are receiving white screen follow jockey's instructions here:
http://forum.xda-developers.com/showthread.php?t=354061
ah, ok, see, this is where i have not been clear.
my phone boots to the tri-color screen and does absolutely nothing else. i'm stuck here, unless there's some magical button combination that will get me back into windows. i can't get it to boot to the operating environment.
--RC
Umm, can't you just soft-reset to get back to windows from where you are? No magic button combination needed.
soft-reset gets me back to the tri-color screen.
--RC
rafadavidc said:
soft-reset gets me back to the tri-color screen.
--RC
Click to expand...
Click to collapse
is your camera button stuck down somehow?
no, it was responding nicely earlier today, and i can also feel the distinctive two-click action now if i play with it.
--RC
rafadavidc said:
soft-reset gets me back to the tri-color screen.
--RC
Click to expand...
Click to collapse
ok this is what i originally asked "are you stuck at tri color screen?"
follow these instructions and stop ****ing yourself over by reading everyone's post at once: (who else helps n00bs at 5am)
First download attached file: Next follow these steps
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
Okay. I tried to install one of Dutty's ROM's that can be found here: http://forum.xda-developers.com/showthread.php?t=398271.
I read through all the stickys and FAQ's first. I read Dutty's wiki, the Kaiser wiki, and the flashing new ROM wiki. I followed all of the directions and followed Dutty's instructions to the T.
After installing the HardSPL found here(http://forum.xda-developers.com/showthread.php?t=334679), I backed up all my personal info/data.
Then used the Custom RUU Dutty supplied and proceed through the ROM flashing process. Everything went fine and I got no error messages. But when my phone booted up I got a black screen. I waited but my phone stayed on the black screen. So I pressed the standby button on and off a few times and eventually I wound up with a black screen that had about a million multi-colored speckled dots all over it. And I have been stuck on this screen since. I've tried soft-reseting and hard resetting but nothing is working.
I am Using an ATT Tilt BTW.
Please Help me. My phone is my life so right now I'm feeling like Dionne Farris.....Hopeless....
ahh that sounds like a nightmare... wish i could help
klrob33 said:
Okay. I tried to install one of Dutty's ROM's that can be found here: http://forum.xda-developers.com/showthread.php?t=398271.
I read through all the stickys and FAQ's first. I read Dutty's wiki, the Kaiser wiki, and the flashing new ROM wiki. I followed all of the directions and followed Dutty's instructions to the T.
After installing the HardSPL found here(http://forum.xda-developers.com/showthread.php?t=334679), I backed up all my personal info/data.
Then used the Custom RUU Dutty supplied and proceed through the ROM flashing process. Everything went fine and I got no error messages. But when my phone booted up I got a black screen. I waited but my phone stayed on the black screen. So I pressed the standby button on and off a few times and eventually I wound up with a black screen that had about a million multi-colored speckled dots all over it. And I have been stuck on this screen since. I've tried soft-reseting and hard resetting but nothing is working.
I am Using an ATT Tilt BTW.
Please Help me. My phone is my life so right now I'm feeling like Dionne Farris.....Hopeless....
Click to expand...
Click to collapse
can you get into bootloader mode?
hold down power and camera button while inserting stylus it should introduce you to the tri color screen. Please tell us what it states. You may have just experienced a bad flash or you have the radio from hell installed on your device
redbandana said:
can you get into bootloader mode?
hold down power and camera button while inserting stylus it should introduce you to the tri color screen. Please tell us what it states. You may have just experienced a bad flash or you have the radio from hell installed on your device
Click to expand...
Click to collapse
Yes I can get to Bootloader mode.
In the red bar it says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
And Serial at the bottom in the white bar where USB normaly would be.
klrob33 said:
Yes I can get to Bootloader mode.
In the red bar it says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
And Serial at the bottom in the white bar where USB normaly would be.
Click to expand...
Click to collapse
ok soft reset your phone and when it starts up does something like this appear in red text?
r 1.65.20.29
g 25.88.40.04w
d 3.29.xx.xx
please tell me what it says after R
R- 1.58.25.17
klrob33 said:
R- 1.58.25.17
Click to expand...
Click to collapse
well it appears to be a bad flash. unplug your device from the usb cable, restart your computer, and flash again.
Hopefully after your computer restarts it will recognize the device as being connected. If it doesn't just double click on your windows mobile device center icon and it should connect. After connecting just reflash the rom
edit
I had the same problem, what i did was read all through the thread of the ROM or while inside the thread i use the search function and type in the keywords like "blank screen" it happened to me exactly, but i didnt bother to post since i found the answer, 1 user said flash it to WM 6.1 i did exactly that and it helped! some said not necessary, but i didnt see that instruction so i flashed the 6.1 blindly and fortunately it worked...
here is the thread
http://forum.xda-developers.com/showthread.php?t=375583&page=30
on the search function type black screen and you should get and idea what you need to do...
redbandana said:
well it appears to be a bad flash. unplug your device from the usb cable, restart your computer, and flash again.
Hopefully after your computer restarts it will recognize the device as being connected. If it doesn't just double click on your windows mobile device center icon and it should connect. After connecting just reflash the rom
edit
Click to expand...
Click to collapse
I tried that and It different work. I'm trying a whole new ROM now and I hope it works.
Problem solved.
Thanks to everybody for their help.
I just used a different ROM and everything worked perfectly. I guess that ROM just didn't want to work with my phone. But it's okay. The ROM I'm using now is perfect.
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!
I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?
bsgbelg said:
I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?
Click to expand...
Click to collapse
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!
Not possible to flash anything
what I've tried so far:
- activate active sync to install hardSPL. Not working
- install HardSPL through microSD. Not working
- install ROM through SD. Not working
I tried a non HCSD for a change, and then I see the loading scree flashing up, but quickly says No rom found and returns to the bootloader screen.
The only thing that works is load the bootloader (red green blue white) into a screen that says:
KAIS130
SPL-3.29.0000
CPLD-8
Serial
When connected to USB, it says USB, but no disk is showing in Explorer or any connection is made to AS
The only thing I've done in the past is flash the 6.1 rom through the system provided by HTC with a file called RUU_Kaiser_HTC_NLD_3.29.404.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe
Please help, I really like this phone and hate to loose it
put it into bootloader, connect it to the computer and then flash one of the htc roms. make sure its an htc rom, you cant flash a custom rom cause you dont have hardspl
I have not been able to find the original rom, only the exe from htc which says Connect with active sync. Do I have to set it in bootloader and then execute the program?
Solved
Just want to let you know I sorted it out!
Flashing the original rom does not need active sync, the bootloader USB connection is sufficient.
After this, the phone restarted in 'Erasing memory' mode, but was able to finish it and reinstall the whole rom.
I believe I got the taste of it and will start testing some other roms...
msd24200 said:
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!
Click to expand...
Click to collapse
Thanks, worked fine
majedaly said:
Thanks, worked fine
Click to expand...
Click to collapse
good to know