Database Users

[Q] Help with Android Transporter for Nexus 7 and Raspberry Pi

Hello,
I saw this android transporter tutorial for the nexus 7 and the raspberry pi on this site named esrlabs dot com. (sorry, i cant post links yet) I got the image for the raspberry pi on my raspberry, but I don't get it on the Nexus 7. In the tutorial they give the instruction that I must open the flash-all.sh file and than its done. The only problem is that I cant get it opened, maybe because i'm running windows 7 (64-bit). I read on the internet that a .sh file in linux is the same as a .bat file in windows. So, does somebody know how I can get that image flashed to my nexus 7?
Thanks

Aswin645 said:
In the tutorial they give the instruction that I must open the flash-all.sh file and than its done. The only problem is that I cant get it opened, maybe because i'm running windows 7 (64-bit).
Click to expand...
Click to collapse
.sh, shell script file is very similar to a .bat file, the only reason you would open one is to edit it. Normally you would run it in the environment it's meant to be run i.e. not Windows. You haven't given any info on where the information you got is so no-one will be able to tell you if it's accurate or not. I have to say that my experience of 'some' Linux instructions is that they are intentionally, frustratingly obscure, possibly to give the writer that 'superior' feeling or to hide that they know not a lot themselves.

Troute said:
.sh, shell script file is very similar to a .bat file, the only reason you would open one is to edit it. Normally you would run it in the environment it's meant to be run i.e. not Windows. You haven't given any info on where the information you got is so no-one will be able to tell you if it's accurate or not. I have to say that my experience of 'some' Linux instructions is that they are intentionally, frustratingly obscure, possibly to give the writer that 'superior' feeling or to hide that they know not a lot themselves.
Click to expand...
Click to collapse
the file is on esrlabs dot com, I already said I cant post links. scroll down a bit and you wil see a title called "ANDROID TRANSPORTER FOR THE NEXUS 7 AND THE RASPBERRY PI"

The shell script is meant to be run on your Nexus 7. The instructions are rather clear but it is meant for advanced users. You realize that this will flash new firmware on your Nexus 7, right?
The instructions tell you everything you need to do. First, you must install the adb and fastboot utilities and, if you're on windows, you must install the USB drivers as well. The .sh is a shell script and won't run on a regular Windows PC. The script simply automates the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update android-transporter.zip
Run each of those commands in turn and it'll do the same thing as the script.

jefftheworld said:
The shell script is meant to be run on your Nexus 7. The instructions are rather clear but it is meant for advanced users. You realize that this will flash new firmware on your Nexus 7, right?
The instructions tell you everything you need to do. First, you must install the adb and fastboot utilities and, if you're on windows, you must install the USB drivers as well. The .sh is a shell script and won't run on a regular Windows PC. The script simply automates the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update android-transporter.zip
Run each of those commands in turn and it'll do the same thing as the script.
Click to expand...
Click to collapse
Thanks for your reply,
I tried to put this commands in the adb command line but when I do that I get this:
Code:
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>adb reboot bootl
oader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>android-transpor
ter\flash-all.sh
The system cannot find the path specified.
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>flash-all.sh
'flash-all.sh' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot erase b
oot
erasing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.141s
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot erase c
ache
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.269s
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot erase r
ecovery
erasing 'recovery'...
OKAY [ 0.138s]
finished. total time: 0.140s
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot erase s
ystem
erasing 'system'...
OKAY [ 0.467s]
finished. total time: 0.471s
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot erase u
serdata
erasing 'userdata'...
OKAY [ 23.257s]
finished. total time: 23.258s
C:\Users\user\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
ootloader bootloader-grouper-3.34.img
error: cannot load 'bootloader-grouper-3.34.img'
C:\Users\Aswin\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
ootloader bootloader-grouper-3.34.img
error: cannot load 'bootloader-grouper-3.34.img'
Do you know why I cant load the bootloader? And did I maybe put the commands in the wrong way?

Anyone?

Seeing as how you've been spamming my inbox asking for an answer, I suppose I'll just chime in and say that you probably don't have the technical skill to complete this project currently. I'd recommend learning a bit more about using fastboot and working with a command line interface.
I see that in this case you've attempted to run a unix shell script again:
Code:
'flash-all.sh' is not recognized as an internal or external command,
operable program or batch file
As I mentioned before, that simply won't work. You need to run the commands that I gave you and while you seem to have run most of them, you didn't correctly run the following command:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
I think the problem is that you're running all these commands from the platform-tools directory and the image you're trying to flash probably isn't in that directory. The command you're issuing is formatted in a way that it's checking for bootloader-grouper-3.34.img in the current directory. The easy way to fix this is to change the command to use an absolute path to the file in question (c:\directory\where\you\put\bootloader-grouper-3.34.img). Really, you should add the platform-tools directory to your PATH so that you can run those commands from any given directory.
If you have more questions or issues, please be patient and don't spam people.

[PROBLEM!] I can't unlock the bootloader

Greetings to all the XDA forum
Is anyone able to help me? Let me explain my problem:
I can not unlock the bootloader, I tried the procedure to be CMD, even by flashing the sbf file called "intl-fix-try1.sbf"
The result is bootloop status
I have root permissions...
The specifications of my phone are:
_______________________________________________
-SYSTEM VERSION: 45.31.0.MB860.Retail.en.IT
-MODEL NUMBER: MB860
-ANDROID VERSION: 2.3.4
-MODEM VERSION: N_01.100.00R
-WEBTOP VERSION: WT.1.2.0-133_38
-KERNEL VERSION:
2.6.32.9
[email protected] #3
-APflex VERSION:
GAS_EMEA_USAOLYGBRTIT_P018
GAS_EMEA_USAOLYGBRTIT_A006
GAS_EMEA_USAOLYPRTEU_M001
-BUILD NUMBER: 4.5.2A-74_OLE-31
________________________________________________
Thanks to all who help me!!! :good:

Now turn on ur mobile (power+volume up key), and after that connect ur phone via usb, opet cmd and navigate to moto-fastboot folder. Enter command moto-fastboot.exe oem unlock, u will see ID of ur phone. After that type moto-fastboot.exe oem unlock yourID and ur phone is unlocked. After that just type moto-fastboot.exe reboot and enjoy.

neoxx3m said:
Now turn on ur mobile (power+volume up key), and after that connect ur phone via usb, opet cmd and navigate to moto-fastboot folder. Enter command moto-fastboot.exe oem unlock, u will see ID of ur phone. After that type moto-fastboot.exe oem unlock yourID and ur phone is unlocked. After that just type moto-fastboot.exe reboot and enjoy.
Click to expand...
Click to collapse
My Atrix is Italian... which files should I download?
Could you put the link?
thanks

M4nu3l1c4t4 said:
My Atrix is Italian... which files should I download?
Could you put the link?
thanks
Click to expand...
Click to collapse
Just try cmd again, it should work after failed flashing sbf.
Sent from my MB860 using xda app-developers app

In my pc i haven't the folder "moto-fastboot"...
I have an folder "fastboot" contenents 3 files...
Are talking about the same folder?
I've already tried, but without engaging in the command "moto-fastboot.exe".
I try again by entering that command?

M4nu3l1c4t4 said:
In my pc i haven't the folder "moto-fastboot"...
I have an folder "fastboot" contenents 3 files...
Are talking about the same folder?
I've already tried, but without engaging in the command "moto-fastboot.exe".
I try again by entering that command?
Click to expand...
Click to collapse
What files u have in fastboot folder?
Sent from my MB860 using xda app-developers app

neoxx3m said:
What files u have in fastboot folder?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I have:
AdbWinApi.dll ( 94KB )
AdbWinUsbApi.dll ( 60 KB )
fastboot.exe ( 180 KB )

M4nu3l1c4t4 said:
I have:
AdbWinApi.dll ( 94KB )
AdbWinUsbApi.dll ( 60 KB )
fastboot.exe ( 180 KB )
Click to expand...
Click to collapse
ok, type fastboot.exe oem unlock, than fastboot.exe oem unlock yourid, and than fastboot.exe reboot. u must put ur phone in fastboot mode first.

neoxx3m said:
ok, type fastboot.exe oem unlock, than fastboot.exe oem unlock yourid, and than fastboot.exe reboot. u must put ur phone in fastboot mode first.
Click to expand...
Click to collapse
I used the command "fastboot oem unlock"
The CMD was successful, but then the phone was in a state of bootloop
I try again with "fastboot.exe oem unlock"?

M4nu3l1c4t4 said:
I used the command "fastboot oem unlock"
The CMD was successful, but then the phone was in a state of bootloop
I try again with "fastboot.exe oem unlock"?
Click to expand...
Click to collapse
Did u retype that command with ID that u get after typing first command? Did u reboot in the end?
Sent from my MB860 using xda app-developers app

Leeco blocked !

Hello, I just received my leeco, But I received it with a modified rom
I have try to install TWRP recovery, for recovery its good It is installed
But since the phone dosent started he stay on the logo leeco android As if there were no rom
So I tried to push a rom via ADB but I have a closed error, and Since the recovery I can not mount the system or the SD on my PC for copy rom
i try this :
C:\Program Files (x86)\Minimal ADB and Fastboot> adb sideload leco.zip
loading: 'leco.zip'
* cannot read 'leco.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push leco.zip /data/media/0/
adb: error: connect failed: closed
I do not know what to do
EDIT : in recovery he says me he have not rom installed, so i think usb debuging is desactivated
thanks

k3npachi said:
Hello, I just received my leeco, But I received it with a modified rom
I have try to install TWRP recovery, for recovery its good It is installed
But since the phone dosent started he stay on the logo leeco android As if there were no rom
So I tried to push a rom via ADB but I have a closed error, and Since the recovery I can not mount the system or the SD on my PC for copy rom
i try this :
C:\Program Files (x86)\Minimal ADB and Fastboot> adb sideload leco.zip
loading: 'leco.zip'
* cannot read 'leco.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push leco.zip /data/media/0/
adb: error: connect failed: closed
I do not know what to do
thanks
Click to expand...
Click to collapse
The First error "cannot read leco.zip" looks like a typo maybe it's called leeco.zip?
Otherwise for me it looks like a adb problem or somehow a connection problem with adb
You sure installed all the drivers? Or has your cable a connection problem?
These are my theories, try some of them...

Antisound said:
The First error "cannot read leco.zip" looks like a typo maybe it's called leeco.zip?
Otherwise for me it looks like a adb problem or somehow a connection problem with adb
You sure installed all the drivers? Or has your cable a connection problem?
These are my theories, try some of them...
Click to expand...
Click to collapse
No leco.zip its the good name.
But before is locked adb working good, it's only since blocked
He have not solution for Mount internal storage since TWRP ?
Thanks

k3npachi said:
No leco.zip its the good name.
But before is locked adb working good, it's only since blocked
He have not solution for Mount internal storage since TWRP ?
Thanks
Click to expand...
Click to collapse
Maybe you have to try the EDL

venezolano69 said:
Maybe you have to try the EDL
Click to expand...
Click to collapse
sorry but what is EDL ?

k3npachi said:
sorry but what is EDL ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-note-3/help/flashing-locked-phone-via-edl-mode-t3373275/page1

venezolano69 said:
http://forum.xda-developers.com/redmi-note-3/help/flashing-locked-phone-via-edl-mode-t3373275/page1
Click to expand...
Click to collapse
ok thanks i test that

Haha i have find how to, If it can help some
http://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/

u find Qualcomm Drivers to download ?

what to do

this is happening during installing twrp
android 9

reeeju said:
this is happening during installing twrp
android 9
Click to expand...
Click to collapse
Download that dll and place it at the root of the folder of the program that errors
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
Download that dll and place it at the root of the folder of the program that errors
Sent from my ZenFone Max Pro M1 using Tapatalk
Click to expand...
Click to collapse
already tried that but same result..pls help me...my phones bootloader is unlocked but cant install twrp

reeeju said:
already tried that but same result..pls help me...my phones bootloader is unlocked but cant install twrp
Click to expand...
Click to collapse
Hmm did you installed fastboot?
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
Hmm did you installed fastboot?
Sent from my ZenFone Max Pro M1 using Tapatalk
Click to expand...
Click to collapse
YES

this is showing when trying to istall twrp
RedGreenBlue123 said:
Hmm did you installed fastboot?
Sent from my ZenFone Max Pro M1 using Tapatalk
Click to expand...
Click to collapse
what to do now?

reeeju said:
what to do now?
Click to expand...
Click to collapse
Use cmd instead of powershell
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
Use cmd instead of powershell
HTML:
C:\Users\Dr Arkaprava Simlai>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse

reeeju said:
C:\Users\Dr Arkaprava Simlai>fastboot devices'fastboot' is not recognized as an internal or external command,operable program or batch file.
Click to expand...
Click to collapse
You have your answer now. Use platform tools and open cmd on platform tools folder with admin rights.
And please avoid posting your issue in different threads simultaneously.

Tianhe said:
You have your answer now. Use platform tools and open cmd on platform tools folder with admin rights.
And please avoid posting your issue in different threads simultaneously.
Click to expand...
Click to collapse
this is showing when trying to do with platform tools
HTML:
PS C:\platform-tools> .\fastboot devices
J9AAGF09K499AXA fastboot
PS C:\platform-tools> .\fastboot flash recovery twrp.img
Sending 'recovery' (28884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed

Tianhe said:
You have your answer now. Use platform tools and open cmd on platform tools folder with admin rights.
And please avoid posting your issue in different threads simultaneously.
Click to expand...
Click to collapse
using platform tools and cmd run with administrator permission,,,,but fails....it shows as follows:-
HTML:
C:\WINDOWS\system32>fastboot flash recovery twrp.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Tianhe said:
You have your answer now. Use platform tools and open cmd on platform tools folder with admin rights.
And please avoid posting your issue in different threads simultaneously.
Click to expand...
Click to collapse
using minimal adb and cmd.exe turns into this result
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (28884 KB)...
FAILED (command write failed (No error))
finished. total time: 0.008s

reeeju said:
using platform tools and cmd run with administrator permission,,,,but fails....it shows as follows:-
HTML:
C:\WINDOWS\system32>fastboot flash recovery twrp.img'fastboot' is not recognized as an internal or external command,operable program or batch file.
Click to expand...
Click to collapse
You must cd to the folder of fastboot
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
You must cd to the folder of fastboot
Sent from my ZenFone Max Pro M1 using Tapatalk
Click to expand...
Click to collapse
didnt understand...please elaborate if you dont mind

reeeju said:
didnt understand...please elaborate if you dont mind
Click to expand...
Click to collapse
Sorry for slow respond. I mean you type "cd C:\Path\to\adb"
Then fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using XDA Labs

RedGreenBlue123 said:
Sorry for slow respond. I mean you type "cd C:\Path\to\adb"
Then fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using XDA Labs
Click to expand...
Click to collapse
HTML:
C:\WINDOWS\system32>cd C:\Path\to\adb
The system cannot find the path specified.

reeeju said:
HTML:
C:\WINDOWS\system32>cd C:\Path\to\adbThe system cannot find the path specified.
Click to expand...
Click to collapse
I mean you cd " the folder of adb "
Sent from my ZenFone Max Pro M1 using Tapatalk

[Guide] Bypass "FAILED (Write to device failed (Invalid argument))" in ADB and root your MM3.

THIS ILLUSTRATION IS FOR MI MAX 3 , NITROGEN. THE LINKS FOR ORANGEFOX RECOVERY IS ONLY FOR MI MAX 3, IT IS NOT SUITABLE FOR OTHER PHONE. PLEASE DOWNLOAD THE APPROPRIATE ONE FOR YOUR PHONE.
As some of you might be aware, many of us with modern hardware (especially Ryzen users) are encountering this error in ADB.
"FAILED (Write to device failed (Invalid argument))".
Today, i have successfully bypass this error. Plus, i will teach you how to install OrangeFox Recovery and Magisk Root without the need of having these files inside your phone.
PLEASE READ AND FOLLOW THE STEPS CAREFULLY.
1. This guide shows the proper way to Setup ADB, USB Drivers and Enable USB Debugging. Take note, Extract the platform-tools folder to C drive . Example: "c:\platform-tools".
If you do not do these properly you might have issues with PowerShell not recognizing commands. After following this guide, you should have downloaded adb, setup windows environmental variables, installed universal ADB driver and set phone into debugging mode.
- https://wiki.lineageos.org/adb_fastboot_guide.html
2. Download Magisk-v20.4.zip and OrangeFox-R10.1-Stable-nitrogen.zip then place these two files into the folder "c:\platform-tools".
https://sourceforge.net/projects/orangefox/files/nitrogen/
https://github.com/topjohnwu/Magisk/releases
3. Open OrangeFox-R10.1-Stable-nitrogen.zip and extract recovery.img into the folder "c:\platform-tools". At this point, the "c:\platform-tools" folder should have these three files.
OrangeFox-R10.1-Stable-nitrogen.zip
Recovery.img
Magisk-v20.4.zip
4. Open Windows Powershell in the same folder
Result: PS C:\platform-tools>
Follow instructions carefully from here, DO NOT PLUG IN YOUR DEVICE YET. This is where you bypass the error.
5. Type fastboot boot recovery.img (DO NOT PLUG IN YET!!)
Result: PS C:\platform-tools> fastboot boot recovery.img
Result: < waiting for any device >
6. Boot your device to Fastboot Mode option and plug in now, you will be booted into OrangeFox Recovery.
Result: Sending 'boot.img' (63952 KB) OKAY [ 1.588s]
Result: Booting OKAY [ 0.130s]
Result: Finished. Total time: 1.782s
7. In OrangeFox Recovery menu, setup your device for ADB sideloading. Feel free to wipe any of them cache when prompted, it does not matter. Once it has established ADB sideloading mode, head back to your computer.
8. Type adb sideload OrangeFox-R10.1-Stable-nitrogen.zip
Result: PS C:\platform-tools> adb sideload OrangeFox-R10.1-Stable-nitrogen.zip
9. Repeat step 7 then Type adb sideload Magisk-v20.4.zip
Result: PS C:\platform-tools> adb sideload Magisk-v20.4.zip
10. You have succesfully installed orangefox recovery, as well as rooted your phone with magisk.

I assume this can only by done when bootloader is unlocked?

annoniem said:
I assume this can only by done when bootloader is unlocked?
Click to expand...
Click to collapse
of course, u need boot-loader unlock for most modification.

This didn't work for me. I gave me this error.
< waiting for any device >
Sending 'boot.img' (65536 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
adb devices
adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
bf42de30 device
What do i do now????

This resulted the same thing for me. Did not work.

ra4452 said:
This didn't work for me. I gave me this error.
< waiting for any device >
Sending 'boot.img' (65536 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
adb devices
adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
bf42de30 device
What do i do now????
Click to expand...
Click to collapse
This is a different error, u have to find another resolution.

HSWG said:
THIS ILLUSTRATION IS FOR MI MAX 3 , NITROGEN. THE LINKS FOR ORANGEFOX RECOVERY IS ONLY FOR MI MAX 3, IT IS NOT SUITABLE FOR OTHER PHONE. PLEASE DOWNLOAD THE APPROPRIATE ONE FOR YOUR PHONE.
As some of you might be aware, many of us with modern hardware (especially Ryzen users) are encountering this error in ADB.
"FAILED (Write to device failed (Invalid argument))".
Today, i have successfully bypass this error. Plus, i will teach you how to install OrangeFox Recovery and Magisk Root without the need of having these files inside your phone.
PLEASE READ AND FOLLOW THE STEPS CAREFULLY.
1. This guide shows the proper way to Setup ADB, USB Drivers and Enable USB Debugging. Take note, Extract the platform-tools folder to C drive . Example: "c:\platform-tools".
If you do not do these properly you might have issues with PowerShell not recognizing commands. After following this guide, you should have downloaded adb, setup windows environmental variables, installed universal ADB driver and set phone into debugging mode.
- https://wiki.lineageos.org/adb_fastboot_guide.html
2. Download Magisk-v20.4.zip and OrangeFox-R10.1-Stable-nitrogen.zip then place these two files into the folder "c:\platform-tools".
https://sourceforge.net/projects/orangefox/files/nitrogen/
https://github.com/topjohnwu/Magisk/releases
3. Open OrangeFox-R10.1-Stable-nitrogen.zip and extract recovery.img into the folder "c:\platform-tools". At this point, the "c:\platform-tools" folder should have these three files.
OrangeFox-R10.1-Stable-nitrogen.zip
Recovery.img
Magisk-v20.4.zip
4. Open Windows Powershell in the same folder
Result: PS C:\platform-tools>
Follow instructions carefully from here, DO NOT PLUG IN YOUR DEVICE YET. This is where you bypass the error.
5. Type fastboot boot recovery.img (DO NOT PLUG IN YET!!)
Result: PS C:\platform-tools> fastboot boot recovery.img
Result: < waiting for any device >
6. Boot your device to Fastboot Mode option and plug in now, you will be booted into OrangeFox Recovery.
Result: Sending 'boot.img' (63952 KB) OKAY [ 1.588s]
Result: Booting OKAY [ 0.130s]
Result: Finished. Total time: 1.782s
7. In OrangeFox Recovery menu, setup your device for ADB sideloading. Feel free to wipe any of them cache when prompted, it does not matter. Once it has established ADB sideloading mode, head back to your computer.
8. Type adb sideload OrangeFox-R10.1-Stable-nitrogen.zip
Result: PS C:\platform-tools> adb sideload OrangeFox-R10.1-Stable-nitrogen.zip
9. Repeat step 7 then Type adb sideload Magisk-v20.4.zip
Result: PS C:\platform-tools> adb sideload Magisk-v20.4.zip
10. You have succesfully installed orangefox recovery, as well as rooted your phone with magisk.
Click to expand...
Click to collapse
PS C:\Users\prakh> fastboot flash recovery C:\adb\twrp-3.2.3-0-X00TD-20180814.img < waiting for device > sending 'recovery' (58108 KB)... FAILED (remote: Requested download size is more than max allowed)
why i am facing this issue ??