Related
Bear with me here, tis a long and windy tale!
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
amaru007 said:
Bear with me here, tis a long and windy tale! [emoji14]
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
Click to expand...
Click to collapse
Open/install terminal emulator and do "pm install /path/to/application.apk", it will give you aore detailed error about whats going wrong.
Sent from my Tw5ted SM-G900A using Tapatalk
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
amaru007 said:
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
Click to expand...
Click to collapse
Ah, try doing su first so you are running as root.
Sent from my Tw5ted SM-G900A using Tapatalk
Okay.
tried with su:
pkg: whatever.apk
Failure [INSTALL_FAILED_INVALID_URI]
Looking like Titanium restore hasn't worked properly either, loads of programs needing to be reinstall again.
Dunno if its connected to this problem or not.
Invalid uri means you did the path wrong, tab complete the path(volup+t i think, if not voldown+t) so you have it exactly correct, it doesnt matter if you are already in the directory containing the apk it needs the full path.
Sent from my Tw5ted SM-G900A using Tapatalk
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
amaru007 said:
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
Click to expand...
Click to collapse
So the error is consistently failed invalid apk? The ones that install fine on other devices?
Sent from my Tw5ted SM-G900A using Tapatalk
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
amaru007 said:
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
Click to expand...
Click to collapse
No problem, glad you got it figured out.
Sent from my Tw5ted SM-G900A using Tapatalk
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Risk3 said:
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Click to expand...
Click to collapse
No clue, usually if it errors in the visual installer it will also with command line, maybe try a factory reset? I'm not too sure, that's odd.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Turns out that the inability to install from the user interface coincides with a Cyanogenmod 13 (6.0.1) nightly upgrade. I'll either go back to a snapshot or try another nightly next week and see if that helps things along.
Thanks for your reply.
Ok so i rooted my s5 using odin 3.07, CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5 and SM-G900p.knox_removal.android.5.0.zip
Its probably worth noting my phone is on lolipop from samsung.
After i used those via odin the phone rebooted as expected. However the first time it booted it would not work. It would get to the home screen after start up and system process would fail.
I rebooted into recovery and used the fix permissions and fix selinux option.
Now my phone works fine with 1 exception, i get an error that says google play services encountered an unknown error. Any idea what is causing this?
I also have installed twrp 2.8.7 ( i think that was the latest available ) this was done using the twrp app which initially said it failed but when i rebooted into recovery it was there.
Any help would be appreciated. Also is it normal for the rom to refuse to check for upgrades once rooted?
I have been trying to flash gapps to my phone in the hopes of getting rid of this google play services error but i cant seem to flash gapps.
TdiGuy said:
Also is it normal for the rom to refuse to check for upgrades once rooted?
Click to expand...
Click to collapse
Yes, it's normal.
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.
Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
no its not working......After install recovery stuck in Samsung Flashing logo....
TWRP is making the devices get stuck on Samsung logo....
I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.
Having root and no encryption sucks. Think I'll wait
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.
guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.
CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly
hello, i have a new problem found few days ago and been trying to fix it but to no avail.
here is how it started.
i tried to install an app called fsecure vpn network from google play. then the phone when into a bootloop. then i did a clean wipe (reset, wipe cache and dalvik from recovery) but somehow my files were not gone. that is some kinda miracle i have no idea how it happened.
since then my phone have issue whenever i installed mihome:
-. google play services, trebuchet, package installer, and some other has stopped.
-. cannot open apps list in settings when mihome is present. the settings just stopped and crashed.
-. if i try to open the mihome, the phone goes reboot.
-. even uninstalling mihome from application list is not working, the package installer stopped. have to uninstall from google play.
-. i tried to make a bluetooth printer app, but when i put the app-debug.apk into my phone. file manager would crash whenever it tried to read the file. even by just scrolling down. example: file manager work fine if the file is not copied inside (meaning we can scroll around and not crash). but once the file is copied in then the file manager will work if we dont scroll down to find the file, but when we scrolled down to find the file then the app crash.
things i've tried:
-. clean wipe then reflashing rom and gapps.
-. manually update google play store, download google package installer and reinstall it.
-. tried to download google play services apk but was unable to install it.
-. tried the idea of clearing cache of google play service but still no luck (force stop was disabled anyway so i cant try that)
i have no idea how this all happen just because i tried to install that fsecure app. its not even fully installed yet. it was just starting to install after download then this hell happened.
im desperate for some help as i've tried for 3 days in fixing it but to no luck. any helps would be very appreciated.
thanks and regards,
hendry
yohhendry said:
hello, i have a new problem found few days ago and been trying to fix it but to no avail.
here is how it started.
i tried to install an app called fsecure vpn network from google play. then the phone when into a bootloop. then i did a clean wipe (reset, wipe cache and dalvik from recovery) but somehow my files were not gone. that is some kinda miracle i have no idea how it happened.
since then my phone have issue whenever i installed mihome:
-. google play services, trebuchet, package installer, and some other has stopped.
-. cannot open apps list in settings when mihome is present. the settings just stopped and crashed.
-. if i try to open the mihome, the phone goes reboot.
-. even uninstalling mihome from application list is not working, the package installer stopped. have to uninstall from google play.
-. i tried to make a bluetooth printer app, but when i put the app-debug.apk into my phone. file manager would crash whenever it tried to read the file. even by just scrolling down. example: file manager work fine if the file is not copied inside (meaning we can scroll around and not crash). but once the file is copied in then the file manager will work if we dont scroll down to find the file, but when we scrolled down to find the file then the app crash.
things i've tried:
-. clean wipe then reflashing rom and gapps.
-. manually update google play store, download google package installer and reinstall it.
-. tried to download google play services apk but was unable to install it.
-. tried the idea of clearing cache of google play service but still no luck (force stop was disabled anyway so i cant try that)
i have no idea how this all happen just because i tried to install that fsecure app. its not even fully installed yet. it was just starting to install after download then this hell happened.
im desperate for some help as i've tried for 3 days in fixing it but to no luck. any helps would be very appreciated.
thanks and regards,
hendry
Click to expand...
Click to collapse
Hello,
Did you try to reinstall Stock ROM ?
https://www.sammobile.com/firmwares/galaxy-grand2/SM-G7102/
It happened to me that sometimes, apps or rom just run into a bug and maybe it corrupt the firmware but after a Stock ROM flash (via Odin) + custom recovery (via Odin) to wipe Cache + Data, everything was fix.
Hai, could u possible post me a tutorial on how to do those thing via odin? Coz i usually only do it via cwm. Thanks
yohhendry said:
Hai, could u possible post me a tutorial on how to do those thing via odin? Coz i usually only do it via cwm. Thanks
Click to expand...
Click to collapse
Hey, maybe this one ? https://forum.xda-developers.com/showthread.php?t=1372414.
yumi14 said:
Hey, maybe this one ? https://forum.xda-developers.com/showthread.php?t=1372414.
Click to expand...
Click to collapse
hello, im currently trying to download the stock rom however i couldnt seems to be able to find any working download link for indonesia version of firmware.
can i use other country firmware for flashing then later flash to RR back?
yohhendry said:
hello, im currently trying to download the stock rom however i couldnt seems to be able to find any working download link for indonesia version of firmware.
can i use other country firmware for flashing then later flash to RR back?
Click to expand...
Click to collapse
Did you try to flash a recovery only ?
Maybe your firmware/system is not corrupted and then you could just reflash a clean rom ?
In Odin, Select AP and load your recovery.tar
I am having the very same issue. The difference is that it's happening with Spotify, Xposed and Relay for Reddit. So yeah it's been much worse for me. I will try to flash stock rom + reinstall another recovery and see if it fixes. By the way, I got a couple of questions:
1 - Does the country that I select when downloading the stock ROM matters?
2 - Which Recovery can you guys recommend? There's a bunch here but not sure if all them are worthy
Okay so I flashed an Indian stock ROM (I'm not indian nor live in the country), then I wiped all data, so I could boot. This is the default procedure to revert back to a Stock ROM.
After that, I noticed the Wifi wasn't working, probably due to the Stock rom I've downloaded. Anyway, I installed a custom Recovery (even an updated version of what I used before, then I reinstalled Ressurection Remix, and tried again.
....It didn't work. Relay for Reddit crashes everything, Spotify puts my phone into a bootloot. Same with Xposed. I have no idea what to do anymore. Someone, please help. I really can't afford to buy another phone right now and I really need those apps. Expecially Spotify.
Wagnelles said:
Okay so I flashed an Indian stock ROM (I'm not indian nor live in the country), then I wiped all data, so I could boot. This is the default procedure to revert back to a Stock ROM.
After that, I noticed the Wifi wasn't working, probably due to the Stock rom I've downloaded. Anyway, I installed a custom Recovery (even an updated version of what I used before, then I reinstalled Ressurection Remix, and tried again.
....It didn't work. Relay for Reddit crashes everything, Spotify puts my phone into a bootloot. Same with Xposed. I have no idea what to do anymore. Someone, please help. I really can't afford to buy another phone right now and I really need those apps. Expecially Spotify.
Click to expand...
Click to collapse
Ok try to flash 4 files firmware repair but do it at your own risk.
you must know you how to do it with no mistake
Just do a search on Google about (4 file firmware repair for grand 2) the way is easy but have to do not a mistake.
Then good luck
mahmmoud1231 said:
Ok try to flash 4 files firmware repair but do it at your own risk.
you must know you how to do it with no mistake
Just do a search on Google about (4 file firmware repair for grand 2) the way is easy but have to do not a mistake.
Then good luck
Click to expand...
Click to collapse
Okay, so I guess there won't be any need for that. I've redownloaded the stock ROM, but this time, I checked my phone Serial Number so I could download the right stock ROM for my phone. Now everything seems to be working again. Spotify and Relay installed without any issue. I will now try to reflash recovery and then another ROM and see if the problem persists.
For those who don't know how to check your Serial number, it's right above your android version, at the "About phone" section on Settings.
I still need advice on which Recovery I should use.
Anyway, thank you guys. I probably would't be able to solve this without your help.
UPDATE: I've installed TWRP 3.1.0.0, and also rooted the phone using it. Still on stock ROM. Everything seems to be still working without problems. I think I'll stick with it for now. Maybe later I'll try to lash a Custom ROM and see if it still works.
Wagnelles said:
Okay, so I guess there won't be any need for that. I've redownloaded the stock ROM, but this time, I checked my phone Serial Number so I could download the right stock ROM for my phone. Now everything seems to be working again. Spotify and Relay installed without any issue. I will now try to reflash recovery and then another ROM and see if the problem persists.
For those who don't know how to check your Serial number, it's right above your android version, at the "About phone" section on Settings.
I still need advice on which Recovery I should use.
Anyway, thank you guys. I probably would't be able to solve this without your help.
UPDATE: I've installed TWRP 3.1.0.0, and also rooted the phone using it. Still on stock ROM. Everything seems to be still working without problems. I think I'll stick with it for now. Maybe later I'll try to lash a Custom ROM and see if it still works.
Click to expand...
Click to collapse
Hi,
I'm glad you fixed you're problem. Sticking on Stock ROM is the best thing you can do if you need your phone as every functionnality is checked and working.
I personnaly use TWRP as recovery, its good you got usb, root and everything you need to backup/restore your phone + reset your phone.
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
yosry said:
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
Click to expand...
Click to collapse
Try wiping cache and data on those two apps from settings/apps
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
yosry said:
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
Click to expand...
Click to collapse
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
strongst said:
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
Click to expand...
Click to collapse
Nope its not rotted
And if there is a way to avoid rooting would be better
yosry said:
Nope its not rotted
And if there is a way to avoid rooting would be better
Click to expand...
Click to collapse
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
strongst said:
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
Click to expand...
Click to collapse
Right
yosry said:
Right
Click to expand...
Click to collapse
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
strongst said:
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
Click to expand...
Click to collapse
Done no change i mentioned in the 1 St post that i cleared cache after every install
yosry said:
Done no change i mentioned in the 1 St post that i cleared cache after every install
Click to expand...
Click to collapse
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
strongst said:
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
Click to expand...
Click to collapse
Ok i will try to install 9.0.0 then 9.0.2 again lets see if it will work thanks
Hey there i tried downgrading to 9.0.0 then to 9.0.2 with no luck leaving me with no choice but to factory reset and thankfully it worked eventually after talking a backup
So thank you all guys for support and appreciate your help