Develop Bugs

113MB of bad blocks on /data...can i be helped???

Edit: summary of what ive tried and failed with.
Wipe all userdata from cwm and amon recovery ... no effect.
erase_image from cwm ... no effect.
fastboot erase ... no effect.
fastboot erase -w ... no effect.
RUU ... no effect.
cat zero to mtd ... no effect.
dd zero to mtd ... no effect.
flash_image (image edited with hex editor to contain only zero's) ... no effect.
fastboot oem task 28 ... no effect.
fastboot oem task 29 ... no effect.
fastboot flash hboot (different partition tables) ... no effect.
I'm out of ideas.
Original post:
Even after clearing all userdata from recovery and erasing userdata from fastboot i am missing over 100mb from /data, but there are no files there taking up the space.
How can i reclaim this space, is it corrupted??? How do i check for (and fix) a corrupt filesystem on android?
I'm thinking of flashing a new HBOOT, oxygen table, but if it's corrupt will it screw it up or fix it?
Below was done from recovery and fastboot and shows the problem, look at how much space is in use on data after wipe.
Code:
[email protected]:~$ sudo su
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.1M 93.9M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock5 197.6M 187.5M 10.2M 95% /data
/dev/block/mmcblk0p1 3.7G 3.4G 302.9M 92% /sdcard
[B]/ # #wipe all userdata from recovery (amonra 2.0.0)[/B]
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # reboot bootloader
[B][email protected]:/home/mercianary# fastboot erase userdata
erasing 'userdata'... OKAY[/B]
[email protected]:/home/mercianary# #into recovery again
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # ls /data
lost+found
/ # du /data
2 /data/lost+found
4 /data
I'm using
CM7
amonra recovery 2.0.0
N1 Boot table
Any help troubleshooting this would be great, thanks.

did you wipe the /data/ partition in mounts & storage in recovery? try that if not, also try flashing a stock ruu, it will revert and changes made to the MTD Partitions

that was the first thing i tried, no luck. it erased fine but space was still missing
I dont particularly want to flash a RUU or another HBOOT untill i know what's wrong because if there's 100mb of bad nand on my phone i can imagine flashing a RUU or HBOOT going very wrong and leaving me with a very pretty paperweight.

I tried flashing some different hboots, problem still there, it just moves round a bit....
on the original boot table the space is missing on system and data..about 10mb or 20mb on system, the rest on data.
on oxygen and n1 boot table its just missing on data.
I cant seem to reclaim this space
anyone know how to check the disk for errors?

thats bad news, sounds like you may have some corrupt blocks

AndroHero said:
thats bad news, sounds like you may have some corrupt blocks
Click to expand...
Click to collapse
just a few, only 897 of them the phone is still working, so i suppose i'm kinda lucky.
I think i may have screwed it up a few weeks ago when i was messing around with cat, dd, fastboot and flash_image. I remember when i finished messing around i tried to restore my nand backup back on it but it failed, looking back it must have been because it didnt fit anymore due to the bad blocks. This must have been when the corruption occured.
Is it normal to have this many bad blocks? i've never seen more than a few, i'm hoping they aren't actually bad and it just thinks they are because of something stupid i did, is there anything i can do to remove the bad block flag (if there is one???) and then try again?
Code:
/sdcard/badblock # flash_image userdata mtd5.img
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00020000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00040000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00060000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00080000 (errno=0)
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
...
edited because it put the post over the 30,000 character limit!
...
mtd: not writing bad block at 0x0c520000
mtd: not writing bad block at 0x0c540000
mtd: not writing bad block at 0x0c560000
mtd: not writing bad block at 0x0c580000
error writing userdata: No space left on device
/sdcard/badblock #

That's way too high. NAND blocks usually fail at once and in the same area but not that many at once unless it be software error or a major stressor placed on them. It may be faulty bad block management defuncting those cells. If you could somehow find a way to Secure Erase the NAND, it could help. NAND cells sometimes work fine after this and cell state becomes reset so all those marked bad will be recycled back in use to test. The reason why they can sometimes spring back to perfect retention after a SE is academically quite known.
------------------------------
- Sent via HTC Desire -

I guess that you should use an RUU as it should format nand. If it does not the update wikl fail which mesns that your bad block could never be recoverd. Keep in mind to use RUU and not a PB.img i believe it is safer as long as it comed to bricking the phone. I know that some pvt 1 boards had some bad blocks on nands but never so muny( if it is a pvt1) . Regards
Sent from my LeeDroided Desire HD

I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun

mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
mercianary said:
I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun
Click to expand...
Click to collapse

mariosraptor said:
mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
Click to expand...
Click to collapse
That's what I was planning to do but I decided against it for several reasons.
I'm not feeling lucky, I dont think I will get away with it this time.
With the nature of the problem I can imagine whoever gets their hands on it at HTC will look into what's happened and discover my warranty's void...paranoid I know.
It doesn't help that there is no RUU for orange UK branded desires, I have to use a dodgy method to unroot (restoring an old backup, removing superuser and su then updating OTA.)
I'm happy with the way it is at the moment, who knows, I might drop it under my car at some point in the near future

anyone know anything about performing a low level format or clearing the bad block map so i can start a fresh???
PS...turns out the stock orange rom doesn't even fit on /system because its missing 10MB of space...damn you orange bloatware...damn you to hell!!!
PPS...Bump.

Get in contact with a dev. I am sure they will help you out to access and do a secure wipe on your memory. Way beyond me for sure

unified storage setup on re-partitioned FP1

In reference to the new storage configuration scheme mentioned in this thread
http://forum.xda-developers.com/showpost.php?p=54537828&postcount=677
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.

Donat.Callens said:
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.
Click to expand...
Click to collapse
Used that method, worked like a charm. Since I'm using AOSP and there have been zero updates for it, I probably won't reformat unless Fairphone starts updating their AOSP OS as well. Will update this post when/if they do.

to repartition or not to repartition
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?

Donat.Callens said:
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?
Click to expand...
Click to collapse
Hello, The partition upgrader rewrites MBR/EBR1/EBR2 *after* performing the update to the /system partition. It assumes the /system partition is not altered. I have not tried modifying the partition layout using the methods discussed on this forum (modifying the extended master boot record). As a result of the upgrade EBR2 is no longer used but remains present. MBR is not altered so only EBR2 and the PMT partition are modified before the cache and data partition are formatted. If only /data and the FAT partition are modified you should be fine. These are at the "end" of the disk.
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone

download the repartitioning tool
_keesj said:
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Click to expand...
Click to collapse
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
This site refers to another download links to the same file:
http://www.china-devices.com/Thread-Tool-App-for-repartitioning-MTK-6589-Memory
As sear for Meteos MTK6589 will pop up many sites where it is to be found.

Donat.Callens said:
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
Click to expand...
Click to collapse
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1

Donat.Callens said:
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1
Click to expand...
Click to collapse
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.

it did not seem to work for me
_keesj said:
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.
Click to expand...
Click to collapse
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.

Donat.Callens said:
I will post the output of these commands here in my next post: df and mount.
Click to expand...
Click to collapse
$ df
Filesystem Size Used Free Blksize
/dev 487M 52K 487M 4096
/mnt/secure 487M 0K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/asec/com.camsam.plus-1 22M 19M 2M 4096
/mnt/asec/com.nuance.swype.dtc-1 36M 32M 3M 4096
/mnt/asec/com.koushikdutta.backup.license-1 1M 280K 1M 4096
/mnt/asec/ginlemon.flowerpro-1 5M 3M 1M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 351M 288M 4096
/data 3G 1G 2G 4096
/cache 124M 4M 119M 4096
/mnt/cd-rom 1M 1M 0K 2048
/protect_f 8M 4M 4M 4096
/protect_s 8M 4M 4M 4096
/storage/emulated 487M 0K 487M 4096
/storage/sdcard1 7G 6G 425M 32768
/storage/emulated/0 3G 1G 2G 4096
/storage/emulated/0/Android/obb 3G 1G 2G 4096
/storage/emulated/legacy 3G 1G 2G 4096
/storage/emulated/legacy/Android/obb 3G 1G 2G 4096
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.camsam.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/ginlemon.flowerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Donat.Callens said:
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.
Click to expand...
Click to collapse
Can you please execute the following (as root e.g. adb shell ; su) and paste the result?
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?

_keesj said:
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?
Click to expand...
Click to collapse
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0

Donat.Callens said:
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0
Click to expand...
Click to collapse
Only the first part of the uprade has happend. The first part replaces the root file system, recovery and some other system partitions.
The second part of the upgrade is launched on the next boot in /system/etc/install-recovery.sh (itself copied from /system/bin/fp1_partition_upgrade ).
It checks if the partition upgrade has happened and if not perform the upgrade.
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
/system/bin/fp1_partition_upgrade
Code:
#!/system/bin/sh
#
# Upgrade the partition layout from FP1 to FP1U
#
#
# dump pmt to see if the upgrade has happend
if /system/bin/fp_part -r -f /dev/pmt | grep FAT > /dev/null
then
echo Starting partition upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
echo "--wipe_data" > /cache/recovery/command
reboot recovery
fi

logcat
_keesj said:
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
Click to expand...
Click to collapse
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long

Donat.Callens said:
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long
Click to expand...
Click to collapse
Can you please also provide the dmesg output, possibly using a private message? (the logcat does contains the info I am looking for an might contain private data)

custom recovery might be the source of the problem
_keesj said:
Donat.Callens said:
_keesj said:
The partition upgrdate is not happening, there should be lines containins SD_UPGRADE something like
Click to expand...
Click to collapse
could it be because I have a custom recovery installed?
Click to expand...
Click to collapse
This is an interesting idea.
-The sd_upgrade command is executed when not on the recovery so this is not probable.
-I think the recovery will also be replace back to "original" because we need a diifferent kernel.
Did you run the command and does the device reboot afterwards? A different recovery might not perform the factory reset?
Click to expand...
Click to collapse
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I get
ROM may flash stock recovery on boot. Fix?
Click to expand...
Click to collapse
I then reply
Yes - Disable recovery flash
Click to expand...
Click to collapse
I can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.

Donat.Callens said:
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I getI then replyI can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.
Click to expand...
Click to collapse
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.

_keesj said:
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.
Click to expand...
Click to collapse
I replied No to the question: ROM may flash stock recovery on boot. Fix?
This solved the issue. The installer completed and now my phone is back to factory default. I have 13.37 GB total space . I will restore my backups. Thank you for your support _keesj.
Please ensure user are informed they have to let the installer replace the existing custom recovery with the factory one for the partition upgrader to work correctly. You can always restore your custom recovery afterwards
I hereby confirm that, in my case, the partition upgrader worked with a modified partition scheme. For reference, I had changed the internal storage space to 4GB in the past.

Awesome guys!
This is why I like xda-developers and Fairphone and its community accompanied development so much. Not only I can follow the rapid conversations on problems and solutions that I could even run into, I also learn a lot about related techniques, background and the challenges in throwing a fair phone on the market.
I definitely appreciate the work of the xda developers, keejs and joemier - and of course all the others that stand behind that all. KUDOS!

But will all my apps still work, if I do backup the two partitions and then after the upgrade put everything on the one remaining partition? I guess quite a few apps might still "look" for their data on the no longer existing second partition, won't they?

Steps for "fiixing" your upgrade
Some user have repartitioned the partition of their FP1U using tool mentioned in on this forum. FP1U does not need this as the new layout is perfectly fine.
I think the following steps *should* work to get their phone back to "normal"
#get the partition upgrader
wget http://storage.googleapis.com/updat...G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#unzip it
unzip FP1_Fairphone_OS_1G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#attach your device to your pc and make sure adb works
#after that push the new partition layout to your device
adb push system/bin/fs_upgrade.bin /mnt/sdcard/
#the rest of the command need to run as root
adb shell
su.
# tell the kernel to perform the upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
#reboot and wipe the data
echo "--wipe_data" > /cache/recovery/command
reboot recovery

KF2 Soft brick - /data and /sdcard read-only

My mom has a Kindle 2nd Generation running 10.5.1 stock.
The other day, it started rebooting, but not in the traditional bootloop sense. The OS would load to the lock screen, you could swipe and use it (albeit sluggishly) for approximately 30 seconds before it rebooted again. So, it made it impossible to access the device via ADB.
I made a factory cable, accessed fastboot, and did the following:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
(if using a fastboot USB cable, swap to a normal USB cable before entering the next command)
fastboot -i 0x1949 oem recovery
Click to expand...
Click to collapse
This worked fine. I was able to get into recovery mode with TWRP and access ADB. I pulled all the data off the /sdcard partition. This was a big concern since my mom has been using this thing for a couple years now and she's collected quite a bit. Originally, my directive was to factory reset and reflash the stock firmware from Amazon: update-kindle-10.5.1_user_5174820.bin. It would be nice if they supplied a checksum, but they don't apparently.
Anyway, the more I thought about it, I thought I could clear some caches, uninstall some apks and that would resolve the issue without a new system image. Then I started to notice the problem:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 336.6M 136.0K 336.5M 0% /dev
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /data
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /sdcard
/dev/block/mmcblk0p12
639.8M 11.0M 628.8M 2% /cache
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p13 on /data type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p13 on /sdcard type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
~ #
Click to expand...
Click to collapse
Both /data and /sdcard are read-only. They also use the same block device. Maybe that's normal? I've already tried remounting the partitions read-write to no avail.
mount -o rw,remount /sdcard
mount -o rw,remount /data
Click to expand...
Click to collapse
Both commands execute as if they were accepted successfully (ala no output). However, rechecking mount's output, shows no change. It's still read-only.
I've tried sideloading in TWRP, but that resulted in a protocol fault. Also through TWRP, the factory reset succeeds, but actually does nothing. All of the data is still there. My other idea is to push the image onto the /cache partition (there's just enough room), and try to install that way, but I have a feeling that 1) won't work and 2) may exacerbate problems.
I'm stuck. Anyone have any ideas?

Solved
I was able to free the partitions.
fastboot -i 0x1949 erase userdata
Click to expand...
Click to collapse
It must have been some sort of corruption in userspace. I had previously tried a wipe through TWRP which was claimed to be successful. I still can't determine if TWRP doesn't check all their syscalls and handle the return codes or the Linux subsystem in Android is the root of the bugs. Either way, upon reboot, the device returned to factory "out of box" state.

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.

Question I think I messed up my B Slot Partition(s)

I have a Poco F3 Global, and I currently am running TWRP 3.5.2_11-Nebrassy.
If I tap Reboot and it shows my Current Slot as A, then under Mount I see the following:
System, system_ext, Product, Vendor, ODM, Metadata, Data, Cust, and Firmware
And I can check each of them. I can also perform Wipe -> Format Data -> yes.
But if I boot into Slot B, and tap Mount it doesn't let me click the checkmarks for System, system_ext, Product, or Vendor.
And if I try to execute Wipe -> Format Data -> yes it shows "Failed to mount" in red for all of the following:
'/system_root', '/system_ext', '/product', '/vendor' (Invalid argument)
(Some of them are in there multiple times)
Running cat /etc/fstab in B outputs:
Code:
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/dev/block/bootdevice/by-name/modem_b /firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
Running cat /etc/fstab in A outputs:
Code:
/dev/block/dm-2 /system_root ext4 ro 0 0
/dev/block/dm-3 /system_ext ext4 ro 0 0
/dev/block/dm-1 /product ext4 ro 0 0
/dev/block/dm-4 /vendor ext4 ro 0 0
/dev/block/dm-0 /odm ext4 ro 0 0
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
For both A and B going to Wipe -> Advanced Wipe it only shows Dalvik / ART Cache, Metadata, Data, Internal Storage, and USB-OTG
I can still install an OS, but that is finicky at times.
How can I fix my B Partition?

Solved it:
Download the MiFlash Tool, and the Fastboot version of the Stock ROM. Extract the contents of the zip (and within the zip the tar file) to a directory without spaces in it (I just extracted it directly to C: drive). Open MiFlash, click Select and choose the directory you just extracted. At the bottom of the MiFlash app select "Clean All", NOT "Clean all and Lock" (unless that's what you want). Click Refresh (if phone doesn't appear, make sure your phone is in fastboot mode and connected to PC). Then click Flash. Mine failed the first time with some error about "Antirollback check error". If you get this you have to manually edit the "flash_all.bat" file within the extracted directory and remove the lines that don't start with "fastboot", then save the bat file, and restart the flash. It took MiFlash 604 seconds to complete, and ended with a status of "error: Not catch checkpoint, ..., flash is not done" you can ignore that, or remove that checkpoint in the MiFlash configuration settings. My phone restarted and booted into the stock ROM.

following had the same errors when i mistakenly ignorantly wiped system etc while trying to flash a rom