Database Info

[SOLVED] Desire S frozen after selecting "Simulate Secondary Displays"

Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!

So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.

Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.

SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!

PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.

Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?

Unsuccessful Root of HTC One M7 Need Advice

I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.

[Q] DESPERATE HERE: Phone won't boot after soft reset?

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.

[Q] Warning: Newbie student driver -- Boot animation hang

UPDATE: I was able to fix my phone using Eross's guide 'http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632'. Very relieved and thankful. Good luck and hang in there.
I'm learning my way around slowly... posted incorrectly to XDA Assist forum. This appears to be the more applicable forum, so here is a copy of earlier appeal:
I am very sure that there are all sorts of variations on this but I am sufficiently clueless to need a whole new level of hand-holding. I have a Lolipop level Nexus 5. Never did any modifications. On 7/10/15 I turned off the phone and turned it back on a few minutes later. Google was displayed and it started in with the 4 spinning colored balls..... It never gets past this (is this a bootloop?). I can let it stay in this pretty hypnotic display until the battery is dead... hours and hour. I tried the power down, power up and volume down to get to recover mode ... then the power and volume up to get to wipe and delete phone, it says it completes. Rebooting leaves me in the same condition. I have had the phone for just over a year and never had any issue. It is in prime condition, hardly a scratch.
I need someone to hold my hand and tell me everything is going to be alright. And please, what do I do? I see other posts about partition corruption ... how do I check if this is the issue? If it is the issue, I'll tell you right now, the solutions talked about are well beyond me.. flashing this and editing that and boot to adb and spinning in place, chanting naked during a full moon.
Any body feeling like helping a lost soul?? Beg beg.
Additional info and concern.... Just noticed that what I asked the phone to do is 'wipe date/factory reset' . It responds with :
-- Wiping data--
Formatting /data...
Formatting /cache...
Data wipe complete.
That is all it says, is that the correct sequence? It doesn't say anything about the cache and factory reset. Clueless. Thanks.
Also... saw something saying to run fastboot clear cache , I've downloaded and installed an Android SDK for windows. Getting way over my head I'm afraid.

Question Z flip 3 bootloop

The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer

Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.

I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.

Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left

twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer

There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.

I see, alright, thanks a lot, I'll consider resetting it

It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.

Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )

ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.