Database Info

Mounting in Gentoo Linux with A2SD partitions

I am running cyanogen's rom with a fat32 partition and ext3 partition. When i run fdisk on the device /dev/sdb, i get this as a result and it looks ok:
Code:
# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 8067 MB, 8067743744 bytes
249 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes
Disk identifier: 0x000eadb7
Device Boot Start End Blocks Id System
/dev/sdb1 1 941 7263548 c W95 FAT32 (LBA)
/dev/sdb2 942 1005 487398 83 Linux
Partition 2 does not end on cylinder boundary.
however, I cant mount my partitions reliably. Sometimes when I plug it in, I get the fat32 partition as /dev/android, and sometimes I get the ext3 partition. but under both circumstances, i NEVER see /dev/sdb1 or /dev/sdb2.
Code:
# ls /dev | grep sd
lrwxrwxrwx 1 root root 4 2009-07-20 15:55 root -> sda3
brw-rw---- 1 root disk 8, 0 2009-07-20 15:55 sda
brw-rw---- 1 root disk 8, 1 2009-07-20 15:55 sda1
brw-rw---- 1 root disk 8, 2 2009-07-20 15:55 sda2
brw-rw---- 1 root disk 8, 3 2009-07-20 15:55 sda3
brw-rw---- 1 root disk 8, 16 2009-07-21 20:43 sdb
however, my dmesg reports this:
Code:
78640.618666] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.620661] sd 30:0:0:0: [sdb] Write Protect is off
[78640.620664] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.620667] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.624658] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.626659] sd 30:0:0:0: [sdb] Write Protect is off
[78640.626662] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.626665] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.626669] sdb: sdb1 sdb2
[78640.633034] usb 1-2:1.0: uevent
[78640.633122] usb 1-2: uevent
[78640.899187] usb 1-2:1.0: uevent
[78640.899276] usb 1-2: uevent
[78641.054596] VFS: Can't find ext3 filesystem on dev sdb1.
it takes a bunch of tries of unplugging the usb and plugging it back in until it finally somehow mounts my fat32 partition under /media/disk. Is this some configuration issue? Before I partitioned my sdcard, it was fine mounting just a fat32 partition as the entire card, no problems.

check you hald
/etc/init.d/hald restart
do you have support for udev in you kernel ?
Check this steps and tell us it worked

yes HAL is running and has been running the entire time:
Code:
# rc-update show
alsasound | boot
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
consolefont | boot
cupsd | default
dbus | default
hald | default
hostname | boot
keymaps | boot
lm_sensors | default
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
numlock | default
rdate | default
rmnologin | boot
sshd | default
syslog-ng | default
urandom | boot
xdm | default
Code:
$ ps aux | grep hal
103 3544 0.0 0.0 26956 4032 ? Ss Jul24 0:01 /usr/sbin/hald --use-syslog --verbose=no
root 3545 0.0 0.0 15624 1176 ? S Jul24 0:00 hald-runner
root 3548 0.0 0.0 17748 1124 ? S Jul24 0:00 hald-addon-input: Listening on /dev/input/event1 /dev/input/event0 /dev/input/event3
103 3553 0.0 0.0 16608 968 ? S Jul24 0:00 hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
root 3558 0.0 0.0 17748 1128 ? S Jul24 0:08 hald-addon-storage: polling /dev/sr0 (every 2 sec)
john5788 4596 0.0 0.0 130688 3120 ? Sl Jul24 0:00 /usr/libexec/gvfs-hal-volume-monitor
root 11452 0.0 0.0 17748 1124 ? S Jul24 0:01 hald-addon-storage: polling /dev/sdb (every 2 sec)
john5788 13851 0.0 0.0 84792 864 pts/1 R+ 10:10 0:00 grep --colour=auto hal
restarting does not help anything.

udevd --version ??
since version 140 those stupids rules messed up with removable devices.

Since I'm lazy I built my kernel with genkernel and it took care of everything about udev.

Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux

John5788 said:
Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
Click to expand...
Click to collapse
Yeah i think ...
what's the output of dmesg |grep EXT3-fs ?

the output has a bunch of instances last night when i was plugging and unplugging the device. like i said, sometimes it recognized my fat32 partition, sometimes ext3.
Code:
# dmesg | grep EXT3-fs
[ 9016.479321] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9016.481783] EXT3-fs: mounted filesystem with ordered data mode.
[ 9111.770944] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9134.532699] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9134.534632] EXT3-fs: recovery complete.
[ 9134.536841] EXT3-fs: mounted filesystem with ordered data mode.
[ 9166.843481] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9166.849252] EXT3-fs: mounted filesystem with ordered data mode.
[ 9184.778649] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9243.636550] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9243.638973] EXT3-fs: recovery complete.
[ 9243.638976] EXT3-fs: mounted filesystem with ordered data mode.
[ 9305.343298] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9305.345249] EXT3-fs: mounted filesystem with ordered data mode.
[ 9328.776678] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[15048.450805] EXT3-fs: recovery complete.
[15048.452800] EXT3-fs: mounted filesystem with ordered data mode.
[15055.778655] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal

ok it seems one of partitions is broken i've looked around the web
try to :
e2fsck -p your /home partitions and
fsck.vfat -p /dev/sdb1 and e2fsck -p /dev/sdb2

I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.

Zappletoo said:
I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.
Click to expand...
Click to collapse
tht's strange cfdisk should not help mounting the devices but if it work it's worthing give it a try.
it has to be something with hal and rules :
emerge -pv hal dbus
etc-update
should get rid of that problem
PS : Zappletoo what linux distribution are you using ??

Gentoo.
But I don't use HAL, I don't see any good reason to. I'll try to activate it to see if it makes a difference, but I doubt it.
I'm not sure why cfdisk helps, maybe it simply updates the partition table somewhere.
Update : starting hald makes it work. Using partprobe works as well.. So I guess I was right about the partition table part.

what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?

no no run cfdisk on your computer
Edit: yes I misread. That's what he did.
If things goes well your 2 partitions should appear

John5788 said:
what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?
Click to expand...
Click to collapse
Yes, on the computer.
Apparently it does the same as partprobe, which is available in the sys-apps/parted package.
Hald does everything automatically though, but it's bloated.

Never had a problem with gentoo. No Hal...udev 1.41...custom kernel. Somewhere else on this forum however someone pointed out the phone doesn't show up properly in linux without first probing it. i.e. 'fdisk -l /dev/sda'. This has worked for me whenever I choose to mount it (which is almost never cuz i love adb).

[Q] CyanogenMod 6.3.0 link2sd

Anyone get link2sd working with the latest CyanogenMod 6.3.0 from Moize yet?
Tried reformatting, keep running into the Mount script error.
"Mount script cannot be created.
mount: mounting/dev/block/vold/179:2 on /data/sdext2 failed: No such device"
For quick reference, it was working on Khalpower's EpicSteelBlue rom. I can't seem to get SU to run in adb shell either...
Any workarounds would be appreciated!
(I don't have enough posts to post in the main development thread yet.)

Can you run these commands (either in adb shell or terminal):
Code:
su
fdisk -l /dev/block/mmcblk0 > /sdcard/fdisk.txt
and then post the contents of /sdcard/fdisk.txt ?

I will try as soon as I get back home.
Restored my backup since I need to be heading out for now.

Back. Here are the contents of fdisk.txt.
Code:
Disk /dev/block/mmcblk0: 16.5 GB, 16574840832 bytes
255 heads, 63 sectors/track, 2015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1689 13566861 b Win95 FAT32
/dev/block/mmcblk0p2 1690 1885 1574370 83 Linux
/dev/block/mmcblk0p3 1886 2015 1044225 82 Linux swap
The native app2ext works, but I can't enable link2sd for some reason.

Raydonn said:
Back. Here are the contents of fdisk.txt.
Code:
Disk /dev/block/mmcblk0: 16.5 GB, 16574840832 bytes
255 heads, 63 sectors/track, 2015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1689 13566861 b Win95 FAT32
/dev/block/mmcblk0p2 1690 1885 1574370 83 Linux
/dev/block/mmcblk0p3 1886 2015 1044225 82 Linux swap
The native app2ext works, but I can't enable link2sd for some reason.
Click to expand...
Click to collapse
Can you try making an empty /sd-ext/link2sd directory and reboot? Or have you done that already?

Mioze7Ae said:
Can you try making an empty /sd-ext/link2sd directory and reboot? Or have you done that already?
Click to expand...
Click to collapse
I've tried that.
Link2sd won't recognize it for some reason on this rom.

I found some bugs in the link2sd init.d script. A hotfix can be found here:
http://forum.xda-developers.com/showpost.php?p=16757523&postcount=408

Thanks, link2sd is working now.
But there seems to be another problem I'm running into. I can't seem to get the system to mount anything but ext2.
So ext2? Link2sd and root explorer sees the sd-ext fine and reports the size, etc.
ext3 and ext 4? Unable to mount.
Perhaps there's something I'm overlooking, but I've reformatted the SD card several times now to no avail.

Try to manualy mount like:
mount /dev/block/mmcblk0p2 /sd-ext -t ext4(3) and reboot.

fjfalcon said:
Try to manualy mount like:
mount /dev/block/mmcblk0p2 /sd-ext -t ext4(3) and reboot.
Click to expand...
Click to collapse
Hmm, tried that.
Getting the error message
"mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such device" for ext3.
"mounting /dev/block/mmcblk0p2 on /sd-ext failed: Invalid argument" for ext4.

ls /system/lib | grep ext
show input...

fjfalcon said:
ls /system/lib | grep ext
show input...
Click to expand...
Click to collapse
Code:
libext2_blkid.so
libext2_com_err.so
libext2_e2p.so
libext2_profile.so
libext2_uuid.so
libext2fs.so

Are you sure that u usyng cm 6.3.0?
Cause it has already build-in modules for ext4.
http://www.multiupload.com/VHPFIMOJTR
apply that update again, you don't need to make any wipes.(or just wipe cache...)

Hmm, tried updating/installing again.
Still no luck. Same results.
Does it matter that I skipped 6.1.2 and went straight to 6.3.0? Although that doesn't make much sense since you said 6.3.0 included the modules for ext4.
I also see ext2.ko, ext3.ko, ext4.ko in system/lib/modules so I assume it's all there.

Small update.
I don't know why, but link2sd is working now and apparently with ext4.
Maybe it's because I installed cm6.1.2 and then applied cm6.3.0 overtop it? I didn't factory wipe though, but it still works.
Or maybe it's because I used the new OR to update my ext2 to ext4 instead of fresh formatting it to ext4?
Or maybe the latest version of link2sd fixed ext4 support? I don't know.
But anyhow, thanks for all the help and the great ROM.

Raydonn said:
Or maybe it's because I used the new OR to update my ext2 to ext4 instead of fresh formatting it to ext4?
Click to expand...
Click to collapse
Probably this one. The ext4 update in the OR uses known-working ext4 options. I think there are some features that desktops turn on by default when formatting ext4 that don't work with our kernel. My guess is it's largefile support, but I haven't tested tested that hunch.

Boot loop Unresolvable? Hardware problem?

Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.

I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...

Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.

If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck

My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...

Thanks for your time. I appreciate it.

bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...

it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.

I face this problem too. Please someone give us the solution.

Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.

More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.

There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.

alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?

bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.

strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/

Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #

That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app

alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.

try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip

alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0

[Q] HELP stuck in a serious bootloop

My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me

amitshkuri said:
My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me
Click to expand...
Click to collapse
can you boot into bootloader?
if yes post all the on screen details

rzr86 said:
can you boot into bootloader?
if yes post all the on screen details
Click to expand...
Click to collapse
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

amitshkuri said:
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots

rzr86 said:
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots
Click to expand...
Click to collapse
i flashed 4ext recovery and flashed 3.33 firmware and flashed ARHD 7.2 (i did full wipe for all patitions)
still in bootloop but now it pass the HTC logo and the quitly brilliant logo and start the beats animation then it restart.

HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"

shrex said:
HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"
Click to expand...
Click to collapse
I flashed the new hboot and flashed the recovery again and made a clean installation including format for all partitions and still i stuck in this bootloop! what can i do more?

amitshkuri said:
what can i do more?
Click to expand...
Click to collapse
Absolutely loads of stuff. First thing is to get the logs.
Flash a rom with adb set in the default.prop in the boot image ramdisk ( CM for example )
while the device is bootlooping run
Code:
adb shell dmesg
which gives the kernel messages then you can run
Code:
adb logcat -b system -b radio -b events -b main
this will run forever, you'll notice it repeating the same messages over and over, look out for lines that start with "E/"
they're errors being reported and will lead you to the cause of you're bootloop
If either of these two fail then reboot into recovery and run
Code:
adb shell cat /dev/last_kmsg
This is a saved copy of dmsg from the last session.
Once you've got the logs you can easily pinpoint the cause of the problem all you got is read them
PROTIP: Look for the word error or fail or something similar

ok so that's all the errors i found while booting:
E/QC-NETMGR-LIB( 165): couldn't open file /sys/module/f_rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): couldn't open /sys/module/rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/DxDrmNexPlayerIntegrator( 169): ** Discretix Server loaded config file - result=0 **
E/DxDrmNexPlayerIntegrator( 169): ** Discretix SignalsListener Thread is starting **
E/DxSecureClock( 169): ** Discretix Clock Monitor is starting **
E/msm8660.gralloc( 153): DEBUG_CALC_FPS: 0
E/msm8660.gralloc( 153): period: 10
E/msm8660.gralloc( 153): ignorethresh_us: 500000
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 0
E/SurfaceFlinger( 153): composer device failed to initialize (Invalid argument)
E/rmt_storage( 120): Unable to open /boot/modem_fsg
E/rmt_storage( 120): Invalid rmt_storage client
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 1
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 2
E/HtcBootAnimation( 225): Could not find width.
E/HtcBootAnimation( 225): Could not find height.
E/HtcBootAnimation( 225): Could not find framerate.
E/HtcBootAnimation( 225): Could not find part1.
E/HtcBootAnimation( 225): Could not find part2.
E/HtcBootAnimation( 225): Could not find part3.
E/HtcBootAnimation( 225): sqlite3_open error, sqlite result: 14, errno: 2, No such file or directory
E/QC-DIAG_LSM( 156):
E/QC-DIAG_LSM( 156): Diag_LSM: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 3
E/ExtendedExtractor( 156): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: reloc_library[1290]: 156
E/AudioPolicyManagerBase( 156): Could not open support_receiver()
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 4
And this came at the second of crash:
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 5
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 6
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 7
am i in trouble?

amitshkuri said:
am i in trouble?
Click to expand...
Click to collapse
It's difficult to say with ONLY the errors LOL. You've just removed all the context of what was going on around leading upto it. Can you post the rest of them, not here though, pastebin or somewhere like that.
Also dmesg output would be pretty useful to see if all the drivers are install correctly.
At first glance, You seem to be missing some vital libraries. files, to say anything more at this point would just be guessing? but yeah, dmesg and a full logcat.
Actually to save a back and forth you can run the following commands
Code:
adb root
adb shell stop
adb shell dumpstate > state.txt
adb shell dumpsys > sys.txt
Don't know what you know so I'll explain what this does.
adb root , restarts adb as the root user
adb shell stop, this stops the servicemanager and it's child services , basically stop loading android. If you have a boot animation you should see it stop, this also stops device from rebooting as the next commands take some time to run.
dumpstate and dumpsys will dump your entire device contents to state.txt and sys.txt on your desktop machine. you won't see any output and they do take some time to run so please be patient. As you've fully formatted it I wouldn't expect any personal data to be present in those files but may contain device specific info please have a look before posting. searching the for things like your email address, name, IMEI, serial no's etc should help.
Then zip the files and attach them to this thread. Like I mentioned these files contain everything about the Device and the current state and will give us everything we need to figure out whats wrong.
If you're not comfortable "doing the dump!" ( sounds like a song ) then option 1 of logcat and dmesg should do I'll probably end up asking for more but meh!

ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.

amitshkuri said:
ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.
Click to expand...
Click to collapse
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!

own diBeco
trevd said:
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!
Click to expand...
Click to collapse
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.

amitshkuri said:
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.
Click to expand...
Click to collapse
hi again.
After reading some more e2fsck need some extra options. apologises for that
Also as is usually the case with these things you're not the first person to have this problem. A quick xda search for "The needs_recovery flag is set" brings up this post
I've just tested it because my cache partition has the needs_recovery flag set so I ran the commands in that post in recovery and it did clear the needs_recovery flag. so in your case you need to boot into recovery make sure /system is NOT mount which should be the default state and run the following commands
Code:
adb shell
tune2fs -l /dev/block/mmcblk0p22 | grep features
this command get the list of filesystem features it should look something like this ( order may be different )
Code:
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
Next we'll run e2fsck with the right command this time LOL
Code:
e2fsck -f /dev/block/mmcblk0p22
After that we can remove the old journal with tune2fs
Code:
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
This should remove both the has_journal and needs_recovery flags from the feature list. Seeing as has_journal was set we'll turn it back on
Code:
tune2fs -O has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
Note the caret symbol ( ^ ) which is the difference between the above to commands. This controls whether a feature should be added or removed
Finally check the feature list again
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
It should now look like this or something similar, If it still has needs_recovery in the list then something is wrong
Code:
Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
All we need to do now is pray to the ghost of steve jobs and say the magic words
Code:
reboot
And hopefully we might have a win for you! :good:

when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?

amitshkuri said:
when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?
Click to expand...
Click to collapse
e2fsck -f -y /dev/block/mmcblk0p22
That will answer yes to all questions!

i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?

amitshkuri said:
i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?
Click to expand...
Click to collapse
Time to rinse and repeat, Grab the dmesg and the logcat and lets see what it's saying now? Also Have you tried reflashing the rom, it's possible the tune2fs has deleted some files but we can only find out by looking at the logs!

i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!

amitshkuri said:
i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!
Click to expand...
Click to collapse
Not a problem on the help. At least you bought an interesting problem to solve It's not your normal bootloop cause.
hmmm , It seems to have gone back to needs recovery.... Ok. Can you run the command from earlier but this time do not re-add the journal feature, so these commands
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
e2fsck -f -y -v /dev/block/mmcblk0p22
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
tune2fs -l /dev/block/mmcblk0p22 | grep features
#EDIT Mount as read only to mark it ready for mounting
mount -ro -text4 /dev/block/mmcblk0p22 /system
reboot
can you copy the output of these commands and post them up, I'm just curious to see what its runnning.
Do you know how to make your boot image insecure and how to mount /system with rw by default?
If not can you send me the boot image you're using an i'll fix it up.
The plan is to attempt the fs repair and remove journaling which from what I understand can be responsible for triggering the needs_recovery. should that not work, the kernel will try running recovery on the fs at boot time but this time it won't need to remount the /system partition because it will be already mounted as rw ... that's the theory at least.
If it fails send the logs and we'll have a look a some other options depending on the log out. But I wouldn't be worried there's still a couple of more things we can leverage to fixup the system partition.

[Q] How to repair partition on internal storage?

I was trying to get 4.4.2 (Omnirom / CM11.1) on my Xoom.
The only problem I facing is TWRP is asking for password or else it will have problem mounting to cache.
This lead to cannot wipe cache and cannot wipe cache\dalvik.
I search the forum up and down and people comment that the partition is corrupt that TWRP trying to recover it.
So my question is how can I repair or recreate the partition.
What tool should I use?
Even if it is using adb shell, what kind of program I need to push into the phone.
Hope someone can help me out.
I did try to play around like 5 hours.
At first TWRP complaint that cannot mount /cache
Then I try use CWM recovery to wipe cache and dalvik. Then only install TWRP (without big part). Again I wipe cache and dalvik.
Then when I install TWRP (with big part) and no longer complaint cannot mount cache.
But it keep showing update partition details.
When I try to wipe data it will be unsuccessful.
Hope experience people can guide me. Really want to see my motorola xoom (everest) to be on kit kat.

kblade29m said:
I was trying to get 4.4.2 (Omnirom / CM11.1) on my Xoom.
The only problem I facing is TWRP is asking for password or else it will have problem mounting to cache.
This lead to cannot wipe cache and cannot wipe cache\dalvik.
I search the forum up and down and people comment that the partition is corrupt that TWRP trying to recover it.
So my question is how can I repair or recreate the partition.
What tool should I use?
Even if it is using adb shell, what kind of program I need to push into the phone.
Hope someone can help me out.
I did try to play around like 5 hours.
At first TWRP complaint that cannot mount /cache
Then I try use CWM recovery to wipe cache and dalvik. Then only install TWRP (without big part). Again I wipe cache and dalvik.
Then when I install TWRP (with big part) and no longer complaint cannot mount cache.
But it keep showing update partition details.
When I try to wipe data it will be unsuccessful.
Hope experience people can guide me. Really want to see my motorola xoom (everest) to be on kit kat.
Click to expand...
Click to collapse
hello...
same problem on my xoom Wingray
if i find a fix i posted here
Good luck

ankorez said:
hello...
same problem on my xoom Wingray
if i find a fix i posted here
Good luck
Click to expand...
Click to collapse
Same here too... wingray also

As far as I can tell, you didn't follow the directions. Re-start the BigPart process from the beginning, and when TWRP asks you for a password, just ignore that and press the Home icon at the top. Tap the Wipe tab, and there will be two options, Advanced and Format Data, along with the slider at the bottom for a Factory Reset. Tap the Format Data tab, type yes when prompted, and hit enter/return. Then follow the rest of the steps in the BigPart process.
And, please, if you're going to BigPart, just pretend CWM doesn't exist, because all it's going to do is mess things up for you.

Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
Format MicroSD to Fat32 and copied the following files
- R.A.H._TWRPv2.6.3_BigPart_selinux.zip
- cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip
- pa_gapps-modular-full-4.4.2-20131230-signed.zip
Step 2 - Flash Recovery to TWRP
- Has Android SDK
- Extract R.A.H._TWRPv2.6.3.zip to get recovery.img
- Set Xoom to Fastboot mode by press vol down before dual core logo appeared.
- In command line, type fastboot flash recovery recovery.img
Step 3 - Boot into Recovery
- Set Xoom to Recovery mode by press vol down after dual core logo appeared for 3 seconds.
- Notice at this step you will not have problem mounting to /cache partition.
Step 4 - Create BigPart
Refer to http://forum.xda-developers.com/showthread.php?t=2506997
Go through step by step.
- Use Install to flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe Dalvik Cache, System, Cache, Data, Internal Storage. Exclude sdcard. (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSU (Rebooted into Recovery)
- Home - Wipe - Format Data - Type yes (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe system and cache (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSu (Rebooted into Recovery)
- Home - Mount - Check System and Uncheck System (Just testing only. No Reboot)
Step 5 - Install Rom and Gapps
- Home - Install - cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip and pa_gapps-modular-full-4.4.2-20131230-signed.zip
- Swipe to Flash
- Wipe Dalvik and Cache
- Home - Mount - Reboot - System
- Give 5 - 10 minutes for the installation to complete. Not a boot loop. Just take longer time to finish installation.
Enjoy the CM11 (4.4.2) on Xoom
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)

kblade29m said:
Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
...
Step 2 - Flash Recovery to TWRP
...
Step 3 - Boot into Recovery
...
Step 4 - Create BigPart
...
Step 5 - Install Rom and Gapps
...
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)
Click to expand...
Click to collapse
There is almost the same problem with my "UMTS_Everest". I tried to follow all these instructions (includin the "troubleshooting part". But I'm not able to flash another recovery anymore with fastboot nor with TRWP (CWM e.g.) :crying:
I tried also everything, but there is (has never been) no /data-partition anymore and it says "unable to mount /cache" all the time in TWRP
There is no /data-partition visible to mount in TRWP.

Try again. Hope you still can enter fastboot mode.
If you use adb and fastboot, I sure you can get it work.
If you using Windows, make sure usb installed with right driver.
Make device in fastboot mode.
Power + Vol down (hold before motorola logo appear).
Screen will show some text related to fastboot.
When you type "fastboot devices" you able to see your device.
fastboot flash recovery clockwork-recovery.img
fastboot reboot
If you can enter clockworkmod recovery u can format all the mount. To enter recovery.
Power + Vol down (hold after Motorola logo appear for 3 second). When recovery text appeared press Vol up.
Sent from my Nexus 4 using xda app-developers app

kblade29m said:
fastboot flash recovery clockwork-recovery.img
fastboot reboot
Click to expand...
Click to collapse
fastboot flash recovery fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
or fastboot flash recovery recovery-clockwork-touch-6.0.3.2-everest.img
sending 'recovery' (5270 KB)...
OKAY [ 0.511s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 1.034s
status done!
Still TWRP

peterkling said:
fastboot flash recovery fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
or fastboot flash recovery recovery-clockwork-touch-6.0.3.2-everest.img
sending 'recovery' (5270 KB)...
OKAY [ 0.511s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 1.034s
status done!
Still TWRP
Click to expand...
Click to collapse
Hello,
Ihave the same issue.
You have fixed it ?

How I fixed mine
Hi,
I had the same Problem some weeks ago. After trying to install a newer custom Rom which did not boot I neither was able to wipe dalvik nore had a System Partition anymore.
With big help from HDwally I was able to fix it. The first Thing I did was to install a stock Rom.
For this you have to install the Motorola USB Driver
https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819
and RSD lite.
http://www.chip.de/downloads/RSD-Lite_49139659.html
You might find a suitable stock Rom here:
http://forum.xda-developers.com/showthread.php?t=1049485
After I installed this my Xoom worked fine again. But I installed a crm after that again following these instructions and I was able to install a custom Rom again.
http://forum.xda-developers.com/showthread.php?t=2506997
I hope you will be able to fix your xoom.
Good luck..
Alexander

onlyage said:
Hi,
I had the same Problem some weeks ago. After trying to install a newer custom Rom which did not boot I neither was able to wipe dalvik nore had a System Partition anymore.
With big help from HDwally I was able to fix it. The first Thing I did was to install a stock Rom.
For this you have to install the Motorola USB Driver
https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819
and RSD lite.
http://www.chip.de/downloads/RSD-Lite_49139659.html
You might find a suitable stock Rom here:
http://forum.xda-developers.com/showthread.php?t=1049485
After I installed this my Xoom worked fine again. But I installed a crm after that again following these instructions and I was able to install a custom Rom again.
http://forum.xda-developers.com/showthread.php?t=2506997
I hope you will be able to fix your xoom.
Good luck..
Alexander
Click to expand...
Click to collapse
Hello,
thank you, but don't work for me.
is there another solution ?

I still have not solved my problem, there's really no way to fix my xoom

If anyone is still looking, this article explains really well:
http://www.djsmobiles.com/2014/02/h...epartition-upgrade-on-your-motorola-xoom.html

Fuuuq! Did the BigPart partition and forgot to back up my current ROM, so when I attempt to reinstall I don't see my .zip plus when I reboot. I get the OS not installed.
Mz600 / Vzw / CDMA+Wifi

Got mine to work
I know this is a dead thread, but just in case someone comes here looking for help...
I tried all the directions, and couldn't get stuff to mount. always fails. I finally got it. Not sure why this worked...
Flashed TWRP through fastboot.
Then flashed recovery-Tiamat-R4c-100611-1150-cwm.img
formatted each partition and then mounted them
then flashed the R.A.H._TWRPv2.6.3_BigPart_selinux.zip
Then rebooted recovery
Then in TWRP it actually let me format each individual partition one at a time.
Then it let me flash Omni
Not sure why TWRP (regardless of version) would not let me mount. Only CW would. anyways, hope this helps.

stingray (verzion xoom) information
I had trouble getting my cache to mount. kept giving me an error of E:Unable to mount /cache/. After beating my head for about 5-7 hours. I found the post quoted below. I used TWRP recovery and adb sideloaded R.A.H._TWRPv2.6.3_BigPart_selinux.zip b/c I couldn't figure out how to mount the SDCARD to just drag and drop the file in my windows Operating System.
Still nothing. Then I followed the post below under STEP 4 VERY CAREFULLY where it instructed me to format the ENTIRE INTERNAL STORAGE ONLY. Did that, installed R.A.H._TWRPv2.6.3_BigPart_selinux.zip and the cache error went away. Followed the REST of step 4 and FINALLY CM11 ON MY WORE OUT MOTOROLA XOOM VERIZON (STINGRAY) TABLET! GOD SPEED AND HAPPY NEW YEARS!! :good::good:
kblade29m said:
Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
Format MicroSD to Fat32 and copied the following files
- R.A.H._TWRPv2.6.3_BigPart_selinux.zip
- cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip
- pa_gapps-modular-full-4.4.2-20131230-signed.zip
Step 2 - Flash Recovery to TWRP
- Has Android SDK
- Extract R.A.H._TWRPv2.6.3.zip to get recovery.img
- Set Xoom to Fastboot mode by press vol down before dual core logo appeared.
- In command line, type fastboot flash recovery recovery.img
Step 3 - Boot into Recovery
- Set Xoom to Recovery mode by press vol down after dual core logo appeared for 3 seconds.
- Notice at this step you will not have problem mounting to /cache partition.
Step 4 - Create BigPart
Refer to http://forum.xda-developers.com/showthread.php?t=2506997
Go through step by step.
- Use Install to flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe Dalvik Cache, System, Cache, Data, Internal Storage. Exclude sdcard. (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSU (Rebooted into Recovery)
- Home - Wipe - Format Data - Type yes (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe system and cache (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSu (Rebooted into Recovery)
- Home - Mount - Check System and Uncheck System (Just testing only. No Reboot)
Step 5 - Install Rom and Gapps
- Home - Install - cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip and pa_gapps-modular-full-4.4.2-20131230-signed.zip
- Swipe to Flash
- Wipe Dalvik and Cache
- Home - Mount - Reboot - System
- Give 5 - 10 minutes for the installation to complete. Not a boot loop. Just take longer time to finish installation.
Enjoy the CM11 (4.4.2) on Xoom
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)
Click to expand...
Click to collapse

I believe I flashed a 4.1.2 boot.img file a modified rooted version and possibly also reset before a proper flashing in twrp 2.8.6.0. could be one or the other. Both.
No go on any of the suggested fixes.
I'm experiencing same issues.
Specifically, I am unable to mount /data & /cache partitions in TWRP v2.8.6.0 Bigpart Recovery.
I am unable to recover them both through the repair function and Change File System function in TWRP.
Tried all configurations of file system type and sequence of changing the file system types of system, ,data, cache.
The error that appears after attempting to change file system of data, system,cache, all of them is as follows
ERROR: sbin/e2fsk -p /dev/block/mmcblk1p10 process ended with ERROR=8
unable to repair '/data'.
error repairing file system.
I can successfully erase system, boot, userdata, recovery partitions and flash any .img to according partitions with fastboot commands (i.e. fastboot erase cache fastboot flash recovery recovery.img) Although this does not successfully flash anything. Fastboot says it does but recovery remains the same as well as the boot animation which im assuming is in the boot.img file.
I believe im looking for the next viable option which is to rebuild the systems internal data? I dont know via fastboot?
Can anyone help? Could someone explain how to what actually is missing here?

I was successful with e2fsck through adb on my userdata partition and using an alternate superblock. But not I am unsuccessful with it on my cache. These are the only two partions that I am unable to mount in TWRP. I am not even sure if fixing these is proper. I attempted to go in on the /dev/block/platform/sdhci-tegra.3/mmcblkop9 and 10 which are damaged as well I learned when I attempted repair on TWRP on cache.
Code:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b /dev/block/platform/sdhci-tegra.3/by-name/cache
Invalid non-numeric argument to -b ("/dev/block/platform/sdhci-tegra.3/by-name/c
ache")
~ # ←[6n e2fsck -p 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -p 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # ←[6n e2fsvk -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsvk -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
/sbin/sh: e2fsvk: not found
~ # ←[6n e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 8193 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 8193 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/by-name/cache
mke2fs -n /dev/block/platform/sdhci-tegra.3/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6ne2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/sdhci-tegra.3/by-name/cache
/dev/block/platform/sdhci-tegra.3/by-name/cache:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -p /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -p /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/sdhci-tegra.3/mmcblk0p9
/dev/block/platform/sdhci-tegra.3/mmcblk0p9:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Is a directory while trying to open /dev/block/platform/sdhci-tegra.3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3 is not a block special device.
Proceed anyway? (y,n) y
y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p8
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p8
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3/mmcblk0p8: clean, 11/16384 files, 2089/65536 b
locks
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -n 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -n 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # ←[6ne2fsck -b /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b /dev/block/platform/sdhci-tegra.3/mmcblk0p9
Invalid non-numeric argument to -b ("/dev/block/platform/sdhci-tegra.3/mmcblk0p9
")
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3 is not a block special device.
Proceed anyway? (y,n) y
y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6nmke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs: invalid block size - 98304
~ # ←[6nmke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs: invalid block size - 98304
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
MZ604 US WIFI Can someone pull and send me the partitions files in dev/block/platform/sdhci-tegra.3? Will replacing and overwriting all my mmcblk0, mmcblko9p1, mmcblk0p10, ect. repair the issue of not being able to mount /data & /cache? or would just someone pulling files form this folder in the picture be sufficent. I say this because if i understand correctly the /userdata and /cache are the culprits, that is the root of the damage. Not sure if im making sense but I hope someone has some advice.

Here is a list of all the partitions on MZ604 Motorola Xoom. I obtained a few list using different commands. Take a look.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd c:\adb\adb
c:\adb\adb>adb shell
~ # ←[6nls -l \dev\block\platform\sdchi-tegra.3\by-name
ls -l \dev\block\platform\sdchi-tegra.3\by-name
devblockplatformsdchi-tegra.3by-name: No such file or directory
~ # ←[6nls -l \dev\block
ls -l \dev\block
devblock: No such file or directory
~ # ←[6nls \dev\block
ls \dev\block
devblock: No such file or directory
~ # ←[6nls -al \dev\block
ls -al \dev\block
devblock: No such file or directory
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 98304 zram0
253 1 98304 zram1
179 0 31162368 mmcblk0
179 1 3072 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 1048576 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 29525504 mmcblk0p10
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
~ # ←[6nls -l /dev/block
ls -l /dev/block
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 7, 0 1970-01-02 14:15 loop0
brw------- root root 7, 1 1970-01-02 14:15 loop1
brw------- root root 7, 2 1970-01-02 14:15 loop2
brw------- root root 7, 3 1970-01-02 14:15 loop3
brw------- root root 7, 4 1970-01-02 14:15 loop4
brw------- root root 7, 5 1970-01-02 14:15 loop5
brw------- root root 7, 6 1970-01-02 14:15 loop6
brw------- root root 7, 7 1970-01-02 14:15 loop7
brw------- root root 179, 0 1970-01-02 14:15 mmcblk0
brw------- root root 179, 1 1970-01-02 14:15 mmcblk0p1
brw------- root root 259, 2 1970-01-02 14:15 mmcblk0p10
brw------- root root 179, 2 1970-01-02 14:15 mmcblk0p2
brw------- root root 179, 3 1970-01-02 14:15 mmcblk0p3
brw------- root root 179, 4 1970-01-02 14:15 mmcblk0p4
brw------- root root 179, 5 1970-01-02 14:15 mmcblk0p5
brw------- root root 179, 6 1970-01-02 14:15 mmcblk0p6
brw------- root root 179, 7 1970-01-02 14:15 mmcblk0p7
brw------- root root 259, 0 1970-01-02 14:15 mmcblk0p8
brw------- root root 259, 1 1970-01-02 14:15 mmcblk0p9
drwxr-xr-x root root 1970-01-02 14:15 platform
brw------- root root 253, 0 1970-01-02 14:15 zram0
brw------- root root 253, 1 1970-01-02 14:15 zram1
~ # ←[6n
c:\adb\adb>
No list told me exactly which partition was my /data and/cache but as you can see when I run the "Repair" function on my Data and Cache in TWRP 2.8.6.0, the log returns an error to which file it is attempting to repair respectively.
Repairing Data using e2fsk . . .
E: /sbin/e2fsk -p /dev/block/mmcblk0p10 process ended with ERROR=8
E: Unable to repair '/data' .
E: Error repairing file system.
E: Unable to mount '/data/' .
So from there I wanted to rebuild them due to the fact that they are indeed corrupt. Since I was unsuccessful using the "Change File System" function and "Format" function in TWRP 2.8.6.0 as well as unsuccessful using "fastboot format userdata' command in Fastboot I decided to use a command in ADB, mke2fs -T ext4 /dev/block/mmcblk0p9 and mke2fs -T ext4 /dev/block/mmcblk0p10. Here is the terminal showing these commands. . .
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd c:\adb\adb
c:\adb\adb>adb shell
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p9
mke2fs -T ext4 /dev/block/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p10
mke2fs -T ext4 /dev/block/mmcblk0p10
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1847776 inodes, 7381376 blocks
369068 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
226 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6nmount /dev/block/mmcblk0p9
mount /dev/block/mmcblk0p9
mount: mounting /dev/block/mmcblk0p9 on /cache failed: Invalid argument
~ # ←[6nmount /data
mount /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
~ # ←[6nmount /dev/block/mmcblk0p9
mount /dev/block/mmcblk0p9
mount: mounting /dev/block/mmcblk0p9 on /cache failed: Invalid argument
~ # ←[6nmount /data/media
mount /data/media
mount: can't find /data/media in /etc/fstab
~ # ←[6nreboot
reboot
c:\adb\adb>
Indeed neither of them are able to mount. Am I mistaken when i read these logs it says that these "done" but they do not appear to be as the 0's imply.
Still no fix yet
Is it a probable solution to use the sdcard as a mounting point for these partitions ( /data, /cache)? I cant fully understand it yet but Ive seen some people somehow do this with internal memory and stuff with these specific partitons.