Database Develop

ARHD 10.1 to 10.2

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.

[SOLVED] Calendar Storage crashes on SlimBean-4.2.2

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.

[app, root] IMEI Backup ★Samsung★ - for ALL Samsung devices

A complete IMEI Backup and Restore solution for Samsung devices.
This app should work with almost ALL Samsung devices.
Prerequisite: SAMSUNG device + ROOT permission.
Make sure you own a SAMSUNG device and your device has been ROOTED before purchase.
DESCRIPTION:
This app will make a full backup for the EFS partition and all other IMEI-related partitions, e.g. MODEMST, MODEMST1, MODEMST2, M9KEFS, M9KEFS1, M9KEFS2, M9KEFS3... (these partitions will vary from device to device)
It will perform cross-checks to make sure a good backup was made and ensure the backup is suitable for your device before restoring.
DURING BACKING UP PROCESS:
- Auto detect which partitions to back up
- Check if all needed partitions have been backed up
- Check if all partitions are backed up correctly by comparing the file size to the partition size
- Generate and save MD5 checksum for backup files
- Save all the system properties for restoring purpose, e.g. phone model, product name, OS version, partition structure, partition size...
DURING RESTORING PROCESS:
- Compare saved properties with the current system properties: phone model, product name, OS version...
- Compare partition structure and partition size to ensure that the backup is suitable for your device
- Compare the MD5 checksum for the backup files
The good item will be marked with [✔] and the bad/mismatched item will be marked with [✘].
DOWNLOAD LINK on Play Store: https://play.google.com/store/apps/details?id=org.vndnguyen.imeibackup
NOTE: If you are using Android 4.4 (KitKat) and you cannot backup to the External SD card, you can use SDFix app to fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

HOW TO BACK UP:
• From the main screen, tap Backup button to make a backup.
• You will be asked for backup location, if more than one storage location on your device.
• You can enter a short description for the backup.
• The app will automatically detect all partitions need to back up.
• After backup it will compare the file size and generate the MD5 checksum.
• It also save important system properties.
• The backup files will be saved in the folder in the following format: IMEI_Backup_yyMMddHHmmss
HOW TO RESTORE:
• Select the desired backup in the list.
• It will show you all information: Details, Properties, Backup Files and Status.
• Details: Backup location, size, date created and description.
• Properties: Manufacturer, Model, Product name, OS version, partition structure and partition size.
• Backup Files: shows all backup files and their status. It will show the file size if the file is in good condition. Otherwise it will show 'file not found' or 'bad checksum' etc.
• Status: Overall status of the backup. 'Unsuitable' means some properties do not match with the current device, but you still can use it to restore. 'Unusable' means you cannot restore this backup. This happens when the partition structure or partition size mismatched, file not found or bad MD5 checksum.
• Tap Restore button to restore. You must type 'Yes, Restore!' to confirm.
• Reboot your device after complete restoring.
WARNING: Only restore when you really need it. Do not play around with this tool. Use at your own risk.

Unlike other IMEI Backup apps that typically support only one specific model, this app supports almost ALL Samsung devices.

Tips: You can add the description to differentiate the backup from another.

Hi dev can this app restore my phone completely and remove my yellow triangle error that was caused by trying flash custom Rom let me know your thoughts thx.
Click to expand...
Click to collapse
Unfortunately I can not say for sure that this app can restore your phone completely, as I don't know what is your actual problem.
In the most cases, this app can restore your IMEI by backing up and restore the EFS and ALL IMEI-Related Partitions.
If you made a backup before flashing any ROM, you can restore your IMEI if any problem happens.

I just got the app, love it. But there is one thing that really bugs me. There is no way to change the default save location. It can go on either sdcard0 or sdcard1.
Each backup creates a separate folder on the sdcard. It would be nice if it could backup into a folder at say sdcard1/IMEI Backup. That way it is all consolidated to one folder location.
Click to expand...
Click to collapse
Thank you, this should be a nice suggestion.
I might add this capability in the future release.

Hello, first of all I want to thank you about this really great app, good job developers!
My question is if this app works with Samsung Galaxy S3 mini (GT-i8190/L/N), and if doesn’t work until now, will be possible to work in the future updates?
Many thanks!
Click to expand...
Click to collapse
Regarding Galaxy S3 mini, I didn't test on this phone, but I believe it should work with this phone.
From the user's feedback, I know that it works fine on S3 and S4 devices. And it should work with almost ALL Samsung devices, as I have stated in the app's description.
Best regards,

OK but... Tried the backup and restore. Worked perfectly. But then I needed to use it for real : the dreaded efs loss! And it didn't work. Why? License verification issue. It seems to me the app use some unique id data that resides, wait for it, in the efs partition! Kind of a catch 22. Good thing I also had a utility on my PC for efs backup.
Click to expand...
Click to collapse
Hello, sorry to hear about the problem.
Can you clarify some details:
- "OK but... Tried the backup and restore. Worked perfectly": that means it worked before? for both backup and restore?
- "License verification issue.... Kind of a catch 22": did you face with "license check error"? If so, try to uninstall and then reinstall the app from the Play Store. Or another error?

On Android 4.4.2 there is a problem with writable ability on the External SDcard.
To avoid the problem, please select sdcard as a backup location, do not select ExtSdCard. Sorry about that, I will find a way to fix it.

Update v1.2.9:
Add support for all Note 4 variants: SM-N910A, SM-N910C, SM-N910F, SM-N910FD, SM-N910FQ, SM-N910G, SM-N910H, SM-N910K, SM-N910L, SM-N910P, SM-N910R, SM-N910S, SM-N910T, SM-N910U, SM-N910V, SM-N910W8...

If you are using Android 4.4 (KitKat) and you cannot backup to the External SD card, you can use SDFix app to fix.

Hi,
If I made a backup file from my official note 4 firmware, Is the knox counter go up when I restore ?
Click to expand...
Click to collapse
Hi,
Good question. I have not faced with this question before, but I try to answer.
AFAIK, Knox counter only trip if you root the phone, or if a custom recovery or custom kernel are being installed.
Flashing the backup EFS partitions will not trip the Knox counter.
Hope that answers your question.

Made me feel safer . totally worth a shot

Glad you find it useful.

Please note that on newer Samsung devices, the IMEI is not stored in the EFS partition.
This app mades a backup for not only EFS partition but all other IMEI-related partitions.
If you backup only EFS, your IMEI will not be restored later.

<deleted>

I have Samsung Galaxy J (SC-02F) Japan.
Your application work with my device ?

Thank you!

duc2ht said:
I have Samsung Galaxy J (SC-02F) Japan.
Your application work with my device ?
Click to expand...
Click to collapse
Yes, it will work with ALL Samsung devices.
(except for some older models).

<deleted due to duplicated>

OTA update for GPE 5.1 LMY47O.H9 to H10 -- TWRP

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?!

[HELP] Storage is full on Google Play but system has access to app-lib

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