Develop Bugs

[Q] SD card problem...

Hi, I've just received a 16Gb Kingston SD card (Class 4), and I immediately put it into my phone, and mounted it in recovery, then used GPart to partition it into:
Fat32 (13.5Gb)|1Gb EXT4|300mb EXT4|100mb swap
And I've come to flash a new ROM, and in recovery (CWM-AlphaRev Recovery v2.5.1.8) when I go to install a zip from SD card, then go to choose the zip, I get an error of:
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard"
Anybody know the problem?
Oh, also, the fat32 partition shows up in windows when it's mounted, so it's partitioned OK...

SD brick - I had the same yesterday... But it works!
http://forum.xda-developers.com/showthread.php?t=691639

Rogi_tcz said:
SD brick - I had the same yesterday... But it works!
http://forum.xda-developers.com/showthread.php?t=691639
Click to expand...
Click to collapse
Is this the same? My sd card is mountable from recovery, but it's just not readable by recovery...

cgmorris89 said:
Is this the same? My sd card is mountable from recovery, but it's just not readable by recovery...
Click to expand...
Click to collapse
Yes, I had exactly the same issue. SD card not readable by recovery and usb, only from card reader.

OK thanks I'll take a look

Rogi_tcz said:
Yes, I had exactly the same issue. SD card not readable by recovery and usb, only from card reader.
Click to expand...
Click to collapse
Wait, my card IS readable by USB, just not recovery. I've not tried it in a card reader...

At first. I had the same like below after trying to restore backup from Amon recovery.
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard"
My PC didn't recognize my SD by USB toggle in recovery but it worked by card reader in my PC. After fastboot commands again became visible by recovery, but not by USB toggle or normal mode with Android working. After restore my backup with working recovery I made the rest of the steps from tutorial and now it's fully functional again.

which fastboot command did you use?
fastboot oem enableqxdm 0 ?
I imagine I'll only need to do the "making it visible in recovery" part as it's visible by USB already

Yes, I used "fastboot oem enableqxdm 0" in fastboot mode.

I'm trying it now and I'm down to step 3, and in cmd.exe I'm getting "The system cannot find the path specified."

Fastboot command it's not working? Maybe you need to install this http://www.4shared.com/file/7YyQXBE6/adbfastboot.html and extract to \windows\system32\. Then start your phone in fastboot mode (back + power). I have installed SDK on C:/SDK/tools. In cmd.exe:
cd C:/SDK/tools
After that commands should work.

No, fastboot is working, as I previously used
fastboot oem enableqxdm 0
and 'fastboot oem boot' which gave me my CID
I then edited the mtd0.img with my CID in my hex editor, and attempted to move the flash_image and mtd0.img with the following command
'cat /sdcard/flash_image > /data/flash_image'
which is when I get the error

Below commands work for me:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Maybe you missed "su". If still not work take a look for help in original topic maybe. I used tutorial from our polish board (more detailed). You can translate if you want.
http://bit.ly/fliTad

I wasn't having any luck whatsoever with that unfortunately...so I partitioned it through recovery (advanced>partition SD card) with a 1024mb EXT partition and 0mb swap, and recovery now recognises the SD card...we'll see how it goes

mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument

Any ideas?

lonelliott said:
Any ideas?
Click to expand...
Click to collapse
Which command did you send?
Sent from my Kindle Fire using Tapatalk

are you logged in on adb? Try to type "exit" then "adb shell".
You don't have to mount your sdcard after using adb shell. (at least I didn't have to on my mac)

For some reason it will not mount my sdcard, at all. I can adb shell onto it, but when I try to run the update.zip from it, I get an error saying it cannot mount the sd card.

I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot

I have the same problem. Can't mount sdcard.
I'm doing your fix step by step in Win XP. I formatted partition into Fat32. Though it didn't allow me to select block size. It just has one option "Default allocation size". Capacity is 200MB.
After that I'm trying to tap on the Mount SDCard option, but it wouldn't change to [X] Unmount SDCard. So it wouldn't mount and I'm back to the problem.
Any ideas on what could go wrong?

I finally figured it out!
The key thing is that sdcard HAS to be formatted in a certain way - FAT32 (and presumingly block size 4096 as mentioned above).
Brief history:
I followed the above instruction and formatted sdcard on a mac with Disk Utility. That didn't work. It still wouldn't mount. I tried to do the same thing in Windows XP. No luck. It wouldn't mount with the same "Invalid argument" error.
I figured that I should try and format sdcard right from the TWRP shell. I deleted and recreated partition with fdisk. Then I learned that TWRP 2 comes with pretty old busybox which doesn't have mkfs or mkfs.vfat to format the partition to FAT 32. So took the busybox binary from the pre-rooted 6.2.1 and pushed it to the KF. And I used mkfs.vfat.
Instructions:
Download and unzip pre-rooted 6.2.1..
Rename busybox to busybox1 (just not to mess up existing version) and copy it to your KF.
Code:
adb push /path_to_unzipped_6.2.1/system/xbin/busybox1 /sbin
Go to shell:
Code:
adb shell
~ # chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
~ # mount sdcard
There you go! Now your sdcard is mounted. And you can proceed with the instruction above.

death2all110, thanks for the post. This solved my issues....beer money sent!
Brad

Thanks Dmitry_G, That was exactly what I needed!

You guys are amazing and you have brought my Kindle back from the dead. Thank you sincerely.

i need someone to help me with this please i'm a newbie with the same problem

Same to me, but i got error, help me!
I follow your guide, but have error, pls help!!!
C:\>adb shell
~ # chmod 755 /sbin/busybox1
chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
busybox1 mkfs.vfat /dev/block/mmcblk0p12
mkfs.vfat: can't open '/dev/block/mmcblk0p12': No such file or directory
~ # ^

You try copy mmcblk0p12 file from another KF to your KF.
This error by mmcblk0p12 deleted

Death, I don't know if you will see this reply because this thread is so old but if you do,THANK YOU!!!!!! THANK YOU!!! THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I had messed with kfu, unbrick utility and many other methods to try to unbrick my kindle and your guide was exactly what I needed.

death2all110 said:
I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot
Click to expand...
Click to collapse
THANK YOU! It worked! I was about to trash this thing.

Damaged SD card... Can't mount in recovery

I erased my sd card in an attempt to get back the 8GB of storage that was missing . I successfully copied everything back to the sd but once I unmounted and turned off usb mode I got an error saying "SD card damaged. You may have to reformat it."
Now when I connect to my computer it recognizes the HOX but not the SD. Same in recovery, I get a can't mount SD error message. Can't format from the phone either.
The phone is working fine with the exception of the borked sd card. Anyone have any ideas on how I can fix it. I think that I could format the sd partition by using busybox but I don't know which partition in dev/block points to the sd.
I'm using CM9 btw, any help would be appreciated. Thanks in advance!

kchino said:
I erased my sd card in an attempt to get back the 8GB of storage that was missing . I successfully copied everything back to the sd but once I unmounted and turned off usb mode I got an error saying "SD card damaged. You may have to reformat it."
Now when I connect to my computer it recognizes the HOX but not the SD. Same in recovery, I get a can't mount SD error message. Can't format from the phone either.
The phone is working fine with the exception of the borked sd card. Anyone have any ideas on how I can fix it. I think that I could format the sd partition by using busybox but I don't know which partition in dev/block points to the sd.
I'm using CM9 btw, any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
Settings > Storage > Erase phone storage?

If you are not worried about reintalling applications again and backed up your data, Do a factory reset by going to boot screen.

cjm1979 said:
Settings > Storage > Erase phone storage?
Click to expand...
Click to collapse
I've tried that, the sd isn't mounted so nothing shows up under storage. Just the 2GB of internal memory.

kchino said:
I've tried that, the sd isn't mounted so nothing shows up under storage. Just the 2GB of internal memory.
Click to expand...
Click to collapse
Flash the RUU MAYBE
Sent from my HTC One X using xda premium

skr_xd said:
If you are not worried about reintalling applications again and backed up your data, Do a factory reset by going to boot screen.
Click to expand...
Click to collapse
Tried that as well, nice and clean but the sd card message still appears. Thanks for the suggestions.

matmar said:
Flash the RUU MAYBE
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was hoping that would be my last resort. I found this thread from the flyer forum.
Only problem is I don't know which partition points to the sd.
Someone with a working operation system on a flyer was able to format the sd from the phone using busybox using this command:
mkfs.vfat /dev/block/mmcblk0p33
Maybe a dev with knowledge of the filesystem could point me to where the the sd partition lives under block and I could try the same thing?

kchino said:
I was hoping that would be my last resort. I found this thread from the flyer forum.
Only problem is I don't know which partition points to the sd.
Someone with a working operation system on a flyer was able to format the sd from the phone using busybox using this command:
mkfs.vfat /dev/block/mmcblk0p33
Maybe a dev with knowledge of the filesystem could point me to where the the sd partition lives under block and I could try the same thing?
Click to expand...
Click to collapse
they go from mmcblk0p1 - 20 not sure which is the sd sorry

kchino said:
I was hoping that would be my last resort. I found this thread from the flyer forum.
Only problem is I don't know which partition points to the sd.
Someone with a working operation system on a flyer was able to format the sd from the phone using busybox using this command:
mkfs.vfat /dev/block/mmcblk0p33
Maybe a dev with knowledge of the filesystem could point me to where the the sd partition lives under block and I could try the same thing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1551581

skr_xd said:
http://forum.xda-developers.com/showthread.php?t=1551581
Click to expand...
Click to collapse
Thank you! Well, I tried:
su
#mkfs.vfat /dev/block/mmcblk0p14 (it returned)
lseek:Value too large for defined value type
off to research more...

I'm stuck any help?
1|[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
[email protected]:/ # busybox mkfs.vfat /dev/block/mmcblk0p14
mkfs.vfat: lseek: Value too large for defined data type

I was finally able to reformat the sd partition using the instructions in the thread I shared earlier. I had to push another version of busybox to data/local/tmp, change permissions and run the mkfs.vfat to get it to work. Thanks to those that gave suggestions back in business!

try doing a factory reset in the bootloader. worked for me when nothing else would after my sd got corrupted and would not mount to PC. corruption in my case occurred by leaving the charger connected during an OTA.
Edit : sorry I see you have already sorted it !

Hello
kchino said:
I was finally able to reformat the sd partition using the instructions in the thread I shared earlier. I had to push another version of busybox to data/local/tmp, change permissions and run the mkfs.vfat to get it to work. Thanks to those that gave suggestions back in business!
Click to expand...
Click to collapse
Hey friend stuck in the same situation as you. Any help would be appreciated. Im lost as to how you took the steps to get your phone to mount again. Which busybox did u use and how did you push that script?!

kchino said:
I was hoping that would be my last resort. I found this thread from the flyer forum.
Only problem is I don't know which partition points to the sd.
Someone with a working operation system on a flyer was able to format the sd from the phone using busybox using this command:
mkfs.vfat /dev/block/mmcblk0p33
Maybe a dev with knowledge of the filesystem could point me to where the the sd partition lives under block and I could try the same thing?
Click to expand...
Click to collapse
Hey Packer, follow the steps in the thread I posted here. The SD partition for the HOX is /dev/block/mmcblk0p14 btw. It worked perfectly for me.

NOOB Status
kchino said:
Hey Packer, follow the steps in the thread I posted here. The SD partition for the HOX is /dev/block/mmcblk0p14 btw. It worked perfectly for me.
Click to expand...
Click to collapse
Brother please help I am a noob. What steps to take and how to go about this. I am very desperate and unlocked phone so no warranty. Idk how to enter that code and where. Or what to do with the /dev/block/mmcblk0p14 :/ any help would be appreciated pls?

Packer2058 said:
Brother please help I am a noob. What steps to take and how to go about this. I am very desperate and unlocked phone so no warranty. Idk how to enter that code and where. Or what to do with the /dev/block/mmcblk0p14 :/ any help would be appreciated pls?
Click to expand...
Click to collapse
Okay, no problem...
Look at this thread and make sure you have downloaded the sdk or another copy of adb and for mac. ADB and fastboot are the command line programs, you are going to use ADB to fix your phone. Look at this thread so you can use ADB and fastboot and are familiar with the commands you're gonna need to use.
Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. Quotes below are just used for emphasis.
1. Go into your fastboot/adb folder on your mac, you should see the file "adb" in the folder. You may need to put a "./" in front of your commands i.e. ./adb devices, or ./adb push to actually execute them... Connect your HOX to your mac with USB.
2. Open a terminal window, make sure that your term session is in the same folder that contains your adb files. You can type "ls" <enter> and you should see the adb files and any other SDK files listed. If not, in mac you can drag the icon from the the top of the finder window into your terminal and it will change to the appropriate directory for you.
3. Type ./adb devices <enter>. It should output the serial of your phone. If you don't see anything listed after ./adb devices command you probably are in wrong folder. When you see confirmation of you serial, move on...
4. The following steps are attributed to the user globatron (Thanks!) who I found the fix from on the flyer forums:
You're going to type or copy and paste the following commands to check and then reformat the partition.
./adb push busybox /data/local/tmp - (you should see okay at the end of the dialogue) This will move the busybox file to your phone needed to format.
Next type:
./adb shell - (then type su which will give you superuser if you don't have it already) your command prompt will change from the "$" to "#" don't type these.
$ su
Now just to check that the partition is still there type:
#cat /proc/partitions (you should see a list of 20 partitions, most importantly is this one)
179 14 26476544 mmcblk0p14
If you see the above line after you do your cat command go to the next steps.
Type the following or just copy and paste without the #:
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p14
That should do it. Disconnect from your computer and reboot.

THANK YOU SO FREAKING MUCH! I dont know how else to thank you! You gave my device new life, and gave me some peace of mind. I was close to trying to replace my phone; File a Claim and fulfill my warranty from SquareTrade. You have helped me so much my friend. Thank you once again. May karma be in your favor!

Packer2058 said:
THANK YOU SO FREAKING MUCH! I dont know how else to thank you! You gave my device new life, and gave me some peace of mind. I was close to trying to replace my phone; File a Claim and fulfill my warranty from SquareTrade. You have helped me so much my friend. Thank you once again. May karma be in your favor!
Click to expand...
Click to collapse
Cool, Glad it worked out. Thanks for the karma!

kchino said:
Okay, no problem...
Look at this thread and make sure you have downloaded the sdk or another copy of adb and for mac. ADB and fastboot are the command line programs, you are going to use ADB to fix your phone. Look at this thread so you can use ADB and fastboot and are familiar with the commands you're gonna need to use.
Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. Quotes below are just used for emphasis.
1. Go into your fastboot/adb folder on your mac, you should see the file "adb" in the folder. You may need to put a "./" in front of your commands i.e. ./adb devices, or ./adb push to actually execute them... Connect your HOX to your mac with USB.
2. Open a terminal window, make sure that your term session is in the same folder that contains your adb files. You can type "ls" <enter> and you should see the adb files and any other SDK files listed. If not, in mac you can drag the icon from the the top of the finder window into your terminal and it will change to the appropriate directory for you.
3. Type ./adb devices <enter>. It should output the serial of your phone. If you don't see anything listed after ./adb devices command you probably are in wrong folder. When you see confirmation of you serial, move on...
4. The following steps are attributed to the user globatron (Thanks!) who I found the fix from on the flyer forums:
You're going to type or copy and paste the following commands to check and then reformat the partition.
./adb push busybox /data/local/tmp - (you should see okay at the end of the dialogue) This will move the busybox file to your phone needed to format.
Next type:
./adb shell - (then type su which will give you superuser if you don't have it already) your command prompt will change from the "$" to "#" don't type these.
$ su
Now just to check that the partition is still there type:
#cat /proc/partitions (you should see a list of 20 partitions, most importantly is this one)
179 14 26476544 mmcblk0p14
If you see the above line after you do your cat command go to the next steps.
Type the following or just copy and paste without the #:
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p14
That should do it. Disconnect from your computer and reboot.
Click to expand...
Click to collapse
Hello
thank you for your instructions i have followed it exactly and i have an issue running these commands
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p14
it says not found. I have tried all different things and could not get his to work. What does the chmod 755 do?
Cheers for your help

[Q]: repartitioning hiccup [solved]

Ok, I posted this question in 2 other threads that had info on the process (will delete the posts when this one goes live), but no responses after a couple of days. One of them is old though.
I have TWRP 2.1.1 installed. ADB seems to be working normally. Superuser is working fine after booting to android. I'm running a custom ICS ROM (Energy); read that stock ROM can cause issues repartitioning.
I started with this How-to as it looked very straight forward.
I start throwing the commands at ADB and here's what I got for my efforts:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ # cd /data
cd /data
/data # ls
ls
/data #
decided to go ahead and check the mount command:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ #
and parted just for giggles:
Code:
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)
Ok, so that much worked. Now I tried to shrink 12 so I could double the size of 9. I want to get Switchme set up for his/her profiles and 500MB just isn't going to cut it.
That's when I hit a brick wall:
Code:
(parted) resize 12 2846 7690
resize 12 2846 7690
resize 12 2846 7690
Error: Unable to satisfy all constraints on the partition.
(parted)

One thing that jumps out at me right away is this:
Code:
adb shell
~ # su
su/sbin/sh: su: not found
It seems you are not actually rooted.
To check, enter:
Code:
adb shell
ls /system/xbin
If you don't see "su" in the list, then you don't have root permissions, which would probably prevent you from doing what you need to accomplish.

That's what I was wondering, but apps are able to ask for and receive root permission from within the ROM. SU does exist, just not where the shell is looking when in recovery.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /system/xbin
ls /system/xbin
ls: /system/xbin: No such file or directory
~ #
I did an ls /system/xbin from adb shell and from Terminal Emulator within Android and both returned a long list containing SU.

TWRP provides an unsecured (unsecure? insecure?) boot. Whatever the terminology, it gives you immediate access to root privileges. Apparently CWMR (which was used in the OP of the thread you used) does not and so that author had to use su. For TWRP, it's not necessary and not even available. You already have root privileges as indicated by the hash prompt.
I tried resizing my /sdcard partition and it worked fine with the command you tried. I'm not sure what's going on with your storage device that it wouldn't resize it for you. At first I thought it might be mounted, but your mount command shows otherwise and parted gave me a different error when I had it mounted.
I don't know if this is going to help you, but you might try giving it the "MB" suffix in your numbers....
Code:
resize 12 2846MB 7690MB
Maybe even try changing units to bytes and giving the resize command byte sized boundaries.
Code:
unit B
print
will show you the numbers in bytes and you'd have to use the "B" suffix as in the "MB" example above.
If none of that works, you can always remove and remake the partition. For example...
Code:
rm 12
mkpartfs primary fat32 <start> <end>
name 12 media
You'd obviously need to insert acceptable boundaries for the start and end into that command. It might even be easier to just remove all 9, 10, 11, and 12 and remake/rename them, but remember 9, 10, and 11 are ext4 filesystems so the above mkpartfs command needs to be tweaked accordingly.
One thing I noticed while I was experimenting with the partition table this morning... all of the existing partitions have been allocated in 128MB chunks. I have no idea if this affects performance. I'd imagine you'd only need to stick to the 512B sector sizes, but you might want to stay with those conventions if it's not too inconvenient for you.
If you mess up the partition table, you can always go back to fastboot mode in FFF and use the...
Code:
fastboot oem format
feature to bring your partition table back to stock.
Good luck.

Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I'd say that's a safe bet. Just be very careful about handling partitions 1 and 2 because those two are critical to getting anything to boot on your device. As long as you don't touch the xloader in partition 1 and have FFF installed in partition 2, you can rebuild the rest of it.... in theory. I only say "in theory" because I've never actually had to do it, but I don't see why it wouldn't work.
A couple of additional things I figured out after you put me to work with parted....
It looks like parted doesn't know how to make an ext4 filesystem, so mkpartfs balks if you tell it to make one. You'll have to use mkpart which just makes the partition, but not the filesystem. Then exit out of parted and use mke2fs, which despite its name knows how to make an ext4 filesystem. Like this for the cache partition...
Code:
mke2fs -T ext4 /dev/block/mmcblk0p11
The other thing is that parted sets a "msftres" flag on the fat32 filesystem it makes. The flag apparently is to tell the OS that it's reserved for Windows, or something like that. I didn't have a problem mounting in Linux and MacOS X, but the stuff I've read seems to indicate that older OS's have a problem with it. Unfortunately, the version of busybox on TWRP doesn't have a module to make a fat32 filesystem. I'm looking around to see how to get around that.
In any case, this should get you most of the way there. I'll followup if I find something out.

Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I have a IIgs sitting in the basement... but it's not a mac, it's an Apple ][.
Found the last piece...
Code:
/system/bin/newfs_msdos /dev/block/mmcblk0p12
will make a fat32 filesystem correctly. I think that's all you'll need.
EDIT: OK, I must have been half asleep when I posted the above. That binary is on the stock system software I had mounted. There's nothing on TWRP to create a fat32 filesystem correctly.

Yeah, ][e was my first computer that didn't crash at the drop of a keystroke. Had an Adam tape drive model, but it froze up constantly.
Sent from my TBolt with the XDA App using 1 opposable thumb

So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.

no device found
ProfEngr said:
So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.
Click to expand...
Click to collapse
I get
(parted)
Error: No device found
Retry/Cancel

[Q] Lost. SD partition? Can't install ROMs, soft brick

So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
Here's the solution.
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
1 Working recovery, basic knowledge of adb & the shell
2 Parted (download here)
3 stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!

babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder

Thant said:
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder
Click to expand...
Click to collapse
Initially on the first rom i remember doing so (still didn't work), but after that i did fail to do it for the other roms.

babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
hello babymatrix, i'm wondering if you were able to solve or find a solution to your issue. The reason i'm asking is because i'm on the same boat right now and looking for way to fix a similar issue as yours.
basically, i got a phone with a broken partition like yours. I can still go to recovery but you'll see this message and cannot mount system. I also cannot go into fastboot mode (it hangs when i do a power+vol down)
E: failed to mount block devices /dev/block/mmcblk1p1
E: remount block devices /dev/block/mmcblk1
E: failed to mount /sdcard (No such file or directory)
From searching the net, i figured there's something wrong with the partitioning of the phone. I managed to do adb shell and i could see there's a folder sdcard.
nway, if you've managed to find a solution for your issues, i hope if you could share. thanks.