[Q] Bricked Nexus 5 - Partition table missing - Nexus 5 Q&A, Help & Troubleshooting

Hi all,
I think my wife's Nexus 5 is bricked... hoping it's not a hardware issue but I'm starting to think it is.
It started with the phone turning off when ever it felt like it... then one day it wouldn't boot completely and just be stuck on the flying google colors.
I called Google Support and they told me to wipe cache and wipe to factory defaults... It kinda didn't work and the support agent told me to reboot over and over again...
Now I'm trying to use fastboot to flash stock android and nothing seems to work... I'm getting write failures all over the place.
I then installed TWRP and booted to recovery and from there I can see that the NAND seems to be oddly small and with an invalid partition table...
dmesg | grep mmc
Code:
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.har
dware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 uart_console=e
nable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emm
c=true fastboot=true androidboot.serialno=0315c2990934d564 androidboot.bootloade
r=HHZ12h androidboot.baseband=msm bootreason=power_on androidboot.hardware.sku=D
820 androidboot.hardware.ddr=hynix androidboot.hardware.display=orise
<6>[ 1.515883] mmc0: SDCC Version: 0x00000038
<6>[ 1.518998] mmc0: bam physical base=0xf9884000
<6>[ 1.519201] mmc0: bam virtual base=0xf0378000
<6>[ 1.519766] mmc0: BAM device registered. bam_handle=0xed541c00
<6>[ 1.522174] mmc0: Qualcomm MSM SDCC-BAM at [mem 0xf9884000-0xf988afff flag
s 0x200] [irq 252 flags 0x400]
<6>[ 1.522602] mmc0: Qualcomm MSM SDCC-DML [mem 0xf98a4800-0xf98a48ff flags 0
x200]
<6>[ 1.523032] mmc0: id 2, nonremovable 0
<6>[ 1.527101] mmc0: Qualcomm MSM SDCC-core [mem 0xf98a4000-0xf98a47ff flags
0x200] [irq 157 flags 0x400],0 dma -1 dmacrcri -1
<6>[ 1.527176] mmc0: Controller capabilities: 0x00003ffe
<6>[ 1.527269] mmc0: 8 bit data mode disabled
<6>[ 1.527341] mmc0: 4 bit data mode enabled
<6>[ 1.527380] mmc0: polling status mode disabled
<6>[ 1.527419] mmc0: MMC clock 400000 -> 200000000 Hz, PCLK 0 Hz
<6>[ 1.527490] mmc0: Slot eject status = 1
<6>[ 1.527529] mmc0: Power save feature enable = 1
<6>[ 1.527601] mmc0: SPS-BAM data transfer mode available
<6>[ 1.532221] mmc1: no vmmc regulator found
<7>[ 1.533705] Registered led device: mmc1::
<6>[ 1.535212] mmc1: SDHCI controller on msm_sdcc.1 [msm_sdcc.1] using ADMA
<6>[ 1.655859] mmc1: new MMC card at address 0001
<6>[ 1.657207] mmcblk0: mmc1:0001 SDM032 30.6 MiB
<6>[ 1.661766] mmcblk0: unknown partition table
/sbin # ←[6n
fdisk (take not that disk seems to be only 32MB instead of 32GB)
Code:
/sbin # ←[6nfdisk -ul /dev/block/mmcblk0
fdisk -ul /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 32 MB, 32096256 bytes
4 heads, 16 sectors/track, 979 cylinders, total 62688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
mount
Code:
/sbin # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
cat /proc/partitions
Code:
cat /proc/partitions
major minor #blocks name
179 0 31344 mmcblk0
Does anyone know what is going on?

Try locking the bootloader, fastboot oem lock, and rebooting. Does it stay locked, fastboot oem device-info? If it didn't it's a good sign the nand is bad.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Try locking the bootloader, fastboot oem lock, and rebooting. Does it stay locked, fastboot oem device-info? If it didn't it's a good sign the nand is bad.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
it stays locked... is this something I can potentially fix then?
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) off-mode-charge: true
OKAY [ 0.031s]
finished. total time: 0.031s
Any ideas how I can proceed?

flickers said:
Hi all,
I think my wife's Nexus 5 is bricked... hoping it's not a hardware issue but I'm starting to think it is.
It started with the phone turning off when ever it felt like it... then one day it wouldn't boot completely and just be stuck on the flying google colors.
I called Google Support and they told me to wipe cache and wipe to factory defaults... It kinda didn't work and the support agent told me to reboot over and over again...
Now I'm trying to use fastboot to flash stock android and nothing seems to work... I'm getting write failures all over the place.
I then installed TWRP and booted to recovery and from there I can see that the NAND seems to be oddly small and with an invalid partition table...
dmesg | grep mmc
Code:
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.har
dware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 uart_console=e
nable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emm
c=true fastboot=true androidboot.serialno=0315c2990934d564 androidboot.bootloade
r=HHZ12h androidboot.baseband=msm bootreason=power_on androidboot.hardware.sku=D
820 androidboot.hardware.ddr=hynix androidboot.hardware.display=orise
<6>[ 1.515883] mmc0: SDCC Version: 0x00000038
<6>[ 1.518998] mmc0: bam physical base=0xf9884000
<6>[ 1.519201] mmc0: bam virtual base=0xf0378000
<6>[ 1.519766] mmc0: BAM device registered. bam_handle=0xed541c00
<6>[ 1.522174] mmc0: Qualcomm MSM SDCC-BAM at [mem 0xf9884000-0xf988afff flag
s 0x200] [irq 252 flags 0x400]
<6>[ 1.522602] mmc0: Qualcomm MSM SDCC-DML [mem 0xf98a4800-0xf98a48ff flags 0
x200]
<6>[ 1.523032] mmc0: id 2, nonremovable 0
<6>[ 1.527101] mmc0: Qualcomm MSM SDCC-core [mem 0xf98a4000-0xf98a47ff flags
0x200] [irq 157 flags 0x400],0 dma -1 dmacrcri -1
<6>[ 1.527176] mmc0: Controller capabilities: 0x00003ffe
<6>[ 1.527269] mmc0: 8 bit data mode disabled
<6>[ 1.527341] mmc0: 4 bit data mode enabled
<6>[ 1.527380] mmc0: polling status mode disabled
<6>[ 1.527419] mmc0: MMC clock 400000 -> 200000000 Hz, PCLK 0 Hz
<6>[ 1.527490] mmc0: Slot eject status = 1
<6>[ 1.527529] mmc0: Power save feature enable = 1
<6>[ 1.527601] mmc0: SPS-BAM data transfer mode available
<6>[ 1.532221] mmc1: no vmmc regulator found
<7>[ 1.533705] Registered led device: mmc1::
<6>[ 1.535212] mmc1: SDHCI controller on msm_sdcc.1 [msm_sdcc.1] using ADMA
<6>[ 1.655859] mmc1: new MMC card at address 0001
<6>[ 1.657207] mmcblk0: mmc1:0001 SDM032 30.6 MiB
<6>[ 1.661766] mmcblk0: unknown partition table
/sbin # ←[6n
fdisk (take not that disk seems to be only 32MB instead of 32GB)
Code:
/sbin # ←[6nfdisk -ul /dev/block/mmcblk0
fdisk -ul /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 32 MB, 32096256 bytes
4 heads, 16 sectors/track, 979 cylinders, total 62688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
mount
Code:
/sbin # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
cat /proc/partitions
Code:
cat /proc/partitions
major minor #blocks name
179 0 31344 mmcblk0
Does anyone know what is going on?
Click to expand...
Click to collapse
What is see is that the emmc turned into a 32 mb emmc. Which is interesting because your phone could not boot up if that happen.

Brainstorming: Could we, 1st, retrieve the partition table from another device, 2nd flash it back to this one?
What about LG flashtool? Would that try to restore partition table?
Or all of the above don't matter because the nand really fried?

beekay201 said:
Brainstorming: Could we, 1st, retrieve the partition table from another device, 2nd flash it back to this one?
What about LG flashtool? Would that try to restore partition table?
Or all of the above don't matter because the nand really fried?
Click to expand...
Click to collapse
Exactly what I was thinking...
I know about the LG Flashtool but as I'm not getting Qualcomm HS-USB QDLoader 9008 I'm avoiding that at the moment as I would rather not open the device...
I've also tried installing zip by copying it to /tmp in TWRP and installing from there... no success
I've tried parted and it's reporting pretty much the same as fdisk
I've tried blockdev
Code:
/sbin # ←[6nblockdev --getsize64 /dev/block/mmcblk0
blockdev --getsize64 /dev/block/mmcblk0
32096256
Code:
/sbin # ←[6nblockdev --getss /dev/block/mmcblk0
blockdev --getss /dev/block/mmcblk0
512
Code:
/sbin # ←[6nblockdev --getbsz /dev/block/mmcblk0
blockdev --getbsz /dev/block/mmcblk0
4096
I've tried stock recovery and CWM as well.. nothing is working as they can't mount anything
Any ideas?

This is a device you want to warranty and RUN not walk away from. You've corrupted blocks marked for your partition table (the very first blocks on the drive "physically" iirc) and that isn't going to change even if you can rebuild the file system through some voodoo blacksmith spell.
I only assume you're still in warranty because I notice you spoke with google support once already. If not... Well...
Once you've hurt flash memory bad enough that it starts losing blocks it only gets worse.

Related

[Q] uanble to boot

I have running a desire s with runndroid by the pvteam. I flashed it about a week ago.
This morning I found my phone locked up, It would not become active. I pulled the battery and attempted to reboot. it now just sits on the initial flash screen.
after a lot of mucking about in EXT4 recovery, I feel my problem is that hte system not mounting /data /system and /cache... it just won mount because when I attempt to mount in the recovery I just get an error.. in abd shell.... I get:
# mount -a
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
I have formatted, I have repartitioned and I have reflashed my room. It wont boot, these wont mount.
any ideas?
ah, I just had a brain wave...
#dmesg in the shell.... . I have lots of IO errors:
<3>[ 1660.224365] end_request: I/O error, dev mmcblk0, sector 1384779
<3>[ 1660.224456] end_request: I/O error, dev mmcblk0, sector 1384780
<3>[ 1660.224639] end_request: I/O error, dev mmcblk0, sector 1384781
<3>[ 1660.224761] end_request: I/O error, dev mmcblk0, sector 1384782
<3>[ 1660.224945] end_request: I/O error, dev mmcblk0, sector 1384783
the phone is bricked I assume? the internal NAN has failed?
ye, everytime I attempt to mount I get the following:
<3>[ 2225.836029] mmc0: DMA channel flushed (0x80000004)
<3>[ 2225.836425] Flush data: 0000c003 0bb03000 00000000 00400040 00100010 00000003
<6>[ 2225.837127] mmc0: Controller has been reset
<6>[ 2225.837585] mmc0: Worked around bug 1535304
<3>[ 2225.838256] mmcblk0: error -110 sending read command, response 0x40ff8080
<4>[ 2225.838653] mmcblk0: retrying using single block read
<3>[ 2225.840332] mmc0: DMA channel flushed (0x80000004)
<3>[ 2225.840698] Flush data: 0000c003 0bb03000 00000000 00400040 00080008 00000003
<6>[ 2225.841430] mmc0: Controller has been reset
<6>[ 2225.841857] mmc0: Worked around bug 1535304
<3>[ 2225.848571] mmcblk0: error -110 sending status comand
<3>[ 2225.848937] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[ 2225.849945] mmcblk0: error -5 transferring data, sector 1343490, nr 2, card status 0x0
<6>[ 2225.850585] mmc0: reinit card
<4>[ 2225.850952] mmc0: Starting deferred resume
<6>[ 2228.035705] mmc0: Deferred resume failed
<3>[ 2228.035827] end_request: I/O error, dev mmcblk0, sector 1343490
<3>[ 2228.036041] EXT3-fs (mmcblk0p26): error: unable to read superblock
<3>[ 2228.036560] mmc_blk_issue_rq failed!!
<3>[ 2228.037750] mmc0: DMA channel flushed (0x80000004)
<3>[ 2228.037841] Flush data: 0000c003 0bb03000 00000000 00400040 00100010 00000003
<6>[ 2228.038116] mmc0: Controller has been reset
<6>[ 2228.038299] mmc0: Worked around bug 1535304
<3>[ 2228.038482] mmcblk0: error -110 sending read command, response 0x40ff8080
<4>[ 2228.038604] mmcblk0: retrying using single block read
<3>[ 2228.039764] mmc0: DMA channel flushed (0x80000004)
<3>[ 2228.039855] Flush data: 0000c003 0bb03000 00000000 00400040 00080008 00000003
<6>[ 2228.040130] mmc0: Controller has been reset
<6>[ 2228.040283] mmc0: Worked around bug 1535304
<3>[ 2228.046295] mmcblk0: error -110 sending status comand
<3>[ 2228.046478] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[ 2228.046752] mmcblk0: error -5 transferring data, sector 1343490, nr 2, card status 0x0
<6>[ 2228.046844] mmc0: reinit card
<4>[ 2228.047027] mmc0: Starting deferred resume
<6>[ 2230.288024] mmc0: Deferred resume failed
<3>[ 2230.288421] end_request: I/O error, dev mmcblk0, sector 1343490
<3>[ 2230.289123] EXT2-fs (mmcblk0p26): error: unable to read superblock
<3>[ 2230.290466] mmc_blk_issue_rq failed!!
<3>[ 2230.292266] mmc0: DMA channel flushed (0x80000004)
<3>[ 2230.292633] Flush data: 0000c003 0bb03000 00000000 00400040 00100010 00000003
<6>[ 2230.293365] mmc0: Controller has been reset
<6>[ 2230.293792] mmc0: Worked around bug 1535304
<3>[ 2230.294494] mmcblk0: error -110 sending read command, response 0x40ff8080
<4>[ 2230.294860] mmcblk0: retrying using single block read
<3>[ 2230.296569] mmc0: DMA channel flushed (0x80000004)
<3>[ 2230.296936] Flush data: 0000c003 0bb03000 00000000 00400040 00080008 00000003
<6>[ 2230.297668] mmc0: Controller has been reset
<6>[ 2230.298095] mmc0: Worked around bug 1535304
<3>[ 2230.304412] mmcblk0: error -110 sending status comand
<3>[ 2230.305084] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[ 2230.306060] mmcblk0: error -5 transferring data, sector 1343490, nr 2, card status 0x0
<6>[ 2230.306457] mmc0: reinit card
<4>[ 2230.306793] mmc0: Starting deferred resume
<6>[ 2232.540161] mmc0: Deferred resume failed
<3>[ 2232.540283] end_request: I/O error, dev mmcblk0, sector 1343490
<3>[ 2232.540496] EXT4-fs (mmcblk0p26): unable to read superblock
<3>[ 2232.540954] mmc_blk_issue_rq failed!!
<3>[ 2232.542236] mmc0: DMA channel flushed (0x80000004)
<3>[ 2232.542327] Flush data: 0000c003 0bb03000 00000000 00400040 00080008 00000003
<6>[ 2232.542602] mmc0: Controller has been reset
<6>[ 2232.542755] mmc0: Worked around bug 1535304
<3>[ 2232.548767] mmcblk0: error -110 sending status comand
<3>[ 2232.548950] mmcblk0: error -110 sending read/write command, response 0x40ff8080, card status 0x0
<3>[ 2232.549255] mmcblk0: error -5 transferring data, sector 1343488, nr 1, card status 0x0
<6>[ 2232.549346] mmc0: reinit card
<4>[ 2232.549438] mmc0: Starting deferred resume
<6>[ 2234.632263] mmc0: Deferred resume failed
<3>[ 2234.632629] end_request: I/O error, dev mmcblk0, sector 1343488
<3>[ 2234.633361] FAT: unable to read boot sector
<3>[ 2234.635650] mmc_blk_issue_rq failed!!
Unfortunately it looks like your right, I'm just wondering why you still can access recovery, to be sure pls make a reboot to recovery and straight afterwards execute dmesg | grep mmc0.
You can try to replace your bootloader and check if it works, even take a look at the index, at the bottom is a thread named read this before going to replace emmc chip.
And pls tell what bootloader you're using.
Swyped from my Desire S far away from my PC (maybe)
# dmesg | grep mmc0
<3>[ 7.411163] mmc0: No card detect facilities available
<6>[ 7.411682] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.411926] mmc0: Platform slot type: MMC
<6>[ 7.412048] mmc0: 4 bit data mode disabled
<6>[ 7.412292] mmc0: 8 bit data mode enabled
<6>[ 7.412414] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.412658] mmc0: Slot eject status = 0
<6>[ 7.412780] mmc0: Power save feature enable = 1
<6>[ 7.412902] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c250000
<6>[ 7.413146] mmc0: DM cmd busaddr 0x0c250000, cmdptr busaddr 0x0c250300
<6>[ 7.566467] mmc0: new high speed MMC card at address 0001
<6>[ 7.567840] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 67.214080] mmc0: Failed to get card ready i = 122482
<6>[ 67.214263] mmc0: reinit card
<4>[ 67.214355] mmc0: Starting deferred resume
<6>[ 69.626434] mmc0: Deferred resume failed
is the dmesg output.... asi you can see....... can not mount it.. .:\
and as your post says"
http://forum.xda-developers.com/showthread.php?t=1284196
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Than you internal memory (eMMC) is corrupted i.e. your chip is "fried". This is a hardware issue (reference here) and the chip has to be replaced. Sorry, no other solutions available.
thanks for your help!
Sry, missed it at the op, but this will always stay a riddle to me.
How the hell is it possible to access a recovery located on mmc0 without a working mmc0, anyways.
There is a thread introducing a replacement emmc confirmed working out of the box, if you like to repair it yourself and save a lot of money
Swyped from my Desire S far away from my PC (maybe)
Tectas said:
Sry, missed it at the op, but this will always stay a riddle to me.
How the hell is it possible to access a recovery located on mmc0 without a working mmc0, anyways.
There is a thread introducing a replacement emmc confirmed working out of the box, if you like to repair it yourself and save a lot of money
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
yeah, you got me!
um, do you have a link to that mentioned thread? I will at the worst have a look at replacing it....
http://forum.xda-developers.com/showthread.php?t=1543310
Swyped from my Desire S far away from my PC (maybe)
But found something additional, maybe you're willing to try because you got nothing to lose^^
The only thing a bit tricky could be to find the right backup location of the superblock.
How to restore superblock http://linuxpoison.blogspot.com/2007/10/how-to-recover-damaged-superblock.html?m=1
Edit: Here is how to find the backup locations of the superblock http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition/
Swyped from my Desire S far away from my PC (maybe)

external sdcard wont mount

Ok guys I know I'm behind the times, but I'm running Tiamat 3.2 (Xoom of course).
Suddenly my external sd card isnt mounting. I has previously mounted.
Firing up adb and looking at dmesg, I see the following:
mmcblk0: 14.9 Gb <---Which should be external sdcard
mmcblk1: 29.7 Gb <---Internal sdcard
mount only shows the following:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/pdsb /pds ext2 ro,noatime,nodiratime,barrier=1,data=writeback 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm also finding this on searching dmesg:
sh-4.1# dmesg | grep mmc
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: [email protected] [email protected]
00 video=tegrafb [email protected] console=ttyS0,115200n8 usbcore.old_scheme_fi
rst=1 tegraboot=sdmmc gpt gpt_sector=0x03b6efff mot_prod=1 androidboot.serialno=
170061c241615357 hw_rev=p3 androidboot.modelno=MZ604 product_type=w lp0_vec=8192
@0x1e7f1020 androidboot.bootloader=1045 androidboot.carrier=wifi-only lcd_manfid
=AUO mem_vid=0x101 mem_pid=0x5454 androidboot.carrier=wifi-only product_type=w
<4>[ 12.376571] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376592] mmc0: no vmmc regulator found
<7>[ 12.376680] Registered led device: mmc0::
<6>[ 12.376763] mmc0: SDHCI controller on tegra [sdhci-tegra.1] using ADMA
<4>[ 12.376835] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376856] mmc1: no vmmc regulator found
<7>[ 12.376943] Registered led device: mmc1::
<6>[ 12.377030] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 12.377141] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 12.377158] mmc2: no vmmc regulator found
<7>[ 12.377243] Registered led device: mmc2::
<6>[ 12.377340] mmc2: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<6>[ 12.518127] mmc1: new high speed SDHC card at address b368
<6>[ 12.518364] mmcblk0: mmc1:b368 H1510 14.9 GiB
<6>[ 12.521455] mmcblk0: p1
<6>[ 12.620506] mmc2: new high speed MMC card at address 0001
<6>[ 12.620792] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<6>[ 12.627027] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpani
c) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 12.718736] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode
. Opts: (null)
<7>[ 15.302617] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570874
<7>[ 15.302724] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570873
<7>[ 15.302760] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570851
<6>[ 15.302792] EXT4-fs (mmcblk1p10): 3 orphan inodes deleted
<6>[ 15.302805] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 15.313298] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mod
e. Opts: noauto_da_alloc
<6>[ 20.318570] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 20.319437] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode
. Opts: noauto_da_alloc
<6>[ 20.324635] EXT4-fs (mmcblk1p2): mounted filesystem without journal. Opts:
(null)
<6>[ 42.616835] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.213691] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.215912] EXT4-fs (mmcblk1p10): re-mounted. Opts: (null)
<6>[ 46.020452] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.054467] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.085089] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<4>[ 119.330601] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 119.330686] mmc0: new high speed SDIO card at address 0001
<3>[ 125.914203] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1660.225502] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1665.431378] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1673.260399] FAT: Filesystem error (dev mmcblk0p1)
Obviously there is a Filesystem error on the device. What do I do to rectify the error?
I've tried to mount manually but this is what I get:
sh-4.1# mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
<v/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
mount: I/O error
Really, why don't you upgrade? I think you will be much happier. An upgrade to an EOS ICS build will probably fix your sd mounting problem, unless, of course, the sd card is bad or not seated properly.

Cannot access external SD card

Hi everbody,
Yesterday I received two Transcend 8GB microSDHC cards (Class 4, TS8GUSDHC4) and I wanted to use them with my rooted EEE pad transformer. I've formatted the card using fdisk (with fat32, "c" in fdisk). Then, I copied a jpg to the SD card, but my tablet couldn't open it.
I've checked /Removable but it was empty. I went into the adb shell as root. "dmesg" gave me the following:
Code:
<6>[ 4545.116710] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.117412] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.117802] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.118197] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.118870] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.138425] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.139115] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.139476] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.142621] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.142997] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.143644] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.281748] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.282439] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.282814] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.288602] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.289014] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.290014] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.292451] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.292846] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.293509] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.293896] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.294568] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.294955] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.295618] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.296006] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.296677] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.298838] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.299529] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.299896] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.304242] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.304627] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.305003] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.305677] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.327467] [mmc]:mmc_rescan:1786 mmc1: gpio_69:1 rescan_disable 0
<6>[ 4545.482018] [mmc]:mmc_rescan:1868 mmc1: extend_wakelock 1
Not sure what is happening here, but no device seems to be mounted. With the card inserted, I also ran "df ":
Code:
Filesystem Size Used Free Blksize
/dev 360M 32K 360M 4096
/mnt/asec 360M 0K 360M 4096
/mnt/obb 360M 0K 360M 4096
/system 503M 459M 44M 4096
/data 13G 7G 5G 4096
/cache 521M 22M 498M 4096
/Removable 360M 0K 360M 4096
/mnt/sdcard 13G 7G 5G 4096
And "mount":
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /data ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nodelalloc,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Can somebody help me getting my SD card to work? Is this card simply not compatible or is something else wrong?
I've searched the forums, but I couldn't find the answer anywhere.
Thanks a bunch!
May be try that MMC in some other device like a phone...
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
May be try that MMC in some other device like a phone...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.
chronozphere said:
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.
Click to expand...
Click to collapse
Thanks, I needed a good laugh
Everyone starts some-where, MicroSDHC cards are evil in that respect
I have the sameproblem...icant mount sd card...howto
Enviado desde mi Transformer TF101 usando Tapatalk 2
chronozphere said:
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.
Click to expand...
Click to collapse
I used to think the SD card reader on my laptop was poorly designed as i needed tweezers to pull out the card, then one day i pushed it in and it clicked then the thing flew out, good times :laugh:

[HINT] How Stickmount (and others...) are working with Android 4.2

Hello Guys,
I was very disappointed as I saw that in stickmount the mounting in 4.2 was fixed, and no solution can be found, how that was done.
I found the "magic" which chainfire uses.
Well, as we all should know, we can mount with adb and all apps can access the files.
If you mount as root WITHOUT adb, for example in an terminal, the Terminal-App can access the files, but no another app.
So I explored a bit Stickmount and also installed a rootlogger app. First I thought, it has something to do with the permissions or where it is mountend.
Then I found it. (For the germans: "Ich bin aus allen Wolken gefallen" )
The magic all behind that is, to start a "system service" which android knows.
Stickmount writes the shell-commands in "/system/bin/debuggerd" and runs the shell-file with "start debuggerd"
The "start" and "stop" operates a bit higher in the levels then other apps.. (like adb) so they can mount the devices for all apps.
This also works for cifs. I tested it on my Nexus 7.
I am open-mindend for any questions and hope some mounting-applications that stopped working with android 4.2 can be fixed now.
Best regards
vorcers
PS: I didn't found any information about this, so I started this thread. Please correct me, If I am wrong.
PPS: Sorry for my bad english.
EDIT:
The main mistake is, that with the debuggerd method, it is really really necessary to mount within /data/media/0. NOT within /storage!! Otherwise only the current opened app can see the files!
That's great news, vorcers! I hope, that cifsmanager gets updated asap! Maybe you should direct the attention of the developer to this solution of the problem.
Greetings, Hugo
Hm I looked a bit into the cifs manager... This app wasn't updated since over one year. Maybe the developer isn't active anymore.
I also think about something like a universalmounter.. With the otg things and cifs and NFS. Maybe also sshfs? But I can't compile the NFS and cifs modules for all devices. This need to be done by the owners... I could this only do for the nexus 7 and galaxy nexus. (Maybe for i9001 with ivendor's jelly bean)
vorcers,
thanks for this information. But what do you mean by 'Stickmount writes the shell-commands in "/system/bin/debuggerd"' ?
/system/bin/debuggerd seems to be a binary file. How can we write shell commands in it ?
Thanks.
mrmrmrmr said:
vorcers,
thanks for this information. But what do you mean by 'Stickmount writes the shell-commands in "/system/bin/debuggerd"' ?
/system/bin/debuggerd seems to be a binary file. How can we write shell commands in it ?
Thanks.
Click to expand...
Click to collapse
anybody who could comment on that ?
thanks.
I wish i could make mount work on Cryptonite on Cm 10.1. Facing same mount problem right now.
if only Vorcers could see my question...
I bet he has the answer
I saw your post.
mrmrmrmr said:
if only Vorcers could see my question...
I bet he has the answer
Click to expand...
Click to collapse
I already posted a further explanation in another Thread. (Link)
I post it here again. I hope this helps you.
vorcers said:
(For germans: "Bitte nagelt mich nicht darauf fest" (Auf die Informationen) Sorry, I don't know the english phrase for this...)
The "debuggerd" is an "debugger daemon". It can be started with "start debuggerd" and stopped with "stop debuggerd". I think errors at excecution are posted in dmesg or logcat.
The main thought behind this, that the debuggerd is started by "start" with higher privileges even then our normal su. (Or it does mount something, I don't know) So, if you backup the original /system/bin/debuggerd and write your own commands into that file and start it via "start debuggerd" these commands are executed with these "high privileges". For example, if you write these content in debuggerd and start it, the share should be available for all apps. (Well, only if "others" have r (? wx ?) permissions on server...)
/system/bin/debuggerd
Code:
#!/bin/sh
busybox mount -t cifs //server/share /mnt/sdcard/mnt -o username=max,password=mustermann)
You can also mount devices with this method...
Well, you can't use this with the manager, because the manager needs to be changed to support this.
I hope this helps you.
Click to expand...
Click to collapse
Hi Vorcers,
Thanks for your reply. I justtried this but couldn't succeed.
I have a copy of the /syste/bin/debuggerd, and I have the commands I'd like to start with "start debuggerd" in a file named /system/bin/debuggered.mount.
Then I have a Gscript script which calls the "start debuggerd" command.
/system/bin/debuggerd:
Code:
#!/bin/sh
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/data/com.gameloft.android.ANMP.GloftN3HM
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.GAND.GloftKRHP /sdcard/Android/data/com.gameloft.android.GAND.GloftKRHP
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.rockstar.gta3 /sdcard/Android/data/com.rockstar.gta3
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftA7HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftA7HM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftKRHM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftKRHM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftN3HM
busybox mount -o bind /storage/usbdisk/N7/gameloft /sdcard/gameloft
Gscript script:
Code:
busybox mount -o remount -w /system
cp /system/bin/debuggerd /system/bin/debuggerd.ydk
cp /system/bin/debuggerd.mount /system/bin/debuggerd
start debuggerd
stop debuggerd
cp /system/bin/debuggerd.ydk /system/bin/debuggerd
busybox mount -o remount -r /system
I don't know where my mistake is. I also couldn't find a way to diagnose.
Could you please let me know how I can fix ?
Could it be that debuggerd cannot be copied over (overwritten)? Have you tried mv instead of cp?
Edit: nevermind. Tried all that with mv instead of cp in the terminal emulator, and got nowhere as well. Sorry.
mrmrmrmr said:
[snip]
Click to expand...
Click to collapse
Can you provide the "dmesg" output after you tried this?
And also, it shouldn't have any effect, but leave out the stop command?
I suggest to run this:
Code:
busybox mount -o remount -w /system
cp /system/bin/debuggerd /system/bin/debuggerd.ydk
cp /system/bin/debuggerd.mount /system/bin/debuggerd
start debuggerd
By hand and write the dmesg output after the start command here. I am testing such things with an sshd server... It is the easiest. I use this server: https://play.google.com/store/apps/details?id=me.shkschneider.dropbearserver2
Ok; did as advised through the SSH server:
Code:
130|[email protected]:/system/bin # busybox mount -o remount -w /system
[email protected]:/system/bin # cp /system/bin/debuggerd /system/bin/debuggerd.ydk
[email protected]:/system/bin # cp /system/bin/debuggerd.mount /system/bin/debuggerd
[email protected]:/system/bin # start debuggerd
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin # cat debuggerd
#!/bin/sh
mount
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/data/com.gameloft.android.ANMP.GloftN3HM
mount
sleep 1
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.GAND.GloftKRHP /sdcard/Android/data/com.gameloft.android.GAND.GloftKRHP
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.rockstar.gta3 /sdcard/Android/data/com.rockstar.gta3
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftA7HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftA7HM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftKRHM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftKRHM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftN3HM
busybox mount -o bind /storage/usbdisk/N7/gameloft /sdcard/gameloft
[email protected]:/system/bin #
[email protected]:/system/bin #
dmesg:
Code:
[ 308.593540] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 308.593739] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 308.593849] usb usb2: Product: Tegra EHCI Host Controller
[ 308.594041] usb usb2: Manufacturer: Linux 3.1.10-faux123-grouper-00895-ga842db8 ehci_hcd
[ 308.594148] usb usb2: SerialNumber: tegra-ehci.0
[ 308.595469] hub 2-0:1.0: USB hub found
[ 308.595600] hub 2-0:1.0: 1 port detected
[ 308.596199] Wake39 for irq=52
[ 308.596393] Enabling wake39
[ 309.693303] usb 2-1: new high speed USB device number 2 using tegra-ehci
[ 309.728447] usb 2-1: New USB device found, idVendor=05e3, idProduct=0736
[ 309.728588] usb 2-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[ 309.728813] usb 2-1: Product: USB Storage
[ 309.728937] usb 2-1: Manufacturer: Generic
[ 309.729060] usb 2-1: SerialNumber: 000000000272
[ 309.731639] scsi0 : usb-storage 2-1:1.0
[ 309.826667] tegra_dvfs: voltage 1200 too high for dvfs on cpu_g
[ 309.826871] cpu-tegra: Failed to set cpu frequency to 1400000 kHz
[ 310.003278] INOK=L
[ 310.003630] smb347_charger: [cable_type_detect] Reg39 : 0x10
[ 310.004045] smb347_charger: [cable_type_detect] Reg3F : 0x81
[ 310.004383] smb347_charger: [cable_type_detect] Reg3E : 0x0e
[ 310.004572] Cable: SDP2 host mode charging
[ 310.004674] ========================================================
[ 310.004860] battery_callback usb_cable_state = 1
[ 310.004961] ========================================================
[ 310.005146] battery_callback cable_wake_lock 5 sec...
[ 310.005152]
[ 310.005376] elan-ktf3k 1-0010: Update power source to 1
[ 310.008230] bq27541_get_capacity = 29% ret= 33
[ 310.009171] bq27541_get_psp voltage_now= 3729000 uV
[ 310.010174] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 310.011209] bq27541_get_psp status: Charging ret= 0x0181
[ 310.735079] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 0272 PQ: 0 ANSI: 0
[ 310.736076] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 310.894390] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 310.895868] sd 0:0:0:0: [sda] Write Protect is off
[ 310.895985] sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
[ 310.897500] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.897695] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.903110] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.903351] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.917896] sda: sda1
[ 310.923288] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.923404] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.923593] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 312.004076] bq27541_get_psp status: Charging ret= 0x0181
[ 312.004985] bq27541_get_psp voltage_now= 3750000 uV
[ 312.006516] bq27541_get_capacity = 29% ret= 33
[ 312.007374] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 312.011419] bq27541_get_capacity = 29% ret= 33
[ 312.012459] bq27541_get_psp voltage_now= 3750000 uV
[ 312.013534] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 312.014422] bq27541_get_psp status: Charging ret= 0x0181
[ 312.044011] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 312.328237] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 313.501145] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 313.564481] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 314.555979] init: untracked pid 4652 exited
[ 314.789968] init: untracked pid 4654 exited
[ 314.912327] init: untracked pid 4708 exited
[ 315.138358] init: untracked pid 4711 exited
[ 344.523435] binder: 1069:2048 transaction failed 29189, size 4-0
[ 344.523555] binder: send failed reply for transaction 13169, target dead
[ 349.723016] request_suspend_state: sleep (0->3) at 349589817028 (2013-01-08 21:45:32.731926998 UTC)
[ 349.723293] early_suspend: call handlers
[ 349.742941] [ektf3k]:[elan] elan_ktf3k_ts_suspend: enter
[ 349.743631] stop_drawing_early_suspended
[ 349.752516] tegra_pwm tegra_pwm.0: pwm_disable called on disabled PWM
[ 349.752714] grouper_panel_early_suspended
[ 349.752814] al3010_early_suspend+
[ 349.753308] al3010_early_suspend-
[ 349.753494] early_suspend: sync
[ 349.764688] active wake lock PowerManagerService.Broadcasts
[ 349.764803] active wake lock PowerManagerService
[ 372.134247] bq27541_get_psp status: Charging ret= 0x0180
[ 372.135055] bq27541_get_psp voltage_now= 3766000 uV
[ 372.136648] bq27541_get_capacity = 29% ret= 33
[ 372.137436] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 372.140076] bq27541_get_capacity = 29% ret= 33
[ 372.141065] bq27541_get_psp voltage_now= 3766000 uV
[ 372.141954] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 372.142920] bq27541_get_psp status: Charging ret= 0x0180
[ 395.981736] EXT4-fs (mmcblk0p3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
[ 432.294143] bq27541_get_psp status: Charging ret= 0x0180
[ 432.294976] bq27541_get_psp voltage_now= 3773000 uV
[ 432.296615] bq27541_get_capacity = 30% ret= 34
[ 432.297434] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 432.300096] bq27541_get_capacity = 30% ret= 34
[ 432.301493] bq27541_get_psp voltage_now= 3773000 uV
[ 432.302449] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 432.303476] bq27541_get_psp status: Charging ret= 0x0180
[ 467.479418] EXT4-fs (mmcblk0p3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
[ 492.454200] bq27541_get_psp status: Charging ret= 0x0180
[ 492.455122] bq27541_get_psp voltage_now= 3774000 uV
[ 492.456667] bq27541_get_capacity = 30% ret= 34
[ 492.457485] bq27541_get_psp temperature= 290 (0.1¢XC)
[ 492.460269] bq27541_get_capacity = 30% ret= 34
[ 492.461210] bq27541_get_psp voltage_now= 3774000 uV
[ 492.462224] bq27541_get_psp temperature= 290 (0.1¢XC)
[ 492.463150] bq27541_get_psp status: Charging ret= 0x0180
final mount:
Code:
[email protected]:/system/bin # 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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/dm-0 on /mnt/asec/com.gameloft.android.ANMP.GloftA7HM-2 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
/dev/block/dm-1 on /mnt/asec/com.gameloft.android.ANMP.GloftN3HM-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,relatime,mode=050,gid=1028)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/sda1 on /data/media/0/usbStorage/sda1 type vfat (rw,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/vold/8:1 on /storage/usbdisk type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
[email protected]:/system/bin #
what's wrong ?
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
If I run the commands in "debuggerd" file on the shell (SSH server) ; I get them mounted correctly.
Is that gscript the APP in the play store? I will test if I can get it working with that.
mrmrmrmr said:
Ok; did as advised through the SSH server:
Code:
130|[email protected]:/system/bin # busybox mount -o remount -w /system
[email protected]:/system/bin # cp /system/bin/debuggerd /system/bin/debuggerd.ydk
[email protected]:/system/bin # cp /system/bin/debuggerd.mount /system/bin/debuggerd
[email protected]:/system/bin # start debuggerd
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin # cat debuggerd
#!/bin/sh
mount
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/data/com.gameloft.android.ANMP.GloftN3HM
mount
sleep 1
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.GAND.GloftKRHP /sdcard/Android/data/com.gameloft.android.GAND.GloftKRHP
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.rockstar.gta3 /sdcard/Android/data/com.rockstar.gta3
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftA7HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftA7HM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftKRHM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftKRHM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftN3HM
busybox mount -o bind /storage/usbdisk/N7/gameloft /sdcard/gameloft
[email protected]:/system/bin #
[email protected]:/system/bin #
dmesg:
Code:
[ 308.593540] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 308.593739] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 308.593849] usb usb2: Product: Tegra EHCI Host Controller
[ 308.594041] usb usb2: Manufacturer: Linux 3.1.10-faux123-grouper-00895-ga842db8 ehci_hcd
[ 308.594148] usb usb2: SerialNumber: tegra-ehci.0
[ 308.595469] hub 2-0:1.0: USB hub found
[ 308.595600] hub 2-0:1.0: 1 port detected
[ 308.596199] Wake39 for irq=52
[ 308.596393] Enabling wake39
[ 309.693303] usb 2-1: new high speed USB device number 2 using tegra-ehci
[ 309.728447] usb 2-1: New USB device found, idVendor=05e3, idProduct=0736
[ 309.728588] usb 2-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[ 309.728813] usb 2-1: Product: USB Storage
[ 309.728937] usb 2-1: Manufacturer: Generic
[ 309.729060] usb 2-1: SerialNumber: 000000000272
[ 309.731639] scsi0 : usb-storage 2-1:1.0
[ 309.826667] tegra_dvfs: voltage 1200 too high for dvfs on cpu_g
[ 309.826871] cpu-tegra: Failed to set cpu frequency to 1400000 kHz
[ 310.003278] INOK=L
[ 310.003630] smb347_charger: [cable_type_detect] Reg39 : 0x10
[ 310.004045] smb347_charger: [cable_type_detect] Reg3F : 0x81
[ 310.004383] smb347_charger: [cable_type_detect] Reg3E : 0x0e
[ 310.004572] Cable: SDP2 host mode charging
[ 310.004674] ========================================================
[ 310.004860] battery_callback usb_cable_state = 1
[ 310.004961] ========================================================
[ 310.005146] battery_callback cable_wake_lock 5 sec...
[ 310.005152]
[ 310.005376] elan-ktf3k 1-0010: Update power source to 1
[ 310.008230] bq27541_get_capacity = 29% ret= 33
[ 310.009171] bq27541_get_psp voltage_now= 3729000 uV
[ 310.010174] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 310.011209] bq27541_get_psp status: Charging ret= 0x0181
[ 310.735079] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 0272 PQ: 0 ANSI: 0
[ 310.736076] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 310.894390] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 310.895868] sd 0:0:0:0: [sda] Write Protect is off
[ 310.895985] sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
[ 310.897500] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.897695] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.903110] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.903351] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.917896] sda: sda1
[ 310.923288] sd 0:0:0:0: [sda] No Caching mode page present
[ 310.923404] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 310.923593] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 312.004076] bq27541_get_psp status: Charging ret= 0x0181
[ 312.004985] bq27541_get_psp voltage_now= 3750000 uV
[ 312.006516] bq27541_get_capacity = 29% ret= 33
[ 312.007374] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 312.011419] bq27541_get_capacity = 29% ret= 33
[ 312.012459] bq27541_get_psp voltage_now= 3750000 uV
[ 312.013534] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 312.014422] bq27541_get_psp status: Charging ret= 0x0181
[ 312.044011] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 312.328237] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 313.501145] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 313.564481] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 314.555979] init: untracked pid 4652 exited
[ 314.789968] init: untracked pid 4654 exited
[ 314.912327] init: untracked pid 4708 exited
[ 315.138358] init: untracked pid 4711 exited
[ 344.523435] binder: 1069:2048 transaction failed 29189, size 4-0
[ 344.523555] binder: send failed reply for transaction 13169, target dead
[ 349.723016] request_suspend_state: sleep (0->3) at 349589817028 (2013-01-08 21:45:32.731926998 UTC)
[ 349.723293] early_suspend: call handlers
[ 349.742941] [ektf3k]:[elan] elan_ktf3k_ts_suspend: enter
[ 349.743631] stop_drawing_early_suspended
[ 349.752516] tegra_pwm tegra_pwm.0: pwm_disable called on disabled PWM
[ 349.752714] grouper_panel_early_suspended
[ 349.752814] al3010_early_suspend+
[ 349.753308] al3010_early_suspend-
[ 349.753494] early_suspend: sync
[ 349.764688] active wake lock PowerManagerService.Broadcasts
[ 349.764803] active wake lock PowerManagerService
[ 372.134247] bq27541_get_psp status: Charging ret= 0x0180
[ 372.135055] bq27541_get_psp voltage_now= 3766000 uV
[ 372.136648] bq27541_get_capacity = 29% ret= 33
[ 372.137436] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 372.140076] bq27541_get_capacity = 29% ret= 33
[ 372.141065] bq27541_get_psp voltage_now= 3766000 uV
[ 372.141954] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 372.142920] bq27541_get_psp status: Charging ret= 0x0180
[ 395.981736] EXT4-fs (mmcblk0p3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
[ 432.294143] bq27541_get_psp status: Charging ret= 0x0180
[ 432.294976] bq27541_get_psp voltage_now= 3773000 uV
[ 432.296615] bq27541_get_capacity = 30% ret= 34
[ 432.297434] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 432.300096] bq27541_get_capacity = 30% ret= 34
[ 432.301493] bq27541_get_psp voltage_now= 3773000 uV
[ 432.302449] bq27541_get_psp temperature= 280 (0.1¢XC)
[ 432.303476] bq27541_get_psp status: Charging ret= 0x0180
[ 467.479418] EXT4-fs (mmcblk0p3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
[ 492.454200] bq27541_get_psp status: Charging ret= 0x0180
[ 492.455122] bq27541_get_psp voltage_now= 3774000 uV
[ 492.456667] bq27541_get_capacity = 30% ret= 34
[ 492.457485] bq27541_get_psp temperature= 290 (0.1¢XC)
[ 492.460269] bq27541_get_capacity = 30% ret= 34
[ 492.461210] bq27541_get_psp voltage_now= 3774000 uV
[ 492.462224] bq27541_get_psp temperature= 290 (0.1¢XC)
[ 492.463150] bq27541_get_psp status: Charging ret= 0x0180
final mount:
Code:
[email protected]:/system/bin # 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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/dm-0 on /mnt/asec/com.gameloft.android.ANMP.GloftA7HM-2 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
/dev/block/dm-1 on /mnt/asec/com.gameloft.android.ANMP.GloftN3HM-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,relatime,mode=050,gid=1028)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/sda1 on /data/media/0/usbStorage/sda1 type vfat (rw,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/vold/8:1 on /storage/usbdisk type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
[email protected]:/system/bin #
what's wrong ?
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
If I run the commands in "debuggerd" file on the shell (SSH server) ; I get them mounted correctly.
Click to expand...
Click to collapse
I have tried also mounting a shared folder by using the start debuggerd and the code of debuggerd is the following:
Code:
#!/bin/sh
busybox mount -t cifs //192.168.1.66/share /sdcard/cifs/share -o username=USER,password=PASSWORD
but the mounted directory appears empty, while if I enter
Code:
busybox mount -t cifs //192.168.1.66/share /sdcard/cifs/share -o username=USER,password=PASSWORD
through the shell it mounts correctly...
I don't know what I'm doing wrong, I think I understood correctly what you said that we should do....
vorcers,
yes that's the app on the play store. but as you'll see in the above output, the mount doesn't work when I run "start debuggerd" on the shell as well.
so what's wrong ?
the usage of debuggerd ?
I am going back to SuSE Linux 7.2! This really worked!
@mrmrmrmr @tristaoeast,
You used "#!/bin/sh" it need to be "#!/system/bin/sh" ! There is no /bin in android
I also did the same mistake :victory:
-------------------
I tried around a bit and this feels like I am using Windows 98. This is no Linux anymore...
I need to run my mount and umount scripts three times till I finally see and read the content. Maybe you should also try it. If I am using the ssh server, everything works instantly. I don't know what the hell is going on. I am using SManager.
If someone is interested in, I am using this script...
/mnt/sdcard/scripte/mount_cifs.sh
Code:
#!/system/bin/sh
DEBUGGERD=/system/bin/debuggerd
PATHE=/mnt/sdcard/scripte
su -c "stop debuggerd"
#stop debuggerd
busybox mount -o remount rw /system
cp $DEBUGGERD $DEBUGGERD.bak
insmod $PATHE/md4.ko
insmod $PATHE/nls_utf8.ko
insmod $PATHE/cifs.ko
echo "#!/system/bin/sh" > $DEBUGGERD
echo "mkdir -p /mnt/sdcard/mnt/cifs" >> $DEBUGGERD
echo "busybox mount -t cifs //192.168.100.1/share /mnt/sdcard/mnt/cifs -o username=####,password=###,umask=555,uid=1023,gid=1023" >> $DEBUGGERD
busybox chmod 755 $DEBUGGERD
chown root:shell $DEBUGGERD
su -c "start debuggerd"
#start debuggerd
#####
mv $DEBUGGERD.bak $DEBUGGERD
busybox mount -o remount ro /system
mount
/mnt/sdcard/scripte/umount_cifs.sh
Code:
#!/system/bin/sh
DEBUGGERD=/system/bin/debuggerd
stop debuggerd
busybox mount -o remount rw /system
mv $DEBUGGERD $DEBUGGERD.bak
echo "#!/system/bin/sh" > $DEBUGGERD
echo "busybox umount /mnt/sdcard/mnt/cifs" >> $DEBUGGERD
busybox chmod 755 $DEBUGGERD
chown root:shell $DEBUGGERD
start debuggerd
#####
mv $DEBUGGERD.bak $DEBUGGERD
busybox mount -o remount ro /system
mount
ok; as you'll see below, I have modified debuggerd script to have #!/system/bin/sh
but I still can not run it correctly when I run "start debuggerd" on ssh server:
Code:
[email protected]:/system/bin # cat /system/bin/debuggerd
#!/system/bin/sh
mount
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/data/com.gameloft.android.ANMP.GloftN3HM
mount
sleep 1
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.GAND.GloftKRHP /sdcard/Android/data/com.gameloft.android.GAND.GloftKRHP
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
busybox mount -o bind /storage/usbdisk/N7/Android/Data/com.rockstar.gta3 /sdcard/Android/data/com.rockstar.gta3
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftA7HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftA7HM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftKRHM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftKRHM
busybox mount -o bind /storage/usbdisk/N7/Android/obb/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/obb/com.gameloft.android.ANMP.GloftN3HM
busybox mount -o bind /storage/usbdisk/N7/gameloft /sdcard/gameloft
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin # stop debuggerd
[email protected]:/system/bin # start debuggerd
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin #
[email protected]:/system/bin # 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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/dm-0 on /mnt/asec/com.gameloft.android.ANMP.GloftA7HM-2 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
/dev/block/dm-1 on /mnt/asec/com.gameloft.android.ANMP.GloftN3HM-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,relatime,mode=050,gid=1028)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,discard)
/dev/block/vold/8:1 on /storage/usbdisk type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/system/bin #
what's wrong with my setup ?
---------- Post added at 11:49 PM ---------- Previous post was at 11:39 PM ----------
Code:
[email protected]:/data/data/berserker.android.apps.sshdroid/home # start debuggerd
[email protected]:/data/data/berserker.android.apps.sshdroid/home # dmesg | tail -5
[ 1363.181092] tegra_dvfs: voltage 1200 too high for dvfs on cpu_g
[ 1363.181330] cpu-tegra: Failed to set cpu frequency to 1400000 kHz
[ 1363.691106] tegra_dvfs: voltage 1200 too high for dvfs on cpu_g
[ 1363.691320] cpu-tegra: Failed to set cpu frequency to 1400000 kHz
[ 1365.180568] init: cannot execve('/system/bin/debuggerd'): No such file or directory
[email protected]:/data/data/berserker.android.apps.sshdroid/home # ls -al /system/bin/debuggerd
-rwxr-xr-x 1 root root 1060 Jan 10 23:45 /system/bin/debuggerd
[email protected]:/data/data/berserker.android.apps.sshdroid/home #
it says "no such file or dir." but it is there... how ?
Hm, the only thing that can be wrong, are the group rights... Or maybe something with the script itself. I need to test that.
Try the following:
chown root:shell /system/bin/debuggerd
@vorcers
I changed the group rights of debuggerd in ES File Manager,which I'm using with root to copy the modified debuggerd file...
I still haven't got the chance to try it out, but what does #!/system/bin/sh do?
Thanks for all your patience in this matter man
EDIT: I tried your script but it can't change debuggerd. As it seems it needs root permissions to do
Code:
busybox mount -o remount rw /system
cp $DEBUGGERD $DEBUGGERD.bak
echo "#!/system/bin/sh" > $DEBUGGERD
echo "mkdir -p /mnt/sdcard/mnt/cifs" >> $DEBUGGERD
echo "busybox mount -t cifs //192.168.100.1/share /mnt/sdcard/mnt/cifs -o username=####,password=###,umask=555,uid=1023,gid=1023" >> $DEBUGGERD
busybox chmod 755 $DEBUGGERD
chown root:shell $DEBUGGERD
su -c "start debuggerd"
#start debuggerd
#####
mv $DEBUGGERD.bak $DEBUGGERD
busybox mount -o remount ro /system
otherwise it says that the file system is read only, despite the remount as rw...
so I'd like to understand how o execute multiple lines in su mode, but I have googled for a while and reached no conclusion...
changing woner and group rights didn't help me.
what does this really mean :
Code:
[ 1365.180568] init: cannot execve('/system/bin/debuggerd'): No such file or directory

How to Install official miui v4 stable Rom on Desire S

I followed below steps for installing official miui v4 rom to desire s
1. Download official miui v4 stable rom from www.miui.com
2. Format sd card and system (clean format).
3. Hboot is 7.0
4. Installed official chinese sense 3.6 rom and reboot the phone to recovery.
5. factory reset and wipe cache & delvic cache.
My problem is while installing miui v4 3.2.22 stable official version...my installation aborted saying
updating package....
formatting system.......
do not format system.............
installed successfully....
Post reboot HTC splash screen appears for a while and then phone reboots on its own to recovery.
Please help...
talktoraj83 said:
I followed below steps for installing official miui v4 rom to desire s
1. Download official miui v4 stable rom from www.miui.com
2. Format sd card and system (clean format).
3. Hboot is 7.0
4. Installed official chinese sense 3.6 rom and reboot the phone to recovery.
5. factory reset and wipe cache & delvic cache.
My problem is while installing miui v4 3.2.22 stable official version...my installation aborted saying
updating package....
formatting system.......
do not format system.............
installed successfully....
Post reboot HTC splash screen appears for a while and then phone reboots on its own to recovery.
Please help...
Click to expand...
Click to collapse
Flash the boot.img from the ROM.zip through cmd on your PC.
NVardan said:
Flash the boot.img from the ROM.zip through cmd on your PC.
Click to expand...
Click to collapse
But he's on hboot 7.xxx
Shouldn't he be alrd s-off. Op do tell us if you're s-on or off.
Get 4ext. I think there's an image file that u can flash in fastboot mode. Search dev section for the thread.
Wipe everything (except sdcard)
Flash ROM
Reboot into rom
*flash gapps after set up.
FromBeyondThisWorld
#Fear said:
But he's on hboot 7.xxx
Shouldn't he be alrd s-off. Op do tell us if you're s-on or off.
Get 4ext. I think there's an image file that u can flash in fastboot mode. Search dev section for the thread.
Wipe everything (except sdcard)
Flash ROM
Reboot into rom
*flash gapps after set up.
FromBeyondThisWorld
Click to expand...
Click to collapse
You're right. That makes sense. HBOOT 7.xxx is already S-Off (I'm on this hboot too, I didn't notice ). :silly:
#Fear said:
But he's on hboot 7.xxx
Shouldn't he be alrd s-off. Op do tell us if you're s-on or off.
Get 4ext. I think there's an image file that u can flash in fastboot mode. Search dev section for the thread.
Wipe everything (except sdcard)
Flash ROM
Reboot into rom
*flash gapps after set up.
FromBeyondThisWorld
Click to expand...
Click to collapse
Ya my phone is s-off....and had pushed boot.img successfully bufore and after installation of rom.zip file but still same problem..
I think m missing some step....that is specific for flashing miui v4 official rom for desire s
What recovery is on your device? Try using 4ext :thumbup:
1.full wipe(except sdcard)
2.flash rom
3.reboot
Don't flash gapps first and see if it boots.
FromBeyondThisWorld
#Fear said:
What recovery is on your device? Try using 4ext :thumbup:
1.full wipe(except sdcard)
2.flash rom
3.reboot
Don't flash gapps first and see if it boots.
FromBeyondThisWorld
Click to expand...
Click to collapse
No its not booting..i have tried all permutation & combination....
on latest 4ext recovery
talktoraj83 said:
No its not booting..i have tried all permutation & combination....
on latest 4ext recovery
Click to expand...
Click to collapse
There is one hint if it could help some one to find out issue with my installation...
When m trying below patch for formatting my phone gives error..
http://www.androidfilehost.com/?fid=9390189810980749321
talktoraj83 said:
There is one hint if it could help some one to find out issue with my installation...
When m trying below patch for formatting my phone gives error..
http://www.androidfilehost.com/?fid=9390189810980749321
Click to expand...
Click to collapse
This guy had bootloop too when he tried, but he was trying the russian version. He solve it with amidabuddha kernel.
Cheers
#Fear said:
This guy had bootloop too when he tried, but he was trying the russian version. He solve it with amidabuddha kernel.
Cheers
Click to expand...
Click to collapse
Can you confirm that miuiv4 official version rom has kernel inside it or not?
talktoraj83 said:
Can you confirm that miuiv4 official version rom has kernel inside it or not?
Click to expand...
Click to collapse
Just look inside the zip and you`ll know....
Flashing another kernel wouldn`t harm,
if your device isn`t booting anyway...
take a logcat and attach it and/or look inside,
then all`ll become clear...
asgardr said:
Just look inside the zip and you`ll know....
Flashing another kernel wouldn`t harm,
if your device isn`t booting anyway...
take a logcat and attach it and/or look inside,
then all`ll become clear...
Click to expand...
Click to collapse
Please find below logcat-
10.554687] init: untracked pid 1288 exited
<6>[ 10.666137] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts:
<3>[ 10.779083] EXT3-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<3>[ 10.779937] EXT2-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<6>[ 10.828582] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 10.829498] init: untracked pid 1309 exited
<6>[ 11.487731] pm8058_led_currents_store: bank 6 currents 1
<6>[ 11.487976] pm8058_drvx_led_brightness_set: bank 6 brightness 0
<6>[ 11.488128] pm8058_drvx_led_brightness_set: bank 6 brightness 255
<6>[ 11.488708] pm8058_led_currents_store: bank 6 currents 9
<6>[ 11.488830] pm8058_drvx_led_brightness_set: bank 6 brightness 0
<6>[ 11.489074] pm8058_drvx_led_brightness_set: bank 6 brightness 255
<6>[ 11.490509] pm8058_drvx_led_brightness_set: bank 6 brightness 9
<6>[ 11.491119] pm8058_drvx_led_brightness_set: bank 6 brightness 90
<6>[ 11.491638] pm8058_drvx_led_brightness_set: bank 6 brightness 9
<6>[ 11.492218] pm8058_drvx_led_brightness_set: bank 6 brightness 90
<3>[ 11.875061] init: untracked pid 1343 exited
<6>[ 17.498992] [email protected],236
<6>[ 17.559783] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 17.561279] [ATS][set_vibration][successful]
<6>[ 17.584899] [VIB]vibrator_timer_func
<6>[ 17.663330] [email protected],236
<6>[ 25.172546] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 25.173919] [ATS][set_vibration][successful]
<6>[ 25.197753] [VIB]vibrator_timer_func
<6>[ 34.992889] [BATT] M2A_RPC: set_charging: 0 at 29234003670 (2013-08-30 18:23:52.340426829 UTC)
<6>[ 34.993194] Switch charger OFF
<6>[ 34.994964] [BATT] M2A_RPC: set_charging: 1 at 29236046353 (2013-08-30 18:23:52.342500000 UTC)
<6>[ 34.995269] Switch charger ON (SLOW)
<6>[ 34.996215] batt: Switch charger ON (SLOW): regh 0x03=83
<6>[ 34.997314] [BATT] M2A_RPC: cable_update: USB at 29238332939 (2013-08-30 18:23:52.344847561 UTC)
<6>[ 34.997619] [BATT] htc_cable_status_update: 0 -> 1
<6>[ 34.997741] [USB] msm_hsusb_set_vbus_state: 1
<6>[ 34.997924] [USB] hsusb: OFFLINE -> ONLINE
<6>[ 34.998016] [USB] lpm exit
<6>[ 34.999298] [USB] hsusb: reset controller
<6>[ 35.044311] msm_hsusb_phy_reset
<6>[ 35.189300] [USB] ulpi: write 0x06 to 0x36
<6>[ 35.189392] [USB] ulpi: write 0x0c to 0x31
<6>[ 35.189605] [USB] ulpi: write 0x31 to 0x32
<6>[ 35.189697] [USB] ulpi: write 0x01 to 0x0d
<6>[ 35.189788] [USB] ulpi: write 0x01 to 0x10
<6>[ 35.189971] [USB] handle_notify_offline: notify offline
<6>[ 35.190093] [USB] msm_hsusb: enable pullup
<6>[ 35.193206] [USB] suspend
<6>[ 35.209381] [USB] not AC charger
<6>[ 35.293640] [USB] reset
<6>[ 35.293731] [USB] send connect type 1
<6>[ 35.293853] Touch: cable change to 1
<6>[ 35.295227] fsg_set_ums_state: 1
<6>[ 35.295349] ums: set state 1
<6>[ 35.295745] [BATT] online=1
<6>[ 35.295928] [USB] portchange USB_SPEED_HIGH
<6>[ 35.296112] [BATT] Update SMEM: cable type 1 at 29536839037 (2013-08-30 18:23:52.643353659 UTC)
<6>[ 35.338897] pm8058_pwm_led_brightness_set: bank 0 brightness 0
<6>[ 35.345031] pm8058_pwm_led_brightness_set: bank 1 brightness 1
<6>[ 35.351470] pm8058_pwm_led_brightness_set: bank 0 brightness 0
<6>[ 35.357391] pm8058_pwm_led_brightness_set: bank 1 brightness 1
<6>[ 35.484069] android_usb gadget: high speed config #1: android
<6>[ 35.484222] adb_function_set_alt: maxsize = 512
<6>[ 35.484497] ums: set state 1
<6>[ 66.039398] Release 'boot-time' perf_lock
<6>[ 66.620391] Release 'boot-time' no_halt_lock
<6>[ 67.040405] perflock_notifier_call: cpufreq recover policy 245760 1024000
<6>[ 246.697113] [BATT] M2A_RPC: level_update: 68 at 240732143916 (2013-08-30 18:27:23.838079269 UTC)
<6>[ 246.698181] [BATT] power_supply_changed: battery at 240732906111 (2013-08-30 18:27:23.839176830 UTC)
<6>[ 246.718322] pm8058_pwm_led_brightness_set: bank 0 brightness 0
<6>[ 246.737548] pm8058_pwm_led_brightness_set: bank 1 brightness 1
<3>[ 246.935974] INFO: task audio_mvs:428 blocked for more than 120 seconds.
<3>[ 246.936370] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 246.937011] audio_mvs D c0425f80 0 428 2 0x00000000
<4>[ 246.938323] Backtrace:
<4>[ 246.939056] [<c0425bbc>] (schedule+0x0/0x450) from [<c005101c>] (__msm_rpc_read+0x22c/0xa4c)
<4>[ 246.939758] [<c0050df0>] (__msm_rpc_read+0x0/0xa4c) from [<c0051858>] (msm_rpc_read+0x1c/0x88)
<4>[ 246.940185] [<c005183c>] (msm_rpc_read+0x0/0x88) from [<c0074f34>] (audio_mvs_thread+0x4c/0x164)
<4>[ 246.940856] r6:00000000 r5:c7e69f9c r4:c05ef368
<4>[ 246.942596] [<c0074ee8>] (audio_mvs_thread+0x0/0x164) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 246.942962] r8:00000000 r7:c05ef368 r6:c0074ee8 r5:c7e69fcc r4:c7c1df48
<4>[ 246.945312] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 246.946044] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df48
<3>[ 246.947753] INFO: task krmt_storagecln:460 blocked for more than 120 seconds.
<3>[ 246.948425] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 246.948791] krmt_storagecln D c0425f80 0 460 2 0x00000000
<4>[ 246.950073] Backtrace:
<4>[ 246.950805] [<c0425bbc>] (schedule+0x0/0x450) from [<c004a1c4>] (rpc_clients_cb_thread+0x98/0x1b0)
<4>[ 246.951507] [<c004a12c>] (rpc_clients_cb_thread+0x0/0x1b0) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 246.952239] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 246.952606] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1ddf8
<3>[ 246.954620] INFO: task voice:740 blocked for more than 120 seconds.
<3>[ 246.955261] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 246.955657] voice D c0425f80 0 740 2 0x00000000
<4>[ 246.957031] Backtrace:
<4>[ 246.957763] [<c0425bbc>] (schedule+0x0/0x450) from [<c04266e8>] (schedule_timeout+0x24/0x23c)
<4>[ 246.958465] [<c04266c4>] (schedule_timeout+0x0/0x23c) from [<c04264e0>] (wait_for_common+0x12c/0x1f0)
<4>[ 246.959136] r7:c76f2000 r6:00000002 r5:c05eaf44 r4:7fffffff
<4>[ 246.960876] [<c04263b4>] (wait_for_common+0x0/0x1f0) from [<c0426684>] (wait_for_completion+0x1c/0x20)
<4>[ 246.961578] [<c0426668>] (wait_for_completion+0x0/0x20) from [<c005a38c>] (voice_thread+0x6c/0x554)
<4>[ 246.962280] [<c005a320>] (voice_thread+0x0/0x554) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 246.962707] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 246.963378] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df30
<3>[ 367.073181] INFO: task rpcrouter:274 blocked for more than 120 seconds.
<3>[ 367.073547] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 367.074249] rpcrouter D c0425f80 0 274 2 0x00000000
<4>[ 367.075286] Backtrace:
<4>[ 367.076354] [<c0425bbc>] (schedule+0x0/0x450) from [<c004f748>] (rr_read+0x178/0x1a4)
<4>[ 367.076751] [<c004f5d0>] (rr_read+0x0/0x1a4) from [<c004f900>] (do_read_data+0x1c/0xa08)
<4>[ 367.077453] [<c004f8e4>] (do_read_data+0x0/0xa08) from [<c00ae168>] (worker_thread+0x18c/0x238)
<4>[ 367.078186] [<c00adfdc>] (worker_thread+0x0/0x238) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 367.078887] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 367.079284] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c2bd70
<3>[ 367.081268] INFO: task audio_mvs:428 blocked for more than 120 seconds.
<3>[ 367.081634] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 367.082305] audio_mvs D c0425f80 0 428 2 0x00000000
<4>[ 367.083679] Backtrace:
<4>[ 367.084381] [<c0425bbc>] (schedule+0x0/0x450) from [<c005101c>] (__msm_rpc_read+0x22c/0xa4c)
<4>[ 367.085052] [<c0050df0>] (__msm_rpc_read+0x0/0xa4c) from [<c0051858>] (msm_rpc_read+0x1c/0x88)
<4>[ 367.085479] [<c005183c>] (msm_rpc_read+0x0/0x88) from [<c0074f34>] (audio_mvs_thread+0x4c/0x164)
<4>[ 367.086151] r6:00000000 r5:c7e69f9c r4:c05ef368
<4>[ 367.087554] [<c0074ee8>] (audio_mvs_thread+0x0/0x164) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 367.088195] r8:00000000 r7:c05ef368 r6:c0074ee8 r5:c7e69fcc r4:c7c1df48
<4>[ 367.090545] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 367.090911] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df48
<3>[ 367.092895] INFO: task krmt_storagecln:460 blocked for more than 120 seconds.
<3>[ 367.093627] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 367.093994] krmt_storagecln D c0425f80 0 460 2 0x00000000
<4>[ 367.095336] Backtrace:
<4>[ 367.096038] [<c0425bbc>] (schedule+0x0/0x450) from [<c004a1c4>] (rpc_clients_cb_thread+0x98/0x1b0)
<4>[ 367.096771] [<c004a12c>] (rpc_clients_cb_thread+0x0/0x1b0) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 367.097442] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 367.097808] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1ddf8
<3>[ 367.099822] INFO: task voice:740 blocked for more than 120 seconds.
<3>[ 367.100189] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 367.100860] voice D c0425f80 0 740 2 0x00000000
<4>[ 367.102203] Backtrace:
<4>[ 367.102905] [<c0425bbc>] (schedule+0x0/0x450) from [<c04266e8>] (schedule_timeout+0x24/0x23c)
<4>[ 367.103637] [<c04266c4>] (schedule_timeout+0x0/0x23c) from [<c04264e0>] (wait_for_common+0x12c/0x1f0)
<4>[ 367.104034] r7:c76f2000 r6:00000002 r5:c05eaf44 r4:7fffffff
<4>[ 367.106018] [<c04263b4>] (wait_for_common+0x0/0x1f0) from [<c0426684>] (wait_for_completion+0x1c/0x20)
<4>[ 367.106750] [<c0426668>] (wait_for_completion+0x0/0x20) from [<c005a38c>] (voice_thread+0x6c/0x554)
<4>[ 367.107452] [<c005a320>] (voice_thread+0x0/0x554) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 367.107849] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 367.108520] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df30
<6>[ 486.697143] [BATT] M2A_RPC: level_update: 69 at 480497997575 (2013-08-30 18:31:23.603963416 UTC)
<6>[ 486.699218] [BATT] power_supply_changed: battery at 480500162209 (2013-08-30 18:31:23.606036587 UTC)
<6>[ 486.718139] pm8058_pwm_led_brightness_set: bank 0 brightness 0
<6>[ 486.737762] pm8058_pwm_led_brightness_set: bank 1 brightness 1
<3>[ 487.220397] INFO: task audio_mvs:428 blocked for more than 120 seconds.
<3>[ 487.221069] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 487.221466] audio_mvs D c0425f80 0 428 2 0x00000000
<4>[ 487.222778] Backtrace:
<4>[ 487.223541] [<c0425bbc>] (schedule+0x0/0x450) from [<c005101c>] (__msm_rpc_read+0x22c/0xa4c)
<4>[ 487.224243] [<c0050df0>] (__msm_rpc_read+0x0/0xa4c) from [<c0051858>] (msm_rpc_read+0x1c/0x88)
<4>[ 487.224945] [<c005183c>] (msm_rpc_read+0x0/0x88) from [<c0074f34>] (audio_mvs_thread+0x4c/0x164)
<4>[ 487.225341] r6:00000000 r5:c7e69f9c r4:c05ef368
<4>[ 487.227020] [<c0074ee8>] (audio_mvs_thread+0x0/0x164) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 487.227691] r8:00000000 r7:c05ef368 r6:c0074ee8 r5:c7e69fcc r4:c7c1df48
<4>[ 487.229736] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 487.230468] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df48
<3>[ 487.232208] INFO: task krmt_storagecln:460 blocked for more than 120 seconds.
<3>[ 487.232879] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 487.233551] krmt_storagecln D c0425f80 0 460 2 0x00000000
<4>[ 487.234588] Backtrace:
<4>[ 487.235290] [<c0425bbc>] (schedule+0x0/0x450) from [<c004a1c4>] (rpc_clients_cb_thread+0x98/0x1b0)
<4>[ 487.235992] [<c004a12c>] (rpc_clients_cb_thread+0x0/0x1b0) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 487.236694] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 487.237365] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1ddf8
<3>[ 487.239044] INFO: task voice:740 blocked for more than 120 seconds.
<3>[ 487.239715] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 487.240081] voice D c0425f80 0 740 2 0x00000000
<4>[ 487.241485] Backtrace:
<4>[ 487.242187] [<c0425bbc>] (schedule+0x0/0x450) from [<c04266e8>] (schedule_timeout+0x24/0x23c)
<4>[ 487.242889] [<c04266c4>] (schedule_timeout+0x0/0x23c) from [<c04264e0>] (wait_for_common+0x12c/0x1f0)
<4>[ 487.243560] r7:c76f2000 r6:00000002 r5:c05eaf44 r4:7fffffff
<4>[ 487.245269] [<c04263b4>] (wait_for_common+0x0/0x1f0) from [<c0426684>] (wait_for_completion+0x1c/0x20)
<4>[ 487.245971] [<c0426668>] (wait_for_completion+0x0/0x20) from [<c005a38c>] (voice_thread+0x6c/0x554)
<4>[ 487.246673] [<c005a320>] (voice_thread+0x0/0x554) from [<c00b1f28>] (kthread+0x84/0x8c)
<4>[ 487.247375] [<c00b1ea4>] (kthread+0x0/0x8c) from [<c009e9a0>] (do_exit+0x0/0x6ac)
<4>[ 487.247772] r7:00000013 r6:c009e9a0 r5:c00b1ea4 r4:c7c1df30
<6>[ 491.649566] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 491.650665] [ATS][set_vibration][successful]
<6>[ 491.674682] [VIB]vibrator_timer_func
<6>[ 492.960632] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 492.961486] [ATS][set_vibration][successful]
<6>[ 492.985748] [VIB]vibrator_timer_func
<6>[ 494.228454] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 494.229370] [ATS][set_vibration][successful]
<6>[ 494.253662] [VIB]vibrator_timer_func
<6>[ 494.353851] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<6>[ 505.722808] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts:
<6>[ 507.874176] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 507.875091] [ATS][set_vibration][successful]
<6>[ 507.899688] [VIB]vibrator_timer_func
<6>[ 510.369537] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 510.370391] [ATS][set_vibration][successful]
<6>[ 510.394653] [VIB]vibrator_timer_func
<6>[ 512.736968] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 512.738128] [ATS][set_vibration][successful]
<6>[ 512.762573] [VIB]vibrator_timer_func
<6>[ 514.352325] Touch: calibration confirm
<6>[ 514.373626] Touch Status: 0x01 0x10 0x77 0xA1 0x0A
<6>[ 514.381561] Touch Status: 0x01 0x00 0x77 0xA1 0x0A
<6>[ 514.776885] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 514.777862] [ATS][set_vibration][successful]
<6>[ 514.802093] [VIB]vibrator_timer_func
<6>[ 519.868621] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 519.869506] [ATS][set_vibration][successful]
<6>[ 519.893737] [VIB]vibrator_timer_func
<6>[ 522.455322] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 522.456207] [ATS][set_vibration][successful]
<6>[ 522.480499] [VIB]vibrator_timer_func
<6>[ 523.943817] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 523.944732] [ATS][set_vibration][successful]
<6>[ 523.969024] [VIB]vibrator_timer_func
<6>[ 529.148071] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 529.149322] [ATS][set_vibration][successful]
<6>[ 529.173309] [VIB]vibrator_timer_func
<6>[ 536.841979] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 536.843017] [ATS][set_vibration][successful]
<6>[ 536.867218] [VIB]vibrator_timer_func
<6>[ 543.078704] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 543.079650] [ATS][set_vibration][successful]
<6>[ 543.103851] [VIB]vibrator_timer_func
<6>[ 546.098419] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 546.099304] [ATS][set_vibration][successful]
<6>[ 546.123565] [VIB]vibrator_timer_func
<6>[ 547.273925] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 547.274871] [ATS][set_vibration][successful]
<6>[ 547.299133] [VIB]vibrator_timer_func
<6>[ 549.013427] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 549.014587] [ATS][set_vibration][successful]
<6>[ 549.038635] [VIB]vibrator_timer_func
<6>[ 550.455963] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 550.456909] [ATS][set_vibration][successful]
<6>[ 550.481201] [VIB]vibrator_timer_func
<6>[ 551.694274] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 551.695129] [ATS][set_vibration][successful]
<6>[ 551.719390] [VIB]vibrator_timer_func
<6>[ 562.994323] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 562.995758] [ATS][set_vibration][successful]
<6>[ 563.019470] [VIB]vibrator_timer_func
<6>[ 569.194122] [VIB] recovery(parent:recovery): vibrates 25 msec
<6>[ 569.195098] [ATS][set_vibration][successful]
<6>[ 569.219329] [VIB]vibrator_timer_func
<6>[ 569.385711] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<3>[ 569.644683] tc: version magic '2.6.35.10 preempt mod_unload ARMv7 ' should be '2.6.35.10-g13f6602 preempt mod_unload ARMv7 '
<6>[ 572.967926] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<3>[ 573.057800] EXT3-fs (mmcblk0p28): error: couldn't mount because of unsupported optional features (40)
<3>[ 573.058654] EXT2-fs (mmcblk0p28): error: couldn't mount because of unsupported optional features (40)
<6>[ 573.118988] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 573.575347] EXT3-fs (mmcblk0p29): error: couldn't mount because of unsupported optional features (240)
<3>[ 573.576202] EXT2-fs (mmcblk0p29): error: couldn't mount because of unsupported optional features (240)
<4>[ 573.578399] EXT4-fs (mmcblk0p29): warning: checktime reached, running e2fsck is recommended
<6>[ 573.636688] EXT4-fs (mmcblk0p29): mounted filesystem without journal. Opts: (null)
<6>[ 606.694824] [BATT] M2A_RPC: set_charging: 100 at 600378089037 (2013-08-30 18:33:23.484603659 UTC)
<6>[ 606.695129] Switch charger CHECK
<6>[ 606.695495] TPS65200 STATUS_A27
I´m to late... But extract attached folder and push the folder in the ROM.zip ...
It´s a fix
Some lines are wrong in updater-script

Categories

Resources