[Q] SD-EXT doesn't mount - Desire General

Hi,
I must admit I'm not the most experienced Desire user. I've tried some ROM's but stumbled on the fact that the internal space is way to small to install all the apps I used.
So I tried flashing data2whatever when I was using the Leedroid 2.3d ROM. First off all I used GParted to make an ext4 partition of 1024MB. I downloaded data2whatever and flashed it with Clockwork. Everything looked ok in CWM, but when I rebooted I still had the same small internal memory.
So I decided to give Starburst a try with the data2sd script. Still doesn't work.
Now I looked in the mount / storage menu, the sd-ext seems not to be mounted. If tried to mount it trough clockwork but I keep getting an error. I've searched the forums but cant seem to find a fix for this.
Can anyone help me with this issue?

Redo your partitions and make sure you follow the requirements in the rom thread. Also make sure your card is in a card reader or your phone in recovery.

I did exactly what I found in this thread: http://forum.xda-developers.com/showthread.php?t=932824
Still can't mount it in recovery, I get the error message:
E:/Can't mount /dev/block/mmcblk0p2
(file exists)
This looks like the reason data2sd doesn't work to me. I suppose normally it is shown in recovery?

reemprive said:
I did exactly what I found in this thread: http://forum.xda-developers.com/showthread.php?t=932824
Still can't mount it in recovery, I get the error message:
E:/Can't mount /dev/block/mmcblk0p2
(file exists)
This looks like the reason data2sd doesn't work to me. I suppose normally it is shown in recovery?
Click to expand...
Click to collapse
I had that exact issue and it was a corrupt SD card in the end... there is some references of fixes though for that issue.

reemprive said:
Hi,
I must admit I'm not the most experienced Desire user. I've tried some ROM's but stumbled on the fact that the internal space is way to small to install all the apps I used.
So I tried flashing data2whatever when I was using the Leedroid 2.3d ROM. First off all I used GParted to make an ext4 partition of 1024MB. I downloaded data2whatever and flashed it with Clockwork. Everything looked ok in CWM, but when I rebooted I still had the same small internal memory.
So I decided to give Starburst a try with the data2sd script. Still doesn't work.
Now I looked in the mount / storage menu, the sd-ext seems not to be mounted. If tried to mount it trough clockwork but I keep getting an error. I've searched the forums but cant seem to find a fix for this.
Can anyone help me with this issue?
Click to expand...
Click to collapse
Did you follow the Starbust istructions? Did you install Data2SD script after a first boot without it?
I've Starbust Rom with 1GB of internal memory on ext4 SD... and works like a charm

Hi,
Thanks for the replies. The weirdest thing happened. This morning I booted my phone and the sd-ext was mounted! I was tried everything I could last night, nothing worked. And now everything is working like a charm,
I flashed Starburst and the ext4 partition gives me a gig space.
Sorry for anyone looking for answers, I don't have a clue what might have caused this.
Sent from my HTC Desire using XDA App

Related

I screwed up, now every ROM is effected!

I hated the 128MB partition that mounts with the internal 8GB and my sdcard, so I used gparted via ubuntu to remove it and expand the linux-swap partition to fill the 128MB of unallocated space. Now no ROMs I use can mount the internal or external storage, nor can I mount it via USB- unless I'm in recovery. From recovery I can read the sdcard and mount it to browse via USB. Anyone have a solultion for this? I've wiped data and system and tried other ROMs, but each one is affected with the same issue.
Try a hard reset
Sent from my ADR6300 using XDA App
jdkoreclipse said:
Try a hard reset
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Meaning to remove root, nand unlock, etc and start fresh?
No...its the clear storage option in the bootloadwr
Sent from my ADR6300 using XDA App
jdkoreclipse said:
No...its the clear storage option in the bootloadwr
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
My mistake. I just did that, waiting for results now.
xvenom89 said:
My mistake. I just did that, waiting for results now.
Click to expand...
Click to collapse
Nope, that did not work. My sdcard and internal storage are not mounting. Anyone else have an idea?
try a method posted in the cm6 thread
Sent from my ADR6300 using XDA App
jdkoreclipse said:
try a method posted in the cm6 thread
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
This?
http://forum.xda-developers.com/showpost.php?p=7319333&postcount=753
I don't see that as a solution. I need it to detect my storage like it does out of the box, as it did before I deleted one of the partitions. There has to be a way to restore it to factory defaults; I don't mind having to start from scratch at this point.
My only idea that might work is to flash a PB31IMG.zip from the bootloader... Anyone else have an insight?
Just an update, this fixed it:
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
Update2:
I can get my phone running the original 2.2 leaked ota, but trying to upgrade to skyraider 2.5.2 from there brings me back to square one...
I can only access them while booted using the original 2.1 ROM or the first 2.1 OTA. When I upgrade to ANY Froyo ROM, the internal storage and sdcard disappear. I wish someone here would help me out so I can move on with my life; it's been this way for 24 hours now and I can't take it anymore.
Have you tried to just remake the partitions as they were?
lamerto said:
Have you tried to just remake the partitions as they were?
Click to expand...
Click to collapse
I cannot figure out how. Clue me in? I've used clockworkmod recovery to format each partition manually, but that didn't help.
I restored completely to stock as described here, followed by using unrevoked to root. From the stock 2.1 OS, I can read from the SD Card and Internal storage just fine. I then upgrade the radio to 2.15.00.07.28, as described here; everything still works at this point. Then I choose any 2.2-based ROM (skyraider, pmf, stock, cyanogenmod, etc) to upgrade to and install it via clockworkmod recovery. At that point, the booted system no longer reads from the SD Card or Internal Storage (BOTH are declaired "Unavailable" under Menu -> Settings -> SD & Phone Storage). From recovery I can still mount the SD Card via USB.
Before this mess I was running Skyraider 2.2 almost flawlessly, then I was picky and chose to use gparted via Ubuntu to delete the smaller ~128MB partition that mounted along side the SD Card and Internal Storage because it annoyed me. After deleting it, I expanded the linux-swap partition to fill the unallocated space. I did all this while the system was booted (after applying unrevoked-forever, so it would actually take effect). I then downloaded and installed the Skyraider 2.5.2 upgrade and that is when I first discovered this problem.
I think it MIGHT be fixable if I could figure out how to manually edit configurations to mount both partitions at boot.
I hope what happened is now clear to you all, because I'm dying here without my Incredible. I can't use it properly without the SD Card mounted, so I'm using a Palm Pre Plus for the time being. I could use a 2.1 ROM, but I became too in love with Froyo to part so soon. Please, if anyone has suggestions I would love to hear them. Thanks..
Since it seems nobody else has a clue how to work with this, I'm trying more things. I don't know why I didn't think of it before, but I'm editing the phone's fstab.
What was included:
/dev/block/mtdblock5 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mtdblock6 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
I added "/dev/block/mmcblk0p3 /emmc auto rw" for the internal storage and it worked once after I rebooted, but the sd card issue hasn't changed at all. It's already defined in the fstab, so why isn't it mounting?
So now sometimes the internal storage mounts and sometimes it doesn't. Anyway, with the sd card, now I found another interesting detail: the phone recognizes a different 2GB micro sd card while booted, but not the 16GB one I've been using for ages, the one that mounts fine in clockworkmod recovery and in 2.1 ROMs. It used to mount fine in Froyo, now it is "Unavailable". Why is this?
Xvenom89,
Wished I could help. But being a noob.....
If nothing else, at least I've bumped the thread for you. (-:
Just in case it helps, if the file you're referring to is vold.fstabs, the only entries in mine are;
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 3 /
devices/platform/msm_sdcc.3/mmc_host/mmc2
Maybe you could PM one of the more friendly devs and ask if they'd mind making a suggestion.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)
I'm having the same issue with the OTA Froyo update. So I was wondering, did you figure out a way to fix this issue?
xvenom89 said:
I cannot figure out how. Clue me in? I've used clockworkmod recovery to format each partition manually, but that didn't help.
Click to expand...
Click to collapse
Uh, if you can't figure out how, how did you manage to delete one?
Methinks you should have at least written down the details from the removed partitions before you removed them
It just seems sane.
I'm sorry to sound harsh, but, what were you thinking? It's a few megabytes that you risked the usability of your phone for.
That said, I think only recreating them yourself would fix it properly - possibly given the partition map of another Incredible (heck, maybe just dumping the first 512 bytes of the emmc device, assuming it's MBR, from a working incredible and having you patch that in would fix it.).
Yea what were you thinking, you don't just delete partitions randomly >.

E: Can't mount /dev/block/mmcblk1p2 (File exists)

In Recovery (2.5.0.5) I get the error E:Can't mount /dev/block/mmcblk1p2 (File exists) Everything seems to work except nothing happens when I wipe battery stats. I have tried messing around with parted but it says it doesn't exist and doesn't let me create a new one. Does anyone know what the problem is or how to fix it?
I'm thinking it might have happened when i updated my recovery to 2.5.1.1 But I'm not sure. Thanks.
Sent from my ADR6300 using Tapatalk
cmo220 said:
In Recovery (2.5.0.5) I get the error E:Can't mount /dev/block/mmcblk1p2 (File exists) Everything seems to work except nothing happens when I wipe battery stats. I have tried messing around with parted but it says it doesn't exist and doesn't let me create a new one. Does anyone know what the problem is or how to fix it?
I'm thinking it might have happened when i updated my recovery to 2.5.1.1 But I'm not sure. Thanks.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Check out my sig.
Thanks. I'm backing up my SD card now to try that. Does the new partition need to be that big? I don't move apps to my SD card and right now only have a 2 gig card.
cmo220 said:
Thanks. I'm backing up my SD card now to try that. Does the new partition need to be that big? I don't move apps to my SD card and right now only have a 2 gig card.
Click to expand...
Click to collapse
Probably not. I have an 8 gig and like to plan for the future. Feel free to trim it, then let me know if it works and what size you used.
Thanks. That was quick and painless. I was able to make the SD ext partition 128mb. That's the smallest size it allowed.
I'm like you. Seeing any error really bugs me.
Sent from my ADR6300 using Tapatalk
I have the same problem. What is the fix? Thanks in advance!
SamuraiXDroid
samuraixzodus said:
I have the same problem. What is the fix? Thanks in advance!
SamuraiXDroid
Click to expand...
Click to collapse
Don't know. Try reading the first four posts and then you might be able to tell me.
Sent from my ADR6300 using XDA App
What does check out my sig mean??
SamuraiXDroid
Read his entire post. Including his signature.
Just a further question on that... I have read PonsAsinorem's sig and I understand what is going on, but what I don't understand is how app2SD froyo style is working: it lets me "move" my apps to the SD card from within Froyo, although there is no such /sd-ext partition in my SD card. Does it mean that in fact it is not really moving the apps to the SD card? I am a little bit puzzled here...
Thanks,
DJKarras
DjKarras said:
Just a further question on that... I have read PonsAsinorem's sig and I understand what is going on, but what I don't understand is how app2SD froyo style is working: it lets me "move" my apps to the SD card from within Froyo, although there is no such /sd-ext partition in my SD card. Does it mean that in fact it is not really moving the apps to the SD card? I am a little bit puzzled here...
Thanks,
DJKarras
Click to expand...
Click to collapse
I haven't toyed around with apps2sd extensively. I don't have that many and they read quicker off internal, if only slightly, so that is where I keep them. Also makes it easier to flash ROMs (I'm a firm believer in wiping all data and remnants of the previous ROM). I also didn't come onto the Android scene till rift before Froyo so I was a rookie. Which is what this MIGHT be, a fragment of 2.1, or even earlier, left behind for compatibility purposes. I don't have enough background to answer this with certainty.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
I haven't toyed around with apps2sd extensively. I don't have that many and they read quicker off internal, if only slightly, so that is where I keep them. Also makes it easier to flash ROMs (I'm a firm believer in wiping all data and remnants of the previous ROM). I also didn't come onto the Android scene till rift before Froyo so I was a rookie. Which is what this MIGHT be, a fragment of 2.1, or even earlier, left behind for compatibility purposes. I don't have enough background to answer this with certainty.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
The apps2sd implementation for our phone doesn't actually move it to our sd card, it moves it to emmc (internal storage) instead and doesn't require an ext partition.
Hi, I have Galaxy s and i had the same error message so I did as explained... but now my phone get stuck on defalt recovery screen and when I try to select "apply sdcard:update.zip" it says "E:can't open /sdcard/update.zip (No such file or directory) Installation aborted"...
what I understand is that the instructions for formatting the SD card wiped all the data including update.zip file.
Now my phone is no more usable, it get stuck on main default recovery(not clockwork) :-(
Please hepl me.. I know Its a another phone section but please help me if you can
Thank you in advance
Error Solve
I use "Paragon Partition Manager" to solve this problem with my sd-ext
make sd-ext to 3 partitions
First partition
for keep your data set file system to FAT32
Second partition
create new partition size beteen 32 - 40MB and file system is Linux Swap
Third parition
create new partition size around 517MB and file system is Linux Ext2
Done!!
ps. sorry for my poor english language
I'm having this error happen when I try to wipe Dalvik cache. I don't understand the Check my sig thing. I'm an idiot.
TokedUp said:
I'm having this error happen when I try to wipe Dalvik cache. I don't understand the Check my sig thing. I'm an idiot.
Click to expand...
Click to collapse
Not really, because I took it out. I'll see if I can dig it up again.
TokedUp said:
I'm having this error happen when I try to wipe Dalvik cache. I don't understand the Check my sig thing. I'm an idiot.
Click to expand...
Click to collapse
Here ya go.
http://forum.xda-developers.com/showpost.php?p=8728693&postcount=1823
thank you. i'm gonna leave it alone for now.
Tried That
PonsAsinorem said:
Here ya go.
http://forum.xda-developers.com/showpost.php?p=8728693&postcount=1823
Click to expand...
Click to collapse
I tried solving my problem just as described in the link above. I thought that it had been because I had partitioned my SD with too big a partition, 2 Gig. I resized my partition, exactly like described using AmonRa, without any problems except that the error still remained. I tried it again but this time with Clockwork. Again no success. I finally gave up and re-partitioned it with AmonRa and my original 2 Gig EXT partition. Finally success! I dont know if attempting with different recoveries did something but it worked and it worked with a 2 Gig EXT partition. Hope this helps someone else.

[Q] Did I just FUBAR my Desire? [Fixed]

Hi.
Desire suddenly doesn't want to read any kind of sdcards anymore. Powering on brings me to FASTBOOT. CWM just says that it can't mount /dev/block/mmcblk0p1. Also, SD-EXT was supposed to be there, it fails to find that one as well. Also Win7 suddenly says it can't find driver for Qualcomm CDMA Technologies MSM? WTH is that?
It did OK not ten minutes ago before it happened. PC reads any kind of sdcards fine.
Ok, my bad. I've been swapping sdcards. I've been pulling battery out, because sometimes it had hanged.
In short, did I somehow FUBAR it? Or is there something I can yet try?
have u try to go into recovery an do a fully wipe an the install the rom again
Yes. It wipes DATA, CACHE and then complains that "No app2sd partition found" (I can live with that) and Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
I've done partitioning with GParted. Also, that sdcard is stock 4 GB that came with the device.
Also, for info, I'm running S-OFF and CWM 2.5.1.8
Search for usb brick.
Sent from my HTC Desire using XDA Premium App
Try to remove the SD Card from phone, insert it again, power up and go to the recovery/mounts&storage, try to unmount and then mount SD Card.
See if that helps, i had similiar issue and it helped me. (Also be sure FAT32 is first partition followed by ext3/4 and ofcourse both primary!)
cralias said:
Yes. It wipes DATA, CACHE and then complains that "No app2sd partition found" (I can live with that) and Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
I've done partitioning with GParted. Also, that sdcard is stock 4 GB that came with the device.
Also, for info, I'm running S-OFF and CWM 2.5.1.8
Click to expand...
Click to collapse
try use use cwm 3.0.0.5 an do a fully wipe an new partion whit cwm 3.0.0.5
http://forum.xda-developers.com/showpost.php?p=9207285&postcount=1
Take a look at this thread.
Ok, thx for fast responses. Will try this now.
EDIT: Huuuuge amounts of thanks for pointing me at USB-BRICK fix thread. Didn't even know it was called like that.
I was totally like "what I've done!!?" and started a thread without sitting down and thinking about the problem, sorry about that.

fix "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!.

I flashed a Leedroid 3.0 and it was just stuck in the boot screen. So tried to clear data and all thru recovery and i got this error "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!.
I downloaded gparted to repartition my 8gb sd card. I did a ext3 partition. When i plug back the sd card, the error still comes out in recovery mode. Any rom i flash gets stuck in Bootscreen still. I tried partitioning my 4gb sd card but it also gave the same error in the recovery.
please help. Been trying the whole day and still nothing is happening
Have you tried partitioning it through recovery? (If you have that option available)
I'd begin with reflashing a cwm recovery, cause maybe the problem is not your sd. In "mounts and storage" did you try to mount/amount sd-ext ?
Sent from my Desire using LeeDrOiD 2.4.1
I cant also mount/unmount sd ext. It says the same thing. can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!. should i just buy a fresh new memory card?
What exactly is your recovery ?
Sent from my Desire using LeeDrOiD 2.4.1
flash clockworkmod recovery 2.5.0.7 . Im using a sd card now without partition. It seems to work with the rom. Using Leedroid 2.4.1 . If i use the original SD card and reboot it with it, its just stuck in HTC boot screen.
So you should just use parted again with your stock sd to make it work ...
Sent from my Desire using LeeDrOiD 2.4.1
can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/
Click to expand...
Click to collapse
Common error when card is not partitioned or wrongly partitioned. First make Fat, then make EXT.
http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Thanks man. I was able to repartition. I made a wrong partition in gparted. Made a fat32 primary then the second one extended partition. From your post i made it primary also the second one. Now my rom reads the sd card. Thanks again.
Hmmm I had this exact same problem with LeeDroid 3.0.2... Trying to flash without wiping, had about 80 apps on my EXT3 partition... Got stuck on the white HTC screen for about 2 hours, gave up, pulled the battery, tried to flash the alignment zip, still stuck... tried to restore nandroid backup but then started getting this same error as you.
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
streetdaddy said:
[..]
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
Click to expand...
Click to collapse
May I ask how did you manage to do that?
EDIT:
Ok. Apart from the backup/restore issues that depend on having a healthy ext partition as I figure, the "can't mount [..] error mounting /sd-ext/!" problem is responsible for the "green HTC logo on the white screen freeze" also. So I've been trying to make it work all evening and this is what I found:
The Error (at least in my case) and the freaking "green HTC logo" freezez were generated because the Ext partition got corrupted in some bizarre and mysterious way. I have no idea how that could have happened, but I guess a small role in this ballet got played by the ROM itself and maybe even the nandroid backup built into the CWM (ClockWorkMod). It started right after I finished installing a fresh copy of the LeeDroid 2.4.1 and all my favourite apps (which worked flawlessly), rebooted into bootloader > CWM > nandroid and made the full backup of the system. Rebooting the device afterwards got me into the above mentioned freeze.
I tried many things, among which were flashing different ROMs and Radio images (without wiping though), but none worked. I just wanted to roll back to the previous state (because i've spent quite some time configuring and installing the 2.4.1) and it seemed impossible at that point. Browsing the recovery options got me into the Mount and storage section where I noticed the listed error with the ext partition. I thought maybe formatting will help - well, it didn't. After a couple of weird things I had tried, I've decided I should delete the ext partition (leaving just the fat32 intact). Creating a new ext partition from scratch seemed to solve the error. However this didn't solve the freezing. And the reason had to be the fact that when it created the nandroid backup images, the ext was already corrupt (or however unreadable), so the relative image was not written because it didn't see the source.
I doubt there is any way to fully restore my previously installed ROM with all of it's apps in place and in a functioning order, because the ext partition had data on it and now it's missing (hence the freeze).
Therefore the question: what could have gone so badly wrong to compromise the ext partition?
And another one: is the LeeDroid 2.4.1 ROM or the 2.5.0.7 ClockworkMod Recovery the culprit?
Sorry for the looong post. I look further to hearing from Lee, if his busy schedule allows it and thank him in advance.
Cheers!
streetdaddy said:
Hmmm I had this exact same problem with LeeDroid 3.0.2... Trying to flash without wiping, had about 80 apps on my EXT3 partition... Got stuck on the white HTC screen for about 2 hours, gave up, pulled the battery, tried to flash the alignment zip, still stuck... tried to restore nandroid backup but then started getting this same error as you.
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
Click to expand...
Click to collapse
hi! having the same exact problem right now... could you please help me how did you rescue all of your sd-card and sd-ext partitions? Thank you very much!
same problem on my N1, reparition to resolved
hi..
i got this problem too
i have clockworkmod recovery. pvt4.
cyanogenmod 7.1.
didn't make any partitions,
everything is by default as i got with cyanogenmod
s-on.
sd - 8gb, class2
yesterday my desire freezed.so i had to pull out the battery. but i couldn't turn it on till' i didn't wipe cache and dalvik cache.
When i selected wipe dalvik cache i got this
E: can't mount /dev/ block/mmcblk0p2
(file exists)
but it wiped it and my phone worked.
this appears even without sd card
it freezed after a week again but after a couple of reboots it works again but the error still exists.
i am newbie so i don't know what to do?
So I flashed a ROM which stuffed up my partitions somehow (also became S-ON, WTH?!).
I got 'can't open /dev/block/mmcblk0 (or /dev/block/mmcblk0p1) (invalid argument)' when trying to mount /sdcard.
I also got the aforementioned 'can't open /dev/block/mmcblk0p2 (file exists)' when trying to mount /sd-ext.
After literally 16 hours of head banging, I realised when I partitioned the SD card again that they were logical instead of primary. Partitioned using minitool partition wizard home edition.
Rundown:
I'm using LeeDroid v3.3.3 with clockworkmod recovery 2.5.0.7
Make sure you partition FAT32 first as primary, then ext3 as primary. LeeDroid says to partition ext3 1GB after FAT32, so e.g. my SD card is 16GB, I have ~13.8GB FAT32 | 1GB ext3
This fixed the 'can't mount /dev/block/mmcblk0' error, /sdcard is mountable.
You can now run .zip files from recovery (yay!). Throw alignment_ext3.zip on there and run it. You should now be able to mount /sd-ext.
Do a full wipe + Dalvik cache wipe (to test /sd-ext accessibility). For me it was back to normal and I'm currently doing a restore.
Always do a backup.

S-OFF for SD ext?

Hi, I have a rooted myTouch 3G Slide running a custom mod (similar to stock with some tweaks) with S-ON
I wanted to be able to install my apps on the SD card and increase my internal memory with a 2nd partition on my SD card
I know everything on how to make the partition and the swap partition, how to format the partitions, how big to make them etc. I just want to ask:
DO I NEED TO HAVE S-OFF TO BE ABLE TO DO IT?
i recently tired very hard to do it using the Rom Manager and Link2SD as well as some other techniques such as making the partitions myself and using A2SD script with the A2SDGUI application. With just using Link2SD, i got an error that saied it cannot allocate the memory when I tried to create the boot script and when I used the A2SD script, it said that my apps were being sent to the sd card but when i rebooted, all of the apps i linked to the SD were gone and i was not able to get them back.
I've tried looking around the forums and on google but i have not been able to find a definitive answer to my question. Does my device need S-OFF or will I be able to do this with S-ON?
Thank you in advance.
bumpity?
I believe you do
http://forum.xda-developers.com/showthread.php?t=893706
actually, you don't need S-OFF to move your apps to the ext partition on your sd card. I haven't used any of the apps on market/play store myself, i've always just run the DTApp2SD script. Let me know if you need the zip for that.
@morphuex: the link you provided is for custom MTD, it will allow you to resize your phone's inner storage to fit your need, which does require S-OFF.
Oh, thought that what he was asking, must of read it wrong. :silly:
I've tried to apply dtapps2sd-2.7.5.3-beta04 to my device running CM9 beta 3 (Jun 21 2012) version and got unbootable device. It started and got stuck at the white T-mobile screen before CM9 animation.
Maybe this was caused by having s2e installed on the device which was used to move data to sd-ext partition. So just be careful and make a prior backup just in case.
By the way, does anybody know why I get an error message like 'unable to mount /sd-ext partition. unsupported by your device' while i'm trying to make a nandriod backup using CWM recovery?
Saem persun said:
I've tried to apply dtapps2sd-2.7.5.3-beta04 to my device running CM9 beta 3 (Jun 21 2012) version and got unbootable device. It started and got stuck at the white T-mobile screen before CM9 animation.
Maybe this was caused by having s2e installed on the device which was used to move data to sd-ext partition. So just be careful and make a prior backup just in case.
By the way, does anybody know why I get an error message like 'unable to mount /sd-ext partition. unsupported by your device' while i'm trying to make a nandriod backup using CWM recovery?
Click to expand...
Click to collapse
yes, it means you don't have an sd-ext. if you do it will mount it. it will say the same error on anything that does a backup.
you do not need s-off to move apps to a created sd-ext. when my mt3gs was my daily phone i used simple2ext to manage my sd-ext. worked fine. i was using cm7.2.
makila said:
yes, it means you don't have an sd-ext. if you do it will mount it. it will say the same error on anything that does a backup.
you do not need s-off to move apps to a created sd-ext. when my mt3gs was my daily phone i used simple2ext to manage my sd-ext. worked fine. i was using cm7.2.
Click to expand...
Click to collapse
This is not quite right. I had /sd-ext partition already created when I tried to make a backup. I did move there data & some apps using s2e app.
The same situation I experience right now. The ext partition does exist, but CWM doesn't mount it in backup process - "can't mount /dev/block/mmcblksomething (file already exists)" error.
Initially I partitioned my sd card using CWM. I created just ext partition only, no swap.
I use an unofficial CM9 beta4 build, rom manager version 5.0.0.8, recovery version 2.5.0.7. Should I try to flash more recent experimental version 2.5.1.4?
Sent from my espresso using xda app-developers app
Saem persun said:
This is not quite right. I had /sd-ext partition already created when I tried to make a backup. I did move there data & some apps using s2e app.
The same situation I experience right now. The ext partition does exist, but CWM doesn't mount it in backup process - "can't mount /dev/block/mmcblksomething (file already exists)" error.
Initially I partitioned my sd card using CWM. I created just ext partition only, no swap.
I use an unofficial CM9 beta4 build, rom manager version 5.0.0.8, recovery version 2.5.0.7. Should I try to flash more recent experimental version 2.5.1.4?
Sent from my espresso using xda app-developers app
Click to expand...
Click to collapse
yeah, i duplicated that error just now. i fired up my old mt3gs and flashed the cm9 beta4. it does give that error and won't mount my sd-ext.
i honestly haven't read enough about the cm9 for this phone to give an informed answer, sorry. i know that if i flash my backup cm7.2 everything is fine. the only difference on my phone was the rom change. I did all this on rom manager 5.0.0.8, cwm recovery 2.5.0.7.
Thank you everyone for your contributions. i will try the DT app2sd script right now and will keep you guys informed on whether or nor i was able to do it. thank you!
I got a problem. i am unable to partition my SD because the version of CWM for my phone cannot do it..(it doesnt have the option to do it)
i tried doing it from rom manager but i get an error when i try to do it, saying the signature couldnt be verified.

Categories

Resources