[MOD] Enable init.d scripts support on stock kernel

[MOD] Enable init.d scripts support on stock kernel - Sony Ericsson Xperia Neo, Pro

Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Good, nice to see this posted here too.
Sent from my MT15i using XDA App

great work!

Could this be used in other android devices?

kcthomlau said:
Could this be used in other android devices?
Click to expand...
Click to collapse
Yes, it should be works well on other devices, just try it and let us know.
Sent from my MT15i using XDA App

it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file

sgj1 said:
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
Click to expand...
Click to collapse
no. I have now locked bootloader and it is working

sgj1 said:
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
Click to expand...
Click to collapse
This is working great on mine mate, just try it again maybe you left something, i tested it with init.d scripts from SE Tweaked and it works.
Sent from my MT15i using XDA App

hello guys!
what kind of script is the neo?

Confirmed, working
I tried this mod and it seems to be working. Before its application, Supercharger tells me that he cannot reach init.d or something like that. But with this mod it can use init.d without any problems, no more warning. So it is working. Thank you

iridaki said:
Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!
Click to expand...
Click to collapse
this is working for neo v?

It should on stock yes
Sent from my MT15i using Tapatalk

onlavu said:
Before its application, Supercharger tells me that he cannot reach init.d or something like that.
Click to expand...
Click to collapse
Have you checked original thread from zeppelinrox: http://forum.xda-developers.com/showthread.php?t=991276
where he shared his way(AutoStart Script) of enabling init.d for stock ROM/kernel: http://forum.xda-developers.com/showthread.php?t=1017291

kormatoes said:
It should on stock yes
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
ok but i have a noob question,
how to change vm heapsize to 48?

Pandemic said:
ok but i have a noob question,
how to change vm heapsize to 48?
Click to expand...
Click to collapse
You need to edit build.prop in system folder.
Taptalked

Tenacius D said:
You need to edit build.prop in system folder.
Taptalked
Click to expand...
Click to collapse
hm ok and how will i do that with rootxplorer, what must i do and tick/untick?
Edit: Anyone know??

With rootxplorer go to system mount read/write (see screenshot)
long press build.prop open in text editor find vm heapsize change it to 48 save the change and reboot. Make buckup of build.prop just in case.
Taptalked

Pandemic said:
hm ok and how will i do that with rootxplorer, what must i do and tick/untick?
Click to expand...
Click to collapse
Have you tried long press on file, and select "Open in Text Editor"?
EDIT: was to slow

Tenacius D said:
With rootxplorer go to system mount read/write (see screenshot)
long press build.prop open in text editor find vm heapsize change it to 48 save the change and reboot. Make buckup of build.prop just in case.
Taptalked
Click to expand...
Click to collapse
i cant edit it when i open as text:S

Pandemic said:
i cant edit it when i open as text:S
Click to expand...
Click to collapse
Not open as text, scroll down and open in text editor.
Taptalked

Related

[Boot Animation] GingerBlur - with previews and Installer!

03.30.2011 -=*[ working on automation of backup/install of the Boot Animation... ]*=-
!!COMPLETED!! see bottom of OP
i made a few Boot Animations to go with my GingerBlur'd phone if anyone is interested in them. they're nothing fancy, just something different to look at.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GingerBlur-bootanimation-1.zip
GingerBlur-bootanimation-2.zip
GingerBlur-bootanimation-3.zip
you will need to rename the respective GingerBlur-bootanimation-x.zip to bootanimation.zip.
original design was by ZeliardM for the Eris. i made some changes for GingerBlur.
Installation Instructions:
The script that's run on your phone WILL back up your existing /system/media/bootanimation.zip file ONE time and that's it. As long as the backup (/system/media/bootanimation.zipORG) exists from then on, it will simply overwrite the /system/media/bootanimation.zip file each time you run the install. this script should work for any of the Boot Animations that you get your hands on as long as there is a bootanimation.zip file in the same directory as the batch and script file (explanation(s) below). you can always revert back to your original bootanimation.zip, but you'll need to do so manually using adb to copy the /system/media/bootanimation.zipORG -> /system/media/bootanimation.zip
Download your Boot Animation of choice from the above links
Download the zip file (GB-BootAni.zip) below containing the install .bat and .sh file.
unzip the GB-BootAni.zip file you downloaded (should create you a GB-BootAni directory)
place your downloaded Boot Animation zip file in the above directory and either rename it bootanimation.zip or copy the file to bootanimation.zip
run the GB-BootAni.bat and the rest should take care of itself.
Download GB-BootAni.zip (installation helper for the GingerBlur Boot Animations)
md5sum: f20838c2d293f181f1f2d5650f6e8f83
i welcome any and all feedback...good, bad or indifferent.

Looks good! I'm loving all the boot screen's that have come out so far, great work!

Looks nice, and how would you go about installing this to your phone? Asking b/c I've never done this before.

crea78 said:
Looks nice, and how would you go about installing this to your phone? Asking b/c I've never done this before.
Click to expand...
Click to collapse
i'll try to post a script to facilitate things, but basically:
copy/rename the .zip file to bootanimation.zip
adb push bootanimation.zip /data/local/tmp
adb shell
<the above is done from your windows/linux machine>
<here down is done on your phone>
$ su
# cp /data/local/tmp/bootanimation.zip /system/media
# rm /data/local/tmp/bootanimation.zip (optional)
# reboot
...sit back and watch the magic happen.

itsonlym3 said:
i'll try to post a script to facilitate things, but basically:
copy/rename the .zip file to bootanimation.zip
adb push bootanimation.zip /data/local/tmp
adb shell
<the above is done from your windows/linux machine>
<here down is done on your phone>
$ su
# cp /data/local/tmp/bootanimation.zip /system/media
# rm /data/local/tmp/bootanimation.zip (optional)
# reboot
...sit back and watch the magic happen.
Click to expand...
Click to collapse
Thanks, and a script would be much easier to use

Can I do this on a stock atrix 4g

Always_Jonezen said:
Can I do this on a stock atrix 4g
Click to expand...
Click to collapse
you have to have "root" access in order to write to /system/media/

itsonlym3, I'm trying to do this manually via adb. First, does it matter where we put the bootanimation.zip because when I insert adb push bootanimation.zip /data/local/tmp in the command terminal, I get a "cannot start bootanimation.zip: No such file or directory"
Not sure what I'm doing wrong here...

itsonlym3 said:
you have to have "root" access in order to write to /system/media/
Click to expand...
Click to collapse
that sucks i lost my root with that update to 1.5.7

Always_Jonezen said:
that sucks i lost my root with that update to 1.5.7
Click to expand...
Click to collapse
you know you can get it back, right? you'll have to revert back and what not, but you can still have your update and get your root back.
check out this [SCRIPT] Root for 4.1.57 (RELEASED!) (requires 4.1.26 rooted) thread.

crea78 said:
itsonlym3, I'm trying to do this manually via adb. First, does it matter where we put the bootanimation.zip because when I insert adb push bootanimation.zip /data/local/tmp in the command terminal, I get a "cannot start bootanimation.zip: No such file or directory"
Not sure what I'm doing wrong here...
Click to expand...
Click to collapse
you need to issue the push (adb push) from your Winxx or Linux machine. if you've got adb in your path (which you probably do), then go into the directory where you downloaded the new bootanimation.zip and issue:
adb push bootanimation.zip /data/local/tmp/
that better?
i'm kind of assuming there's a /data/local/tmp. hopefully i'm correct in my assumption....?
sorry, i'm working on a script to automate this, just been busy. :/
also, you should probably back up your existing bootanimation.zip file before overwriting it if you'd like to keep it. PM me and i'll walk you through it if you need help. i'll add manual instructions to the OP once i finish up the automated script.

itsonlym3 said:
you need to issue the push (adb push) from your Winxx or Linux machine. if you've got adb in your path (which you probably do), then go into the directory where you downloaded the new bootanimation.zip and issue:
adb push bootanimation.zip /data/local/tmp/
that better?
i'm kind of assuming there's a /data/local/tmp. hopefully i'm correct in my assumption....?
sorry, i'm working on a script to automate this, just been busy. :/
also, you should probably back up your existing bootanimation.zip file before overwriting it if you'd like to keep it. PM me and i'll walk you through it if you need help. i'll add manual instructions to the OP once i finish up the automated script.
Click to expand...
Click to collapse
That clears things up. I'm patient on you making a script, and good point on making a backup.

added installer and its usage to OP.

itsonlym3 said:
added installer and its usage to OP.
Click to expand...
Click to collapse
Even while using the script, the installer failed because of the data/local/temp not being found. Not sure how to find the path in order to see if bootanimation.zip is located in there.
Edit: when I type in %temp% in the start - search, it pops up my local temp files, but there is nothing in that folder?? I'm using Chrome as a browser if that makes a difference.

crea78 said:
Even while using the script, the installer failed because of the data/local/temp not being found. Not sure how to find the path in order to see if bootanimation.zip is located in there.
Edit: when I type in %temp% in the start - search, it pops up my local temp files, but there is nothing in that folder?? I'm using Chrome as a browser if that makes a difference.
Click to expand...
Click to collapse
/data/local/tmp is a path on your phone.
you should take whichever Boot Animation file you would like to use, copy it to the directory where you unzipped the installer and name it: bootanimation.zip
then while in that directory, you should run GB-BootAni.bat file and it should do the rest for you.
first off, when you get to a command line on your PC and type:
adb devices
does it return return/display something like this:
List of devices attached
TB30607H83 device

Stupid me!! I named the zip as bootanimation.zip so it read "bootanimation.zip.zip" so that is why it never worked. The new bootanimation works perfectly after I figured out my error

Stupid me!! I named the zip as bootanimation.zip so it read "bootanimation.zip.zip" so that is why it never worked. The new bootanimation works perfectly after I figured out my error
Click to expand...
Click to collapse
glad u figured it out and got it installed!
Thanks for the update
Sent from my MB860 using XDA Premium App

where do you put the script folder to run it? im having no luck getting it to take

Spaztazim said:
where do you put the script folder to run it? im having no luck getting it to take
Click to expand...
Click to collapse
you should be able to put it anywhere on your machine, as long as you have adb.exe in your path somewhere. i didn't add it to the zip file, but i suppose i could.
is that what you were asking?

Yep didn't do the adb part, I got creative and made my own animation by combining the peking droid and honeycomb takeover then figured out how to install it manually
Sent from my Atrix 3g

[TWEAKS/SCRIPTS/DOWNLOADS]~ BEST TWEAKS EVER ~ ((26-Oct))

Some great stuff from Amazing devs
-Androguide.fr Pimp My Rom {the best tweak :good:} ((October 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1908269[/url]
- AC!D AUDIO ENGINE Developers ((amazing sound experince))
Code:
[url]http://chautemseric.wix.com/acidaudiotechnology#!devices-support/cdfs[/url]
-croniccorey CronMod-A2SD/D2EXT/INT2EXT {best A2SD tweaks} ((updated 09/19))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909374[/url]
- CarlDeanCatabay Increase RAM using Swap File and Swap Partition and SD card partitioning ((great one try it))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1659231[/url]
-hyperbolic The Complete Guide For Maximum Battery Life {great battery life}
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909996[/url]
-PIT Tech GameBooster ★ root {great games experience }
Code:
[url]https://play.google.com/store/apps/details?id=com.burakgon.gamebooster[/url]
-OOM groupings and priorities tweaks - SuperCharger ((add it with loopy))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
-Loopy Smoothness tweak ((add it with SuperCharger))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
-droidphile Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs ((15th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1369817[/url]
Other tweaks or guidelines
-Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Code:
[url]http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts[/url]
-Use UOT kitchen for basic theming on your device.
Code:
[url]http://uot.dakra.lt/[/url]
-Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=903507[/url]
-Use CyanogenMOD's APN list file - one of the most complete located in
Code:
/system/etc/apns-conf.xml
-Do not use task killers.

for GOD sake ... don't use them all... SELECT/MODIFY according to your ROM and what you want.
WARNING
Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.
TO WHO CARE TO KNOW
What is build.prop:
- The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect
XperienceD said:
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also sift through what works and what doesn't.
Click to expand...
Click to collapse
WAIT
REQUIREMENT BEFORE YOU START :-
- Make a NANDROID BACKUP
- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and
- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),
- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator
- If your build.prop has an additional build properties section the line of code needs to go in there
(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
How to
Replace OR tweaks Build.prop :-
1. Download Es File Explorer ((OR ANY APP LIKE IT))
2.CLick menu, settings, check Root Explorer and Mount File System
3.Copy the Build.prop file into the sd card and copy with file manager
4.Click Favorites tab, Click Phone icon /
5.Navigate to system/
6.Rename build.prop to build.bak
7.Paste build.prop you copied earlier Reboot! Done! :good:
Build.prop tweaks((UPDATED 26-Oct))
Add these at the end of your build.prop
Code:
IN THE ATTACHMENT
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Init.d tweaks ((UPDATED 26-Oct))
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Note:
1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh
2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work
Code:
I COLLECT A LOT OF THEM
IT TOOK ME ALLOT OF TIME AND EFFORT
I PUT THEM IN TEXT
IN THE ATTACHMENT
DELETED WHICH IS DUPLICATED
& MODIFIED SOME
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASH ABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASH ABLE ONE
sysctl tweaks ((UPDATED 26-Oct))
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
-To activate sysctl tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
-sysctl.conf
Code:
IN THE ATTACHMENT

Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal

dr said:
Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal
Click to expand...
Click to collapse
Great great post. That's what we like to see. Keep searching for perfection. More will follow.
Sent from my LG-P500 using xda app-developers app

troullis2004 said:
Great great post. That's what we like to see. Keep searching for perfection. More will follow.
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
thank u sooooo much
yeb more will but every day new tweaks its kind of tooooooooooo much

thank u sooooo much

That Gemini app manager doesn't show i have any auto apps?
Sent from my U30GT-H using Tapatalk 2

RajaSetan said:
thank u sooooo much
Click to expand...
Click to collapse
u r welcooooooooooooome
Ben36 said:
That Gemini app manager doesn't show i have any auto apps?
Sent from my U30GT-H using Tapatalk 2
Click to expand...
Click to collapse
sorry dude but can u tells me
1- do u use task killer
2- ur phone is rooted or not

stumbled upon a weird problem
Hello dr,abd, 1st of all thanks for this wonderful thread, today while i was plying with my xperia P i stumbled upon a very weird problem,
In stock rom i tried following mods-
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown(here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown(here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Click to expand...
Click to collapse
and this initd tweak(modified in accordance to my device.
with these mods my system became very smooth and responsive but the problem is poweramp player(which i purchased) seem not working at all, cant restore previous data from titanium backup, it not even installing from play store and nothing at all, i listen music a lott and i configured eq, playlist bla bla bla in accordance to my taste, now after looong try i give up, would u or anyone with proper knowledge help me out regarding this matter, maybe i made some mistake tweaking the initd script.......:crying:

dr said:
u r welcooooooooooooome
sorry dude but can u tells me
1- do u use task killer
2- ur phone is rooted or not
Click to expand...
Click to collapse
1- hell no. Never!
2- yup!
Sent from my LT26i using Tapatalk 2

musvi said:
Hello dr,abd, 1st of all thanks for this wonderful thread, today while i was plying with my xperia P i stumbled upon a very weird problem,
In stock rom i tried following mods-
and this initd tweak(modified in accordance to my device.
with these mods my system became very smooth and responsive but the problem is poweramp player(which i purchased) seem not working at all, cant restore previous data from titanium backup, it not even installing from play store and nothing at all, i listen music a lott and i configured eq, playlist bla bla bla in accordance to my taste, now after looong try i give up, would u or anyone with proper knowledge help me out regarding this matter, maybe i made some mistake tweaking the initd script.......:crying:
Click to expand...
Click to collapse
hi sorry to replay late
first try this one
loopy new tweaks first ver was buggy somehow
second please after tweaking wipe
((cash and dalvik cash))
Ben36 said:
1- hell no. Never!
2- yup!
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
try to wipe
((cash and dalvik cash))
Any problem, please contact [email protected]
cause it works like charm to me i don't know really

Updated new amazing tweaks and deleted & modified

dr said:
Updated new amazing tweaks and deleted & modified
Click to expand...
Click to collapse
nice update and great collection
i pm u some that i have

Nice, we need speed.
Sent from my LT26i using xda premium

solid7 said:
nice update and great collection
i pm u some that i have
Click to expand...
Click to collapse
thaaaaaaaaaaaaaaaaaaaaaaaaanx
i will add it next release
bl4dy_pt said:
Nice, we need speed.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
that's what i want to give all of u
speed battery saving and amazing multitasking and smoothness

Sent from my MT27i using xda premium

people please dont use alllll the tweaks use according to your use

xperia arcs said:
people please dont use alllll the tweaks use according to your use
Click to expand...
Click to collapse
+1. Dont go mad using every tweak you can find. Very often too many tweaks can cause conflicts.
Sent from my ST25i using xda app-developers app

[SCRIPT PACKAGE] ~zipbackup_v_2~ creates flashable backup zip right from your device!

Hi friends of XDA,
This is my first post in Developer's section
I'm very new to android and linux, actually i'm a noob in scripting but i've tried my best and will try to learn more from here.
i've been using ubuntu for past two months and android phone for past seven months.
i really started to like the open source community and learnt a lot! here i have created a simple piece of shell script
which will backup your phone and create a zip package for flashing with clockworkmod.
this piece of script package works right from your phone from start to end and will create a flashable zip package.
this idea was inspired by onandroid by ameer1234567890
so credits to him for creating a very portable script to create a nandroid backup while the phone is online.
this tool here works the same way as onandroid but instead creates a flashable recovery zip and the compression rate is higher than a Nandroid backup (see comparison chart below).
I have learnt everything i know about android from this forum. I wanted to contribute to XDA so i wrote this package
for you, my friends of XDA.
This is the first release for testing but i will be releasing upgraded versions with increased features and support for more devices.
first is first,
#include
/*
* I am not responsible for bricked devices, dead SD cards or
* thermonuclear war.
* do some research if you have any concerns.
* YOU are choosing to make these changes.
* yes, i copied this disclaimer from FXP because it is cool and i am lazy!
*/
REQUIREMENTS for v_2 :
1. xperia phone and kernel with CWM installed.
(theoretically it can be easily ported to all andriod devices. if interested, please test and let me know)
2. if hte script fails to install busybox and zip bianry, you have to manually place the busybox and zip binary and set permissions (execute the script and read the instructions)
3. script manager (compulsory)
4. some patience.
HOW TO USE:
1. download the attached zipbackup_v_X.zip
2. extract the "zipbackup" folder present in the attachment to the root of your sdcard
3. executed the extracted "zipbackup" present in /sdcard/zipbackup/ with superuser permissions using script manager with appropriate command line parameter (just execute it it will instruct you).
4. follow the on screen instructions.
COMPRESSION COMPARISON CHART:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE:
1. PLEASE DO A NANDROID BACKUP BEFORE TESTING THIS SCRIPT PACKAGE
if this works in your device probably you won't be using nandroid backup anymore
2. this script package was tested in my xperia mini st15i running in my own stock base rom (.431)
and rage kernel so it should probably support all xperia android phones .
3. Everybody is welcome to edit the package without asking my permission provided you inform me and add a link
to this original thread in your version of zipbackup and credits should be awarded where due.
4. Right now in this v_2 release, only the /data , /system and /cache partition backups are done but in future
versions i will try to add support to backup /sd-ext and .android_secure .
5. Anybody interested is encouraged to suggest improvements in script and credits will be awarded where due.
6. If you are using a governor to limit the processor speed during screen off please disable it before back up and enable wakelock in sript manager else it
will greatly increase the time for compression if the screen is off while zipbackup script is running or try keep the screen on while the script is running.
SCREENSHOT:
NOTE: zip binary is actually installed in /system/xbin/ ignore the mistakes in screenshot it was shot during testing and that is a typo.
How this works?
Read second post!
CREDITS:
ameer1234567890 for the creation of his portable onandroid script.
The creators of opkg from which i extracted the zip binary for ARM devices.
to cigognes for informing me about opkg
To all my friends of XDA and XDA forum itself without which i could not have acquired this amount of knowledge in scripting.
to fxp for the busybox binary.
To users of ubuntuforums for helping me with my doubts in shell scripting commands.
please let me know if i have missed you out! if i have missed you out then it was done unintentionally!
VERSION CHANGELOGS:
zipbackup_v_2:
1. Added advanced backup functionality using command line parameters.
2. this version comes with busybox from fxp 142 kernel so it does not use the busybox present in your device for archiving so no need to worry about support for creation of bz2 archives.
USAGE for v_2:
1. to backup all (/system , /data and /cache) partitions use "-a" parameter
2. to backup only /data partition use "-d" parameter
3. to backup only /cache partition use "-c" parameter
4. to backup only /system partition use "-s" parameter
zipbackup_v_1:
1. Completely re-wrote the script from scratch.
3. removed the zipbackup_install.sh script and merged two scripts into one.
4. Included busybox for bz2 archive creation and extraction.
5. added analysis of power status function.
6. added led, vibration and lcd notification upon sucessful completion of backup.
7. this version comes with busybox from fxp 142 kernel so it does not use the busybox present in your device for archiving so no need to worry about support for creation of bz2 archives.
NOTE: please do not use alpha versions (no longer supported and they are buggy)
zipbackup_v_alpha2
1. added support to backup /cache partition
2. added elapsed time function
3. few minor changes in the script
zipbackup_v_alpha
initial release
TESTED SUCESSFULLY ON:
fxp 142 kernel
rage kernel 3.2
mesa kernel 1.9
kernel panic 1.25
PLEASE COMMENT IF IT WORKS OR DOES NOT WORK WITH YOUR DEVICE!
Please press thanks if my thread is useful!

how this works???
HOW THIS WORKS (v_2) :
If you have a good amount of knowledge on shell scripting (which i know a little):
View full code with highlighted syntax and detailed comments, see pastebin entry.
for others,
The package consists of:
zipbackup_v_2.zip
|
|------reqfiles.zip
| |
| |---META-INF.zip (META-INF folder)
| |---busybox (busybox binary)
| |---zip (zip binary)
|
|---zipbackup (main script)
how does it back up?
1. When the zipbackup is executed with superuser permissions and with correct commandline parameters it extracts the busybox, zip binary and META-INF.zip inside the
ziprecovery folder. then it copies the attached busybox binary and zip binary to /tmp/ and /system/xbin folder respectively and assigns 755 permission to both of them.
this busybox binary is necessary for creating .bz2 archives and zip binary is necessary for creating the flashable zip.
2. then it creates /sdcard/zipbackup/temp folder and starts archiving /cache or /data or /system or all the three according to your requirement and
places it inside the temp folder temporarily.
during archiving it also creates a log file of all the files archived and places it in /sdcard/zipbackup/logs/backup/
after archiving it generates a updater-script compatible with provided update-binary (included in the package)
then the META-INF.zip is extracted into the temp folder and creates a compatible META-INF folder tree and includes the
generated updater-script in it.
NOTE: since the compression is higher it may comparatively take longer to backup than a Nandroid backup so if it doesn't throw any errors and
the screen says "please wait...." Then please wait it's actually working!
2. Then a ziprecovery.sh script is generated. this script is necessary for flashing the zip package with clockworkmod.
3. then the busybox included with the package is moved to temp folder
3. Then the zip binary is invoked and the created archives (cache.tar.bz2, data.tar.bz2 and system.tar.bz2), ziprecovery.sh the META-INF folder and included busbox binary are
zipped in store mode as requiered by clockworkmod.
4. A md5 sum is generated for the created zip file and placed in /sdcard/zipbackup/logs/backup/ folder for your reference.
the flashable backup zip is placed in /sdcard/zipbackup/backups/
NOTE: the md5 sum generated is only for your reference and it will not be checked during restore
how does it restore?
1. when the created backup zip file is flashed via clockworkmod the updater script formats the /system and /data and /cache partition first.
then extracts the busybox binary from the recovery zip and places it in /tmp folder and assings 755 permissions to the temporary busybox.
then extracts the three archives (cache.tar.bz2, data.tar.bz2 and system.tar.bz2) to the root of the sd card temporarily. so make sure that you have free space in sdcard prior to restore.
then the ziprecovery.sh is extracted to /tmp and 755 permission is assingned to it.
2. the ziprecovery.sh is executed which inturn extracts the archives (cache.tar.bz2, data.tar.bz2 and system.tar.bz2) present in the root of the sd card (see 1)
to their respective partitions (/cache, /data and /system).
during restore it also creates a log file of all the files restored and places it in /sdcard/zipbackup/logs/restore/
after the extraction, the cache.tar.bz2, data.tar.bz2 and system.tar.bz2 archives are deleted from the root of the sd card.
the symlinks and permissions are preserved by default in a .tar.bz2 archive (because i have tested it personally many times and it works with me).
NOTE:
1. everybody interested in this and have a prior knowledge in shell scripting can add features and optimize ziprecovery,
provided, a link to this thread and credits where due are given in your version of zipbackup.
2. I will try to optimize and add additional features in upcoming releases.
i need your help to implement this zipbackup script package optimally and bug free.
thank you for spending your valuable time in reading my thread.
press thanks if i haved helped you.
-------------------------------------------gouthamthemostwanted-----------------------------------------------

(RESERVED)

(RESERVED)

(RESERVED)

(RESERVED)

(RESERVED)

Great Idea, hope you will contiune this project. Very good that there are some toolkits like yours for linux, too. Maybe I'll try to add some functions

mihahn said:
Great Idea, hope you will contiune this project. Very good that there are some toolkits like yours for linux, too. Maybe I'll try to add some functions
Click to expand...
Click to collapse
Ya thanks! And you are very much welcome to contribute to zipbackup!
Please test and tell me if it works with your device (XMP)
Sent from my smultron using xda app-developers app

gouthamthemostwanted said:
Ya thanks! And you are very much welcome to contribute to zipbackup!
Please test and tell me if it works with your device (XMP)
Sent from my smultron using xda app-developers app
Click to expand...
Click to collapse
Okay if I've time I could let you know tomorrow

Ya thanks man!
press thanks if I have helped you!
sent from my smultron

gouthamthemostwanted said:
Ya thanks man!
press thanks if I have helped you!
sent from my smultron
Click to expand...
Click to collapse
hey really nice method...
keep it coming ...this will help lot of ppl.
ill try it soon
--sorry used all 8 thanks today

mihahn said:
Okay if I've time I could let you know tomorrow
Click to expand...
Click to collapse
Thanks!!
press thanks if I have helped you!
sent from my smultron

Great work from you, if this concept reaches official release stage, post it at android hacking and development forum !
Great future for this work.
Thanks !

kokzhanjia said:
Great work from you, if this concept reaches official release stage, post it at android hacking and development forum !
Great future for this work.
Thanks !
Click to expand...
Click to collapse
Ya thanks but for that I need testers . I've tested it on my Xperia mini but I need users to test it in other Xperia models and give me feedback.
press thanks if I have helped you!
sent from my smultron

gouthamthemostwanted said:
Ya thanks but for that I need testers . I've tested it on my Xperia mini but I need users to test it in other Xperia models and give me feedback.
press thanks if I have helped you!
sent from my smultron
Click to expand...
Click to collapse
Well, i am testing it, report to you later
Thanks !

kokzhanjia said:
Well, i am testing it, report to you later
Thanks !
Click to expand...
Click to collapse
Awaiting your reply! :fingerscrossed:
press thanks if I have helped you!
sent from my smultron

I followed instructions and not sure if im doing it right but the zipbackup.sh didnt appear in the zipbackup after installation
Thanks !

Okay what did the zipbackup_install say? Did you run it with superuser permissions and with script manager? Don't use terminal emulator it throws errors
press thanks if I have helped you!
sent from my smultron

gouthamthemostwanted said:
Okay what did the zipbackup_install say? Did you run it with superuser permissions and with script manager? Don't use terminal emulator it throws errors
press thanks if I have helped you!
sent from my smultron
Click to expand...
Click to collapse
Yup, ran with scriptmanager and superuser permission.
And was told to run the zipbackup.sh at zipbackup folder.
Zipbackup folder was created but no zipbackup.sh inside..
Thanks !

[MOD][SHARE][SCRIPT]Enable Init.D On Stock Kernel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
v1.0
init.d support through an app!!!
Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: View attachment 1612958
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. Paste it into /etc/init.d. If there is no init.d folder, most probably you DO NOT have init.d support. However, if you still wanna try, just create the folder named "init.d"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. If you see a file named Test.log in /data, you have init.d support. If not, you will have to run Uni-init, Term-init or Zip-init.
Requirements:
- a rooted phone of course...
- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script..use "normal install" method, don't use "smart install"...
Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing (shows time of execution), another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors
Instructions:
1. Download the apk.
2. Install the apk like any normal app.
3. Launch the app.
4. The rest are pretty self-explanatory...
5. You can uninstall the app after that...
Screenshots:
Download:
If you have already read all the instructions and understand them, then click here to download:
Uni-init v1.0.apk
Original Source
Credits: Ryuinferno

nice !!! , fb later :thumbsup: :beer:

frooztreited said:
nice !!! , fb later :thumbsup: :beer:
Click to expand...
Click to collapse
nice,,,ill bm it.. :highfive::good::good:

why need app, if we have custom kernel?
no offence btw nice....

Reynaldi said:
why need app, if we have custom kernel?
no offence btw nice....
Click to expand...
Click to collapse
some people prefer stock sometimes for its stability
=========================================================================
For the OP, atleast make credits to original developer bigger? since u cant provide any updates to this app, can anyone consider this development? or app share?

ronnieryan said:
some people prefer stock sometimes for its stability
=========================================================================
For the OP, atleast make credits to original developer bigger? since u cant provide any updates to this app, can anyone consider this development? or app share?
Click to expand...
Click to collapse
app share.. make it move to proper section.. haha.. joke!
for the OP.. tq!
just found this days ago.. when i want enable init.d for my frend ace duos.. but no luck then use custom kernel..
i prefer stock kernel due to its stability.. since this app cant support his kernel thats y im using custom one..
btw.. did u try and did it work with our stock kernel? i meant did Test.log present in /data folder?
sent from my GT-S5360 via WeChat

init.d folder not showing on system/etc/ where find him ?
and when i press activate button then check for succesfully app say init.d not support why ?

Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing (shows time of execution), another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors
Click to expand...
Click to collapse
as stated by OP, in order to make this trick work the kernel must support install-recovery.sh script. too bad that SGY is not one of them. a simple test will prove it. you can make a script in init.d contain.
Code:
#/system/bin/sh
echo "kucing meong" > /data/kucing_meong.txt
if the trick really work. you'll find kucing_meong.txt in /data. in the past there are a lot of script and tweak claimed to be able add init.d support in any stock kernel but none of them work since samsung have disabled all the possibilities to add init.d support for SGY. the only way to add init.d support is by install a custom kernel with modified init.rc script.

kurotsugi said:
as stated by OP, in order to make this trick work the kernel must support install-recovery.sh script. too bad that SGY is not one of them. a simple test will prove it. you can make a script in init.d contain.
Code:
#/system/bin/sh
echo "kucing meong" > /data/kucing_meong.txt
if the trick really work. you'll find kucing_meong.txt in /data. in the past there are a lot of script and tweak claimed to be able add init.d support in any stock kernel but none of them work since samsung have disabled all the possibilities to add init.d support for SGY. the only way to add init.d support is by install a custom kernel with modified init.rc script.
Click to expand...
Click to collapse
in short, this app share is useless

Yeah and no development just an app
"Hate Me Till You Can"

Don't post like app share... because the original thread was in development section...
Sent from my Nexus 4 Using Tapatalk 2 Xparent Blue

Lets state the obvious ok,
at first it was in development section since the creator and developer of the app was the thread starter, and sharing that app to SGY section doesnt mean you developed it and placed in development section?
BTW, what makes it different is that a developer can post in development section because he can, develop,update, fix and whatever it is that he sees fine, but a sharer like you cannot

mod not working for our sgy

General [RMX2202] Realme GT 5G (UI2.0 & UI3.0) - ALL ROOT

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

吨wrp root

Hi, it seems like this version of Magisk doesn't let you enable Magiskhide, am I right ?
(I'm on Realme UI 2.0 - Android 11) , is there a way to use my banking apps, Google Pay, etc.?
Thanks

This worked well.
Didn't work first time, but then I updated magisk to the latest version and it worked perfectly, whereas it was stopping before that.

Hey guys! Last root I did was on android 4.1 and I don't really know how to do it. I have Realme with C.05 soft. Will someone guide me?

Hi guys
This root is worked on europe version? Im from Slovakia. Rmx2202gdpr 11.a.17 .Thank you

qiurigao said:
View attachment 5486671
Click to expand...
Click to collapse
Hello. Is it possible to install this driver on Linux?

I could root a European RMX2202_11_a.17 this way.
First I checked OEM unlock in developer options.
The most difficult part is getting into bootloader. I used a program DeepTesting_realme-release_20210426_newID_signed.apk for this, which I had from https://forum.xda-developers.com/t/...-twrp-2022-02-21.4381727/page-3#post-86279181, I believe.
Hereafter I did under Linux the same as the batch files:
Code:
fastboot flashing unlock
Hereafter an automatic reinstall
Reenabling development options and USB debugging.
Code:
adb reboot bootloader
In bootloader:
Code:
fastboot boot twrp/twrp11.img
Change the language.
Uploaded a recent version of magisk renamed to zip to tmp
Code:
adb push Magisk-v24.3.zip /tmp
Pressed install in twrp and selected this file.
Hereafter reboot to system.
EDIT:
After the update to Android12 RMX2202_11_C.05, I could root it the same way using twrp/twrp12.img.
You can just press Cancel when asked for a password.
EDIT2:
After the last update RMX2202_11.C.16_1160_202204192320.44.7636e18c (for which I didn't remove root), the above method didn't work anymore.
fastboot boot twrp/twrp12.img
resulted in a black screen. I could adb in to recovery, but
/bin/twrp install /sbin/Magisk.zip
gave the following message:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
EDIT3:
Booting the same way from the recovery I found here https://droidfilehost.com/download/download-realme-gt-5g-rmx2202-twrp-recovery-file/ worked. The only problem is that it is Chinese so you have to guess what to do.
EDIT4:
After the update to RMX2202_11.C.20_1200_202207201946.44.84bc864c, this method still works (when the bootloader is unlocked):
adb reboot bootloader
#WAIT
fastboot boot recovery.img
#WAIT
adb push Magisk-v25.2.zip /tmp
adb shell /bin/twrp install /tmp/Magisk-v25.2.zip
adb reboot
EDIT5:
Also works with RMX2202_11.C.27.

Rooted my device successfully but the banking apps not working. Is there any way to make it work magisk hide??

If you are using Magisk 24.3, you have to add the banking app to the DenyList. Go to Magisk settings. Turn on Zygisk and Enforce DenyList and add banking app to Configure DenyList.

Can someone fix systeam read only

Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
there are somethings here and here but i didnt try yet

Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit

jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Thanxx I will try this

grown_man said:
there are somethings here and here but i didnt try yet
Click to expand...
Click to collapse
thnx for your concern buddy

jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??

Kabid0033 said:
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??
Click to expand...
Click to collapse
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.

jkaltes said:
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.
Click to expand...
Click to collapse
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this

Kabid0033 said:
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this
Click to expand...
Click to collapse
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.

jkaltes said:
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.
Click to expand...
Click to collapse
You said that we have to put files in /data/adb/modules so that it can reflect in system
So I like to make one app to place in system /app
(eg: Like in older version of android we mangae to do that directly cause their system is rw)
(From this my apps stop working)
So I manually remove the folder from the modules then reboot
But it didn’t fix how it used to be

Better Mobile App

welcome