View Single Post
Old 10-30-2022, 04:58 PM   #6
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 3,999
Karma: 18026955
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Mmm, those scripts are not going to work.
Getting ADB going is more than just starting the adbd daemon.
Usually setprop sys.usb.config adb is used, but I believe Onyx screwed around with all that.

If you're using Magisk it does the file shadowing/substitution in init. So any changes are not immediately propagated.

In worst case, you can flash the stock boot image back and there won't be any Magisk. Then you can delete/modify your Magisk module.

Keep it simple, no shell scripts in your Magisk module.
Try something simple like putting system/hello in your module and see if it's visible.
Renate is offline   Reply With Quote