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 >.
Related
I'm using ClockworkMod Recovery 2.5.0.1 and i've seen a couple of guides where I go into the recovery and do some bits and bobs there to create it, but the only options I seem to get are to mount the sd-ext partition, which fails because it doesn't exist, or to format it.
I'm guessing there is a step beforehand i'm missing?
Thanks
download rom manager from market , open it , then create a ext3 partionion ... done
before you create a partition , backup your sd card!!
y2viks said:
I'm using ClockworkMod Recovery 2.5.0.1 and i've seen a couple of guides where I go into the recovery and do some bits and bobs there to create it, but the only options I seem to get are to mount the sd-ext partition, which fails because it doesn't exist, or to format it.
I'm guessing there is a step beforehand i'm missing?
Thanks
Click to expand...
Click to collapse
I had the same problem.
You can create the partition using the ROM Manager app downloaded from the market as yasars said.
Alternatively, if you want to do it manually, you can format the card on a *nix system. The Gparted Linux app lets you edit the partitions in a nice and simple GUI. Just remember the order of the partitions: first fat32, then about 512 MB of ext2/3/4 (ext4 may not be supported by all ROMs so better to use ext3) and lastly a swap partition of about 32 MB (totally optional). The size of the fat32 partition is whatever is left over after you've allocated the 512 MB for the ext2/3/4 partitions (and the 32 MB for the swap if you decided you wanted it). For instance, for a 2GB card, leaving 512 MB for the ext2/3/4 partition (no swap) leaves us with about 1.5 GB for the fat32 partition. You do the calculations for your card in your head or on paper and use those values in Gparted.
HTH.
Thanks for the help guys
I think i'll just get it up and running using the ROM Manager and if I find the need I'll do a manual version
Foolowing this guide I partitioned my sd card with GParted Live CD.
gianton said:
Foolowing this guide I partitioned my sd card with GParted Live CD.
Click to expand...
Click to collapse
You have no Idea how cool it is for me that my tutorial was useful... ;-)
chrysochire said:
You have no Idea how cool it is for me that my tutorial was useful... ;-)
Click to expand...
Click to collapse
Yes it should be a sticky!
Having a problem when I try to use ROM Manager.
I select the 512 for EXT and 32Mb for Swap and the phone reboots.
It then shows the big triangle with Mr Android next to it until I press some buttons and then I get the recovery screen with the following messages
Finding Update Package....
Opening Update Package....
Verifying Update Package....
E:failed to seek in /cache/update.zip (Invalid Arguement)
E:signature verification failed
Installation Aborted.
I don't have a cache folder on my sd card so i'm guessing it's looking in the internal memory?
Not sure what to do here
BACK-UP sd card before you do this.
For windows users
have clockwork recovery and rom manager on your desire
then format sd in windows.
put it in your desire and go to rom manager.
select Partition SD Card
select your space i used 32 swap 512 ext
than reboot and your sd card has the ext partition.
than put your files back on your sd card and Done
y2viks said:
Having a problem when I try to use ROM Manager.
Click to expand...
Click to collapse
I had the same problem with ROM Manager. My solution was to downgrade ClockworkMod Recovery to v2.5.0.0 (in ROM Manager) and then partition the card. Worked on first try.
When you're done you can upgrade to latest version again if you want.
I don't think you should use a swap partition, so just set it to 0 MB.
Good luck!
Do i just need to find the 2.5.0.0 update.zip file and flash?
going to 2.5.0.0 worked
so now i have the ext partition do I need to do anything for apps to be installed there, or will they install there by default?
Also i've heard that the ext partitions can be 2 3 or 4. I'm presuming higher is better. How do I go about finding what mine is and how can I upgrade it if it need it?
Thanks
chrysochire said:
You have no Idea how cool it is for me that my tutorial was useful... ;-)
Click to expand...
Click to collapse
Hi, I'm also going to give your guide a go. Just one question, do I have to do it with the SD card still in the phone or can i do it with a SD USB adapter?
Thanks,
Joe
I read the tutorial again and you can use an SD adapter, worked a treat. Cheers
y2viks said:
going to 2.5.0.0 worked
so now i have the ext partition do I need to do anything for apps to be installed there, or will they install there by default?
Also i've heard that the ext partitions can be 2 3 or 4. I'm presuming higher is better. How do I go about finding what mine is and how can I upgrade it if it need it?
Thanks
Click to expand...
Click to collapse
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
Code:
su
ls -l /data
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
I'm not sure which format ROM Manager defaults to, but you can always check the type of format used by mounting the card in Linux and using the GParted Linux app (you could use a card reader or use the 'Disk Drive' option in your phone to connect it to the computer). Also, ext3 should be fine for most custom ROMs. In fact, not all ROMs support ext4.
ikkokusenkin said:
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
.
Click to expand...
Click to collapse
- Another quick way is to install quick system info from the Market, it tells you infos about your system, including the use of your a2sd partition.... ;-)
- About ext 2/3/4 I would advise the use of ext3, as ext4 is poorly supported by Roms (even those who pretend seem to have issues...)
cheers
Does the decrease of available internal storage means apps22sd+ is not working? I've partitioned twice and installed seperate 2.2 roms with apps2sd+ included and every time I install more things I see internal storage drop.
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
Click to expand...
Click to collapse
I checked this and it's doing what you said
ikkokusenkin said:
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
Code:
su
ls -l /data
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
Click to expand...
Click to collapse
I took the liberty of including this information into my tutorial. I added a reference to you. ;-)
I hope this makes it to Sticky one day... ;-)
bloosteak said:
Does the decrease of available internal storage means apps22sd+ is not working? I've partitioned twice and installed seperate 2.2 roms with apps2sd+ included and every time I install more things I see internal storage drop.
Click to expand...
Click to collapse
Not in itself, no. Those symbolic links mean that A2SD is working fine. However, from what I understand about the theory, even A2SD installs a part of the app into the internal memory. That may explain the drop you see. By the way, how much free memory do you see on your device? I usually have about 140 MB free on my Desire. I read somewhere that if A2SD wasn't working, that figure would be about 90 MB.
chrysochire said:
I took the liberty of including this information into my tutorial. I added a reference to you. ;-)
I hope this makes it to Sticky one day... ;-)
Click to expand...
Click to collapse
Thanks. Although, I can hardly claim to have come up with the idea myself.
ikkokusenkin said:
Not in itself, no. Those symbolic links mean that A2SD is working fine. However, from what I understand about the theory, even A2SD installs a part of the app into the internal memory. That may explain the drop you see. By the way, how much free memory do you see on your device? I usually have about 140 MB free on my Desire. I read somewhere that if A2SD wasn't working, that figure would be about 90 MB.
Click to expand...
Click to collapse
108 free total of 148
I just recently opened spare parts apps where it allowed me to change where apps2sd installs things. By default it was set to automatic and I'm guessing that was causing the problem. I set it to external and tried installing a browser while my disk was mounted and it wouldn't let me do it. Then I set it to charge mode and it installed normally.
Some roms probably default to external while some automatic.
edit: Just installed an app that I previously installed while using "automatic" and it still uses up internal storage instead of A2SD storage. Dunno what's wrong. I am using ext2 partitioned through rom manager.
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.
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
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.
Hi, I am a total newbie and I rooted my phone (HTC Desire) and have obviously misread some instruction as I seem to have created and Sd-ext partition on the internal drive instead of the external.
I installed JB4.1.1 which is nice and I like it but whenever I try to use the camera I get a "Gallery closed" error. I'm wondering if these can be linked and if the sd-ext partition shouldn't be there? Perhaps the gallery is trying to save in the wrong place or something? I am clutching at straws to thi problem.
How can I safely remove this partition and reclaim it back if it shouldn't be there?
Sorry for being a complete tube!
Malk
How did u manage to make an ext partition on the internal?
Tell us everything you have done.
Sent from my HTC Desire using xda app-developers app
I think it is on the internal????
I went into recovery and created it?
Options I have are:-
mount /data
mount /sdcard
mount /system
mount /sd-ext
Malk
malkthealk said:
I think it is on the internal????
I went into recovery and created it?
Options I have are:-
mount /data
mount /sdcard
mount /system
mount /sd-ext
Malk
Click to expand...
Click to collapse
I highly doubt you made the partition on your internal. That would be difficult if not impossible.
Im guessing you just incorrectly made the partition.
Are you s-off? If so download the 4ext recovery app from http://4ext.net/. Install the apk and choose Online Install | Upgrade
It will ask if your phone is the HTC Desire GSM. Say yes, unless your phone isnt. (then go to the right forum )
Then you will see a list of all the different versions. Click on the latest one, and then install. It will tell you if it flashed succesfully, and then you can exit the app. To confirm it installed: turn off the phone, then turn it back on using power button + volume down. Then in bootloader select recovery. 4ext should come up instead of cwm.
Once you successfully have 4ext recovery installed look at this guide to see how to properly make the ext partition. Use the 4ext method and start at step [4].
Finally after you have done that, i would recommend doing a full wipe (everything except sd card) and reflashing the rom.
Many thanks, I'll try this. Good to know I couldn't screw anything up
Malk