I am having issues when using a specific app (Pzziz) which relies on a media file stored in data/media/obb folder. Every time I play the media file I am given the following error "Cannot mount media file. Please try again. Error Code: 21". I have tried wiping the folder, uninstalling the app and reinstalling the app but still have the same issues. Anyone have any advice and sorting this out?
Same issue on a different device
I'm not using the OnePlus 3 but have the same issue. It only occurs when I have Magisk installed. If I completely uninstall Magisk using the Magisk manager app Pzizz starts working again after a reboot.
burgess_boy said:
I am having issues when using a specific app Pzziz which relies on a media file stored in data/media/obb folder. Every time I play the media file I am given the following error "Cannot mount media file. Please try again. Error Code: 21". I have tried wiping the folder, uninstalling the app and reinstalling the app but still have the same issues. Anyone have any advice and sorting this out?
Click to expand...
Click to collapse
Did you get any closer to resolving this issue? I have the same problem on a Google Pixel. I emailed the developer and they enrolled me in their alpha test. They seemed genuinely interested in making Pzizz work with Magisk installed but none of the alpha updates have helped.
Yes I did resolve the issue. I replicated your findings by removing magisk and low and behold Pzizz started working again.
I recently installed Nitrogen OS which allows Pzizz to run with Magisk installed. It appears that when I have a OnePlus based OS installed I get the problem however if I install an AOSP based ROM the issue goes away. Let me know how you get on.
I have an AOSP ROM based install on a Nexus 7 2012 and a Pixel with stock OS. Pzizz won’t run with Magisk installed on either. I wonder what Nitrogen OS is doing the others aren’t.
For anyone following this issue: Magisk beta 16.6 fixes these issues with Pzizz.
i got magisk 16.7 beta, issue is still occurring?
Related
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
liran corleone said:
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
Click to expand...
Click to collapse
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
MartCLEANRFr said:
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
Click to expand...
Click to collapse
well, at this point - i just want to make the device work...
Hello, I bricked my phone trying to update it, now I have factory reset it and loaded another firmware over it.
It now starts up again and I did all the setting that you get at the start.
Somehow it doesn't recognize my sim card even though I didn't touch it when doing all this.
It also doesn't load the play store.
Any idea what could cause this and how to fix this?
the same playstore error occurred with my brother's device when he forced uninstalled the play store and tried to install manually, I think the problem in your case is incompatible software. Try to find the stock rom for your device and flash it. It might fix your problem
Apps like play store really ate determined by the phone's SDK version and if any system upgrade ships an stock app of a different Version of phone or phone changes any command relating to phone's increment version, apps will cause a library mismatch hence running of apps with lib support fails. Just download the play store from another source and rename it with a single name, and if you have root, use a root explorer and place it in "/system/vendor/operator/app" and set permissions to "rw-r-r" then reboot your phone wait until it's fully boot up. Then go to "/data/app-lib/'the_name_you_named_the_app'/" you will see an unknown file "named_something.so". Copy the .so file to "/system/lib/" and set permissions too to "rw-r-r" and then finally go to "/system/vendor/operator/app/" and move the app you placed there initially to "/system/app/" and boot up your phone and things will get done for you. In each system app that fail to work in a ROM upgrade. Just do so and all will be well
Sent from my TECNO-J5 using XDA Premium 4 mobile app
Hi folks,
I need your help.
A few days ago I have received my brand new HTC 10. I updated to latest Android 7 Nougat and began to root remaining stock.
I followed the official guide and unlocked the bootloader, flashed latest TWRP (3.1.1.0) and SuperSU v.2.82SR1 and even got S-OFF by SunShine.
System is up an running and readily booting but...
Fact is I cannot mount /system in TWRP without the option "read-only". When I try to install apps via TWRP I get repeated messages saying "Failed to mount '/system' (Invalid argument) " and usually the apps do not install properly - flashed apps do not show up in the system after reboot.
In the system I have tried to rename a file audio_effects.conf (this is needed to install Viper4Android) in the folder /vendor/etc/ on the device but the folder is strictly read only. Any attempts to mount the folder as RW (using "adb shell", "su", "mount -o remount,rw /system" and similar) have failed. I have tried to gain access to files in the system folder using Root Explorer and Total Commander but the files remain strictly read only. I just get error messages trying to change file attributes, permissions,names).
SuperSU seems to work and according to Root Checker I am properly rooted but I doubt this. Somehow /system seems to be locked and not accessible.
Any ideas what I could do ?
Many thanks for your help ! :good:
Well, I simply flashed Viper10 ROM and the issue was gone.
Feel free to suggest solutions to the problem as somebody else might come accross this thread struggling with a similar issue. I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Buddha1979 said:
Well, I simply flashed Viper10 ROM and the issue was gone.
I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Click to expand...
Click to collapse
No, it's not an incompatibility issue.
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
plz help a noob
LibertyMonger said:
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
Click to expand...
Click to collapse
I also just recently updated to nougat and when i tried to root using the latest (TWRP 3.0.3-11) it seems I get stuck on a screen with red text that says, "This build is for development purpose only . Do not distribute outside of htc without htc's permission."
I know this is not the original question but was hoping someone with more experience could help instead of starting a new thread :/
Thanks much!
I just ran the latest Verizon RUU and I am still getting this error when trying to flash Viper10_5.9.0_MAGISK. Seems system is not mounting, I don't know I will appreciate any help Thank you.
My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained
its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed
The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!
Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals
Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????
built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.
ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.
Hi everyone,
I'm using LineageOS with a OnePlus 9 Pro.
I'm trying to install the OnePlus camera app downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/
When I try to install it with the built-in installer, it just says "App not installed."
If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"
What is the reason for this, or how can I fix this?
Thanks!
Is that. Apk file?
Hi @warangekar!
Yep, it's an .apk file downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/, it's com.oneplus.camera_6.2.117-26211918_minAPI29(arm64-v8a)(nodpi)_apkmirror.com.apk
(This is the version for which the Notes say "Extracted from OnePlus 9 Pro", that's why I chose this one. But afterwards I tried a couple more different versions of the same app, and I got the same error message for all of them when tried to install.)
It's extension is exactly. apk something like .xapk, .apks
@warangekar It's exactly .apk
Download Mirror Apk installer and try to install it with it
@warangekar I did, as I wrote in my first message:
>If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"
May be that Apk file is corrupt
If that file is not corrupted then you should try following,
This error is thrown by adb when we use it to install the application on a device/emulator. There are a few things you can try to isolate and resolve the issue.
Try on a different device/emulator. If this works, it is most probably an issue with the device configuration - check that USB debugging is enabled in Developer options.
Try killing the adb process. The CLI will start a fresh one on the next run.
Try to cleanup the configuration and artifacts directories - rm -rf node_module hooks platforms. Then run the application again.
Try installing Android SDK Tools version 28.0.3 and Android SDK 28
If the issue persists, you can run the project with tns run android --log trace > out.txt command and send us the out.txt file that will contain the full output log of the NativeScript CLI.
As the page says :
- "Note: Sideloading this APK may not work, so you may need root to install. Click here for more info.
For some reason, some manufacturers sometimes forget to sign some system APKs with APK Signature Scheme v2, while indicating that these APKs are indeed v2-signed. These APKs are usually signed with only APK Signature Scheme v1 (jar signature), so we can still confirm the signature is valid, but Android will refuse to sideload them due to the missing v2 signature."
So most probably signing it will do the trick.
I signed it with a debug key, see if it work.
EDIT: tested and working on android 11
Okay
You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.
ekin_strops said:
You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.
Click to expand...
Click to collapse
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core
Oneplus# said:
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core
Click to expand...
Click to collapse
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm
ekin_strops said:
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm
Click to expand...
Click to collapse
- First, he have a one plus 9 pro and lineage.
- Second your answer say that it can't be installed on non oos-rom ... so not right.
- Third Maybe will be not good, maybe on some phone will crash but the apk definitely install itself because it was only missing a signature.
- And last I'm not using it, I've installed only to be sure that the apk install itself.
So "You can't install the APK on non-OOS ROMs." Is not right, it can be installed.