hi, i have a problem with my phone, it keeps going to a bootloader screen (?) with three colours and serial at the bottom (usb when i attached it to a pc). info shown is
kais130
spl - 1.56.0000
cpld-8
ive done a bit of a serach before, but basically this problem seems to happen evreytime the screen is off on the phone, or after a soft reset. its happpened half a dozen times in the last couple of hours and its very annoying. it happpened a few times a couple of weeks ago.. if i leave the phone for a bit without he battery in it seems to boot after a few tries (this could be after a few minutes or a few hours of leaving the battery out), but will lock up after a little while and ill have to do the same again. ive done a bit of a search for this, and its brought up a lot, but the thing is ive never flashed my rom, and all the posts seem to be relating to this are from a bad rom flash.
what can i do to solve this?
anyone help? it appears to be doing it more frequently now.
maybe try flashing a new rom?
bapssystupr3m3 said:
maybe try flashing a new rom?
Click to expand...
Click to collapse
it looks like he doesn't even have hardspl so i definitely would not recommend flashing a rom ... especially not a cooked rom. Now if you meant that he should reflash oem original rom than yes that might be a route to go.
Related
I am hoping for some help here, I have a Cingular 8125 its unlocked and all - for about a year I have been like most of you flashing different ROM's without any problems until now. My device will continually reset, it does not seem to matter what ROM I am running including the stock Cingular 2.25 ROM. It happens more often when I its not pluged in, and when I am using the web. It also sometimes cannot come out of the reset - so it will show the first boot screen then the second windows screen then reset again. It will do this until the battery is dead. When I plug it into the wall charger it will fully boot.
I am really stuck here any suggestions. I was thinking it might be a battery problem so I have orderd a new one.
I just need this thing to last for a few more months.
Do not give up !!!
New battery will not help here. I had the exact same problem and posted on this forum many times. Did not help. Changed the battery to a new one. Did not help. Flased the ROM many many times. Did not help.
And then right when I was ready to dump the phone in the dustbin, I downloaded and tried faria-htc-wizard-aku3.3-page-pool-8mb. It became much much better and it would reboot only on bad signals. Then I tried different radio roms, but the problem remained inconsistent.
Finally got hold of T-Mobile-UK_2.19.11_Radinly.zip and that was it. The combination of this radio and a clean faria-htc-wizard-aku3.3-page-pool-8mb (no other software) did the trick for me. I have a useless extra battery now, but the phone is rock solid.
Might not help you, but just wanted to tell you not to give up. There has to be some combination there that works.
Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow
and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.
grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).
Actually, ill just message you tomorrow or something.
Ive been really busy this week.
well did you get it fixed? what did you do?
Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.
I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it
You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.
GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?
Yes,
Note: I have had HardSPL, Olipro, etc for ages, and have been flashing roms in the 81, 85 and now 89 series for years.
An odd issue: I had the RyanCPPR v4 Rom in my Tilt, and the multi-color bootloader screen popped up and froze in my Kaiser, Soft, Hard and Battery Resets ensued, but nothing worked......after multiple tries, it reloaded....
I figured a corrupted Rom and tried the new Friday13thV7Diamond....voila...same problem......try, try, try again, and finally it loads....
But, I don't know what is going on. I would guess a radio issue as it stayed from Rom to Rom, but, this not being my area of expertise, wanted to get some thoughts from the big boys.
Anyone?
Thanks, G
Some more info -
Come on people, throw me a friggin' bone here...I know there are a dozen reasons this could be happening, so I'm not abut to run MTTY and start throwing in commands , no matter how much searching I do without some guidance.
On the bootloader, we have:
KAIS1*0 MFG
SPL-1.0OliPof
CPLD-8
MultiColors and at the Bottom
Serial
PPS: Problem began when Opera 9. whatever froze the Device (IN THE LAST ROM) and I softreset-ed. But this could be coincidence
Thanks again,
G
PS: Mystery Continues: Removed Sim - Booted. Let's see how long this lasts.....yup, Looks like sim is affecting it, though it has booted with the sim before.
Thoughts?
Hey everyone, I had a recent issue (not sure if it's still there) and was wondering if anyone could shed some light on what's going on. Anyway here's what happened:
I have had my Diamond for almost 2 months, I flashed a new ROM cause the one I was using (Franlov V3) was running a bit slow, I used DIBB v1.33, flashed, hard-reset and it was working ok but then it froze (or was really sluggish) so I reseted, and the phone took the reset as a hardreset, weird stuff, when it booted it was incredibly sluggish, so I turned it off, when I turned it on, bam, another hardreset. And well it pretty much entered a hardreset cycle.
I thought it was a problem with DIBB's ROM so I changed to another ROM and whenever I reseted ,the phone hardreseted. And this has been going on with multiple ROMs.
I searched and found a possible solution: leave the phone overnight without battery then reflash HardSPL, Radio and ROM, I did that yesterday...and had the same issue, till I flashed Dutty's 3.6, the only problem now is that drop-down lists, don't drop down. Any help (so it doesn't happen again) would be really appreciated.
I have the same problem
¿Did you solve it?
aemilius said:
¿Did you solve it?
Click to expand...
Click to collapse
...I hope, he's found the solution --> http://forum.xda-developers.com/showthread.php?t=490182&highlight=strange+problem+solved&page=3
post#22
CU
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
welbis said:
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
Click to expand...
Click to collapse
LOL,
no idea why.
Installed any tweaking software??
Sadly no - and I've tried it with 2 different roms too
welbis said:
Sadly no - and I've tried it with 2 different roms too
Click to expand...
Click to collapse
Heh, don't know.
Maybe some other rom's installation messed up something....
hmm... I faced the same problem...
So.. I did have to send it for repair :S ....
maybe i have the same problem... many roms tried, many soft and hard-reset, but the lifetime cycle of the phone before to re-flash the device is at maximum 1-2 days... now i'm trying the tips about quickgps (maybe could be correlated) on the thread in this forum... but the most probably truth i think that could be an internal memory rom damage... if anyone find a soluzion about this problem via software i'm here...
I seem to be having the same problem.
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
ristiisa said:
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
Click to expand...
Click to collapse
i had approximatively also the same problem... i'm trying to understand what is the reason of this instable situation... gps location? memory? graphic instance that use HTC sense? is heavy to understand... if anyone could also find the right solution...
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
lebkom said:
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
Click to expand...
Click to collapse
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
ristiisa said:
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
Click to expand...
Click to collapse
ye mine did it again aswell this morning
i just tried hard reseting then install a stock rom then hardreset again and install a custom rom, will let you know if it works
Do you guys often use Opera Mobile?
Ahah!
Very encouraging to see other people had the same difficulties... and I suppose that it's just a question of making sure a fresh ROM flash works properly.
Sadly mine has reached the stage where it's no longer working for 'a day' before crashing... it's just pretty much dead.
Now I can bring up the tricolour screen if I'm plugged in, the ROM then begins to flash off the memory card, but crashes half way through every time.
I have tried this with 2 batteries, one of which (which I have used once and was working fine but only lasted 2 days before breaking) now does nothing whatsoever. The other lets me get half way through the flash every time.
- I can't send it back on the warranty until I reflash it myself (and I don't have a receipt anyway) so I'm going to go find a high street mobile fixing place and see if they can help.
hardresetting then flashing a stock rom (R3A generic) then hardresetting again then installing custom rom and hardresetting, definately fixed my phone, has been working for more than 2 days now it usually stops in less than 1 day.
FYI - high street phone guys managed to reflash the device for £15....it lasted 4 days but has just died again.