can anyone tell how install infoalarm on firefly rom. Thank you
You don't "install" it you just need to copy it to /system/app with root explorer, super manager, another file manager with root access, or using adb commands.
A reboot may be necessary as well.
I got the file (infoalarm.apk) tried moving it over to /system/app dir, but root explorer will not do this. I have downloaded 'Terminal Emulator' but I can not find the proper commands to do it correctly. Any help please?
In the top right corner of root explorer there is a button that says "mount r/w" press that BEFORE you paste.
studacris said:
In the top right corner of root explorer there is a button that says "mount r/w" press that BEFORE you paste.
Click to expand...
Click to collapse
I tried that... selected copy file, go back to click 'mount r/w' then go into system/app and select paste. A window pops up and disappears under a second.
The top window in the systems/app says... 218.5 mb used, 57.32mb free, r/w 'Mount R/O' (button). Nothing happens when I tap on it.
Why wouldn't that be working? What about thru TE?
Thanks!
Did you allow root explorer, superuser access? If you didn't that button wouldn't work.
studacris said:
Did you allow root explorer, superuser access? If you didn't that button wouldn't work.
Click to expand...
Click to collapse
ya every time I go into it, it has the pop up screen on the bottom saying superuser access, and in su it logs root explorer with su access. When I click 'Mount R/W' (on the first screen) it does change, so the button now reads 'Mount R/O', but after coping and pasting nothing happens.
AS for TE I'm getting the error I have read else where.
SU
# mount -o rw,-remount /system (enter)
I get (Usage: mount [-r] [-w] [-o options] [-t type] device directory
#)
This is firefly ROM, not making sense?
---------- Post added at 04:09 PM ---------- Previous post was at 03:57 PM ----------
Trying to restore it right now via titanium back up, APP only and it is just sitting here running, doubt it will work, but was worth a shot. Still running.
Well I had to use 'Super Manager' from the market. Before going into /system it asks you if you want to RW, click yes and then you can copy and paste the infoalarm.apk into /system/app. Reboot and the app is there. Hurray! However it doesn't have the widget/screen that is on 2.1, but still works when you go in.
Weird why root explorer didn't work... oh well!
Related
I found a thread over in the I9000 section that may explain our problems with the Market on JH2.
http://forum.xda-developers.com/showthread.php?t=757461
This would seem to suggest that if you are running an unreleased firmware you need to replace the build.prop file from the released version in order to fix the market.
I have not tried this yet, I need to find the build.prop file from the original firmware first.
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Explorer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
I found this JF6 build.prop file in the stock system dump here. Let's see how this works:
http://forum.xda-developers.com/showthread.php?t=730226
Uploaded the stock build.prop to /system. It seems to make no difference in terms of availibility of the missing apps (only tried Fandango, but still missing). Grrrrr...need solution.
This did work for me. Thanks for the JF6 build.prop file.
This requires a rooted phone. You can brick your phone messing around with root. Not my fault...
I shut down the Market app, cleared its cache in Settings/Applications/Market (Filter select All Files to show Market app).
I added the JF6 build.prop to /system, replacing the JH2 version. I use root explorer to move the file on and off the SD internal.
Changed the permissions back to rw-r-r, using root explorer permissions. When the file is transferred back to the phone from the SD, the permissions will be rw-rwx-rx. Changed ownership back to root.root on the phone using terminal emulator:
$ su
# chown root.root /system/build.prop
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
rajendra82 said:
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
Click to expand...
Click to collapse
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
dontshakepandas said:
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
Click to expand...
Click to collapse
Working now. This is great. Now with the last issue resloved, I can keep the new firmware around. This needs a sticky, with all these weekly firmware releases from samsung-firmwares showing up.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Can you post the commands used to do this for users who aren't as knowledgeable.
yes. walkthrough please?
would love to get this working, I don't want to have to flash back to original.
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
Edited post with details
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
daverup said:
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
Click to expand...
Click to collapse
Either that, or get a full flash of the newly released Froyo firmware with GPS Fix in September (hoping and praying), and flash it forward to the new stock version. Of course, not all parts of the system are fooled. Checking Settings -> About Phone, still shows the correct JH2 information.
Nice. Seems to have worked. Funny, it didn't work until after i installed/ uninstalled a couple items.
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
staySICK said:
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
Click to expand...
Click to collapse
I am guessing that your root privilages are not working. Does you phone give you a popup when you do su in ADB shell. If so, tell the phone to allow su privlages to ADB in that popup. If you do, ADB should not complain. If that doesn't work, you have to redo your rooting procedure, as something might be messed up there.
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
staySICK said:
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
Click to expand...
Click to collapse
Probably best to ask about this issue in that thread, as more knowledgeable folks might know how to overcome this.
rajendra82 said:
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app.
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
Click to expand...
Click to collapse
This worked for me, one thing to note, when I ran the last command from Root Explorer "# chown root.root /system/build.prop" Root Explorer responded with
chown: unknown user/group root:root
But after restarting and installing/uninstalling a few apps Fandango shows up where it did not before.
Thanks.
This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot
has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads
No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
A good guide, if a little misplaced, but another option is the /system overlay.
JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes
where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd
Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.
Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App
Can you link me the apk of adfree? I can't download the app from my phone
BTW it's 'ADs" single d
short for advertisment (notice the single d?)
Fixed that English is not my main language
Sent from my Legend using XDA App
JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.
It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)
Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.
When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?
I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.
adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!
Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)
Is this so i can push files through my phone, without having to do it on the computer? How does this work. Anyone have a link? I did a search and came up with nothing. Just wondering, thanks!
It's the same as a Terminal on a unix/linux box or for that matter, command line on a windows box.
Terminal emulator app will give you command line access to your (rooted) phone. You can then go into SU mode, as well.
Yes, you are correct, it will allow you to do things that an ADB shell would allow, from a computer.
You can download it from the market.
im sure that you might have known this already, but when you are using a terminal emulator, and you get root access (su), you really should follow the directions to the letter. if you make a mistake in the typing, it is possible that you could do some damage.
it is also recommended to not enter in terminal commands unless someone with more experience than you (based off their post number) reports success in completing the wanted task. so essentially, use the terminal at your own risk.
(all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
What does "cat" mean?
Oh my bad i didn't see it in there, all the times i lookedO sorry.
where could i get this app?
i couldnt find it on market using keyword "terminal", "terminal emulator" or even "adb terminal emulator"
bla.k.offee said:
where could i get this app?
i couldnt find it on market using keyword "terminal", "terminal emulator" or even "adb terminal emulator"
Click to expand...
Click to collapse
https://market.android.com/details?id=jackpal.androidterm&feature=search_result
Terminal Emulator Hell!!!!
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventur, 6+ hours ago. Any help would be great.
hockeyfamily737 said:
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventur, 6+ hours ago. Any help would be great.
Click to expand...
Click to collapse
I keep TB on the root of my sdcard named TB.apk. Then I go into terminal emulator (it is in most roms already).
su
cp /sdcard/TB.apk /data/app/TB.apk
Then I back out of TE and TB is installed. Any commands you type in TE are case sensitive. All file names are case sensitive and spaces do not work well. So if your TB apk is "Titanium Backup-1.3.3.apk", I would rename it to something without the spaces like Titanium_Backup-1.3.3.apk.
I rename it TB.apk because who wants to type all of that?
kyouko said:
(all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
Click to expand...
Click to collapse
Sent you a pm
#Root/Hack_Mod-Always®
Okay, I hate to ask, because I just know it's been asked before.
I've done a search and also read the adb how to here:
http://forum.xda-developers.com/showthread.php?t=723596
So I'm going to ask anyway, and I apologise profusely.
I am trying to push a file back to my Samsung Galaxy I9000.
I have it rooted using 'Super one click', and have managed to pull the file from the phone.
When I try to push it says 'Failed to copy, file is a read-only system'
The suggestions so far have included 'Adb remount', which gives me an additional error.
remount failed: No such file or directory
Also when I jump in shell apparently I am supposed to see a $, which indicates ADB is ready, instead I am seeing a #. I assume this means I'm not in super user mode, but unsure how to get there.
Any assistance appreciated. Basically I'm trying to upload a glass task bar just to get an idea of how to play around with this. But I get stuck at the first hurdle.
Yes, I have created backups of the files I am pulling and pushing
Thanks.
The easiest way if you're rooted is to use root explorer. Just go in the directory where you want to put the file, click in the upper right corner below the clock on R/W to change the system from read-only (R/O) to read & write and you're good to go to do whatever yoy want with the files on your phone.
edit: Also, you get in super user mode when you write su
is that adb su insert command here ?
Well, you asked how to get in super user mode - just write su. But I think # is what you should be getting in super user mode and not the dollar sign. Also, did you try using root explorer
Yeah, went and purchased root explorer. Does the job well, (cheers for that) I was just hoping to understand the computer system also.
there is a free program alternative to root explorer and i use it .it's supermanager.
I think this might help (for understanding)
adb shell
su
mount -rw,remount /dev/block/stl9 /system. (u can know u r /system complete path by typing "mount" in the shell).
after ur work
mount -ro
exit
exit
hope this helps.(The part i got stuck was after mounting as rw i could not get it back to ro )
I have a problem.
I want to install AX8MT.Ko but I have to change the modules permission because every time when I write on terminal "insmod/system/lib/modules/ax8mt.ko telling me operation not permitted
I want a step-by-step tutorial for changing modules permission.
I will press thx button!
Sorry for my English!
fuuuuuuuuuuuuuuu said:
I have a problem.
I want to install AX8MT.Ko but I have to change the modules permission because every time when I write on terminal "insmod/system/lib/modules/ax8mt.ko telling me operation not permitted
I want a step-by-step tutorial for changing modules permission.
I will press thx button!
Sorry for my English!
Click to expand...
Click to collapse
You have to enter "su" first - only root is allowed to load or unload kernel modules!
B.Jay said:
You have to enter "su" first - only root is allowed to load or unload kernel modules!
Click to expand...
Click to collapse
I write but the same result
You need Root Explorer for doing this.
You can buy it on the market, or search on google for a cracked apk.
In RE, you go to the folder and long-press on the module, and in the menu choose "change permissions".
I did this but don't work, any ideas?
In Root Explorer, you need to mount the /system partition as rw first.
To do this, click on the small button in the right corner of your screen.
After that, you can set the permissions, delte or edit files and other things you can do in a file explorer
codfreak said:
In Root Explorer, you need to mount the /system partition as rw first.
To do this, click on the small button in the right corner of your screen.
After that, you can set the permissions, delte or edit files and other things you can do in a file explorer
Click to expand...
Click to collapse
I did this because I can't. change permission if I don't press the little button. I want a master member
You know, all you have to do is READ ...
1. Copy ax8mt.ko to your SD card
2. Start Root Explorer and navigate to /sdcard
3. LONG press ax8mt.ko and select "MOVE"
4. Navigate into /system/lib/modules
5. Press "Mount r/w"
6. Select "Paste"
7. LONG press ax8mt.ko and change permissions to
r w -
r - -
r - -
8. Exit Root Explorer
9. Open the terminal
10. Type (followed by enter after each line)
su
insmod ax8mt.ko
Alternatively you can do the whole thing in just the terminal (assuming you already copied ax8mt.ko to your SD card):
Type:
su
cp /sdcard/ax8mt.ko /system/lib/modules
chmod 644 /system/lib/modules/ax8mt.ko
insmod ax8mt.ko
If you can't get this simple thing done you better don't even keep on trying.
B.Jay said:
You know, all you have to do is READ ...
1. Copy ax8mt.ko to your SD card
2. Start Root Explorer and navigate to /sdcard
3. LONG press ax8mt.ko and select "MOVE"
4. Navigate into /system/lib/modules
5. Press "Mount r/w"
6. Select "Paste"
7. LONG press ax8mt.ko and change permissions to
r w -
r - -
r - -
8. Exit Root Explorer
9. Open the terminal
10. Type (followed by enter after each line)
su
insmod ax8mt.ko
Alternatively you can do the whole thing in just the terminal (assuming you already copied ax8mt.ko to your SD card):
Type:
su
cp /sdcard/ax8mt.ko /system/lib/modules
chmod 644 /system/lib/modules/ax8mt.ko
insmod ax8mt.ko
If you can't get this simple thing done you better don't even keep on trying.
Click to expand...
Click to collapse
do you know another mod to enable dualtouch for games.