Database Users

Android 4.3 Update

Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
macyccam-jwr66v trant_macbook$ ./flash-all.sh
sending 'bootloader' (2201 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.142s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (54321 KB)...
OKAY [ 3.397s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 3.399s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ10o
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number........: 027af952120bb5bf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ10o'.
Update requires 'MAKOZ20i'.
finished. total time: 0.012s
Click to expand...
Click to collapse
Is something wrong with my bootloader ?

xDer_ said:
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
Is something wrong with my bootloader ?
Click to expand...
Click to collapse
Your bootloader seems like it's locked. You need to unlock it first with fastboot by running "fastboot oem unlock". Note that this will wipe all data on your device, which you probably don't mind since you just got the device.

Nexus 7 boot.img flash fails with FileWriteFailed

Device: Nexus 7 (2012) WIFI only
After 4.3 update device started locking up and had to repeatedly long-press power to reboot. Factory defaut fixed first time, Second time (because it started happening again) could not recover from factory default. boot.img will not install and returns a (remote: FileWriteFailed) error.
I've tried multiple cables, PCs, and toolkits with no luck.
I can load bootloaders without issue.
I can format and load system, userdata, recovery (have loaded stock, TWRP, CWM recoveries) all appear to load without issue and work fine but haven't been able to fix this issue.
Once the boot.img flash is attempted, the device locks up hard and a long-press of power is needed to bring it back.
I can boot to Google screen with (Start, Power off, Recovery mode, Restart bootloader options) or directly to bootloader without issue.
First tried restoring 4.3 factory, but have since been trying 4.2.2 factory using Nexus Root Toolkit, Nexus 7 Toolkit, and a lot of SDK command line of fastboot commands. I can run ADB commands if I first get into recovery.
Is there a option I can tickle or something else anyone knows I can try? I'm beginning to think the boot sector of the flash is defective (if this makes sense).
Here's an example of a fastboot update. It hasn't mattered the method, the outcome is always identical. It fails at boot.img flash write failure.
>fastboot devices
015d490651281e0e fastboot
>fastboot erase boot
erasing 'boot'...
OKAY [ 1.186s]
finished. total time: 1.186s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.998s]
finished. total time: 0.998s
>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.796s]
finished. total time: 0.796s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.649s]
finished. total time: 4.649s
>fastboot flash bootloader bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.312s]
writing 'bootloader'...
OKAY [ 9.875s]
finished. total time: 10.202s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot -w update image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d490651281e0e
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.686s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 5.210s
>

This issue has been resolved. The Nexus 7 was returned to Asus support and the motherboard was replaced under warranty.

[Q] Failed KitKat 4.4 Fastboot

Hi All,
I'm using Mac Terminal, have latest SDK, adb and fastboot installed. I have Nexus 7 (2012) Wifi - Nakasi
I followed the pinned post to upgrade my 4.3 (JWR66Y) to KitKat 4.4. I rebooted into fastboot and started ./flash-all.sh
Mid way through the process had stalled so I 'control C' out of the process.
$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.993s]
finished. total time: 0.994s
erasing 'cache'...
OKAY [ 1.059s]
finished. total time: 1.059s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.855s
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'userdata'...
OKAY [ 6.154s]
finished. total time: 6.154s
sending 'bootloader' (2100 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
OKAY [ 9.666s]
finished. total time: 9.969s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d4226501005
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.024s]
sending 'boot' (4990 KB)...
OKAY [ 1.045s]
writing 'boot'...
OKAY [ 1.047s]
sending 'recovery' (5530 KB)...
OKAY [ 3.340s]
writing 'recovery'...
OKAY [ 1.381s]
sending 'system' (611878 KB)...
^C
Click to expand...
Click to collapse
I ran same process and it was hanging again at the same spot. I exited the same way. Now terminal cannot find device in adb devices. I can still boot into recovery mode.
$ ./adb devices
List of devices attached
Click to expand...
Click to collapse
$ ./flash-all.sh
< waiting for device >
Click to expand...
Click to collapse
I'm not sure what to do now!!! any help would be...helpful. Please.

You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4

Just wanted to update you on a solution if anyone has a similar problem.
I erased the system image through fastboot.
./fastboot erase system
Click to expand...
Click to collapse
Flashed the system image for old stock 4.3
./fastboot flash system system.img
Click to expand...
Click to collapse
Ran the flash-all script
./flash-all.sh
Click to expand...
Click to collapse
System was updated and worked! I back-dated to android 4.3, then did a second flash-all script to update to the current version of android 4.4. I believe that the original factory image for 4.4 was not working. The factory image was updated a day later - this is the file i used.
Thanks to everyone in xda. The many posts I read - even not directly related to my problem - provided a solution.
I hope my next post isn't so noob

whitext said:
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Click to expand...
Click to collapse
Well,I got the similar problem the other day on my Nakasig when I was flashing factory images through Fastboot.
Not only did I try the "flash-all.bat" command, but I also manually inputted each command line one after another.
However, I still encountered the same issue and waited for more 30 minutes during the "sending system" process.
Even worse was that I unplugged my N7 and tried to boot it,which led me to be stuck with the Google logo.:crying:
After removing the battery and booting it into Fastboot again,this time I decided to use Wug's toolkit to flash it.:good:
And thankfully,it worked and I can grab the delicious Kitkat now.
BTW, my N7 still failed to pass Hashcheck while using Wug's automatic method, therefore I just downloaded the Factory images and used Wug's tool to navigate to the .tgz file and then flash it.It spent me around 2 minutes to complete the "sending system" process this time.

Bootloop and can't fastboot flash image

I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.

carlowahlstedt said:
I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
Click to expand...
Click to collapse
Possibly... or possibly not.
Hi, carlowahlstedt...
carlowahlstedt said:
...Only this time, I can't get a factory image to flash...
Click to expand...
Click to collapse
It might be helpful if you could be more specific... like, what errors did you encounter?... how did you go about flashing a factory image?... did you use a toolkit, like Wugs?... or just regular fastboot?
For somebody to assist you in diagnosing a given problem, in the hope of fixing it... they need all the facts available... no matter how seemingly innocuous or irrelevant.
The 'devil', as it is said, resides very much in the 'detail'.
Rgrds,
Ged.

Thanks Ged. I guess I was kinda hoping for a tool that could some how test the memory.
Here's the output from the toolkit:
********************************************************************************
* Universal Nexus Linux Toolkit v2.4.2 by tatelucas *
********************************************************************************
Flash Google Factory Image
Before starting the process your device must be in Bootloader Mode.
In the following instructions you will learn how to do it:
1. Power off the device.
2. Press and hold Volume Down, then press and hold Power.
3. Your device screen should show an image of an opened android.
You're now in the Bootloader Mode! If you don't see the image,
you must follow the instructions again.
4. Please connect the device to your PC via USB.
5. Do you want to start the process? [Y/N]: Y
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.019s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.247s
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting into bootloader...​
You'll notice that it doesn't have anything past the "rebooting into bootloader". The screen is locked up on the device and nothing is happening. After sometime I manually reboot into bootloader and get:
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 174.893s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 0## (removed this)
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4990 KB)...
OKAY [ 0.682s]
writing 'boot'...
FAILED (remote: (AccessDenied))
finished. total time: 2.378s​
I also seems to have lost recovery mode? If I click on Recovery Mode in the bootloader it just flashes the text and that's it.
Not sure what else would be helpful to see/know. Thanks for the help.

Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. I downloaded the latest image for the Nexus 7 Wifi (NOT 2013) and attempted to flash the bootloader but I get this:
sending 'bootloader' (2100 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.466s​
I found this thread, which I took to mean to download the bootloader from the 4.3 image. I did that but get the same result.
Also, it shows that I already have 4.23 so it seems like I wouldn't need to flash this in the first place?
Thanks again for the help.

Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, no toolkits.
Looks like the erase system command is having issues writing as well. Included the reference to the command so you could see that as well:
platform-tools carlo.wahlstedt$ ./fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 81.408s​

Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think it's looking good:
platform-tools carlo.wahlstedt$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot flash system nakasi-kot49h/image-nakasi-kot49h/system.img
erasing 'system'...
OKAY [ 0.011s]
sending 'system' (625382 KB)...
OKAY [ 86.819s]
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 152.721s
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
^C (I forced a reboot here after waiting a long time)
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
sending 'boot' (4992 KB)...
OKAY [ 0.818s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.374s
platform-tools carlo.wahlstedt$ ./fastboot flash data nakasi-kot49h/image-nakasi-kot49h/userdata.img
sending 'data' (104289 KB)...
OKAY [ 14.212s]
writing 'data'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 14.227s
platform-tools carlo.wahlstedt$ ./fastboot flash recovery nakasi-kot49h/image-nakasi-kot49h/recovery.img
sending 'recovery' (5532 KB)...
OKAY [ 0.893s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.448s
platform-tools carlo.wahlstedt$ ./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting... (I forced a reboot here)
ERROR: usb_write failed with status e00002ed
finished. total time: 106.130s​
It's also "locking up" on most every command that I send. By that I mean, you can't move through the bootloader menu.
Any other thoughts?

Sorry to say but I feel your nand is fried... If you still have warranty you should claim it but as of now I would give it 50/50 that even JTAG would work to resurrect you tab
Sorry for the bad news, best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app

Well that sucks. Thanks for the help.

adt-3: fastboot get_unlock_ability 0

Hi All,
I am trying to flash Android TV 13 beta 4 ~ to the developer tools adt-3. After flash ... the adt-3 keep reboot. And cna't load the bootloader and OS. when I try to flash the device again ... adt-3 said that FAILED (remote: 'locked device').
I would like to know how to unlock adt-3 !?
ToTo

./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.049s]
Finished. Total time: 0.050s
sudo ./flash-all.sh
[sudo] password for toto:
error: no devices/emulators found
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'data' FAILED (remote: 'locked device')
fastboot: error: Command failed
Sending 'bootloader' (1591 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
--------------------------------------------
Bootloader Version...: 01.01.220621.133524
Baseband Version.....: N/A
Serial Number........: ACHE0000xxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.015s]
Checking 'version-bootloader' OKAY [ 0.014s]
extracting boot.img (16 MB) to disk... took 0.031s
archive does not contain 'boot.sig'
Sending 'boot' (16384 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
OKAY [ 0.023s]
Finished. Total time: 0.023s
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.305s
Need help to unlock adt-3

fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock

Many thanks, I using adt-3. I think oem not working ... many thanks. Here is the result.
./fastboot oem 'setenv lock 10101000;save'
FAILED (remote: 'locked device')
fastboot: error: Command failed
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed

That is the command that is within flash-all.sh for build adt3_gtv-stt1.211025.001.z3-factory-91f7efe7.
It was designed specifically to fix this particular issue/bug with the adt-3.
This problem started before android 12. Read article;
[Update: Fixed] Android TV 12 preview builds for ADT-3 can't be flashed
The first builds of Android TV 12 for Google's own ADT-3 developer device are completely broken, leaving developers unable to install them.
9to5google.com

Yes, I know ... I also go through that issue when I did Android TV 12. Right now I have the issue again. When I was doing Android TV 13 beta 4. Here flash-all.sh come with Android TV 13 beta 4.
if ! [ $($(which ./fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
./adb reboot bootloader || true
if ! ./fastboot flashing unlock ; then
./fastboot oem 'setenv lock 10101000;save' || true
./fastboot reboot bootloader; sleep 3
./fastboot flashing unlock || true
fi
./fastboot erase data
./fastboot flash bootloader bootloader-adt3_gtv-01.01.220621.133524.img
./fastboot reboot bootloader; sleep 3
./fastboot -w --skip-reboot update image-adt3_gtv-trb4.220715.005.zip
./fastboot reboot bootloader; sleep 3
./fastboot flashing lock
./fastboot reboot
But this time ... it is not working

Are you sure that your fastboot version/drivers are new/good?
Within a few days I will try to update mine, in order to see if there are any issues.
Are you familiar with worldcup burn mode?
Obtain worldcup drivers and command line "update" program for your OS.
Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;
update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"
Then reboot and see if fastboot works.

./fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/platform-tools/fastboot
I just upgrade it b4 I do the Android TV 13 Beta 4.
Sorry ... I have no idea of "worldcup burn mode"

Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3

ToToHayashi said:
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
Click to expand...
Click to collapse
Did you try the update method as suggested by "Deleted member 11959327" ?
To get the tool i recommend the Khadas Git (khadas/utils) then the aml-flash-tool/ is the folder with Amlogic tools
for the update tool its in tools/linux-x86/update