Hey Guys I Have Rooted My X10 Mini Kindly Let Me Know How To Install Applications on SDCARD
Sent from my E10i using XDA App
follow app2sd procedure.its given in this forum.
Thanks Bro
Sent from my E10i using XDA App
X10 Mini rooten.
ADB muß da sein.
busybox und dieses script auf /sdcard kopieren und script ausführen.
#!/system/bin/sh
cd /sdcard
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
if !(type busybox) then
mkdir /system/xbin
cat /sdcard/busybox > /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin/
fi
mv /data/app /data/app0
mkdir /data/app
chmod 4777 /data/app
mount -t ext2 /dev/block//vold/179:2 /data/app
cp -a /data/app0/* /data/app/
rm /data/app0/*
umount /data/app
ln -s /data/app0 /data/app
rm /system/bin/mkdir
echo "#!/system/bin/sh" >/system/bin/mkdir
echo "if !(grep /data/app /proc/mounts >/dev/null) then mount -t ext2 /dev/block//vold/179:2 /data/app;fi" >>/system/bin/mkdir
echo "busybox mkdir \"\[email protected]\"" >>/system/bin/mkdir
chmod 4755 /system/bin/mkdir
reboot
Related
Hi, I want to freeing up some space in my /data partition so I can install more apps...
I manage to get 60mb more space by doing this: forum.xda-developers.com/showthread.php?p=7459981
Then I also thought to move /data/dalvik-cache since it's very big... In other forum, people move /data/dalvik-cache to SD card or /cache...
Moving dalvik-cache to SD card is a little unstable while /cache partition in X10 mini only have 50mb free space... (my data/dalvik-cache had 65mb size)
Besides that, /cache is used by FOTA, browser and market apps to download a files...
Then I look another partition, and I see that /dev partition has 86mb free space! If I do this, I can install 65mb more application to my phone...
Then after searching, I found this script. It must be executed at boot:
Code:
#!/system/bin/sh
echo "++++ DALVIK 2 DEV STARTING ++++"
if [ ! -d /dev/dalvik-cache ]
then
mkdir /dev/dalvik-cache
chown 1000:1000 /dev/dalvik-cache
chmod 775 /dev/dalvik-cache
fi
if [ -L /data/dalvik-cache ]
then
rm -f /data/dalvik-cache
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ ! -d /data/dalvik-cache ]
then
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ -d /data/dalvik-cache ]
then
for filename in /data/dalvik-cache/*
do
if [ -L $filename ]
then
rm -f $filename
fi
done
mv /data/dalvik-cache/* /dev/dalvik-cache/
fi
mount -o bind /dev/dalvik-cache/ /data/dalvik-cache/
The question is, how to execute this script during boot up? Another peoples do it this way in their phones:
Hacre said:
paste the text into a file called 02dalvik2cache (no file extension)
adb remount
adb push 02dalvik2cache /system/etc/init.d/
adb shell chown root:2000 /system/etc/init.d/02dalvik2cache
adb shell chmod 755 /system/etc/init.d/02dalvik2cache
Reboot phone.
Click to expand...
Click to collapse
But it seems that the file structure is different. Also, adb remount command gives "not permitted" errors because ro.secure is 1 in /default.prop
If I change ro.secure=1 to re.secure=0 in /default.prop then reboots, it comes back to ro.secure=1
Any thoughts?
Hello guys, im working to boot any CM9 Rom in stock kernel with Bootloader Locked
The Fix, requires a number of changes in the Ramdizk, this Ramdizk is obtained through the kernel, the ramdizk is that the system starts.
This file consists of the following
Ramdizk .... obtained from the kernel
chargemon .... modified to start the ramdizk
charger ... for charging the phone
sh .... responsible for early in the phone
Chargemon
Code:
#!/system/xbin/sh
# Chargemon script for Xperia NEO by Xperiafan
# Boot to CWM
cat /dev/input/event2 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -e /cache/recovery/boot ]
then
rm /cache/recovery/boot
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount eMMCs
umount -l /dev/block/mmcblock0p10
umount -l /dev/block/mmcblock0p11
umount -l /dev/block/mmcblock0p12
# Mount recovery
cd /
rm -r /sbin /sdcard
rm -f etc init* uevent* default*
if [ -f /system/bin/recovery.tar ]
then
tar -xf /system/bin/recovery.tar
fi
# Umount /system
umount -l /dev/block/mmcblk0p10
# chroot
chroot / /init
fi
# Ramdizk
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount eMMCs
umount -l /dev/block/mmcblock0p10
umount -l /dev/block/mmcblock0p11
umount -l /dev/block/mmcblock0p12
# Mount ramdisk
cd /
rm -r /sbin /sdcard
rm -f etc init* uevent* default*
tar -xf /system/bin/ramdisk.tar
# Fix permissions
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /mnt/sdcard
umount -l /sdcard
rm -r /mnt/sdcard
mkdir /tmp
# chroot
chroot / /init
To use these files, you need to put them in the following path
Ramdizk system/bin
Chargemon system/bin
Charger system/bin
sh system/xbin
I have not got this phone, please appreciate your comments, you need to put these files on those routes the rom, and erase the file boot.img
Downloads
Ramdizk Beta Here
Chargemon Done Here
Charger Done Here
SH Done Here
We need custom wifi modules, right?
Sent from my MT15i using xda app-developers app
Its nice that we'll be having CyanogenMod for locked bootloaders.
Keep up the good work dev!
Anyone having locked bl
Tried his efforts?
Sent from my MT11i using xda premium
I tried it, but i doesnt boot, just stuck at sony logo... I will try to manually extract the ramdisk from the latest get.cm and it seems we will have aosp roms on locked bootloader
Sent from my MT15i using xda app-developers app
I will try to make a build what at least boots succesfully
Sent from my MT15i using xda app-developers app
it would be nice if anyone try to make this work i realised that we have mtdblocks not mmcblocks ... lets see if i can get it to work
Im work in this.... But first im make a new ramdizk for xperia u and later for neo and others
Sent from my ST25i using xda app-developers app
I have just cooked my rom( update.zip) and successful installation. But when I restart my mobile, I can't find my settings in bootanimation.zip, Build.prop...
I open Root Explorer and find folder ADB. This Folder has: adb.sh, bootanimation.zip, Build.prop… I can delete this folder but when I restart my mobile, I see it again.
I open file: adb.sh. It has content:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p6 /system
mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /data
mkdir /data/app
cat /adb/gotiengviet3.apk>/data/app/gotiengviet3.apk
chmod 0644 /data/app/gotiengviet3.apk
mkdir /system
cat /adb/build.prop>/system/build.prop
chmod 0644 /system/build.prop
mkdir /system/media
cat /adb/bootanimation.zip>/system/media/bootanimation.zip
chmod 0644 /system/media/bootanimation.zip
mkdir /system/etc/permissions
cat /adb/com.google.android.features.vendor.xml>/system/etc/permissions/com.google.android.features.vendor.xml
chmod 0644 /system/etc/permissions/com.google.android.features.vendor.xml
rm /adb/gotiengviet3.apk
rm /adb/build.prop
rm /adb/bootanimation.zip
rm /adb/com.google.android.features.vendor.xml
how to cook room or delete folder ADB?
Hi, have problem with restore script. This script is for init.d. First boot with restore app and app data. Have problem with restore app data. If run script for restore app data then restore only from one tar.gz file, no from all. Where problem? Thanks
App restore:
#!/system/bin/sh
su
mount -o remount,rw /system
mount -o remount,rw /data
for filename in /system/app2/*.apk;
do
busybox install $filename /data/app;
done
busybox rm -rf /system/app2
busybox rm -rf /system/etc/init.d/90app
App data restore:
#!/sbin/busybox sh
sleep 45
su
mount -o remount,rw /system
mount -o remount,rw /data
for filenamezip in /system/appdata/*.zip;
do
busybox chown -R root /data/data/${filenamezip%.zip}/*
busybox chmod -R 777 /data/data/${filenamezip%.zip}/*
busybox rm -rf /data/data/${filenamezip%.zip}
done
for izip in /system/appdata/*.zip;
do
busybox unzip -o $izip -d /;
done
for filenametar in /system/appdata/*.tar.gz;
do
busybox chown -R root /data/data/${filenametar%.tar.gz}/*
busybox chmod -R 777 /data/data/${filenametar%.tar.gz}/*
sleep 1
busybox rm -rf /data/data/${filenametar%.tar.gz}
done
for itar in /system/appdata/*.tar.gz;
do
busybox tar -xzf $itar -C /;
done
sleep 5
busybox rm -rf /system/appdata
busybox rm -rf /system/etc/init.d/95appdata
reboot
For manual backup:
su
mount -o remount,rw /system
mount -o remount,rw /data
BACKUPDIR=/system/appdata
DATADIR=/data/data
echo
# create BACKUPDIR if necessary and modify ownership/permissions
if [ -d $BACKUPDIR ]; then
rm -rf $BACKUPDIR
mkdir $BACKUPDIR
else
mkdir $BACKUPDIR
fi
chown root $BACKUPDIR
chmod 777 $BACKUPDIR
# make
for name in $DATADIR/*; do
tar -cpvzf $BACKUPDIR/${name#/data/data/}.tar.gz $name
done;
# modify ownership/permissions of all archives
chown root $BACKUPDIR/*
chmod 777 $BACKUPDIR/*
echo
Sorry my bad english
Any solution please?
Hi. Please help my with this problem.
HI,
I can't delete "/system/etc/install-recovery.sh" on my rooted device.
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # cd /system/etc
cd /system/etc
[email protected]:/system/etc # rm install-recovery.sh
rm install-recovery.sh
rm failed for install-recovery.sh, Operation not permitted
255|[email protected]:/system/etc # chown shell install-recovery.sh
chown shell install-recovery.sh
Unable to chown install-recovery.sh: Operation not permitted
10|[email protected]:/system/etc #
Anyone knows why ?
(My device is Redmi 1 by the way)
Thanks.
Slash