[SOLVED] Calendar Storage crashes on SlimBean-4.2.2 - Galaxy S I9000 Q&A, Help & Troubleshooting

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.

Related

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.

[RECOVERY] Cyanogen recovery for Nexus 5

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!

I think I messed up my fire tablet 7(5th gen)

I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
{
"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"
}
This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/
berttheturt said:
I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
Click to expand...
Click to collapse
berttheturt said:
This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/
Click to expand...
Click to collapse
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.
Thanks so much, that worked perfectly
Davey126 said:
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.
Click to expand...
Click to collapse

[Guide] PROJECT TREBLE for ZOOM

{
"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"
}
So, we have a fully functional TWRP. Now we can install custom firmware. I've been trying to get a working system on the Project Treble firmware for a long time, and found the right a working GSI images!
The firmware was taken as an example for installation Havoc-OS 3.5
Prerequisites - bootloader must be unlocked, clean Stock firmware must be installed.
Installation Instruction
1. Download the Project Treble system image archive without included GAPPs (Vanilla, ARM64-AB). Otherwise the system will not start. Unpack the archive and copy the ROM image to an external SDCard.
Download and copy to external SD Card GAPPs archive (ARM64, Android 10), Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4) and Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ), Permissiver_v4 (look at the attached files);
2. Install TWRP according to the Instruction, doing everything up to the 6th step.
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Project Treble system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. Installing GAPPs. If you try to install the GAPPs archive immediately, the installation will be aborted with an error: 70 (Error 70). This will be eliminated as follows:
- Go to the "Wipe" tab;
- Then select "Advanced Wipe";
- In the menu that opens, select the System partition and click "Repair or change file system";
- A few buttons will appear and click "Resize File System". If the process failed the first time with Error 1, then repeat this action again.
Now you can install the GAPPs archive without any errors.
6. When the installation is complete, go to Wipe and perform a "Swipe Factory reset".
7. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, do not worry.
Important additions
Adaptive brightness - Copy framework-res__auto_generated_rro.apk to /vendor/overlay. Give this application permission 644. Remove the "FrameworkResVendor" folder from /vendor/overlay. Reboot the phone. In "Phone Settings" you will have a new item "Adaptive brightness" and this feature will work in "Quick Settings".
Noticed problems on Havoc-OS 3.5:
- Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated.
- Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
- Unlocking by fingerprint is implemented for scanners on the back of the phone.
Automatic brightness setting does not work - Fixed!
Found working Project Treble firmware:
Havoc-OS-v3.5 https://sourceforge.net/projects/ha...fficial-arm64-ab-vanilla-nosu.img.xz/download
AOSP 10.0 v216 https://github.com/phhusson/treble_...oad/v216/system-quack-arm64-ab-vanilla.img.xz
Firmware installation instructions will be available later.
It's truely impressive what you are doing!
Wooooooow! Finally!
Awesome work!!!
Can you confirm if the fingerprint scanner works with any of the roms?
Or if there is something missing?
Also whichone would you recommend over stock?
Thanks!!!
One zoom
Can we install this project in our one zoom?
spcarlos2 said:
Can we install this project in our one zoom?
Click to expand...
Click to collapse
I don't understand the question
ilia3367 said:
I don't understand the question
Click to expand...
Click to collapse
can i install this rom on my one zoom cell phone?
spcarlos2 said:
can i install this rom on my one zoom cell phone?
Click to expand...
Click to collapse
Buddy! And for which phone is this theme created? Isn't it for Moto One Zoom? :laugh:
After the flashes I get this:
Failed to mount '/system's (Invalid argument)
After I unpack the image zip, I rename to .img, maybe that's why, help me please...
After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...
thirdphotographer said:
After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...
Click to expand...
Click to collapse
Install again Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip.
I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?
Afifus said:
I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=968480&view=findpost&p=96932663
Try to read with a translator.

[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

Categories

Resources