rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?
Make sure AVB verity is unchecked in magisk then reinstall from the app
qman66 said:
rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?
Click to expand...
Click to collapse
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion
virtyx said:
Make sure AVB verity is unchecked in magisk then reinstall from the app
Click to expand...
Click to collapse
It's always been unchecked
billyt1 said:
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion
Click to expand...
Click to collapse
Ok I'm willing to do this. What module do I download exactly?
qman66 said:
It's always been unchecked
Click to expand...
Click to collapse
Strange
That's the only thing I know that could cause you're issue
Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...
CyberpodS2 said:
Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...
Click to expand...
Click to collapse
ok does anyone know?
bump
qman66 said:
ok does anyone know?
Click to expand...
Click to collapse
What exactly is the question?
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
I think it needs to be done "systemless" with a magisk module. Maybe if you ask @Tulsadiver nicely, he might be able to give you a template or even make you up what is needed. If so and it's possible others might have used for it you could share it.
qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
You are welcome to try this. Put your file in the vrtheme/system/bin folder. Leave the system folder alone. This is untested.
qman66 said:
Ok I'm willing to do this. What module do I download exactly?
Click to expand...
Click to collapse
BusyBox is the module I always use
Related
Hi,
I'm studying how PackageManagerService works, and i noticed that if an application was downloaded to /data/app i can access the file and open inputstream .
but if APK was downloaded to SD card, i can't access the file from PackageManagerService.
is there something i can do?
I want to be able to read the APK before it get installed...
Thanks,
pi.publicSourceDir = apk file path
pyler said:
pi.publicSourceDir = apk file path
Click to expand...
Click to collapse
not sure i follow you.
I'm in the packageManagerService context, i don't have PackageInfo (the application is still not installed)
You could hook PermissionGranter and give the process extra permissions, or see where the system is actually parsing the APK's manifest before installing it.
GermainZ said:
You could hook PermissionGranter and give the process extra permissions, or see where the system is actually parsing the APK's manifest before installing it.
Click to expand...
Click to collapse
Thanks, what I don't understand is, if i give my xposed module permissions to read external storage, why does it still can't read it?
shnapsi said:
Thanks, what I don't understand is, if i give my xposed module permissions to read external storage, why does it still can't read it?
Click to expand...
Click to collapse
They're different processes.
http://forum.xda-developers.com/showpost.php?p=55332926&postcount=9
http://forum.xda-developers.com/showpost.php?p=55186575&postcount=2
GermainZ said:
They're different processes.
http://forum.xda-developers.com/showpost.php?p=55332926&postcount=9
http://forum.xda-developers.com/showpost.php?p=55186575&postcount=2
Click to expand...
Click to collapse
So just to make sure I understand, I can create a service and run it from the hooked method and it should work?
if so, i have another question
How can i stop the original method from running until a point i allow it to continue?
Thanks GermainZ !
shnapsi said:
So just to make sure I understand, I can create a service and run it from the hooked method and it should work?
Click to expand...
Click to collapse
I don't understand how you read that from my reply, to be honest. Here's what I meant:
Hooked code *is not* run as your app. The hooked code is run as the hooked app.
If the hooked app can't do X, then the hooked code can't do X either.
Your app's permissions do not affect the hooked code in any way, only normal (not hooked) code.
shnapsi said:
How can i stop the original method from running until a point i allow it to continue?
Click to expand...
Click to collapse
Using the normal ways you'd normally use if it weren't an Xposed module, in the beforeHookedMethod hook. I'm not familiar with the exact methods, you can look that up. Just be aware that blocking it for too long will cause an ANR.
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Shtiff1 said:
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Click to expand...
Click to collapse
maybe it is enough if you download the module-template edit config.sh and module.prop to an ID if your choice and in config.sh also the REPLACE part with /system/app or priv-app/Lockscreen/ ?
something like this maybe? but here ends my know-how
Shtiff1 said:
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Click to expand...
Click to collapse
First, that's not a donation you're talking about, it's a bounty.
Second, if it can't be done without Xposed, it can't be done with Magisk. So don't hold your breath.
wiQbold said:
maybe it is enough if you download the module-template edit config.sh and module.prop to an ID if your choice and in config.sh also the REPLACE part with /system/app or priv-app/Lockscreen/ ?
Click to expand...
Click to collapse
What? I don't think you understand what the REPLACE part of the config.sh file does.
During installation, that little entry puts a file called "replace" in each folder listed, in the module folder structure. Every time Magisk mounts a module and finds that file it will completely wipe (systemlessly, of course) the corresponding folder in /system.
If you want to replace a file on your device with one you've edited, all you have to do is to put that file in the module zip, under the same folder structure it can be found on your device. After that Magisk's Magic Mount will do it's thing...
Didgeridoohan said:
First, that's not a donation you're talking about, it's a bounty.
Second, if it can't be done without Xposed, it can't be done with Magisk. So don't hold your breath.
What? I don't think you understand what the REPLACE part of the config.sh file does.
During installation, that little entry puts a file called "replace" in each folder listed, in the module folder structure. Every time Magisk mounts a module and finds that file it will completely wipe (systemlessly, of course) the corresponding folder in /system.
If you want to replace a file on your device with one you've edited, all you have to do is to put that file in the module zip, under the same folder structure it can be found on your device. After that Magisk's Magic Mount will do it's thing...
Click to expand...
Click to collapse
right. my consideration was to wipe the lockscreen folder in system to disable it
wiQbold said:
right. my consideration was to wipe the lockscreen folder in system to disable it
Click to expand...
Click to collapse
Ok. In that case I believe you haven't quite understood the request...
Didgeridoohan said:
Ok. In that case I believe you haven't quite understood the request...
Click to expand...
Click to collapse
that could be true. do not have any device older then nougat and can t try the xposed-module.
thought it disable only the lockscreen.
wiQbold said:
that could be true. do not have any device older then nougat and can t try the xposed-module.
thought it disable only the lockscreen.
Click to expand...
Click to collapse
From what I can tell it disables the lockscreen while tricking apps that require a lockscreen into thinking it's enabled.
Easy-ish with Xposed, impossible with Magisk unless you manually edit the app in question to not detect the lockscreen state and then use a Magisk module to mount it to your device.
Didgeridoohan said:
From what I can tell it disables the lockscreen while tricking apps that require a lockscreen into thinking it's enabled.
Easy-ish with Xposed, impossible with Magisk unless you manually edit the app in question to not detect the lockscreen state and then use a Magisk module to mount it to your device.
Click to expand...
Click to collapse
That is correct. When i opened phone before it just had swipe up to open. Now I have to enter lock code every time. I haven't done anything with adb before, always do everything from the phone. I've seen the apk "exchangenopin" but I can't try it, cause I can't download the apk anywhere. Those from other thread seem to go to ad sites. I figured that it wouldn't of been that difficult because the exchangenopin "supposedly" works w/o Xposed. That's why I was hoping for a module. I found something to replace my "insert custom text" module from Xposed, now just need something to replace for lockscreen. Lol. Liking Magisk though.
I experienced the same problem with my realme 5i smartphone, I tried to install the latest Magisk via the OrangeFox recovery because I had never rooted my smartphone before. but I have installed pixel 5 archipelago project. In this case, after installing magisk and successfully entering the lockscreen, here the problem occurs because I can't enter the lockscreen PIN and can't do anything, I can't even turn off my phone. But here I found a solution, namely using a google account and trying to wipe data via the Google Play application, namely find my devices and then delete it there and it worked for me
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
eXtremeDevil said:
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
Click to expand...
Click to collapse
you can get it working pretty easilyg without a module having to be installed, just install it like a normal app on your phone and then put the file it makes after it installs into the magisk.img (while its mounted) in the post-fs-data folder.
It will look like this:
/magisk/.core/post-fs-data.d/0000liveboot
the contents of my working 0000liveboot script is:
#!/system/bin/sh
/system/bin/sh /data/user_de/0/eu.chainfire.liveboot/files/liveboot &
If for any reason the file called is not in that spot, you'll gave to find it manually and change the script to reflect where it is on your particular phone. Possible locations might be /data/user/0/ or /data/data/
Best case is you can just use the 0000liveboot script exactly like I have it. Try that first. If you have no log overlay next boot, you'll have to did where the I installed liveboot app you have is keeping its data and simply change the script so it reflects wherever you find it, then try rebooting again and it should work!
I should mention I'm using v1.60 of chainfire's app
the attachment here is just the script that I know works, just in case anyone wants it.
Sent from my LG V20 using XDA Labs
Thanks, I'll try and tell you. And nice signature by the way haha
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Didgeridoohan said:
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Click to expand...
Click to collapse
How? I don't know exactly what you mean
eXtremeDevil said:
How? I don't know exactly what you mean
Click to expand...
Click to collapse
All the LiveBoot app needs is a working init.d. If your ROM doesn't have that already, the easiest way to achieve this with Magisk is to symlink /magisk/.core/post-fs-data.d to /system/etc/init.d.
I haven't tried it myself, but you should simply be able to install the init.d linker module, reboot, install LiveBoot and then let it do it's thing. Nice and systemless.
Reading your previous posts again I see that the app already has asked to install the script, meaning you already have init.d support. Why not just let it install the script? If you have init.d you don't have to worry about official OTAs anyway and it is very unlikely it'll trip SafetyNet (if that's what you're worried about). Or, just use the above mentioned module.
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
eXtremeDevil said:
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
Click to expand...
Click to collapse
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Rhaegar85 said:
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Click to expand...
Click to collapse
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Thanks.Yes, I have. Found the path and managed to create a symlink, still not working. I used sdmaid to move files and Mount the partition and terminal to symlink.I am using MI 5 Gemini with ViperOS 3.1. Can this be done on my device?
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Thanks for your help. Yes, I had the file on that path. It was not working even after moving the 0000liveboot file to magisk/.core/post-data-fs.d. I have now done a clean install of Viper with SuperSU rather than magisk. And now it's working like a charm. I never had the liveboot working with Magisk except for test run. Thanks for your help.
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Hi,
Yes, sorry, I moved the file to magisk/.core/post-fs-data.d, and created a symlink as well, but it was not working. And I really don't want to leave viper or liveboot either, so I installed SuperSU. But can this be done using Magisk? I am using mi5 Gemini, Viper OS 3.1.1. Thank you again.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Ha! Finally it's working now on magisk . I copied the liveboot file in magisk directory and installed init.d linker on magisk. Instead of creating a symlink using terminal, just moved the initlinker.sh file to the original source and Bingo! Thank you very much mate. I almost lost hope using liveboot with magisk. It was possible for you, THANK YOU?
(Magisk 15.1 / init.d enabler v2.2 , LiveBoot v1.6 )
I can also confirm that the Official Liveboot v1.60 from Playstore in combination with Magisk 15.1 works as soon as it finds a working /system/etc/init.d.
The Linker Modul does its job as expected by Didgeridoohan.
The Test Run works perfect.
When i boot up the phone i can see that Liveboot starts, as the screen is flickering shortly in the transition from Boot-Bootscreen and System-Bootscreen (same logo).
But the scrolling liveboot log itsself just shows up for half a second, when the boot screen switches to "home" respective Lockscreen respective the launcher.
From the previous state (SuperSu/Magisk 12) i know thats it is supposed to appear very soon on the screen.
The liveboot option "overlay on top of the boot animation" changes the appearance of that mentioned half second, but not the timing of the appearance.
Any ideas ? Which Logs ?
Thanks, Greets and a happy 2018
Just put the (liveboot) script in /magisk/.core/service.d, works like a charm.
Confirmed !
Now works like expected. Thank you !
Any way to get this to work on pixel 2 xl ? I tried the above and it fails The closest ive gotten so far is the google logo changed to an android one and the test on the liveboot app works.
Im confused I tried all the steps again but from fromflash fire and it failed, but flash fire itself reboots and scrolls the catlog while its flashing. ( think it reboots twice )
Exist an easy way to export magisk module list? Export and import?
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Didgeridoohan said:
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Click to expand...
Click to collapse
only the one i have installed. full list for backup / reinstall purpose. installed and not active. xposed ha a function to export /import list. I like it.
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
simona70 said:
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
Click to expand...
Click to collapse
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Thanks. Providential.
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Where are the ZIP files located, in case I just want to backup those rather than the img?
oroboros74 said:
Where are the ZIP files located, in case I just want to backup those rather than the img?
Click to expand...
Click to collapse
Zip files are not saved. It gets extracted in to the location as mentioned in this thread. But each time you flash a module the zip file is downloaded in to Download folder of your internal storage. Save it for future use.
Now /data/adb/magisk.img is no more used... What folder must I backup?
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
Hi how can i find data/adb/magisk/img
Sk7007 said:
Hi how can i find data/adb/magisk/img
Click to expand...
Click to collapse
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Didgeridoohan said:
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Click to expand...
Click to collapse
How to backup now then?
Sent from my motorola one power using Tapatalk
Always wondered the same..
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
rodken said:
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
Click to expand...
Click to collapse
I actually havent tried it since the change from the img method
I can tell you i do backup and restore the magisk.db file....i have a Galaxy Active2 Watch, and if it even sniffs root i have to reset the watch and start over to get Samsung Pay working. So i flash the ROM/GApps, then Magisk, reboot and setup the ROM and Magisk, set my Android ID back to the previous one (to avoid having to reset the Watch, and have it connectable in Gear app) then copy the magisk.db to /data/adb, then reboot. Then enable MagiskHide, and hide Magisk Manager. When i restore my apps the Samsung ones are already in the MagiskHide list and Samsung Pay works as before, once i reconnect the watch.
Next time i flash ill try copying back the /data/adb/modules and let you know
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
73sydney said:
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
Click to expand...
Click to collapse
Thanks for the update.
So like a total dumbass I didn't check the source and downloaded a module (fde.ai) from magiskroot.net . Seemed to install fine, boot took a bit longer than usual, after boot the module was not listed in Magisk manager.
Is that site safe?
Thanks!
PS I guess I'm asking opinions about the specific site...
I would investigate and open the zip and look what it changes? Did you install it in recovery or in magisk?
I don't know that site.
McFlypants said:
I would investigate and open the zip and look what it changes? Did you install it in recovery or in magisk?
I don't know that site.
Click to expand...
Click to collapse
In Magisk. I'm trying to search for added files in the system right now, nothing found so far. I have also opened the zip (just before your reply) but I'm not sure I'll be able to decipher...
krakout said:
In Magisk. I'm trying to search for added files in the system right now, nothing found so far. I have also opened the zip (just before your reply) but I'm not sure I'll be able to decipher...
Click to expand...
Click to collapse
a magisk module wouldn't change system files it'll just create a folder in data/adb/modules so look there for strange folders
jons99 said:
a magisk module wouldn't change system files it'll just create a folder in data/adb/modules so look there for strange folders
Click to expand...
Click to collapse
Only the few, known modules there. Should I assume I'm ok then?
krakout said:
Only the few, known modules there. Should I assume I'm ok then?
Click to expand...
Click to collapse
not sure it might have done something else like put a script that magisk run on boot or something maybe send me this module in pm and I'll look at what's in there
Sure thing, thanks. Also, here is the Magisk log:
jons99 said:
not sure it might have done something else like put a script that magisk run on boot or something maybe send me this module in pm and I'll look at what's in there
Click to expand...
Click to collapse
Sure thing, thanks. Also, here is the Magisk boot log: