Missing call log entries after the android 9 update - Samsung Galaxy Note 8 Questions and Answers

After the android 9 update there are missing entries in my call log, only recent one remains in log while others are getting deleted automatically!!whats the problem?

Try wiping the Cache Partition in Recovery Mode and this sounds like a software issue. If that doesn't work then backup all the data stored on your device and perform a ahrd factory reset.

Related

[Q] i897 dont boot

I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.

TWRP Backup/Restore ERROR 255

I don't think this is a Moto X (XT1096) specific problem, but more so with TWRP. Phone works fine, just can't backup or restore
I'll try to get a log as soon as I can, just need to figure out how
Problem
I can't backup or restore (and maybe can't delete via TWRP?) from TWRP, getting errors at the start (can't access .../data/cmthemes and can't access .../data/motogallery) and then at the end TarFork() process ended with ERROR=255
Tried Solutions
Reflash TWRP (broke, had to use TWRP app to fix)
Upgrade TWRP (says it failed, but worked)
Enable Compression (no real difference that I can tell)
Cause?
I was on CM13 (2/2 ?), upgraded to most recent (2/6), didn't like it so wiped and flashed to original (1/29 ?) then restored backup (2/2). Probably wasn't the best way to do that, oops. Since then I have wiped and reflashed 2/2 and upgraded to 2/7, haven't done anything since (besides mess with TWRP)
Any help or ideas would be appreciated!
Please lock/delete
Solution: Factory reset, only method that worked for me
Be sure to clear cache
Solution: There is a file on the phone that is preventing the backup. Not sure what is creating it. It could be an artifact of a TWRP backup restoration, which is the first time I had the problem.
Look in the TWRP log ([SDCard]/recovery.log) and scroll near the end - you will find the culprit there, almost always in the [root]/SYSTEM folder but sometimes in multiple folders. It has many names. I've seen it called, simply "999". On my Moto G4, it was "d.addon". Delete the folder and you're good to go.

OTA Updates and Proper Procedures (wipe data/factory reset, wipe cache partition etc)

New Verizon S6 Edge (sitting in the box for 1-2 years) and I used the OEM adaptive fast charger to bring it from zero to 100% and then waited 10-15 minutes.
I used the built-in OTA updater, not Samsung/Verizon's Software Upgrade Assistant, and went through 11 system updates over the course of 2-3 hours. Out of curiosity, would using the SUA have reduced the number of updates to apply? Edit: I am almost certain now SUA updates straight to the current build (based on their wording, link at bottom). Apparently if I wanted to go straight to current system build, I should have used SUA or a tool such as Odin to flash the stock firmware directly.
Here is a list of the software builds I went through:
G925VVRU3BOG5 - This was the build on my phone out of the box.
G925VVRU4BOG7
G925VVRU4BOG9
G925VVRU4BOK7
G925VVRU4CPC2 - This is the first official build of Marshmallow for this phone. After update success, I decided to wait a few minutes and then restart the phone.
G925VVRU4CPD2 - I received error 404 after automatic download failed. Manual download attempt OTA was successful.
G925VVRU4CPF4 - I received error 401 after answering no to the automatic download request because I was trying to prevent the error above. Manual download attempt OTA was successful.
G925VVRU4CPH1
G925VVRS4CPI2
G925VVRU4CPK2
G925VVRS4CPL3 - My battery charge ticked down from 41% to 40% just before I applied this update, 35% upon completion/success message.
G925VVRS4CQA3 - This is the last Marshmallow build available for this phone.
On Verizon's webpage it says to have at least 40% charge or 20% when hooked up to the charger. I am worried because I did not connect my phone back up to the charger for these last two updates. The last one really bothers me because it was 34% when applied and 29% upon completion/success message. Is there a way to verify everything was written correctly? Should I even be worried?
With exception of a few failed downloads, all updates -when applied- said successful first try.
I have the understanding that it is important to wipe (system) cache partition and wipe data/factory reset from the recovery menu after major system updates to avoid all sorts of potential problems. So, here are my questions:
Does wipe data/factory reset from the recovery menu also wipe (system) cache partition? If not, should I wipe cache partition before or after? I have found conflicting information on this. Edit: It is so confusing because when you search around there are tutorials only mentioning the reset, others saying to wipe cache before reset and vice versa! There are also people going as far as doing both of these before -and- after a system update! Edit 2: It appears that wipe data/factory reset formats /data, /cache and /sbfs partitions. So, wipe cache partition is redundant when performing a factory reset from the recovery menu.
Both of these videos demonstrate wipe cache partition followed by wipe data/factory reset. You will see /cache is unnecessarily formatted twice (picard facepalm).
https://youtu.be/-Y-aHwdjAZA?t=175
https://youtu.be/NUsV75KFLzA?t=65
Note: there is no Google account to remove (Factory Reset Protection/FRP, Google Account Lock etc) as this is a new phone.
I am under the impression that I should clear all app cache, app data and maybe reset network settings before I attempt the recovery menu methods above. This is overkill/redundant, right? Edit: All this stuff appears to be stored in somewhere in /data (even an app's cache, within a subfolder of each app).
Aside from backup (in my case does not apply), is there anything I should do before (or after) recovery menu wipe(s)? I want to ensure clean slate. Edit: It seems wiping /data and /cache is all you can do in terms of user-accessible data.
I notice there is a "Factory data reset" option from within the OS under Settings: Backup and Reset. Does this behave any differently from the recovery menu method? Edit: I found via thedroidguy.com that it does not reformat the /data partition as the recovery menu reset does but only clears it. It also has Backup and Restore options. Are there any other differences? Does it clear other partitions than /data?
Also, I notice in Settings: About Phone: Status there is "Factory data reset". For me, it says "Unknown". I assume this value is a counter, log or timestamp of the last known factory data reset(s). Maybe it is only triggered when the reset is performed within the OS, but I have no idea. Anyone know what this really is? Will a recovery menu factory reset trigger it?
Under Settings: Storage there is Cached Data. If I clear this, does it include all application cache -and- all application data or just the app cache? Edit: I am pretty sure now it just clears all applications' cache, so it shouldn't affect anything unless maybe an app is poorly coded and stores things in cache that should be elsewhere. On a related note, when clearing app data from apps individually its app cache will also be cleared. I am not sure if clearing Cached Data from this Storage menu touches the system cache partition.
Any documentation or links would be very much appreciated; I am running out of steam here sifting through search results with different keywords and modifiers.
If anything I said is wrong or not entirely correct please say so!
Links:
https://android.stackexchange.com/q...set-exactly-the-same-as-wiping-data-and-cache
https://android.stackexchange.com/q...-factory-reset-and-clean-the-phone-completely
http://thedroidguy.com/2015/08/sams...-cache-partition-factory-master-reset-1048263
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
http://www.androidcentral.com/android-201-how-and-when-clear-app-cache-or-data
https://www.verizonwireless.com/support/knowledge-base-80200/

Lockscreen notifications gone after system update

Hello guys,
My Huawei Mate 20 lite has just updated to latest firmware (SNE-LX1 8.2.0.138(C432))
Now all application notifications are gone from the drawer and the lock screen. I have tried enabling all possible settings, including ignoring battery saver, allowing to draw over other apps, etc.
All messengers get just a dot on the icon - no banner, no lockscreen notification.
Spotify and Poweramp have no drawer and no lockscreen control as well - to skip a song, I need to unlock the phone and open the actual application.
I did honestly try to google, disabled smart lock (no face unlock present) and smart cover - no luck.
I have tried re-installing Spotify - no result.
Any ideas?
Worked just fine up until the firmware update.
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
CamoAndres said:
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
Click to expand...
Click to collapse
Thanks for suggestion, but I couldn't say it's a fix. I'm rather trying to check if anyone else is having the same issue with the latest firmware and if there is an actual solution (ok, selling this phone and buying a normal one is another considerable option)

Help in decrypt data

hello can anybody help me please
i have forgotten my pin so i used this way to bypass it
rebooted to recovery and selected cancel in decrypt data
Because i don't remember what it was
and deleted what i have found form those files
--------------------------
recoverablekystore.db
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
--------------------------
now my phone opens up but stuck after lock screen at phone is starting
Note: i can enter notification bar and phone settings
could you please guide me how to fix it without wiping the data
ROM: CRDroid 6.13
TWRP: 3.4.0-10 by mauronofrio
@M.WeWe
This sounds like the issue with early Pixel Launcher Mods.
When disabling / removing the module, it caused exactly your problem.
Is your device rooted, did you use such a model and removed it recently?
With a root explorer (or within TWRP File Manager), navigate to:
data/system and delete the "package_cache" folder, then reboot.
This fixed the described issue in the past.
I've been looking for a solution to the same problem for a month.
After installing recovery the memory was encrypted and No os warning came.
It's been in my phone for the last 3 years.
goddamn google
I don't know if I can find a solution without losing the memory.
My nerves are gone now.
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
selaam34 said:
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
Click to expand...
Click to collapse
Whenever you switch the ROM you have to (!) Format Data - it's described in any good guide for how to install a custom ROM to Xiaomi
Formatting Data (that includes also Internal memory) establishes the new filesystem for the new ROM, ie for its encryption - that's why Formatting (not Wiping - wiping wipes the files but keeps the old filesystem) is required

Categories

Resources