Hello.
So I was planning on completely wiping my phone and updating to a whole new rom.
I resized my ext3 and linux-swap partitions using parted in recovery.
Then I was planning on wiping my ext3 clean, so I used the following:
mount -o rw /dev/block/mmcblk0p2
Click to expand...
Click to collapse
I thought that this would simply clear the partition, but it did some crazy stuff deleting the partition I think.
This rendered my SD Card pretty much dead. I could no longer access parted through recovery, unless I typed "parted /dev/block/mmcblk0", but it wouldn't load normally, saying "No device found"
Anyways, I figured I'd just reformat the SD Card by removing it and using a micro sd to SD USB adapter and formatting, but the card does not show up on my computer, not even on Paragon Partition Manager... weird
Did I kill my 8gb micro sd? Thanks for any help you can offer!
Related
after searching, i found that the solution to the 'System UID's inconsistent' issue is to reformat the ext2 partition on the SD card.
But how do i do that. I tried removing the SD card and putting it in a card reader, but Paragon doesn't recognize the drive that way.
If i let it be in the phone and connect the phone via USB to my PC, Paragon recognizes it, and when i click on Format Partition option and point it to the SD card drive, it starts the format and then asks to reboot the PC. When it reboots, the phone reboots as well. My PC comes back and Paragon tries to continue the reformat (but the phone is not yet up), so Paragon fails with an error 'Invalid partition id'.
What the heck am I doing wrong?
Thanks in advance,
KG
kgdg said:
after searching, i found that the solution to the 'System UID's inconsistent' issue is to reformat the ext2 partition on the SD card.
But how do i do that. I tried removing the SD card and putting it in a card reader, but Paragon doesn't recognize the drive that way.
If i let it be in the phone and connect the phone via USB to my PC, Paragon recognizes it, and when i click on Format Partition option and point it to the SD card drive, it starts the format and then asks to reboot the PC. When it reboots, the phone reboots as well. My PC comes back and Paragon tries to continue the reformat (but the phone is not yet up), so Paragon fails with an error 'Invalid partition id'.
What the heck am I doing wrong?
Thanks in advance,
KG
Click to expand...
Click to collapse
if you are installing some different update like going from rc33 rc9 or whatever to dev phone/haykuro/or such you need to wipe...
I have the same problem, and wiping doesn't do squat. Can't use my phone now...
The easiest way to partition your card is to download a live ubuntu cd and use the partition editor included on the cd.
This happened to me when I had /data/data on the ext2 partition using the Symlink method for Apps2SD.
http://forum.xda-developers.com/showthread.php?t=512057&highlight=System+UID
Basically, all I did was move the /data/data back to the internal memory...
rm /data/data
busybox cp -a /system/sd/data /data
rm -r /system/sd/data /data
reboot
Had a couple of stale NFS file errors, so I could not really delete the /data directory from the /system/sd. Ended up reformatting the partition to go with a different Apps2SD method.
Used Paragon as described above and everything worked fine for me.
Vermithrax
I tredged past it. I just redid my A2SD and then ran the optimizer (I'm on Hero btw) and it seems to be working fine and speedy.
Probably the cleanest solution HERE
Okay so I'm pretty sure my SD card got fried (or damaged) last night.
The notification of "Damaged SD card" kept on showing up.
I tried running the repair file systems from CM recovery 1.4, all variations of rebooting, powering down, removing the SD card and all that to help 'fix' my problem.
I also went into settings to see if i have the option to mount and format the SD, but shows unavailable. Also SD secondary is unavailable as well.
So for sure my SD card is fried..... i think lol.
The thing that I am confused about is that I have apps2sd and try to use the apps that I know are installed on my SD card, I'm still able to access and use them, even though my SD card is damaged. I tried rebooting without the SD card inserted and I get FC's galore.
So does that mean my FAT32 partition is damaged and not my EXT partition?
How do I go about to remedy this?
Do I go ahead and click the on the notification to format my SD card?
Then it'll format my FAT32 partition and not my EXT partition?
Or is that totally wrong?
Confused and in need of some guidance. Thanks.
mrcrs said:
So does that mean my FAT32 partition is damaged and not my EXT partition?
.
Click to expand...
Click to collapse
Spot on
Format your card. If you use Linux, you can back up your apps, but you'll have to format and then re-install the EXT2 partition.
Basically, the FAT32 partition got corrupted. Anytime you actually see anything about the SD card on the phone itself, it's always the FAT32 partition.
hey there i had that same problem all i did was resize my fat32 partition
i used GNU parted so go to console and type
Code:
parted /dev/block/mmcblk0
now type
Code:
print
this displays the sd cards size in MB write down the max memory
now type
Code:
resize
it will ask what partition number type 1 it will the ask for a start size just type 0 if it errors saying couldnt write 0 but can write 8192B just say yes and for the end size type 1MB less than your max
Example for my 8gig card
Code:
resize
1
8192B
7965 - change to 7964
this will bring up a error saying the filesystem is damaged do you want to fix say yes
then type
Code:
quit
then
Code:
upgrade_fs
and that should do it
forgot to add your going to have to delete your ext partition FIRST! for that type
Code:
rm 2
i can load a hero rom on my g1 and flash it, but the phone says the sd card has been removed after the rom loads. also card reader says the sd card is write protected and when i go to settings it gives me greyed out area in the mount and available space areas. tried alot of things on the forum but none have worked so far. any ideas or is the card dead.
Boot to recovery, go to console (you have cyan1.4?) and issue this command:
Code:
parted /dev/block/mmcblk0 print
Post what it says.
Your card reader, what kind is it and what OS are you using. You aren't using an SD adapter with a write protect switch on it are you?
you may need to reformat your sd card and repartition it. dont use your card reader just mount if from the phone. you DO have a mini usb right? if not... you may have to reformat it on you phone. but all of your apps will be gone. if you dont have one, go out and buy one. they shouldnt cost more than...5 bucks.
1 512b 3420mb 3420mb primary fat32
2 3420mb 3932mb 512mb primary ext3
3 3932mb 3964 32.0mb primary linux-swap (v1)
4 3965mb 3973mb 8225kb primary linux-swap(v1)
whoa why do you have 2 linux swaps? you only need one....
thanks for all the help, what do i do now.some detailed instructions would be very good.
follow this tutorial on how to partition your sd card. your gonna have to reformat it to fat32 before. scroll down to the part where it says time to partition your sd card.
http://forums.t-mobile.com/tmbl/boa...roidDev&message.id=7674&query.id=130222#M7674
also when loading a hero rom it needs a clear ext2/3 to boot properly.
disk is write protected thats what i get when i put it in a card reader and try reformatting
long story short
i formatted 4gb card using recovery all fine
i updated ext2 to ext3 and the battery fell out
sd card not working
i can only format the card via recovery mount usb and disk management
it says unallocated so i format simple partiton select fat32 it formats fine
i can access it and add a file to it
then...
i reboot phone and sd card needs formatting again even booting back to recovery go to disk management it says unallocated again
i've used many tools sd formatters 'DISKPART' 'testdisk-6.11.3.win'
PTEDIT32
i have an image of what the sd card says
any ideas
Have you tried partitioning directly from recovery via parted?
Code:
parted /dev/block/mmcblk0
yes ive tried that and i get bad superblocks
sitimber said:
long story short
i formatted 4gb card using recovery all fine
i updated ext2 to ext3 and the battery fell out
sd card not working
i can only format the card via recovery mount usb and disk management
it says unallocated so i format simple partiton select fat32 it formats fine
i can access it and add a file to it
then...
i reboot phone and sd card needs formatting again even booting back to recovery go to disk management it says unallocated again
i've used many tools sd formatters 'DISKPART' 'testdisk-6.11.3.win'
PTEDIT32
i have an image of what the sd card says
any ideas
Click to expand...
Click to collapse
how did you format the card in recovery?
usb mount then windows management console it says unallocated raw
right clicked then selected simple volume then fat32 all works fine but reboot phone or take card out of phone put it back to phone(get unalocated raw) or reader(get nothing)
damn thing
I had an idea this minute
if we are using images with a size of 1,7GB or what else... why aren't we using some tools like resize_reiserfs and so on to repartition the Internal SD and creating a new partition with native yaffs2 or ext4 on it?
I dont't really know where our ext2 images are laying but if this could be possible it should be much faster right?
That's the thing - it won't be faster. The internal SD card is pretty slow. That's why the original lagfix used a repartitioned external SD card..
r3loaded2010 said:
That's the thing - it won't be faster. The internal SD card is pretty slow. That's why the original lagfix used a repartitioned external SD card..
Click to expand...
Click to collapse
Actually, it IS faster... That's why the newer lag fix uses an image on the internal SD card
I'm also wondering why nobody's trying to mount the internal SD with ext or yaffs2 instead of rfs...
EDIT : some answers : http://forum.xda-developers.com/showthread.php?t=750663
That's right !!!
We are using a mounted image with a filesystem laying on a native filesystem.
The reason why we aren't using the whole internal SD card with yaffs2 or ext4... is we cannot partition the whole internal SD card and copy our files afterwards.
BUT... we are able to compile some tools like "fdisk", "resize_[filesystem]" for ARM to use them direcly on the system for resizing (smaller) -> creating a new one -> and format it with yaffs2 for example.
After that we have the ability to use this partition like the ones in all other lagfixes mounting, symlinking...
That's the Idea
DasLeo said:
That's right !!!
We are using a mounted image with a filesystem laying on a native filesystem.
The reason why we aren't using the whole internal SD card with yaffs2 or ext4... is we cannot partition the whole internal SD card and copy our files afterwards.
BUT... we are able to compile some tools like "fdisk", "resize_[filesystem]" for ARM to use them direcly on the system for resizing (smaller) -> creating a new one -> and format it with yaffs2 for example.
After that we have the ability to use this partition like the ones in all other lagfixes mounting, symlinking...
That's the Idea
Click to expand...
Click to collapse
Did you read what's already been written in this thread: http://forum.xda-developers.com/showthread.php?p=7739573 ??
It's been tried by mimocan already, but didn't give a better result. Please do not start new threads on topics that's already been discussed elsewhere.
okay then close this