[TUT] V6 SuperCharger & Kickass Kerneliser Scripts & init.d Tutorial [All Devices]
For Tipo/Dual/miro/J/E
Hi all just wanted to share this because i dint see any threads on it. old android users like me will no what these are but for new users these scripts will install new tweaks and performance enhancements to stock rom & kernel. you have to install script manager from google play to run these scripts. all thanks go to the original author Zepp make sure you thank them.
init.d Tutorial
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel.
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 r.w.e, r.x.e, r.x.e
OR
b. If the file install-recovery.sh is already here, 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 i've repacked it to work it flashes to xperia j don't know about Tipo/Dule/Miro
if it doesn't extrack and push the files to there relevant places in /system.
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!
All credits for this tutorial go to iridaki & Doomlord. i just copied and pasted for new users & people who don't like searching to make it easier to find.
Original Thread: http://forum.xda-developers.com/showthread.php?t=1422061
First Time SuperCharge Tutorial
First of all downloads go here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 and download V6 supercharger update9 rc12, kickass kerneliser update 3 rc11 & the supercharger starter kit Rc12 zip and move them to the root of your sd card. then download & install script manager from google play.
Applying SuperCharger Starterkit
Next extract supercharger starterkit.zip to the root of your sd card (the easyest way would be with root explorer). Then open script manager and click browse as root then select ok. next navigate to sdcard and click StartMeUp.sh that was extracted from the zip (it will prepare your rom and install the features from the zip at onece) click the su icon (This is superuser) then click run grant the superuser prompt and follow any on screen instructions. after script has finished exit out by clicking the X icon in the top lefthand corner. You should be using the new RC12 this one gives you the option to install which features you want if your on jb all you need is the zipaline binary the bussybox and the su binary is for a fault in ics also if your USING SUPER SU DO NOT INSTALL THE SU BINARY AS SUPER SU USES A DIFFARENT BINARY!!!
Running V6 SuperCharger & KaK Scripts
Note if you have init.d do not follow the run at boot part. as the 99supercharger.sh & 98kickasskernel.sh scripts will run as shell scripts at boot.
In script manager navigate to where you saved V6 superCharger then select it then use the same prosses click the su icon then run follow all on screen instruction and choose which options you would like. do the same for the kak script. after you have ran both scripts in script manager navigate to the file v6 supercharger wich will have been created in the internel sdcard. Find 99supercharger.sh we want to run this scrip at boot so select it press su and this time the boot icon then run grant superuser prompt if requsted then let the script finish following any instructions then exit out. Do the same for 98kickasskernel.sh. then reboot. you should now be supercharged.
init.d is 100% recommended so follow that first
This is what i have done and has worked for me. Follow At Your Own Risk I Am Not Reponsable For Any Damage Your Device Suffers
V6 SuperCharger Original Thread: http://forum.xda-developers.com/showthread.php?p=16635544#post16635544
New V8 SuperCharger Is In Alpha Stage So Use At Your Own Risk
V8 SuperCharger Original Thread:http://forum.xda-developers.com/showthread.php?t=1250276
For tipo only or evry phone
Sent from my ST21i using xda app-developers app
tusharkulkarni008 said:
For tipo only or evry phone
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
For every android device mate
Re: V6 SuperCharger & Kickass Kerneliser Scripts. + New V8 Supercharger
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app
tusharkulkarni008 said:
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
Do you mean v6 starterkit
Re: V6 SuperCharger & Kickass Kerneliser Scripts. + New V8 Supercharger
+1
Sent from my GT-I9000 using Tapatalk 2
tusharkulkarni008 said:
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
sorry im not to sure about that. backup and have a try
What is the purpose of this? Sorry for the noob question. And will this work on cm10?
exelion04 said:
What is the purpose of this? Sorry for the noob question. And will this work on cm10?
Click to expand...
Click to collapse
the main purpose ive used it for is to stableise stock xperia roms ive used it since my xperia x8 from 2010 it even helped minicm 7 on it. the slight modifications to the rom kernel and 3g network is defiantly apparent. if u want to run it on cm10 then make sure u download the jb script the main thing i use it for is the home screen redrawing but when rom is 100% SuperCharged thats a thing of the past im not an expert with these scripts but there useful thats why ive shared the links.
Not Working.
When ever I try to run the StartMeUp.sh it with the root access it carries on running for infinity time . Dont know whats wrong with me.
RounakCreationz said:
When ever I try to run the StartMeUp.sh it with the root access it carries on running for infinity time . Dont know whats wrong with me.
Click to expand...
Click to collapse
Is it showing any errors when its running.
Added
init.d tutorial added
Re: V6 SuperCharger & Kickass Kerneliser Scripts & init.d Tutorial
Startmeup.sh runs towards singularity dosent stop
noob and learning
tusharkulkarni008 said:
Startmeup.sh runs towards singularity dosent stop
noob and learning
Click to expand...
Click to collapse
Ive never heard of that happening before I will look into it when im home from work
I installed supercharger 6 with Die hard launcher...the system works very well but I don't if is coincidence but I see that battery drains faster than without supercharger :S is it normal?
ercea said:
I installed supercharger 6 with Die hard launcher...the system works very well but I don't if is coincidence but I see that battery drains faster than without supercharger :S is it normal?
Click to expand...
Click to collapse
yes if the battery tweaks are not installed did you install them
gavster26 said:
yes if the battery tweaks are not installed did you install them
Click to expand...
Click to collapse
Are you referring the Die Hard battery calibrator script? I installed but I don't know if I did it well. The steps that I did was:
- Charge battery up 100%
- Run Die hard calibrator and execute the "wait 20 mins" option
After that, system restarts... but I didn't see any success/error messages and I don't know if it's working. If the steps are incorrect, please, can you say me the correct process??
Regards!
ercea said:
Are you referring the Die Hard battery calibrator script? I installed but I don't know if I did it well. The steps that I did was:
- Charge battery up 100%
- Run Die hard calibrator and execute the "wait 20 mins" option
After that, system restarts... but I didn't see any success/error messages and I don't know if it's working. If the steps are incorrect, please, can you say me the correct process??
Regards!
Click to expand...
Click to collapse
wich script of v6 supercharger are you using it should be update9 Rc11. im not finding that option you should be using that one. you will get abit more battery drain more performance = more power.
tusharkulkarni008 said:
Startmeup.sh runs towards singularity dosent stop
noob and learning
Click to expand...
Click to collapse
hi ive trawlled the web i have not found anyone ever having that problem. you can try reinstalling script manager and installing busybox from google play. i no startmeup.sh installs busybox 1.19.4 withdrawu but it will help sorry if this is not much help as i say in tutorial i did not create it i just shared it. if problem persists then your device may not be properly rooted. if all else fails go to v6 original thread and ask zepprinox
gavster26 said:
hi ive trawlled the web i have not found anyone ever having that problem. you can try reinstalling script manager and installing busybox from google play. i no startmeup.sh installs busybox 1.19.4 withdrawu but it will help sorry if this is not much help as i say in tutorial i did not create it i just shared it. if problem persists then your device may not be properly rooted. if all else fails go to v6 original thread and ask zepprinox
Click to expand...
Click to collapse
it can be made flashable just a suggestion
Related
Hey people I have recently developed overclocking scripts enjoy!!!
Please tell me if you find any problems
Will work on all custom GB roms
Fixed bugs
Readonly error fixed
All you need is in the zip file including instructions
Instructions
Step 1
Copy opperator.ko & symsearch.ko to sdcard (root)
Step 2
Install and run script manager
Step 3.1
Run Copy Modules Script as root only once
View attachment 803999
Step 3.2
Run Intall Modules Script as root & at boot
View attachment 804000
Step 3.3
Run Overclock Script as root and Select Cpu speed
View attachment 804001
Step 4 Enjoy !!!
What is different on your modules ? Or you just explaining how to install tekahuna's ones ?
It's the same Modules Ijust created the scriptsto make the overclocking easier
Thanks. Will it work on Acura V5 ? I tried earlier zip from tekahuna's and it not only not work but also changed the clock to default. HOwever I had to manually edit the overclock.sh in system folder to change the clock to 1230mhz.
Yes it will work for any GB rom
Doesn't work, I get error something like: Cannot copy opperator.ko to the system readonly error. and cannot find systemsearch.ko.
visualizer2k said:
Doesn't work, I get error something like: Cannot copy opperator.ko to the system readonly error. and cannot find systemsearch.ko.
Click to expand...
Click to collapse
is true, I'm the same
copy modules manually to system/lib/modules with roor explorer
just use2 modules, firstly install modules then overclock
a shortcut of overclock will be useful
running on Stock GB?
if you have root, it will work
visualizer2k said:
Doesn't work, I get error something like: Cannot copy opperator.ko to the system readonly error. and cannot find systemsearch.ko.
Click to expand...
Click to collapse
No problem i'll fix it.
richard711 said:
No problem i'll fix it.
Click to expand...
Click to collapse
thanks, richard711
I need to hit 1230 or 1240 so can it be edited in the script?
Never mind i edited the script and changed to 1 for 1200 2 for 1230 and 3 for 1240. So far at 1240 it's doing fine and beating samsung by good margin in CF. 11560, 3600 6404
O.k people I fixed the bugs
I'll bring out extra overclocking speeds soon !!!
I've tried this metod, and it works great and it's so easy, but I've got one nob question...
Everytime a reboot the phone, must I do the process again?
Yes just the overclocking script but i'm currently trying to change it so it will stay the same speed after a reboot
Sent from my LG-P920
Its not working for me.
I'm on stock rooted GB Europe v21a Nov 15 2011, the latest I suppose.
Did I do something wrong?
ßєş┼ rєGąrđş
ąßđЦL rєJąЙ
şєЙ┼ Fr๏M MY LG ๏P┼IMЦş 3D
Can someone attach "Script Manager", can't download the free app from market due to "Incompatible device" running CM7.2.
Doesn´t work?!!?!
Rooted 2.3 GB and I´m doing just like in first page,
it wount let me copy:
Cannot create ' /system/lib/moduls/symsearch.ko' Read-only file system
Cannot create ' /system/lib/moduls/opperator.ko' Read-only file system
What I am doing wrong or is it just this ****ty system what sucks?!?!
Atleast in computer those don´t seem to be read-only files?
Can anyone please tell me how to get init.d support on rooted stock rom? If its possible by flashing any kernel then please tell me a kernel that will work.
For solution see post number 6
Cranium supports init.d scripts, but apparently some people have had it not work with stock ROM. Personally it's working fine for me (using rel #2, #3 has a bug).
EDIT: Fairly sure Titanium support them as well. Don't know if it works well with stock ROM or not.
Trying out...
Won't work wit Stockrom
Sent from my HTC
vjz567 said:
Won't work wit Stockrom
Sent from my HTC
Click to expand...
Click to collapse
I personally have it working on stock ROM.
Method to get init.d support on stock rom
I thoroughly searching on many websites i found a way to do it
I found a tutorial here
SOME EXTRA INSTRUCTIONS:
I tried out the method myself on a pre-rooted stock rom. The tutorial mentioned above provides a .zip file that you can flash via CWM. I was successful in getting the test init.d script to run without creating install-recovery.sh, which the tutorial asks you to create.
:good::good:
Hit thanks if i helped
thank you for the guide.....:good:
sabaatworld said:
I thoroughly searching on many websites i found a way to do it
I found a tutorial here
SOME EXTRA INSTRUCTIONS:
I tried out the method myself on a pre-rooted stock rom. The tutorial mentioned above provides a .zip file that you can flash via CWM. I was successful in getting the test init.d script to run without creating install-recovery.sh, which the tutorial asks you to create.
:good::good:
Hit thanks if i helped
Click to expand...
Click to collapse
Whats the role of busy box here?
and I have to write following code manually?
Code:
# init.d support
busybox run-parts /system/etc/init.d/
I have done it and when i flash init.d zip file i got "installation aborted"
U can also try pimp my Rom ....through this you can also add init.d support to ur stock kernal.
typed from htc pico powered by nextgen 1.5
droidbot678 said:
Whats the role of busy box here?
and I have to write following code manually?
Code:
# init.d support
busybox run-parts /system/etc/init.d/
I have done it and when i flash init.d zip file i got "installation aborted"
Click to expand...
Click to collapse
For installation aborted
Check a2SD on stock rom in index and check FAQ section on that post
Sent from my HTC Explorer A310e using xda app-developers app
rockingmanish said:
U can also try pimp my Rom ....through this you can also add init.d support to ur stock kernal.
typed from htc pico powered by nextgen 1.5
Click to expand...
Click to collapse
Use this method. Its much better and works. I have tested it
Sent from my LT26i using xda premium
@sabaatworld: Dude that method seemed to work for you but i have tried ur method (by not making that file) and the original one as well but both failed for me. Even tried to flash the .zip file in twrp as well but it did not work so can u tell me which stock rom are u using?? i mean is it the indian one or some else. help would be appreciated...
xedi95 said:
@sabaatworld: Dude that method seemed to work for you but i have tried ur method (by not making that file) and the original one as well but both failed for me. Even tried to flash the .zip file in twrp as well but it did not work so can u tell me which stock rom are u using?? i mean is it the indian one or some else. help would be appreciated...
Click to expand...
Click to collapse
Did you leave an extra empty line
And did you give it full 777 permissions to install-recovery.sh?
"If it's not now, then it's when"?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
ptcpayme said:
Did you leave an extra empty line
And did you give it full 777 permissions to install-recovery.sh?
"If it's not now, then it's when"?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
Click to expand...
Click to collapse
The permission are the same as given by the iridaki in the tutorial. aren't they?? and about that extra empty line, do i need to simply press the enter key to go down and leave that line empty or do i have to press the space key to leave that line??
xedi95 said:
The permission are the same as given by the iridaki in the tutorial. aren't they?? and about that extra empty line, do i need to simply press the enter key to go down and leave that line empty or do i have to press the space key to leave that line??
Click to expand...
Click to collapse
Press enter twice.
Just give it full permissions anyway.
Did you get "done" in /data /local /tmp ?
"If it's not now, then it's when"?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
ptcpayme said:
Press enter twice.
Just give it full permissions anyway.
Did you get "done" in /data /local /tmp ?
"If it's not now, then it's when"?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
Click to expand...
Click to collapse
gonna try right now. keeping my fingers crossed:fingers-crossed:
edit: flashing the zip fails . M gonna flash sense 4.0 instead
ptcpayme said:
For installation aborted
Check a2SD on stock rom in index and check FAQ section on that post
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Tried this but i am getting same message "Status 0" Installation aborted
imran521 said:
Tried this but i am getting same message "Status 0" Installation aborted
Click to expand...
Click to collapse
Exchange update binary from cranium kernel to the new one.. it should work..
(there's also one uploaded there )
Can you post Giving clear and full details, if it doesn't work.
Sent from my HTC Explorer A310e using xda app-developers app
Dude, download the stock Rom by immortal yash with ext support. Will save a lot of hassle.. 2nd one in this http://forum.xda-developers.com/showthread.php?p=39590976
i got *** syntax error when i run the script on my O3D p920.. i installed busybox 1.18.2.. and script manager. im sorry, im newbie here, using this script... can someone help me...
heres the link... http://forum.xda-developers.com/showthread.php?t=991276
tambol said:
i got *** syntax error when i run the script on my O3D p920.. i installed busybox 1.18.2.. and script manager. im sorry, im newbie here, using this script... can someone help me...
Click to expand...
Click to collapse
Post the scripts so the dev's can see whats wrong with
i download this V6_SuperCharger-AOR.zip from this link http://forum.xda-developers.com/showthread.php?t=991276 and V6_SuperCharger_for_Android-update8.sh.txt... in that link also. when i click that, they open in another window. is it right, that i copy all the txt and paste it in another notepad that ends with .sh.txt??? im sorry again..
heres what i do... i extract the V6_SuperCharger-AOR.zip at the root of my sd cardthen i open the script manager an choose browse as root. then browse to V6_SuperCharger_for_Android-update8.sh.txt and choose su then run... the in end says 87: syntax error: expecting "in"... is my steps are right? if not, can you help me how to do???
tambol said:
heres what i do... i extract the V6_SuperCharger-AOR.zip at the root of my sd cardthen i open the script manager an choose browse as root. then browse to V6_SuperCharger_for_Android-update8.sh.txt and choose su then run... the in end says 87: syntax error: expecting "in"... is my steps are right? if not, can you help me how to do???
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=1301041&d=1346732906
DOWNLOAD THIS and open it with script manager
Pesach85 said:
http://forum.xda-developers.com/attachment.php?attachmentid=1301041&d=1346732906
DOWNLOAD THIS and open it with script manager
Click to expand...
Click to collapse
wow... thanks... it helps me a lot and it works now... thanks for the help...:laugh:
Works on 2.3.7 upto 4.2.2(At least thats all I have tested).
Hi,Guys this is an awesome app here let me start by stating.
Advantages of Odexed Rom.
1.Better Battery life
2.Better app performance.
3.lower ram usage.
Disadvantages of Odexed Rom.
1.no themes can be applied(and i mean at all).
2.Lower /system space.
How to Install -Guide-
1) make sure you have a custom rooted rom / kernel with init.d support (scripts must be able to run at boot: it is a folder in /system/etc). It is very important or it won't run pre-boot scripts.
2) make sure that you don't have any themes applied before odexing or you will loose your themed apps after odexing.
3) simply put the apk in /system/app folder with a file browser like "Root Explorer" and ofcourse give correct permissions rw-,r--,r-- and reboot.
4) do a nandroid backup(just added safety) and/or a titanium backup of all user apps and system data
5)Start ODEX ME app
6) follow the onscreen instructions.
7)your device will boot several times or even boot for a long time(Its all normal).
8)to see if you rom is odexed go to /system/app partition and you will see a whole lot of .odex files.
Credit :
paulobrien : for the app.Original Thread : http://forum.xda-developers.com/showthread.php?t=1215271
Dark Passenger : for testing the app and sharing.
NOTE : doesnt work with any app2sd script that moves system dalvik cache to /sd-ext eg.INT2EXT4+
copy paste already share in galaxy mini section,anyway nice
fitranger said:
copy paste already share in galaxy mini section,anyway nice
Click to expand...
Click to collapse
hello this is no copy paste work.
yes there may be a shared thread in mini section but here i posted to share the app as I thought it might be useful for fit users.
Dark Passenger said:
Hi,Guys this is an awesome app here let me start by stating.
Advantages of Odexed Rom.
1.Better Battery life
2.Better app performance.
3.lower ram usage.
Disadvantages of Odexed Rom.
1.no themes can be applied(and i mean at all).
2.Lower /system space.
How to Install -Guide-
1) make sure you have a custom rooted rom / kernel with init.d support (scripts must be able to run at boot: it is a folder in /system/etc). It is very important or it won't run pre-boot scripts.
2) make sure that you don't have any themes applied before odexing or you will loose your themed apps after odexing.
3) simply put the apk in /system/app folder with a file browser like "Root Explorer" and ofcourse give correct permissions rw-,r--,r-- and reboot.
4) do a nandroid backup(just added safety)
5)Start ODEX ME app
6) follow the onscreen instructions.
7)your device will boot several times or even boot for a long time(Its all normal).
8)to see if you rom is odexed go to /system/app partition and you will see a whole lot of .odex files.
Credit :
paulobrien : for the app.Original Thread : http://forum.xda-developers.com/showthread.php?t=1215271
Dark Passenger : for testing the app and sharing.
Works on 2.3.7 upto 4.2.2(At least thats all I have tested).
Click to expand...
Click to collapse
How to make nandroid backup if I not have Amon-RA, than CWM5?
ZmisiS said:
How to make nandroid backup if I not have Amon-RA, than CWM5?
Click to expand...
Click to collapse
I think all recoveries support backup options(that is nandroid backup)
else backup all user apps and system data using titanium backup.
Partial odexing from fixes themes
Sent from my GT-S5570 using Tapatalk 2
Tried it!! It's Working!!!:thumbup::thumbup: Odexed my Cyanmobile rom without any issues. Thanks for sharing this ONE-CLICK-ODEX app. I really needed it.
Pls. tell if this app can odex 2.3.6 custom rom (like Razodroid,creeds...etc), I've read the heading already but just curious.
Thnks Again
Sent Via XDA™ Premium
Galaxy_Rohit said:
Tried it!! It's Working!!!:thumbup::thumbup: Odexed my Cyanmobile rom without any issues. Thanks for sharing this ONE-CLICK-ODEX app. I really needed it.
Pls. tell if this app can odex 2.3.6 custom rom (like Razodroid,creeds...etc), I've read the heading already but just curious.
Thnks Again
Sent Via XDA™ Premium
Click to expand...
Click to collapse
yes.
Looks interesting will try it!!
For me in CM 10.1 Setting.apk removed and it has disappeared in the menu.How to solve it?
Android Daymon said:
For me in CM 10.1 Setting.apk removed and it has disappeared in the menu.How to solve it?
Click to expand...
Click to collapse
Huh what sorry are you saying that you placed the apk in /system/app partition gave it permission rw-,r--,r-- rebooted , clicked on the app icon from the app drawer of odex me. choice odex now let the phone remain aside till it stabalised about 5 min max. and then your settings app is not there.
what did you do cause I am using latest release and nothing happened.
Yes,I do what you say.but my settings disappeared.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
Doesn't it work with INT2EXT4+?????
Android Daymon said:
Yes,I do what you say.but my settings disappeared.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
Doesn't it work with INT2EXT4+?????
Click to expand...
Click to collapse
OH MY did you do the steps I mentioned after flashing int2ext4+ no wonder go into /system/app and tell me if there is a file called settings.apk and settings.odex
for most safe and best result always run first any script. mod .anything you need done then flash any app2sd script.
Sry... but I can't odex official cyanogenmod (2.3.7). It goes to bootloops. (Cyanmobile, Razodroid etc. were odexed successfully by your mentioned method but not this one)
Sent Via XDA™ Premium
Galaxy_Rohit said:
Sry... but I can't odex official cyanogenmod (2.3.7). It goes to bootloops. (Cyanmobile, Razodroid etc. were odexed successfully by your mentioned method but not this one)
Sent Via XDA™ Premium
Click to expand...
Click to collapse
I'm using cm7 official odexed so what exactly did you do is your dalvik cache moved to /sd-ext cause that will explain the boot-loop.
sol. don't use any app2sd solutions till after you have odexed k.
Dark Passenger said:
I'm using cm7 official odexed so what exactly did you do is your dalvik cache moved to /sd-ext cause that will explain the boot-loop.
sol. don't use any app2sd solutions till after you have odexed k.
Click to expand...
Click to collapse
I use Link2SD. I also used Link2SD on Cyanmobile too but no bootlooping in that while odexing.
So, do I've to unlink all the links of Link2SD & then try odexing??
If Yes, then I'll give it a try...
Sent Via XDA™ Premium
Galaxy_Rohit said:
I use Link2SD. I also used Link2SD on Cyanmobile too but no bootlooping in that while odexing.
So, do I've to unlink all the links of Link2SD & then try odexing??
If Yes, then I'll give it a try...
Sent Via XDA™ Premium
Click to expand...
Click to collapse
that doesnt make any sense link2sd moves only user installed apps not system so should give no problem....? but you can try and unlink from link2sd and see how it goes.
After I installed this OdexMe, in system/app, I have only 4,96 MB free.
ZmisiS said:
After I installed this OdexMe, in system/app, I have only 4,96 MB free.
Click to expand...
Click to collapse
hmm thats actually not really any problem or bug the app converts the dex files to odex files and stores the file onto /system/app basically the dalvik cache of system apps is moved to the /system/app directory. Hence the lower space.
Dark Passenger said:
hmm thats actually not really any problem or bug the app converts the dex files to odex files and stores the file onto /system/app basically the dalvik cache of system apps is moved to the /system/app directory. Hence the lower space.
Click to expand...
Click to collapse
I know, but now I can't install some applications.
Is there a possibility that I can remove .odex files, and that I do not again install ROM?
This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.
Reserved just in case
Buddyjohn said:
This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 and been trying all kind of things to get to media_rw folder to keep its read writable and nothing worked so far. I did everything in you post to see if it would help/work but script not working. I can only keep permissions if I set manually set permission using root browser and then it working until I reboot the phone and I tried adding the script using ROM Toolbox pro but its not even changing the media_rw permission when run it.
This my first time using the script tool but to me seems to be setup properly. If needed I will get some screenshots of the script windows to show how I set it up. I am just posting this now to see if anyone can help or wants to ask some questions.
I know how permissions work in Windows and getting up to speed with Android. I been trying to make the media_rw folder r/w to be able to able to path it to my Titanium Backup folder on my external SD.
This looks similar to setting boot bat files in Windows so I know it should work but no go so far.
Heres the screenshots of my script that failed to run and the output file hoping to get some advice why script did not work.
Is this thread dead? Should I seek answers elsewhere?
techmanc said:
Is this thread dead? Should I seek answers elsewhere?
Click to expand...
Click to collapse
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.
Buddyjohn said:
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.
Click to expand...
Click to collapse
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.
techmanc said:
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.
Click to expand...
Click to collapse
try these three xposed modules, i recommend enabling one at a time to see which works, reboot after enabling one.
http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521
http://forum.xda-developers.com/xposed/modules/kitkat-sd-card-access-t2790992
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267
also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.
Buddyjohn said:
also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.
Click to expand...
Click to collapse
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.
techmanc said:
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.
Click to expand...
Click to collapse
Install it to /xbin
Buddyjohn said:
Install it to /xbin
Click to expand...
Click to collapse
What the difference between installing to /xbin vs /system/bin might I ask?
techmanc said:
What the difference between installing to /xbin vs /system/bin might I ask?
Click to expand...
Click to collapse
Honestly I am not to sure, I just assumed xbin was the right one as a lot of older mods and roms required busybox on xbin. so i tried it and it worked.