[Q] Baseband loss when when flashing any rom

[Q] Baseband loss when when flashing any rom - Samsung Captivate Glide

Any way to preserve a baseband when flashing a custom rom every time I flash a rom it takes away the band leaving no signal or data connection

No ROM touches the baseband partition. If you don't have a valid value under About Phone the ROM doesn't like it for some reason.
What baseband are you running when it works?

roothorick said:
No ROM touches the baseband partition. If you don't have a valid value under About Phone the ROM doesn't like it for some reason.
What baseband are you running when it works?
Click to expand...
Click to collapse
It means the firmware can't access the ril ... firmware=modem
Sent from my SGH-I927 using xda premium

Need to look at build.prop and make sure is says "ro.telephony.ril_class=Smdk4210RIL" on 4.1.2 and "ro.telephony.ril_class=SamsungExynos4RIL" on 4.2.1
Sent from my SGH-I927 using xda premium

dman3285 said:
Need to look at build.prop and make sure is says "ro.telephony.ril_class=Smdk4210RIL" on 4.1.2 and "ro.telephony.ril_class=SamsungExynos4RIL" on 4.2.1
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I have a similar issue to the one above, though the line on build.prop is correct from the line you posted
Running on CM10.1 ROM, of your work of course.

try installing literom .... select the latest modem during installation (it is selected by default) then install JB

I have the same issue, and the build.prop line is correct.

Update to UCLJ3 baseband and make sure your following ALL the instructions for that Rom! Some will have you flash a kernel after the Rom is flashed!
Sent from my SGH-I927 using Tapatalk 2

dbrannon79 said:
Update to UCLJ3 baseband and make sure your following ALL the instructions for that Rom! Some will have you flash a kernel after the Rom is flashed!
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
Again, you don't need UCLJ3, we *know* UCLH2 works and UCLG9 should work. UCKI2/3 may not work but we haven't confirmed that yet.

I get the same issue when i try to flash any ROM onto the i927. I am on UCLJ3 and have tried flashing almost all the roms. Everytime I flash a rom the IMEI and Baseband becomes null. I have tried using EFS Professional backup tool on the phone in order to restore the IMEI, but that hasn't helped as well. Everytime I've had to go back to flashing the UCLJ3 Stock ICS Rom to get the IMEI/Baseband back. :crying:
Has anybody faced and solved this problem? I would really like to start trying out the PAC-Man roms that Kick's been building.

tanmayk said:
I get the same issue when i try to flash any ROM onto the i927. I am on UCLJ3 and have tried flashing almost all the roms. Everytime I flash a rom the IMEI and Baseband becomes null. I have tried using EFS Professional backup tool on the phone in order to restore the IMEI, but that hasn't helped as well. Everytime I've had to go back to flashing the UCLJ3 Stock ICS Rom to get the IMEI/Baseband back. :crying:
Has anybody faced and solved this problem? I would really like to start trying out the PAC-Man roms that Kick's been building.
Click to expand...
Click to collapse
EDIT: Bump!! Anybody??

roothorick said:
Again, you don't need UCLJ3, we *know* UCLH2 works and UCLG9 should work. UCKI2/3 may not work but we haven't confirmed that yet.
Click to expand...
Click to collapse
FYI, I've been having issues with UCLH2. It works for a while, but I'll suddenly be without service in an area I know has good service, and won't be able to connect to anything besides Wi-Fi until I reboot. I'm also having issues with Odin... I didn't know LiteROM bundles the latest baseband, I'll have to try that!

---

---

Same here, but for me this isn't problem.
Somehow gsm modem freez on boot, device restart helps
Sent from my SGH-I927 using xda app-developers app

hardware or software?
---

Is there anyone who could help with this??
Sent from my SGH-I927 using xda app-developers app

--
---

idulkoan said:
I wish there was a known fix.. but it might just be a manufacturing issue..
Click to expand...
Click to collapse
I experience baseband loss as well when flashing the latest CM JB 4.3 build from bubor. It does not even have
GSM after booting. With the original 4.0.4 firmware I experienced baseband loss from time to
time.
I noticed a few things.
First of all, `dmesg` shows the loss of an usb device repeatedly:
Code:
<6>[ 5801.766126] hub 1-0:1.0: USB hub found
<6>[ 5801.766538] hub 1-0:1.0: 1 port detected
<3>[ 5801.841951] tegra_usb_phy_bus_connect: timeout waiting for hsic connect detect
<6>[ 5801.844898] mif: xmm6260_on: xmm6260_on()
<3>[ 5801.845217] xmm_gpio_revers_bias_clear
<6>[ 5802.037072] tegra_usb_phy_bus_reset
<6>[ 5802.042446] tegra_usb_phy_bus_reset:4:USBMODE:3 USBCMD:10005 USBPORTSC1:8001205 USBSTS:80
<6>[ 5802.154629] usb 1-1: new high speed USB device number 2 using tegra-ehci
<3>[ 5802.416690] xmm_gpio_revers_bias_restore
<6>[ 5802.417287] Wake12 for irq=370
<6>[ 5802.417629] mif: link_pm_ioctl: 6f33
<3>[ 5802.417995] cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>[ 5802.714681] usb 1-1: device not accepting address 2, error -71
This seems to be the modem. Something is wrong when initializing.
Starting cbd manually yields the following output:
Code:
127|[email protected]:/efs # cbd -t xmm626x -o t
cbd -t xmm626x -o t
<3>cbd: /main: Start CP Boot Daemon (CBD)
CP Boot Daemon
<3>cbd: /main: start cp boot
<3>cbd: /main: Default Modem type = 1
<3>cbd: /main: Default Boot link = 4
<3>cbd: /main: Default Main link = 4
Cp Boot Daemon
<3>cbd: /main: [MODEM_IF] ggg
5d 2d 00 ea 6c 69 48 55 01 a0 fe fd 02 00 02 00
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
<3>cbd: /hsic_xmit_boot: check [BOOTROM] link connected = [0]
Segmentation fault
Finally, `logcat -b radio` is a bit more specific:
Code:
D/boot ( 2446): <4>cbd: main: Daemon Mode
D/boot ( 2446): <4>cbd: main: EHCI Tegra
D/boot ( 2446): <4>cbd: main: partition number : 7
D/boot ( 2446): <4>cbd: main: partition path : /dev/block/mmcblk0p7
D/boot ( 2446): <4>cbd: main: call boot start
D/boot ( 2446): <4>cbd: start_xmm626x_boot: start
D/boot ( 2446): <4>cbd: update_cp_imgmap: CP img map from default table
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/boot ( 2446): <4>cbd: hsic_xmit_boot: PSI send ----
D/boot ( 2446): <4>cbd: hsic_xmit_psi: Sent ATAT 4 byte
E/use-Rlog/RLOG-RIL( 115): Modem boot timeout
D/use-Rlog/RLOG-RIL( 115): wait xmm6260_boot_hsic boot ready
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/boot ( 2446): <4>cbd: s_read: select TIMEOUT
E/boot ( 2446): <3>cbd: err(No such file or directory) hsic_xmit_psi: ack read fail: 0x00
E/boot ( 2447): <3>cbd: err(No such file or directory) check_debug_level: /mnt/.lfs/debug_level.inf file open fail err = -1
D/boot ( 2447): <4>cbd: main: Daemon Mode
D/boot ( 2447): <4>cbd: main: EHCI Tegra
D/boot ( 2447): <4>cbd: main: partition number : 7
D/boot ( 2447): <4>cbd: main: partition path : /dev/block/mmcblk0p7
D/boot ( 2447): <4>cbd: main: call boot start
D/boot ( 2447): <4>cbd: start_xmm626x_boot: start
D/boot ( 2447): <4>cbd: update_cp_imgmap: CP img map from default table
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/boot ( 2447): <4>cbd: hsic_xmit_boot: PSI send ----
D/boot ( 2447): <4>cbd: hsic_xmit_psi: Sent ATAT 4 byte
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/boot ( 2447): <4>cbd: s_read: select TIMEOUT
E/boot ( 2447): <3>cbd: err(No such file or directory) hsic_xmit_psi: ack read fail: 0x00
E/boot ( 2448): <3>cbd: err(No such file or directory) check_debug_level: /mnt/.lfs/debug_level.inf file open fail err = -1
D/boot ( 2448): <4>cbd: main: Daemon Mode
D/boot ( 2448): <4>cbd: main: EHCI Tegra
D/boot ( 2448): <4>cbd: main: partition number : 7
D/boot ( 2448): <4>cbd: main: partition path : /dev/block/mmcblk0p7
D/boot ( 2448): <4>cbd: main: call boot start
D/boot ( 2448): <4>cbd: start_xmm626x_boot: start
D/boot ( 2448): <4>cbd: update_cp_imgmap: CP img map from default table
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
D/use-Rlog/RLOG-RIL( 115): modem status [ 0x3 ]
E/use-Rlog/RLOG-RIL( 115): Modem boot timeout
It seems to me that the modem initialization goes wrong but I'm not experienced enough
to know why. Any hints are appreciated.
It's also noteworthy that I'm using the ATT version of the i927 with UCLJ3 modem.

hmm
---

Related

[WIP] Lets recover hard-bricks

Hey guys. I'm doing some work to figure out how to recover Galaxy Nexus devices which are hard-bricked.. ie.. they have a bad or no bootloader installed.
the boot sequence
1. IROM - the Internal ROM which cannot be rewritten on the device. This loads the XLoader.
2. XLoader/MLO - This completes the initialization of the processor and memory, and loads up the relatively huge U-Boot ( Samsung modified this and calls it SBL)
3. UBoot/SBL - This "Bootloader" is almost a complete operating system. The U-Boot initializes the screen, provides Odin mode, Fastboot Mode as well as loading the kernel/recovery and provides a UART debugging mode (Yet to be unlocked).
4. Kernel - Once we reach this point, it's all clear.. the kernel is linux which loads android and all sorts of other things.
The Problem
People are bricking their devices at stage 2 and 3 of this boot sequence... This leaves them unable to boot Fastboot or Odin. The device is 100% interchangable with a brick. These devices are ending up hard bricked.
The solution
We must come up with a way to undo the hard brick. Here are some things i'm looking at to use the native hardware to recover itself.
When you plug in the device (when off), you will immediately notice a Texas Instruments D010 device gets enumerated. This is a debug mode for the processor.
Code:
Bus 001 Device 023: ID 0451:d010 Texas Instruments, Inc.
We've started looking at some bootloader output here: http://forum.xda-developers.com/showthread.php?t=1461986
You can find information about the OMAP4 bootloaders here: http://omapedia.org/wiki/Bootloader_Project
Help
I need help locating drivers to initialize the 0451:d010 device and make it readable from within Linux or Windows.. Generally Linux is easier to find appropriate drivers.
I could use some help collecting more reading materials and resources.
I think together as a community we can take care of this problem.

I kinda forgot that thread, it got lost among rom/kernel threads. Thanks for the reminder.
sent from my i9250

Ok... so here's the most complete boot log I've been able to obtain from the device
Code:
[Thermal] OK to boot
Initialize runtime thermal monitoring ...done!
-- OMAP 00004460 (version 04460e11) PPA release 1.6.1 Hash 30639809--
Device type: HS, DEBUG OFF
CPFROM HAL API support integrated
THERMAL support integrated: Run Time + Boot time
HDCP support integrated
-- PROD PPA RC3.2.3 --
Reset reason = 00037ba2
PRM_RSTST = 00000002
PPA freed 2992 bytes
Texas Instruments X-Loader 1.41 (Nov 16 2011 - 16:28:45)
Starting OS Bootloader from MMC/SD1 ...
EXCEPTION : CM_CLKMODE_DPLL_ABE = 0x7
EXCEPTION : CM_IDLEST_DPLL_ABE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_ABE = 0x804018
EXCEPTION : CM_CLKMODE_DPLL_CORE = 0xf
EXCEPTION : CM_IDLEST_DPLL_CORE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_CORE = 0x7d05
EXCEPTION : CM_CLKMODE_DPLL_PER = 0x107
EXCEPTION : CM_IDLEST_DPLL_PER = 0x1
EXCEPTION : CM_CLKSEL_DPLL_PER = 0x1400
EXCEPTION : CM_CLKMODE_DPLL_MPU = 0x117
EXCEPTION : CM_IDLEST_DPLL_MPU = 0x1
EXCEPTION : CM_CLKSEL_DPLL_MPU = 0x807d07
CFG_LOADADDR = 0xa0208000
1st instruct = 0xEA000007
[ __omap_twl6030_init_vbat_cfg :49] SA_PHOENIX_START_CONDITION = 0x4a
[ __omap_twl6030_init_vbat_cfg :54] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :63] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :86] SA_BBSPOR_CFG = 0x78
====== VCELL : 381375, SOC : 49, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
dev : 5
[sbl_board_charger_init_post] : Succeed set model data : 0x78!!!!!
====== VCELL : 381500, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381500000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x1
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x1
message.command =
message.status =
message.recovery =
<hit enter twice to activate fiq debugger>
[Thermal] OK to boot
Initialize runtime thermal monitoring ...done!
-- OMAP 00004460 (version 04460e11) PPA release 1.6.1 Hash 30639809--
Device type: HS, DEBUG OFF
CPFROM HAL API support integrated
THERMAL support integrated: Run Time + Boot time
HDCP support integrated
-- PROD PPA RC3.2.3 --
Reset reason = 0003fba2
PRM_RSTST = 00000002
PPA freed 2992 bytes
Texas Instruments X-Loader 1.41 (Nov 16 2011 - 16:28:45)
Starting OS Bootloader from MMC/SD1 ...
EXCEPTION : CM_CLKMODE_DPLL_ABE = 0x7
EXCEPTION : CM_IDLEST_DPLL_ABE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_ABE = 0x804018
EXCEPTION : CM_CLKMODE_DPLL_CORE = 0xf
EXCEPTION : CM_IDLEST_DPLL_CORE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_CORE = 0x7d05
EXCEPTION : CM_CLKMODE_DPLL_PER = 0x107
EXCEPTION : CM_IDLEST_DPLL_PER = 0x1
EXCEPTION : CM_CLKSEL_DPLL_PER = 0x1400
EXCEPTION : CM_CLKMODE_DPLL_MPU = 0x117
EXCEPTION : CM_IDLEST_DPLL_MPU = 0x1
EXCEPTION : CM_CLKSEL_DPLL_MPU = 0x807d07
CFG_LOADADDR = 0xa0208000
1st instruct = 0xEA000007
[ __omap_twl6030_init_vbat_cfg :49] SA_PHOENIX_START_CONDITION = 0x8
[ __omap_twl6030_init_vbat_cfg :54] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :63] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :86] SA_BBSPOR_CFG = 0x78
====== VCELL : 381375, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
<hit enter twice to activate fiq debugger>
Communications established====== VCELL : 381375, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
<hit enter twice to activate fiq debugger>
debug> console
console mode
[ 3.320373] cannot apply mgr(lcd) on inactive device
[ 3.325805] omapfb omapfb: failed to apply dispc config
[ 3.331359] cannot apply mgr(tv) on inactive device
[ 3.336578] omapfb omapfb: failed to apply dispc config
[ 3.341949] cannot apply mgr(lcd2) on inactive device
[ 3.347167] omapfb omapfb: failed to apply dispc config
[ 3.354888] regulator_init_complete: VDAC: disabling
[ 3.361053] omaplfb OMAPLFBInitFBDev: Device 0: Requesting 4 TILER 2D framebuffers
[ 3.369232] ## wifi_probe
[ 3.371917] wifi_set_power = 1
[ 3.631866] wifi_set_carddetect = 1
[ 3.647338]
[ 3.647338] Dongle Host Driver, version 5.90.125.94
[ 3.647338] Compiled in drivers/net/wireless/bcmdhd on Nov 21 2011 at 19:05:54
[ 3.764984] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3.817810] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3.837463] mmc1: new high speed SDIO card at address 0001
[ 3.844818] F1 signature read @0x18000000=0x16844330
[ 3.859436] DHD: dongle ram size is set to 294912(orig 294912)
[ 3.866546] wl_create_event_handler thr:5b started
[ 3.871673] dhd_attach thr:5c started
[ 3.875488] dhd_attach thr:5d started
[ 3.879272] dhd_attach thr:5e started
[ 3.883148] wifi_get_mac_addr
[ 3.888519] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
[ 3.897430] wifi_set_power = 0
[ 4.157012] =========== WLAN placed in RESET ========
[ 4.163116] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'uart'
[ 4.171203] twl_rtc twl_rtc: setting system clock to 2012-05-13 00:25:12 UTC (1336868712)
[ 4.180816] Freeing init memory: 276K
[ 4.187561] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 4.214172] max17040 4-0036: online = 1 vcell = 3795000 soc = 48 status = 3 health = 1 temp = 330 charger status = 0
[ 4.288116] keychord: using input dev tuna-gpio-keypad for fevent
[ 4.354614] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)
[ 4.446746] mms_ts 3-0048: fw version 0x62 already present
[ 4.454498] mms_ts 3-0048: Melfas MMS-series touch controller initialized
[ 4.757202] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 4489868
[ 4.765838] omap-rproc omap-rproc.1: BIOS image version is 2
[ 4.785888] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
[ 4.806243] omap_hwmod: ipu: failed to hardreset
[ 4.811035] omap-iommu omap-iommu.0: ducati: version 2.1
[ 4.822448] omap-rproc omap-rproc.1: remote processor ipu is now up
[ 4.835571] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.842071] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.848541] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.855072] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.861816] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x32
[ 4.869812] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x33
[ 4.877899] virtio_rpmsg_bus virtio0: creating channel rpmsg-omx addr 0x3c
[ 4.885192] rpmsg_omx rpmsg-omx0: new OMX connection srv channel: 1024 -> 60!
[ 5.959960] EXT4-fs (mmcblk0p12): recovery complete
[ 5.974639] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 6.021484] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c
[ 6.029602] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
[ 6.170227] EXT4-fs (mmcblk0p11): recovery complete
[ 6.178833] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 6.199371] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.269744] android_usb: already disabled
[ 6.274810] mtp_bind_config
[ 6.277740] adb_bind_config
[ 6.297790] HDCP: loaded keys
[ 6.481079] warning: `adbd' uses 32-bit capabilities (legacy support in use)
[ 6.488433] adb_open
[ 6.702026] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns1
[ 6.709808] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns2
[ 6.718780] init: sys_prop: permission denied uid:1001 name:net.rmnet1.gw
[ 6.726196] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns1
[ 6.733612] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns2
[ 6.741455] init: sys_prop: permission denied uid:1001 name:net.rmnet2.gw
[ 6.749481] PVR: Installing MISR with cookie c0800c2c
[ 6.757415] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 6.766174] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8be0000
[ 6.773162] PVR: SysFinalise: Version string: SGX revision = 1.2.0
[ 6.797027] [MODEM_IF] misc_open : umts_boot0
[ 6.801666] omap_hsi omap_hsi.0: HSI clock is now 96000000
[ 6.824066] omap_hsi omap_hsi.0: Entering RX wakeup in 3 wires mode (no CAWAKE)
[ 6.831634] [MODEM_IF] xmm6260_off()
[ 6.835327] [MODEM_IF] PA EVENT : reset =0, pa=1
[ 6.840057] [MODEM_IF] umts_ipc0 state changed: OFFLINE
[ 6.845367] [MODEM_IF] xmm6260_on()
[ 6.866821] SMC: SecureCRC=0xBC7458DC
[ 6.959045] [MODEM_IF] PA EVENT : reset =1, pa=0
[ 7.042053] SMC PA: INFO 00000001 00:00:00.000 ------ ------ --------------- Booting... (t=00:25:15.356) SMCXG01.04p11.32196 /Widevine Integration
[ 7.058532] SMC PA: INFO 00000002 00:00:00.017 ------ ------ --------------- Booted
[ 7.238128] [MODEM_IF] misc_release : umts_boot0
[ 7.245147] omap_hsi omap_hsi.0: hsi_write_cancel ch 0
[ 7.251708] omap_hsi omap_hsi.0: __hsi_write_cancel : -125
[ 7.258941] omap_hsi omap_hsi.0: hsi_read_cancel ch 0
[ 7.265106] omap_hsi omap_hsi.0: __hsi_read_cancel : -125
[ 7.270629] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 7.276794] omap_hsi omap_hsi.0: __hsi_read_cancel : -61
[ 7.282470] [MODEM_IF] misc_open : umts_boot1
[ 7.287506] omap_hsi omap_hsi.0: Entering RX wakeup in 4 wires mode
[ 8.299774] misc dsscomp: [c7234000] ignoring set failure -22
[ 8.530609] s6e8aa: d/b 1, p 1, b-01390ffb
[ 8.530639] s6e8aa: c0, 1, b-001215fb, got v 3534794, factory wants 3529338
[ 8.530670] s6e8aa: c1, 1, b-00478927, got v 3764175, factory wants 3755229
[ 8.530700] s6e8aa: c2, 1, b-0012a421, got v 3486385, factory wants 3481495
[ 8.530731] s6e8aa: d/b 1, p 2, b-044d7cf9
[ 8.530761] s6e8aa: c0, 2, b-00bc6c9a, got v 3336878, factory wants 3330014
[ 8.530761] s6e8aa: c1, 2, b-01688d4e, got v 3556595, factory wants 3547367
[ 8.530792] s6e8aa: c2, 2, b-00a7db92, got v 3293516, factory wants 3285750
[ 8.530822] s6e8aa: d/b 1, p 3, b-0b323808
[ 8.530853] s6e8aa: c0, 3, b-026395cd, got v 3203365, factory wants 3194725
[ 8.530883] s6e8aa: c1, 3, b-0331a9fb, got v 3435905, factory wants 3424659
[ 8.530914] s6e8aa: c2, 3, b-021e3100, got v 3149091, factory wants 3139262
[ 8.530944] s6e8aa: d/b 1, p 4, b-186611f4
[ 8.530944] s6e8aa: c0, 4, b-062b8517, got v 3065435, factory wants 3053644
[ 8.531036] s6e8aa: c1, 4, b-0725b7f8, got v 3297279, factory wants 3284148
[ 8.531249] s6e8aa: c2, 4, b-053f8b4b, got v 3005194, factory wants 2992315
[ 8.531280] s6e8aa: d/b 1, p 5, b-6840e4ff
[ 8.531311] s6e8aa: c0, 5, b-221c3d41, got v 2688265, factory wants 2667329
[ 8.531341] s6e8aa: c1, 5, b-24fd4a51, got v 2906316, factory wants 2884895
[ 8.531372] s6e8aa: c2, 5, b-1d67176e, got v 2594260, factory wants 2571400
[ 8.531402] s6e8aa: d/b 1, p 6, b-ffffffff
[ 8.531433] s6e8aa: c0, 6, b-59b1b4d2, got v 2325286, factory wants 2292333
[ 8.531463] s6e8aa: c1, 6, b-60d28a3e, got v 2534439, factory wants 2499333
[ 8.531463] s6e8aa: c2, 6, b-4efd2a80, got v 2197307, factory wants 2162000
[ 11.727386] [MODEM_IF] misc_release : umts_boot1
[ 11.732147] omap_hsi omap_hsi.0: hsi_write_cancel ch 0
[ 11.756225] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 11.762268] omap_hsi omap_hsi.0: hsi_read_cancel ch 0
[ 11.767791] omap_hsi omap_hsi.0: __hsi_read_cancel : -125
[ 11.773620] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 11.779174] omap_hsi omap_hsi.0: __hsi_read_cancel : -61
[ 11.785552] [MODEM_IF] misc_open : umts_ipc0
[ 11.790954] omap_hsi omap_hsi.0: Entering RX wakeup in 4 wires mode
[ 11.798675] [MODEM_IF] misc_open : umts_rfs0
[ 11.829528] [MODEM_IF] PA EVENT : reset =1, pa=1
[ 11.834228] [MODEM_IF] umts_ipc0 state changed: ONLINE
[ 14.545074] drivers/misc/inv_mpu/mldl_cfg.c|inv_mpu_get_slave_config|1792 returning 4
[ 26.044372] request_suspend_state: wakeup (3->0) at 26030029299 (2012-05-13 00:25:34.359069826 UTC)
[ 26.622772] acc_open
[ 26.625122] acc_release
[ 26.670013]
[ 26.670043] Dongle Host Driver, version 5.90.125.94
[ 26.670043] Compiled in drivers/net/wireless/bcmdhd on Nov 21 2011 at 19:05:54
[ 26.684082] wl_android_wifi_on in
[ 26.687622] wifi_set_power = 1
[ 26.971282] =========== WLAN going back to live ========
[ 26.977600] sdio_reset_comm():
[ 27.066314] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 27.228179] wifi_get_mac_addr
[ 27.232513] Firmware up: op_mode=1, Broadcom Dongle Host Driver mac=a0:0b:ba:e6:73:ae
[ 27.344390] dhd_rx_frame: net device is NOT registered yet. drop packet
[ 27.351531] dhd_rx_frame: net device is NOT registered yet. drop packet
[ 27.360076] Firmware version = wl0: Oct 5 2011 14:41:12 version 5.90.125.94
[ 28.639709] wl_bss_connect_done succeeded status=(0x9)
[ 28.732391] wl_bss_connect_done succeeded status=(0x11)
[ 29.166564] nfc_power_apply ON
[ 29.201965] nfc_power_apply OFF
[ 29.272308] nfc_power_apply ON
[ 35.672241] rpmsg_omx rpmsg-omx1: local addr assigned: 0x401
[ 35.682067] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
[ 35.703735] omap_hwmod: ipu: failed to hardreset
[ 35.713470] omap-iommu omap-iommu.0: ducati: version 2.1
[ 35.826934] rpmsg_omx rpmsg6: conn rsp: status 0 addr 101
[ 35.975158] rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101
[ 39.279998] wlan0: no IPv6 routers present
[ 44.895355] init: untracked pid 1113 exited
[ 44.905731] init: untracked pid 1119 exited
[ 44.918914] init: untracked pid 1123 exited
[ 44.923248] init: untracked pid 1124 exited
[ 44.927612] init: untracked pid 1117 exited
[ 44.932067] init: untracked pid 1120 exited
[ 54.283905] max17040 4-0036: online = 1 vcell = 3788750 soc = 48 status = 3 health = 1 temp = 350 charger status = 0
[ 61.938812] request_suspend_state: sleep (0->3) at 61924468996 (2012-05-13 00:26:10.253540041 UTC)
[ 61.959869] dhd_set_suspend: force extra Suspend setting
first. The device checks if it's too hot or too cold to boot via IROM software (internal read only memory). After that it begins initialization. The IROM version is displayed. Then the device type..
The OMAP processor in the Galaxy Nexus is a HS (High Security) processor, as opposed to GP (General Purpose) processor. This means the first bootloader (AKA MLO or X-Loader) is a signed binary which is e-fused to the device.
I've seen in the past on similar Hummingbird processors that only the first 1K is checked for speed because hashing it takes a little bit of time. This may or may not be the case with this particular device. We will see.
Anyway.. There's a possiblity we can find an MLO which is already presigned somewhere on the Internet. We need whatever they use at Samsung which provides the initial firmware load to a device without any firmware on it.
Here is a relevant page: http://omapedia.org/wiki/Bootloader_Project
Code:
If you are using an HS (High Security) OMAP device, an extra step is required. First, build x-load.bin using the steps above. Then, download the MShield signing tool and use the commands below. Contact your TI representative to get access to this tool.
In order to get the firmware onto the device in the first place, this bootloader must exist. We need a copy of it. Once we have this bootloader, we can revive Galaxy Nexus devices.

You may have seen this already, but just in case - this seems to be a bootloader of some kind. I couldn't get it to work with my bricked SGN, but it may be of some use to the unbricking effort.
Can't post link, so search for "Unbrick dead Samsung GT-i9250 Galaxy Nexus 32GB".
Best of luck!

The user above is referring to this link, I think:
http://forum.xda-developers.com/showthread.php?t=1640443
The user there shares a .zip file that supposedly is able to unbrick a 32gb GNex using some samsung software. It calls OMAPFlash.exe with a bunch of parameters. I don't know whether it will be useful or not, but it's a start.

The batch file that the post above ^ asks the users to run is this:
Code:
::::
:: Copyright (C) 2010-2011, Samsung Electronics, Co., Ltd. All Rights Reserved.
:: Written by System S/W Group, S/W Platform R&D Team,
:: Mobile Communication Division.
::::
::::
:: Project Name : Proxima GED
::
:: Project Description :
::
:: Comments : tabstop = 8, shiftwidth = 8, noexpandtab
::::
::::
:: File Name : omap4460_tuna_hs.bat
::
:: File Description :
::
:: Author : System Platform 2
:: Dept : System S/W Group (S/W Platform R&D Team)
:: Created : 17/Aug/2011
:: Version : Baby-Raccoon
::::
:__loop
@OMAPFlash.exe -v @Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
@PAUSE
GOTO __loop
Seeing the text file path, I went and looked. Here's what I found:
Code:
##
# Copyright (C) 2010-2011, Samsung Electronics, Co., Ltd. All Rights Reserved.
# Written by System S/W Group, S/W Platform R&D Team,
# Mobile Communication Division.
##
##
# Project Name : Proxima GED
#
# Project Description :
#
# Comments : tabstop = 8, shiftwidth = 8, noexpandtab
##
##
# File Name : omap4460_tuna_hs.txt
#
# File Description :
#
# Author : System Platform 2
# Dept : System S/W Group (S/W Platform R&D Team)
# Created : 17/Aug/2011
# Version : Baby-Raccoon
##
-omap 4
-t 36000 -p OMAP4460_TUNA_8G_HS_PRO -2
#chip_download [email protected] Targets\Projects\tuna\MBR.bin
chip_download [email protected] Targets\Projects\tuna\MLO_4460_HS_PRO
chip_download [email protected] Targets\Projects\tuna\sbl.img
command cold_sw_reset
So it appears that the software writes the files MLO_4460_HS_PRO and sbl.img to different parts of the internal memory.

Any success for the device driver? In the documents above, they say you should use the FTDI VCP (Virtual COM Port) drivers... But included in the package above, there is a driver in the ../usb_drv_windows directory, for exactly the TI driver you mentioned:
Code:
%USB_OMAP4460% = USB_Install, USB\VID_0451&PID_d010
For lazy reference:
Code:
[SIZE=2]-- Usage --
OMAPFlash Host is a command-line based application. It is currently available
for Windows XP only and will run in a Windows command shell. The application can
take commands directly from the command line or via a script file (a more useful
approach). The syntax for calling the tool is:
[B]omapflash [ <option> ] <command>[/B]
or, if a script file is used: omapflash @<file>
-- Options --
The tool has a number of options that can be used to control its overall
behavior.
[B]-com <port number> [/B]By default OMAPFlash will try to communicate with the
target platform using a USB serial link. This option will force OMAPFlash to
use a UART for serial communication and specify the host side COM-port to use.
-t <timeout> By default the timeout for communication on the serial link is 5
seconds. This option allows control of the timeout value by specifying another
timeout value in seconds.
[B]-p <platform>[/B] This option is required by OMAPFlash and specifies the platform
for which the download is to take place. The platform specified is a name tag
that allows OMAPFlash to identify the correct second loader to use. The tag
typically identifies the platform type and the memory used with the OMAP
device present on the platform (“e.g. SDP_MDDR_HYNIX_4G). The tag is used to
look up the second loader in a configuration file (omapflash2nd.txt) in
combination with an OMAP device identifier received from the platform during
peripheral boot.
[B]-omap <version> [/B]This option is required by OMAPFlash if a peripheral boot
sequence is used to transfer a second loader to a target platform. The option
specifies the OMAP generation used on the platform – without this option set,
OMAPFlash will be unable to determine how to correctly perform the peripheral
boot sequence necessary for transfer of the second loader to the platform. The
version number is a single digit integer (e.g. ‘3’ for an OMAP3xxx based
platform or ‘4’ for an OMAP4xxx based platform).
[B]-2[/B] This option controls whether OMAPFlash will try to use the ROM code
peripheral boot sequence to transfer a second loader to internal RAM before
doing anything else. This option will be required for most scenarios where
OMAPFlash is used but can be left out if OMAPFlash Host is interacting with a
second loader already running on a target platform.
[B]-v[/B] The ‘-v’ option controls whether OMAPFlash Host will run in verbose mode.
If set, more information will be shown during the execution of the flashing
sequence. Note that this option should be set in order to see the target
platform response to certain commands (e.g. ‘chips’).
-- Commands --
Commands are executed on the target platform. Any command is prefixed by the
keyword ‘command’ and anything following this keyword will be passed directly to
OMAPFlash Second by OMAPFlash Host without interpretation or modification.
Typically the ‘verbose’ option should be used with commands in order to ensure
that information returned from the platform will be shown on the console.
branch <device> <offset>
This command will cause OMAPFlash Second to make an
unconditional branch to a memory mapped address. The device will typically be
the SDRAM handled by the OMAP SDRAM controller in this case, and the offset
typically zero. The device ID must be one known by OMAPFlash Second and the
offset an integer within the address offset range valid for the device.
peek32 <address> Get the register value of the register with the given
address.
poke32 <address> <value> Modify the register at the given address to the given
value
peekpoke32 <address> <value> <mask> Modify the register at the given address
with the given value and mask
-- Flashing --
OMAPFlash Host is able to handle three basic procedures for accessing memory
devices through the OMAPFlash Second loader. These procedures are used to erase
memory devices, transfer a binary file to a device or upload the device content
to a binary file. In all cases, parameter values specifying sizes or offsets are
hexadecimal.
[B]chip_erase <device>[@offset] <size> [/B]
This procedure is used to erase the
content of a device, either for the whole device or for part of its address
range. The ‘device’ identifier is a string matching one of the devices
available on the platform as listed from the ‘chips’ command – in other words,
a device known to OMAPFlash Second for the particular platform used (SDRAM is
not a valid choice). If an ‘offset’ is used, the device erasure will start at
the offset specified. The offset will need to be compatible with the memory
structure of the device in question – e.g. if the device has a block size of
40000h bytes, the offset will need to be a multiple of the block size. The
‘size’ specifies the number of bytes to erase – a value of zero has the
special meaning of “to the end of the device”, either starting at offset zero
or at the specified ‘offset’ value, and can be used to erase the entire
device. Note that the typical erase functionality of a memory device is based
on the erasure of blocks of memory – it may not make sense to ask for erasure
of a size that is not a multiple of the block size of the device.
[B]chip_download <device>[@offset] <file> [/B]
In order to transfer a binary file to a
device on the platform this procedure is used. The ‘device’ identifier is a
string matching one of the devices available on the platform. If an ‘offset’
is specified the binary will be downloaded to the device starting at the
offset address specified. Using an offset should be done with some caution,
since the meaning of the offset value may be unclear for some device types
(e.g. for a NAND device the offset will be used without consideration of bad
blocks present in the memory space preceding the offset address). The file to
be downloaded is specified by the ‘file’ parameter and must be a raw image.
[B]chip_upload <device>[@offset] <size> <file> [/B]
In order to upload the content of
a memory device this procedure is used. The ‘device’ identifier is a string
matching one of the devices available on the platform. If an ‘offset’ is
specified content will be uploaded from the device starting at the offset
address specified. As for the ‘chip_download’ procedure the use of an offset
should be done with caution. The ‘size’ parameter specifies the number of
bytes to upload and the ‘file’ parameter the file to which the uploaded data
will be saved. Note that due to some limitations on the serial link, upload of
data will be considerably slower than download.
[/SIZE]

First things first. I recieved a PM from user itsalllgood with information regarding this topic. Here's the whole PM, copied and pasted:
itsalllgood said:
Dear fred,
Sorry to bother you...I wanted to post here but iam not allowed.. I am a computer engineer from montreal current living abroad..I had gnex that died and did a lot of work to try to get it back..to summ it all the omapidia project add TI site will get the full picture. the tool you linked is based on TI 1.6 omap flash.. i will keep it short... the link below will summ my work and please copy past it if you think its worth it..thanks in advance..
http://forum.xda-developers.com/showthread.php?p=26334564&posted=1#post26334564
Click to expand...
Click to collapse

^^ Somehow your link got messed up, but I think its this one.

Is it possible to hardware prevent a device like Samsung Galaxy S2 to go fastboot / odin mode when powering on but still be able to load the operating system?
Because even although I have a password set on the device, if it is stolen anyone can connect it to fastboot with power+voldown+menu and restore it to defaults. For example filling that corresponding partition with zeros will prevent from entering odin mode unless you boot into the operating system and with dd restore the partition.

First of all, that's off-topic. But I'll provide a speculative answer nonetheless.
I would think that you would be able to prevent a device from reaching recovery/fastboot/odin-download-mode, but it would have a big disadvantage, which is that if you are not able to boot into the OS somehow, you would have an unusable device. Although a device like the Galaxy Nexus, if stolen, could have its data retrieved by potentially using Odin and/or fastboot to reset the password, removing these failsafes would mean that you have a higher chance of bricking. Besides, that's what remote wipe apps (and other stolen-phone tools) are for. Check out Avast! if you don't have an antivirus/stolen-phone toolkit.
I'm by no means an expert here, but that's just my two cents.
EDIT: By the way, could we have someone (like AdamOutler) look at what we've got in this thread so far to see if the MLO file that we found is what's needed (as mentioned by Adam in the first couple posts)?

It's just that I don't either know the exact boot sequence of the SGS2 GT-I9100 nor the partitions interdependence (for example say that the boot partition needs the recovery or the sbl), I coudn't zero that partition because is a dependence.
What I woukd like to know if is possible:
- Backup all partitions.
- Zero, from android with dd, all partitions that allow anyone to enter odin/fastboot/clockworkmod/recovery so, if I lose the device, no one can make a odin backup or reset my device, unless you restore the partitions from the android or you use a hardware JTAG.
- Even the previous done, the phone must be able to normal boot into operating system.

I have a gut feeling that that's not possible. For recovery/odin modes, it may be possible due to them not really being directly involved in the boot process. However, for fastboot, I think it's part of the bootloader itself and therefore cannot be disabled using simple commands without also disabling the phone's booting process. For example, if you have the proper drivers installed on your computer, a Galaxy Nexus that's booting into Android will show up the same device as if you're connected via Fastboot. Unless someone can alter the source and recompile a bootloader with disabled fastboot, I don't think what you stated above is completely possible.

FredFS456 said:
I have a gut feeling that that's not possible. For recovery/odin modes, it may be possible due to them not really being directly involved in the boot process. However, for fastboot, I think it's part of the bootloader itself and therefore cannot be disabled using simple commands without also disabling the phone's booting process. For example, if you have the proper drivers installed on your computer, a Galaxy Nexus that's booting into Android will show up the same device as if you're connected via Fastboot. Unless someone can alter the source and recompile a bootloader with disabled fastboot, I don't think what you stated above is completely possible.
Click to expand...
Click to collapse
I think what I need could be done with a locked bootloader. As far as I know, the Samsung Galaxy S2 comes with an unlocked bootloader (causing the security flaw) while other like Samsung Galaxy Nexus come with a locked one: that means on stock devices, with use pattern or password and usb debugging disabled, there is no way someway can access you data even if not encryption is set.
Anyone can clarify things on this?

Bump, and back on topic.
Any developments here?

Yes. http://forum.xda-developers.com/showthread.php?t=1640443
it's done.

AdamOutler said:
Yes. http://forum.xda-developers.com/showthread.php?t=1640443
it's done.
Click to expand...
Click to collapse
Does anyone know HOW it's done??
EDIT: Actually the accompanying documentation explains quite well!
@Adam: Do you think we could tweak these drivers etc. for other devices not using OMAP?
(It seem that many protocols are standard, inducing the serial (UART) over USB FTDI-drivers...)

E:V:A said:
Does anyone know HOW it's done??
EDIT: Actually the accompanying documentation explains quite well!
@Adam: Do you think we could tweak these drivers etc. for other devices not using OMAP?
(It seem that many protocols are standard, inducing the serial (UART) over USB FTDI-drivers...)
Click to expand...
Click to collapse
It works just like UBM... but stock.
No. I dont think we can do that. Its an omap tool that requires bootmodes to be proper to work on omap. It can be applied to other properly configured omap devices.

Establishing a UART connection to the Ancora

As some of us here know, there are 3 ancora devices that are 100% known: The SGW, the Exhibit 2 and the Rugby Smart. For the last few weeks, I've been trying to establish a UART connection to the Rugby, being met with little to no success. (For those watching on G+, you've been privie to the information).
I know this is possible, since my TWRP image (using an arco68 based 2.6.35.14) for the Rugby can echo a kmsg to a serial monitor, but I haven't got 3.0.68 to do the same. So I'm calling in a global effort to get this cracked in the 3.0 kernel, that way we can deeper debug things.
What say the SGW and Exhibit 2 guys and gals?

Motorhead1991 said:
As some of us here know, there are 3 ancora devices that are 100% known: The SGW, the Exhibit 2 and the Rugby Smart. For the last few weeks, I've been trying to establish a UART connection to the Rugby, being met with little to no success. (For those watching on G+, you've been privie to the information).
I know this is possible, since my TWRP image (using an arco68 based 2.6.35.14) for the Rugby can echo a kmsg to a serial monitor, but I haven't got 3.0.68 to do the same. So I'm calling in a global effort to get this cracked in the 3.0 kernel, that way we can deeper debug things.
What say the SGW and Exhibit 2 guys and gals?
Click to expand...
Click to collapse
are you really trying to "UART", because you have adb, it also works when the phone is turned off.
for a really uart, we need a module, that enables a uart and make android a host.

adb kicks in too late for what I need, therefore I need to see what the SBL is doing with the kernel ant whatnot via UART.

Motorhead1991 said:
adb kicks in too late for what I need, therefore I need to see what the SBL is doing with the kernel ant whatnot via UART.
Click to expand...
Click to collapse
maybe you need some hardware mods, because you need to be listen before android starts, and the bootloader dont have specific code for that(i think).
unless you could mod you bootloader, try a jtag cable.

zezadas said:
maybe you need some hardware mods, because you need to be listen before android starts, and the bootloader dont have specific code for that(i think).
unless you could mod you bootloader, try a jtag cable.
Click to expand...
Click to collapse
As said in the OP, it works on 2.6.35.14 in recovery mode, just not 3.0.68 running the system. I don't even need the SBL log, as a kmsg would suffice.

What is UART?
Hi guys, What is UART?
I have google it already for the meaning,but i cant seem to understand its purpose or benefits on our device..
PS. Please no negative Feedback, i'm just asking!!

[iop]wah said:
Hi guys, What is UART?
I have google it already for the meaning,but i cant seem to understand its purpose or benefits on our device..
PS. Please no negative Feedback, i'm just asking!!
Click to expand...
Click to collapse
Using a UART connection on the ancora family (or any device) will help with kernel and filesystem debugging on boot, before adbd is even loaded, much less awake.

BTW, what you want to do with uart, beside log the bootloader?

AW: Establishing a UART connection to the Ancora
zezadas said:
BTW, what you want to do with uart, beside log the bootloader?
Click to expand...
Click to collapse
Obviously debugging.
Sent from my GT-I9001 using xda app-developers app

zezadas said:
BTW, what you want to do with uart, beside log the bootloader?
Click to expand...
Click to collapse
What XeLLaR* said... The Rugby 3.0 kernel is stuck without a camera because I have no idea what's killing the boot sequence. Initializing the cameras kills boot and it hangs on the second splash (ARIESVE.rle). I saw this with the a2220 chip also, which isn't something you guys have worked with (As far as I know).

Humm. Maybe you can post whay you have reached until now. Maybe we can help.
Also is always a interesting thread for me.
Sent from my GT-I8150 using xda app-developers app

Motorhead1991 said:
What XeLLaR* said... The Rugby 3.0 kernel is stuck without a camera because I have no idea what's killing the boot sequence. Initializing the cameras kills boot and it hangs on the second splash (ARIESVE.rle). I saw this with the a2220 chip also, which isn't something you guys have worked with (As far as I know).
Click to expand...
Click to collapse
I don't know if it helps or not, but Jocala (he started working on cm9 for ancora_tmo) used to use the a2220: https://github.com/Jocala/kernel.ancora_tmo.ics/blob/master/include/linux/a2220.h
However when it got official support from arco, it disappeared: https://github.com/arco/samsung-kernel-msm7x30/commit/4669dbff4ad08a084b11eabe350b3b6adb2f317e

any news about this project?

zezadas said:
any news about this project?
Click to expand...
Click to collapse
Not anything new I'm afraid... I'm still trying to figure it out however.

about the uart, can you already log bootloader?

zezadas said:
about the uart, can you already log bootloader?
Click to expand...
Click to collapse
I haven't got a bootloader response yet, just a kmsg, and only on 2.6.

1 year later...
Any progress?
On I9001 I can log something via UART cable... if I hold:
Code:
Volume -
and
Power on
http://forum.xda-developers.com/showpost.php?p=52944982&postcount=29
Some problems, because different speed... not 100 % managed yet...
But need also solution for I8150 Logging...
Thanx in advance.
Best Regards

bump...
I have now I8150 in my hands...
If I hold Volume - then I can see something...
Maybe wrong speed or some wrong settings... but something is send...
Maybe someone knows solution?
Thanx in advance.
Best Regards

adfree said:
bump...
I have now I8150 in my hands...
If I hold Volume - then I can see something...
Maybe wrong speed or some wrong settings... but something is send...
Maybe someone knows solution?
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
Hello adfree
Good to know you have a i8150 from this moment :good:
İ couldnt understand good your problem but İf you want to enter into download mode : hold volume - and power on keys
Also i think we must revive this thread because seems mr.Blefish(who is maintaining ideos x5) ported lk bootloader into ideos x5 (so msm7x30/8x55)
Our devices(ancora and ariesve) are in same family with ideos x5 (msm7x30/8x55)
Here is the initial work on lk bootloader for msm7x30/8x55 devices:
https://github.com/Blefish/android_bootable_bootloader_lk/compare/973308d69a...7d422c985a
İf you are interested in lets start to PMing
Regards

http://forum.xda-developers.com/showpost.php?p=52944982&postcount=29
My goal is to see something like this with I8150...
Code:
AST_POWERON
[1810] 0' Partition Information
[1810] dstatus = 0
[1810] dtype = 12
[1810] dfirstsec = 1
[1810] dsize = 212991
[1810] name = modem
size=5[1810] *********************************************************************
[1810] 1' Partition Information
[1810] dstatus = 128
[1810] dtype = 77
[1810] dfirstsec = 212992
[1810] dsize = 1000
[1810] name = dbl
size=3[1810] *********************************************************************
[1810] 2' Partition Information
[1810] dstatus = 0
[1810] dtype = 70
[1810] dfirstsec = 213992
[1810] dsize = 7192
[1810] name = osbl
size=4[1820] *********************************************************************
[1820] 3' Partition Information
[1820] dstatus = 0
[1820] dtype = 5
[1820] dfirstsec = 221184
[1820] dsize = 30883840
[1820] name =
size=0[1820] *********************************************************************
[1820] 4' Partition Information
[1820] dstatus = 0
[1830] dtype = 71
[1830] dfirstsec = 229376
[1830] dsize = 10240
[1830] name = emmcboot
size=8[1830] *********************************************************************
[1830] 5' Partition Information
[1830] dstatus = 0
[1830] dtype = 73
[1830] dfirstsec = 245760
[1830] dsize = 40000
[1830] name = amss
size=4[1830] *********************************************************************
[1840] 6' Partition Information
[1840] dstatus = 0
[1840] dtype = 88
[1840] dfirstsec = 286720
[1840] dsize = 6144
[1840] name =
size=0[1840] *********************************************************************
[1840] 7' Partition Information
[1840] dstatus = 0
[1840] dtype = 72
[1840] dfirstsec = 294912
[1850] dsize = 10240
[1850] name = boot
size=4[1850] *********************************************************************
[1850] 8' Partition Information
[1850] dstatus = 0
[1850] dtype = 80
[1850] dfirstsec = 311296
[1850] dsize = 14000
[1850] name = adsp
size=4[1850] *********************************************************************
[1860] 9' Partition Information
[1860] dstatus = 0
[1860] dtype = 74
[1860] dfirstsec = 327680
[1860] dsize = 6144
[1860] name = modem_st1
size=9[1860] *********************************************************************
[1860] 10' Partition Information
[1860] dstatus = 0
[1860] dtype = 75
[1860] dfirstsec = 335872
[1870] dsize = 6144
[1870] name = modem_st2
size=9[1870] *********************************************************************
[1870] 11' Partition Information
[1870] dstatus = 0
[1870] dtype = 144
[1870] dfirstsec = 344064
[1870] dsize = 16384
[1870] name = persist
size=7[1870] *********************************************************************
[1880] 12' Partition Information
[1880] dstatus = 0
[1880] dtype = 145
[1880] dfirstsec = 360448
[1880] dsize = 15360
[1880] name = recovery
size=8[1880] *********************************************************************
[1880] 13' Partition Information
[1880] dstatus = 0
[1880] dtype = 146
[1880] dfirstsec = 376832
[1880] dsize = 10240
[1890] name = parameter
size=9[1890] *********************************************************************
[1890] 14' Partition Information
[1890] dstatus = 0
[1890] dtype = 147
[1890] dfirstsec = 393216
[1890] dsize = 1064960
[1890] name = system
size=6[1890] *********************************************************************
[1900] 15' Partition Information
[1900] dstatus = 0
[1900] dtype = 148
[1900] dfirstsec = 1458176
[1900] dsize = 204800
[1900] name = cache
size=5[1900] *********************************************************************
[1900] 16' Partition Information
[1900] dstatus = 0
[1900] dtype = 149
[1900] dfirstsec = 1662976
[1900] dsize = 2826240
[1910] name = userdata
size=8[1910] *********************************************************************
[1910] 17' Partition Information
[1910] dstatus = 0
[1910] dtype = 150
[1910] dfirstsec = 4489216
[1910] dsize = 409600
[1910] name = preload
size=7[1910] *********************************************************************
[1910] 18' Partition Information
[1920] dstatus = 0
[1920] dtype = 151
[1920] dfirstsec = 4898816
[1920] dsize = 1000
[1920] name = dbl_backup
size=10[1920] *********************************************************************
[1920] 19' Partition Information
[1920] dstatus = 0
[1920] dtype = 152
[1920] dfirstsec = 4907008
[1920] dsize = 7192
[1930] name = osbl_backup
size=11[1930] *********************************************************************
[1930] 20' Partition Information
[1930] dstatus = 0
[1930] dtype = 153
[1930] dfirstsec = 4915200
[1930] dsize = 10240
[1930] name = emmcboot_backup
size=15[1930] *********************************************************************
[1940] 21' Partition Information
[1940] dstatus = 0
[1940] dtype = 154
[1940] dfirstsec = 4931584
[1940] dsize = 40000
[1940] name = amss_backup
size=11[1940] *********************************************************************
[1940] 22' Partition Information
[1940] dstatus = 0
[1940] dtype = 155
[1940] dfirstsec = 4972544
[1940] dsize = 10240
[1950] name = boot_backup
size=11[1950] *********************************************************************
[1950] 23' Partition Information
[1950] dstatus = 0
[1950] dtype = 156
[1950] dfirstsec = 4988928
[1950] dsize = 14000
[1950] name = adsp_backup
size=11[1950] *********************************************************************
[1960] 24' Partition Information
[1960] dstatus = 0
[1960] dtype = 157
[1960] dfirstsec = 5005312
[1960] dsize = 10240
[1960] name = recovery_backup
size=15[1960] *********************************************************************
[1960] 25' Partition Information
[1960] dstatus = 0
[1960] dtype = 158
[1960] dfirstsec = 5021696
[1970] dsize = 10240
[1970] name =
size=0[1970] *********************************************************************
[1970] 26' Partition Information
[1970] dstatus = 0
[1970] dtype = 159
[1970] dfirstsec = 5038080
[1970] dsize = 10240
[1970] name =
size=0[1970] *********************************************************************
[1970] 27' Partition Information
[1980] dstatus = 0
[1980] dtype = 160
[1980] dfirstsec = 5054464
[1980] dsize = 26050560
[1980] name =
size=0[1980] *********************************************************************
[1980] fsa_i2c_init ENTRY !!!
[2010] fsa_i2c_write done.
[2060] fsa_i2c_read done.
[2060] GPIO i2c init SUCCESS i2c_data : 1e
[2060] KEY_VOLUMEDOWN detected! start with no console mode.
[2060] charger_attached ENTRY !!!
[2190] dtype =0x0 dtype2=0x8 !!!
[2190] charger_attached check [[ 0 ]] !!!
[2190] boot_chg check [[ 0 ]] !!!
magic_key_offset : 2551183360
Load boot partition.
[2380] cmdline = 'console=ttyMSM2,115200 androidboot.hardware=qcom androidboot.emmc=true hw=7'
[2380]
Booting Linux
[2380] cmdline: console=ttyMSM2,115200 androidboot.hardware=qcom androidboot.emmc=true hw=7
[2380] Backlight off
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.35.7-1207170 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Oct 30 12:33:11 KST 2012
[ 0.000000] CPU: ARMv7 Processor [511f00f2] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache
[ 0.000000] Machine: GT-I9001 Board
[ 0.000000] AriesVE H/W revision : 0x07
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] allocating 10772480 bytes at c10a4000 (14a4000 physical) for fb
[ 0.000000] allocating 2097152 bytes at c1aea000 (1eea000 physical) for audio pmem arena
[ 0.000000] allocating 6291456 bytes at c1d00000 (2100000 physical) for kernel ebi1 pmem arena
[ 0.000000] allocating 31457280 bytes at c7600000 (7a00000 physical) for sf pmem arena
[ 0.000000] allocating 30212096 bytes at c9400000 (9800000 physical) for adsp pmem arena
[ 0.000000] allocating 5242880 bytes at cb0d0000 (b4d0000 physical) for hdmi pmem arena
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 112136
[ 0.000000] Kernel command line: console=ttyMSM2,115200 androidboot.hardware=qcom androidboot.emmc=true hw=7
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 58MB 134MB 256MB = 448MB total
[ 0.000000] Memory: 359932k/359932k available, 98820k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
<5>[ 0.000000] DMA : 0xff000000 - 0xffe00000 ( 14 MB)
[ 0.000000] vmalloc : 0xe0800000 - 0xf0000000 ( 248 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0036000 ( 184 kB)
[ 0.000000] .text : 0xc0036000 - 0xc072f000 (7140 kB)
[ 0.000000] .data : 0xc075e000 - 0xc07dcc20 ( 508 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:566
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000122] Calibrating delay loop... 933.88 BogoMIPS (lpj=4669440)
[ 0.250244] pid_max: default: 32768 minimum: 301
[ 0.250366] Mount-cache hash table entries: 512
[ 0.250579] Initializing cgroup subsys cpuacct
[ 0.250579] Initializing cgroup subsys freezer
[ 0.250610] CPU: Testing write buffer coherency: ok
[ 0.270660] NET: Registered protocol family 16
[ 0.290863] socinfo_init: v4, id=74, ver=2.1, raw_id=1402, raw_ver=1402, hw_plat=2, hw_plat_ver=65536
[ 0.290863] Clock ownership
[ 0.290893] GLBL : 07d82110
[ 0.290893] APPS : 00000000 00000000 00000000
[ 0.290893] ROW : 00000000 00000000
[ 0.291046] acpu_clock_init()
[ 0.291687] ACPU running at 1401600 KHz
[ 0.293090] msm_wlan_gpio_init: msm_wlan_gpio_init
[ 0.293182] msm7x30_init_mmc: Initialized wlan GPIO's
[ 0.294128] snddev_poweramp_gpio_init
[ 0.294158] aux_pcm_gpio_init
[ 0.294281] fsa9480_gpio_init
[ 0.294433] [TSP] M1 TSP LDO init
[ 0.300292] yda165:register yamaha amp device
[ 0.300292] si4709:register fm radio si4709 device
[ 0.300292] i2c_register_board_info 12
[ 0.300292] i2c_register_board_info 8
[ 0.300323] i2c_register_board_info 10
[ 0.300354] i2c_register_board_info 17
[ 0.300354] bt_power_init
[ 0.300354] bluetooth_gpio_init on system_rev:0
[ 0.300781] touch_keypad_gpio_init.
[ 0.300781] Boot Reason = 0x04
[ 0.300781] hw perfevents: enabled with ARMv7 Scorpion PMU driver, 5 counters available
[ 0.300903] Scorpion registered PMU device
[ 0.300964] pm8058_init: i2c_add_driver: rc = 0
[ 0.301330] pm8058_probe: PMIC revision: E3
[ 0.302734] pm8058_gpio_probe: gpiochip_add(): rc=0
[ 0.302917] pm8058_mpp_probe: gpiochip_add(): rc=0
[ 0.306365] bio: create slab <bio-0> at 0
[ 0.306610] pmic8058_pwm_probe: OK
[ 0.306854] SCSI subsystem initialized
[ 0.307006] usbcore: registered new interface driver usbfs
[ 0.307037] usbcore: registered new interface driver hub
[ 0.307128] usbcore: registered new device driver usb
[ 0.307281] i2c-gpio i2c-gpio.9: using pins 171 (SDA) and 170 (SCL)
[ 0.307342] i2c-gpio i2c-gpio.19: using pins 123 (SDA) and 122 (SCL)
[ 0.307403] i2c-gpio: probe of i2c-gpio.14 failed with error -16
[ 0.307464] i2c-gpio i2c-gpio.20: using pins 125 (SDA) and 124 (SCL)
[ 0.307556] i2c-gpio i2c-gpio.10: using pins 55 (SDA) and 89 (SCL)
[ 0.307617] i2c-gpio i2c-gpio.13: using pins 165 (SDA) and 164 (SCL)
[ 0.307708] i2c-gpio i2c-gpio.17: using pins 173 (SDA) and 172 (SCL)
[ 0.307800] i2c-gpio i2c-gpio.8: using pins 149 (SDA) and 148 (SCL)
[ 0.307861] i2c-gpio i2c-gpio.12: using pins 88 (SDA) and 86 (SCL)
[ 0.307952] i2c-gpio i2c-gpio.11: using pins 169 (SDA) and 168 (SCL)
[ 0.308013] msm_i2c_probe
[ 0.308074] msm_i2c_probe: clk_ctl 35d, 100000 Hz
[ 0.308349] msm_i2c_probe
[ 0.308410] msm_i2c_probe: clk_ctl 35d, 100000 Hz
[ 0.308807] Advanced Linux Sound Architecture Driver Version 1.0.23.
[ 0.360412] Bluetooth: Core ver 2.15
[ 0.360443] NET: Registered protocol family 31
[ 0.360473] Bluetooth: HCI device and connection manager initialized
[ 0.360473] Bluetooth: HCI socket layer initialized
[ 0.360534] Switching to clocksource gp_timer
[ 0.363250] NET: Registered protocol family 2
[ 0.380584] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.460723] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.460906] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.460998] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.460998] TCP reno registered
[ 0.461029] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.461029] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.461120] NET: Registered protocol family 1
[ 0.461273] RPC: Registered udp transport module.
[ 0.461273] RPC: Registered tcp transport module.
[ 0.461273] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.461395] Trying to unpack rootfs image as initramfs...
[ 0.488372] Freeing initrd memory: 652K
<6>[ 0.488494] PMU: registered new PMU device of type 0
[ 0.488891] sdio_al:SDIO-AL SW version 1.30
[ 0.489135] smd probe
[ 0.489166] smd_core_init()
[ 0.489196] smd_core_init() done
[ 0.489196] smd_alloc_loopback_channel: 'local_loopback' cid=100
[ 0.489349] get_nand_partitions: no flash partition table in shared memory
[ 0.489776] smd_alloc_channel() 'DS' cid=0
[ 0.489837] smd_alloc_channel() 'RPCCALL' cid=2
[ 0.489868] smd_alloc_channel() 'DATA1' cid=7
[ 0.489929] smd_alloc_channel() 'DATA2' cid=8
[ 0.489959] smd_alloc_channel() 'DATA3' cid=9
[ 0.490020] smd_alloc_channel() 'DATA4' cid=10
[ 0.490051] smd_alloc_channel() 'DATA5' cid=11
[ 0.490081] smd_alloc_channel() 'DATA6' cid=12
[ 0.490112] smd_alloc_channel() 'DATA7' cid=13
[ 0.490173] smd_alloc_channel() 'DATA8' cid=14
[ 0.490203] smd_alloc_channel() 'DATA9' cid=15
[ 0.490264] smd_alloc_channel() 'DATA11' cid=17
[ 0.490295] smd_alloc_channel() 'DATA12' cid=18
[ 0.490325] smd_alloc_channel() 'DATA13' cid=19
[ 0.490356] smd_alloc_channel() 'DATA14' cid=20
[ 0.490417] smd_alloc_channel() 'DAL00' cid=38
[ 0.490447] smd_alloc_channel() 'BRG_0' cid=39
[ 0.490509] smd_alloc_channel() 'DATA5_CNTL' cid=40
[ 0.490539] smd_alloc_channel() 'DATA6_CNTL' cid=41
[ 0.490600] smd_alloc_channel() 'DATA7_CNTL' cid=42
[ 0.490631] smd_alloc_channel() 'DATA8_CNTL' cid=43
[ 0.490692] smd_alloc_channel() 'DATA9_CNTL' cid=44
[ 0.490753] smd_alloc_channel() 'DATA12_CNTL' cid=45
[ 0.490783] smd_alloc_channel() 'DATA13_CNTL' cid=46
[ 0.490814] smd_alloc_channel() 'DATA14_CNTL' cid=47
[ 0.490875] smd_alloc_channel() 'DATA40' cid=48
[ 0.490905] smd_alloc_channel() 'DATA40_CNTL' cid=49
[ 0.492126] SMD Packet Port Driver Initialized.
[ 0.492156] Notify: smsm init
[ 0.492309] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492340] Notify: general
[ 0.492370] Notify: general
[ 0.492370] Notify: general
[ 0.492614] SMD: ch 2 0 -> 1
[ 0.492828] [afe.c:afe_init] AFE driver init
[ 0.492950] SMD: ch 2 1 -> 2
[ 0.493194] [audpp.c:audpp_probe] Number of decoder supported 5
[ 0.493225] [audpp.c:audpp_probe] Number of concurrency supported 7
[ 0.493225] [audpp.c:audpp_probe] module_name:AUDPLAY4TASK
[ 0.493225] [audpp.c:audpp_probe] queueid:17
<6>[ 0.493225] [audpp.c:audpp_probe] decid:4
[ 0.493255] [audpp.c:audpp_probe] nr_codec_support:1
[ 0.493255] [audpp.c:audpp_probe] module_name:AUDPLAY3TASK
[ 0.493255] [audpp.c:audpp_probe] queueid:16
[ 0.493255] [audpp.c:audpp_probe] decid:3
[ 0.493255] [audpp.c:audpp_probe] nr_codec_support:11
[ 0.493286] [audpp.c:audpp_probe] module_name:AUDPLAY2TASK
[ 0.493286] [audpp.c:audpp_probe] queueid:15
[ 0.493286] [audpp.c:audpp_probe] decid:2
[ 0.493286] [audpp.c:audpp_probe] nr_codec_support:11
[ 0.493286] [audpp.c:audpp_probe] module_name:AUDPLAY1TASK
[ 0.493286] [audpp.c:audpp_probe] queueid:14
[ 0.493316] [audpp.c:audpp_probe] decid:1
[ 0.493316] [audpp.c:audpp_probe] nr_codec_support:11
[ 0.493316] [audpp.c:audpp_probe] module_name:AUDPLAY0TASK
[ 0.493316] [audpp.c:audpp_probe] queueid:13
<6>[ 0.493316] [audpp.c:audpp_probe] decid:0
Example from I9001...
Now Question how to set right settings for I8150...
LK sounds interesting... because I am playing with GT-S8600 here:
http://forum.xda-developers.com/showthread.php?t=2116846
Best Regards

[ SOLVED ]HELP NEEDED...Stuck on CM Bootscreen after Nandroid Restore

EDIT : The issue has been resolved.
----------------------------------------------------
Hi guys,sorry for starting a new thread.I've been searching XDA forum and Googling for the solution for 3 days but haven’t found one. I am facing very weird and annoying problem and in desperate need of help.
My Wildfire was working fine on CM 7.2 Stable .Few days back I performed the following things :
1).To resolve the wireless related issues I reflashed Radio (3.35.20.10)
2)Flashed latest Kernel (SympKernV4.5) to give it a try ,was not satisfied and reflashed the previous Kernel (SympKernV4.1)
After that my phone got stuck on the CM boot screen.
I have tried following things :
1)Wiped everything and took nandroid backup without any problem.Everything went well but at the end same boot screen.Yes,I have got two partitions in SDCard FAT32 and ext3.And obviously I used the same version of CWM to restore as I did when creating the backup.
2)Tried the same things 3-4 times to no avail.
3)Ran RUU (RUU_Buzz_HTC_WWE_1.25.405.1_Radio_13.45.55.24_3.35.15.31_release_142189_signed).Downgraded and rooted using unrevoked once again.It was booting fine.Flashed recovery 5.0.2.8.Took nandroid backup everything went perfectly without any Error but when I did the reboot,same CM boot screen.
4.Flashed RemPuzzle_2.81-full and the boot was fine.But again when I tried to restore nandroid backup,got stuck on the same boot screen.I have waited for 5 hours.
5)Tried some other RUUs but the result is still the same.Phone boots perfectly when I flash the RUU. After downgrading and rooting when I try to restore the nandroid backup,it works fine till the end without any error but when I reboot the system it stucks on boot screen.
6) Followed what eventcom has mentioned in http://forum.xda-developers.com/showthread.php?t=1401784&page=2 .Booting was okay but again stuck on boot screen after nandroid restore.
7)Went back to CWM 2.5.0.7 and reflashed the CWM 5.0.2.8.
8.Removed SDCard and SIM before reboot.
9)Don’t think the problem is related to MTD partition as I have formatted all the 3 partitions(/cache,/data and /system).
10)I don’t think the Nandroid Backup has got corrupted coz Nandroid Restore was successful 4 days back before that Radio and Kernel thing moreover I have the backup file saved in PC and I copy the file to SDCard before every new Nandroid restore operation.
Any clues ?
Your help will be much appreciated.Thanks for your time.
Regards

Anybody ?

Hi pal, sorry for my delayed response. Xmas is nuts here :/ ok what I would like you to try is a clean install of cm7 stable and once that's installed go to the play store. The app I want you to get is called nandroid manager, install it and allow it to check your back up. I want to see if it will restore from it or if it will find it corrupt. All going well it will resotre your apps and data and we cam go from there
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

heavy_metal_man said:
The app I want you to get is called nandroid manager, install it and allow it to check your back up. I want to see if it will restore from it or if it will find it corrupt. All going well it will resotre your apps and data and we cam go from there
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
Click to expand...
Click to collapse
Hi mate,thanks for your reply.I really appreciate it.There are somethings I need to ask.
1.Right now I am on CWM 2.5.0.1,so before restoring the backup taken by CWM 5.0.2.8 I will have to flash CWM 5.0.2.8 first.Right ?
2.AFAIK,Nandroid Backup is stored in the "backup" folder
Code:
clockworkmod\backup
Right ?
There is another folder "download"
Code:
clockworkmod\download
and two files
Code:
.nomedia
and
Code:
.settings
inside "clockworkmod" folder.
What is the role of "download" folder and those two files ?Do they have anything to do with the nandroid backup ?If I want to restore any nandroid backup,do I also need to move that "download" folder and those two files to "clockworkmod" folder or only moving the backup inside "backup" folder will do the job ?

optimusodd said:
Hi mate,thanks for your reply.I really appreciate it.There are somethings I need to ask.
1.Right now I am on CWM 2.5.0.1,so before restoring the backup taken by CWM 5.0.2.8 I will have to flash CWM 5.0.2.8 first.Right ?
2.AFAIK,Nandroid Backup is stored in the "backup" folder
Code:
clockworkmod\backup
Right ?
There is another folder "download"
Code:
clockworkmod\download
and two files
Code:
.nomedia
and
Code:
.settings
inside "clockworkmod" folder.
What is the role of "download" folder and those two files ?Do they have anything to do with the nandroid backup ?If I want to restore any nandroid backup,do I also need to move that "download" folder and those two files to "clockworkmod" folder or only moving the backup inside "backup" folder will do the job ?
Click to expand...
Click to collapse
If you made the back up with cwm 5 you will need cwm 5 pal. The difference between those two recovery is a scripting change, going from amend to edify I believe. So you need version 5 if that's what the back up was made with
Second your back ups are indeed within the cwm/backup folder. The other folder is for if you use the Rom manager application ( which is made by the same gentleman who makes and maintains cwm recovery) the setting file tells the app your default app settings and preferences and the .nomedia is a dummy file. When android apps like music players and picture viewers ect scan the sdcard for content they also look for the .nomedia file, which tells the app simply that there is no media in the folder and that it does not need to scan it should you want to make one simply create a .txt file and rename it to .nomedia and android apps will ignore the folder when looking for media
So should you want to back up your backups as it were simply copy the whole backup folder from your sd card to your pc, job done
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

heavy_metal_man said:
The other folder is for if you use the Rom manager application ( which is made by the same gentleman who makes and maintains cwm recovery) the setting file tells the app your default app settings and preferences and the .nomedia is a dummy file. When android apps like music players and picture viewers ect scan the sdcard for content they also look for the .nomedia file, which tells the app simply that there is no media in the folder and that it does not need to scan it should you want to make one simply create a .txt file and rename it to .nomedia and android apps will ignore the folder when looking for media
Click to expand...
Click to collapse
Ah okay,thanks for the explanation.
Okay I used nandroid manager to restore the backup and evrything went well till the end.No error.Nothing.After the completion it rebooted the device and it again got stuck on bootscreen.It has been stuck on bootscreen for last 20 mints.I don't understand why

optimusodd said:
Ah okay,thanks for the explanation.
Okay I used nandroid manager to restore the backup and evrything went well till the end.No error.Nothing.After the completion it rebooted the device and it again got stuck on bootscreen.It has been stuck on bootscreen for last 20 mints.I don't understand why
Click to expand...
Click to collapse
Hmmmm. That's very strange. Do you know how to do a logcat to a text file? If so do one and capture it at boot and we will see if it gives us an error
Sent from my Nexus 7 using Tapatalk 4

heavy_metal_man said:
Hmmmm. That's very strange. Do you know how to do a logcat to a text file? If so do one and capture it at boot and we will see if it gives us an error Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Okay I had taken a nandroid backup using CWM 5.0.2.8 to be on the safe side before trying to restore the backup via Nandroid manager.So when the restore process via Nandroid manager ended up again as stucked on bootscreen I wiped everything and took the nandroid restore and it was successful.WTH is going on.Seriously,I am clueless
Okay,capture it using adb or CatLog ?

optimusodd said:
Okay I had taken a nandroid backup using CWM 5.0.2.8 to be on the safe side before trying to restore the backup via Nandroid manager.So when the restore process via Nandroid manager ended up again as stucked on bootscreen I wiped everything and took the nandroid restore and it was successful.WTH is going on.Seriously,I am clueless
Click to expand...
Click to collapse
OK so now you have the rom installed with the correct data restored? That's a plus not sure how this has came about though
Sent from my Nexus 7 using Tapatalk 4

heavy_metal_man said:
OK so now you have the rom installed with the correct data restored? That's a plus not sure how this has came about though Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Nope not the one I want to restore.It's the restoration of the nandroid backup taken of clean CM 7.2 i.e CM7.2+Gapps+Nandroid Manager.
Okay,I do a logcat.
................................EDITED..........................
Hi,I have sent you the logcats.

Here is one of the logcats
HTML:
--------- beginning of /dev/log/main
[ 12-15 19:32:52.341 100:0x64 I/cm ]
Welcome to Android 2.3.7 / CyanogenMod-7.2.0-buzz
[ 12-15 19:32:52.351 101:0x65 I/cm ]
_
[ 12-15 19:32:52.371 102:0x66 I/cm ]
__ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
[ 12-15 19:32:52.391 103:0x67 I/cm ]
((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
[ 12-15 19:32:52.401 104:0x68 I/cm ]
)) _))
[ 12-15 19:32:52.421 105:0x69 I/cm ]
[ 12-15 19:32:52.651 119:0x77 I/mountsd ]
Checking filesystems..
[ 12-15 19:32:52.771 95:0x5f I/run-parts ]
e2fsck 1.41.12 (17-May-2010)
[ 12-15 19:32:52.801 95:0x5f I/run-parts ]
/dev/block/mmcblk0p2: clean, 84/65808 files, 53844/262912 blocks
[ 12-15 19:32:52.972 134:0x86 I/mountsd ]
/sd-ext successfully mounted
[ 12-15 19:32:53.602 169:0xa9 D/AK8973 ]
AK8973 daemon 1.3.4 Start
(Library version : 1.2.1.620)
--------- beginning of /dev/log/system
[ 12-15 19:32:53.832 160:0xa0 I/Vold ]
Vold 2.1 (the revenge) firing up
[ 12-15 19:32:53.872 160:0xa0 D/Vold ]
Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
[ 12-15 19:32:53.993 160:0xb5 D/Vold ]
USB connected
[ 12-15 19:32:54.003 160:0xb5 D/Vold ]
Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
[ 12-15 19:32:54.033 160:0xb5 D/Vold ]
Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
[ 12-15 19:32:54.093 161:0xa1 I/Netd ]
Netd 1.0 starting
[ 12-15 19:32:54.213 160:0xb5 D/Vold ]
USB connected
[ 12-15 19:32:54.423 162:0xa2 I/DEBUG ]
debuggerd: Jun 15 2012 12:13:45
[ 12-15 19:32:55.744 164:0xa4 D/AndroidRuntime ]
>>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
[ 12-15 19:32:55.744 164:0xa4 I/AndroidRuntime ]
Heap size: -Xmx32m
[ 12-15 19:32:55.744 164:0xa4 D/AndroidRuntime ]
CheckJNI is OFF
[ 12-15 19:32:56.285 165:0xa5 I/ ]
ServiceManager: 0xad50
[ 12-15 19:32:56.305 165:0xa5 I/HTC Acoustic ]
libhtc_acoustic.so version 1.0.1.4.
[ 12-15 19:32:56.305 165:0xa5 E/HTC Acoustic ]
Fail to open /system/etc/AudioPara_ALL.csv -1.
[ 12-15 19:32:56.305 165:0xa5 I/HTC Acoustic ]
open /system/etc/AudioPara4.csv success.
[ 12-15 19:32:56.335 165:0xa5 I/HTC Acoustic ]
acoustic table version: Buzz_Generic_20100804
[ 12-15 19:32:56.365 165:0xa5 I/HTC Acoustic ]
read_audio_para_from_file success.
[ 12-15 19:32:56.365 165:0xa5 I/HTC Acoustic ]
get_audpp_filter
[ 12-15 19:32:56.365 165:0xa5 I/HTC Acoustic ]
open /system/etc/AudioFilter.csv success.
[ 12-15 19:32:56.365 165:0xa5 I/HTC Acoustic ]
ADRC Filter ADRC FLAG = ffff.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP THRESHOLD = 2550.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP SLOPE = b333.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP RMS TIME = 106.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP ATTACK[0] = 7f7d.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP ATTACK[1] = 3096.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP RELEASE[0] = 7ff7.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP RELEASE[1] = 4356.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
ADRC Filter COMP DELAY = 16.
[ 12-15 19:32:56.375 165:0xa5 I/HTC Acoustic ]
EQ flag = ffff.
[ 12-15 19:32:56.395 165:0xa5 I/HTC Acoustic ]
get_audpre_filter
[ 12-15 19:32:56.395 165:0xa5 I/HTC Acoustic ]
open /system/etc/AudioPreProcess.csv success.
[ 12-15 19:32:56.395 165:0xa5 D/AudioHardwareMSM72XX ]
mNumSndEndpoints = 80
[ 12-15 19:32:56.405 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH HANDSET
[ 12-15 19:32:56.405 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH SPEAKER
[ 12-15 19:32:56.405 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH HEADSET
[ 12-15 19:32:56.405 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH BT
[ 12-15 19:32:56.405 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH CARKIT
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH TTY_FULL
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH TTY_VCO
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH TTY_HCO
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH NO_MIC_HEADSET
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH FM_HEADSET
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH HEADSET_AND_SPEAKER
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH FM_SPEAKER
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH BT_EC_OFF
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareMSM72XX ]
BT MATCH CURRENT
[ 12-15 19:32:56.415 165:0xa5 D/AudioHardwareInterface ]
setMode(NORMAL)
[ 12-15 19:32:56.415 165:0xa5 I/AudioHardwareMSM72XX ]
Set master volume to 5.
[ 12-15 19:32:56.435 165:0xa5 I/CameraService ]
CameraService started (pid=165)
[ 12-15 19:32:56.445 165:0xd5 I/AudioFlinger ]
AudioFlinger's thread 0xf2e0 ready to run
[ 12-15 19:32:56.445 165:0xd4 D/AudioFlinger ]
setParameters(): io 1, keyvalue routing=2, tid 212, calling tid 165
[ 12-15 19:32:56.455 165:0xd5 I/AudioHardwareMSM72XX ]
Routing audio to Speakerphone
[ 12-15 19:32:56.455 165:0xd5 D/HTC Acoustic ]
msm72xx_enable_audpp: 0x0007
[ 12-15 19:32:56.465 165:0xd4 D/AudioHardwareMSM72XX ]
setVoiceVolume(1.000000)
[ 12-15 19:32:56.465 165:0xd4 I/AudioHardwareMSM72XX ]
Setting in-call volume to 5 (available range is 0 to 5)
[ 12-15 19:32:57.836 164:0xa4 I/SamplingProfilerIntegration ]
Profiler is disabled.
[ 12-15 19:32:57.906 164:0xa4 I/Zygote ]
Preloading classes...
[ 12-15 19:32:57.916 164:0xa4 E/Zygote ]
setreuid() failed. errno: 2
[ 12-15 19:32:57.926 164:0xa4 D/dalvikvm ]
GC_EXPLICIT freed 48K, 77% free 239K/1024K, external 0K/0K, paused 11ms
[ 12-15 19:32:58.137 164:0xa4 I/bluetooth_ScoSocket.cpp ]
Entry name = MY-CAR ScoTypes = 0x7f
[ 12-15 19:32:58.137 164:0xa4 I/bluetooth_ScoSocket.cpp ]
Entry name = Motorola HF850 ScoTypes = 0x7
[ 12-15 19:33:00.199 164:0xa4 D/szipinf ]
Initializing inflate state
[ 12-15 19:33:04.683 164:0xa4 D/dalvikvm ]
GC_FOR_MALLOC freed 2913K, 57% free 2209K/5123K, external 0K/0K, paused 99ms
[ 12-15 19:33:06.375 164:0xa4 D/dalvikvm ]
GC_FOR_MALLOC freed 2631K, 52% free 2488K/5123K, external 0K/0K, paused 93ms
[ 12-15 19:33:10.529 164:0xa4 I/Zygote ]
...preloaded 1829 classes in 12629ms.
[ 12-15 19:33:10.529 164:0xa4 D/Zygote ]
setreuid() error ignored, same uid.
[ 12-15 19:33:10.619 164:0xa4 D/dalvikvm ]
GC_EXPLICIT freed 891K, 48% free 2685K/5123K, external 0K/0K, paused 82ms
[ 12-15 19:33:10.619 164:0xa4 I/Zygote ]
Preload resources disabled, skipped.
[ 12-15 19:33:10.689 164:0xa4 D/dalvikvm ]
GC_EXPLICIT freed 25K, 49% free 2660K/5123K, external 0K/0K, paused 67ms
[ 12-15 19:33:10.759 164:0xa4 D/dalvikvm ]
GC_EXPLICIT freed <1K, 49% free 2660K/5123K, external 0K/0K, paused 66ms
[ 12-15 19:33:10.819 164:0xa4 D/dalvikvm ]
GC_EXPLICIT freed <1K, 49% free 2660K/5123K, external 0K/0K, paused 66ms
[ 12-15 19:33:10.839 164:0xa4 I/dalvikvm ]
System server process 222 has been created
[ 12-15 19:33:10.839 164:0xa4 I/Zygote ]
Accepting command socket connections
[ 12-15 19:33:11.239 222:0xde I/sysproc ]
Entered system_init()
[ 12-15 19:33:11.239 222:0xde I/sysproc ]
ServiceManager: 0x817f8
[ 12-15 19:33:11.249 222:0xde I/SurfaceFlinger ]
SurfaceFlinger is starting
[ 12-15 19:33:11.249 222:0xde I/SurfaceFlinger ]
dithering enabled
[ 12-15 19:33:11.249 222:0xe6 I/SurfaceFlinger ]
SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
[ 12-15 19:33:11.269 222:0xe6 I/gralloc ]
using (fd=27)
id = msmfb
xres = 240 px
yres = 320 px
xres_virtual = 240 px
yres_virtual = 640 px
bpp = 16
r = 11:5
g = 5:6
b = 0:5
[ 12-15 19:33:11.269 222:0xe6 I/gralloc ]
width = 49 mm (124.408165 dpi)
height = 65 mm (125.046150 dpi)
refresh rate = 60.00 Hz
[ 12-15 19:33:11.279 222:0xe6 D/libEGL ]
egl.cfg not found, using default config
[ 12-15 19:33:11.289 222:0xe6 D/libEGL ]
loaded /system/lib/egl/libGLES_android.so
[ 12-15 19:33:11.309 222:0xe6 I/SurfaceFlinger ]
EGL informations:
[ 12-15 19:33:11.309 222:0xe6 I/SurfaceFlinger ]
# of configs : 8
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
vendor : Android
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
version : 1.4 Android META-EGL
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_ANDROID_image_native_buffer EGL_ANDROID_swap_rectangle EGL_ANDROID_get_render_buffer
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
Client API: OpenGL ES
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
EGLSurface: 5-6-5-0, config=0x0
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
OpenGL informations:
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
vendor : Android
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
renderer : Android PixelFlinger 1.4
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
version : OpenGL ES-CM 1.0
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_OES_EGL_image GL_OES_compressed_ETC1_RGB8_texture GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
GL_MAX_TEXTURE_SIZE = 4096
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
GL_MAX_VIEWPORT_DIMS = 4096
[ 12-15 19:33:11.319 222:0xe6 I/SurfaceFlinger ]
flags = 000c0000
[ 12-15 19:33:11.330 222:0xde D/SensorService ]
nuSensorService starting...
[ 12-15 19:33:11.340 169:0xa9 D/AK8973 ]
Compass Start
[ 12-15 19:33:11.390 222:0xde I/SensorService ]
BMA150 3-axis Accelerometer
[ 12-15 19:33:11.390 222:0xde I/SensorService ]
AK8973 3-axis Magnetic field sensor
[ 12-15 19:33:11.390 222:0xde I/SensorService ]
AK8973 Orientation sensor
[ 12-15 19:33:11.390 222:0xde I/SensorService ]
CM3602 Proximity sensor
[ 12-15 19:33:11.400 222:0xde I/SensorService ]
CM3602 Light sensor
[ 12-15 19:33:11.400 222:0xde I/sysproc ]
System server: starting Android runtime.
[ 12-15 19:33:11.400 222:0xde I/sysproc ]
System server: starting Android services.
[ 12-15 19:33:11.410 222:0xeb D/SensorService ]
nuSensorService thread starting...
[ 12-15 19:33:11.420 222:0xde I/SystemServer ]
Entered the Android system server!
[ 12-15 19:33:11.440 222:0xde I/sysproc ]
System server: entering thread pool.
[ 12-15 19:33:11.440 222:0xec I/SystemServer ]
Entropy Service
[ 12-15 19:33:11.500 222:0xec I/SystemServer ]
Power Manager
[ 12-15 19:33:11.520 222:0xec I/SystemServer ]
Activity Manager
[ 12-15 19:33:11.610 222:0xed I/ActivityManager ]
Memory class: 32
[ 12-15 19:33:11.750 232:0xef D/libEGL ]
egl.cfg not found, using default config
[ 12-15 19:33:11.760 232:0xef D/libEGL ]
loaded /system/lib/egl/libGLES_android.so
[ 12-15 19:33:11.790 232:0xef W/zipro ]
Unable to open zip '/data/local/bootanimation.zip': No such file or directory
[ 12-15 19:33:12.010 232:0xef I/ARMAssembler ]
generated scanline__00000077:03010104_00008004_00000000 [ 84 ipp] (103 ins) at [0x4076c1e8:0x4076c384] in 3387451 ns
[ 12-15 19:33:12.130 222:0xed I/UsageStats ]
Deleting usage file : usage-20130830
[ 12-15 19:33:12.270 169:0xa9 D/AK8973 ]
Compass CLOSE
[ 12-15 19:33:12.421 222:0xec I/SystemServer ]
Telephony Registry
[ 12-15 19:33:12.461 222:0xec I/SystemServer ]
Package Manager
[ 12-15 19:33:12.501 167:0xa7 I/installd ]
new connection
[ 12-15 19:33:12.501 222:0xec I/Installer ]
connecting...
[ 12-15 19:33:12.771 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 156K, 47% free 3020K/5639K, external 0K/0K, paused 7ms+22ms
[ 12-15 19:33:13.602 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 314K, 47% free 3239K/6023K, external 0K/0K, paused 22ms+12ms
[ 12-15 19:33:14.733 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 537K, 49% free 3260K/6279K, external 0K/0K, paused 7ms+9ms
[ 12-15 19:33:16.014 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:16.124 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 272K, 46% free 3423K/6279K, external 0K/0K, paused 8ms+49ms
[ 12-15 19:33:16.715 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:16.785 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:16.875 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:16.965 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:17.746 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:18.136 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:18.336 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:18.446 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 164K, 42% free 3694K/6343K, external 0K/0K, paused 7ms+20ms
[ 12-15 19:33:18.466 222:0xec W/PackageParser ]
No actions in intent filter at /system/app/Bluetooth.apk Binary XML file line #132
[ 12-15 19:33:18.466 222:0xec W/PackageParser ]
No actions in intent filter at /system/app/Bluetooth.apk Binary XML file line #154
[ 12-15 19:33:18.667 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:18.847 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:19.167 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:19.387 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:19.507 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:19.888 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:20.138 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:20.388 222:0xec I/PackageManager ]
Package com.android.vending at /system/app/Vending.apk ignored: updated version 80230011 better than this 8007003
[ 12-15 19:33:20.779 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:21.600 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 275K, 42% free 3934K/6727K, external 0K/0K, paused 7ms+38ms
[ 12-15 19:33:21.630 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:21.760 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:22.811 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:23.071 222:0xec I/PackageManager ]
Package com.noshufou.android.su at /system/app/Superuser.apk ignored: updated version 46 better than this 38
[ 12-15 19:33:23.081 222:0xec D/PackageManager ]
No files in app dir /vendor/app
[ 12-15 19:33:23.231 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.nuance.swype.trial-1.apk'
[ 12-15 19:33:23.231 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.nuance.swype.trial-1.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:23.321 222:0xec W/PackageManager ]
Package mobi.infolife.uninstaller desires unavailable shared library com.sec.android.app.multiwindow; ignoring!
[ 12-15 19:33:23.531 222:0xec W/ResourceType ]
Failure getting entry for 0x7f09002b (t=8 e=43) in package 0 (error -75)
[ 12-15 19:33:23.992 222:0xe0 D/dalvikvm ]
GC_CONCURRENT freed 300K, 41% free 4064K/6855K, external 0K/0K, paused 20ms+27ms
[ 12-15 19:33:24.042 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.google.android.gms-2.apk'
[ 12-15 19:33:24.062 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.google.android.gms-2.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:24.132 222:0xec D/asset ]
failed to open Zip archive '/data/app/netgenius.bizcal-1.apk'
[ 12-15 19:33:24.132 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/netgenius.bizcal-1.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:24.352 222:0xec W/ResourceType ]
Failure getting entry for 0x7f050000 (t=4 e=0) in package 0 (error -75)
[ 12-15 19:33:24.392 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.googlecode.droidwall.free-1.apk'
[ 12-15 19:33:24.402 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.googlecode.droidwall.free-1.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:24.412 222:0xec D/szipinf ]
Initializing inflate state
[ 12-15 19:33:24.522 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.ruimaninfo.approtect-1.apk'
[ 12-15 19:33:24.532 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.ruimaninfo.approtect-1.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:24.783 222:0xec D/asset ]
failed to open Zip archive '/data/app/org.adaway-2.apk'
[ 12-15 19:33:24.793 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/org.adaway-2.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:25.003 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.modoohut.dialer.theme.dark-1.apk'
[ 12-15 19:33:25.013 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.modoohut.dialer.theme.dark-1.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)
[ 12-15 19:33:25.013 222:0xec D/asset ]
failed to open Zip archive '/data/app/com.buak.Link2SD-2.apk'
[ 12-15 19:33:25.023 222:0xec W/PackageParser ]
Unable to read AndroidManifest.xml of /data/app/com.buak.Link2SD-2.apk
java.io.FileNotFoundException: AndroidManifest.xml
at android.content.res.AssetManager.openXmlAssetNative(Native Method)
at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
at android.content.pm.PackageParser.parsePackage(PackageParser.java:428)
at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2715)
at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2640)
at com.android.server.PackageManagerService.<init>(PackageManagerService.java:1029)
at com.android.server.PackageManagerService.main(PackageManagerService.java:725)
at com.android.server.ServerThread.run(SystemServer.java:178)

Is there any chance someone can explain what's going wrong and help me to get it running again ?
I will really appreciate that.
dmseg log
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 2.6.35.14-SympFinity+ ([email protected]) (gcc version 4.4.3 (GCC) ) #40 PREEMPT Wed May 2 14:11:03 CEST 2012
<4>[ 0.000000] CPU: ARMv6-compatible processor [4117b362] revision 2 (ARMv6TEJ), cr=00c5387f
<4>[ 0.000000] CPU: VIPT aliasing data cache, VIPT aliasing instruction cache
<4>[ 0.000000] Machine: buzz
<7>[ 0.000000] find the smi tag
<7>[ 0.000000] parse_tag_smi: smi size = 0
<7>[ 0.000000] find the hwid tag
<7>[ 0.000000] parse_tag_hwid: hwid = 0x1
<7>[ 0.000000] find the skuid tag
<7>[ 0.000000] parse_tag_skuid: hwid = 0x2490b
<7>[ 0.000000] tag_panel_parsing: panel type = 0
<7>[ 0.000000] find the engineer tag
<7>[ 0.000000] parse_tag_engineerid: 0x0
<4>[ 0.000000] Ignoring unrecognised tag 0x4d534d76
<4>[ 0.000000] Ignoring unrecognised tag 0x5441000a
<6>[ 0.000000] CAM_AWB_CAL Data size = 514 , 0x59504550, size = 2048
<4>[ 0.000000] Ignoring unrecognised tag 0x41387898
<4>[ 0.000000] BT Data size= 4, 0x43294329,d4,20,6d,94,70,72,00,00,Memory policy: ECC disabled, Data cache writeback
<7>[ 0.000000] On node 0 totalpages: 82432
<7>[ 0.000000] free_area_init_node: node 0, pgdat c052ed50, node_mem_map c06d2000
<7>[ 0.000000] Normal zone: 1156 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 81276 pages, LIFO batch:15
<4>[ 0.000000] buzz_init_map_io()
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 81276
<5>[ 0.000000] Kernel command line: board_buzz.disable_uart3=0 board_buzz.usb_h2w_sw=0 board_buzz.disable_sdcard=0 diag.enabled=0 board_buzz.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=false androidboot.baseband=3.35.20.10 androidboot.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL androidboot.mid=PC4910000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=MB139PY05248 androidboot.bootloader=6.01.1002 zygote_oneshot=off no_console_suspend=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected]40000(system),[email protected](cache),[email protected](userdata)
<6>[ 0.000000] board_bootloader_setup: 6.01.1002
<6>[ 0.000000] board_bootloader_setup: default ENG BUILD
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 210MB 112MB = 322MB total
<5>[ 0.000000] Memory: 319632k/319632k available, 10096k reserved, 0K highmem
<5>[ 0.000000] Virtual kernel memory layout:
<5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
<5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
<5>[ 0.000000] DMA : 0xffa00000 - 0xffe00000 ( 4 MB)
<5>[ 0.000000] vmalloc : 0xe4800000 - 0xf8000000 ( 312 MB)
<5>[ 0.000000] lowmem : 0xc0000000 - 0xe4200000 ( 578 MB)
<5>[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
<5>[ 0.000000] .init : 0xc0008000 - 0xc002c000 ( 144 kB)
<5>[ 0.000000] .text : 0xc002c000 - 0xc04f6000 (4904 kB)
<5>[ 0.000000] .data : 0xc04f6000 - 0xc052f360 ( 229 kB)
<6>[ 0.000000] NR_IRQS:277
<4>[ 0.000000] buzz_init_irq()
<6>[ 0.000000] Calibrating delay loop... 480.05 BogoMIPS (lpj=2400256)
<6>[ 0.250122] pid_max: default: 32768 minimum: 301
<4>[ 0.250579] Mount-cache hash table entries: 512
<6>[ 0.251434] Initializing cgroup subsys cpuacct
<6>[ 0.251525] Initializing cgroup subsys freezer
<6>[ 0.251525] Initializing cgroup subsys net_cls
<6>[ 0.251556] Initializing cgroup subsys bfqio
<6>[ 0.251586] Initializing cgroup subsys timer_slack
<6>[ 0.251647] CPU: Testing write buffer coherency: ok
<6>[ 0.256469] NET: Registered protocol family 16
<4>[ 0.257446] buzz_init() revision = 0x81
<6>[ 0.257507] BT HW address=d4:20:6d:94:70:72
<6>[ 1.876647] acpu_clock_init()
<6>[ 1.877136] ACPU running at 480000 KHz
<6>[ 1.878387] ram_console: got buffer at 2d9b000, size 20000
<6>[ 1.878936] ram_console: uncorrectable error in header
<6>[ 1.879028] ram_console: no valid data in buffer (sig = 0xffffffff)
<6>[ 1.905426] console [ram-1] enabled
<6>[ 1.905761] buzz_init_mmc
<6>[ 1.908264] buzz_wifi_init: start
<4>[ 1.919372] bio: create slab <bio-0> at 0
<6>[ 1.922119] [DISP]mdp_probe: initialized
<6>[ 1.922943] msm_i2c_probe
<6>[ 1.923492] msm_i2c_probe: clk_ctl 315, 400000 Hz
<6>[ 1.927551] Bluetooth: Core ver 2.16
<6>[ 1.928070] NET: Registered protocol family 31
<6>[ 1.928375] Bluetooth: HCI device and connection manager initialized
<6>[ 1.928924] Bluetooth: HCI socket layer initialized
<6>[ 1.929229] Bluetooth: L2CAP socket layer initialized
<6>[ 1.930267] Bluetooth: SCO socket layer initialized
<6>[ 1.931182] Switching to clocksource gp_timer
<6>[ 1.934631] NET: Registered protocol family 2
<6>[ 1.935455] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>[ 1.937103] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
<6>[ 1.938598] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
<6>[ 1.939666] TCP: Hash tables configured (established 16384 bind 16384)
<6>[ 1.940216] TCP reno registered
<6>[ 1.940521] UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 1.940856] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 1.942077] NET: Registered protocol family 1
<6>[ 1.943023] Unpacking initramfs...
<6>[ 1.975341] Freeing initrd memory: 144K
<6>[ 1.976989] [SMD]smd_init()
<6>[ 1.977294] [SMD]smd_core_init()
<6>[ 1.977600] [SMD]phy addr of smd_info.state=0x8023A0
<6>[ 1.978302] [SMD]smd_core_init() done
<3>[ 1.978607] msm_init_last_radio_log: could not retrieve SMEM_CLKREGIM_BSP
<3>[ 1.979278] _smem_log_init: no power log or log_idx allocated, smem_log disabled
<6>[ 1.980804] [SMD]smd_alloc_channel() cid=01 size=08192 'SMD_DIAG'
<6>[ 1.981658] [SMD]smd_alloc_channel() cid=02 size=08192 'SMD_RPCCALL'
<6>[ 1.984985] [SMD]SMD: ch 2 0 -> 1
<6>[ 1.985382] [SMD]smd_alloc_channel() cid=11 size=65536 'SMD_DATA5'
<6>[ 1.985687] [SMD]SMD: ch 2 1 -> 2
<6>[ 1.986602] [SMD]smd_alloc_channel() cid=12 size=08192 'SMD_DATA6'
<6>[ 1.987152] [SMD]smd_alloc_channel() cid=13 size=08192 'SMD_DATA7'
<6>[ 1.987884] [SMD]smd_alloc_channel() cid=38 size=08192 'SMD_DATA5_CNTL'
<6>[ 1.988342] [SMD]smd_alloc_channel() cid=39 size=08192 'SMD_DATA6_CNTL'
<6>[ 1.989044] [SMD]smd_alloc_channel() cid=40 size=08192 'SMD_DATA7_CNTL'
<6>[ 1.996368] Acquire 'boot-time' no_halt_lock 60s
<6>[ 1.997589] [HS_MGR] (headset_notifier_register) Register MIC_BIAS notifier
<6>[ 1.998138] [HS_MGR] (headset_notifier_update) HS_MGR driver is not ready
<7>[ 2.018249] Registered led device: flashlight
<6>[ 2.018585] [FLT]flashlight_probe: led_count = 0
<6>[ 2.019104] [FLT]flashlight_probe: The Flashlight Driver is ready
<6>[ 2.029968] atmega-microp 0-0066: microp version [06][22]
<3>[ 2.034484] microp_function_check: No function 2 !!
<6>[ 2.038024] [HS_MGR] (htc_headset_mgr_probe) ++++++++++++++++++++
<6>[ 2.040222] input: h2w headset as /devices/virtual/input/input0
<6>[ 2.041198] [HS_MGR] (hs_notify_driver_ready) HS_MGR ready
<6>[ 2.042266] [HS_MGR] (htc_headset_mgr_probe) --------------------
<6>[ 2.043060] [HS_MICROP] (htc_headset_microp_probe) ++++++++++++++++++++
<6>[ 2.047729] [HS_MGR] (headset_notifier_register) Register REMOTE_ADC notifier
<6>[ 2.048309] [HS_MGR] (headset_notifier_register) Register MIC_STATUS notifier
<6>[ 2.048614] [HS_MGR] (headset_notifier_register) Register KEY_INT_ENABLE notifier
<6>[ 2.049133] [HS_MGR] (hs_notify_driver_ready) HS_MICROP ready
<6>[ 2.049865] [HS_GPIO] (htc_headset_gpio_probe) ++++++++++++++++++++
<6>[ 2.051300] [HS_MGR] (headset_notifier_register) Register HPIN_GPIO notifier
<6>[ 2.052032] [HS_MGR] (hs_notify_driver_ready) HS_GPIO ready
<6>[ 2.052368] [HS_GPIO] (htc_headset_gpio_probe) --------------------
<6>[ 2.052917] [HS_MICROP] (htc_headset_microp_probe) --------------------
<6>[ 2.080139] [BATT] M2A_RPC: cable_update: USB at 458867027 (1970-01-01 00:00:00.458257102 UTC)
<6>[ 2.081024] [BATT] htc_cable_status_update: 0 -> 1
<6>[ 2.081329] [USB] msm_hsusb_set_vbus_state: 1
<6>[ 2.083099] ashmem: initialized
<6>[ 2.084472] [BATT] A2M_RPC: get_batt_info: batt_id=1, batt_vol=3893, batt_temp=309, batt_current=1017, level=72, charging_source=1, charging_enabled=1, full_bat=1300000, over_vchg=0 at 463716046 (1970-01-01 00:00:00.462557151 UTC)
<5>[ 2.087890] Slow work thread pool: Starting up
<5>[ 2.101501] Slow work thread pool: Ready
<6>[ 2.102264] fuse init (API version 7.14)
<6>[ 2.104644] aufs 2.1-standalone.tree-35-20110418
<4>[ 2.104980] yaffs May 2 2012 14:03:42 Installing.
<6>[ 2.116912] io scheduler noop registered
<6>[ 2.117492] io scheduler bfq registered
<6>[ 2.118041] io scheduler sio registered (default)
<6>[ 2.118316] io scheduler vr registered
<6>[ 2.119354] [DISP]mddi: init() base=0xe4814000 irq=16
<7>[ 2.120178] [DISP]mddi runs at 81920000
<6>[ 2.122161] [DISP]mddi cmd send rtd: int 3a000, stat 8063, rtd val 10
<6>[ 2.125061] [DISP]mddi: registering panel mddi_c_0101_04d1
<6>[ 2.125366] [DISP]mddi: publish:
<7>[ 2.128784] [DISP]mddi_s6d04d1_probe: enter.
<6>[ 2.129547] [DISP]vsync on gpio 97 now 0
<6>[ 2.129852] [DISP]CABC enabled
<7>[ 2.131408] Registered led device: lcd-backlight
<6>[ 2.133544] [DISP]msmfb_probe() installing 240 x 320 panel
<6>[ 2.137268] PRUE G
<6>[ 2.137908] msm_serial_hs.0: ttyHS0 at MMIO 0xa0200000 (irq = 45) is a MSM HS UART
<6>[ 2.139251] msm_serial_hs module loaded
<6>[ 2.139923] [BT]msm_serial_hs module loaded
<6>[ 2.141357] [BT]msm_serial_hs module loaded
<6>[ 2.142852] [BT]msm_serial_hs module loaded
<6>[ 2.149993] loop: module loaded
<6>[ 2.150695] pmem: 1 init
<6>[ 2.151824] pmem_adsp: 0 init
<6>[ 2.153259] pmem_camera: 0 init
<6>[ 2.155090] spi_bma150_probe: G-sensor connect with microP: start initial, kvalue = 0x0
<6>[ 2.165435] [GSNR] Gsensor disable
<6>[ 2.167724] msm_nand: allocated dma buffer at ffa47000, dma_addr 26ecc000
<6>[ 2.168334] status: c03120
<6>[ 2.168640] nandid: 5500bcec maker ec device bc
<6>[ 2.169158] Found a supported NAND device
<6>[ 2.169433] NAND Id : 0xBCEC
<6>[ 2.169738] Buswidth : 16 Bits
<6>[ 2.170257] Density : 512 MByte
<6>[ 2.170532] Pagesize : 2048 Bytes
<6>[ 2.170806] Erasesize: 131072 Bytes
<6>[ 2.171295] Oobsize : 64 Bytes
<6>[ 2.171691] msm_nand: read CFG0 = aa5400c0, CFG1 = 8746a
<6>[ 2.172149] CFG0 Init : 0xe85408c0
<6>[ 2.172668] CFG1 Init : 0x0008746a
<6>[ 2.172943] CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=0 num_addr_cycles=5
<6>[ 2.173553] DEV_CMD1: f00f3000
<6>[ 2.173889] <6>NAND_EBI2_ECC_BUF_CFG: 1ff
<5>[ 2.174255] 6 cmdlinepart partitions found on MTD device msm_nand
<5>[ 2.174774] Creating 6 MTD partitions on "msm_nand":
<5>[ 2.175140] 0x00001ff60000-0x000020000000 : "misc"
<5>[ 2.178192] 0x000002760000-0x000002b80000 : "recovery"
<5>[ 2.184356] 0x000002b80000-0x000002e40000 : "boot"
<5>[ 2.189056] 0x000002e40000-0x000009c40000 : "system"
<6>[ 2.214324] [SMD]smd_alloc_channel() cid=27 size=08192 'SMD_GPSNMEA'
<5>[ 2.324920] 0x000009c40000-0x00000ab40000 : "cache"
<6>[ 2.337524] [SMD]smd_alloc_channel() cid=00 size=08192 'SMD_DS'
<6>[ 2.338500] [SMD]smd_alloc_channel() cid=07 size=08192 'SMD_DATA1'
<6>[ 2.339569] [SMD]smd_alloc_channel() cid=08 size=08192 'SMD_DATA2'
<6>[ 2.340545] [SMD]smd_alloc_channel() cid=09 size=08192 'SMD_DATA3'
<6>[ 2.341217] [SMD]smd_alloc_channel() cid=10 size=08192 'SMD_DATA4'
<6>[ 2.342712] [SMD]smd_alloc_channel() cid=15 size=65536 'SMD_DATA9'
<5>[ 2.348907] 0x00000ab40000-0x00001ff60000 : "userdata"
<6>[ 2.694793] PPP generic driver version 2.4.2
<6>[ 2.695587] PPP Deflate Compression module registered
<6>[ 2.695892] PPP BSD Compression module registered
<6>[ 2.699340] PPP MPPE Compression module registered
<6>[ 2.699676] NET: Registered protocol family 24
<6>[ 2.701385] tun: Universal TUN/TAP device driver, 1.6
<6>[ 2.701690] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>[ 2.706115] [USB] msm72k_probe
<6>[ 2.706451] [USB] accessory detect 1
<6>[ 2.706726] [USB] id_pin_gpio 19
<6>[ 2.707000] [USB] dock detect 0
<6>[ 2.707275] [USB] dock pin gpio 0
<6>[ 2.707763] [USB] msm72k_probe() io=e481c000, irq=47, dma=ffa48000(26ef6000)
<6>[ 2.710296] android init
<6>[ 2.710784] android_probe pdata: c0509938
<6>[ 2.711273] android_bind
<7>[ 2.711578] android_bind_config
<6>[ 2.712707] android_usb gadget: android_usb ready
<6>[ 2.713012] [USB] msm72k_udc: registered gadget driver 'android_usb'
<6>[ 2.713775] f_adb init
<6>[ 2.714050] android_register_function adb
<6>[ 2.714355] f_mass_storage init
<6>[ 2.714996] fsg_probe pdev: c0509a98, pdata: c050a484
<6>[ 2.715454] android_register_function usb_mass_storage
<6>[ 2.715728] f_rndis init
<6>[ 2.716491] android_register_function rndis
<6>[ 2.716766] f_accessory init
<6>[ 2.717041] android_register_function accessory
<6>[ 2.717559] diag init
<6>[ 2.717864] android_register_function diag
<6>[ 2.718170] rndis_function_bind_config MAC: 00:00:00:00:00:00
<4>[ 2.718841] android_usb gadget: using random self ethernet address
<4>[ 2.719177] android_usb gadget: using random host ethernet address
<6>[ 2.721954] acc_bind_config
<6>[ 2.723724] [USB] hsusb: IDLE -> ONLINE
<6>[ 2.724060] [USB] lpm exit
<6>[ 2.724639] [USB] hsusb: reset controller
<6>[ 2.725219] android_usb gadget: Mass Storage Function, version: 2009/09/11
<6>[ 2.725524] android_usb gadget: Number of LUNs=1
<6>[ 2.726074] lun0: LUN: removable file: (no medium)
<6>[ 2.726623] adb_bind_config
<6>[ 2.727661] diag_bind_config
<6>[ 2.728210] [SMD]SMD: ch 1 0 -> 1
<6>[ 2.728546] [SMD]SMD: ch 1 1 -> 2
<6>[ 2.729675] buzz_syn_ts_power: power 1
<6>[ 2.762145] msm_hsusb_phy_reset
<6>[ 2.912231] [USB] ulpi: write 0x2c to 0x31
<6>[ 2.912536] [USB] ulpi: write 0x20 to 0x32
<6>[ 2.913024] [USB] ulpi: write 0x01 to 0x0d
<6>[ 2.913299] [USB] ulpi: write 0x01 to 0x10
<6>[ 2.913604] [USB] handle_notify_offline: notify offline
<6>[ 2.914154] [USB] msm_hsusb: enable pullup
<6>[ 2.917449] [USB] suspend
<6>[ 2.932250] [USB] not AC charger
<6>[ 2.932800] [USB] accessory_detect_init: id pin 19
<6>[ 2.993591] synaptics_ts_probe: panel_version: 301
<6>[ 2.995056] max_x: 3DE, max_y: 5A6
<6>[ 2.996887] synaptics_ts_probe: max_x 990, max_y 1446
<6>[ 2.997161] input_set_abs_params: mix_x 0, max_x 990, min_y 0, max_y 1300
<6>[ 2.998229] input: synaptics-rmi-touchscreen as /devices/virtual/input/input1
<6>[ 2.999450] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode
<6>[ 3.000122] atmel_ts_init():
<6>[ 3.000915] buzz_ts_atmel_power():
<6>[ 3.023895] [USB] reset
<6>[ 3.024291] [USB] send connect type 1
<6>[ 3.024566] [BATT] online=1
<6>[ 3.024841] [BATT] Update SMEM: cable type 1 at 1403189275 (1970-01-01 00:00:01.402670622 UTC)
<6>[ 3.026184] [USB] portchange USB_SPEED_HIGH
<6>[ 3.184234] [USB] reset
<6>[ 3.186492] [USB] portchange USB_SPEED_HIGH
<6>[ 3.282318] No Messages after reset
<3>[ 3.282989] msm_i2c msm_i2c.0: error, status c8 (4A,00,01)(20,13,01)(cnt:7,pos:0)
<3>[ 3.283325] msm_i2c msm_i2c.0: Error during data xfer (-5) (4A,00,01)
<6>[ 3.283874] No Atmel chip inside
<4>[ 3.284362] atmel_qt602240: probe of 0-004a failed with error -5
<6>[ 3.285217] [PS][CM3602] capella_cm3602_probe: probe
<6>[ 3.286346] input: proximity as /devices/virtual/input/input2
<6>[ 3.287506] [PS][CM3602] capella_cm3602_setup
<6>[ 3.288635] [KEY] GPIO Matrix Keypad Driver: Start keypad matrix for buzz-keypad... in interrupt mode
<6>[ 3.289764] [KEY] GPIO_Input_ISR : 0, return IRQ_HANDLED;
<6>[ 3.290252] [KEY] GPIO Input Driver: Start gpio inputs for buzz-keypad... in interrupt mode
<6>[ 3.291442] input: buzz-keypad as /devices/virtual/input/input3
<6>[ 3.292602] input: buzz-nav as /devices/virtual/input/input4
<6>[ 3.294708] input: lightsensor-level as /devices/virtual/input/input5
<6>[ 3.295867] [KEY] gpio_keys_scan_keys: key 1-116, 0 (20) changed to 0
<6>[ 3.296295] [LS][CM3602] set_ls_kvalue: ALS calibrated als_kadc=0x6da5007b
<6>[ 3.296813] [LS][CM3602] set_ls_kvalue: als_kadc=0x7b, als_gadc=0xcf
<6>[ 3.297088] [LS][CM3602] ls_table: data[0] , data[0] = 0, 0
<6>[ 3.297607] [LS][CM3602] ls_table: data[1] , data[1] = 0, 1
<6>[ 3.297882] [LS][CM3602] ls_table: data[2] , data[2] = 0, 2
<6>[ 3.298370] [LS][CM3602] ls_table: data[3] , data[3] = 0, 8
<6>[ 3.298645] [LS][CM3602] ls_table: data[4] , data[4] = 0, 16
<6>[ 3.299163] [LS][CM3602] ls_table: data[5] , data[5] = 0, 59
<6>[ 3.299438] [LS][CM3602] ls_table: data[6] , data[6] = 0, a2
<6>[ 3.299957] [LS][CM3602] ls_table: data[7] , data[7] = 0, b1
<6>[ 3.300231] [LS][CM3602] ls_table: data[8] , data[8] = 0, bf
<6>[ 3.300720] [LS][CM3602] ls_table: data[9] , data[9] = 3, ff
<7>[ 3.303375] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[ 3.305236] input: curcial-oj as /devices/virtual/input/input6
<3>[ 3.307250] curcial_oj_poweron:eek:J:power status ok
<6>[ 3.356567] OpticalJoystick Device ID: 0d
<6>[ 3.359466] OJ Driver: Revision : 02
<6>[ 3.362548] OJ: driver loaded
<6>[ 3.365692] using rtc device, msm_rtc, for alarms
<6>[ 3.366058] rs30000048:915823fc rs30000048:915823fc: rtc core: registered msm_rtc as rtc0
<6>[ 3.367004] AKM8973 compass driver: init
<6>[ 3.368713] input: compass as /devices/virtual/input/input7
<6>[ 3.370635] [FLT]adp1650 Led Flash driver: init
<4>[ 3.371124] [CAM]s5k4e1gx_init
<4>[ 3.371643] [CAM]__s5k4e1gx_probe
<6>[ 3.372161] [CAM]s5k4e1gx_vreg_enable camera vreg on
<6>[ 3.372772] [CAM]sctrl.node 0
<4>[ 3.373046] [CAM]s5k4e1gx_sensor_probe()
<6>[ 3.373657] [CAM]s5k4e1gx_probe called!
<6>[ 3.424224] [CAM]s5k4e1gx_probe successed! rc = 0
<6>[ 3.424652] [CAM]s5k4e1gx s->node 0
<6>[ 3.437164] android_usb gadget: high speed config #1: android
<6>[ 3.471588] [CAM]s5k4e1gx_sensor_init(): reseting sensor.
<6>[ 3.472961] [CAM]sensor_lc_disable=0
<4>[ 3.568450] [CAM]sensor evt version : 0x10
<4>[ 3.568725] [CAM]use analog_settings_evt3
<6>[ 3.580780] s5k4e1gx_sysfs_init : kobject_create_and_add
<6>[ 3.581146] s5k4e1gx_sysfs_init : sysfs_create_file
<6>[ 3.583343] device-mapper: uevent: version 1.0.3
<6>[ 3.584838] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: [email protected]
<6>[ 3.585510] Bluetooth: HCI UART driver ver 2.2
<6>[ 3.585784] Bluetooth: HCI H4 protocol initialized
<6>[ 3.587799] cpuidle: using governor ladder
<6>[ 3.588104] cpuidle: using governor menu
<6>[ 3.589965] mmc0: Qualcomm MSM SDCC at 0x00000000a0400000 irq 24,0 dma 8
<6>[ 3.590484] mmc0: Platform slot type: N/A
<6>[ 3.590759] mmc0: 4 bit data mode enabled
<6>[ 3.591278] mmc0: 8 bit data mode disabled
<6>[ 3.591552] mmc0: MMC clock 144000 -> 49152000 Hz, PCLK 80000000 Hz
<6>[ 3.591827] mmc0: Slot eject status = 1
<6>[ 3.592437] mmc0: Power save feature enable = 1
<6>[ 3.592712] mmc0: DM non-cached buffer at ffa4a000, dma_addr 0x26f55000
<6>[ 3.593231] mmc0: DM cmd busaddr 0x26f55000, cmdptr busaddr 0x26f55300
<6>[ 3.594573] buzz_sdslot_switchvdd: Disabling SD slot power
<6>[ 3.595428] mmc1: Qualcomm MSM SDCC at 0x00000000a0500000 irq 26,102 dma 8
<6>[ 3.595733] mmc1: Platform slot type: SD
<6>[ 3.596221] mmc1: 4 bit data mode enabled
<6>[ 3.596496] mmc1: 8 bit data mode disabled
<6>[ 3.596984] mmc1: MMC clock 144000 -> 49152000 Hz, PCLK 80000000 Hz
<6>[ 3.597259] mmc1: Slot eject status = 1
<6>[ 3.597534] mmc1: Power save feature enable = 1
<6>[ 3.598022] mmc1: DM non-cached buffer at ffa4b000, dma_addr 0x26f56000
<6>[ 3.598327] mmc1: DM cmd busaddr 0x26f56000, cmdptr busaddr 0x26f56300
<7>[ 3.599487] Registered led device: amber
<7>[ 3.600006] Registered led device: green
<7>[ 3.600677] Registered led device: jogball-backlight
<7>[ 3.601135] Registered led device: button-backlight
<6>[ 3.601654] microp_led_probe: succeeded
<6>[ 3.604522] logger: created 256K log 'log_main'
<6>[ 3.605133] logger: created 256K log 'log_events'
<6>[ 3.605926] logger: created 256K log 'log_radio'
<6>[ 3.606445] logger: created 256K log 'log_system'
<6>[ 3.607299] zram: num_devices not specified. Using default: 1
<6>[ 3.607574] zram: Creating 1 devices ...
<6>[ 3.609008] GACT probability NOT on
<6>[ 3.609558] Mirror/redirect action on
<6>[ 3.609832] u32 classifier
<6>[ 3.610076] Actions configured
<6>[ 3.610595] Netfilter messages via NETLINK v0.30.
<6>[ 3.611083] nf_conntrack version 0.5.0 (4996 buckets, 19984 max)
<4>[ 3.611846] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
<4>[ 3.612518] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
<4>[ 3.613037] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<6>[ 3.613647] ctnetlink v0.93: registering with nfnetlink.
<6>[ 3.614288] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
<6>[ 3.614593] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>[ 3.615936] xt_time: kernel timezone is -0000
<6>[ 3.616363] IPv4 over IPv4 tunneling driver
<6>[ 3.617950] GRE over IPv4 tunneling driver
<6>[ 3.619628] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 3.620452] arp_tables: (C) 2002 David S. Miller
<6>[ 3.620880] TCP cubic registered
<6>[ 3.621704] NET: Registered protocol family 10
<6>[ 3.626342] Mobile IPv6
<6>[ 3.626800] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 3.627410] IPv6 over IPv4 tunneling driver
<6>[ 3.630920] NET: Registered protocol family 17
<6>[ 3.631317] NET: Registered protocol family 15
<6>[ 3.632507] Bluetooth: RFCOMM socket layer initialized
<6>[ 3.633026] Bluetooth: RFCOMM ver 1.11
<6>[ 3.633361] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 3.633850] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 3.634796] clock_late_init() disabled 16 unused clocks
<6>[ 3.635345] [Port list] init()
<6>[ 3.635620] [Port list] Virtual Address for port_list: [f8149a48]
<6>[ 3.636108] [Port list] Physical Address for port_list: [849A48]
<6>[ 3.637756] cpufreq: cpu0 init at 480000 switching to 352000
<6>[ 3.642211] rs30000048:915823fc rs30000048:915823fc: setting system clock to 2013-12-16 11:43:36 UTC (1387194216)
<4>[ 3.643127] Warning: unable to open an initial console.
<6>[ 3.643981] Freeing init memory: 144K
<6>[ 3.918975] keychord: using input dev h2w headset for fevent
<6>[ 3.919464] keychord: using input dev buzz-keypad for fevent
<6>[ 3.926330] yaffs: dev is 32505859 name is "mtdblock3"
<6>[ 3.926757] yaffs: passed flags ""
<4>[ 3.927001] yaffs: Attempting MTD mount on 31.3, "mtdblock3"
<4>[ 4.099121] yaffs: restored from checkpoint
<4>[ 4.100067] yaffs_read_super: isCheckpointed 1
<6>[ 4.103546] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 4.104003] yaffs: passed flags ""
[COLOR="Red"]<4>[ 4.104248] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<4>[ 4.712463] block 725 is bad
<4>[ 4.744262] block 845 is bad
<4>[ 4.797912] block 1049 is bad[/COLOR]
<4>[ 18.353271] Partially written block 1006 detected
<4>[ 18.353942] Partially written block 1006 detected
<4>[ 18.354339] Partially written block 1006 detected
<4>[ 18.354766] Partially written block 1006 detected
<4>[ 18.355346] Partially written block 1006 detected
<4>[ 18.355773] Partially written block 1006 detected
<4>[ 18.356353] Partially written block 1006 detected
<4>[ 18.356781] Partially written block 1006 detected
<4>[ 18.357360] Partially written block 1006 detected
<4>[ 18.357788] Partially written block 1006 detected
<4>[ 18.358184] Partially written block 1006 detected
<4>[ 18.358795] Partially written block 1006 detected
<4>[ 18.359191] Partially written block 1006 detected
<4>[ 18.359802] Partially written block 1006 detected
<4>[ 18.360198] Partially written block 1006 detected
<4>[ 18.360595] Partially written block 1006 detected
<4>[ 18.361206] Partially written block 1006 detected
<4>[ 18.361633] Partially written block 1006 detected
<4>[ 18.362213] Partially written block 1006 detected
<4>[ 18.362640] Partially written block 1006 detected
<4>[ 18.363250] Partially written block 1006 detected
<4>[ 18.363677] Partially written block 1006 detected
<4>[ 18.364105] Partially written block 1006 detected
<4>[ 18.364715] Partially written block 1006 detected
<4>[ 18.460662] yaffs_read_super: isCheckpointed 0
<6>[ 18.461517] yaffs: dev is 32505860 name is "mtdblock4"
<6>[ 18.461791] yaffs: passed flags ""
<4>[ 18.462005] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<4>[ 18.521240] yaffs_read_super: isCheckpointed 0
<3>[ 20.180206] init: service 'console' requires console
<6>[ 20.258422] enabling adb
<6>[ 20.281280] [USB] msm_hsusb: disable pullup
<6>[ 20.293457] [USB] msm_hsusb: enable pullup
<6>[ 20.297027] [USB] suspend
<6>[ 20.311981] adb_open
<6>[ 20.482727] [USB] reset
<6>[ 20.483032] [USB] handle_notify_offline: notify offline
<6>[ 20.484069] adb_release
<6>[ 20.485015] [USB] portchange USB_SPEED_HIGH
<6>[ 20.485534] adb_open
<6>[ 20.642822] [USB] reset
<6>[ 20.645080] [USB] portchange USB_SPEED_HIGH
<6>[ 20.715698] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 20.854614] android_usb gadget: high speed config #1: android
<6>[ 20.928436] [SMD]SMD: ch 0 0 -> 1
<6>[ 20.928771] [SMD]SMD: ch 0 1 -> 2
<6>[ 20.939819] [SMD]SMD: ch 38 0 -> 1
<6>[ 20.940155] [SMD]SMD: ch 38 1 -> 2
<6>[ 20.940368] [RIL] qmi: smd opened
<6>[ 20.942810] [RIL] qmi: ctl: wds use client_id 0x01
<6>[ 20.947113] [SMD]SMD: ch 39 0 -> 1
<6>[ 20.947448] [SMD]SMD: ch 39 1 -> 2
<6>[ 20.947875] [RIL] qmi: smd opened
<6>[ 20.948699] [RIL] qmi: ctl: wds use client_id 0x01
<6>[ 20.950500] [SMD]SMD: ch 40 0 -> 1
<6>[ 20.951080] [SMD]SMD: ch 40 1 -> 2
<6>[ 20.951324] [RIL] qmi: smd opened
<6>[ 20.952941] [RIL] qmi: ctl: wds use client_id 0x01
<6>[ 22.985412] [AUD][snd.c:snd_ioctl] snd_set_device 1 1 1
<6>[ 22.989074] [AUD][snd.c:snd_rpc_thread] snd_rpc_thread() start
<6>[ 22.989624] [AUD][snd.c:snd_rpc_thread] snd: rpc_reply status 0
<6>[ 22.992858] [AUD][snd.c:snd_ioctl] snd_set_volume 256 0 5
<6>[ 22.996887] [AUD][snd.c:snd_rpc_thread] snd: rpc_reply status 0
As you can see
<4>[ 4.104248] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<4>[ 4.712463] block 725 is bad
<4>[ 4.744262] block 845 is bad
<4>[ 4.797912] block 1049 is bad
Click to expand...
Click to collapse
Does that indicate bad blocks on SDCard ?

So i have reviewed your logcat and its not showing up anything that could make it bootloop :/ can you use nandroid manager to restore just the app data and see how it gets on for me? it shouldnt need to reboot to do it.

heavy_metal_man said:
So i have reviewed your logcat and its not showing up anything that could make it bootloop :/ can you use nandroid manager to restore just the app data and see how it gets on for me? it shouldnt need to reboot to do it.
Click to expand...
Click to collapse
Okay,thanks,I restored some user apps and system apps (including data).Some apps are working fine and restored back to previous state including CM Settings but some apps got messed up and data didn't get restored.
What should be the next move ?

optimusodd said:
Okay,thanks,I restored some user apps and system apps (including data).Some apps are working fine and restored back to previous state including CM Settings but some apps got messed up and data didn't get restored.
What should be the next move ?
Click to expand...
Click to collapse
Well that tells us that the nandroid back up has became corrupted somehow, or your sdcard partition is not the same as your nandroids. If it's corruption your pretty stuffed and will have to just start fresh, but I would first double check your partitioning and then attempt a final restore with nandroid manager. If it fails then delete the apps that don't work data and keep what works I suppose :/
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

heavy_metal_man said:
Well that tells us that the nandroid back up has became corrupted somehow, or your sdcard partition is not the same as your nandroids. If it's corruption your pretty stuffed and will have to just start fresh, but I would first double check your partitioning and then attempt a final restore with nandroid manager.
Click to expand...
Click to collapse
Thanks for the reply.
Huh,What do you mean by sdcard partition is not the same ?
Okay let me go into a little more detail.Few months back I was using 8GB card.And the nandoid backup I want to restore was taken on that card.
MTD partition size : 110 10
Ext3 :512 MB
Now I am using 16GB card with 1GB Ext3 partition.
No custom MTD partition.
Do I need to run custom MTD script ?
SDCard partition could be a problem if I was using a card of less capacity.But as both the memory capacity and the size of Ext3 partition are larger in this scenario so I think partition should not be a problem.
Correct me if I am wrong
Furthermore,the same nandroid backup got restored perfectly using the new card before that kernel and radio thing.Gah!

optimusodd said:
Thanks for the reply.
Huh,What do you mean by sdcard partition is not the same ?
Okay let me go into a little more detail.Few months back I was using 8GB card.And the nandoid backup I want to restore was taken on that card.
MTD partition size : 110 10
Ext3 :512 MB
Now I am using 16GB card with 1GB Ext3 partition.
No custom MTD partition.
Do I need to run custom MTD script ?
SDCard partition could be a problem if I was using a card of less capacity.But as both the memory capacity and the size of Ext3 partition are larger in this scenario so I think partition should not be a problem.
Correct me if I am wrong
Furthermore,the same nandroid backup got restored perfectly using the new card before that kernel and radio thing.Gah!
Click to expand...
Click to collapse
If you made the nandroid with a custom mtd the you had best restore it with a custom mtd. I'm not 100% sure how it's done or the theory around it though, it's been a long time since I've had to do such things.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

heavy_metal_man said:
If you made the nandroid with a custom mtd the you had best restore it with a custom mtd. I'm not 100% sure how it's done or the theory around it though, it's been a long time since I've had to do such things.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
Click to expand...
Click to collapse
Alright,buddy,I give it a try.:fingers-crossed:

Happy New Year! Well, sorry for being a bit unresponsive - I'm really late (and still have no time) - just a quick $ 0.02: if I'm not totally mistaken it makes a huge difference if you use custom mtd partitions. The recovery makes an image of the partitions which means on restore the same size is expected (which would also apply to your sd-ext...)
Best bet should be: make a restore with the old settings (custom mtd partitions and sd-ext) and sequentially backup the stuff in other ways than with a nandroid backup. See if it works. Alternatively you could extract the stuff out of the backup - but this might become really painful...
Hope this helps.
BTW: my problem you were refering to has been totally different as I've never been stuck on boot - I had massive random reboots - so this was another story...

heavy_metal_man said:
If you made the nandroid with a custom mtd the you had best restore it with a custom mtd. I'm not 100% sure how it's done or the theory around it though, it's been a long time since I've had to do such things.
Click to expand...
Click to collapse
eventcom said:
if I'm not totally mistaken it makes a huge difference if you use custom mtd partitions. The recovery makes an image of the partitions which means on restore the same size is expected (which would also apply to your sd-ext...)
Click to expand...
Click to collapse
Hello guys,Belated Happy New Year!!!Sorry for the late response.I was out of town and didn't have a chance to check the thread until today.I had finally got it working on 29th Dec after 15 days tearing my hair out trying to fix it.
Ah,after trying a lot of things and epic struggle finally some peace and quiet.:victory:
Thank you very much "heavy_metal_man" for your continued support and kind cooperation.I couldn't have done this without your inexhaustible support.I really appreciate it.
Thank you "eventcom" for the reply.I appreciate it.Though you were a bit late but you got it right.Probably it was the MTD thing.
I am not sure what exactly happened and what did the trick in the end.In all probability it was MTD partition thing which was messing up.
Not is case of Ext partition though.Because as I have mentioned my previous ext3 was 512 MB while now I am using 1GB Ext3 partition.
So I think Restore with old MTD settings and Ext partition >/= previous Ext partition should do the job.
Steps followed:
>Unroot and S-ON
http://forum.xda-developers.com/showthread.php?p=22832599
>Root
http://forum.xda-developers.com/showthread.php?t=1145035&nocache=1&nocache=1
>Data Wipe - Factory Reset
>Wipe Cache Partition
>Format /cache
>Format /system
>Format /data
>Wipe cache partition
>Wipe Dalvik Cache
>Create text file with custom MTD partition settings you had while taking Nandroid Backup
>Go to Recovery
>Mounts and Storage
>Format /cache
>Format /system
>Format /data
>Wipe Data / Factory Reset
>Flash "recovery-v1.5.8-Beta-CustomMTD_S.zip"
>Go to Advanced
>Reboot Recovery
>Restore Nandroid Backup
>Fix permissions
>Without restarting, flash "boot-v1.5.8-Beta-CustomMTD_S.zip"
>Reboot device
After Nandroid Restore Superuser started malfunctioning.Apps (including Titanium Backup) requiring ROOT access were not getting required permissions while it was being displayed that Superuser had granted the permissions.Anyway,was able to resolve that problem somehow and now my device is working perfectly.:victory:

Modem kernel panic help

Hi, I am trying to get the latest version of CM KitKat to allow modem resets, but instead I get rebooting. Can anyone make heads or tails from the following crash? Also, it works fine in older roms, and the second output shows that it handles the reset fine without rebooting.
[ 436.254661] SMSM: Modem SMSM state changed to SMSM_RESET.
[ 436.260521] Notify: start reset
[ 436.260552] Probable fatal error on the modem.
[ 436.260552] modem subsystem failure reason: (unknown, smem_get_entry failed).
[ 436.260552] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = 1.
[ 436.260582] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
[ 436.260613] [<c0013d84>] (unwind_backtrace+0x0/0xe0) from [<c0741084>] (panic+0x88/0x1f8)
[ 436.260613] [<c0741084>] (panic+0x88/0x1f8) from [<c0050844>] (subsystem_restart_dev+0xf8/0x124)
[ 436.260643] [<c0050844>] (subsystem_restart_dev+0xf8/0x124) from [<c0051928>] (restart_modem+0xa0/0xd4)
[ 436.260674] [<c0051928>] (restart_modem+0xa0/0xd4) from [<c002ff28>] (notify_smsm_cb_clients_worker+0xa4/0x1c4)
[ 436.260674] [<c002ff28>] (notify_smsm_cb_clients_worker+0xa4/0x1c4) from [<c0086314>] (process_one_work+0x22c/0x428)
[ 436.260704] [<c0086314>] (process_one_work+0x22c/0x428) from [<c00866d8>] (worker_thread+0x19c/0x2bc)
[ 436.260704] [<c00866d8>] (worker_thread+0x19c/0x2bc) from [<c008ad08>] (kthread+0x84/0x94)
[ 436.260735] [<c008ad08>] (kthread+0x84/0x94) from [<c000e9e4>] (kernel_thread_exit+0x0/0x8)
[ 436.366030] CPU0: stopping
[ 436.368777] [<c0013d84>] (unwind_backtrace+0x0/0xe0) from [<c0012e0c>] (handle_IPI+0x100/0x1cc)
[ 436.377414] [<c0012e0c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 436.386052] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000db00>] (__irq_svc+0x40/0x70)
[ 436.394384] Exception stack(0xec939e48 to 0xec939e90)
[ 436.399359] 9e40: c0c7ff38 373cff38 00205b3e 00000000 00000001 0000000f
[ 436.407569] 9e60: 00000029 00000003 c0c7ff54 00000003 c0b61970 60000113 00000000 ec939e90
[ 436.415717] 9e80: c006ec50 c006f128 60000113 ffffffff
[ 436.420723] [<c000db00>] (__irq_svc+0x40/0x70) from [<c006f128>] (vprintk+0x3a8/0x420)
[ 436.428658] [<c006f128>] (vprintk+0x3a8/0x420) from [<c074120c>] (printk+0x18/0x24)
[ 436.436319] [<c074120c>] (printk+0x18/0x24) from [<c0020e24>] (modem_notifier_test_call+0x3c/0x54)
[ 436.445200] [<c0020e24>] (modem_notifier_test_call+0x3c/0x54) from [<c0090270>] (notifier_call_chain+0x38/0x68)
[ 436.455333] [<c0090270>] (notifier_call_chain+0x38/0x68) from [<c0090304>] (__srcu_notifier_call_chain+0x40/0x58)
[ 436.465557] [<c0090304>] (__srcu_notifier_call_chain+0x40/0x58) from [<c0090330>] (srcu_notifier_call_chain+0x14/0x18)
[ 436.476239] [<c0090330>] (srcu_notifier_call_chain+0x14/0x18) from [<c0086314>] (process_one_work+0x22c/0x428)
[ 436.486220] [<c0086314>] (process_one_work+0x22c/0x428) from [<c00866d8>] (worker_thread+0x19c/0x2bc)
[ 436.495406] [<c00866d8>] (worker_thread+0x19c/0x2bc) from [<c008ad08>] (kthread+0x84/0x94)
[ 436.503677] [<c008ad08>] (kthread+0x84/0x94) from [<c000e9e4>] (kernel_thread_exit+0x0/0x8)
[ 436.612147] Rebooting in 5 seconds..
[ 441.616511] Going down for restart now
[ 441.619471] msm_restart : clear reset flag
Here is the same thing in a working rom.
<3>[ 166.851182] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 166.851396] Notify: start reset
<3>[ 166.851518] Modem SMSM state changed to SMSM_RESET.
<3>[ 166.851518] Probable err_fatal on the modem. Calling subsystem restart...
<6>[ 166.851670] subsys-restart: subsystem_restart(): Restart sequence requested for modem, restart_level = 3.
<6>[ 166.851762] subsys-restart: subsystem_restart_thread(): [d9091b00]: Shutting down modem
<3>[ 166.882038] unvote_dfab: dfab is already off
<4>[ 166.882038] [<c010eb68>] (unwind_backtrace+0x0/0x108) from [<c0122658>] (unvote_dfab+0xa4/0xcc)
<4>[ 166.882069] [<c0122658>] (unvote_dfab+0xa4/0xcc) from [<c0123318>] (bam_dmux_smsm_cb+0x134/0x748)
<4>[ 166.882069] [<c0123318>] (bam_dmux_smsm_cb+0x134/0x748) from [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254)
<4>[ 166.882099] [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254) from [<c018ed7c>] (process_one_work+0x14c/0x444)
<4>[ 166.882099] [<c018ed7c>] (process_one_work+0x14c/0x444) from [<c018f3ac>] (worker_thread+0x174/0x37c)
<4>[ 166.882130] [<c018f3ac>] (worker_thread+0x174/0x37c) from [<c0193dcc>] (kthread+0x88/0x90)
<4>[ 166.882130] [<c0193dcc>] (kthread+0x88/0x90) from [<c0108f70>] (kernel_thread_exit+0x0/0x8)
<3>[ 166.882221] release_wakelock: bam_dmux wakelock not locked
<4>[ 166.882252] [<c010eb68>] (unwind_backtrace+0x0/0x108) from [<c012090c>] (release_wakelock+0xc0/0xec)
<4>[ 166.882252] [<c012090c>] (release_wakelock+0xc0/0xec) from [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254)
<4>[ 166.882282] [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254) from [<c018ed7c>] (process_one_work+0x14c/0x444)
<4>[ 166.882282] [<c018ed7c>] (process_one_work+0x14c/0x444) from [<c018f3ac>] (worker_thread+0x174/0x37c)
<4>[ 166.882282] [<c018f3ac>] (worker_thread+0x174/0x37c) from [<c0193dcc>] (kthread+0x88/0x90)
<4>[ 166.882313] [<c0193dcc>] (kthread+0x88/0x90) from [<c0108f70>] (kernel_thread_exit+0x0/0x8)
<3>[ 166.882588] ch_notify: smd closed
<3>[ 166.882588] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882649] ch_notify: smd closed
<3>[ 166.882649] ch_notify: smd closed
<6>[ 166.882649] diag: clean modem registration
<6>[ 166.886311] subsys-restart: subsystem_restart_thread(): [d9091b00]: Powering up modem
<7>[ 166.886311] load_image: load modem_fw.mdt image
<6>[ 167.219807] pil_qdsp6v4 pil_qdsp6v4.1: brought out of reset
<7>[ 167.220479] load_image: load modem.mdt image
<6>[ 168.853898] bl_level:40,cd:2:Candela:40 aid_change:1
<6>[ 169.392156] pil_qdsp6v4 pil_qdsp6v4.2: brought out of reset
<6>[ 169.393224] subsys-restart: subsystem_restart_thread(): [d9091b00]: Restart sequence for modem completed.
<3>[ 170.125438] Notify: smsm init
<6>[ 171.607202] diag: incomplete pkt on Modem CNTL ch
<6>[ 171.632565] diag: event mask not set yet, so no update
<6>[ 172.412513] sps:REVISION of BAM 0xe5b14000 is 0x5.
<3>[ 175.133770] handle_bam_mux_cmd: dropping invalid LCID 10 reserved 0 cmd 4 pad 0 ch 10 len 0
<3>[ 175.133862] handle_bam_mux_cmd: dropping invalid LCID 11 reserved 0 cmd 4 pad 0 ch 11 len 0
<6>[ 175.473401] pm8921_enable_batt_therm: [pm8921] enable Vref_batt_therm
<6>[ 175.983122] pm8921_enable_batt_therm: [pm8921] disable Vref_batt_therm
<6>[ 175.983122] sec_bat_monitor_work: battery check is present (1 time )
<6>[ 175.984800] [battery] level(99), vcell(4346250), therm(248)
<6>[ 175.984800] [battery] cable_type(1), chg_status(1), health(1)
<6>[ 175.984800] [battery] timeout_chgstp(0), chg_enabled(1), rechg_status(0)

[Q] Native Linux on SM-P600

I have managed to install an Arch Linux system boot on my SGN 10.1 2014 edition (P600) on the external SD Card using the RECOVERY partition. I have encountered an issue though: I can't manage to get any screen output. That's why I'm calling for help here.
Let me sum up what I did and what's working first.
I flashed on my tablet Xluco's kernel (1.7, found in the thread) and installed Arch Linux on the external SD Card using Linux Deploy.
In the chroot, I got rid of systemd and replaced it by initscripts-fork (found on the AUR). That is because I could not manage to boot using systemd. I also tried openrc without success.
I copied the mfc firmware from android's system partition. I then configured some wireless connection with netcfg and enabled sshd.
I built Xluco's kernel 1.7 with a few tweaks: enabled virtual terminal and fbcon (as a module), changed the CMDLINE to be able to boot. I copied all that in my chrooted linux and mkinitcpio built an initial ramdisk for me. A finally packed all that in some flashable image for my recovery partition using abootimg.
I dd'd my image to the RECOVERY and rebooted.
So. It boots (after quite a long Samsung Galaxy Note screen, seems to be linked with enabling VT), I can log in through ssh. The problem is, I can't get the screen to work. Calling "modprobe fbcon" gives me
Code:
modprobe: ERROR: could not insert 'fbcon': Invalid argument
but nothing new in dmesg.
I also tried to configure an X server using fbdev as a video driver. The screen blinks as a call startx, but nothing more. It speaks a lot in dmesg though
Code:
# dmesg | grep fb
[ 1299.916361] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 1
[ 1299.916372] s3c-fb exynos5-fb.1: pm_relax
[ 1300.224278] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1300.224283] s3c-fb exynos5-fb.1: ready to suspend!
[ 1300.224327] s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 1301.288983] s3c-fb exynos5-fb.1: s3c_fb_pan_display::output_on is FALSE
[ 1301.290184] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.290249] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.290255] s3c-fb exynos5-fb.1: ready to suspend!
.
.
.
[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!
[ 1302.254599] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 0
[ 1302.255261] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1302.256138] s3c-fb exynos5-fb.1: pm_stay_awake
[ 1302.256146] s3c-fb exynos5-fb.1: mali level : 0
[ 1302.256243] s3c-fb exynos5-fb.1: - s3c_fb_blank
The dots symbolize a few hundreds occurences of the three lines
Code:
[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!
My guess is, there should be nothing like "s3c_fb_pan_display:utput_on is FALSE" in here...
Does anyone have any idea or suggestion to solve that problem? Or to get a better diagnosis at least?
Has someone managed to have it working?
EDIT:
I've tested to use the framebuffer through some low-level tools. Using
Code:
fbi -d /dev/fb0 -T 1 -a picture.jpg
drew the nice picture on my screen. No output in the log files though.

Okay, I've investigated a bit. Looking at dmesg right after android's boot (the dmesg gets flooded by thermal stuff if you wait), I found that the s3c-fb driver start sequence begins with
Code:
[ 5.507243] B3 2007 s3c-fb exynos5-fb.1: + s3c_fb_blank mode 0
[ 5.507339] B3 2007 s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 5.779631] B2 1233 s3c-fb exynos5-fb.1: s3c_fb_psr_enter +
[ 5.791298] B2 1233 s3c-fb exynos5-fb.1: s3c_fb_psr_enter -
[ 5.870133] B3 2007 s3c-fb exynos5-fb.1: s3c_fb_psr_exit +
[ 5.905940] B3 2007 s3c-fb exynos5-fb.1: s3c_fb_psr_exit -
while linux's begins with
Code:
[ 1176.701586] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 1
[ 1176.701598] s3c-fb exynos5-fb.1: pm_relax
[ 1177.008097] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1177.008102] s3c-fb exynos5-fb.1: ready to suspend!
[ 1177.008146] s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 1178.076551] s3c-fb exynos5-fb.1: s3c_fb_pan_display::output_on is FALSE
Looking in s3c-fb source file, s3c_fb_blank mode 0 corresponds to displaying something while s3c_fb_blank mode 1 is, well, blanking the screen.
Stupidely forcing mode 0 in the driver's code, I got a fully functional X display. The question is now: why is xf86-video-fbdev calling for a blank screen? Is it a misunderstanding with the driver?
I'll post any development here, hopefully soon.

Awesome, doing something similar on my Tab S and this solved it! Thanks.
I think this is also applicable on any 2014+ Sammy flagship devices Exynos variant since GS4 and below (panning instead of blanking) :thumbsup:
EDIT:Would you mind sharing the modifications you have done to source? huge cpu drain with my method, messed up loop maybe. Thanks

Any chance you'd post your "rom" so I could give it a go?

Does anybody have any advice on how to get this going again? I'm kinda stumped..

Develop Bugs

welcome