Kaiser entering three-colour screen by itself - Tilt, TyTN II, MDA Vario III General

My Kaiser has entered the three-colour boot screen by itself twice. It happened the first time after I did a soft reset, and I didn't know what to do to solve it, but on attempting a ROM flash, it reset itself back to normal with all my information intact.
Now, it has gone into the bootloader again, without me having done anything at all - I just pulled it out of my pocket to use it, and there was the coloured screen again. This time I've made multiple attempts to clear it, using both the method above (no joy at all, just endless error messages) and MTTY, which won't connect properly at all.
I'm really anxious about this - I can't get the thing to come out of it however hard I try, and I really don't know what to do. I'm worried it's become a brick.
Lee

PrimitivePerson said:
My Kaiser has entered the three-colour boot screen by itself twice. It happened the first time after I did a soft reset, and I didn't know what to do to solve it, but on attempting a ROM flash, it reset itself back to normal with all my information intact.
Now, it has gone into the bootloader again, without me having done anything at all - I just pulled it out of my pocket to use it, and there was the coloured screen again. This time I've made multiple attempts to clear it, using both the method above (no joy at all, just endless error messages) and MTTY, which won't connect properly at all.
I'm really anxious about this - I can't get the thing to come out of it however hard I try, and I really don't know what to do. I'm worried it's become a brick.
Lee
Click to expand...
Click to collapse
See my guide here: http://forum.xda-developers.com/showthread.php?t=423486
Please post any more info in that thread.
ta
Dave

Please Follow Dave's Advice.
Thread Closed

Related

Stuck in bootloader

Hopefully, someone can help me fix my f*ckup...
I attempted to flash the qtek "test" rom to my I-mate K-jam branded wizard. The flash worked, and the customisation from the extnded rom completed.
then the fun began...
the device booted, and hung at the splash screen. I soft reset, and it hung at the same point. I then tried a hard reset, and it still hung...
At this point, I thought "oh well" and tried to flash back the old os.. which wouldn't work, as I couldn't get an activesync connection. so I put the device in bootloader, and flashed the rom. but.. it's now stuck in bootloader. no combination of soft or hard reset will allow it to boot, but I can flash roms.
anyone got any ideas?
thanks!
<edit>
Just a quick update.. flashing button's custom rom image got me out of bootloader, and booting as far as the splash screen again, but showin the old i-mate, not his pint..
I'll keep tinkering, and hoping that someone has a clue what i've screwed up.
</edit>
2 others with same problem
You're not alone...
http://forum.xda-developers.com/viewtopic.php?t=40871
Yeah, I saw
Sadly mine came from ebay, so returning it's going to be hard!
Hopefully, it's fixable.
It looks bad!! I'm afraid
I've given up and hopefully will get a replacement from T-mobile?? Somebody suggested I try running the battery down. I did this and now it won't start at all or even charge - so it's now well and truly dead!!!
I think whatever we have all down is terminal - as you say you can't even run activesync. Hope you didn't pay too much for your ebay wizard?!

Phone frozen on bootup screen

I have a Cingular 8125, and after installing Xplore 1.1 using ShellTool override, I did the hard reset on my phone, but it just stays on the bootup screen with all the device information (OS, GSM, SPL, IPL) at the top left. I left the phone on for over 20 minutes and nothing changed.
I've tried doing a few hard resets now (which may have messed it up even more) and don't really know what else to try.
enph said:
I have a Cingular 8125, and after installing Xplore 1.1 using ShellTool override, I did the hard reset on my phone, but it just stays on the bootup screen with all the device information (OS, GSM, SPL, IPL) at the top left. I left the phone on for over 20 minutes and nothing changed.
I've tried doing a few hard resets now (which may have messed it up even more) and don't really know what else to try.
Click to expand...
Click to collapse
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
mfrazzz said:
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I had someone help me try and fix my problem last night. After going to the bootloader screen and flashing it using a RUU, it was still frozen on the splash screen. I then tried to hard reset it again, only to get the "Format is failed" message that I forgot to mention earlier. He said this message indicates is a hardware issue and that I would have to send it in to get it fixed. Is there any possible way to fix this problem myself?
From what I've gathered so far, a 'format fail' problem cannot be fix yourself. I think you will need to send it back.

BRICK - QMobile, Orange, hard spl'd ???

....before anyone moderates my ass i wasnt sure whch forum was the appropriate one for a bricking!
****
My phone seems to have given up the ghost. A few days after having put on the excellent Q-Mobile system. My phone has refused to boot properly. Heres what happens:
In start up from Soft reset, or Power off, i get the tricolour screen saying:
KAIS130 MFG
SPL-1.0 OliPof
CPLD-8
a few2 lines benath that is written 'Serial'
it then flashed onto a white screen saying 'loading......no image file' - this all takes about a second.
And then it rests on the screen mentioned above.
I haven't dropped it or done anything other than flash- correctly.
AAAARGH! it does randomly decide to boot up properly after its been left of for a whil if that helps.
Also - active synch wont recognise it , in the tr-colour state.
HELP!!!
Phone now stable
wondering what the best thing to do is to get it back on track...
i had same issue read the link to my post
http://forum.xda-developers.com/showthread.php?t=352859
mtty worked for me then i reflashed its worth a try i guess
kishorvalji said:
i had same issue read the link to my post
http://forum.xda-developers.com/showthread.php?t=352859
mtty worked for me then i reflashed its worth a try i guess
Click to expand...
Click to collapse
mtty is the way to do...you are not bricked...just take a few breaths and search the forums. When it happened to me, I had to use the BOOT command with MTTY. After it boots back up, run HARDSPL once again otherwise anytime you soft reset it will return to the bootloader screen.
thanks, but what is MTTY - i checked the posts and couldn't find it anywhere

Having A Lot of Trouble Flashing

My phone won't take the flash of ANY ruus!
It gives me the same error with everyone of them. I've been trying for like two hours, it always says image is corrupted. so i redownload, re-extract. same problem, I've tried all the ones I can find and none!
it's hard to help if you dont give any info
phone-wing, p4350, etc
ipl/spl -number
did u hard spl your phone
did u follow instructions given here
http://forum.xda-developers.com/showthread.php?t=358225
you've been on the site for a while so i assumed you have.
list the steps you took when flashing
give out more info and i'm sure someone will help
Yeah I read all the posts but I was still a little fuzzy.
SPL4.10.0000
IPL4.10.0000
Tmobile Wing
First I Hard Reset my phone, put it into flight mode, and ran the USPL program
It gets all the way to the point where it's showing the progress bar, at 3% everytime, my phone resets and it says the image file is corrupted.
I re-downloaded all of them numerous times, used different programs to extract them, reset my computer etc. etc. etc. same thing every time
have you tried the link i gave you, i also have 2 wings and successfully did it with both using this method, the way to check your ipl/spl is press the soft reset with holding down the camera key until the colored screen shows up and you will see it then, to go back just press the soft reset button to boot back to normal, go see here
http://wiki.xda-developers.com/index.php?pagename=HTC_Herald
this is the best place to start, i've read through alot of these pages before flashing my first rom and i'm actually flashed 22 different roms over the two phones with no problems except the ones that need the keyboard fix. i'm still new to these phones as you can see in my sig but i'm trying to learn as much as I can since I wanna be able to cook my own rom, later.
What OS are u using on you're computer some people have been having problems with Vista there is also a thread on that
No I'm on XP, do I have to Hard-SPL? I think maybe that's the problem?
Voila! You're my savior! Thanks a lot! It's working fine now

Complete and utter noob in help.

Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
koglaa said:
Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
Click to expand...
Click to collapse
First of all, stop taking out the battery when the phone is on because that really screws up the files. You are doing more harm than good there.
Try a series of soft resets to try and fix it. If that doesn't work, try a series of hard resets to solve the problem.
If no luck there, go into bootloader ( tri color screen ), hold in power and camera button at same time while doing a soft reset. The try flashing a stock Orange rom ( found in the wiki ) Then re-flash with shifu rom.
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
koglaa said:
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
Click to expand...
Click to collapse
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
denco7 said:
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
Click to expand...
Click to collapse
The phone just soft reset's when I try to hard reset.
And yes, it does change from serial to usb when I plug it into my computer
Seem's like I was doing the hard reset wrong. Same thing is still happeneing, not getting past the part where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
EDIT:
After 20 or so hard resets, I've moved onto the boot-loader, then it took about 5 minute's to load to the main OS. I think everything is sorted out now. Thanks
omg, this is getting really annoying now. The phone keeps on crashing at random interval's and can only be recovered by hard resetting :\
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Flash OEM Rom before the new one and if you have 2GB or smaller SD Card flash using the SD Card method.
stylez said:
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Click to expand...
Click to collapse
It happen's when the phone freeze's and I soft reset it :\
koglaa said:
It happen's when the phone freeze's and I soft reset it :\
Click to expand...
Click to collapse
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
stylez said:
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
Click to expand...
Click to collapse
I'll do that next time it crashes .
Thanks for all your help guys

Categories

Resources