Question After magisk root & ro2rw fix i get a crazy serviceprovider-update nag screen. Any idea how to fix that one? - Samsung Galaxy S23 Ultra

Hi Together,
I think something went wrong, but i cant say what.
After using magisk to root (like very often before) and a confirmation that everything should be fine i had to use the ro2rw fix to get rw access. I didnt know that one but got help & a lot of cool info to solve that rw topic. I used the tutorial here: https://forum.xda-developers.com/t/how-to-root-23-and-have-full-access-to-system-partitions.4585399/
Shortly after that i get now a crazy serviceprovider-update nag screen. Crazy because it tells that something has to be updated and i have to reboot. And if i click the reboot link it just starts a notification that it cant be updated.
My phone service is fine i can call my landline without any problem. But the blocking everything nag screen still appears. So as a rooted user with android expierence since android 1 i choose my SD Maid App to find the apk that is causing this notification. And after i ended com.samsung.android.cidmanager (2.0.23) the notification on the the top disappeared. But after a reboot the One Ui updated something and there was it back again. And it was running even any autostart reason was disabled. I checked it with 2 apps. There was no autostart that i could remove. And after my next reboot it is running again.
The message in the pic translated from german tells:
"Serviceprovider-Update
Your phone have to be restarted, to setup functions and services of your provider.
. Apps and Layouts might change, after your phone was updated."
Emergency Call
Reboot"
{
"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 comes back again and again after 5-60 Min. If i force stop com.samsung.android.cidmanager (2.0.23)
its gone. Removing all "Receiver Manager"/ Autostart also doesnt work. I guess another app calls that service. But i dont know which one.
The notification just tells:
"Serviceprovider-Update
Serviceproviderfunctions could not be setup."
Any idea other than just wipe data/cache and reinstall?
===Edit===
OK a complete new flash and new root was fine until i used the ro2rw script again.
Same Error as before. I guess there is one Service that is causing that nag screen.
Thanks a lot for reading.
Greetings
4summer

4summer said:
Hi Together,
I think something went wrong, but i cant say what.
After using magisk to root (like very often before) and a confirmation that everything should be fine i had to use the ro2rw fix to get rw access. I didnt know that one but got help & a lot of cool info to solve that rw topic. I used the tutorial here: https://forum.xda-developers.com/t/how-to-root-23-and-have-full-access-to-system-partitions.4585399/
Shortly after that i get now a crazy serviceprovider-update nag screen. Crazy because it tells that something has to be updated and i have to reboot. And if i click the reboot link it just starts a notification that it cant be updated.
My phone service is fine i can call my landline without any problem. But the blocking everything nag screen still appears. So as a rooted user with android expierence since android 1 i choose my SD Maid App to find the apk that is causing this notification. And after i ended com.samsung.android.cidmanager (2.0.23) the notification on the the top disappeared. But after a reboot the One Ui updated something and there was it back again. And it was running even any autostart reason was disabled. I checked it with 2 apps. There was no autostart that i could remove. And after my next reboot it is running again.
The message in the pic translated from german tells:
"Serviceprovider-Update
Your phone have to be restarted, to setup functions and services of your provider.
. Apps and Layouts might change, after your phone was updated."
Emergency Call
Reboot"
View attachment 5920713
I comes back again and again after 5-60 Min. If i force stop com.samsung.android.cidmanager (2.0.23)
its gone. Removing all "Receiver Manager"/ Autostart also doesnt work. I guess another app calls that service. But i dont know which one.
The notification just tells:
"Serviceprovider-Update
Serviceproviderfunctions could not be setup."
Any idea other than just wipe data/cache and reinstall?
===Edit===
OK a complete new flash and new root was fine until i used the ro2rw script again.
Same Error as before. I guess there is one Service that is causing that nag screen.
Thanks a lot for reading.
Greetings
4summer
Click to expand...
Click to collapse
Remove CSC Manager from ADB or via Root.
That solves the nagging screen.

@JazonX: Thanks a lot. I found that out by removing the most likely apk and froze all of them with sd maid. But good to know that the bugger was the CSC Manager.
I finally got most stuff that i need working. Did you figure out how to delete the "RO2RW_Super" Folder? I backuped the files inside it on my dektop. But after that I cant delete, move or take the files over. And the .img files are ~23GB in size. So a lot of space. I tryed also to rm -f them in Terminal with su. No chance. Maybe with TWRP?
---edit---
OK TWRP works if you remove any lockscreen stuff. Remove fingers and Pin/Patter (...) and than
it worked on my 2nd try with the integrated filemanager. ;-) 23GB more.
Dont forget that your TWRP Backups on your internal Space wont be there. By the way without any error! I read about that topic but forgot already that it wont work. So it works only with a external device like a usb-c Stick.

Related

[Q] Touchscreen problem after install Webtop hack

Anybody have this problems???? I recently decided to try install the webtop hack over hdmi (by _unknown) using the cmw zip file provided by Ronaldo. after successfully hacked and used it on my TV, i now have a problem with the touchscreen
{
"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"
}
The area circled in the image, is not registering any touch. i cannot choose Motorola Widget, i cannot press the back button in Dialer, i cannot choose Sign In when you first set-up the Google Account. It seems like that line on the screen is dead or something.
i tried format data/cache/system/ in recovery mode and fastboot mode, i flashed several ROMs (Alien, Aura, piCRUST even sbf the original 4.5.91 from Motorola) to see if it's ROM-related but problem not solved. i even replaced the screen protector and its still the same.
anyone have seen this before and suggest a solution????
- Update: i also try Touchscreen Booster suggested in another thread, but still no help.
- Also, the navalynt ROM does have a new kernel, which i did flashed, but the problem is still there. i flashed back to Alien with the default kernel, the touchscreen is still messed up.
anyone suggest something???
Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.
Did you skipped the MotoBlur account setup?
If so, then try to set it up and see if that helped.
Cheers!
Rayan
Sent from my Atrix using Tapatalk
Rayan said:
Did you skipped the MotoBlur account setup?
Click to expand...
Click to collapse
i did Motoblur setup, that's why i was stuck at the Google sign-in account, had to rotate screen to select Sign In
xploited said:
Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.
Click to expand...
Click to collapse
I tried permission fix last night and the problem is still there. i also did a clean install of stock sbf 2.3.4 and fully wipe everything i can think of ( i thought it was the webtop hack that cause the problem, so i tried to delete all ) but its still there. i think this might be a hardware problem at this point. this sucks
also, my phone's root is now crazy im on Alien 4. it denied access of Quickboot but granted access to Root Explorer, which is weird.
ok, so i have tried everything i have searched on this forum: permission fix, pdsfix flash, change the value of touchpad.cfg, reflash stock sbf twice, and im still having this problem (see picture below). anyone know what is the symptoms of this ????
(i flashed ROMs occasionally, from stock to Alien, to Aura, to Homebase, i also tried webtop hack over hdmi).
anyone can help define my screen problems like in the picture???? i press one spot and the screen registers 2 touch. i now have 2 dead area on my screen.
Holy hell this is EXACTLY what my phone is doing.Except mine is randomly touching the top left corner of the screen. So when I type it enters the letter q no matter what letter I hit. Today it got so bad that everytime I hit the backspace button it would type q 5 times.
It seems asthough the multitouch hack seems to scew up the digitizer.
When I "hit" the phone (against my hand, and the phone is in a Otterbox) sometimes it would fix it. Or if a press hard on certain corners of the glass.
I reflashed the phone today to Home Base, and it hasnt done it since. I even ran Quadrant and Smart bench for a hour, while running at 1.3Ghz, and it didnt do it. So its not the phone heating up. But I am not certain its fixed. Its very random.
My only answer is the digitizer. Which is gonna suck. Not going to be as easy to fix as a iphone..

(puerto rico)AmericaMovil ICS Leak

{
"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"
}
Download Link: http://goo.im/roms/mattlgroff/Blur_Version.651.167.3370.XT910.AmericaMovil.en.01.zip
MD5: FAF583BA8E5BE1D1EAC10C0BF775BAF0
Mattlgroff's Notes:
Upgraded CDT.bin, so no going back to GB after this.
Android 4.0.4 ICS - "AMXLA/XT910_MOTO_AMXLA/umts_spyder:4.0.4/6.7.2-180_SLC-34/1340677325:user/release-keys"
HOW TO ROOT: http://goo.im/apps/mattlgroff/DroidRazrRoot404.zip ---- Run the batch file in this. Be connected via USB (MTP Mode recommended), and have USB Debugging Enabled (Settings>Developer Options)
If you have Superuser left over and root is failing use this: http://rombot.droidhive.com/ROMs/spyder/ROOT/DroidRazrRoot404(IfYouAlreadyHaveSuperUser).zip
Build Date 26/6/2012
How to install from another ICS leak (same carrier, model, etc.):
Put the leak on your external SD card.
Fastboot a patched boot.img using the boot.img.p from this leak's /patch/ folder and the boot.img from the latest official version's fastboot files. (See my thread on patching boot images here: http://forum.xda-developers.com/showthread.php?p=27211509 )
NOTE: If someone posts a reply with a boot.img they patched, you can use that one as well. Only one person has to make one and post it.
Fastboot the system.img and preinstall.img from the latest official version
Boot to recovery and install the newer ICS leak.
Must be on 651.167.3370.XT910.AmericaMovil.en.01 stock rooted to install.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Be on STOCK 651.167.3370.XT910.AmericaMovil.en.01. No frozen apps. No custom recoveries, etc.
Install instructions are using ES File Manager and Rom Manager (free) from the Play Store download these and be rooted on 651.167.3370.XT910.AmericaMovil.en.01.
open rom manager free, hit OK, now press the home button.
open es file explorer, press YES, press menu, open settings, scroll down to Path settings and under Root settings: Enable
Up to Root (path settings)
Root Explorer (root settings)
Mount File System (root settings)
"DOWNLOAD THE ICS UPDATE ZIP AND PLACE INTO YOUR PHONES /CACHE DIRECTORY (not /system/cache, but in the root of the phone)"
open ES FILE EXPLORER, locate your /cache directory and then select the Blur_Version.651.167.3370.XT910.AmericaMovil.en.01.zip
(now choose Open With ROM MANAGER)
phone will restart, and begin installation of the ICS leak (takes 10-15minutes)
phone restarts, boot animation begins, Android is upgrading :: Profit success!! Celebrate!!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Oh! This I want!
woohooo... aqui voy!!!
After Rooting and installing this rom, it showed the CLARO logo, then started doing the "android is upgrading" counting the apps... but after that it froze on starting applications... don't know how to unfreeze it or restart it... There is no way to do a battery pull, so can anyone help????
I managed to reset it, and it booted, but...
No Sound and it drained the battery pretty fast...
Gonna do a Factory reset to reinstall all the apps to see if that resolves this...
You should definitely just do a factory reset, along with wiping your caches from Recovery. I wonder how many people complaining of ICS issues just never did a factory reset in fact...with such a huge OS change, there's no way I would trust it just "upgrading" what was installed. I just got my unlocked RAZR and went straight from fresh Gingerbread with nothing installed to this Claro ICS, and immediately upon booting I got force closes from Google's own apps. A factory reset along with wiping the caches fixed it up. Loving it so far, only really noticeable problem I've had is the widget selection screen having each widget's name whited out, but other than that, it's been stable and solid. Battery life has been pretty great as well, easily hit 15 hours of nearly non-stop screen usage to set everything back up before it said to plug in the charger. In regular usage I can see myself going 2-3 days.
The problem as I have stated in other threads is that the battery is not charging and it wont let me do a FR... Something went very fubar and stiil don't know how to fix it... and I'nm still reading... a lot...
Waiting for someone kind enough to give a try from the retail BR ICS version to move to this one and post instructions on how to.
Edit: After a lot of reading and getting scared a couple of times, patched my own boot.img
Download here
After updating I waited for the new system to boot and rebooted to recovery to master reset, works like a charm.
Thanks juanfers! Needed that file to upgrade from the Brazil leak!
Update...
I managed to make it charge, but still I notice the battery goes very fast... I saw that there is a script for taht or something. Can anyone point me to the correct download?
Honestly, i don't know why you guys didn't use the LATAM Retail version, is the best rom for our phones, and is not full of all the claro crap
Does anyone know when ics ota is coming to Puerto Rico for our razr
hi, i write for a web page called QiiBO.com, we want to feature this rom/update to help our readers upgrade their phone, if anyone here is so kind to write a guide, we will feature you, your twitter or your name, thanking you for your help. Thanks, and you can contact me thru [email protected]

E: failed to mount /efs

Hi, I was wondering if anyone can help me.
My tablet is unable to mount my /efs directory, or whatever. And while I don't know if they are directly connected,
things like my lock screen, holding my power button to get options like Flight Mode, Data Network, Restart, Etc., is gone. And I have tried screen lock to work, it doesn't. Holding my power button shuts my tablet down (in the same amount of
time that holding it would normally bring up the options screen, as well). I also loose completely my 3g, no matter wish successfully installed rom I run. I am not new to flashing rom at all and navigate trough all kind of step regarding specifics to rom by heart. All I can remember was to try the latest Android 4.1.1 - CyanogenMod 10 Preview and failed to load it, I was stuck in the boot animation for half an hour. So I decide to go back to the new stuck 4.0.4 from my provider. That is where I found the problem. Since, I have try 4.0.4 stuck, 4.04 rooted. The problem occur the same way in every rom and everything else was juste fine. I try the 3.1 stuck and 3.2 stuck and the message E: failed to mount /efs appear when rebooting from odin install.Never been able to load any version of the latest 4.1.1 from pershot. I have found a thread about the same issues from another device http://forum.xda-developers.com/showthread.php?t=1766748. I pass the entire day reading the web for solution, but no cigars so far.
I have the a Telus samsung galaxy tab 10.1 3g.
Thanks in advance if you have any idea how to resolve the /efs mounting problem.
I will added these picture to show that I have lost all important information that is apparently store in some file inside this /efs folder. Apparently this folder as been corrupt when flashing the CyanogenMod 10 Preview especially made for my tablet. So my new question would be to ask.
Do anyone know how to restore this folder even if I have no backup of it?
{
"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"
}
on off on off
try to copy the content of the efs folder with any root browser. it will have files and folders like in the screenshot atached.
Solved.
i had exactly the same problem. Was working on it for the last two days (ofcourse i am a simpleton and rookie )
But yes at last the phone is fixed and working fine with all the parameters.
So dont worry dear. Try to follow these steps : -
1. flash a rom using odin or heimdall - either stock or Cyanogenmod. You can check the repartition if using with the pit file.
2. Root your phone if not already rooted
3. Install busybox
4. Install kTool.apk (Its a small and wonderful apk. Freely available)
5. Install any file manager that supports root browsing
6. Make a backup of your efs with the help of kTool.apk (Its simple)
7. Decompress your earlier backup and copy all the files in the root efs folder with the root explorer
8. Now rename the one that you decompressed the files from as efs.img and copy it into the internal sdcard root
9. Now retore the egs.img using the kTool.apk
This will solve the problem i guess.
Good luck
8.
No file in /efs folder, and no backup
Thanks a lot for the answer guys, but unfortunately there is nothing inside my /efs folder. It's completely empty and therefore I can't copy it, move it backup it,or anything. I also have no backup of this folder. As I understand some file in this folder contain the super important information of my own system like IEME, Serial, etc... So my concern is more like is there is a way to restore this folder even if it doesn't exist. I think the answer is no and the only solution for me is to send it back to Samsung with the stuck roms from my provider and hope for them to not deny the repair so I won't have to pay. I wonder if there is other thing to do but I am pretty sure not. If someone know something let me know. I have already contact Samsung and tell them that my 3g is broken and some strange behavior occur during OTA update. They are going to send me something for me to send the tablet for reparation. Til then I really want to know if there is something I don't understand and if there is still hope. Anyway thanks in advance for anyone who know better then me.
This is EXACTLY what's going on with my tablet, and yes, there's nothing to copy. What do we do?
I originally edited my old post with this, but I wanted to be sure the OP saw it.
I finally fixed mine. See my thread at http://forum.xda-developers.com/showthread.php?t=1876260
I hope it helps

Help ME Please OTA Update Has my phone stuck in a boot loop

So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
While you can (sometimes) install an OTA while your phone is rooted, you should never try to install one when it is fully unlocked (i.e. - custom recovery installed). You edit seems to indicate you fixed it, but if you're still having issues I know there are steps to get out of the bootloop you're experiencing, I just don't have off hand where they're at. Bottom line, if you're root AND unlocked (running twrp), you should never take an OTA as there's no reason for it. You can install one of the fine stock-based roms that have been updated to the latest VZW software and have no risk in doing so. Just for future reference
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Pays to have a copy of LG Flashtool and the stock firmware
See the first post here: http://forum.xda-developers.com/showthread.php?t=2907508
If you have a USB otg cable, you can put the flash...zip file linked in the post on a flash drive, then tell twrp to install that to clear the ota.
Alternately, twrp has a small terminal emulator. Look at the part of the post with the commands listed. Only input the su and two dd command lines, in twrp.
After either of the above, tell twrp to reboot to system.
Once you can successfully get back to your normal system, either freeze "System updates...." or use a file manager to rename the two LGDMSClient files found in /system/app, then reboot your phone one more time.
{
"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"
}
HTH!

Poco F1 After 11.0.9 update(Not MiUi12) dialer not opening.

Apologies guys as this may be a very small problem with very small solution but somehow I spent over an hour trying to make it work but I couldn't. This phone is on stock MiUi and even the bootloader is not unlocked. Elaboration:
1. Before update dialer functioned okay, I had restricted maybe one or two permissions like Location but still it worked.
2. After Update I got to know google had my location history 'on' so being a privacy freak I turned it 'off' (I know they can still get the location, but atleast not where I was 6months ago now).
3. I didn't find any other issue post update but I hadn't tried to open dialer yet;
When I tried it said required permission has been not allowed and it just wouldn't open. Sms app worked fine, contacts and dialer didn't.
4. Them I tried giving the 'contacts & dialer' app all the permissions it required via the settings ->apps-> Contacts & dialers -> permissions, including the location which is I haven't allowed on my other Poco F1(yes I have 3 at home, all purchased before COVID time) and the same update was already on that phone and it works fine.
For now I have a third party dialer app installed which does the work, it would be very helpful if someone could help me getting the original dialer to work. And yes I know Mi sucks with things like this and bloatware I might install Lineage or something in months to come but this belongs to my father he might not want his phone to be unable to operate banking apps and wallets so on hold for now.
Thanks already guys.
Not sure but try to clear all data of the "contacts and dialer" app first (Settings -> apps -> manage apps -> contacts and dialer).
If it doesn't work then I suggest you re-download the latest update and install it again. (Settings -> about phone -> system update -> the three dots menu -> download latest package).
{
"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"
}
Sent from my POCOPHONE F1 using Tapatalk
Go to "menage apps" -> "phone services" and force stop it. Then Open "storage" and clear the data.. Then do the same in "call manager" (i think thats the name in inglish). The 2 apps haver a phone símbolo. Then restart you Poco F1. Turn it completly off and turn ir on again.
Worked with me..
You have disabled a required permission. Tried what both of you suggested above except for reinstalling the update. Not resolved
OsGhaly said:
Not sure but try to clear all data of the "contacts and dialer" app first (Settings -> apps -> manage apps -> contacts and dialer).
If it doesn't work then I suggest you re-download the latest update and install it again. (Settings -> about phone -> system update -> the three dots menu -> download latest package).
Click to expand...
Click to collapse
Didn't work, but I'm a little sceptical about download latest package and installing, never done it before so. I tried the other solution you have but didn't solve the problem.
SmaxTRex said:
Didn't work, but I'm a little sceptical about download latest package and installing, never done it before so. I tried the other solution you have but didn't solve the problem.
Click to expand...
Click to collapse
First of all downloading the latest package is just the same as installing a normal update, no difference at all.
Second, I think to avoid all this hassle; you might need to do factory default/factory reset.. But of course before doing that you have to write down all your accounts login data (especially Mi account and Google account) and also backing up your personal data (photos, docs, music, videos downloads,...etc.) as it will be deleted when you do this factory reset.. But this will eventually solve all these problems.
Sent from my POCOPHONE F1 using Tapatalk
OsGhaly said:
First of all downloading the latest package is just the same as installing a normal update, no difference at all.
Second, I think to avoid all this hassle; you might need to do factory default/factory reset.. But of course before doing that you have to write down all your accounts login data (especially Mi account and Google account) and also backing up your personal data (photos, docs, music, videos downloads,...etc.) as it will be deleted when you do this factory reset.. But this will eventually solve all these problems.
Click to expand...
Click to collapse
I was hoping to avoid Factory Reset, and all the efforts and time associated with doing it but I'm being sure by the days that pass, of there being no other alternative for me. I'm so fed up of Xiaomi after this. Once a stable Lineage or PE comes after MiUi 12 upgrade I'll lose no time to this. Also out of 4 phones in my home 3 are Poco F1 and the last one was Lenovo zuk till Feb and Vivo since, but non Mi phone doesn't get as many ads on YT and Instagram (virtually none on insta when I get one ad every 10-15posts, despite of having not allowed similar permission to Mi during setting up of my phone).
So I spent good time backing up and reloading after factory reset. The problem is solved costing me alot of time and effort for backup and stuff.
So basically problem solved by a factory reset.

Categories

Resources