Hey guys,
I just need your opinion or some ideas.
I was wondering why my galaxy s3 was locking up, so I took a look into the kernel output.
So the malfunction is: Phone locks up, no reaction to any key pressing and so on, but I can reboot it by holding the power button.
By having a ssh connection to my phone I can see that when the phone "locks" up the kernel is still living. So there is no kernel panic or what so ever.
After that I got curious, will the lock up go away? And yes, it did. After 30 minutes or so. And after that the phone was working without problems again. Here is the relevant log output of the kernel (/proc/kmesg):
Code:
<3>[26695.166202] c0 mmc0: Timeout waiting for hardware interrupt.
<7>[26695.166317] c0 mshci: ============== REGISTER DUMP ==============
<7>[26695.166440] c0 mshci: MSHCI_CTRL: 0x00000010
<7>[26695.166534] c0 mshci: MSHCI_PWREN: 0x00000001
<7>[26695.166628] c0 mshci: MSHCI_CLKDIV: 0x00000001
<7>[26695.166723] c0 mshci: MSHCI_CLKSRC: 0x00000000
<7>[26695.166814] c0 mshci: MSHCI_CLKENA: 0x00000000
<7>[26695.166907] c0 mshci: MSHCI_TMOUT: 0xffffffff
<7>[26695.167004] c0 mshci: MSHCI_CTYPE: 0x00010000
<7>[26695.167100] c0 mshci: MSHCI_BLKSIZ: 0x00000200
<7>[26695.167192] c0 mshci: MSHCI_BYTCNT: 0x0000f000
<7>[26695.167288] c0 mshci: MSHCI_INTMSK: 0x0000bfce
<7>[26695.167380] c0 mshci: MSHCI_CMDARG: 0x00010000
<7>[26695.167472] c0 mshci: MSHCI_CMD: 0x80202000
<7>[26695.167574] c0 mshci: MSHCI_MINTSTS: 0x00000000
<7>[26695.167666] c0 mshci: MSHCI_RINTSTS: 0x00000030
<7>[26695.167757] c0 mshci: MSHCI_STATUS: 0x01fe6b01
<7>[26695.167860] c0 mshci: MSHCI_FIFOTH: 0x503f0040
<7>[26695.167954] c0 mshci: MSHCI_CDETECT: 0x00000001
<7>[26695.168045] c0 mshci: MSHCI_WRTPRT: 0x00000001
<7>[26695.168145] c0 mshci: MSHCI_GPIO: 0x00000000
<7>[26695.168238] c0 mshci: MSHCI_TCBCNT: 0x00007800
<7>[26695.168331] c0 mshci: MSHCI_TBBCNT: 0x0000f0d8
<7>[26695.168432] c0 mshci: MSHCI_DEBNCE: 0x000fffff
<7>[26695.168523] c0 mshci: MSHCI_USRID: 0xffffffff
<7>[26695.168615] c0 mshci: MSHCI_VERID: 0x5342240a
<7>[26695.168717] c0 mshci: MSHCI_HCON: 0x00e424c1
<7>[26695.168811] c0 mshci: MSHCI_UHS_REG: 0x00010000
<7>[26695.168904] c0 mshci: MSHCI_BMOD: 0x00000582
<7>[26695.169000] c0 mshci: MSHCI_PLDMND: 0x00000000
<7>[26695.169090] c0 mshci: MSHCI_DBADDR: 0x6bee0000
<7>[26695.169182] c0 mshci: MSHCI_IDSTS: 0x00000000
<7>[26695.169282] c0 mshci: MSHCI_IDINTEN: 0x00000000
<7>[26695.169374] c0 mshci: MSHCI_DSCADDR: 0x6bee00e0
<7>[26695.169465] c0 mshci: MSHCI_BUFADDR: 0x00000000
<7>[26695.169564] c0 mshci: MSHCI_WAKEUPCON: 0x00000000
<7>[26695.169658] c0 mshci: MSHCI_CLOCKCON: 0x00000000
<7>[26695.169751] c0 mshci: MSHCI_FIFODAT: 0x00000000
<7>[26695.169845] c0 mshci: ===========================================
<3>[26695.170166] c0 mmcblk0: error -110 sending status command, aborting
<3>[26695.170367] c0 end_request: I/O error, dev mmcblk0, sector 22589728
<3>[26695.170540] c0 Buffer I/O error on device mmcblk0p12, logical block 2000420
<4>[26695.170747] c0 EXT4-fs warning (device mmcblk0p12): ext4_end_bio:258: I/O error writing to inode 65490 (offset 12288 size 4096 starting block 2823717)
<3>[26695.171109] c0 CMD aborting case in MMC's block layer ret 0.
<3>[26695.171271] c0 mmcblk0: CMD25, ARG=0x158b120.
<3>[26695.171370] c0 packed CMD type = 0.
<3>[26695.171461] c0 mmc0, request returns 4.
And here is the part I am concerned about: My internal memory is faulty! mmcblk0p12 belongs to /data and truely speaking this is not good!
Code:
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
Normaly the system shouldn't notice any defect sectors (because the hardware has some spare sectors and remaps the request to them) so I think I have serious trouble here.
What do you think? Do you agree on that assumption?
Have you read the sds and unusual freezing threads?
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Have you read the sds and unusual freezing threads?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the hint. It is a good starting point...
I switched to CM 10.1.3 RC2 and I still have the same problem with the same partition (see first post). As far as I know the Samsung eMMC bug should be fixed as it is included in the vanilla linux kernel.
Any ideas?
The bug is fixed the freezing is not.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Related
Hi XDA community
I have a weird problem on my S3
I can't use Camera with Custom Kernels on Sammy (Samsung) based ROMs (I tried Googy-Max and Boeffla kernel). When I try to access to Camera, applications says "Camera Failed" or "Failed to connect Camera". If I use stock kernel with sammy based ROMs, I can use camera.
And also, I haven't got any problem in CyanogenMod based ROM with custom kernel (Googy-Max).
Here is the last lines of dmesg when I try to access to camera;
Code:
<6>[ 276.325203] c0 [TSP] DVFS On![8]
<5>[ 276.352810] c0 melfas-ts 3-0048: finger [0] up, palm 0
<6>[ 276.388363] c0 lcd panel: brightness=30, bl=1, candela=30
<6>[ 276.394264] c0 audss_reg_restore: SRC[0x1], DIV[0xf10], GATE[0x42]
<6>[ 276.394306] c0 audss_clk_enable(1): SRC[0x1], DIV[0xf10], GATE[0x1c7]
<6>[ 276.394408] c0 wm8994-codec wm8994-codec: midas_wm1811_aif1_hw_params ++
<6>[ 276.394449] c0 wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[ 276.394488] c0 wm8994-codec wm8994-codec: midas_wm1811_aif1_hw_params --
<6>[ 276.394796] c0 I:P:[email protected] Total=16384 PrdSz=4096 #Prds=4 dma_area=0xf4270000
<6>[ 276.395901] c3 wm8994-codec wm8994-codec: write 3d = 2f
<6>[ 276.396106] c0 wm8994-codec wm8994-codec: write 3e = 27
<6>[ 276.396318] c3 wm8994-codec wm8994-codec: write 38 = 80
<6>[ 276.396515] c0 wm8994-codec wm8994-codec: write 3 = 3c00
<6>[ 276.396706] c0 wm8994-codec wm8994-codec: write 39 = 1ee
<6>[ 276.396896] c0 wm8994-codec wm8994-codec: write 1 = 3
<6>[ 276.450402] c0 [TSP] DVFS Off!
<6>[ 276.450447] c0 wm8994-codec wm8994-codec: write 39 = 18c
<6>[ 276.450654] c0 wm8994-codec wm8994-codec: write 2 = 6000
<6>[ 276.450845] c0 wm8994-codec wm8994-codec: write 208 = 1a
<6>[ 276.452292] c0 wm8994-codec wm8994-codec: write 5 = 303
<6>[ 276.452492] c0 wm8994-codec wm8994-codec: write 3 = 3f30
<6>[ 276.452691] c0 wm8994-codec wm8994-codec: write 3 = 3ff0
<6>[ 276.452892] c0 wm8994-codec wm8994-codec: write 1 = 3003
<6>[ 276.453113] c0 wm8994-codec wm8994-codec: write 3 = 33f0
<6>[ 276.454363] c0 wm8994-codec wm8994-codec: write 15 = 0
<6>[ 276.454578] c0 wm8994-codec wm8994-codec: write 420 = 0
<7>[ 276.455292] c0 i2s_txctrl:Turn on
<6>[ 276.488590] c0 lcd panel: brightness=41, bl=2, candela=40
<6>[ 276.521833] c0 lcd panel: brightness=50, bl=3, candela=50
<6>[ 276.654188] c0 cm36651_work_func_light, red = 109 green = 82 blue = 42 white = 122
<4>[ 276.668636] c3 s3c-fimc0: FIMC0 1 opened.
<7>[ 276.671789] c3 s5c73m3_probe
<7>[ 276.672223] c3 s5c73m3_power_on: in
<7>[ 276.672246] c3 s5c73m3 vddCore : 1100000
<4>[ 276.707655] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 276.707692] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 276.707723] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 276.737748] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 276.743783] c0 s5c73m3_get_af_cal_version: Cal_Device = 0x7bfdcb2d, Cal_DLL = 0xaae44d9f
<7>[ 276.747932] c0 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 276.747992] c0 s5c73m3_power_down: in
<6>[ 276.771564] c0 lcd panel: brightness=62, bl=4, candela=60
<6>[ 276.788274] c0 lcd panel: brightness=76, bl=5, candela=70
<6>[ 276.838325] c0 lcd panel: brightness=83, bl=6, candela=80
<4>[ 276.853203] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<6>[ 276.854938] c0 lcd panel: brightness=90, bl=7, candela=90
<4>[ 276.858011] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 276.858116] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 276.858161] c0 s5c73m3_power_on: in
<7>[ 276.858185] c0 s5c73m3 vddCore : 1100000
<4>[ 276.898340] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<6>[ 276.905002] c0 lcd panel: brightness=100, bl=8, candela=100
<6>[ 276.921645] c0 lcd panel: brightness=105, bl=10, candela=104
<6>[ 276.954938] c0 lcd panel: brightness=108, bl=12, candela=108
<6>[ 276.988237] c0 lcd panel: brightness=116, bl=13, candela=110
<6>[ 277.021637] c0 lcd panel: brightness=120, bl=14, candela=120
<3>[ 277.070368] c0 [HOTPLUG IN] check_up 1400000>=500000 && 390>200
<3>[ 277.070433] c0 CPU_UP 1
<4>[ 277.075267] c1 CPU1: Booted secondary processor
<6>[ 277.075332] c1 notifier_call_chain : NOTIFY BAD tick_notify
<6>[ 277.080053] c1 Switched to NOHz mode on CPU #1
<7>[ 277.347577] c3 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 277.360953] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 277.361009] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 277.430073] c3 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 277.430142] c3 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 277.430597] c3 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 277.430676] c3 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 277.430744] c3 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 277.430785] c3 s5c73m3_check_fw: i2c failed, err -22
<7>[ 277.430817] c3 s5c73m3_init: isp.bad_fw is true
<3>[ 277.430854] c3 s5c73m3_init: i2c failed, err -22
<7>[ 277.430893] c3 s5c73m3_power_down: in
<4>[ 277.469209] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 277.469410] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 277.469442] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 277.570142] c0 s3c-fimc0: Retry power on(1/3)
<3>[ 277.570172] c0
<7>[ 277.570203] c0 s5c73m3_power_on: in
<7>[ 277.570236] c0 s5c73m3 vddCore : 1100000
<4>[ 277.587394] c3 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 277.587461] c3 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 277.587518] c3 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 277.613817] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 277.617854] c3 s5c73m3_get_af_cal_version: Cal_Device = 0x7bbdcb2d, Cal_DLL = 0x22e44d9f
<7>[ 277.623486] c0 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 277.623596] c0 s5c73m3_power_down: in
<4>[ 277.665259] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 277.665512] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 277.665568] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 277.665626] c0 s5c73m3_power_on: in
<7>[ 277.665663] c0 s5c73m3 vddCore : 1100000
<4>[ 277.681156] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 278.091274] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 278.102394] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 278.102440] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 278.170062] c1 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 278.170114] c1 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 278.170332] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 278.170369] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 278.170407] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 278.170438] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 278.170464] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 278.170491] c0 s5c73m3_init: i2c failed, err -22
<7>[ 278.170521] c0 s5c73m3_power_down: in
<4>[ 278.204486] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 278.204743] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 278.204797] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 278.305271] c0 s3c-fimc0: Retry power on(2/3)
<3>[ 278.305328] c0
<7>[ 278.305402] c0 s5c73m3_power_on: in
<7>[ 278.305471] c0 s5c73m3 vddCore : 1100000
<4>[ 278.322980] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 278.323023] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 278.323062] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 278.339376] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 278.342579] c0 s5c73m3_get_af_cal_version: Cal_Device = 0x7bfdcb2d, Cal_DLL = 0x1ae44d9f
<7>[ 278.344412] c0 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 278.344468] c0 s5c73m3_power_down: in
<4>[ 278.377010] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 278.377206] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 278.377239] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 278.377273] c0 s5c73m3_power_on: in
<7>[ 278.377298] c0 s5c73m3 vddCore : 1100000
<4>[ 278.391573] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 278.802462] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 278.814234] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 278.814286] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 278.880112] c1 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 278.880208] c1 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 278.880653] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 278.880715] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 278.880773] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 278.880828] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 278.880875] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 278.880917] c0 s5c73m3_init: i2c failed, err -22
<7>[ 278.880963] c0 s5c73m3_power_down: in
<4>[ 278.917260] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 278.917511] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 278.917565] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 279.020126] c1 s3c-fimc0: Retry power on(3/3)
<3>[ 279.020170] c1
<7>[ 279.020212] c1 s5c73m3_power_on: in
<7>[ 279.020253] c1 s5c73m3 vddCore : 1100000
<4>[ 279.035238] c1 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 279.035278] c1 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 279.035310] c1 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 279.049503] c3 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 279.052394] c3 s5c73m3_get_af_cal_version: Cal_Device = 0x7bfdcb2d, Cal_DLL = 0x22e44d9f
<7>[ 279.055958] c3 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 279.056014] c3 s5c73m3_power_down: in
<4>[ 279.088649] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 279.088822] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 279.088847] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 279.088875] c0 s5c73m3_power_on: in
<7>[ 279.088893] c0 s5c73m3 vddCore : 1100000
<4>[ 279.102944] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 279.462221] c1 i2s_txctrl: Turn Off - spr is no active
<6>[ 279.462262] c1 wm8994-codec wm8994-codec: write 420 = 200
<6>[ 279.462459] c1 audss_reg_save: SRC[0x1], DIV[0xf10], GATE[0x42]
<6>[ 279.462490] c1 audss_clk_enable(0): SRC[0x1], DIV[0xf10], GATE[0x42]
<7>[ 279.513019] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 279.524195] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 279.524241] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 279.590032] c3 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 279.590074] c3 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 279.590268] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 279.590297] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 279.590325] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 279.590352] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 279.590376] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 279.590398] c0 s5c73m3_init: i2c failed, err -22
<7>[ 279.590421] c0 s5c73m3_power_down: in
<4>[ 279.623632] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 279.623849] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 279.623890] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 279.623933] c0 s3c-fimc0: Camera power/init failed!!!!
<3>[ 279.623963] c0
<3>[ 279.623987] c0 s3c-fimc0: fimc_runtime_suspend : invalid fimc control
<3>[ 279.624239] c0 s3c-fimc0: fimc_configure_subdev: fail to initialize subdev
<3>[ 279.624355] c0 s5c73m3_remove: camera is not ready!!
<3>[ 279.624830] c0 s3c-fimc0: fimc_s_input: Could not register camera sensor with V4L2.
<4>[ 279.625113] c0 s3c-fimc0: FIMC0 0 released.
<4>[ 279.834038] c3 s3c-fimc0: FIMC0 1 opened.
<7>[ 279.838480] c0 s5c73m3_probe
<7>[ 279.839113] c0 s5c73m3_power_on: in
<7>[ 279.839176] c0 s5c73m3 vddCore : 1100000
<4>[ 279.854931] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 279.855086] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 279.855180] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 279.880593] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 279.885959] c0 s5c73m3_get_af_cal_version: Cal_Device = 0x7bfdcb29, Cal_DLL = 0x22e04d9f
<7>[ 279.891421] c0 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 279.891474] c0 s5c73m3_power_down: in
<4>[ 279.924538] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 279.924710] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 279.924736] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 279.924764] c0 s5c73m3_power_on: in
<7>[ 279.924781] c0 s5c73m3 vddCore : 1100000
<4>[ 279.938832] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 280.348995] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 280.360108] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 280.360153] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 280.430039] c3 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 280.430081] c3 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 280.430287] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 280.430315] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 280.430344] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 280.430371] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 280.430395] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 280.430416] c0 s5c73m3_init: i2c failed, err -22
<7>[ 280.430440] c0 s5c73m3_power_down: in
<6>[ 280.462058] c1 wm8994-codec wm8994-codec: write 1 = 3
<6>[ 280.462285] c1 wm8994-codec wm8994-codec: write 3 = 3f0
<6>[ 280.462502] c1 wm8994-codec wm8994-codec: write 3 = 330
<6>[ 280.462720] c1 wm8994-codec wm8994-codec: write 3 = 0
<6>[ 280.462935] c1 wm8994-codec wm8994-codec: write 5 = 300
<4>[ 280.464164] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 280.464409] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 280.464454] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<6>[ 280.464661] c1 wm8994-codec wm8994-codec: write 3 = 3000
<6>[ 280.464900] c1 wm8994-codec wm8994-codec: write 3 = 3c00
<6>[ 280.465141] c1 wm8994-codec wm8994-codec: write 39 = 18f
<6>[ 280.465378] c1 wm8994-codec wm8994-codec: write 37 = 81
<6>[ 280.465613] c1 wm8994-codec wm8994-codec: write 38 = b0
<3>[ 280.565126] c0 s3c-fimc0: Retry power on(1/3)
<3>[ 280.565183] c0
<7>[ 280.565239] c0 s5c73m3_power_on: in
<7>[ 280.565299] c0 s5c73m3 vddCore : 1100000
<4>[ 280.581615] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 280.581713] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 280.581802] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 280.607965] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 280.613378] c0 s5c73m3_get_af_cal_version: Cal_Device = 0x7bbdcb2d, Cal_DLL = 0x3ae44d9f
<7>[ 280.618882] c3 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 280.619011] c3 s5c73m3_power_down: in
<6>[ 280.620201] c1 wm8994-codec wm8994-codec: write 3 = 0
<6>[ 280.620606] c1 wm8994-codec wm8994-codec: write 37 = 80
<6>[ 280.620993] c1 wm8994-codec wm8994-codec: write 39 = 181
<6>[ 280.621309] c1 wm8994-codec wm8994-codec: write 1 = 0
<6>[ 280.621521] c1 wm8994-codec wm8994-codec: write 2 = 2000
<6>[ 280.621734] c1 wm8994-codec wm8994-codec: write 208 = a
<6>[ 280.621972] c3 wm8994-codec wm8994-codec: write 15 = 40
<6>[ 280.622166] c3 wm8994-codec wm8994-codec: write 3d = 3f
<6>[ 280.622357] c3 wm8994-codec wm8994-codec: write 3e = 37
<4>[ 280.653105] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 280.653290] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 280.653327] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 280.653367] c0 s5c73m3_power_on: in
<7>[ 280.653391] c0 s5c73m3 vddCore : 1100000
<4>[ 280.667626] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 281.076954] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 281.088096] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 281.088140] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 281.155062] c1 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 281.155107] c1 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 281.155317] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 281.155347] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 281.155375] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 281.155402] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 281.155426] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 281.155448] c0 s5c73m3_init: i2c failed, err -22
<7>[ 281.155472] c0 s5c73m3_power_down: in
<4>[ 281.188526] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 281.188704] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 281.188730] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 281.290243] c0 s3c-fimc0: Retry power on(2/3)
<3>[ 281.290300] c0
<7>[ 281.290375] c0 s5c73m3_power_on: in
<7>[ 281.290446] c0 s5c73m3 vddCore : 1100000
<4>[ 281.307308] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 281.307405] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 281.307492] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 281.333269] c0 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 281.336535] c0 s5c73m3_get_af_cal_version: Cal_Device = 0x7bbdcb2d, Cal_DLL = 0x22e44d9f
<7>[ 281.338519] c1 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 281.338573] c1 s5c73m3_power_down: in
<4>[ 281.371084] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 281.371276] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 281.371309] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 281.371344] c0 s5c73m3_power_on: in
<7>[ 281.371366] c0 s5c73m3 vddCore : 1100000
<4>[ 281.385639] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 281.794634] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 281.805819] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 281.805873] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 281.875081] c0 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 281.875142] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 281.875312] c3 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 281.875349] c3 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 281.875384] c3 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 281.875418] c3 s5c73m3_check_fw: i2c failed, err -22
<7>[ 281.875448] c3 s5c73m3_init: isp.bad_fw is true
<3>[ 281.875474] c3 s5c73m3_init: i2c failed, err -22
<7>[ 281.875501] c3 s5c73m3_power_down: in
<4>[ 281.890129] c0 [email protected] 9
<4>[ 281.908748] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 281.908923] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 281.908952] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 282.010122] c0 s3c-fimc0: Retry power on(3/3)
<3>[ 282.010165] c0
<7>[ 282.010205] c0 s5c73m3_power_on: in
<7>[ 282.010245] c0 s5c73m3 vddCore : 1100000
<4>[ 282.025939] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 282.026008] c0 s5c73m3_init: vdd core value from OTP : 1.05V
<7>[ 282.026069] c0 s5c73m3_init: chip info from OTP : 0x1184, 0x6fad, 0xa0e4
<7>[ 282.047737] c1 s5c73m3_get_sensor_fw_version: Sensor_version = BHFJ02, Sensor_Type = CML0801-M0
<7>[ 282.051090] c3 s5c73m3_get_af_cal_version: Cal_Device = 0x7bfdcb2d, Cal_DLL = 0xaae44d9f
<7>[ 282.056629] c1 s5c73m3_get_phone_fw_version: can't open BHFJ02 Ver. Firmware. so, download from F-ROM
<7>[ 282.056783] c1 s5c73m3_power_down: in
<4>[ 282.091531] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 282.091788] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 282.091843] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<7>[ 282.091903] c0 s5c73m3_power_on: in
<7>[ 282.091941] c0 s5c73m3 vddCore : 1100000
<4>[ 282.108014] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were ON
<7>[ 282.518842] c0 s5c73m3_get_sensor_fw_binary: sent SPI ready CMD
<6>[ 282.530086] c0 s3c-pl330 s3c-pl330.2: Reset Channel-1 CS-20000f FTC-2000
<3>[ 282.530132] c0 s3c64xx-spi s3c64xx-spi.1: DmaAbrtTx-65536
<3>[ 282.600040] c1 s5c73m3_spi spi1.0: I/O Error: rx-1 tx-1 res:rx-f tx-f len-65536
<3>[ 282.600082] c1 s3c64xx-spi s3c64xx-spi.1: DmaAbrtRx-65536
<3>[ 282.600288] c0 s5c73m3_spi spi1.0: spi_xmit_rx - error -5
<3>[ 282.600317] c0 s5c73m3_get_sensor_fw_binary: i2c failed, err -22
<3>[ 282.600345] c0 s5c73m3_get_phone_fw_version: i2c failed, err -22
<3>[ 282.600372] c0 s5c73m3_check_fw: i2c failed, err -22
<7>[ 282.600396] c0 s5c73m3_init: isp.bad_fw is true
<3>[ 282.600417] c0 s5c73m3_init: i2c failed, err -22
<7>[ 282.600440] c0 s5c73m3_power_down: in
<4>[ 282.634053] c0 s3c_csis_power: vmipi_1.8v is on. so OFF
<4>[ 282.634288] c0 s3c_csis_power: vmipi_1.1v is on. so OFF
<4>[ 282.634331] c0 s3c_csis_power: vmipi_1.0v and vmipi_1.8v were OFF
<3>[ 282.634380] c0 s3c-fimc0: Camera power/init failed!!!!
<3>[ 282.634415] c0
<3>[ 282.634442] c0 s3c-fimc0: fimc_runtime_suspend : invalid fimc control
<3>[ 282.634706] c0 s3c-fimc0: fimc_configure_subdev: fail to initialize subdev
<3>[ 282.634839] c0 s5c73m3_remove: camera is not ready!!
<3>[ 282.635470] c1 s3c-fimc0: fimc_s_input: Could not register camera sensor with V4L2.
<4>[ 282.635754] c1 s3c-fimc0: FIMC0 0 released.
How can I fix it?
Thanks in advance.
forumber2 said:
Hi XDA community
I have a weird problem on my S3
I can't use Camera with Custom Kernels on Sammy (Samsung) based ROMs (I tried Googy-Max and Boeffla kernel). When I try to access to Camera, applications says "Camera Failed" or "Failed to connect Camera". If I use stock kernel with sammy based ROMs, I can use camera.
And also, I haven't got any problem in CyanogenMod based ROM with custom kernel (Googy-Max).
How can I fix it?
Thanks in advance.
Click to expand...
Click to collapse
Does your phone have the latest camera firmware. Not sure if it would help but worth a shot. Search around for camera firmware update/upgrade in the forums. There is a thread that shows you how to check with links to updates.
forumber2 said:
Hi XDA community
I have a weird problem on my S3
I can't use Camera with Custom Kernels on Sammy (Samsung) based ROMs (I tried Googy-Max and Boeffla kernel). When I try to access to Camera, applications says "Camera Failed" or "Failed to connect Camera". If I use stock kernel with sammy based ROMs, I can use camera.
And also, I haven't got any problem in CyanogenMod based ROM with custom kernel (Googy-Max).
How can I fix it?
Thanks in advance.
Click to expand...
Click to collapse
Just try clearing data and cache for the camera app and reboot and see if it works after that
Sent from my GT-I9300 using Tapatalk 2
wangdaning said:
Does your phone have the latest camera firmware. Not sure if it would help but worth a shot. Search around for camera firmware update/upgrade in the forums. There is a thread that shows you how to check with links to updates.
Click to expand...
Click to collapse
Galaxy S3 doesn't support external camera update I think. ( I couldn't find )
galaxys3lover said:
Just try clearing data and cache for the camera app and reboot and see if it works after that
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Tried but no way. This problem is exits in every camera application, not only on sammy camera.
I added the dmesg log to #1 post.
I had the same problem. Try to flash stock with odin and then flash foxhound 2.5. Mine worked after that.
Sent from my GT-I9300 using xda app-developers app
sosferatu said:
I had the same problem. Try to flash stock with odin and then flash foxhound 2.5. Mine worked after that.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Which firmware did you flash with Odin?
I9300XXEME2
Sent from my GT-I9300 using xda app-developers app
And?
Sent from my GT-I9300 using xda app-developers app
forumber2 said:
Galaxy S3 doesn't support external camera update I think. ( I couldn't find )
Click to expand...
Click to collapse
It does. There is a thread about it in the general section. I think they call it camera driver and not firmware, but it is firmware. Type in *#34971539# in the dial pad and check your phone and camera firmware. They should match.
sosferatu said:
I had the same problem. Try to flash stock with odin and then flash foxhound 2.5. Mine worked after that.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I'll try
wangdaning said:
It does. There is a thread about it in the general section. I think they call it camera driver and not firmware, but it is firmware. Type in *#34971539# in the dial pad and check your phone and camera firmware. They should match.
Click to expand...
Click to collapse
I understand that I need to reflash camera chip and I think it's very risky. I will try to reflash official firmware with ODIN.
I think I found a solution;
First,boot the ROM with original kernel and open the camera. After that,flash any kernel do you want and you have a working camera. But If I wipe /data partition, this problem appears again.
Hey, I'm getting the massage There is no PIT partition while flashing with Odin... tried Stock rom, flash only ROOT-CF, Flash pit file., flash 3 parts rom. nothing worked.
My device is GT-I9300 32GB White. cant enter recovery. it shows white stripes.
From what I've searched in the forum it looks like i have the problem with Emmc chip.
In Download mode I'm getting all the information like the product number etc'
* when i was searching for the problem i sow that if it show the product number then its not bricked. and my phone is 32GB, i heard that only the 16GB model are infected.
I'm just wants to make sure that there nothing else i can do before replacing the motherboard
P.S
I think maybe it all stated when i accidentally flashed wrong pit
Thanks,
Go read the dead boot recovery thread in general forum.
Thanks,
Ive fallowed the guide.
the output from teraterm is :
PMIC rev = PASS2(2)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
[MMC] there are pending interrupts 0x00010000
card_init: mmc_send_op_cond fail! ret = -2147483663
mmc_initialize: mmc init fail once! ret = -2147483663
[MMC] there are pending interrupts 0x00010000
[MMC] response timeout error : 00000104 cmd 1, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL: 0x00000010
mshci: MSHCI_PWREN: 0x00000001
mshci: MSHCI_CLKDIV: 0x0000007d
mshci: MSHCI_CLKSRC: 0x00000000
mshci: MSHCI_CLKENA: 0x00000001
mshci: MSHCI_TMOUT: 0xffffffff
mshci: MSHCI_CTYPE: 0x00000000
mshci: MSHCI_BLKSIZ: 0x00000200
mshci: MSHCI_BYTCNT: 0xf0000000
mshci: MSHCI_INTMSK: 0x00000000
mshci: MSHCI_CMDARG: 0x40300000
mshci: MSHCI_CMD: 0x20002041
mshci: MSHCI_MINTSTS: 0x00000000
mshci: MSHCI_RINTSTS: 0x00000000
mshci: MSHCI_STATUS: 0x0001f906
mshci: MSHCI_FIFOTH: 0x20400040
mshci: MSHCI_CDETECT: 0x00000001
mshci: MSHCI_WRTPRT: 0x00000001
mshci: MSHCI_GPIO: 0x00000000
mshci: MSHCI_TCBCNT: 0x000ffe00
mshci: MSHCI_TBBCNT: 0x00000000
mshci: MSHCI_DEBNCE: 0x000fffff
mshci: MSHCI_USRID: 0xffffffff
mshci: MSHCI_VERID: 0x5342240a
mshci: MSHCI_HCON: 0x00e424c1
mshci: MSHCI_UHS_REG: 0x00000000
mshci: MSHCI_BMOD: 0x00000200
mshci: MSHCI_PLDMND: 0x00000000
mshci: MSHCI_DBADDR: 0x00000000
mshci: MSHCI_IDSTS: 0x00000000
mshci: MSHCI_IDINTEN: 0x00000000
mshci: MSHCI_DSCADDR: 0x00000000
mshci: MSHCI_BUFADDR: 0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON: 0x00000000
mshci: MSHCI_FIFODAT: 0x0000000e
mshci: ===========================================
card_init: mmc_send_op_cond fail! ret = -2147483665
mmc_initialize: mmc->capacity = 0
mmc_initialize: mmc init fail twice! ret = -2147483663
what is that mean?
i dont see the "[Patch Stop]" in the end. so its good right ???
please help
,thanks,
anyone can please confirm if my device chip is lost or not ??
thanks...
Ohh very bad
Up
Hi!
I have a problem with my HTC Desire X. The device was ok until it went off and was plugged to a power source, then only the HBOOT menu appeared.
The device has not been touched concerning custom roms, boot loaders etc. until then. So it had the stock rom and as far as I know, there was no update going on, when the device turned off.
To solve the problem, I unlocked the bootloader and installed the recovery image TWRP 2.5.0. But in the Recovery mode I could not mount any internal partition. So it was not possible to wipe anything or install a custom rom.
The only explanation I found for this is, that maybe the internal memory (EMMC) was corrupted and the system could not mount it and boot up. My question is: Is there something I can do to about it?
It would be nice if I could boot up an Android system from SD card. Is this possible? I only found solutions for other HTC devices so far.
I did some more research.
First I tried to start fdisk/parted to print the partition table. Both did not work. parted hangs, while fdisk says it could not read the device.
So I looked what I can find with procfs. There are only four partitions printed.
Code:
cat /proc/partitions
major minor #blocks name
179 0 3784708 mmcblk0
179 1 20 mmcblk0p1
179 2 544 mmcblk0p2
179 3 4500 mmcblk0p3
179 4 1 mmcblk0p4
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 00c7f600 00000200 "recovery"
mmcblk0p27: 00fffc00 00000200 "boot"
mmcblk0p24: 3bdffe00 00000200 "system"
mmcblk0p26: 0f000000 00000200 "cache"
mmcblk0p25: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p31: 46800000 00000200 "fat"
mmcblk0p29: 00011c00 00000200 "extra"
Then I tried to find out wether there were error messanges concerning the emmc:
Code:
dmesg |grep mmc
<6>[ 7.378778] C0 mmc0: SDCC Version: 0x00000000
<3>[ 7.378981] C0 mmc0: No card detect facilities available
<6>[ 7.380389] C0 mmc0: Qualcomm MSM SDCC-core at 0x00000000a0600000 irq 80,0
dma 7 dmacrcri 12
<6>[ 7.380416] C0 mmc0: Controller capabilities: 0x00000001
<6>[ 7.380434] C0 mmc0: Platform slot type: MMC
<6>[ 7.380451] C0 mmc0: 8 bit data mode enabled
<6>[ 7.380468] C0 mmc0: 4 bit data mode disabled
<6>[ 7.380484] C0 mmc0: polling status mode disabled
<6>[ 7.380504] C0 mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 80000000 Hz
<6>[ 7.380524] C0 mmc0: Slot eject status = 0
<6>[ 7.380541] C0 mmc0: Power save feature enable = 1
<6>[ 7.380561] C0 mmc0: DM non-cached buffer at ffdc0000, dma_addr 0x13740000
<6>[ 7.380584] C0 mmc0: DM cmd busaddr 0x13740000, cmdptr busaddr 0x13757f40
<6>[ 7.381294] C0 mmc1: SDCC Version: 0x00000000
<6>[ 7.383129] C0 mmc1: Qualcomm MSM SDCC-core at 0x00000000a0400000 irq 56,2
94 dma 10 dmacrcri 6
<6>[ 7.383156] C0 mmc1: Controller capabilities: 0x00000001
<6>[ 7.383174] C0 mmc1: Platform slot type: SD
<6>[ 7.383191] C0 mmc1: 8 bit data mode disabled
<6>[ 7.383208] C0 mmc1: 4 bit data mode enabled
<6>[ 7.383224] C0 mmc1: polling status mode disabled
<6>[ 7.383244] C0 mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 80000000 Hz
<6>[ 7.383264] C0 mmc1: Slot eject status = 1
<6>[ 7.383281] C0 mmc1: Power save feature enable = 1
<6>[ 7.383301] C0 mmc1: DM non-cached buffer at ffda0000, dma_addr 0x13760000
<6>[ 7.383324] C0 mmc1: DM cmd busaddr 0x13760000, cmdptr busaddr 0x13777f40
<6>[ 7.383951] C0 mmc2: SDCC Version: 0x00000000
<6>[ 7.385494] C0 mmc2: Qualcomm MSM SDCC-core at 0x00000000a0500000 irq 58,0
dma 8 dmacrcri 7
<6>[ 7.385521] C0 mmc2: Controller capabilities: 0x00000001
<6>[ 7.385539] C0 mmc2: Platform slot type: SDIO(WIFI)
<6>[ 7.385556] C0 mmc2: 8 bit data mode disabled
<6>[ 7.385573] C0 mmc2: 4 bit data mode enabled
<6>[ 7.385589] C0 mmc2: polling status mode disabled
<6>[ 7.385609] C0 mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 80000000 Hz
<6>[ 7.385629] C0 mmc2: Slot eject status = 1
<6>[ 7.385646] C0 mmc2: Power save feature enable = 1
<6>[ 7.385666] C0 mmc2: DM non-cached buffer at ffd80000, dma_addr 0x13780000
<6>[ 7.385689] C0 mmc2: DM cmd busaddr 0x13780000, cmdptr busaddr 0x13797f40
<6>[ 7.447169] C0 mmc_attach_sdio mmc_send_io_op_cond error1: -110
<3>[ 7.470703] C0 mmc0: ACMD 41 init process fail : resp : 0x0
<6>[ 7.534723] C0 mmc0: cid 90014a2058494e594814005f562a8f6e
<6>[ 7.534738] C0 mmc0: csd d02701320f5903d7ffffffe78a4040e6
<6>[ 7.534758] C0 mmc0: ext_csd 00000000000000010301000000000000
<6>[ 7.534776] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534794] C0 mmc0: ext_csd 00004000000000080000000000000000
<6>[ 7.534813] C0 mmc0: ext_csd 00000000000000000000080000000000
<6>[ 7.534831] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534849] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534868] C0 mmc0: ext_csd 00000800000000000000000000000000
<6>[ 7.534886] C0 mmc0: ext_csd 00000000000001040000000000000000
<6>[ 7.534904] C0 mmc0: ext_csd 00000000000000000000200000000000
<6>[ 7.534923] C0 mmc0: ext_csd 00000000000000000000080000000000
<6>[ 7.534941] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534959] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534978] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.534996] C0 mmc0: ext_csd 00000040000000000000020000000000
<6>[ 7.535014] C0 mmc0: ext_csd 00001000000000000000000000000000
<6>[ 7.535033] C0 mmc0: ext_csd 00000000000000000000080000000000
<6>[ 7.535051] C0 mmc0: ext_csd 00000000000000000000000000000a00
<6>[ 7.535069] C0 mmc0: ext_csd 0000000000000001150a0a0700100701
<6>[ 7.535088] C0 mmc0: ext_csd 02010807070013000073800800080808
<6>[ 7.535108] C0 mmc0: ext_csd 08080800000000000202020700020005
<6>[ 7.535126] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.535144] C0 mmc0: ext_csd 00000000000000101f05000000010003
<6>[ 7.535163] C0 mmc0: ext_csd 00011e00000000000000000000000000
<6>[ 7.535181] C0 mmc0: ext_csd 00000000000000000000000000000004
<6>[ 7.535199] C0 mmc0: ext_csd 00000008000000000000000000000200
<6>[ 7.535218] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.535234] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.535253] C0 mmc0: ext_csd 00000010000000000000000000000000
<6>[ 7.535271] C0 mmc0: ext_csd 00000000000000000000000000000002
<6>[ 7.535289] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.535308] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.535326] C0 mmc0: ext_csd 00000000000000000000000000000000
<6>[ 7.539618] C0 mmc0: set ext_csd.erase_group_def
<6>[ 7.550189] C0 mmc0: new high speed MMC card at address 0001
<6>[ 7.550671] C0 mmcblk0: mmc0:0001 XINYH 3.60 GiB
<6>[ 7.607051] C0 mmc2: Slot status change detected (0 -> 1)
<3>[ 7.857109] C0 mmc0: CMD18: Data timeout
<3>[ 7.857121] C0 mmc0: SDCC PWR is ON
<3>[ 7.857169] C0 mmc0: SDCC clks are ON, MCLK rate=50000000
<3>[ 7.857181] C0 mmc0: SDCC irq is enabled
<3>[ 7.857399] C0 mmc0: MCI_TEST_INPUT = 0x000003fe
<3>[ 7.857411] C0 mmc0: ADM mode: busy=1, chnl=7, crci=12
<3>[ 7.857423] C0 mmc0: xfer_size=4096, data_xfered=0, xfer_remain=4096
<3>[ 7.857438] C0 mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done
=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 7.857454] C0 mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspendi
ng=0
<3>[ 7.857471] C0 mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0,
disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 7.857538] C1 mmc0: DMA channel flushed (0x80000004)
<6>[ 7.857621] C1 mmc0: Controller has been reinitialized
<3>[ 7.857711] C0 mmcblk0: error -110 sending stop command, original cmd resp
onse 0x40000900, card status 0x400900
<3>[ 7.857728] C0 mmcblk0: r/w command failed, status = 0x40000900
<3>[ 7.857751] C0 end_request: I/O error, dev mmcblk0, sector 10128
<3>[ 7.857768] C0 Buffer I/O error on device mmcblk0, logical block 1266
<3>[ 8.163094] C0 mmc0: CMD18: Data timeout
<3>[ 8.163106] C0 mmc0: SDCC PWR is ON
<3>[ 8.163153] C0 mmc0: SDCC clks are ON, MCLK rate=50000000
<3>[ 8.163163] C0 mmc0: SDCC irq is enabled
<3>[ 8.163381] C0 mmc0: MCI_TEST_INPUT = 0x000003fe
<3>[ 8.163393] C0 mmc0: ADM mode: busy=1, chnl=7, crci=12
<3>[ 8.163404] C0 mmc0: xfer_size=4096, data_xfered=0, xfer_remain=4096
<3>[ 8.163419] C0 mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done
=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 8.163436] C0 mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspendi
ng=0
<3>[ 8.163453] C0 mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0,
disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 8.163514] C1 mmc0: DMA channel flushed (0x80000004)
<6>[ 8.163596] C1 mmc0: Controller has been reinitialized
<3>[ 8.163676] C0 mmcblk0: error -110 sending stop command, original cmd resp
onse 0x40000900, card status 0x400900
<3>[ 8.163693] C0 mmcblk0: r/w command failed, status = 0x40000900
<3>[ 8.163713] C0 end_request: I/O error, dev mmcblk0, sector 10128
<3>[ 8.163729] C0 Buffer I/O error on device mmcblk0, logical block 1266
<6>[ 8.163773] C0 mmcblk0: p1 p2 p3 p4 < >
<6>[ 8.164671] C0 mmc_rescan_try_freq: Find a MMC/eMMC card
<6>[ 8.233194] C0 mmc2: new high speed SDIO card at address 0001
<6>[ 8.251248] C0 mmc_rescan_try_freq: Find a SDIO card
<3>[ 8.790308] C0 mmc0: CMD18: Data timeout
<3>[ 8.790318] C0 mmc0: SDCC PWR is ON
<3>[ 8.790366] C0 mmc0: SDCC clks are ON, MCLK rate=50000000
<3>[ 8.790376] C0 mmc0: SDCC irq is enabled
<3>[ 8.790594] C0 mmc0: MCI_TEST_INPUT = 0x000003fe
<3>[ 8.790606] C0 mmc0: ADM mode: busy=1, chnl=7, crci=12
<3>[ 8.790618] C0 mmc0: xfer_size=4096, data_xfered=0, xfer_remain=4096
<3>[ 8.790633] C0 mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done
=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 8.790649] C0 mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspendi
ng=0
<3>[ 8.790666] C0 mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0,
disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 8.790741] C1 mmc0: DMA channel flushed (0x80000004)
<6>[ 8.790841] C1 mmc0: Controller has been reinitialized
<3>[ 8.790936] C0 mmcblk0: error -110 sending stop command, original cmd resp
onse 0x40000900, card status 0x400900
<3>[ 8.790953] C0 mmcblk0: r/w command failed, status = 0x40000900
<3>[ 8.790979] C0 end_request: I/O error, dev mmcblk0, sector 10128
<3>[ 8.790998] C0 Buffer I/O error on device mmcblk0, logical block 1266
<3>[ 9.096353] C0 mmc0: CMD18: Data timeout
<3>[ 9.096363] C0 mmc0: SDCC PWR is ON
<3>[ 9.096408] C0 mmc0: SDCC clks are ON, MCLK rate=50000000
<3>[ 9.096416] C0 mmc0: SDCC irq is enabled
<3>[ 9.096591] C0 mmc0: MCI_TEST_INPUT = 0x000003fe
<3>[ 9.096599] C0 mmc0: ADM mode: busy=1, chnl=7, crci=12
<3>[ 9.096609] C0 mmc0: xfer_size=4096, data_xfered=0, xfer_remain=4096
<3>[ 9.096621] C0 mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done
=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 9.096634] C0 mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspendi
ng=0
<3>[ 9.096648] C0 mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0,
disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 9.096721] C1 mmc0: DMA channel flushed (0x80000004)
<6>[ 9.096803] C1 mmc0: Controller has been reinitialized
<3>[ 9.096889] C0 mmcblk0: error -110 sending stop command, original cmd resp
onse 0x40000900, card status 0x400900
<3>[ 9.096903] C0 mmcblk0: r/w command failed, status = 0x40000900
<3>[ 9.096924] C0 end_request: I/O error, dev mmcblk0, sector 10128
<3>[ 9.096941] C0 Buffer I/O error on device mmcblk0, logical block 1266
I see some I/O errors there.
Hello,
my i9300 has been rebooting strangely in the past days, and this morning was stuck in boot loop. Unfortunately I didn't get to backup the last pictures I took. I am trying to find a way to get access to the data it might still hold.
I can enter recovery mode (works but sometimes requires several attemps). Once there it cannot read system partitions (and thus can't wipe cache).
I tried to remove battery / sdcard, hold power button for a long time, hold it with home + up as well
More info:
* kernel has some issues to access the root system
Code:
$ dmesg | grep mmc
<5>[ 0.000000] c0 Kernel command line: console=ram loglevel=4 bootmode=2 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] s3cfb.bootloaderfb=0x5ec00000 sysscope=0xff000000 lcdtype=96 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=144m oops=panic pmic_info=65 cordon=80682fa972fd0742b08c3ec03dbe74be connie=GT-I9300_OPEN_EUR_ca5a0240c80b887511e34b14c9d00c16 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=I9300XXUGND5 androidboot.serialno=4df1dd821ee57fd9 snd_soc_core.pmdown_time=1000
<6>[ 1.741101] c2 dw_mmc dw_mmc: clock source 0: sclk_dwmci (40000000 Hz)
<3>[ 1.741379] c2 mmc0: Version ID 0x5342240a.
<6>[ 1.741630] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 1.742124] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<6>[ 1.742616] c2 s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (88888888 Hz)
<6>[ 1.742906] c2 mmc1: vtf_2.8v regulator found
<3>[ 1.770850] c0 mmc0: cmd 52 response timeout error
<3>[ 1.771702] c0 mmc0: cmd 52 response timeout error
<3>[ 1.775742] c0 mmc0: cmd 8 response timeout error
<3>[ 1.776591] c0 mmc0: cmd 5 response timeout error
<3>[ 1.777420] c0 mmc0: cmd 5 response timeout error
<3>[ 1.778246] c0 mmc0: cmd 5 response timeout error
<3>[ 1.779073] c0 mmc0: cmd 5 response timeout error
<3>[ 1.779920] c0 mmc0: cmd 55 response timeout error
<3>[ 1.780767] c0 mmc0: cmd 55 response timeout error
<3>[ 1.781613] c0 mmc0: cmd 55 response timeout error
<3>[ 1.782463] c0 mmc0: cmd 55 response timeout error
<3>[ 1.801773] c1 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 1.801805] c1 mmc0: VTU00M: 15010056545530304df1dd821ee57fd9
<7>[ 1.848333] c0 Registered led device: mmc1::
<6>[ 1.848801] c0 mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 1.849085] c0 mmc1: card inserted.
<6>[ 1.849225] c0 s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (8888888 Hz)
<3>[ 1.849340] c0 mmc2: no vmmc regulator found
<7>[ 1.849600] c0 Registered led device: mmc2::
<6>[ 1.849898] c0 mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 1.883922] c0 mmc0: cmd 13 response timeout error
<6>[ 1.885069] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 1.885909] c0 mmc0: cmd 6 response timeout error
<3>[ 1.887775] c0 mmc0: cmd 6 response timeout error
<3>[ 1.889637] c0 mmc0: cmd 6 response timeout error
<3>[ 1.891500] c0 mmc0: cmd 6 response timeout error
<3>[ 1.892612] c0 mmc0: error -110 whilst initialising MMC card
<6>[ 1.920360] c0 mmc1: cmd 52 command timeout error
<6>[ 1.920726] c0 mmc1: cmd 52 command timeout error
<6>[ 1.924597] c0 mmc1: cmd 5 command timeout error
<6>[ 1.924932] c0 mmc1: cmd 5 command timeout error
<6>[ 1.925265] c0 mmc1: cmd 5 command timeout error
<6>[ 1.925601] c0 mmc1: cmd 5 command timeout error
<6>[ 2.149524] c0 mmc1: new high speed SDHC card at address aaaa
<6>[ 2.150146] c0 mmcblk0: mmc1:aaaa SU32G 29.7 GiB
<6>[ 2.151639] c0 mmcblk0: p1
* note that there are errors for both internal and external cards, but if I remove/readd the external card while booted:
Code:
<6>[ 554.482789] c0 mmc1: card removed.
<6>[ 554.483031] c0 mmc1: card inserted.
<6>[ 554.484051] c0 mmc1: card inserted.
<6>[ 554.484199] c0 mmc1: card removed.
<6>[ 554.484371] c0 mmc1: card removed.
<6>[ 554.484487] c0 mmc1: card removed.
<6>[ 554.680618] c0 mmc1: card aaaa removed
<6>[ 554.701931] c0 sdhci_set_ios : MMC Card OFF samsung-hsmmc
<6>[ 555.482722] c0 mmc1: card inserted.
<6>[ 555.482883] c0 mmc1: card removed.
<6>[ 555.483037] c0 mmc1: card inserted.
<6>[ 555.483154] c0 mmc1: card removed.
<6>[ 555.483279] c0 mmc1: card inserted.
<6>[ 555.483414] c0 mmc1: card removed.
<6>[ 555.483529] c0 mmc1: card inserted.
<6>[ 555.483649] c0 mmc1: card inserted.
<6>[ 555.483772] c0 mmc1: card removed.
<6>[ 555.483891] c0 mmc1: card inserted.
<6>[ 555.485434] c0 mmc1: card removed.
<6>[ 555.485614] c0 mmc1: card inserted.
<6>[ 555.486618] c0 mmc1: card inserted.
<6>[ 555.486961] c0 mmc1: card inserted.
<6>[ 555.487101] c0 mmc1: card inserted.
<6>[ 555.681309] c0 sdhci_set_ios : MMC Card ON samsung-hsmmc
<6>[ 555.710511] c0 mmc1: cmd 52 command timeout error
<6>[ 555.711030] c0 mmc1: cmd 52 command timeout error
<6>[ 555.715224] c0 mmc1: cmd 5 command timeout error
<6>[ 555.715679] c0 mmc1: cmd 5 command timeout error
<6>[ 555.716136] c0 mmc1: cmd 5 command timeout error
<6>[ 555.716587] c0 mmc1: cmd 5 command timeout error
<6>[ 555.915431] c3 mmc1: new high speed SDHC card at address aaaa
<6>[ 555.918560] c3 mmcblk0: mmc1:aaaa SU32G 29.7 GiB
<6>[ 555.923272] c3 mmcblk0: p1
<7>[ 557.842034] c3 SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts
~ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 425992 136 425856 0% /dev
tmpfs 425992 8 425984 0% /tmp
tmpfs 425992 0 425992 0% /storage
tmpfs 425992 0 425992 0% /mnt/secure
tmpfs 425992 0 425992 0% /mnt/fuse
/dev/block/vold/179:1
31154688 29870720 1283968 96% /storage/sdcard1
What are my options ?
* I've seen some people using JTAG software tools and soldering to reset the eMMC. E.g. http://forum.gsmhosting.com/vbb/f60...n7100-without-removing-emmc-pictures-1945278/ Are there a combination of these operations that might allow me to read without destroying the data ? I also read http://forum.xda-developers.com/galaxy-note-2/help/to-recover-data-corrupted-emmc-t3292290/page2 but was not 100% sure of how to use that.
* are there some soft solutions I should try before I do this ? Maybe reflashing recovery software? Some magic combinations I don't know ?
The phone has
* CWR v6.0.4.6
* BlissPop 3.6 (if I recall long time since I set it up it.)
Thanks anyone for their help.
Yes you can get the data from it, if it's hardware-dead then no, your best bet is JTAG, I'm sure it won't be too expensive
Sent from my HTC 10 using Tapatalk
I can see the following quite often in dmesg
<3>[ 2695.992006] mmc0: CMD52: Command CRC error
<3>[ 2695.992024] mmc0: SDCC PWR is ON
<3>[ 2695.992033] mmc0: SDCC clks are ON, MCLK rate=100000000
<3>[ 2695.992043] mmc0: SDCC irq is enabled
<3>[ 2695.992166] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 2695.992259] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 2695.992274] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 2695.992285] mmc0: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
Does that mean that eMMC is having hardware issues?