[SOLVED] SD-EXT doesn't mount on boot - Nexus One Q&A, Help & Troubleshooting

Hi,
If you experienced this problem go to the 6th post where the answer is.
Have a weird problem.
SD-EXT partition seems to not mount and be discovered by system at boot. As a result cannot use DT, S2E for CM7.
Here is some background info, I suppose my diagnosis is right. Please help
I bought google-branded Nexus One with Eclair, opened the bootloader installed CWM, partitioned SD card and installe newest CM7 nightly with gapps and DT. That made the phone reboot each time any new app was installed.
I tried with different DT versions, S2E app from Market and the problem wasn't solved. Then tried MIUI, but when enabled A2SD there all apps from data were gone.

The card might need to be repartitioned/reformatted.

Did that as well, even have used different cards, formatted on different recoveries and so on. Now I found out method of Data2SD from Desire, it works on CM7 and MIUI, but I am afraid of poor performance as dalvik and data of apps are on SD-EXT now...

You could try to perform a simple copy test to/from /data and to/from SD-EXT, to know how do the speeds differ, if at all. Internal memory of Nexus isn't really speedy.

You mean via ADB? I'll send some file as soon as I'll be on Win and give it a try
After all I noticed that both SD cards were Class 2, whereas in my Wildfire I have class 10. But that really shouldn't make that difference, should it?
Also an app Link2SD works fine, so the partition itself is accessible.
I also noticed, that on Wildfire there are 4 statbars in menu (Internal Memory, System, SD card, sd-ext), but on Nexus the last one is gone. This is why I think something curious is about mounting.
Does anyone know at what stage of boot DT A2SD is activated? When the SD-EXT partition gets mounted?

Nexus One controller speed is limited, so anything beyond Class 4 most probably will be simply a waste.
The SD-EXT should be mounted when the kernel is up and running the boot scripts (/system/init.d/*). Usually it's mounted in one of the first scripts (they're numbered, and run by number sorting order).
The tab in the phone menu is an option of specific ROM. No stock ROM supports A2SD, so in order to get this tab you need a custom ROM that has this specific option integrated. I don't know of any - though MIUI most probably has it.

[SOLVED]
Thx all for help.
It was radio to blame. I installed CM7 after stock Eclair with very old radio.
Solution: go back to stock Eclair, do all OTAs and try once more with A2SD.
(and never buy a Wildfire to be afraid of doing OTAs on Nexus (I've lost root possibility by doing OTA on WF))

Related

ROM - Deodexed with root, newest busybox, supports JAC kernel, no more lag fix

This has been updated to be deodexed+root+busybox only (though it still supports JAC kernel out of the box). At this point there are so many different lag fixes that it's hard to keep up with them all.
What it does have:
ROOT
No .odex files (deodexed)
Newest Busybox
ext manipulation files and libs, so it makes it easier to e2fsck or tune2fsck if you want ext4.
Also thanks to eugene373 for his work in establishing a baseline update.zip without which this would have taken a great deal more work.
Should work in clockwork, doesn't seem to need a wipe. If you have problems, use regular recovery, just rename it to "update.zip" on the root of your sdcard and it should flash just fine.
WARNING:
This should be completely safe. Nonetheless, should loss of job/loss of fertility/nuclear war ensue, I am not responsible.
Instructions:
1. Load the .zip file onto the root of your internal SD card (/sdcard)
2. Using Clockwork recovery, do "Install zip from SD card", then "Choose zip from sdcard", choose the VibrantDeodexed.zip, and choose "Yes"
2b.(ONLY If you don't have Clockwork) rename the download to "update.zip" and place it on the root of your sdcard. Then reboot into recovery and choose "Update packages".
3. (Optional) Flash JAC's kernel with ODIN using the directions specified HERE It is more stable and gets better benchmarks but there do seem to be some issues with the screen taking a while to wake up.
http://www.getyourboneon.com/VibrantDeodexed1_2.zip
NOTE: The first boot takes a long time because it has to dexopt stuff.
Version 1.0:
Just stock and rooted w/busybox
Version 1.1:
Uses the latest version of busybox and comes with support for JAC kernel out of the box (no need to flash the init.d update.zip and supersedes my method if his kernel is flashed.)
Version 1.2:
Updated busybox, added ext tools. Removed all lag fixes, though it will still work with the JAC kernels.
There are so many lag fixes out there at the moment that I didn't want to "lock in" people to a particular one.
Part of the high quadrant score is the 90 million triangles/sec. The data script boosts the data score.
Sent from my SGH-T959 using XDA App
what is the ext hack? and how does it make the phone faster?
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
original link is here for the hack--http://forum.xda-developers.com/showthread.php?t=739647
anomalous, thanks for all your hard work...
so if we get a good deodexed rom, someone could compile JIT for our 2.1 right?
junkdruggler said:
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
Click to expand...
Click to collapse
why does the phone run faster with the data stored externaly? or is it because of the partition type?
im not quite sure, I would have figured our internal mem had a faster transfer rate than an sdcard, but Im on a class 2 and still getting better results... so it cant be a faster transfer rate...
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Just so everyone Knows, the Format via the update script don't work, still trying to find the correct command for it....
But, in clockworkmod, just format the system / data / cache partition's before flashing.
designerfx said:
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Click to expand...
Click to collapse
Er, the internal storage is "rfs", samsung's proprietary fs. (And the read/write speed of fat32 tends to be a little faster than ext2, and TONS faster than ext3/4 - journals slow it down in exchange for stability after crashes)
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Disconn3ct said:
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Click to expand...
Click to collapse
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
FastKatt said:
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll see what I can do to test it out this afternoon. (If you want to jump the gun, what I'm figuring is finding a static-linked arm version of bonnie++ or similar. Booting recovery, mount data or sdcard - not both - and test. Reboot recovery, test the other one. Maybe test dbdata and external sd as well, but the interesting numbers will be the first two - onboard-with-rfs and onboard-with-vfat..)
ivanmmj said:
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
Click to expand...
Click to collapse
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
anomalous3 said:
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
Click to expand...
Click to collapse
Which ROM kitchen? I used my own script. Does the ROM boot up and run doing it that way? Should be interesting to play with.
Hmm, got the update script working almost perfect, but now it causes crashes. Seems to be missing dbus.conf.
OP updated - it works.
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
theMAGNUM said:
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
ArbitrageMan said:
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
Click to expand...
Click to collapse
No adb shell doesn't find my device

[Q] HELP TY

CM7 can make you install apps on the sd card, how does it differ from app2sd or app2ext? i have been trying to decide if i should partition my new sd card or its not necessary. There must be an advantage to have app2ext right?
Thank you.
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
bassmadrigal said:
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Can you do this with rooted stock?
lolobabes said:
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Click to expand...
Click to collapse
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
yes you can.
bassmadrigal said:
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
Click to expand...
Click to collapse
thanks for the reply i think i read on darktremors post class 4 will do for the data2sd. I have class 4 16GB sd card would 1GB good for the ext? ty
It really depends on how much you think you will be installing. I did a 1GB partition on mine, but now that I install most of the Amazon free daily apps, that space is dwindling quickly. I have programs that will resize the partition for me, but most will have to wipe the card and partition it manually. I do have the install location set to automatic, so it allows developers to specify whether they want it in the "internal" (really it is on the sdext partition, but to the phone it is internal) or external using the froyo method. The Angry Bird apps all default to install on the sdcard, so my installed app base is even larger than 1GB.
bassmadrigal said:
... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
I second this
Sent from my Nexus One using XDA App
is it true that cwm sets the partition to ext3 by default? unlike in ra recovery where you still need to convert it? ta
I have heard that it creates it in ext3, but right now, DTa2sd is showing that it is a ext2 partition. I can't figure out how to find out for sure while the card is in the phone. Either way, it is getting mounted as an ext2 partition.
temasek said:
I thought CWM will create ext3 by default? Your steps are ok, np.
Anyway when u read the ext partition type in android, most likely u will see ext2 if u are using official DT script cuz of the auto syntax it uses.
Click to expand...
Click to collapse
then it maybe so, this was posted on the darktremor thread
http://forum.xda-developers.com/showthread.php?p=14134665#post14134665
Well, whether or not it is formatted as an ext3 partition, Android is still mounting mine as an ext2 partition.
Code:
mount | grep ext
NOTE: the "|" is called a pipe. On the keyboard it is the shift option on the backslash key "\". I don't know exactly where it is on the stock keyboard, but on swype it is located under the "D" key when the keyboard has the shift key pressed and you access it by longpressing.
To get your sdcard to ext3, you just need to turn on journaling. You can do this through adb while in the recovery (because you need the partition unmounted to do this).
Code:
adb reboot recovery
adb shell
mount system
e2fsk /dev/block/mmcblk0p2
tune2fs -j /dev/block/mmcblk0p2
reboot
Supposedly Android should auto-mount this as ext3 on boot (which you can check with the first command). At that point, I don't think it will matter what a2sd shows. As the writing of the journal (the big thing with ext3, since it helps minimize write errors on a bad shutdown) is done at the OS level, not the a2sd level.

Nexus One internal storage low

So out of curiousity I backed up all of my apps using titanium backup and installed the new MIUI Rom based on ICS. It kept crashing because for some reason the internal storage filled up. Now I re-installed CM7.1, but my internal storage is again almost full.
My question is, what can I do? I moved ALL my apps to my SD card before I even installed MIUI and before I installed MIUI, I had 170mb free. Actually while typing this I realized that I guess MIUI didn't remove CM7 when it installed or something... hmm. Anyway any help is appreciated, and be gentle this is my first post.
Also android.process.acore keeps stopping.
did you wipe data/factory reset,cache and dalvik cache atleast 3 times before flashing new rom???
Sent from my Nexus One using Tapatalk
Do it 4x, just to be sure
Each apk (program) on your system has a corresponding entry in the dalvik-cache that gets generated from the .apk. If your storage (/data) filled up things are going to be broken in all sorts of ways, including the inability to make the dalvik caches. Since you didn't format between ROMs, you'll also run into permission issues and settings that don't make sense in the new ROM. Cyanogen uses an alternate location (/cache) for the dalvik-cache for system apps, I don't know if MIUI does, but that could be some of the difference in space. Duplicating data for the same .apks in different ROMs could've also filled up your space. It's best to format all the phone partitions to not worry about this stuff. Usually you're safe not formatting /sdcard, but some ROMs are picky. Some ROM install scripts don't format /system and that leads to BIG headaches. If you format all the partitions, then you don't need to worry about clearing user data/battery stats/dalvik-cache because that was already handled when you formatted the storage that contained that data.
tl;dr: Fix permissions after installing a new ROM. If the old and new ROMs are different enough, everything will still be broken because you made the android gods angry. Sacrifice (format) /system, /data, and /cache (and sd-ext if you have it) *before* installing the new ROM and things should be fine.
Haven't used MIUI for awhile, but didn't think it had an ICS version. There is one in XDA, but it is not stable and I think requires blackrose hboot and differnet partition sizes for hboot. It also runs a2sd on reboot i think?
CM7 uses Dark Tremor beta4, that's what I use. It needs flashed after rom and scripts run to move apps. Check out their site
As suggested format all including system and format sd card with sdformatter, full erase and size adjustment on and set up 1gb ext 0 swap
copy sdcard and have a good nandroid first
rugmankc said:
Haven't used MIUI for awhile, but didn't think it had an ICS version. There is one in XDA, but it is not stable and I think requires blackrose hboot and differnet partition sizes for hboot. It also runs a2sd on reboot i think
Click to expand...
Click to collapse
MIUI has both blackrose and non blackrose version of ICS
Sent from my Nexus One using Tapatalk
right, but one is unstable and he can't keep his ics partition if flashing non ics one
I've tried the latest versions and both br and non-br ones seemed have problem with data connectivity. Some others have experienced the same. Thought the dev's investigating it. But, previous version, i.e. 2.3.2, worked fine.
Try non-br 2.3.2 with 185/85/166 partition layout, that was great.
Sent from my Nexus One
Having similar issues with ICS MiUI which really seems rather unstable (v2.3.2), and going to flash the latest update from a few days ago (v2.3.9).
Any suggestions on how to deal with some of the stock MiUI "bloatware" that comes with it and seems stuck on the system ROM? A2SD is supposed to be enabled, but unless stuff I dowload off market/play or restore is deemed systems apps, which I doubt is the case, I can't seem to choose to move them to SD card or in this case the "USB Storage" (Sorry, my postcount's too low to post on the actual MiUI Dev thread)
Also, as a sidetrack, does anyone know how best I can sieve through my contacts storage/DB? recently I think i might've accidentally synched with my FB countacts and it seems to have bloated up to 16-18+Mb which is alot from the previous 10-12Mb or less from what I recall. Is there an app or something to help 'manage" it better or do I have to manually go through and get rid of excess contact info on the phone or from my Google contacts list?
Thanks in advance for any advice you guys might have.

[Guide]How 2 Create EXT3 for the Salsa only! * Increased Internal Memory*

Ok seems many usrs here have the same problems over and over again. so heres a tut!
This will probably cover many other topics but simplified here as much as i can.
You Must have the following to get this to work:
ROOT
Recovery 5.0.2.6
busybox installed.
if you have non of these...do not attempt any of this thread till you have!
To start with.
Creation of EXT3 Partitions.
you will need Minitool Partition Wizard. Mini Tool Partition Wizard Download
This is a harddrive/diskspace program allowing accurate modification of disk space.
Never create an EXT3 in CWM, as this will create whats known as a swap drive.
this causes the bootloop. Hence the non boot!
EXT3 has to be set as primary drive not logical.
Size allowance recommendations (personal choice, but this is after a few findings and results given by Salsa users)
SD Card Size.................................EXT3 Size
2GB......(Class 2).............................250MB
4GB......(Class 2-4)..........................500MB
8GB......(Class4-6)...........................500MB-1GB
16GB....(Class8-10).........................1.2GB​
WARNING, anything over 1.5GB will result in serious problems and SD damage
This also works around class types of SD Card. the higher the class the faster it works, there are various brands offering different class cards, find a fast and big card for best performance. I currently use Class 8 16GB with 1GB Ext3 with little/no lag
Wise idea before this to make an SD backup, if done correctly your data will not be affected...if you screwed up...you'll loose everything...so back it up!
To start with,
Remove Sd Card and use and SD Reader and insert into your computer USB Slot.
Open Minitool Partition Wizard.
Resize your sd card accordingly leaving 1.2-1.5gb of unallocated space. Apply the actions.
Now you have the unallocated space, reformat the space in EXT3 and set as Primary drive. Apply Actions.
Now normally the Application throws your sd out and says bad drive......this is sometimes normal so don't panic.
Reinsert your Sd in Phone and boot into recovery only
Data2sd script
theres 2 scripts available for these roms.
htc-data2sd-ext3 or data2whatever by m1ndh8x4r.
2.1 Roms work well with htc-data2sd-ext3 script with no problems.
data2whatever works really well with 3.5 sense Roms (Bens/M1nds)
*****There is a warning with this data2whatever script....When using this script, you will notice after a short period, that you cannot update or install any more apks. This is due to a Dalvik error within the script on Deodexed roms, currently it cannot be fixed, you have been warned*****​
these can be used easily but the following rules must be applied.
You must flash the rom firstly by the 3 wipes...regardless!
flash the rom as normal and reboot full, letting the rom fully build it self and load up... ie input your details/sign in wifi etc.
check it out for a few mins while your waiting...hey even make a backup lol!
OK now reboot in recovery and flash the chosen script....DO NOT WIPE ANYTHING!
once flashed reboot normally.
it will boot, it may take up to 5-10mins but it will boot. if by any chance you a boot loop at the boot animation screen then you have an EXT3 fault and you must redo the EXT3 Partition in Minitool to proceed again.
data2sd scripts are here>
http://www.mediafire.com/download.php?duigp9ky9796b65 for htc-data2sd-ext3.zip
http://www.mediafire.com/download.php?m7bv6pk024p63ef for d2extv0.43.zip (New/Advanced)
http://www.mediafire.com/download.php?qr5rh2fho1hnbnl for data2whatever
This is a proven way and so many have tried and failed other ways.
Please try this guide. If you get stuck please just ask!
Please Answer my poll at the top and Thank this post...Ty!
If you Answer NO to this guide, please post below and tell me why so i may help further
Heyy it worked thanks man
BigBearEvo said:
Open Minitool Partition Wizard.
Resize your sd card accordingly leaving 1.2-1.5gb of unallocated space. Apply the actions.
Now you have the unallocated space, reformat the space in EXT3 and set as Primary drive.
Click to expand...
Click to collapse
Trying to do this with fdisk on linux
It works but runs slowly for some reason
I have a 2GB cards, first partition is about 1.4 for normal /sdcard the remaining .4GB for /data
Both partitions are start aligned on 2048 sectors
Issue - applications get corrupted after restart
I am facing strange issue. I did everything described above and have /data on sd. But everytime I reboot something happens to most apps. They are installed but when I try to launch any of them I got errors and application closes. I need to reinstall EVERY app and they work until next reboot. Any ideas about the cause or what to check ? At this point I am trying not to discharge or reboot my phone by it;s impossible to keep it that way.
procek said:
I am facing strange issue. I did everything described above and have /data on sd. But everytime I reboot something happens to most apps. They are installed but when I try to launch any of them I got errors and application closes. I need to reinstall EVERY app and they work until next reboot. Any ideas about the cause or what to check ? At this point I am trying not to discharge or reboot my phone by it;s impossible to keep it that way.
Click to expand...
Click to collapse
thats a rom issue.
What rom are you running?
Are you using a Data2sd script? if so which one?
Are you using links2sd?
BigBearEvo said:
thats a rom issue.
What rom are you running?
Are you using a Data2sd script? if so which one?
Are you using links2sd?
Click to expand...
Click to collapse
I am running standard HTC ROM 1.12.401.2 With Sense 2.1.
I used ext3 version of script.
No. Shall I ?
procek said:
I am running standard HTC ROM 1.12.401.2 With Sense 2.1.
I used ext3 version of script.
No. Shall I ?
Click to expand...
Click to collapse
no dont lol...ok sounds a bit stupid but have u got root? because what your describing is and apps2sd thing...which u cant get on stock rom....but if u dont have full root....then this sort of thing does happen....or...you got a faulty ext3 partition...
questions next...
which guide did u make ext3?
size and did u make swap?
root?
Need file name of the data2sd script u used and how u used it...(this is important)
so i need full break down....assuming u have root that is....this almost sounds like a silly problem, but then most of us don't use stock roms anymore....so we dont have this problem lol
BigBearEvo said:
no dont lol...ok sounds a bit stupid but have u got root? because what your describing is and apps2sd thing...which u cant get on stock rom....but if u dont have full root....then this sort of thing does happen....or...you got a faulty ext3 partition...
questions next...
which guide did u make ext3?
size and did u make swap?
root?
Need file name of the data2sd script u used and how u used it...(this is important)
so i need full break down....assuming u have root that is....this almost sounds like a silly problem, but then most of us don't use stock roms anymore....so we dont have this problem lol
Click to expand...
Click to collapse
Of course I have a root - it works perfectly. I created the partition according to above instructions (I mean this thread). My ext3 partition is about 800 MB and 3200 MB is for FAT32. I did not create swap - just fat32 and ext3 with Partition Wizard. I used htc-data2sd-ext3.zip in I think normal way - phone reset, installing busybox, reboot, installing script with recovery - done. Everything is perfect until next reboot.
procek said:
Of course I have a root - it works perfectly. I created the partition according to above instructions (I mean this thread). My ext3 partition is about 800 MB and 3200 MB is for FAT32. I did not create swap - just fat32 and ext3 with Partition Wizard. I used htc-data2sd-ext3.zip in I think normal way - phone reset, installing busybox, reboot, installing script with recovery - done. Everything is perfect until next reboot.
Click to expand...
Click to collapse
sounds like a problem with your rom my friend....hard to tell without seeing it really...
have you thought about changing the rom itself?
BigBearEvo said:
sounds like a problem with your rom my friend....hard to tell without seeing it really...
have you thought about changing the rom itself?
Click to expand...
Click to collapse
To this moment no. But if there's no other option I will probably have to...
procek said:
To this moment no. But if there's no other option I will probably have to...
Click to expand...
Click to collapse
either that or find your ruu and reinstall stock again!
Funny thing
I used my previous card (smaller - just 2 GB) and there's no such behaviour as with my 4GB. Smaller one is Sandisk, bigger one is Kingstone - both known for good products. So switching ROM is rather not an option. There's something about SD but I can not figure out what...
Pls help
I have created 6gb of fat32 and copied ROM and data2sd-ext3.zip then formatted remaining 1gb space in ext3. When I tried to install zip from recovery mode it throws "E: can't mount /sdcard/"
pls help
Thx
yuva0103 said:
I have created 6gb of fat32 and copied ROM and data2sd-ext3.zip then formatted remaining 1gb space in ext3. When I tried to install zip from recovery mode it throws "E: can't mount /sdcard/"
pls help
Thx
Click to expand...
Click to collapse
how did you make the partitions? and are they set as primary?
what class sd card is it? you need a class 8 or 10 on that size.
I used mini tool for partition. I set fat32 as logical and ext3 as primary. I have 8gb class 10 SD.
Sent from my HTC Salsa C510e using XDA
Shrink the ext3 to 750mb and set all partitions as primary.
BigBear is using Xparent Tapatalk Purple
Yep now I can see my data in SD card. Another problem I triple wiped and flash arc rom again, and given detail/sign in. When trying to flash script in recovery mode, it asks for busybox in some sys folder. I don't have busybox and also script installed, but ext3 memory not reflects in as main memory. Am I used different script or I need to install busybox, if so how to do that.?
I installed busybox @ system/xbin and flashed script, it worked. Finally my internal memory problem solved:thumbup:
I request to add installing busybox step and download link for script in tutorial.
Thx bb
Sent from my HTC Salsa C510e using XDA
I used data2sd without without any problem for past two days, suddenly today some apps force closing. Instagram app show error msg like"unfortunately this device's filesystem is reporting a problem." and pointing to this url "bit.ly/igfilesystem".
pls help.
I'm using arc V2 ROM, class 10 8gb sd, with 750mb of ext3.
yuva0103 said:
I used data2sd without without any problem for past two days, suddenly today some apps force closing. Instagram app show error msg like"unfortunately this device's filesystem is reporting a problem." and pointing to this url "bit.ly/igfilesystem".
pls help.
I'm using arc V2 ROM, class 10 8gb sd, with 750mb of ext3.
Click to expand...
Click to collapse
contact instagram with a logcat or report for them to check

Formatting SD Card Ext

I have my phone unlocked and rooted and have used Big Bear's Iconic rom to flash my phone. This completed fine but part of the process after flashing describes flashinf with data2sd ext3 script. When i tried this I realised my sdcard was formatted fat 32 and not ext3. My desktop machine uses ubuntu linux and I wondered if its possible to format the card via terminal or some piece of software and in what proportions should i partition it to extend my salsa's pitiful internal memory. Also when this is done does the script need to be on a particular partition or just somewhere on the card.
If its easier to configure the card via windows I also have a winxp laptop that could do the job.
Any help greatly appreciated.
bean12345 said:
I have my phone unlocked and rooted and have used Big Bear's Iconic rom to flash my phone. This completed fine but part of the process after flashing describes flashinf with data2sd ext3 script. When i tried this I realised my sdcard was formatted fat 32 and not ext3. My desktop machine uses ubuntu linux and I wondered if its possible to format the card via terminal or some piece of software and in what proportions should i partition it to extend my salsa's pitiful internal memory. Also when this is done does the script need to be on a particular partition or just somewhere on the card.
If its easier to configure the card via windows I also have a winxp laptop that could do the job.
Any help greatly appreciated.
Click to expand...
Click to collapse
yeah it would be easier via windows, i still not found software on Ubuntu to do the partitions lol.
just copy the data2sd-ext3.zip onto your sd card that's all and flash from there. you only need a small 1gb partition max on the sd cad the rest in fat32.
Cool will give that a try tomorrow and let you know how it goes
Worked a charm thanks I do have a couple of question though if i may. Although working with no probs the script mentions preparing the partition with ext2 (I used ext3) and an app called busybox to be installed into system/xbin. What does this app do and is it needed.
Also is this script tailored to the salsa or can it be used on other android devices to achieve more internal memory?. My Desire has the same issue you see.
Thanks in advance for all the help
Yes busybox is requiredlol, otherwise it wouldn't work. We never changed the txt over from ext2 but its still the same and works on both anyway. As for desire....I have no idea, this was based on wildfire s/salsa only, try it out see what happens lol
Busybox is part of the superuser setup without this builtin or added in we wouldn't have root at all. Deleting it would cause issues too.
BigBear is using Xparent Tapatalk Purple
Busybox is part of the superuser setup without this builtin or added in we wouldn't have root at all
Click to expand...
Click to collapse
So given my phone is rooted (thanks to your help a few weeks ago) I take it I must already have this Busybox installed otherwise the script would have failed correct?
I partitioned my test 1 gig sd card into two equal parts one ext3 and one left fat32, the phone reports equal portions on sd card and internal memory via the Settings----> Storage menu. So I'm assuming all is well.
Yeah busybox will already be there lol. That's all fine on the SD, but just be aware, the lower the class SD your using, I assume its a 2gb, you may have a class 4, which will lag. If you experience lag, reduce the ext3 size to 500mb you will see a difference.
BigBear is using Xparent Tapatalk Purple
Is there any difference between data2sdext3 and data2whatever? If yes which one is better to flash with a custom ROM (I am using Bear's XSeries V11).
(Data2ext3 is causing problems for me. Crashing various apps time to time. Using a class 4 sdcard with 470 MB partition. Found data2whatever on Razer's ROM page)
razasohail said:
Is there any difference between data2sdext3 and data2whatever? If yes which one is better to flash with a custom ROM (I am using Bear's XSeries V11).
(Data2ext3 is causing problems for me. Crashing various apps time to time. Using a class 4 sdcard with 470 MB partition. Found data2whatever on Razer's ROM page)
Click to expand...
Click to collapse
A big difference between them.data2SD ext3 is designed for non apps2SD roms ie mine, data2whatever is for apps2SD roms only.if you're having force close issues then you didn't install something correctly. Using these scripts on the wrong Rom could have adverse affects in the Rom.
Each Rom made will have the correct script to use in the listing. If you choose to use them the opposite way round then the developer won't help you correct the problems I'm afraid, all I can suggest is redo the Rom of your choice till it works correctly.
If your having problems with mine, post up in the thread as long as your using the setup I gave and I'll help as much as I can.
For force close issues you can always use fix permissions in Rom manager or in recovery advanced section, this normally stops them.if it dont reinstall them Rom. It tends to be a user error when this happens, I'm using my own Rom and never get force close problems.
BigBear is using Xparent Tapatalk Purple

Categories

Resources