Stuck acter flash rom - Moto Z Questions & Answers

Hello,
My moto Z is stuck un bootloop after I flash it with a ROM STOCK.
Here is the log during the first boot:
HTML:
<6>[ 23.468352,0] Report pwrkey release event at: 1970-01-01 19:48:05 UTC
<6>[ 23.674478,3] F2FS-fs (sda20): Magic Mismatch, valid(0xf2f52010) - read(0xb2447253)
<3>[ 23.674490,3] F2FS-fs (sda20): Can't find valid F2FS filesystem in 1th superblock
<6>[ 23.674656,3] F2FS-fs (sda20): Magic Mismatch, valid(0xf2f52010) - read(0xc83920b4)
<3>[ 23.674662,3] F2FS-fs (sda20): Can't find valid F2FS filesystem in 2th superblock
<6>[ 23.674672,3] F2FS-fs (sda20): Magic Mismatch, valid(0xf2f52010) - read(0xb2447253)
<3>[ 23.674677,3] F2FS-fs (sda20): Can't find valid F2FS filesystem in 1th superblock
<6>[ 23.674682,3] F2FS-fs (sda20): Magic Mismatch, valid(0xf2f52010) - read(0xc83920b4)
<3>[ 23.674686,3] F2FS-fs (sda20): Can't find valid F2FS filesystem in 2th superblock
<3>[ 23.674940,3] EXT4-fs (sda20): VFS: Can't find ext4 filesystem
<6>[ 25.799356,0] EXT4-fs (sda19): mounted filesystem with ordered data mode. Opts:
<7>[ 25.799383,0] SELinux: initialized (dev sda19, type ext4), uses xattr
How can I do to unstuck it?

What & how did you flash exactly?
Do you have locked or unlocked bootloader?

Related

Hack your S3 Mini with the serial port

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

[Q] rendering chrooted xorg uising /dev/graphics/fb0

Hey
i got archlinux chroot which works with vnc and I'm really interested in trying to use xorg on /dev/graphics/fb0. But i have no luck at my attempts.
blog.rot13 org/2012/08/x11-running-on-nook-color-without-android-stack.html
i also shutdown android stuff with
Code:
adb shell setprop ctl.stop media
adb shell setprop ctl.stop zygote
adb shell setprop ctl.stop surfaceflinger
adb shell setprop ctl.stop drm
and then i use xinit, startx through ssh, and adb but they both stop at the same level:
Code:
[ 10635.484]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 10635.486] X Protocol Version 11, Revision 0
[ 10635.486] Build Operating System: Linux 3.2.34-2-FARM armv7l
[ 10635.487] Current Operating System: Linux localhost 3.0.8+ #290 PREEMPT Sat Apr 28 21:08:11 CST 2012 armv7l
[ 10635.487] Kernel command line: console=ttyS0,115200 rw init=/init loglevel=8
[ 10635.489] Build Date: 18 April 2013 12:09:06AM
[ 10635.489]
[ 10635.491] Current version of pixman: 0.28.2
[ 10635.493] Before reporting problems, check
to make sure that you have the latest version.
[ 10635.493] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 10635.496] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 8 20:00:35 2013
[ 10635.498] (==) Using config file: "/etc/X11/xorg.conf"
[ 10635.499] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 10635.499] (==) No Layout section. Using the first Screen section.
[ 10635.500] (==) No screen section available. Using defaults.
[ 10635.501] (**) |-->Screen "Default Screen Section" (0)
[ 10635.501] (**) | |-->Monitor "<default monitor>"
[ 10635.501] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 10635.502] (**) | |-->Device "Allwinner A10/A13 FBDEV"
[ 10635.502] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 10635.502] (==) Automatically adding devices
[ 10635.502] (==) Automatically enabling devices
[ 10635.502] (==) Automatically adding GPU devices
[ 10635.502] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 10635.502] Entry deleted from font path.
[ 10635.502] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 10635.502] Entry deleted from font path.
[ 10635.502] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 10635.502] Entry deleted from font path.
[ 10635.502] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 10635.502] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 10635.502] Entry deleted from font path.
[ 10635.502] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 10635.502] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 10635.502] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 10635.502] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 10635.503] (II) Loader magic: 0x1c0698
[ 10635.503] (II) Module ABI versions:
[ 10635.503] X.Org ANSI C Emulation: 0.4
[ 10635.503] X.Org Video Driver: 14.1
[ 10635.503] X.Org XInput driver : 19.1
[ 10635.503] X.Org Server Extension : 7.0
[ 10635.504] Initializing built-in extension Generic Event Extension
[ 10635.505] Initializing built-in extension SHAPE
[ 10635.505] Initializing built-in extension MIT-SHM
[ 10635.506] Initializing built-in extension XInputExtension
[ 10635.507] Initializing built-in extension XTEST
[ 10635.507] Initializing built-in extension BIG-REQUESTS
[ 10635.508] Initializing built-in extension SYNC
[ 10635.508] Initializing built-in extension XKEYBOARD
[ 10635.509] Initializing built-in extension XC-MISC
[ 10635.509] Initializing built-in extension SECURITY
[ 10635.510] Initializing built-in extension XINERAMA
[ 10635.510] Initializing built-in extension XFIXES
[ 10635.510] Initializing built-in extension RENDER
[ 10635.511] Initializing built-in extension RANDR
[ 10635.511] Initializing built-in extension COMPOSITE
[ 10635.511] Initializing built-in extension DAMAGE
[ 10635.512] Initializing built-in extension MIT-SCREEN-SAVER
[ 10635.512] Initializing built-in extension DOUBLE-BUFFER
[ 10635.512] Initializing built-in extension RECORD
[ 10635.512] Initializing built-in extension DPMS
[ 10635.512] Initializing built-in extension X-Resource
[ 10635.512] Initializing built-in extension XVideo
[ 10635.512] Initializing built-in extension XVideo-MotionCompensation
[ 10635.512] Initializing built-in extension XFree86-VidModeExtension
[ 10635.513] Initializing built-in extension XFree86-DGA
[ 10635.513] Initializing built-in extension XFree86-DRI
[ 10635.513] Initializing built-in extension DRI2
[ 10635.513] (II) LoadModule: "glx"
[ 10635.514] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 10635.515] (II) Module glx: vendor="X.Org Foundation"
[ 10635.515] compiled for 1.14.1, module version = 1.0.0
[ 10635.515] ABI class: X.Org Server Extension, version 7.0
[ 10635.515] (==) AIGLX enabled
[ 10635.515] Loading extension GLX
[ 10635.515] (II) LoadModule: "sunxifb"
[ 10635.516] (II) Loading /usr/lib/xorg/modules/drivers/sunxifb_drv.so
[ 10635.516] (II) Module sunxifb: vendor="X.Org Foundation"
[ 10635.516] compiled for 1.14.1, module version = 0.3.1
[ 10635.516] Module class: X.Org Video Driver
[ 10635.516] ABI class: X.Org Video Driver, version 14.1
[ 10635.516] (II) SUNXIFB: driver for framebuffer: sunxifb
[ 10635.517] (--) using VT number 2
my xorg.conf:
Code:
# This is a minimal sample config file, which can be copied to
# /etc/X11/xorg.conf in order to make the Xorg server pick up
# and load xf86-video-sunxifb driver installed in the system.
#
# When troubleshooting, check /var/log/Xorg.0.log for the debugging
# output and error messages.
#
# Run "man sunxifb" to get additional information about the extra
# configuration options for tuning the driver.
Section "Device"
Identifier "Allwinner A10/A13 FBDEV"
Driver "sunxifb"
Option "fbdev" "/dev/graphics/fb0"
EndSection
same goes with fbdev and sunxifb drivers i tried.
i can't find the reason it stops.
dd if=/dev/urandom of=/dev/graphics/fb0 does work.
and yeah i tried googling :\
thanks for helpers!

[Q] External Wi-Fi USB adapter

Hello, guys! I've already posted this in Nexus 5 section but nobody answered. As far as I suppose that this question is not very device specific I've decided to ask it once again here.
I got Nexus 5 running vanilla AOSP Android 4.4.3 compiled by myself. It works like a charm. I would like to use external Wi-Fi USB adapter with my Nexus 5. I've tried to use AWUS036NHA (with Atheros AR92721 chip) and two other models from different vendors. Every time I get the same error.
So, what have I done? I've rebuilt kernel to add support for my devices (in usual Linux way) and added firmwares they need to /vendor/firmware. When I plug AWUS036NHA into my phone I get the following (dmesg):
Code:
<6>[ 1587.856305] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1587.887070] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
<6>[ 1587.887129] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[ 1587.887221] usb 1-1: Product: UB91C
<6>[ 1587.887273] usb 1-1: Manufacturer: ATHEROS
<6>[ 1587.887365] usb 1-1: SerialNumber: 12345
<4>[ 1587.887857] usb 1-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888693] usb 1-1: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888968] usb 1-1: ep 0x5 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.889115] usb 1-1: ep 0x6 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1587.890044] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
<6>[ 1588.180755] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
<6>[ 1588.416902] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
<6>[ 1588.644279] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
<7>[ 1588.644345] ath: EEPROM regdomain: 0x833a
<7>[ 1588.644351] ath: EEPROM indicates we should expect a country code
<7>[ 1588.644360] ath: doing EEPROM country->regdmn map search
<7>[ 1588.644367] ath: country maps to regdmn code: 0x37
<7>[ 1588.644374] ath: Country alpha2 being used: GB
<7>[ 1588.644379] ath: Regpair used: 0x37
<6>[ 1588.648677] ieee80211 phy3: Atheros AR9271 Rev:1
<7>[ 1588.650804] Registered led device: ath9k_htc-phy3
It seems to me that everything here is ok. But when I try to switch on the adapter (ifconfig wlan1 up) I get an error (dmesg):
Code:
ADDRCONF(NETDEV_UP): wlan1: link is not ready
By the way, "ifconfig" command shows no error, but it doesn't swith my device on.
So, I got the same error with 3 different adapters. I got no idea about possible ways of solving this problem.
Please, share your ideas, I'm really stuck Looking forward for your help. And thanks in advance!

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

AOSP boot fails: failed to read fstab from dt

I am currently trying to build AOSP for the Hikey 970 development board (I am not allowed to post the link to the guide).
Building succeeds, but during booting, there seems to be an issue with fstab, which prevents the device from booting properly:
Code:
...
[ 5.748555] init: init first stage started!
[ 5.752941] init: [libfs_mgr]dt_fstab: Processing partition vendor
[ 5.79152] init: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 5.766463] init: [libfs_mgr]dt_fstab: Processing partition system
[ 5.772678] init: [libfs_mgr]dt_fstab: Skip disabled entry for partition system
[ 5.780000] init: [libs_mgr]ReadFstabFromDt(): failed to read fstab from dt
[ 5.787095] init: [libfs_mgr]dt_fstab: Processing partition vendor
[ 5.793289] init: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 5.800600] init: [libfs_mgr]dt_fstab: Processing partition system
[ 5.806793] init: [libfs_mgr]dt_fstab: Skip disabled entry for partition system
[ 5.814588] kvm: exiting hardware virtualization
[ 5.819423] hifi_misc [I][364638]:hifi_reboot_notifier:1378: reboot +.
[ 5.825950] hifi_misc [I][364852]:hifi_reboot_notifier:1387: reboot -.
[ 5.833832] sd 0:0:0:3: [sdd] Synchronizing SCSI cache
[ 5.839301] sd 0:0:0:2: [sdc] Synchronizing SCSI cache
[ 5.844710] sd 0:0:0:1: [sdb] Synchronizing SCSI cache
[ 5.850109] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 6.021721] reboot: Restarting system with command 'bootloader'
...
(system reboots)
(The lines "Processing partition ..." have been added by me to the function read_fstab_from_dt in fs_mgr_fstab.cpp to see if there are any other partitions besides vendor and system.)
I also tried modifying the device tree kirin970-hikey970.dts according to changes suggested in another forum (96boards: "Filesystem not available"), but that did not change the observed error.
I am new to AOSP and don't know which direction to continue searching:
Should there be other partitions except vendor and system?
Is it correct behavior that these partitions are skipped (disabled entry)?
I appreciate your suggestions.
did u manage to fix this ? i have the same issue

Categories

Resources