I've used had my Ouya for a few years now and today it just locks up. I get static audio, vertical lines, and lockups. I took the Ouya out and I noticed it is super hot. The fan only kicks on for a second during boot but never again... so it just seems to sit there and fry.
1: That fan should be kicking on.
2: It only locks up when I do certain things. Like Search, Factory Reset, nagivate menus, do stuff. If I just let it sit there, it typically won't lock up, but has.
I am kinda at a loss. I am thinking of reflashing another rom on it to see if that works. It boots up normally just locks up after about 10min. I am having problems with getting ADB working. When I connect it, it connects as a Media device MTP but no ADB driver being requested. I also cannot see the device with adb. I've tried the sysrq+Alt+i methods but it just reboots to a black screen with a ! on it. Doesn't really do anything from there.
Any suggestions?
Hey guys, I have a 5th gen Fire HD 10 tablet. I rooted it and put Google services and play store etc onto it. I wanted to remove it and go back to stock so what I did was go into recovery and did a factory reset from in there. Upon reboot all seemed fine, I entered my Amazon username and pw, chose my time zone, etc. However once I get past the initialization part and try to get to my homescreen it is just a black screen. I can swipe down from the top and get the menu and go into settings etc but as soon as I hit the home key it looks like it wants to go to my homescreen but I get the black screen again. Any idea what is wrong and how to fix it? I want my Fire tablet back to stock as if I took it out of the box and powered it on for the first time. Thanks in advance!
EDIT: Also, I've noticed if I restart the tablet and it's rebooting, I get to the Optimizing system storage and applications part and it never gets past there. The yellow bar is completely filled but it is just stuck there.
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
EDIT: I am now severely ****ed. Sideloaded android 11, didn't fix it. Went to see developper options and fat fingered disable developper options and to re-enable you need your pin which crashes the settings app. Since it wasn't fixed in android 11, september 5 security update AND september 1st google play update I am 100% certain that there will be no fix put out. Resetting later today and never buying a Google phone.
Without flashing a fresh OS I'm not sure if anything can be done. But a clean flash will wipe everything. Google won't help because they don't care.
frankbodyofwater said:
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
Click to expand...
Click to collapse
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
https://developer.android.com/studio/command-line/adb
jalado said:
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
Click to expand...
Click to collapse
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
frankbodyofwater said:
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
Click to expand...
Click to collapse
what is your issue you're having? you said you weren't able to download your files etc?
what was the problem in the 1st place?
My Fire HD 8 tablet got a forced FIre OS update from Amazon a couple of days ago, and I was surprised to see that it jumped from 6.3 to 7.3.1.6. Apparently Fire OS 7 is based on Android 9 (Pie).
Unfortunately the update brought the usual bunch of screwups:
- Most of the tablet settings reverted to default, and it has taken a lot of time to correct them all as issues arise.
- Many components and apps did not update automatically to match, and had to be updated manually.
- I was left with one item stubbornly stuck in the Download Manager queue that wouldn't go away or stop notifying me - the U.S. English Dictionary. After clearing the queue, clearing data and cache for the download manager, and rebooting several times, I finally found a place I could do a manual update of the dictionary several levels deep in the keyboard settings. That seems to have fixed it. Not a good design.
- Show Mode is broken. The tablet will still enter Show Mode and work for about 20 minutes or as long as the screen is active. But it now drops out of Show Mode just a few minutes after the screen goes to sleep, every time. I'm accustomed to it dropping out of Show Mode from time to time, but it's now unusable because of this. And that's not the only issue - the feature to automatically wake the Show Mode screen when the camera detects movement has stopped working after the update.
The issue of it dropping out of Show Mode was the most annoying. I tried everything I could think of that might affect it, and I finally hit on the cause by process of elimination: it's Bluetooth. The tablet is normally connected to a nearby Bluetooth speaker in Show Mode. That still works, but since the update it's causing the tablet to constantly drop out of Show Mode. If I turn off Bluetooth, the tablet stays in Show Mode. I suspect that this is a power management issue - somehow since the update reset all the settings, the tablet reverted to powering down Bluetooth after 20 minutes, and there's a bug that causes it to drop out of Show Mode when that happens. I went through all the settings related to power management, but no luck finding anything that apparently affected it. I even went to the trouble of creating a Tasker task to activate the Bluetooth audio every 15 minutes as a preventative measure. That was effective in preventing the tablet from dropping out of Show Mode. And then a day later I shut that Tasker routine off as a test, and the tablet stayed in Show Mode anyway! Somehow after enough time and enough reboots, the problem fixed itself.
Better luck on the camera motion-detection front - it started working again after I went through all the settings and flipped them back and forth to make sure they were set correctly. There has always been a bug in Show Mode that it has a fixed camera sleep period of 10pm to 7am, and Amazon forgot to provide a setting to change it (it's not the same as the Do Not Disturb setting). I suspect that the camera was stuck in sleep mode until I flipped all the settings back and forth.
DJames1 said:
My Fire HD 8 tablet got a forced FIre OS update from Amazon a couple of days ago, and I was surprised to see that it jumped from 6.3 to 7.3.1.6. Apparently Fire OS 7 is based on Android 9 (Pie).
Unfortunately the update brought the usual bunch of screwups.....
Click to expand...
Click to collapse
My tablet gets stuck in a bootloop after doing the update. Previously, I was on Lineage but restored it back to the previous OS6 version - now any time it does an update, i have to revert back to an old stock. Anyone have a suggestion?
Your Fire tablet is updated forcefully without your interaction. You can use a firewall to block these crappy and spammy updates.
Hope someone can help. I have an Android 8.1 head unit (Chinese) which has been working fine. I removed it from my car and powered it up in the house with a PC PSU, this enabled me to sit for a few hours and set all my apps and home screen up just as I want it. Once all was done, it was running great. I installed back in the car and on powering up, everything was good. A couple of days later, I got in the car and the android displayed “Erasing" and took about 10 minutes to boot. On boot it has gone back to factory defaults and deleted everything. Even worse, the original launcher screen will not come on and it just says “Starting android" but does not progress any further and I cannot get into any settings.
Does anyone know - How to Install the original or another Android that will work with my unit?
Or any other ideas? I'm fairly confident when it comes to fixing stuff, just need a walkthrough to get me up and running again.