So last night I installed the newest JAC Hero build and it was forcing close on google maps and a few others. In the thread it said to format your ext2 partition so I used paragon and I thought I formated it but now It wont get past the HTC screen. I can go to recovery and fastboot but when i try to push any new update it just updates to the hero rom again. Also if I use ls to list the files it shows nothing in /sdcard but obviously it has stuff since it still will flash the hero rom fine. How can I make a new update override this one when I push it to the phone? I dont have a card reader so I have to use my phone.
You must have your FAT32 partition first, the big one,where you put your update.zip and then a ext2 or ext3 partition of ≈500mb.
have you respect this order ?
Yes, I have a 1gb card and my 600mb fat32 is first then a 400mb ext2.
When you are in adb your ext2 partition is /system/sd
More than likely you need to do this part from my post here: http://forum.xda-developers.com/showthread.php?t=517874
Delete existing apps on SD
Code:
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/app-private
imfloflo said:
≈500mb.
Click to expand...
Click to collapse
You have 500mb of bacon?!?!
When I try those commands it says no such directory or file for both.
EDIT: I just got it fixed with these commands from brandenk's thread:
adb shell mount /sdcard
adb shell rm /sdcard/update.zip
adb push *filename* /sdcard/update.zip
Charbo said:
When I try those commands it says no such directory or file for both.
Click to expand...
Click to collapse
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
phantasm714 said:
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
Ok, so I thought it was fixed but it was stuck at the android screen. Im guessing because of my apps still on the card? When I tried your command it said no such file or directory also so I did mkdir /system/sd and tried again and it said invalid argument.
I got it into android now with the sd card out when i turned it on. So now is there any way i can completly wipe the sd card of all partitions from in windows so I can start over?
EDIT: Got it formatted from the sd card settings on the phone lol... now I can start over thanks for all your help.
I'm hoping someone could help me with loading JAC's 2.2 Hero rom
I've never had any problems updating, but I had never tried a hero rom before
When trying to update i get this error
"Copying files...
E:Can't chown/mod /system/xbin
(No such file or directory)
E:Failure at line 12:
set_perm_recursive 0 2000 0755 0
6755 SYSTEM:xbin
Installation aborted"
Anyone know whats causing this?
There's a handful of people also experiencing this issue
Am running the Phiremod/HC dual boot on sd, and want to flash the 1.1Ghz OC kernel.
Can someone point me to the right kernel download, and a guide on how to flash it to SD card?
From reading I assume there are versions for emmc and different ones for SD roms, but I'm a little worried I'll pick the wrong one and ruin everything.
Yeah, wot he said ^ 'cept for a CM7 kernel.
Don't know about phiremod, but the cm7 and stock kernels can be found in Dalingrin's OC kernel. The files are named with sdcard or emmc to avoid confusion.
As far as flashing it, get a bootable sd card and put the OC zip in the root of the card (don't unzip it).
Boot the card and install the zip using CWM (something like "install zip from sd card"). For CWM, the N button is select, the power is back, and the volume buttons are up/down.
First apologies if I'm hijacking the OP's thread. But where I come unstuck is getting into CW Recovery.
Assume I need an OC kernel on the uSD card; I can't seem to find a way to get into CWR. I've tried RomManager -> CWR, but that just reboots the Nook. When I remove the uSD card and reboot THEN the machine boots into recovery, but for the eMMC system. But I dont want that!
So the big question is how can I run the system from the SD card AND get into CW Recovery for that system and NOT the embedded one?
'Confused of Tunbridge Wells'
doncaruana said:
Don't know about phiremod, but the cm7 and stock kernels can be found
Click to expand...
Click to collapse
Thanks for the helpful links!
I've managed to flash one of Dalingrin's older OC kernels successfully, but when I try the latest one, the nook doesn't boot into phiremod.
The screen flashes, and then nothing happens.
I was going to try and flash via ADB, following the instructions in Dalingrin's thread, but the instructions for flashing to EMMC and SD look exactly the same to me (shouldn't the sd version NOT go into emmc?), and I'm not sure what location to place the unzipped files:
If not using CWM, unzip the contents of the update and push uImage onto /boot partition. Then you will need to copy the system folder.
if flashing to sdcard:
adb shell mount -t vfat /dev/block/mmcblk1p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
if flashing internal eMMC
adb shell mount -t vfat /dev/block/mmcblk0p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
Reboot Nook!
siskiou said:
Thanks for the helpful links!
I've managed to flash one of Dalingrin's older OC kernels successfully, but when I try the latest one, the nook doesn't boot into phiremod.
The screen flashes, and then nothing happens.
Click to expand...
Click to collapse
To use one of the later kernels you need to update your uboot to either the one that comes with the most recent nightly's or the stoc bn 1.2 uboot.
obsidianblackhawk said:
To use one of the later kernels you need to update your uboot to either the one that comes with the most recent nightly's or the stoc bn 1.2 uboot.
Click to expand...
Click to collapse
I would, but am too new at this, and need instructions.
siskiou said:
Thanks for the helpful links!
I've managed to flash one of Dalingrin's older OC kernels successfully, but when I try the latest one, the nook doesn't boot into phiremod.
The screen flashes, and then nothing happens.
I was going to try and flash via ADB, following the instructions in Dalingrin's thread, but the instructions for flashing to EMMC and SD look exactly the same to me (shouldn't the sd version NOT go into emmc?), and I'm not sure what location to place the unzipped files:
If not using CWM, unzip the contents of the update and push uImage onto /boot partition. Then you will need to copy the system folder.
if flashing to sdcard:
adb shell mount -t vfat /dev/block/mmcblk1p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
if flashing internal eMMC
adb shell mount -t vfat /dev/block/mmcblk0p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
Reboot Nook!
Click to expand...
Click to collapse
THIS IS WHERE I AM STUCK.
I'm a NOOB, running CM7 from SD CARD.
I can't figure out how to install the kernel to my NK.
I copy the unzipped file into my SD card and using size agnostic installer trying to boot into recovery mode to run install.
For some reason, I cannot get into recovery mode. I'm trying the suggested power button and N button combinations, tried selecting reboot into recovery mode from CM7 desktop and selecting reboot into recovery mode from ROM manager that came with install, with no luck.
AM I DOING SOMETHING WRONG??
Also, what does this mean??
siskiou said:
if flashing to sdcard:
adb shell mount -t vfat /dev/block/mmcblk1p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
Click to expand...
Click to collapse
Is this a command line to use in terminal emulator????
HELP HELP!!!
no need for me to worry about this, actually change to nightly build 102 and the Size agnostic installer did its magic to install kernel with no issues.
Hi all, originally intending to post this tutorial to Ideos S7 Android Development but got a nice greeting from xda-developers.com unallowing newbies to post there
So I just got a brand-new-in-a-box, dead cheap, Ideos S7 tablet -- my first android tablet, and my second android device. I brought my last device about 2 years ago, a G1 that I only kept for a week and sold it afterwards. I was thinking that at that time Android isn't ready yet for replacing my E71.
Back to the Ideos S7, mine is already preloaded with TRZ-mod-0.2 ROM, which is nice. However, I had some issue with wireless network. Whenever I disable my wifi, I would ge trouble activating it as it constantly disabled by itself. Thus, I decided to go back to available stock ROM. Long story short, I've chosen the Froyo 2.2.2 Sweden coded S7V100R001C63B110, and made myself comfortable with repeating Huawei's flashing process.
The firmware seems more stable, and does not have the wireless network activation/deactivation issue. Stock ROM lover anyone
However, the stock ROM doesn't have apps2d+ or whatever that was called, to extend the internal storage. 137MB of free space is really pity for such device. I couldn't run Data2Ext* script successfully, as the default shell /system/bin/sh doesn't seems to support square brackets on scripts conditional parts. Busybox 1.18 supports it, but somehow it would cause all the commands executed in the script to ran by Busybox, causing "applet not found" errors. The other option would be Link2SD, which could probably saved me 10+ hours of hacking. It had its drawback though, the current version on the market expects the extended internal tablet storage partition to reside on the external SD card. Some hacking to mount the internal SD partition works, but not sure whether it would got correctly mounted on boot.
Also, the most important thing: nothing feels better than looking at "Available space" on "Internal tablet storage" of 5.5GB
So here it is, the tutorial for extending the internal storage. Most of the information used are gathered from various sources, and rewritten here for your enjoyment!
REQUIREMENTS:
=========
a) All hardware: Ideos S7 -- should work on Slim as well, data cable, charger, a living being..
b) Rooting -- I've used Gingerbreak from the market
c) Terminal Emulator -- Android Terminal Emulator works fine. Irritating blue background though.
d) Busybox -- 1.18 version is working fine
e) Root explorer -- Optionally used, for easier file editing and copying.
STEPS:
=========
0) Backup your data, as all data in internal storage will be lost!
---------
Well honestly I didn't do this as I got my contacts and mail synced on the internet. My S7 only got 5 days of lifetime so not much data there yet. Sorry no guide on how to do this
1) Partition the internal SD (or external SD card if you intend to do so).
---------
It is recommended to use a good class of memory card when using external SD card for the tablet storage partition.
There's possibly partitioning tools available for the architecture, but I did it with EASUS Partition Master on a Windows system. Mac OS's Disk Utiliy should work as well. Don't worry too much about the partition type, we'll reformat it later with busybox later anyway.
To partition the internal (or external) SD card, connect your data cable to your phone. When the USB connection notification came up, activate the USB storage mode. You don't need to install the Huawei S7 (or adb) drivers.
Fire up your partitioning application, and identify your storage. Delete (or) resize the existing FAT partition. Create another primary partition afterwards, with ext2 filesystem. ext3 and ext4 isn't supported in the stock ROM, so you probably have to either install a kernel module for the ext3,4 or replace your boot.img. Hey but that's not going to be a stock ROM
2) Root the device
---------
Install Gingerbreak from the market. Enable USB debugging in Settings -> Application -> Development, or else it won't work. Run Gingerbreak, root your device! The device will restart after successful process, and you are ready to modify your root filesystem.
3) Prepare the required tools
---------
You'll optionally need busybox to format and edit the files. Copy over the busybox binary file to /system/xbin/. The terminal login path would automatically points there so you can run busybox from anywhere inside the terminal.
4) Prepare the new data directory
---------
Fire up your terminal emulator. You'll need to be logged in as root to do the whole operation mentioned. Thus, type in:
Code:
su
Mount the new partition you've prepared on step (1). For internal SD, it's going to be /dev/block/mmcblk0p2 device, or for external SD, /dev/block/mmcblk1p2. You can also use other shorthand such as /dev/block/vold/179:2. But for simplicity, I'll use mmcblk*p* throughout the tutorial.
Prepare the mount point for your prepared data partition, and mount it. If it's currently mounted, unmount it first.
Code:
umount /dev/block/mmcblk0p2
mkdir /system/sd
You can also format the partition now if you didn't specify the partition type during the partition creation.
Code:
busybox mke2fs -m0 -b4096 /dev/block/mmcblk0p2
Now mount the extended data partition.
Code:
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
We'll still need to be able to access the original data partition now and later, so, prepare the mount point and mount it as well.
Code:
mkdir /system/internal
mount -t yaffs2 /dev/block/mtdblock4 /system/internal
At this stage, you'll need to copy over all files inside the original /data directory to your new sd directory. You'll also need to make sure that the permissions isn't changed during the process. To do this, just tar the entire original data directory to your new one.
Code:
cd /system/internal
busybox tar -cvf /system/sd/old-data.tar *
cd /system/sd
busybox tar -xvf old-data.tar
busybox rm old-data.tar
The initialization for the new data directory mounting in the boot process does not modifies the boot image's init.rc. Thus, it seems that the initialization process is called after the radio initialization. I can't get my GSM to work without this step. We'll need to symbolic-link back the /system/sd/radio directory to the original internal storage /data/radio directory. And remember that on the boot process, we'll need to mount /system/internal *before* /system/sd.
Code:
cd /system/sd
busybox rm -rf radio
ln -s /system/internal/radio /system/sd/radio
After fiddling for several hours, I realized that the date and time settings gets reset on each boot. Fixed by symlinking the /data/date.time back to the internal storage.
Code:
cd /system/sd
busybox rm -rf date.time
ln -s /system/internal/date.time /system/sd/date.time
5) Prepare the boot init script
---------
The Froyo boot process runs init.rc script, which is replaced by the boot.img when system boots. So we can't put our new /data directory mount commands there, unless we extract, unpack, modify, repack the boot.img. Ok so I decided that modifying boot.img will be the last step if I can't get it working without it. There must be an easier way!
Also, there aren't any rc.d, rc3.d, bla bla directory in which we can put our custom initialization script.
Luckily, there is a script that is called from the init.rc script during boot, which is stored on the root filesystem and can be customized. It's called /system/etc/install-recovery.sh. Thus, we'll put the initialization script there. If you already got a /system/etc/install-recovery.sh, you can just add our initialization script in the beginning of the. Alternatively, you can create a separate script to perform init, and call it from your modified /system/etc/install-recovery.sh.
There will be drawback, for example, it seems that the script is called after radio initialization, so we'll need to use the old /data/radio directory from the original /data directory, prepared on step (4).
So now you'll need to create (or copy) the install-recovery.sh script. You can use vi from the busybox, or easier is to just copy and paste the install-recovery.sh script provided in this post. In case you're a vi expert, fire up these commands. Don't forget to remount the root filesystem as rw first!
Code:
busybox vi /system/etc/install-recovery.sh
Write in the install-recovery.sh script:
Code:
#!/system/bin/sh
mount -t yaffs2 /dev/block/mtdblock4 /system/internal
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -o bind /system/sd /data
Don't forget to set executable and readable attribute at least for root user, or else the system can't run the script!
Code:
chmod 755 /system/etc/install-recovery.sh
So now you're ready to reboot the system. Double check the install-recovery.sh script, make sure all commands mounts the partition exactly to where you intend it.
6) Reboot your Ideos S7!
---------
Reboot and enjoy the trendemous increase on your internal tablet storage
WARNING!!! Do not attempt to perform factory data reset while running with /data mounted. It seems that S7 will format the /data partition as yaffs2, not sure as I haven't checked it. But it worth to try to change the install-recovery.sh script to mount the data partition as yaffs2, and then performing factory data reset.
Sorry I can't post either an image or attachment yet
watch_mania said:
Sorry I can't post either an image or attachment yet
Click to expand...
Click to collapse
Btw, if someone with account capable of posting images and files would like to help, I can send the image links and files to your e-mail, so you can post it here
Should've post the title with [HOWTO] prefix. Sorry about the newbie-ish thing
Hey, sure i can post them! I've set up a site for the "Install GNU/Linux" anyway. I'll be looking to follow this howto sometime in the future. Tell ya what tho, i'd have saved 10+ hours hacking had i known gingerbreak was in market also!
threader said:
Hey, sure i can post them! I've set up a site for the "Install GNU/Linux" anyway. I'll be looking to follow this howto sometime in the future. Tell ya what tho, i'd have saved 10+ hours hacking had i known gingerbreak was in market also!
Click to expand...
Click to collapse
Unfortunately I don't own the Ideos anymore
Good luck on your site!
can you make a simple tutorial to us? i need it badly.
Could you help me.... do I have to label the drives as "mmcblk..." because it's not recognizing the directory
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
I'm stuck after entering su in the emulator...please help
Nice guide
work perfectly on S7 slim
i do all the steps using sshdroid and putty so i can use cut&paste from web page
the only think that i've to add is mount syster as readwrite:
mount -o rw,remount -t yaffs2 /dev/block/XXXXXXX /system
Thanks for this guide i will do the same on all my device
i'm triing to increase internal memory on stock rom.
I successfully done on S7 slim (i found i guide writen by watch_mania) but on Vodafone Smart i've some trouble (i use sshdroid and putty).
I do the following step :
1) Partiton the external SD with two filesystem the the first one FAT32 the second one ext2
this is the output of fdisk :
/system/sd # fdisk -l /dev/block/mmcblk0 Disk /dev/block/mmcblk0: 7969 MB, 7969177600 bytes
255 heads, 63 sectors/track, 968 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 509 4088511 83 Linux
/dev/block/mmcblk0p2 510 968 3686917+ b Win95 FAT32
2) mount system as read-write and create new mount point
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
mkdir /system/sd
mkdir /system/internal
3) format ext2 partition created at 1)
mke2fs -m0 -b4096 /dev/block/mmcblk0p1
4) mounting the "original" /data on /system/internal and new ext2 partition on /system/sd
mount -t yaffs2 /dev/block/mtdblock6 /system/internal
mount -t ext2 /dev/block/mmcblk0p1 /system/sd
5) copy the content on "original" /data on /system/sd
cd /system/internal
tar -cvf /system/sd/old-data.tar *
cd /system/sd
tar -xvf old-data.tar
rm old-data.tar
6) create boot init script
vi /system/etc/install-recovery.sh
and write inside :
#!/system/bin/sh
mount -t yaffs2 /dev/block/mtdblock6 /system/internal
mount -t ext2 /dev/block/mmcblk0p1 /system/sd
mount -o bind /system/sd /data
Originally in the guide for S7 slim you have to do :
cd /system/sd
rm -rf radio
ln -s /system/internal/radio /system/sd/radio cd /system/sd
rm -rf date.time
ln -s /system/internal/date.time /system/sd/date.time
BUT if i try to do that the device does not recognize the sim.
If i try to don't do that the device loop during boot.
on S7 Slim in /system/internal/radio i found this file :
srwxrwxrwx 1 0 0 2048 Dec 31 06:49 qmux_connect_socket
the same file on vodafone smart is located in /system/internal/local/tmp/
but if i try to link it does not work and the device loop.
Will this also work on altek A14 LEO(an Android 2.1 phone)? It has less than 100MB internal storage, although it built-in dtapps2sd with the newest stock firmware, "/data/data" is still stored in internal storage. Because the version of dtapps2sd in stock firmware is not latest version, no "/data/data" mount on SD-EXT support. And I can't upgrade dtapps2sd myself due to no reflash tool for this phone.
Thank for the niec post, i,ll try it shortly
Increasing Internal Memory
Hi,
Has anyone tried a superb "setinstalllocation-xxx.apk" available in xda-developers.
I have been using it and it is really good. But as mentioned by watch-mania that 139 or 140 MB of available storage is a pity.
Your device must be rooted to use the above apk. You can successfully use gingerbreak available from this excellent forum.
more info
watch_mania said:
Hi all, originally intending to post this tutorial to Ideos S7 Android Development but got a nice greeting from xda-developers.com unallowing newbies to post there
So I just got a brand-new-in-a-box, dead cheap, Ideos S7 tablet -- my first android tablet, and my second android device. I brought my last device about 2 years ago, a G1 that I only kept for a week and sold it afterwards. I was thinking that at that time Android isn't ready yet for replacing my E71.
Back to the Ideos S7, mine is already preloaded with TRZ-mod-0.2 ROM, which is nice. However, I had some issue with wireless network. Whenever I disable my wifi, I would ge trouble activating it as it constantly disabled by itself. Thus, I decided to go back to available stock ROM. Long story short, I've chosen the Froyo 2.2.2 Sweden coded S7V100R001C63B110, and made myself comfortable with repeating Huawei's flashing process.
The firmware seems more stable, and does not have the wireless network activation/deactivation issue. Stock ROM lover anyone
However, the stock ROM doesn't have apps2d+ or whatever that was called, to extend the internal storage. 137MB of free space is really pity for such device. I couldn't run Data2Ext* script successfully, as the default shell /system/bin/sh doesn't seems to support square brackets on scripts conditional parts. Busybox 1.18 supports it, but somehow it would cause all the commands executed in the script to ran by Busybox, causing "applet not found" errors. The other option would be Link2SD, which could probably saved me 10+ hours of hacking. It had its drawback though, the current version on the market expects the extended internal tablet storage partition to reside on the external SD card. Some hacking to mount the internal SD partition works, but not sure whether it would got correctly mounted on boot.
Also, the most important thing: nothing feels better than looking at "Available space" on "Internal tablet storage" of 5.5GB
So here it is, the tutorial for extending the internal storage. Most of the information used are gathered from various sources, and rewritten here for your enjoyment!
REQUIREMENTS:
=========
a) All hardware: Ideos S7 -- should work on Slim as well, data cable, charger, a living being..
b) Rooting -- I've used Gingerbreak from the market
c) Terminal Emulator -- Android Terminal Emulator works fine. Irritating blue background though.
d) Busybox -- 1.18 version is working fine
e) Root explorer -- Optionally used, for easier file editing and copying.
STEPS:
=========
0) Backup your data, as all data in internal storage will be lost!
---------
Well honestly I didn't do this as I got my contacts and mail synced on the internet. My S7 only got 5 days of lifetime so not much data there yet. Sorry no guide on how to do this
1) Partition the internal SD (or external SD card if you intend to do so).
---------
It is recommended to use a good class of memory card when using external SD card for the tablet storage partition.
There's possibly partitioning tools available for the architecture, but I did it with EASUS Partition Master on a Windows system. Mac OS's Disk Utiliy should work as well. Don't worry too much about the partition type, we'll reformat it later with busybox later anyway.
To partition the internal (or external) SD card, connect your data cable to your phone. When the USB connection notification came up, activate the USB storage mode. You don't need to install the Huawei S7 (or adb) drivers.
Fire up your partitioning application, and identify your storage. Delete (or) resize the existing FAT partition. Create another primary partition afterwards, with ext2 filesystem. ext3 and ext4 isn't supported in the stock ROM, so you probably have to either install a kernel module for the ext3,4 or replace your boot.img. Hey but that's not going to be a stock ROM
2) Root the device
---------
Install Gingerbreak from the market. Enable USB debugging in Settings -> Application -> Development, or else it won't work. Run Gingerbreak, root your device! The device will restart after successful process, and you are ready to modify your root filesystem.
3) Prepare the required tools
---------
You'll optionally need busybox to format and edit the files. Copy over the busybox binary file to /system/xbin/. The terminal login path would automatically points there so you can run busybox from anywhere inside the terminal.
4) Prepare the new data directory
---------
Fire up your terminal emulator. You'll need to be logged in as root to do the whole operation mentioned. Thus, type in:
Code:
su
Mount the new partition you've prepared on step (1). For internal SD, it's going to be /dev/block/mmcblk0p2 device, or for external SD, /dev/block/mmcblk1p2. You can also use other shorthand such as /dev/block/vold/179:2. But for simplicity, I'll use mmcblk*p* throughout the tutorial.
Prepare the mount point for your prepared data partition, and mount it. If it's currently mounted, unmount it first.
Code:
umount /dev/block/mmcblk0p2
mkdir /system/sd
You can also format the partition now if you didn't specify the partition type during the partition creation.
Code:
busybox mke2fs -m0 -b4096 /dev/block/mmcblk0p2
Now mount the extended data partition.
Code:
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
We'll still need to be able to access the original data partition now and later, so, prepare the mount point and mount it as well.
Code:
mkdir /system/internal
mount -t yaffs2 /dev/block/mtdblock4 /system/internal
At this stage, you'll need to copy over all files inside the original /data directory to your new sd directory. You'll also need to make sure that the permissions isn't changed during the process. To do this, just tar the entire original data directory to your new one.
Code:
cd /system/internal
busybox tar -cvf /system/sd/old-data.tar *
cd /system/sd
busybox tar -xvf old-data.tar
busybox rm old-data.tar
The initialization for the new data directory mounting in the boot process does not modifies the boot image's init.rc. Thus, it seems that the initialization process is called after the radio initialization. I can't get my GSM to work without this step. We'll need to symbolic-link back the /system/sd/radio directory to the original internal storage /data/radio directory. And remember that on the boot process, we'll need to mount /system/internal *before* /system/sd.
Code:
cd /system/sd
busybox rm -rf radio
ln -s /system/internal/radio /system/sd/radio
After fiddling for several hours, I realized that the date and time settings gets reset on each boot. Fixed by symlinking the /data/date.time back to the internal storage.
Code:
cd /system/sd
busybox rm -rf date.time
ln -s /system/internal/date.time /system/sd/date.time
5) Prepare the boot init script
---------
The Froyo boot process runs init.rc script, which is replaced by the boot.img when system boots. So we can't put our new /data directory mount commands there, unless we extract, unpack, modify, repack the boot.img. Ok so I decided that modifying boot.img will be the last step if I can't get it working without it. There must be an easier way!
Also, there aren't any rc.d, rc3.d, bla bla directory in which we can put our custom initialization script.
Luckily, there is a script that is called from the init.rc script during boot, which is stored on the root filesystem and can be customized. It's called /system/etc/install-recovery.sh. Thus, we'll put the initialization script there. If you already got a /system/etc/install-recovery.sh, you can just add our initialization script in the beginning of the. Alternatively, you can create a separate script to perform init, and call it from your modified /system/etc/install-recovery.sh.
There will be drawback, for example, it seems that the script is called after radio initialization, so we'll need to use the old /data/radio directory from the original /data directory, prepared on step (4).
So now you'll need to create (or copy) the install-recovery.sh script. You can use vi from the busybox, or easier is to just copy and paste the install-recovery.sh script provided in this post. In case you're a vi expert, fire up these commands. Don't forget to remount the root filesystem as rw first!
Code:
busybox vi /system/etc/install-recovery.sh
Write in the install-recovery.sh script:
Code:
#!/system/bin/sh
mount -t yaffs2 /dev/block/mtdblock4 /system/internal
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -o bind /system/sd /data
Don't forget to set executable and readable attribute at least for root user, or else the system can't run the script!
Code:
chmod 755 /system/etc/install-recovery.sh
So now you're ready to reboot the system. Double check the install-recovery.sh script, make sure all commands mounts the partition exactly to where you intend it.
6) Reboot your Ideos S7!
---------
Reboot and enjoy the trendemous increase on your internal tablet storage
WARNING!!! Do not attempt to perform factory data reset while running with /data mounted. It seems that S7 will format the /data partition as yaffs2, not sure as I haven't checked it. But it worth to try to change the install-recovery.sh script to mount the data partition as yaffs2, and then performing factory data reset.
Sorry I can't post either an image or attachment yet
Click to expand...
Click to collapse
can you make a video about how increase the internal memory? i trying but at final step after restart my ideos nothing happens, or screenshots, please i have 4 for weeks looking for a solution about the low memory on my ideos, i install joenilan rom but dont like me the launcher, please and sorry for my bad english.
This is one good tutorial that I missed
Sent from my Ideos S7 using XDA App
HELP
Hi, i followed the steps, and my ideos keep looping at the ideos start screen
is there anything i can do?
zonyman said:
Hi, i followed the steps, and my ideos keep looping at the ideos start screen
is there anything i can do?
Click to expand...
Click to collapse
Reflash with new program,search it ..
My way !
My device : Huawei S7-105
Another way to increse internal memory :
1 flash with stock rom 2.2.2 norvegian
2 flash trizetmod v3
3 with MiniTool Partition Wizard Home Edition i've made 3 partitions on internal memory ( s7-105 using mass storage options )
- 1.2 Gb fat32
- 6 Gb ext4
- 157 Mb swap linux partition
This was one of many attempts to increase memory , and at the end i was happy with that result ! I think that you can make your own partitions , as you wish ! I have seen many movies on youtube .
Most important thing to remember : first you create fat32 partition and make it primary , second is ext4 partition also primary and the last swap partition !
After you create the partitions , reboot in recovery and make a factory reset , and your S7 has 6Gb program memory !!!!!!
Another important thing : I am a newbie in " Android world " , so I do not know how correct is what I did but one thing is certain : I HAVE 5.28 Gb and I got rid of that annoying message LOW MEMORY !!!!!!
I hope I posted in the right place , so i ask an admin to check ! Thx
in summary of this post..
all you have to do is to backup ur current rom via cwm by goodane..
make a 2nd primary partition formatted ext2/ext4 (for ext2 supports 2GB or less.. ext4 for 2GB or higher)
flash trizet's v3 rom
-THE END :good:
Hello guys!
I have a Huawei Ideos S7 Slim too,
Specifications
- Model: Huawei Ideos S7 Slim
- Version: 202u
- Intermal memory: 160 mb
I'm trying to do the steps to increase the internal memory
I don't getting success with the process
I wonder if the process works with the model Huawei Ideos S7 Slim 202u
Thank you
Hello there
I was wondering, can the internal sd card can be mounted with CWM?
If so, can you provide the button count to do it?
I have a S4 with a broken LCD, and I want to retrieve the data, but since I can't enter the passcode, not kies or windows see the files.
I managed to root it and flash CWM but now I got stuck and I just don't remember if I can't mount the internal SD with CWM
dsv591 said:
Hello there
I was wondering, can the internal sd card can be mounted with CWM?
If so, can you provide the button count to do it?
I have a S4 with a broken LCD, and I want to retrieve the data, but since I can't enter the passcode, not kies or windows see the files.
I managed to root it and flash CWM but now I got stuck and I just don't remember if I can't mount the internal SD with CWM
Click to expand...
Click to collapse
install android sdk if you dont have it.
boot your phone into cwm and connect to pc.
open cmd line where adb file exist, and type:
Code:
adb devices
you must see your serial number with recovery
Code:
adb pull /sdcard/ /sdcard/
when it finish, "sdcard" folder in "c" directory
samersh72 said:
install android sdk if you dont have it.
boot your phone into cwm and connect to pc.
open cmd line where adb file exist, and type:
Code:
adb devices
you must see your serial number with recovery
Code:
adb pull /sdcard/ /sdcard/
when it finish, "sdcard" folder in "c" directory
Click to expand...
Click to collapse
So, after some struggling with the adb drivers I got the device detected by adb and gave this a try, but I think I hit another wall.
sdcard showed 0 files, so I entered the shell and realized the sdcard was not mounted.
I tried to mount it by running mount /sdcard/ but it says sdcard can't be found in fstab{
This is what my fstab has:
cat fstab
/dev/block/mmcblk0p19 /cache ext4 rw
/dev/block/mmcblk0p21 /data ext4 rw
/dev/block/mmcblk0p20 /system ext4 rw
Any suggestion? Thanks in advance
EDIT: I'm thinking that maybe CWM didn't flash correctly (I did it from Odin, and since I'm going blindly there is no way for me to know for sure)
dsv591 said:
So, after some struggling with the adb drivers I got the device detected by adb and gave this a try, but I think I hit another wall.
sdcard showed 0 files, so I entered the shell and realized the sdcard was not mounted.
I tried to mount it by running mount /sdcard/ but it says sdcard can't be found in fstab{
This is what my fstab has:
cat fstab
/dev/block/mmcblk0p19 /cache ext4 rw
/dev/block/mmcblk0p21 /data ext4 rw
/dev/block/mmcblk0p20 /system ext4 rw
Any suggestion? Thanks in advance
EDIT: I'm thinking that maybe CWM didn't flash correctly (I did it from Odin, and since I'm going blindly there is no way for me to know for sure)
Click to expand...
Click to collapse
did you try this
Code:
adb shell
mount /sdcard
samersh72 said:
did you try this
Code:
adb shell
mount /sdcard
Click to expand...
Click to collapse
I did. That's when it said that /sdcard/ coudn't be found in /etc/fstab
****************************
UPDATE
I got it to work.
If anyone is interested, this is how I mounted the sdcard
Code:
mount /dev/block/mmcblk0p21 /sdcard/
where mmcblk0p21 is the partition that sdcard usually mounts.
After that, it was a simple as exiting the shell and run
Code:
pull /sdcard/ /sdcard/
as recommended above