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.
Related
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
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.
Hey guys, just got my hands on one of these suckers, it runs 2.1
Can anyone point me in the right direction to get root?
Im also looking for froyo, however dont expect it soon, manufacturer is working on it.
Sent from my S7 using XDA App
I second davidcampbell! We need froyo here
The root method is the same as the s7.
download z4root from market and root, after wards install busybox by titanium backup and you are set.
The app2sd mod works for this device since it is similar to the sony x10 on 2.1 but is risky because i lost wifi aftewards. So just explore until we get some real developers working on it hopefully cm6.1 port but after huawei realeases the recovery.img and source to mess around with though.
being able to overclock to 1ghz wouldnt hurt either.
S7 Bootloader?
Has anyone figured out how to get into the bootloader for this device?
Havent been able to through any apps \ commands. Just go to a black screen and thats it, and recovery sends you into factory settings for your device
I only know that pressing back key and call\send key when when powering on the device puts it into update mode.
alexisprz said:
The root method is the same as the s7.
download z4root from market and root, after wards install busybox by titanium backup and you are set.
The app2sd mod works for this device since it is similar to the sony x10 on 2.1 but is risky because i lost wifi aftewards. So just explore until we get some real developers working on it hopefully cm6.1 port but after huawei realeases the recovery.img and source to mess around with though.
being able to overclock to 1ghz wouldnt hurt either.
Click to expand...
Click to collapse
Zomg, nice, thank you alexisprz, it's rooting time
I really wish Android had a better term for rooting, it sounds like I'm either breaking it, or trying to cram my man bits into it some how.
Will this affect my ability to use the manufacturers update to froyo in the future?
UPDATE: z4root worked great, I installed busybox no problemo, very happy forum member here
sir i just bought one telstra touch tab can you plz help me to debrand it and unlock it i also have jtag too
pre needs, new rom and rooted with busybox on SD with linux ext2/3 Partition.
download z4root from market and root
copy 3 files to sd
run App-2-sd.sh
File 1 "App-2-sd.sh"
#!/bin/sh
# untitled.sh
#
#
# Created by Andew Blazely on 5/02/11.
# Copyright 2011 SOFTHOUSE. All rights reserved.
#
# un Hash data if you wish but it will slow the S7 down and cause lots of waiting problems
# pre needs, new rom and rooted with busybox on SD with linux ext2/3 Partition.
# mount the file systems
mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
busybox mkdir /system/sd
mount -t ext2 /dev/block/vold/179:2 /system/sd
# archive dirs (easier than copying)
cd /data/
busybox tar -cvf /system/sd/app.tar app
busybox tar -cvf /system/sd/app-private.tar app-private
# busybox tar -cvf /system/sd/data.tar data
busybox tar -cvf /system/sd/dalvik-cache.tar dalvik-cache
# unpack arcives in correct place
cd /system/sd
busybox tar -xvf app.tar
busybox tar -xvf app-private.tar
# busybox tar -xvf data.tar
busybox tar -xvf dalvik-cache.tar
# cleanup
busybox rm *.tar
# copy and set system files
busybox cp /sdcard/install-recovery.sh /system/etc
busybox cp /sdcard/init-sd.sh /system/etc
busybox chmod 755 /system/etc/install-recovery.sh
busybox chmod 755 /system/etc/init-sd.sh
# un Hash whatis needed if you intend NOT to remove SD
#cd /data/app
#busybox rm -rf *
#cd /data/app-private
#busybox rm -rf *
#cd /data/data/
#busybox rm -rf *
#cd /data/dalvik-cache
#busybox rm -rf *
# binding mount of new file structure
mount -o bind /system/sd/app /data/app
mount -o bind /system/sd/app-private /data/app-private
# mount -o bind /system/sd/data /data/data
mount -o bind /system/sd/dalvik-cache /data/dalvik-cache
reboot
File 2 "init-sd.sh"
#!/system/bin/sh
#
MYLOG=/sdcard/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
sleep 10
# un Hash whatis needed if you intend NOT to remove SD
#echo "$(date) Erasing system files..." >> $MYLOG
#cd /data/app
#busybox rm -rf *
#cd /data/app-private
#busybox rm -rf *
#cd /data/data/
#busybox rm -rf *
#cd /data/dalvik-cache
#busybox rm -rf *
#echo "$(date) Erased system files..." >> $MYLOG
mount -t ext2 /dev/block/vold/179:2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app-private /data/app-private 1>>$MYLOG 2>>$MYLOG
# Hash this out if you haven't moved /data/data
#mount -o bind /system/sd/data /data/data 1>>$MYLOG 2>>$MYLOG
# Hash this out if you haven't move /data/dalvik-cache
mount -o bind /system/sd/dalvik-cache /data/dalvik-cache 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG
echo "$(date) Finishing install-recovery.sh" >> $MYLOG
File 3 "install-recovery.sh"
#!/system/bin/sh
#
/system/etc/init-sd.sh&
And BOB's your uncle.. this has worked many times for me give it a try
I managed to break my micro sd card in half today and I wasn't able to pickup a class 10 or 6 replacement locally so I thought I could use some of the 6gb of internal memory as a virtual filesystem to get me out of trouble.
So, after quickly looking at the android docs and the supported busybox commands I created a 2gb sdcard.img in /data and mounted to /sdcard. I copied some files to it with astro filemanager and fired up raging thunder 2 and it went ahead and downloaded the game data to /sdcard/ and worked correctly.
But, a few apps won't recognise it as an sdcard (Motorola SD card and phone storage settings applet) as well as things like PlayPro (states I have no sdcard present). I thought perhaps I could modify the /etc/vold.fstab file to auto mount the sdcard.img I created using vi but I'm a bit clueless as to what I should change on the dev_mount /sdcard line to get it automounted at boot and hopefully fool the rest of the apps into thinking it is a physical sdcard.
Can anyone possibly point me in the right direction? Not sure how to invoke cmd mode in vi using the milestone qwerty either but I'll keep digging.
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
+ 1 for this, it would be great to can use internal storage for user data
Why do you let this nice post die.. so "flibbulator" found anything more out?.. I'd like to know more.. like if you got it to work with Music Players and Video players??
Try to mount /data/sdcard.img to /mnt/sdcard (/sdcard is a link to /mnt/sdcard)
or try "export EXTERNAL_STORAGE /sdcard"
I made in a different way: created a 4GB storage.img in /data and mounted it in /sdcard/storage, so internal storage is finally usable for user data
the problem was to set mount point on boot, I can't find a way to execute a script on boot (you can't permanently modify init.rc)
flibbulator said:
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
Click to expand...
Click to collapse
I have actually tried this on my Droid2Global, and I get the error "unknown operand if/dev/zero" I feel like I am missing the point or do not fully understanding how to use the "dd" command?
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
patton82 said:
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
Click to expand...
Click to collapse
Thank you bro.
Quick question I keep getting these errors. I do have a folder in "/" named "sdcard-int"
Better Terminal Emulator Pro
/ # busybox mount -o loop /data/sdcard.img /sdcard-int/
mount: can't setup loop device: No such file or directory
/ # busybox mount -o /data/sdcard.img /sdcard-int
mount: can't read /etc/fstab: No such file or directory
/ #
Sent from my DROID2 GLOBAL using Tapatalk
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Will be lost anything after reboot when use this storage?
Sent from my MotoA953 using XDA App
all the stuff in img file will not be lost, as long as you put it in /data/
on the contrary the mount point must be restored after reboot
patton82 said:
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Click to expand...
Click to collapse
Thank you, I will use the Thank you button when I login via PC.
I still get the same error, I know that I'm doing something incorrectly or maybe I don't understand "mount" comment correctly?
/ $ su
/ # mkdir /sdcard/storage
/ # dd if=/dev/zero of=/data/storage.img bs=1024 count=41943404194340+0 recordsn
4194340+0 records out
4295004160 bytes (4.0GB) copied, 339.823883 seconds, 12.1MB/s
/ # busybox mkfs.vfat /data/storage.img
/ # mount -o loop -t vfat /data/storage.img /sdcard/storage
mount: can't setup loop device: No such file or directory
/ #
I am using my sdcard also, I'm not too sure if that makes any difference?
Sent from my DROID2 GLOBAL using Tapatalk
Better terminal pro uses BASH shell, I presume
try to switch to android shell, in preferences
or to use terminal emulator (free) from market
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Sent from my DROID2 GLOBAL using Tapatalk
resource busy, you have to reboot the phone
I use Gscript lite, add a script with the string
mount -o loop -t vfat /data/storage.img /sdcard/storage
and create a shortcut to homescreen, so when I reboot, I can mount the img file in one click
Cool mod for my ROM. Could I take it??
sure, they are simple shell commands
the best would be to do what happen with Samsung Galaxy S: internal storage mounted as sdcard and physical sdcard mounted in a folder /sdcard/sd
storage.img is 3-4 times faster than my peak 8GB class 6
There is an application "Autostart" in the market, which can automatially execute a script with root after boot up.
I up because I'm now also interested in making profit of the huge internal storage. I'd like to put my wikipedia data from wikidroyd to the internal storage. Hopefully I'm skilled enough to follow the given steps...I doubt that though
fKngFtd said:
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Click to expand...
Click to collapse
Guys, I need your help! I have exactly. The same problem:
Every time I try to mount my storage.img I get
Ioctl LOOP_SET_FD failed: Device or resource busy.
I rebooted several times and also tried to mount smaller images (first I tried 3gb then I tried 1mb).
Any solution?
Edit: I solved it myself. I always forgot to punch in busybox before the command. Now it worked for me!!
I do have a question now. With help of Gscript I made a shortcut to mount the storage.img to my sdcard. But my pc wont recognise the sdcard as long as the image is mounted. What is the command to unmount the partition so I wouldnt have to reboot my phone before connecting it to the pc...?
Any help is much appreciated! Thx
(Something like busybox unmount -o loop -t vfat...?)
Sent from my MotoA953 using XDA App
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 ???