Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flash repacked rom #11

Open
terblaj3 opened this issue Feb 1, 2021 · 0 comments
Open

Flash repacked rom #11

terblaj3 opened this issue Feb 1, 2021 · 0 comments

Comments

@terblaj3
Copy link

terblaj3 commented Feb 1, 2021

Good Day

I have a MXQ Pro S905x
I managed to complete all the steps to build my own rom and repack the image in Ubuntu 18.04 however have a issue flashing it. I'm using the USB Burning Tool 2.1.7.0 in Windows 10. I get the following error from the USB Burning Tool.

[10:48:03 686][HUB1-4][Inf]-------------Download system.PARTITION-----------
[10:48:03 687][HUB1-4][Inf]--0-7-0-16
[10:48:03 687][HUB1-4][Inf]--download store system sparse 1724405900
[10:48:03 687][HUB1-4][Inf]--Send download command success
[10:48:03 705][HUB1-4][Inf]--Read command status success
[10:52:11 842]Write Media read Continue:32,will sleep 3s
[10:52:27 932]Write Media read Continue:32,will sleep 3s
[10:52:43 988]Write Media read Continue:32,will sleep 3s
[10:53:00 073]Write Media read Continue:32,will sleep 3s
[10:53:03 074]UsbRomDll Return buffer=Continue:32
[10:53:06 459][HUB1-4][Inf]--Transfer complete
[10:53:06 460][HUB1-4][Inf]--Send download get_status command succeed
[10:55:36 460][HUB1-4][Err]--usb_reap_async_nocancel Try 2 time! usbReadFile len=512, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] reaping request failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.

[10:55:36 465][HUB1-4][Err]--[0x30404002]UBOOT/Partition system/Get download status/USB Control setup error
[10:55:36 465][HUB1-4][Inf]--Close device handle 0x000005a0

I suspect that I have to edit a pointer that indicates the new system.img partition size inside the bootloader or something within the package file that indicates the size of the new partitions.

How do I correct the new size within the bootloader step by step or if I missed something what could it be?

Johann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant