Data2ext CyanogenMOD - UPDATE 26/01/11

[TheGrammarFreak]

I'm a bit stumped really. It's beyond the scope of what I currently know, and I still think that this issue is best raised in the ROM's thread

 

[frostrunner]

Ok ive ran into a problem and cant seem to troubleshoot my way out of it.

Ive used your data2ext4 v4 before and used it just fine with my cdma hero running CM7.0.2

No problems there. But i recently decided to start over and update to 7.0.3. So i factory wiped, wiped dalvik, wiped cache, wiped everything.

Flashed CM7 7.0.3 and gApps then your data2ext zip.

Followed instructions down to the dot on terminal emulator. i reinstall all my apps via titanium then i try and open my apps and i get booted back to home screen. doing a reinstall of the app fixes it till i reboot the phone.

So my problem is just that. When i check my storage it looks all fine, but when i open my apps they all seem to not work.

Any ideas?

 

[frostrunner]

Is there any way to check if your data2ext is running correctly? cause under settings > storage it looks like it is, just when i reset my phone all my apps no longer work.

 

[waterpolo]

Is there any way to check if your data2ext is running correctly? cause under settings > storage it looks like it is, just when i reset my phone all my apps no longer work.

Run logcat during reboot.
See if data2ext is running.

Sent from my Legend using XDA App

 

[skygunner]

Thanks, works well on the Cyanogenmod for ZTE V9 tab.
One question: what's the right steps to flash new CyanogenMod build if I have this enabled?
disable it, flash new build? need to flash this .zip again after flash new build?
Do I have to disable it first before flash new build? Thanks.

 

[YouArePoop]

Thanks, works well on the Cyanogenmod for ZTE V9 tab.
One question: what's the right steps to flash new CyanogenMod build if I have this enabled?
disable it, flash new build? need to flash this .zip again after flash new build?
Do I have to disable it first before flash new build? Thanks.

Not sure if its the right method, but I disable, flash rom, flash data2extra, enable. Works fine, but breaks widgets. Have to remove and re-add.

Sent from my LG-VM670 using XDA App

 

[jjsan]

working

its working like a charm.

only problem for me was finding out that data2ext --enable has to be executed after booting the phone so maybe it will be good to write in first post (because mke2fs -m0 -b4096 /dev/block/mmcblk0p2 can be executed still in recovery mode)

but still many thanks

 

[eracet]

Works good thanks

 

[TheGrammarFreak]

Works good thanks

Nice edit dude

 

[doubleup]

My Data2ext is behaving really strange.
The ext app and dalvik-cache are not being used.
The files still show dates of a couple months ago.
So newer apps are not there but the ext data partition
is in active use by all apps. When I run data2ext -- enable
it tells me that is already in use and active.
Has enyone else found this problem?

 

[Zin0]

Sorry for bringing this thread back to the dead to the land of the living again but I just found out about this and I have a question I decided to make the size of my ext partition 2048 since that's the speed of my sd booster ( app on the market). I was on the 5.0.2.7 img of Clockwork but i flashed the 3.0.0.5 version, since that's what the instructions said. Anyway, process was fine and i got about 1.8 gigs of "internal memory". However, I was wondering if I had to stay on 3.0.0.5 because after I finished enabling data2ext, I went back to 5.0.2.7 and i tried to do a backup (nandroid), but it seemed to be hung up when it got to backing up the logcat, in cache. I've waited close to 2 hours but it's stuck there. On the flip side though, I tried doing a backup (nandroid) on 3.0.0.5 and it finished like normal. So do i have to stay on 3.0.0.5 to make the nandroid backups and restores work? Could the size of the partition be an issue as well?

 

[TheGrammarFreak]

Newer versionf of CWM shousld work, yeah. I wrote all this when CWM 3 was the latest version

 

[Zin0]

Newer versionf of CWM shousld work, yeah. I wrote all this when CWM 3 was the latest version

Ah. So why is it freezing/hanging up/whatever you call it (lol) when it gets to backing up the logcat?

Edit- BTW i'm using the ext4 version.

 

[TheGrammarFreak]

Ah. So why is it freezing/hanging up/whatever you call it (lol) when it gets to backing up the logcat?

Edit- BTW i'm using the ext4 version.

Err, I don't follow. It doesn't back up logcats

 

[Zin0]

Err, I don't follow. It doesn't back up logcats

Okay. So when i back up , it does the usual. It goes through data, system, android_secure, etc. but when it gets to cache, it tries to back up the logcat. So Cache is the header and logcat is the detail. Idk why it goes to logcat but it is and its get stuck there. Do you follow now?

Edit- I'm going to try doing this again but this time should I try changing the partition size to 1024 or can I leave it at 2048? Also, i'm gonna try using the 5.0.2.7 version of CWM instead of the 3.0.0.5 version.

---------- Post added at 07:43 PM ---------- Previous post was at 06:48 PM ----------

I'm getting a "tune2fs: applet not found" error after doing
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2

 

[TheGrammarFreak]

I would assume that your current version of busybox doesn't have tune2fs in it, try installing a new version of busybox (busybox installer from the market)

 

[Zin0]

I would assume that your current version of busybox doesn't have tune2fs in it, try installing a new version of busybox (busybox installer from the market)

I tried installing the latest version of busybox and i rebooted the ol' hero but alas, i still get the same error. (Using the Busybox Installer app on the market)
Edit- I tried using the "Busybox"app and apparently it worked. Trying the commands now.

---------- Post added at 08:54 PM ---------- Previous post was at 08:38 PM ----------

It's still not working. This is so strange since it worked perfectly the first time I did this...So what do you think, Grammar?

Edit- Now instead of the applet not found, i get "tune2fs: not found" What's that mean?

 

[TheGrammarFreak]

I don't really know, I don't understand why the commands would simply stop working. Tune2fs: not found means exactly what it says by the way, Unix is good like that

In all honesty, if you can get it back to where you had it when you first posted (data2ext working, CWM 3.0.0.5) I'd leave it there. CWM3 and CWM5 are functional identical, especially for older devices.

Seeing as I don't know the exact state of your phone at the moment I can't really advise on getting everything working again. However, restoring your ROM without deleting your data would just be a case of re-flashing the ROM without a data wipe. That will revert busybox to what it was before, and it should bring tunefs back too

 

[Zin0]

I don't really know, I don't understand why the commands would simply stop working. Tune2fs: not found means exactly what it says by the way, Unix is good like that

In all honesty, if you can get it back to where you had it when you first posted (data2ext working, CWM 3.0.0.5) I'd leave it there. CWM3 and CWM5 are functional identical, especially for older devices.

Seeing as I don't know the exact state of your phone at the moment I can't really advise on getting everything working again. However, restoring your ROM without deleting your data would just be a case of re-flashing the ROM without a data wipe. That will revert busybox to what it was before, and it should bring tunefs back too

I see... Unfortunately, when i flashed 5.0.2.7, my backups "disappeared" somewhere. So i guess i'm basically screwed. Right now, i was actually to do the ext2 version and everything seemed to go well except when i rebooted, I still had the same amount of memory left (150 mb). It most likely has something to do with the tune2fs thing. I don't suppose there's another way I could restore my busybox back to what it was 2 days ago or at least reset data2ext so it can be clean lol.
Edit- I had another thought..Could it be my Rom?

 

[TheGrammarFreak]

I see... Unfortunately, when i flashed 5.0.2.7, my backups "disappeared" somewhere. So i guess i'm basically screwed. Right now, i was actually to do the ext2 version and everything seemed to go well except when i rebooted, I still had the same amount of memory left (150 mb). It most likely has something to do with the tune2fs thing. I don't suppose there's another way I could restore my busybox back to what it was 2 days ago or at least reset data2ext so it can be clean lol.
Edit- I had another thought..Could it be my Rom?

Wrong button there -_-

I doubt your ROM is the issue. The first few lines of the logcat while booting would help in working out why data2ext2 isn't working.

The only suggestion I have left it to back up what you can, wipe and start over. In the interest of transparency, there are probably less destructive ways of fixing this; however I haven't used data2ext in ages. I think I stopped using it about a month after I posted it here, so I have no idea how this works any more

To restore your version of busybox just flash your ROM again with no wipe. All your data will be intact (assuming the creator of your ROM wasn't a jerk by putting a wipe in the updater-script). What the re-flash does is restore the /system partition back to default. (Busybox is stored on /system). To reset data2ext run data2ext --disable, wipe /sd-ext then re-enable data2ext, but you lose all your data (I think).