I hope someone can help me, I have a Sprint Touch Pro2. Last night it randomly started rebooting itsself, i was not loading a new rom, i was not installed any software, i wasn't doing anything other that texting and IMing people. After i removed the SD Card, there were a few times i got it to load to the unlock screen, but once i got passed that it would say "starting device activation..." or something like that. Then i got it loaded but Touch Flo 3D would not automatically start. So i removed the battery and restarted it again and i went to bed and left it charging, and it kept restart itself again, when i woke up it the phone was dead, and will not turn on. The charging light is on but it will not turn on.
This happenned to me, i ended up having to exchange the phone.
have u tried a hard reset. U can do this by holding power button and call and end keys.
Phone must be off and it will completely erase your data
this sounds like what my phone is doing. is there a fix? i think im sol because i didnt buy it though sprint.
Not Hopeless
This happened to my Sprint TP2 I soft and hard-reset it but it still went back to the reboot loop.
I put it in the tri-boot screen and re-reflashed the stock ROM and all was well.
Same here
The same thing is happening for me right now. Soft-resets aren't helping. It's sporadic, however, sometimes saying it successfully activated and needs to reboot (then going into activation right away), sometimes saying it failed, and sometimes not coming up at all (but I'm pretty sure it's running in the background, even if I hit cancel, because the phone is very warm and the battery drains very quickly).
I took it to Sprint and they confirmed it was already activated. They tried manually activating it, succeeded, and it still kept doing it. However, both them and I were able to place a phone call, text, and visit a website... so basically it was working. But, like I said, this constant nagging of activation was running in the background sucking juice and killing performance. Their diagnosis was "it's acting weird". The main home screen clock has also been stuck at 0:00 ever since this started (though the lock screen clock and clocks in the World Clock screen are correct).
They said I could go to their service shop and do a diagnostic and backup/wipe/restore or they'd replace it under warranty if it still didn't work.
I figured I'd just try the hard reset myself tonight. Will post how that goes. I'm not sure what this "tri-boot" screen is, but I'll do some searching and check that out too.
Related
Ok, so far I've dumped the ROM and uploaded the kaiser-HardSPL and all was going lovely. However, after most of a day of pretty much inactivity I find the device suddenly goes very slowly. By which, I mean it can take several seconds to draw the screen.
Thinking this might be a rogue application using up all the processor cycles, I poked it up the bottom with the stick. (While doing this the first time, I held in power and camera just to see the boot loader text, but then I did it again with no buttons held.) It's a Vodafone device but it sat on the Vodafone splash screen for about 2-3 minutes then spent longer than that on the Windows Mobile screen before eventually dropping me into normality.
Except it's incredibly slow normality - I clicked on "start" and after a minute, it's not done anything yet.
Next step is a hard reset unless anyone has any better suggestion?
Help!
I assume you've pulled the battery?
Never assume anything... The full answer is, "No, but I have now"... I'm not sure that's going to do anything more than a soft (poke up the bottom) reset though. I'm now just waiting for the splash screen to subside while I'm typing this.
Having left it half an hour, while it went into standby and after noticing that the clock had stopped updating, I'm of the opinion that the already slow device has got slower...
Ok between 1 and 2 minutes to move from the splash screen to the "Windows Mobile" screen.
Now there's a turn up... After a further minute or so, I get a message, which has now cleared and gone back to the "Windows Mobile" screen before I had chance to copy it here. Basically it said that it had failed to boot either because I'd turned it off improperly or I'd installed something that it was opposed to. I should press send (I guess the green button) to reset to manufacturer's defaults.
Since that's my next stage anyway, I'll re-poke it with the pointy stick and press 'send' when it pops the message up. I'll put my trusty old Nokia N73 into flight mode and take a picture of the message so I can transcribe it here for everyone's amusement.
More news as it breaks.
I've now hit the 'send' button so it's doing a hard-reset. Meanwhile, here's the text it showed me:
Code:
The device is unable to boot be-
cause either you have turned off
the device incorrectly or tried to
install an application from untrusted
source. Press SEND to reset your
device or press any other button
to cancel. This operation will delete
all your personal data and restore
the device to its factory default
settings.
Nice. Ok, I'm at the 'tap the screen to set up your device' screen now.
Wonder what triggered all that nonsense then...
If you're like the rest of us and tooling around the all the fun programs in this forum, there's no telling.
I tell folks on computers, "Every piece of software you put on a machine is a liability to the operation of that machine." We can say that applies to this nifty little devices too.
I've had my phone experience the same symptoms you have posted here. Luckly for me a battery pull fixed mine. Sounds like the luck didn't spread much. Sorry.
Keep at it though. And don't fret the crashes. They do happen from time to time when you play hard.
So, a hard reset and a restore of a backup (Yes, I made a backup a few days ago even though I've been in the trade 20 years!) later, I'm back to normality. All I've done that's weird is install pof's loader and I can't see that's anything to do with it. What I was doing at the time of the slowdown was trying to connect to the wifi network at work. I thought the networking had just got itself tied in knots somehow but as the machine was even mega slow to boot, I can't really see that. At least I can still get back to square one at the moment.
I just need to create a .nbh out of the rom parts I dumped yesterday so that I can recover from anything more major...
Meanwhile, if you do a 'boot loader reset', would you expect it to say 'serial' if the USB isn't plugged in?
I'm starting to wonder if there is a major bug in the WiFi of the Tilt. There are some other threads on AT&T's site about this, and my work with WiFi on this unit has been dicey. Hmmmmm...
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
So last night, I was on my phone, running stock rom, not rooted, and I was setting a wallpaper through Zedge and it hung up and GoLauncherEx hung up a couple of times and the message with the Force Close - Wait - Report came up so I hit force close both times, then the phone restarted.
Now the problem is that nothing on the phone seems to be functioning. Can't swipe the unlock screen, power button doesn't bring up the lock screen or get rid of it. I unplug the phone and plug it back in, and it the screen comes on and sits there in it's non responsive state.
I still receive notifications, and everything but can't unlock the phone. I have noticed the phone doesn't hold a charge now, and when it's plugged in gets abnormally hot, but I don't know if that's what's causing these problems.
Any help is appreciated, as I do not want to buy another phone. lol.
I would do a warranty exchange with Motorola
That is very strange, there should be no reason that Zedge or a Wallpaper changing would make that happen...
Anyways, before you decide to try an exchange with Motorola, try flashing the fxz to revert yourself back to complete stock (this wipes ALL of your data!). Tutorial found here.
The only reason I suggested the warranty exchange is because of it getting abnormally hot. He has some weird issues going on that I don't believe the FXZ will fix, but its worth a try.
Apologies if this has been asked before but I have had a look through and although there are similar threads nothing is quite the same.
HTC Desire s
This is my sons phone and is contract Vodafone
He reported that the phone was freezing and turning itself off
I did a quick look up and found the factory reset tips so told him to do this.
Using the volume down and power button brought up the menu but not exactly as described as it had no erase data tag, it did however have a factory restore tag so he used this.
the phone shut down ok but then on restart just kept starting to the HTC quietly brilliant screen, made its jingle then displayed the vodafone screen, then after about five seconds turned itself off and then on then the same again. Not wishing to disturb the process and assuming it may do this a few times I told him just to leave it doing its thing. It continued to do this all night (12 hours).
In the end the battery was removed, reinserted then switched on. All looked good when the PAYG/contract screen came on and it proceeded through all the first time screens but then it froze, turned itself off and started doing the loop again with HTC quietly brilliant, then Vodafone then off.
this went on for ages, occasionally going as far as the phones home screen then repeating.
have now tried the factory reset again, taken out the SD card, removed the sim card and although it has slowed the process down it is still repeating and never going beyond the Vodafone symbol.
Has anyone got any ideas?
Many thank's Ian
Update to this, when the battery is removed and reinserted now without the SD and sim, the phone is turned on, it will go as far as the no sim inserted screen, if you then slide the bar down to unlock it goes to the White screen with HTC on then after a few minutes turns off, turns back on, does its jingle then Vodafone screen.
Please help as it appears my sons life has ended and the whole world has crashed.
Further update
Got message
the process com.htc.bg has stoped unexpectedly.
Does that mean no one can help?
Looks like time to send it back to the professionals.
I was using an app on Sunday, when the app froze completely and the screen of the s3 went black. The only thing I could see was the status bar up top, but even that was unresponsive. So I pulled the battery and turned it back on, and it was acting extremely slow so I got impatient and started trying to get into settings, when it went unresponsive again.
This time I held down the power button to see if I could get it to respond and the lock screen came up, without my wallpaper and instead of Verizon Wireless at the top, it said "No Service". After a couple of seconds my wallpaper showed up and then it said Verizon Wireless. After I get through the lock screen, I would go through the same whole routine - e.g. try and get into settings, freeze, hold power, have it come back up, etc. So I battery pulled again.
Finally, I got it to boot OK, by just letting it be for 10 minutes and completely ignoring it.
However, today my battery drain was pretty fast, it was on for 12 hours and was down to 40% after only 30 minutes of screen time. The culprit was "Android System" at 61%, i've never seen this that high before. Because of the high "Android System" power usage, I thought it might be good to power it down. Upon boot up, I assumed I'd be able to use it immediately, so I started going into Settings, and yet again it went unresponsive.
Are the two issues unrelated? What should I do?
As a warning, I'm extremely new to anything smarter than a Nokia brick, so be patient - Thanks!
As inconvenient as it is, I would recommend a full system wipe and go back to out of the box. That seems to fix everything and unfortunately it is rather difficult to diagnose issues on phones, especially unrooted.
In order to do a wipe you can do one of two things, goto settings then backup and reset, then hit factory data reset.
-OR-
Turn off the phone. When you start it again hold volume-up, power, and home to get into recovery. Then do the factory reset.
Ok, I thought that's what my option was. Thanks dwibbles.