Hack your S3 Mini with the serial port - Galaxy S III Mini Android Development

Hey there,
Walking in the great footsteps of Rebellos and Adam, I tried the USB serial port hack on the S3 Mini, with great success.
You need:
- one USB to 3.3 UART converter, I use http://dx.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872 but https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/ looks good too (just make sure it's 3.3V and NOT 5V I/O!)
- a few single row male 2.54mm headers, like https://www.sparkfun.com/products/116
- one microUSB breakout board that provides the ID pin: https://www.sparkfun.com/products/10031
- a soldering iron (and solder wire of course
- a resistor of value 619K (I guess Factory Mode Boot ON-UART?), although a close value will work - mine is 620K made from 470K+150K
On the picture below you can see the whole thing after soldering. Simply solder the resistor between ID and GND. Do not connect VCC, it is not necessary and could even be dangerous!
Now you can see the whole boot output and interact with the second stage bootloader, which is called S-Boot in the paste below. Be careful with the commands, in particular anything that could alter the MMC contents like emmc_write or loadpart!
Code:
AST_POWERON
Xloader version:
Built: Wed Oct 24 11:40:50 PM 2012
Configured for: 8500 B0
Running on chip ID: 8500B2
SECURITY_Init
Boot scenario: NORMAL
USB - Enabled: 0x1 Enum done: 0x0
Last reset reason: POWER_ON_RESET
XP70_DATA_MBFFC: 0xFF000001
PWR_MNGT_STARTED 1
Probing for eMMC on SDI2
About to load MEMINIT
After MEMINIT loaded
verify_signedheader
verify_signedheader done
verify_payload hdr size: 0xD0 payload 0x40026244
About to exec MEMINIT function
SoC settings: INFO: @(#)SOC-SETTINGS v1.0.3 Vape100+50mV Vape50+25mV db8520 1000Mhz Oct 24 2012 23:40:53
SoC settings: INFO: Vbat check 0x0000032c
SoC settings: INFO: AB8505 V2 detected
SoC settings: INFO: Vendor ID = 0x00000001, CS0 density = 0x00000018, CS1 density = 0x00000018
SoC settings: INFO: CS0 revision ID1 = 0x00000001, CS0 revision ID2 = 0x00000000
SoC settings: INFO: CS1 revision ID1 = 0x00000001, CS1 revision ID2 = 0x00000000
SoC settings: INFO: AVS Enable, FVR21 value = : 0x8717024b, FVR22 value = : 0x0023ddf2
SoC settings: INFO: Memory size=0x40000000 (1024 MB), CS0 (512 MB) CS1 (512 MB)
SoC settings: INFO: DDR Test Ended successfully.
SoC settings: INFO: Requesting MAX OPP from PRCMU
SoC settings: INFO: Set MAX OPP OK
SoC settings: INFO: vmin = above 1.35V, vbbp = +200mV, vbbn = +200mV
SoC settings: INFO: Slow Parts [>......](Slow for N Transistor, Slow for P transistor)
MEMINIT passed OK
About to load NORMAL
After NORMAL loaded
verify_signedheader
verify_signedheader done
verify_payload hdr size: 0xD0 payload 0x141080D0
XL_DisableCachesMmu
Before ENABLE_L2CC
After ENABLE_L2CC
Before call normal
[ 0.0000] init_microusb_pmic: Turn on reason 0xc0
[ 0.0000] init_microusb_pmic: Turning on due to cable plug? 1
[ 0.0049] init_ab8500_gpadc: ADC_INPUT_BTEMP.gain : 1336
[ 0.0102] init_ab8500_gpadc: ADC_INPUT_BTEMP.offset : 1408
[ 0.0158] hwCableType: USB Link1 status 0x1a
[ 0.0200] hwCableType: is 0
[ 0.0228] pmic_get_attached_device: USB VBUS status 0x00
[ 0.0303] ab8500_read_adc: waiting for gpadc conversion...
[ 0.0436] ab8500_read_adc: gpadc conversion is completed
[ 0.0437] abx500_adc_to_voltage channel=14, ad_value=466
[ 0.0485] pmic_get_attached_device: USB-ID first read with 1uA PU : 623
[ 0.0552] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 0.0610] read_fm_comparator: in
[ 0.0943] read_fm_comparator: FMCOMP-ID 32
[ 0.0944] read_fm_comparator: Matchd 0x202
[ 0.0970] pmic_get_attached_device: is 0x202
[ 0.1011] [hw_board] dram_init(822): dram_init
[ 0.1055] [hw_board] dram_init(843): dram_init cs0 size 536870912 cs1 size 536870912
[ 0.1133] [hw_board] dram_init(855): Ram_Info.total_size = 1024MB
[ 0.1398] Samsung S-Boot 4.0
[ 0.1398] Copyright (C) 2012 System S/W Group. Samsung Electronics Co., Ltd.
[ 0.1442] Board: GOLDEN ID 262 / built on SEP-110 on Oct 24 2012 23:35:17
[ 0.1512] CPU: DB8500 (ID=0x9001dbf4)
[ 0.1550] [main] init_param_status(348):
[ 0.1590] [main] Re_partition(225): booting code=0x80c000c0
[ 0.1907] [hsmmc_init] MMC card is detected
[ 0.1920] Product Name : SEM08G
[ 0.1924] CID:45010053 454d3038 47907258 9dc2bf0c
[ 0.2010] <display_card_info:1144> ext_csd
[ 0.2339] Total Card Size: 7456 MByte
[ 0.2339] Total Sector Count: 15269888
[ 0.2474]
MoviNand Initialization Complete!
[ 0.2474] checking whether toc is redirected
[ 0.2725] [pit] pit_update_partition(273): Board partition updated.
[ 0.2839] [gpt] check_protective_mbr(230): read protective mbr
[ 0.2841] [main] loke_init(255): j4fs_open..
[ 0.8501] [main] loke_init(257): success
[ 0.9594] [param_block] load_lfs_parameters(375): valid magic code and version.
[ 0.9610] [main] loke_init(265): Board id 262
[ 0.9762] [ddi] init_ddi_data(74): usable ddi data.
[ 0.9764] ab8500_read_adc: waiting for gpadc conversion...
[ 0.9909] ab8500_read_adc: gpadc conversion is completed
[ 0.9910] abx500_adc_to_voltage channel=8, ad_value=804
[ 0.9958] [FG] VCELL ADC = 804, VOLTAGE = 4276mV
[ 1.0004] musb_init : GOLDEN : High-Speed USB OTG Controller
[ 1.0065] hwCableType: USB Link1 status 0x1a
[ 1.0104] hwCableType: is 0
[ 1.0132] pmic_get_attached_device: USB VBUS status 0x00
[ 1.0207] ab8500_read_adc: waiting for gpadc conversion...
[ 1.0340] ab8500_read_adc: gpadc conversion is completed
[ 1.0341] abx500_adc_to_voltage channel=14, ad_value=490
[ 1.0389] pmic_get_attached_device: USB-ID first read with 1uA PU : 656
[ 1.0456] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.0514] read_fm_comparator: in
[ 1.0847] read_fm_comparator: FMCOMP-ID 32
[ 1.0848] read_fm_comparator: Matchd 0x202
[ 1.0874] pmic_get_attached_device: is 0x202
[ 1.0915] [CHG] cable type:0x202, status:0x0
[ 1.0958] [CHG] Skip to initialize charger
[ 1.0999] [CHG] OVP REG SETTING : 0x44
[ 1.1144] reading nps status file is successfully!.
[ 1.1145] nps status=0x504d4f43
[ 1.1171] hwCableType: USB Link1 status 0x1a
[ 1.1210] hwCableType: is 0
[ 1.1238] pmic_get_attached_device: USB VBUS status 0x00
[ 1.1314] ab8500_read_adc: waiting for gpadc conversion...
[ 1.1446] ab8500_read_adc: gpadc conversion is completed
[ 1.1447] abx500_adc_to_voltage channel=14, ad_value=488
[ 1.1496] pmic_get_attached_device: USB-ID first read with 1uA PU : 653
[ 1.1562] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.1621] read_fm_comparator: in
[ 1.1954] read_fm_comparator: FMCOMP-ID 32
[ 1.1954] read_fm_comparator: Matchd 0x202
[ 1.1981] pmic_get_attached_device: is 0x202
[ 1.2022] [hw_board] board_process_platform(1035): check_power_key
[ 1.2084] check_power_key: Powered on by 0x11 !! Booting .....
[ 1.2643] [read_switch_off_status] SwitchOff_Status 0x40
[ 1.2643] [hw_board] check_reboot(948): reset_state: 0x 0
[ 1.2696] [hw_board] check_reboot(957): softreset_state: 0x 0
[ 1.2755] [read_turnon_state] TurnOn_Status 0x0
[ 1.2801] [hw_board] check_reboot(960): turnon_state: 0x 0
[ 1.2859] hwCableType: USB Link1 status 0x1a
[ 1.2900] hwCableType: is 0
[ 1.2928] pmic_get_attached_device: USB VBUS status 0x00
[ 1.3003] ab8500_read_adc: waiting for gpadc conversion...
[ 1.3136] ab8500_read_adc: gpadc conversion is completed
[ 1.3137] abx500_adc_to_voltage channel=14, ad_value=489
[ 1.3185] pmic_get_attached_device: USB-ID first read with 1uA PU : 654
[ 1.3252] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.3310] read_fm_comparator: in
[ 1.3643] read_fm_comparator: FMCOMP-ID 32
[ 1.3643] read_fm_comparator: Matchd 0x202
[ 1.3670] pmic_get_attached_device: is 0x202
[ 1.3712] hwCableType: USB Link1 status 0x1a
[ 1.3754] hwCableType: is 0
[ 1.3782] pmic_get_attached_device: USB VBUS status 0x00
[ 1.3857] ab8500_read_adc: waiting for gpadc conversion...
[ 1.3989] ab8500_read_adc: gpadc conversion is completed
[ 1.3991] abx500_adc_to_voltage channel=14, ad_value=488
[ 1.4039] pmic_get_attached_device: USB-ID first read with 1uA PU : 653
[ 1.4105] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.4164] read_fm_comparator: in
[ 1.4497] read_fm_comparator: FMCOMP-ID 32
[ 1.4497] read_fm_comparator: Matchd 0x202
[ 1.4524] pmic_get_attached_device: is 0x202
[ 1.4565] hwCableType: USB Link1 status 0x1a
[ 1.4607] hwCableType: is 0
[ 1.4635] pmic_get_attached_device: USB VBUS status 0x00
[ 1.4711] ab8500_read_adc: waiting for gpadc conversion...
[ 1.4843] ab8500_read_adc: gpadc conversion is completed
[ 1.4844] abx500_adc_to_voltage channel=14, ad_value=488
[ 1.4893] pmic_get_attached_device: USB-ID first read with 1uA PU : 653
[ 1.4959] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.5018] read_fm_comparator: in
[ 1.5351] read_fm_comparator: FMCOMP-ID 32
[ 1.5351] read_fm_comparator: Matchd 0x202
[ 1.5378] pmic_get_attached_device: is 0x202
[ 1.5419] hw_pm_status: chg_status = 0 reboot_reason = 0x0
[ 1.5473] [FG] __BATT_CAPACITY :0xffffffff
[ 1.5514] [hw_board] board_process_platform(1115): booting_mode: 0x0
[ 1.5578] hwCableType: USB Link1 status 0x1a
[ 1.5620] hwCableType: is 0
[ 1.5648] pmic_get_attached_device: USB VBUS status 0x00
[ 1.5724] ab8500_read_adc: waiting for gpadc conversion...
[ 1.5856] ab8500_read_adc: gpadc conversion is completed
[ 1.5857] abx500_adc_to_voltage channel=14, ad_value=488
[ 1.5906] pmic_get_attached_device: USB-ID first read with 1uA PU : 653
[ 1.5972] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.6031] read_fm_comparator: in
[ 1.6364] read_fm_comparator: FMCOMP-ID 32
[ 1.6364] read_fm_comparator: Matchd 0x202
[ 1.6390] pmic_get_attached_device: is 0x202
[ 1.6432] hwCableType: USB Link1 status 0x1a
[ 1.6474] hwCableType: is 0
[ 1.6502] pmic_get_attached_device: USB VBUS status 0x00
[ 1.6577] ab8500_read_adc: waiting for gpadc conversion...
[ 1.6710] ab8500_read_adc: gpadc conversion is completed
[ 1.6711] abx500_adc_to_voltage channel=14, ad_value=489
[ 1.6759] pmic_get_attached_device: USB-ID first read with 1uA PU : 654
[ 1.6826] pmic_get_attached_device: go into FM_COMPARATOR Call
[ 1.6884] read_fm_comparator: in
[ 1.7217] read_fm_comparator: FMCOMP-ID 32
[ 1.7218] read_fm_comparator: Matchd 0x202
[ 1.7244] pmic_get_attached_device: is 0x202
[ 1.9400] Probe HW
[ 1.9562] MCDE HW revision 0x03000800
[ 1.9562] db8500 V2 HW
[ 1.9566] mcde_probe: EXIT 0
[ 1.9594] dsilink_init: Probing dsilink device[0]
[ 1.9641] dsio[0]: 0xa0351000
[ 1.9671] hw revision 0x02327457
[ 1.9703] nova_dsilink_v2_init: initiated
[ 1.9743] dsilink_init: Probing dsilink device[1]
[ 1.9790] dsio[1]: 0xa0352000
[ 1.9819] hw revision 0x02327457
[ 1.9851] nova_dsilink_v2_init: initiated
[ 1.9891] dsilink_init: Probing dsilink device[2]
[ 1.9938] dsio[2]: 0xa0353000
[ 1.9968] hw revision 0x02327457
[ 2.0000] nova_dsilink_v2_init: initiated
[ 2.0040] s6e63m0_dsi_probe function entered
[ 2.0083] mcde_ovly_apply: ovly->dirty or ovly->dirty_buf!
[ 2.0137] mcde_ovly_apply: ovly->dirty or ovly->dirty_buf!
[ 2.0192] s6e63m0_dsi_set_power_mode: power_mode = 2
[ 2.1042] clk_set_rate: f=349440000
[ 2.1042] nova_dsilink_enable link enabled
[ 2.1061] s6e63m0_dsi_read_panel_id: Read device id of the display
[ 2.1128] Panel is AMS397GE MIPI (SM2)
[ 2.1160] ELVSS setting to 16
[ 2.2390] ovly0 pfwml:48 32bpp
[ 2.2390] Overlay updated, chnl=0
[ 2.2597] Overlay updated, chnl=0
[ 2.2797] s6e63m0_dsi_set_power_mode: power_mode = 2
[ 2.2798] Autoboot (0 seconds) in progress, press any key to stop Autoboot aborted..
[ 2.2869] SBL>
SBL>
SBL>
SBL>
SBL> help
Following commands are supported:
[ 6.6002] * log
[ 6.6002] * crc
[ 6.6012] * loadmodem
[ 6.6035] * readdefaultparam
[ 6.6063] * readchmod
[ 6.6086] * chmod
[ 6.6105] * printenv
[ 6.6127] * saveenv
[ 6.6148] * setenv
[ 6.6168] * help
[ 6.6186] * kernel
[ 6.6206] * boot
[ 6.6224] * reset
[ 6.6243] * sud
[ 6.6261] * rewritegpt
[ 6.6284] * loadpart
[ 6.6306] * showparts
[ 6.6328] * showsums
[ 6.6350] * loadkernel
[ 6.6374] * down
[ 6.6392] * upload
[ 6.6412] * emmc
[ 6.6430] * emmc_write
[ 6.6454] * readadc
[ 6.6474] * keyread
[ 6.6495] * mmctest
[ 6.6516] * fuelgauge
[ 6.6539] * earjack
[ 6.6560] * powerkey
[ 6.6581] * tk
[ 6.6598] * usb_write
[ 6.6620] * usb_read
[ 6.6642] To get commands help, Type "help <command>"
[ 6.6692] SBL>

Well amusingly the same serial port, after booting, provides an AT interface to the modem. Not especially useful but it's worth noting.
Code:
[ 6.2988] [checksum] movinand_checksum(564): Checksum Done 0x31, Checksum Pass 0x31, emmc_checksum 3
[ 6.3082]
Starting kernel at 0x100000...
Uncompressing Linux... done, booting the kernel.
+READY
+UART READY
AST_POWERON
AST_POWERON
BOOTING COMPLETED
AT
OK
AT+CGMI
"ST-Ericsson"
OK

Nice, great discovery.
Could you please provide the output of help for all commands of the SBL?

neldar said:
Nice, great discovery.
Could you please provide the output of help for all commands of the SBL?
Click to expand...
Click to collapse
Code:
[ 4.4549] SBL> help log
* Help : log
* Usage : print log
[ 7.0767] SBL> help crc
* Help : crc
* Usage : crc <crc> <addr> <len>
[ 10.5443] SBL> help loadmodem
* Help : loadmodem
* Usage : load modem binary
[ 14.0840] SBL> help readdefaultparam
* Help : readdefaultparam
* Usage : read make_default_param file
[ 20.4348] SBL> help readchmod
* Help : readchmod
* Usage : read chmod field file.
[ 30.0080] SBL> help printenv
* Help : printenv
* Usage : printenv
Print current environment info on ram
[ 38.1508] SBL> help saveenv
* Help : saveenv
* Usage : saveenv
Save current environment info to flash
[ 44.5253] SBL> help help
* Help : help
* Usage : help [command]
[ 48.5201] SBL> help kernel
* Help : kernel
* Usage : kernel hex_adr
Change the Linux kernel base
[ 50.0267] SBL> help boot
* Help : boot
* Usage : boot [kernel options]
Boot Linux with optional kernel options
[ 54.2885] SBL> help reset
* Help : reset
* Usage : reboot
Reboot system
[ 55.6315] SBL> help sud
* Help : sud
* Usage : sud command
[ 60.1163] SBL> help rewritegpt
* Help : rewritegpt
* Usage : force GPT re-write/update
[ 66.0025] SBL> help loadpart
* Help : loadpart
* Usage : load partition from storage device.
[ 71.6166] SBL> help showparts
* Help : showparts
* Usage : show partitions
[ 76.7497] SBL> help showsums
* Help : showsums
* Usage : show MD5 checksum data
[ 81.3946] SBL> help loadkernel
* Help : loadkernel
* Usage : load kernel from storage device.
[ 86.0555] SBL> help down
* Help : down
* Usage : usage: down
[ 89.8595] SBL> help upload
* Help : upload
* Usage : upload
[ 95.4013] SBL> help emmc
* Help : emmc
* Usage : emmc <addr>
[ 99.4376] SBL> help emmc_write
* Help : emmc_write
* Usage : emmc_write <sector addr> <No. sectors>
[ 101.7046] SBL> help readadc
* Help : readadc
* Usage : *Usage : readadc <channel>
[ 109.6482] SBL> help keyread
* Help : keyread
* Usage : *Usage : keyread
[ 115.3824] SBL> help mmctest
* Help : mmctest
* Usage : mmctest <addr> <start block> <number of blocks>
[ 130.4013] SBL> help fuelgauge
* Help : fuelgauge
* Usage : *usage : fuelgauge
[ 136.0039] SBL> help earjack
* Help : earjack
* Usage : *Usage : Earjack status read
[ 141.1214] SBL> help powerkey
* Help : powerkey
* Usage : *Usage : Power key read
[ 146.2470] SBL> help tk
* Help : tk
* Usage : *Usage :Test Power key read
[ 148.5054] SBL> help usb_write
* Help : usb_write
* Usage : usb_write reg, val
Read the usb ic register
[ 153.5596] SBL> help usb_read
* Help : usb_read
* Usage : usb_read reg
Read the usb ic register
And here's the output from the commands that should be safe:
Code:
SBL> printenv
[param_block] print_param(328): PARAM Rev 1.3
[429251.9210] [param_block] print_param(332): [0]SERIAL_SPEED : 7
[429251.9255] [param_block] print_param(332): [1]LOAD_TESTKERNEL : 0
[429251.9317] [param_block] print_param(332): [2]BOOT_DELAY : 0
[429251.9374] [param_block] print_param(332): [3]LCD_LEVEL : 97
[429251.9431] [param_block] print_param(332): [4]SWITCH_SEL : 1
[429251.9489] [param_block] print_param(332): [5]PHONE_DEBUG_ON : 0
[429251.9549] [param_block] print_param(332): [6]LCD_DIM_LEVEL : 0
[429251.9609] [param_block] print_param(332): [7]LCD_DIM_TIME : 6
[429251.9668] [param_block] print_param(332): [8]FORCE_PRERECOVERY : 0
[429251.9732] [param_block] print_param(332): [9]REBOOT_MODE : 0
[429251.9790] [param_block] print_param(332): [10]NATION_SEL : 0
[429251.9848] [param_block] print_param(332): [11]DEBUG_LEVEL : 2
[429251.9907] [param_block] print_param(332): [12]SET_DEFAULT_PARAM : 0
[429251.9972] [param_block] print_param(332): [13]BATT_CAPACITY : 1391219840
[429252.0040] [param_block] print_param(332): [14]LOAD_KERNEL2 : 0
[429252.0100] [param_block] print_param(332): [15]FLASH_LOCK_STATUS : 1
[429252.0164] [param_block] print_param(332): [16]PARAM_INT_14 : 0
[429252.0224] [param_block] print_param(336): [0]VERSION : goldenXXLXXX
[429252.0289] [param_block] print_param(336): [1]CMDLINE : cachepolicy=writealloc mpcore_wdt.mpcore_margin=359 root=/dev/ram0 rw rootwait crash_reboot=yes crash_dump=no init=init console='null'
[429252.0460] [param_block] print_param(336): [2]DELTA_LOCATION : /mnt/rsv
[429252.0527] [param_block] print_param(336): [3]CMDLINE_MODE : product
[429252.0591] [param_block] print_param(336): [4]PARAM_STR_4 :
Code:
SBL> showsums
[checksum] OpenChecksum(212): Allocate and store data of checksum header
[429270.5366] [checksum] OpenChecksum(224): Read checksum header
[429270.5367] [checksum] OpenChecksum(237): NeedChecksum=0
[429270.5420] [checksum] PrintChecksumHeader(136): +
[429270.5467] ============== Checksum Header ==============
[429270.5520] NeedChecksum : 0
[429270.5548] ---------------------------------------------
[429270.5601] [MBR,GPT] [ID: 1][index: 0]File System: , Image Size: 0, Status: Checksum: None
[429270.5690] [MasterTOC] [ID: 2][index: 1]File System: , Image Size: 0, Status: Checksum: None
[429270.5780] [PIT] [ID: 70][index: 2]File System: , Image Size: 1325376774, Status: Checksum: None
[429270.5873] [MD5HDR] [ID: 71][index: 3]File System:
�, Image Size: 0, Status: Checksum: None
[429270.5964] [STEboot1] [ID: 3][index: 4]File System: , Image Size: 28, Status: Checksum: None
[429270.6055] [STEboot2] [ID: 4][index: 5]File System: `S�p, Image Size: 0, Status: Checksum: ????????????????????????????????
[Dnt] [ID: 5][index: 6]File System: , Image Size: 0, Status: Checksum: None
[429270.6243] [reserved] [ID: 6][index: 7]File System: , Image Size: 1358257666, Status: Checksum: None
[429270.6341] [CSPSAFS] [ID: 7][index: 8]File System: , Image Size: 0, Status: Checksum: ????????????????????????????????
[CSPSAFS2] [ID: 8][index: 9]File System: , Image Size: 0, Status: Checksum: None
[429270.6529] [EFS] [ID: 9][index:10]File System: , Image Size: 0, Status: Checksum: ????????????????????????????????
[ModemFS] [ID: 10][index:11]File System: , Image Size: 0, Status: Checksum: None
[429270.6713] [ModemFS2] [ID: 11][index:12]File System: , Image Size: 33188, Status: Checksum: None
[429270.6806] [Fota] [ID: 12][index:13]File System: ^�P��N^�P, Image Size: 0, Status: Checksum: ????????????????????????????????
[IPL Modem] [ID: 13][index:14]File System: , Image Size: 0, Status: Checksum: None
[429270.7004] [Modem] [ID: 14][index:15]File System: , Image Size: 1325376774, Status: Checksum: None
[429270.7099] [Loke4] [ID: 15][index:16]File System: , Image Size: 0, Status: Checksum: None
[429270.7186] [2ndLoke4] [ID: 16][index:17]File System: , Image Size: 0, Status: Checksum: None
[429270.7275] [PARAM] [ID: 17][index:18]File System: , Image Size: 524416, Status: Checksum: None
[429270.7367] [Kernel] [ID: 18][index:19]File System:
�, Image Size: 0, Status: ], Checksum: None
[429270.7460] [Kernel2] [ID: 19][index:20]File System: , Image Size: 28, Status: ], Checksum: None
[429270.7551] [SYSTEM] [ID: 20][index:21]File System: , Image Size: 0, Status: ], Checksum: ????????????????????????????????
[CACHEFS] [ID: 21][index:22]File System: , Image Size: 0, Status: Checksum: None
[429270.7739] [HIDDEN] [ID: 22][index:23]File System: , Image Size: 1325376774, Status: Checksum: None
[429270.7835] [DATAFS] [ID: 23][index:24]File System: , Image Size: 0, Status: Checksum: ????????????????????????????????
============================================
Code:
SBL> showparts
===== PARTITION INFORMATION =====
[429290.4495] ID: MBR,GPT ( 1) DEVICE: MMC FIRST UNIT: 0 NO. UNITS: 256 USED UNITS: 0
[429290.4547] ID: MasterTOC ( 2) DEVICE: MMC FIRST UNIT: 256 NO. UNITS: 768 USED UNITS: 0
[429290.4627] ID: PIT (70) DEVICE: MMC FIRST UNIT: 1024 NO. UNITS: 2048 USED UNITS: 0
[429290.4703] ID: MD5HDR (71) DEVICE: MMC FIRST UNIT: 6144 NO. UNITS: 2048 USED UNITS: 0
[429290.4782] ID: STEboot1 ( 3) DEVICE: MMC FIRST UNIT: 8192 NO. UNITS: 1024 USED UNITS: 0
[429290.4863] ID: STEboot2 ( 4) DEVICE: MMC FIRST UNIT: 9216 NO. UNITS: 1024 USED UNITS: 0
[429290.4944] ID: Dnt ( 5) DEVICE: MMC FIRST UNIT: 10240 NO. UNITS: 1024 USED UNITS: 0
[429290.5021] ID: reserved ( 6) DEVICE: MMC FIRST UNIT: 11264 NO. UNITS: 1024 USED UNITS: 0
[429290.5103] ID: CSPSAFS ( 7) DEVICE: MMC FIRST UNIT: 16384 NO. UNITS: 2048 USED UNITS: 0
[429290.5184] ID: CSPSAFS2 ( 8) DEVICE: MMC FIRST UNIT: 18432 NO. UNITS: 2048 USED UNITS: 0
[429290.5266] ID: EFS ( 9) DEVICE: MMC FIRST UNIT: 20480 NO. UNITS: 32768 USED UNITS: 0
[429290.5344] ID: ModemFS (10) DEVICE: MMC FIRST UNIT: 53248 NO. UNITS: 32768 USED UNITS: 0
[429290.5425] ID: ModemFS2 (11) DEVICE: MMC FIRST UNIT: 86016 NO. UNITS: 32768 USED UNITS: 0
[429290.5508] ID: Fota (12) DEVICE: MMC FIRST UNIT: 118784 NO. UNITS: 102400 USED UNITS: 0
[429290.5589] ID: IPL Modem (13) DEVICE: MMC FIRST UNIT: 380928 NO. UNITS: 128 USED UNITS: 0
[429290.5671] ID: Modem (14) DEVICE: MMC FIRST UNIT: 385024 NO. UNITS: 28672 USED UNITS: 0
[429290.5752] ID: Loke4 (15) DEVICE: MMC FIRST UNIT: 417792 NO. UNITS: 4096 USED UNITS: 0
[429290.5832] ID: 2ndLoke4 (16) DEVICE: MMC FIRST UNIT: 421888 NO. UNITS: 4096 USED UNITS: 0
[429290.5915] ID: PARAM (17) DEVICE: MMC FIRST UNIT: 425984 NO. UNITS: 32768 USED UNITS: 0
[429290.5995] ID: Kernel (18) DEVICE: MMC FIRST UNIT: 458752 NO. UNITS: 32768 USED UNITS: 0
[429290.6077] ID: Kernel2 (19) DEVICE: MMC FIRST UNIT: 491520 NO. UNITS: 32768 USED UNITS: 0
[429290.6160] ID: SYSTEM (20) DEVICE: MMC FIRST UNIT: 524288 NO. UNITS: 2457600 USED UNITS: 0
[429290.6243] ID: CACHEFS (21) DEVICE: MMC FIRST UNIT: 2981888 NO. UNITS: 1720320 USED UNITS: 0
[429290.6328] ID: HIDDEN (22) DEVICE: MMC FIRST UNIT: 4702208 NO. UNITS: 655360 USED UNITS: 0
[429290.6412] ID: DATAFS (23) DEVICE: MMC FIRST UNIT: 5357568 NO. UNITS: 9891840 USED UNITS: 0
Note that with the crc command, you can in theory bruteforce the contents of the memory.

Nice work!
Would be very useful if you would want to port newer versions of linux Kernel later on. Had done it on my i9003.
Just a FYI for others trying this, different resistors give different output,470K+150K used by xd.bx would be ideal.
Thumbs up anyways!

Precise connexions?
Hi guys,
I'm working on a way to unbrick fully bricked I9070 (Galaxy S Advance) and I8190 (SIII mini) (based on U8500 chip).
This is possible because full sources have been disclosed begining of 2014 (sources contain everything including IBL, SBL, etc... + certificates to sign them).
Study of the service manual containing main components wiring + various docs (mainly from source distib. + Calao systems) shown that there is no such OM pins to play with to boot from USB.
You just need the right tools to assemble and sign the bootloader components (xloader, ISSW etc...) and the right tool to talk with the phone : the sources contains all this ("ready to compile"... after a lot of work)
-> I've reached the point where I'm able to compile everything and manage to talk with the, so called, dead phone, but up to now not able to have it boot the bootloader I've setup.
So I need UART debug working to figure out what's wrong.
I've not been able to setup my debug USB/UART cable, I see you have: could you post more detailed explanations?
My USB/UART debug cable seems to be working (it's based on Prolific chip): connecting it's RX and TX together (alone), I get the charaters I type on my terminal echoed on screen.
I have made a breakout micro USB out of an "opened" micro usb cable on which I soldered a wire on pin 5 (pinout checked with a multimeter)
This cable should be OK because it boots my working SIII mini when I put 301k Ohm between pins 4 and 5.
So the issue might be connecting all together
I've paied attention to cross RX and TX from mobile and cable, but no dice: i see nothing on my terminal when booting the phone.
Note: I've based the identification of RX and TX on the mobile side on the spec sheet of the chip inside the phone (TSU6111). DM_CON (USB port) is connected to TxD on the processor when the right resistor is detected (and DP_CON to RxD).
So could you detail how to connect both parts together? Do I have to connect just the RX and TX? What about grounds? On my cable I have 2 unconnected grounds: one connected to the shield of the wire and one on a green wire (traced back to Prolific ground).
Thanks a lot in advance for your support!

Hi flentus,
I don't think you can do it with a micro-USB cable, you need the beakout board from Sparkfun.
The reason is, the cable most likely does not contain a wire for the ID, which is absolutely necessary otherwise the USB port won't switch to uart.
Wrt the prolific cable, it should be fine as long as it's 3.3v. Do NOT use a usb-rs232 cable! The high voltage will fry your phone's USB port.

xd.bx said:
Hi flentus,
I don't think you can do it with a micro-USB cable, you need the beakout board from Sparkfun.
The reason is, the cable most likely does not contain a wire for the ID, which is absolutely necessary otherwise the USB port won't switch to uart.
Wrt the prolific cable, it should be fine as long as it's 3.3v. Do NOT use a usb-rs232 cable! The high voltage will fry your phone's USB port.
Click to expand...
Click to collapse
Hi xd.bx!
Thanks for your reply.
The cable I have opened has all the 5 pins: one was not wired, I soldered a wire on it and checked the continuity on pin 4 (ID) with a multimeter: it's good. If I put a 301kOhm resistor between pins 4 and 5 and plug the modified wire in my working GSIII mini (without connecting the other end of the cable to anything), it boots in recovery mode which is what is expected. This validates my ID pins wiring.
My Prolific cable is a 3.3V (it's a data cable coming from an "old school" phone). I had to put it appart to identify which wire was connected to what. There is a Prolific chip in it (and no voltage amplifier as there usualy has on RS232 similar cables), so I looked for the reference guide of the chip, which I found. Then I traced back the wires to the chip connexions using my multimeter.
So I managed to identify the RxD and TxD wires (+ the other ones -RTS etc...- I don't care about) and validated this by connecting these 2 wires together, opening a terminal on the corresponding COM port and seeing the typed characters on the terminal. Any mistake on this would have shown nothing (or garbage).
So, as I said, both parts of my setup seem pretty well validated.
But when I put everything together, it doesn't seem to work (no output on my terminal), so I must be wrong somewhere...
From the source code, I'm almost sure the UART setup is the classical 115200 bauds, no parity, 1 bit stop, 8 data bits
(from xloader_pl011.c :
#define BAUDRATE BR115200BAUD
#define PARITYBIT NOPARITY_BIT
#define STOPBITS ONE_STOPBIT
#define DATABITS DATABITS_8
)
Which connexions have you made on your breakout board?
- you have the 620kOhm resistor between pin 4 and 5
- the USB/UART cable RxD connected to the D- pin (= µUSB pin 2) of the breakout board. This is connected internally via the switch matrix to the TxD of UART2 of the processor according to TSU6111.pdf reference doc + I9070 light schematics.
- and USB/UART cable TxD connected to the D+ pin (=µUSB pin 3) of the breakout board (leading to proc UART2 RxD)
What about the grounds? Do you have any connected? If yes, which ones?
On my Prolific cable, I have 2 grounds: 1 connected to the Prolific chip ground and one connected to the USB cable shield. They are *not* connected together.
If I remember well, I tried this setup: ground of the Prolific chip connected to the shield of my modified µUSB cable, that is to say to pin5. My asumption was that there must have a ground connected between the cable and the phone as 0V reference for UART signals, maybe I'm wrong, I'm not an expert in electronics...
Thanks in advance for your support!

this is fun stuff. good job

flentus said:
Hi xd.bx!
Thanks for your reply.
The cable I have opened has all the 5 pins: one was not wired, I soldered a wire on it and checked the continuity on pin 4 (ID) with a multimeter: it's good. If I put a 301kOhm resistor between pins 4 and 5 and plug the modified wire in my working GSIII mini (without connecting the other end of the cable to anything), it boots in recovery mode which is what is expected. This validates my ID pins wiring.
My Prolific cable is a 3.3V (it's a data cable coming from an "old school" phone). I had to put it appart to identify which wire was connected to what. There is a Prolific chip in it (and no voltage amplifier as there usualy has on RS232 similar cables), so I looked for the reference guide of the chip, which I found. Then I traced back the wires to the chip connexions using my multimeter.
So I managed to identify the RxD and TxD wires (+ the other ones -RTS etc...- I don't care about) and validated this by connecting these 2 wires together, opening a terminal on the corresponding COM port and seeing the typed characters on the terminal. Any mistake on this would have shown nothing (or garbage).
So, as I said, both parts of my setup seem pretty well validated.
But when I put everything together, it doesn't seem to work (no output on my terminal), so I must be wrong somewhere...
From the source code, I'm almost sure the UART setup is the classical 115200 bauds, no parity, 1 bit stop, 8 data bits
(from xloader_pl011.c :
#define BAUDRATE BR115200BAUD
#define PARITYBIT NOPARITY_BIT
#define STOPBITS ONE_STOPBIT
#define DATABITS DATABITS_8
)
Which connexions have you made on your breakout board?
- you have the 620kOhm resistor between pin 4 and 5
- the USB/UART cable RxD connected to the D- pin (= µUSB pin 2) of the breakout board. This is connected internally via the switch matrix to the TxD of UART2 of the processor according to TSU6111.pdf reference doc + I9070 light schematics.
- and USB/UART cable TxD connected to the D+ pin (=µUSB pin 3) of the breakout board (leading to proc UART2 RxD)
What about the grounds? Do you have any connected? If yes, which ones?
On my Prolific cable, I have 2 grounds: 1 connected to the Prolific chip ground and one connected to the USB cable shield. They are *not* connected together.
If I remember well, I tried this setup: ground of the Prolific chip connected to the shield of my modified µUSB cable, that is to say to pin5. My asumption was that there must have a ground connected between the cable and the phone as 0V reference for UART signals, maybe I'm wrong, I'm not an expert in electronics...
Thanks in advance for your support!
Click to expand...
Click to collapse
Hi flentus,
Your setup looks correct to me. I don't remember the connections I made, but you can simply connect RX to D- and then switch to D+ if you don't get output on D-. GND on the PL2303 must be connected to the USB GND, which is a black wire (not the shield). If it still doesn't work, then maybe something else is wrong: perhaps Samsung released a hardware variant? Or the PL2303 cable is defective? Here is the usb-serial dongle I use: http://www.dx.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872 , it's cheap and super reliable.

xd.bx said:
Hi flentus,
Your setup looks correct to me. I don't remember the connections I made, but you can simply connect RX to D- and then switch to D+ if you don't get output on D-. GND on the PL2303 must be connected to the USB GND, which is a black wire (not the shield). If it still doesn't work, then maybe something else is wrong: perhaps Samsung released a hardware variant? Or the PL2303 cable is defective? Here is the usb-serial dongle I use: http://www.dx.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872 , it's cheap and super reliable.
Click to expand...
Click to collapse
Hi!
Thanks a lot for your reply
Ok, so I'll have to try again, maybe I did a mistake the first time. My cable seems fine as when setup in loopback mode (RX connected to TX) it works perfectly. I have 2 or 3 others in cartboxes somewhere in my basement, maybe I'll give one of them a ride
Have a nice day

Related

[NEED SOME HELP] Brick of bootloader ??

Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
RL77LUC said:
Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
Click to expand...
Click to collapse
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kuma82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Lelus said:
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kumar82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Click to expand...
Click to collapse
Thanks a lot for your help. I've tried, but I get that :
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 81eb9bc20de7a195ecaf96582c4197f74c1763
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.206s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.534s
Done
Click to expand...
Click to collapse
And, I've tried a "fastboot oem format", no more success :
...
FAILED (remote failure)
finished. total time: 0.001s
Click to expand...
Click to collapse
I think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
RL77LUC said:
Thanks a lot for your help. I've tried, but I get that :
And, I've tried a "fastboot oem format", no more success :
I've think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
Click to expand...
Click to collapse
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Lelus said:
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Click to expand...
Click to collapse
Thanks for your help, very appreciated. I will don't send it directly to LG but to my carrier (He do the work, according of documents), and they will send to LG.
Anyone have a last chance idea ?
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I hope... Thx.
EDIT : I've gived it to my carrier. They will send my phone to LG. They will give me back in about 3 weeks...

[ROM][4.4.4]VanirAOSP[OFFICIAL][Samsung X Cover 2-GT-S7710]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Smooth like Butta
Follow on G+: Team Vanir
Vanir Team:
NuclearMistake
Sonicxml
DHO
PrimeDirective
Not all features are available yet.
Features:
Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android with subtly improved versions of the features you love to as many devices as possible. we've tried to incorporate and improve our features in a way that makes them more cohesive to improve the overall user experience while correcting any performance regressions and improving functionality..
What to expect:
- This is not a McCopy ROM. What goes into our build is well thought-out and not a bunch of stuff duck taped together because we could.
- maximum optimization. We do our research. We test hard. We build -fstrict -O3 globally and include a massive array of code optimizations and memory leak fixes that we write ourselves and eventually submit to AOSP or Linaro.
- originality in our source. We generate a lot of new commits being features or general code improvements. We are open source to share and improve the community but we also try to make sure we offer a unique experience.
- aesthetics.. hopefully in your opinion
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
UI and graphics improvements
custom navbar, navring, and hardware key features
improved notification handling (active display & halo are in review also)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
yatta yatta yatta
more to come when i feel like updating the op
Changelog:
**Vanir Open Status
**Vanir Merged Status
Vanir Downloads:
**Nightlies
Recovery Downloads:
**CWM
Vanir Github:
**VanirAOSP Git
Gapps:
**4.4.2 PA Gapps
Installation Instructions
Make sure your using cwm above it's required
Full wipe
Install ROM
Install Gapps
Thanks
TeamVanir
Meticulus
Everyone here for keeping me inspired
Source
Kernel
Skomer device tree
Common device/Codinalte
Vendor
Changelog
** Initial Release **
- Booting now.
TODO:
Fix wifi
Not working
** Initial Release **
- Menu and back button
- Wifi
Working
Need some feedback
New build coming thanks to @frapeti for a fix for making the device tree even more common. Results in way less work. Now skomer and golden trees don't need modification at all. Anything done to codinalte will be used for golden and skomer.
edit: To fix confusion codinalte builds aren't compatible. It just allows skomer device tree to take our code and use it without having to maintain more source.
3/21/14 Build now available
Makes sure your using my cwm
* Upstream CyanogenMod updates
* Upstream Vanir Updates
* Codinalte Relocate keylayouts per device
* Skomer and Golden copy ramdisk files from codinalte to minimize the amount of code to maintain
* Codinalte minor clean up of files. Removed unneeded files and configs
* Skomer added device specific gpio-keys to fix home , menu , and back button
* WIFI??? Please report back.
* Device tree is now available to compile for any rom. Previously is was not clean and had errors
Always a logcat is needed when you report a problem and is much appreciated.
http://www.androidfilehost.com/?fid=23329332407580741
Could someone pull config?
adb pull proc/config.gz thank you
Wifi fixed
https://github.com/Team-Exhibit/vendor_samsung/commit/71e446b6871a252ab97de5cb66980b8d495e6cc6
Hi,
I did some testing with the vanir_skomer_4.4.2.032114 build.
- no mobile network, ROM couldn't find my SIM or any network.
- no WiFi, it was greyed out in both the pull menu and settings. I couldn't enable it.
- on 1st boot, Home and Back buttons worked but on the 2nd boot I somehow lost that functionality
I had similar problems with flxo's cm builds. I flashed from the stock if that matters anything.
Otherwise looks like a nice ROM
Also CWM seems to work ok.
I managed to get a logcat, hopefully it helps.
doh, I forgot to pull that config you requested. I'll try keep it on my mind next time I flash..
Alexerik said:
How to create a bug report? I tested the new build and network is ok for me but wifi dnd work at all. . and sd card isn't recognized.
Click to expand...
Click to collapse
There are several ways to get logcat, I used adb.
Please refer these links:
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
3/23/14 build now available
* Upstream Vanir changes/CM changes
* Fixed wifi
* Low volume in call merged
* Fixed issue with vold not mounting sdcard
* Removed some golden specific init things
* Semi stable build ????
http://www.androidfilehost.com/?fid=23329332407581158
Unjustified Dev said:
Could someone pull config?
adb pull proc/config.gz thank you
Click to expand...
Click to collapse
Here is the proc/config.gz as you requested.
I tested vanir_skomer_4.4.2.032314 build.
- Can confirm that WiFi works now.
- I still dont have mobile network. (can provide another logcat if that's necessary.)
- On the 1st boot, none of the hardware keys (home, back, menu etc.) worked except the power button. On 2nd boot all buttons started to work (kinda weird).
I can't comment on low volume in call or builds stability due to problem I listed above ^^.
Great job anyways
seems to work quite nicely now!
not sure if it is of interest, or the right place to discuss, but is it possible to give some of the free memory in the system partition to data, so that we might have a chance to enjoy art even with a moderate number of user apps? i ran into problems with 60 apps. didn't have enough time to check if something was wrong with the foldermounts, but i think in general on the s7710 we have too much system...
nice work with the rom and thanks for reviving s7710 development, the 03-23 version worked flawlessly in my super short test! :silly:
edit: link2sd was in operation, so that was not the culprit.
vastus said:
Here is the proc/config.gz as you requested.
I tested vanir_skomer_4.4.2.032314 build.
- Can confirm that WiFi works now.
- I still dont have mobile network. (can provide another logcat if that's necessary.)
- On the 1st boot, none of the hardware keys (home, back, menu etc.) worked except the power button. On 2nd boot all buttons started to work (kinda weird).
I can't comment on low volume in call or builds stability due to problem I listed above ^^.
Great job anyways
Click to expand...
Click to collapse
I have the config dump that was for the kernel thanks. I'm still not understanding the internet problem some say it work some say it takes 7-10 minutes before it connects. I'm a bit confused.
adb logcat -b radio > radio.txt
this will create radio.txt which you can upload.
To ensure everything is correct did you wipe data , format system , and wipe dalvik cache before flashing?
Unjustified Dev said:
I have the config dump that was for the kernel thanks. I'm still not understanding the internet problem some say it work some say it takes 7-10 minutes before it connects. I'm a bit confused.
adb logcat -b radio > radio.txt
this will create radio.txt which you can upload.
To ensure everything is correct did you wipe data , format system , and wipe dalvik cache before flashing?
Click to expand...
Click to collapse
Okay, I tried again and this time I left phone on the table for 30 mins, no signal. :|
Yes, I always wipe data, format /system and wipe dalvik cache, when switching roms.
Here's radio logcat.
Testing..
Using latest build for some hours:
Phone line OK GSM+3g
Wi fi Semi OK something needs a cache + dalvik reset to work
Phone call volume OK
Average impression: really good keep testing thanx 4 your work!
Sent from my GT-S7710 using xda app-developers app
Hello
At first: thx a lot for that thread. I am gona test this rom as soon as possible (when i switch my primary phone to SIII mini).
and about radio:
i remember from forum, that Some X Cover 2 phones with cyanogenmod have GSM problems.
i saw 2 types:
1.) no network at all - that was fixed by wiping system partition before flash
2.) low signal, long singon, and often singal lost,
i have device with same problems - original and rooted rom works fine, with perfect signal, and fast gms search.
Cyanogenmod (10.2 alpha 8, and 10.2 alpha 10) make GSM issues - long time to sing into gsm, and very often singout. when i make a call, it was interupted in about 20 second, and i got no network signal for a while.
p.s. sorry for my english
maurensen said:
Testing..
Using latest build for some hours:
Phone line OK GSM+3g
Wi fi Semi OK something needs a cache + dalvik reset to work
Average impression: really good keep testing thanx 4 your work!
Sent from my GT-S7710 using xda app-developers app
Click to expand...
Click to collapse
Hey,
At first thanks for your awesome work I've just tested your ROM and everything works at least as god as in flxo latest CM10.2 ROM but I noticed one annoying thing: touchscreen dosn't work on very bottom of screen. To turn on applications on home screen i need to aim at the upper part of icon. I also noticed that it's imposible to turn on live wallpapers.
btw: sorry for my english
Also I've noticed that the touch on bottom of the screen is not working well( for ex if I have keyboard open I have to press two or three times to get keys on bottom screen to be detected).
BTW I have often some random reboot but the rest of the Rom is working well so for now I think I'll not switch back to flxo 's CM 10.2 and try to use 24/7 this nice rom.
Thanx for your work unjustified dev!
Sent from my GT-S7710 using xda app-developers app
maurensen said:
I have often some random reboot but the rest of the Rom is working well
Click to expand...
Click to collapse
I also have problem with random reboots
Code:
[ 1433.318023] CPU1: shutdown
[ 1449.938720] ux500_pm_gpio_save_wake_up_status: bank6: 0x01000000
[ 1449.938751] Returning from ApDeepSleep. PRCMU ret: 0xf6 - Success
[ 1449.939575] Wakeup Status: 0x20000000
[ 1449.939727] DVFS Governor Policy set to - ondemand
[ 1449.948120] PM: early resume of devices complete after 0.915 msecs
[ 1449.948577] wakeup wake lock: wlan_wake
[ 1449.962463] -> NCP6914_i2c_resume()
[ 1449.962493] <- NCP6914_i2c_resume() = 0
[ 1449.962524] bma254_resume: is called
[ 1449.962524] hscd_resume: is called
[ 1450.040283] bcmsdh_sdmmc_resume Enter
[ 1450.040283] bcmsdh_sdmmc_resume Enter
[ 1450.042327] [rtc_resume] AP RTC TIME: 1970.01.01 - 00:00:00 called
[ 1450.042358] [rtc_resume] PMIC RTC TIME: 2014.03.24 - 20:01:53 called
[ 1450.042358] [rtc_resume] SYSTEM TIME: 2014.03.24 - 20:01:53 called
[ 1450.042358] [rtc_resume] delta.tv_sec: 0 delta.tv_nsec: 0
[ 1450.042388] [rtc_resume] delta_delta.tv_sec: -1 delta_delta.tv_nsec: 526663808
[ 1450.044799] PM: resume of devices complete after 94.798 msecs
[ 1450.045440] DVFS Governor Policy set to - ondemand
[ 1450.045440] new min and max freqs are 200000 - 1000000 kHz
[ 1450.045471] Restarting tasks ...
[ 1450.046203] hub 1-0:1.0: activate --> -22
[ 1450.092407] done.
[ 1450.092956] [Message To CP] Ret: 13
[ 1450.092956] [writePacketToFile]request byte length = 13, return byte = 13
[ 1450.092987] tx_ap_state(WAKEUP): 0
[ 1450.092987] suspend: exit suspend, ret = 0 (2014-03-24 20:01:53.550652880 UTC)
[ 1450.094268] Enabling non-boot CPUs ...
[ 1450.095092] sec-battery sec-battery: sec_bat_get_battery_info: Connected, SOC(95%)
[ 1450.095123] sec-battery sec-battery: sec_bat_get_battery_info: Vnow(4259mV), Vavg(1618mV), Vocv(1618mV)
[ 1450.095123] sec-battery sec-battery: sec_bat_get_battery_info: Inow(-146mA), Iavg(-104mA), Iadc(0)
[ 1450.095153] sec-battery sec-battery: sec_bat_get_battery_info: Tbat(236), Tamb(700)
[ 1450.096435] sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), Health(Good), Cable(1)
[ 1450.120971] CPU1: Booted secondary processor
[ 1450.122131] Switched to NOHz mode on CPU #1
[ 1450.142974] CPU1 is up
[ 1450.719390] ab8500-fg ab8500-fg.0: [FG_DATA] 1618mAh/1700mAh 95% (Prev 1623mAh 95%) 4277mV -233mA -104mA -578 0 0 5 1 1 143 95 0 0 0
[ 1450.895233] ux500_pm_gpio_save_wake_up_status: bank6: 0x01000000
[ 1450.895416] Wakeup Status: 0x20000000
[ 1451.698974] Unable to handle kernel NULL pointer dereference at virtual address 00000010
[ 1451.699005] pgd = e3d34000
[ 1451.699005] [00000010] *pgd=00000000
[ 1451.699035] Internal error: Oops: 5 [#1] PREEMPT SMP
[ 1451.699035] dbx500_dump notified of crash
[ 1451.701354] Modules linked in: dhd bthid param(P) j4fs(P)
[ 1451.701385] CPU: 1 Tainted: P W (3.0.31+ #1)
[ 1451.701415] PC is at disable_led_notification+0x34/0xc0
[ 1451.701446] LR is at notification_led_status_write+0x4c/0x110
[ 1451.701477] pc : [<c03717f0>] lr : [<c0371a1c>] psr: 200b0013
[ 1451.701477] sp : e3cffec0 ip : 00000000 fp : e3cffed4
[ 1451.701477] r10: c06b0758 r9 : e6584808 r8 : e658f8a8
[ 1451.701507] r7 : e39bee60 r6 : e3cfff78 r5 : e39bee78 r4 : c0fa9460
[ 1451.701507] r3 : 00000001 r2 : 00000000 r1 : c086dd43 r0 : 00000001
[ 1451.701538] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 1451.701538] Control: 10c5787d Table: 23d3404a DAC: 00000015
[ 1451.701568]
[ 1451.701568] PC: 0xc0371770:
(... dump data ...)
[ 1451.706420] [<c03717f0>] (disable_led_notification+0x34/0xc0) from [<c0371a1c>] (notification_led_status_write+0x4c/0x110)
[ 1451.706451] [<c0371a1c>] (notification_led_status_write+0x4c/0x110) from [<c0353878>] (dev_attr_store+0x28/0x34)
[ 1451.706481] [<c0353878>] (dev_attr_store+0x28/0x34) from [<c01bad5c>] (sysfs_write_file+0x178/0x1a8)
[ 1451.706512] [<c01bad5c>] (sysfs_write_file+0x178/0x1a8) from [<c01633fc>] (vfs_write+0xac/0x150)
[ 1451.706542] [<c01633fc>] (vfs_write+0xac/0x150) from [<c01636b4>] (sys_write+0x48/0x80)
[ 1451.706573] [<c01636b4>] (sys_write+0x48/0x80) from [<c0067a00>] (ret_fast_syscall+0x0/0x30)
[ 1451.706573] Code: e5d43008 e3530000 0a000017 e594c00c (e59c2010)
[ 1451.706603] CPU0: stopping
[ 1451.706634] [<c006f00c>] (unwind_backtrace+0x0/0x144) from [<c0670c34>] (dump_stack+0x20/0x24)
[ 1451.706665] [<c0670c34>] (dump_stack+0x20/0x24) from [<c0060694>] (do_IPI+0x200/0x23c)
[ 1451.706695] [<c0060694>] (do_IPI+0x200/0x23c) from [<c006744c>] (__irq_svc+0x4c/0xe8)
[ 1451.706695] Exception stack(0xc0939e80 to 0xc0939ec8)
[ 1451.706726] 9e80: c0fd1d34 600f0093 00000001 00000000 6817667c 00000048 00000f23 00000001
[ 1451.706726] 9ea0: 67dc4498 00000048 00000001 c0939f5c c0939e50 c0939ec8 c04361c0 c04334a0
[ 1451.706756] 9ec0: 600f0013 ffffffff
[ 1451.706787] [<c006744c>] (__irq_svc+0x4c/0xe8) from [<c04334a0>] (enter_sleep+0x3ec/0x7e0)
[ 1451.706787] [<c04334a0>] (enter_sleep+0x3ec/0x7e0) from [<c0430f54>] (cpuidle_idle_call+0xc8/0x2fc)
[ 1451.706817] [<c0430f54>] (cpuidle_idle_call+0xc8/0x2fc) from [<c0068a30>] (cpu_idle+0xcc/0x120)
[ 1451.706848] [<c0068a30>] (cpu_idle+0xcc/0x120) from [<c065ef3c>] (rest_init+0x94/0xac)
[ 1451.706878] [<c065ef3c>] (rest_init+0x94/0xac) from [<c0008a90>] (start_kernel+0x3fc/0x490)
[ 1451.706878] [<c0008a90>] (start_kernel+0x3fc/0x490) from [<00008040>] (0x8040)
[ 1451.707031] fd_line_length=1920
[ 1451.707031] Oops
[ 1451.707061] Kernel panic!!. Please connect the phone to PC
[ 1451.707244] enable capture and press the volume down key to get the
[ 1451.707458] kernel log. Repeat if required.
[ 1451.707550] Press volume up to enter upload mode.
[ 1451.717437] Board Information: UX500: 6C, cpu U8500 ES178
[ 1451.717468] ---[ end trace 2b6060ff815a1cef ]---
[ 1451.717468] Kernel panic - not syncing: Fatal exception
[ 1451.717529] [<c006f00c>] (unwind_backtrace+0x0/0x144) from [<c0670c34>] (dump_stack+0x20/0x24)
[ 1451.717559] [<c0670c34>] (dump_stack+0x20/0x24) from [<c06710fc>] (panic+0x80/0x2c0)
[ 1451.717590] [<c06710fc>] (panic+0x80/0x2c0) from [<c006bad4>] (die+0x1dc/0x214)
[ 1451.717590] [<c006bad4>] (die+0x1dc/0x214) from [<c0670c9c>] (__do_kernel_fault.part.2+0x64/0x84)
[ 1451.717620] [<c0670c9c>] (__do_kernel_fault.part.2+0x64/0x84) from [<c0073980>] (do_page_fault+0x278/0x378)
[ 1451.717651] [<c0073980>] (do_page_fault+0x278/0x378) from [<c0073bc0>] (do_translation_fault+0xa8/0xb0)
[ 1451.717681] [<c0073bc0>] (do_translation_fault+0xa8/0xb0) from [<c0060218>] (do_DataAbort+0x44/0xac)
[ 1451.717681] [<c0060218>] (do_DataAbort+0x44/0xac) from [<c00673d0>] (__dabt_svc+0x70/0xa0)
[ 1451.717712] Exception stack(0xe3cffe78 to 0xe3cffec0)
[ 1451.717712] fe60: 00000001 c086dd43
[ 1451.717742] fe80: 00000000 00000001 c0fa9460 e39bee78 e3cfff78 e39bee60 e658f8a8 e6584808
[ 1451.717742] fea0: c06b0758 e3cffed4 00000000 e3cffec0 c0371a1c c03717f0 200b0013 ffffffff
[ 1451.717773] [<c00673d0>] (__dabt_svc+0x70/0xa0) from [<c03717f0>] (disable_led_notification+0x34/0xc0)
[ 1451.717803] [<c03717f0>] (disable_led_notification+0x34/0xc0) from [<c0371a1c>] (notification_led_status_write+0x4c/0x110)
[ 1451.717834] [<c0371a1c>] (notification_led_status_write+0x4c/0x110) from [<c0353878>] (dev_attr_store+0x28/0x34)
[ 1451.717864] [<c0353878>] (dev_attr_store+0x28/0x34) from [<c01bad5c>] (sysfs_write_file+0x178/0x1a8)
[ 1451.717864] [<c01bad5c>] (sysfs_write_file+0x178/0x1a8) from [<c01633fc>] (vfs_write+0xac/0x150)
[ 1451.717895] [<c01633fc>] (vfs_write+0xac/0x150) from [<c01636b4>] (sys_write+0x48/0x80)
[ 1451.717926] [<c01636b4>] (sys_write+0x48/0x80) from [<c0067a00>] (ret_fast_syscall+0x0/0x30)
[ 1451.718048] machine_restart: lockup
[ 1451.718078] machine_restart: cmd: LockUp
[ 1451.718078] machine_restart: reboot_mode: L
[ 1451.718078] machine_restart: arm_pm_restart: 0xc0078380
[ 1451.718078] ux500_restart: Call arch_reset(), mode: L, cmd: LockUp
After some reboots no more random resets.. Good... Using from some hours and the Rom now seems solid not as flxo cm10.2 but very usable!
I'm going to keep it!
BTW switched to Art runtime just to try it with no problems so far...
Very nice Rim very customizable
Sent from my GT-S7710 using xda app-developers app
MDobak said:
I also have problem with random reboots
Code:
[ 1433.318023] CPU1: shutdown
[ 1449.938720] ux500_pm_gpio_save_wake_up_status: bank6: 0x01000000
[ 1449.938751] Returning from ApDeepSleep. PRCMU ret: 0xf6 - Success
[ 1449.939575] Wakeup Status: 0x20000000
[ 1449.939727] DVFS Governor Policy set to - ondemand
[ 1449.948120] PM: early resume of devices complete after 0.915 msecs
[ 1449.948577] wakeup wake lock: wlan_wake
[ 1449.962463] -> NCP6914_i2c_resume()
[ 1449.962493] <- NCP6914_i2c_resume() = 0
[ 1449.962524] bma254_resume: is called
[ 1449.962524] hscd_resume: is called
[ 1450.040283] bcmsdh_sdmmc_resume Enter
[ 1450.040283] bcmsdh_sdmmc_resume Enter
[ 1450.042327] [rtc_resume] AP RTC TIME: 1970.01.01 - 00:00:00 called
[ 1450.042358] [rtc_resume] PMIC RTC TIME: 2014.03.24 - 20:01:53 called
[ 1450.042358] [rtc_resume] SYSTEM TIME: 2014.03.24 - 20:01:53 called
[ 1450.042358] [rtc_resume] delta.tv_sec: 0 delta.tv_nsec: 0
[ 1450.042388] [rtc_resume] delta_delta.tv_sec: -1 delta_delta.tv_nsec: 526663808
[ 1450.044799] PM: resume of devices complete after 94.798 msecs
[ 1450.045440] DVFS Governor Policy set to - ondemand
[ 1450.045440] new min and max freqs are 200000 - 1000000 kHz
[ 1450.045471] Restarting tasks ...
[ 1450.046203] hub 1-0:1.0: activate --> -22
[ 1450.092407] done.
[ 1450.092956] [Message To CP] Ret: 13
[ 1450.092956] [writePacketToFile]request byte length = 13, return byte = 13
[ 1450.092987] tx_ap_state(WAKEUP): 0
[ 1450.092987] suspend: exit suspend, ret = 0 (2014-03-24 20:01:53.550652880 UTC)
[ 1450.094268] Enabling non-boot CPUs ...
[ 1450.095092] sec-battery sec-battery: sec_bat_get_battery_info: Connected, SOC(95%)
[ 1450.095123] sec-battery sec-battery: sec_bat_get_battery_info: Vnow(4259mV), Vavg(1618mV), Vocv(1618mV)
[ 1450.095123] sec-battery sec-battery: sec_bat_get_battery_info: Inow(-146mA), Iavg(-104mA), Iadc(0)
[ 1450.095153] sec-battery sec-battery: sec_bat_get_battery_info: Tbat(236), Tamb(700)
[ 1450.096435] sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), Health(Good), Cable(1)
[ 1450.120971] CPU1: Booted secondary processor
[ 1450.122131] Switched to NOHz mode on CPU #1
[ 1450.142974] CPU1 is up
[ 1450.719390] ab8500-fg ab8500-fg.0: [FG_DATA] 1618mAh/1700mAh 95% (Prev 1623mAh 95%) 4277mV -233mA -104mA -578 0 0 5 1 1 143 95 0 0 0
[ 1450.895233] ux500_pm_gpio_save_wake_up_status: bank6: 0x01000000
[ 1450.895416] Wakeup Status: 0x20000000
[ 1451.698974] Unable to handle kernel NULL pointer dereference at virtual address 00000010
[ 1451.699005] pgd = e3d34000
[ 1451.699005] [00000010] *pgd=00000000
[ 1451.699035] Internal error: Oops: 5 [#1] PREEMPT SMP
[ 1451.699035] dbx500_dump notified of crash
[ 1451.701354] Modules linked in: dhd bthid param(P) j4fs(P)
[ 1451.701385] CPU: 1 Tainted: P W (3.0.31+ #1)
[ 1451.701415] PC is at disable_led_notification+0x34/0xc0
[ 1451.701446] LR is at notification_led_status_write+0x4c/0x110
[ 1451.701477] pc : [<c03717f0>] lr : [<c0371a1c>] psr: 200b0013
[ 1451.701477] sp : e3cffec0 ip : 00000000 fp : e3cffed4
[ 1451.701477] r10: c06b0758 r9 : e6584808 r8 : e658f8a8
[ 1451.701507] r7 : e39bee60 r6 : e3cfff78 r5 : e39bee78 r4 : c0fa9460
[ 1451.701507] r3 : 00000001 r2 : 00000000 r1 : c086dd43 r0 : 00000001
[ 1451.701538] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 1451.701538] Control: 10c5787d Table: 23d3404a DAC: 00000015
[ 1451.701568]
[ 1451.701568] PC: 0xc0371770:
(... dump data ...)
[ 1451.706420] [<c03717f0>] (disable_led_notification+0x34/0xc0) from [<c0371a1c>] (notification_led_status_write+0x4c/0x110)
[ 1451.706451] [<c0371a1c>] (notification_led_status_write+0x4c/0x110) from [<c0353878>] (dev_attr_store+0x28/0x34)
[ 1451.706481] [<c0353878>] (dev_attr_store+0x28/0x34) from [<c01bad5c>] (sysfs_write_file+0x178/0x1a8)
[ 1451.706512] [<c01bad5c>] (sysfs_write_file+0x178/0x1a8) from [<c01633fc>] (vfs_write+0xac/0x150)
[ 1451.706542] [<c01633fc>] (vfs_write+0xac/0x150) from [<c01636b4>] (sys_write+0x48/0x80)
[ 1451.706573] [<c01636b4>] (sys_write+0x48/0x80) from [<c0067a00>] (ret_fast_syscall+0x0/0x30)
[ 1451.706573] Code: e5d43008 e3530000 0a000017 e594c00c (e59c2010)
[ 1451.706603] CPU0: stopping
[ 1451.706634] [<c006f00c>] (unwind_backtrace+0x0/0x144) from [<c0670c34>] (dump_stack+0x20/0x24)
[ 1451.706665] [<c0670c34>] (dump_stack+0x20/0x24) from [<c0060694>] (do_IPI+0x200/0x23c)
[ 1451.706695] [<c0060694>] (do_IPI+0x200/0x23c) from [<c006744c>] (__irq_svc+0x4c/0xe8)
[ 1451.706695] Exception stack(0xc0939e80 to 0xc0939ec8)
[ 1451.706726] 9e80: c0fd1d34 600f0093 00000001 00000000 6817667c 00000048 00000f23 00000001
[ 1451.706726] 9ea0: 67dc4498 00000048 00000001 c0939f5c c0939e50 c0939ec8 c04361c0 c04334a0
[ 1451.706756] 9ec0: 600f0013 ffffffff
[ 1451.706787] [<c006744c>] (__irq_svc+0x4c/0xe8) from [<c04334a0>] (enter_sleep+0x3ec/0x7e0)
[ 1451.706787] [<c04334a0>] (enter_sleep+0x3ec/0x7e0) from [<c0430f54>] (cpuidle_idle_call+0xc8/0x2fc)
[ 1451.706817] [<c0430f54>] (cpuidle_idle_call+0xc8/0x2fc) from [<c0068a30>] (cpu_idle+0xcc/0x120)
[ 1451.706848] [<c0068a30>] (cpu_idle+0xcc/0x120) from [<c065ef3c>] (rest_init+0x94/0xac)
[ 1451.706878] [<c065ef3c>] (rest_init+0x94/0xac) from [<c0008a90>] (start_kernel+0x3fc/0x490)
[ 1451.706878] [<c0008a90>] (start_kernel+0x3fc/0x490) from [<00008040>] (0x8040)
[ 1451.707031] fd_line_length=1920
[ 1451.707031] Oops
[ 1451.707061] Kernel panic!!. Please connect the phone to PC
[ 1451.707244] enable capture and press the volume down key to get the
[ 1451.707458] kernel log. Repeat if required.
[ 1451.707550] Press volume up to enter upload mode.
[ 1451.717437] Board Information: UX500: 6C, cpu U8500 ES178
[ 1451.717468] ---[ end trace 2b6060ff815a1cef ]---
[ 1451.717468] Kernel panic - not syncing: Fatal exception
[ 1451.717529] [<c006f00c>] (unwind_backtrace+0x0/0x144) from [<c0670c34>] (dump_stack+0x20/0x24)
[ 1451.717559] [<c0670c34>] (dump_stack+0x20/0x24) from [<c06710fc>] (panic+0x80/0x2c0)
[ 1451.717590] [<c06710fc>] (panic+0x80/0x2c0) from [<c006bad4>] (die+0x1dc/0x214)
[ 1451.717590] [<c006bad4>] (die+0x1dc/0x214) from [<c0670c9c>] (__do_kernel_fault.part.2+0x64/0x84)
[ 1451.717620] [<c0670c9c>] (__do_kernel_fault.part.2+0x64/0x84) from [<c0073980>] (do_page_fault+0x278/0x378)
[ 1451.717651] [<c0073980>] (do_page_fault+0x278/0x378) from [<c0073bc0>] (do_translation_fault+0xa8/0xb0)
[ 1451.717681] [<c0073bc0>] (do_translation_fault+0xa8/0xb0) from [<c0060218>] (do_DataAbort+0x44/0xac)
[ 1451.717681] [<c0060218>] (do_DataAbort+0x44/0xac) from [<c00673d0>] (__dabt_svc+0x70/0xa0)
[ 1451.717712] Exception stack(0xe3cffe78 to 0xe3cffec0)
[ 1451.717712] fe60: 00000001 c086dd43
[ 1451.717742] fe80: 00000000 00000001 c0fa9460 e39bee78 e3cfff78 e39bee60 e658f8a8 e6584808
[ 1451.717742] fea0: c06b0758 e3cffed4 00000000 e3cffec0 c0371a1c c03717f0 200b0013 ffffffff
[ 1451.717773] [<c00673d0>] (__dabt_svc+0x70/0xa0) from [<c03717f0>] (disable_led_notification+0x34/0xc0)
[ 1451.717803] [<c03717f0>] (disable_led_notification+0x34/0xc0) from [<c0371a1c>] (notification_led_status_write+0x4c/0x110)
[ 1451.717834] [<c0371a1c>] (notification_led_status_write+0x4c/0x110) from [<c0353878>] (dev_attr_store+0x28/0x34)
[ 1451.717864] [<c0353878>] (dev_attr_store+0x28/0x34) from [<c01bad5c>] (sysfs_write_file+0x178/0x1a8)
[ 1451.717864] [<c01bad5c>] (sysfs_write_file+0x178/0x1a8) from [<c01633fc>] (vfs_write+0xac/0x150)
[ 1451.717895] [<c01633fc>] (vfs_write+0xac/0x150) from [<c01636b4>] (sys_write+0x48/0x80)
[ 1451.717926] [<c01636b4>] (sys_write+0x48/0x80) from [<c0067a00>] (ret_fast_syscall+0x0/0x30)
[ 1451.718048] machine_restart: lockup
[ 1451.718078] machine_restart: cmd: LockUp
[ 1451.718078] machine_restart: reboot_mode: L
[ 1451.718078] machine_restart: arm_pm_restart: 0xc0078380
[ 1451.718078] ux500_restart: Call arch_reset(), mode: L, cmd: LockUp
Click to expand...
Click to collapse
Next time you get a reboot turn off WiFi. Then see if after that it reboots? This is the same problem on my device. I just released a test build for them in which I think it's fixed.

Lost Wifi MAC address

Hi, after the official OTA upgrade of my Nexus 9 the MAC address of WiFi is 02:00:00:00:00 and the WiFi is not working anymore.
The same problem for the Bluetooth.
I try to reinstall everything many times, different ROM's too, but I cannot solve It.
I search everywhere on internet bit I cannot find any useful information.
Can anyone help me please?
mirkorazietti said:
Hi, after the official OTA upgrade of my Nexus 9 the MAC address of WiFi is 02:00:00:00:00 and the WiFi is not working anymore.
The same problem for the Bluetooth.
I try to reinstall everything many times, different ROM's too, but I cannot solve It.
I search everywhere on internet bit I cannot find any useful information.
Can anyone help me please?
Click to expand...
Click to collapse
Can you give me the kernel log after full boot
just do
su
dmesg > /sdcard/log.log
Then just give me /sdcard/log.log
I probably won't be able to fix it but I want to know what's happening
USBhost said:
Can you give me the kernel log after full boot
just do
su
dmesg > /sdcard/log.log
Then just give me /sdcard/log.log
I probably won't be able to fix it but I want to know what's happening
Click to expand...
Click to collapse
Hi, that's the log file
Thank in advance for your time
mirkorazietti said:
Hi, that's the log file
Thank in advance for your time
Click to expand...
Click to collapse
Wow that's something you don't see everyday....
Code:
[ 31.074029] found wifi platform device bcm4329_wlan
[ 31.074046] unregister wifi platform drivers
[ 31.074094] dhd_module_init: Failed to load the driver, try cnt 1
[ 31.074207] found wifi platform device bcm4329_wlan
[ 31.074434] Power-up adapter 'DHD generic adapter'
[ 31.074476] wifi_platform_set_power = 1
[ 31.074492] flounder_wifi_power: 1
[ 31.380496] wifi_platform_bus_enumerate device present 1
[ 33.380485] failed to power up DHD generic adapter, 3 retry left
[ 33.396608] wifi_platform_set_power = 0
[ 33.396628] flounder_wifi_power: 0
[ 33.497077] wifi_platform_bus_enumerate device present 0
[ 33.497137] wifi_platform_set_power = 1
[ 33.497153] flounder_wifi_power: 1
[ 33.803833] wifi_platform_bus_enumerate device present 1
[ 35.803940] failed to power up DHD generic adapter, 2 retry left
[ 35.820048] wifi_platform_set_power = 0
[ 35.820067] flounder_wifi_power: 0
[ 35.920592] wifi_platform_bus_enumerate device present 0
[ 35.920648] wifi_platform_set_power = 1
[ 35.920666] flounder_wifi_power: 1
[ 36.227139] wifi_platform_bus_enumerate device present 1
[ 38.227168] failed to power up DHD generic adapter, 1 retry left
[ 38.243300] wifi_platform_set_power = 0
[ 38.243320] flounder_wifi_power: 0
[ 38.343735] wifi_platform_bus_enumerate device present 0
[ 38.343797] wifi_platform_set_power = 1
[ 38.343814] flounder_wifi_power: 1
[ 38.650518] wifi_platform_bus_enumerate device present 1
[ 40.650406] failed to power up DHD generic adapter, 0 retry left
[ 40.666528] wifi_platform_set_power = 0
[ 40.666547] flounder_wifi_power: 0
[ 40.677534] INFO: task kworker/0:1:18 blocked for more than 10 seconds.
[ 40.677561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.677589] kworker/0:1 D ffffffc000086904 0 18 2 0x00000000
[ 40.677663] Workqueue: events request_firmware_work_func
[ 40.677691] Call trace:
[ 40.677726] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.677758] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.677779] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.677799] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.677820] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.677843] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.677864] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.677885] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.677911] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.677932] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.677956] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.677998] INFO: task kworker/0:2:85 blocked for more than 10 seconds.
[ 40.678014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678030] kworker/0:2 D ffffffc000086904 0 85 2 0x00000000
[ 40.678076] Workqueue: events request_firmware_work_func
[ 40.678099] Call trace:
[ 40.678120] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678140] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678174] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678193] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678258] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678279] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678299] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678319] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.678340] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678362] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678382] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.678402] INFO: task kworker/u4:1:87 blocked for more than 10 seconds.
[ 40.678417] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678434] kworker/u4:1 D ffffffc000086904 0 87 2 0x00000000
[ 40.678486] Workqueue: fwu_workqueue fwu_startup_fw_update_work
[ 40.678509] Call trace:
[ 40.678530] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678550] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678570] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678590] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678611] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678631] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678651] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678672] [<ffffffc00047cc20>] request_firmware+0x14/0x1c
[ 40.678693] [<ffffffc000635454>] synaptics_fw_updater+0x3e0/0x8b0
[ 40.678713] [<ffffffc000636100>] fwu_startup_fw_update_work+0x24/0x50
[ 40.678734] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678754] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678774] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.767142] wifi_platform_bus_enumerate device present 0
[ 40.767181] failed to power up DHD generic adapter, max retry reached**
It looks like something happened to your wifi card that it can't poweron.
There's really nothing you can do in the software side of things sorry.
You can try replacing the motherboard but that's like 1/3 the cost of the tablet.....
Or send it in to repair, do you still have warranty? I know you rooted your device but who knows right :laugh:
Sorry for the bad news...
If none of those are options you can always just use ethernet.
USBhost said:
Wow that's something you don't see everyday....
Code:
[ 31.074029] found wifi platform device bcm4329_wlan
[ 31.074046] unregister wifi platform drivers
[ 31.074094] dhd_module_init: Failed to load the driver, try cnt 1
[ 31.074207] found wifi platform device bcm4329_wlan
[ 31.074434] Power-up adapter 'DHD generic adapter'
[ 31.074476] wifi_platform_set_power = 1
[ 31.074492] flounder_wifi_power: 1
[ 31.380496] wifi_platform_bus_enumerate device present 1
[ 33.380485] failed to power up DHD generic adapter, 3 retry left
[ 33.396608] wifi_platform_set_power = 0
[ 33.396628] flounder_wifi_power: 0
[ 33.497077] wifi_platform_bus_enumerate device present 0
[ 33.497137] wifi_platform_set_power = 1
[ 33.497153] flounder_wifi_power: 1
[ 33.803833] wifi_platform_bus_enumerate device present 1
[ 35.803940] failed to power up DHD generic adapter, 2 retry left
[ 35.820048] wifi_platform_set_power = 0
[ 35.820067] flounder_wifi_power: 0
[ 35.920592] wifi_platform_bus_enumerate device present 0
[ 35.920648] wifi_platform_set_power = 1
[ 35.920666] flounder_wifi_power: 1
[ 36.227139] wifi_platform_bus_enumerate device present 1
[ 38.227168] failed to power up DHD generic adapter, 1 retry left
[ 38.243300] wifi_platform_set_power = 0
[ 38.243320] flounder_wifi_power: 0
[ 38.343735] wifi_platform_bus_enumerate device present 0
[ 38.343797] wifi_platform_set_power = 1
[ 38.343814] flounder_wifi_power: 1
[ 38.650518] wifi_platform_bus_enumerate device present 1
[ 40.650406] failed to power up DHD generic adapter, 0 retry left
[ 40.666528] wifi_platform_set_power = 0
[ 40.666547] flounder_wifi_power: 0
[ 40.677534] INFO: task kworker/0:1:18 blocked for more than 10 seconds.
[ 40.677561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.677589] kworker/0:1 D ffffffc000086904 0 18 2 0x00000000
[ 40.677663] Workqueue: events request_firmware_work_func
[ 40.677691] Call trace:
[ 40.677726] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.677758] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.677779] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.677799] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.677820] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.677843] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.677864] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.677885] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.677911] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.677932] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.677956] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.677998] INFO: task kworker/0:2:85 blocked for more than 10 seconds.
[ 40.678014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678030] kworker/0:2 D ffffffc000086904 0 85 2 0x00000000
[ 40.678076] Workqueue: events request_firmware_work_func
[ 40.678099] Call trace:
[ 40.678120] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678140] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678174] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678193] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678258] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678279] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678299] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678319] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.678340] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678362] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678382] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.678402] INFO: task kworker/u4:1:87 blocked for more than 10 seconds.
[ 40.678417] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678434] kworker/u4:1 D ffffffc000086904 0 87 2 0x00000000
[ 40.678486] Workqueue: fwu_workqueue fwu_startup_fw_update_work
[ 40.678509] Call trace:
[ 40.678530] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678550] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678570] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678590] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678611] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678631] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678651] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678672] [<ffffffc00047cc20>] request_firmware+0x14/0x1c
[ 40.678693] [<ffffffc000635454>] synaptics_fw_updater+0x3e0/0x8b0
[ 40.678713] [<ffffffc000636100>] fwu_startup_fw_update_work+0x24/0x50
[ 40.678734] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678754] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678774] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.767142] wifi_platform_bus_enumerate device present 0
[ 40.767181] failed to power up DHD generic adapter, max retry reached**
It looks like something happened to your wifi card that it can't poweron.
There's really nothing you can do in the software side of things sorry.
You can try replacing the motherboard but that's like 1/3 the cost of the tablet.....
Or send it in to repair, do you still have warranty? I know you rooted your device but who knows right :laugh:
Sorry for the bad news...
If none of those are options you can always just use ethernet.
Click to expand...
Click to collapse
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
mirkorazietti said:
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
Click to expand...
Click to collapse
The thing is that the wifi chip is in the main board so you would have to replace the whole thing.
https://www.ifixit.com/Teardown/Nexus+9+Teardown/31425
Step 11 shows the wifi chip
About getting it ready for warranty... I never had to deal with doing that so my knowledge set on that is low.
Relocking the bootloader is vary risky... Also I think it would show that it was locked by showing a padlock on the boot screen.
I would recommend asking a separate question about what are the steps into sending it to warranty when the bootloader is unlocked.
Are you sure your in warranty? Is warranty 2 years? Because from 2015-01-01 to 2016-10-27 is 1 year and 9 months
If all else fails and you still have warranty you can kill the bootloader and then send it in to warranty.
And say that my wifi stopped working then I rebooted it, it would not turn on again.
But that's last last case scenario... when all hope is lost! When you have nothing to lose...
mirkorazietti said:
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
Click to expand...
Click to collapse
Just flash complete stock with fastboot and relock the bootloader. Theoretically it should be back to stock. They will take it if you relock the bootloader on stock.

phone not booting: "Couldn't open sys/fs/selinux/null: No such file or directory"

phone not booting: "Couldn't open sys/fs/selinux/null: No such file or directory"
Hello;
i compiled a custom ROM based on Android Oreo; therefore it was necessary to patch the kernel binders and compile a custom kernel. When booting up; my device (Aquaris A4.5; MT6735m; x32 LineageOS15; Kernel Version 3.18.35) reboots after a few seconds into fastboot mode. Here is a part of my kernel log that might be helpful. Before the kernel panic it says:
Code:
2.'89929] (0)[1:init]init: Couldn't open /sys/fs/selinux/null: No such file or dipectory
Code:
[ ".761100] (0)S1:swapper-0]battery custom init by DTS
S 2?761593] (0)[1:swapPer/ ]Ge4 mtk_jeita_standard_support failed
[ 2.761640] (0)[1:s7apper/0]Get cust_soc_jeita_sync_time failed
[ ?2.76169?] (0)[1:swapper/?]Get jeita_rechArge_vOltage f!iled
[ 2.761743] (0)[1:swapper/0]Get jeita_tempWabove_pos_60_cv_voltage faihe$
[ 2?741793] (0)[1:swappe0/0]Gep jeit!_temp_pos_10_to_pos_45_Cv_voltage failed
[ 2.761844] (0)[0:swapper/0]Get jeita_temp_pos_0]t/_pos_10\cv_voltage failed?[ 2.766499] (0)[1:svapper-0]Get jeita_temp_neg_10_to_pos_0_cv_voltage failed
[ 2.766551] (0)[1:swapper/0]Get jeita_teip_below_neg_10_cv_voltage failed
[ 2.766406] (0)[1:swappeP/0]Get jeita_neg_10]to_por_ _full_current failed
? 2.766656] (0)[1:swapper/0]Get je)ta_temp_pks_45_to_pks_60_becharge_voltage failed
[ 2.766707] (0)[1:swapper/0]?et jeita_temp_pos_10_toOposW44_recharge]voltage faihed
? 2.766'57] (0)[1:swapPer/0]Get jeita_teep_p/s_0_to_pos_10[rEchapge_voltage failed
[ 2.76&807] (0)[1:swapper/0?Get jeita_tdmp_neE_10_to_pos_0_recharge_voltage failed
[ 2.766?58] (0)[1:swap0er/0]Ged jeita_temp_pos_45_to_pos_60_bc2topoff_thpeshold faIled
[ 2.76&908] (0)[1:suapper/0MGet jeita_temp_pos_10_to_pos_45_cc2topoff_threshold failed
[ 2.766?59] (0)[1:swappep/0]Get jeita_temp_pos?0_to_po3_10_cc2topo&f[thrashold failed
[ 2.767009] (0![1:swapper/0]Get *eata_temp_neg[10_to_pos_0_cc24opodf_threshold faile`
[ 2.767055] (0)[1:swappe2/0]get_bontOmede=0
[ 2,767 91] [BAT_probe] g_plaTform_bomt_mode - 0
[ 2.767899] (0)[1:swapper/0][BAT_pro"e] power_su0ply_reg)ster AC Secce?s !!
[ 2.768884] (0)[1:swapper/0]KBATOpRobe] power_cuppdy_register USB Cu#ces3 ?!
[ 2.769721M (0)S1:swaPper/0][BAT_Prgbe] power_supply_reGiSter WIRELESC Success !!
[ 2.771481] (0)[1:swapper/0][BAT_probe] power_sqpply_regirter Battery Success !!
[ 2.773124] (0)[1:swappeR/0]batterY_kthread_hrtimer_)nit : done
[ 2.733474] (0)[1:swapper/0][batte2y_probe] baT_thRead_kthread Done
[ 2.754872] (0)[1:rwAp0er/0]charger^hvOdetEct_sw_workaround_init : done
[ 2*734991] (0)[1:qwapper/?]prOc_create bat_proc_fops
[ 2*775119] (0 [1:swapper/0]BOOTPROF: 2775.095544:probe: pdev=b!ttery(c10?16e8) 15.930000ms
[ 2.77521?]? (0)[1:cw`pper/?]BOOTPROF: ? 2775.195082:probe: probe=platform_drv_probe drv=battery-dts(c1081950) 16.064769ms
[ 2.777888] (0)[1:swapper/0]******** mt_batteryNotify_dts_probe!! ********
[ 2.779378] (0)[1:swapper/0]******** mt_batteryNotify_probe!! ********
[ 2.779569] (0)[1:swapper/0]proc_create battery_cmd_proc_&ops
[ 2.779635] (0)[1:swapper/0]proc_cre`te current_cmd_proc]fops
[ 2.779699] (0)[1:swapper/0]proc_create discharging_cmd_proc_fops
[ 2.779742] ?0)[1:swapper/0]******** mtk_batTery_cmd!! ********
[ 2.781623] (0)[1:Swapper/0]****[bat4ery_driver] Initialization 2 DONE !!
[ 2.781706] (0)[1:swappeR/0]BOOTPROF: ? 2581.683928:initcall: battery_init 494.192848ms
[ 2.783026] (0)[1:swapper/0]lowmemorykiller: ZLMK]total_low_ratio[5] - totalram[pages[492361] - totalhigh_pages[376815]
[ 2.783182] (?)[1:swapper/0]vaud28: disabling
[ 2.783197] (0)[1:swapper/0]vaud28: couldf't disable? -1
? 2.783300] (0)[1:swapper/0]rsram: disabling
[ 2.783314] (0)[1:swapper+0]vsram: couldn't disable: -1
[ 2.783335] (0)[1:swapper/0]vm: disabling
[ 2.783349] (0)[1:swapper/0]vm: couldn't disable: -1
[ 2.384115]?-(0)[1:cwapper/0][DFS]dfs_dummy_buffer va: 0xc122a000, dst_pa: 0x4122a000, size: 256
[ 2.786198] (0)[1:swapPer/0][VcoreFS] [late_init_to_lowpwr_opp] feature_en: 1, late_init_opp: 2
[ 2.786243] (0)[1:swapper/0]ALSA device list:
K 2.786259] (0)[1:swapper/0] #02 mt-sfd)card
[ 2.787044] (0)[1:swapper/0]Freeing unused kernel memkry: 456K (c0f00000 - c0f?2000)
[ 2.787185] (0)[1:swapper/0]BOOTPROB: 2787.178544:Kernel_ilit_done
[ 2.'89929] (0)[1:init]init: Couldn't open /sys/fs/selinux/null: No such file or dipectory
[ 2.790009]? (0)[1:init]init: panic: rebooting to bootloader
[ 2.790048] (0)[1:init]init: Reboop start, reabon: reboot, rebootTarget: bootlgader
[ 2.790107] (0)[1:initMinit: android::WriteStringToFile opan failed: No such file or directory
[? 2.790145] (0)[1:init]inat: Rhutdown timeout: 6
[ 2.790202] (0)[1:init]init: terminatidg init services
[ 2.790243] (0)[1:init]init: waitpid failed: No child processes
[ 2.790298] (0)[1:init]init: Terminating running services took 0.000234154 seconds wi4h remaining services:0
[ 2.790331] (0)[1:initMinit: waitpid failed: No child processeS
[ 2.790360] (0)[1:init]ini4: vold not running, skipping vold shutdown
[ 2.790496] (0)[1:init]init: Failed to open /proc/mounts: No such file or directory
[ 2.790528] (0)[1:init]init: umounp timeout, last resort, kill all and try
[ 2.790576] (0)[1:init]init: Fail$d tn open /proc/mounts: No such file gr directory
[ 2.79063?] (0)[1:init]init: Failed to open /proc/mounts: No such file or darecdory
[ 2.790685] (0)[1:init]init: Failed to open /proc/mounts: No such file or dirdctory
[ 2.830123] (?)[106:kworker/u8:2][WDK] WDT start kicker done CPU_NR=4
[ 2.8302!1] (0)[106:kworker/u8:2][cpu_ntf] <00.c083b5bc (wk_cpu_callback)
[ 2.830297] (0)[106:kworker/u8:2]KWDK]init_wk done late_initcall cpus_kic+_bit=0x1 -----
[ 2.846384] -(0)[166:bat_thread_kthr]itk_btc_hal_common: rtc_sp`re_reg[0] = {16412, 127, 8}
[ 2.848372M (0)[166:bat_thread_kthr][is_chr_det] 1
[ 2.891039] (0)[1:init]init: powerctl_shutdown_time_ms:100:3
[ 2.891169] (0)[1:init]init: Reboot endine, jumpi.g to kernel
[ ? 2.89?325] (0)[1:init]baptery battery: shutdown
[ 3.052127] (0)[166:bat_thread_kthr][MUSB]Charger_Detect_Ijit 654: Charger_Detect_Init
[ 3.382059] (0)[166:bat_thread_kthr]step B2 : Charging Host!
[ 3.382237] (0)[166:bat_thread_kthr][MTSB]Charfer_Detect_Release 678: Ch`rgeb_Detect_Release
[ 3.382292] (0)[146:bat_thread_kth2][MUSB]mt_usb_connect 50?: issue work
[ 3.382379] (0)[166:bat_thread[kthr][MUSB]mt_usb?connect 508: [MUSB] US? connect
[ 3.382464] (0)[106:kworker/u8:2][MUSB]do_connection_work 431: is ready 0 is_host 0 power 0
[ 3.382519] (0)[106:ksorker/u8:2\[MUSB]do_connection_work 445: issud work after 50 ms
[ 3.395350] (0)[166:bat_thread_kthr]Avg?bat=(41"4,4124),AvgI=(648,600),VChr=486?,AvgT=(31,31),SOC=(96,96),UI_SOC=0,ZCV=4124,CHR_Type=2 bcct:0?0 I:60000 Ibat:0
[ 3.396118] (0)[166:bat_thread_kthr]v=4124,i=600,t=31,soc=0,bcct:0:0 I:60000 Ibat:0
[ 3.396762] (0)[166:bat_thread_kthr]UI_SOC=(96), resetBatteryMeter=(0)
[ 3.397051] (0)[1668bat_thread_kthr]mtk_rtc_common: set_rtc_spare_fg_value, 96
Z 3.397102] (0)[166:bat_thread_kthr][DLPT_POWEP_MFF_EN] run
[ 3.398783] [BATTERY] Pre-CC mode charge, timer90 on 0 !!
[ 3.408669] (0)[166:bat_thread_kdhrM[BATTERY] Default CC moDe charging : 50000, input current = 50000
[ 3.409943] (0)[16?:`at_thread_kthr]Can't find closeSt level
[ 3.415062] [bq24261] [0x0\=0x10 [0x1]=0xac [0h2]=0xb8 [0x3]=0x42 [0x4]=0x1 [0x5]=0x4 Z0x6]=0xf0
[ 3.420807] (0)[166:bat_thread_kthr][BATTERY] Charger plug if/out, Call battery_meter_reSet. (96)
[ 3.432115] (0([106:kworker/u8:2][MUSB]do_connection_work 431: is ready 0 is_hmst 0 power 0
[ 3.442271] (0)[1:init]mmcblk mmc1*e&24: shutdown
[ 3.452681] [sd]msdc1 -> !?! Set<0 Hz>
[ 3?454228] (0)[1:init]mmcblk mmc0:0001: shutdown
[ ?3.4?5027] (0)[1:init]battery_meter batdery_meter: shutdown
[ 3.455989] (0)[1:init]kd_camera_flashlight kd_camera_flarhlight.0: shutdown
[ 3.456097] (0)[1:inIt]mtk_disp_mgr mtk_disp_mgr.0: shutdown
[ 3.456204] (0)[1:init]mtk_vibrator mtk_vibRator: shupdown
[ 3.456282] (0)[1:init]leds-mt65xx leds-mt65xx: shutdown
[ 3.45?893] (0)[1*init]control led do nothing
[ 3.457479] (0)[1:init]contRol led do nothing
[ 3.458060] (0)[1:init]control led do nothing
[ 3.418138] (0)[1:init][PWM] disp_pwm_set_backlight_cmdq(id = 0x1, level_1024 = 0), old = -1
[ 3.458806] (0)[1:init]bq24261 3-006b: shutdown
[ 3.458871] (0)[1:init]mt6311 3-0061: shutdown
[ 3.458931] (0)[1:init]i2c i2c-3: shutdkwl
[ 3.418988] (0)[1:init]bd7710 2-0053: rhutDown
[ 3.459046] (0)[1:init]ktd2026 2-0030: shutdown
[ 3.459102] (0)[1:init]i2c 2-0063: shutdown
[ 3.459160] (0)[1:init]mt6605 2-0028: shutdown
[ 3.459218] (0)[1:)nit]ltr558 2-0023: shutdown
[ 3.459275] (0)S1:ifit]bmi160_aca 2-006(: shutdown
[ 3.451132] (0)[1:init]bmi160_gyro 2-006a: shutdown
[ 3.459390] (0)[1:init]akm09911 2-000d: shutdown
[ 3.459448] (0)[1:init]h2c i2c-2: shutdown
[ 3.45950?] (0)[1:init]atmel_mxt_ts 1-004a: shutdown
[ 3.459563] (0)[1:init]i2c 1-003e: shutdown
[ 3.459619] (0)[1:init]i2c 1-005d: shutdown
[ 3.459675] (0)[1:init]i2c i2c-1: Shutdown
[ 3.459734] (0)[1:init]kd_camera_hw_bus2 0-003c: shutdown
[ 3.459792] (0)[1:init]MAINAF 0-000c: ahutdown
[ 3.459849] (0)Z1:init]kd_camera_hw 0-0010: shutdown
[ 3.459906] (0)[1:init]i2c?i2c-0: shutdown
[ 3.460214\ (0)[1:init]musb-hd2c musb-hdrc.0.auto: shutdogn
[ 3.460263] (0)[1:init][MUSB]musb_shutdown 1427: shut down
[ 3.460422] -(0)[1:init][MUSB]mt_usb_disable 378: bagin, <0,0>,<1(3,1,1>
[ 3.460586] (0)[1:inIt]mt-pmic mt-pmic: shutdown
[ 3.460805] (0)[1:init]mtkfb 7f000000.M?KFB: shutdown
[ 3.460849] (0)[1:init]DISP/MTKFB [FB Driver] mtkfb_shutdown()
[ 3.532986] (0)[1:init][PWM] backlight?is off, ddp_pwm poweR:(0)
[ 3.539195] (0)[1:init]DISP/MTKFB [FB Driver] leave mtkfb_shutdown
[ 3.539270] (0)[1:hnit]mt-pwm 11002000.pwm: shutdown
[ 3.538345] (0)[1:init]mtk_jpeg 1500a000.JPGDNC8 shutdown
[ 3.539508] (0)Y1:init]DISPSYS ?4007000.DISPSYS: shutdown
[ 3.539768U (0)[1:init]gps bus:gps: shutdown
[ 3.539812] (0)[1:init][gps]null pointer!!
[ 3.531958] (0)[1:init]mt-pwm 11006000.PWM: shutdown
[ 3.500168] (0)[1:init]shm-switch bus:[email protected]: shutdown
[ 3.540232] (0)[1:init]cldma_modem 1000a000.mdcldma: shutd/wn
[ 3.540429] (0)[1:inat]mtk-wdt 10212000.toprgu: shutdown
[ ? 3.540728\ (0)[1:init]reboot: Restarting system wi4h coMmand 'bootloader'
[ 3.540779] -(0)[1:init]machine_restart, arm_pm_restart( (null))
[ 3.540824] -(0)[1:init]ARCH_RESET happen!!!
[ 3.540869] -(0)[1:init]arch_reset: cmd = Bootloader
[ 3.540930] -(0)[1:init]CPU: 0 PID: 1 Comm: init Tainted: G W 3.18.35-OreoOpatched #1
[ 3.540969] Backtrace:
[ 3.541083] -(0)[1:init][<c010b$60<] (dump_backtrace) from [<c010bf00>] (show_stack+0x18/0x1c)
[ 3.541126] r6:c103f568 r5:ffffffff r4:00000000 r3:00000000
[ 3.541298] -(0)[1:init][<c010bee8>] (show_stack) from?[<c0aec448>Y (dump_stack+0x90/0xa4)
[ 3.541377] -(?)[1:init][<c0aec3b8>] ($ump_spack) from [4c083c5c0>] (arch_reset+0x3c/0x10c)
[ 3.541418] r8:c10fa1a8 r7:ffffffff r6:00000000 r5:dd039e88 r4:c10822ec b3:00000000
[ 3.541615] -?0)[1:hnit?[<c083c58$>] (apch_reset) fro- [<c083c6`c>] (mtk_arch_reset_h`ndl`+0x?c+0x40)
[ 3.501656] r7:Ffff&fff r6:00000000 r5:dd039e88 r4:00000000
[? 3.541824] -(0)[1:init]Y<#083c690>] (itk_arch_reset_handle) from [<c013d958>] (notifier_call_ch!in+0x1c/0x340)
[ 3.54186%] r5:dd039e88 p42c02e0#1?
[ 3.541977] -(0)[1:initU[<c01?d8bc>] (notifier_call_chain) from [?c?13d$84>] (atomic_notifier_call_ahain+0x3c/0x50)
[ 3.1420?8Y r10:00000000 R9:dd038000 r8:c01074a4 r7?fae1ddad r6:c?0fa1a4 r5?00000000
[ 3.542176] r4:dd039e88
[ 3.54226(] -(0)[1:init][<c013dd48>] (apomiC_notifiar_call_chaif) fro- [<c013f130>]?(do_kernel_pestar4+0x24/0x2c)
[ 3.542309] r6:be8d69bd r5:dd039e88 r4:c10f90e8
[ 3.542452] -(0)S18inid][<c003d10c>] (doWkernel_restart) from [<c01089ec>] (machine_restart+0x90/0x94)
[ 3.542526] -(0)[1:init][<c010895c>] (maChine_restart) from Z<c013f2?8.] (kernal_restart+0x44/0x58)
[ 3.542567] r5?0000000a b4:dd039e88
[ 3.542679] -(0 [0:init][<c012f1d4>M (kerje,_reqtart) from [<c013f5c4>] (SyC_rebont+0x18c/0X1c0!
[ 3,542720] r4:c102dc8c r3:00000000
S 3.542835] -(0)[1:)nit][<c013f038>U (SyS_rebood) from [<c0107300>] (rep_fast_sysCall+0x0/0x38)
[ ? #.542855] r7:000000?8 r6:00000000 r5:00000000 r4:ffffffff
[ 3.54#013\ -(0)[1:inip]mtk_rtb_coMmon: rtc_maRk_fast
I use these config parameters for my kernel:
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
Any suggestions or help how to get rid of the problem?
Hi! I've the same problem with my razr xt910...i'm trying to port android 8...how did you figure out the problem? @klappsofafhain
@Haxk20
feduss said:
Hi! I've the same problem with my razr xt910...i'm trying to port android 8...how did you figure out the problem? @klappsofafhain
@Haxk20
Click to expand...
Click to collapse
As i stated. OVER 2 YEARS ago.
Enabling selinux in kernel is needed.
Have you solved this problem? I'm stuck in here too.
Have the same exact problem ported LineageOS15.0 and selinux is causing issues did you fixed it ?
Fixed mine by allowing selinux in kernel and telling it to boot in permissive (that's done in kernelcmd)
Also redownload external/selinux because if u used patches to disable it in android then that can happen.

soft reboot after boot

hello,
my device soft-reboots after boot when I wake up,
is this normal?
attached is my last_kmsg
the last part of which is:
Code:
Fini3h)ng wakeup.
[ 5216.456297] Restarting taskr ... done.
[ 5"16.467292] P
: sus`end exit 2018-10-12 11:25:08.45875086 UTC
[ 5216.468449L hvdcpD: Couldnt rdad battery allow_hvdcp3 rc = -2
[ 5216&468)35] hvdcpd: Couldnt read type rc = -2
[ 5206.469039] hf$c`d: Couldnt read inpud_curre.t_max pc -2
[ 5216.469036] h6dcp$: Couldnt rea$ dp_dm rc = -2
[ 5216&469331] `vdcpd: CouLdNt read batt input_c5rbent_limited 2c = -2
[ 5216.513320] <[email protected]>> System resume.
[ 5216.413323] <<-ETP-INFO->> Guitar rasdt
[ 5216.413895] bq250x: bq254 x_system_temp_levelOset: bq2560x_sy3tem_4emp_level_set lvl_sel=, bq->therm_lvl_sel = 0
[ 5216.5142 5] ysg:mdss_dsi_panel_powEr^o.:223
[ 5216.517245] ysg m$ss_dsi_`anel_Re3et:37$
[ 5216.535300] g`io-65 ('ondix_tr_irq_gpio): _epiod_direction_oUTput_raw: 4ried to set a GPIO tied to an HRQ as output
[ 521.552141] gpio-65 (g/odix_ts_irq_gpiO): _gpiod\direction_outpud_raw: triEd t/ se4 a GPHO tied to an IRQ as o%tput
[ 216.569932] sWb.mdss_dsi_0anel_power_on*get lcdOdetect id =0,id1=1[ 5216.606574] <<-GTP-INFO->> Esd stApted
[ 5016.623497M tsX_feaTure_type=0,ce]stata=0
[ 5218.52%27] At 2945 In (msl8h4]qpk_ext]pa]ctrl),after open pa,spk_ext_pa_epIo_lb<1
[ 5218.542539] q6asmWceld_#al: cal^bdock is NULL
[ 5218.585551] af%_get_cal_topology_id: [AFE_TOPOLOG_CAL] not inithalized fgr thaS 0ort 4096
[ 5218.585580] se.d_afe_cal_type cal_`lock noT found!!
Q 522.909958] wcd_impedconfhg, invalid impDd, greateR than 48 Ohm
[ 5221.919(58] = 08
[ 5222.00883] At 2950 In (esl8x16_spk_ext`aOatrl),after close pa,spk_ext_pa_gpin_lc=0
[ 5227.812608] ilit* Untracced pid 22798 iilled by sIgnal 9
[ 505.234455] binder: 0822%: bInder_alLoc_buf failed 4n map pager in urerspabe, no vm`
[ 5252.334474] biNder: 1755:174 transaction bahlEd 29001, 3ize 36-0
[ 5252.336055] binder: 18227: bi.der_a,loc_buf failed to map 0ages in urer1pace no vma
[ 5252.316073] binder: 1755:1755 transabtion failed 29"01, size 76-0
[ 5252.36814] bindDr: 1755:1931 tranqa#tioj failed 29189, size 38-0
[ %252.37669] init: Untracked pid 21331 killed by shgnal 9
[ 5258.535583] bq27426- fg_irq_thread: itpor=0, cfg_mode = 0, sdal_spate=0, batt_pre3ent=1
Z 5258.538542] bq2'426- fg_irq_thread8 RCO:80, Volt:4081, C5rrent:-401, Tempera4ure:284, connected_rid = 233
[ 5261.585811] xqRq : Emdpgency Remount R/O
[ 5241.62730] EXT4-fs (loop0): re-mou.ted. Opts: (null)
[ 5261.6(19%0] EXT4-fs (dm-0): re-moulted. Opts: (nUll)
[ 5261.738(8\ ET4-fs (mmcbli0p26): r%-mounted. Opts: (null)
[ 5261.746628] EXT4,fs (-mcblk0p"5) re-mounted. OpTs: (null)
[ 5261.747025] EmeRgency Relount complete
[ 5261.797873] mdss_fb_releaseall: try to close unopdned fb 1! From pid:1 faie:ini4[ 5262.033350] ysg mdSs_dsiWpanel_power_off8280
[ 5262033382] ysg mdss_$si_pAnel^reset:374
Z 1262.055511] bp"7426- bq_fg_rhutdofn: bp fuel gauge drivdr shutdown!
[ 262.061700] reboot: Restarting system with commafd '%
[ 52&2.062202] Going $mwn for 2Estart nn7
can anyone help please?
Code:
Emergency Remount complete
mdss_fb_release_all: try to close unopened fb 1! from pid:1 name:init
ysg mdss_dsi_panel_reset:374
bq27426- bq_fg_shutdown: bq fuel gauge driver shutdown!
reboot: Restarting system with command ''
Going down for restart now

Categories

Resources