yashsingh1/xdaforums huggingface dataset:
[Android TV General] Daniel Smedegaard Buus:
I'm sorry if I'm noobing up the place, but I simply cannot figure out how to get this X88 Pro X3 box of mine flashed. I find different versions of ROMs out there, but so far attempting to flash by SD card has yielded no positive results. I'm guessing because it's encrypted, but I don't know. I don't understand where you're getting those logs from, and how you use them to detect if your device is encrypted. I also don't understand how you're connecting these boxes via OTG, since — at least on mine — there are only TYPE-A USB ports, and I've never seen a TYPE-A-to-TYPE-A OTG cable? I have an external drive with a TYPE-A-to-TYPE-A USB 3.0 cable, but using that cable doesn't work (as in Windows detects absolutely nothing upon insertion, and there's no reaction I can see from the box itself.

Perhaps my Googling skills are as limited as my understanding skills, but I also cannot find anything about such cables. If that's really the kind of cable I need, can I solder one of my own? Any links to guides?

Thanks :)
[Android TV General] Raxone:
Hello.

I use cable A to A usb 2.0 used for external usb/hdd .

Must use black usb(2.0) on x88pro what is OTG.

Problem is probably usb 3.0 what you use wire is connect diffrent.

Usb A-A 2.0 is connect wire to wire +5v to +5v,GND to GND D+ to D+ and D- to D-.

If you got old usb 2.0 cable you can just cat cable and connect wire to wire no need solder.

Almost all usb 2.0 cable use Red for +5v,Black GND,D+,D-(green,white) only thing what you must be careful about +5v and GND wire.

If not work tray exchange D+/D- wire connection.

+5v ------ +5V (Red)

GND -----GND(Black)

D+ ------ D+ (green or white)

D- -------D- (green or white).

Post above is script for dump all partition from x88prox3 .

I recommand to you to dump all parition of your x88pro.

If you dump successfully partition you can send me bootloader.img and i can tell you what version of x88pro you got,encrypted or not.
[Android TV General] Daniel Smedegaard Buus:
Thank you, Raxone, for replying :)

So, if I understand you correctly, if I simply take two identical USB 2.0 cables, cut the TYPE-B connectors off, and then connect every wire inside to the same color (e.g. red to red, black to black, white to white, and green to green), then I can use that cable as OTG cable?

I'm pretty sure I have a bunch of USB 2.0 cables lying around in the basement, I'll go have a look :)
[Android TV General] Daniel Smedegaard Buus:
He he :D Brilliant.

I found a couple (about 20) spare USB 2.0 cables, made a TYPE-A-to-TYPE-A one from two identical ones, red-to-red, black-to-black, white-to-white, and green-to-green.

The cable works as a connector for the HDD I mentioned before, so it seems it basically does the same as my USB 3.0 cable, only with four connectors instead of eight. And, more importantly, at least the connectors and plugs are working, that is if this is the correct cable connections for an OTG cable?

However, this didn't do anything for the Android box. When I connect it, absolutely nothing happens. No Windows ding, and nothing in AML Burn Tool. I've tried V2.1.7.3, V2.2.0, and V2.2.3.3, all installed with the drivers, but no donut. I tried both the USB 3 and USB 2 port on the box. I noticed that with the USB 2 cable, the device doesn't boot when plugged in via the USB 3 port, which it did with the USB 3 cable I tried to use to begin with. I assume because the computer notices that it's USB 2.0, so it stays within those specs and don't deliver enough juice for the box to boot.

I then noticed the mentioning of a hub in the AML Burn Tool instructions on the right of its screen, and I just tried using a powered USB 2.0 hub, but with the same lack of results, except that the box now boots when plugged into the hub (via either the USB 2.0 or 3.0 port on the box).

Am I missing something here? I feel like there's something I should do, just don't know what...

EDIT: I just noticed it actually does get enough juice to boot without the hub attached, still not appearing though. Also, I tried holding down the reset switch in the A/V hole while plugging it in, also without success.
[Android TV General] jaketri:
I dumped again everything today and I got exactly same binaries!

Box is using stock rom as I was not able to burn vtx or sbx ....

This started with my attempt to burn vtx image and fail with following errors:

[16:49:24 125][HUB1-3][Inf]-------------Download DDR.USB-----------

[16:49:24 125][HUB1-3][Inf]--3-2-0-0

[16:49:24 125][HUB1-3][Inf]--Control write pll reg1 0xfffa0000:0x000000b1

[16:49:24 640][HUB1-3][Inf]--Control write pll reg1 0xfffa0000:0x00005183

[16:49:25 145][HUB1-3][Inf]--Control write pll reg1 0xfffa0000:0x000000b1

[16:49:25 665][HUB1-3][Inf]--Control write pll reg1 0xfffa0000:0x00005183

[16:49:26 172][HUB1-3][Inf]--Write initial succeed

[16:49:26 172][HUB1-3][Inf]--Upload encrypt at 0xff800228

[16:49:26 172][HUB1-3][Inf]--ulValue = 0x20444142

[16:49:26 172][HUB1-3][Inf]--Read encrypt value succeed

[16:49:26 172][HUB1-3][Inf]--Download DDR.USB,size: 65536!

[16:49:26 172][HUB1-3][Err]--Download file failed, sequence 0

[16:49:26 172][HUB1-3][Err]--usbWriteFile len=4096, ret=-5 error_msg=libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.

[16:49:26 176][HUB1-3][Inf]--Failure : 1, FailureMax : 3

[16:49:36 702][HUB1-3][Err]--Download file failed, sequence 0

[16:49:36 702][HUB1-3][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error

[16:49:36 702][HUB1-3][Inf]--Failure : 2, FailureMax : 3

[16:49:47 210][HUB1-3][Err]--Download file failed, sequence 0

[16:49:47 210][HUB1-3][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error

[16:49:47 210][HUB1-3][Inf]--Failure : 3, FailureMax : 3

[16:49:47 222][HUB1-3][Err]--[0x10103003]Romcode/Initialize DDR/Download buffer/USB transfer error

[16:49:47 222][HUB1-3][Inf]--Close device handle 0x000004d8

This log above was from USB burning tool 2.1.8

Today I also tried to use different USB burning tool 2.2.3.3 were I get totaly different error:

[17:06:18 937][HUB1-3][Inf]-------------Download DDR.USB-----------

[17:06:18 937][HUB1-3][Inf]--3-2-0-0-1-0-0-15

[17:06:18 939][HUB1-3][Err]--[0x10102004]Romcode/Need PWD

[17:06:18 940][HUB1-3][Inf]--Close device handle 0x000004c8

I do not have the password.bin file so I guess no success for me with this box and have to stay with stock :(

Overall the X88 box behave strange with any USB burning tool version as it is detected after about 5 seconds of plugging the USB cable the the USB 2.0 port and only if I hold the reset switch pressed for the 5 seconds until box is detected.

BTW .... Both version of USB burning tool (2.1.8 and 2.2.3.3) are burning fine older box (A95X) from same system and using same usb cable (from an old USB external HDD). The old A95X box is detected immediately after I plug the USB cable not after ~5 seconds like the X88 box.
[Android TV General] Raxone:
Here is differences of your bootloader and any bootloader what i have and i see.

That bootloader is from firmware image 04.25.20 and after that is firmware 06.27.20.

Do you ever try to update your x88pro from android ota update becouse if i install 04.25.20 version on x88pro android try to update to version 06.27.20.

And differences from your bootloder is strange in first section just copy 0x202 and in bootloader.img and boot.img just added 0x0D to all file.

Everything is same just added 0x0D what's like transaction error when you dump bootloader.

I can make usb burn firmware with your bootloader.img,boot.img.
[Android TV General] jaketri:
I got the box initially with 4.25 image then ota update to 6.27 some time ago.

It look like there are two separate corruptions in my dumps :(

First for unknown reasons the booloader files I send to you initially got corrupted while I copy it from the system I used for dumping to the system were I created the zip file and send to you. It look like the bootloader file was mixed somehow with an old copy from an old dump before I used 6.27 ota update.

Second, it look like 0x0d are added by adb while redirecting the output for dumping the images to file on PC.

To workaround the 0x0D I created separate simple script (attached) that will dump only boot, bootloader and dtb using existing method (dump with dd then redirect adb shell output to local file) and also by first dumping each partition to a file on the box using dd then pull the file from the box to the PC via adb pull.

Sorry for my mess with the initially bootloader dump and for missing it on my second attempt to check it when I just check the old dumped file locally without checking the content from the zip file that I send to you.

Edit: Attached UART u-boot logs from USB burn mode (power on with reset pressed by toothpick).
[Android TV General] Raxone:
Do you OverClock you CPU or Ram?

Error whan you dump x88pro bootloader etc. looks like:

Damaged usb on x88pro,usb cable ,usb on pc ,OC CPU problem,Ram OC problem or damaged ram.

I think problem is in USB Burnning Tool beacuse 0x20444142 not now like encrypted box.

And i must you ask what firmware you try to flash?

Do you try my version or?
[Android TV General] Daniel Smedegaard Buus:
Hmmm... I managed to get the device detected by finding a YouTube video that actually explained how to connect it properly, using the reset switch while connecting it.

I get an error similar to jaketri, though... I think... Attached. Is there any way forward with this box? I did try an OTA update earlier today, and it said I had the latest version already. Is my stupid box encrypted?

Thanks :)
[Android TV General] Daniel Smedegaard Buus:
Oh, hello. I had gone back to version 2.1.7.3 of the burning tool while trying to connect the box with the reset pin depressed, and not having any success. I now tried the latest version again that I have, v2.2.3.3, and this time it's a different error: "Romcode/Need PWD," so at least to me that reads like, "Hey, I'm encrypted, please unlock me." Right?

So as to your OP question: No, I have never flashed anything on this before.

I don't know how to dump anything from this. You mention needing a dumped bootloader? How would I do that?

Cheers :)
[Android TV General] Daniel Smedegaard Buus:
Okay, so I managed to get the bootloader off — I think... I installed the TWRP tool from the Play Store, and it could dump boot and recovery images from the device. I put them here:

X88 Pro X3 bootloader and recovery from TWRP - Google Drive

drive.google.com

Only took me like two hours to figure out how to get these files off the internal storage. Ended up with MiXplorer and a Samba share on another computer. My god, Android Pie and/or this particular firmware is bad XD

Was this the kind of boot image you mentioned in the OP?

Thanks mate :)
[Android TV General] jaketri:
No overclock at all.... however, I suspect box have fake 4 GB ram and in realty only have 2GB RAM but kernel was modified by vendor to report 4GB....

I installed https://play.google.com/store/apps/details?id=com.rektgames.memoryfill and not able to fill more than 50% of memory :( ... same test on other boxes allow to fill more than 90% of memory!

I was trying to flash your firmware x88_pro_x3_enc_R@xOne_stock_27_06_20.zip as initial test but aiming to use x88_pro_x3_enc_R@xOne_atv_vtx_v2.3.0.zip.
[Android TV General] Daniel Smedegaard Buus:
Okay, so while trying a bunch of different things, I managed to get Vortex installed using the files and instructions here (don't know what to do with the TWRP zip, if anything, so I've only flashed the firmware using the instructions given there): https://4pda.to/forum/index.php?showtopic=982302&st=300#entry96036753 (use Google Translate)
[Android TV General] Raxone:
Your box CPUID SM1:BL:511f6b:81ca2f;FEAT:B2F939B2:202B2060

my x88prox3 CPUID SM1:BL:511f6b:81ca2f;FEAT:B2F831B0:202B2060.

You can try my version of firmware but fisrt you need to dump your box firmware and than try flash firmware.

Download Rom_DumP from above post and dump bootloader.img,boot.img,dt.img.

Best way is to dump all nand exept data and cache.

What you box brend?

It is DreamBox.

If you dump bootloader.img you can send me to compare bootloader maybe custumize firmware for you box.
[Android TV General] vladakru:
Box is Beacon bi60r

thanks for the reply, I'll try to, so we'll talk ...
[Android TV General] vladakru:
Raxone frend, here is files... look what u can doe.. Thx.​
[Android TV General] Raxone:
Hello vladakru.

Try this firmware.

I made it from you dump but here is only bootloader,boot and dtb.img.

Bootloader and boot.img is encrypted but dtb.img not encrypted.

If firmware work we can try made it with all system or another system.

If work i need log of boot kernel/linux you stoped log or not send me.

I need this:

Starting kernel ...

uboot time: 4833082 us

[ 0.000000@0] Booting Linux on physical CPU 0x0

[ 0.000000@0] Linux version 4.9.113

version of linux "Linux version 4.9.113" if you box have this version of linux i can try make all system firmware.

Also i need dump partition from you box:

odm

product

recovery

dtbo -not dtb

vendor

and

vbmeta.

P.S.

I start working and i not free time.
[Android TV General] Raxone:
Can you send me usb burning tool log but without box or board from box is hard to fix problem with this board
[Android TV General] Raxone:
Sorry my mistake try again please and send me log from usb burning tool work or not work.

Firmware
[Android TV General] Raxone:
To make usb burning tool firmware need file name "platform.conf" in this file is;

Platform:0x0811

DDRLoad:0xfffa0000

DDRRun:0xfffa0000

DDRSize:0x10000

Control0=0xfffa0000:0x000000b1

Control1=0xfffa0000:0x00005183

Encrypt_reg:0xff800228.

Encrypt_reg:0xff800228 is address where is my box read B2F831B0 what is something about encrypt firmware

"SM1:BL:511f6b:81ca2f;FEAT:B2F831B0:202B2060"

[18:16:07 672][HUB2-10][Inf]--Upload encrypt at 0xff800228

[18:16:07 673][HUB2-10][Inf]--ulValue = 0xb2f831b0

in another case UBT software read wrong register

[10:31:52 502][HUB4-8][Inf]--Upload encrypt at 0xff800228

[10:31:52 502][HUB4-8][Inf]--ulValue = 0x20444142.

What we need is find "Encrypt_reg" address what is not 0xff800228.

For example board "Beacon bi60r"

SM1:BL:511f6b:81ca2f;FEAT:B2F939B2:202B2060;

and from UBT log need to be

ulValue = 0xB2F939B2

not

ulValue = 0x20444142
[Android TV General] vladakru:
where i can find "platform.conf" ? can I somehow get them out of the box?
[Android TV General] Raxone:
You can just create file name "platform.conf" must be .conf extension.

But that file is only for USB_Burning_tool firmware image .

If you got maybe stock firmware of you box you can extract file from firmware.

I think that file not exist in nand/flash on box.

If you use linux maybe i can help you to find some information of you box.
[Android TV General] vladakru:
I try this https://4pda.to/forum/index.php?showtopic=982302&st=300#entry96036753

This is some Vortex firmware, but now is bricked in bootloop 🥺

I try this https://4pda.to/forum/index.php?showtopic=982302&st=300#entry96036753

This is some Vortex firmware, but now is bricked in bootloop 🥺

the worst part is that I can no longer get into the fastboot to try another firmware version
[Android TV General] Raxone:
With that firmware and fastboot it's very easy to brick box.

Becouse whan flash no any control is firmware ok just blind flash image.

Can you send me uart log of bootloop.
[Android TV General] vladakru:
here is log... Rebooting in 5 seconds..
[Android TV General] Raxone:
Booloader,boot and dtb.img is from stock/manufacturer firmware?

System partition is not burn correct on flash try burn again.

Maybe original boot.img(kernel) not mount system partition without some encryption security.

You need to stop u-boot with any key on keyboard (enter) and type "fastboot" in u-boot

example g12a_u212_v1#fastboot and you can use fastboot to flash firmware.

This is vortex firmware aosp v2.3.0 version but with beacon bi60r bootloader,boot,and dtb.img.

Download
[Android TV General] vladakru:
I try when came home, thanky very much fror answer.
[Android TV General] vladakru:
i connected the usb keyboard to the box but the box does not respond to the keyboard. I follow this via the uart connection
[Android TV General] vladakru:
i managed to run fastboot. a computer keyboard is used. I flashed again but again without success ... bootloop
[Android TV General] Raxone:
Problem is in dtb.img.Size of system partition is to small.You got failed info.

Max size of system.img is 800Mb
[Android TV General] vladakru:
I did it! :)

I unpacked a few different firmware, and I succeeded with Aidan's Rom [S905X3] (TX3).

I want to thank you once again. Thanks a lot friend!
[Android TV General] Raxone:
Dump bootrom,aeskey s905x2

GitHub - Raxone/amlogic-usbdl_s905x2: s905x2 Dump Bootrom BL1

s905x2 Dump Bootrom BL1. Contribute to Raxone/amlogic-usbdl_s905x2 development by creating an account on GitHub.

github.com

Dump bootrom aeskey s905x3

GitHub - Raxone/amlogic-usbdl_s905x3: Dump s905x3

Dump s905x3 . Contribute to Raxone/amlogic-usbdl_s905x3 development by creating an account on GitHub.

github.com
[Android TV General] kalehrl:
Hi. I've got an X99 Max plus which is the same as X88 Pro X3. However, I'm unable to install slimbox and I get the following error. Please see the amlogic log. Thank you.
[Android TV General] Raxone:
You got encrypted version box.
[Android TV General] kalehrl:
Would any of your ROMs work?
[Android TV General] Raxone:
Try this. This is vortex firmware.

Problem is here:

[13:30:09 032][HUB3-4][Inf]--3-2-0-0

[13:30:09 032][HUB3-4][Inf]--Control write pll reg1 0xfffa0000:0x000000b1

[13:30:09 535][HUB3-4][Inf]--Control write pll reg1 0xfffa0000:0x00005183

[13:30:10 055][HUB3-4][Inf]--Control write pll reg1 0xfffa0000:0x000000b1

[13:30:10 576][HUB3-4][Inf]--Control write pll reg1 0xfffa0000:0x00005183

[13:30:11 091][HUB3-4][Inf]--Write initial succeed

[13:30:11 091][HUB3-4][Inf]--Upload encrypt at 0xff800228

[13:30:11 091][HUB3-4][Inf]--ulValue = 0xb2f831b0

[13:30:11 091][HUB3-4][Inf]--File change to DDR_ENC.USB

[13:30:11 091][HUB3-4][Inf]--Read encrypt value succeed

[13:30:11 091][HUB3-4][Inf]--Download DDR_ENC.USB,size: 0!

[13:30:11 091][Global][Err]--DDR_ENC.USB

[13:30:11 091][Global][Err]--DDR_ENC.USB

[13:30:11 091][HUB3-4][Err]--Read item data error, code -1

If use firmware for non encrypted s905x3.
[Android TV General] kalehrl:
If something goes wrong, can I recover it by installing factory image?
[Android TV General] :
Were you able to dump the bootrom keys with this script? If so, describe your process with maximum specificity.

If you have a log of a successful execution of this script, please post it.

Edit: I've resolved the issue, no response needed.
[Android TV General] Raxone:
Like original owner of this git repo frederic i just modded this repo to work with s905x2.

If you just ask me how to dump key i help you.
[Android TV General] :
Thanks, but as I mentioned in my post a couple of months ago, I resolved this issue.

My issue was that many certified devices using the s905x2 have password enabled for usb download mode. Even old certified devices. When password is enabled, the usbdl method can't work.

Once I used the script on a non-certified generic s905x2 box, it worked fine.

But I haven't found any certified s905x2 box that didn't have usb download mode protected by password.
[Android TV General] Raxone:
Dump bootrom(BL1),Bootloader,DTB,AESkey,Decrypt Bootloader for s905x2.

git clone https://github.com/Raxone/amlogic-usbdl_s905x2.git

GitHub - Raxone/amlogic-usbdl_s905x2: s905x2 Dump Bootrom BL1

s905x2 Dump Bootrom BL1. Contribute to Raxone/amlogic-usbdl_s905x2 development by creating an account on GitHub.

github.com

Dump bootrom(BL1),Bootloader,DTB,AESkey,Decrypt Bootloader for s905x3

git clone https://github.com/Raxone/amlogic-usbdl_s905x3.git

GitHub - Raxone/amlogic-usbdl_s905x3: Dump s905x3

Dump s905x3 . Contribute to Raxone/amlogic-usbdl_s905x3 development by creating an account on GitHub.

github.com

Youtube
[Android TV General] reza0511:
hi Raxone , I have a gtmedia gtcombo hybrid tv box without A/V port and rest switch.

when I try to install temporary TWRP35_by_VIT , either from local update or in recovery mode , it gives error 21 ,is the bootloader Locked ? can you unlock it if I upload it here ?
[Android TV General] reza0511:
part of log
[Android TV General] reza0511:
last page of log
[Android TV General] iAbdul:
Hi,

I was trying to use your tool on Skyworth HP40A S905X2, but encountered in error which says:

device is protected by password

Is there any solutions?
[Android TV General] Raxone:
Hi,

Board is usb password protected if you have password for usb burnning tool maybe you can something but i think if board usb password protect is not possible to dump sram/bl1 with usb.
[Android TV General] nimatest2022:
Hi everyone I have a x88 pro x3 that yesterday flash it with different img files that find in different sites

and test different modes(erase flash and overwrite key ,...)

now it didnt, boot but when connect it to computer detect and i can flash it again with pc

(i didn,t back up it )

is there any way to i recover it or any way to work with it

please Help me

thanks.
[Android TV General] alexnov71:
Hello. I have an encrypted device X88 Pro X3 4/64. I flashed an alternative firmware. I have not saved the source code. I've tried all the options. it doesn't go beyond the first screensaver, ALM sees the device. I'm asking for help.

I forgot to add I can't get into the recovery
[Android TV General] deponija:
Hi @Raxone.

Could you please confirm what exactly this means? Which app did you take from Vortex image and added to Slimbox?

I'm struggling with fixing front-panel clock in Slimbox on another device, and this information would greatly help.

Thanks a lot in advance!
[Touch Diamond, MDA Compact IV General] MasterSL:
hey guys

im searching the unmodified manila.cab from 1.93 german htc rom.

could anybody upload it for me please?
[Touch Diamond, MDA Compact IV General] Unchained:
Lad Dir doch die Kitchen runter und dumpe eben fix das HTC ROM. Dann noch mal fix nen Cab draus bauen und gut.. Hab hier leider auch kein original mehr..
[OnePlus 8T Guides, News, & Discussion] sharkie405:
Credit: @stelio_kontos - https://xdaforums.com/t/guide-add-more-columns-to-the-oneplus-launcher.3659772/

They were saying in that thread that it was no longer working for them, but it does still work, at least on 8T. Not sure how long it will continue to work though. They were also talking about changing the number of columns, but I'm only concerned with changing the number of rows. There is a column entry in the path listed below, I just haven't tried it myself because five columns is what I want.

Root required.

Go to: /data/data/net.oneplus.launcher/shared_prefs/net.oneplus.launcher.prefs.xml

Adjust this value to your liking: <int name="workspace_rows" value="9" />

Find OnePlus Launcher app in Settings and force close. Wait a second or two, then go home. Viola!

So far it's stuck through reboots and updating the launcher from Playstore.
[OnePlus 8T Guides, News, & Discussion] sharkie405:
If you have trouble finding the data/data/net.oneplus.launcher folder due to Android 11 nonsense, you can copy the file or folder to your sdcard via terminal, edit it, then push it back. Below are the commands for that process.

C:\xxx\00_OnePlus8T>adb shell
OnePlus8T:/ $ su
OnePlus8T:/ # getenforce
Enforcing
OnePlus8T:/ # setenforce 0
OnePlus8T:/ # getenforce
Permissive
OnePlus8T:/ # cp -r /data/data/net.oneplus.launcher/shared_prefs /sdcard
OnePlus8T:/ # cp -r /sdcard/shared_prefs/net.oneplus.launcher.prefs.xml /data/data/net.oneplus.launcher/shared_prefs
OnePlus8T:/ # setenforce 1
OnePlus8T:/ # getenforce
Enforcing
OnePlus8T:/ # exit
OnePlus8T:/ $