Related
Hello everybody. I am facing INTERNAL SD CORRUPTION problem and hope this is the right thread where to post as many such articles have been found here.
When I try to format internal SD card via Windows (no Quick mode), repartition via adb, format via CWM, delete internal SD card via rm –rf, it does not work. File seems to be deleted until next mount of /sdcard or reflash.
I have tried many ROMs including PIT 512 file to reflash via Odin 1.3 or 1.85. Some of them stucked, some let me boot into Android but had problems with crashing applications.
JVU-RE, Ficeto JVB, Darky ROM 10.2 RE, ROMS with XWJVH/XXJVO/NEEJV3; XXJP2/XXJP2/OXAJP2; XXJVU/XXJVU/OXAJVU
I have been searching and trying for nearly a week. Would buy beers/whiskeys to the ONE who can help me to solve that. Thanks a lot for any valuable hint how to correct that.
FDISK
~ # fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 6056 MB, 6056542208 bytes
4 heads, 16 sectors/track, 184831 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ # fdisk -l /dev/block/mmcblk0p2
Disk /dev/block/mmcblk0p2: 2013 MB, 2013265920 bytes
4 heads, 16 sectors/track, 61440 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
FSTAB
~ # more /etc/fstab
/dev/block/stl11 /cache rfs rw
/dev/block/mmcblk0p2 /data rfs rw
/dev/block/stl10 /datadata rfs rw
/dev/block/stl9 /system rfs rw
/dev/block/mmcblk0p1 /sdcard vfat rw
MOUNT
~ # mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,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)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
DEV/BLOCK DIR
/dev/block # ls
bml0!c bml7 loop7 ram13 ram9 stl7 tfsr4
bml1 bml8 mmcblk0 ram14 stl1 stl8 tfsr5
bml10 bml9 mmcblk0p1 ram15 stl10 stl9 tfsr6
bml11 loop0 mmcblk0p2 ram2 stl11 tfsr0!c tfsr7
bml12 loop1 platform ram3 stl12 tfsr1 tfsr8
bml2 loop2 ram0 ram4 stl2 tfsr10 tfsr9
bml3 loop3 ram1 ram5 stl3 tfsr11
bml4 loop4 ram10 ram6 stl4 tfsr12
bml5 loop5 ram11 ram7 stl5 tfsr2
bml6 loop6 ram12 ram8 stl6 tfsr3
/dev/block # ls –l | grep mmcblk
brw------- 1 root root 179, 0 Apr 29 12:04 mmcblk0
brw------- 1 root root 179, 1 Apr 29 12:17 mmcblk0p1
brw------- 1 root root 179, 2 Apr 29 12:00 mmcblk0p2
PARTITIONING
/dev/block # parted mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
(parted) print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 8070MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 6057MB 6057MB primary fat32 lba
2 6057MB 8070MB 2013MB primary lba
(parted) rm 2
rm 2
rm 2
(parted) rm 1
rm 1
rm 1
(parted) print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 8070MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 6057MB 6057MB primary fat32 lba
2 6057MB 8070MB 2013MB primary lba
(parted) mkfs
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? Yes
Yes
Yes
Partition number? 1
1
1
File system type? [ext2]? ext2
ext2
ext2
Error: Invalid superblock. Are you sure this is an ext2 file system?
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
DMESG
/system/csc # dmesg
dmesg
S + ADB (Debugging mode)
<4>[ 58.641985] [composite_switch_work]config=0xc0d70b50
<3>[ 106.982404] FAT: Unrecognized mount option "check=no" or missing value
<3>[ 108.002658] FAT: Unrecognized mount option "check=no" or missing value
<3>[ 108.876726] FAT: Unrecognized mount option "check=no" or missing value
<4>[ 114.816057] [BIF: ] FSR VERSION: FSR_1.2.1p1_b139_RTM
<4>[ 114.816079] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:6) / 1171 line
<4>[ 114.816118] [SIF:INF] ===> STL Clst[ 3] Scan Root Info
<4>[ 114.816710] [SIF:INF] ===> STL Zone[ 3, 0] Open Zone Meta
<4>[ 114.818579] [SIF:INF] Latest Header Index ( 8) Vbn ( 10)
<4>[ 114.819247] [SIF:INF] Latest Header Clean Page Offset ( 5)
<4>[ 114.819257] [SIF:INF] POR write timer : 0x6
<4>[ 114.819519] [SIF:INF] Latest Context BlockIdx ( 8) Offset ( 4) Vpn ( 644)
<4>[ 114.819657] [SIF:INF] Number of Free Block ( 22)
<4>[ 114.819665] [SIF:INF] Active Log List : Num ( 0)
<4>[ 114.819676] [SIF:INF] ===> STL Zone[ 3, 0] Open Zone Post
<4>[ 114.819686] [SIF:INF] ===> STL Zone[ 3, 0] Validity check
<4>[ 114.819706] [SIF:INF] Partition [0, 23] open is success
<3>[ 116.209628] FAT: Unrecognized mount option "check=no" or missing value
<3>[ 144.052742] FAT: Unrecognized mount option "check=no" or missing value
<4>[ 182.622852] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 5)
<4>[ 183.623957] [SIF:INF] INACTIVATED LOG BLOCKS nDgn( 4) nVbn( 95) nCPOffs( 33)
<4>[ 183.627334] [SIF:INF] INACTIVATED LOG BLOCKS nDgn( 0) nVbn( 96) nCPOffs( 3)
<4>[ 183.627851] [SIF:OUT] --FSR_STL_FlushAllMetaInfo()
<4>[ 183.627880] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 4)
<4>[ 186.121411] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 3)
<3>[ 1511.603164] init: untracked pid 673 exited
<7>[ 1741.143938] max8998_charging_control : chg(0) cable(1) dis(0) esafe(2) bat(76,0,0)
<7>[ 1741.144150] [TSP] TA NON-Detect!!!
<3>[ 1771.984929] init: untracked pid 680 exited
<7>[ 1801.268706] max8998_charging_control : chg(1) cable(1) dis(0) esafe(2) bat(76,0,0)
<7>[ 1801.269545] [TSP] TA Detect!!!
<4>[ 2833.138728] [BIF: ] FSR VERSION: FSR_1.2.1p1_b139_RTM
<4>[ 2833.138751] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:4) / 1171 line
<4>[ 2833.138790] [SIF:INF] ===> STL Clst[ 2] Scan Root Info
<4>[ 2833.139382] [SIF:INF] ===> STL Zone[ 2, 0] Open Zone Meta
<4>[ 2833.146141] [SIF:INF] Latest Header Index ( 16) Vbn ( 18)
<4>[ 2833.146829] [SIF:INF] Latest Header Clean Page Offset ( 6)
<4>[ 2833.146839] [SIF:INF] POR write timer : 0x6
<4>[ 2833.147222] [SIF:INF] Latest Context BlockIdx ( 16) Offset ( 5) Vpn ( 1157)
<4>[ 2833.147363] [SIF:INF] Number of Free Block ( 26)
<4>[ 2833.147372] [SIF:INF] Active Log List : Num ( 0)
<4>[ 2833.147382] [SIF:INF] ===> STL Zone[ 2, 0] Open Zone Post
<4>[ 2833.147392] [SIF:INF] ===> STL Zone[ 2, 0] Validity check
<4>[ 2833.147414] [SIF:INF] Partition [0, 22] open is success
<4>[ 3354.057290] [BIF: ] FSR VERSION: FSR_1.2.1p1_b139_RTM
<4>[ 3354.057313] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:5) / 1171 line
<4>[ 3354.057353] [SIF:INF] ===> STL Clst[ 4] Scan Root Info
<4>[ 3354.057959] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Meta
<4>[ 3354.058837] [SIF:INF] Latest Header Index ( 2) Vbn ( 4)
<4>[ 3354.059650] [SIF:INF] Latest Header Clean Page Offset ( 6)
<4>[ 3354.059660] [SIF:INF] POR write timer : 0x10
<4>[ 3354.059805] [SIF:INF] Latest Context BlockIdx ( 2) Offset ( 5) Vpn ( 261)
<4>[ 3354.059946] [SIF:INF] Number of Free Block ( 9)
<4>[ 3354.059955] [SIF:INF] Active Log List : Num ( 0)
<4>[ 3354.059965] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Post
<4>[ 3354.059975] [SIF:INF] ===> STL Zone[ 4, 0] Validity check
<4>[ 3354.059993] [SIF:INF] Partition [0, 24] open is success
Start over with flashing ezbase 3.0 or 4.0.(find it in insanity rom thread) with pit 512 and repatition ticked and untick reboot and flash via Odin.when flash is done unplug your phone remove battery,put it back and use 3button combo to get in recovery,under advanced press fix permissions and reboot.if u still get fc's go back to recovery/mount/storage and format system and data and flash a rom from recovery.
Thank you a lot for the answer. I have tried your step-by-step (just EZBase 2.0) nevertheless not working even flashing from recovery. I guess the problem is deeper. Whatever I use (Odin/recovery mode) every time internal memory is not cleaned from old files.
Also using fdisk in adb all seems fine until remounting of the /sdcard. Either the problem lies in partition table or....I don't know. I am not able to do any operation on internal SD from command line and that is weird.
When using recovery mode + install, I have to use adb push to upload the zip file, then flash. After restart or umount, zip file has gone, old files are back. Thanks to anybody for other hint what to check.
Sorry for that,sound like a partition mount fault.might be corrupted
somehow.
A long time ago there was some (i think) similar problems try search for "dbdata.tar" fix,but this is a longshot and i think it was in the froyo days,search here in xda and read
---------- Post added at 09:58 PM ---------- Previous post was at 09:25 PM ----------
OK I found the file.go to (rom) i9000xxjw4 (2.3.6)[19.03.2012] post 76 page 8.
Sorry I cant provide links I'm on my phone
But remember this is a longshot.
Thank you a lot! I really do appreciate your attitude. I have found the dbdata.tar in this post but when applied on EZBase 2.0 it started to reboot. Now I reflashed by JVU-RE and waiting on boot screen (I guess it checks rfs vs. ext4), but I really think the issue will be somewhere in the partitions or partition table.
Do you or somebody know where to check partition table? I tried to check via fdisk but no help. I think that the list of files are stored in header of those partitions. Is it possible to rebuild them from OS level or to rebuild the whole mmcblk0? It is Linux, it should be possible. Thanks a lot.
any news on that issue? i might have the same problem...
I also have this problem. I can partition mmcblk0p1 with FAT32 and mmcblk0p2 with ext4 or whatever, than format the partitions and after reboot (recovery) all files (pictures, documents, etc.) are completely restored. No chance at all to change files oder partitions permanent.
I have a SGS GT-I9000.
Does anybody have an idea? What information can I provide to support diagnosis?
same here, tried deleting, formating, installing ROM's... Nothing works..
ghostjak said:
same here, tried deleting, formating, installing ROM's... Nothing works..
Click to expand...
Click to collapse
Hey ghostjak, what is your model ? is it i9000 or i9000B, cause all the while I been trying to help you based on i9000 if it is i9000B than its very similar to my unit M110S both have a DMB TV and not compatible to i9000
any news on this issue ?
Have the same problem, formating, killing, dropping the phone, nothing helps, all old files are back and i cant do nothing !!!!!
igalva said:
Have the same problem, formating, killing, dropping the phone, nothing helps, all old files are back and i cant do nothing !!!!!
Click to expand...
Click to collapse
you do not have to back up data via Google? It sometimes can tease.
misacek said:
you do not have to back up data via Google? It sometimes can tease.
Click to expand...
Click to collapse
Please refer this, it seems you had a brick on sdcard, In turn the partition table got currupted due to formatting the sdcard using CMXX removery mode.
http://forum.xda-developers.com/showthread.php?t=1813386&page=2
kat0072 said:
Please refer this, it seems you had a brick on sdcard, In turn the partition table got currupted due to formatting the sdcard using CMXX removery mode.
http://forum.xda-developers.com/showthread.php?t=1813386&page=2
Click to expand...
Click to collapse
Yeah I know. Its fine now samsung customer care office helped me to reflash the firmware.
But now question is how to reset the custom rom count to 0 ??
Sent from my GT-N7105 using xda app-developers app
kat0072 said:
Yeah I know. Its fine now samsung customer care office helped me to reflash the firmware.
Click to expand...
Click to collapse
Could you revive the corrupted internal sd card? Is it just flashing a firmware and that's it?
Thanks in advance.
I dont know what exactly they have done to correct the partition table.
I guess they re-partitioned using the pit file.
Sent from my GT-N7105 using xda app-developers app
kat0072 said:
I dont know what exactly they have done to correct the partition table.
I guess they re-partitioned using the pit file.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Hello,
I have the same problem... you mention samsung guys fixed, did you send the phone to them? Or did they give you the files?
I have the same problem on my Samsung.
If you found any solution to this problem could you please help me??
karamjit123 said:
If you found any solution to this problem could you please help me??
Click to expand...
Click to collapse
I dont know what problem ur facing but if sd internal corrupt, u should just follow this guy instruction
http://forum.xda-developers.com/showthread.php?t=845708
https://www.youtube.com/watch?v=zdMhYYdMB08
herolpx said:
Hello,
I have the same problem... you mention samsung guys fixed, did you send the phone to them? Or did they give you the files?
Click to expand...
Click to collapse
I just visited the near by Samsung customer care office in my area and they took 6hours to fix it and gave me back with no cost of repair. Remember even they fix this up the Custom ROM counter will still intact which was earlier. They will not reset it.
HTH
Sent from my GT-N7105 using xda app-developers app
can't open '/dev/block/mmcblk0p2': No such file or directory
parted /dev/block/mmcblk0
Error: Can't have a partition outside the disk!
~ # e2fsck -b8193 /dev/block/mmcblk0p2
e2fsck -b8193 /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # fdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': No such file or directory
more /etc/fstab
/dev/block/stl11 /cache rfs rw
/dev/block/mmcblk0p2 /data rfs rw
/dev/block/stl10 /datadata rfs rw
/dev/block/stl9 /system rfs rw
/dev/block/mmcblk0p1 /sdcard vfat rw
Please Help !!!
Hey all,
for some reason I have a infinite boot loop on my rooted Note (the boot animation plays, but then it restarts); firmware version is stock XXLSZ with root and CWM Recovery 6.0.3.0/PhilZ Touch 4.
I have not done anything to the OS since I fixed it up the last time a month ago; and once again I have no backup of the data on the internal memory.
How can I find out what is broken, and how do I get the data off the phone with CWM recovery? adb shell works and the data in /data, /system and /emmc still appears to be there, however I can't mount /sd-ext - cwm says "can't mount /dev/block/mmcblk1p2 /sd-ext (no such file).
dmesg shows this here:
<3>[ 7.713599] c0 mmc1: cmd 17 data timeout error
<3>[ 7.713903] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 7.714072] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 9.225020] c0 mmc1: cmd 17 data timeout error
<3>[ 9.225481] c0 end_request: I/O error, dev mmcblk1, sector 7
<3>[ 9.981223] c0 mmc1: cmd 18 data timeout error
<3>[ 10.737259] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 10.737431] c0 end_request: I/O error, dev mmcblk1, sector 0
<3>[ 11.493134] c0 end_request: I/O error, dev mmcblk1, sector 1
<3>[ 12.248358] c0 mmc1: cmd 17 data timeout error
<3>[ 12.248804] c0 end_request: I/O error, dev mmcblk1, sector 2
<3>[ 13.004323] c0 mmcblk1: error -110 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
<3>[ 13.759713] c0 mmc1: cmd 17 data timeout error
<3>[ 13.759997] c0 mmcblk1: error -110 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
<3>[ 14.515904] c0 mmc1: cmd 17 data timeout error
<3>[ 15.271589] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539288] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539595] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 18.295005] c0 mmc1: cmd 17 data timeout error
<3>[ 18.295297] c0 mmcblk1: error -110 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
<7>[ 18.725004] c0 usb: set_config_number single config
<7>[ 18.725108] c0 usb: set_interface_count next_interface_id=2
<7>[ 18.729004] c0 usb: set_config e mass_storage[0]
<7>[ 18.729131] c0 usb: set_config e adb[1]
<7>[ 18.729239] c0 usb: SET_CON
<7>[ 18.729487] c0 usb: android_work config=c0b77704,connected=1,sw_connected=1
<7>[ 18.730247] c0 usb: android_work sent uevent USB_STATE=CONFIGURED
<7>[ 20.098554] c0 usb: set_config_number single config
<7>[ 20.100774] c0 usb: set_config_number single config
<7>[ 20.100879] c0 usb: set_interface_count next_interface_id=2
<3>[ 21.317770] c0 mmc1: cmd 17 data timeout error
<3>[ 21.318081] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 21.318253] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 22.073490] c0 mmc1: cmd 17 data timeout error
<3>[ 22.829455] c0 mmcblk1: error -110 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
<3>[ 22.829743] c0 Buffer I/O error on device mmcblk1, logical block 0
Click to expand...
Click to collapse
To me this sounds like a dead SD card (can't test though, no other SD reader), but even without the SD card the phone refuses to boot :/
Any idea how to get at least the phone booting again or where to look for errors?
When doing a dmesg|grep mmc without the SD, I get
dmesg|grep mmc
<6>[ 2.035409] c1 dw_mmc dw_mmc: clock source 0: sclk_dwmci (80000000 Hz)
<3>[ 2.035839] c1 mmc0: Version ID 0x5342230a.
<6>[ 2.036227] c1 mmc0: FIFO WMARK FOR RX 0x20 WX 0x10. ###########
<6>[ 2.036920] c1 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<6>[ 2.037542] c1 s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (8888888 Hz)
<6>[ 2.037914] c1 mmc1: vtf_2.8v regulator found
<7>[ 2.038207] c1 Registered led device: mmc1::
<6>[ 2.039448] c0 sdhci_set_ios : MMC Card ON samsung-hsmmc
<6>[ 2.039522] c0 mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 2.039802] c0 mmc1: card removed.
<6>[ 2.039929] c0 s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (8888888 Hz)
<3>[ 2.040095] c0 mmc2: no vmmc regulator found
<7>[ 2.040405] c0 Registered led device: mmc2::
<6>[ 2.040749] c0 mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 2.065390] c0 mmc0: cmd 52 response timeout error
<3>[ 2.065799] c0 mmc0: cmd 52 response timeout error
<3>[ 2.071569] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071985] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072351] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072712] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073074] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073460] c0 mmc0: cmd 55 response timeout error
<3>[ 2.073840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074218] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074596] c0 mmc0: cmd 55 response timeout error
<6>[ 2.096913] c0 mmc0: VYL00M: 15010056594c30304d196b9c70418ed1
<4>[ 2.109437] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109486] c0 mmc0: power class selection to bus width 8 failed
<4>[ 2.109746] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109795] c0 mmc0: power class selection to bus width 8 ddr 2 failed
<6>[ 2.110081] c0 mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.110881] c0 mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.117703] c0 mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
<6>[ 2.175199] c1 sdhci_set_ios : MMC Card OFF samsung-hsmmc
<6>[ 3.776696] c1 EXT4-fs (mmcblk0p9): recovery complete
<6>[ 3.776832] c1 EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.001439] c0 EXT4-fs (mmcblk0p7): recovery complete
<6>[ 4.001574] c0 EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 5.878636] c0 EXT4-fs (mmcblk0p10): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.892909] c0 EXT4-fs (mmcblk0p10): recovery complete
<6>[ 5.892945] c0 EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts:
<6>[ 15.762233] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762407] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762519] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762628] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
nokiamodeln91 said:
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
Click to expand...
Click to collapse
A nandroid backup would backup to the SD card, which is a) totally full and b) presumed dead, I'd need something that works over USB...
What can it be backed up to internal storage?
nokiamodeln91 said:
What can it be backed up to internal storage?
Click to expand...
Click to collapse
Internal storage is full to the brim, too, and I dont have any money left to buy other SD card. Also, won't the internal storage be overwritten by flashing ROM?
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
nokiamodeln91 said:
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
Click to expand...
Click to collapse
Yeah, I'm pulling the card contents now, will need two hours - lol, 2.8MB/s transfer speed! -.-
Looks like the memory has issues. I can not make a backup of /data - it always crashes somewhere. Either it locks up or it reboots without errormessage.
When doing a tar cvf /emmc/data.tar /data, it always crashes at data/log/dumpstate_ril_RESET_BY_CP_SILENTRESET_20130422194108.log; I'll just exclude data/log and try again - but is it possible that I have a defective memory chip?!
Try running a scan in recovery.
e2fsck - f - c - y /dev/block/mmcblk0p10
****. Apparently I have one of the broken ones:
/sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001 # cat name hwrev fwrev manfid oemid date type serial cid
cat name hwrev fwrev manf
id oemid date type serial cid
VYL00M
0x0
0x0
0x000015
0x0100
08/2011
MMC
0x6b9c7041
15010056594c30304d196b9c70418ed1
Click to expand...
Click to collapse
Can I somehow scan for defective blocks and "blank" them like with badblocks on a PC?
I had a look in the last_kmsg and saw that xposed was getting a mention
Code:
[31786.019327 / 07-02 01:11:32.755] SysRq : Emergency Remount R/O
[31786.059022 / 07-02 01:11:32.795] IRQ40 no longer affine to CPU1
[31786.121847 / 07-02 01:11:32.855] EXT4-fs (mmcblk0p43): re-mounted. Opts: (null)
[31786.131331 / 07-02 01:11:32.865] EXT4-fs (mmcblk0p37): re-mounted. Opts: (null)
[31786.133075 / 07-02 01:11:32.865] EXT4-fs (mmcblk0p36): re-mounted. Opts: (null)
[31786.134943 / 07-02 01:11:32.875] EXT4-fs (mmcblk0p38): re-mounted. Opts: (null)
[31786.137818 / 07-02 01:11:32.875] EXT4-fs (mmcblk0p41): re-mounted. Opts: (null)
[31786.140658 / 07-02 01:11:32.875] EXT4-fs (mmcblk0p19): re-mounted. Opts: (null)
[31786.151057 / 07-02 01:11:32.885] Emergency Remount complete
[31786.232682 / 07-02 01:11:32.965] mdss_fb_release_all: try to close unopened fb 2! from busybox-xposed
[31786.232754 / 07-02 01:11:32.965] mdss_fb_release_all: try to close unopened fb 1! from busybox-xposed
[31786.233151 / 07-02 01:11:32.965] mdss_fb_release_all: WARN:mfd->ref=1 < pinfo->ref=2
[31786.233167 / 07-02 01:11:32.965] mdss_fb_release_all: unknown process busybox-xposed pid=13988 mfd->ref=0
[31786.243149 / 07-02 01:11:32.975] mdss_fb_blank_sub: fb0 BLANK +
[31786.243166 / 07-02 01:11:32.975] mdss_mdp_overlay_off: fb0 BLANK +
[31786.243182 / 07-02 01:11:32.975] mdss_dsi_blank+:
[31786.243195 / 07-02 01:11:32.975] mdss_dsi_panel_off+: ctrl=e041c810 ndx=0
[31786.243211 / 07-02 01:11:32.975] mdss_dsi_panel_off:-
[31786.243221 / 07-02 01:11:32.975] mdss_dsi_blank-:End
[31786.243233 / 07-02 01:11:32.975] mdss_dsi_blank+:
[31786.243252 / 07-02 01:11:32.975] mdss_dsi_panel_off+: ctrl=e041d010 ndx=1
[31786.399687 / 07-02 01:11:33.135] mdss_dsi_panel_off:-
[31786.399742 / 07-02 01:11:33.135] mdss_dsi_blank-:End
[31786.399793 / 07-02 01:11:33.135] mdss_dsi_off+: ctrl=e041c810 ndx=0
[31786.430764 / 07-02 01:11:33.165] mdss_dsi_off-:
[31786.430778 / 07-02 01:11:33.165] mdss_dsi_off+: ctrl=e041d010 ndx=1
[31786.500341 / 07-02 01:11:33.235] mdss_dsi_off-:
[31786.506362 / 07-02 01:11:33.245] mdss_mdp_mixer_free: called with ref_cnt=0
[31786.506380 / 07-02 01:11:33.245] mdss_mdp_mixer_free: called with ref_cnt=0
[31786.506396 / 07-02 01:11:33.245] mdss_mdp_overlay_off: fb0 BLANK -
[31786.506423 / 07-02 01:11:33.245] mdss_fb_blank_sub: fb0 BLANK -
[31786.507072 / 07-02 01:11:33.245] uei_irrc_shutdown
[31786.507466 / 07-02 01:11:33.245] Restarting system.
[31786.507955 / 07-02 01:11:33.245] Going down for restart now
[31786.508924 / 07-02 01:11:33.245] Calling SCM to disable SPMI PMIC arbiter
No errors detected
UTS_VERSION
Anyone have any idea on what's going wrong here?
"busybox-xposed" is only used during (un-) installation of Xposed. Can you confirm that this happened while you were trying to do this? Also a bit before that, it says something about "Emergency Remount R/O" - this sounds similar to a "feature" of some HTC phones which panic if /system is mounted r/w. If a device/kernel does that, it might as well reboot... what's in the log before that? Here it says that it might be due to a badly formatted filesystem: https://groups.google.com/forum/#!msg/android-building/kSXumkT9-oc/oFooPNNptD0J
rovo89 said:
"busybox-xposed" is only used during (un-) installation of Xposed. Can you confirm that this happened while you were trying to do this? Also a bit before that, it says something about "Emergency Remount R/O" - this sounds similar to a "feature" of some HTC phones which panic if /system is mounted r/w. If a device/kernel does that, it might as well reboot... what's in the log before that? Here it says that it might be due to a badly formatted filesystem: https://groups.google.com/forum/#!msg/android-building/kSXumkT9-oc/oFooPNNptD0J
Click to expand...
Click to collapse
Nope, I'm neither installing or uninstalling, I've installed and it's just running in the background when the reboot happens. Also this is an LG G3 running the ROM it ships with. Regards to Xposed, I merely used towel root and then Xposed and it's just been running with the random reboots.
Code:
[31775.475128 / 07-02 01:11:22.215] [Touch] 1 finger pressed : <0> x[ 961] y[1303] z[ 52]
[31775.642713 / 07-02 01:11:22.375] [Touch] touch_release[ ] : <0> x[ 797] y[1734]
[31777.964802 / 07-02 01:11:24.705] [DFPSv1|INFO]send_event_to_mdss_display, val=0, freq=50
[31777.964868 / 07-02 01:11:24.705] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps + : trying to fps = 50
[31777.969822 / 07-02 01:11:24.705] mdss_mdp_video_config_fps: mdss_mdp_video_config_fps entering line_cnt : 156, exiting line_cnt = 160
[31777.969888 / 07-02 01:11:24.705] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps - : fps = 50
[31777.969938 / 07-02 01:11:24.705] [DFPSv1|INFO]g3_display_send_event_to_mdss_display: configured to '50' FPS
[31779.755143 / 07-02 01:11:26.495] [Touch] 1 finger pressed : <0> x[ 993] y[1996] z[ 49]
[31779.796927 / 07-02 01:11:26.535] [DFPSv1|INFO]send_event_to_mdss_display, val=1, freq=60
[31779.796945 / 07-02 01:11:26.535] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps + : trying to fps = 60
[31779.808979 / 07-02 01:11:26.545] mdss_mdp_video_config_fps: mdss_mdp_video_config_fps entering line_cnt : 36, exiting line_cnt = 38
[31779.808992 / 07-02 01:11:26.545] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps - : fps = 60
[31779.809003 / 07-02 01:11:26.545] [DFPSv1|INFO]g3_display_send_event_to_mdss_display: configured to '60' FPS
[31779.876026 / 07-02 01:11:26.615] [Touch] touch_release[ ] : <0> x[1130] y[1464]
[31780.304181 / 07-02 01:11:27.045] pet_watchdog
[31780.309022 / 07-02 01:11:27.045] [XO_THERM] Result:33 Raw:32106
[31781.017194 / 07-02 01:11:27.755] [Touch] 1 finger pressed : <0> x[ 351] y[2559] z[ 38]
[31781.045045 / 07-02 01:11:27.785] ImmVibeSPI_ForceOut_AmpEnable : g_bAmpEnabled:0
[31781.045521 / 07-02 01:11:27.785] ImmVibeSPI_ForceOut_AmpEnable : g_bAmpEnabled:1
[31781.065715 / 07-02 01:11:27.805] ImmVibeSPI_ForceOut_AmpEnable : g_bAmpEnabled:1
[31781.096902 / 07-02 01:11:27.835] [Touch] touch_release[ ] : <0> x[ 351] y[2559]
[31781.105565 / 07-02 01:11:27.845] ImmVibeSPI_ForceOut_AmpDisable : g_bAmpEnabled:1
[31781.106114 / 07-02 01:11:27.845] ImmVibeSPI_ForceOut_AmpDisable : g_bAmpEnabled:0
[31781.844425 / 07-02 01:11:28.585] IRQ40 no longer affine to CPU2
[31782.936472 / 07-02 01:11:29.675] [DFPSv1|INFO]send_event_to_mdss_display, val=0, freq=50
[31782.936534 / 07-02 01:11:29.675] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps + : trying to fps = 50
[31782.942546 / 07-02 01:11:29.675] mdss_mdp_video_config_fps: mdss_mdp_video_config_fps entering line_cnt : 46, exiting line_cnt = 51
[31782.942604 / 07-02 01:11:29.675] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps - : fps = 50
[31782.942652 / 07-02 01:11:29.675] [DFPSv1|INFO]g3_display_send_event_to_mdss_display: configured to '50' FPS
[31783.036307 / 07-02 01:11:29.775] [Touch] 1 finger pressed : <0> x[1203] y[ 47] z[ 48]
[31783.080929 / 07-02 01:11:29.815] [DFPSv1|INFO]send_event_to_mdss_display, val=1, freq=60
[31783.080949 / 07-02 01:11:29.815] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps + : trying to fps = 60
[31783.082262 / 07-02 01:11:29.815] mdss_mdp_video_config_fps: mdss_mdp_video_config_fps entering line_cnt : 6, exiting line_cnt = 9
[31783.082275 / 07-02 01:11:29.815] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps - : fps = 60
[31783.082286 / 07-02 01:11:29.815] [DFPSv1|INFO]g3_display_send_event_to_mdss_display: configured to '60' FPS
[31783.177841 / 07-02 01:11:29.915] [Touch] touch_release[ ] : <0> x[ 585] y[ 603]
[31784.174342 / 07-02 01:11:30.915] [DFPSv1|INFO]send_event_to_mdss_display, val=0, freq=50
[31784.174362 / 07-02 01:11:30.915] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps + : trying to fps = 50
[31784.182579 / 07-02 01:11:30.915] mdss_mdp_video_config_fps: mdss_mdp_video_config_fps entering line_cnt : 46, exiting line_cnt = 50
[31784.182596 / 07-02 01:11:30.915] mdss_mdp_ctl_update_fps: mdss_mdp_ctl_update_fps - : fps = 50
[31784.182612 / 07-02 01:11:30.915] [DFPSv1|INFO]g3_display_send_event_to_mdss_display: configured to '50' FPS
[31785.356677 / 07-02 01:11:32.095] [Touch] 1 finger pressed : <0> x[ 914] y[1055] z[ 31]
[31785.444714 / 07-02 01:11:32.185] [Touch] touch_release[ ] : <0> x[ 913] y[1055]
[31785.755094 / 07-02 01:11:32.495] send sigkill to 13556 (earchbox:search), adj 764, size 9312
[31785.822724 / 07-02 01:11:32.555] mmc0: mmc_start_bkops: raw_bkops_status=0x2, from_exception=1
@rovo89 any news? Did the additional log text help?
No, unfortunately not. As I mentioned, "busybox-xposed" is only used during (un-)installation. It's even deleted afterwards, so I don't see how it should be running in the background. To me, it looks more like improper resource management in the kernel or someting like that. Maybe you can take this to a kernel dev who can interpret the kmsg log better than me and knows what can trigger this "Emergency Remount R/O".
@rovo89 I've been testing and it's simply down to Xposed not installing properly. I think this device has fastboot enabled or something. Apparently it was an issue on some Samsung's too. Is there any way you can make sure the installation finishes properly before prompting the reboot?
You will only get the reboot prompt if all the commands to install Xposed were executed successfully. I don't see what else I should do there.
rovo89 said:
You will only get the reboot prompt if all the commands to install Xposed were executed successfully. I don't see what else I should do there.
Click to expand...
Click to collapse
is there a debug version I can install to help diagnose the problem?
No. What should it log? Any errors are already shown. If you want to debug it step by step, the source is available here: https://github.com/rovo89/XposedInstaller
rovo89 said:
No. What should it log? Any errors are already shown. If you want to debug it step by step, the source is available here: https://github.com/rovo89/XposedInstaller
Click to expand...
Click to collapse
Honestly, I have no idea. I'm simply an end user trying to do all I can do to get the app working. There's clearly something failing hence why after I've installed there's crashes with the log showing references to something that should've been removed. Thus I'd surmise something is failing prior to the supposed removal. Maybe a debug version can print something after every command in order to pinpoint the faulty command and then we can look for a workaround?
sabret00the said:
Maybe a debug version can print something after every command in order to pinpoint the faulty command and then we can look for a workaround?
Click to expand...
Click to collapse
I really wouldn't know what to print there and what this could verify. As I said - if any of the commands hangs or shows unwanted results, you wouldn't even get the reboot prompt.
Took a look and thats what I think:
- the system is working fine, no signs of troublse (at least no signs within the logged stuff).
- immediately something called "mmc0: mmc_start_bkops: raw_bkops_status=0x2, from_exception=1" happens. It's undoubtly some kind of error related to mmc0 = internal memory (equals to WHOLE nand in a typical configuration). Neverthless of what happens next, this is the event that triggers further steps leading to sys collapse. Also it does not look like something you should totały ignore, as it is always possible that its caused by a hardware failure resulting in disconnecting nand from time to time, however the chance is small... well, i wouldn't be surprised if it is a something natural that read failures happen on every system from time to time . It would be a good idea to investigate further into this issue as it may be everything or even nothing. Maybe ef2fsck -y mmcblk* of all ext4 partitions will help? Check if ext4 filesystems are mounted with barrier=1 and remount if the answer is no; maybe set a different governor or check io_scheduler settings like nomerges which is recommended to be 1 at least, if you have touched it in any way or if you are using some tweaking app...
- sysrq 40 is called due to discussed failure. Sysrq is a linux interface providing possibility of echo'eing some values to call various system reactions, including forcing kernel panic, syncing data, shutting something down, etc random stuff. It is turned off by default on Android as it is more applicable for desktop pcs with harddisks etc. I also think that we should worry about why something opens up sysrq access and dont care about the fact that something was allowed to sendit, guess calling sysrqs remained from linux code.
Any sysctl tweaking recently?
The most possible solution that may stop the reboots is to turn off depreciated sysrq support so no strange actions, some of them probably not tested within android at all, shall happen.
echo 0 > /proc/sys/kernel/sysrq
chmod 000 /proc/sys/kernel/sysrq
You may want to run above commandś using init.d script on boot.
Please however remember that it is your responsibility for what you'll do and there is a light chance that if the real issue is the hardware, disabling the security exit for the system giveś some risk of blowing something up ;]
The most recommended solution is to either diagnose and solve mmc0 error or/and find out what may be the cause of opening such a depreciated interface as sysrq at all.
- first action after receiving signal is short and is CPU related. No idea what happens here - maybe it is some kind of reset given to the core which iś responsible for mmc0 support, or i dunno...
- second action is a procedure of remounting some partitions as read-only. I wonder if it is triggered just to stop writing operations before reboot or it is causing the reboot because it is designed for desktop linux pcs, not for mmc/android devices, ill bet the 2nd one is a winner.
- amount of ext4 devices suggest that /data and other standard partitions were included without exceptions.
- all partitions are probably remounted as ro. Nothing can write nowhere. Some stuff starts to call first warnings, iincluding xposed process, which is not the cause but the victim. Even android cannot save anything for any purposes anywhere. And soon....
...something worse than warning happened. Something fragile stopped working due to writing denial. Reboot.
I guess Android finally dies in a result of numerous failures caused by the fact that no data can be written to physical memory by any system component or any other element.
Summarize: something is opening sysrq support, guess not the best idea...? Solution: close it, lock it, investigate into why it is opened and what causes that it becomes open.Anyway, after some time, unpredictable suspicious event related to mmc0 of unknown origin happens, may be dangerous! However, event causes system to initiate procedure which consist of disabling write access to any partition. In short time various failures happened and as Android was designed with assumption of 24/7 rw mounted /data plus also using /cache is impossible reboot happens.
Hi,
I flashed Motorola Camera on CM12.1. Previously I was using the standard AOSP Camera (through lockscreen and without and was working fine). For some reason I get soft-reboots whenever I try to access the gallery through the camera (by swiping to the right and reviewing previous images). This happens whenever using the Camera (phone locked or unlocked). I checked last_kmsg and logcat before the crash and this is what I see.
last_kmsg
[ 5.433023,0] SELinux: Context u : object_r:system_app_data_file:s0 is not valid (left unmapped).
[ 48.948115,0] SELinux: Context u : object_r: property_data_file:s0 is not valid (left unmapped).
[ 48.980253,0] SELinux: Context u : object_r:dalvikcache_profiles_data_file:s0 is not valid (left unmapped).
[ 49.282191,0] SELinux: Context u : object_r:resourcecache_data_file:s0 is not valid (left unmapped).
[ 88.358431,0] SELinux: Context u : object_r:mpctl_data_file:s0 is not valid (left unmapped).
[ 88.383763,0] SELinux: Context u : object_r:theme_data_file:s0 is not valid (left unmapped).
[ 88.395849,0] SELinux: Context u : object_r:system_ndebug_socket:s0 is not valid (left unmapped).
[ 88.677949,0] SELinux: Context u : object_r:time_data_file:s0 is not valid (left unmapped).
[ 88.698061,0] SELinux: Context u : object_r:install_data_file:s0 is not valid (left unmapped).
[ 88.699191,0] SELinux: Context u : object_r:batt_health_data_file:s0 is not valid (left unmapped).
[ 88.731817,0] SELinux: Context u : object_r:adb_data_file:s0 is not valid (left unmapped).
[ 88.767404,0] zcache: created ephemeral tmem pool, id=1, client=65535
[ 88.767862,0] EXT4-fs (mmcblk0p38): mounted filesystem with ordered data mode. Opts:
[ 88.768960,0] zcache: destroyed pool id=1, cli_id=65535
[ 89.992705,0] zcache: created ephemeral tmem pool, id=1, client=65535
[ 89.992888,0] EXT4-fs (mmcblk0p38): mounted filesystem with ordered data mode. Opts: (null)
[ 89.998107,0] EXT4-fs (mmcblk0p38): re-mounted. Opts: data=ordered
[ 90.000976,0] EXT4-fs (mmcblk0p38): re-mounted. Opts: (null)
[ 92.435495,0] warning: `su' uses 32-bit capabilities (legacy support in use)
[ 97.439768,0] zcache: destroyed pool id=1, cli_id=65535
[ 99.921745,0] SysRq : Emergency Remount R/O
[ 100.251457,0] EXT4-fs (mmcblk0p36): re-mounted. Opts: (null)
[ 100.251701,0] Emergency Remount complete
[ 100.457836,0] panel_power_ctrl (0) is called
[ 100.457866,0] synaptics_dsx_panel_cb: PANEL PWR-OFF
[ 100.470135,0] pn544 reboot notification received
[ 100.470166,0] pn544_dev_ioctl ven_logic_high = 1.
[ 100.470166,0] pn544_dev_ioctl ven_logic_low = 0.
[ 100.470196,0] pn544_dev_ioctl discharge_delay = 0.
[ 100.470227,0] pn544_dev_ioctl : power off
[ 102.494155,0] pn544 calling ioctl power off returned = 0
[ 102.494155,0] mmc0: reboot notification received
[ 103.002899,0] msm_fb_release: try to close unopened fb 2!
[ 103.002960,0] msm_fb_release: try to close unopened fb 1!
[ 103.354158,0] mdp4_dsi_cmd_off: Error, SET_CLK_OFF by force
[ 103.354860,0] panel_disable is called
[ 103.355226,0] panel_disable completed
[ 103.355470,0] panel_power_ctrl (2) is called
[ 103.361025,0] MFD is Null
[ 103.362215,0] Restarting system with command ''.
[ 103.372928,0] Current task:init(1) Parent task:swapper/0(0)
[ 103.373233,0] Going down for restart now
PREV
Linux version 3.4.99-g329cc7b ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Mar 25 05:57:42 UTC 2015
THIS
ABOOT.GIT = MBM-NG-V30.71-0-g913941e
TZ.GIT = MBM-NG-V30.71-0-g0dbc2ca
RPM.GIT = MBM-NG-V30.71-0-gc35359a
SBL3.GIT = MBM-NG-V30.71-0-gcee9d3f
SBL2.GIT = MBM-NG-V30.71-0-gcee9d3f
SBL1.GIT = MBM-NG-V30.71-0-gcee9d3f
Linux version 3.4.42-gfd15b99 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Jun 3 20:46:07 PDT 2015
RAM: Samsung, S4 SDRAM, 2048 MB, MR5:0x01, MR6:0x11, MR7:0x00, MR8:0x18
ACPU Krait PVS: 4 Hexagon: 4 Fuse: 0x41000
socinfo: id=138, ver=1.1, raw_id=2017, raw_ver=1, hw_plat=0, hw_plat_ver=65536, hw_plat_subtype=0
No errors detected
#############
Current Boot info:
POWERUPREASON: 0x00004000
console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.write_protect=0 androidboot.emmc=true androidboot.serialno=T076000OVM androidboot.baseband=msm androidboot.mode=normal androidboot.bootloader=0x3071 androidboot.cid=0x9 androidboot.hwrev=0x8300 androidboot.radio=0x6 battery= mot_sst=0 androidboot.modelno="Moto X" product=ghost androidboot.device=ghost androidboot.secure_hardware=1 androidboot.write_protect=0 [email protected]_retail:/ $
Click to expand...
Click to collapse
logcat
D/CloudNode(25537): handleSyncResponse: seqId 192217
D/CloudNode(25537): setting mLastSentSeqId to 192217
I/MDMCTBK ( 268): NetlinkHandler, power_supply subsys
I/MDMCTBK ( 268): NetlinkHandler, usbChargerStateChanged
I/MDMCTBK ( 268): MdmCutbackHndler,readFromFile = /sys/class/power_supply/usb/online
I/MDMCTBK ( 268): MdmCutbackHndler,readFromFile = /sys/class/power_supply/pm8921-dc/online
D/HeadsetStateMachine(28027): Disconnected process message: 10, size: 0
D/ZWSleepReceiver(26378): Received: android.intent.action.BATTERY_CHANGED
W/CursorWrapperInner( 2321): Cursor finalized without prior close()
W/CursorWrapperInner( 2321): Cursor finalized without prior close()
V/GCMBroadcastReceiver(27429): onReceive: com.google.android.c2dm.intent.RECEIVE
V/GCMBroadcastReceiver(27429): GCM IntentService class: de.gmx.mobile.android.mail.GCMIntentService
V/GCMBaseIntentService(27429): Acquiring wakelock
V/GCMBaseIntentService(27429): Intent service name: GCMIntentService-388120349134,1030161858651,506544515496-1
V/GCMBaseIntentService(27429): Releasing wakelock
I/PowerManagerService(24855): Going to sleep due to screen timeout (uid 1000)...
D/k9 (27429): setPaymailStatus(7e0e12d0-cd58-4b68-b772-bf9cbb0e34b1, SHOWBANNER)
I/DisplayManagerService(24855): Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 1280, 60.0 fps, supportedRefreshRates [60.0], density 320, 315.31 x 315.65 dpi, appVsyncOff 0, presDeadline 17666667, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
D/SurfaceFlinger( 244): Set power mode=0, type=0 flinger=0xb6082000
D/qdhwcomposer( 244): hwc_blank: Blanking display: 0
V/ActivityManager(24855): Display changed displayId=0
D/qdhwcomposer( 244): hwc_blank: Done blanking display: 0
D/SurfaceControl(24855): Excessive delay in setPowerMode(): 198ms
I/QCOM PowerHAL(24855): Got set_interactive hint
I/PowerManagerService(24855): Sleeping (uid 1000)...
D/AndroidRuntime(24855): Shutting down VM
E/AndroidRuntime(24855): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime(24855): java.lang.IllegalArgumentException: Comparison method violates its general contract!
E/AndroidRuntime(24855): at java.util.TimSort.mergeHi(TimSort.java:864)
E/AndroidRuntime(24855): at java.util.TimSort.mergeAt(TimSort.java:481)
E/AndroidRuntime(24855): at java.util.TimSort.mergeForceCollapse(TimSort.java:422)
E/AndroidRuntime(24855): at java.util.TimSort.sort(TimSort.java:219)
E/AndroidRuntime(24855): at java.util.TimSort.sort(TimSort.java:169)
E/AndroidRuntime(24855): at java.util.Arrays.sort(Arrays.java:2010)
E/AndroidRuntime(24855): at java.util.Collections.sort(Collections.java:1883)
E/AndroidRuntime(24855): at com.android.server.IntentResolver.sortResults(IntentResolver.java:504)
E/AndroidRuntime(24855): at com.android.server.IntentResolver.queryIntent(IntentResolver.java:459)
E/AndroidRuntime(24855): at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16410)
E/AndroidRuntime(24855): at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16579)
E/AndroidRuntime(24855): at android.app.ContextImpl.sendOrderedBroadcastAsUser(ContextImpl.java:1524)
E/AndroidRuntime(24855): at android.app.ContextImpl.sendOrderedBroadcastAsUser(ContextImpl.java:1495)
E/AndroidRuntime(24855): at com.android.server.power.Notifier.sendGoToSleepBroadcast(Notifier.java:483)
E/AndroidRuntime(24855): at com.android.server.power.Notifier.sendNextBroadcast(Notifier.java:450)
E/AndroidRuntime(24855): at com.android.server.power.Notifier.access$300(Notifier.java:69)
E/AndroidRuntime(24855): at com.android.server.power.Notifier$NotifierHandler.handleMessage(Notifier.java:513)
E/AndroidRuntime(24855): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(24855): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(24855): at com.android.server.SystemServer.run(SystemServer.java:298)
E/AndroidRuntime(24855): at com.android.server.SystemServer.main(SystemServer.java:186)
E/AndroidRuntime(24855): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(24855): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(24855): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime(24855): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
Click to expand...
Click to collapse
Ideas anyone?? I prefer Motorola camera so it would be great if I don't have to revert back.
Hi,
i just wanted to give some information on my latest attempts to boot kernel 4.11 on the Nexus 5.
This is just for fun or at least a proof of concept to boot mainline kernel.
Have a look at bootup text file attached to this post.
You may first see my other post here:
https://forum.xda-developers.com/showpost.php?p=72681973&postcount=13
As i already stated this "project" is of no real practical use, other then learning about latest kernel and getting used to DTS files.
Many parts are missing and booting into Android would be a very dusty and rocky road... it is more that this will never happen!
Anyway i decided to switch to kernel 4.11, as there'd been some improvements on some SoC internals (e.g. USB).
So i took this kernel:
https://git.linaro.org/landing-team...shot/kernel-release/db820c/qcomlt-4.11.tar.gz
After some first tests i decided to check out more options in the kernel config file to get little nearer to the 3.4 kernel config we all know.
You'll find the config file below.
In order to do some testing easily i decided to use TWRP recovery as an initrd here.
To make it more handy i simply added a service to get a console shell.
In other words, there's busybox and some other tools to examine the system.
The image uses the serial debug console as the user interface.
To interact with the system you'll need an earjack debug adapter.
See the image (debug_3.5mm.jpg) for some information... or search the web.
To boot the image, unzip hammerhead-4.11.zip go into bootloader mode and use fastboot:
fastboot boot hammerhead-4.11.img
EDIT: Updated the attachments, as there'd been some progress (see post #7).
EDIT2: YAU (Yet Another Update)
Have fun!
scholbert
Nice job!
Some time ago I tried to build from scratch 3.10 kernel, you can find the code here.
From the log look like that the internal memory is missing, maybe due incomplete device tree entry. The related documentation should be this.
Hi 95A31!
95A31 said:
Nice job!
Some time ago I tried to build from scratch 3.10 kernel, you can find the code here.
From the log look like that the internal memory is missing, maybe due incomplete device tree entry. The related documentation should be this.
Click to expand...
Click to collapse
Thanks for your reply. Any hints and ideas are higly appreciated
Basically the sdhc entries look o.k. to me.
I already compared many parts of the DT entries in kernel 4.11 with the ones in kernel 3.4 as well (and yes they slightly changed their style).
There might be some issues with DT in general here, but i suspect some basic stuff is missing to initiate the power supply (PM8841 & PM8941) correctly.
Maybe i'll dig a little deeper... maybe not :angel:
Anyway, leave some comments here if you like!
Cheers,
scholbert
scholbert said:
...
There might be some issues with DT in general here, but i suspect some basic stuff is missing to initiate the power supply (PM8841 & PM8941) correctly.
....
Click to expand...
Click to collapse
What make you think this?
Gonna test it on my phone.
95A31 said:
What make you think this?
Click to expand...
Click to collapse
See those snippets from bootlog of kernel 3.4:
Code:
...
[ 0.143223] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.144749] socinfo_print: v8, id=126, ver=2.2, raw_id=1968, raw_ver=7, hw_plat=150, hw_plat_ver=65536
[ 0.144755] accessory_chip=0, hw_plat_subtype=0, pmic_model=65537, pmic_die_revision=196609
[ 0.158993] gpiochip_add: registered GPIOs 0 to 145 on device: msmgpio
[ 0.175335] msm_watchdog f9017000.qcom,wdt: MSM Watchdog Initialized
[ 0.194446] 8841_s1: 675 <--> 1050 mV at 0 mV normal idle
[ 0.194895] 8841_s1_ao: 675 <--> 1050 mV at 0 mV normal idle
[ 0.195357] 8841_s1_so: 675 <--> 1050 mV at 675 mV normal idle
[ 0.195859] 8841_s2: 500 <--> 1050 mV at 0 mV normal idle
[ 0.196322] 8841_s2_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.196785] 8841_s2_corner_ao: 0 <--> 0 mV at 0 mV normal idle
[ 0.197235] 8841_s2_floor_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.197723] 8841_s3: 1050 mV normal idle
[ 0.198201] 8841_s4: 815 <--> 900 mV at 0 mV normal idle
[ 0.198675] 8841_s4_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.199145] 8841_s4_floor_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.199630] 8941_s1: 1300 mV normal idle
[ 0.200131] 8941_s2: 2150 mV normal idle
[ 0.200614] 8941_s3: 1800 mV normal idle
[ 0.201146] 8941_l1: 1225 mV normal idle
[ 0.201627] 8941_l2: 1200 mV normal idle
[ 0.202120] 8941_l3: 1225 mV normal idle
[ 0.202608] 8941_l4: 1225 mV normal idle
[ 0.203117] 8941_l5: 1800 mV normal idle
[ 0.203599] 8941_l6: 1800 mV normal idle
[ 0.204088] 8941_l7: 1800 mV normal idle
[ 0.204588] 8941_l8: 1800 mV normal idle
[ 0.205066] 8941_l9: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.205554] 8941_l10: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.206025] 8941_l11: 1300 mV normal idle
[ 0.206520] 8941_l12: 1800 mV normal idle
[ 0.206982] 8941_l12_ao: 1800 mV normal idle
[ 0.207462] 8941_l13: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.207961] 8941_l14: 1800 mV normal idle
[ 0.208434] 8941_l15: 2050 mV normal idle
[ 0.208930] 8941_l16: 2700 mV normal idle
[ 0.209418] 8941_l17: 3000 mV normal idle
[ 0.209909] 8941_l18: 2850 mV normal idle
[ 0.210405] 8941_l19: 3000 <--> 3300 mV at 3300 mV normal idle
[ 0.210917] 8941_l20: 2950 mV normal idle
[ 0.211414] 8941_l21: 2950 mV normal idle
[ 0.211907] 8941_l22: 3000 <--> 3300 mV at 3100 mV normal idle
[ 0.212411] 8941_l23: 3000 mV normal idle
[ 0.212898] 8941_l24: 3075 mV normal idle
[ 0.213387] 8941_lvs1:
[ 0.213821] 8941_lvs2:
[ 0.214265] 8941_lvs3:
...
...and these messages from kernel 4.11:
Code:
...
[ 0.213352] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.215005] cpuidle: using governor menu
[ 0.215647] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.215657] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.216665] irq: no irq domain found for /smp2p-adsp/slave-kernel !
[ 0.232062] irq: no irq domain found for /soc/[email protected] !
[ 0.251356] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[ 0.251635] reg-fixed-voltage vreg-boost: could not find pctldev for node /soc/[email protected]/[email protected]/[email protected]/boost-bypass, deferring probe
...
Regards,
scholbert
Hey,
short update... found something to get the messages from PMIC :victory:
There was a missing option in my configuration. We need CONFIG_RPMSG_QCOM_SMD to be set.
Unfortunately still no sign from the eMMC ...
EDIT: grrrrr... still some issues here.
If RPM shared memory driver gets activated, this seems to change some setup in clock unit of the chip, which as a result disables RTC or destroys something else.
So in the end i'm not sure if shared memory driver should be used here
Anyway will play around with all this in the next weeks... but remember it's summer... so it may all take it's time!
EDIT2: yeeeessssss.. some issues solved!
I forgot that i made a change in dtsi which seemed to block the interrupt to smbi... in the end reverted it, applied new configuration, and there it is.
We got eMMC now :highfive:
See new attached files and have anice weekend!
EDIT3: Moved the attachments to the first post!
BTW, there's a guy at the fairphone forum who does similar experiments with the FP2 (MSM8974 based as well):
https://forum.fairphone.com/t/kernel-hackers-upstream-kernel-for-fp2-openos/28628
Here's his github repo:
https://github.com/z3ntu/linux
Regards,
scholbert
scholbert said:
Hey,
short update... found something to get the messages from PMIC :victory:
There was a missing option in my configuration. We need CONFIG_RPMSG_QCOM_SMD to be set.
Unfortunately still no sign from the eMMC ...
[...]
Click to expand...
Click to collapse
Good job!
Look like system can not access to memory:
Code:
[ 1.800624] init: /init.rc: 66: invalid command 'load_system_props'
Code:
[ 1.995481] init: /init.recovery.hammerhead.rc: 17: invalid command '/sbin/ln'
Maybe the change msm_sdcc.1 -> f9824900.sdhci had broke something. Before the kernel messages I have this part in my logs:
Code:
[7040] use_signed_kernel=0, is_unlocked=1, is_tampered=1.
[7040] Loading boot image (9416704): start
[7380] Loading boot image (9416704): done
[7380] Found Appeneded Flattened Device tree
[7380] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[7390] get_display_kcal = 0, 0, 0, x
[7390]
Booting Linux
[7440] vibe
[7540] splash: boot
[7580] splash: unlocked
[7620] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 msm_watchdog_v2.enable=1 mdss_mdp.panel=dsi androidboot.bootdevice=msm_sdcc.1 uart_console=enable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emmc=[7640] Updating device tree: start
[7650] Updating device tree: done
[7660] booting linux @ 0x8000, ramdisk @ 0x2900000 (1115413), tags/device tree @ 0x2700000
[7660] Turn off MIPI_CMD_PANEL.
[7660] Continuous splash enabled, keeping panel alive.
Uncompressing Linux... done, booting the kernel.
Can be the value of androidboot.bootdevice related with this problem?
Here a Linaro guy is working on Nexus 7 (APQ8064 based unfortunately).
EDIT:
Moreover fstab.hammerhead use msm_sdcc.1 and this is wrong for sure.
Hi 95A31,
thanks for your comments and information about the Nexus 7 project.
The errors you find in the logs are related to the TWRP initrd and setup stuff.
Please refer to these messages i grabbed some time ago from the standard TWRP image:
Code:
...
[ 5.341167] init: /init.rc: 66: invalid command 'load_system_props'
[ 5.346559] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
[ 5.353919] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
[ 5.362647] healthd: wakealarm_init: timerfd_create failed
[ 5.863315] android_usb: already disabled
[ 6.134887] init: Unable to open persistent property directory /data/property errno: 2
[ 6.141831] init: Unable to open persistent property directory /data/property errno: 2
...
As you see it's barely the same stuff printed out (independent of the kernel you use).
You may modify the initrd as you like to
The partitions can be mounted and accessed from serial console with this kernel now:
Code:
~ # mount -t ext4 /dev/block/mmcblk0p28 /data
[ 237.878280] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 968568 28 968540 0% /dev
tmpfs 968568 288 968280 0% /tmp
/dev/block/mmcblk0p28
27971732 10849488 17105860 39% /data
~ # cd data
/data # ls
adb backup data media security
anr bootchart drm mediadrm ss
app bugreports fdAlbum misc su
app-asec cam_socket1 local nfc system
app-lib cam_socket2 lost+found property tombstones
app-private dalvik-cache maru resource-cache user
/data #
Please check out the expermimental image and try yourself.
Be careful what you do at anytime though, because your dealing with your phones file system from within an experimental ramdisk.
So please do not brick your phone, while playing around :angel:
BTW... speaking of memory is more common for RAM, while storage may be used for eMMC and mass storage devices.
Of course a lot of tweaks and fixes are needed as this is all very experimental, so anyway thanks for your hint.
EDIT: ... and yes as for the numbering and naming this has to be corrected somewhere in time.
The eMMC is detected as device mmc0 (controller sdhci1) for now, because WLAN SDIO (using controller sdhci2) is not implemented yet.
Same for the fstab file.
Someone may try to rename some entries and see what happens, but as far as many parts are missing, there's no need for this right now.
Regards,
scholbert
scholbert said:
[...]
The errors you find in the logs are related to the TWRP initrd and setup stuff.
[...]
Click to expand...
Click to collapse
You are more skilled than me about this topic
scholbert said:
[...]
Someone may try to rename some entries and see what happens, but as far as many parts are missing, there's no need for this right now.
[...]
Click to expand...
Click to collapse
Which should be the next thing to fix?
I attached the list of commits commited by LG in aosp kernel
95A31 said:
You are more skilled than me about this topic
Click to expand...
Click to collapse
Thanks for the flowers
95A31 said:
Which should be the next thing to fix?
Click to expand...
Click to collapse
I would like to get a working usb connection and use adb to communicate with the phone.
This would possibly increase the amount of interested people to check out a console based system on their phone and do some experiments.
I guess there are only a few people who got this earjack adapter or something.
At least the Nexus 5 is an interesting piece of embedded hardware to play with, even if the display got crashed.
95A31 said:
I attached the list of commits commited by LG in aosp kernel
Click to expand...
Click to collapse
Nice! Thanks for the list.
As this refers to AOSP kernel 3.4 it gives a good overview of the patches fixes and changes of course.
For mainline kernel 4.11 this is list would look very different though.
I still concentrate on fine tuning of the kernel configuration, as there are still many things to discover.
To get some Nexus 5 specific device drivers integrated would be nice as well (e.g. check BQ24190/2 code and implement it to DT).
Anyway... always remember this is a just for fun thing.
Could be some educational project if your like, but without all the binary blobs adopted to kernel 4.11 there will never be a working Android.
EDIT:
As for the educational purpose (my very own )
We can sample some interrupts from the PM8941 subsystem very well:
Code:
~ # cat /proc/interrupts
CPU0
18: 8925 GIC-0 20 Level arch_timer
20: 0 GIC-0 39 Level arch_mem_timer
22: 0 GIC-0 194 Edge adsp
23: 0 GIC-0 190 Edge smp2p
24: 0 GIC-0 59 Edge smp2p
25: 0 GIC-0 175 Edge smp2p
26: 1181 GIC-0 139 Level msm_serial0
27: 80 GIC-0 155 Edge mmc0
28: 0 GIC-0 170 Edge f9824900.sdhci
176: 0 GIC-0 127 Level i2c_qup
178: 0 GIC-0 271 Level bam_dma
179: 0 GIC-0 166 Edge msm_otg
186: 0 pmic_arb 6357309 Edge pm8xxx_rtc_alarm
187: 2 pmic_arb 524325 Edge pm8941_pwrkey
188: 0 pmic_arb 1050408 Edge chg-done
189: 0 pmic_arb 1049896 Edge chg-fast
190: 0 pmic_arb 1049640 Edge chg-trkl
191: 0 pmic_arb 1179946 Edge bat-temp-ok
192: 0 pmic_arb 1179690 Edge bat-present
193: 0 pmic_arb 1245739 Edge chg-gone
194: 4 pmic_arb 1245483 Edge usb-valid
195: 0 pmic_arb 1311020 Edge dc-valid
197: 2 pmic_arb 12648535 Edge volume_up
198: 2 pmic_arb 12714072 Edge volume_down
243: 0 GIC-0 188 Edge adsp
244: 0 GIC-0 57 Edge modem
245: 47 GIC-0 200 Edge rpm
246: 0 GIC-0 58 Edge smsm
247: 0 GIC-0 189 Edge smsm
248: 0 GIC-0 176 Edge smsm
249: 0 smp2p 0 Edge adsp
250: 0 smp2p 1 Edge adsp
251: 0 smp2p 2 Edge adsp
252: 0 smp2p 3 Edge adsp
IPI0: 0 CPU wakeup interrupts
IPI1: 0 Timer broadcast interrupts
IPI2: 652 Rescheduling interrupts
IPI3: 5 Function call interrupts
IPI4: 0 CPU stop interrupts
IPI5: 0 IRQ work interrupts
IPI6: 0 completion interrupts
Err: 0
To be more precisely:
volume_up, volume_down, pwrkey and usb-valid are detected and working.
Unfortunately no reaction from the host and no kernel message, when micro usb cable is attached or detached...
Whatever...
Regards,
scholbert
scholbert said:
[..]
I would like to get a working usb connection and use adb to communicate with the phone.
This would possibly increase the amount of interested people to check out a console based system on their phone and do some experiments.
I guess there are only a few people who got this earjack adapter or something.
At least the Nexus 5 is an interesting piece of embedded hardware to play with, even if the display got crashed.
[...]
Click to expand...
Click to collapse
Nice, I hope to have time to seriously play with it and maybe make something work.
scholbert said:
[...]
Anyway... always remember this is a just for fun thing.
Could be some educational project if your like, but without all the binary blobs adopted to kernel 4.11 there will never be a working Android.
[...]
Click to expand...
Click to collapse
I know, I know, sometime I follow my enthusiasm . Yes, blobs are a big problem for a working Android and when I think about how address it, and how much time it will require I die inside
Wow!!!
Hey there,
i just wondered how time goes by
I'm still using my hammerhead for daily use and from time to time i'm searching the web how things are evolving.
This is the coolest project i've seen for a while:
https://github.com/flto/linux/wiki/hammerhead-upstream
Need to do some research who's behind it
Have a nice day!
scholbert