Database Info

[DEV] Discussion about USB-TTL UART JIG

Hey all,
I've created this thread to gather all the info and doubts about UART JIG (also so <I> don't pollute OpenFIMG's thread ).
Readings of interest:
Fun with resistors
Setup in a Nexus S (with pictures)
UART / Serial / JTAG
Odd serial port on Spica (samdroid)
Galaxy S UART JIG & Debugging connector
Developing methods to recover bricks without JTAG
Kernel serial console on i9100
UART Output / Bootloader Hacking / Kernel debugging
Configuration:
Vcc (Pin 1) -> Disconnected.
D- (Pin 2) -> RXD.
D+ (Pin 3) -> TXD.
ID (Pin 4) -> Connected to GND with 523k ohm attached.
GND (Pin 5) -> GND
Baud rate: 115200, 8N1. No control flow.
Boot from the SBL:
Code:
SBL>loadkernel
SBL>loadmodem
SBL>boot
How to get output from kernel.

tom3q said:
<Quote Snipped>.
Click to expand...
Click to collapse
Awesome. Thanks donator!
You've got the uart jig there? Can you test it? (I'm not getting any output.. not [X]BL, nor kernel)

moikop said:
Awesome. Thanks donator!
You've got the uart jig there? Can you test it? (I'm not getting any output.. not [X]BL, nor kernel)
Click to expand...
Click to collapse
This is what I get from the serial port of G3:
Code:
Secondary Boot Loader(SBL)
Built for apollo rev02 by root on Oct 27 2010 17:10:33
Copyright (C) SAMSUNG Corporation 2006-2010
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 10
partitions loading success
==== PARTITION INFORMATION ====
ID : IBL & PBL (0x0)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : SBL (0x1)
ATTR : RO ENTRYPOINT SLC BOOTLOADING PREWRITING (0xd402)
FIRST_UNIT : 1
NO_UNITS : 5
===============================
ID : PARAM (0x2)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 6
NO_UNITS : 2
===============================
ID : EFS (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 8
NO_UNITS : 32
===============================
ID : KERNEL (0x4)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 40
NO_UNITS : 30
===============================
ID : FACTORYFS (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 70
NO_UNITS : 880
===============================
ID : DATAFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 950
NO_UNITS : 810
===============================
ID : CACHE (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1760
NO_UNITS : 152 (*mismatch* 152 should be 150)
===============================
ID : TEMP (0x3)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 1912
NO_UNITS : 28 (*mismatch* 28 should be 30)
===============================
ID : MODEM (0x5)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 1940
NO_UNITS : 64
===============================
Read image(PARAM) from flash .......
..Done
read 2 units.
Normal Case : MAIN(O) & BACKUP(O)
main: Debug Level Low
RST_STAT = 0x00000004 WAKEUP_STAT = 0x00000000
s5p_fb_info_init start
s5p_fb_info_init end
s5p_fimd_info_init start
s5p_fimd_info_init end
LoadPNG: width:240, height:400, bpp:32, color_type:6, channels:4, rowbytes:960
lcd_gpio_init start
lcd_gpio_init end
lcd_backlight_ctrl start
lcd type: 1
ldi mtpdata: 52 9 11
lcd type is smd
set brightness:0x43
lcd_backlight_ctrl end
SBL:Phone Boot Mode=0
AST_POWERON
usb_download_mode:0
Autoboot (0 seconds) in progress, press any key to stop
AST_ERROR
Autoboot aborted
Type "help" to get a list of commands
SBL>
SBL>
SBL>
SBL> help
Following commands are supported:
* setenv
* savedefault
* saveenv
* printenv
* help
* sec_log
* kernel
* boot
* reset
* nandwrite
* nandread
* nkernel
* readcheck
* savepart
* delpart
* addpart
* showpart
* loadmodem
* loadkernel
* eraseall
* erasepart
* close
* open
* format
* getreg
* setreg
* getadc
* sleep
To get commands help, Type "help <command>"
SBL>
When I let the kernel boot instead of entering the console I get no output from the kernel, possibly because UART switch is being reconfigured to modem somewhere in the kernel, kernel doesn't have serial console enabled or the serial port passed to the kernel in kernel arguments by the bootloader isn't the serial port accessible from microUSB connector.
For reference:
Code:
Secondary Boot Loader(SBL)
Built for apollo rev02 by root on Oct 27 2010 17:10:33
Copyright (C) SAMSUNG Corporation 2006-2010
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 10
partitions loading success
==== PARTITION INFORMATION ====
ID : IBL & PBL (0x0)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : SBL (0x1)
ATTR : RO ENTRYPOINT SLC BOOTLOADING PREWRITING (0xd402)
FIRST_UNIT : 1
NO_UNITS : 5
===============================
ID : PARAM (0x2)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 6
NO_UNITS : 2
===============================
ID : EFS (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 8
NO_UNITS : 32
===============================
ID : KERNEL (0x4)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 40
NO_UNITS : 30
===============================
ID : FACTORYFS (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 70
NO_UNITS : 880
===============================
ID : DATAFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 950
NO_UNITS : 810
===============================
ID : CACHE (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1760
NO_UNITS : 152 (*mismatch* 152 should be 150)
===============================
ID : TEMP (0x3)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 1912
NO_UNITS : 28 (*mismatch* 28 should be 30)
===============================
ID : MODEM (0x5)
ATTR : RO SLC PREWRITING (0x9002)
FIRST_UNIT : 1940
NO_UNITS : 64
===============================
Read image(PARAM) from flash .......
..Done
read 2 units.
Normal Case : MAIN(O) & BACKUP(O)
main: Debug Level Low
RST_STAT = 0x00000004 WAKEUP_STAT = 0x00000000
s5p_fb_info_init start
s5p_fb_info_init end
s5p_fimd_info_init start
s5p_fimd_info_init end
LoadPNG: width:240, height:400, bpp:32, color_type:6, channels:4, rowbytes:960
lcd_gpio_init start
lcd_gpio_init end
lcd_backlight_ctrl start
lcd type: 1
ldi mtpdata: 52 9 11
lcd type is smd
set brightness:0x43
lcd_backlight_ctrl end
SBL:Phone Boot Mode=0
AST_POWERON
usb_download_mode:0
Autoboot (0 seconds) in progress, press any key to stop
FOTA Check Bit
Read BML page=1e4ff, NumPgs=1
FOTA Check Bit (0x0)
Load Partion idx = (4)
..............................done
Kernel read success from kernel partition
setKernelParam: setting param.serialnr=3930c0cf08x 0x159100ec
setKernelParam: setting param.board_rev=0x2
setKernelParam: setting param.cmdline=console=ttySAC1,115200 loglevel=4 version=Sbl(1.0.0) 2010-10-27 17:10:33
Starting kernel at 0x22000000...

moikop said:
Awesome. I think ttySAC1 is defined as s3c2410_serial1 in the kernel. And maybe you'll have to change SWITCH_SEL from the sbl console (from 65 to 6543).
I still don't understand why all I get this � weird character :/
Vcc connected to 3.3v, 150k ohm (though tried with 619k too) resistor and baud rate 115200 8N1, right?
Click to expand...
Click to collapse
Maybe something wrong with your level converter?
Also, if I decoded color codes of resistors correctly, I have 522k ohms connected between GND and ID pins (two 1M connected in parallel and additional 22k after them).
Edit: Would make sense, as according to http://forum.xda-developers.com/showthread.php?t=820275 it would be
Code:
RID_FM_BOOT_OFF_UART, /* 1 1 1 0 0 523K Factory Mode Boot OFF-UART */

tom3q said:
Maybe something wrong with your level converter?
Also, if I decoded color codes of resistors correctly, I have 522k ohms connected between GND and ID pins (two 1M connected in parallel and additional 22k after them).
Edit: Would make sense, as according to http://forum.xda-developers.com/showthread.php?t=820275 it would be
Code:
RID_FM_BOOT_OFF_UART, /* 1 1 1 0 0 523K Factory Mode Boot OFF-UART */
Click to expand...
Click to collapse
Tried with both, 522k & 523k (just in case) and still the same.. So it's gotta be my level converter... that's weird :S

moikop said:
Tried with both, 522k & 523k (just in case) and still the same.. So it's gotta be my level converter... that's weird :S
Click to expand...
Click to collapse
Just for reference, my level converter: http://translate.google.com/transla...unikacja-przez-usb---modul-em212.html&act=url
EDIT: Maybe we should create new topic for discussion on such things?

tom3q said:
Just for reference, my level converter: http://translate.google.com/transla...unikacja-przez-usb---modul-em212.html&act=url
EDIT: Maybe we should create new topic for discussion on such things?
Click to expand...
Click to collapse
You're right. So here it is.
I don't see why my level converter wouldn't work, since it supports the right voltage, baud rate, etc.
mmm, some weird idea: what's you're bootloader version? (I mean from which release). I'm thinking maybe the bootloader version is my problem? (since I have Samsungs latest installed)

moikop said:
You're right. So here it is.
I don't see why my level converter wouldn't work, since it supports the right voltage, baud rate, etc.
mmm, some weird idea: what's you're bootloader version? (I mean from which release). I'm thinking maybe the bootloader version is my problem? (since I have Samsungs latest installed)
Click to expand...
Click to collapse
I don't know the exact version as it was already on the phone as I got it. The only thing saying a bit about the version is its output:
Code:
Built for apollo rev02 by root on Oct 27 2010 17:10:33
Have you tried different baud rates? Common ones other than 115200 are 9600 and 38400.
Also this thread would become a bit more informative if all the posts on this topic would get moved here from OpenFIMG thread.
EDIT: Also make sure that ground signal is properly connected, otherwise the converter might not recognize voltage levels correctly. What's exactly your connection layout? I have only 4 lines wired to the microUSB connector, RX, TX, GND and ID with VCC left unconnected.

tom3q said:
I don't know the exact version as it was already on the phone as I got it. The only thing saying a bit about the version is its output:
Code:
Built for apollo rev02 by root on Oct 27 2010 17:10:33
Click to expand...
Click to collapse
mmm.. I have JPU, so my bootloader is at least from 2011..
tom3q said:
Have you tried different baud rates? Common ones other than 115200 are 9600 and 38400.
Click to expand...
Click to collapse
Tried with those 3. With 9600 and 38400 I don't get anything, when with 115200 I get the "?" character.
tom3q said:
Also this thread would become a bit more informative if all the posts on this topic would get moved here from OpenFIMG thread.
Click to expand...
Click to collapse
I'll contact a mod and see what can be done.
tom3q said:
EDIT: Also make sure that ground signal is properly connected, otherwise the converter might not recognize voltage levels correctly. What's exactly your connection layout? I have only 4 lines wired to the microUSB connector, RX, TX, GND and ID with VCC left unconnected.
Click to expand...
Click to collapse
Double checked my GND connection and is ok. My layout is the following:
VCC -> 3.3v
Tx & Rx with their corresponding pins.
ID connected to GND with 523k ohm in between
and GND connected to GND.

Could you try without VCC connected?
I really don't think that Samsung would disable bootloader console used in service centers for phone diagnostics...

tom3q said:
Could you try without VCC connected?
Click to expand...
Click to collapse
Exact same result.
With GND disconected also same result.
If Tx is disconnected there's no output (obviously). So a badly soldered/connected Pin2 can be discarded.
Checked Rx too, So a badly soldered/connected Pin3 can be discarded as well..
tom3q said:
I really don't think that Samsung would disable bootloader console used in service centers for phone diagnostics...
Click to expand...
Click to collapse
You must be right..
Edit: I changed pin2 & pin3 (now Pin2 is to Rx and Pin3 to Tx). Also connected GND (but left vcc disconnected as you) and got it working
Thanks for the help!

moikop said:
Edit: I changed pin2 & pin3 (now Pin2 is to Rx and Pin3 to Tx). Also connected GND (but left vcc disconnected as you) and got it working
Thanks for the help!
Click to expand...
Click to collapse
So what good is this that you are doing? Benefits etc.
And are we meant to be doing something similar to make phone work better?
Sent from the Persian Sphinx's private Galaxy

PersianSphinx said:
So what good is this that you are doing? Benefits etc.
And are we meant to be doing something similar to make phone work better?
Sent from the Persian Sphinx's private Galaxy
Click to expand...
Click to collapse
With this, we can get into the SBL console, get information about kernel panics (not yet) and this will help us debug kernel ports, drivers ports, etc.
And no. This would be useless for a normal user. Unless that (s)he wants to make a Download JIG (to get into download mode without having to use the three-button combo). In that case, a different resistor value (301k) is needed (and no level converter, of cource )

@PersianSphinx
This wud resurrect a hard bricked phone...this JTAG thing
Sent from my GT-I9100 using Tapatalk

Orr.Penn.18 said:
@PersianSphinx
This wud resurrect a hard bricked phone...this JTAG thing
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
This is not JTAG.

moikop said:
Edit: I changed pin2 & pin3 (now Pin2 is to Rx and Pin3 to Tx). Also connected GND (but left vcc disconnected as you) and got it working
Thanks for the help!
Click to expand...
Click to collapse
This is common fault people are doing - phone Rxd must be connected to converter Txd and vice versa.

Kernel output:
To get kernel output, all you need to do is:
Code:
setenv SWITCH_SEL 6543
And then boot normally from SBL.
To make this setting permanent:
Code:
setenv SWITCH_SEL 6543
saveenv
Result:
Code:
SBL> boot
setKernelParam: setting param.serialnr=3830f5ff08x 0xd44100ec
setKernelParam: setting param.board_rev=0x2
setKernelParam: setting param.cmdline=console=ttySAC1,115200 version=Sbl(1.0.0)2
Starting kernel at 0x22000000...
Uncompressing Linux.............................................................
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.32.9 ([email protected]) (gcc version 4.5.2 (Sourcery G++ Lite2
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv6TEJ), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: GT-I5800
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c0aa7640, node_mem_map c0c3e000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<7>On node 1 totalpages: 0
<7>free_area_init_node: node 1, pgdat c0aa7cf8, node_mem_map c0e47800
<4> Normal zone: 1 pages exceeds realsize 0
<7>On node 2 totalpages: 0
<7>free_area_init_node: node 2, pgdat c0aa83b0, node_mem_map c0e4f880
<4> Normal zone: 1 pages exceeds realsize 0
<7>On node 3 totalpages: 0
<7>free_area_init_node: node 3, pgdat c0aa8a68, node_mem_map c0e57900
<4> Normal zone: 1 pages exceeds realsize 0
CPU S5P6442 (id 0xababab00)
<7>s5p6442_init_clocks: initialising clocks
<6>S3C24XX Clocks, (c) 2004 Simtec Electronics
<7>s5p6442_setup_clocks: registering clocks
<6>mout_apll: source is fout_apll (1), rate is 667000000
<6>mout_epll: source is fout_epll (1), rate is 48000000
<6>mout_mpll: source is mpll (1), rate is 166000000
<6>mout_d0: source is mout_mpll (0), rate is 166000000
<6>mout_d1: source is mout_mpll (0), rate is 166000000
<6>mout_d0sync: source is mout_d0 (0), rate is 166000000
<6>mout_d1sync: source is mout_d1 (0), rate is 166000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>sclk_uart: source is mout_mpll (6), rate is 166000000
<6>sclk_uart: source is mout_mpll (6), rate is 166000000
<6>sclk_uart: source is mout_mpll (6), rate is 83000000
<6>spi-bus: source is mout_epll (7), rate is 48000000
<6>sclk_lcd: source is mout_mpll (6), rate is 166000000
<6>sclk_cam0: source is mout_mpll (6), rate is 166000000
<6>sclk_cam1: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>clk_g2d: source is mout_mpll (1), rate is 166000000
<6>i2sclk: source is i2smain_clk (0), rate is 48000000
<6>audss_hclk: source is i2smain_clk (0), rate is 48000000
<6>i2smain_clk: source is fout_epll (1), rate is 48000000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttySAC1,115200 version=Sbl(1.0.0) 2011-05-27 142
<6>PID hash table entries: 1024 (order: 0, 4096 bytes)
<6>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>Memory: 256MB = 256MB total
<5>Memory: 247040KB available (7488K code, 1639K data, 2972K init, 0K highmem)
<6>SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=4
<6>NR_IRQS:287
<7>s5p64xx_init_irq: initialising interrupts
<6>VIC @f4000000: id 0x00041192, vendor 0x41
<6>VIC @f4010000: id 0x00041192, vendor 0x41
<6>VIC @f4020000: id 0x00041192, vendor 0x41
<3>vic_pm_register: too few VICs, increase CONFIG_ARM_VIC_NR
Console: colour dummy device 80x30
s3c24xx_serial_initconsole
s3c24xx_serial_init_ports: initialising ports...
s3c24xx_serial_init_port: port=c0ad8a60, platdev=c0aabb10
s3c24xx_serial_init_port: c0ad8a60 (hw 0)...
...

moikop said:
To get kernel output, all you need to do is:
Code:
setenv SWITCH_SEL 6543
And then boot normally from SBL.
To make this setting permanent:
Code:
setenv SWITCH_SEL 6543
saveenv
Result:
Code:
SBL> boot
setKernelParam: setting param.serialnr=3830f5ff08x 0xd44100ec
setKernelParam: setting param.board_rev=0x2
setKernelParam: setting param.cmdline=console=ttySAC1,115200 version=Sbl(1.0.0)2
Starting kernel at 0x22000000...
Uncompressing Linux.............................................................
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.32.9 ([email protected]) (gcc version 4.5.2 (Sourcery G++ Lite2
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv6TEJ), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: GT-I5800
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c0aa7640, node_mem_map c0c3e000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<7>On node 1 totalpages: 0
<7>free_area_init_node: node 1, pgdat c0aa7cf8, node_mem_map c0e47800
<4> Normal zone: 1 pages exceeds realsize 0
<7>On node 2 totalpages: 0
<7>free_area_init_node: node 2, pgdat c0aa83b0, node_mem_map c0e4f880
<4> Normal zone: 1 pages exceeds realsize 0
<7>On node 3 totalpages: 0
<7>free_area_init_node: node 3, pgdat c0aa8a68, node_mem_map c0e57900
<4> Normal zone: 1 pages exceeds realsize 0
CPU S5P6442 (id 0xababab00)
<7>s5p6442_init_clocks: initialising clocks
<6>S3C24XX Clocks, (c) 2004 Simtec Electronics
<7>s5p6442_setup_clocks: registering clocks
<6>mout_apll: source is fout_apll (1), rate is 667000000
<6>mout_epll: source is fout_epll (1), rate is 48000000
<6>mout_mpll: source is mpll (1), rate is 166000000
<6>mout_d0: source is mout_mpll (0), rate is 166000000
<6>mout_d1: source is mout_mpll (0), rate is 166000000
<6>mout_d0sync: source is mout_d0 (0), rate is 166000000
<6>mout_d1sync: source is mout_d1 (0), rate is 166000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>mmc_bus: source is mout_mpll (6), rate is 83000000
<6>sclk_uart: source is mout_mpll (6), rate is 166000000
<6>sclk_uart: source is mout_mpll (6), rate is 166000000
<6>sclk_uart: source is mout_mpll (6), rate is 83000000
<6>spi-bus: source is mout_epll (7), rate is 48000000
<6>sclk_lcd: source is mout_mpll (6), rate is 166000000
<6>sclk_cam0: source is mout_mpll (6), rate is 166000000
<6>sclk_cam1: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>lclk_fimc: source is mout_mpll (6), rate is 166000000
<6>clk_g2d: source is mout_mpll (1), rate is 166000000
<6>i2sclk: source is i2smain_clk (0), rate is 48000000
<6>audss_hclk: source is i2smain_clk (0), rate is 48000000
<6>i2smain_clk: source is fout_epll (1), rate is 48000000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttySAC1,115200 version=Sbl(1.0.0) 2011-05-27 142
<6>PID hash table entries: 1024 (order: 0, 4096 bytes)
<6>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>Memory: 256MB = 256MB total
<5>Memory: 247040KB available (7488K code, 1639K data, 2972K init, 0K highmem)
<6>SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=4
<6>NR_IRQS:287
<7>s5p64xx_init_irq: initialising interrupts
<6>VIC @f4000000: id 0x00041192, vendor 0x41
<6>VIC @f4010000: id 0x00041192, vendor 0x41
<6>VIC @f4020000: id 0x00041192, vendor 0x41
<3>vic_pm_register: too few VICs, increase CONFIG_ARM_VIC_NR
Console: colour dummy device 80x30
s3c24xx_serial_initconsole
s3c24xx_serial_init_ports: initialising ports...
s3c24xx_serial_init_port: port=c0ad8a60, platdev=c0aabb10
s3c24xx_serial_init_port: c0ad8a60 (hw 0)...
...
Click to expand...
Click to collapse
Yep, on Spica setenv SWITCH_SEL 3 is enough. According to SBL sources, bit 0 selects USB switch mode and bit 1 selects UART swtich mode.

Orr.Penn.18 said:
@PersianSphinx
This wud resurrect a hard bricked phone...this JTAG thing
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
this is not jtag.... this is UART...this gives us info on what went wrong when the phone dosnt boot up properly when devs are testing new things.

I just received my level converter and it's working fine, I can get SBL logs.
But how to access the SBL prompt ?
I tried with some key combinaison but nothing work :/

[Q] UART Kernel output

I did some probing and found the UART pins on the board. Connecting to it on reboot dumps out the bootloader messages, but goes quiet as soon as the kernel boots. Has anyone been able to get the kernel to output? I feel like I'm missing something simple.
It boots fine into the OS using stock CM12.1 nightlies, but my current modifications to the kernel is causing it to hang mid-boot without panic. Gettings the kernel to output to the UART console would be super helpful for debugging.
Code:
Format: Log Type - Time(microsec) - Message
Log type: B - since boot(excluding boot rom). D - delta
B - 62098 - SBL1, Start
B - 67374 - scatterload_region && ram_init, Start
D - 0 - scatterload_region && ram_init, Delta
B - 84363 - pm_device_init, Start
D - 26474 - pm_device_init, Delta
B - 110928 - boot_flash_init, Start
D - 11407 - boot_flash_init, Delta
B - 122701 - boot_config_data_table_init, Start
D - 0 - boot_config_data_table_init, Delta
B - 128893 - sbl1_ddr_set_params, Start
B - 133651 - Pre_DDR_clock_init, Start
D - 274 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 147284 - pm_driver_init, Start
D - 16500 - pm_driver_init, Delta
B - 163815 - clock_init, Start
D - 183 - clock_init, Delta
B - 166896 - Image Load, Start
B - 185714 - Tz Execution, Start
D - 183610 - Tz Execution, Delta
B - 377407 - Image Load, Start
B - 387075 - Signal PBL to Jump to RPM FW
B - 387350 - sbl1_wait_for_ddr_training, Start
D - 31689 - sbl1_wait_for_ddr_training, Delta
B - 426298 - Image Load, Start
B - 427000 - WDT Execution, Start
D - 213 - WDT Execution, Delta
B - 429623 - Image Load, Start
B - 447648 - sbl1_efs_handle_cookies, Start
D - 244 - sbl1_efs_handle_cookies, Delta
B - 449631 - RPM sync cookie updated
B - 453931 - SBL1, End
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk
[10] platform_init()
[10] target_init()
[210] hw version voltage value=3
[210] ddr version value=1,14
[210] rf version voltage value=37
[290] Done initialization of the card
[310] Display Init: Start
[310] detect pannel ID=:0x0
[310] JDI panel, panel_id=1
[560] MDP GDSC already enabled
[560] msm_fb_alloc enter:fb->width=1080,fb->height=1920,fb->bpp=24
[570] fbcon_setup enter.
[570] Config MIPI_CMD_PANEL.
[690] Neal board_hardware_id = 8!
[700] partition_get_index : name=reserve3
[700] partition_get_index : name=reserve3, n=25
[710] get_gamma_index : -48
[710] msm_display_on enter.
[710] Turn on MIPI_CMD_PANEL.
[710] Display Init: Done
[720] vbatt_low_shutdown_handle enter.
[720] lfc Configure gpios for QUP instance: 0
[720] bq27541_init:eek:K
[730] partition_get_index : name=aboot
[730] partition_get_index : name=aboot, n=4
[740] after msm_boot_mode_init, boot mode is=0
[740] reboot mode is=2003195137
[740] sxh set_msm_boot_mode_by_gpio goto normal mode power on!
# [800] command not found
# # [900] wwx reboot mode =2003195137
[900] partition_get_index : name=LOGO
[900] partition_get_index : name=LOGO, n=21
[910] splash_screen_mmc:MAGIC: SPLASH!!, width: 1080, height: 1919
[930] splash_screen_mmc 4101 YXQ first_read_flag=1
[940] msm_display_on enter.
[940] Turn on MIPI_CMD_PANEL.
YXQ backlight level 200
[950] lm3630_enable-----lm3630_enable: !
[950] yanghai Configure gpios for QUP instance: 1
[960] QUP IN:bl:8, ff:32, OUT:bl:8, ff:32
[960] gpio_ap_switch_config
[960] lfc Configure gpios for QUP instance: 5
[970] bq24196_init:eek:K
[980] QUP IN:bl:8, ff:32, OUT:bl:8, ff:32
[990] partition_get_index : name=misc
[990] partition_get_index : name=misc, n=20
[990] ERROR: Partition table not found
[1000] partition_get_index : name=bootselect
[1000] Unable to locate /bootselect partition
[1000] Boot Select Partition do not exists
[1010] partition_get_index : name=misc
[1010] partition_get_index : name=misc, n=20
[1020] wwx read_misc:
[1020] partition_get_index : name=misc
[1020] partition_get_index : name=misc, n=20
[1030] partition_get_index : name=boot
[1030] partition_get_index : name=boot, n=6
[1030] use_signed_kernel=0, is_unlocked=1, is_tampered=1.
[1040] Loading boot image (6385664): start
[1080] Loading boot image (6385664): done
[1090] Using DTB entry 194/00010000/8/0 for device 194/00010001/8/0
[1090] ddr info: ddr_manufacture_info=Samsung ddr_row0_info=14,len:47,version:1
[1100] LCD_id 0 yxr
[1100] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 console=ttyHSL0,115200,n8 androidboot.emmc=true androidboot.serialno= androidboot.baseband=msm mdss_m[1130] pm8x41_get_is_cold_boot: Warm boot
[1130] WARM: power_on_reason is KPADPWR_N [0x80]
[1130] The power_on_reason is androidboot.startupmode=pwrkey
[1140] cmdline = console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 console=ttyHSL0,115200,n8 androidboot.emmc=true androidboot.serialno= androidboot.baseband=msm mdss_[1160] Updating device tree: start
[1180] Updating device tree: done
[1190] Turn off MIPI_CMD_PANEL.
[1190] Continuous splash enabled, keeping panel alive.
[1190] booting linux @ 0x8000, ramdisk @ 0x2000000 (873073), tags/device tree @ 0x1e00000

Perhaps try and pass console=ttyHSL0,112500 n8 as the command line for the kernel.

This is the cmd line from the boot.img
Code:
cmd_line="console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1"
It also shows up in the bootloader console output:
Code:
[1140] cmdline = console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 console=ttyHSL0,115200,n8 androidboot.emmc=true androidboot.serialno= androidboot.baseband=msm mdss_[1160] Updating device tree: start

It's old though, did you manage to get kernel log on UART? This link says to get kernel messages on UART, kernel needs to be compiled with serial port driver enabled: CONFIG_SERIAL_MSM and CONFIG_SERIAL_MSM_CONSOLE.

mtk6737 baseband unknown and imei blank..how to repair

my phone model- CENTRIC CM2221
android -6.0
problem- no service
i check imei blank and baseband unknown .
how to solve ?
please provide me stock rom or good solution ..
Phone Info Log .........
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 16 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6737
BB_CPU_NME : [MediaTek] MT6737M|MT6737_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x93
NAND Flash : NOT INSTALLED
eMMC Flash : 510001154D333238E8020042AF2EBAF4
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM328
[eMMC] : FLASH_CID : 150100513832334D420002E8F4BA73AF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xEF0B331D1BA71095953C8F7CFAA875FB
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro

abuk91 said:
You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bro allready try but not done .....need flash file

no solution????????????????????????????????????????????????????????????

I have the same problem
phone accent neon no service imei not found
I'm looking for rom file for this model

MBW vodacom kicka 4 plus won't boot , what could be the problem

What could be the problem ..
Operation : Identify [ v2.18 ]
Mode : FLASH
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection ...
PTFN : MediaTek USB Port (COM7)
MODE : BOOTROM
PORT : 7
Waiting BOOT ack ...
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : MEID : 84E1311723E5F72DDF767B7B831BD757
BROM : SecLevel : 0x00000000
BROM : SecMode : PLAIN [+PRL]
BROM : BROM|BL : 0x05|0xFE
BROM : BOOTROM
MODE : 0_base : BASE_v2044 | Manual : Enabled
AGENT : Look for suitable BootChain in DA ...
AGENT : MTK_AllInOne_DA_SP.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA ...
BROM : DA sent
BROM :Transfer control to DA ...
DA : AGENT started!
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
eMMC : OK
eMMC : 45000170414934456E0101344F2524D7
DAInf: 4 : 2 : 156
DA : EXT_RAM NOT initialized!
eMMC : OK
eMMC : 70010045453449413401016ED724254F
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
DRAM : 0x0178
EMI : DEV : MT6752
EMI : SRC : preloader_k80hd_bsp_fwv_512m.bin
EMI : CNT : 0003
EMI : [00] : ID : 700100454534454134 : VEN : KINGSTON | DEV : EE4EA4 : RAM : [ 512.00 MB ]
EMI : [01] : ID : C80111344D45594D41 : VEN : UNKNOWN | DEV : 4MEYMA : RAM : [ 512.00 MB ]
EMI : [02] : ID : 700100454534494134 : VEN : KINGSTON | DEV : EE4IA4 : RAM : [ 512.00 MB ]
EMI : Init EMI from PRELOADER
INIT : 0xBC : DRAM [ 0x00000000 : [ 0 B ] ]
DRAM : DRAM: 0x20000000 [ 512.00 MB ]
DA : DRAM ready!
DA : BOOT to 2nd DA ...
DA : Receiving HW info
EMMC: 70010045453449413401016ED724254F
EMMC: VEN : KINGSTON | OEM : 01 | DEV : EE4IA4
EMMC:
BOOT1 : 0x00200000 [ 2.00 MB ]
BOOT2 : 0x00200000 [ 2.00 MB ]
RPMB : 0x00080000 [ 512.00 KB ]
USER : 0xE2000000 [ 3.53 GB ]
SRAM: 0x00020000 [ 128.00 KB ]
DRAM: 0x20000000 [ 512.00 MB ]
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000 , EVOL : 0x0000
RNID : C936D9FF3A84D90E7B2010FA5212EA26
STATUS : BLANK FLASH
BSTYLE : EMMC FLASH BOOT
DA : USB : FULL-SPEED
DA : USB : Change Port Speed
PTFN : MediaTek DA USB VCOM (Android) (COM9)
MODE : PRELOADER PORT
PORT : 9
Boot done!
Patch Level : O11019
Display ID : O11019 release-keys
Ver. CodeName : REL
Ver. Release : 8.1.0
Sec. Patch : 2019-09-05
Build Time : 23.08.2019
Product Model : Kicka_4_Plus
Product Brand : MobiWire
Product Name : Kicka_4_Plus
Product Device : Kicka_4_Plus
Product Manfct : MobiWire
Product Info : k80hd_bsp_fwv_512m
Board Platform : mt6580
Product Board : VP402_Mobiwire_Kicka4Plus
USERDATA : FILESYSTEM : F2FS with FDE ( Full Disk Encryption ***)
Done!
Elapsed: 00:00:30
Operation : HW Test [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 1 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v3.3001.2018-04-25.11:26_437806
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x9C
NAND Flash : NOT INSTALLED
eMMC Flash : 70010045453449413401016ED724254F
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x70 , OEM : 0100
[eMMC] : FLASH_INF : [KINGSTON] , 4AI4E
[eMMC] : FLASH_CID : 70010045453449413401016ED724254F
[eMMC] : FLASH_BRT : 0x00200000 , 0x00200000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000000E2000000
[eMMC] : FLASH_UCP : 3616 MiB [eMMC 4 GiB]
DEV RID : 0x4EA014B2FFD936C90ED9843AFA10207B
INT RAM : 0x00020000
EXT RAM : 0x20000000 [512 MiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
Processing Miscellaneous test
MSC : BatteryLevel : 3009 mV
[Processing] FlashMemory Read-Write test
[eMMC] : [KINGSTON] , 4AI4E , 0xE2000000 , 3616 MiB
[eMMC] : CID : 70010045453449413401016ED724254F
[eMMC] : MODE : SQ-WR
[PASSED] : eMMC RW Check #1 Ok!
[eMMC] : MODE : RA-WR
[PASSED] : eMMC RW Check #2 Ok!
[eMMC RO CHECK] : eMMC Ok! READ-WRITE Passed!
[Processing] RAM Read-Write test
[DRAM] : 0x20000000 , 512 MiB
[DRAM] : ADDRESS BUS test
[PASSED] : Bus Count : 0x1C
[DRAM] : DATA BUS test
[PASSED] : Bus Count : 0x1F
[DRAM] : PATTERN test
[PASSED] : PATTERN Ok
[DRAM] : INCDEC test
[PASSED] : INCDEC Ok
All Done!
Done!
Elapsed: 00:01:40
Reconnect Power/Cable!

Help Please...MDZ-24-AA , no power led, no video...

Hi all, this is my fist post....
As subject I have a problem with my poor xiaomi MDZ-24-AA...
no boot...no led...nothing on screen
This is the loop serial output captured with PL2303
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:1;RCY:0;SPI:0;CHK:A7;EMMC:0;READ:0;0.0;0.0;CHK:5E6;READ:0;0.0;0.0;CHK:5E6;READ:0;0.0;0.0;CHK:0;
TE: 2330954
BL2 Built : 10:18:52, Sep 14 2020. gxl g9f162b4-dirty - [email protected]
set vcck to 1120 mv
set vddee to 1000 mv
id=3
DDR4 board
CPU clk: 1200MHz
DDR scramble enabled
DDR4 chl: Rank0+1 @ 1056MHz - FAIL
DDR4 chl: Rank0 @ 1056MHz
bist_test rank: 0 19 07 2b 24 11 38 1a 08 2d 28 14 3c 15 04 26 28 16 3b 1b 08 2e 27 17 38 751 - PASS
Rank0: 1024MB(auto)-2T-18
AddrBus test pass!
eMMC boot @ 2
sw8 s
emmc switch 3 ok
BL2: rpmb counter: 0x00000020
emmc switch 2 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 2
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600, part: 2
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x0002b400, part: 2
aml log : R1024 check pass!
Load bl32 from eMMC, src: 0x0004c200, des: 0x01700000, size: 0x0003e200, part: 2
aml log : R1024 check pass!
Load bl33 from eMMC, src: 0x0008c200, des: 0x01700000, size: 0x0007f600, part: 2
sd/emmc cmd 18 arg 0x00000761 status 01ff3000
sdio read data fail
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 0
emmc switch 0 ok
sd/emmc cmd 18 arg 0x00000061 status a1ff3000
sdio read data fail
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 1
emmc switch 1 ok
can someone help me ?
Thanks

device always died after trying the file and method at this address
Xiaomi Mi TV Stick - Обсуждение - 4PDA
Xiaomi Mi TV Stick - Обсуждение, [ТВ-приставка]
4pda.to
Step-by-step instructions for restoring a stick with an old bootloader:
#
1. Stick MDZ-24-AA
- Cyclic reboot on the logo;
- Does not enter the recovery;
- Old bootloader installed*;
*If you have a new bootloader, then this method is not for you. It is necessary to unsolder the chip and restore it using the programmer. The author of the video does this too.
2. What is needed for firmware:
- USB-UART cable for firmware, for example PL2303 + drivers;
- micro usb cable for connection with PC;
- Putty program;
- adb drivers;
- backup from the working stick (from the author of the recovery method https://disk.yandex.ru/d/aL5XolrdAbTJ0g )
3. Solder to the connectors on the stick.
Connect RX from PL2303 to TX on the stick,
connect TX from PL2303 to RX on the stick and connect GND.
4. Install the PL2303 drivers.
Install the Putty program.
Install ADB drivers.
(You can download from the link at the bottom of the instructions)
5. Connect the PL2303 to the PC. We check the device manager, if it is not recognized, we put the necessary drivers. We remember the number of the assigned COM port.
6. Run the pre-installed Putty - select the Serial connection, enter the COM port number PL2303, set the speed to 115200 and click Open. Connect micro usb cable to PC. Press the Inter key several times until the command prompt appears. If the commands went, congratulations, you have an old bootloader and you can restore the backup.
7. Enter the command: fastboot
Run the command line, go to the ADB folder with the command: cd c:\adb (the address of the adb folder) and enter the following commands one by one:
fastboot oem unlock
fastboot flashing unlock
fastboot unlock_critical
You can check the unlock status with the command
fastboot oem device- info
8. Reconnect PL2303 to PC. We repeat point 5. Enter the command: update
The stick goes into firmware mode. Open the previously unpacked folder with the author's backup. First, install the driver from the backup folder, this should be done every time you plan to make a dump or upload a dump.
There are batch files in the backup:
- a.bat automatically dumps stick sections;
- b.bat automatically downloads the backup to the stick.
After the end, the firmware window will close.
9. Now we connect the stick to the TV and set it up again.
Necessary programs and drivers for firmware

definitely don't try
won't boot in download or fastboot recovery mode

now i got some progress
will be seen from the log
a pair of pin shorts and
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;0.0;CHK:0;
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:0;RCY:0;USB:0;
let's solve this one more job done I have dump files that I got from my own device, but it doesn't work for me because uboot doesn't work. When I short-circuit 2 pins, the device The GX-CHIP is seen as hardware connected to the computer. Let's find the process we will do next, let's solve the lock of the device

GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;0.0;CHK:0;
TE: 128917
BL2 Built : 10:18:52, Sep 14 2020. gxl g9f162b4-dirty - [email protected]
set vcck to 1120 mv
set vddee to 1000 mv
id=3
DDR4 board
CPU clk: 1200MHz
DDR scramble enabled
DDR4 chl: Rank0+1 @ 1056MHz - FAIL
DDR4 chl: Rank0 @ 1056MHz
bist_test rank: 0 12 00 25 2b 1a 3c 13 00 27 2f 1e 41 0f 00 1f 30 1f 42 15 00 2a 2b 19 3e 706 - PASS
Rank0: 1024MB(auto)-2T-18
AddrBus test pass!
eMMC boot @ 0
sw8 s
emmc switch 3 ok
BL2: rpmb counter: 0x00000020
emmc switch 0 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 0
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600, part: 0
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x0002b400, part: 0
aml log : R1024 check pass!
Load bl32 from eMMC, src: 0x0004c200, des: 0x01700000, size: 0x0003e200, part: 0
aml log : R1024 check pass!
Load bl33 from eMMC, src: 0x0008c200, des: 0x01700000, size: 0x00080e00, part: 0
aml log : R1024 check pass!
aml log : SIG CHK : 231 for address 0x01700000
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 1
emmc switch 1 ok
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:0;RCY:0;USB:0;
begins to wait to continue processing

short point for emmc to usb

dijitalxyz said:
device always died after trying the file and method at this address
Click to expand...
Click to collapse
I guess the problem is in the vbmeta partition and the integrity check (Android Verified Boot). During startup, the bootloader checks the partition hashes (system, vendor, dtb etc...) with those stored in vbmeta. In case of a mismatch - bootloop.
This archive from 4pda contains partitions of firmware with build date May 26 2020 (PI.293) (including vbmeta) BUT lacks a dtb partition. Accordingly, after you have completed the instructions for restore, the old dtb from the firmware Sep 14 2020 (PI.536) remains in internal memory. Therefore, the bootloader detects a dtb hash mismatch and goes to bootloop.
You can try edit vbmeta.img for disabling integrity check by adding the AVB disable flag. To do this, open vbmeta.img in the hex editor. Go to the offset 7B, replace 00 with 03. Save it.
Spoiler: Hex
Then you need to get into the flash mode (fastboot or update/UBT) using the uboot console via uart (like in Instruction for restoring point 6-7), and flash this edited vbmeta.

dijitalxyz said:
short point for emmc to usb
Click to expand...
Click to collapse
Hi, did you to restore the stick ???
How did you pair the short points?

is there a way to recover?
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;0.0;CHK:0;
TE: 136033
BL2 Built : 10:18:52, Sep 14 2020. gxl g9f162b4-dirty - [email protected]
set vcck to 1120 mv
set vddee to 1000 mv
id=3
DDR4 board
CPU clk: 1200MHz
DDR scramble enabled
DDR4 chl: Rank0+1 @ 1056MHz - FAIL
DDR4 chl: Rank0 @ 1056MHz
bist_test rank: 0 18 02 2f 28 16 3a 13 00 27 2d 1b 3f 15 00 2b 2e 1d 3f 19 04 2f 29 18 3a 706 - PASS
Rank0: 1024MB(auto)-2T-18
AddrBus test pass!
eMMC boot @ 0
sw8 s
emmc switch 3 ok
BL2: rpmb counter: 0x00000020
emmc switch 0 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 0
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600, part: 0
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x0002b400, part: 0
aml log : R1024 check pass!
Load bl32 from eMMC, src: 0x0004c200, des: 0x01700000, size: 0x0003e200, part: 0
aml log : R1024 check pass!
Load bl33 from eMMC, src: 0x0008c200, des: 0x01700000, size: 0x00080e00, part: 0
aml log : R1024 check pass!
NOTICE: BL3-1: v1.0(release):129a6bc
NOTICE: BL3-1: Built : 17:09:37, Apr 25 2019
[BL31]: GXL CPU setup!
NOTICE: BL3-1: GXL secure boot!
NOTICE: BL3-1: BL33 decompress pass
mpu_config_enable:system pre init ok
dmc sec lock
[Image: gxl_v1.1.3377-2941e55e3 2020-07-08 17:19:09 [email protected]]
OPS=0xb4
21 0d b4 00 05 d4 ef 6c f8 a2 76 d1 10 3a 4e ae
[0.732014 Inits done]
secure task start!
high task start!
low task start!
INFO: BL3-2: ATOS-V2.4-239-g48b8c37d #1 Wed Feb 5 09:34:09 UTC 2020 arm
INFO: BL3-2: Chip: GXL Rev: D (21 - B0:2)
INFO: BL3-2: crypto engine DMA
INFO: BL3-2: secure time TEE
INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e
U-Boot 2015.01-g2e3e77d-dirty (Nov 07 2020 - 00:20:15), Build: jenkins-aquaman-664
DRAM: 1 GiB
Relocation Offset is: 36e80000
gpio: pin gpiodv_24 (gpio 43) value is 1
register usb cfg[0][1] = 0000000037f4c4f8
[CANVAS]canvas init
MMC: aml_priv->desc_buf = 0x0000000033e80ab0
aml_priv->desc_buf = 0x0000000033e82df0
SDIO Port B: 0, SDIO Port C: 1
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
[mmc_startup] mmc refix success
init_part() 297: PART_TYPE_AML
[mmc_init] mmc init success
is there a way to recover?

czemu netflix nie dziala po wymianie emmc
hello why this netflix does not work after replacing the memory I have a damp from a good stick and it does not work on another