Related
this is what I had to do on Linux Mint 12 but should work with most ubuntu based distros
1: download twrp
2: if you dont already have it then you need to download the linux fastboot binary, extract the .zip and place the extracted file in your androidsdk/platform-tools directory
2: place the file you downloaded from TWRP into your androidsdk/platform-tools directory
3: connect your fire to your computer and disable mass storage mode
4: open a terminal and cd to your androidsdk/platform-tools directory and enter the following commands pressing enter after each line
Code:
./adb shell
su
idme bootmode 4002
then back out of the adb shell by
Code:
exit
exit
then
Code:
./adb reboot
after it reboots to the "Kindle Fire" boot screen its time to flash the recovery
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
once flashed and it installs and boots to the "firefirefire" screen (screen with the yellow sign and text that says "press power for recovery" you have to change the boot mode back out of fastboot
Code:
sudo ./fastboot oem idme bootmode 4000
sudo ./fastboot reboot
it should reboot to the "firefirefire" screen, to enter recovery press and hold the power button until it turns from green to orange then let go. You should boot into TWRP and be able to make your first backup.
from now on if you dont want to go into recovery then just let it sit and it will boot normally
Thanks to all the Teamwin members, agrabren for the port, pyrostic for testing, pokey9000 for the "FireFireFire" bootloader, and I am sure there are more but I dont know who you are so thank you.
if you can donate to these guys please do becuase without them we would just have an e-reader.
I am not responsable for any damage that YOU may cause buy following these directions.
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
issue the command with sudo
Nevermind, wasn't using ./ when I was issuing commands. As usual, need to pay better attention.
Thanks OP. Sweet.
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
abiezer said:
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
Click to expand...
Click to collapse
adb wont recogonize it after you change the boot mode thats where you issue the fastboot commands
smirkis said:
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
Click to expand...
Click to collapse
Download this file and place it in the folder your fastboot is located in: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
do the following
open a command window where fastboot is located:
Step 1:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. if it still says "waiting for device" close the window and then then open a command window where fastboot is located and do step 2.
Step 2:
Code:
fastboot -i 0x18d1 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. If it is still not doing anything, this is where my knowledge is no good anymore, and you should consult someone else.
TWRP should be showing on your screen. Close your old fastboot window and open a new command window where ADB is located. Proceed to Step 3.
Step 3:
Code:
adb shell
idme bootmode 4000
reboot
your device should reboot, and if you had problems with Step 3 try the following from your ADB command window
Code:
su
adb kill-server
adb start-server
adb devices
your device should be listed. If so try Step 3 again.
hope this helps or at least puts you in the right direction.
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
craftyguy said:
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
sl0ttedpig said:
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
Click to expand...
Click to collapse
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
EDIT: Ok, had to pass "-i 0x1949" to fastboot. Got the device back, going to try it all over again
craftyguy said:
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
Click to expand...
Click to collapse
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
smirkis said:
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
try rebooting manually n see if u get fastbot.
Sent from my HTC Glacier using xda premium
craftyguy said:
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
Click to expand...
Click to collapse
woot for fedora! anyway, i set things up via /etc/udev/rules.d/51-android.rules and at first I had this...
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
and everything was cool. but after flashing twrp, i noticed there was firefirefire 1.0 out where previously i had flashed .9 so i thought id update I went to update and after putting the device in fastboot mode, it rebooted to the bootloader where fastboot wasnt recognizing the device started digging around and found windows users having driver issues and thought to myself... we dont have drivers BUT we do have rules!! added this line to the udev rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and everything working as it should again
Hey guys, I'm a new member to XDA but I've been browsing on it for a while. I figured you guys could help. I rooted my Kindle Fire a couple months ago and had Clockwork Recovery(TWRP is better). I decided I didn't want it rooted so I restored the Kindle thinking it would remove the root, it actually bricked it. Now all that comes up is the Kindle Fire boot screen with the android bot over top of it, it doesn't glimmer or flash, that's all. It isn't recognized by ADB or Windows(and Device Manager). I haven't found a thread exactly like mine so I figured I'd post one. Please help guys, I miss Minecraft PE and Netflix!
Assuming you know how to access recovery...
Download the latest version of FireFireFire and either "adb push" it to your sdcard or use the mount function in recovery and transfer it.
FireFireFire 1.4 can be found here. It comes in a .zip file for flashing in recovery. DO NOT install the .zip file with the "fastboot flash bootloader" command or you will brick your device.
When installed reboot and use your power button at the kindle fire screen as if you were trying to enter recovery. At some point some options will show up on the bottom. Use the power button to select "Normal Boot".
@soupmagnet
what do you mean by ADB Push? Recovery as in turning the kindle on and then holding the power button again until it turns orange?
mrpike9416 said:
@soupmagnet
what do you mean by ADB Push?
Click to expand...
Click to collapse
Actually, it would be easier to explain how to mount your sdcard.
Recovery as in turning the kindle on and then holding the power button again until it turns orange?
Click to expand...
Click to collapse
Yes. While in recovery, there will be a mount to USB function that will mount the sdcard partition to your computer as if it were an external drive, such as a USB thumb drive.
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
mrpike9416 said:
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
Click to expand...
Click to collapse
Recovery is in a separate partition from the system files and cannot be formatted while in recovery. I'm not sure why you wouldn't be able access recovery so you'll probably need to reinstall it.
How comfortable are you with using command prompt?
A little experienced, how hard can entering commands be?
mrpike9416 said:
A little experienced, how hard can entering commands be?
Click to expand...
Click to collapse
OMG Don't EVER say that.
Do you have adb and fastboot on your computer? If yes...Is it from AndroidSDK or KFU?
Hahahahha my mistake.
I do have ADB but I don't think I have fastboot(I probably do).
I do have fastboot.
mrpike9416 said:
I do have fastboot.
Click to expand...
Click to collapse
Okay, make sure the you have TWRP version 2.1 and place it in the same folder as fastboot. It would be wise to rename it to something manageable like "twrp.img"
In your command prompt, enter:
fastboot flash recovery twrp.img
Note: version 2.0 will not work with this command
And while you're at it:
fastboot oem idme bootmode 4000
fastboot reboot
[Edit:] That will likely fix your problem (barring driver issues) but you should still install FFF1.4
I just tried a different cable and the computer recognizes my kindle in device manager as Android ADB Interface... the twrp 2.1 cmd thing you told me to do was a no go but I assume we have more options now now that device manager recognizes it?
(EDIT)
It is now recognized on device manager as "Unknown Device" and no longer as Android ADB Interface..
1. What happens when you enter:
Code:
fastboot devices
2. What error message, if any, did you receive when entering the "twrp 2.1 cmd thing"?
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
mrpike9416 said:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
Click to expand...
Click to collapse
Do you have fastboot and what folder is it in?
Yeah its an .exe file i believe... under the "Files and Tools" folder when I downloaded ADB from Android SDK.
Better yet...fastboot and adb are programs with a certain set of commands associated with them. Those commands only work with each individual program. In order to issue a certain command that isn't associated with "shell" or "DOS" you have to include an "identifier" so the computer knows from which program to run the commands. In this case it is "fastboot" because you are using the fastboot program. In order issue commands this way, the program you are using must either be listed in your "PATH" or be in the directory from which you are issuing the commands.
The easiest way to do this in Windows is to shift+right click on the folder containing the program and select "Run in Command". The command window that opens is were you will be entering your commands.
error: cannot load "twrp.img"
I typed "fastboot devices!" (out of frustration I must admit).
This is what came up:
C:\Users\Nick\Documents\KindleRoot\tools>fastboot devices!
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
soupmagnet said:
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
Click to expand...
Click to collapse
what command am I entering?
My kindle fire is bricked. I'm not sure it can be undone, as fastboot can't seem to change the bootmode.
Where I'm at (short version):
Mac os x 10.6.8
Kindle stuck on the amazon stock "Kindle fire" logo.
Kindle connected with factory cable.
Log:
> fastboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.000s
> fastboot -i 0x1949 oem idme bootmode 4000
...
^C
How I go here:
I tried the KFU on a Windows VM running on Mac osx 10.6.8. Yes, that was dumb.
I went for the quick and dirty solution, it did not end well.
I've read the kindle beginners guide. Excellant resource. Switched to the Mac terminal interface.
My Knowledge:
I'm a knowledgeable unix user, android newbie. Meaning I know just enough to get myself in trouble.
Any suggestions would be appreciated. About the only other thing I can think to try is a linux interface instead of MAC.
Thanks,
Ann
The command you posted was successful. Did you reboot the device?
soupmagnet said:
The command you posted was successful. Did you reboot the device?
Click to expand...
Click to collapse
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
adavis749 said:
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
Click to expand...
Click to collapse
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
prahladvarda said:
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
Click to expand...
Click to collapse
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
soupmagnet said:
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
Click to expand...
Click to collapse
I have tried that as well.
Ok, so I got another kindle fire gen 1 to play with and fix. I have a factory fastboot cable and can get into the device with TWRP. I am able to use fastboot to flash the boot, bootloader and recovery img files to the device and change it back to stock or use KFU to install TWRP and firefirefire to get those options back.
When I was wiping the device, I did wipe the system as well as the cache. I don't have a system.img to flash back onto it and I can't connect to it with ADB to push the update.zip down to the device either. The device is not recognized by my Windows 7 computer for the ADB side of the house anymore. (It did work for both ADB and Fastboot on previous devices and this one). I have tried reinstalling the KFU drivers, amazon drivers etc. The only function I can get to work is fastboot, which does allow me to flash partitions.
When I go into TWRP it will not allow me to mount the system, and the size says "0". It also says "unable to mount /system" in the window when trying to run various commands in TWRP. Is there another way to get a system.img so I can flash that as well. If I try the update update.zip method it tells me there are missing android.txt files. I've done a lot of research up here and tried a lot of the solutions here as well, but this device is being stubborn or I'm missing something or need to repartition system to mount it or some other issue.
Any help is appreciated, would like to beat this and flash the system to stock if possible?
smloftus said:
Ok, so I got another kindle fire gen 1 to play with and fix. I have a factory fastboot cable and can get into the device with TWRP. I am able to use fastboot to flash the boot, bootloader and recovery img files to the device and change it back to stock or use KFU to install TWRP and firefirefire to get those options back.
When I was wiping the device, I did wipe the system as well as the cache. I don't have a system.img to flash back onto it and I can't connect to it with ADB to push the update.zip down to the device either. The device is not recognized by my Windows 7 computer for the ADB side of the house anymore. (It did work for both ADB and Fastboot on previous devices and this one). I have tried reinstalling the KFU drivers, amazon drivers etc. The only function I can get to work is fastboot, which does allow me to flash partitions.
When I go into TWRP it will not allow me to mount the system, and the size says "0". It also says "unable to mount /system" in the window when trying to run various commands in TWRP. Is there another way to get a system.img so I can flash that as well. If I try the update update.zip method it tells me there are missing android.txt files. I've done a lot of research up here and tried a lot of the solutions here as well, but this device is being stubborn or I'm missing something or need to repartition system to mount it or some other issue.
Any help is appreciated, would like to beat this and flash the system to stock if possible?
Click to expand...
Click to collapse
which TWRP and bootloader versions, original file names
sd_shadow said:
which TWRP and bootloader versions, original file names
Click to expand...
Click to collapse
TWRP is v2.2.2.1 which I read somewhere on here I need this version, I have others though.
openrecovery-twrp-2.2.2.1-blaze
The stock bootloader is what downloaded with the KFU option 6 Extras (Requires Root) option.
7 Download Amazon Kindle Fire 6.3.2 stock update.zip
8 Download Amazon Kindle Fire 6.3.1 stock update.zip
smloftus said:
TWRP is v2.2.2.1 which I read somewhere on here I need this version, I have others though.
openrecovery-twrp-2.2.2.1-blaze
The stock bootloader is what downloaded with the KFU option 6 Extras (Requires Root) option.
7 Download Amazon Kindle Fire 6.3.2 stock update.zip
8 Download Amazon Kindle Fire 6.3.1 stock update.zip
Click to expand...
Click to collapse
Those are stock firmware files (Bootloader/recovery/ROM)
first you should verify the md5 for the stock rom
about worst thing you can do is try to install incomplete file
update-kindle-6.3.2_D01E_4110520.bin MD5 Sum: 5ed369364db7c3409ce5fb651abd7cfa
update-kindle-6.2.2_D01E_3205220.bin MD5 Sum: 597c41d7a7dc20700af9cdb59608ac2b
https://sites.google.com/site/sdshadowscollection/home/hash-checksums
if correct make sure file ends in .zip like update.zip
or safer option is my update-kindle-prerooted.6.3.3.v1.zip does not replace FFF/TWRP
how is kindle shown in device manager?
sd_shadow said:
Those are stock firmware files (Bootloader/recovery/ROM)
first you should verify the md5 for the stock rom
about worst thing you can do is try to install incomplete file
update-kindle-6.3.2_D01E_4110520.bin MD5 Sum: 5ed369364db7c3409ce5fb651abd7cfa
update-kindle-6.2.2_D01E_3205220.bin MD5 Sum: 597c41d7a7dc20700af9cdb59608ac2b
https://sites.google.com/site/sdshadowscollection/home/hash-checksums
if correct make sure file ends in .zip like update.zip
or safer option is my update-kindle-prerooted.6.3.3.v1.zip does not replace FFF/TWRP
how is kindle shown in device manager?
Click to expand...
Click to collapse
It only shows up in the DM when connected with my fastboot cable as "Android ADB Interface".
The checksums appear fine.
As my original post stated I can't push files to the device with ADB because it won't recognize it in that mode, I'm stuck with fastboot and my factory cable. Is there a different way to us the file you posted? It won't upddate with fastboot update "FileName".
smloftus said:
It only shows up in the DM when connected with my fastboot cable as "Android ADB Interface".
The checksums appear fine.
As my original post stated I can't push files to the device with ADB because it won't recognize it in that mode, I'm stuck with fastboot and my factory cable. Is there a different way to us the file you posted? It won't upddate with fastboot update "FileName".
Click to expand...
Click to collapse
Yes it should be android phone/adb interface or android adb interface
Sent from my XT894 using Tapatalk
sd_shadow said:
Yes it should be android phone/adb interface or android adb interface
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
So is there a way using only fastboot to force a system partition update using your .zip file? The "E:unable to mount '/system' (tw_mount)" error I get is what really concerns me. If I could figure out why it's doing that or how to troubleshoot that I think I could figure out the rest...
smloftus said:
So is there a way using only fastboot to force a system partition update using your .zip file? The "E:unable to mount '/system' (tw_mount)" error I get is what really concerns me. If I could figure out why it's doing that or how to troubleshoot that I think I could figure out the rest...
Click to expand...
Click to collapse
Have you tried my update-kindle-prerooted.6.3.3.v1.zip ?
sd_shadow said:
Have you tried my update-kindle-prerooted.6.3.3.v1.zip ?
Click to expand...
Click to collapse
Oddly enough, I installed TWRP v2.6.3.1 and from teh device I did a wipe on the System partition and it used make_ext4fs function to format and update the partition, I was then able to mount it from within the device.
When I try to do an update I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Your update .zip is in both directories just to be sure it finds it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>set a
ANDROID_PRODUCT_OUT=C:\Program Files (x86)\Minimal ADB and Fastboot\FLASHALL
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashall update.zip
error: could not load android-info.txt: No error
smloftus said:
Oddly enough, I installed TWRP v2.6.3.1 and from teh device I did a wipe on the System partition and it used make_ext4fs function to format and update the partition, I was then able to mount it from within the device.
When I try to do an update I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Your update .zip is in both directories just to be sure it finds it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>set a
ANDROID_PRODUCT_OUT=C:\Program Files (x86)\Minimal ADB and Fastboot\FLASHALL
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashall update.zip
error: could not load android-info.txt: No error
Click to expand...
Click to collapse
no updates/roms must be installed in twrp, from sd card
---------- Post added at 03:11 PM ---------- Previous post was at 02:53 PM ----------
in TWRP>Mount>check sd card>Mount usb
copy pre-rooted 6.3.3 to sd card
unmount
Install
Having a weird issue I've never run into. Used to be on Invitrix rom, returned to stock via latest oreo flashall and wanted to get onto Lineage 15.1. While flashall works, I cannot boot from TWRP. I've attempted on both Windows 10, Ubuntu 18.04 LTS and Ubuntu 18.10 and ensured all drivers are installed. I've tried with and without sudo privilege just in case. I've tried renaming the .img to recovery.img, boot.img, etc.. Yet, I keep getting a simple failed message. Bootloader is still unlocked and I've tried multiple cables including the stock one, USB 2.0 and 3.0 ports on both my desktop and and laptop. Is my phone simply corrupted or am I missing something?
sudo fastboot boot twrp-3.2.3-0-nash.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
41rw4lk said:
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
Click to expand...
Click to collapse
I did. Device shows up like normal. I verified by typing
fastboot devices