Hello, there.
Objective - Need to have always "adb tcpip 5555" even after reboot.
Got a solution saying that, we have to set "service.adb.tcp.port=5555" in build.prop. I tried all the possible way to mount r/w but couldn't succeed.
Got to know that Android 10 system is always Read only. Checking if we can/have a module in Magisk to r/w the system & edit the build.prop.
Need you valuable help. Thanks in advance.
MagiskHide Props Config By Didgeridoohan. You can find it in Magisk's downloads tab.
Go to adb/data/post-fs-data.d folder, create a new file called "whatever".sh (note the .sh extension).
Then write whatever build prop changes you want in there.
If I remember correctly, this is the easiest way to change build prop and it will run when device starts.
Edit: https://forum.xda-developers.com/7t-pro/help/mount-r-want-to-update-build-prop-t4096033/post82521979
Kevorex1 said:
MagiskHide Props Config By Didgeridoohan. You can find it in Magisk's downloads tab.
Click to expand...
Click to collapse
@vinu4u4ever Here's the link to above mentioned: [MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.2.4 by @Didgeridoohan
Lossyx said:
Go to adb/data/post-fs-data.d folder, create a new file called "whatever".sh (note the .sh extension).
Then write whatever build prop changes you want in there.
If I remember correctly, this is the easiest way to change build prop and it will run when device starts.
Click to expand...
Click to collapse
Almost...
You are correct that what you're suggesting is the simplest way to change props. But the .sh extension isn't necessary, only that the file has the correct permissions to be executable.
And for the contents, you need to use the resetprop tool, so for each prop you want to change you'll have to add this to the file:
Code:
resetprop <prop> <value>
Didgeridoohan said:
Almost...
You are correct that what you're suggesting is the simplest way to change props. But the .sh extension isn't necessary, only that the file has the correct permissions to be executable.
And for the contents, you need to use the resetprop tool, so for each prop you want to change you'll have to add this to the file:
Click to expand...
Click to collapse
Ah, knew I did something wrong when It did not work.
Just tried with the way you described and now it works perfectly, thanks!
FK kernel manager also includes a build.prop editor.
Kevorex1 said:
MagiskHide Props Config By Didgeridoohan. You can find it in Magisk's downloads tab.
Click to expand...
Click to collapse
Thanks for the info.
I'm new to this. Can u share me the steps/info to execute the service thru this props..?
Thank you!
Lossyx said:
Go to adb/data/post-fs-data.d folder, create a new file called "whatever".sh (note the .sh extension).
Then write whatever build prop changes you want in there.
If I remember correctly, this is the easiest way to change build prop and it will run when device starts.
Edit: https://forum.xda-developers.com/7t-pro/help/mount-r-want-to-update-build-prop-t4096033/post82521979
Click to expand...
Click to collapse
Thanks for the information.
Here is the things which I did:
Created an "testing.sh" file under path "data/adb/post-fs-data.d/" & added "service.adb.tcp.port=5555" thru Text Editor.
I don't no how to execute it. In root explorer when I clicked testing.sh it should an option to execute, I click on it but nothing happens...
Code:
D:\Android\Scrcpy>adb connect 192.168.10.111:5555
cannot connect to 192.168.10.111:5555: No connection could be made because the target machine actively refused it. (10061)
I'm new to this. Kindly guide me to execute it.
Oswald Boelcke said:
@vinu4u4ever Here's the link to above mentioned: [MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.2.4 by @Didgeridoohan
Click to expand...
Click to collapse
Thanks for the info.
I'm new to this.
When I accessed this thru terminal, it prompts to update something related to fingerprint. I'm very much new to this. Kindly provide me the steps to execute "service.adb.tcp.port=5555"
Thank you!
vinu4u4ever said:
Thanks for the information.
Here is the things which I did:
Created an "testing.sh" file under path "data/adb/post-fs-data.d/" & added "service.adb.tcp.port=5555" thru Text Editor.
I don't no how to execute it. In root explorer when I clicked testing.sh it should an option to execute, I click on it but nothing happens...
I'm new to this. Kindly guide me to execute it.
Click to expand...
Click to collapse
Check my edit / Didgeridoohan post, he explains what you should do.
And you don't execute it yourself, magisk does when your device boots.
Didgeridoohan said:
Almost...
You are correct that what you're suggesting is the simplest way to change props. But the .sh extension isn't necessary, only that the file has the correct permissions to be executable.
And for the contents, you need to use the resetprop tool, so for each prop you want to change you'll have to add this to the file:
Code:
resetprop <prop> <value>
Click to expand...
Click to collapse
Thanks for the information.
Here is what I did, Kindly review & guide me as I'm new to this:
In terminal,
I executed - "resetprop service.adb.tcp.port 1" also I tried "resetprop service.adb.tcp.port 5555" but still I'm not access it through adb from PC.
By default this service was set to [-1]. Kindly help.
Sorry if I have asked some silly queries.
EDIT: After reboot, the service is set to default [-1]
vinu4u4ever said:
Almost...
You are correct that what you're suggesting is the simplest way to change props. But the .sh extension isn't necessary, only that the file has the correct permissions to be executable.
And for the contents, you need to use the resetprop tool, so for each prop you want to change you'll have to add this to the file:
Thanks for the information.
Here is what I did, Kindly review & guide me as I'm new to this:
In terminal,
I executed - "resetprop service.adb.tcp.port 1" also I tried "resetprop service.adb.tcp.port 5555" but still I'm not access it through adb from PC.
By default this service was set to [-1]. Kindly help.
Sorry if I have asked some silly queries.
EDIT: After reboot, the service is set to default [-1]
Click to expand...
Click to collapse
Think it works be easier to use this app to be honest, that's what I do.
https://play.google.com/store/apps/details?id=moe.haruue.wadb
Lossyx said:
Check my edit / Didgeridoohan post, he explains what you should do.
And you don't execute it yourself, magisk does when your device boots.
Click to expand...
Click to collapse
Thanks.
It worked... We have to restart the adbd service to use the port value.
Thanks Much appreciated.
Lossyx said:
Think it works be easier to use this app to be honest, that's what I do.
https://play.google.com/store/apps/details?id=moe.haruue.wadb
Click to expand...
Click to collapse
Wow... That's simple... Great...
Thanks for app suggestion. wonderful app.
vinu4u4ever said:
Thanks for the information.
Here is what I did, Kindly review & guide me as I'm new to this:
In terminal,
I executed - "resetprop service.adb.tcp.port 1" also I tried "resetprop service.adb.tcp.port 5555" but still I'm not access it through adb from PC.
By default this service was set to [-1]. Kindly help.
Sorry if I have asked some silly queries.
EDIT: After reboot, the service is set to default [-1]
Click to expand...
Click to collapse
EDIT 2: Its working. I had to restart the adbd service in phone to start the tcp port value of 5555.
Thanks for your help.
Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later. Now my system, vendor and product partitions are read-write!
Use at your own risk!
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
Related
NOTE: DO NOT DO THIS UNLESS YOU KNOW WHAT YOU ARE DOING, YOU CAN EASILY SCREW UP YOUR SYSTEM, AND THIS WON'T HELP YOU.
BACKUP FIRST, AND MAKE SURE YOU HAVE A SETUID SH AS ROOT SO YOU CAN RECOVER FROM BACKUPS IF NECESSARY.
First you have to re-sign framework-res.apk using testkeys. This will allow you to use testkeys for system uid packages.
Next step is to re-sign all other apks that use shared uid system.
That is: bootinfo, Fota, GoogleCheckin, GoogleSubscribedFeedsProvider, NetworkLocation, ServiceMenu, Settings, SettingsProvider, VpnServices
Next you have to re-sign all apks that use the platform key, which turns out to be the shared uid phone - these require implicit permissions from the platform like DEVICE_POWER:
TelephonyProvider, Stk, semc-backup-rachael, Phone
Finally, I think GoogleEnhancedSearch also needs it or something otherwise a settings menu will fc.
The nice part about re-signing is that you don't actually need to deodex the files.
One important thing is that in the new versions, the fota.action.DEBUG_ENTRY is actually disabled, and moreover, requires special permissions that aren't granted. This is where re-signing comes in.
Now, you need to deodex fota.apk, modify the manifest to remove permissions required for DEBUG_ENTRY, and finally, force enable the debug menu:
In com/sonyericsson/android/fota/common/fotaview/FotaDebugEntry.smali,
find "debug UI is not available!"
a few lines above, there is if-nez v0 :cond_0
change it to if-eqz v0 :cond_0
This forces it to enable the debug menu.
Now we re-smali the Fota.apk, re-sign, then push it on to the phone along with the rest of the modified packages.
Repush all the files to the phone and it's done
problem !
baksmali gives an error at fota.apk
can you post your deodex scrypt
Why is this required?
TechGuru_x10 said:
Why is this required?
Click to expand...
Click to collapse
So that you won't have to keep re-flashing the older firmware to root (and keep re-installing stuff afterwards), and it should save time in repairing your firmware if you mess system files up.
It should also allow us to upgrade to newer firmwares from the current one, so we don't have to lose all of our apps/settings when rooting our phones again with a newer firmware.
Is this right guys? Anyway, thanks and good luck!
jerpelea said:
problem !
baksmali gives an error at fota.apk
can you post your deodex scrypt
Click to expand...
Click to collapse
You need to add the classpath by deodexing everything in the framework folder and including it.
zephyrix said:
You need to add the classpath by deodexing everything in the framework folder and including it.
Click to expand...
Click to collapse
oki
will try
thanks
found my error
i was using smali1.2.2 tested with 1.2.3 and is working
jerpelea said:
oki
will try
thanks
found my error
i was using smali1.2.2 tested with 1.2.3 and is working
Click to expand...
Click to collapse
Could these steps be made into a script, to run everything at once? Or at least in sections?
Daneshm90's autodeodexer 2.3 modified by me for X10
http://hotfile.com/dl/53736770/16a1bc8/Deodexer_2_3_SE.rar.html
So eventually (with this) we can take a newer build and run this script thus allowing us to then run the files necessary for root?
what do you mean by newer builds like R2BA020
Sorry if Im being a noob but lets say I mess up a framework file and get stuck at the bootscreen. When I try to use adb to push my backup it says permission denied. Will this allow me to make the changes?
Well what I've done is use a modified adb which runs as root and replaces on boot. However, I believe you could use a setuid sh and achieve the same result.
i.e. cp /system/bin/sh /system/bin/rootsh
chmod 6755 /system/bin/rootsh
then you can push to a folder where you can normally write, and use rootsh and move it.
Great thanks, I'm going to wait until I have to try it...
Hi!
I have installed the [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes, but I have no WiFi.
In a previous version was included by default Debugging tool which would allow a terminal to be launched in order to copy the wifi-nvram file from the SD card towards the /data folder.
How to get the Debugging Tool / Terminal in this version ?
Any help welcome !
Thanks,
JM
jsalsa said:
Hi!
I have installed the [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes, but I have no WiFi.
In a previous version was included by default Debugging tool which would allow a terminal to be launched in order to copy the wifi-nvram file from the SD card towards the /data folder.
How to get the Debugging Tool / Terminal in this version ?
Any help welcome !
Thanks,
JM
Click to expand...
Click to collapse
Unfortunately you can't. Use ConnectBot from the Market.
For the wifi-nvram.txt trick why don't you just use the user.conf file to bind mount it? That way you wouldn't ever have to do it again... Do it once, then never worry about it again...
Thanks !
For ConnectBot, this is a SSH client. how to connect locally: localhost I presume, But which login/password?
For user.conf file, I did not know its existence . have added the "cp /sdcard/wifi-nvram.txt /data/wifi-nvram.txt" at the end, let's see if this works at next reboot.
Thanks again !
jsalsa said:
Thanks !
For ConnectBot, this is a SSH client. how to connect locally: localhost I presume, But which login/password?
For user.conf file, I did not know its existence . have added the "cp /sdcard/wifi-nvram.txt /data/wifi-nvram.txt" at the end, let's see if this works at next reboot.
Thanks again !
Click to expand...
Click to collapse
ConnectBot works locally. Instead of SSH, choose "Local"...
Let me know if you need help with the user.conf command. Should work, haven't tried it myself...
Thanks once more.
the user.conf trick did the trick already.
Many thanks !
JMS
jsalsa said:
Thanks once more.
the user.conf trick did the trick already.
Many thanks !
JMS
Click to expand...
Click to collapse
np. Figured that is the easiest method for fixing this... now you can just leave the file on your SD card and user.conf will always mount it for you .
arrrghhh said:
ConnectBot works locally. Instead of SSH, choose "Local"...
Let me know if you need help with the user.conf command. Should work, haven't tried it myself...
Click to expand...
Click to collapse
can u tell me how does user.conf work ? what do i have to do ?
the show stopper said:
can u tell me how does user.conf work ? what do i have to do ?
Click to expand...
Click to collapse
Boot back to WinMo, edit the froyo.user.conf file (in the 'conf' folder on your SD card, where Android is...)
I like editing these files with Notepad++ but I think Wordpad will handle the enter keys correctly (regular Windows Notepad won't!)
At the bottom, you'll see a "CustomCommands" section. Within the braces ({}) add a line -
Code:
ln -s /sdcard/wifi-nvram.txt /data/wifi-nvram.txt
Make sure it's on its own line, look at some of the other commands for an example (look at the rm command...)
That's the skinny... hopefully it works! This assumes the wifi-nvram.txt file you created (with your MAC address in it) is at the root of the SD card (look at the command, /sdcard/wifi-nvram.txt... if it's in a 'mods' folder which is at the root of the SD, then the path would be /sdcard/mods/wifi-nvram.txt...)
? Purpose
arrrghhh said:
Boot back to WinMo, edit the froyo.user.conf file (in the 'conf' folder on your SD card, where Android is...)
I like editing these files with Notepad++ but I think Wordpad will handle the enter keys correctly (regular Windows Notepad won't!)
At the bottom, you'll see a "CustomCommands" section. Within the braces ({}) add a line -
Code:
ln -s /sdcard/wifi-nvram.txt /data/wifi-nvram.txt
Make sure it's on its own line, look at some of the other commands for an example (look at the rm command...)
That's the skinny... hopefully it works! This assumes the wifi-nvram.txt file you created (with your MAC address in it) is at the root of the SD card (look at the command, /sdcard/wifi-nvram.txt... if it's in a 'mods' folder which is at the root of the SD, then the path would be /sdcard/mods/wifi-nvram.txt...)
Click to expand...
Click to collapse
What is the result of moving this file what does this do,fix,solve? P.s. sincere?Not being sarcastic just curious.
Phatboyj420 said:
What is the result of moving this file what does this do,fix,solve? P.s. sincere?Not being sarcastic just curious.
Click to expand...
Click to collapse
What is this, I don't even...
If you're asking what this fixes, it's for wifi problems. I think someone tried this trick, and it didn't work. You actually have to place the .txt file instead of symlinking.
Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.
For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.
How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.
But now "Step-by-Step":
Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.
Step-by-Step Instructions:
1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'
Now finished .... it should work !
After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.
Have fun with the new 'init.d' support and apologize for my weak English !!
Special thanks to DooMLord for the idea and first implementation.
Source: http://forum.xda-developers.com/show....php?t=1431134
am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.
Thanx for a nice "how-to"
Seems simple and straightforward enough
Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)
Now you should find the zip on the end of first post.
Sorry - how do you gve the 777 file permissions?
SWFlyerUK said:
Sorry - how do you gve the 777 file permissions?
Click to expand...
Click to collapse
Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.
Whoops, my device is in a bootloop lol
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?
obicom said:
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
Click to expand...
Click to collapse
Doh! Thanks
SWFlyerUK said:
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
Click to expand...
Click to collapse
Not permissions fault. Mine didn't bootloop
obicom said:
Special thanks to DooMLord for the idea and first implementation.
Click to expand...
Click to collapse
yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
obicom said:
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
Click to expand...
Click to collapse
hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.
I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"
If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.
Click to expand...
Click to collapse
SWFlyerUK said:
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Click to expand...
Click to collapse
I wrote in many threads about 'rescue-backdoor', why havent you made it?
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!
-- Edit --
Rolled the build.prop increment value back
Click to expand...
Click to collapse
Does it mean now you have the original value or the lower value?
If first case , that was a fault.
SWFlyerUK said:
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
Click to expand...
Click to collapse
The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!
Resolution on post #10, in post #11 a second resolution and on post #12 the confirmation.
I need a init.d script to run or execute a service that is on system/bin
Is this possible?
Which commands to use?
I researched a lot, and I do not find anything about it.
The file name is jellyservice.
Jellyservice is a normal service that need to be running before run a app, without that, the app does not run.
I know that:
1. The jellyservice is presented on stock rom and the stock rom use init.rc to call the jellyservice at boot, and i can change the init.rc by change the boot.img (unpack, change, repack), but i wanna to be able to run it on any device wit any kernel, and don't wanna to change it kernel for it rom.
2. I can use SManager to run the file on boot. but i don't wanna to need a app just init.d, init.d is already implemented and working on almost every custom rom, so I put the init.d file on a zip that flash the apk, libs etc, and no more app or config is need.
Thanks.
baybutcher27 said:
I need a init.d script to run a service that is on system/bin
Is this possible?
Which commands to use?
I researched a lot, and I do not find anything about it.
The file name is jellyservice.
Jellyservice is a normal service that need to be running before run a app, without that, the app does not run.
I know that:
1. The jellyservice is presented on stock rom and the stock rom use init.rc to call the jellyservice at boot, and i can change the init.rc by change the boot.img (unpack, change, repack), but i wanna to be able to run it on any device wit any kernel, and don't wanna to change it kernel for it rom.
2. I can use SManager to run the file on boot. but i don't wanna to need a app just init.d, init.d i already have implemented on rom, so I put the init.d file on a zip that flash the apk, libs etc, and no more app or config is need.
Thanks.
Click to expand...
Click to collapse
Is this what you are looking for, or I am missing something?
http://forum.xda-developers.com/showthread.php?t=1933849
And this, which is more up to date:
http://www.xda-developers.com/init-d-support-for-any-rooted-phone/
Ciuffy said:
Is this what you are looking for, or I am missing something?
http://forum.xda-developers.com/showthread.php?t=1933849
And this, which is more up to date:
http://www.xda-developers.com/init-d-support-for-any-rooted-phone/
Click to expand...
Click to collapse
No you did not read what I wrote.
As I said, i wanna a script of init.d that runs or execute a file, i already have init.d working...
baybutcher27 said:
No you did not read what I wrote.
As I said, i wanna a script of init.d that runs or execute a file, i already have init.d working...
Click to expand...
Click to collapse
Sorry, I was assuming you could find help there. By the way, you should be able to do this just by using a script like:
#!/system/bin/sh
-Give permission
/path/jelliservice
Then place it in init.d or write a specific script for init.d to run the above one.
http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Sorry if there's a bigger obstacle I'm not aware of.
Ciuffy said:
Sorry, I was assuming you could find help there. By the way, you should be able to do this just by using a script like:
#!/system/bin/sh
-Give permission
/path/jelliservice
Then place it in init.d or write a specific script for init.d to run the above one.
http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Sorry if there's a bigger obstacle I'm not aware of.
Click to expand...
Click to collapse
No is all good.
but??? that willl run the service, or just give a permission.
I don't really know much about init.d script and the web does not help in that thing i wanna.
i'm implemented it now to see what that script does. :good:
baybutcher27 said:
No is all good.
but??? that willl run the service, or just give a permission.
I don't really know much about init.d script and the web does not help in that thing i wanna.
i'm implemented it now to see what that script does. :good:
Click to expand...
Click to collapse
Oh, so you are just asking for help with the actual script, fine. See if you can figure it out yourself from that post, I'm trying to build an easy example right now. I seem to not have this jelliservice you are talking about, maybe you can give me a few more insights about this.
Ciuffy said:
Oh, so you are just asking for help with the actual script, fine. See if you can figure it out yourself from that post, I'm trying to build an easy example right now. I seem to not have this jelliservice you are talking about, maybe you can give me a few more insights about this.
Click to expand...
Click to collapse
ok.
i tested that you post doesn't do what i need.
i have this on init.d to now if it works.
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt
so i change the "done" of the last line to wherever and it time i reboot it change to wherever i wrote.
so init.d is working fine.
The jellyservice is a service that only exist on motorola stock rom on devices that have dedicated hardware of DTV.
it is started by i .rc file:
init.mmi.dtv.rc
and the content of that .rc is:
Code:
on boot
# DTV feature
service dtv-jelly /system/bin/jellyservice
class main
user system
group system audio camera graphics inet net_bt net_bt_admin net_raw sdcard_rw
iknow that is possible to implemented that .rc on any device by add it to the kernel or boot.img but it will be need to do on any rom and that is allot of work and will be impossible.
so i have created a tread to give support for that DTV to any custom rom, and i wanna to make a more completed .zip to the app.
see the thread here
baybutcher27 said:
ok.
i tested that you post doesn't do what i need.
i have this on init.d to now if it works.
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt
so i change the "done" of the last line to wherever and it time i reboot it change to wherever i wrote.
so init.d is working fine.
The jellyservice is a service that only exist on motorola stock rom on devices that have dedicated hardware of DTV.
it is started by i .rc file:
init.mmi.dtv.rc
and the content of that .rc is:
Code:
on boot
# DTV feature
service dtv-jelly /system/bin/jellyservice
class main
user system
group system audio camera graphics inet net_bt net_bt_admin net_raw sdcard_rw
iknow that is possible to implemented that .rc on any device by add it to the kernel or boot.img but it will be need to do on any rom and that is allot of work and will be impossible.
so i have created a tread to give support for that DTV to any custom rom, and i wanna to make a more completed .zip to the app.
see the thread here
Click to expand...
Click to collapse
You are right, it's not easy to test this out because of default .rc hardcoded into kernel... in order to do this you would have to edit .rc to run that service that runs userinit.sh... Have you already done this? And, are you able to start the service manually?
Ciuffy said:
You are right, it's not easy to test this out because of default .rc hardcoded into kernel... in order to do this you would have to edit .rc to run that service that runs userinit.sh... Have you already done this? And, are you able to start the service manually?
Click to expand...
Click to collapse
i didn't try implemented that .rc on boot.img, that is too much work, and need to be done on it kernel or rom update, but yes can be done.
The file is just like any other executable, just like a .sh or any file you can execute using a app that can execute files like, root browser or SManager.
all the process to run the file is on the thread i just post.
The thing is i already know how to run it via app, but i don't wanna to stop there i wanna to run it via init.d because is a very simple way, but very difficult to find the commands.
Exists any command on init.d that can run a file commands like, run, execute, open or start ?
any of those work? and how to use they?
have any website that have all the command available on init.d?
Hey, you can run a binary from sh by just invoking its path, for example:
Code:
#!/bin/sh
/system/bin/jellyservice
The proccess will spawn with UID 0 (root)
You can change that if you have a good root binary by doing this:
Code:
#!/bin/sh
su system -c '/system/bin/jellyservice'
If you're using supersu I think you have to enable root at boot (Look at the application settings)
baybutcher27 said:
i didn't try implemented that .rc on boot.img, that is too much work, and need to be done on it kernel or rom update, but yes can be done.
The file is just like any other executable, just like a .sh or any file you can execute using a app that can execute files like, root browser or SManager.
all the process to run the file is on the thread i just post.
The thing is i already know how to run it via app, but i don't wanna to stop there i wanna to run it via init.d because is a very simple way, but very difficult to find the commands.
Exists any command on init.d that can run a file commands like, run, execute, open or start ?
any of those work? and how to use they?
have any website that have all the command available on init.d?
Click to expand...
Click to collapse
so i resolve this :silly: :laugh: :victory:
after writing I read, and is so lame.
if the file is just like any other executable way not put it in the init.d folder?
and i put, rename to 99jellyservice
and the init.d run it and the apk that need that file to be running before you open it work.
@Ciuffy
Thanks you help me to find a way...
nagalun said:
Hey, you can run a binary from sh by just invoking its path, for example:
Code:
#!/bin/sh
/system/bin/jellyservice
The proccess will spawn with UID 0 (root)
You can change that if you have a good root binary by doing this:
Code:
#!/bin/sh
su system -c '/system/bin/jellyservice'
If you're using supersu I think you have to enable root at boot (Look at the application settings)
Click to expand...
Click to collapse
the 1° option work perfectly!, but i use like this
Code:
#!/system/bin/sh
/system/bin/jellyservice
i think doesn't make a difference.
Thanks man I will use your way, is better that my. :good:
baybutcher27 said:
the 1° option work perfectly!, but i use like this
Code:
#!/system/bin/sh
/system/bin/jellyservice
i think doesn't make a difference.
Thanks man I will use your way, is better that my. :good:
Click to expand...
Click to collapse
Yeah basically the only difference is that Android has no /bin/sh but /system/bin/sh. I though about just putting that there honestly but I couldn't get any of this working on my cyanogenmod so I was trying to figure out why >.>, but I'm probably missing something.
Anyway, glad I could help!
I need a way to get rid of the annoying carrier bootanimation thats in /product/OP/poweron and use the LG animation in /system/media
#Rooty_Mikes# said:
I need a way to get rid of the annoying carrier bootanimation thats in /product/OP/poweron and use the LG animation in /system/media
Click to expand...
Click to collapse
Nevermind! Figured it out! Searched for the G8X Twrp installer, flashed the ramdisk, flashed Disable DM-Verity&Force Encryption, then just used the twrp file manager to handle what i needed in the directories.
I was under the impression that their was no twrp for g8x.
#Rooty_Mikes# said:
Nevermind! Figured it out! Searched for the G8X Twrp installer, flashed the ramdisk, flashed Disable DM-Verity&Force Encryption, then just used the twrp file manager to handle what i needed in the directories.
I was under the impression that their was no twrp for g8x.
Click to expand...
Click to collapse
We can change root files from twrp? I tried with file managers but it got replaced again by ui. I have root
thekalpkuleria_24 said:
We can change root files from twrp? I tried with file managers but it got replaced again by ui. I have root
Click to expand...
Click to collapse
Yes, operating in twrp you are basically running abd root in terminal and you are system-as-root in the file manager so be careful, back-up prior to any changes. Any apk managers has a hard time with system-as-root permissions in production builds unless your the root master topjohnwu lol
#Rooty_Mikes# said:
Yes, operating in twrp you are basically running abd root in terminal and you are system-as-root in the file manager so be careful, back-up prior to any changes. Any apk managers has a hard time with system-as-root permissions in production builds unless your the root master topjohnwu lol
Click to expand...
Click to collapse
But making change from manager not works coz the ui changes my change again
It should work in twrp; unless you have a recovery.from.boot file in your system. I would go to terminal and run # getprop and see what's going on, you may have a ro.prop that's not allowing what you want to change
Yes it is ro.prop so what should i do?
thekalpkuleria_24 said:
So will running #getprop in terminal help me or twrp will help
Click to expand...
Click to collapse
It will help you find to see if you have a RO "read-only" property and value on your desired item example; I want to set my adb port to 5555 i would run # getprop and look through the property's to find my item and if it says:
$ service.adb.tcp.port=5038
I would change it with:
$ su -c resetprop service.adb.tcp.port=5555
Its all depending on the property and the location in the partition the files are in really in how its modified. What exactly are you trying to do?
#Rooty_Mikes# said:
It will help you find to see if you have a RO "read-only" property and value on your desired item example; I want to set my adb port to 5555 i would run # getprop and look through the property's to find my item and if it says:
$ service.adb.tcp.port=5038
I would change it with:
$ su -c resetprop service.adb.tcp.port=5555
Its all depending on the property and the location in the partition the files are in really in how its modified. What exactly are you trying to do?
Click to expand...
Click to collapse
Im trying to change sounds from product/OP plz tell a proper command what you wrote here it confused me a bit
thekalpkuleria_24 said:
Yes it is ro.prop so what should i do?
Click to expand...
Click to collapse
Run $ su -c resetprop [property]=value
And what to write in property and value ? I have no idea
thekalpkuleria_24 said:
Im trying to change sounds from product/OP plz tell a proper command what you wrote here it confused me a bit
Click to expand...
Click to collapse
thekalpkuleria_24 said:
/product/OP is mounted to a RO only partition, I would modify in the manager built in twrp. The modifications will remain when you reboot the system that way.
Click to expand...
Click to collapse
thekalpkuleria_24 said:
And what to write in property and value ? I have no idea
Click to expand...
Click to collapse
The property doesnt change only value "usually" a number 1 for yes, 0 for no
Okay thanks going for it
#Rooty_Mikes# said:
The property doesnt change only value "usually" a number 1 for yes, 0 for no
Click to expand...
Click to collapse
Do you have twrp?
#Rooty_Mikes# said:
Do you have twrp?
Click to expand...
Click to collapse
No im doing it in termux
thekalpkuleria_24 said:
No im doing it in termux
Click to expand...
Click to collapse
Not going to work
#Rooty_Mikes# said:
Not going to work
Click to expand...
Click to collapse
Ohh why it a terminal too
#Rooty_Mikes# said:
Not going to work....you need twrp or a recovery manager flash like AromiaFM.zip
Click to expand...
Click to collapse
Okay then will do in twrp