Hello, I have several days trying to install bootloader and TWRP, but I can not.
I have a kindle fire 2, 10.4.6, standard USB cable.
If I can get into fastboot mode without problem, but when you type the command:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
I get this error:
target reported max download size of 486539264 bytes
Error: can not load otter2-u-boot-prod-10.2.4.bin No Error
I have windows 7 and all the drivers installed. I tried it on another computer, but same error.
I would appreciate some help, I have looking forward to putting on another rom
thanks
Related
Hi all,
I purchased a One X from eBay and it's got a custom rom on it which is horrendous - just keeps rebooting the phone etc. I'm trying to putting a stock rom back on (or just a better custom rom if it's easy enough to do) so I followed a tutorial I found on this forum for going back to ruu (there's no recovery image on the phone either).
Following those instructions I typed in 'fastboot oem lock'. Since doing that I've been stuck in the boot menu (it now refuses to load the rom that's installed and says 'relocked' at the top), and all I can do is switch between hboot and fastboot. If I run the correct ruu exe it just says it can't find the phone. Giving up on going back to stock I thought I'd just switch to a better quality custom rom but struggling with that as well..
I've just tried to reunlock the phone by following the instructions on htcdev.com, but when typing in fastboot oem get_identifier_token I get the following error:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
...
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
Infact, it appears to not be able to execute any fastboot commands!
What would you recommend the next step is? Is there any way out of this?
Copy these files and place them looking like this
C:\fastboot\*files i gave with the link*
http://db.tt/ldx3qOOU
and also install the HTC drivers (if you didn't install them yet), after that you put the phone in the fastboot usb mode and open a dosprompt inside the fastboot folder and type
Fastboot devices
This should give the serial in return .... try this all first and we take it from there !
Hi, i'm running on my Huawei watch the following developer preview:
android wear:
2.0.0.134438342
android os
7.0
I'm about to change to negalite rom, but i can't install the TWRP howewer hard i try via minimal adb and fastboot and i cant install anything on my watch.
this rom:
http://forum.xda-developers.com/hua...-negalite-huawei-rom-nx-root-bb-v1-6-t3406813
Every time i try to upload something to my watch as "adp sideload" or adb push i always have this message:
error: device '(null)' not found or "waiting for device"
I made all the steps like becoming a developer, setting to debugging, running the commands in Minimal ADB and Fastboot but as i try to flash recovery i got the error message all the time:
i tried these 2 versions:
fastboot flash recovery TWRP2.8.7.0-Sturgeon.img
fastboot flash recovery twrp-f2fs-3.0.2-sturgeon.img
I placed all the files in adb minimal and fastboot folder:
link for picture:
https://www.sugarsync.com/pf/D913403_07999065_914974
So the error is this when itry toflash recovery :
"waiting for device"
link for picture:
https://www.sugarsync.com/pf/D913403_07999065_914976
So the error is this when itry to upload in adb sideload an ota.zip (original rom):
error: device '(null)' not found
link for picture:
https://www.sugarsync.com/pf/D913403_07999065_914840
please help me what to do?
thanks
Hi all,
I am getting a headached with my mix 2 ......
Bootloader is unlocked (shown in Developer Settings and as little text when entering Backup/Fastboot).. I tried different Versions of fastboot from an old version 1:7.0.0+r33-2 to an new one -> fastboot version 28.0.0-4797878.
MIUI Version: 9.6.1.0(ODEMIFD) (Stable)
And yes I did it like the manual here on xda for this mobile ...
I also changed the System from Windows 10 to an Kali....
There isn't a single line of output.
Trying to directly boot the TWRP Image stucks at the first line telleng me: Downloading 'boot.img'
Someone can help me?
Friend here who helped him:
Even just listing the variables didn't yield any output (download got stuck on the "getvar: stuff, too)
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
ernesto.ulloa said:
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
Click to expand...
Click to collapse
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
techler said:
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
Click to expand...
Click to collapse
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
techler said:
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
Click to expand...
Click to collapse
EDIT:
It worked, i changed to my laptop(win 10). I used a git bash(random used this), no usb devices are connected and no internet.
Just typed .\fastboot.exe flash recovery twrp.img
It worked
Warning: Only reboot to Recovery and install the .img with the "temporary" again, if you don't Xiaomi will place it's own bootloader again there.
Code:
C:\Users\......\Desktop\MTK Usb Driver v1.0.8\MTK_Driver_ ext>fastboot flash system
"C:\Users\......\Latest ADB Fastboot Tool\system.img"
load_file: could not allocate -854277216 bytes
error: cannot load 'C:\Users\trg\Latest ADB Fastboot Tool\system.img'
See below...
Code:
C:\Users\......\Desktop\MTK Usb Driver v1.0.8\MTK_Driver_ ext>fastboot flash system
"C:\Users\......\Latest ADB Fastboot Tool\system.img"
load_file: could not allocate -854277216 bytes
error: cannot load 'C:\Users\trg\Latest ADB Fastboot Tool\system.img'
How to fix this error:
Method 1
I found people online saying that the reason for this error was that the Fastboot/ADB version was too old, and maybe that is true. According to them, there is a limit to the file size that older versions of Fastboot can flash. So you could try that if you like. If it doesn't work, try the method below.
Method 2
This method actually worked for me. Using this tool called mfastboot (I've attached the file below too) allows you to simply use mfastboot in your commands instead of fastboot and large files will flash successfully. Just place the correct file for your OS into your Fastboot/ADB folder, and flash away!
Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards
caraman said:
Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards
Click to expand...
Click to collapse
Ok, I managed the problem, I guess.
I startet power shell from the "platform tools" folder.
Now there is a other issue:
PS C:\Program Files\platform-tools> fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.535s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.836s
PS C:\Program Files\platform-tools>
The problem seems to be the partition, but I have no idea where to start troubleshooting...
Still reaching out to you for a little help, please...
Thx, regards