Hello. My ultratablet has been running fine on 2.0.305 since the release but last night it crashed on me and rebooted. During the reboot I saw the "updating" screen and when it finally booted up I had a warning that I was running out of disk space (o have 52gb free). This warning keeps popping up and the whole system runs very slow. After a few mins it reboots on its own and repeats all over again with the updating screen and everything. Is there any way out of this loop?
dylantep said:
Hello. My ultratablet has been running fine on 2.0.305 since the release but last night it crashed on me and rebooted. During the reboot I saw the "updating" screen and when it finally booted up I had a warning that I was running out of disk space (o have 52gb free). This warning keeps popping up and the whole system runs very slow. After a few mins it reboots on its own and repeats all over again with the updating screen and everything. Is there any way out of this loop?
Click to expand...
Click to collapse
You're going to have to wipe the device via fastboot -w
Seems like a system partition may be corrupted.
In an earlier thread in this subforum you'll find a link to the factory image. Follow the instructions and hopefully you'll be back to normal. Unfortunately you will lose all files and info on the device so backup first
dylantep said:
Hello. My ultratablet has been running fine on 2.0.305 since the release but last night it crashed on me and rebooted. During the reboot I saw the "updating" screen and when it finally booted up I had a warning that I was running out of disk space (o have 52gb free). This warning keeps popping up and the whole system runs very slow. After a few mins it reboots on its own and repeats all over again with the updating screen and everything. Is there any way out of this loop?
Click to expand...
Click to collapse
Do u have Spotify on your tablet?
Your Jide Ambassador is here!!!?
I did not have spotify installed on the tablet. I fixed it by doing a factory reset via the bootloader. Seems to be okay now.
Other.. options
Android uses db files... to keep a log of the indexed files of your harddisks
http://www.cnx-software.com/2016/12/21/something-is-eating-my-android-tv-box-internal-storage/
Opera and mega (filehost) downloads... (mine was 1.7 gb) not releasing temp/local/file
On Allwinner units.. its the cache..most of the times (fix : settings/storage/cache)
Just some thoughts... for next time
Related
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Godders11 said:
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Click to expand...
Click to collapse
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Many thanks, I'll give that a try.
sfhub said:
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Click to expand...
Click to collapse
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
doggie123 said:
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
Click to expand...
Click to collapse
Hmm, I wasn't expecting that to happen, just expecting some file corruption to be overwritten, but it looks like you potentially had some bad sectors in the eMMC as well that got blocked out automatically by the erase.
This reminds me of the eMMC problem we had on Samsung where they changed wipe data to do a secure erase and that triggered an eMMC bug that left people with megabytes of unusable sectors.
If I were you, I would only run my system using a JSS15Q kernel because that has the fixes for the type of issue your unit seems susceptible to.
http://forum.xda-developers.com/showthread.php?p=44954087#post44954087
Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
norysrinivas said:
Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
Click to expand...
Click to collapse
Try wait little more time. I must wait 20 minutes but with another situation and it boot up. Give also information about rom and kernel which you use (build version too of both) will be easy.
Did a wipe cache partition which didn't help, later wiped to factory reset via recovery mode which helped to regain the device access.
How ever the device was running on stock android on android 6. It just rebooted automatically and never came up. Though as said about factory reset helped.
The optimization took me more than 30min. I just left it and did my jogging.
sent from OPO using Tapatalk
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
I'm currently running the latest PureNexus (MM) with a pretty vanilla setup, I.e. no xposed, root, etc. All the sudden yesterday I had a hard crash while doing nothing in particular, a sudden reboot that sent me into a boot loop. It reboots right before the boot animation would appear. The only way I was able to fix it was to wipe the data partition. I was subsequently able to restore my backup and it booted successfully. The frustrating part is it's happened several times since then. In fact I can't keep it running more than a few hours without the same thing happening, even after doing a full wipe. Any ideas?
Thanks!
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
ts_mpls said:
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
Click to expand...
Click to collapse
Did you use flash-all.bat from google image or you flashed the images one by one?
I tried both. Both N and MM. Apparently I stumped Google too, they're sending me a new one.
that's weird... Glad you got a replacement though!
OnePlus 5 keeps turning off as soon as it gets to the lock screen. I installed the latest ota file from OnePlus website for the device via adb and it was successful but again every time it gets to the lock screen it shuts down and go back to recovery mode.
Any idea how to fix it ??
PS. In adb installation the cmd window stops at 94% with failed to read command no error but the device shows the installed successfully.
You can try flash a Roll Back ROM. I had a similar problem but it was a corrupted OTA I had of the 8.1 update due to unstable internet where I live, my phone would freeze, black screen and stay until I force rebooted. It wasn't until I noticed my phone using 5 out of 6 GB of memory that it dawned my phone had corrupt drivers somewhere so I downloaded a roll back OTA all the way back to 8.0 and my phone has been happy since.
Bilal.Android said:
OnePlus 5 keeps turning off as soon as it gets to the lock screen. I installed the latest ota file from OnePlus website for the device via adb and it was successful but again every time it gets to the lock screen it shuts down and go back to recovery mode.
Any idea how to fix it ??
PS. In adb installation the cmd window stops at 94% with failed to read command no error but the device shows the installed successfully.
Click to expand...
Click to collapse
Redownload the file, and flash via MSMTool. Go to guides section here on OP5, and use that tool. Just until you setup, do not activate lock screen or FP yet. Then do 3-4 reboot and couple of power off activities. This is just to understand if you have issues with any system hardware / software.
vdbhb59 said:
Redownload the file, and flash via MSMTool. Go to guides section here on OP5, and use that tool. Just until you setup, do not activate lock screen or FP yet. Then do 3-4 reboot and couple of power off activities. This is just to understand if you have issues with any system hardware / software.
Click to expand...
Click to collapse
i don't want to lose all of data, i have a lot of important data.
thats why i didn't perform factory reset in the first place.
arcticphoenix said:
You can try flash a Roll Back ROM. I had a similar problem but it was a corrupted OTA I had of the 8.1 update due to unstable internet where I live, my phone would freeze, black screen and stay until I force rebooted. It wasn't until I noticed my phone using 5 out of 6 GB of memory that it dawned my phone had corrupt drivers somewhere so I downloaded a roll back OTA all the way back to 8.0 and my phone has been happy since.
Click to expand...
Click to collapse
i tried last year's update, fortunately , i had the file on my phone from last year but still after installing it, the same problem. the phone shuts down as soon as it gets to the lockscreen.
Bilal.Android said:
OnePlus 5 keeps turning off as soon as it gets to the lock screen. I installed the latest ota file from OnePlus website for the device via adb and it was successful but again every time it gets to the lock screen it shuts down and go back to recovery mode.
Any idea how to fix it ??
PS. In adb installation the cmd window stops at 94% with failed to read command no error but the device shows the installed successfully.
Click to expand...
Click to collapse
Sounds like something got corrupt or incompatible files. Try downloading the full ROM from the OnePlus website and flashing in recovery. MSM tool is very helpful but a last resort.
Bilal.Android said:
i don't want to lose all of data, i have a lot of important data.
thats why i didn't perform factory reset in the first place.
Click to expand...
Click to collapse
If it's really that important you should have already had a backup... Sometimes we learn the hard way.?
Cheers!?