I just flashed ARHD 10.2 onto my phone after flashing 10.1 about 2 weeks ago. When I rebooted my phone, it said my system UID's were inconsistent and it sugested I wipe my phone. I am fairly new to this so I have no idea what to do.
Please help. Thanks!
xeron72548 said:
I just flashed ARHD 10.2 onto my phone after flashing 10.1 about 2 weeks ago. When I rebooted my phone, it said my system UID's were inconsistent and it sugested I wipe my phone. I am fairly new to this so I have no idea what to do.
Please help. Thanks!
Click to expand...
Click to collapse
Wipe /data. These are the struggles of dirty flashing oh and just wipe /cache and /dalvik (all together same as factory reset)
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 06:31 PM ---------- Previous post was at 06:18 PM ----------
{
"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"
}
xeron72548 said:
I just flashed ARHD 10.2 onto my phone after flashing 10.1 about 2 weeks ago. When I rebooted my phone, it said my system UID's were inconsistent and it sugested I wipe my phone. I am fairly new to this so I have no idea what to do.
Please help. Thanks!
Click to expand...
Click to collapse
Yes it is a consequence of dirty flashing.
You can do (in the following order)
1) Try fixing permissions from recovery
2) wipe dalvik and cache
3) do a full wipe (factory reset)
Each time do one thing, reboot and see if your system works.
Something I just learned a few days ago on the Renovate thread is there is a file in /data/system that keeps track of the UID errors. If you check /data/system/uiderrors.txt and check the errors from the date of flash and clear data for those apps you can clear the error. I like shortcuts and this will work fine. If you do it this way, you can find what is causing the error. It gives the package name and not the apk name so it may not be 100% obvious which app at first.
tiny4579 said:
Something I just learned a few days ago on the Renovate thread is there is a file in /data/system that keeps track of the UID errors. If you check /data/system/uiderrors.txt and check the errors from the date of flash and clear data for those apps you can clear the error. I like shortcuts and this will work fine. If you do it this way, you can find what is causing the error. It gives the package name and not the apk name so it may not be 100% obvious which app at first.
Click to expand...
Click to collapse
I cannot seem to find this
stmilosh said:
Yes it is a consequence of dirty flashing.
You can do (in the following order)
1) Try fixing permissions from recovery
2) wipe dalvik and cache
3) do a full wipe (factory reset)
Each time do one thing, reboot and see if your system works.
Click to expand...
Click to collapse
This worked for me
xeron72548 said:
I cannot seem to find this
Click to expand...
Click to collapse
You need a file browser with root to see /data. /data/system/uiderrors.txt should be present even after a clean install as it reports any UID related errors or cleanup. The issue with UI I saw on renovate earlier was with the way the system handled the Quadrant high I/O score benchmark hack. That just caused issues on that ROM but it has been fixed since then in later 4.2.2 renovate builds.
tiny4579 said:
You need a file browser with root to see /data. /data/system/uiderrors.txt should be present even after a clean install as it reports any UID related errors or cleanup. The issue with UI I saw on renovate earlier was with the way the system handled the Quadrant high I/O score benchmark hack. That just caused issues on that ROM but it has been fixed since then in later 4.2.2 renovate builds.
Click to expand...
Click to collapse
I used Astro file manager and I have root. I got to the system folder but could not see the log
After much trial and error, I finally found a solution. I wiped everything and then installed 10.2. After I made sure that worked, I restored the data only from my nandroid.
Thanks for everyone's help!
defert retedmt
tiny4579 said:
You need a file browser with root to see /data. /data/system/uiderrors.txt should be present even after a clean install as it reports any UID related errors or cleanup. The issue with UI I saw on renovate earlier was with the way the system handled the Quadrant high I/O score benchmark hack. That just caused issues on that ROM but it has been fixed since then in later 4.2.2 renovate builds.
Click to expand...
Click to collapse
Mike didn't fix it in ARHD instead it is always recommended to remove completely quadrant before dirty flashing since it brakes things.
Related
So, I've noticed after doing a factory data reset in TWRP (wipes data and caches), and installing Titanium Backup with the in app generated flashable zip; when I start TiB the first time I get a notice that my Android device ID has changed. TiB will offer me the choice to ignore this or restore the old ID. If I restore the ID, then restore system data, it breaks all sorts of things: Play Store, soft home button, quick settings buttons, wi-fi. If I ignore it no problems at all.
I guess the fix is just ignore device ID change.
Anyone else seeing this?
From which device & o/s version does the TB data come from?
It's normally recommended not to restore.system data only applications and associated data if from different Android versions
Sywepd form my DsereiS
ben_pyett said:
From which device & o/s version does the TB data come from?
It's normally recommended not to restore.system data only applications and associated data if from different Android versions
Sywepd form my DsereiS
Click to expand...
Click to collapse
From stock OTA Nexus 4 to Jellytime-AOSP+ built on 4.2
So, here, I made a TWRP backup of system and boot. Did a full wipe (factory data reset and /system) restored my backup, flashed TiB from the zip made in app, on the build I'd just backed up. Booted up, opened TiB, granted root rights, and this popped up.
{
"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 select restore and then it reboots. After I open TiB again and restore all system data, show below, and Wi-Fi Access Points is unseen. Reboot.
Now, when I try to download anything from the market I get this error. Did not bork soft buttons this time.
However, if I do all this again, and tell it to ignore the change, no issues.
USSENTERNCC1701E said:
So, here, I made a TWRP backup of system and boot. Did a full wipe (factory data reset and /system) restored my backup, flashed TiB from the zip made in app, on the build I'd just backed up. Booted up, opened TiB, granted root rights, and this popped up.
I select restore and then it reboots. After I open TiB again and restore all system data, show below, and Wi-Fi Access Points is unseen. Reboot.
Now, when I try to download anything from the market I get this error. Did not bork soft buttons this time.
However, if I do all this again, and tell it to ignore the change, no issues.
Click to expand...
Click to collapse
Do not touch system app, may be next time, it will screw your phone
nguyen47 said:
Do not touch system app, may be next time, it will screw your phone
Click to expand...
Click to collapse
As long as you are on the same device and the same build of android there are usually no issues from migrating system app data, I've been doing it for years.
I'm just trying to let people know, if you get this notice in TiB, select ignore to prevent errors.
If you restore from the same ROM all is working, tested myself yesterday. I just click on restore Id.
Sent from my GT-I9100 using Tapatalk 2
What if you wipe the app data for the play store?
Sent from my Nexus 7 using xda premium
So if I have no intention of restoring system app data, it's fine if I restored the ID?
But what other stuff will happen if I ignored? Would there be any potential problems elsewhere?
mlj11 said:
So if I have no intention of restoring system app data, it's fine if I restored the ID?
But what other stuff will happen if I ignored? Would there be any potential problems elsewhere?
Click to expand...
Click to collapse
nope. im always flashing new roms and use TiBu and yea i get that every time i start fresh. like what has been said, dont restore system data, just restore user data. and yea you can restore your ID from a previous rom without problems
Use this app:
http://forum.xda-developers.com/showthread.php?t=2109484
Sent from my Nexus 4 using xda app-developers app
USSENTERNCC1701E said:
As long as you are on the same device and the same build of android there are usually no issues from migrating system app data, I've been doing it for years.
I'm just trying to let people know, if you get this notice in TiB, select ignore to prevent errors.
Click to expand...
Click to collapse
BIG question here. I first install an app of a smart cover wich has a unique serial number i backed it up with titanium. after i change the rom wich is a ported rom of a different model i cannot get the data of the app do you have any idean on how to get it back?
I'm wondering if that was my problem
I did a factory reset and chose to reclaim my old ID nothing else now SVOX Victoria UK English won't load my data package
Greetings!
I flashed SlimBean-4.2.2 (tried both build 1.1 and build 3) and the calendar storage keeps force closing all the time (from the moment the phone boots). This happened even if I didn't install gapps (I know I must install them immediately, but I tried not installing them once - made no difference) and before I setup any google account. Needless to say I tried cleaning data, cache, reflashing numerous times. I tried installing the AIO Aroma addon (that includes gapps and all the rest) both build 8 and build 6. I tried replacing Calendar Storage with my ICS backup. I tried replacing it with another CalendarProvider.apk. NONE if this worked....
Edit: Forgot to mention that every time I flash AIO Aroma addon it exits with:
AROMA installer finished
Error in /sdcard/AIO_Aroma.4.2.2.zip
Status 0
Installation aborted
But when I boot into SlimBean it runs all of the app optimization as if they have been reinstalled.... (this happened with both build 6 and 8). However, calendar storage comes with the actual ROM, not the addons and as I mentioned it kept force closing even before I installed any addon. Could this error have to do with the fact that after I flashed SlimBean (that came with Semaphore 2.9.8) I flashed Semaphore 3.0.0?
AaylaSecura said:
Greetings!
I flashed SlimBean-4.2.2 (tried both build 1.1 and build 3) and the calendar storage keeps force closing all the time (from the moment the phone boots). This happened even if I didn't install gapps (I know I must install them immediately, but I tried not installing them once - made no difference) and before I setup any google account. Needless to say I tried cleaning data, cache, reflashing numerous times. I tried installing the AIO Aroma addon (that includes gapps and all the rest) both build 8 and build 6. I tried replacing Calendar Storage with my ICS backup. I tried replacing it with another CalendarProvider.apk. NONE if this worked....
Edit: Forgot to mention that every time I flash AIO Aroma addon it exits with:
AROMA installer finished
Error in /sdcard/AIO_Aroma.4.2.2.zip
Status 0
Installation aborted
But when I boot into SlimBean it runs all of the app optimization as if they have been reinstalled.... (this happened with both build 6 and 8). However, calendar storage comes with the actual ROM, not the addons and as I mentioned it kept force closing even before I installed any addon. Could this error have to do with the fact that after I flashed SlimBean (that came with Semaphore 2.9.8) I flashed Semaphore 3.0.0?
Click to expand...
Click to collapse
I am having the same problem ... any ideas?
MrCabana said:
I am having the same problem ... any ideas?
Click to expand...
Click to collapse
[26] Problem:- ClockworkMod Recovery giving Status 0 error "Installation aborted".
Solution:- Most likely you have a incompatible CWM, or your Zip files are corrupted or you have mounted /system or /data
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
No.
Problem: Google Calendar crashing all the time with this ROM.
MrCabana said:
No.
Problem: Google Calendar crashing all the time with this ROM.
Click to expand...
Click to collapse
its due to bug on Aroma version 7, read this
xsenman said:
its due to bug on Aroma version 7, read this
Click to expand...
Click to collapse
Indeed I think it was a bug - I downloaded Aroma v6, did another factory reset, this time I formatted /system (which I should have done, but I had forgotten) and it started working properly. Sorry, I forgot to post in the topic how I solved it.
EDIT: Post removed since there's an official download now!
Just open download.cyanogenmod.org, choose your device and download the latest recovery
Much fun! Thanks CyanogenMod!
How to get back the automatic recovery update!
I activated 'Update Cyanogen update' but it doesn't work?!
Okay, so you activated the option + flashed a new build and Cyanogen recovery is still not there? Here's what's the cause and how to fix it:
Some third-party recovery systems (e.g. TWRP) prevent to be overwritten by deactivating the automatic recovery update function. This happens by renaming the file /system/recovery-from-boot.p into recovery-from-boot.bak.
To get that functionality back:
- Rename /system/recovery-from-boot.bak back to recovery-from-boot.p
- Execute /system/bin/install-recovery.sh to actually install Cyanogen recovery.
Both steps can be done with CM file manager. You have to give the app root access!
After performing the steps above you can use 'Update Cyanogen recovery' for the future builds to keep your recovery up to date.
You can use this method if you don't want to download/use the img file above or don't want to regularly update the recovery manually.
Questions:
If you have any questions don't hesitate to ask in this thread! I'm not a developer but I'll try my best to help you out
Note to users: I'm not responsible if you brick your phone.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Reserved
Seems like you're not having trouble with CM recovery. I've tried this before using the 2nd method of renaming and executing. I might go back to CM recovery in a while. I notice the latest TWRP 2.8.5.2 is not really clearing the data partitions of my device. Already gave you a +1 on the CM thread, but I will still give you one for this thread! Nice job!.
Yeah.. it's working fine for me
Thanks for the first comment on this thread! Really appreciate it
Just want to clear this one, does "Wipe data/factory reset" includes internal storage?
No, it doesn't Or at least shouldn't It didn't format internal storage on CWM and TWRP and the same should apply for CM recovery Would be freaking thankful if you could try that (of course backup ur internal storage before if you want to try)
experience7 said:
No, it doesn't Or at least shouldn't It didn't format internal storage on CWM and TWRP and the same should apply for CM recovery Would be freaking thankful if you could try that (of course backup ur internal storage before if you want to try)
Click to expand...
Click to collapse
Okay, I will. I'll report back soon.
@Moderators:
{
"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 just wanted to pop into this thread and say that I installed cyanogen recovery (homebrewed)- it seems fine- gestures work well. There is no option to wipe system, but hey, dirty flashing is the in thing nowadays. Life is too short to wipe data and and then restore it from backup.
I did install PA gapps with cyanogen recovery - the PA script and the recovery graphics fight each other, but it's not like I have to look at it all the time. There is a lot of scrreen flashing between the script output and the little android dude. If you blink your eyes fast enough, you can see just one or the other.
Yeah, i also found out that CM recovery tries to 'hide' what's going on so that you can only see the green Andy Looks weird with PA GApps but works fine with official CM nightly builds
Am I able to update official nightlies with cyanogen recovery?
is the touch screen swipe based or touch based?
Did you even read the OP?
I removed my Google Drive link with the image files since there's an official download now!
hammerhead-recovery: http://download.cyanogenmod.org/?device=hammerhead
hammerheadcaf-recovery: http://download.cyanogenmod.org/?device=hammerheadcaf
Have fun!
Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available. It only works for clean H9 installs that are NOT rooted.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
{
"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"
}
http://forum.xda-developers.com/showthread.php?t=2708589
Sent from my HTC6535LVW using Tapatalk
Getting an Error Executing updater binary in zip, error.
/system/bin/app_process32 has unexpected contents
/system/app/BasicDreams/BasicDreams.apk has unexpected contents
Please advise!
UPD1 Sorry, it was Philz recovery. Now I got TWRP and getting the same issue with app_process32
UPD2. It seems I have to unxpose and unroot first - but my M8 keeps rooting itself, cannot get into unrooted mode.
radeon_x said:
Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
Click to expand...
Click to collapse
Thanks for the update, but it didn't work and causes an error like the post before this.
Unexpected error .... etc.
I got the same errors trying to sideload the original OTA zip through stock recovery, so it must be something in the zip itself.
Maybe a security measure to prevent installing on modded phones.
Would it be possible to post the entire H10 ROM .zip? I usually have problems updating just the OTA file. graffixnyc usually posted it but for some reason that thread got closed.
Thanks!
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
sudaltsov said:
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
Click to expand...
Click to collapse
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
If you received the OTA notification for H10
Well, I have tried it twice (from H6 I believe to H9 and now from H9 to H10) and it worked and I did not loose any data files! I got the OTA notification and followed the following protocol (I am rooted and running TWRP):
1. Revert any app that had root access (i.e. Adblock... just revert and disable). If you have XPOSED framework you have to revert everything to stock!
2. Withing the SuperUser app (SU), fully "un-root" the phone.
3. Restart (probably not necessary)
4. Install H9 Recovery (I downloaded it from graffixnyc: http://forum.xda-developers.com/showthread.php?t=2708589) Do not forget to at least thank him!
5. Erase cache (Fastboot erase cache) just in case and Restart.
6. Install OTA :good:
7. Done! Now you have to install again TWRP via fastboot (erase cache once again, just in case...) for root access and re-install whatever you had before with root access. :laugh:
Long process but saves me a lot of headaches with data and any other errors may occur...
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
sudaltsov said:
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
Click to expand...
Click to collapse
Well the initial boot after clearing the cache takes a really long time of course.... But if it really and truly doesn't boot after several minutes just install the full H10 from that other thread.
Seems I have no choice but to sideload (thanks to TWRP) the full OTA H10..
radeon_x said:
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
Click to expand...
Click to collapse
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
m_atze said:
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
Click to expand...
Click to collapse
Thanks, it's work for me.
btw the original thread is here http://forum.xda-developers.com/showthread.php?t=2706441
After multiple issues I just installed the H9 RUU unrooted from @graffxnyc, then installed the ota which popped up as soon as it rebooted.
For now I'm leaving it unrooted etc until marshmallow drops later this month.
Don't know whats the update for tho. But anyways installed. Maybe to prepare our system for Marshmallow update? Like what cyanogen did?
i'm not sure what's going on, but the update is a POS. Like sure it's a stagefright fix, but they've broken more than fixed it. Im having massive lag issues, the text windows are stuttering at times, unlocking the phone freezes it for a while and there are times where the notification sounds don't even sound off.
Sorry guys. I've had no problems at all.
This Version is woking like charm.
H10 update recovery
Could someone provide the recovery image from the H10 update?!
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
{
"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"
}
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Possible solution
Jandresgomez said:
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Click to expand...
Click to collapse
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
XiaomiFixer69 said:
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
Click to expand...
Click to collapse
Stupid solution [emoji1787]
Enviado do meu ASUS_I001DC através do Tapatalk