I seem to be frequently flashing or messing up my G1 so I decided to write some shell scripts to help out but they seem to only half work if at all. Actually I'm not sure what they did because they displayed no output.
This script is supposed to backup the default init.rc and mountd.conf files then replace the existing ones with the modified ones.
Though it does not work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
busybox cp -a /system/etc/mountd.conf /sdcard/recovery/mountd.conf.bak
busybox cp -a /system/init.rc /sdcard/recovery/init.rc.bak
busybox cp -a /sdcard/recovery/mountd.conf /system/etc/mountd.conf
busybox cp -a /sdcard/recovery/init.rc /system/init.rc
then this is the next set to move the apks and the program caches which doesn't work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
busybox cp -a /data/app /system/sd
rm -r /data/app
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -R /data/data/com.android.browser/cache/webviewCache
ln -s /sdcard/cache/webviewCache /data/data/com.android.browser/cache/webviewCache
rm -R /data/data/com.android.vending/cache
ln -s /sdcard/cache/marketCache /data/data/com.android.vending/cache
rm -R /data/data/com.google.android.street/cache
ln -s /sdcard/cache/streetCache /data/data/com.google.android.street/cache
reboot
Plus both run and output no errors either. Who knows what problems I'll run into because I have no idea what they actually did.
Anyone see anything wrong here?
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
I have a menu that does that and I have got some experience as why it works one day and not the other.
Rafase282 said:
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
Click to expand...
Click to collapse
I took the reboot out after the mountd.conf and init.rc did not appear to copy due to the lack of /dev/mmcblk0p2 hoping to see some sort of output why it did not run. Unfortunately it runs and backs up the files but does not replace them with the modded ones.
Rafase282 said:
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
Click to expand...
Click to collapse
Not copying the apps is a good idea, modified the script to not do so.
Rafase282 said:
I have a menu that does that and I have got some experience as why it works one day and not the other.
Click to expand...
Click to collapse
Does Android require that you do a chmod on all shell scripts first?
On Debian I usually just use sudo sh ./ and it runs the script w/o changing anything on the file permissions so I figured Android would be similar if I just ran them as root. Still I see a lot of people requiring a chmod 777 on any guide referring to running shell scripts.
I will try that and report back with my findings. Thanks for replying.
Does Android require that you do a chmod on all shell scripts first? I just have to type m oon anywhere in the androud shell and my scripts run, for that i put it on /system/bin and do a chmod 4755 to the file. it is still needed to type su before you run the script.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
cp /sdcard/media/Data/mountd.conf /system/etc/mountd.conf
cp /sdcard/media/Data/init.rc /system/init.rc
Thats my code for copying the modified files to the right place. So maybe you should try that.
Oh for androoid you dont unless you put it on /system/bin then you will have to use sude and sometiems it still wont run due to lack or permisions so is better to do a chmod 4755
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
joshtheitguy said:
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
Click to expand...
Click to collapse
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
LucidREM said:
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
Click to expand...
Click to collapse
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
joshtheitguy said:
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
Click to expand...
Click to collapse
yes .. but you can't create the sym links when they already exist .. running the update.zip only wipes the /system .. not /data .. if the links were there before the update.zip they will be there after
Related
I've tried the method below and it doesn't seem to work........it doesn't give me errors......but it doesn't delete the files that I don't want anymore.
I did try searching the forums but didn't see any posts regarding this....but seeing how new the 1.5 firmware it is...I didn't think there would be a post on it anyway and didn't think the command prompt or the location of these files would change
Any help is appreciated
-Type su
mount -o rw,remount -t yaffs2 /dev/block/
mtdblock3 /system
rm -r /system/media/audio/ringtones
rm -r /system/media/audio/notifications
I did this yesterday, and removed all the stock ringtones and replaced with htc defaults.
I did this from ADB shell, I suppose you can do it from the terminal, matter of fact I'm sure you can.
The trick is to use busybox.
#commands below
busybox rm -rf /system/media/audio/ringtones # remove ringtones
busybox rm -rf /system/media/audio/notifications # removes notifications
# this removed all my ringtones and folders
After that I just used "adb push c:\ringtones /system/media/audio/ringtones"
That simply took whatever .ogg / .mp3 ringtones and put them back on the system memory of my G1.
Using JF 1.5, didn't need to go into recovery or anything.
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
if you wish to save your userinit.sh
Code:
mount /system/
mount /data/
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
rm- rf /data/*
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
This is awesome thanx. It will be useful.
Question:
I understand wiping the apps of the ext but why would you want to wipe the data when you can just do an alt+w? Wouldn't an alt+w also wipe the data?
Mine shows /system/sd/ empty, but when I boot up into the OS all the apps are still there.
Thanks Denkai, one thing missing...
First
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
I usually would do mount /system/sd/ then rm -rf /system/sd/*
Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.
this should be included in the cyanogen+JF recovery, so we can just do it there before installing new roms.
devsk said:
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.
Click to expand...
Click to collapse
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.
Denkai said:
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.
Click to expand...
Click to collapse
Mount command is not recursive. Somebody cribbed about their '/system/sd' being empty, it was because of this.
no it wasn't. I've tested it. the apps folder is there with all the .apks. test it out yourself. they probably didn't know what they were doing.
it says device or resource busy.. :S
what to do?
UPDATE: this works..
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
but honestly i dont know the difference between all these commands...
When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`
so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.
elingreen said:
so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.
Click to expand...
Click to collapse
Your FAT32 should not be touched using this.
dumfuq said:
When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`
Click to expand...
Click to collapse
awesome, tried it and works... i have 4 apps installed.. so nuking is my best option!!!
thanks man!
Denkai said:
however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
I believe this 'could' work
the files are in RAM, so not all needed. Possibly deleting them all and then an immediate reboot would work
or delete and then r/o really fast.
I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
check with chuckhriczko, he successfully completed what you are trying to do. Also check out his ROM...it already has this action implemented into the ROM
techie4971 said:
I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
Click to expand...
Click to collapse
I am assuming you are in the system when doing this? If so, you need to back out into recovery and do it. We currently don't have write access to the system partition while Android is running. Only in recovery. Highly recommend you look up Rom Manager on the market and use that to install the "fake-flash" recovery. It's truly the best recovery we have atm.
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Click to expand...
Click to collapse
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
joeykrim said:
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
Click to expand...
Click to collapse
Oh I didn't know about the symlink. Good call.
Good point. I forgot to mention I did change the build number in the build.prop to be .6 instead of .1 so maybe that helps.
chuckhriczko,
I first tried it in system and no luck, then I went to recovery. I figured the active system partition was the issue.
Now I know I was in the wrong place. I will get Rom Manager and take a look at your customized ROM.
Nice job on the ROM. Love to say goodbye to those Sprint Apps.
Thanks for the quick response.
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
Click to expand...
Click to collapse
Will this work on the Incredible as well?
SteelH said:
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
Click to expand...
Click to collapse
So to reverse this could I use cmd
mv otacerts.zip.bak otacerts.zip
??
Thanks.
How about:
adb shell
su
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
This should disable the OTA updates without removing any files from system.
I did not write these scripts. I claim zero credit for them. I pulled them from somewhere (another ROM or a mod for another phone, I can't remember.) I am simply passing on the information.
Here is a way you can add two scripts to change your /system from read-only to read-write and visa-versa. I am not going to hold your hand through this one. If you don't understand it, then don't do it. This is only for those that want a command line script to set their system filesystem to RW and back to RO in a simple way. This is only for people that are comfortable with the command prompt and adb shell to begin with. I am not responsible if you brick your phone.
I'll say it again. I am not responsible if you brick your phone.
Save a text file called: ro that contains:
Code:
#!/system/bin/sh
fs=`mount | grep system | awk '{print $5}'`
mount -t $fs -o remount,ro /dev/block/stl9 /system
Save a text file called: rw that contains:
Code:
#!/system/bin/sh
fs=`mount | grep system | awk '{print $5}'`
mount -t $fs -o remount,rw /dev/block/stl9 /system
Then open a command prompt and change directory to where you have the ro and rw files located. Notice that the ro and rw files DO NOT have any file extension on them. These should NOT show up as text files with Notepad icons when using Windows Explorer. If they do, then you need to take the .txt off the end of the filename. If you can't see it, then you have to be sure to show the hidden extensions.
The following steps assumes that you either have adb.exe and related files in the same directory as your rw and ro scripts OR you have added adb.exe to the PATH environment variable on your computer system.
When you are ready do this:
Code:
adb push rw /data/local/tmp/rw
adb push ro /data/local/tmp/ro
adb shell chmod 0755 /data/local/tmp/rw
adb shell
/data/local/tmp/rw
cp /data/local/tmp/rw /system/xbin/rw
cp /data/local/tmp/ro /system/xbin/ro
chmod 0755 /system/xbin/ro
chmod 0755 /system/xbin/rw
/system/xbin/ro
reboot
Notice that the last command will reboot your phone. This is only necessary if you want these scripts to be usable immediately. When you have rebooted, you should be able to type the command: rw to set your /system to read-write and ro to set your /system to read-only
Personally, I skip that last "reboot" command and I just run /system/xbin/ro manually until the next time I reboot my phone anyway.
These two scripts should be compatible with what ever file system you have on /system since if you read the script it actually checks the file system type first and then uses that response in the next line.
Use at your own risk, though.
EDIT: On Gingerbread, I had to use /dev/block/stl10 instead of /dev/block/stl9 above.
i want to use INT2EXT in cm9 i followed this tutorial
xpmode said:
INT2EXT+ INSTALLATION TUTORIAL
IF YOU ALREADY HAVE S2E, LINK2SD OR SIMILAR, YOU MUST REPARTITION SD CARD AND FACTORY WIPE
int2ext+ is a relatively new script that instead of making symbolic links(Link2SD) or moving certain partitions(S2E) to sd, extends your internal storage into your ext partition in sd, which means S2E's potential space saving and Link2SD's stability combined together and gives you something to brag about.
PREPARATIONS
Download the latest build of CyanogenMod 9.
Download the latest version of CronMod INT2EXT+ here.
Open CyanogenMod 9 zip.
Navigate to /system/etc/init.d
Open INT2EXT+ zip.
Navigate to /system/etc/init.d
Add the file called 40int2ext in the /system/etc/init.d directory in CM9 zip.
INSTALLATION
Go to recovery, do factory reset and advanced > partition sd card.
Select 1024M for ext(for some reason, I selected 4096 and it only read the first 1GB-ish) and 0M for swap.
Wait until it says Done and goes to menu.
Go to Mounts and Storage.
Select USB storage and connect your phone to your computer.
Copy your modified CM9 zip file to the root of your sd.
Select unmount.
Reflash ROM.
Reboot.
After reboot, go to settings > developer settings > root access and select Apps and ADB.
Go to your adb directory and do adb shell.
Type su.
Then do:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Reboot.
After reboot, reboot into recovery and flash gapps.zip normally.
Then go to Applications and enjoy your new, extended internal storage.
Click to expand...
Click to collapse
can someone help me how to do adb shell and go to adb directory
Use the directory that you used to root your device.
Hpsgill said:
can someone help me how to do adb shell and go to adb directory
Click to expand...
Click to collapse
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Thanks
No worries =)
Chaosgod27 said:
No worries =)
Click to expand...
Click to collapse
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Hmm, if you want. Right now I'm a bit busy with work...
Chaosgod27 said:
Hmm, if you want. Right now I'm a bit busy with work...
Click to expand...
Click to collapse
Anytime ,when u r free or pm me
Sent from my HTC Explorer A310 using xda premium
What did you want to know about them? You want to know how to install them or?
Chaosgod27 said:
What did you want to know about them? You want to know how to install them or?
Click to expand...
Click to collapse
Every thing about there scripts I never partation my memory card
Sent from my HTC Explorer A310 using xda premium
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Hmmm, you don't need adb for this. Just use terminal emulator on your phone. It comes installed by default on CM9 roms. Or you can search play store for android terminal emulator. The app is by Jack Palevich
Code:
su
mount -rwo remount /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -ro remount /system
Then again, I don't really see why it is necessary to deny execute permissions to these scripts in first place. They are just empty shells - unless they have been modified.
I'm using int2ext4 right now and never really had to...
EDIT: If you want to reverse these changes then
Code:
su
mount -rwo remount /system
chmod -R 755 /system/etc/init.d
mount -ro remount /system
Hpsgill said:
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Click to expand...
Click to collapse
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
sabaatworld said:
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
Click to expand...
Click to collapse
thanks maaaaaan!!!
where is the adb directory?? do we have to install it in our pc or its there in our explorer?
Sent from my HTC Explorer A310e using xda premium
everything i did went well and i checked the internal memory its shows 850mb ... now the problem is when i type adb shell in terminal its say error:device not found ... so what should i do ???