Develop Bugs

Help Internal Space 0Byte / Data Partition missing

After i finally unbricked the phone a few hours ago, i had the problem that every rom made problems. Until i found out that the soft always claimed Internal Space 0 Byte !
which explained the problems downloading apps ect.
But after ~3h flashing other roms and doing factory resets im at a loss. different Kernels, different ROM's all claim internal space consists of 0 Byte
Somebody has any idea where im making the mistake ? I just got the Phone today.
Greetz
Chang

I digged a bit further and found that i cant mount the /data partition with cwm
"failed to find "userdata" partition to mount at "/data"
Hope it helps
Greetz
Chang
EDIT: I tried flashing the SE Original Firmware, with litte success. It was stuck on bootloop, after flashing doom kernel it at least booted but still Problem persists

Possibly a corrupt partition/cwm; use flashtool to flash a stock rom, reboot, then fastboot to boot your custom kernel

GChang said:
After i finally unbricked the phone a few hours ago, i had the problem that every rom made problems. Until i found out that the soft always claimed Internal Space 0 Byte !
which explained the problems downloading apps ect.
But after ~3h flashing other roms and doing factory resets im at a loss. different Kernels, different ROM's all claim internal space consists of 0 Byte
Somebody has any idea where im making the mistake ? I just got the Phone today.
Greetz
Chang
Click to expand...
Click to collapse
Flash stock rom using flashtool. I have this prob once and this solve it
Sent from my LT18i using xda premium

As i wrote in the second post i already did that with no success whatsoever
I uses Busybox to look at the partitions and got this:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 175880 76 175804 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
tmpfs 175880 0 175880 0% /mnt/asec
tmpfs 175880 0 175880 0% /mnt/obb
/dev/block/mtdblock0 320000 230724 89276 72% /system
/dev/block/mtdblock2 103936 1160 102776 1% /cache
/dev/block/mtdblock1 6144 824 5320 13% /system/vendor
/dev/block/vold/179:1 1954560 1686592 267968 86% /mnt/sdcard
/dev/block/vold/179:1 1954560 1686592 267968 86% /mnt/secure/asec
tmpfs 0 0 0 0% /mnt/sdcard/.android_secure
This explains why i get error ^^ but i have no clue how to get it right (or how it should look ^^ just that a /data partition should be mentioned)
Greetz
Chang

Use fastboot to erase the partition then boot the kernel again;
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline

Just one Question
which partition should i erase?

use 'fastboot erase data' to wipe your data partition. Obviously you'll lose user data, just download/boot the kernel and restore apps/data with titanium or similar

Okay that didnt went as expected
Code:
erasing 'data'...
(bootloader) Erase of partition 'data' requested
FAILED (remote: Partition not found, or permission denied)
finished. total time: 0.002s

if the bootloader is definitely unlocked, i.e. you unlocked it yourself, then there should be no permission errors, so that implies the partition is damaged/corrupted. In that case you could try re-locking your bootloader and use pc companion to repair the phone. Otherwise, check here and if needs be contact Alejandrissimo.

So relocking and repairing via Companion worked. Phone is running and Data partition is back. now lets hope i get the rom running ^^
THX !!!
Greetz
Chang

[Q] {URGENT} SDCard won't mount or format!

Hello, this is my first post but been seeing lot of threads here with lot of help, so I thank you all before you start helping me.
I have my HTC One X, tried to update to Jelly Bean using Dragon's ROM, all went fine but the phone got stuck on HTC logo.
Since that I can only start on recovery (ClockWork Mod 5.8.4.0), HBOOT (0.94) or fastboot.
There is no way I can access the SDCard from recovery to flash the rom.
I tried factory reset with no luck, wipe cache, wipe data.../factory reset. all with no luck! Every time I try to format my sdcard it says:
"Formatting /sdcard/.android_secure..."
"Error mounting /sdcard/.android_secure!"
"Skipping format..."
If I try with "mounts and storage" then "format sdcard":
"Formatting sdcard..."
"Error mounting /sdcard!"
I must say that I can use "Mount USB storage", did format with FAT32 on Windows & Mac, no luck. Also tried using parted with adb shell, formatting on ext2, but no luck.
Here is my "recovery.fstab":
~ # cat /etc/recovery.fstab
# mount point fstype device [device2]
# /recovery emmc recovery
# /boot emmc boot
# /system ext4 system
# /cache ext4 cache
# /misc emmc misc
# /sdcard vfat /dev/block/sda1 /dev/block/sda
# /internal_sdcard vfat /dev/block/mmcblk0p14
# /data ext4 userdata
# /devlog ext4 devlog
/recovery emmc /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p4
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p15
/sdcard vfat /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/misc emmc /dev/block/mmcblk0p17
------------
And here my fstab:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p15 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p14 /sdcard vfat rw
---------------
There is no way that ClockWork Mod can read my internal card for installing any zip. Any help would be really appreciated, even I would pay if necessary.
Thanks in advance for all the great work you guys do, and hope to get my phone back working!

If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app

TToivanen said:
If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...

poloivan said:
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...
Click to expand...
Click to collapse
Someone could please tell me how do I restore my phone as it came?
I have downloaded a RUU, my version main is: version-main: 1.28.161.9
When I click the RUU it does nothing, someone please help?
Thanks.

You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app

TToivanen said:
You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you all.
I have fixed my phone running the correct RUU.
Right now I am using Android Revolution HD 9.8. How can I update my HBOOT to run Android Revolution HD 18.0?
Best regards.

Two choices: Use a JB RUU or flash the correct firmware for your cid.

Not enough free space on /system to apply patches

Just want to give everyone a heads up, when attempting to apply OTA updates to my Nexus 7 2013, I was getting the error: "Not enough free space on /system to apply patches". The error was showing up in the recovery log and I was really confused. I tried reflashing various versions, but still all OTA updates would fail with the same error.
TL;DR: Turns out it was the cache, read on for the fix.
I found the following in the OTA update script:
"apply_patch_space(56661556) || abort("Not enough free space on /system to apply patches.");"
So I assumed that I should have at least 56 MB free in "/system"
Doing df would show this:
Code:
f:\AndroidADT\sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 903.4M 56.0K 903.3M 4096
/sys/fs/cgroup 903.4M 12.0K 903.4M 4096
/mnt 903.4M 0.0K 903.4M 4096
/system 827.8M 819.5M [B]8.3M[/B] 4096
/cache 31.5M 4.2M 27.3M 4096
/data 26.4G 7.9G 18.5G 4096
/persist 14.5M 4.2M 10.2M 4096
/storage 903.4M 0.0K 903.4M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 26.4G 7.9G 18.5G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
I didn't, and I couldn't figure out why.
The answer was, after much searching, is that the error message is wrong.
I found this here (ok, so I can't post links, just Google for "edify_generator.py")
Code:
def CacheFreeSpaceCheck(self, amount):
"""Check that there's at least 'amount' space that can be made
available on [B]/cache[/B]."""
self.script.append(('apply_patch_space(%d) || abort("Not enough free space '
'on [B]/system[/B] to apply patches.");') % (amount,))
Notice that the comment talks about /cache, while the error is showing /system.
Turns out my /cache was formatted incorrectly. All I had to do was reboot into the bootloader and then format the cache.
Code:
adb reboot bootloader
...wait for bootloader to start...
fastboot format cache
I just wanted to post this somewhere because I've been Googling for a while now and I've seen others get this error with no solution.
Oh, and the reason why it got into this messed up state is because I did:
Code:
fastboot flash cache cache.img
This was using the official images from Google. So don't ever do that

When you say cache was formatted "incorrectly", had you converted it to f2fs or something?

Thank you very much AlexPi, I can finally receive OTAs and avoid the hassle of flashing a new image, specially now that they are releasing more images with minor bug fixes for the same Android version (there are now 3 images for 6.0.0). I had one OTA of only 2 MB in size and I didn't want to flash a new image just because of this minor change.
I just enter (stock) recovery mode and selected "wipe cache" and it worked just fine after that, so it wasn't even necessary any USB data cable to execute adb and fastboot commands.
By the way, the error message was indeed wrong and it was already fixed.

Thanks. I also flashed the cache partition because I remember that it was effectively the same as wiping the cache. I guess that is not correct.

Help with /dev/block/mmcblkxxx (HTC Desire 816)

The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?

jacobjake683 said:
The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?
Click to expand...
Click to collapse
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.

uhm said:
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.
Click to expand...
Click to collapse
Sorry, but I do not have the file anymore due to the fact that I have gone through various hard drive formats and I don't seem to have it on the HTC anymore.

No problem. Thanks for your reply.

BRICKED? I would pay for quick fix if there is any..

Hello.
I bought an M9, that is stuck on bootloader, but also can boot to recovery, willing to fix it, but haven't checked recovery before paying and this is what I got:
wiping, formatting, adb sideload error - unable to mount /data, /cache/, /system and it shows that cache is 0mb, ok this is one is maybe ok, but system is 0mb, data 0mb, android secure 0mb. I'm using twrp v2.8.7.0, tried flashing stock recovery or other version though fastboot, no errors, but recovery won't change and boots to same twrp recovery.
Tried to fix this using corrupted data partition fix method > http://android-revolution-hd.blogspot.lt/2013/10/fix-data-htc-one.html
but this is what I got:
C:\adb>adb push mkfs.ext4 /tmp
2604 KB/s (3537143 bytes in 1.326s)
C:\adb>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32 inodes, 64 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
32 inodes per group
Writing inode tables: done
Filesystem too small for a journal
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n
Click to expand...
Click to collapse
I don't think it should be 32 inodes, 64 blocks, same as others in bold.
I don't know what to do, if someone could help me fix this I could transfer to PP let's say 20$, as, in my opinion, this problem could take some time to sort out and at least I would be lazy to help someone that much.

That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.

shivadow said:
That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you, good to know that I don't need to play around with it anymore as it won't help. What about M9 Sprint parts, are they interchangeable with 0PJA100? I know that on other models there might be slight difference (comparing to Sprint) in form, even specs, but in M9 they look, at least, same.

Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.

shivadow said:
Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.
Click to expand...
Click to collapse
Got it. Bought wrong item on Ebay and though about miracle that it would work, thank god seller noticed my message about canceling order before shipping it.