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?

Tablet stuck in "Installing System Update to Error!" loop

My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.

Meth_Badger said:
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Click to expand...
Click to collapse
If I read your post correctly, you selected the right icon which is a Wipe data from your bootloader. When you executed that Wipe data, it will wipe everything on your internal SD including your /media folder or your personal files and data... The chance is very slim unless someone knows how to recover data from a wipe. Technically, your data is still there but it is only a dumb files which contain only 0's and 1's. Some recovery tools may be able to retrieve your data but I don't have that knowledge.. I hope that someone will be able to help you out and good luck...:fingers-crossed:

I'm afraid LMK is right: Your data is gone.
Do I suspect correctly that you interrupted the Wipe Data process after selecting it "accidentally"?
Choosign Wipe Data from the bootloader causes the BL to write a command to the misc partition to start the recovery and wipe the data partition. If you interrupted the process, there's no telling what and where that got corrupted - unless you just let it loop and pray that it finishes the wipe process which would erase the BL command. Connect it to power and let it loop for a few hours. What have you got to loose?
But your data is gone either way - sorry.

Morning, cheeky question(s)
Where are you located, and would you be interested in selling your bricked TF700? I have a broken screen among other things and would be interested in buying your tablet for spares if you are getting a new one?
PM me if you are interested.
Thank you
Freddie

I'm not all too sure what the Icon on the left wad, but I'm sure it said RKU or some sort. I would have given up all hope if I had hit the wipe data on the right.
Days recovery aside, is there anyway I can get my looped tablet to work? I plugged it into a comp and it didn't recognise it.

[Completed] [Q] Mercy. Newbie's Nexus 5 Bootloop

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.

Duplicate.
http://forum.xda-developers.com/google-nexus-5/help/warning-newbie-student-driver-boot-t3155923

Hudl 2 won't power on, boot partition corrupt

Hi guys looking for some advice for some problems I am experiencing with my Tesco Hudl 2. I was directed here by a friend of my mothers, so I am new here. I have searched and searched for a possible solution and haven't had any luck however I sincerely apologise if this question has already been asked.
So onto my problem I have a roughly 2 year old Hudl, other than the current problem it is in good condition, never been out the case or dropped and I haven't rooted it. This is the first problem I have had. A few months ago a friend was using it and despite me telling her not to, she played some Facebook games on it. After that it started coming up with crash reports and error messages and within a few hours was switching itself off. I had a quick search for some help at the time but as I have very little experience with android devices and couldn't find any kind of help I switched it off and left it at that. I realise now being switched off for that few months may not have helped.
Yesterday I tried switching it on to see if I could get it working, on switching it on with a full charge, it goes as far as the powered by android logo, sits for a minute, switches off and then tries again. I have attempted to perform a reset using the power button only, this done nothing.
I also attempted to bring up the Android system recovery menu using the power and volume up buttons. This brought up and error message stating that the 'efi hard drive boot failed', the next error message was 'no bootable device, hit any key' '[ok]', from here I can do nothing. The touch screen and the volume buttons are unresponsive.
Holding the power button eventually powers off the device.
I know this means that my boot partition is corrupted as I have previously performed boot partition fixes on a pc when a Linux clean install went haywire but I have very limited Android experience. The advice I received was that I have to factory reset the device and install a new copy of my boot partition, using abd on my laptop and to come here to XDA-developers forum for help with the process. I am using a windows 7 laptop currently. To be honest I don't know where to start and any advice would be hugely appreciated! Thanks in advance and sorry about length!

[HELP] GT-I9300 Stuck at bootscreen and "more"

Hey guys,
I spent about 2 days reading through every piece of guide I can find in here to resolve my issue and now, here I am. So the thing that started this whole pileup is that I did a cache and dalvik wipe. After which it booted to till the bootanimation and stayed there............Forever. I understand this is fixable, but here is the real problem. My volume button doesn't work. So I cannot go into recovery or download mode (download mode was accessible for a while until that button failed too). So then I tried rebooting with adb. But then it says that the device in unauthorized (I remember that the USB debugging option was set to ON a long time ago). In a desperate attempt to fix things, I opened the phone and checked out the volume buttons to see if anything can be done. The buttons are like fully damaged from the wear and tear over the years and I'm not just talking about the button but also the contacts. It still boots up to the bootscreen. At this point I'm only interested in getting my data back. My last backup was done a month ago.
Can someone please help me?