Related
Hi,
I have jsute bought a I9000 (called Galaxy S in France) and I was quiet happy before I change the gmail configuration.
I have configure it to synchronize all my email and my device became unusable (error message every 5 second saying that applications XXX was unable to run).
I think this is because the internal memory of the phone was full.
I success (this take me nearly 1 hours) to clear gmail cache and the phone is working back correctly.
However I would like to make a full system clean in order to start with a fresh system but when I go to Privacy and choose Factiry reset, I get the message "no factory reset was performed because the system clear service is not available".
Does someone know why I get this error and how to fix that?
I plan to fkash the mobile and (first) get the recovery mode has it is not available on my device but I would like to have a fresh system first.
Thanks a lot for your help!!
minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)
This is great. Will give this a shot today or tomorrow. Thanks!
themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.
I still get notification prompts for ota.
themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way
Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much
Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...
ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.
Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.
Hello,
i did not find MI-Assistant, where exctely?
Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????
ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?
It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .
Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh:
Hi everyone,
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
NahteT said:
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
Click to expand...
Click to collapse
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
KOLIOSIS said:
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
Click to expand...
Click to collapse
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
NahteT said:
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
Click to expand...
Click to collapse
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
KOLIOSIS said:
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
Click to expand...
Click to collapse
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
NahteT said:
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
Click to expand...
Click to collapse
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
KOLIOSIS said:
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
Click to expand...
Click to collapse
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
NahteT said:
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
Click to expand...
Click to collapse
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
KOLIOSIS said:
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
Click to expand...
Click to collapse
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
NahteT said:
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
Click to expand...
Click to collapse
That would be my guess, otherwise, you should be able to update.
KOLIOSIS said:
That would be my guess, otherwise, you should be able to update.
Click to expand...
Click to collapse
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
NahteT said:
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
Click to expand...
Click to collapse
Please keep us posted on your outcome.
KOLIOSIS said:
Please keep us posted on your outcome.
Click to expand...
Click to collapse
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
NahteT said:
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
Click to expand...
Click to collapse
No problem, glad to be of help.
As for the ADB Removal & re-install of apps, I 1st heard about it from this XDA article/how-to:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
As it mentions the inability to re-install/re-enable apks, I just took their word for it & never uninstalled anything that I might need at some point.
That's why I like using package disablers, it's easily reversible without a reset.
Regardless, a factory reset isn't the end of the world, just a PITA at most.
Glad you got things going again.
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
NahteT said:
Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware..
Click to expand...
Click to collapse
Glad the problem was solved. My view is that concern with bloatware is a vestige of the past. On present-day phones, I'd guess that less than 0.1% of storage, memory, processor time, or battery charge are tied up with bloatware apps. So trying to identify and disable them won't have any noticeable benefit, and may well break things.
NahteT said:
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
Click to expand...
Click to collapse
The message is just a generic one (as used when you grant admin rights for work e-mail,for example).
What it comes down to is if you trust the package disabler app & its developer,as I don't think there is any way to revoke the permission as long as you are using it to disable any apps at all.
I may be wrong on that,but,it seems like that's what's going on here.
If this still bothers you,then the next best solution is to continue using the disabling app long enough to determine which apps you are 100% certain are not needed/wanted.
Make a list & then switch to the ADB method.
That way,you get the admin rights to the disabler app off of your phone,but,you do give up the flexibility of the app as well.
The only way I see around your predicament is gaining root access & using the disabler app w/o admin rights,or,another app such as SD Maid Pro or Titanium Backup Pro.