Disclaimer:
---------------------------------------------------------
Im Not Responsible If you Bricked Your device,boot loops,data lose,dead sd cards etc...
---------------------------------------------------------
I discovered this init.d Folder FIX which Fix the auto delete for files in it.
this will help alot of people who like tweaking thier devices.
YOUR DEVICE SHOULD BE ROOTED!!
Lets Start:
1.open Root Browser.
2.go to system/etc/.
3.if you have a stock rom you properly won't have the Init.d folder,so just create it.
4.change init.d permissions to "rwxr-xr-x"
5.open the folder and create a file with any name.
6.go back to system/etc.
7.open init.d agian.
8.the file still there,You are done.
Tip/s:
to make the rwxr-xr-x permission tick the following:
OWNER:read,write,execute.
GROUP:read,execute.
OTHERS:read,execute.
Hit the thanks button if i helped .
Related
Need some help. Yesterday i tried to mod the widgetlocker, i used the root-explorer metod. Followed the steps in this tread
http://forum.xda-developers.com/showthread.php?t=825553
ROOT EXPLORER
- - - - - - - -
1) Open Root Explorer and navigate into data/app and find com.teslacoilsw.widgetlocker-1.apk
2) Copy the .apk to your SD card
3) Open the .apk and navigate to /res/drawable-hdpi
4) Copy the two images you've chosen, overwriting the 'old' PNGs in \drawable-hdpi
5) Exit the .apk and copy it back to /data/app, overwriting the old .apk
You need to be in R/W mode.
Long click the app - Select permissions and do the checkmarks like this (* represents a checkmark)
* . * . -
* . - . -
* . - . -
it didnt work, so as dumb as iam i used the permission trick on data/''app'' folder, now all my apps dissappeard, only the orginal apps from galaxy s are there... what to do ? dont want to do a factory resert
thx in advance
This script will Odex your /system/framework/ directory live while booted into android. You can thank freeza for providing the original boot class path from the s3 when I was initially trying to do this on that platform. Tonight I was bored, and putting together my note II ROM and out of pure curiosity wanted to know if it would work straight across to this device as the framework directories of the two devices have similar contents... apparently the bootclasspath for the two devices are identical otherwise this script wouldn't have executed in the first place. But it did! So here we go. Devs, feel free to place this is in your ROMs as an optional add on. It should be noted that most themes for the UI are not odex compatible, and will cause boot loops if flashed. BUT... you can flash a theme, modifying your framework (as a theme does) THEN run this script
This is beneficial for those who flash deodexed ROMs in order to theme. The idea is simple: find your favorite theme/ROM, then optimize it using this script.
Simple instruction, this is easy to do.
Download the attached zip file...
http://db.tt/na11Ma9L
Extract the zip file (the ouput should be a folder named "odex' with some files in it)... place the odex folder it in your /data/local/tmp/ directory with a file explorer such as FX File explorer...
Use said file explorer to give the folder, and all of its file contents FULL read/write/execute permissions and root ownership. This is typically done with a file explorer by long pressing on the folder/file and selecting the appropriate options. With FX long pressing will give you an option for "permissions" select that then change all tabs on the left to say root, and check all boxes for full 0777 perms (this will need to be done individually for each file and folder, you cannot just do it to the folder because it will not change the content's)...
With root explorer you should also be able to figure out this process...
Use said file explorer to mount your /system/ directory as r/w... this is done by simply clicking the green "locked" icon while browsing the /system/ directory with FX File explorer...
with root explorer there is a grey tab at the top of the app window that says "mount as r/w"...
Download terminal emulator from the market and open it up... type the following commands:
su (hit enter and it will ask for root perms... grant it)
Then type:
/data/local/tmp/odex/odex (hit enter, it will do some things you will not be able to read so don't worry about it lol
When it finishes type "reboot" without quotes and hit enter
Done. Profit.
This will work on any deodexed ROM for the note II running 4.1.1
Question: how will this benefit me?
Answer: odexed framework is more efficiently accessed by the CPU thus reducing CPU cycles and saving battery life a tick. Apps/frameworks that are odexed are opened faster, thus performance is improved - smoother UI, etc.
IMPORTANT * * * DO NOT DO THIS IF YOU HAVE ODEXED YOUR /SYSTEM/APP/ DIRECTORY WITH AN APP LIKE TITANIUM BACKUP. UNDO IT, REBOOT, RUN THIS, THEN RE-ODEX /SYSTEM/APP/ ....not doing this will likely cause you to boot loop/lock up at boot. You have been warned.
reserved
This is cool thank you very much. By chance is it possible to write a script to deodex also?
Worked great on my s3, just what ive been looking for. THANKS
Awesome! Love odexed roms
Master'd Note 2
Only framework is odexed?
Lol. Guess the first line of op answers that dumb question. Thanks for sharing :thumbup:
Sent from my SGH-T889 using xda premium
Use this for the rest, it works great.
http://forum.xda-developers.com/showthread.php?t=1839445
This only works on Gingerbread, not anything else.
Hello guys i found this awesome tweak package http://forum.xda-developers.com/showthread.php?t=2167228
About the script:An awesome script that make your gaming smoother
Warning:this tweak package is made for adreno 205+ gpus but it's working very well on my desire ; we( me or Spizzy01 or xda) are not responsable for any damage done to your phone by flashing this mod and by flashing this mod you accept that
Instructions:
Download and copy the ZIP to SD Card. Then flash using CWM.
NOTE: Please ensure you reboot your device after the first boot post-installation of the mod or it will not be active.
Requirements
Init.d support
Root
Any Gingerbread ROM
DOWNOAD: in the original thread linked above
Credits: All credits goes to developer of this script- @Spizzy01
Troubleshooting
First, give yourself another reboot - Just in case!
If it still doesn't seem to be working for you, check to see if the files have copied to your device. Check the following locations for the following files with any file manager with Root support.
/system/etc/init.d - Filename: 93adreno
/system/etc - Filename: adreno_config.txt
You should also see adreno_config.txt in the following location if the init.d script is working correctly: /data/local/tmp
If this file is not in this location then chances are you do not have init.d support.
Black screen on boot? See here: http://forum.xda-developers.com/show...&postcount=377
Extras
You can assist with the testing of some of these settings by doing the following:
Open a new text file in a standard text editor (Notepad++ or Notepad for Windows)
Choose values from the above post to put into your configuration file. (Use the attached adreno_config.txt file as an indication of what setting does what)
Save this new file as 'adreno_config.txt'
Copy this text file to your phones SD Card.
Open your File Manager on your phone (I use ES File Explorer)
Prepare adreno_config.txt on your SD Card for copying
Navigate to /Data/local/tmp and paste the file there
Reboot.
Please be aware that if you have any cleaner init.d scripts this will NOT work, as when you reboot /data/local/tmp will be deleted.
Great thing, THANK YOU!
I installed it, but i see no difference in perfomance
Hi everyone
This is my first thread, so I decide to make it useful to everyone
Let's GO !
What You Want :
ES File Explorer File Manager (OR any file explorer supports zip extracting)
Rooted Phone
Nandroid Backup (You don't know how important it is)
1- enable root explorer and set permission to r/w (read & write)
2- extract the flashable zip to your memory
3- go to the existing folder
4- copy everything except META-INF folder to the root of your phone
5- "Must" show replace confirmation select confirm
6- After the copy operation is finished, reboot your device
7- Done, Congratulations
PLEAS NOTE THAT I AM NOT RESPONSIBLE ABOUT YOUR DEVICE IF YOU BREAK IT RESTORE THE NANDROID BACKUP
note if its a new file you need to set permissions of the file
most files in app are rw-w-w however some may vary depending on what file it is
at the end of the day if you have a flashable zip its much better to flash certain things than push to system so if the flashable zip has already been made for you than you might as well use it
One doubt please
Ahmad YH said:
Hi everyone
This is my first thread, so I decide to make it useful to everyone
Let's GO !
What You Want :
ES File Explorer File Manager (OR any file explorer supports zip extracting)
Rooted Phone
Nandroid Backup (You don't know how important it is)
1- enable root explorer and set permission to r/w (read & write)
2- extract the flashable zip to your memory
3- go to the existing folder
4- copy everything except META-INF folder to the root of your phone
5- "Must" show replace confirmation select confirm
6- After the copy operation is finished, reboot your device
7- Done, Congratulations
PLEAS NOTE THAT I AM NOT RESPONSIBLE ABOUT YOUR DEVICE IF YOU BREAK IT RESTORE THE NANDROID BACKUP
Click to expand...
Click to collapse
I think this method only for apk files. "my doubt is this method is posible to replace frameworks files..?"
krsharjun said:
I think this method only for apk files. "my doubt is this method is posible to replace frameworks files..?"
Click to expand...
Click to collapse
yes just push to system and set permissions - normally rw-r-r
although I dont know why you would want to do this as its always better to flash the file and since you have a flashable zip why not just flash it
Just a confuse
marcussmith2626 said:
yes just push to system and set permissions - normally rw-r-r
although I dont know why you would want to do this as its always better to flash the file and since you have a flashable zip why not just flash it
Click to expand...
Click to collapse
as by my knowlege While replacing framework files means it will stuck the mobile then how can we set permission.. ? please help me.. and yes u said is correct but creating update.zip which need an a computer i am so lazy
krsharjun said:
as by my knowlege While replacing framework files means it will stuck the mobile then how can we set permission.. ? please help me.. and yes u said is correct but creating update.zip which need an a computer i am so lazy
Click to expand...
Click to collapse
with root browser you can set permissions of any file - please search how
it depends what framework files you are replacing - you cant just replace with any old file from a different rom - it wont work
if its been designed for your rom or you are modding your own files then thats fine
and a flashable zip takes two secs - you dont need a pc - and iv posted a template loads of times
here is it again - just add any files you want to flash to framework in the framework folder
if you want files to go to the app folder just create a folder in system in the zip called app and put files there
same for any other folder in system
http://d-h.st/sr9
Hey all,
I'm a HUGE fan of the true stock AOSP keyboard with the long-press alternates on every key. However, it is always difficult to get it installed (or find the proper files on the web, for that matter). This tutorial is NOT for the newish Google Keyboard on the Play Store - I consider that one an inferior frakking piece of shtako. But everyone is entitled to their own opinions.
Anyhow, here are two tutorials to install the AOSP Keyboard on the OnePlus X. First tutorial is for those people running OOS 2.2.0-X (i.e. the latest OTA). Second tutorial is for those people running OOS 2.2.0 (i.e. without the latest OTA - y'all have it easier than those of us who updated!)
Before you begin... I'd recommend performing a Nandroid backup through your recovery (TWRP/CWM/etc).
FIRST TUTORIAL - IF YOU'VE UPDATED TO OOS 2.2.0-X:
1. Download the attached AOSP Keyboard.zip file & extract to your SD card.
2. Go into your file manager & browse to Root/system/app. Look for the folder LatinImeGoogle.
3. Rename the LatinImeGoogle folder to something else. I used LatinImeGoogle-backup for safety reasons. Always leave yourself an out!
4. Change the LatinImeGoogle-backup folder permissions to r-r-r (really this is flexible - just use something other than what is currently assigned to the folder.)
5. Go back to where you extracted the AOSP Keyboard folder contents.
6. Copy libjni_latinime.so to system/lib/
7. Set libjni permissions to rw-r--r-- (aka 644)
8. Copy LatinIME folder to system/app/
9. Set LatinIME folder permissions to drwxr-xr-x (aka 755)
10. Open "LatinIME" folder.
11. Set LatinIME.apk permissions to rw-r--r--(aka 644)
12. Set "lib" folder permissions to drwxr-xr-x (aka 755)
13. Open "lib" folder.
14. Set "arm" folder permissions to drwxr-xr-x (aka 755)
15. Open "arm" folder. IF there is anything in the "arm" folder, delete it. (Sometimes Android will auto add libjni_latinime.so in there. Just delete it).
16. Go back to your root /system/lib/ and scroll down to libjni_latinime.so.
17. Long press on the libjni_latinime.so file. Choose "Create symlink".
18. In the Symlink location field, choose Browse. Navigate to /system/app/LatinIME/lib/arm/ and Create the symlink there.
19. Go back to your root /system/app/LatinIME/lib/arm/. You should now see a symlink "shortcut" to libjni_latinime.so. Set the shortcuts permissions to rw-r--r-- (aka 644).
20. Reboot your device.
21. Celebrate with a cookie!
SECOND TUTORIAL - IF YOU'RE RUNNING OOS 2.2.0 WITHOUT THE LATEST OTA:
1. Download the attached AOSP Keyboard.zip file & extract to your SD card.
2. Copy libjni_latinime.so to system/lib/
3. Set libjni permissions to rw-r--r-- (aka 644)
4. Copy LatinIME folder to system/app/
5. Set LatinIME folder permissions to drwxr-xr-x (aka 755)
6. Open "LatinIME" folder.
7. Set LatinIME.apk permissions to rw-r--r--(aka 644)
8. Set "lib" folder permissions to drwxr-xr-x (aka 755)
9. Open "lib" folder.
10. Set "arm" folder permissions to drwxr-xr-x (aka 755)
11. Open "arm" folder. IF there is anything in the "arm" folder, delete it. (Sometimes Android will auto add libjni_latinime.so in there. Just delete it).
12. Go back to your root /system/lib/ and scroll down to libjni_latinime.so.
13. Long press on the libjni_latinime.so file. Choose "Create symlink".
14. In the Symlink location field, choose Browse. Navigate to /system/app/LatinIME/lib/arm/ and Create the symlink there.
15. Go back to your root /system/app/LatinIME/lib/arm/. You should now see a symlink "shortcut" to libjni_latinime.so. Set the shortcuts permissions to rw-r--r-- (aka 644).
16. Reboot your device.
17. Celebrate with a brownie!
I've also tucked a txt copy of the barebones instructions into the zip file.
Feel free to ask any questions below.
Cheers,
equi
hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas
lukas235 said:
hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas
Click to expand...
Click to collapse
To create a symlink I used the root Explorer pro
lukas235 said:
hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas
Click to expand...
Click to collapse
Glad it worked out in the end. I use Solid Explorer now. About a year ago, I gave up on ES since they were dropping & hidden files onto my SD card. I'd suggest looking around for another file manager if you can.
Sent from my OnePlus using XDA Labs