[dev] memory mapping! - HD Mini Android Development

sorry my bug

Becouse photon have 384M memory but our android port in this time have 290M I will try to add another bank for more memmory. Photon memory map dumped from WinCe is:
Code:
v=virtual
p=physhical
==========================================================
v80000000-8cb00000 -> p00100000-0cc00000 cb00000
v8cb00000-8cc00000 -> p00000000-00100000 100000
v8cc00000-8cd00000 -> p0ff00000-10000000 100000
v8cd00000-8da00000 -> p0f200000-0ff00000 d00000
v90000000-90100000 -> p98000000-98100000 100000
v90100000-90200000 -> p9c000000-9c100000 100000
v90200000-90f00000 -> pac000000-acd00000 d00000
v90f00000-91000000 -> pa0e00000-a0f00000 100000
v91000000-91100000 -> pa0d00000-a0e00000 100000
v91100000-91200000 -> pa0d00000-a0e00000 100000
v91200000-91300000 -> pa0c00000-a0d00000 100000
v91300000-91500000 -> pa0a00000-a0c00000 200000
v91500000-91600000 -> pa0800000-a0900000 100000
v91600000-91700000 -> pa0700000-a0800000 100000
v91700000-91800000 -> pa0600000-a0700000 100000
v91800000-91900000 -> pa0500000-a0600000 100000
v91900000-91a00000 -> pa0400000-a0500000 100000
v91a00000-91c00000 -> pa0200000-a0400000 200000
v91c00000-91d00000 -> pa0100000-a0200000 100000
v91d00000-91e00000 -> pa0000000-a0100000 100000
v91e00000-91f00000 -> paa600000-aa700000 100000
v91f00000-92000000 -> paa500000-aa600000 100000
v92000000-92100000 -> paa300000-aa400000 100000
v92100000-92200000 -> pa8100000-a8200000 100000
v92200000-92300000 -> pa9d00000-a9e00000 100000
v92300000-92400000 -> pa9900000-a9a00000 100000
v92400000-92500000 -> pa8700000-a8800000 100000
v92500000-92600000 -> paa200000-aa300000 100000
v92600000-92700000 -> pa9c00000-a9d00000 100000
v92700000-92800000 -> pa9b00000-a9c00000 100000
v92800000-92900000 -> pa9a00000-a9b00000 100000
v92900000-92a00000 -> pa9800000-a9900000 100000
v92a00000-92b00000 -> pa9700000-a9800000 100000
v92b00000-92c00000 -> pa9600000-a9700000 100000
v92c00000-92d00000 -> pa9500000-a9600000 100000
v92d00000-92e00000 -> pa9400000-a9500000 100000
v92e00000-92f00000 -> pa9300000-a9400000 100000
v92f00000-93000000 -> pa9200000-a9300000 100000
v93000000-93100000 -> pa9100000-a9200000 100000
v93100000-93200000 -> pa9000000-a9100000 100000
v93200000-93300000 -> pa8800000-a8900000 100000
v93300000-93400000 -> pa8600000-a8700000 100000
v93400000-93500000 -> pa8500000-a8600000 100000
v93500000-93600000 -> pa8300000-a8400000 100000
v93600000-93700000 -> pa8200000-a8300000 100000
v93700000-93800000 -> pa8200000-a8300000 100000
v93800000-93900000 -> pa8200000-a8300000 100000
v93900000-93a00000 -> pa8200000-a8300000 100000
v93a00000-93b00000 -> pa8200000-a8300000 100000
v93b00000-93c00000 -> pa8000000-a8100000 100000
v93c00000-94100000 -> pc0000000-c0500000 500000
v94100000-94200000 -> p80100000-80200000 100000
v96000000-96200000 -> p88000000-88200000 200000
v96200000-98000000 -> p20000000-21e00000 1e00000
v98000000-98200000 -> p8c000000-8c200000 200000
v98200000-9a000000 -> p21e00000-23c00000 1e00000
v9a000000-9a200000 -> p90000000-90200000 200000
v9a200000-9c000000 -> p23c00000-25a00000 1e00000
v9c000000-9c100000 -> p94000000-94100000 100000
v9c100000-9d000000 -> p25a00000-26900000 f00000
v9d000000-9d100000 -> p98000000-98100000 100000
v9d100000-9e000000 -> p26900000-27800000 f00000
v9e000000-9e200000 -> p9c000000-9c200000 200000
v9e200000-9ea00000 -> p27800000-28000000 800000
v9f000000-9f100000 -> p80000000-80100000 100000
vf0400000-f0500000 -> p00000000-00100000 100000
vfffd0000-fffd4000 -> p01a10000-01a14000 4000
vffff0000-ffff1000 -> p01a14000-01a15000 1000
vffffc000-ffffd000 -> p01a15000-01a16000 1000
Anyone know at which memmory offset radio is located???

may be add smi and ebi bank?

derefas said:
may be add smi and ebi bank?
Click to expand...
Click to collapse
I dont know. Curent definitions for Photon memory:
Code:
#define MSM_MEM1_BASE 0x00000000
#define MSM_MEM1_SIZE 0x0CC00000
#define MSM_MEM2_BASE 0x20000000
#define MSM_MEM2_SIZE 0x08000000
#define MSM_LINUX_BASE_OFFSET 0x00200000
#define MSM_MM_HEAP_SIZE 0x02A00000
#define MSM_PHOTON_LINUX1_BASE (MSM_MEM1_BASE + MSM_LINUX_BASE_OFFSET) /* 2MB alignment */
#define MSM_PHOTON_LINUX1_SIZE (MSM_MEM1_SIZE - MSM_LINUX_BASE_OFFSET)
#define MSM_PHOTON_LINUX2_BASE MSM_MEM2_BASE /* 2MB alignment */
#define MSM_PHOTON_LINUX2_SIZE (MSM_MEM2_SIZE - MSM_MM_HEAP_SIZE)
#define MSM_FB_BASE MSM_MEM2_BASE + MSM_MEM2_SIZE - MSM_MM_HEAP_SIZE
#define MSM_FB_SIZE 0x00200000 // 2M
#define MSM_GPU_MEM_BASE MSM_FB_BASE + MSM_FB_SIZE
#define MSM_GPU_MEM_SIZE 0x00300000 // 3M
#define MSM_PMEM_MDP_BASE MSM_GPU_MEM_BASE + MSM_GPU_MEM_SIZE
#define MSM_PMEM_MDP_SIZE 0x01000000 // 16M
#define MSM_PMEM_ADSP_BASE MSM_PMEM_MDP_BASE + MSM_PMEM_MDP_SIZE
#define MSM_PMEM_ADSP_SIZE 0x00C1B000 // ~12M
#define MSM_PMEM_CAMERA_BASE MSM_PMEM_ADSP_BASE + MSM_PMEM_ADSP_SIZE
#define MSM_PMEM_CAMERA_SIZE 0x00800000 // 8M
#define MSM_RAM_CONSOLE_BASE 0x00100000
#define MSM_RAM_CONSOLE_SIZE SZ_1M
I analysed Aria kernel code and I found aria have (0x18000000 - 0x02C00000 - 0x02800000 = ) 314M of the ram memory!! So my idea is to add new bank and realign MSM_MM_HEAP things. With new (bank3?) we will get ~20M (290M + 20M = ) ~310M ram memory like Aria have! But only problem is: I need to find memory offsets: spl (ok I know), radio (not analysed), splash (not analysed)...etc
EDIT:
Code:
v9c100000-9d000000 -> p25a00000-26900000 f00000
v9d000000-9d100000 -> p98000000-98100000 100000
v9d100000-9e000000 -> p26900000-27800000 f00000
v9e000000-9e200000 -> p9c000000-9c200000 200000
v9e200000-9ea00000 -> p27800000-28000000 800000
Possible MSM_PMEM_MDP_BASE is p25a00000-26900000 f00000 or maybe p26900000-27800000 f00000
Also I think MSM_PMEM_MDP_SIZE is not 0x01000000, I think it is 0xf00000 .. it free 1M of the memory!
p27800000-28000000 800000 is: #define MSM_PMEM_CAMERA_BASE 0x27800000
But maybe MSM_PMEM_ADSP_BASE is wrong here becouse we have two regions of the 0xd00000 size, so I think one of it is MSM_PMEM_ADSP_BASE ?? it will give 13M++ memory for our phone!!
Or maybe MSM_GPU_MEM_BASE and MSM_PMEM_ADSP_BASE need to be strict inside memory region with size of the 0xf00000 ?? It will free 2-3M (MSM_MM_HEAP_SIZE - 3M)!
Need help to find (Radio=2+36=38M) where is radio located, in which offset! Lets analyse memory regions, ok? What you think?
EDIT:
Tried region 0xac000000 without success: Ignoring RAM at ac000000-accfffff (vmalloc region overlap)

. .

I have good news
<6>[ 0.000000] Memory: 202MB 13MB 86MB = 301MB total !!!
I will move MSM_PMEM_ADSP_BASE to region of the 13M

munjeni said:
I have good news
<6>[ 0.000000] Memory: 202MB 13MB 86MB = 301MB total !!!
I will move MSM_PMEM_ADSP_BASE to region of the 13M
Click to expand...
Click to collapse
good news,

#define MSM_VFE_PHYS 0xA0F00000
#define MSM_VFE_SIZE SZ_1M
0xa0f00000 not found in wince memory, maybe need 0xa0e00000 ?? maybe fix for video??

I realigned memory and got only 2M++ so now phone have 290M ram memory.... I tried more ram but not possible becouse: 0xac000000 region already used by MSM_AD5, also I tried region 0x0f200000 but that region have flag "not execute" and phone crash ater load screen! So now memory is propertly realigned... commits are here -> http://gitorious.org/2-6-32-photon I will update attachment in mine release

... ..

maybe the 290m ram is free,not all the 384m was activied or the other ram was used by wince or haret when android was started.
i thought that ram or rom is not important ,they were rooted by the bootloader on the motherboard.
if bootloader was crashed by anyone ,then ram or rom would be free.
maybe some bug like ps3 or xbox360 may let us have rights to rewrite the rom .

Sorry, but I think you did not understand what this is about and how things work =)

ncla2000 said:
maybe the 290m ram is free,not all the 384m was activied or the other ram was used by wince or haret when android was started.
i thought that ram or rom is not important ,they were rooted by the bootloader on the motherboard.
if bootloader was crashed by anyone ,then ram or rom would be free.
maybe some bug like ps3 or xbox360 may let us have rights to rewrite the rom .
Click to expand...
Click to collapse
No, you are wrong, but one thing is ok, yes, 40m memory is for radio (I not know offset) and I think Aria have radio in different memory offset region, but I see some memory regions is locked with flag "can not execute" but have flag super user read/write... so I think its locked by bootloader or by radio, I dont know exatly I ordered the Segger J-Link EDU and think it will arrive in ten days to me... I will try other bootloaders. Also I need your help to find jtag pins for our phone!

Related

[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 :/

somthing intresting help unbrick

[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
how to unbrick?
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
how did you check this out?
theonecallednick said:
how did you check this out?
Click to expand...
Click to collapse
I found uart pin on mainboard for debuging .
with serial usb cable pl2303
This is the red light only and unknown hardware found (the unknown hardware is in fact mtk usb vcom driver buth sony version ) if you try sp flash tool for mtk then it comunicates with de phone buth it needs some authentication file.
Help..
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
.........................
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
Samuel Wankhede said:
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
Click to expand...
Click to collapse
Try the guide given in thread linked below
http://forum.xda-developers.com/showpost.php?p=57614511&postcount=13
Please share uart pinout
Baudrate should be 115200??
Thanks
uart
please share the uart pinout , thanks

HELP!!!!! I NEED TO REINsTALL LINUX ON A TV BOX

Hello all ,
I linked a serial cable to my allwinner a20 based Android Tv box.
It can not pass after the boot logo and next is all what it display in serial console.
Somebody pelase help i need to reisntall linux on it ,if you knwo any u boot keys that i have to press on the uboot serial consoel pelase help.I tryed to press ransom keys but i see nothin.
Here is all i see when it start:
====================================
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =512
sum=0x9c3bd8cf
src_sum=0x9c3bd8cf
Ready to disable icache.
Jump to secend Boot.
[ 0.133]
U-Boot 2011.09-rc1-dirty (Nov 08 2013 - 11:06:32) Allwinner Technology
[ 0.141]version: 1.1.0
[ 0.144]pmbus: ready
axp read error
probe axp20x failed
axp_probe error
boot_clock = 912
dcdc2_vol = 1400
axp set dcdc2_vol to 1400 failed
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
usb_recovery = 0
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.293]DRAM: 512 MiB
relocation Offset is: 15b27000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.560]boot_disp.output_type=2
[ 0.563]boot_disp.output_mode=5
[ 0.567]boot_disp.auto_hpd=1
workmode = 0
[ 1.871]NAND: NAND_UbootInit
NB1 : enter NAND_LogicInit
nand : get id_number_ctl from script, 3
not burn nand partition table!
NB1 : nftl num: 3
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 2.381]sunxi flash init ok
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:12-
-name- -start- -size-
bootloader : 1000000 1000000
env : 2000000 1000000
boot : 3000000 1000000
system : 4000000 20000000
recovery : 24000000 2000000
databk : 26000000 2000000
misc : 28000000 1000000
private : 29000000 1000000
sysrecovery : 2a000000 21000000
data : 4b000000 40000000
cache : 8b000000 17000000
UDISK : a2000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
Fastboot detected, will boot fastboot
to be run cmd=run setargs_nand boot_fastboot
the user data'magic is bad
WORK_MODE_BOOT
board_status_probe
sunxi_bmp_display
WORK_MODE_BOOT
[ 2.509]Hit any key to stop autoboot: 0
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x582580a8
delay time 0
usb init ok
------------------------------------------------------------------
After this nothing .Please help me
After searching all google and reading documantation ,I contacted the box seller and he gied me the files i neeeded.
I used a image file named sun7i_A20v2.0_android_sugar-ref001_2014.09.04_TakenYBSJ.img and a windwos software to flash it via usb named PhoenixPacketV333
To flash teh device you muist hava a serial console to the box (veru easy to do if you have the cable ) ,and keep pushed the key 2
on serial consle (putty) while powering the device ,so it enter in fel mode ( something like recovery mode ,it accept usb connection) .Then oyu need a usb male to male cable to conect the android tv box usb port to the windows usb port ,and start flasing using the PhoenixPacketV333 software.
If somebody needs more help or files just write here I check daily .
have a nice day all!

Can't initializate repository

Hi, I'm starting to build Android ROM's, I tryed using my PC but sync the repo takes so much time because my internet conection is slow, for that reason, I bought a Google cloud platform, I set ubuntu 14.04LTS and I started to installing a few things, but when everything is ready when I use: "repo init -u https://github.com/LineageOS/android_device_lge_d851.git -b cm-14.1" I get this error:
Get https://gerrit.googlesource.com/git-repo/clone.bundle
... A new repo command ( 1.23) is available.
... You should upgrade soon:
cp /home/jesusgabriel_91/ArtxOS/.repo/repo/repo /usr/bin/repo
Get https://github.com/LineageOS/android_device_lge_d851.git
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
remote: Counting objects: 308, done.
remote: Total 308 (delta 0), reused 0 (delta 0), pack-reused 308
Receiving objects: 100% (308/308), 43.57 KiB | 0 bytes/s, done.
Resolving deltas: 100% (162/162), done.
From https://github.com/LineageOS/android_device_lge_d851
* [new branch] cm-11.0 -> origin/cm-11.0
* [new branch] cm-12.0 -> origin/cm-12.0
* [new branch] cm-12.1 -> origin/cm-12.1
* [new branch] cm-13.0 -> origin/cm-13.0
* [new branch] cm-14.0 -> origin/cm-14.0
* [new branch] cm-14.1 -> origin/cm-14.1
* [new branch] stable/cm-11.0 -> origin/stable/cm-11.0
* [new branch] stable/cm-12.0-YNG3C -> origin/stable/cm-12.0-YNG3C
* [new branch] stable/cm-12.0-YNG4N -> origin/stable/cm-12.0-YNG4N
* [new branch] stable/cm-12.1-YOG7D -> origin/stable/cm-12.1-YOG7D
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
I would be so grateful if someone tell me if I'm missing something, I installed phablet-tools, Java 8, Git and updated everything...
First of all, try installing java 7 (tons of guides on how to do that), second of all, have you tried the linux version of the good 'ol "have you tried turning it on and off again?" by running the command
Code:
sudo apt-get update && sudo apt-get upgrade

Mi Stick stuck on boot logo (bricked?)

Hello everybody.
A couple of years ago I bought a Mi Stick for my mother, to use connected to an old LED tv she had. She used just 3 o 4 times tops with a Netflix account my brother shared with her. The device was practically new. My brother stopped paying Netflix a couple of months ago so she stopped using the device altogether so I disconnected it. But yesterday she told me my brother started paying Netflix again and told me to connect the MiStick to her TV again. Surprisingly, the device is now stuck on the boot logo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm really angry because the device had very little use and especially because I live in third world ****hole: a new MiStick costs almost 4 times more now. It's not like I have couple of dollars getting dust on a drawer somewhere and I can go buy another one.
Anyway, I know it's possible to flash/unbrick a MiBox, I did it some time ago. Anybody knows if it's possible to the same with the Mi Stick??? I googled about it but I didn't find anything.
Thank you for your time.
hello, my Mi TV Stick MDZ-24-AA also unfortunately hangs all the time on the logo, checked on various cables and on a decent power supply
through the remote control (arrow + OK) does not want to enter the bootloader
I have purchased PL2303HX converter
According to the instructions from https://forum.xda-developers.com/t/help-pleas...-no-power-led-no-video.4452819/#post-87044521
and partially supported by Ruslan's film
With a backup downloaded from https://disk-yandex-ru.translate.goog/d/aL5Xo...en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_hist=true
Using Putty and ADB
I went through the entire installation process
Unfortunately, my mi stick still hangs on the logo: / What could be the cause? Is my mi stick still salvageable?
kedzior.kedzior said:
I have purchased PL2303HX converter
Using Putty and ...
I went through the entire installation process
Unfortunately, my mi stick still hangs on the logo
Click to expand...
Click to collapse
With the PL2303HX connected to the uart while the device is booting (to a hung state), what is shown in the uart log while the device is trying to boot?
Are you able to get a prompt over the uart as shown in the video?
Functioner said:
With the PL2303HX connected to the uart while the device is booting (to a hung state), what is shown in the uart log while the device is trying to boot?
Are you able to get a prompt over the uart as shown in the video?
Click to expand...
Click to collapse
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;0.0;CHK:0;
TE: 138335
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 05 2e 28 16 3a 17 02 2d 2b 1d 3a 17 02 2c 2c 1c 3d 18 02 2f 27 16 38 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 6b a3 4a 05 e8 35 9e 81 38 16 4f b7
[0.733983 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
aml log : R1024 check pass!
start dts,buffer=0000000033e85640,dt_addr=0000000033e85640
get_partition_from_dts() 71: ret 0
parts: 17
00: logo 0000000000800000 1
01: recovery 0000000001800000 1
02: misc 0000000000800000 1
03: dtbo 0000000000800000 1
04: cri_data 0000000000800000 2
05: param 0000000001000000 2
06: boot 0000000001000000 1
set has_boot_slot = 0
07: rsv 0000000001000000 1
08: tee 0000000002000000 1
09: vendor 0000000006400000 1
10: odm 0000000001400000 1
11: metadata 0000000001000000 1
12: vbmeta 0000000000200000 1
13: system 000000005ac00000 1
14: product 0000000006a00000 1
15: cache 0000000010000000 2
16: data ffffffffffffffff 4
init_part() 297: PART_TYPE_AML
eMMC/TSD partition table have been checked OK!
crc32_s:0x1577dad == storage crc_pattern:0x1577dad!!!
crc32_s:0xee152b83 == storage crc_pattern:0xee152b83!!!
crc32_s:0x7fd3b243 == storage crc_pattern:0x7fd3b243!!!
mmc env offset: 0x17400000
In: serial
Out: serial
Err: serial
reboot_mode=cold_boot
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-2755: calc 6955a20f, store 6955a20f
_verify_dtb_checksum()-2755: calc 6955a20f, store 6955a20f
dtb_read()-2972: total valid 2
update_old_dtb()-2953: do nothing
aml log : R1024 check pass!
vpu: clk_level in dts: 7
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x300)
vpu: vpu_clk_gate_init_off finish
vpp: vpp_init
hpd_state=0
vpp: vpp_matrix_update: 2
cvbs performance type = 6, table = 0
cvbs_config_hdmipll_gxl
cvbs_set_vid2_clk
the HHI_VDAC_CNTL0 =b0001
the HHI_VDAC_CNTL0 =b0200
the HHI_VDAC_CNTL1 =0
the HHI_VDAC_CNTL1 =8
amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[BL31]: tee size: 0
[BL31]: tee size: 0
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[region] not programed yet
CONFIG_AVB2: avb2
Start read misc partition datas!
info->magic =
info->version_major = 1
info->version_minor = 0
info->slots[0].priority = 15
info->slots[0].tries_remaining = 7
info->slots[0].successful_boot = 0
info->slots[1].priority = 14
info->slots[1].tries_remaining = 7
info->slots[1].successful_boot = 0
info->crc32 = -1075449479
active slot = 0
wipe_data=successful
wipe_cache=successful
upgrade_step=2
reboot_mode:::: cold_boot
[OSD]load fb addr from dts:/meson-fb
[OSD]fb_addr for logo: 0x3f800000
[OSD]load fb addr from dts:/meson-fb
[OSD]fb_addr for logo: 0x3f800000
[OSD]VPP_OFIFO_SIZE:0xfff00fff
[CANVAS]addr=0x3f800000 width=5760, height=2160
[OSD]osd_hw.free_dst_data: 0,719,0,575
Command: bcb uboot-command
Start read misc partition datas!
BCB hasn't any datas,exit!
do_monitor_bt_cmdline
gpio: pin GPIOX_17 (gpio 17) value is 0
gpio: pin GPIOX_17 (gpio 17) value is 1
gpio: pin GPIOX_18 (gpio 18) value is 1
hw_config_start:state = 3
bt_cmdline: fw downloaded
no recovery mod!
gpio: pin GPIOX_8 (gpio 8) value is 1
Hit Enter or space or Ctrl+C key to stop autoboot -- : 0
CONFIG_SYSTEM_AS_ROOT: systemroot
system_mode: 1
CONFIG_AVB2: avb2
active_slot: normal avb2: 1
Err imgread(L328):Fmt unsupported!genFmt 0x0 != 0x3
InUsbBurn
[MSG]sof
Set Addr 4
Get DT cfg
Get DT cfg
Get DT cfg
set CFG
Get DT cfg
Get DT cfg
Get DT cfg
Get DT cfg
waitIdentifyTime(751) > timeout(750)
(Re)start USB...
USB0: USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
active_slot: normal
Err imgread(L328):Fmt unsupported!genFmt 0x0 != 0x3
gxl_aquaman_v1#
kedzior.kedzior said:
Err imgread(L328):Fmt unsupported!genFmt 0x0 != 0x3
Click to expand...
Click to collapse
The above error might be an issue.
at the prompt:
gxl_aquaman_v1#
type:
printenv
and post the output.
Functioner said:
The above error might be an issue.
at the prompt:
gxl_aquaman_v1#
type:
printenv
and post the output.
Click to expand...
Click to collapse
gxl_aquaman_v1#printenv
1080p60hz_deepcolor=444,12bit
480p60hz_deepcolor=rgb,8bit
EnableSelinux=permissive
active_slot=normal
avb2=1
baudrate=115200
bcb_cmd=get_avb_mode;get_valid_slot;
boardid=3
boot_part=boot
bootargs=init=/init console=ttyS0,115200 no_console_suspend earlycon=aml_uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 ro rootwait skip_initramfs reboot_mode_android=normal androidboot.selinux=permissive logo=osd1,loaded,0x3d800000,576cvbs maxcpus=4 vout=576cvbs,enable hdmimode=1080p60hz frac_rate_policy=1 cvbsmode=576cvbs hdmitx=,444,12bit cvbsdrv=0 androidboot.firstboot=0 jtag=apao androidboot.veritymode=enforcing androidboot.hardware=amlogic androidboot.btmacaddr=00:00:00:00:00:00 androidboot.wifimac=00:00:00:00:00:00 androidboot.wificountrycode=US androidboot.bootloader= androidboot.serialno=26919800002433906 androidboot.boardid=3 androidboot.region=none androidboot.reboot_mode=cold_boot page_trace=on androidboot.rpmb_state=0 aml_dt= recovery_part={recovery_part} recovery_offset={recovery_offset} aml_dt= recovery_part={recovery_part} recovery_offset={recovery_offset}
bootcmd=run storeboot
bootdelay=1
bootup_offset=0x1133b50
bootup_size=0x5eec7a
btmac=00:00:00:00:00:00
cmdline_keys=keyman init 0x1234; setkeys;
colorattribute=444,12bit
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_index=24
display_height=576
display_layer=osd1
display_width=720
dtb_mem_addr=0x1000000
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi;
fb_addr=0x3d800000
fb_height=1080
fb_width=1920
fdt_high=0x20000000
firstboot=0
frac_rate_policy=1
fs_type=ro rootwait skip_initramfs
hdmimode=1080p60hz
identifyWaitTime=750
init_display=get_rebootmode;echo reboot_mode:::: ${reboot_mode};if test ${reboot_mode} = quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;osd open;osd clear;else if test ${reboot_mode} = recovery_quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;osd open;osd clear;else setenv reboot_mode_android normal;run storeargs;osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale; fi;fi;
initargs=init=/init console=ttyS0,115200 no_console_suspend earlycon=aml_uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000
jtag=apao
loadaddr=1080000
lock=10001000
maxcpus=4
outputmode=576cvbs
page_trace=on
preboot=run cmdline_keys;run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;bcb uboot-command;run switch_bootmode;
reboot_mode=cold_boot
reboot_mode_android=normal
recovery_from_flash=get_valid_slot;echo active_slot: ${active_slot};if test ${active_slot} = normal; then setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if itest ${upgrade_step} == 3; then if ext4load mmc 1:2 ${dtb_mem_addr} /recovery/dtb.img; then echo cache dtb.img loaded; fi;if ext4load mmc 1:2 ${loadaddr} /recovery/recovery.img; then echo cache recovery.img loaded; wipeisb; bootm ${loadaddr}; fi;else fi;if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi;else setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part=${boot_part} recovery_offset=${recovery_offset};if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;fi;
recovery_from_udisk=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_offset=0
recovery_part=recovery
region=none
rpmb_state=0
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serialno=26919800002433906
sn2=3236393139383030303032343333393036
stderr=serial
stdin=serial
stdout=serial
storeargs=get_rebootmode;setenv bootargs ${initargs} ${fs_type} reboot_mode_android=${reboot_mode_android} androidboot.selinux=${EnableSelinux} logo=${display_layer},loaded,${fb_addr},${outputmode} maxcpus=${maxcpus} vout=${outputmode},enable hdmimode=${hdmimode} frac_rate_policy=${frac_rate_policy} cvbsmode=${cvbsmode} hdmitx=${cecconfig},${colorattribute} cvbsdrv=${cvbs_drv} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.veritymode=enforcing androidboot.hardware=amlogic androidboot.btmacaddr=${btmac} androidboot.wifimac=${wifimac} androidboot.wificountrycode=${wifi_ccode} androidboot.bootloader=${bootloader} androidboot.serialno=${serialno} androidboot.boardid=${boardid} androidboot.region=${region} androidboot.reboot_mode=${reboot_mode};setenv bootargs ${bootargs} page_trace=${page_trace};setenv bootargs ${bootargs} androidboot.rpmb_state=${rpmb_state};
storeboot=get_system_as_root_mode;echo system_mode: ${system_mode};if test ${system_mode} = 1; then setenv fs_type ro rootwait skip_initramfs;run storeargs;fi;get_valid_slot;get_avb_mode;echo active_slot: ${active_slot} avb2: ${avb2};if test ${active_slot} != normal; then setenv bootargs ${bootargs} androidboot.slot_suffix=${active_slot};fi;if test ${avb2} = 0; then if test ${active_slot} = _a; then setenv bootargs ${bootargs} root=/dev/mmcblk0p23;else if test ${active_slot} = _b; then setenv bootargs ${bootargs} root=/dev/mmcblk0p24;fi;fi;fi;if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;run update;
switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then setenv reboot_mode_android normal;run storeargs;run recovery_from_flash;else if test ${reboot_mode} = update; then setenv reboot_mode_android normal;run storeargs;run update;else if test ${reboot_mode} = quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;else if test ${reboot_mode} = recovery_quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;run recovery_from_flash;else if test ${reboot_mode} = cold_boot; then setenv reboot_mode_android normal;run storeargs;else if test ${reboot_mode} = fastboot; then setenv reboot_mode_android normal;run storeargs;fastboot;fi;fi;fi;fi;fi;fi;if monitor_bt_cmdline; then run update; fi;
system_mode=1
try_auto_burn=update 700 750;
update=run try_auto_burn; if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi;
upgrade_step=2
usb_burning=update 1000
wifi_ccode=US
wifimac=00:00:00:00:00:00
wipe_cache=successful
wipe_data=successful
Environment size: 7334/65532 bytes
I'm not sure if imgread is being called by the normal boot process, or a recovery process because the device failed to boot.
At the uart prompt type:
imgread dtb boot 0x1000000
imgread kernel boot 0x1080000
bootm 0x1080000
and post the output.
If it's the same error as before, the boot partition might not be flashed with the correct image.
gxl_aquaman_v1#imgread dtb boot 0x1000000
Err imgread(L220):Fmt unsupported! only support 0x3
gxl_aquaman_v1#imgread kernel boot 0x1080000
Err imgread(L328):Fmt unsupported!genFmt 0x0 != 0x3
gxl_aquaman_v1#imgread kernel boot 0x1080000
Err imgread(L328):Fmt unsupported!genFmt 0x0 != 0x3
gxl_aquaman_v1#<INTERRUPT>
gxl_aquaman_v1#bootm 0x1080000
aml log : Sig Check 1830
kedzior.kedzior said:
gxl_aquaman_v1#imgread dtb boot 0x1000000
Err imgread(L220):Fmt unsupported! only support 0x3
Click to expand...
Click to collapse
Are you able to flash the boot partition with the boot image again?
Which version of the firmware did you flash?
Are you able to flash the boot partition with the boot image again?
Yes
Which version of the firmware did you flash?
https://disk.yandex.ru/d/aL5XolrdAbTJ0g How to check it?
Other than this one I have no other
Did you flash it with fastboot or burn mode?
According to the instructions from the post https://forum.xda-developers.com/t/help-please-mdz-24-aa-no-power-led-no-video.4452819/post-87044521
but one of the commands "fastboot oem unlock" not working
"astboot flashing unlock" worked
"fastboot flashing unlock_critical" worked
I notice from the environment that the bootloader is currently locked.
The russian guy in the video mentioned that it is important to keep the older version of the bootloader, because the newer version could lock you out.
What I would try is starting fastboot, and then using the ota source files, flashing all of the partitions again, except NOT the bootloader.
What you could try first is just flashing the boot partition again from whatever firmware you used the last time.
Unfortunately, I do not have the previous works version :/
kedzior.kedzior said:
https://disk.yandex.ru/d/aL5XolrdAbTJ0g How to check it?
Click to expand...
Click to collapse
I will check that version, and will also check which version is the newest version.
At the uart prompt, type:
get_bootloaderversion
and post the version.
Functioner said:
At the uart prompt, type:
get_bootloaderversion
and post the version.
Click to expand...
Click to collapse
gxl_aquaman_v1#get_bootloaderversion
Nieznane polecenie 'get_bootloaderversion' - spróbuj 'help'
C:\adb>fastboot getvar version-bootloader
version-bootloader: U-Boot 2015.01-g2e3e77d-dirty
Finished. Total time: 0.003s
The version of the firmware in backup-Restore.rar from the above yandex link is r293:
Xiaomi/aquaman/aquaman:9/PI/293:user/release-keys
This is quite old. It's from May 26 2020.
If you flashed the tee image from that download, it could have corrupted your device.
thank you very much for your help and your time. I will continue to try to bring my stick back to life
kedzior.kedzior said:
thank you very much for your help and your time. I will continue to try to bring my stick back to life
Click to expand...
Click to collapse
sure, good luck.

Categories

Resources