Related
I don't know the cause. I have noticed that it has happened on different devices, there have been assumptions if it's because of a specific kernel or rom, although it may be, I beg to differ. I feel it is happening during the Android Upgrading Apps # of # process.
I noticed that this error pops up on most of the apps that I had installed, but are not there after my update. So far with me, it happened only to my paid apps, but not all of them.
When the app disappears, android thinks it's missing, but some files think it is still installed.
Regularly when you install an app over itself, there is a notice telling you that the application info will remain. That's where the problem lies once an app mysteriously disappears. Because part of it is still installed.
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.:good:
Delete it
Install the application, it'll work, trust me. :fingers-crossed:
Now replace it with your copy.
Done.
Stop factoring resetting if you don't want to. Of course, if you have a lot missing, it might be better. :crying:
If someone can automate this process by making something check the com.address to installed apps, that would be awesome. :highfive:
This totally worked. Thanks bro!
I was setting up my Nexus 4, and this was Tune In Radio Pro was the last app and wouldn't install, I kept getting that stupid -24 error.
Saved me from doing a factory reset!
Works!
Qewbicle said:
I don't know the cause. I have noticed that it has happened on different devices, there have been assumptions if it's because of a specific kernel or rom, although it may be, I beg to differ. I feel it is happening during the Android Upgrading Apps # of # process.
I noticed that this error pops up on most of the apps that I had installed, but are not there after my update. So far with me, it happened only to my paid apps, but not all of them.
When the app disappears, android thinks it's missing, but some files think it is still installed.
Regularly when you install an app over itself, there is a notice telling you that the application info will remain. That's where the problem lies once an app mysteriously disappears. Because part of it is still installed.
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.:good:
Delete it
Install the application, it'll work, trust me. :fingers-crossed:
Now replace it with your copy.
Done.
Stop factoring resetting if you don't want to. Of course, if you have a lot missing, it might be better. :crying:
If someone can automate this process by making something check the com.address to installed apps, that would be awesome. :highfive:
Click to expand...
Click to collapse
Didn't work for me. I'm using the Skyrocket CM 10 and gapps didn't flash youtube, maps, or gmail. I searched the phone directory and deleted each file. I still get the same error. Should I reflash gapps?
Thanks
maxlax1592 said:
Didn't work for me. I'm using the Skyrocket CM 10 and gapps didn't flash youtube, maps, or gmail. I searched the phone directory and deleted each file. I still get the same error. Should I reflash gapps?
Thanks
Click to expand...
Click to collapse
are you looking in /sdcard/data/data or /sdcard/android/data?
jurassic512 said:
are you looking in /sdcard/data/data or /sdcard/android/data?
Click to expand...
Click to collapse
exactly how do i go about getting to the data/data on my phone? i'm stuck there... thanks
It didn't work for me. =( I'm trying to install an app I used to have before. I don't have it anymore and was trying to reinstall it.
Great!
Thanks
Stuck
jurassic512 said:
are you looking in /sdcard/data/data or /sdcard/android/data?
Click to expand...
Click to collapse
mr-dunbar said:
exactly how do i go about getting to the data/data on my phone? i'm stuck there... thanks
Click to expand...
Click to collapse
I'm also stuck. I was able to go to sdcard/data, but there is no second /data folder.
I have this issue with Swiftkey and there is no 'data/data/' folder, checked both root and sdcard and hidden files are shown ...
Edit: Configured ES File Explorer to mount partition as writable and gave root access -> files were there now and deleting the one with Swiftkey solved my problem.
Thx
Working!
Thanx, it worked for me too!
I am on X8 with CM10 from NaA!!
goldenninja said:
I'm also stuck. I was able to go to sdcard/data, but there is no second /data folder.
Click to expand...
Click to collapse
Anyone one you know anything about android..!?!?!?!
U need to root first...!!!
Worked for me as well.
You need to use something like ES File Browser with Root access to get to /Data/Data
I'm running into this issue with a bunch of apps that got lost when flashing a newer CM10.1 nightly. I can't access those folders in data/data since ES File Manager is one of the apps that gets this error!
Is there any other way to fix this? I can't install anything, not even Chrome :crying:
It's worked for me, too!
Someone maybe didn't understand the meaning of the thread creater. You must have the root access. Then, open Root Explore and go to "data/data" NOT "sdcard/data/data"
SlimAndwios said:
It's worked for me, too!
Someone maybe didn't understand the meaning of the thread creater. You must have the root access. Then, open Root Explore and go to "data/data" NOT "sdcard/data/data"
Click to expand...
Click to collapse
Yeah, that's awesome, but how do you expect to get to that folder without a file explorer? because you cannot install one.....
Thx mate, perfect!
Qewbicle said:
I don't know the cause. I have noticed that it has happened on different devices, there have been assumptions if it's because of a specific kernel or rom, although it may be, I beg to differ. I feel it is happening during the Android Upgrading Apps # of # process.
I noticed that this error pops up on most of the apps that I had installed, but are not there after my update. So far with me, it happened only to my paid apps, but not all of them.
When the app disappears, android thinks it's missing, but some files think it is still installed.
Regularly when you install an app over itself, there is a notice telling you that the application info will remain. That's where the problem lies once an app mysteriously disappears. Because part of it is still installed.
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
:highfive:
Click to expand...
Click to collapse
Figure it out?
gastonw said:
Yeah, that's awesome, but how do you expect to get to that folder without a file explorer? because you cannot install one.....
Click to expand...
Click to collapse
I've got the same problem. Root explorer is one of the apps I didn't get back and ES won't give me access to data/data, and I am rooted BTW
---------- Post added at 06:47 PM ---------- Previous post was at 06:26 PM ----------
tt100b said:
I've got the same problem. Root explorer is one of the apps I didn't get back and ES won't give me access to data/data, and I am rooted BTW
Click to expand...
Click to collapse
In case it might help someone else I thought I'd pass along what I just did to fix the problem. I booted into recovery and found the com.speed.... file for root explorer that way and deleted it and then rebooted. I then was able to load and install root explorer from the play store and now I can sit back and delete all the rest of the apps that won't install correctly...
I guess I could have done it from recovery also but I forgot to write them all down before I rebooted!
Qewbicle said:
I don't know the cause. I have noticed that it has happened on different devices, there have been assumptions if it's because of a specific kernel or rom, although it may be, I beg to differ. I feel it is happening during the Android Upgrading Apps # of # process.
I noticed that this error pops up on most of the apps that I had installed, but are not there after my update. So far with me, it happened only to my paid apps, but not all of them.
When the app disappears, android thinks it's missing, but some files think it is still installed.
Regularly when you install an app over itself, there is a notice telling you that the application info will remain. That's where the problem lies once an app mysteriously disappears. Because part of it is still installed.
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.:good:
Delete it
Install the application, it'll work, trust me. :fingers-crossed:
Now replace it with your copy.
Done.
Stop factoring resetting if you don't want to. Of course, if you have a lot missing, it might be better. :crying:
If someone can automate this process by making something check the com.address to installed apps, that would be awesome. :highfive:
Click to expand...
Click to collapse
Worked Like a Charm Thank you for you help
can't find data
used es file explorer with root access can't find data/data
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end
deleted
Hi all,
The latest update has some issues- the OS boots and I am immediately presented with a system.ui has been stopped dialogue. I'm unable to open the app drawer, open an app, open the notification drop-down. The popup appears almost immediately after dismissing. I think the Testers really missed something here.......
I'm going to have to try and locate the previous version and hope I can install it through twrp.
Has anyone else seen this happen?
typhoonikan said:
Hi all,
The latest update has some issues- the OS boots and I am immediately presented with a system.ui has been stopped dialogue. I'm unable to open the app drawer, open an app, open the notification drop-down. The popup appears almost immediately after dismissing. I think the Testers really missed something here.......
I'm going to have to try and locate the previous version and hope I can install it through twrp.
Has anyone else seen this happen?
Click to expand...
Click to collapse
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
rdmack said:
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
Click to expand...
Click to collapse
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Brax33 said:
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Click to expand...
Click to collapse
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
rdmack said:
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
Click to expand...
Click to collapse
I'm not running stock. Other people seem to be having similar issues in the Viper Rom discussion.
Brax33 said:
I'm not running stock. Other people seem to be having similar issues in the Viper Rom discussion.
Click to expand...
Click to collapse
on what rom you are? and you @typhoonikan ?
...and on what rom version you are, still marshmallow I assume.
A logcat will be really helpful.
rdmack said:
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
Click to expand...
Click to collapse
I was unable to install the apks located there in the traditional way. I tried to install them through TWRP via adb push file.apk /system/app but it didn't work. I'm unaware of how to install APKs outside of the system otherwise? Regardless, downgrading, if this method is viable, didn't work. I had to completely wipe clean and start fresh.
Brax33 said:
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Click to expand...
Click to collapse
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
rdmack said:
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
Click to expand...
Click to collapse
The bug doesn't allow the user to enter any screen. So doing this is not an option
j to the 4n said:
on what rom you are? and you @typhoonikan ?
...and on what rom version you are, still marshmallow I assume.
A logcat will be really helpful.
Click to expand...
Click to collapse
Viper 3.5.0. I haven't upgraded to ANdroid 7.0 for reasons.
typhoonikan said:
I was unable to install the apks located there in the traditional way. I tried to install them through TWRP via adb push file.apk /system/app but it didn't work. I'm unaware of how to install APKs outside of the system otherwise? Regardless, downgrading, if this method is viable, didn't work. I had to completely wipe clean and start fresh.
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
The bug doesn't allow the user to enter any screen. So doing this is not an option
Viper 3.5.0. I haven't upgraded to ANdroid 7.0 for reasons.
Click to expand...
Click to collapse
Not sure if HTC is to blame, or we...or you being still on marshmallow.
Next time please post in the viper thread, then I would have seen your post much earlier to debug your issue.
we found the issue.
run:
adb shell settings put system tweaks_hquicksettings Tweaks
..and it will be fixed. when you resetup your toggles, don't pick any of the two sync toggles.
I'll create a flashable zip to remove those soon.
typhoonikan said:
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
Click to expand...
Click to collapse
You should have been able to fix it without wiping by booting to recovery and dirty flashing the ROM.
EDIT: No, this actually won't work. Sorry
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Have this issue on an M8...
Will your fix work on my device too?
Found your solution in the m8 thread...
Thank you sir
j to the 4n said:
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Click to expand...
Click to collapse
Thank You! Flashing this file fixed the issue and saved me a huge headache. Now to take away the HTC Lockscreen app's
"auto update" rights since it clearly can't be trusted.
drumz0rz said:
Thank You! Flashing this file fixed the issue and saved me a huge headache. Now to take away the HTC Lockscreen app's
"auto update" rights since it clearly can't be trusted.
Click to expand...
Click to collapse
read the info on our homepage.
Not sure who is to blame, htc or we.
You can install the update, with either the fix installed or the sync toggles removed.
or you dirty flash the fullrom on top, that way the sync toggles stay working.
..what I'm wondering, why so many people are still on marshmallow...
j to the 4n said:
..what I'm wondering, why so many people are still on marshmallow...
Click to expand...
Click to collapse
There's a few xposed modules I like.
Is nougat really that big a difference? I have it on my tablet and it's very similar to marshmallow.
eoinzy said:
There's a few xposed modules I like.
Is nougat really that big a difference? I have it on my tablet and it's very similar to marshmallow.
Click to expand...
Click to collapse
guiness is also just a usual beer.
Well I like Marshmallow and Nougat. But I don't like Guinness!
If Guinness had Xposed modules then I'd drink it!
I have this problem on my m8 as well. Unfortunately I was not able to solve this problem with your post. I cannot execute the adb command since adb is telling me that my device is offline (I booted into the OS with the screen going on and off).
I also flashed the zip file, but it didn't work out either. I am not sure which version of viper I have (I assume it's the 6.0.1), so I tried different zips but no success...
Could anyone tell me what I did wrong? I really don't want to do a full reset.
obaern said:
I have this problem on my m8 as well. Unfortunately I was not able to solve this problem with your post. I cannot execute the adb command since adb is telling me that my device is offline (I booted into the OS with the screen going on and off).
I also flashed the zip file, but it didn't work out either. I am not sure which version of viper I have (I assume it's the 6.0.1), so I tried different zips but no success...
Could anyone tell me what I did wrong? I really don't want to do a full reset.
Click to expand...
Click to collapse
another way would be to go to twrp->advanced->file manager
navigate to /data/app/ and delete the com.htc.lockscreen folder do the same in /data/data
boot up, then go back to recovery and flash the fullrom on top.
if nothing helps, you can do a twrp backup, then clean flash. Now you can restore your apps and data with titanium backup.
Been looking for a solution to this ! My gf phone had the exact same issue, dirty flashed and still no good etc.
I shall try the packages J posted. Thanks so much!
Sent from my HTC One M9 using Tapatalk
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
j to the 4n said:
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Click to expand...
Click to collapse
Just downloaded this. And it saves as .... File.Bin is that correct ? Thanks
Sent from my HTC One M9 using Tapatalk
Okay I was able to modify /system on android Q beta 2 just fine but on beta 3 I cant do it no matter what I do. Everything I do either results in "invalid argument" or "/dev/block/sda7 is read only" Heres what Ive done so far:
1. Magisk Canary
2. Boot into TWRP and try mounting there
3. Flashing Q again but with -w
4. Custom Kernel
5. Issuing any mount commands I can think of
6. Resetting back to Pie then updating to Q again
7. Relocking the bootloader and then unlocking it again but this time with unlock_critical (for some reason the phone wouldnt let me do unlock_critical before)
Any help would be greatly appreciated, I need access to /system to edit build.prop to get rid of the navbar and to disable carrier provisioning
Also yes I have verified root works, as my kernel manager can modify kernel related settings
I don't have a "fix" for it unfortunately, but I just wanted to let you know you're not alone. I've experienced the same thing. I tried Magisk Stable and Canary, FX Explorer, Root Explorer, ES Explorer, and a couple of other root file explorers, several busy boxes "versions," setting SELinux to permissive, upgrading to beta file explorers in the Play Store, and on and on. Regardless of what I tried, nothing work to make /system read-writable. I can only assume it's a new security "feature" in Q that apps devs are going to have adjust for. I've left a few messages with some of the devs letting them know about the issue.
Unfortunately, in situations like this, most non-XDA, Play Store devs wait until the new version is official before they bother "fixing" their apps. That means it could be several months from now before it works again, unless it's a bug in Q3, which is entirely possible. If that's the case, the maybe we'll get lucky and Q4 will fix it.
In the meantime, coming to that realization was enough for me to go back to Pie. I've got to be able to make manual changes to /system.
I had a really hard time when I tried to Google search this issue. This issue specifically to do with the Android Q beta 3 doesn't seem to be mentioned anywhere that I came across. I'm going to subscribe to this thread. We can use it to post updates on this issue as new betas come out, or if someone actually finds a way to "fix" it.
Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.
all43 said:
Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.
Click to expand...
Click to collapse
Someone mentioned MiX explorer in that thread, did you try that one. I think I looked for it when I was on Q, but couldn't find it. I don't think I checked XDA though. In any event, they posted a link to it. If you're still on Q, try it out and let us know.
Sent from my Moto G6 using XDA Labs
Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me
all43 said:
Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me
Click to expand...
Click to collapse
Someone in the MiX thread said something that makes it's seem like it's a Magisk issue and not a file explorer issue. I've asked them to clarify.
Sent from my Moto G6 using XDA Labs
nice one sharkie, would be a bonus!
Same goes for A10 OTA. There is a updated Magisk 19.4 but still didn't fix /system problem yet.
MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?
adeelsmatrix said:
MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?
Click to expand...
Click to collapse
It's due to a fundamental change in Android Q. Topjohnwu had an article explaining it in more detail somewhere. I wouldn't hold your breath for it to be worked around any time soon. You'll have to make due with Magisk modules to accomplish whatever it is you want to do.
I can try and help you out with whatever it is you want to do, either by giving you a link to a module that already exists, or helping you create your own.
Sent from my moto g(6) using XDA Labs
Here we are folks latest fireos release for the HD10(Suez) (actual 5.6.4.0) MAY 2019
Deodexed
Removed Kindle special offers aka lock screen ad's
pre-rooted with Magisk 19.1
Disabled OTA
Busybox
changelog V2 5/16/19
fix some wonky dhcp related permissions because amazon doesn't know what the fk they are doing
recommend you guys update asap to avoid wonky wifi
/System increased to 1.6GB to accommodate Gapps
there should be no issue upgrading from previous versions but I have not extensively tested that so if you encounter issues do a factory reset
*Gapps Please do not use hacky tools like fire toolbox. Instead, Install Gapps via TWRP as it is the 'right' way to install Gapps (something reinvent wheel.... )
https://opengapps.org/ 5.1 ARM nano package has been tested and confirmed working **
*it may crash once or twice during account setup but it works just fine once you get logged in
please note that play store version of Amazon apps are NOT Compatible with fireOS exercise caution when allowing apps to update it is highly
recommended you turn auto update OFF, or flash a market detatch script failure todo so will result in you losing amazon stock apps!
if you encounter issues with flashing/updating magisk or do not want root flash the stockboot zip there seems to be a wee bit of jank when flashing over an unclean boot image (an example is if you are updating and already have magisk installed)
the same warning as other stock roms apply do not update magisk from magisk manager use TWRP, flashing modules should be fine
DL:
Rom V2: https://www.androidfilehost.com/?fid=1395089523397966787
Magisk https://github.com/topjohnwu/Magisk/releases/download/v19.1/Magisk-v19.1.zip
Gapps: https://androidfilehost.com/?fid=1395089523397966611
stock boot https://www.androidfilehost.com/?fid=1395089523397965517
Tested this and It's working !
Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!
AngryManMLS said:
Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!
Click to expand...
Click to collapse
this is what I get for uploading at 3am
should be fixed momentarily
edit: link corrected
Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.
Kctucka said:
Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.
Click to expand...
Click to collapse
because play services are meant to be installed as a /system app
it will also survive a factory reset
sideloading the apk's can also lead to weird bugs
WiFi? How did you avoid dhcp errors?
DragonFire1024 said:
WiFi? How did you avoid dhcp errors?
Click to expand...
Click to collapse
that was _fixed_ in like 5.6.3 ?
edit apparently it was not fixed
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup and it still randomly disconnects sigh ...
I guess it better look into seeing why its doing that
edit fixed rom updated
Legitsu said:
that was _fixed_ in like 5.6.3 ?
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup
you can also just chmod 755 the configs
i may experiment with replacing the dhcp binaries with ones built from source at a later date
Click to expand...
Click to collapse
I'll have to make a test build and seeif that's what the case was. If so I could kick myself repeatedly. I have a 64 bit build built for this thing, built from AOSP. I have yet to test it. But if you need any of the bins for it, I have them.
deleted see next post for fix to all wifi problems
attached is example updater script
ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away
Legitsu said:
ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away
Click to expand...
Click to collapse
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
and
chmod 555 /system/etc/wifi_log_levels.sh
I am updating the installer script todo this for you reuploading rom gimme a few
Legitsu said:
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
I am updating the installer script todo this for you reuploading rom gimme a few
Click to expand...
Click to collapse
I think it's time we checked the permissions in other files this might be worth a shot at fixing the rest of the problems these things have with Wi-Fi.
Edit: has anyone uninstalled the wifi locker app yet? The only thing it has permissions to do is upload and store credentials or something to that nature but I don't think it has anything to do with storing Android credentials.
DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
some of these daemons are executed under a different group which leads to issues
this occurs even on a virgin untouched tablet
I should have posted this a long time ago I have known about it for a year just have not had time lol
Legitsu said:
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
Click to expand...
Click to collapse
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.
DragonFire1024 said:
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.
Click to expand...
Click to collapse
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon
rom updated op updated
amazon made aware of the problem hopefully will get fixed so you don't need to root your device to have wifi that works
Legitsu said:
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon
Click to expand...
Click to collapse
It would make sense if they wanted to throw off whoever could successfully pull off deodexing. It wasn't easy pre twrp. I had to do it piece by piece, and only some of the manually replaced ones worked. But you are right I've never seen those files with 555 before.
Sent from my Droid Razr M using XDA Labs
DragonFire1024 said:
It would make sense if they wanted to throw off whoever could successfully pull off deodexing.
Click to expand...
Click to collapse
Lol. Do you seriously think some engineer at Amazon (or whomever they contract with) is charged with scheming up bizarre ways to throw off the miniscule community of deodexers? Too much daytime TV.