Database Users

[Q] Problem: Unresponsive screen after update

My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated

I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.

Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.

When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.

You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"

Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.

[Q] Is My Atrix Fixable?

My apologies, as I wasn't sure where to post this.
For a long time now I've been running CM7 both the nightlies and the weeklys with no issues. Yesterday I decided I would try Neutrino ROM and installed GT 2.5. After that I noticed I had no data connection so I attempted to patch the ROM using Notorious's recommendations to no avail so I installed 2.2 and the Google addons, Sync, etc..
All was working great, however everyone said 2.5 was better in the forums so I installed it again today and attempted to patch as explained and this time was successful. I had data connection again and all was well. About an hour later I went to use my phone and it was completely black.
I attempted to power it up and nothing happened. I finally had to pull the battery and was able to get it to boot up properly, however my data connection was gone again. I ran the sysctl -p command in terminal again and rebooted it to no avail. I finally decided to go back to 2.2 which worked properly last night, however after installing from the zip and the addon zips it went to the 'Dual Core' screen and then rebooted back to the 'Dual Core' screen and keeps doing that.
I attempted to go into Recovery Mode, however when it says 'Entering Recovery Mode' it just goes black and I can't power it back on. I then have to reseat the battery before I can get it to work.
I guess at this point, is there anything I can do to get my phone back? I've seen the hard brick messages and I don't have that (yet), but I am not sure, because I apparently can't get that far. Thanks for any help you can provide.
-Dave

Sounds like a hardware problem to me. I recommend taking it to a service center ( for me ATT has one I use.) and sometimes they can boot it up. Or they can maybe give you ideas.
Just to confirm you can't boot anything right??
Sent from my Atrix with XDA Premium App

Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.

JeRrYFaR said:
Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.
Click to expand...
Click to collapse
Awesome good to hear. I would change the title or at least add, solved problem
Sent from my Atrix with XDA Premium App

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.

Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.

I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

No root access, cannot update, no way to fastboot.

Okay guys, I need your help. I wanted to return to complete stock and update to newest version. So I downloaded a stock ROM and let it flash the stock recovery. I got a notification for 4.3 update and went ahead and flashed that sucker. During the installation, up popped "Error". It stayed frozen on that screen, so I hard rest it, and restarted my nexus. Well, the installation went through fine. Disabled super user and went about trying to force the 4.4.2 update. Sure enough that kicked in as well. Now, I also got the error on installation of that as well, but this time, when I rebooted, it was still 4.3. I've gone through it about 10 times now. And it gives me the error every single time and remains 4.3. I did a little googling and found out how to get there error log, and it says unexpected content in boot animation.zip.
Unfortunately one of my data pins is busted in my Nexus's USB port, so connecting to PC is not an option for me. Plus my PC is down for the count until I can get a new motherboard in her. Is there anyway to obtain root without connecting to a PC on 4.3 or at least get the update to take?
Is there possibly anyway to wirelessly adb from another android device? Would that even help in my situation?
I've tried " root master" and it seemed to work, even made the Chinese root permissions manager(as a system app) for me, but I can't grant access to anything, nor am I even give the option to. Also, when I tried that, it kicked SuperSU out of system and into regular old data apps.
I suppose I can just stick with 4.3, but if you guys could, I'd love some help.

[Q] Black screen after installing Xposed

Hey guys,
So I've got a problem. When I had originally rooted my phone in the beginning, I hadn't installed safestrap; I installed everything else: busybox, superuser, etc. So I kept on regularly using my phone and what not, updating and making sure I kept root. I was able to follow muniz_ri's tutorials to stay up to date and keep root. So eventually I was on OE1 stock rooted rom and had stopped there (accidentally accepted an OTA update after OE1 so I quickly froze the update thing [forget what it's called] through TiBU, hence not being on the most current firmware).
I wanted Snapprefs but needed Xposed. And to get Xposed, you need safestrap (from my understanding). I followed this to get safestrap (I think that's what the overall goal of the tutorial was for) and got safestrap working. Then, tried to install xposed using this and this. Successfully got the app, but then it said something along the lines of "you have not installed the framework" or something like that (that would be the zip file that I had to download right? The file that came from following the flow chart?). Used safestrap to install the framework (aforementioned zip file), then rebooted. However, after the Samsung Galaxy S5 menu and the safestrap menu, the screen just stays black. There is nothing. When I have my phone connected to the computer, the computer makes its jingle like it recognizes it (however, nothing comes up on the computer), the phone stays black for 2-3 minutes maybe, then boots into recovery mode (not safestrap recovery but stock recovery, where you use the volume buttons). I did a wipe data/factory reset (or whatever the option is called) in the stock recovery menu hoping it would fix something but it didn't. Just trying to include as much info as possible. Would flashing with this in Odin help? Read somewhere that it would put me back at square one so I could do everything over again, which I am not opposed to. However, I thought you couldn't downgrade from OE1 or anything higher?
I'm at a loss as to what to do next. Searched everywhere but couldn't find anyone with the same problem as me. Any help would be appreciated.
Thanks guys!
P.S. Sorry for going parentheses crazy

Found out what to do right after posting. Had to flash the BOE1 factory tar image in ODIN so back to stock, unrooted with all this bloat
Will be checking back periodically in hopes of a root method for latest firmware.