I've seen a few similar issues on the web with various devices... I believe mine to be a bit different though.
Before today my Blackjack 2 (Windows Mobile 6.1) worked perfectly fine, it fell today and the battery went flying out of the phone. I put it back together and it was working fine. a few hours later i realized the phone shut off on its own. Well, it does that sometimes for me since it is over 2 years old and is quite beat up, so I took it as normal behavior, i started it up, and…. it hangs on the windows mobile green splash screen.
Whenever I shut it down, the loading circle that normally pops up, shows on the screen as its shutting down. I've actually gotten it to show the status bar (signal strength, battery, etcetera, however the rest of the screen remained at the splash screen.
Bootup process: it shows the Samsung splash screen, then the AT&T animation, and then the windows mobile splash screen where it finally hangs. When I plug it into my computer using the data cable, it dings on connection, and my computer starts to connect, but then errors out.
I'd like to try to avoid a hard reset or re installation if possible… just added a bunch of contacts that I haven't backed up, and I don't know their numbers off hand, so I'd have to wait for them to call/text me or until i see them again.
Also, if I have to perform a hard reset, I'm unsure if the phone will actually work after-wards since this did appear to begin after it hit the ground.
Since installing WM 6.1 I have not installed any software/programs/apps on the device, just some new contacts. It's not the sim card, my friend has the same phone so I tried it out on his and it worked fine.
Anyone able to advise on this?
Sorry for the double post, decided to format anyways. I have a trip tomorrow and absolutely needed a functional phone. It is now functioning perfectly fine, boot time is a bit longer than usual but it does boot.
Any idea what could have caused this and how to avoid the issue in the future?
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...
I'm not sure how many people, if any, have experience with this phone, but I'm taking a shot in the dark because I am completely out of options here. The phone is similar to the Cect M88, and the other Cect iPhone-clones available, although I'm not sure how similar the button layout is.
I installed PCM Keyboard last night, and all was working fine until this afternoon, when all of a sudden, my phone wouldn't wake up. I ended up having to pull the battery in order to get it to restart, but then it wouldn't boot past the Windows Mobile screen (the first one - didn't even make it to the second screen).
After several attempts to hard reset (top volume button + camera button + power button), I was able to get it reset, but even though active sync was running, folders weren't showing up properly on the phone itself. I did a soft reset, and folders then showed up, but this time active sync wouldn't load on the phone. Several more soft resets did nothing, but I kept trying, and finally... the phone froze up again to the point where it hung on the Windows Mobile screen again. Now, despite all attempts, I can't even get it to hard reset. When I push all buttons from an off state, the screen will turn blue (which seems to indicate some kind of resetting is going on since it normally goes straight to the WM screen) and then a few seconds later, the Windows Mobile screen will come up and hang. I've tried every combination of buttons possible, and I've tried hard resetting probably a good 20-30 times since this happened. I've removed the SIM card, removed the SD card... I've basically tried hard resetting seemingly every way possible, and yet it still will not reset and load up WM 6.0 pro like it should.
Any ideas on how I can get this thing to at least move past the WM screen? If I'm totally unable to hard reset, what would be the next best course of action? Since this is an off-brand phone with no support or any kind of warranty, are there repair places out there that can restore the OS? Is that something I can do myself? (Phone didn't come with any software or anything.) I'm at a loss here... I really don't want to end up with a $200 blue flashlight/paperweight. I know I took my chances when I bought it, but well... this stinks.
worked
hey man i know its old and hopefully you still have your phone.. ok what you need to do is let the phone die completely so you may have to keep the blue screen on and keep turning it on till your phone does this like you i have hard reseted serveral time to no avail but when the phone died i took out the battery plugged it in to the wall charger placed the battery in the phone let the red led light by the camera light up then i turned it on and before the screen could show the splash i did the hard reset phone is aye ok !! hope this helps man.. your post helped me..
eric
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.
Hello all,
I'm hoping this can be fixed, for my fiancée's sake, as she has alot of pictures and videos of our little boys when they were born and can't be replace on her Treo 750v, unlocked via code from Voda, it's still running WM5.
It started when she was sending a text, press sent, and randomly, parts of the list of messages starting turning into blanks, around that time it popped up saying low on memory, she deleted a installer cab for facebook, and the little busy circle appeared but did nothing and crashed the phone, so she took the battery out, put it back in and now all it does is boot with the Palm logo, goes onto the Windows Mobile splash screen then blank, pressing red brings the keyboard light on and makes the key sound, but doesn't do anything, all with the blank screen. The orange light flashs for loss of signal constantly, but the red charge light doesn't come on at all, and ActiveSync doesn't pick up anything. I can boot into the bootloader screen, which behaves as it should, getting picked up by windows. I have tried itsutilsbin, but does nothing as ActiveSync isn't initiated to try and pull the files off the device. And Google has only so much information.
So I'm pleading (nicely ) is there anyway to get files off a semi-bricked Treo? I am competent playing and messing around with flashing and upgrading, and willing to try anything to get all the files off it.
Hope someone can help!
how many photos can you fit on a palm without a memory card cant to much can it. Well have you tried ringing palm and ask them if they have data recovery. there is one very very very long shot like 1% chance that it will work and do not do this if you can not find a data recovery program for the palm is hard reset it if you can then run the data recovery software. I do repeat 1%!!!!!!!!!!!!! I say ring palm see what they say.
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here