Problem with save the settings in P8 Lite - Android General

Hello,
Few days ago after few failed attempts to root my P8 Lite, I accidentally formatted system partition. I've found an image from my operator and installed it. Everything seems to be fine, but after rebooting system all changes (like default booting program, administrators of the device or displaying over other apps) are discarded and setting to default ones, they are not permanent.
Does someone know how can I fix it? This error keeps preventing me to personalise my phone in any way.

Related

[Q] Android 4.2.1 & encryption?

hi,
after i've lost root i had to downgrade/upgrade again and my tablet got reset and therefore encryption was gone too. now that i have successfully rooted again and upgraded to android 4.2.1 i wanted to encrypt again.
but it does not work. after choosing encryption within the security settings and entering the passphrase, it shows the android logo for a few seconds and then reboots normally. i've tried that 4-5 times now, it just does nothing, no error..
does it work for anyone?
i've found out why encryption didn't work:
if you have already created an additional user account (multi-user feature), it seems it is not possible to encrypt the tablet afterwards. after deleting the additional account, it worked properly to encrypt the tablet. then i've also created the additional user again without problems. no idea if that's a bug in asus firmware or normal behaviour in android (didn't find any reference regarding that).
Well found though. It does kind of make sense not to allow encryption if more than one user exists.

[Q] "Unfortunately, System UI has stopped." after OTA to LRY47I

After OTA update from LRX22C to LRY47I, device reboots with:
"Android is starting... Optimizing app xx of xx." (few minutes)
"Starting apps." (few seconds) "Unfortunately, System UI has stopped. Report/OK"
Whatever is pressed, pop-up just reappears.
Clearing cache from recovery restarts app optimization, but error persists.
Basically it's unusable but everything works in the background.
If e-mail arrives, notification sound is heard. Already set alarms work. Notification LED works.
Device is without any modifications, bootloader is locked and usb debugging isn't enabled.
Is there any way to access data?
Is sideloading customized kernel with usb debugging possible with locked bootloader?
Can application for wi-fi access be pushed via google play with preconfigured options and started automagically?
Anyone tried to rescue data after factory reset with dumping disk image and doing forensics?
Any other ideas are welcome.
Btw, there is a thread on Google's Nexus support group were users reported same issue:
(as a new user I can't post direct link here so search for "Android 5.1 is Here!" on google)
From one message it looks as if they are working on this but there was no official answer yet.
Have you pressed playstore? Id a similar problem and it was a playstore system app needed to be updated. Got a message when pressed playstore
zerosum0 said:
Have you pressed playstore? Id a similar problem and it was a playstore system app needed to be updated. Got a message when pressed playstore
Click to expand...
Click to collapse
I wish it would be that simple. There isn't anything on the screen except pop-up.
Hi,
I've just updated from 5.0.1 to 5.1 (Nexus 5) and I'm having the same problem. The device won't go past a black screen with the error popping up every time.
I have tried wiping the cache twice but the problem persists. I don't want to factory reset because I haven't backed up my data in ages and I'm unable to retrieve that data via USB or whatever.
I believe the problem is caused by the launcher (stock in my case), when attempting to draw the wallpaper based on the info posted in Google's productforums by another user who had the same problem (xda won't let me post the URL since my account has too few posts).
I thought of sideloading a launcher from the recovery menu, considering that maybe it will be able to draw the wallpaper and the other stuff, but I don't know if that will work as I think.
Any ideas, please? Right now my Nexus is software bricked.
heatley said:
Hi,
I've just updated from 5.0.1 to 5.1 (Nexus 5) and I'm having the same problem. The device won't go past a black screen with the error popping up every time.
I have tried wiping the cache twice but the problem persists. I don't want to factory reset because I haven't backed up my data in ages and I'm unable to retrieve that data via USB or whatever.
I believe the problem is caused by the launcher (stock in my case), when attempting to draw the wallpaper based on the info posted in Google's productforums by another user who had the same problem (xda won't let me post the URL since my account has too few posts).
I thought of sideloading a launcher from the recovery menu, considering that maybe it will be able to draw the wallpaper and the other stuff, but I don't know if that will work as I think.
Any ideas, please? Right now my Nexus is software bricked.
Click to expand...
Click to collapse
i had the same problem. i think it was a rogue setting in an app. all fixed now.
Go to settings>apps>system ui and clear the cache and restart the phone. It worked for me
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
fpga said:
After OTA update from LRX22C to LRY47I, device reboots with:
"Android is starting... Optimizing app xx of xx." (few minutes)
"Starting apps." (few seconds) "Unfortunately, System UI has stopped. Report/OK"
Whatever is pressed, pop-up just reappears.
Clearing cache from recovery restarts app optimization, but error persists.
Basically it's unusable but everything works in the background.
If e-mail arrives, notification sound is heard. Already set alarms work. Notification LED works.
Device is without any modifications, bootloader is locked and usb debugging isn't enabled.
Is there any way to access data?
Is sideloading customized kernel with usb debugging possible with locked bootloader?
Can application for wi-fi access be pushed via google play with preconfigured options and started automagically?
Anyone tried to rescue data after factory reset with dumping disk image and doing forensics?
Any other ideas are welcome.
Btw, there is a thread on Google's Nexus support group were users reported same issue:
(as a new user I can't post direct link here so search for "Android 5.1 is Here!" on google)
From one message it looks as if they are working on this but there was no official answer yet.
Click to expand...
Click to collapse
Go to settings>apps>system ui and clear the cache and restart the phone. It worked for me
Gekko2 said:
i had the same problem. i think it was a rogue setting in an app. all fixed now.
Click to expand...
Click to collapse
But what did you do? I can't do anything, it won't show the app drawer, it won't even let me enter the PIN for the sim card. Either I do stuff from recovery or nothing, and wiping the cache didn't solve it.
heatley said:
But what did you do? I can't do anything, it won't show the app drawer, it won't even let me enter the PIN for the sim card. Either I do stuff from recovery or nothing, and wiping the cache didn't solve it.
Click to expand...
Click to collapse
i was getting the same error loop and i was trapped in the loop with no way out.
here's what i did -
1. wiped cache partition, NO factory wipe - did this 2X - problem persisted.
2. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps and load all app settings backup files - problem persisted.
3. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps. this time i did not load my app settings backup files (Nova Launcher Prime, Fancy Widgets Unlocker, Calendar Status Pro, eWeather HD, Deliveries Package Tracker) on the hunch that perhaps there was an incompatible conflicting setting with 5.1 UI and one of the old app settings backups. AND i seemed to remember that the problem started as soon as i loaded the Calendar Status Pro backup settings file. i loaded all of the backup app settings files except for that one and had no problems. then i deleted that old backup file and started fresh with Calendar Status Pro and i've had no problems since.
so my guess is that you need to do a factory wipe and then reinstall all apps fresh. there may be an old setting from an old app that's conflicting with 5.1.
this is probably not what you wanted to hear but my fix required a hard reset and then starting fresh with the culprit app. yes it's a PIA and i spent most of the afternoon and my battery life fixing this problem.
let us know what you discover.
good luck!
I had the same problem: Seems that Calendar Status Pro is causing these issues.
This seems to be a huge problem with Nexus 5 and Nexus 6 users. You can see the complaints in Google's product forum.
Google Product Forums regarding the random reboots
On Android 5.1 I have been getting random reboots. There is no way to predict when it will happen. First time I was sending a message through line and phone went to a boot loop. I thought the power button was broken/stuck. Eventually it stopped boot looping and went through optimizing apps (I think i was holding down the power button). I thought I had a bad flash so i flashed the stock android 5.1 LRY47I through fastboot using the most recent usb drivers. Also wiped the device/set to default. Worked for a while and got Google Play and Gapps errors. Again I flashed the image through fastboot, reformatted/set to default settings in recovery. The third time I was getting gapps errors again so I reflashed/reformatted image through fastboot manually and not using the flash-all.bat. It seemed to work and put in all my settings again. Again I was looking at my phone, put it down, the screen was fading for sleep mode and then it boot looped and got it working and again went to optimizing apps. It booted then 2 minutes later it happened again when swiping apps away. Then a 3rd time. Clearing the Ui seemed to temporarily stop the boot loops. I am using a N5 unlocked, stock android. I thought it was a hardware problem until I saw a large number of users having the same issue on two different devices. Is there any way to create a system log to track down this problem? Thank you for suggesting the UI cache thing, but I am assuming it will boot loop/optimize apps again soon. This seems to be a huge problem for users. I hope this will be fixed soon.
chrisinsocalif said:
This seems to be a huge problem with Nexus 5 and Nexus 6 users. You can see the complaints in Google's product forum.
Google Product Forums regarding the random reboots
On Android 5.1 I have been getting random reboots. There is no way to predict when it will happen. First time I was sending a message through line and phone went to a boot loop. I thought the power button was broken/stuck. Eventually it stopped boot looping and went through optimizing apps (I think i was holding down the power button). I thought I had a bad flash so i flashed the stock android 5.1 LRY47I through fastboot using the most recent usb drivers. Also wiped the device/set to default. Worked for a while and got Google Play and Gapps errors. Again I flashed the image through fastboot, reformatted/set to default settings in recovery. The third time I was getting gapps errors again so I reflashed/reformatted image through fastboot manually and not using the flash-all.bat. It seemed to work and put in all my settings again. Again I was looking at my phone, put it down, the screen was fading for sleep mode and then it boot looped and got it working and again went to optimizing apps. It booted then 2 minutes later it happened again when swiping apps away. Then a 3rd time. Clearing the Ui seemed to temporarily stop the boot loops. I am using a N5 unlocked, stock android. I thought it was a hardware problem until I saw a large number of users having the same issue on two different devices. Is there any way to create a system log to track down this problem? Thank you for suggesting the UI cache thing, but I am assuming it will boot loop/optimize apps again soon. This seems to be a huge problem for users. I hope this will be fixed soon.
Click to expand...
Click to collapse
i bet many problems are the result of incompatible apps/settings. mine was. try a fresh device with no apps installed and see if you get the same errors. it's easy to blame Google/Android/Lollipop but i don't think you can blame them if you install a rogue/incompatible/conflicting app or setting. Developers are not perfect and they often do not update their apps. the OS is only as stable as what you load onto it.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
alephh said:
I had the same problem: Seems that Calendar Status Pro is causing these issues.
Click to expand...
Click to collapse
tell me more. did you load the app backup file? how did you fix? fresh app settings?
try a fresh device with no apps installed and see if you get the same errors.
Click to expand...
Click to collapse
I did, fresh install with wipe/default and when I typed in my email address and not restoring from saved profile got a Google Play Services and Gapps error before anything was installed. The flash was through fastboot. Plus the HUGE number of users getting the reboot/optimization problem in the Google forums affecting the Nexus 5 & Nexus 6, it's definitely the software.
Gekko2 said:
i was getting the same error loop and i was trapped in the loop with no way out.
here's what i did -
1. wiped cache partition, NO factory wipe - did this 2X - problem persisted.
2. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps and load all app settings backup files - problem persisted.
3. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps. this time i did not load my app settings backup files (Nova Launcher Prime, Fancy Widgets Unlocker, Calendar Status Pro, eWeather HD, Deliveries Package Tracker) on the hunch that perhaps there was an incompatible conflicting setting with 5.1 UI and one of the old app settings backups. AND i seemed to remember that the problem started as soon as i loaded the Calendar Status Pro backup settings file. i loaded all of the backup app settings files except for that one and had no problems. then i deleted that old backup file and started fresh with Calendar Status Pro and i've had no problems since.
so my guess is that you need to do a factory wipe and then reinstall all apps fresh. there may be an old setting from an old app that's conflicting with 5.1.
this is probably not what you wanted to hear but my fix required a hard reset and then starting fresh with the culprit app. yes it's a PIA and i spent most of the afternoon and my battery life fixing this problem.
let us know what you discover.
good luck!
Click to expand...
Click to collapse
Thanks for the post. I thought the same, that some app must be causing trouble due to some misconfiguration. I've tried booting in safe mode and the problem persists. I'll try a couple things via ADB and if not I'll give up, lose all my data and wipe to factory state.
Hi All,
I'm the developer of Calendar Status
I'm not sure yet if my app is the cause for the issue but Ill happy to assist with whatever I can.
I tried to look for LRY47I but couldn't find anything .. (I did find LMY471 but not LRY471, is it typo?)
Did anyone install fresh copy (Downloaded from Play Store) and get systemui crash ?
Does anyone who restored a backup file and got this crash still have the backup file ? (can be found under sd-card/calendarstatus/preferencesBackup.xml the other files aren't relevant)
In case it's relevant, I didn't/don't have Calendar Status installed in my device yet I suffer from the System UI error.
heatley said:
In case it's relevant, I didn't/don't have Calendar Status installed in my device yet I suffer from the System UI error.
Click to expand...
Click to collapse
Well
I know it isn't "Calendar Status bug", it is definitely an Android bug which is triggered by one of the configurations in Calendar Status (and in some other apps too)
---------- Post added at 06:32 PM ---------- Previous post was at 06:22 PM ----------
I suspect this to be due to 'transparent icon'.
Is anyone who experienced the crash can confirm he had an application (any application) with transparent icon ? (transparent isn't like 'no icon', it looks like an empty spot on the status bar)
I know from one of the backup files which were sent to me it is the case, and might be why the app crashed after restore (the default is white icon while the backup file has transparent icon selected)
SagiLo said:
Well
I know it isn't "Calendar Status bug", it is definitely an Android bug which is triggered by one of the configurations in Calendar Status (and in some other apps too)
---------- Post added at 06:32 PM ---------- Previous post was at 06:22 PM ----------
I suspect this to be due to 'transparent icon'.
Is anyone who experienced the crash can confirm he had an application (any application) with transparent icon ? (transparent isn't like 'no icon', it looks like an empty spot on the status bar)
I know from one of the backup files which were sent to me it is the case, and might be why the app crashed after restore (the default is white icon while the backup file has transparent icon selected)
Click to expand...
Click to collapse
i'm currently using transparent icon with no problems. my guess is problem is a specific font/size/number of events configuration is the culprit.
Gekko2 said:
i'm currently using transparent icon with no problems. my guess is problem is a specific font/size/number of events configuration is the culprit.
Click to expand...
Click to collapse
It was a long shot...
The log doesn't say much (thank you Google).
Ill try keep looking for the issue, if anyone have more info ill be happy to get it. (backup files / scenarios to reproduce / any thoughts..)
Bug was found (and submitted to Android issues)
https://code.google.com/p/android/issues/detail?id=163385&thanks=163385&ts=1428445417
What happened was a different notification (the one shown when no events available, like when setting the events interval to small value) was built in a specific way (as described in the bug).
The restore actually restored the interval value and this is why this bug happened after restore.
I believe there are more apps doing the same as I did (it should be fine), I hope the bug will help them to fix the issue (it is an easy workaround).
Thanks for the assistance guys.
SagiLo said:
Hi All,
I'm the developer of Calendar Status
I'm not sure yet if my app is the cause for the issue but Ill happy to assist with whatever I can.
I tried to look for LRY47I but couldn't find anything .. (I did find LMY471 but not LRY471, is it typo?)
Did anyone install fresh copy (Downloaded from Play Store) and get systemui crash ?
Does anyone who restored a backup file and got this crash still have the backup file ? (can be found under sd-card/calendarstatus/preferencesBackup.xml the other files aren't relevant)
Click to expand...
Click to collapse
It was a typo, should've been LMY47I.

TWRP Nandroid Backup fails (Huawei P9) –createTarFork() process ended with ERROR: 255

Hi guys,
whenever I try to backup my NAND using TWRP 3.0.2-0 on the Huawei P9 (Android 6.0 stock ROM, rooted), it fails for the DATA partition.
I know I have finished one backup successfully in the past by deleting the file that caused problems and retrying the backup.
However, now I again have problems, always with different files causing the problem according to the log (and I cannot simply delete all those problematic files! )
Does anyone of you know what's going on there and how to debug or even solve the problem?
The log output is always the same, except for the file causing the problem, which varies from time to time.
Code:
I:Error adding file '/data/hw_init/system/themes/Medal.hwt' to '/usbotg/TWRP/BACKUPS/MWS0216713001291/2017-04-17--19-31-21//data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbotg/TWRP/BACKUPS/MWS0216713001291/2017-04-17--19-31-21/data.info'
[COLOR="Red"]createTarFork() process ended with ERROR: 255[/COLOR]
Backup Failed. Cleaning Backup Folder.
Damn. Having the same problem, have you found a solution?
No, sorry. Still waiting for a solution.
In the meantime I created backups with Titanuim Backup and with Huawei Backup, in the hope that if I should ever need a backup, that these backups at least help to reduce the time a bit to set up the phone anew.
No, sorry. Still waiting for a solution.
In the meantime I created backups with Titanuim Backup and with Huawei Backup, in the hope that if I should ever need a backup, that these backups at least help to reduce the time a bit to set up the phone anew.
Hi Dude.. Just sharing ..
Device : Kenzo
OS : Nitrogen 8.0 (beta)
TWRP : 3.1.1 Official
The problem persist when i did restoring my back up :
createTarFork() process ended with ERROR=255
So.. It seems the problem happened when i make backup (even no error found) exactly in firmware partition backup.
I ve founded it by make 9 backup partitions (system, data, boot, recovery, cache, modem, firmware, BL and Efs) and do restoring one by one, and then the problem persist when I restored firmware partition
So I make this step when doing backup :
1. Open mount option and unchecked firmware partition.
2. Then I make full backup (9 partition)
3. The result is I got no error when restore it, and everything just fine now.
I don't even know the explanation, is there anyone can help explain it?, and is there any hidden problem with this way?
Seriously I Don't understand why but my backup and restoring running fine anyway now.. LOL
Just sharing my experiences, hope can help somebody here..
In the meantime it turns out that the phone's NAND seems to be faulty, which causes those errors.
I have two other P9 now for testing and reference, and on those the TWRP backup and restore runs flawlessly.
That faulty phone had other issues that I now understand also probably to be caused by faulty NAND. It seriously lagged very often. As soon as more than about 250-300MB of RAM was taken by apps, it wasn't operable for seconds anymore. It was always a bit laggy in the UI.
Now that I have the two other phones, I see how fast it can be. It feels like a totally new phone. (With the same software setup as the faulty one, just Android 7 instead of 6).
So apperently that phone really had a hardware issue.
Glad that I foud that out now. Makes me feel much better about trusting in the software and in my setup
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.

Phone stuck on "Phone is starting" screen

Hi everyone, I have a weird problem with my OnePlus 7 Pro. I made a mistake with an app that leaded me to edit some system files about screen resolution. Now the phone boots up, the main screen appears but I can't use any app. They result installed in the "all apps" menu, but I can't use any of them, neither the launcher or Google Apps, just the clock and the phone (that crashes immediately). How can I solve it? I'd like not to restore the phone, it's too long to backup and then restore all the data. Please, help :crying:
Bernard_99 said:
Hi everyone, I have a weird problem with my OnePlus 7 Pro. I made a mistake with an app that leaded me to edit some system files about screen resolution. Now the phone boots up, the main screen appears but I can't use any app. They result installed in the "all apps" menu, but I can't use any of them, neither the launcher or Google Apps, just the clock and the phone (that crashes immediately). How can I solve it? I'd like not to restore the phone, it's too long to backup and then restore all the data. Please, help :crying:
Click to expand...
Click to collapse
Which version of the OS and what files did you change?
So you must be rooted, if you are messing with system files?
Cardinal rule with these devices (especially while doing root mods, etc.) is don't do anything, that you don't know how to reverse or recover from.
You should be able to flash the OTA file to the inactive slot, flash TWRP (installer zip) and install Magisk to inactive slot. Keeping data, and just keep motoring on!

7 Pro stuck in boot after removing Magisk

I've been having a bunch of problems recently with my rooted 7 Pro including Magisk Manager constantly "keeps stopping", not being able to access Hide to add new applications, banking apps starting to detect that I'm rooted and camera issues: the camera app not starting, the camera not popping up automatically and the image being usually reversed and occasionally upside down as well, depending on the app I'm using.
Given that Magisk appears to be dead/dying, having lost its developer to Google, I thought I'd start by getting rid of that and then performing a firmware upgrade in necessary to see if that fixes the other issues.
I uninstalled the Manager then ran the uninstall zip within TWRP. Rebooting though hangs on the initial "ASUS" screen.
I can get back to TWRP ok so I guess I'm not bricked yet. My next thought was to try a system upgrade but I seem to need to know the exact version I need, which, seemingly, I can only get via a working phone?
From the back, it says only model I002D along with SN and IMEIs.
I've done a TWRP backup to the external uSD card, and I have a syncthing copy of all of the internal memory that I can access without root.
My questions:
1. Is there something there which can help my figure out which firmware I need to download?
2. Is there any way to install this without wiping the phone?
Please see this post.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com

Categories

Resources