Database Info

[Q] what have i done wrong here (Root ics)

ive just followed this thread http://forum.xda-developers.com/showthread.php?t=2144738
and this was the output from the window
Code:
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 255028
usb_write 4
usb_write 255028
** Done **
< waiting for device >
sending 'recovery' (6187 KB)...
OKAY [ 3.219s]
writing 'recovery'...
OKAY [ 0.766s]
finished. total time: 3.984s
You chooesd ICS//TWRP Recovery
waiting for OMAP44xx device...
when i try any combination of keys to go into recovery its just a black screen. any ideas? id it actually finish? when it says waiting for omap44xx device i tried unplugging and plugging in the cable but it did nothing

just tried to reboot normally and it says security error

if anyone can get this up and running ill thank every one of their posts for a week... i cant believe its gone wrong for me AGAIN

seriously panicing now, cant get into SW mode, i can get into fastboot and SW via wpark but the flash wont go past 17%

flash process now gets to 30% and quits

I got security error as well with that tutorial. Flashing bootloaders and recovery using this http://forum.xda-developers.com/showthread.php?t=1978543 helped.
Also - I used SmartFlash to flash bin and fls

Lg p920 ressurection

you have soft bricked or hard your Phone its easy
Now just follow the Steps and do it properly
And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Tools and files needed :-
1-bootv21e.rar from here http://d-h.st/RC5 and after downloading this file unrar it by any unzip or unrar software
2- lg usb drivers and usb cable of LG from here http://csmg.lgmobile.com:9002/data/L...in7_LGEAll.zip
3-http://csmg.lgmobile.com:9002/data/S...shTool_1.1.zip is the LG FLASH tool
4-download the .dll file from here http://www.mediafire.com/?mc6ia9o8iqwqndw
5- Optional Smart flashtool if you get get through the KEy of LG flash tool but this would be hactic and you would also need lg support tool for imei fix download links
-https://docs.google.com/file/d/0B8IkQjiPjX_DS2s1NC1zVGtLWDQ/edit?pli=1 smartflash tool
-Google LG suppot tool
Before you start READ THE GUIDE once so you can understand it and then proceed with repair.
http://d-h.st/U08 omap4420 wkparks
and google omap flashinstaller
Step1.
Install LGflashtool (also copy/paste crack)
P920 users should run LG FlashTool and load BOOTV21E_AP.bin (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
SU760 users should run LG FlashTool and load SU760V10GROM (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
Step 2.
Extract WKPARKS omap4boot and follow installation steps:
Install OMAP4430 USB driver
Quote:
If you plug your Phone on PC without battery, OMAP4430 device appeared for seconds and then disappeared in your Windows Device Manager
(check arsen4oo photo guide in post #3)
On windows 7 sometimes OMAP4430 flashes too fast so you cant install driver.
There is a a windows feature that will help you install the driver easier.
To view devices that were once installed but are no longer attached to the computer, open a Command Prompt window using the Run As Administrator option and enter the command:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then, from the same command prompt, type devmgmt.msc to open Device Manager. Choose View, Show Hidden Devices. The new instance of Device Manager will show “ghosted” entries for devices that were once present. This technique is especially useful for fixing problems caused by leftover drivers after replacing a network card or video card—you can easily delete the ghosted device or update the OMAP4430 driver.
After driver installation ends remove usb cable BUT keep windows device manager open.
Step 3. Run start_fastboot.bat and select option 2
Step 4. Pull out battery
Step 5. Hold Vol+
Step 6. Connect USB cable, the usbboot will start
Step 7. Insert battery while the usbboot is waiting
Step 8. Script tells you to remove cable but i dont think it's necessary in this version
Step 9. Release Vol+ and look in your Windows Device manager
If everything worked ok your phone got recognised and now you are in downoad mode.
Step 10. Change LG USB Serial Port according to LG FlashTool Guide to port 41.
Step 11. Remove cable and battery from P920/SU760
Step 12. Set LG FlashTool ready for flashing.
Step 13. Run Steps 3-9 again and you will see your phone being flashed from LG FlashTool.
It will be stopped at 26-30% because phone will turn off on its own BUT the next time you try to enter NORMAL DOWNLOAD MODE it will be available again.
Step 14. Set LG FlashTool ready to flash your P920 with BOOTV21E_AP.bin again.
SU760 users should use SU760V10GROM bin .
Step 15. Put your phone in DOWNLOAD MODE without using omap4boot this time.
Step 16. LG FlashTool will recognise the phone and flash it completely this time.
P920 after reboot will go to CWM. You can flash your personal backup or reboot to STOCK V21E.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5-Restoring IMEI
a.Connect phone by USB
b.Activate USB debug mode
c.Enter 3845#*920# in dialer if that doesn’t work try 3845#*925# or 3845#*720# if device is SU760
d.Select Port Settings -> Select CP Image Download
e.A new device should appear at let it install
f.Open Tutty (or hyperterminal) and select serial protocol. Click on open
g.Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
h.Type at%imei, it should display a dummy IMEI
i.Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x where x,x,x... is your orginal IMEI number (found under the battery of your phone). It should response IMEI WRITE OK
j.Reboot phone
if u dont understand it LG support tool will so
6-now open lg suppot tool and remove battery follow step 4 till u get the download mode with S/w and something written in chinese and wait till phone is detected now click customer Support and then recovery Phone then you will be asked for imei insert the imei and it will recognise ur pphone press ok depending on the speed of ur internet connection it will take the time to download the files and update ur phone let the whole procedure complete with me it took around one hour
7- after the process is completed disconnected the phone insert battery and boot ur phoen again it will boot and now again u will find the same issue but this time the trick is simple and easy ur internal memory curropted so format it u will get around 5.57gb and then .Enter 3845#*920# in dialer and do a factory reset or a normal factory reset after reset ur phone wll boot and display android and a package and the loading bar this means the phone is fixed with imei and u will get what you need have a look at the attachment and the vidoe on youtube i have posted [YOUTUBE]http://www.youtube.com/watch?v=BR1_jrsAibk[YOUTUBE]
the last step of factory reset is essential or you wont fix the imei
all the best
download reebooter utility from here http://d-h.st/24C
and do this
Info:
This utility will not work if you don't have Omap Drivers installed
Select task:
1. Flash ICS FastbootLoaders+Recovery
2. Flash V21E Loaders+Recovery
x. Exit
----------------------------------------
Please select 1,2 or exit(x): 2
Ready to Flash V21E+recovery
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 40a11fbe08c36fb34f6a113fc2516c63395c7947
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 232512
usb_write 4
usb_write 232512
** Done **
< waiting for device >
sending 'recovery' (5854 KB)...
OKAY [ 3.012s]
writing 'recovery'...
OKAY [ 1.230s]
finished. total time: 4.252s
sending 'u-boot' (512 KB)...
OKAY [ 0.268s]
writing 'u-boot'...
OKAY [ 0.355s]
finished. total time: 0.627s
sending 'x-loader' (128 KB)...
OKAY [ 0.070s]
writing 'x-loader'...
OKAY [ 0.051s]
finished. total time: 0.127s
Loaders have been flashed.
Your P920 is ready to boot into GB again. Reboot.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
GOOD LUCK and lets get those bricks fixed.
TROUBLESHOOTING
If you get the Silver LG Screen u are on Fastboot mode
if you get a message like usb not recognised then u probably have a faulty cable
all the Best f++k the Brick:good:
If something doesn't work for you make a post describing exactly what you did , your phone model and your operating system.
Before making pointless posts READ THE GUIDE.
If you don't know how to make one of the recovery programs work READ THEIR GUIDE .
You can find links in the end of this post.
http://forum.xda-developers.com/showthread.php?p=18134614
http://forum.xda-developers.com/showthread.php?t=1629307
http://forum.xda-developers.com/showthread.php?t=1244490
http://forum.xda-developers.com/showthread.php?t=1540163
Sent from my LG-P920 using xda premium
I will edit this thread for the atachments so wait for it

And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Sent from my LG-P920 using xda premium

This is more or less a duplicate of the thread below
http://forum.xda-developers.com/showthread.php?t=1942836&page=58
Thread Closed

[Q] Bricked p920 can't enter Fastboot

Hello, i have a big problem. Since yesterday i try to revive my bricked p920, but without sucess.
After flashing the ICS update with the LG flasher
the display stayed black. I tried many "how to's" on how to enter the fastboot mode, but without sucess.
Code:
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p920emu - Optimus 3D (P920 EMU)
[4] p940 - Prada 3.0 (P940)
[5] su540 - Prada 3.0 (SU540/KU5400)
[6] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device : 2
p920 selected
============================================================
You have to hold volume-up button to enter S/W donwload mode
============================================================
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x2
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 12bd240a5cbb4df74165e28847c766b87268a144
MPKH: 6d473e6a0470e01a52601081128b053b74490ee000000000000000000000000
CRC0: 31b46fa0
CRC1: 611e8642
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
1. I already tried omap4boot 1.21 and 1.25a
2. I already tried a different computer.
3. I Installed the driver, OMAP 4430 USB is recognized at the pc.
4. I am using Windows 7 64bit
5. I am startign with battery out, connecting then after or while wait 5 sec, putting bat back in. Tried with VOL +, without VOL +, With battery and without, tried almost all compination possible.
Does someone have an idea ? What else could i try ?

Daniil S. said:
Hello, i have a big problem. Since yesterday i try to revive my bricked p920, but without sucess.
After flashing the ICS update with the LG flasher
the display stayed black. I tried many "how to's" on how to enter the fastboot mode, but without sucess.
Code:
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p920emu - Optimus 3D (P920 EMU)
[4] p940 - Prada 3.0 (P940)
[5] su540 - Prada 3.0 (SU540/KU5400)
[6] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device : 2
p920 selected
============================================================
You have to hold volume-up button to enter S/W donwload mode
============================================================
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x2
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 12bd240a5cbb4df74165e28847c766b87268a144
MPKH: 6d473e6a0470e01a52601081128b053b74490ee000000000000000000000000
CRC0: 31b46fa0
CRC1: 611e8642
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
1. I already tried omap4boot 1.21 and 1.25a
2. I already tried a different computer.
3. I Installed the driver, OMAP 4430 USB is recognized at the pc.
4. I am using Windows 7 64bit
5. I am startign with battery out, connecting then after or while wait 5 sec, putting bat back in. Tried with VOL +, without VOL +, With battery and without, tried almost all compination possible.
Does someone have an idea ? What else could i try ?
Click to expand...
Click to collapse
Use the omap4boot (EMU version) from here http://forum.xda-developers.com/showthread.php?t=2246001 and folloe the guide's steps.

Karim Kahale said:
Use the omap4boot (EMU version) from here http://forum.xda-developers.com/showthread.php?t=2246001 and folloe the guide's steps.
Click to expand...
Click to collapse
Thank you, but i end up with the same problem. Any other ideas ?

Daniil S. said:
Thank you, but i end up with the same problem. Any other ideas ?
Click to expand...
Click to collapse
Try another port, reinstall omap drivers, change usb cable, try different pc.

try v1.2 of this tool

Karim Kahale said:
Try another port, reinstall omap drivers, change usb cable, try different pc.
Click to expand...
Click to collapse
Thank you, but used a different pc (New Driver install, different port...) same thing there. Also tried the ALLINONE Tool 1.2, and also replaced the cable...

Daniil S. said:
Thank you, but used a different pc (New Driver install, different port...) same thing there. Also tried the ALLINONE Tool 1.2, and also replaced the cable...
Click to expand...
Click to collapse
go back to LG Flash tools and flash "28b large partition" by xbsall and then install the 1.25 bootloader.

p-vlad said:
go back to LG Flash tools and flash "28b large partition" by xbsall and then install the 1.25 bootloader.
Click to expand...
Click to collapse
Can you find a "how to" for what you told me to do ? Sorry, not a pro =)

Daniil S. said:
Can you find a "how to" for what you told me to do ? Sorry, not a pro =)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39269819

drastic00 said:
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
you were faster
do it till point 6.. then you can install you favorite ROM/MOD

drastic00 said:
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
Followed this how to till f6 - f7, the phone is not beeng recognized as "LGE CDMA USB SERIAL PORT" or simmilar, no drivers are installed. It shows up for a second as "OMAP4430" as before, and disappears again. Battery is not in the phone, connecting while Vol +
Am i doing something wrong ? And yes, the OMAP driver is installed, rebooted ect..

Daniil S. said:
Followed this how to till f6 - f7, the phone is not beeng recognized as "LGE CDMA USB SERIAL PORT" or simmilar, no drivers are installed. It shows up for a second as "OMAP4430" as before, and disappears again. Battery is not in the phone, connecting while Vol +
Am i doing something wrong ? And yes, the OMAP driver is installed, rebooted ect..
Click to expand...
Click to collapse
Did you install LG drivers ?

Karim Kahale said:
Did you install LG drivers ?
Click to expand...
Click to collapse
Yes, installed, uninstalled, reinstalled. Currently, they are installed.

Daniil S. said:
Yes, installed, uninstalled, reinstalled. Currently, they are installed.
Click to expand...
Click to collapse
Did you try another PC ?

Karim Kahale said:
Did you try another PC ?
Click to expand...
Click to collapse
Yes, two computers, all USB ports, two cables... Both Win 7 64bit, but it shouldn't be a prob.

Daniil S. said:
Yes, installed, uninstalled, reinstalled. Currently, they are installed.
Click to expand...
Click to collapse
I suggest rechecking driver install carefully. Disable all antivirus before downloading or extracting anything.

drastic00 said:
I suggest rechecking driver install carefully. Disable all antivirus before downloading or extracting anything.
Click to expand...
Click to collapse
Just reinstalled everything, disabled antivirus, uninstalled ALL DRIVERS, rebooted, installed drivers again. Same thing, installing OMAP4430 drivers like described, everything okay. Disconnecting phone, connecting again while pressing V+ and no battery, it installs as OMAP4430 and not "LGE CDMA USB SERIAL PORT" or "LG USB driver".

Daniil S. said:
Just reinstalled everything, disabled antivirus, uninstalled ALL DRIVERS, rebooted, installed drivers again. Same thing, installing OMAP4430 drivers like described, everything okay. Disconnecting phone, connecting again while pressing V+ and no battery, it installs as OMAP4430 and not "LGE CDMA USB SERIAL PORT" or "LG USB driver".
Click to expand...
Click to collapse
There are two separate times that the phone is connected to pc in the driver install process. Once while forcing omap win usb to install... After that, another when LG Drivers take. If you had wkpark bootloaders, check that detail. If you were unable to catch and force omap4430 to install under other devices, check that detail. Be sure you are using the driver from the fastboot folder, not in the omap 4 flash installer folder. Part 1 is tricky the first few times you do it. Don't be in a hurry. Read carefully. The devil is in the details.

drastic00 said:
There are two separate times that the phone is connected to pc in the driver install process. Once while forcing omap win usb to install... After that, another when LG Drivers take. If you had wkpark bootloaders, check that detail. If you were unable to catch and force omap4430 to install under other devices, check that detail. Be sure you are using the driver from the fastboot folder, not in the omap 4 flash installer folder. Part 1 is tricky the first few times you do it. Don't be in a hurry. Read carefully. The devil is in the details.
Click to expand...
Click to collapse
At first, what's the wkpark bootloader ? I had 2.3.3 Original ROM branded by T-Mobile Germany, was updating to ICS German after what it died.
Yes there are two times i connect the phone. At first it shows up in devices, i install the omap driver. Disconnect, connect again with vol up and no batt, and it should automatically as "LG USB" as i understand, but it is only recognized as the omap3340 that i installed previously. nothing more.

Daniil S. said:
At first, what's the wkpark bootloader ? I had 2.3.3 Original ROM branded by T-Mobile Germany, was updating to ICS German after what it died.
Yes there are two times i connect the phone. At first it shows up in devices, i install the omap driver. Disconnect, connect again with vol up and no batt, and it should automatically as "LG USB" as i understand, but it is only recognized as the omap3340 that i installed previously. nothing more.
Click to expand...
Click to collapse
If you had custom bootloader the LG logo would always be grey when you started the phone so probably not.
Battery is always out of the phone when doing driver install, the whole time.
Did you uninstall all things LG in Programs and Features and reboot pc before beginning? There would have been LG drivers and software left on your pc from your flash attempt that have to be removed first.
When you ran the 2 LG driver installers in the pack, you should have seen a warning one is unsigned, about 3 times. PC should especially be restarted after that too.
I would triple check everything. I can't imagine a bad flash would screw up your phone this bad, but it's possible that you can't enter 'normal download mode,'
If you are totally, completely sure that everything was done correctly you might then look at xbsall's unbrick guide or Karim Kahale's unbrick guide.
The good news is O3D can't be killed unless you hit it with a hammer.

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

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.