Database Users

[Q] N7 8GB Broken eMMC

I have a strange problem with my 8GB Nexus 7 and I hope, its not a hardware fault.
I buyed the Tablet in 08/2012 at googles playstore and installed CWM Recovery.
After Updating to Android 4.2 at 11/2012, the Tablet works 2 days without any Problems.
After a restart (battery was empty), the Tablet boots and stops at a screen for unlocking encrypted storage. It asks for a password.
Because i never entered a password, and never encrypt the Tablet, i try a wipe at CWM. It ends with an error message:
-- wiping data
Formatting /data
Error mounting /data
...
So i checked dmesg at ADB (cutted, full LOG is attached):
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 3.1.10-g52027f9 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 28 16:19:26 PDT 2012
<6>[ 7.684297] mmc1: new high speed SDIO card at address 0001
<6>[ 7.691530] [mmc]:mmc_rescan_try_freq:1892 mmc1: sdio completed
<6>[ 9.020863] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 9.021726] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts:
<6>[ 9.070219] cable_detection_work_handler(): vbus_active = 0 and is_active = 1
<6>[ 9.070227] The USB cable is connected
<3>[ 9.088156] mmcblk0: error -110 transferring data, sector 1391352, nr 64, cmd response 0x900, card status 0x4000d00
<3>[ 9.088301] end_request: I/O error, dev mmcblk0, sector 1391352
<3>[ 9.088379] end_request: I/O error, dev mmcblk0, sector 1391360
<3>[ 9.088515] end_request: I/O error, dev mmcblk0, sector 1391368
<3>[ 9.088590] end_request: I/O error, dev mmcblk0, sector 1391376
<3>[ 9.088725] end_request: I/O error, dev mmcblk0, sector 1391384
<3>[ 9.088800] end_request: I/O error, dev mmcblk0, sector 1391392
<3>[ 9.088935] end_request: I/O error, dev mmcblk0, sector 1391400
<3>[ 9.089011] end_request: I/O error, dev mmcblk0, sector 1391408
<3>[ 9.089177] Aborting journal on device mmcblk0p4-8.
<0>[ 9.090018] journal commit I/O error
<4>[ 28.937444] adbd (125): /proc/125/oom_adj is deprecated, please use /proc/125/oom_score_adj instead.
i tried to mount /dev/block/mmcblk0p9 with the following error:
Code:
<3>[ 1252.621408] EXT3-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (40)
<3>[ 1252.670984] EXT2-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (44)
<3>[ 1255.510979] mmcblk0: error -110 transferring data, sector 5997888, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.511068] end_request: I/O error, dev mmcblk0, sector 5997888
<4>[ 1255.511204] quiet_error: 2283 callbacks suppressed
<3>[ 1255.511279] Buffer I/O error on device mmcblk0p9, logical block 458792
<4>[ 1255.511412] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.511489] end_request: I/O error, dev mmcblk0, sector 5997896
<3>[ 1255.511624] Buffer I/O error on device mmcblk0p9, logical block 458793
<4>[ 1255.511755] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.511828] end_request: I/O error, dev mmcblk0, sector 5997904
<3>[ 1255.511962] Buffer I/O error on device mmcblk0p9, logical block 458794
<4>[ 1255.512036] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.512172] end_request: I/O error, dev mmcblk0, sector 5997912
<3>[ 1255.512247] Buffer I/O error on device mmcblk0p9, logical block 458795
<4>[ 1255.512379] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.512454] end_request: I/O error, dev mmcblk0, sector 5997920
<3>[ 1255.512588] Buffer I/O error on device mmcblk0p9, logical block 458796
<4>[ 1255.512661] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543050] mmcblk0: error -110 transferring data, sector 6526376, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.543191] end_request: I/O error, dev mmcblk0, sector 6526376
<3>[ 1255.543268] Buffer I/O error on device mmcblk0p9, logical block 524853
<4>[ 1255.543400] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543476] end_request: I/O error, dev mmcblk0, sector 6526384
<3>[ 1255.543607] Buffer I/O error on device mmcblk0p9, logical block 524854
<4>[ 1255.543679] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543811] end_request: I/O error, dev mmcblk0, sector 6526392
<3>[ 1255.543885] Buffer I/O error on device mmcblk0p9, logical block 524855
<4>[ 1255.544015] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.544089] end_request: I/O error, dev mmcblk0, sector 6526400
<3>[ 1255.544221] Buffer I/O error on device mmcblk0p9, logical block 524856
<4>[ 1255.544351] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.544426] end_request: I/O error, dev mmcblk0, sector 6526408
<3>[ 1255.544571] Buffer I/O error on device mmcblk0p9, logical block 524857
<4>[ 1255.544644] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.573641] mmcblk0: error -110 transferring data, sector 13861888, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.573780] end_request: I/O error, dev mmcblk0, sector 13861888
<3>[ 1255.573870] end_request: I/O error, dev mmcblk0, sector 13861896
<3>[ 1255.574004] end_request: I/O error, dev mmcblk0, sector 13861904
<3>[ 1255.574080] end_request: I/O error, dev mmcblk0, sector 13861912
<3>[ 1255.574215] end_request: I/O error, dev mmcblk0, sector 13861920
<3>[ 1255.583454] mmcblk0: error -110 transferring data, sector 13862120, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.583593] end_request: I/O error, dev mmcblk0, sector 13862120
<3>[ 1255.583732] end_request: I/O error, dev mmcblk0, sector 13862128
<3>[ 1255.583808] end_request: I/O error, dev mmcblk0, sector 13862136
<3>[ 1255.583944] end_request: I/O error, dev mmcblk0, sector 13862144
<3>[ 1255.584019] end_request: I/O error, dev mmcblk0, sector 13862152
<4>[ 1255.597238] JBD: recovery failed
<3>[ 1255.597322] EXT4-fs (mmcblk0p9): error loading journal
I tried to erase the Memory with "dd if=/dev/zero of=/dev/block/mmcblk0p9". Dmesg was flooding with:
Code:
<3>[ 150.817559] end_request: I/O error, dev mmcblk0, sector 2503504
<3>[ 150.817665] end_request: I/O error, dev mmcblk0, sector 2503512
<3>[ 150.817842] end_request: I/O error, dev mmcblk0, sector 2503520
Also fastboot flash recovery/system etc. wont work.
It looks like the eMMC Chip died and got Read-Only.
I backed up the data by mounting with "-o loop,ro,noexec,noload" and ADB Pull. The chip dont write any changes back.
Any suggestions to fix the eMMC Chip?
Thanks

I know you mentioned fastboot flash partition, what about
fastboot erase system
fastboot erase userdata
Sent from my Nexus 7 using Tapatalk HD

Fastboot runs without error, but no change after booting. System and Userdata are not erased. Android stop at: unlock decrypted storage.
Code:
[email protected]:~# fastboot erase system
erasing 'system'... OKAY
[email protected]:~# fastboot erase userdata
erasing 'userdata'... OKAY

XMChrizzz said:
Fastboot runs without error, but no change after booting. System and Userdata are not erased. Android stop at: unlock decrypted storage.
Code:
[email protected]:~# fastboot erase system
erasing 'system'... OKAY
[email protected]:~# fastboot erase userdata
erasing 'userdata'... OKAY
Click to expand...
Click to collapse
So if you do those commands up top and nothing else it still boots into Android? If that's the case if contact Google to see what to do. If you got it from the Play Store it should be covered under warranty
Sent from my Nexus 7 using Tapatalk HD

OP's problem seems like a hardware issue.
Sent from my Nexus 7 using Tapatalk HD

Okay thank you, i will contact google.

Is my Nexus 7 dead?

Okay, I have fastboot and ADB, the only way to get into recovery is through wugs toolkit. I have pushed a ROM to my phone but is says FAILED when I try to flash.
it says TWRP v 2.4.1.0 errors saying
Error flashing zip
Updating partition details...
E:Unable to mount ' /system'
E:Unable to mount ' /cache'
If I use fastboot to try and install recovery, boot, bootloads, or anything it fails as well.
C:\Program Files (x86)\WugFresh Development\data>fastboot devices
xxxxxxxxxxxxxxxxxxxx fastboot
C:\Program Files (x86)\WugFresh Development\data>fastboot erase boot
erasing 'boot'...
OKAY [ 2.531s]
finished. total time: 2.533s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootl
oader-grouper-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
C:\Program Files (x86)\WugFresh Development\data>fastboot -w update image-nakasi
-jop40d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: xxxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.585s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 0.760s
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>
(and I get the same for every file I try.
Any help is much appreciated.
Now this is my 4 year olds tablet and we woke up the other morning and it just wouldnt boot anymore. I did unlock it just for fun when we got it a couple months ago but I dont know why it would just not boot into the OS after two months.

In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools located in the /system/bin or /sbin folder of the TWRP boot to re-initialize the /system, /data partitions as necessary.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.

bftb0 said:
In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools on the /system/bin or /sbin folder of the TWRP boot to re-initialize those filesystems.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.
Click to expand...
Click to collapse
I went into fastboot
opened cmd
fastboot boot recovery.img
Recovery booted up
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # mount /system
mount /system
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/APP on /system failed:
No such file or directory
~ # mount /data
mount /data
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: N
o such file or directory
~ # # mount /system
# mount /system
~ # # mount /data
# mount /data
~ #
I tried to mount system and data in recovery and it didnt work...i tried cwm 6.0.2.3 and twrp 2.4.1.0
I see files in /sbin folder in recovery, how do I use those files?

well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted

bftb0 said:
well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted
Click to expand...
Click to collapse
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!

Skyler2Dope said:
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!
Click to expand...
Click to collapse
just type them in and hit the return key.
report any errors or successes, pls.

NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7

bradman117 said:
NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7
Click to expand...
Click to collapse
My partition is shot, I can't do anything with the toolkit. But I'll give it another go
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.198s
rebooting into bootloader...
OKAY [ 7.302s]
finished. total time: 7.303s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >

should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found

Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
add me on gtalk, [email protected]

did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously

bftb0 said:
did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously
Click to expand...
Click to collapse
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?

Skyler2Dope said:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?
Click to expand...
Click to collapse
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.

bftb0 said:
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.
Click to expand...
Click to collapse
I am using TWRP 2.4.1.0
ls -ld /dev/block/* gets me
C:\Program Files (x86)\WugFresh Development\data>adb shell ls -ld /dev/block/*
brw------- 1 root root 7, 0 Jan 2 05:41 /dev/block/loop0
brw------- 1 root root 7, 1 Jan 2 05:41 /dev/block/loop1
brw------- 1 root root 7, 2 Jan 2 05:41 /dev/block/loop2
brw------- 1 root root 7, 3 Jan 2 05:41 /dev/block/loop3
brw------- 1 root root 7, 4 Jan 2 05:41 /dev/block/loop4
brw------- 1 root root 7, 5 Jan 2 05:41 /dev/block/loop5
brw------- 1 root root 7, 6 Jan 2 05:41 /dev/block/loop6
brw------- 1 root root 7, 7 Jan 2 05:41 /dev/block/loop7
C:\Program Files (x86)\WugFresh Development\data>adb shell cat /proc/partitions
major minor #blocks name

.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?

bftb0 said:
.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?
Click to expand...
Click to collapse
<4>[ 2.271075] GTCO usb driver version: 2.00.0006
<6>[ 2.271234] usbcore: registered new interface driver hanwang
<6>[ 2.271401] usbcore: registered new interface driver kbtab
<6>[ 2.271531] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
<6>[ 2.271638] usbcore: registered new interface driver wacom
<6>[ 2.271769] wacom: v1.52:USB Wacom tablet driver
<4>[ 2.271841] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 2.272001] [ektf3k]:[ELAN] Start HW reset!
<4>[ 2.529906] [ektf3k]:The boot code is new!
<4>[ 2.709905] INOK=L
<5>[ 2.710168] smb347_charger: [cable_type_detect] Reg3F : 0x93
<5>[ 2.710486] smb347_charger: [cable_type_detect] Reg3E : 0x09
<4>[ 2.710561] Cable: CDP
<4>[ 2.710632] ========================================================
<4>[ 2.710765] battery_callback usb_cable_state = 3
<4>[ 2.710837] ========================================================
<4>[ 2.710978] inok_isr_work_function -
<6>[ 3.259898] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 3.260032] The USB cable is connected
<4>[ 3.310055] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:
55
<4>[ 3.310189] [ektf3k]:[elan] hello packet's rc = 0
<4>[ 3.521744] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xb018
<4>[ 3.523705] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x0078
<4>[ 3.525607] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00c6
<4>[ 3.546763] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3021
<4>[ 3.546901] [ektf3k]:[Elan] Max X=2111, Max Y=1279
<6>[ 3.547105] input: elan-touchscreen as /devices/virtual/input/input0
<4>[ 3.547345] [ektf3k]:The firmware was version 0xB018 and id:0x3021
<4>[ 3.547444] [ektf3k]: /proc/ektf_dbg created
<4>[ 3.547690] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrup
t mode
<4>[ 3.547877] [ektf3k]:[ELAN]misc_register finished!!
<6>[ 3.548014] elan-ktf3k 1-0010: Update power source to 1
<6>[ 3.548383] in function ____rmi_bus_init____
<6>[ 3.548495] rmi_bus_init: successfully registered RMI bus.
<6>[ 3.548667] rmi_spi_init: registering synaptics spi driver (ref=124)
<6>[ 3.548742] driver.owner = 0x0
<6>[ 3.548872] driver.name = rmi_spi
<6>[ 3.548944] id_table[0].name = rmi
<6>[ 3.549073] id_table[1].name = rmi_spi
<6>[ 3.549145] probe function ptr = 0xc064f2b8
<6>[ 3.549297] in function ____rmi_register_driver____
<6>[ 3.549389] in function ____rmi_get_function_handler____
<6>[ 3.549523] in function ____rmi_get_function_handler____
<6>[ 3.549596] in function ____rmi_get_function_handler____
<6>[ 3.549727] in function ____rmi_get_function_handler____
<6>[ 3.549798] in function ____rmi_get_function_handler____
<6>[ 3.549947] in function ____rmi_get_function_handler____
<6>[ 3.550242] lid_init+ #####
<5>[ 3.550316] hall_sensor: [lid_init] start LID init.....
<6>[ 3.550672] input: lid_input as /devices/virtual/input/input1
<6>[ 3.550875] Wake28 for irq=374
<6>[ 3.551041] Wake28 for irq=374
<6>[ 3.551114] Enabling wake28
<6>[ 3.581073] using rtc device, max77663-rtc, for alarms
<6>[ 3.581222] max77663-rtc max77663-rtc.0: rtc core: registered max77663-rtc
as rtc0
<6>[ 3.581783] i2c /dev entries driver
<6>[ 3.582240] Linux video capture interface: v2.00
<6>[ 3.582387] usbcore: registered new interface driver uvcvideo
<6>[ 3.582461] USB Video Class driver (1.1.1)
<6>[ 3.582652] trpc_sema_init: registered misc dev 10:45
<6>[ 3.582782] trpc_node_register: Adding 'local' to node list
<6>[ 3.583912] nvavp nvavp: allocated IOVM at ff00000 for AVP os
<6>[ 3.584248] tegra_camera tegra_camera: tegra_camera_probe
<6>[ 3.584603] sensor_init+ #####
<6>[ 3.584706] mi1040 sensor_probe
<6>[ 3.584912] sensor_init- #####
<6>[ 3.585084] al3010_init+ #####
<4>[ 3.585157] light sensor info : al3010 init
<4>[ 3.585991] light sensor info : al3010 probe successed
<6>[ 3.586127] al3010 2-001c: driver version 1.0 enabled
<4>[ 3.586355] i2c-core: driver [al3010] using legacy suspend method
<4>[ 3.586491] i2c-core: driver [al3010] using legacy resume method
<6>[ 3.586572] al3010_init- #####
<6>[ 3.586918] device-mapper: uevent: version 1.0.3
<6>[ 3.587154] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: d
[email protected]
<6>[ 3.587314] Bluetooth: HCI UART driver ver 2.2
<6>[ 3.587388] Bluetooth: HCI H4 protocol initialized
<6>[ 3.587461] Bluetooth: HCILL protocol initialized
<6>[ 3.587592] Bluetooth: BlueSleep Mode Driver Ver 1.1
<6>[ 3.587714] Wake7 for irq=390
<6>[ 3.588340] cpuidle: using governor ladder
<6>[ 3.588764] cpuidle: using governor menu
<6>[ 3.588884] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.589016] sdhci: Copyright(c) Pierre Ossman
<6>[ 3.589088] sdhci-pltfm: SDHCI platform and OF driver helper
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
<6>[ 3.600056] sdhci_tegra_init- #####
<7>[ 3.600422] Registered led device: statled
<6>[ 3.601595] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.603034] usbcore: registered new interface driver usbhid
<6>[ 3.603175] usbhid: USB HID core driver
<6>[ 3.603501] logger: created 256K log 'log_main'
<6>[ 3.603696] logger: created 256K log 'log_events'
<6>[ 3.603823] logger: created 256K log 'log_radio'
<6>[ 3.604008] logger: created 256K log 'log_system'
<6>[ 4.150710] inv_mpu_probe: Probe name mpu6050
<6>[ 4.150789] i2c i2c-2: MPU6050 is ready to go!
<4>[ 4.151024] i2c-core: driver [LTR_558ALS] using legacy suspend method
<4>[ 4.151100] i2c-core: driver [LTR_558ALS] using legacy resume method
<6>[ 4.152010] inv_ami306_probe: Probe name ami306
<6>[ 4.649906] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
<4>[ 4.690540] rt5640_modinit
<4>[ 4.690642] rt5640_i2c_probe
<4>[ 4.690753] i2c-core: driver [rt5640] using legacy suspend method
<4>[ 4.690885] i2c-core: driver [rt5640] using legacy resume method
<5>[ 4.710594] bq27541_get_psp status: Full ret= 0x0201
<5>[ 4.711314] bq27541_get_psp voltage_now= 4157000 uV
<5>[ 4.711963] bq27541_get_psp current_now= -172000 uA
<5>[ 4.712664] bq27541_get_capacity = 100% ret= 100
<5>[ 4.713310] bq27541_get_psp temperature= 289 (0.1óXC)
<6>[ 4.921173] DSP version code = 0x501a
<4>[ 4.921407] ************************realtek_ce_init_hwdep*****************
********************
<4>[ 4.921545] do_rt5640_dsp_set_mode mode=0
<6>[ 4.921628] rt5640 4-001c: w->name=SDI1 TX Mux
<6>[ 4.921701] rt5640 4-001c: path->name=IF2 path->connect=0
<6>[ 4.921833] rt5640 4-001c: path->name=IF1 path->connect=1
<6>[ 4.921978] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922113] rt5640 4-001c: path->name=DAC L1 Switch connect=1
<6>[ 4.922241] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922375] rt5640 4-001c: path->name=DAC L2 Switch connect=0
<6>[ 4.922655] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.922791] rt5640 4-001c: path->name=DAC R1 Switch connect=1
<6>[ 4.922918] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.923054] rt5640 4-001c: path->name=DAC R2 Switch connect=0
<6>[ 4.923333] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923410] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923538] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.923613] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923797] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923873] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924055] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.924130] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924311] rt5640 4-001c: w->name=Mono ADC MIXL
<6>[ 4.924386] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.924569] rt5640 4-001c: w->name=Mono ADC MIXR
<6>[ 4.924643] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.931835] asoc: rt5640-aif1 <-> tegra30-i2s.1 mapping ok
<6>[ 4.934256] asoc: dit-hifi <-> tegra30-spdif mapping ok
<6>[ 4.938087] asoc: dit-hifi <-> tegra30-i2s.3 mapping ok
<6>[ 4.938881] headset_init+ #####
<4>[ 4.938954] HEADSET: Headset detection init
<4>[ 4.939240] HEADSET: Headset detection mode
<4>[ 4.939315] HEADSET: Config Headset Button detection gpio
<7>[ 4.939389] gpio_request: gpio-186 (btn_INT) status -16
<4>[ 4.939521] HEADSET: Config uart<->headphone gpio
<4>[ 4.939592] HEADSET: Config Jack-in detection gpio
<4>[ 4.939722] HEADSET: Turn on micbias power
<6>[ 4.939800] Wake12 for irq=402
<6>[ 4.939942] Wake12 for irq=402
<6>[ 4.940073] Enabling wake12
<6>[ 4.940145] gpio bank wake found: wake12 for irq=119
<6>[ 4.940217] Enabling wake12
<4>[ 4.959895] HEADSET: Turn off micbias power
<4>[ 4.959977] HEADSET: Config LineOut detection gpio
<7>[ 4.960051] gpio_request: gpio-179 (lineout_int) status -16
<6>[ 4.960182] headset_init- #####
<6>[ 4.960253] ALSA device list:
<6>[ 4.960324] #0: HDA NVIDIA Tegra at 0x70038000 irq 113
<6>[ 4.960453] #1: tegra-rt5640
<6>[ 4.960734] oprofile: using arm/armv7-ca9
<6>[ 4.960914] GACT probability NOT on
<6>[ 4.961050] Mirror/redirect action on
<6>[ 4.961123] u32 classifier
<6>[ 4.961193] Actions configured
<6>[ 4.961325] Netfilter messages via NETLINK v0.30.
<6>[ 4.961462] nf_conntrack version 0.5.0 (15580 buckets, 62320 max)
<6>[ 4.961848] ctnetlink v0.93: registering with nfnetlink.
<6>[ 4.961958] NF_TPROXY: Transparent proxy support initialized, version 4.1.
0
<6>[ 4.962091] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>[ 4.962439] xt_time: kernel timezone is -0000
<6>[ 4.962722] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.962960] arp_tables: (C) 2002 David S. Miller
<6>[ 4.963069] TCP cubic registered
<6>[ 4.963314] NET: Registered protocol family 10
<6>[ 4.964057] Mobile IPv6
<6>[ 4.964153] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.964423] IPv6 over IPv4 tunneling driver
<6>[ 4.965272] NET: Registered protocol family 17
<6>[ 4.965424] NET: Registered protocol family 15
<6>[ 4.965602] Bluetooth: RFCOMM TTY layer initialized
<6>[ 4.965687] Bluetooth: RFCOMM socket layer initialized
<6>[ 4.965818] Bluetooth: RFCOMM ver 1.11
<6>[ 4.965891] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 4.966024] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 4.966249] NET: Registered protocol family 37
<6>[ 4.966326] VFP support v0.3: implementor 41 architecture 3 part 30 varian
t 9 rev 4
<5>[ 4.966494] Registering SWP/SWPB emulation handler
<4>[ 4.974201] Do not disable PWM clock when kernel inits
<4>[ 4.974289] Disabling clocks left on by bootloader:
<4>[ 4.974361] fuse_burn
<4>[ 4.974498] cclk_lp
<4>[ 4.974570] pll_x_out0
<4>[ 4.974642] pll_d2_out0
<4>[ 4.974712] pll_d_out0
<4>[ 4.974842] pll_p_out2
<4>[ 4.974918] pll_c_out1
<4>[ 4.974992] pll_m_out1
<6>[ 4.975161] CPU rate: 1000 MHz
<3>[ 4.975332] tegra_fuse_program_init: no vdd_fuse. fuse write disabled
<4>[ 4.975836] tegra3_dvfs: minimum cap.cbus rate 228000000 requires 1000 mV
<6>[ 4.976034] tegra dvfs: tegra sysfs cap interface is initialized
<6>[ 4.976374] tegra_actmon.emc: Completed initialization (0)
<6>[ 4.976649] tegra_actmon.avp: Completed initialization (0)
<4>[ 4.977660] regulator_init_complete: fixed_reg_cdc_en: incomplete constrai
nts, leaving on
<4>[ 4.977806] regulator_init_complete: max77663_ldo8: incomplete constraints
, leaving on
<4>[ 4.977945] regulator_init_complete: max77663_ldo4: incomplete constraints
, leaving on
<4>[ 4.978188] ## wifi_probe
<4>[ 4.978323] wifi_set_power = 1
<3>[ 4.978395] Powering on wifi
<4>[ 5.278776] wifi_set_carddetect = 1
<4>[ 5.278986]
<4>[ 5.278989] Dongle Host Driver, version 5.90.195.75
<4>[ 5.278993] Compiled in drivers/net/wireless/bcmdhd on Oct 14 2012 at 16:3
1:58
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
<4>[ 11.899466] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 11.900153] wl_create_event_handler thr:69 started
<4>[ 11.900863] p2p0: P2P Interface Registered
<4>[ 11.901081] dhd_attach thr:6a started
<4>[ 11.901224] dhd_attach thr:6b started
<4>[ 11.901371] dhd_attach thr:6c started
<4>[ 11.901653] wifi_get_mac_addr
<4>[ 11.902142] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 0
0:90:4c:11:22:33
<4>[ 11.902293] wifi_set_power = 0
<3>[ 11.902366] Powering off wifi
<6>[ 11.909977] [mmc]:mmc_rescan_try_freq:1903 mmc1: sdio completed
<4>[ 12.202737] =========== WLAN placed in RESET ========
<6>[ 12.202902] Wake24 for irq=392
<6>[ 12.203228] input: gpio-keys as /devices/platform/gpio-keys.0/input/input2
<6>[ 12.203445] gpio_keys: Released KEY_POWER
<6>[ 12.203523] gpio_keys: Released KEY_VOLUMEUP
<6>[ 12.203654] gpio_keys: Released KEY_VOLUMEDOWN
<6>[ 12.218332] max77663-rtc max77663-rtc.0: setting system clock to 2000-01-0
2 05:54:49 UTC (946792489)
<4>[ 12.218590] Warning: unable to open an initial console.
<6>[ 12.218875] Freeing init memory: 272K
<5>[ 12.225884] bq27541_get_psp status: Full ret= 0x0201
<5>[ 12.226540] bq27541_get_psp voltage_now= 4168000 uV
<5>[ 12.227244] bq27541_get_psp current_now= -10000 uA
<5>[ 12.227888] bq27541_get_capacity = 100% ret= 100
<5>[ 12.228534] bq27541_get_psp temperature= 289 (0.1óXC)
<3>[ 12.283042] init: Unable to open persistent property directory /data/prope
rty errno: 2
<3>[ 12.284820] android_usb: already disabled
<3>[ 12.285298] android_usb: already disabled
<6>[ 12.287073] adb_open
<6>[ 12.287178] adb_open(adbd)
<6>[ 12.287329] adb_bind_config
<6>[ 12.453844] android_work: did not send uevent (0 0 (null))
<5>[ 12.635110] bq27541_get_capacity = 100% ret= 100
<5>[ 12.635916] bq27541_get_psp status: Full ret= 0x0201
<6>[ 12.692380] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 12.719994] set_config : usb set config wake lock ++
<6>[ 12.720088] android_usb gadget: high speed config #1: android
<6>[ 12.720350] android_work: sent uevent USB_STATE=CONFIGURED
<6>[ 13.279938] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 13.280080] The USB cable is connected
<6>[ 13.280157] elan-ktf3k 1-0010: Update power source to 1
<4>[ 46.107840] adbd (118): /proc/118/oom_adj is deprecated, please use /proc/
118/oom_score_adj instead.
<5>[ 64.800603] bq27541_get_psp status: Full ret= 0x0200
<5>[ 64.801328] bq27541_get_psp voltage_now= 4173000 uV
<5>[ 64.801977] bq27541_get_psp current_now= 73000 uA
<5>[ 64.802680] bq27541_get_capacity = 100% ret= 100
<5>[ 64.803329] bq27541_get_psp temperature= 288 (0.1óXC)
<5>[ 72.747283] bq27541_get_capacity = 100% ret= 100
<5>[ 72.748015] bq27541_get_psp status: Full ret= 0x0200
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol

Skyler2Dope said:
<4>[ 2.271075]
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
...
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
Click to expand...
Click to collapse
ouch.
Skyler2Dope said:
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol
Click to expand...
Click to collapse
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.

bftb0 said:
ouch.
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.
Click to expand...
Click to collapse
I called and I am doing an RMA, Ill be shipping it off tomorrow or the next day. I will post back if they actually send me another one. Google was amazing by the way, a real pleasure to deal with. I appreciate all the time you and bradman put in tonight to help me figure this out. I REALLY REALLY REALLY appreciate your time and efforts! This has by far been the best experience I have had on any forum! You guys are awesome!

Well they received my device. Waiting to see if I get charged or get a new one.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

bftb0
You deserve a lot more 'thanks' in your posts for doing so much to help the OP.
Sent from my Nexus 7 using xda premium

Help! Stuck in bootloop ("E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC"

Help! Stuck in bootloop ("E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC"
something went wonky with my device when I was experimenting with unlocking/rooting earlier today. I've managed to get it stuck on the Google logo. I've tried flashing different versions of Google's stock roms through Nexus 7 ToolKit, Nexus Root Toolkit, and even Windows CMD using adb.exe numerous times (using a guide from androidcentral forums that someone on this forum linked to). When I boot into stock recovery, I get a strange set of messages. Perhaps this may have to do with my bootloop?
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)
E:failed to mount /cache (No such file or directory)"
I get pretty much the same errors when I soft flash CWMR, just in a slightly different order.
"E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)"
Through research, I found out that the cache errors are appearing because I haven't fully been able to boot my device. Could the "E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC" be the problem? I'm running out of ideas and patience!

so what are you trying to do now? flash a rom to at least get into desktop?
if you using CWMR, just boot into recovery and adb sideload a rom

jt.one said:
so what are you trying to do now? flash a rom to at least get into desktop?
if you using CWMR, just boot into recovery and adb sideload a rom
Click to expand...
Click to collapse
Yeah, I'm just trying to get out of this bootloop. And I just tried sideloading 2 different roms in CWMR. Got the same error as before both times.
">> INSTALLATION IN PROGRESS <<
E:Error in /tmp/update.zip
(Status 0)
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)"

It seems like my "E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC" is originating from /misc
More specifically, the MSC apparently relates to bootloader commands and other misc stuff.
Is my Nexus 7 boned?

To my knowledge MSC is never mounted and never contained a valid file system.
It might be used as part of the BCB (Boot Control Block) by the bootloader, but it isn't obvious to me why the custom recovery would be trying to *read* it. Write it - OK, maybe (reboot instructions).
How about
Code:
fastboot erase cache
fastboot format cache
fastboot erase system
fastboot format system
followed by a ROM flash?
[Edit] After further consideration, it is a bit odd that the recovery is claiming that the MSC raw device does not exist - that should be plumbed into the device tree after the kernel reads the emmc partition table during kernel initialization.
The weird thing is that if the partition table was borked (missing misc partition), I'm not sure that the bootloader would even behave correctly.
If you can get an adb shell to the custom recovery, you might try to get a kernel log immediately after booting, e.g.
Code:
adb shell cat /proc/kmsg > kmsg.text
or
Code:
adb shell dmesg > dmesg.text
and see if the kernel is having trouble reading the partition table (iirc the log enumerates all found partitions)

First 1/2 of the dmesg.txt
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 3.1.10-g6a965d1 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 13 15:14:42 PDT 2013
<4>[ 0.000000] CPU: ARMv7 Processor [412fc099] revision 9 (ARMv7), cr=10c5387d
<4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
<4>[ 0.000000] Machine: grouper
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<4>[ 0.000000] Ignoring unrecognised tag 0x41000801
<6>[ 0.000000] Found tegra_fbmem: [email protected]
<6>[ 0.000000] Tegra reserved memory:
<6>[ 0.000000] LP0: bddf9000 - bddfafff
<6>[ 0.000000] Bootloader framebuffer: abe01000 - ac5d1fff
<6>[ 0.000000] Framebuffer: bec00000 - bf4fffff
<6>[ 0.000000] 2nd Framebuffer: bf500000 - bfdfffff
<6>[ 0.000000] Carveout: 00000000 - 00000000
<6>[ 0.000000] Vpr: 00000000 - 00000000
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
<7>[ 0.000000] On node 0 totalpages: 256768
<7>[ 0.000000] free_area_init_node: node 0, pgdat c09f52c0, node_mem_map c11ce000
<7>[ 0.000000] Normal zone: 864 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 97440 pages, LIFO batch:31
<7>[ 0.000000] HighMem zone: 1436 pages used for memmap
<7>[ 0.000000] HighMem zone: 157028 pages, LIFO batch:31
<6>[ 0.000000] fuse_speedo_calib: ATE prog ver 3.8
<6>[ 0.000000] Tegra3: CPU Speedo ID 7, Soc Speedo ID 1
<6>[ 0.000000] Tegra Revision: A03 SKU: 0x83 CPU Process: 3 Core Process: 0
<6>[ 0.000000] tegra: PLLP fixed rate: 408000000
<4>[ 0.000000] Lowering cpu_lp maximum rate from 620000000 to 500000000
<4>[ 0.000000] Lowering sbus maximum rate from 378000000 to 267000000
<4>[ 0.000000] Lowering vi maximum rate from 470000000 to 409000000
<4>[ 0.000000] Lowering vde maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering mpe maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering 2d maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering epp maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering 3d maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering 3d2 maximum rate from 600000000 to 416000000
<4>[ 0.000000] Lowering se maximum rate from 625000000 to 416000000
<4>[ 0.000000] Lowering host1x maximum rate from 300000000 to 267000000
<4>[ 0.000000] Lowering cbus maximum rate from 700000000 to 416000000
<4>[ 0.000000] Lowering pll_c maximum rate from 1400000000 to 1066000000
<4>[ 0.000000] Lowering ndflash maximum rate from 240000000 to 200000000
<4>[ 0.000000] Lowering sbc1 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering sbc2 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering sbc3 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering sbc4 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering sbc5 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering sbc6 maximum rate from 160000000 to 100000000
<4>[ 0.000000] Lowering dsia maximum rate from 500000000 to 275000000
<4>[ 0.000000] Lowering dsib maximum rate from 500000000 to 275000000
<4>[ 0.000000] Lowering cpu_g maximum rate from 1700000000 to 1300000000
<6>[ 0.000000] tegra dvfs: VDD_CPU nominal 1025mV, scaling enabled
<6>[ 0.000000] tegra dvfs: VDD_CORE nominal 1200mV, scaling enabled
<6>[ 0.000000] L310 cache controller enabled
<6>[ 0.000000] l2x0: 8 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x7e080001, Cache size: 1048576 B
<6>[ 0.000000] PERCPU: Embedded 8 pages/cpu @c1ad7000 s11104 r8192 d13472 u32768
<7>[ 0.000000] pcpu-alloc: s11104 r8192 d13472 u32768 alloc=8*4096
<7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 254468
<5>[ 0.000000] Kernel command line: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 [email protected] android.commchip=0 vmalloc=512M androidboot.serialno=015d32203b2ffc09 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=61079551 androidboot.bootloader=4.23 androidboot.baseband=unknown
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 1003MB = 1003MB total
<5>[ 0.000000] Memory: 995612k/995612k available, 50916k reserved, 625844K highmem
<5>[ 0.000000] Virtual kernel memory layout:
<5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
<5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
<5>[ 0.000000] DMA : 0xff000000 - 0xffe00000 ( 14 MB)
<5>[ 0.000000] vmalloc : 0xd8800000 - 0xf8000000 ( 504 MB)
<5>[ 0.000000] lowmem : 0xc0000000 - 0xd8000000 ( 384 MB)
<5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
<5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
<5>[ 0.000000] .text : 0xc0008000 - 0xc0906a58 (9211 kB)
<5>[ 0.000000] .init : 0xc0907000 - 0xc0949b60 ( 267 kB)
<5>[ 0.000000] .data : 0xc094a000 - 0xc0a08b60 ( 763 kB)
<5>[ 0.000000] .bss : 0xc0a08b84 - 0xc0b8a1b0 (1542 kB)
<6>[ 0.000000] Preemptible hierarchical RCU implementation.
<6>[ 0.000000] NR_IRQS:800
<6>[ 0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms
<6>[ 0.000175] Calibrating delay loop... 1993.93 BogoMIPS (lpj=9969664)
<6>[ 0.060082] pid_max: default: 32768 minimum: 301
<6>[ 0.060241] Mount-cache hash table entries: 512
<6>[ 0.060843] Initializing cgroup subsys debug
<6>[ 0.060855] Initializing cgroup subsys cpuacct
<6>[ 0.060900] Initializing cgroup subsys freezer
<6>[ 0.060908] Initializing cgroup subsys bfqio
<6>[ 0.060931] CPU: Testing write buffer coherency: ok
<6>[ 0.061136] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
<4>[ 0.181307] CPU1: Booted secondary processor
<4>[ 0.241289] CPU2: Booted secondary processor
<4>[ 0.301290] CPU3: Booted secondary processor
<6>[ 0.321115] Brought up 4 CPUs
<6>[ 0.321125] SMP: Total of 4 processors activated (7975.73 BogoMIPS).
<6>[ 0.324390] print_constraints: dummy:
<6>[ 0.324572] NET: Registered protocol family 16
<6>[ 0.325308] host1x bus init
<6>[ 0.325368] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>[ 0.441359] [MISC]: pcbid=0x009e (projectid=0x00)
<4>[ 0.442633] The pingroup KB_ROW0 was configured to RSVD3 instead of <UNKNOWN>
<4>[ 0.443445] grouper_booting_info reg=0
<4>[ 0.443450] grouper_booting_info-normal
<6>[ 0.443844] grouper_edp_init: CPU regulator 6000 mA
<3>[ 0.443988] fiq_debugger_probe: could not install irq handler
<4>[ 0.444004] fiq_debugger: probe of fiq_debugger.0 failed with error -22
<6>[ 0.445083] ram_console: got buffer at beb00000, size 100000
<6>[ 0.445204] ram_console: uncorrectable error in header
<6>[ 0.445212] ram_console: no valid data in buffer (sig = 0xefee9baf)
<6>[ 0.455108] console [ram-1] enabled
<4>[ 0.581106] [ELAN] Touch dirver register
<6>[ 0.581186] grouper_modem_init
<6>[ 0.581258] Registering gpio keys
<4>[ 0.581724] grouper_camera_init: pmic_id= 0x0
<6>[ 0.581798] mi1040 i2c_register_board_info
<6>[ 0.581938] *** MPU START *** mpuirq_init...
<6>[ 0.582134] *** MPU END *** mpuirq_init...
<4>[ 0.582261] grouper_emc_init:mem_bootstrap_ad4=0 mem_bootstrap_ad5=0
<6>[ 0.582437] tegra: validated EMC DFS table
<4>[ 0.582514] grouper_emc_init: Nakasi_dvfs_Elpida_table_0430
<6>[ 0.582588] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
<6>[ 0.582718] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
<6>[ 0.582860] hw-breakpoint: maximum watchpoint size is 4 bytes.
<6>[ 0.583668] tegra_iovmm_register: added iovmm-smmu
<6>[ 0.590527] bio: create slab <bio-0> at 0
<6>[ 0.591206] vgaarb: loaded
<4>[ 0.591350] i2c-core: driver [tps6591x] using legacy suspend method
<4>[ 0.591485] i2c-core: driver [tps6591x] using legacy resume method
<4>[ 0.591580] i2c-core: driver [tps80031] using legacy suspend method
<4>[ 0.591713] i2c-core: driver [tps80031] using legacy resume method
<4>[ 0.591833] i2c-core: driver [ricoh583] using legacy suspend method
<4>[ 0.591964] i2c-core: driver [ricoh583] using legacy resume method
<5>[ 0.592333] SCSI subsystem initialized
<6>[ 0.593318] usbcore: registered new interface driver usbfs
<6>[ 0.593461] usbcore: registered new interface driver hub
<6>[ 0.593670] usbcore: registered new device driver usb
<6>[ 0.593814] tegra-otg tegra-otg: otg transceiver registered
<4>[ 0.595743] [MAX77663 probe]:CID4=23!
<6>[ 0.600507] Wake18 for irq=118
<6>[ 0.600583] Enabling wake18
<6>[ 0.602954] print_constraints: max77663_sd0: 600 <--> 3387 mV at 1025 mV normal standby
<6>[ 0.604174] print_constraints: max77663_sd1: 800 <--> 1587 mV at 1200 mV normal standby
<6>[ 0.605446] print_constraints: max77663_sd2: 1800 mV normal standby
<6>[ 0.606764] print_constraints: max77663_sd3: 600 <--> 3387 mV at 1350 mV normal standby
<6>[ 0.607986] print_constraints: max77663_ldo0: 800 <--> 2350 mV at 1000 mV normal standby
<6>[ 0.608137] set_supply: max77663_ldo0: supplied by max77663_sd3
<6>[ 0.609209] print_constraints: max77663_ldo1: 800 <--> 2350 mV at 1200 mV normal standby
<6>[ 0.609301] set_supply: max77663_ldo1: supplied by max77663_sd3
<6>[ 0.610590] print_constraints: max77663_ldo2: 800 <--> 3950 mV at 2800 mV normal standby
<6>[ 0.611824] print_constraints: max77663_ldo3: 800 <--> 3950 mV at 3000 mV normal standby
<6>[ 0.613164] print_constraints: max77663_ldo4: 800 <--> 1587 mV at 1000 mV normal standby
<6>[ 0.614177] print_constraints: max77663_ldo5: 800 <--> 2800 mV at 2800 mV normal standby
<6>[ 0.615206] print_constraints: max77663_ldo6: 800 <--> 3950 mV at 3300 mV normal standby
<6>[ 0.616188] print_constraints: max77663_ldo7: 800 <--> 3950 mV at 1200 mV normal standby
<6>[ 0.616338] set_supply: max77663_ldo7: supplied by max77663_sd3
<6>[ 0.617503] print_constraints: max77663_ldo8: 800 <--> 3950 mV at 1200 mV normal standby
<6>[ 0.617595] set_supply: max77663_ldo8: supplied by max77663_sd3
<6>[ 0.617975] max77663 register misc device for I2C stress test rc=0
<6>[ 0.623177] Advanced Linux Sound Architecture Driver Version 1.0.24.
<6>[ 0.623653] Bluetooth: Core ver 2.16
<6>[ 0.623756] NET: Registered protocol family 31
<6>[ 0.623888] Bluetooth: HCI device and connection manager initialized
<6>[ 0.623964] Bluetooth: HCI socket layer initialized
<6>[ 0.624096] Bluetooth: L2CAP socket layer initialized
<6>[ 0.624180] Bluetooth: SCO socket layer initialized
<6>[ 0.624570] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 0.624795] NFC: NFC Core ver 0.1
<6>[ 0.624899] NET: Registered protocol family 39
<6>[ 0.625179] print_constraints: fixed_reg_en_3v3_sys_a01: 3300 mV normal standby
<6>[ 0.625569] print_constraints: fixed_reg_en_avdd_hdmi_usb_a01: 3300 mV normal standby
<6>[ 0.625713] set_supply: fixed_reg_en_avdd_hdmi_usb_a01: supplied by fixed_reg_en_3v3_sys_a01
<6>[ 0.626025] print_constraints: fixed_reg_en_1v8_cam: 1800 mV normal standby
<6>[ 0.626111] set_supply: fixed_reg_en_1v8_cam: supplied by max77663_sd2
<6>[ 0.626434] print_constraints: fixed_reg_en_vddio_vid: 5000 mV normal standby
<6>[ 0.626720] print_constraints: fixed_reg_en_vdd_pnl: 3300 mV normal standby
<6>[ 0.626803] set_supply: fixed_reg_en_vdd_pnl: supplied by fixed_reg_en_3v3_sys_a01
<6>[ 0.627136] print_constraints: fixed_reg_en_vdd_com: 3300 mV normal standby
<6>[ 0.627278] set_supply: fixed_reg_en_vdd_com: supplied by fixed_reg_en_3v3_sys_a01
<6>[ 0.627541] print_constraints: fixed_reg_en_3v3_fuse: 3300 mV normal standby
<6>[ 0.627682] set_supply: fixed_reg_en_3v3_fuse: supplied by fixed_reg_en_3v3_sys_a01
<6>[ 0.627995] print_constraints: fixed_reg_cdc_en: 1200 mV normal standby
<6>[ 0.628085] set_supply: fixed_reg_cdc_en: supplied by max77663_sd2
<6>[ 0.628736] tegra: started io power detection dynamic control
<6>[ 0.628813] tegra: NO_IO_POWER setting 0x1200
<6>[ 0.628947] Switching to clocksource timer_us
<4>[ 0.629037] stop_machine_cpu_stop smp=1
<4>[ 0.629043] stop_machine_cpu_stop smp=2
<4>[ 0.629050] stop_machine_cpu_stop smp=3
<4>[ 0.629056] stop_machine_cpu_stop smp=0
<6>[ 0.631128] Switched to NOHz mode on CPU #0
<6>[ 0.631321] Switched to NOHz mode on CPU #2
<6>[ 0.631327] Switched to NOHz mode on CPU #3
<6>[ 0.631341] Switched to NOHz mode on CPU #1
<6>[ 0.639028] nvmap_page_pool_init: nvmap uc page pool size=31112 pages
<6>[ 0.735694] nvmap_page_pool_init: nvmap wc page pool size=31112 pages
<6>[ 0.831777] nvmap_page_pool_init: nvmap iwb page pool size=31112 pages
<6>[ 0.928486] tegra-nvmap tegra-nvmap: created carveout iram (255KiB)
<6>[ 0.929658] NET: Registered protocol family 2
<6>[ 0.929885] IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>[ 0.930344] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
<6>[ 0.931262] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
<6>[ 0.932189] TCP: Hash tables configured (established 65536 bind 65536)
<6>[ 0.932322] TCP reno registered
<6>[ 0.932398] UDP hash table entries: 256 (order: 1, 8192 bytes)
<6>[ 0.932539] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
<6>[ 0.932819] NET: Registered protocol family 1
<6>[ 0.933208] RPC: Registered named UNIX socket transport module.
<6>[ 0.933285] RPC: Registered udp transport module.
<6>[ 0.933416] RPC: Registered tcp transport module.
<6>[ 0.933487] RPC: Registered tcp NFSv4.1 backchannel transport module.
<7>[ 0.933621] PCI: CLS 0 bytes, default 32
<6>[ 0.933816] Unpacking initramfs...
<6>[ 1.011935] Freeing initrd memory: 1844K
<6>[ 1.012974] host1x host1x: initialized
<6>[ 1.013128] PMU: registered new PMU device of type 0
<6>[ 1.013600] Tegra auto-hotplug initialized: disabled
<6>[ 1.013746] cpu-tegra: init EDP limit: 1150 MHz
<4>[ 1.030388] highmem bounce pool size: 64 pages
<6>[ 1.030674] ashmem: initialized
<6>[ 1.031706] NTFS driver 2.1.30 [Flags: R/O].
<6>[ 1.031858] fuse init (API version 7.17)
<6>[ 1.032105] Registering char device tf_driver (122:0)
<6>[ 1.032270] TF : INFO 00000001 00:00:00.000 ------ ------ Kernel --------- Booting... (t=00:01:09.824) TFNXBF01.15.36932 /Trusted-Logic
<6>[ 1.033382] io scheduler noop registered
<6>[ 1.033458] io scheduler deadline registered
<6>[ 1.033636] io scheduler cfq registered (default)
<6>[ 1.033740] io scheduler bfq registered
<6>[ 1.034676] mpe mpe: initialized
<6>[ 1.035871] gr3d gr3d: initialized
<6>[ 1.036078] dsi dsi: initialized
<6>[ 1.036824] gr2d gr2d: initialized
<6>[ 1.037113] isp isp: initialized
<6>[ 1.037313] vi vi: initialized
<4>[ 1.037840] Disp: diff_msec= 69830
<6>[ 1.310174] tegradc tegradc.0: probed
<6>[ 1.310483] tegradc tegradc.0: probed
<6>[ 1.310764] Wake4 for irq=335
<6>[ 1.311213] nvhdcp: using "always on" policy.
<6>[ 1.311600] tegradc tegradc.1: probed
<6>[ 1.311901] tegradc tegradc.1: probed
<6>[ 1.312430] tegra_uart.1: ttyHS1 at MMIO 0x70006040 (irq = 69) is a TEGRA_UART
<6>[ 1.509419] Registered UART port ttyHS1
<6>[ 1.509565] tegra_uart.2: ttyHS2 at MMIO 0x70006200 (irq = 78) is a TEGRA_UART
<6>[ 1.669417] Registered UART port ttyHS2
<6>[ 1.669562] tegra_uart.3: ttyHS3 at MMIO 0x70006300 (irq = 122) is a TEGRA_UART
<6>[ 1.829417] Registered UART port ttyHS3
<6>[ 1.829559] tegra_uart.4: ttyHS4 at MMIO 0x70006400 (irq = 123) is a TEGRA_UART
<6>[ 1.989416] Registered UART port ttyHS4
<6>[ 1.989570] Initialized tegra uart driver
<6>[ 1.991980] loop: module loaded
<4>[ 1.992141] i2c-core: driver [apds9802als] using legacy suspend method
<4>[ 1.992274] i2c-core: driver [apds9802als] using legacy resume method
<4>[ 1.992423] nct1008_probe+
<6>[ 1.992511] nct1008 4-004c: no regulator found for vdd. Assuming vdd is always powered
<6>[ 1.994857] nct1008 register misc device for I2C stress test rc=0
<6>[ 1.995184] nct1008 4-004c: nct1008_probe: initialized
<4>[ 1.996259] nct1008_get_temp: ret temp=-31C
<4>[ 1.996480] nct1008_probe-
<4>[ 1.996647] i2c-core: driver [nct1008] using legacy suspend method
<4>[ 1.996720] i2c-core: driver [nct1008] using legacy resume method
<4>[ 1.996921] bcm4330_rfkill_probe: can't find bcm4330_32k_clk. assuming 32k clock to chip
<4>[ 1.997055] bcm4330_rfkill_probe : can't find reset gpio.
<3>[ 1.997293] vibrator_init:Couldn't get regulator vdd_vbrtr
<6>[ 1.997412] Loading pn544 driver
<6>[ 1.997627] pn544_probe : requesting IRQ 408
<6>[ 1.997960] PPP generic driver version 2.4.2
<6>[ 1.998181] PPP Deflate Compression module registered
<6>[ 1.998256] PPP BSD Compression module registered
<6>[ 2.000057] PPP MPPE Compression module registered
<6>[ 2.000195] NET: Registered protocol family 24
<6>[ 2.000611] tun: Universal TUN/TAP device driver, 1.6
<6>[ 2.000746] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>[ 2.000950] usbcore: registered new interface driver asix
<6>[ 2.001117] usbcore: registered new interface driver cdc_ether
<6>[ 2.001231] usbcore: registered new interface driver smsc95xx
<6>[ 2.001398] usbcore: registered new interface driver rndis_host
<6>[ 2.001501] usbcore: registered new interface driver cdc_subset
<6>[ 2.001642] cdc_ncm: 04-Aug-2011
<6>[ 2.001744] usbcore: registered new interface driver cdc_ncm
<6>[ 2.001920] usbcore: registered new interface driver bb_raw_ip_net
<6>[ 2.002036] usbcore: registered new interface driver rndis_wlan
<5>[ 2.002178] smb347_charger: [smb347_init] project_id=0, pcba_ver=3, dock_in_gpio=164
<6>[ 2.004500] [charger] Disable AICL, retval=93 setting=83
<6>[ 2.004965] [charger] set cahrger limmit, limit=900 retval =73 setting=73
<6>[ 2.005366] [charger] re-enable AICL, setting=93
<4>[ 2.030280] GPIO pin irq 388 requested ok, smb347_DOCK_IN# = H
<6>[ 2.030360] Wake1 for irq=393
<4>[ 2.030514] GPIO pin irq 393 requested ok, smb347_INOK = L
<4>[ 2.030625] i2c-core: driver [smb347] using legacy suspend method
<4>[ 2.030757] i2c-core: driver [smb347] using legacy resume method
<5>[ 2.030860] bq27541_probe + client->addr= 55
<5>[ 2.031594] bq27541_get_psp status: Discharging ret= 0x0201
<5>[ 2.032317] bq27541_get_psp voltage_now= 4146000 uV
<5>[ 2.032959] bq27541_get_capacity = 100% ret= 100
<5>[ 2.033673] bq27541_get_psp temperature= 260 (0.1¢XC)
<6>[ 2.034282] Wake25 for irq=372
<5>[ 2.034391] setup_low_battery_irq irq=372, LL_BAT_T30=0
<5>[ 2.034560] bq27541_get_psp status: Discharging ret= 0x0201
<6>[ 2.034669] Wake25 for irq=372
<6>[ 2.034798] Enabling wake25
<6>[ 2.034871] gpio bank wake found: wake25 for irq=87
<6>[ 2.034942] Enabling wake25
<6>[ 2.035118] The USB cable status = 0
<5>[ 2.035194] bq27541_probe - bq27541-battery driver registered
<4>[ 2.035297] i2c-core: driver [bq27541-battery] using legacy suspend method
<4>[ 2.035430] i2c-core: driver [bq27541-battery] using legacy resume method
<5>[ 2.035591] bq27541_get_psp voltage_now= 4146000 uV
<6>[ 2.035698] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<5>[ 2.036240] bq27541_get_capacity = 100% ret= 100
<5>[ 2.036884] bq27541_get_psp temperature= 260 (0.1¢XC)
<6>[ 2.037533] tegra-ehci tegra-ehci.1: Tegra EHCI Host Controller
<6>[ 2.037689] tegra-ehci tegra-ehci.1: new USB bus registered, assigned bus number 1
<4>[ 2.047962] nct1008_get_temp: ret temp=34C
<6>[ 2.059495] tegra-ehci tegra-ehci.1: irq 53, io mem 0x7d004000
<6>[ 2.079434] tegra-ehci tegra-ehci.1: USB 2.0 started, EHCI 1.00
<6>[ 2.079567] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 2.079703] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 2.079778] usb usb1: Product: Tegra EHCI Host Controller
<6>[ 2.079912] usb usb1: Manufacturer: Linux 3.1.10-g6a965d1 ehci_hcd
<6>[ 2.079985] usb usb1: SerialNumber: tegra-ehci.1
<6>[ 2.080387] hub 1-0:1.0: USB hub found
<6>[ 2.080472] hub 1-0:1.0: 1 port detected
<6>[ 2.080735] Wake40 for irq=53

2/2 of the dmesg.txt
<6>[ 2.080867] Enabling wake40
<6>[ 2.081107] usbcore: registered new interface driver cdc_acm
<6>[ 2.081181] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[ 2.081352] usbcore: registered new interface driver cdc_wdm
<6>[ 2.081483] Initializing USB Mass Storage driver...
<6>[ 2.081619] usbcore: registered new interface driver usb-storage
<6>[ 2.081752] USB Mass Storage support registered.
<6>[ 2.081876] usbcore: registered new interface driver libusual
<6>[ 2.082100] usbcore: registered new interface driver usbserial
<6>[ 2.082174] usbserial: USB Serial Driver core
<6>[ 2.085067] usbcore: registered new interface driver baseband_usb_58b_41_1
<6>[ 2.085241] USB Serial support registered for GSM modem (1-port)
<6>[ 2.085459] usbcore: registered new interface driver option
<6>[ 2.085533] option: v0.7.2:USB Driver for GSM modems
<6>[ 2.085688] USB Serial support registered for pl2303
<6>[ 2.085808] usbcore: registered new interface driver pl2303
<6>[ 2.085881] pl2303: Prolific PL2303 USB to serial adaptor driver
<6>[ 2.086013] NVidia Tegra High-Speed USB SOC Device Controller driver (Apr 20, 2007)
<6>[ 2.086146] read_hw_version project_id = 0X0, pcb_id = 0X3
<6>[ 2.086376] phy->instance = 0, phy->xcvr_setup_value = 58
<4>[ 2.086524] create_regulator: fixed_reg_en_avdd_hdmi_usb_a01: Failed to create debugfs directory
<6>[ 2.086600] tegra_usb_phy_open instance 0 MAX77663_IRQ_ACOK_RISING
<6>[ 2.089486] fsl-tegra-udc fsl-tegra-udc: usb_bat_chg regulator not registered: USB charging will not be enabled
<4>[ 2.101709] nct1008_get_temp: ret temp=34C
<6>[ 2.109434] tegra-otg tegra-otg: SUSPEND --> PERIPHERAL
<6>[ 2.109571] fsl_vbus_session(): vbus_active = 0 and is_active = 1
<6>[ 2.111645] android_usb gadget: Mass Storage Function, version: 2009/09/11
<6>[ 2.111782] android_usb gadget: Number of LUNs=1
<6>[ 2.111857] lun0: LUN: removable file: (no medium)
<4>[ 2.112149] Gadget Android: controller 'fsl-tegra-udc' not recognized
<6>[ 2.112230] android_usb gadget: android_usb ready
<6>[ 2.112362] fsl-tegra-udc: bind to driver android_usb
<6>[ 2.112568] usbcore: registered new interface driver xpad
<6>[ 2.112745] usbcore: registered new interface driver usb_acecad
<6>[ 2.112819] acecad: v3.2:USB Acecad Flair tablet driver
<6>[ 2.112981] usbcore: registered new interface driver aiptek
<6>[ 2.113054] aiptek: v2.3 (May 2, 2007):Aiptek HyperPen USB Tablet Driver (Linux 2.6.x)
<6>[ 2.113185] aiptek: Bryan W. Headley/Chris Atenasio/Cedric Brun/Rene van Paassen
<6>[ 2.113287] usbcore: registered new interface driver gtco
<4>[ 2.113416] GTCO usb driver version: 2.00.0006
<6>[ 2.113519] usbcore: registered new interface driver hanwang
<6>[ 2.113745] usbcore: registered new interface driver kbtab
<6>[ 2.113819] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
<6>[ 2.113984] usbcore: registered new interface driver wacom
<6>[ 2.114056] wacom: v1.52:USB Wacom tablet driver
<4>[ 2.114187] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 2.114346] [ektf3k]:[ELAN] Start HW reset!
<4>[ 2.369425] [ektf3k]:The boot code is new!
<6>[ 2.549424] INOK=L
<5>[ 2.549685] smb347_charger: [cable_type_detect] Reg39 : 0x10
<5>[ 2.549944] smb347_charger: [cable_type_detect] Reg3F : 0xc0
<5>[ 2.550075] smb347_charger: [cable_type_detect] USB_IN
<5>[ 2.550334] smb347_charger: [cable_type_detect] Reg3E : 0x0c
<6>[ 2.550466] Cable: SDP
<4>[ 2.550536] ========================================================
<4>[ 2.550666] battery_callback usb_cable_state = 1
<4>[ 2.550736] ========================================================
<4>[ 2.550867] battery_callback cable_wake_lock 5 sec...
<4>[ 2.550870]
<6>[ 3.109422] cable_detection_work_handler(): vbus_active = 0 and is_active = 1
<6>[ 3.109622] The USB cable is connected
<4>[ 3.149577] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:55
<4>[ 3.149709] [ektf3k]:[elan] hello packet's rc = 0
<4>[ 3.361262] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xb018
<4>[ 3.363223] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x0078
<4>[ 3.365126] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00c6
<4>[ 3.383043] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3021
<4>[ 3.383181] [ektf3k]:[Elan] Max X=2111, Max Y=1279
<6>[ 3.383380] input: elan-touchscreen as /devices/virtual/input/input0
<4>[ 3.383561] [ektf3k]:The firmware was version 0xB018 and id:0x3021
<4>[ 3.383659] [ektf3k]: /proc/ektf_dbg created
<4>[ 3.383913] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrupt mode
<4>[ 3.384101] [ektf3k]:[ELAN]misc_register finished!!
<6>[ 3.384179] elan-ktf3k 1-0010: Update power source to 1
<6>[ 3.384552] in function ____rmi_bus_init____
<6>[ 3.384657] rmi_bus_init: successfully registered RMI bus.
<6>[ 3.384828] rmi_spi_init: registering synaptics spi driver (ref=124)
<6>[ 3.384902] driver.owner = 0x0
<6>[ 3.385032] driver.name = rmi_spi
<6>[ 3.385104] id_table[0].name = rmi
<6>[ 3.385233] id_table[1].name = rmi_spi
<6>[ 3.385305] probe function ptr = 0xc066135c
<6>[ 3.385457] in function ____rmi_register_driver____
<6>[ 3.385551] in function ____rmi_get_function_handler____
<6>[ 3.385683] in function ____rmi_get_function_handler____
<6>[ 3.385755] in function ____rmi_get_function_handler____
<6>[ 3.385885] in function ____rmi_get_function_handler____
<6>[ 3.385957] in function ____rmi_get_function_handler____
<6>[ 3.386087] in function ____rmi_get_function_handler____
<6>[ 3.386381] lid_init+ #####
<5>[ 3.386454] hall_sensor: [lid_init] start LID init.....
<6>[ 3.386822] input: lid_input as /devices/virtual/input/input1
<6>[ 3.387027] Wake28 for irq=374
<6>[ 3.387135] Wake28 for irq=374
<6>[ 3.387207] Enabling wake28
<3>[ 3.387279] CAP1106: [cap1106_init] Cap1106 driver doesn't support this project
<6>[ 3.417283] using rtc device, max77663-rtc, for alarms
<6>[ 3.417374] max77663-rtc max77663-rtc.0: rtc core: registered max77663-rtc as rtc0
<6>[ 3.417974] i2c /dev entries driver
<6>[ 3.418433] Linux video capture interface: v2.00
<6>[ 3.418590] usbcore: registered new interface driver uvcvideo
<6>[ 3.418721] USB Video Class driver (1.1.1)
<6>[ 3.418858] trpc_sema_init: registered misc dev 10:45
<6>[ 3.419045] trpc_node_register: Adding 'local' to node list
<6>[ 3.420154] nvavp nvavp: allocated IOVM at ff00000 for AVP os
<6>[ 3.420538] tegra_camera tegra_camera: tegra_camera_probe
<6>[ 3.420835] sensor_init+ #####
<6>[ 3.420993] mi1040 sensor_probe
<6>[ 3.421204] sensor_init- #####
<6>[ 3.421375] al3010_init+ #####
<4>[ 3.421447] light sensor info : al3010 init
<4>[ 3.422336] light sensor info : al3010 probe successed
<6>[ 3.422412] al3010 2-001c: driver version 1.0 enabled
<4>[ 3.422696] i2c-core: driver [al3010] using legacy suspend method
<4>[ 3.422771] i2c-core: driver [al3010] using legacy resume method
<6>[ 3.422908] al3010_init- #####
<6>[ 3.423243] device-mapper: uevent: version 1.0.3
<6>[ 3.423427] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: [email protected]
<6>[ 3.423587] Bluetooth: HCI UART driver ver 2.2
<6>[ 3.423721] Bluetooth: HCI H4 protocol initialized
<6>[ 3.423793] Bluetooth: HCILL protocol initialized
<6>[ 3.423865] Bluetooth: BlueSleep Mode Driver Ver 1.1
<6>[ 3.424046] Wake7 for irq=390
<6>[ 3.424700] cpuidle: using governor ladder
<6>[ 3.425072] cpuidle: using governor menu
<6>[ 3.425252] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.425327] sdhci: Copyright(c) Pierre Ossman
<6>[ 3.425456] sdhci-pltfm: SDHCI platform and OF driver helper
<6>[ 3.425528] sdhci_tegra_init+ #####
<6>[ 3.425698] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported for sdhci-tegra.3
<4>[ 3.426851] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.428115] Registered led device: mmc0::
<6>[ 3.431508] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<6>[ 3.431700] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported for sdhci-tegra.2
<4>[ 3.432789] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.434026] Registered led device: mmc1::
<6>[ 3.436234] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
<6>[ 3.436405] sdhci_tegra_init- #####
<7>[ 3.436719] Registered led device: statled
<6>[ 3.438137] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.439658] usbcore: registered new interface driver usbhid
<6>[ 3.439860] usbhid: USB HID core driver
<6>[ 3.440175] logger: created 256K log 'log_main'
<6>[ 3.440305] logger: created 256K log 'log_events'
<6>[ 3.440489] logger: created 256K log 'log_radio'
<6>[ 3.440613] logger: created 256K log 'log_system'
<6>[ 3.531173] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 3.542706] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3a40000 prod_name HBG4e BOOT_MULTI 0x10
<6>[ 3.548773] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.548962] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.549328] mmcblk0: mmc0:0001 HBG4e 29.1 GiB
<6>[ 3.549602] mmcblk0boot0: mmc0:0001 HBG4e partition 1 2.00 MiB
<6>[ 3.549887] mmcblk0boot1: mmc0:0001 HBG4e partition 2 2.00 MiB
<6>[ 3.552271] mmcblk0: unknown partition table
<6>[ 3.557636] mmcblk0boot1: unknown partition table
<6>[ 3.560092] mmcblk0boot0: unknown partition table
<6>[ 3.560341] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
<6>[ 3.990200] inv_mpu_probe: Probe name mpu6050
<6>[ 3.990279] i2c i2c-2: MPU6050 is ready to go!
<4>[ 3.990524] i2c-core: driver [LTR_558ALS] using legacy suspend method
<4>[ 3.990599] i2c-core: driver [LTR_558ALS] using legacy resume method
<6>[ 3.991503] inv_ami306_probe: Probe name ami306
<6>[ 3.991610] RIL: [ril_init] RIL init
<3>[ 3.991742] RIL: [ril_init] Ril driver doesn't support this project
<6>[ 4.489423] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
<4>[ 4.530033] rt5640_modinit
<4>[ 4.530138] rt5640_i2c_probe
<5>[ 4.550337] bq27541_get_psp status: Full ret= 0x0201
<5>[ 4.551403] bq27541_get_psp voltage_now= 4155000 uV
<5>[ 4.552398] bq27541_get_capacity = 100% ret= 100
<5>[ 4.553394] bq27541_get_psp temperature= 260 (0.1¢XC)
<6>[ 4.672451] DSP version code = 0x501a
<4>[ 4.672689] ************************realtek_ce_init_hwdep*************************************
<4>[ 4.672830] do_rt5640_dsp_set_mode mode=0
<6>[ 4.672910] rt5640 4-001c: w->name=SDI1 TX Mux
<6>[ 4.673042] rt5640 4-001c: path->name=IF2 path->connect=0
<6>[ 4.673116] rt5640 4-001c: path->name=IF1 path->connect=1
<6>[ 4.673294] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.673371] rt5640 4-001c: path->name=DAC L1 Switch connect=1
<6>[ 4.673531] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.673606] rt5640 4-001c: path->name=DAC L2 Switch connect=0
<6>[ 4.673926] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.674002] rt5640 4-001c: path->name=DAC R1 Switch connect=1
<6>[ 4.674109] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.674244] rt5640 4-001c: path->name=DAC R2 Switch connect=0
<6>[ 4.674507] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.674642] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.674749] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.674882] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.674985] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.675118] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.675219] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.675352] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.675453] rt5640 4-001c: w->name=Mono ADC MIXL
<6>[ 4.675527] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.675684] rt5640 4-001c: w->name=Mono ADC MIXR
<6>[ 4.675759] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.683596] asoc: rt5640-aif1 <-> tegra30-i2s.1 mapping ok
<6>[ 4.686828] asoc: dit-hifi <-> tegra30-spdif mapping ok
<6>[ 4.691261] asoc: dit-hifi <-> tegra30-i2s.3 mapping ok
<6>[ 4.691990] headset_init+ #####
<4>[ 4.692123] HEADSET: Headset detection init
<4>[ 4.692462] HEADSET: Headset detection mode
<4>[ 4.692539] HEADSET: Config LineOut detection gpio
<7>[ 4.692671] gpio_request: gpio-179 (lineout_int) status -16
<4>[ 4.692744] HEADSET: Config Headset Button detection gpio
<7>[ 4.692874] gpio_request: gpio-186 (btn_INT) status -16
<4>[ 4.692945] HEADSET: Config uart<->headphone gpio
<4>[ 4.693073] HEADSET: Config Jack-in detection gpio
<4>[ 4.693144] HEADSET: Turn on micbias power
<6>[ 4.693221] Wake12 for irq=402
<6>[ 4.693401] Wake12 for irq=402
<6>[ 4.693471] Enabling wake12
<6>[ 4.693543] gpio bank wake found: wake12 for irq=119
<6>[ 4.693673] Enabling wake12
<4>[ 4.709423] HEADSET: Turn off micbias power
<6>[ 4.709514] headset_init- #####
<6>[ 4.709585] ALSA device list:
<6>[ 4.709714] #0: HDA NVIDIA Tegra at 0x70038000 irq 113
<6>[ 4.709786] #1: tegra-rt5640
<6>[ 4.710061] oprofile: using arm/armv7-ca9
<6>[ 4.710307] GACT probability NOT on
<6>[ 4.710384] Mirror/redirect action on
<6>[ 4.710457] u32 classifier
<6>[ 4.710587] Actions configured
<6>[ 4.710660] Netfilter messages via NETLINK v0.30.
<6>[ 4.710796] nf_conntrack version 0.5.0 (15585 buckets, 62340 max)
<6>[ 4.711182] ctnetlink v0.93: registering with nfnetlink.
<6>[ 4.711293] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
<6>[ 4.711425] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>[ 4.711764] xt_time: kernel timezone is -0000
<6>[ 4.712046] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.712301] arp_tables: (C) 2002 David S. Miller
<6>[ 4.712475] TCP cubic registered
<6>[ 4.712651] NET: Registered protocol family 10
<6>[ 4.713392] Mobile IPv6
<6>[ 4.713545] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.713769] IPv6 over IPv4 tunneling driver
<6>[ 4.714597] NET: Registered protocol family 17
<6>[ 4.714749] NET: Registered protocol family 15
<6>[ 4.714933] Bluetooth: RFCOMM TTY layer initialized
<6>[ 4.715078] Bluetooth: RFCOMM socket layer initialized
<6>[ 4.715151] Bluetooth: RFCOMM ver 1.11
<6>[ 4.715224] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 4.715357] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 4.715577] NET: Registered protocol family 37
<6>[ 4.715713] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
<5>[ 4.715877] Registering SWP/SWPB emulation handler
<4>[ 4.723555] Do not disable PWM clock when kernel inits
<4>[ 4.723644] Disabling clocks left on by bootloader:
<4>[ 4.723776] fuse_burn
<4>[ 4.723854] cclk_lp
<4>[ 4.723927] pll_x_out0
<4>[ 4.723999] pll_d2_out0
<4>[ 4.724129] pll_d_out0
<4>[ 4.724199] pll_p_out2
<4>[ 4.724272] pll_c_out1
<4>[ 4.724348] pll_m_out1
<6>[ 4.724579] CPU rate: 1000 MHz
<3>[ 4.724694] tegra_fuse_program_init: no vdd_fuse. fuse write disabled
<4>[ 4.725192] tegra3_dvfs: minimum cap.cbus rate 228000000 requires 1000 mV
<6>[ 4.725393] tegra dvfs: tegra sysfs cap interface is initialized
<6>[ 4.725799] tegra_actmon.emc: Completed initialization (0)
<6>[ 4.726018] tegra_actmon.avp: Completed initialization (0)
<4>[ 4.727037] regulator_init_complete: fixed_reg_cdc_en: incomplete constraints, leaving on
<4>[ 4.727124] regulator_init_complete: max77663_ldo8: incomplete constraints, leaving on
<4>[ 4.727260] regulator_init_complete: max77663_ldo4: incomplete constraints, leaving on
<4>[ 4.727557] ## wifi_probe
<4>[ 4.727633] wifi_set_power = 1
<3>[ 4.727706] Powering on wifi
<4>[ 5.028082] wifi_set_carddetect = 1
<4>[ 5.029484]
<4>[ 5.029487] Dongle Host Driver, version 5.90.195.104
<4>[ 5.029491] Compiled in drivers/net/wireless/bcmdhd on Apr 13 2013 at 15:14:32
<6>[ 5.073638] mmc1: new high speed SDIO card at address 0001
<4>[ 5.074430] F1 signature read @0x18000000=0x16044330
<4>[ 5.078070] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 5.078653] wl_create_event_handler thr:6c started
<4>[ 5.079457] p2p0: P2P Interface Registered
<4>[ 5.079601] dhd_attach thr:6d started
<4>[ 5.079733] dhd_attach thr:6e started
<4>[ 5.079926] dhd_attach thr:6f started
<4>[ 5.080048] dhd_attach thr:70 started
<4>[ 5.080673] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
<6>[ 5.080826] [mmc]:mmc_rescan_try_freq:1903 mmc1: sdio completed
<4>[ 5.080971] wifi_set_power = 0
<3>[ 5.081043] Powering off wifi
<4>[ 5.381445] =========== WLAN placed in RESET ========
<6>[ 5.381669] Wake24 for irq=392
<6>[ 5.381994] input: gpio-keys as /devices/platform/gpio-keys.0/input/input2
<6>[ 5.396821] max77663-rtc max77663-rtc.0: setting system clock to 2000-01-03 06:56:22 UTC (946882582)
<4>[ 5.396999] Warning: unable to open an initial console.
<6>[ 5.397319] Freeing init memory: 264K
<3>[ 5.400608] init: could not import file '/init.recovery.grouper.rc' from '/init.rc'
<5>[ 5.406176] bq27541_get_psp status: Full ret= 0x0201
<5>[ 5.406829] bq27541_get_psp voltage_now= 4155000 uV
<5>[ 5.407529] bq27541_get_capacity = 100% ret= 100
<5>[ 5.408172] bq27541_get_psp temperature= 260 (0.1¢XC)
<3>[ 5.461814] android_usb: already disabled
<3>[ 5.462223] init: Unable to open persistent property directory /data/property errno: 2
<4>[ 5.724677] Disp: diff_msec= 238
<3>[ 16.531891] android_usb: already disabled
<6>[ 16.533585] adb_open
<6>[ 16.533669] adb_open(adbd)
<6>[ 16.533798] adb_bind_config
<6>[ 16.636762] android_work: did not send uevent (0 0 (null))
<6>[ 16.701618] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 16.746169] set_config : usb set config wake lock ++
<6>[ 16.746261] android_usb gadget: high speed config #1: android
<6>[ 16.746527] android_work: sent uevent USB_STATE=CONFIGURED
<6>[ 17.529514] cable_detection_work_handler(): vbus_active = 0 and is_active = 1
<6>[ 17.529655] The USB cable is connected
<6>[ 17.529733] elan-ktf3k 1-0010: Update power source to 1
<4>[ 21.781088] adbd (125): /proc/125/oom_adj is deprecated, please use /proc/125/oom_score_adj instead.
<5>[ 42.079434] shutdown_enable_set bq27541_device->shutdown_disable = 0
<5>[ 64.640111] bq27541_get_psp status: Full ret= 0x0201
<5>[ 64.640762] bq27541_get_psp voltage_now= 4158000 uV
<5>[ 64.641404] bq27541_get_capacity = 100% ret= 100
<5>[ 64.642055] bq27541_get_psp temperature= 260 (0.1¢XC)
<3>[ 106.250122] init: untracked pid 147 exited
<5>[ 124.800146] bq27541_get_psp status: Full ret= 0x0200
<5>[ 124.800867] bq27541_get_psp voltage_now= 4158000 uV
<5>[ 124.801513] bq27541_get_capacity = 100% ret= 100
<5>[ 124.802162] bq27541_get_psp temperature= 260 (0.1¢XC)
<3>[ 161.752844] init: untracked pid 153 exited
<5>[ 184.960128] bq27541_get_psp status: Full ret= 0x0200
<5>[ 184.960838] bq27541_get_psp voltage_now= 4157000 uV
<5>[ 184.961480] bq27541_get_capacity = 100% ret= 100
<5>[ 184.962123] bq27541_get_psp temperature= 270 (0.1¢XC)
<3>[ 190.534361] init: untracked pid 156 exited
<3>[ 209.725481] init: untracked pid 159 exited

Have you succeed ?
Hi k91191,
Have you manage to bring back to live you phone because I managed to kill mine (ZTE V985 Tegra 3 device) and the error is the same ?

:cyclops:
LamqtaSpas said:
Hi k91191,
Have you manage to bring back to live you phone because I managed to kill mine (ZTE V985 Tegra 3 device) and the error is the same ?
Click to expand...
Click to collapse
Unfortunately not. I'm bringing this topic back up from the dead hoping someone can help me.

k91191 said:
:cyclops:
Unfortunately not. I'm bringing this topic back up from the dead hoping someone can help me.
Click to expand...
Click to collapse
Sorry k91191 for not getting back to this thread. I don't use e-mail notifications, so I slipped up on this one.
I just booted my grouper two times - once using TWRP 2.6.3.1 and once using a CyanogenMod 10.2 kernel (a nightly from 9/22). Here are the mmc- related kernel messages:
TWRP kernel (TWRP 2.6..3.1)
Code:
<4>[ 5.715260] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 5.716525] Registered led device: mmc0::
<6>[ 5.719914] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<4>[ 5.721257] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 5.722463] Registered led device: mmc1::
<6>[ 5.724691] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
<6>[ 5.797969] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 5.809412] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name MMC32G BOOT_MULTI 0x10
[b]<6>[ 5.811368] mmc0: new high speed DDR MMC card at address 0001
<6>[ 5.811573] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 5.811942] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 5.812175] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 5.812467] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
[color=green]<6>[ 5.814738] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9[/color]
<6>[ 5.816718] mmcblk0boot1: unknown partition table
<6>[ 5.817971] mmcblk0boot0: unknown partition table[/b]
<6>[ 5.818225] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
CyanogenMod kernel (20130922-Nightly)
Code:
<4>[ 3.493854] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.495082] Registered led device: mmc0::
<6>[ 3.498527] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<4>[ 3.499809] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.501001] Registered led device: mmc1::
<6>[ 3.503290] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
<6>[ 3.578428] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 3.589857] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name MMC32G BOOT_MULTI 0x10
[b]<6>[ 3.591774] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.592051] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.592365] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.592659] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.592886] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
[color=green]<6>[ 3.595089] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9[/color]
<6>[ 3.597134] mmcblk0boot1: unknown partition table
<6>[ 3.598279] mmcblk0boot0: unknown partition table[/b]
<6>[ 3.598530] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
... and now here is your kernel boot messages:
Code:
<4>[ 3.426851] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.428115] Registered led device: mmc0::
<6>[ 3.431508] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<4>[ 3.432789] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.434026] Registered led device: mmc1::
<6>[ 3.436234] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
<6>[ 3.531173] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 3.542706] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3a40000 prod_name HBG4e BOOT_MULTI 0x10
[b]<6>[ 3.548773] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.548962] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.549328] mmcblk0: mmc0:0001 HBG4e 29.1 GiB
<6>[ 3.549602] mmcblk0boot0: mmc0:0001 HBG4e partition 1 2.00 MiB
<6>[ 3.549887] mmcblk0boot1: mmc0:0001 HBG4e partition 2 2.00 MiB
[color=red]<6>[ 3.552271] mmcblk0: unknown partition table[/color]
<6>[ 3.557636] mmcblk0boot1: unknown partition table
<6>[ 3.560092] mmcblk0boot0: unknown partition table[/b]
<6>[ 3.560341] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
I wouldn't be very optimistic. That seems to suggest that your kernel can not detect ANY valid android partitions.
I note that you seem to have a eMMC Flash Memory chip from a different vendor than I (HBG4e vs. MMC32G). I doubt that is relevant, though.
I am not aware of a single report here in the N7 forums where someone actually altered or restored the eMMC partitioning.
I'm sure it can be done - but only by Asus (perhaps with an engineering bootloader, or using nvflash with knowledge of the security keys).
sorry.

Internal memory not working: host doesn't support card's voltages

A friend of mine got a new tablet and gave me his older S7-105.
He tried to upgrade to android 4.2.2 and repartition internal sd to have more internal space, and somewhere in the process his internal sd card seems to be dead.
After a couple of days reading this and some other forums, I have finally been able to install PAC-man 23 JB 4.2.2 rom, but all without external sd card. I tried to access the internal sd card from all systems: 2.1-upd1, 2.2.2 and 4.2.2, but no success.
I have also tried downgrading and zeroing the mbr with dd if=/dev/zero of=/dev/block/mmcblk0
but it just creates a 204mb file in /dev/block/mmcblk0 as /dev/block/mmcblk0 doesn't exist.
Now I have PAC-man 23 JB 4.2.2, and I have manually installed parted binaries.
This is what I get in dmesg related with mmc.
Code:
~/data/berserker.android.apps.sshdroid/home $ dmesg|grep -i mmc
[ 1.261768] [qsd8x50_init_mmc,4148] request GPIO 157 OK
[ 1.261927] [qsd8x50_init_mmc,4155] configure GPIO 157 OK
[ 4.133880] [vreg_mmc_control,3635] Switching ON vreg_mmc OK
[ 4.134412] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000002 sdccid=1 on=1
[ 4.142679] mmc0: Qualcomm MSM SDCC at 0x00000000a0300000 irq 24,221 dma 8
[ 4.149306] mmc0: 8 bit data mode disabled
[ 4.153476] mmc0: 4 bit data mode enabled
[ 4.157375] mmc0: polling status mode disabled
[ 4.161794] mmc0: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.168154] mmc0: Slot eject status = 0
[ 4.171863] mmc0: Power save feature enable = 1
[ 4.176492] mmc0: DM non-cached buffer at ffd52000, dma_addr 0x3fb93000
[ 4.182975] mmc0: DM cmd busaddr 0x3fb93000, cmdptr busaddr 0x3fb93c00
[ 4.203892] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000006 sdccid=2 on=1
[ 4.206968] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
[ 4.213593] mmc1: 8 bit data mode disabled
[ 4.217583] mmc1: 4 bit data mode enabled
[ 4.221663] mmc1: polling status mode disabled
[ 4.226000] mmc1: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.232341] mmc1: Slot eject status = 1
[ 4.236067] mmc1: Power save feature enable = 1
[ 4.240574] mmc1: DM non-cached buffer at ffd53000, dma_addr 0x3fb94000
[ 4.247282] mmc1: DM cmd busaddr 0x3fb94000, cmdptr busaddr 0x3fb94c00
[ 4.254142] mmc2: No card detect facilities available
[ 4.273889] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000006 sdccid=1 on=1
[ 4.293982] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=3 on=1
[ 4.333879] [msm_sdcc3_setup_power,4077] Switching ON vreg_emmc in msm_sdcc3_setup_power OK
[ 4.336856] mmc2: Qualcomm MSM SDCC at 0x00000000a0500000 irq 10,0 dma 8
[ 4.343490] mmc2: 8 bit data mode enabled
[ 4.347392] mmc2: 4 bit data mode disabled
[ 4.351562] mmc2: polling status mode enabled
[ 4.355814] mmc2: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.362151] mmc2: Slot eject status = 0
[ 4.365882] mmc2: Power save feature enable = 1
[ 4.370387] mmc2: DM non-cached buffer at ffd54000, dma_addr 0x3fb96000
[ 4.377093] mmc2: DM cmd busaddr 0x3fb96000, cmdptr busaddr 0x3fb96c00
[ 5.093877] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=1 on=1
[ 5.113877] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=1 on=1
[ 5.129089] mmc0: new high speed SDHC card at address b72f
[ 5.137774] mmcblk1: mmc0:b72f SU08G 7.40 GiB
[ 5.142280] mmcblk1: p1 p2
[ 5.313958] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 5.333916] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 6.686815] mmc2: host doesn't support card's voltages
[ 6.708055] mmc2: error -22 whilst initialising SDIO card
[ 7.862767] mmc2: host doesn't support card's voltages
[ 7.871566] EXT4-fs (mmcblk1p2): mounted filesystem without journal
[ 7.884177] mmc2: error -22 whilst initialising SDIO card
[ 9.036666] mmc2: host doesn't support card's voltages
[ 9.054071] mmc2: error -22 whilst initialising SDIO card
[ 10.196824] mmc2: host doesn't support card's voltages
[ 24.154689] mmc2: error -22 whilst initialising SDIO card
[ 25.214152] mmc1: Slot status change detected (0 -> 1)
[ 25.309190] mmc2: host doesn't support card's voltages
[ 25.324092] mmc2: error -22 whilst initialising SDIO card
[ 25.494016] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.514020] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.569839] mmc1: queuing CIS tuple 0x80 length 50
[ 25.592533] mmc1: queuing CIS tuple 0x80 length 7
[ 25.602561] mmc1: queuing CIS tuple 0x80 length 9
[ 25.610713] mmc1: queuing CIS tuple 0x80 length 6
[ 25.675273] mmc1: queuing CIS tuple 0x02 length 1
[ 25.694244] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.714010] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.725996] mmc1: new SDIO card at address 0001
[ 26.469183] mmc2: host doesn't support card's voltages
[ 26.484220] mmc2: error -22 whilst initialising SDIO card
[ 27.659404] mmc2: host doesn't support card's voltages
[ 27.674591] mmc2: error -22 whilst initialising SDIO card
[ 28.817352] mmc2: host doesn't support card's voltages
"host doesn't support card's voltages" seems to be the main error... this looks as a kernel config error.
My external 8gb SD card is properly detected (mmcblk1).
It has two partitions, mmcblk1 and mmcblk1, but app2sd is not working. /sd-ext is mounted. I'll have to study a bit more.
Here is some system information:
Code:
# ls -la /dev/block/mm*
brw------- 1 root root 179, 16 Sep 20 11:38 /dev/block/mmcblk1
brw------- 1 root root 179, 17 Sep 20 11:38 /dev/block/mmcblk1p1
brw------- 1 root root 179, 18 Sep 20 11:38 /dev/block/mmcblk1p2
# mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/mtdblock2 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock3 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk1p2 on /sd-ext type ext4 (rw,relatime,barrier=1,data=writeback)
/dev/block/vold/179:17 on /storage/sdcard0 type 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)
tmpfs on /storage/sdcard0/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 204.2M 84.0K 204.1M 0% /dev
tmpfs 204.2M 0 204.2M 0% /storage
tmpfs 204.2M 0 204.2M 0% /mnt/secure
tmpfs 204.2M 0 204.2M 0% /mnt/asec
tmpfs 204.2M 0 204.2M 0% /mnt/obb
tmpfs 204.2M 0 204.2M 0% /mnt/fuse
/dev/block/mtdblock2 250.0M 216.5M 33.5M 87% /system
/dev/block/mtdblock4 160.0M 96.1M 63.9M 60% /data
/dev/block/mtdblock3 33.0M 1.2M 31.8M 4% /cache
/dev/block/mmcblk1p2 3.8G 52.0K 3.6G 0% /sd-ext
/dev/block/vold/179:17 3.6G 860.9M 2.7G 23% /storage/sdcard0
# cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 0fa00000 00020000 "system"
mtd3: 02100000 00020000 "cache"
mtd4: 0a000000 00020000 "userdata"
mtd5: 00200000 00020000 "logo"
mtd6: 000e0000 00020000 "splash"
mtd7: 00200000 00020000 "misc"
# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 117554 3761718+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk1p2 117554 242560 4000201 83 Linux
Partition 2 does not end on cylinder boundary
# fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': No such file or directory
# uname -a
Linux localhost 2.6.32.9-ideos #1 PREEMPT Thu Aug 15 15:06:53 FET 2013 armv7l GNU/Linux
# cat /system/etc/vold.fstab
# Mounts the first usable partition of the specified device s7-105
dev_mount sdcard /storage/sdcard0 auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount usbdisk /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0/usb1
Could someone help me revive my internal sd?
I'm not sure but it might be a hardware problem.
It could also be some kernel problem, as I didn't see those mmc errors in dmesg with 2.1 or 2.2.2. (I coudn't access internal mmc anyway)
what other kernels can I try?
Thanks just for reading this long post!!

I'll need to install or build a kernel with CONFIG_MMC_DEBUG enabled to see what might be going on with more detail.
Which kernel sources and .config do you (devs) recomend to use for s7-105 on 4.2.2?

I just installed 2.1-upd1 from dload in external sd card.
After getting root and installling busybox and sshdroid I see the same error in dmesg:
Code:
# dmesg|grep -i mmc
<6>[ 0.270488] [qsd8x50_init_mmc,3928] request GPIO 157 OK
<6>[ 0.270553] [qsd8x50_init_mmc,3935] configure GPIO 157 OK
<3>[ 4.071736] get_emmc_state(): msm_rpc_call_reply succeed! proc=23, emmc_state=0x4000000, g_emmc_state = 4
<6>[ 4.300377] [vreg_mmc_control,3408] Switching ON vreg_mmc OK
<6>[ 4.320455] mmc0: Qualcomm MSM SDCC at 0x00000000a0300000 irq 24,221 dma 8
<6>[ 4.325593] mmc0: 8 bit data mode disabled
<6>[ 4.329672] mmc0: 4 bit data mode enabled
<6>[ 4.333712] mmc0: polling status mode disabled
<6>[ 4.338120] mmc0: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.344508] mmc0: Slot eject status = 0
<6>[ 4.348188] mmc0: Power save feature enable = 1
<6>[ 4.363768] mmc0: DM non-cached buffer at ffc09000, dma_addr 0x3ee05000
<6>[ 4.369093] mmc0: DM cmd busaddr 0x3ee05000, cmdptr busaddr 0x3ee05300
<6>[ 4.400529] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 4.401619] mmc1: 8 bit data mode disabled
<6>[ 4.405725] mmc1: 4 bit data mode enabled
<6>[ 4.409690] mmc1: polling status mode disabled
<6>[ 4.414191] mmc1: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.421695] mmc1: Slot eject status = 1
<6>[ 4.424232] mmc1: Power save feature enable = 1
<4>[ 4.428740] mmc0: host doesn't support card's voltages
<6>[ 4.433849] mmc1: DM non-cached buffer at ffc0a000, dma_addr 0x3ee10000
<6>[ 4.440464] mmc1: DM cmd busaddr 0x3ee10000, cmdptr busaddr 0x3ee10300
<3>[ 4.447673] mmc2: No card detect facilities available
<3>[ 4.452126] mmc0: error -22 whilst initialising SDIO card
<6>[ 4.530392] [msm_sdcc3_setup_power,3865] Switching ON vreg_emmc in msm_sdcc3_setup_power OK
<6>[ 4.533203] mmc2: Qualcomm MSM SDCC at 0x00000000a0500000 irq 10,0 dma 8
<6>[ 4.539794] mmc2: 8 bit data mode disabled
<6>[ 4.546097] mmc2: 4 bit data mode enabled
<6>[ 4.547890] mmc2: polling status mode enabled
<6>[ 4.554118] mmc2: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.558487] mmc2: Slot eject status = 0
<6>[ 4.565169] mmc2: Power save feature enable = 1
<6>[ 4.566816] mmc2: DM non-cached buffer at ffc0b000, dma_addr 0x3ecdd000
<6>[ 4.573473] mmc2: DM cmd busaddr 0x3ecdd000, cmdptr busaddr 0x3ecdd300
<6>[ 4.836918] mmc0: new high speed SDHC card at address b72f
<6>[ 4.843839] mmcblk0: mmc0:b72f SU08G 7.40 GiB
<6>[ 4.847051] mmcblk0:<6>android_bind
<7>[ 16.480324] mmc1: card_present 1
<7>[ 16.708405] mmc1: queuing CIS tuple 0x80 length 50
<7>[ 16.764824] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 16.788457] mmc1: queuing CIS tuple 0x80 length 9
<7>[ 16.806202] mmc1: queuing CIS tuple 0x80 length 6
<7>[ 16.813065] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 17.019966] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 17.027365] mmc1: queuing CIS tuple 0x02 length 1
<6>[ 17.238124] mmc1: new SDIO card at address 0001
#
# dd if=/dev/zero of=/dev/block/mmcblk1
/dev/block/mmcblk1: write error: No space left on device
424601+0 records in
424600+0 records out
217395200 bytes transferred in 7.517 secs (28920473 bytes/sec)
# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 217 MB, 217395200 bytes
255 heads, 63 sectors/track, 26 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/block/mmcblk1 doesn't contain a valid partition table
# fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 117554 3761718+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 117554 242560 4000201 83 Linux
Partition 2 does not end on cylinder boundary
host doesn't support card's voltages, same error than with 4.2.2
I have noticed that mmcblk0 and mmcblk1 are opposite than they were with 4.2.2!!!!

Maybe someone could post a full cwm backup of a clean 4.2.2 system with working internal and external sd?
I can create a ftp account to upload it to my cloud server, if needed.
I think there might be something wrong with some of my config files, which doesn't get overwritten when I flash a rom.
Some settings are kept, as language, so maybe the wrong partition information is passed from one installation to the other.

Contents of /system/etc/vold.conf are completely different in android 2.1, can someone post his /system/etc/vold.conf ?
This is mine:
Code:
# cat /system/etc/vold.conf | grep -v ^#
volume_sdcard {
media_path /devices/platform/msm_sdcc.1/mmc_host
media_type mmc
mount_point /sdcard2
ums_path /devices/platform/msm_hsusb/gadget/lun0
}
volume_sdcard3 {
media_path /devices/platform/msm_sdcc.3/mmc_host
media_type mmc
mount_point /sdcard
ums_path /devices/platform/msm_hsusb/gadget/lun1
}
volume_usb {
media_path /devices/platform/msm_hsusb_host.0/usb1
media_type usb
mount_point /data/disk/media/disk
}
volume_usb2 {
media_path /devices/platform/msm_hsusb_host.1/usb2
media_type usb
mount_point /data/disk/media/disk
}

ramoncio said:
...
Could someone help me revive my internal sd?
I'm not sure but it might be a hardware problem.
It could also be some kernel problem, as I didn't see those mmc errors in dmesg with 2.1 or 2.2.2. (I coudn't access internal mmc anyway)
what other kernels can I try?
Thanks just for reading this long post!!
Click to expand...
Click to collapse
It sure looks to be hardware related but hope I am wrong and you get your memory back!
Regards
J.

[Q] Flashed TWRP and now " Can't find ext4 filesystem" ?

Following the howto here. I flashed twrp-2.8.6.0-mako.img and then hilighted "Reboot" with the volume keys and selected "Recovery". TWRP booted, and there was a small text field that flashed by with some red text in it about "/cache" or something and then the phone rebooted. It's stuck now in a TWRP boot loop. I was able to get into the device shell over ADB while TWRP was busy looping around and found this in dmesg. Um, where do I go from here? I have a hunch I can probably mkfs.ext4 /dev/mmcblk0p23 and then TWRP will boot but it's just a gues; is there an official fix for this? Is mmcblk0p23 really hosed from flashing TWRP or is this a TWRP bug? I've installed TWRP on a few different devices and never had this happen before. Thanks!
Code:
<6>[ 2.949000] android_work: android_work: sent uevent USB_STATE=CONFIGURED
<3>[ 3.009308] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 3.040012] unplug_usbcheck_work: usb_vin : 4607444, max_voltage_mv=4360
<3>[ 3.089516] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.194109] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.270044] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.375156] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.459606] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 3.562276] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mode. Opts:
<7>[ 3.562643] SELinux: initialized (dev mmcblk0p22, type ext4), uses xattr
<6>[ 3.594140] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts:
<7>[ 3.594353] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<3>[ 3.704318] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.789684] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.884846] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.999938] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.103647] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.199725] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.304318] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.399664] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.998077] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.069708] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.667968] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.739722] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 6.346558] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 6.439554] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.028109] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.099710] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 7.129040] msm_ta_detect_work: USB exit ta detection - frindex
<3>[ 7.707828] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.799694] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 8.598992] mipi_lgit_lcd_off started
<6>[ 8.729040] mipi_lgit_lcd_off finished
<6>[ 8.729253] mipi_dsi_panel_power: mipi lcd function started status = 0
<6>[ 9.403784] mipi_dsi_panel_power: mipi lcd function started status = 1
<6>[ 9.405493] mipi_dsi_panel_power : reset start.
<6>[ 9.426644] mipi_lgit_lcd_on started
<6>[ 9.489211] mipi_lgit_lcd_on finished
<3>[ 9.796978] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 9.879536] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 9.961513] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.059697] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.155226] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.239707] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 10.329375] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts:
<7>[ 10.329620] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<3>[ 10.444407] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.519670] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.624752] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.699679] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.812604] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.889760] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.984465] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.069647] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.667907] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.739752] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 12.338074] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 12.429360] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.037906] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.139600] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.744819] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.819655] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 14.438242] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 14.529681] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 15.298977] mipi_lgit_lcd_off started
<6>[ 15.429055] mipi_lgit_lcd_off finished
<6>[ 15.429238] mipi_dsi_panel_power: mipi lcd function started status = 0
<6>[ 16.103982] mipi_dsi_panel_power: mipi lcd function started status = 1
<6>[ 16.105692] mipi_dsi_panel_power : reset start.
<6>[ 16.126842] mipi_lgit_lcd_on started
<6>[ 16.199114] mipi_lgit_lcd_on finished
<4>[ 16.457347] adbd (162): /proc/162/oom_adj is deprecated, please use /proc/162/oom_score_adj instead.

Hi,
- have you updated your android-sdk (adb, etc) to the newest version?
- bootloader unlocked?
- boot your device into the bootloader and reflash twrp. (In case you did not try again)
If something is not clear to you, just ask.
cheers

greg17477 said:
Hi,
- have you updated your android-sdk (adb, etc) to the newest version?
- bootloader unlocked?
- boot your device into the bootloader and reflash twrp. (In case you did not try again)
cheers
Click to expand...
Click to collapse
Just updated android SDK tools to v24.1.2 and SDK platform tools to v22 (latest) and re-flashed twrp. Still no go. /data is still messed up. I've flashed a Nexus 4 before (a year ago maybe? ) without having this problem and wondering if something changed in the newer models?

eris170 said:
<3>[ 14.529681] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
[/CODE]
Click to expand...
Click to collapse
Seems to be fixed now. I ran ADB shell while TWRP was "looping" and got back into the device. I formatted /dev/block/mmcblk0p23 with mke2fs which creates an EXT2 filesystem. There is no utility to create an EXT4 FS on the device... although now that I think about it, maybe I should have checked the /system directory which wasn't mount... ? Dunno... anyway android won't use the EXT2 filesystem as is so I used tune2fs utility to create the neccesary journals and "features" to make it match /dev/block/mmcblk022 (/system partition). After rebooting, the phone sat at the "flying dots" boot logo for about 5 mins. I figured it was likely still hosed so powered it off and got some sleep. This morning, I decided to let it boot for 10 mins before I would try something else. Surprisingly, it booted up within a couple mins to the Android 5.0 setup screen! Rebooting into TWRP Recovery now works too. Here is what I did in case it helps someone else:
Code:
# view kernel logs
~ # dmesg
<3>[ 30.179703] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
# figure out where "/data" is
~ # cat /etc/fstab
/dev/block/mmcblk0p21 /system ext4 rw
/dev/block/mmcblk0p23 /data ext4 rw
/dev/block/mmcblk0p22 /cache ext4 rw
# list features of "good" partition
~ # tune2fs -l /dev/block/mmcblk0p22 << good partition
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
# format ext2 FS onto p23
~ # mke2fs /dev/block/mmcblk0p23
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
863264 inodes, 3449600 blocks
172480 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3535798272
106 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
# just have an ext2 FS on p23 now
~ # dmesg
<4>[ 591.519548] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 591.547810] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 592.099709] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 592.127758] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
# Add FS features to p23.. I had to keep removing features here until it would succeed.
~ # tune2fs -O has_journal,ext_attr,resize_inode,filetype,needs_recovery,extent,sparse_super,large_file,uninit_bg /dev/block/mmcblk0p23
tune2fs 1.42.9 (28-Dec-2013)
Setting filesystem feature 'ext_attr' not supported.
~ # tune2fs -O has_journal,filetype,extent,sparse_super,large_file,uninit_bg /dev/block/mmcblk0p23
tune2fs 1.42.9 (28-Dec-2013)
Creating journal inode: done
# reboot and wait for a while to see what happens. After 10 mins, maybe try a reboot again??
~ # reboot