Develop Bugs

[Q] stuck at "teamwin" logo - twrp does not start - HELP!

hi
first of all iam from germany so my english is not that good.
i got a kindle fire a week ago from a friend. it was not rooted but in a bootloop.
somehow i managed to install twrp via the kf utility. unfortunally it was version 2.1.1.1 so i was not able to install a other rom via sideload.
i also tried the soupkit.
the last idea was that i just copy the zip file onto the device. it stuck in the middle an after 20 minutes i decided to abort.
now the kf just stuck at the "teamwin" logo right before entering the twrp interface.
i tried to reinstall twrp but that didnt worked. i also tired the unbrick tool with no result.
i have a factory cable too.
if you guys have any ideas please let me know!
thanks

nobody really...?

Just speculation. If this had the kindle software on it, then my guess is it tried to update to the 6.3.3 version, which is currently a real problem. Go to this thread and follow the instructions:
http://forum.xda-developers.com/showthread.php?t=2790183
Once you are rooted, please install a different wonderful rom, like kitkat, so that Amazon does not dump on you again!

redassmonkey said:
hi
first of all iam from germany so my english is not that good.
i got a kindle fire a week ago from a friend. it was not rooted but in a bootloop.
somehow i managed to install twrp via the kf utility. unfortunally it was version 2.1.1.1 so i was not able to install a other rom via sideload.
i also tried the soupkit.
the last idea was that i just copy the zip file onto the device. it stuck in the middle an after 20 minutes i decided to abort.
now the kf just stuck at the "teamwin" logo right before entering the twrp interface.
i tried to reinstall twrp but that didnt worked. i also tired the unbrick tool with no result.
i have a factory cable too.
if you guys have any ideas please let me know!
thanks
Click to expand...
Click to collapse
what bootloader is installed, do you see a press power for bootmenu?
likely need adb/fastboot.exe files from KFU, download a twrp.img from http://techerrata.com/browse/twrp2/blaze,
latest is openrecovery-twrp-2.7.1.0-otter.img
verify md5 check sum
move adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe)
and twrp.img to same folder like c:adb
connect fastboot cable to kindle powered off, connect to pc, power on kindle
if you have non stock bootloader use
open command prompt
cd\adb
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot reboot
if you have stock bootloader you also need FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
---------- Post added at 11:39 AM ---------- Previous post was at 10:51 AM ----------
sorry wrong twrp file use openrecovery-twrp-2.7.1.0-otter.img

Ixthusdan said:
Just speculation. If this had the kindle software on it, then my guess is it tried to update to the 6.3.3 version, which is currently a real problem. Go to this thread and follow the instructions:
http://forum.xda-developers.com/showthread.php?t=2790183
Once you are rooted, please install a different wonderful rom, like kitkat, so that Amazon does not dump on you again!
Click to expand...
Click to collapse
step 2 says - "Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)"
i cant put anything on my storage because twrp is not starting. because of that i cant use my storage. (no rom installed...)

redassmonkey said:
step 2 says - "Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)"
i cant put anything on my storage because twrp is not starting. because of that i cant use my storage. (no rom installed...)
Click to expand...
Click to collapse
correct use my instructions to reflash twrp

sd_shadow said:
correct use my instructions to reflash twrp
Click to expand...
Click to collapse
i did. at first everything looks good.
after rebooting the screen stayed black (green power light was on) and windwos played the "connected - disconnected" sounds for a while.
when i tryed to reset the kf (20sec power button) and turned it back on the problem was the same... is there any way to completley erase the kf without twrp? and if yes can i use ur methode to install twrp and flash a rom?

redassmonkey said:
i did. at first everything looks good.
after rebooting the screen stayed black (green power light was on) and windwos played the "connected - disconnected" sounds for a while.
when i tryed to reset the kf (20sec power button) and turned it back on the problem was the same... is there any way to completley erase the kf without twrp? and if yes can i use ur methode to install twrp and flash a rom?
Click to expand...
Click to collapse
did command promt show sending and writing details?
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
should have looked like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
redassmonkey said:
is there any way to completley erase the kf without twrp?
Click to expand...
Click to collapse
no, you need twrp

Yes it looked exactly like this...

could be bootloader is partially toast
try reflashing it like you did twrp
download FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot

sd_shadow said:
could be bootloader is partially toast
try reflashing it like you did twrp
download FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot
Click to expand...
Click to collapse
same... how ****ed am i...?

redassmonkey said:
same... how ****ed am i...?
Click to expand...
Click to collapse
you are pressing power to open bootmenu, selecting , recovery and releasing power button? does it say v1.5? did it before?

sd_shadow said:
you are pressing power to open bootmenu, selecting , recovery and releasing power button? does it say v1.5? did it before?
Click to expand...
Click to collapse
yes and yes.....

redassmonkey said:
yes and yes.....
Click to expand...
Click to collapse
try booting to fastboot mode with
.
fastboot reboot-bootloader
.
if that works
.
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot

sd_shadow said:
try booting to fastboot mode with
.
fastboot reboot-bootloader
.
if that works
.
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot
Click to expand...
Click to collapse
"fastboot reboot-bootloader" worked but after that the fk tryed to boot in recovery again and it stocked at the "teamwin" logo... problem is that at this point no comunication between pc and kf is impossible... adb just says "waiting for device"..
i double checked my version of twrp... it says now V1.4a
i have to go now but i will check your answer tomorrow...
thanks for your help so far! :good:

Don't know could be hardware failure.
Could try Cannibal Open Touch v2.1 recovery (COTR)
cotr.img
fastboot flash recovery cotr.img

sd_shadow said:
Don't know could be hardware failure.
Could try Cannibal Open Touch v2.1 recovery (COTR)
cotr.img
fastboot flash recovery cotr.img
Click to expand...
Click to collapse
that does not work either...
i told you that abter typing "fastboot reboot" the kf screen stayed black and connected - disconnected the whole time. its the same issue like in thuis thread : http://forum.xda-developers.com/showthread.php?t=1413358
the only diffrence is that my kf loads the bootloader again after reseting it. does that help?

kindle is showing as Omap4430 usb device ?

sd_shadow said:
kindle is showing as Omap4430 usb device ?
Click to expand...
Click to collapse
after rebooting yes.

nobody any ideas? iam kind of depressed...

[Q] Help! Help! :(

Hello
I don't know what happend. I am triying to install cm-4.4-20140212-cmb4.4.2-otter on my Kindle Fire first generatión, and now I only saw this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kindle fire utility said Offline
Windows vista stops detecting my device too!
Please help!

While pictures are lovely, could you explain what you were doing to install the rom? The steps you took can help others give you directions.

3349
Ixthusdan said:
While pictures are lovely, could you explain what you were doing to install the rom? The steps you took can help others give you directions.
Click to expand...
Click to collapse
On TWRP install otterx-u-boot_v2.05, then the tablet....RIP

the picture is showing otterx-u-boot_v2.05
the pc will see it differently than before
on that screen did you select recovery?

sd_shadow said:
the picture is showing otterx-u-boot_v2.05
the pc will see it differently than before
on that screen did you select recovery?
Click to expand...
Click to collapse
When I selected recovery the Kindle turns off
Can select only advance

Lepori said:
When I selected recovery the Kindle turns off
Can select only advance
Click to expand...
Click to collapse
the rom you are installing is for stock partitions, the bootloader you have is for OtterX partition roms
did you use advanced options to change partitions? if so you need a different rom or change back to stock kindle partitions
recovery may be toast
in device manager, do you see an android phone, if so drivers should be good

sd_shadow said:
the rom you are installing is for stock partitions, the bootloader you have is for OtterX partition roms
did you use advanced options to change partitions? if so you need a different rom or change back to stock kindle partitions
recovery may be toast
in device manager, do you see an android phone, if so drivers should be good
Click to expand...
Click to collapse
I can change partition from Amazon to OtterX. Advance menu has Trigger USBboot mode and EMMC corruption fix options.
Device manager detects Kindle ! but the old drivers I have didnt work.

Lepori said:
I can change partition from Amazon to OtterX.
Click to expand...
Click to collapse
ok so you need to decide if you are sticking with OtterX or reverting back to Kindle partitions
Advance menu has Trigger USBboot mode and EMMC corruption fix options.
Device manager detects Kindle ! but the old drivers I have didnt work.
Click to expand...
Click to collapse
it still maybe ok
test with fastboot.exe
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe from kindle fire utility/tools
to a folder like c:adb
open command prompt
enter commands
cd\adb
fastboot reboot-bootloader
if it reboots to fastboot mode drivers are fine for now

sd_shadow said:
ok so you need to decide if you are sticking with OtterX or reverting back to Kindle partitions
it still maybe ok
test with fastboot.exe
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe from kindle fire utility/tools
to a folder like c:adb
open command prompt
enter commands
cd\adb
fastboot reboot-bootloader
if it reboots to fastboot mode drivers are fine for now
Click to expand...
Click to collapse
Want to go ahead with OtterX and Android Kit Kat
Device Manager detects Kindle, but cant install drivers, need another drivers? then kindle turns off
Fastboot reboot-bootloader.....waiting for device

Lepori said:
Want to go ahead with OtterX and Android Kit Kat
Device Manager detects Kindle, but cant install drivers, need another drivers? then kindle turns off
Fastboot reboot-bootloader.....waiting for device
Click to expand...
Click to collapse
hello?

download a otterx twrp.img like otterx-twrp-2.7.0.1-recovery-f2fs.img
verify md5 checksum https://sites.google.com/site/sdshadowscollection/home/hash-checksums
.
copy otterx-twrp-2.7.0.1-recovery-f2fs.img to adb folder
when you see the bootloader screen (like your posted pic)
press the power button once to open bootmenu, that will give you a couple of minutes before it continues boot to rom
then try the
fastboot reboot-bootloader
kindle show reboot to fastboot screen
then
fastboot flash recovery otterx-twrp-2.7.0.1-recovery-f2fs.img
fastboot reboot
if that works download a compatible OtterX rom
and follow directions on how to push rom and gapps to twrp

sd_shadow said:
download a otterx twrp.img like otterx-twrp-2.7.0.1-recovery-f2fs.img
verify md5 checksum https://sites.google.com/site/sdshadowscollection/home/hash-checksums
.
copy otterx-twrp-2.7.0.1-recovery-f2fs.img to adb folder
when you see the bootloader screen (like your posted pic)
press the power button once to open bootmenu, that will give you a couple of minutes before it continues boot to rom
then try the
fastboot reboot-bootloader
kindle show reboot to fastboot screen
then
fastboot flash recovery otterx-twrp-2.7.0.1-recovery-f2fs.img
fastboot reboot
if that works download a compatible OtterX rom
and follow directions on how to push rom and gapps to twrp
Click to expand...
Click to collapse
didn't work Fastboot reboot-booloader.....<waiting for device>..and nothing happen. Then KF turns off

how is it listed in device manager?

sd_shadow said:
how is it listed in device manager?
Click to expand...
Click to collapse
listed as Kindle with a "!" , but no ABD adapter detected. This is for only a few minutes because the KF turns off.

Lepori said:
listed as Kindle with a "!" , but no ABD adapter detected. This is for only a few minutes because the KF turns off.
Click to expand...
Click to collapse
You have tried,
in device manager, right click on kindle fire> select properties>Driver Tab>uninstall>check remove driver
then open KFU folder, run install_drivers.bat
when it's done, reboot pc

sd_shadow said:
You have tried,
in device manager, right click on kindle fire> select properties>Driver Tab>uninstall>check remove driver
then open KFU folder, run install_drivers.bat
when it's done, reboot pc
Click to expand...
Click to collapse
mm....... nothing hapends.......next advice...try a Saw and Hammer...lol

you mean it reinstall wrong driver.
using a pc with windows vista right?
could try using [HOW-TO] Amazon Kindle Fire Signed Driver for WinXP/Vista/7/8/8.1

sd_shadow said:
you mean it reinstall wrong driver.
using a pc with windows vista right?
could try using [HOW-TO] Amazon Kindle Fire Signed Driver for WinXP/Vista/7/8/8.1
Click to expand...
Click to collapse
mmm..............nop.....didnt work

I would try using a different pc, install drivers first.
Other than that don't know.
Sent from my XT894 using Tapatalk

[Q] Bricked (Stuck) Kindle Fire 6.3.2

My Kindle Fire is 6.3.2.
I tried to root it using KFU. I went to install_drivers.bat, and it says "google, inc- Winusb failed." For some stupid reason, i chose to ignore that and went on to root through the KFU and "Install permanent root with superuser" and now it says
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU
Installing FFF...
<waiting for device>
So I am now stuck on a permanent logo screen (Black and orange), with no animation. I can turn it off and on.
Pretty much everything I try to do ends with "waiting for device."
I believe it has something to do with missing drivers, although I am not entirely sure on any of this at this point.

Windows 7 or 8?
Sent from my XT862 using Tapatalk

Maybe try the unbrick utility.
I'm having some issues with the KFU myself, after installing the drivers Windows device manager no longer sees the Kindle when it's stock booted. I can mount from TWRP but it appears under Portable devices as E:/ , not Kindle. Root and installation of google apps did not take, though it ran to completion and said all done. KFU hangs when it tries to activated Fastboot (4002) so many of the other options of KFU wont run.

Arkasai said:
Maybe try the unbrick utility.
I'm having some issues with the KFU myself, after installing the drivers Windows device manager no longer sees the Kindle when it's stock booted. I can mount from TWRP but it appears under Portable devices as E:/ , not Kindle. Root and installation of google apps did not take, though it ran to completion and said all done. KFU hangs when it tries to activated Fastboot (4002) so many of the other options of KFU wont run.
Click to expand...
Click to collapse
If drivers are installed correctly Kindle Fire should be seen as Android Phone>adb interface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------

sd_shadow said:
Windows 7 or 8?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Windows 8.1, sorry. I've already disabled driver signature reinforcement.

Itzel_55 said:
Windows 8.1, sorry. I've already disabled driver signature reinforcement.
Click to expand...
Click to collapse
is kindle listed like in screenshots in my last post?

sd_shadow said:
is kindle listed like in screenshots in my last post?
Click to expand...
Click to collapse
Ok, this is new...
It says:
Kindle Fire
-Kindle Orange Fastboot Mode | Gen 1

Itzel_55 said:
Ok, this is new...
It says:
Kindle Fire
-Kindle Orange Fastboot Mode | Gen 1
Click to expand...
Click to collapse
have you tried the install TWRP option in KFU?
may have to restart the Kindle a couple of times

sd_shadow said:
have you tried the install TWRP option in KFU?
may have to restart the Kindle a couple of times
Click to expand...
Click to collapse
Note: Now the Kindle is not being recognized when plugged in via USB. not sure why, no conditions have changed.
Tried to install TWRP via KFU. Says that...
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
<waiting for device >
I have already tried the options on the KF Unbricking Utility.

Itzel_55 said:
Note: Now the Kindle is not being recognized when plugged in via USB. not sure why, no conditions have changed.
Tried to install TWRP via KFU. Says that...
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
<waiting for device >
I have already tried the options on the KF Unbricking Utility.
Click to expand...
Click to collapse
could be low battery, power off, then try charging with wall charger
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
or maybe time for SoupKit

sd_shadow said:
could be low battery, power off, then try charging with wall charger
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
or maybe time for SoupKit
Click to expand...
Click to collapse
Ok, I wasn't running KFU through administrator. Smoooooth...
The Kindle is now recognized when plugged in through USB, still says
Kindle
-Kindle Orange Fastboot Mode | Gen 1
KFU says ADB Status: Online, Boot Status: Unknown
I tried installing TWRP through KFU and now it says
Setting normal bootmode
Please wait....
The system cannot find the path specified
The system cannot find the path specified
*******************************************************
* All Done! *
*******************************************************
Thats all folks, TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue....
So obviously, I tried rebooting again, and again, and still the same logo screen, no animation.
Note: In the device manager driver details, my kindles drivers are the same as the screenshot posted earlier.

Ok, just switched to a Windows 7 PC. I just successfully installed the drivers using the install_drivers.bat in the KFU.
In the Device Manager, it's now showing up as..
Android Phone
Android ADB Interface
The Kindle still shows as the white and orange splash screen, with no animation.

try my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
just don't need the fastboot cable if already in fastboot mode

sd_shadow said:
try my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
just don't need the fastboot cable if already in fastboot mode
Click to expand...
Click to collapse
THANK YOU!
I followed the video, and now I am at the point that the video left on.
So obviously I'm trying to install a ROM (Jellybean/ Cyanamogen). From this point, how would I go about doing that?
I just really don't want to screw this up again.

Itzel_55 said:
THANK YOU!
I followed the video, and now I am at the point that the video left on.
So obviously I'm trying to install a ROM (Jellybean/ Cyanamogen). From this point, how would I go about doing that?
I just really don't want to screw this up again.
Click to expand...
Click to collapse
Some more here http://forum.xda-developers.com/showthread.php?t=2828056
[How To][Videos] For Kindle Fire 1 [2014]
Sent from my XT894 using Tapatalk

sd_shadow said:
Some more here http://forum.xda-developers.com/showthread.php?t=2828056
[How To][Videos] For Kindle Fire 1 [2014]
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Once again, thanks for the help.
I am now happily running cyanogen.

Itzel_55 said:
Once again, thanks for the help.
I am now happily running cyanogen.
Click to expand...
Click to collapse
Ok, now I have another problem, with a completely different Kindle (6.3.2)
I've installed FFF and TWRP, and I'm trying to install Jellybean 4.2.2 on it through TWRP.
When I'm trying to move the ROM and GAPPS zips to the G: folder, it won't show up, even though the kindle is recognized as..
Android Phone
Android ADB Composite Interface
I'm almost positive this is because the Kindle has a passcode on it, which i forgot to remove before this whole process. This wouldn't be a huge deal, as a factory reset through TWRP would erase the pass code anyways. However, after I do the factory reset successfully, and then go to reboot-system, it will go back to the blue/white logo, then go to the white/orange unanimated logo, which it gets stuck at.
If there was a way to get the files onto the SD without going through the conventional way, it wouldn't be an issue, but i don't know of way to

In twrp wipe/advanced/SD card swipe to wipe
Or
Use adb
adb push filename /sdcard
Sent from my XT894 using Tapatalk

sd_shadow said:
In twrp wipe/advanced/SD card swipe to wipe
Or
Use adb
adb push filename /sdcard
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Tried the first one, didn't work.
What do you mean by the second one?

Itzel_55 said:
Tried the first one, didn't work.
Click to expand...
Click to collapse
what does that mean? error(s)?
What do you mean by the second one?
Click to expand...
Click to collapse
You used fastboot.exe to flash twrp and bootloader, right?
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
so you have adb.exe that came with it, use adb.exe to push rom and gapps to sd card
place rom and gapps files in c:adb folder use exact file names
Code:
adb push romname.zip /sdcard
adb push gappsname.zip /sdcard
like I did in my [YouTube] OtterX ROM/TWRP/Bootloader [2014-05-08] @12:20

[HELP] Did I just brick my Kindle? Wiped system and data and now nothing will install

So I was rooted and decided I wanted to go back to stock. Foolishly before doing anything I wiped my SDcard, deleting my TWRP backup. I went in to TWRP and wiped DATA and SYSTEM. Now I can not get my Kindle to boot. It just sits at the booting screen. I have tried to install several ROMs but nothing works. They all fail to install. I changed my build.prop to read as a Nexus 7 so that may be the issue but I can't find the build.prop file to edit it back. It's not in /system. KFU didn't help and I cant get the Unbrick tool to even run on my laptop (Windows 10). Any help would be greatly appreciated!

CannibalAngel said:
So I was rooted and decided I wanted to go back to stock. Foolishly before doing anything I wiped my SDcard, deleting my TWRP backup. I went in to TWRP and wiped DATA and SYSTEM. Now I can not get my Kindle to boot. It just sits at the booting screen. I have tried to install several ROMs but nothing works. They all fail to install. I changed my build.prop to read as a Nexus 7 so that may be the issue but I can't find the build.prop file to edit it back. It's not in /system. KFU didn't help and I cant get the Unbrick tool to even run on my laptop (Windows 10). Any help would be greatly appreciated!
Click to expand...
Click to collapse
see Fastboot cable in
Fire Index: Which Amazon (Kindle) Fire Do I have?
---------- Post added at 03:18 AM ---------- Previous post was at 03:17 AM ----------
build.prop has nothing to do with drivers

sd_shadow said:
see Fastboot cable in
Fire Index: Which Amazon (Kindle) Fire Do I have?
---------- Post added at 03:18 AM ---------- Previous post was at 03:17 AM ----------
build.prop has nothing to do with drivers
Click to expand...
Click to collapse
I'm not sure what you are trying to tell me here. I can see the Kindle in ADB. I can run ABD commands against the kindle. This is not an ADB or Driver issue. The issue is that I wiped the system and data partitions and now the Kindle has no OS and I can not get a new one installed.

CannibalAngel said:
I'm not sure what you are trying to tell me here. I can see the Kindle in ADB. I can run ABD commands against the kindle. This is not an ADB or Driver issue. The issue is that I wiped the system and data partitions and now the Kindle has no OS and I can not get a new one installed.
Click to expand...
Click to collapse
if you wiped /system
adb commands are not going to fix it
flash FFF and Twrp with fastboot

sd_shadow said:
if you wiped /system
adb commands are not going to fix it
flash FFF and Twrp with fastboot
Click to expand...
Click to collapse
Ahh okay. Thanks! I'll try that when I get home tonight then.
EDIT: Thought I could get FFF installed via KFU. I could not. Guess I'll have to order a fastboot cable to fix it

sd_shadow said:
if you wiped /system
adb commands are not going to fix it
flash FFF and Twrp with fastboot
Click to expand...
Click to collapse
Finally got around to getting a fastboot cable. Now, how do I fix the Kindle? I'm not sure that it is going into fastboot mode. It just sits on a screen with the white and blue Kindle Fire logo and says "Booting..." at the bottom of the screen.

CannibalAngel said:
Finally got around to getting a fastboot cable. Now, how do I fix the Kindle? I'm not sure that it is going into fastboot mode. It just sits on a screen with the white and blue Kindle Fire logo and says "Booting..." at the bottom of the screen.
Click to expand...
Click to collapse
with Fire powered off,
cable not connected to the computer
connect the Fastboot cable to the Fire
then connect cable to the computer
Sent from my XT1254 using Tapatalk

sd_shadow said:
with Fire powered off,
cable not connected to the computer
connect the Fastboot cable to the Fire
then connect cable to the computer
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Still not working. As soon as I plug the cable into the powered off Kindle, the Kindle turns on. I then plug the USB into the PC. It sits at that same screen.
I run adb devices and it sees it just fine. I run "fastboot -i 0x1949 getvar product" and is says "Waiting for device". I run "fastboot -i 0x1949 devices" and it returns a blank line. It may be a driver issue. I tried installing drivers from KFU but it fails every time. Any idea where I can get the drivers? I'm on Windows 10.

CannibalAngel said:
Still not working. As soon as I plug the cable into the powered off Kindle, the Kindle turns on. I then plug the USB into the PC. It sits at that same screen.
I run adb devices and it sees it just fine. I run "fastboot -i 0x1949 getvar product" and is says "Waiting for device". I run "fastboot -i 0x1949 devices" and it returns a blank line. It may be a driver issue. I tried installing drivers from KFU but it fails every time. Any idea where I can get the drivers? I'm on Windows 10.
Click to expand...
Click to collapse
driver signature enforcement needs to be turned off, to install drivers from KFU
if adb commands work, fastboot commands will not, and visa versa
they are mutually exclusive
Could try running fastboot command before plugging fastboot cable in

sd_shadow said:
driver signature enforcement needs to be turned off, to install drivers from KFU
if adb commands work, fastboot commands will not, and visa versa
they are mutually exclusive
Could try running fastboot command before plugging fastboot cable in
Click to expand...
Click to collapse
YAY! I got it recognized in fastboot. Now, can you point me to a guide on how to install fff and TWRP with fastboot?

CannibalAngel said:
YAY! I got it recognized in fastboot. Now, can you point me to a guide on how to install fff and TWRP with fastboot?
Click to expand...
Click to collapse
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2

sd_shadow said:
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Click to expand...
Click to collapse
Thanks! It seems that I got fff and TWRP installed just fine. However, when trying to install a ROM I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk

CannibalAngel said:
Thanks! It seems that I got fff and TWRP installed just fine. However, when trying to install a ROM I get this:
Click to expand...
Click to collapse
which Rom
which twrp?

sd_shadow said:
which Rom
which twrp?
Click to expand...
Click to collapse
TWRP 2.8.5.0
Stock Kindle ROM from Amazon
Sent from my LG-H901 using Tapatalk

CannibalAngel said:
TWRP 2.8.5.0
Stock Kindle ROM from Amazon
Click to expand...
Click to collapse
stock rom will only install with twrp 2.2.2.1 or lower

sd_shadow said:
stock rom will only install with twrp 2.2.2.1 or lower
Click to expand...
Click to collapse
Thanks for all of your help! I installed TWRP 2.2.2.0 and it worked perfectly.

Help how to REFLASH Google pixel 3 XL stock firmware

Hello,
My friend tried to root my phone and now its in bootloop. I downloaded files from pixel website and its not working, its giving errors. please see screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me

You need to try the crosshatch-pq1a.181205.006-factory-96b23504.zip

Your sdk platform tools are not up to date. Without the latest you'll get the errors you're getting. The latest is r28
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Your sdk platform tools are not up to date. Without the latest you'll get the errors you're getting. The latest is r28
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks so much, it worked.

jd1639 said:
Your sdk platform tools are not up to date. Without the latest you'll get the errors you're getting. The latest is r28
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have the same issue but my platform tools are up to date

cdakaharpo said:
I have the same issue but my platform tools are up to date
Click to expand...
Click to collapse
well at that point at the very least you should be able to get back into Android recovery and sideload the OTA
GL!

cdakaharpo said:
I have the same issue but my platform tools are up to date
Click to expand...
Click to collapse
Which specific issue? If it fails to flash where does it fail and are there any errors it reports?

cmh714 said:
well at that point at the very least you should be able to get back into Android recovery and sideload the OTA
GL!
Click to expand...
Click to collapse
It won't recognize adb device now :/ but it will recognize fast boot but idk if you can sideload in recovery using fast boot
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
jd1639 said:
Which specific issue? If it fails to flash where does it fail and are there any errors it reports?
Click to expand...
Click to collapse
This is the new error I'm getting now when I run flash-all "failed to load <file name> : not enough space
---------- Post added at 07:34 PM ---------- Previous post was at 07:05 PM ----------
I just tried again with a different factory image flash-all and it says "command failed (error reading sparse file)

cdakaharpo said:
It won't recognize adb device now :/ but it will recognize fast boot but idk if you can sideload in recovery using fast boot
No, you need to go to recovery, select sideload with adb and then you can use adb commands to send the ota
Click to expand...
Click to collapse

cdakaharpo said:
It won't recognize adb device now :/ but it will recognize fast boot but idk if you can sideload in recovery using fast boot
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
This is the new error I'm getting now when I run flash-all "failed to load <file name> : not enough space
---------- Post added at 07:34 PM ---------- Previous post was at 07:05 PM ----------
I just tried again with a different factory image flash-all and it says "command failed (error reading sparse file)
Click to expand...
Click to collapse
First, "adb devices" only works if you're booted into the system or recovery. If you're booted into the bootloader you need to use fastboot commands, "fastboot devices".
You need to be booted into the stock recovery to sideload an ota. But if you're booted into the bootloader can't you use the volume keys to get to recovery?
Finally, do you have the latest sdk platform tools? r28.0.2 is the latest and if you don't have an r28 version you'll get errors flashing.

jd1639 said:
First, "adb devices" only works if you're booted into the system or recovery. If you're booted into the bootloader you need to use fastboot commands, "fastboot devices".
You need to be booted into the stock recovery to sideload an ota. But if you're booted into the bootloader can't you use the volume keys to get to recovery?
Finally, do you have the latest sdk platform tools? r28.0.2 is the latest and if you don't have an r28 version you'll get errors flashing.
Click to expand...
Click to collapse
I fixed it back to stock by simply using a different usb port and running flash-all. I know i should have tried that earlier but all i did was try two different chords. I was using type c to the type c port on my laptop. I switched it to the normal usb slot and it worked. Thanks for all the advise guys

cdakaharpo said:
I fixed it back to stock by simply using a different usb port and running flash-all. I know i should have tried that earlier but all i did was try two different chords. I was using type c to the type c port on my laptop. I switched it to the normal usb slot and it worked. Thanks for all the advise guys
Click to expand...
Click to collapse
Glad you got it. I'm not sure if anybody has gotten a c to c to work. I haven't heard of anyone but I've heard a lot from people where it doesn't work.