Related
Hi and thanks for the help, well after i install ginger dx v10, everithing works good, but the multitouch and the overclock doesn´t work, or maybe i don´t know how to make it work.
But when i try to use this module and go to edit mi hw_config.sh i found this:
# modules
insmod /system/lib/modules/ax8_smartass.ko
insmod /system/lib/modules/ax8mt.ko
insmod /system/lib/modules/x8oc.ko
(in the middle of some other stuff)
so i have three modules but how do i know if them are working or not?
1)multitouch doesn´work in any app or game
2)i didn´t see the option for overclock
3)i found the options for smartass but i really don´t understand it at all
Sorry for mi bad english, and thanks for everything in advance.
Overclock and other modules are not pre-installed in GingerDX.
Download the modules from there thread home, and use adb to push them to
/system/lib/modules/
thanks now i know the modules are not in the rom, but can i install cy8ctma300 module even if my hw_config.sh other shows these modules # modules
insmod /system/lib/modules/ax8_smartass.ko
insmod /system/lib/modules/ax8mt.ko
insmod /system/lib/modules/x8oc.ko
thanks for the help again
Hi all!
Surfing a bit into XDA, I've created this mod in order to add to Froyo/GB/CM7 the way to access CWM on boot pressing any hardware keys.
Once installed, to access recovery you only have to repeatedly press any hard key; it works like eRecovery in Nova ROM.
In order to install/remove it, you only have to flash it via CWM, so you need CWM recovery installed at your OB.
V20B:
Installer: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-V20B.zip
Remover: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-remover-V20B.zip
V20N:
Installer: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-V20N.zip
Remover: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-remover-V20N.zip
CM7:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-CM7.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-CM7.zip
Stock V10D:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-V10D.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-V10D.zip
Stock V10E:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-V10E.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-V10E.zip
PD: This stuff will probably work flawlessly in other stock rom versions, but to ensure that it will work, send me your /system/bin/pvrsrvinit file indicating your ROM version and I will create a specific .zip for this version. Thanks pbog1 for the file.
Credits go to knzo and D4rKn3sSyS.
If you find this useful, please thank it!
Regards.
No need to nandroid before install it... is fully probed.
Regards!
Suggestion: Information about CWM version?
It only changes one file at /system/bin, then I would suggest to use the latest CWM.
Regards.
It's a bit late on the boot, inject a sooner service.
Yeah, it's still at beta stage.
I though it would be a good point because is just before init.d starts.
I will find the first service and hijack it, but at least this mod can handle framework's loopboots.
Regards!
i'm doing the same thing for 2.3.4
but i was failed.
i hijacked lgdrmserver,no response
can you help me?
Try with another service... I can't say more ATM...
Send me the init.rc
This is great news!! AAMOF, the no-hard-reboot is one of the things that prevents me from flashing these days. Last time I bicked the phone I lost one full day.
I'll install this as soon as it's improved.
Thank you Huexx!
knzo said:
Send me the init.rc
Click to expand...
Click to collapse
sorry i dont know why i can't send you pm,here's link
http://hotfile.com/dl/132897861/3f3e377/init.rar.html
thx
Try to inject: /system/bin/pvrsrvinit.
It's the PowerVR SGX 540 driver and it's earlier in the boot.
Rename it to /system/bin/pvrsrvinit2, then create an empty bash file with that name and inject the command I used on my eRecovery and in the last line (after the keypress check) run /system/bin/pvrsrvinit2 or it won't boot.
got it,try it now thx
Hi all.
Looking at init.rc and according with the suggested service by knzo, why you say that my inject point would be sooner?
sysinit is executed before ueventd, console, adbd, pvrsrvinit, etc... it's before ALL the services, and I haven't to modify it because it's a script by itself.
Regards.
Huexxx said:
sysinit is executed before ueventd, console, adbd, pvrsrvinit, etc... it's before ALL the services, and I haven't to modify it because it's a script by itself.
Click to expand...
Click to collapse
That doesn't even make sense.
You want to execute a sh without console running?
Or why can you see the first init.d in the adb logcat then?
Just because it comes in a previous line doesn't make it start sooner.
Well, if I've understood, the place at init.rc doesn't determines the run order, doesn't it?
Then how can you know which service will be launched the first?
If I hack pvrsrvinit, would it check for keystroke sooner?
Regards.
Depends on the trigger/call.
Pvrsrvinit ought to be sooner indeed.
Ok, let's try it then!
Regards.
it make nosense at all.
i don't know where i did wrong.
hijack pvrsrvinit,and create init.d folder ,write script to make original pvrsrvinit run...
My version doesn't work...
It's strange... later but It sholud run.
**I did not write these scripts, just updated the flashable zip for our x86 Asus phones**
**All work done by @Paget96**
ORIGINAL Mod Thread here : http://forum.xda-developers.com/android/software-hacking/tweak-l-speed-v1-0-02-02-2015-t3020138
@Paget96 has added an x86 version to the original thread with the (more appropriate) fixes!! Go discuss there!
Big thanks to him. Use the v2.4 Test3 or greater "x86" file
Reqs:
1) Need root
2) Need Custom recovery (TWRP)
3) Need kernel with init.d support (like @TheSSJ 's here: http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822)
** Use v44 or greater for proper init.d support
Download zip from the original thread
and flash in recovery.
Then look at the original thread for config options while you're in there
Added the Emergency Uninstaller zip as well. (i think you still need to use this version, until an x86 version is up there too)
Ch-Ch-Ch-Ch-Changes
Jul 23 2015: OG thread updated by dev. Updated flashing instructions in OP (mods can probably lock this thread)
Jul 15 2015: Fixed script to properly set perms on /system/bin/LS; Added Emergency Uninstaller zip
Jul 14 2015: Initial upload. Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
I would have expected that some parts of my kernel would fight against this tweak, nice to see that it seems to work
Yean I don't know that some of the governor stuff is working 100%, still messing around with it .
Thanks man Been using TheSSJ kernel with this pack of tweak. Its awesome Thanks to both of you
Added in index, thanks for updating the mod!
taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
Thanks! Working A++
Edit: I tried running the script from terminal with no luck. I have to cleanup the alpha version first with the provided uninstaller by Paget96. Its a great idea to have the uninstaller zip working with x86.
++Uninstaller patched, permssions fixed, kudos @taylor.fowler
Need help can't get to run in terminal
Sent from my ASUS_Z00AD using Tapatalk
taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
how can i do that because not work for me
Have u guys tried with Kernel Adiutor?
su
LS > permission denied
selinux already permissive
chobztopz said:
su
LS > permission denied
selinux already permissive
Click to expand...
Click to collapse
I've got it too
The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator
lordpipa said:
Have u guys tried with Kernel Adiutor?
Click to expand...
Click to collapse
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
mustatir said:
The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator
Click to expand...
Click to collapse
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .
ansebovi said:
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .
Click to expand...
Click to collapse
Hrmph. I must have Ul'd the wrong version. I had the same issue. Will re-up in a couple hours.
@ansebovi cause u can use it for some of the init scripts.
Hmm, mine does all have logs. Yep, I had to set LS permissions to all in /system/bin folder. I think it might be because I still have the old alpha version files and I can't flash the uninstaller as it needs the x86 code.
Edit: ++Uninstaller patched, permssions fixed, kudos @taylor.fowler
Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file
TheSSJ said:
Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file
Click to expand...
Click to collapse
OK, so I fixed the updater-script (and found another error with setting the permissions on init.d). Apparently I had changed them to 0775 instead of 0755 :silly:
Also added the emergency uninstaller script too.
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...
taylor.fowler said:
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...
Click to expand...
Click to collapse
Bummer...was convinced this would work...twrp code at least shows that it executes updater-binary if present,otherwise it interprets the script itself...
Sorry!
SYSTEM/LESS MODULE TEMPLATE FOR MAGISK
This template is a modified version of the original one.
Its purpose is to make Magisk Modules install in either Magisk (as a module) or directly in /system.
How to use/create a module:
Clone / download this repo
Open config.sh, follow the instructions written at the beginning of the file. You should at least change config.sh and module.prop
Zip your files, the zipped file is a flashable zip for both Magisk Manager and custom recoveries
Please check Notes for precautions
You can make a module from this template almost the same as you can make one in the Original template.
It should be easy to transition from there to here.
ADDITIONAL STUFF
Installation is configurable. It means that you can control on where it installs (system or magisk), and a few other variables that is also important.
For Devs:
Installation is configurable in config.sh. You can control the variables (starting in line 95) that will help you how to configure your module.
Code:
Variables:
[B]MAGISKINSTALL [/B]- forces magisk installation (might conflict with SYSTEMINSTALL) (values: [B]true [/B]or [B]false[/B])
[B]SYSTEMINSTALL [/B]- forces system installation (might conflict with MAGISKINSTALL) (values: [B]true[/B] or [B]false[/B])
[B]INITPATH [/B]- sets path to install scripts (post-fs-data.sh, service.sh) if system install (values: [B]directories[/B])
[B]BUILDPROP [/B]- sets properties from system.prop directly to build.prop (values: [B]true [/B]or [B]false[/B])
[B]PERMANENTDELETE [/B]- PERMANENTLY delete folders in $REPLACE (values: [B]true [/B]or [B]false[/B])
[B]ERROREXIT[/B] - exits with an error on every failed attempt to install to Magisk (enabled by default) (values: [B]true [/B]or [B]false[/B])
set_permissions_system
It behaves like set_permissions, but it sets them on whatever file you want and will be executed in system install only.
System Install
The directories in system folder will correspond to which directory the files will be copied.
Ex. if you put in the zip /system/example.file, it will be copied to /system/example.file.
Click to expand...
Click to collapse
For Users:
If a module is based on this template, you can also configure it's installation.
The variables that is in /dev/.config will overwrite the dev's setting for the module.
Code:
Variables:
[B]MAGISKINSTALL [/B]- forces magisk installation (might conflict with SYSTEMINSTALL) (values: [B]true [/B]or [B]false[/B])
[B]SYSTEMINSTALL [/B]- forces system installation (might conflict with MAGISKINSTALL) (values: [B]true[/B] or [B]false[/B])
[B]INITPATH [/B]- sets path to install scripts (post-fs-data.sh, service.sh) if system install (values: [B]directories[/B])
[B]BUILDPROP [/B]- sets properties from system.prop directly to build.prop (values: [B]true [/B]or [B]false[/B])
[B]PERMANENTDELETE [/B]- PERMANENTLY delete folders in $REPLACE (values: [B]true [/B]or [B]false[/B])
They need to be in /dev/.config to be read by the installer.
To enter them, just create the file and then add.
How to do it on Terminal:
Code:
Example:
echo "SYSTEMINSTALL=TRUE" >> /dev/.config
You can add them in different lines to be valid.
I put it in /dev/.config to make it a temporary file. So whenever a module is flashed, the file will be gone and won't interrupt the installation process of the currently installing module.
Click to expand...
Click to collapse
XDA:DevDB Information
System/Less Module Template for Magisk, Tool/Utility for all devices (see above for details)
Contributors
veez21, topjohnwu
Source Code: [url]https://github.com/veez21/unify-magisk-module-template[/URL]
Version Information
Status: Beta
Current Beta Version: v0.3
Beta Release Date: 2017-06-11
Created 2017-06-11
Last Updated 2017-06-14
Reserved
Reserved
reserved+
UPDATE TO v0.2
commit 3709f37
Changelog:
add more notes
fixed some terms
fix setting PERM
added ERROREXIT variable
added post-fs-data and late_start service scripts notes and better compatibility with system install
Hi veez. I like to know about how to edit default.prop using magisk module. There are somes ro. In default.prop i want to edit. I had seen some module make by others and i look at post-fs-data.sh they edit ro.fingerprint or dpi screen using magisk module it for build.prop. but now i want to edit default.prop . Can u help me how to edit default.prop using magisk module. I search on google some people said that i must to unpack boot.img to edit defaukt.prop thanks before. And I newbie for this magisk module.
Duden17 said:
Hi veez. I like to know about how to edit default.prop using magisk module. There are somes ro. In default.prop i want to edit. I had seen some module make by others and i look at post-fs-data.sh they edit ro.fingerprint or dpi screen using magisk module it for build.prop. but now i want to edit default.prop . Can u help me how to edit default.prop using magisk module. I search on google some people said that i must to unpack boot.img to edit defaukt.prop thanks before. And I newbie for this magisk module.
Click to expand...
Click to collapse
If you just want to set a new value to the prop, it's the same procedure as the modules you've been looking at. Just add the prop and new value to the system.prop file of the module and you're done. Shameless promotion: if you don't want to make a module yourself, my MagiskHide Props Config module can actually set custom props for you.
If you want to edit the default.prop file itself you're going to have to go about the way you found about unpacking the boot image, etc.
Didgeridoohan said:
If you just want to set a new value to the prop, it's the same procedure as the modules you've been looking at. Just add the prop and new value to the system.prop file of the module and you're done. Shameless promotion: if you don't want to make a module yourself, my MagiskHide Props Config module can actually set custom props for you.
If you want to edit the default.prop file itself you're going to have to go about the way you found about unpacking the boot image, etc.
Click to expand...
Click to collapse
Oke. I use ur module man. Its great for people need to change their cts or selinux. Good job :good::good: i will look at to ur magiskhide prop again. Thanks man
Not sure where to post this as I was looking for guide/s on how to create a magisk module for this feature.
iZLeeP said:
Not sure where to post this as I was looking for guide/s on how to create a magisk module for this feature.
Click to expand...
Click to collapse
This isn't. Also this template is abandoned.
You should start here https://github.com/topjohnwu/magisk-module-template
veez21 said:
This isn't. Also this template is abandoned.
You should start here https://github.com/topjohnwu/magisk-module-template
Click to expand...
Click to collapse
That was the first thing I did. I was just looking for additional sources to better understand on how to make a Magisk module as this is the first time I'm doing so. Anyway, thanks for pointing out.
Old topic but this is a great idea, I think a better way of doing this would be automatically detecting if magisk is installed and acting accordingly otherwise install to system..
Hi i want to make auto face unlock module
Could you please help me
and also want to make quick pin unlock module
ntrimurthulu said:
Hi i want to make auto face unlock module
Could you please help me
and also want to make quick pin unlock module
Click to expand...
Click to collapse
Not possible with magisk
Sent from my Moto G 2015 using XDA Labs
DanGLES3 said:
Not possible with magisk
Click to expand...
Click to collapse
Oh sad
---------- Post added at 05:11 PM ---------- Previous post was at 05:11 PM ----------
DanGLES3 said:
Not possible with magisk
Click to expand...
Click to collapse
Do you know other way
ntrimurthulu said:
Oh sad
---------- Post added at 05:11 PM ---------- Previous post was at 05:11 PM ----------
Do you know other way
Click to expand...
Click to collapse
The only way would be a custom ROM or xposed but it only supports up to Oreo and I don't think there's a module for face auto unlock
Sent from my Moto G 2015 using XDA Labs
DanGLES3 said:
The only way would be a custom ROM or xposed but it only supports up to Oreo and I don't think there's a module for face auto unlock
Click to expand...
Click to collapse
Yeah no such module that's why i want to create
BTW thank you
!Magisk is not activated !... abort
! Installation failed
obviously magisk is activated 19.1 ... is this template too old ?
edit: nevermind ... i just edited the zip directly from github so there was a folder in the root of the zip :silly:
Trying to flash the enablestadia zip to be able to play Stadia on my phone.
Had this installed successfully before I flashed EvolutionX ROM yesterday.
The zip installs and everything looks fine until reboot, then it just disappear.
My file system seems to be vfat which should be ext4?
Is this the problem?
See attachment for log.
The zip is outdated:
https://didgeridoohan.com/magisk/Magisk#hn_Cant_install_modules
Didgeridoohan said:
The zip is outdated:
https://didgeridoohan.com/magisk/Magisk#hn_Cant_install_modules
Click to expand...
Click to collapse
Any other way of changing the device id to Pixel?
Aleksanderbjorn said:
Any other way of changing the device id to Pixel?
Click to expand...
Click to collapse
That module just changes the manufacturer and model props to match a Pixel 4, right?
You can do that quite easily with a boot script and the resetprop tool (see the Magisk docs on GitHub for details).
Or you could use the device simulation or custom props features of my MagiskHide Props Config module:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Didgeridoohan said:
That module just changes the manufacturer and model props to match a Pixel 4, right?
You can do that quite easily with a boot script and the resetprop tool (see the Magisk docs on GitHub for details).
Or you could use the device simulation or custom props features of my MagiskHide Props Config module:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
That's right, just changed it to Pixel 4xl.
Will look into this, thanks for the help.