2016 Fire HD 8 (6th Gen) ADB, Fastboot & Recovery - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

Spent all day trying different root techniques. Unable to root but along the way got into fastboot and recovery.
ADB
Drivers:
https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
FASTBOOT
use the adb command
adb reboot bootloader
and the tablet will reboot into fastboot mode
RECOVERY (Factory)
use the adb command
adb reboot recovery
and the tablet will reboot into stock recovery mode

Yeah, that's exactly as far as I could get. Tried to boot from a couple of boot and recovery images, but no luck, the device is so locked, it does not even try to boot.

you can't oem unlock in fastboot?

PizzaG said:
you can't oem unlock in fastboot?
Click to expand...
Click to collapse
If only it was that simple!

There is root available for these tablets at least. Relesed recently

Related

[Q] ADB sideload & fastboot not working

Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?

Flashed the wrong recovery

I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?
codfreak said:
I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?
Click to expand...
Click to collapse
Install the ADB drivers on your PC, and then use the command prompt to boot into recovery : adb reboot recovery
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
What? I can't boot into recovery mode because I flashed a recovery for the Nexus 7. And I can't use ADB because I can't boot into Android either.
Use WugFresh Nexus Root Toolkit. It's worked for me on tablets that could not get past the bootloader on their own.
http://www.wugfresh.com/nrt/
1) Press power + volup + voldown and enter bootloader
2) Flash recovery with command:
fastboot flash recovery recovery.img
done

Ascend XT H1611 – Bricked

Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
sri1225 said:
Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
Click to expand...
Click to collapse
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
clsA said:
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
Click to expand...
Click to collapse
divineBliss said:
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
Click to expand...
Click to collapse
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
sri1225 said:
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
Click to expand...
Click to collapse
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Fwiw, the 'boot' command only boots twrp, it doesn't flash it. Thats useful for testing that twrp works. The proper command to flash is immediately above this post. Take it from me - always test first. If it boots, it works.
clsA said:
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Click to expand...
Click to collapse
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
sri1225 said:
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
Click to expand...
Click to collapse
Try the command 'fastboot devices', what does it output..? Are you sure you are in fastboot mode, with the screen and the Android with its chest popped open..?

I lost TWRP and deleted OS on my K20 pro and now when I boot it just enters into Fastboot Mode. Is there any way at all to fix it?

Hello, I really need someone to help me out.
I wanted to flash Pixel Experience on my Redmi K20 Pro so I unlocked the Bootloader and flashed TWRP using ADB tools.
Later I cleared the internal storage by mistake using TWRP without knowing that it would clear my OS too.
But once I cleared my internal storage, even TWRP was missing.
Now I don't have an OS and TWRP.
Every time I reboot, I enter into Fastboot mode. When I use the command "fastboot devices" it lists my device.
And when I flash TWRP, it gives me a Positive response but when I use Power + Vol Up, it just restarts and enters Fastboot mode.
I really want this to be fixed. If there's any way please help me out guys.
Download your device fastboot rom and install with mi flash tool
Download TWRP from here: https://twrp.me/xiaomi/xiaomimi9t.html
Then use the following commands:
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot twrp.img
Now TWRP should be flashed and you can try to flash PE again.
Audiowaste said:
Download TWRP from here: https://twrp.me/xiaomi/xiaomimi9t.html
Then use the following commands:
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot twrp.img
Now TWRP should be flashed and you can try to flash PE again.
Click to expand...
Click to collapse
He has 9t pro...
I see, this topic was opened in the forum for the 9T.

flashing oneplus one

howto flash the one without working volume controls??
is this possible?
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
thanks for the reply. is there any manual to do so?
for im´m an absolute newbie on this. adb and faastboot are installed on my ubuntu machine.
Depends on what you are trying to accomplish.
Flash TWRP recovery? You may also use LineageOS recovery instead of TWRP if you want. Follow their instructions https://twrp.me/oneplus/oneplusone.html
Flash LineageOS? Follow the wiki instructions https://wiki.lineageos.org/devices/bacon/install
Beware that unlocking the bootloader will erase all data on the phone.
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
yes i tried but failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point iḿ in fastboot mode and adb reboot recovery won work?!
yes i tried but i failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point i'm in fastboot mode and adb reboot recovery won't work?!
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
kekerosberg said:
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
Click to expand...
Click to collapse
doesn't work on my ubuntu machine. "unkown rebbot target recvery..
i tried .guess i check it on my win machine.
You can also reboot to recovery from within the OS by using "adb reboot recovery". It should work if you were able to reboot to fastboot using this method.
unfortunately it does not work while being in fastboot mode.
adb says device 'null'not found..
Yes, you are supposed to use adb from whatever OS you have installed, CM, CyanogenOS, LOS, ...
but?
is flashing possible without being in fastboot mode? just using adb?
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
yes i think that's it and therefore i had to reboot to recovery without working controls..
koeskemc said:
yes i think that's it and therefore i had to reboot to recovery without working controls..
Click to expand...
Click to collapse
any idea?
kekerosberg said:
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
Click to expand...
Click to collapse
yes, and that's my prob how to boot into recovery without using any controls?
or is there another way?e.g adb sideload??
You have a working operating system installed? Cyanogenmod, LineageOS or something similar?
Use the power button to boot into the operating system. Then connect the phone to your PC and "adb reboot recovery".
hello again.
i got a new prob. i've istalled twrp(don know how!)
with terp i imstalled lineage 18.1...zip.
but after booting i alwasy get twrp and not the os.
whats my fault
or do ihavr to istall the .img file??instead of.zip?
hello again,
everything's fine so far. i got lineage os on boot up! but how to get back to twrp again to install gapps??

Categories

Resources