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?
Related
Ok I can use commands VIA fastboot when the phone is on. The problem is using commands when the phone is in bootloader. It says "fastboot usb" But when i am trying to use commands like :adb reboot" i get a " device not found " error
The device is Eng s off and ship s off
Tryed this with 3 computers with no luck
I have all the needed drivers.
And using commands in bootloader worked before.
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
AndroHero said:
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
Click to expand...
Click to collapse
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
primpower said:
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
Click to expand...
Click to collapse
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
AndroHero said:
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
Click to expand...
Click to collapse
I was using Leedroid, i f**** up and installed multiple .zip at once.... first "leedroidRom.zip" and then "theme" without rebooting between.
After that it stopped working ( I think )
I then wiped everything and installed Android Revolution 2.0.12..
"Terminal"
# Reboot
not permited!
About the question i asked earlier. So its not possible to use adb commands trough fastboot. only fastboot commands.
so i have to use : "fastboot flash" and "fastboot push" to execute commands ?
you cannot use the push command while in fastboot for the same reason you cannot use ADB commands, because at that moment android is not booted, you can use adb commands from recovery though
here are the fastboot commands i know of:
fastboot devices - fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - Dont think this works with the DHD
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Connect your KF to you computer and open a terminal.
Navigate to your platform-tools folder
cd Path to platform-tools
Once here check to see your KF is recognized by ADB
sudo ADB devices
Click to expand...
Click to collapse
*Note you may have to use the command Sudo ./adb devices, it really depends on how you have your SDK setup.
If you see a series of numbers it verifies your KF is being seen by ADB. Next you'll type
sudo ADB shell or sudo ./adb shell
Click to expand...
Click to collapse
Then ask for root permission
SU
Click to expand...
Click to collapse
Next you'll need to set your bootmode to fastboot
idme bootmode 4002
Click to expand...
Click to collapse
It will tell you that <idme> write 4002 to offset 0x1000. Now you'll need to exit the shell
Exit
Click to expand...
Click to collapse
Exit
Click to expand...
Click to collapse
Once you're back in your platform-tools folder restart adb
Sudo adb reboot or sudo ./adb reboot
Click to expand...
Click to collapse
ADB will restart then you can issue the fastboot command
sudo fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img or sudo ./fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img
Click to expand...
Click to collapse
If memory serves me correctly, the device will reboot to TWRP and saying its installed. It will reboot itself. Once rebooted you'll be shown a yellow triangle with a fire on it. Don't panic as its a modified bootloader that allows you to access your recovery. It boots here because your device is still set to boot into the bootloader. To fix this type
sudo fastboot oem idme bootmode 4000 or sudo ./fastboot oem idme bootmode 4000
Click to expand...
Click to collapse
Then simply give fastboot the command to reboot
sudo fastboot reboot or sudo ./fastboot reboot
Click to expand...
Click to collapse
Your device will reboot to the bootloader again, except this time it only stays like that for a short period in order for you to access your recovery if need be. To access TWRP simply hold your power button down for around 2 seconds. Your power button will change to an orange color, release the button and TWRP will show up. If you do nothing at the bootloader your rom of choice will continue to boot.
Click to expand...
Click to collapse
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
czucker said:
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
Click to expand...
Click to collapse
If you are trying to install TWRP version 2.1.x then those steps will not get TWRP installed onto your recovery partition. "fastboot boot" just loads the image into memory and boots from there. You'll need to "fastboot flash" the image to actually get it on to the recovery partition.
Just to clarify a possible source of confusion... version 2.0.0 was distributed as a boot image wrapped around the recovery image. So, the instructions were to "fastboot boot" the boot image and then it would run an internal script that would flash the recovery image contained within the boot image. Now, version 2.1.x is just a recovery image, so you'll need to flash it manually.
Code:
fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img
Thank you.
That worked perfectly.
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.
When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?
deathknight842 said:
When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?
Click to expand...
Click to collapse
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.
GizmoTheGreen said:
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.
Click to expand...
Click to collapse
Thanks. that did it.
I did the same but i got an purple screen and I can not read the text because if aligned to the left :S
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.