Develop Bugs

[Scripts]Build.prop Scripts - OnScreen Keys - Model Edits

Fix Model
This will install a script to fix ro.product.model, CM 10.1 uses GT-N7105 for the model this can cause a few issues with play store and what not. It also shows on xda app and tapatalk. With nightlies coming out every night its a pain to keep changing build.prop to fix so just flash this and run one command then you are set. This will help those not sure or wanting to manually edit build.prop.
This will work for any rom but it seems this issue is only on CM 10.1 because they are supporting other carriers too.
Usage:
Flash in recovery right after flashing/updating CM
Open up terminal emulator and type su be sure the $ changes to #
Then type fixit
Reboot
Profit !
On a side note you can make model whatever you want by editing the script /system/bin/fixit, change SGH-I317 to whatever you want it to be...
Enable/Disable OnScreen Keys:
These scripts will enable or disable onscreen navigation keys.
Usage:
Flash zip in recovery right after flashing/upgrading cm
Open terminal emulator type su be sure $ changes to #
Type keyson to enable onscreen keys or keysoff to disable them
Reboot
Profit !
Note: These will work with ANY rom Touchwhiz or AOSP builds !!

Re: [FIX]Build.prop Fix Script for CM 10.1
what does this fix
Sent from my GT-N7105

dkotoric said:
what does this fix
Sent from my GT-N7105
Click to expand...
Click to collapse
Just what it says it does...it names the phone correctly in the build prop files. .or whatever you want it to while flashing CM nightlies or any other rom
Mac

Works Beautifully
I have tried this on several different installs - and it works beautifully each time. Thanks for your help with this - a great tool for those 'Flashaholics' amoung us who need to be able to re-identify their phone - thanks again -

Added scripts to enable/disable onscreen keys

It gives me an error message saying: permission denied. The terminal has root and the $ did change to #. Any ideas?
Edit: this was the OnSreen Keys script

Getting permission denied trying to use this on CM10.1 latest

abduleo77 said:
Getting permission denied trying to use this on CM10.1 latest
Click to expand...
Click to collapse
On which script ?
Sent from HERE......

Currently running JellyBam 4.2.1 and having trouble getting voicemail to work. Would flashing this, changing my model name back to I317, possibly create a fix?

Fixed the permission problems in the OP redownload the build.prop.onscreen.keys and flash i didnt set the perms in the zip sorry
Let me know if it fixed the issue please.
Careyst said:
Currently running JellyBam 4.2.1 and having trouble getting voicemail to work. Would flashing this, changing my model name back to I317, possibly create a fix?
Click to expand...
Click to collapse
Maybe. it's worth a try let me know if it works....

smokin1337 said:
Maybe. it's worth a try let me know if it works....
Click to expand...
Click to collapse
Well, I don't think it fixed the voicemail issue. I had to call ATT to get it working. I did go through the instructions with terminal emulator and my correct model is showing now. Thanks for this fix!!

Seems to have fixed the problem! Thanks.

smokin1337 said:
Fixed the permission problems in the OP redownload the build.prop.onscreen.keys and flash i didnt set the perms in the zip sorry
Let me know if it fixed the issue please.
Maybe. it's worth a try let me know if it works....
Click to expand...
Click to collapse
On JellyBam now, but definitely keeping this for when I go back to a TW rom.
Thanks for making this!
Side note-- u know of a way to way to script a change the navbar height?
I usually decomp framework-res, and edit the dimens.xml, but wondering if u knew a diff way.
I know this would make it non-universal, but was just curious.

OP, is it possible to get PCs to recognize our phones as 317 instead of 7105? If there's a way, I'll be all over it.
I unfortunately heavily rely on Kies to sync my Outlook contacts with my phone, and no, I don't like having my contacts only in GMail and running the risk of my address book going blank somehow if data or reception in general cuts out for me, since if that ever happens, I can at least use my phone as an address book to make phone calls through another device. And Kies doesn't seem to want to finish "establishing connection" with my phone... :\

BlackPhantomX said:
OP, is it possible to get PCs to recognize our phones as 317 instead of 7105? If there's a way, I'll be all over it.
I unfortunately heavily rely on Kies to sync my Outlook contacts with my phone, and no, I don't like having my contacts only in GMail and running the risk of my address book going blank somehow if data or reception in general cuts out for me, since if that ever happens, I can at least use my phone as an address book to make phone calls through another device. And Kies doesn't seem to want to finish "establishing connection" with my phone... :\
Click to expand...
Click to collapse
Just FYI, once your contacts are on Google and synced with the phone they won't ever disappear, on the phone or online, unless you delete the account or make changes. Even with no connection you can view them on your device, and they can be exported to a csv file if you want an actual hard-list on your computer as well as the phone. I made the switch from outlook about a year ago & have never looked back. Although I did set up a separate Google account so their location & ad data doesn't ever mingle with my contacts.
Sent from my Note 2

This is the new version of this mod
http://forum.xda-developers.com/showthread.php?t=2114993
Please head over there
Sent from HERE......

[ROM] Marshmallow for Nexus 10

Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10

My nexus 4 and nexus 10 are happy today thanks to you.

dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.

jase33 said:
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.
Click to expand...
Click to collapse
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.

dmitrygr said:
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.
Click to expand...
Click to collapse
thanks

For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root

Used these gapps, follow the instructions though, use "touch 'filename' " in TWRP terminal for the file creation. Gapps on 6.0 is struggling right now, but these instructions worked for me.
EDIT: Forgot the link. http://forum.xda-developers.com/and...le-apps-minimal-edition-t2943330/post63226314

Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.

billyx1 said:
Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.
Click to expand...
Click to collapse
did you erase all data and cache when flashing?
if no, nothing i can do - i do not support that
if yes send me logcat

peachpuff said:
For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root
Click to expand...
Click to collapse
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.

it is a userdebug image, so at least in adb you have root

Amazing piece of work. Gonna try it as soon as a reliable gapps package is out!

dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Woot nice!
Could you share your device tree ?
edit thx for sharing :
I was having the bootloop at google logo and couldn't figure out what to do.

great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?

phonetec said:
great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?
Click to expand...
Click to collapse
home softbutton in systemui (the middle one)

dmitrygr said:
home softbutton in systemui (the middle one)
Click to expand...
Click to collapse
Ok I tried that and nothing happened, maybe I was using it wrong, I'll try again later when I get home
Sent from my SM-G925P using Tapatalk

I think I might cry. Flashing now.
---------- Post added at 11:12 AM ---------- Previous post was at 10:42 AM ----------
corumuk said:
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.
Click to expand...
Click to collapse
Maybe we need a kernel that supports root. That's how it is on the Nexus 5 anyway. I don't know if any of the lollipop kernels would work on this. Maybe I'll try that sometime soon.

Just an FYI.....
Updating Google Play Services (required for YouTube) sends it into a FC loop.

Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?

fifthelement said:
Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?
Click to expand...
Click to collapse
I've noticed it has been pretty quick. Did a full wipe and used the system.img from his website. Used these gapps. https://github.com/XorgMC/gapps-mm/releases/download/v1-mini/gapps-mm-mini.zip
Also, if you use those gapps it will say it failed if you try to restore your apps. Hit skip and it will say restoring. It will take a long time to install the apps. If you lock the screen and then unlock it swiping from the side to open the google app you can use the device while it restores your apps.
I havent had any issues related to the rom, just the gapps. Google app fails when i try to search something.

Gravity box running on marshmallow 6.0.1

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

zANTI & nmap

Hello XDA,
I can't seem to get zANTI(the merged version of dSploit) to work properly. When it scans my network in it's initial auto mode as well as in its nmap mode no open ports are detected nor are any operating systems. Conversely cSploit see open ports and operating systems, as does fing.
I'm guessing that this is a problem with the nmap binary however I'm not entirely sure how to go about installing it. I've read the various instructions online without luck. I wish we had apt or were able to use a standard makefile! (maybe we can... I've never tried)
Does anybody have any idea how to fix this? It's kind of annoying because zANTI seems like a great pentesting tool. I just don't want to play around too much as I've broken my Android installs in the past!
-MeeGz
EDIT: I'm curious if systemless root has anything to do with this... Also, I've noticed that there is no bin in /sdcard/opt/nmap-6.46(I'm in the process of installing 7.12)

EDIT: Meh... Turns out that it was bad permissions in /data/data/com.ziperium.zanti/files/nmap
I actually replaced the nmap binary with a newer version and then replaced it with the older binary before realizing that the permissions were fubar'd... Good thing I installed 'MiXplorer' because 'ES' wouldn't even show me the directory. I've never had to play with an apps file's in the past....

How did you fix it?
Also have you tried cSploit.org
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
MeeGz said:
EDIT: Meh... Turns out that it was bad permissions in /data/data/com.ziperium.zanti/files/nmap
I actually replaced the nmap binary with a newer version and then replaced it with the older binary before realizing that the permissions were fubar'd... Good thing I installed 'MiXplorer' because 'ES' wouldn't even show me the directory. I've never had to play with an apps file's in the past....
Click to expand...
Click to collapse
I have not been able to get zanti or cSploit to work like they did back on 4.4.4

I can't really help you with cSploit because I haven't had any issues with it. With zANTI just go to the above mentioned directory and make sure that everything you need is executable and that the "owner" matches the correct app id. A word of advice though; use "miXplorer" to browse for the files and makr sure that you're rooted before attempting any of this...

I put 755 permissions on all files in that directory. All files have the same owner and group app ID, but still I can't get open ports in Zanti.
Can you be more specific.
Thanks!
Sent from my ONEPLUS A3003 using Tapatalk

Did you find any solution?
I have the same issue on my lg v10.
Thank you

Yeah, having the same problem with my 3T. Tried fixing the permissions to the app but with no success.

Still no info on a fix? Same issue on zanti 2.5, S8+ , Nougat.
Batman ROM and kernel. Aswell as OP3 on MM and nougat. This issue has been around for a LONG time. I was told by Zimperium that this is known issue and would be fixed with the next major update. This was at version 2.4.

Android Q beta 3 wont mount /system as rw

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