Database Info

[Q] Why does it do this?

Every ICS ROM that I have flashed on my phone has done this. I never hear anyone discussing this and I can't be the only one. Why and is there a fix?
{
"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"
}
I get it in the app drawer as well.

Have you done a full wipe and is hardware acceleration enabled?

Not So Strange...
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your device like with official firmware?
And several other things...

peter_dizai said:
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your devce like with official firmware?
And several other things...
Click to expand...
Click to collapse
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.

Now,It's Better...
kazerak2 said:
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.
Click to expand...
Click to collapse
Ok,first try to flash latest official firmware which I think is:
Ics 4.0.4
Baseband Version: D720SPRKH1
Build Number:IMM26
and here is a how to:
http://www.techzek.com/how-to-update-sprint-nexus-s-4g-on-android-4-0-4-ics-firmware/
Afterward flash following recovery:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo.img
Then try to flash:
http://bigota.d.miui.com/2.3.30/miui_NS_2.3.30_c1e078377e_4.0.zip
or
a cyanogenmod 9 and report back please...

^ Is that the correct firmware to flash for the 4G nexus s?

That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?

wild1z said:
That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?
Click to expand...
Click to collapse
Stock launcher, I've never used a different launcher other than stock on all my ICS ROMs.

I Edit the firmware,check and flash it.

Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?

kazerak2 said:
Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?
Click to expand...
Click to collapse
See my signature for proper FULL wipe. Something tells me you're not wiping system.

I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?

[email protected] said:
I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?
Click to expand...
Click to collapse
I too have done a full proper wipe with that same rom and still have the issue from time to time. Next time you get it try to fore stop the stock launcher. That fixes it for me, until it happens again. But for me its something with the stock launcher.

Display broken after root

Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
{
"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"
}
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.

This looks bad. Hope you can fix it!

I seriously doubt that this was caused by rooting or flashing the firmware. You've got a faulty screen.

This has nothing to do with rooting.
This is clearly a Hardware defect. Root is only a Software modification.
Gesendet von meinem SM-G930F mit Tapatalk

Have seen many people with this faulty screen. This should be a hardware issue. Get it replaced
Sent from my Silver Titanium Galaxy S7 Edge

BigMani said:
Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.
Click to expand...
Click to collapse
I agree with what other said. This has nothing to do with rooting. Somehow the bad display showed off it's real colors coincidentally after you root. Only way is to approach Samsung ASAP for warraty repair. Not sure whether they will check the device is in 'modifed' state (rooted) or in 'official' state for any such serious hardware issues. But you gotta say a lie about when this issue popped up. That's it. If you're lucky you will get the LCD replaced.

Hi all
many thanks for all your feedback. under the condition that we believe it is a hardware issue, I can keep my decision about doing the rooting, on the other side I will never understand why it was happing exactly at that moment.
However it seems that I had extremly luck. Today I went to the shop where I've ordered it online and they informed be about the DOA (Dead-On-Arrival) warranty, which is only possible within 7 days after purchase - today was day 7
they did just replace the device with a brand new one, they even didn't had to send it to Samsung before giving me a replacement. I was walking out with a new device :angel: :angel:
To finish here, I tried now exactly the same process as on saturday: first flashed latest firmware G930FXXU1APD1 and then I applied CF-auto-root. You can't imagine how nervous I was during these few reboots and hoping that the same problem does not reappear again (I could not go a second time to the shop with the same issue...). but this time all went well. latest firmware, rooted and now also debloated a bit.
again thanks to all of you.

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"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"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

S7 battery life issues on Oreo, Nougat, Stock, Superman etc.

Hello all,
Whilst there are many posts like this about battery issues, I thought I'd make my own because I've already tried all the approaches I can think of and I'd like to avoid any unnecessary confusion between posters.
I have less than 3 hours screen-on time on my Samsung S7 SM-G930F (international model) and horrific standby time, meaning I'll run out of battery before the end of the day even if I don't touch the phone at all. When I first got the phone, I got 4-6 hours screen on time and I see no reason why this should have changed so drastically. This is a somewhat recent occurrence, over the last 2-6 months (I believe it was gradual, so I can't quite pick out the time it started happening).
{
"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"
}
So far, I have tried:
Factory reset
Uninstalling all unnecessary (non-core) apps
replacing the battery
draining and recharging the battery fully
underclocking the processor
a multitude of different stock ROMs, both Nougat and Oreo
a few different Kernels
At best, playing around with these options has net me maybe a 5-15% improvement overall, much less than the 70-100% improvement I need to get back to what I had during early Nougat / late Marshmallow days.
Bar literally just getting a new phone, I would appreciate any advice you can give me.
EDIT: System2 log:

Was the flashing of different ROM's via TWRP or Odin?

Beanvee7 said:
Was the flashing of different ROM's via TWRP or Odin?
Click to expand...
Click to collapse
TWRP

I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.

Beanvee7 said:
I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.
Click to expand...
Click to collapse
I formatted internal storage via TWRP more than once though. I would have thought that would have fixed it.

I've added a System2 log for extra information in the OP

Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.

Beanvee7 said:
Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.
Click to expand...
Click to collapse
Ok. Thanks a lot. I'll try it and report back in a few days.
I'll probably need to get the latest files from Sammobile (more like Sam-slow-bile).

samfirm tool still works for obtaining the latest firmware files, and I get max speed using it on my internet (100mbs down)
For older versions you might have more luck with updato.com, for me I get almost full speed if I use a download manager, but it does have a bit of a slow start period.

hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?

dengiz-islam said:
hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?
Click to expand...
Click to collapse
Change battery in Samsung service

Finnishman said:
Change battery in Samsung service
Click to expand...
Click to collapse
Hey, I was about to open a new topic, but maybe you could answer me here I was about to change the battery I installed an app called AccuBattery when I go to health it shows that my battery health is 48% and the estimated capacity 1.429mAh is the battery dead? I don't know if those are also acurate stats what you think? when I calculated how much I lose me with apps and stuff it exactly comes out like 1.400mAh huh? ...

Question Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"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"
}

It seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..