Related
The problem is the following: suddenly the device froze, and I waited quite alot before pulling out the battery. After that it would not start: it showed the HTC logo, over a white background, then, a black background with a sound and that was it.
I triede to reset it contless times withh no succes.
So I went into bootloader and made a factory reset, it worked but again the phone froze completely. What do I do now?
Edit - new info: now sometimes it starts after it freezes, and sometimes I have to pull out the battery, something is definetely wrong here...
Have try to flash ruu
Sent from my HTC Hero using XDA Premium App
No, I haven't tried to flash any RUU, I'm on the original ROM.
No more frezes since last freeze last night an hour after i started this topic; I reinstalled some apps but not as much as before; hope I'm lucky and things stay like this....
Anyone else had problems similar to this?
j1mmy said:
The problem is the following: suddenly the device froze, and I waited quite alot before pulling out the battery. After that it would not start: it showed the HTC logo, over a white background, then, a black background with a sound and that was it.
I triede to reset it contless times withh no succes.
So I went into bootloader and made a factory reset, it worked but again the phone froze completely. What do I do now?
Edit - new info: now sometimes it starts after it freezes, and sometimes I have to pull out the battery, something is definetely wrong here...
Click to expand...
Click to collapse
Exactly the same thing happened to mine this morning - it froze during normal operation (after six weeks of perfect use) I had no response to hardware buttons or screen touches so I was forced to remove the battery in order to reboot it.
It then would boot but each time would stick at the white htc logo screen and then the screen would timeout.
I was dreading that I'd have to try a hard reset just after I'd finally set the phone up as I like it.
so I removed the sd card from the device and rebooted by removing the battery once again
the device then booted normally, so I did a controlled power off, replaced the sd card and it booted fine.
Thankfully all fine so far (two hours later) fingers crossed.
The application that I was using when the device hung was a streaming digital radio apps that was located on the sd card.
Sent from my HTC Desire S using XDA App
j1mmy said:
The problem is the following: suddenly the device froze, and I waited quite alot before pulling out the battery. After that it would not start: it showed the HTC logo, over a white background, then, a black background with a sound and that was it.
I triede to reset it contless times withh no succes.
So I went into bootloader and made a factory reset, it worked but again the phone froze completely. What do I do now?
Edit - new info: now sometimes it starts after it freezes, and sometimes I have to pull out the battery, something is definetely wrong here...
Click to expand...
Click to collapse
The absolutely same symptoms. DS hangs installing new app. Has carried it in service-center. Now I wait for diagnostics results
Did you try to remove the sd card?
Sent from my HTC Desire S using XDA App
ben_pyett
Click to expand...
Click to collapse
For sure.
After the first hangup I have taken out the battery. Then DS hung again showing the HTC logo, over a white background. Then SIM has been removed. SIM were the first suspect. At the very first day of owning DS I have been forced to get new SIM card from mobile provider. Previous card was quite new, only one year old and works normally in Xperia X1i and other phones, but doesn't recognized in DS).
Finally, when I delivered phone in service-center, it was without the SIM and without SDHC cards, but all problems were the same.
Dare I ask was what was the application that you installed?
Sent from my HTC Desire S using XDA App
ReadItLater, but I think that it is simple coincidence. Phone wasn't started even when I managed to make factory reset (Volume Down+Power). After that phone wasn't launched any more.
Needed Hard Reset!
Removed. see duplicate post in more appropriately named thread [URL="http://forum.xda-developers.com/showthread.php?t=1036835&page=3"]http://forum.xda-developers.com/showthread.php?t=1036835&page=3[/URL]
Removing both cards solved it for me today
The frequency of the reboots on mine increased and today it crashed. Hard reset brings it to the white screen + htc logo but no further.
Tried with and without SIM Card, with and without SD card. The only way it will get past the white screen is with both cards removed but then of course, you get to the screen where it tells you to take insert a SIM Card. Doing so, turns the phone off again, but then (for me at least), it was OK to carry on with setting up the phone....which I am now doing...hope this isn't going to be a regular feature.
So far I've only got the stock ROM and nothing clever on it.
kc1 said:
The frequency of the reboots on mine increased and today it crashed. Hard reset brings it to the white screen + htc logo but no further.
Tried with and without SIM Card, with and without SD card. The only way it will get past the white screen is with both cards removed but then of course, you get to the screen where it tells you to take insert a SIM Card. Doing so, turns the phone off again, but then (for me at least), it was OK to carry on with setting up the phone....which I am now doing...hope this isn't going to be a regular feature.
So far I've only got the stock ROM and nothing clever on it.
Click to expand...
Click to collapse
Blimey, thats doesn't sound good
This is the point where I had to perform my first hard reset to re-enable the device.
How many times has this happened to you now and in what timeframe? have you had to do a hard reset before now?
I'd consider getting a new replacement SIM card and even using a different SD card, just so that you can rule them both out of causing the problem and if it happens again then return the device and be confident that its at fault!
If you return the device currently the shop's bound to say that the problem is with SIM and/or SD!
I've had it about 2 months and the involuntary reboots must have happened about 8-10 times starting in a about week 2. A sort of partial reset happened about a week ago (wallpapers and app short cuts disappeared). Then the phone crashed today while dialling into voice mail (Vodafine UK), and rebooted into a black home screen that would report a com.<whatever> error if I tried to get into the settings, or run anything. It would let me power off, but the only way to invoke the hard reset was vol key down when powering up
Today has received the answer from the service center.
They didn't name the reason, but have told that it is a guarantee case. Have suggested to replace the motherboard.
HTC DESIRE S Factory reset doesnt work
Sorry I'm new to this forum:, Hi I need some help please. I managed to unlock boot loader, today than when I was trying to turn s-off. With cmd I wrote on C:\Android this command "fastboot flash boot boot.img" downloaded from dev website viva unsecured boot zip. than since than mobile doesn't restart it just goes on various colours (blue red purple) and freezes.
Can anyone help me please.
Thanks
Petrit
Petrit said:
Sorry I'm new to this forum:, Hi I need some help please. I managed to unlock boot loader, today than when I was trying to turn s-off. With cmd I wrote on C:\Android this command "fastboot flash boot boot.img" downloaded from dev website viva unsecured boot zip. than since than mobile doesn't restart it just goes on various colours (blue red purple) and freezes.
Can anyone help me please.
Thanks
Petrit
Click to expand...
Click to collapse
did you flash a ROM? which one? did you wipe the phones partitions before the ROM flash via recovery?
I'm running stock S3 software, and I hit a snag this morning where the phone was stuck in a reboot/deadlock cycle. It would come up to the lock screen, and after about 10 seconds, deadlock. I was getting ready to wipe the phone, when I got a call from my wife during the brief "uptime" of the phone, which seemed to break the deadlock.
I was able to get what data I could off of the data partition (photos, etc), but now it remained stuck on the same issue on boot. Anyone ever see this before? I had to factory reset the device to get it back to normal.
mikecico said:
I'm running stock S3 software, and I hit a snag this morning where the phone was stuck in a reboot/deadlock cycle. It would come up to the lock screen, and after about 10 seconds, deadlock. I was getting ready to wipe the phone, when I got a call from my wife during the brief "uptime" of the phone, which seemed to break the deadlock.
I was able to get what data I could off of the data partition (photos, etc), but now it remained stuck on the same issue on boot. Anyone ever see this before? I had to factory reset the device to get it back to normal.
Click to expand...
Click to collapse
I replaced my phone, it was working fine for a few weeks, and now this bull**** is back. It gets up into the Touchwiz UI, then hangs for a while, and then resets the UI. This keeps happening repeatedly. I have to boot into the stock recovery and wipe the phone.
Does anyone out there know of anything like this? Are there incompatible apps with the S3 and touchwiz that can cause this? Anyway to debug it?
Thanks,
Mike
A couple of months back I decided to root my device. I did this using the unlocking the bootloader method. As a result, I lost my DRM keys, and I managed to restore DRM function by following the methods detailed here: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
I had to download the stock Android 4.4.4 from online, which I flashed my phone with - no problems. Things ran smoothly from then for about a month, and then I realised that my cellular network started to malfunction, and I couldn't access apps like YouTube and Snapchat on the cellular network. This prompted me today to do a "soft reset" of my phone, by holding the power button and volume up button simultaneously for about 3 seconds - under the impression that it would restore my phone settings back to the factory default.
Much to my horror, the worst case scenario happened. When I performed the soft reset, my phone vibrated 3 times and switched off. When I tried to turn it back on, it would show the boot-up screen indicating "SONY", followed by the next screen indicating "powered by android", and then it would show the blue screen with the wavy lines. It stayed on this screen for about 20 minutes. I figured something was wrong, and I tried to soft reset it again, only to be stuck at the blue screen once again. I decided to let it stay that way for 2 more hours, in order to drain the battery. When the battery drained, I turned it back on, and it was still stuck at the blue wavy screen.
I don't know a whole lot about Android phones, and I have no idea why this is happening, but it is causing me an immense amount of frustration - I have invaluable data on that phone, and to lose it would just be devastating. I can't even begin to describe it. I'm using TWRP recovery, and I'm also using TitaniumBackup which is backed up onto my phone's internal storage, and I can't access any of the files on my phone from my computer, because it doesn't recognise my phone.
This has been a long one, thanks for bearing with me. I've got a few questions:
1. What's the problem that's preventing my phone from booting?
2. How do I fix it?
3. If it's unfixable, how can I retrieve my data from my phone?
Really, really hoping someone can help me out on this - I'm completely lost and am desperate here. Thank you in advance!
Can you boot into TWRP's recovery mode using the volume down key?
Just press volume down when you see the green light on your notification led upon powering on your phone
Well something keeps the phone to boot, try to clean cache in recovery, it might help.
But to restore data on internal storage, count it as unpossible.
Hello all,
Hoping you might be able to help me troubleshoot a family member's dead S6. He took it in to Sprint a couple of days ago with some issues, and got it back from them the next day claiming they detected water damage. No warranty on the phone, and to make things worse it's a rental. The phone turned on before being brought in and was just sluggish and chugged out sometimes, and now will only go through the Samsung logo and hang immediately after on every boot attempt. From what I've been told, the phone's never been dropped in any liquid, so I'm not sure where the water damage claim may have come from.
Either way, I've been trying to see if I can do something about it. Here's what I've tried so far (in order), to no avail:
Hard reset: Since phone hangs after the initial splash screen, I have to enter download mode, restart, and then hold the proper keys then. I am able to wipe all data/factory reset, but nothing changes.
Let battery drain down completely, charge, start phone. It actually managed to boot part-way, and hung up on "Updating Applications" screen. Subsequent restart attempts led back to black screen.
Reflash: Phone boots successfully into download mode, and I am able to flash firmware for G920P. May be important to note that the two times I tried 5.0.2 with PDA G920PVPU1AOCF, I got a FAIL in ODIN at NAND Write, but was able to successfuly flash 5.1.1 with PDA G920PVPU3BOL1.
Still not sure if I am able to distinguish a hardware issue. I would highly appreciate it if someone here can help or suggest further troubleshooting steps!
Bump?
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