I have a beelink m18 androidbox, I tried to install new firmware, while choosing the file I get the message size of image larger than target device, how can i this fix.
Related
I have Android 4.0.4 device (Bluebo B3000) with MTK 6575.
I'm trying to backup my ROM.
I'm using the MTK Flash_Tool_v3.1206.01.
I do "read back" to create a backup ROM file:
- I select the "read back" tab.
- I select the scatter file
- I specify the file name
- I select the read method "read page" (I also tried the other methods. same result).
- I specify an address range to read. For example 0x0000 - 0x1000
- I press "read back" button.
- I put the battery into the device.
- I get a success message.
The backup file is created. But the file is full with zeros.
When I try to read the file for writing a ROM, the FlashTool tells me that the file is corrupted.
What I am doing wrong?
Hello!
So, I have a Android Box MXQ 4K and I'm trying to create an update.zip from the latest update (wich I only found in .IMG format).
I know the box can do a update from a update.zip file. So I extracted the files from the IMG, extracted the system.img, and created the update.zip file using instructions that I found here in the forum. But it gave me an error that wasn't a valid package (yes, I signed it). I didn't tried to aply the update.zip direct from the Recovery Menu, because if I stay too much time (30s+) on the recovery menu, it gives me a Green Screen. What are my options?
I have a Z17 Phone and i trying to install new rom, Mokee 90.0. In twrp 3.3.1-0 installation operation error: "Invalid zip file format! Error installing zip file '/sdcar.....'
I deleted all "asserts" line into "Updater-script" file but don't function.
hould I update twrp or something else?
I tried to install atvExperience Rom and I got an error in half of installation then I reboot my X96 Mini and nothing happen just the start screen of atvExperience and when I reboot into recovery mod to install a new rom with zip file I got this error:
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/s905w9.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/external_sd/s905w9.zip'
Updating partition details...
Any solution please! I tried many Firmware images in zip file and same error :/ Heeeeeeelp please!
anasBn said:
I tried to install atvExperience Rom and I got an error in half of installation then I reboot my X96 Mini and nothing happen just the start screen of atvExperience and when I reboot into recovery mod to install a new rom with zip file I got this error:
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/s905w9.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/external_sd/s905w9.zip'
Updating partition details...
Any solution please! I tried many Firmware images in zip file and same error :/ Heeeeeeelp please!
Click to expand...
Click to collapse
[Resolved] I used this Zip file rom to flash with TWRP https://mega.nz/file/A8dGWCjI#5T7YRQuOeR6f__53KbJCh3qw0N-jol_9xIiz-XhTFBY ! I wish that helps anyone else here!
I can backup my firmware using twrp. But I'm concerned that I won't be able to boot to TWRP after I mess up. So, is there a way to backup current firmware in img format for USB Burn Tool?
I also want to know. I have read that you can use tools in the Amlogic Tools folder.
I have several Android boxes where the manufacturers only supply the SD card version of the firmware update and not the AML version of the img file that can be flashed with the Amlogic USB Burning Tool should the unit brick.
I want the same thing, as the stock firmware for these boxes can be hard to find. I tried dumping /dev/block/mmcblk0 to an .img file but UBT wouldn't accept it.
leon_733 said:
I want the same thing, as the stock firmware for these boxes can be hard to find. I tried dumping /dev/block/mmcblk0 to an .img file but UBT wouldn't accept it.
Click to expand...
Click to collapse
I think MyGica's SD card type update firmwares have a code that checks the signature of the version it is replacing so if the signature does not match it will not install the firmware you're trying to update to.