[Q] [Problem] Galaxy Nexus memory bug and reboot problem - Samsung Galaxy Nexus

Hello everyone, I have a BIG problem on my Galaxy Nexus ("yakju maguro" (GSM/HSPA+) currently with 4.3 (JWR66Y) stock installed).
In the last few months I used AOSP Lollipop and my phone worked well. Few days ago it has restarted suddenly and contined to do it after random time... Then I flashed again the AOSP 5.1 but in the TeamWin recovery I noticed that my phone memory was more than 13 Gb, but my phone is the 8 Gb version! I checked online for a solution and I flashed the stock image to try a "reset" of the bug, but nothing happened: my phone still shows around 13 Gb. To test it, I copied up to 11 Gb of files and it worked, so the memory is really bigger than the previuos one (or at least it seems).
Now I'd like to know how can I fix this problem? If the phone will start again with freezes and reboot, what can I do?
I hope there's anyone with any suggestion... I have really no idea about what to do. Thanks to all that will try to help me, and excuse me for my poor english.
P.S.: here are 4 images that show the memory "bug":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: after I deleted the folder with the 10 Gb of files, the phone freezed and after a sound like a "pop" it restarted.

Related

[Q] WiFi not turning on and other problems

A relative has recently given me there Note 10.1 2014 LTE (Model number: p605) which is currently encountering some issues, in the hope that I will sort it out for them. The issues are all to do with the WiFi.
The device has absolutely no modifications, and running the stock ROM. Here is a screenshot from the "About" section:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem is that WiFi sometimes refuses to turn on. You slide the toggle, and then it just turns grey:
After a minute or so, it will then return to the off state. The funny thing is, rebooting the tablet will temporarily fix the issue, allowing WiFi to be turned on again. However, once idling for a few hours, the issue will return.
My relative says that this issue never happened on JB, but only started happening once upgrading to KK. So my question is: have any other p605 owners experienced this? If so, how did they fix it? If nobody has experienced this, could anybody recommend a good way to fix this? I was thinking about a factory reset, but this should be a last resort, as they really don't want to loose all of there data!
Thanks for the help!
Sent from my Nexus 7 2013, Running Android L

what's the problem?

My tablet seems to be messed up...
I get constant app crashes even when just browsing, watching a youtube video is almost impossible due to lag and antutu reboots the device or the app crashes and when I get a benchmark done I get this....:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's almost as bad as the Galaxy Y....
My device is clocked at 2.0gHz(or 1.7 or 1.5 it does not matter)
Trust me I've tried every rom... from kitkat cm11 to stock 5.1 and it's all the same
Is this thing broken?
Restore stock clock speeds, then maybe someone can help? Revert to stock kernel and ROM, replicate. That would be the first order of business.
Save your stuff and perform a factory reset: delete everything, flash the latest 5.1.1 factory image.
I guess you have dirty flashed your ROMs too often ? Some leave thrash behind and some so called "developers" like to use some tweaks which are no use anymore ( and have been made for Android 2 or even older ..)
If your device behaves like this even in a 100% Stock environment, it might be faulty indeed..

[SOLVED] HELP! Internal System error, GApps Crash

UDPATE June 17, 2016 - SOLVED!
Flashed stock KitKat ROM using the TOT method. Phone working fine again. Thanks to all
Main story
Ok guys so I tried to flash Beanstalk ROM and on the first start I got an error saying my phone has internal problems and will become unstable until I do a factory reset. Then the play store kept on crashing and crashing as I just ignored it until I got to the homescreen. After that, I went back to TWRP and factory reset my phone and wiped my internal storage. I booted up to the system and there goes the error again.
So, what I did is to flash Fulmics ROM once again and boom! The error was there ALSO! I couldn't start the play store to install apps. I tried to use LGUP to flash stock kdz but it seems like it can't detect my phone no matter what I did.
Please help me guys how do I fix this :S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My G3 is not my main phone as I have the G5 now, but please help me to fix this I still use my G3 a lot as a backup device.

Strange bootloop issue after display switch

Hi,
story first, problem below: I crashed (a while ago) the display of my Nexus 4. I changed it with some cheap chinese crap (that was offered as original, but well, China ) ... and the Nexus was stuck in endless bootloop. First I thought I did flash it wrong or did a mistake changing the display. After hours of looking for clues I gave up. Recently I found some idiot-proof flashing tool (SkipSoft) and tried it again with the oldest factory image available: occam 4.2.2 (JDQ39).
The Nexus did not only boot, but boot up faster than my none damaged Nexus 4. Ok, the display was in comparison like scaled to 90 %, but no real problem. I was kinda happy and tried to flash CM or the latest (5.1.1.) factory image available. And again, there way my problem. I did flash every factory image, except 4.2.2, and same sh**. Flashed 4.2.2. (again) - no problem at all. I did the auto upgrade to 4.3 - endless bootloop again.
Did anybody had this problem before? I think it's a driver issue, since it works with 4.2.2. but no later images. But is it Androids fault (display driver switch between 4.2.2. to 4.3)?
Btw.: pic of the original and the "oliginal" display:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Android 7.0 problem to recover my personal data

Hi
I bought an OUKITEL U11 PLUS years ago
It was working fine and one day it got stuck on logo screen after boot
i tried to backup my file with the android recovery on sd card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then i flashed it with OUKITEL_U11_Plus_OUKITEL_U11_Plus_V4.0_20170814
I tried to flash it with OUKITEL_U11_Plus_V1.0_20180310(20180529).zip
but no result the result was the same (stuck on logo screen)
After i flashed it with v4.0 version it worked
I did not recover my .backup files
I tried another faster thing
I backed up the userdata.img with spflashtool to my pc
then i flashed it back to the phone after i flashed it with v4.0
I got this screen
No matter what password i try i get this message
So i reseted the phone to use it
but how to recover my files ? please help me
Other thing how is the V1.0 more recent than the v4.0
This are the roms i found online
OUKITEL_U11_Plus_V1.0_20180310(20180529).zip
OUKITEL_U11_Plus_V2.0_20170624
oukitel u11 plus v3.0 20170809 20170811 2302
OUKITEL_U11_Plus_OUKITEL_U11_Plus_V4.0_20170814
I didn't recover my .backup files from sd card because it takes a looot of time like 3 days...
I think the phone was v1.0 when the problem happened
now it is v4.0
Thank you
I really hope you can help me
have a nice day
what am I missing?
why nobody is answering?

Categories

Resources