• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Howto install DATA2SD: Guide

Reserved for FAQs

NOTE: As you read some of the posts in this thread, you may come across issues that I faced and description thereof..

Please Note: THESE ISSUES I FACED WERE HARDWARE BASED AND HAVE NOTHING TO DO WITH DATA2SD AS SUCH.

Data2SD cant wreck your hardware.. The worst it can do is to make you do a Recovery wipe and reinstall a Rom..But don't we "Rooters" do that every other day? ;)
 
  • Like
Reactions: dtortora
Upvote 0
Far too much work just to save a few MB on app data...I'll be leaving this well alone

you should have disclaimer in red saying don't do this if you're in any way unsure how to fix it should it go wrong

Well, I was so sick of Android telling me that I dont have enough free space. MTD partitions too seemed a bother. The rewards (huge internal memory) won me over..

I added a Caution message...
 
Upvote 0
Caution message is spot on - just hope people actuall read it!!!
:D

More complex than mtd layouts. Honestly wouldn't recommend for newbies
Not a big fan of MTD. Maybe it works well for deodexed ROMs but Stock Roms are usually huge..Not much can be taken from /system

why do you have swap? desire has plenty of ram
also you should have more of a boost than that even without sync (from what ive read)
I wonder too. Will take off Swap and Sync next time and see. Though this is going to be Class 2, I dont expect improvements.

By the way, Android Application manager has a definite lag.
 
Upvote 0
OK,

this is EXACTLY what I did, nothing else. Although I already have e2fs on defrost.

Each line is a separate command, waiting for the prompt to return after each.

**obviousely there are certain assumptions about the location and name of your Busy box, ADB and data file.

Code:
cd\

cd\android-sdk-windows\tools

adb shell

mount /system

mount /data

mount /sdcard

exit

adb push c:\01data /system/etc/init.d/01data

adb push c:\busybox-armv6l /system/xbin/busybox

adb shell

chmod 755 /system/xbin/busybox

cd /

mount /dev/block/mmcblk0p2 /sd-ext

dd if=/dev/zero of=/sd-ext/ext2 bs=1048576

chmod 777 /system/xbin/busybox

/system/xbin/busybox mke2fs -m 0 -F -L userdata /sd-ext/ext2

mkdir /sd

chmod 777 /system/xbin/busybox

/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd

cd /data

cp -a * /sd
 
Upvote 0
OK,

this is EXACTLY what I did, nothing else. Although I already have e2fs on defrost.

Each line is a separate command, waiting for the prompt to return after each.

**obviousely there are certain assumptions about the location and name of your Busy box, ADB and data file.

Code:
cd\

cd\android-sdk-windows\tools

adb shell

mount /system

mount /data

mount /sdcard

exit

adb push c:\01data /system/etc/init.d/01data

adb push c:\busybox-armv6l /system.xbin/busybox

adb shell

chmod 755 /system/xbin/busybox

cd/

mount /dev/block/mmcblk0p2 /sd-ext

dd if=/dev/zero of=/sd-ext/ext2 bs=1048576

chmod 777 /system/xbin/busybox

/system/xbin/busybox mke2fs -, 0 -F -L userdata /sd-ext/ext2

mkdir /sd

chmod 777 /system/xbin/busybox

/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd

cd /data

cp -a * /sd

Hmm..I guess Sibere added a lot of code later..
 
Upvote 0
:eek:

It's certainly daunting. 6 months ago I would have left this thread straight after joining it.

Ain't that the truth. But then 3 months ago I had an unrooted, Orange-branded Desire, and now I have a rooted, custom-ROMed, modded-radio, overclocked Desire. Maybe small successes have emboldened me, but I'm interested to learn more now.

Although I'll probably wait until I've saved up a bit more cash in case I do something I'll regret ;)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones