Database Users

[Q] How do I update my rom?

I am running aokp 4.4 kitkat nighly and I wanted to update. When I update without wiping anything on top of my previous rom it works, but my google play is missing. Also , my folders and widgets went away leaving me with only gallery and setting on the main page. Google now was not there either.
How do I update without losing my data?
Do i have to wipe anything before flashing?
Thank you in advance

Gapps are stored in system which is formatted when you update, you have to flash gapps again.
Nightlys are not really for normal use so you shouldn't have any data that you're worried about losing on there.

Nexus4boi said:
I am running aokp 4.4 kitkat nighly and I wanted to update. When I update without wiping anything on top of my previous rom it works, but my google play is missing. Also , my folders and widgets went away leaving me with only gallery and setting on the main page. Google now was not there either.
How do I update without losing my data?
Do i have to wipe anything before flashing?
Thank you in advance
Click to expand...
Click to collapse
I would think about trying another rom. You should be able to dirty flash an update for the rom that's already on your phone without losing anything.
DrFredPhD said:
Gapps are stored in system which is formatted when you update, you have to flash gapps again.
Nightlys are not really for normal use so you shouldn't have any data that you're worried about losing on there.
Click to expand...
Click to collapse
Some nightlies can be a daily driver, just have to pick a developer who is well known for their work and not someone who just started learning last night!
Sure, you have to start somewhere, but I think you know what I'm saying.
Sent from my Nexus 7 (2013)

DrFredPhD said:
Gapps are stored in system which is formatted when you update, you have to flash gapps again.
Nightlys are not really for normal use so you shouldn't have any data that you're worried about losing on there.
Click to expand...
Click to collapse
yea it worked once i tried it with gapps and all my setting were left the same
thanks for all you help everyone

"download pending" in play store even tho nothing else is downloading....

i tried restarting and it didnt work

Force close play store and open it again
It'll start downloading

berezker said:
Force close play store and open it again
It'll start downloading
Click to expand...
Click to collapse
didnt work, i also tried to clear data and that didnt work i reflashed everything also didnt fix it then after some time it just magically worked again
EDIT: ok i now flashed another rom and the issue accured again doesnt seem like the thing that happend the previous time is happening again

YayJohn said:
didnt work, i also tried to clear data and that didnt work i reflashed everything also didnt fix it then after some time it just magically worked again
EDIT: ok i now flashed another rom and the issue accured again doesnt seem like the thing that happend the previous time is happening again
Click to expand...
Click to collapse
Guys, an easier way is this. Just turn on Battery Saver mode and your update or download will start immediately...
Same thread: https://forum.xda-developers.com/mi-a1/help/solution-play-store-t3834264/post77446595#post77446595

Converted007 said:
Guys, an easier way is this. Just turn on Battery Saver mode and your update or download will start immediately...
Same thread: https://forum.xda-developers.com/mi-a1/help/solution-play-store-t3834264/post77446595#post77446595
Click to expand...
Click to collapse
i ended up reinstalling gapps and that fixed it for me, but if this issue occurs to me again i will try to fix it using this, thank u

YayJohn said:
i ended up reinstalling gapps and that fixed it for me, but if this issue occurs to me again i will try to fix it using this, thank u
Click to expand...
Click to collapse
Your phone download update of google play service in the background, that's why other download are in "pending" status

itsnie said:
Your phone download update of google play service in the background, that's why other download are in "pending" status
Click to expand...
Click to collapse
I don't think that's the case, because it took quite a lot of time

For about a week, I also have this problem.

Ontkebong said:
For about a week, I also have this problem.
Click to expand...
Click to collapse
YayJohn said:
I don't think that's the case, because it took quite a lot of time
Click to expand...
Click to collapse
You can also delete Google Play Services cache, this works pretty well in those cases. Even if you have problems trying to download a device system update.
Even it's data (in this case you'll have to add an account for Google's data backup again).
However, keep in mind this kind of processes won't work well if you have enabled apps, device features or Magisk modules that force device to save battery in some way.

KaaMyA said:
You can also delete Google Play Services cache, this works pretty well in those cases. Even if you have problems trying to download a device system update.
Even it's data (in this case you'll have to add an account for Google's data backup again).
However, keep in mind this kind of processes won't work well if you have enabled apps, device features or Magisk modules that force device to save battery in some way.
Click to expand...
Click to collapse
Done that. Didn't work for me sadly.

Ontkebong said:
Done that. Didn't work for me sadly.
Click to expand...
Click to collapse
Would be good to tell us which system you've installed.
Any custom ROM? Are you in stock?
On the first case, check ROM installation.
If it came with gapps preinstalled, better flash an updated version of that ROM (clean or dirty would change, depending of Android major verion in which that update is based), otherwise flash another gapps, I use OpenGapps.Try to flash, at least, nano gapps.
If you're on stock, things are quite different, since there you haven't the same way so solve things, more than than reflashing firmware.

KaaMyA said:
Would be good to tell us which system you've installed.
Any custom ROM? Are you in stock?
On the first case, check ROM installation.
If it came with gapps preinstalled, better flash an updated version of that ROM (clean or dirty would change, depending of Android major verion in which that update is based), otherwise flash another gapps, I use OpenGapps.Try to flash, at least, nano gapps.
If you're on stock, things are quite different, since there you haven't the same way so solve things, more than than reflashing firmware.
Click to expand...
Click to collapse
Stock Android One version 9 (Pie) with regular updates. :silly:

Looks like something is screwed up there.
Is your device rooted?
I feel that would be better to backup your data and flash latest firmware with Mi Flasher tool.

The same is happening some times and on my A1 and is fully updated stock rom without root or any other thing...
I think it has to do with the latest version of Google store or Google services...

After flashing(S8 exenos)one UI stable version(SD card method)some apps are stopped

Dear developers,
Yesterday i am updated my S8 from oreo to One UI via SD card method.
All thingks are great, but there is 1 problem,after update some apps are not working such as MX Player Pro, SNOW.(Attach available of error message & software version). https://imgur.com/a/iYnK6IX
I do factory reset last night but the issue remain same. Please suggest me how can i solve this ?

Simple, do a clean flash. More exactly a factory reset.

Swrv said:
Dear developers,
I do factory reset last night but the issue remain same. Please suggest me how can i solve this ?
Click to expand...
Click to collapse
dmartuniac said:
Simple, do a clean flash. More exactly a factory reset.
Click to expand...
Click to collapse
He did mention that he made one ??*

ELMoro752 said:
He did mention that he made one ??*
Click to expand...
Click to collapse
Sorry, I thought that I read every line
Well, he can download the entire rom+firmware from sammobile and erase all the data. If that didn't works, then there is a problem with the apps.

Try to reset it from Reccovery mode and wipecache

I found a solution. Perticular 2 apps are not working. So i download the previous version of those app & install it. Then update it from play store. After that it works without any error :victory:

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.

Alternatively is it possible to access the settings of this submenu through a different app or way?

hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen

True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages

Have you got any magisk module active?

estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.

hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP

Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!

@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers

Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.

hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers

Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:

Is there any risk involved concerning the encryption?

hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.

Stuck with the same issue. Did you manage to get it fixed somehow?

Actually the latest available oo update to 10.3.1 fixed it.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.

You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.

Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though

Bricked and need help

NM: I've was able to flash 10.3.4...but my internal storage got wiped out. It's saying I have 105GB of 108GB free...I have backups but my backup is corrupted since I forgot to remove my security pattern...oh well...

just4sc said:
HI!
I tried looking in the 255 error thread but couldn't find a solution and was thinking maybe it has something to do with the -32 version of TWRP so I went to the TWRP thread but no answer so here I am hoping someone here can help.
I made a backup however I found out later that I had forgotten to remove my security pattern prior to backup. Don't know if that's the issue but upon doing a restore I'm getting the dreaded 255 error. I also forgot to run magisk uninstall and don't know if that's the issue too (yeah, not a good idea to be working on stuff like this in the middle of the night and lacking sleep).
I haven't rebooted yet fearing I won't be able to get in.
I have since tried running the magisk uninstall (gave me an error - didn't write it down and now I can't see it anymore).
Tried installing magisk again (installed ok).
Install 10.3.4 ROM and that went ok.
Still not rebooted - thinking the install of 1.0.3.4 might have solved my problem I reinstalled TWRP -32 and then tried restoring my backup again. Of course I still have the 255 error.
I hoping someone has gone down my path or have some advise so that I can restore my backup.
Again, I still haven't rebooted yet so maybe that's my issue?
Edit: So, I rebooted and it gives me a crash dump. I can get into TWRP still but tried flashing the full 10.3.4 rom and it completes but it just goes into the crash dump again. I noticed while looking at Filemanager in TWRP all the filenames in storage are jumbled. Does that mean the encryption is messed up and I am hosed? I've tried searching but there's just so much information I'm a bit tired and am hoping someone point me to the right direction and maybe let me know if I can still recover. Thanks
Click to expand...
Click to collapse
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk

clsA said:
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks!