I was pretty bored a few minutes ago so i decided to try using my phone with a super low res. I opened up the app resolution changer and put the resolution to that of a galaxy young. For a few seconds, it worked and then came up with the failsafe "will revert after 13 secs" and then the phone rebooted itself. The boot took ages which told me that i'd messed up. Eventually it booted, and as i then expected, System UI crashed, Along with Contacts, and the Keyguard.. I tried to access the phone over AFT and adb, no luck. I've backed it up, and i'm going to try restoring an old one i had, although i'd prefer not to. I use PhilZ touch, and the build i have doesn't support adb either.Is there anyway i can pull the build.prop or otherwise reset the resolution?
Related
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.
Short and sweet. I haven't used SetCPU for awhile and I've been using the ROM in my sig, which isn't entirely stable. Though I went to set the CPU to max 1890Mhz just before I went to use Titanium Backup to do a huge compressed backup. So it makes it a little faster. I accidentally (honest accident) swiped to the end of the list on available CPU frequencies.. I think the highest was like 2334 or something.. well the phone crashed at something like 2035. I rebooted it and it booted up fine, but there had been some noticeable changes. Some apps I had frozen had been unfrozen, some apps had lost their settings etc. I figured this was due to a bad shut down.
Today I was asleep and I left my phone like usual so the alarm would ring. When I woke up I dismissed the alarm and the phone hung for a good 20 seconds. Then 3 apps updated and the phone crashed whilst browsing the play store.
Now when I tried to boot I got that typical vibration that something had got unresponsive in the background and was crashing. (Whilst at boot logo) It was just doing a loop of that. Then I rebooted it myself again and now it does nothing. But it still was stuck at the logo forever.
So I went into PhilZ recovery and wiped everything. Dalvik, Cache and Wipe to Install a New ROM.
Now it won't even GET to the Booting Logo and just stays on the 'Samsung Galaxy S4 Gt-I9505' screen..
So gradually my phone is retreating into an even worse position.
Is there a chance I could have blown my CPU or something with overclocking by accident for a few seconds?
Nope, you shouldn't have blown a cpu, since it was working afterwards. Seems more like hangs due to some bad wipe.
What you can do is try to install any rom and make a full wipe. If that doesn't work apply a new kernel.
If that doesn't work. Try install stock samsung rom (no wipe)
If it's still in boot loop (do full wipe) however if you got any saved data do the last step if you're sure nothing else works.
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
I didn't set it to 'Apply on Boot' because it was only meant to be a temporary overclock.
I just took the MicroSD out now and I am going to put the latest release of the ROM I am using on it, flash it and see if it works and flash the modem too to try and get some more stability out of it. I'll see how that goes, if it doesn't get off the 'Galaxy S 4' screen I am going to have to assume there's a big problem...
Well then there can be something else, if you haven't sent it to apply at boot it can be some kernel issue or something got stuck. It seems like there's something that blocks you from booting the phone up. Interesting,
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
boot into recovery.. wipe /system, /data and /cache then install rom from external sd card
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.
Sorry for the long post! As a bit of background, I was running stock rom with sytemless root, EX Kernel, TWRP and I had just enabled xposed (the only new variable in my setup). So I plugged my 6P in at the gym before I play some ball. Phone proceeds to random "reboot" a few seconds later, no huge deal I thought. Then it enters The Indestructible Bootloop (IBL). It won't boot past the animated colored dots. Play for a couple hours, phone still not booted; slight to moderate anxiety setting in. I figure, worst case scenario, I have to flash a factory image when I get home. So I try to reboot it a couple times by booting into the bootloader (holding power and down vol), then recovery then reboot. I also flashed the xposed uninstaller and deleted /data/data/de.robv.android.xposed.installer/conf/modules.list: neither worked to solve the IBL. Then I just waited til I got home and tried to plug it into my Win 10 PC. Nothing. Device manager doesn't even recognize it as anything plugged in; moderate to high anxiety setting in. Note that I could previously connect it just fine and device manager doesn't see ANY kind of device connected, so I don't believe it's a driver issue or anything like that. So, through TWRP, I look to see what's on the device storage: I have an old nandroid ( I believe stock unrooted) and a custom rom, Chroma as well as some GApps and a couple custom kernels. At this point I wanted to preserve my text messages so I did a new nandroid then tried restoring the old nandroid as well as flashing Chroma without wiping data. Nothing, still won't get past the colored dot IBL. So then I tried doing a full wipe before trying the old nandroid and Chroma again. Nothing. Figured it may have been a malicious file on my sd card so I deleted a few files that I didn't immediately recognize in TWRP and tried all the above steps again. Still nothing. So I just called Google and they offered to replace it. However I would like to have my phone for the weekend and not have to have a $650 hold on my account. I'm on Project Fi so I can't use a temporary burner phone. I figure I'm probably screwed but hopefully one of you geniuses could help me out. Thanks in advance!
tl;dr: Phone randomly rebooted and entered indestructible bootloop. Windows device manager won't recognize it at all. Tried everything I can, including clean flash of custom rom and an old nandroid: phone still won't get past bootloop.
At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.