Hi. I'm having a problem. I have a S905X box from a Portuguese Company that was given to me, I've been flashing ROM's on it for a while, ATVXperience, Poison, and another Pie Android TV one, even Libreelec, Coreelec, Armbian, everything worked fine on it. But I flashed a ROM I found on Freaktab that was a Port from S905X2 to S905X, the ROM booted and worked fine but when I was reflashing the regular ROM I used the amlogic program started giving me errors, I don't remember what I did but after a while the box flashed the ROM but took like 12 minutes to flash, where usually takes 4, I connected the BOX to the TV and the LED doesn't even turn on, just the digital audio input and the ethernet port light up, usually when it's connected to the PC the led is pink, now the led doesn't work but the PC recognizes but when flashing a ROM. The box doesn't even have a reset buton, usually I connect to the PC and works, when it doesn't shorting the pin's works. But now simply the box is dead and I don't know why, if I flash from the PC I get the same error "[0x32030201]Uboot/Get result/DiskInitial error" (I will attach the full log bellow) and if I do it with the SD Card it get's stuck on a loop or simply freezes. I don't know what to do, the only thing I have from the original firmware is a TWRP backup. I tried all sorts of stuff online and I couldn't find a way to "revive it", if I could find a way to boot Libreelec or something from the SD Card I would be happy. I also will attach pictures of the board.
Full log
Code:
[15:22:24 996][Global][Inf]--USB_Burning_Tool soft Version: V2.1.9.0
[15:22:24 996][Global][Inf]--Windows Version: Microsoft Windows 10, Bit: 64
[15:22:25 001][Global][Inf]--Scan usb device
[15:22:25 001][Global][Inf]--Aml scan WorldCup Device
[15:22:25 005][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:25 005][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:25 005][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 005][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 007][Global][Inf]---------->[Port0]Other device
[15:22:25 007][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:25 008][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:25 008][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:25 009][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:25 009][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:25 009][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 107][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 107][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:25 107][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port2]Other device
[15:22:25 108][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:25 108][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:25 108][Global][Inf]--Scan USB host controller complete
[15:22:25 108][Global][Inf]--Update data center with HubMap
[15:22:25 108][Global][Inf]--Insert new hub2
[15:22:25 108][Global][Inf]--Update hub2 device data
[15:22:25 108][Global][Inf]--Update HUB2-1
[15:22:25 108][HUB2-1][Inf]--Update device path
[15:22:25 108][Global][Inf]--Update HUB2-2
[15:22:25 108][HUB2-2][Inf]--Update device path
[15:22:25 108][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:25 108][HUB2-3][Inf]--Update device path
[15:22:25 109][Global][Inf]--Begin thread for HUB2-3
[15:22:25 109][Global][Inf]--Burning thread HUB2-3 start
[15:22:25 109][Global][Inf]--Update HUB2-4
[15:22:25 109][HUB2-4][Inf]--Update device path
[15:22:25 109][Global][Inf]--Burning thread HUB2-3 begin run
[15:22:25 109][Global][Inf]--Update HUB2-5
[15:22:25 109][HUB2-5][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-6
[15:22:25 109][HUB2-6][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-7
[15:22:25 109][HUB2-7][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-8
[15:22:25 109][HUB2-8][Inf]--Update device path
[15:22:25 109][Global][Inf]--Add Hub2: \\.\USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8} to m_HubDeviceDataVector
[15:22:25 109][Global][Inf]--Scan end
[15:22:29 719][Global][Inf]--User click open button
[15:22:35 909][Global][Inf]--Image path C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:35 910][Global][Inf]--OpenImg C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:48 951][Global][Inf]--check img crc success!
[15:22:48 951]Parse platform.conf
[15:22:48 966][Global][Inf]--Parsing burning package
[15:22:48 966][Global][Inf]--Load configuration file C:\Program Files (x86)\Amlogic\USB_Burning_Tool\temp
[15:22:48 966][Global][Inf]--Parse burning configuration file C:\Program Files (x86)\Amlogic\USB_Burning_Tool\temp\burn_config.xml
[15:22:48 982][Global][Inf]--Get burning key
[15:22:51 026][Global][Inf]--User click start button
[15:22:51 028][Global][Inf]--SetErase
[15:22:51 028][Global][Inf]--Enable burning 1
[15:22:51 028][Global][Inf]--Scan usb device
[15:22:51 028][Global][Inf]--Aml scan WorldCup Device
[15:22:51 029][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:51 029][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:51 029][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 029][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 030][Global][Inf]---------->[Port0]Other device
[15:22:51 030][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:51 030][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:51 030][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:51 031][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:51 031][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:51 031][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 045][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:51 096][HUB2-3][Inf]--CloneImageProxy
[15:22:51 096][Global][Inf]--OpenImg C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:51 096][HUB2-3][Inf]--Connect path=Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26/P0/P0/P2
[15:22:51 096][HUB2-3][Inf]--Start burning...
[15:22:51 132][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 132][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:51 132][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port2]Other device
[15:22:51 133][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:51 133][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:51 133][Global][Inf]--Scan USB host controller complete
[15:22:51 133][Global][Inf]--Update data center with HubMap
[15:22:51 133][Global][Inf]--Update hub2 device data
[15:22:51 133][Global][Inf]--Update HUB2-1
[15:22:51 133][HUB2-1][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-2
[15:22:51 133][HUB2-2][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:51 133][HUB2-3][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-4
[15:22:51 133][HUB2-4][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-5
[15:22:51 133][HUB2-5][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-6
[15:22:51 133][HUB2-6][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-7
[15:22:51 133][HUB2-7][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-8
[15:22:51 133][HUB2-8][Inf]--Update device path
[15:22:51 133][Global][Inf]--Scan end
[15:22:51 147][HUB2-3][Inf]--------------ERASE BOOTLOADER------------
[15:22:51 248][HUB2-3][Inf]--start SendIdentifyCmd
[15:22:51 249][HUB2-3][Inf]--2-2-0-0
[15:22:51 249][HUB2-3][Inf]-------------Download DDR.USB-----------
[15:22:51 249][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:22:51 299][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:51 358][HUB2-3][Inf]--2-2-0-0
[15:22:51 358][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[15:22:51 859][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x00005183
[15:22:52 359][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[15:22:52 860][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x00005183
[15:22:53 361][HUB2-3][Inf]--Write initial succeed
[15:22:53 361][HUB2-3][Inf]--Upload encrypt at 0xc8100228
[15:22:53 361][HUB2-3][Inf]--ulValue = 0xadfc318c
[15:22:53 361][HUB2-3][Inf]--Read encrypt value succeed
[15:22:53 361][HUB2-3][Inf]--Download DDR.USB,size: 49152!
[15:22:53 372][HUB2-3][Inf]--Transfer complete 49152
[15:22:53 372][HUB2-3][Inf]--Run at address 0xd9000000
[15:22:53 373][HUB2-3][Inf]--RunInRam success
[15:22:53 385][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 385][HUB2-3][Inf]--CheckFileRunState return 8
[15:22:53 385][HUB2-3][Inf]--Run at address 0xd900c000
[15:22:53 386][HUB2-3][Inf]--RunInRam succeed
[15:22:53 553][HUB2-3][Inf]--runResult:0x 0,paraMagic:0x7856efab
[15:22:53 553][HUB2-3][Inf]--ddrCapacity:0x 800
[15:22:53 553][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 553][HUB2-3][Inf]-------------Download UBOOT.USB-----------
[15:22:53 553][HUB2-3][Inf]--Get Encrpt ulValue = 0xadfc318c
[15:22:53 553][HUB2-3][Err]--download 1 time!
[15:22:53 553][HUB2-3][Inf]--Download UBOOT.USB buffer at 0x0200c000
[15:22:53 660][HUB2-3][Inf]--Transfer complete
[15:22:53 860][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 860][HUB2-3][Inf]--DownCheckPara succeed
[15:22:53 860][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 860][HUB2-3][Inf]--RunInAddr at address 0xd900c000
[15:22:53 907][HUB2-3][Inf]--ReadCheckPara succeed
[15:22:53 907][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 907][HUB2-3][Inf]--DownRunPara succeed
[15:22:53 907][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 907][HUB2-3][Inf]--RunInAddr at address 0xd900c000
[15:22:55 276][Global][Inf]--Catch DBT_DEVICEREMOVECOMPLETE
[15:22:55 277][Global][Inf]--Scan usb device
[15:22:55 277][Global][Inf]--Aml scan WorldCup Device
[15:22:55 280][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:55 280][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:55 280][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 281][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 282][Global][Inf]---------->[Port0]Other device
[15:22:55 282][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port2]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:55 283][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:55 283][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:55 283][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:55 286][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:55 286][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:55 286][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 385][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 385][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:55 385][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port2]Other device
[15:22:55 386][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:55 386][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:55 386][Global][Inf]--Scan USB host controller complete
[15:22:55 386][Global][Inf]--Update data center with HubMap
[15:22:55 386][Global][Inf]--Update hub2 device data
[15:22:55 386][Global][Inf]--Update HUB2-1
[15:22:55 386][HUB2-1][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-2
[15:22:55 386][HUB2-2][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-3
[15:22:55 386][HUB2-3][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-4
[15:22:55 386][HUB2-4][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-5
[15:22:55 386][HUB2-5][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-6
[15:22:55 386][HUB2-6][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-7
[15:22:55 386][HUB2-7][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-8
[15:22:55 386][HUB2-8][Inf]--Update device path
[15:22:55 387][Global][Inf]--Scan end
[15:22:55 391][HUB2-3][Inf]--Device is removed
[15:22:56 477][Global][Inf]--Catch DBT_DEVICEARRIVAL
[15:22:56 477][Global][Inf]--Scan usb device
[15:22:56 477][Global][Inf]--Aml scan WorldCup Device
[15:22:56 482][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:56 482][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:56 482][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 482][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 482][Global][Inf]---------->[Port0]Other device
[15:22:56 482][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:56 482][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:56 482][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:56 487][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:56 487][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:56 487][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 588][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 588][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port2]Other device
[15:22:56 588][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:56 588][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:56 588][Global][Inf]--Scan USB host controller complete
[15:22:56 588][Global][Inf]--Update data center with HubMap
[15:22:56 588][Global][Inf]--Update hub2 device data
[15:22:56 588][Global][Inf]--Update HUB2-1
[15:22:56 588][HUB2-1][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-2
[15:22:56 588][HUB2-2][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:56 588][HUB2-3][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-4
[15:22:56 588][HUB2-4][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-5
[15:22:56 588][HUB2-5][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-6
[15:22:56 588][HUB2-6][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-7
[15:22:56 588][HUB2-7][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-8
[15:22:56 588][HUB2-8][Inf]--Update device path
[15:22:56 588][Global][Inf]--Scan end
[15:22:56 628][HUB2-3][Inf]--Device is connected
[15:22:56 628][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:22:56 678][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:59 759][HUB2-3][Inf]--0-7-0-16
[15:22:59 759][HUB2-3][Inf]--CheckFileRunState succeed
[15:22:59 759][HUB2-3][Inf]-- low_power
[15:22:59 759][HUB2-3][Inf]--Send command success
[15:22:59 759][HUB2-3][Inf]--Read command status success
[15:22:59 759][HUB2-3][Inf]-------------Download meson1.dtb-----------
[15:22:59 759][HUB2-3][Inf]--0-7-0-16
[15:22:59 759][HUB2-3][Inf]--Enc(0xadfc318c)
[15:22:59 759][HUB2-3][Inf]-- download mem dtb normal 116736
[15:22:59 759][HUB2-3][Inf]--Send download command success
[15:22:59 779][HUB2-3][Inf]--Read command status success
[15:22:59 794][HUB2-3][Inf]--Transfer complete
[15:22:59 794][HUB2-3][Inf]--Send download get_status command succeed
[15:22:59 794][HUB2-3][Inf]--get_status success
[15:23:00 305][HUB2-3][Inf]-------------ERASE FLASH-----------
[15:23:02 305][HUB2-3][Inf]--send command diskinit
[15:23:02 305][HUB2-3][Inf]--disk_initial 1
[15:23:02 306][HUB2-3][Inf]--Send command success
[15:23:04 181][HUB2-3][Err]--failed:[15:23:04 181][HUB2-3][Inf]--Read command diskinit status
[15:23:04 181][HUB2-3][Err]--Check command return failed
[15:23:04 259][HUB2-3][Err]--[0x32030201]Uboot/Get result/DiskInitial error
[15:23:04 259][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:23:05 690][Global][War]--User click stop button
[15:23:05 691][Global][Inf]--Enable burning 0
{
"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"
}
using usb burning tool delete "bootloader" only and unplug the device, flash original "uboot.bin" for your device to microsd with BootcardMaker.
copy to microsd aml_sdc_burn.ini (edit to match your fw), originalfw.img and "uboot.bin".
turn off the device and insert microsd the turn on again, now it should be "upgrading" screen.
DiogoSilva48 said:
Hi. I'm having a problem. I have a S905X box from a Portuguese Company that was given to me, I've been flashing ROM's on it for a while, ATVXperience, Poison, and another Pie Android TV one, even Libreelec, Coreelec, Armbian, everything worked fine on it. But I flashed a ROM I found on Freaktab that was a Port from S905X2 to S905X, the ROM booted and worked fine but when I was reflashing the regular ROM I used the amlogic program started giving me errors, I don't remember what I did but after a while the box flashed the ROM but took like 12 minutes to flash, where usually takes 4, I connected the BOX to the TV and the LED doesn't even turn on, just the digital audio input and the ethernet port light up, usually when it's connected to the PC the led is pink, now the led doesn't work but the PC recognizes but when flashing a ROM. The box doesn't even have a reset buton, usually I connect to the PC and works, when it doesn't shorting the pin's works. But now simply the box is dead and I don't know why, if I flash from the PC I get the same error "[0x32030201]Uboot/Get result/DiskInitial error" (I will attach the full log bellow) and if I do it with the SD Card it get's stuck on a loop or simply freezes. I don't know what to do, the only thing I have from the original firmware is a TWRP backup. I tried all sorts of stuff online and I couldn't find a way to "revive it", if I could find a way to boot Libreelec or something from the SD Card I would be happy. I also will attach pictures of the board.
Full log
Code:
[15:22:24 996][Global][Inf]--USB_Burning_Tool soft Version: V2.1.9.0
[15:22:24 996][Global][Inf]--Windows Version: Microsoft Windows 10, Bit: 64
[15:22:25 001][Global][Inf]--Scan usb device
[15:22:25 001][Global][Inf]--Aml scan WorldCup Device
[15:22:25 005][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:25 005][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:25 005][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 005][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 007][Global][Inf]---------->[Port0]Other device
[15:22:25 007][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:25 008][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:25 008][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:25 008][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:25 009][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:25 009][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:25 009][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 107][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:25 107][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:25 107][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port2]Other device
[15:22:25 108][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:25 108][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:25 108][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:25 108][Global][Inf]--Scan USB host controller complete
[15:22:25 108][Global][Inf]--Update data center with HubMap
[15:22:25 108][Global][Inf]--Insert new hub2
[15:22:25 108][Global][Inf]--Update hub2 device data
[15:22:25 108][Global][Inf]--Update HUB2-1
[15:22:25 108][HUB2-1][Inf]--Update device path
[15:22:25 108][Global][Inf]--Update HUB2-2
[15:22:25 108][HUB2-2][Inf]--Update device path
[15:22:25 108][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:25 108][HUB2-3][Inf]--Update device path
[15:22:25 109][Global][Inf]--Begin thread for HUB2-3
[15:22:25 109][Global][Inf]--Burning thread HUB2-3 start
[15:22:25 109][Global][Inf]--Update HUB2-4
[15:22:25 109][HUB2-4][Inf]--Update device path
[15:22:25 109][Global][Inf]--Burning thread HUB2-3 begin run
[15:22:25 109][Global][Inf]--Update HUB2-5
[15:22:25 109][HUB2-5][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-6
[15:22:25 109][HUB2-6][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-7
[15:22:25 109][HUB2-7][Inf]--Update device path
[15:22:25 109][Global][Inf]--Update HUB2-8
[15:22:25 109][HUB2-8][Inf]--Update device path
[15:22:25 109][Global][Inf]--Add Hub2: \\.\USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8} to m_HubDeviceDataVector
[15:22:25 109][Global][Inf]--Scan end
[15:22:29 719][Global][Inf]--User click open button
[15:22:35 909][Global][Inf]--Image path C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:35 910][Global][Inf]--OpenImg C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:48 951][Global][Inf]--check img crc success!
[15:22:48 951]Parse platform.conf
[15:22:48 966][Global][Inf]--Parsing burning package
[15:22:48 966][Global][Inf]--Load configuration file C:\Program Files (x86)\Amlogic\USB_Burning_Tool\temp
[15:22:48 966][Global][Inf]--Parse burning configuration file C:\Program Files (x86)\Amlogic\USB_Burning_Tool\temp\burn_config.xml
[15:22:48 982][Global][Inf]--Get burning key
[15:22:51 026][Global][Inf]--User click start button
[15:22:51 028][Global][Inf]--SetErase
[15:22:51 028][Global][Inf]--Enable burning 1
[15:22:51 028][Global][Inf]--Scan usb device
[15:22:51 028][Global][Inf]--Aml scan WorldCup Device
[15:22:51 029][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:51 029][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:51 029][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 029][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 030][Global][Inf]---------->[Port0]Other device
[15:22:51 030][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:51 030][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:51 030][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:51 030][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:51 031][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:51 031][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:51 031][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 045][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:51 096][HUB2-3][Inf]--CloneImageProxy
[15:22:51 096][Global][Inf]--OpenImg C:\Users\diogo\Downloads\aml_upgrade_package-tx5-atv9-ap6212-1GB-2GB.img
[15:22:51 096][HUB2-3][Inf]--Connect path=Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26/P0/P0/P2
[15:22:51 096][HUB2-3][Inf]--Start burning...
[15:22:51 132][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:51 132][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:51 132][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port2]Other device
[15:22:51 133][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:51 133][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:51 133][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:51 133][Global][Inf]--Scan USB host controller complete
[15:22:51 133][Global][Inf]--Update data center with HubMap
[15:22:51 133][Global][Inf]--Update hub2 device data
[15:22:51 133][Global][Inf]--Update HUB2-1
[15:22:51 133][HUB2-1][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-2
[15:22:51 133][HUB2-2][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:51 133][HUB2-3][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-4
[15:22:51 133][HUB2-4][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-5
[15:22:51 133][HUB2-5][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-6
[15:22:51 133][HUB2-6][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-7
[15:22:51 133][HUB2-7][Inf]--Update device path
[15:22:51 133][Global][Inf]--Update HUB2-8
[15:22:51 133][HUB2-8][Inf]--Update device path
[15:22:51 133][Global][Inf]--Scan end
[15:22:51 147][HUB2-3][Inf]--------------ERASE BOOTLOADER------------
[15:22:51 248][HUB2-3][Inf]--start SendIdentifyCmd
[15:22:51 249][HUB2-3][Inf]--2-2-0-0
[15:22:51 249][HUB2-3][Inf]-------------Download DDR.USB-----------
[15:22:51 249][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:22:51 299][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:51 358][HUB2-3][Inf]--2-2-0-0
[15:22:51 358][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[15:22:51 859][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x00005183
[15:22:52 359][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[15:22:52 860][HUB2-3][Inf]--Control write pll reg1 0xd9000000:0x00005183
[15:22:53 361][HUB2-3][Inf]--Write initial succeed
[15:22:53 361][HUB2-3][Inf]--Upload encrypt at 0xc8100228
[15:22:53 361][HUB2-3][Inf]--ulValue = 0xadfc318c
[15:22:53 361][HUB2-3][Inf]--Read encrypt value succeed
[15:22:53 361][HUB2-3][Inf]--Download DDR.USB,size: 49152!
[15:22:53 372][HUB2-3][Inf]--Transfer complete 49152
[15:22:53 372][HUB2-3][Inf]--Run at address 0xd9000000
[15:22:53 373][HUB2-3][Inf]--RunInRam success
[15:22:53 385][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 385][HUB2-3][Inf]--CheckFileRunState return 8
[15:22:53 385][HUB2-3][Inf]--Run at address 0xd900c000
[15:22:53 386][HUB2-3][Inf]--RunInRam succeed
[15:22:53 553][HUB2-3][Inf]--runResult:0x 0,paraMagic:0x7856efab
[15:22:53 553][HUB2-3][Inf]--ddrCapacity:0x 800
[15:22:53 553][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 553][HUB2-3][Inf]-------------Download UBOOT.USB-----------
[15:22:53 553][HUB2-3][Inf]--Get Encrpt ulValue = 0xadfc318c
[15:22:53 553][HUB2-3][Err]--download 1 time!
[15:22:53 553][HUB2-3][Inf]--Download UBOOT.USB buffer at 0x0200c000
[15:22:53 660][HUB2-3][Inf]--Transfer complete
[15:22:53 860][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 860][HUB2-3][Inf]--DownCheckPara succeed
[15:22:53 860][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 860][HUB2-3][Inf]--RunInAddr at address 0xd900c000
[15:22:53 907][HUB2-3][Inf]--ReadCheckPara succeed
[15:22:53 907][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 907][HUB2-3][Inf]--DownRunPara succeed
[15:22:53 907][HUB2-3][Inf]--2-2-0-8-0-1-0-0
[15:22:53 907][HUB2-3][Inf]--RunInAddr at address 0xd900c000
[15:22:55 276][Global][Inf]--Catch DBT_DEVICEREMOVECOMPLETE
[15:22:55 277][Global][Inf]--Scan usb device
[15:22:55 277][Global][Inf]--Aml scan WorldCup Device
[15:22:55 280][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:55 280][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:55 280][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 281][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 282][Global][Inf]---------->[Port0]Other device
[15:22:55 282][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port2]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:55 282][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:55 283][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:55 283][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:55 283][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:55 286][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:55 286][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:55 286][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 385][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:55 385][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:55 385][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port2]Other device
[15:22:55 386][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:55 386][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:55 386][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:55 386][Global][Inf]--Scan USB host controller complete
[15:22:55 386][Global][Inf]--Update data center with HubMap
[15:22:55 386][Global][Inf]--Update hub2 device data
[15:22:55 386][Global][Inf]--Update HUB2-1
[15:22:55 386][HUB2-1][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-2
[15:22:55 386][HUB2-2][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-3
[15:22:55 386][HUB2-3][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-4
[15:22:55 386][HUB2-4][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-5
[15:22:55 386][HUB2-5][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-6
[15:22:55 386][HUB2-6][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-7
[15:22:55 386][HUB2-7][Inf]--Update device path
[15:22:55 386][Global][Inf]--Update HUB2-8
[15:22:55 386][HUB2-8][Inf]--Update device path
[15:22:55 387][Global][Inf]--Scan end
[15:22:55 391][HUB2-3][Inf]--Device is removed
[15:22:56 477][Global][Inf]--Catch DBT_DEVICEARRIVAL
[15:22:56 477][Global][Inf]--Scan usb device
[15:22:56 477][Global][Inf]--Aml scan WorldCup Device
[15:22:56 482][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E26
[15:22:56 482][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_064b1025&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:56 482][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&28e9c911&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 482][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&aaaed60&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 482][Global][Inf]---------->[Port0]Other device
[15:22:56 482][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port2]\\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:56 482][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port6]NoDeviceConnected
[15:22:56 482][Global][Inf]---------->[Port7]NoDeviceConnected
[15:22:56 482][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:56 487][Global][Inf]--Host: Controlador Anfitrião Avançado da Família Intel(R) 7 Series/C216 Chipset USB - 1E2D
[15:22:56 487][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_064b1025&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[15:22:56 487][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1f395b94&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 588][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&345359b9&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[15:22:56 588][Global][Inf]---------->[Port0]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port1]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port2]Other device
[15:22:56 588][Global][Inf]---------->[Port3]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port4]NoDeviceConnected
[15:22:56 588][Global][Inf]---------->[Port5]NoDeviceConnected
[15:22:56 588][Global][Inf]-------->[Port1]NoDeviceConnected
[15:22:56 588][Global][Inf]--Scan USB host controller complete
[15:22:56 588][Global][Inf]--Update data center with HubMap
[15:22:56 588][Global][Inf]--Update hub2 device data
[15:22:56 588][Global][Inf]--Update HUB2-1
[15:22:56 588][HUB2-1][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-2
[15:22:56 588][HUB2-2][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-3 \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[15:22:56 588][HUB2-3][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-4
[15:22:56 588][HUB2-4][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-5
[15:22:56 588][HUB2-5][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-6
[15:22:56 588][HUB2-6][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-7
[15:22:56 588][HUB2-7][Inf]--Update device path
[15:22:56 588][Global][Inf]--Update HUB2-8
[15:22:56 588][HUB2-8][Inf]--Update device path
[15:22:56 588][Global][Inf]--Scan end
[15:22:56 628][HUB2-3][Inf]--Device is connected
[15:22:56 628][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:22:56 678][HUB2-3][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223f1529&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000bc4
[15:22:59 759][HUB2-3][Inf]--0-7-0-16
[15:22:59 759][HUB2-3][Inf]--CheckFileRunState succeed
[15:22:59 759][HUB2-3][Inf]-- low_power
[15:22:59 759][HUB2-3][Inf]--Send command success
[15:22:59 759][HUB2-3][Inf]--Read command status success
[15:22:59 759][HUB2-3][Inf]-------------Download meson1.dtb-----------
[15:22:59 759][HUB2-3][Inf]--0-7-0-16
[15:22:59 759][HUB2-3][Inf]--Enc(0xadfc318c)
[15:22:59 759][HUB2-3][Inf]-- download mem dtb normal 116736
[15:22:59 759][HUB2-3][Inf]--Send download command success
[15:22:59 779][HUB2-3][Inf]--Read command status success
[15:22:59 794][HUB2-3][Inf]--Transfer complete
[15:22:59 794][HUB2-3][Inf]--Send download get_status command succeed
[15:22:59 794][HUB2-3][Inf]--get_status success
[15:23:00 305][HUB2-3][Inf]-------------ERASE FLASH-----------
[15:23:02 305][HUB2-3][Inf]--send command diskinit
[15:23:02 305][HUB2-3][Inf]--disk_initial 1
[15:23:02 306][HUB2-3][Inf]--Send command success
[15:23:04 181][HUB2-3][Err]--failed:[15:23:04 181][HUB2-3][Inf]--Read command diskinit status
[15:23:04 181][HUB2-3][Err]--Check command return failed
[15:23:04 259][HUB2-3][Err]--[0x32030201]Uboot/Get result/DiskInitial error
[15:23:04 259][HUB2-3][Inf]--Close device handle 0x00000bc4
[15:23:05 690][Global][War]--User click stop button
[15:23:05 691][Global][Inf]--Enable burning 0
Click to expand...
Click to collapse
Hi, you could try my s905x rom, I also found that once I had to downgrade from 9.0 to a 6.0 firmware to reinstall 7.1 as they wouldn't boot otherwise, and there is the route of flashing the uboot.bin as already mentioned above
@ewwink and @aidanmacgregor thanks for the help. I was actually successful in unbricking my TV Box one month ago, I was able to do it by flashing some random 6.0 m8s ROM I found online, after the 10th time giving me errors the USB tool was able to flash the rom successfully, but was still giving me errors with the 9.0 DaivietPDA Rom I was using, but then I updated from 6.0 to 9.0 using the SD Card Method and so far so good, except the LED that stopped working... Unfortunately I don't have the original uboot.bin neithe the original ROM... Might not mess with the box so much now since it seems like has some kind of NAND issue... Once again, thanks for the help.
DiogoSilva48 said:
@ewwink and @aidanmacgregor thanks for the help. I was actually successful in unbricking my TV Box one month ago, I was able to do it by flashing some random 6.0 m8s ROM I found online, after the 10th time giving me errors the USB tool was able to flash the rom successfully, but was still giving me errors with the 9.0 DaivietPDA Rom I was using, but then I updated from 6.0 to 9.0 using the SD Card Method and so far so good, except the LED that stopped working... Unfortunately I don't have the original uboot.bin neithe the original ROM... Might not mess with the box so much now since it seems like has some kind of NAND issue... Once again, thanks for the help.
Click to expand...
Click to collapse
Thays good I plan on sharing the 9.0 rom I'm using, super stable but it only works on bluetooth boxes as it need a bluetooth remote paired to pass set up screen, this can be worked around by renamining your phones bluetooth to the remotes bluetooth name, you can use a usb or bluetooth (or your tv remote with HDMI CEC if your tv supports it)
aidanmacgregor said:
Thays good I plan on sharing the 9.0 rom I'm using, super stable but it only works on bluetooth boxes as it need a bluetooth remote paired to pass set up screen, this can be worked around by renamining your phones bluetooth to the remotes bluetooth name, you can use a usb or bluetooth (or your tv remote with HDMI CEC if your tv supports it)
Click to expand...
Click to collapse
Is it the mecool km8 rom ? I tried it but i couldn't get passed that screen, tried the phone bluetooth but I think it simply didn't had my Bluetooth drivers.
DiogoSilva48 said:
Is it the mecool km8 rom ? I tried it but i couldn't get passed that screen, tried the phone bluetooth but I think it simply didn't had my Bluetooth drivers.
Click to expand...
Click to collapse
thats the exact one, had to rename phone to "RemoterATV3" and connect from phone o the box, if your phone cant find your box when searching for devices then your drivers must be missing, a few things i would like to change in the rom but because its google certified firmware im very limited on what i can change although i can change the partition that has the wifi/bt drivers in it, for example from davietpda rom
aidanmacgregor said:
thats the exact one, had to rename phone to "RemoterATV3" and connect from phone o the box, if your phone cant find your box when searching for devices then your drivers must be missing, a few things i would like to change in the rom but because its google certified firmware im very limited on what i can change although i can change the partition that has the wifi/bt drivers in it, for example from davietpda rom
Click to expand...
Click to collapse
That would be cool because that rom has very good support on my box. But do you get widevine L1 using that firmware ?
DiogoSilva48 said:
That would be cool because that rom has very good support on my box. But do you get widevine L1 using that firmware ?
Click to expand...
Click to collapse
No widevine Level 1 on any firmware, the widevine keys have to be flashed at the factory, there is no way to add level 1 widevine to an unsupported device as far as I know
aidanmacgregor said:
No widevine Level 1 on any firmware, the widevine keys have to be flashed at the factory, there is no way to add level 1 widevine to an unsupported device as far as I know
Click to expand...
Click to collapse
Thank you. So other than that what advantage does that rom have against others ? Does it have Auto Frame rate switch for example ?
DiogoSilva48 said:
Thank you. So other than that what advantage does that rom have against others ? Does it have Auto Frame rate switch for example ?
Click to expand...
Click to collapse
It has the option in settings for HDMI self -adaption (AFR) but not tested this specifically as I leave it off, Main things it does well vs others is stability, video codec performance, a decent 3.6 gb free space (vs others on 8 gb box), and I dont get "developer warning notifacation" errors when opening or returning to homescreen from my modded ad free spotify app (might be because it's a release keys firmware not a test keys firmware or could be unrelated completley) and hdmi CEC works properly (on other 9.0 roms changing volume on tv box would adjust the actual TV volume at same time as system volume where the km8 FW just adjusts android volume correctly), I believe the firmware has good performance because its google certified l, and google wouldn't certify a hot mess of a firmware it would probably have to meet some minimum standards, so even though no widevine L1 you still get the performance and stability improvments
aidanmacgregor said:
It has the option in settings for HDMI self -adaption (AFR) but not tested this specifically as I leave it off, Main things it does well vs others is stability, video codec performance, a decent 3.6 gb free space (vs others on 8 gb box), and I dont get "developer warning notifacation" errors when opening or returning to homescreen from my modded ad free spotify app (might be because it's a release keys firmware not a test keys firmware or could be unrelated completley) and hdmi CEC works properly (on other 9.0 roms changing volume on tv box would adjust the actual TV volume at same time as system volume where the km8 FW just adjusts android volume correctly), I believe the firmware has good performance because its google certified l, and google wouldn't certify a hot mess of a firmware it would probably have to meet some minimum standards, so even though no widevine L1 you still get the performance and stability improvments
Click to expand...
Click to collapse
Pretty good. I don't have that Spotify problem because I always stream from my phone which has the modded app and I never have ads there. But about the HDMI CEC I actually prefer the TV volume instead of Android volume as I leave it on max on Android every time, I've gotten used to it because of my gaming consoles, set top box, etc. If you end up making that rom with extra drivers hit me up, I would gladly test it for you.
DiogoSilva48 said:
Pretty good. I don't have that Spotify problem because I always stream from my phone which has the modded app and I never have ads there. But about the HDMI CEC I actually prefer the TV volume instead of Android volume as I leave it on max on Android every time, I've gotten used to it because of my gaming consoles, set top box, etc. If you end up making that rom with extra drivers hit me up, I would gladly test it for you.
Click to expand...
Click to collapse
Yhea modded app on phone too , it would be good tv volume but it does both system volume and tv volume at same time, get into some strange volume situations with bost adjusting esp when changing hdmi input, volume will be out of whack, the I tend to leave mine 100% too and use tv remote to control tv volume, use the tv remote for everything barely use the usb keyboard, but it would turn box volume down at same time adjusting tv volume
I am deffo wanting to make a 9.0 version but steep learning curve, new linux only tools, mostly in russian
And unfortunately cant base one off the km8 firmware as limited due to cerified fw, my thinking is edit vendor in another rom and just use that vendor partition, I should be able to extract anything essential from the official vendor partition and add it to the 3rd party version, that's the thinking anyway, whether it work out like that is another story haha
aidanmacgregor said:
Yhea modded app on phone too , it would be good tv volume but it does both system volume and tv volume at same time, get into some strange volume situations with bost adjusting esp when changing hdmi input, volume will be out of whack, the I tend to leave mine 100% too and use tv remote to control tv volume, use the tv remote for everything barely use the usb keyboard, but it would turn box volume down at same time adjusting tv volume
I am deffo wanting to make a 9.0 version but steep learning curve, new linux only tools, mostly in russian
And unfortunately cant base one off the km8 firmware as limited due to cerified fw, my thinking is edit vendor in another rom and just use that vendor partition, I should be able to extract anything essential from the official vendor partition and add it to the 3rd party version, that's the thinking anyway, whether it work out like that is another story haha
Click to expand...
Click to collapse
So you can't replace the whole vendor like GSI due to the certified firmware ? Interesting. Maybe I'll give it a shot at trying too since I'm familiar with Linux and Android as well, would be cool to learn more.
DiogoSilva48 said:
So you can't replace the whole vendor like GSI due to the certified firmware ? Interesting. Maybe I'll give it a shot at trying too since I'm familiar with Linux and Android as well, would be cool to learn more.
Click to expand...
Click to collapse
I can replace the whole vendor.partition form another 9.0 FW, only issue I saw was the more setting section in the settings stopped working, to work around this I extracted the "droidsettings.apk" from the original vendor.partition and just installed the apk like side loading any other app, I could then change settings in the more settings section, but on reboot the droid settings would be gone again, not an issue if already set settings and can just reinstall the droid settings apk again if needed, the issue with certified FW was I can unpack the firmware but it wouldn't repack correctly, being about 25mb smaller even with nothing changed, you deffo should experiment
aidanmacgregor said:
I can replace the whole vendor.partition form another 9.0 FW, only issue I saw was the more setting section in the settings stopped working, to work around this I extracted the "droidsettings.apk" from the original vendor.partition and just installed the apk like side loading any other app, I could then change settings in the more settings section, but on reboot the droid settings would be gone again, not an issue if already set settings and can just reinstall the droid settings apk again if needed, the issue with certified FW was I can unpack the firmware but it wouldn't repack correctly, being about 25mb smaller even with nothing changed, you deffo should experiment
Click to expand...
Click to collapse
Hey guys,
What do you think about flashing that davietpda or any other atv9 pie roms for s905x, mini m8s ii? I'm afraid the toothpick method for detecting in burning tool would stop working and I can't restore to any other roms if something fails. I'm currently in aidans excellently stable 7.1.2 rom.
Thanks
Related
Hi Folks!
I'm a happy owner of a Galaxy Tab 10.1, and an EE engineer who frequently uses a small USB microscope while assembling boards.
I would be really happy to be able to use my Galaxy Tab as a lightweight portable screen for this microscope. This would be much more handy than having a bulky laptop stand in there.
So I've seen that the Galaxy Tab 10.1 has USB host capabilities. And after a quick verification, I've noted that the stock kernel has the uvcvideo driver builtin (the microscope is UVC compatible, actually it's a Logitech C310 hardware with added optics).
Seems like everything is in place to make it work. However when I plug the device in, I get an unrecognized USB device message popping up.
Here's the output from dmesg:
Code:
<6>[11734.027241] Board P4 : tegra_otg_en = 1<6>[11734.037361] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[11734.037391] tegra-otg tegra-otg: tegra_start_host+
<4>[11734.038884] tegra_usb_phy_open() called instance :0
<6>[11734.038966] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[11734.039001] utmi_phy_power_on() called. instance : 0
<6>[11734.040244] tegra-otg tegra-otg: Acc power on detect
<6>[11734.057205] Board P4 : tegra_acc_power token : (1,1) on
<4>[11734.057234] utmi_phy_clk_enable() called. instance : 0
<6>[11734.058757] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[11734.059016] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[11734.067158] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[11734.087920] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[11734.107159] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[11734.107282] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[11734.107306] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[11734.107326] usb usb1: Product: Tegra EHCI Host Controller
<6>[11734.107343] usb usb1: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[11734.107359] usb usb1: SerialNumber: tegra-ehci.0
<6>[11734.111805] hub 1-0:1.0: 1 port detected
<6>[11734.113078] tegra-otg tegra-otg: tegra_start_host-
<6>[11734.113101] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[11734.327059] usb 1-1: new high speed USB device using tegra-ehci and address 2
<3>[11734.592745] usb 1-1: device v046d p081b is not supported
<6>[11734.618692] host_notify: ndev name=tegra-ehci.0: from state=0 -> to state=5
<3>[11734.620877] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11734.787068] usb 1-1: new high speed USB device using tegra-ehci and address 3
<3>[11735.040504] usb 1-1: device v046d p081b is not supported
<6>[11735.076960] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.077029] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.237112] usb 1-1: new high speed USB device using tegra-ehci and address 4
<3>[11735.505766] usb 1-1: device v046d p081b is not supported
<6>[11735.528455] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.528541] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.687712] usb 1-1: new high speed USB device using tegra-ehci and address 5
<3>[11735.950203] usb 1-1: device v046d p081b is not supported
<6>[11735.978040] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.978125] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.137097] usb 1-1: new high speed USB device using tegra-ehci and address 6
<3>[11736.393178] usb 1-1: device v046d p081b is not supported
<6>[11736.417207] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.419203] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.580821] usb 1-1: new high speed USB device using tegra-ehci and address 7
<3>[11736.840702] usb 1-1: device v046d p081b is not supported
<6>[11736.866992] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.867057] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.027074] usb 1-1: new high speed USB device using tegra-ehci and address 8
<3>[11737.279441] usb 1-1: device v046d p081b is not supported
<6>[11737.306990] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.307086] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.467126] usb 1-1: new high speed USB device using tegra-ehci and address 9
<3>[11737.736913] usb 1-1: device v046d p081b is not supported
<6>[11737.758513] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.758578] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.916947] usb 1-1: new high speed USB device using tegra-ehci and address 10
[email protected]:/ $ dmesg
Then it goes on and on with the 'new device [...] unable to enumerate' messages until I unplug it.
The device is found, and early init seems to go through (VID/PID are correct) but it doesn't seem to make it to the uvcvideo driver (or the driver is rejecting it, I don't know).
I am not very savvy as regards to linux's USB stack (though I know my way around linux, having cross compiled it, and tweaked it several times for boards I design), so I'm a bit lost as to what I could further investigate to pinpoint the issue.
I am certain that uvcvideo is present (dmesg shows 'usbcore: registered new interface driver uvcvideo' after boot).
Things works fine when I plug in a USB flash drive.
Things works fine too when I plug the microscope to my linux desktop (through uvcvideo).
Any idea or advices would be greatly appreciated!
Thanks,
Theo
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi tbeauchant,
I am also looking for same , till now i didn't get any success but after going through with the code , i have seen that samsung have disable the feature of detecting a few device , in my case it says , unkown usb device and
dmesg says :: device ######(product id) ######(vendor id) not supported ,
did you get any success or any approch which you will follow.
Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one
Analysis of USB port,Please insert phone USB cable.
Connecting...
CPU TYPE:MT6572
Hardware version:CA01
Software version:0000
Boot downloading complete!
Analysis of USB port,Please insert phone USB cable.
Connecting...
CPU TYPE:MT6572
Hardware version:CA01
Software version:0000
Boot downloading complete!
Analysis of USB port,Please insert phone USB cable.
Connecting...
CPU TYPE:MT6572
Hardware version:CA01
Software version:0000
SecCfgVal :0x00000000
BromVersion :0xFF
BLVersion :0x01
Boot downloading complete!
FlashID:002C00BC00900055
Flash Type: NAND_MT29C4G48MAZAPAKD
FlashLen:20000000
PRELOADER: addr:0x000000 --length:0x080000
PRO_INFO: addr:0x080000 --length:0x100000
NVRAM: addr:0x180000 --length:0x180000
PROTECT_F: addr:0x300000 --length:0x180000
PROTECT_S: addr:0x480000 --length:0x180000
SECCFG: addr:0x600000 --length:0x020000
UBOOT: addr:0x620000 --length:0x060000
BOOTIMG: addr:0x680000 --length:0x600000
RECOVERY: addr:0xC80000 --length:0x600000
SEC_RO: addr:0x1280000 --length:0x040000
MISC: addr:0x12C0000 --length:0x060000
LOGO: addr:0x1320000 --length:0x100000
EXPDB: addr:0x1420000 --length:0x200000
FAT: addr:0x1620000 --length:0x1E00000
ANDROID: addr:0x3420000 --length:0x14000000
CACHE: addr:0x17420000 --length:0x700000
USRDATA: addr:0x17B20000 --length:0x7AA0000
BMTPOOL: addr:0xFFFF0050 --length:0x000000
Format addr:0x17B20000 --Format length:0x70A0000
Dear all
i'm trying to enable rndis communication between a tablet running Android 4.4.2 KOT49H rooted.
in the setting menu i'm not able to find any tethering option, so i've uploaded the script usb_tether_start.sh found here:
https://forum.xda-developers.com/showthread.php?t=2127850
After the start of the service, on andorid side i see that the rndis0 device is created and is up:
13: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether a2:63:00:89:3d:46 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 scope global rndis0
inet6 fe80::a063:ff:fe89:3d46/64 scope link
valid_lft forever preferred_lft forever
Click to expand...
Click to collapse
On the laptop side (running ubunto 14.0.4 LTS) the device is created too
dmes:
[ 8643.359537] usb 3-1: new high-speed USB device number 10 using xhci_hcd
[ 8643.495555] usb 3-1: New USB device found, idVendor=10d6, idProduct=4d02
[ 8643.495564] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 8643.495568] usb 3-1: Product: P706
[ 8643.495571] usb 3-1: Manufacturer: P706
[ 8643.495575] usb 3-1: SerialNumber: A03B610405C78BB9
[ 8643.512630] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:45:00.0-1, RNDIS device, 32:ff:48:ea:0c:df
Click to expand...
Click to collapse
and ifconfig usb0 reports the device:
# ifconfig usb0
usb0 Link encap:Ethernet IndirizzoHW 32:ff:48:ea:0c:df
indirizzo inet:192.168.2.3 Bcast:192.168.2.255 Maschera:255.255.255.0
indirizzo inet6: fe80::30ff:48ff:feea:cdf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:252 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:552 (552.0 B) Byte TX:40689 (40.6 KB)
Click to expand...
Click to collapse
I also see some TX/RX bytes but the ping or any other kind of communication between the laptop and the tablet isnt' working, i've tried both static ip configuration and request via dhcp client on laptop side (the dhcp request on the laptop hangs...)
Any idea or help?
Thanks to all in advance
Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar