Develop Bugs

[BOOT] FIREFIREFIRE 1.3 - Replacement bootloader w/ recovery selection

{
"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"
}
FIREFIREFIRE​
FIREFIREFIRE is a replacement bootloader originally created by pokey9000 for the Kindle Fire. While the stock bootloader simply boots into the system, FIREFIREFIRE provides an option to boot into recovery and also enables fastboot for a short period of time. Everyone from developers to users of alternative ROMs will certainly benefit from having FIREFIREFIRE on their device.
FEATURES
Recovery Selection - As the Kindle Fire boots up, the power button LED will change from bright green to a dim green. Once it changes to a dim green, press the power button again and release (repeat a few times to be sure). The LED will then change to an orange color indicating recovery selection and boot into recovery.
Enable Fastboot - As described above, when the power button LED changes to a dim green, the Kindle Fire will enter fastboot mode for approximately 4-5 seconds. During this time, fastboot commands can be issued and the device will remain in fastboot until it is rebooted.
Write Partition Tables - During fastboot, issuing a 'fastboot oem format' command will overwrite the existing partition table with the stock table values.
HOW TO INSTALL
From stock bootloader fastboot
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
From FIREFIREFIRE fastboot
Code:
fastboot flash bootloader u-boot.bin
From gscript - Details in the gscript thread
For a step-by-step guide on how to update FIREFIREFIRE from a previous version using fastboot, see this post by smirkis
RELEASE NOTES
1.3 - MD5: 928ae401d91963e1cb8f4dae6ca9519b
March 11, 2012
Replaced the original FIREFIREFIRE boot logo with a "kindle fire android" logo
Shortened the fastboot delay from ~10 seconds to ~5 seconds
0.9 - 1.2
Original FIREFIREFIRE thread
ADDITIONAL NOTES
I originally just wanted to rebuild the FIREFIREFIRE bootloader to bake in a custom boot logo for my own use. That opened the door enough for me to become interested in making some minor improvements in how it handles recovery selection. When I contacted pokey9000, he encouraged me to work on it and gave me enough confidence to begin studying the code. Although I couldn't begin to estimate a timeframe, I hope to continue working on it and build in some enhancements that would be worthy of eventually calling it version 2.0.
The bootloader is possibly the most underappreciated piece of software on the Kindle Fire. It's not overreaching to say that everything else is built on top of this foundation. Without the work of pokey9000, the XDA Kindle Fire community would not have gotten the other great developments as quickly as it did. When the next great device comes along, we will certainly need the work of talented people like pokey9000 again. If you enjoy using your Kindle Fire as an Android tablet, please consider making a donation to pokey9000.
A special thanks to smirkis for having the guts to be the first in line to flash my build on his device.

props to this gentleman for expanding on pokey9ks work, I love the logo and shortened delay. I love being a test dummy, thanks for the opportunity
ill update my gscript method when I get home!
Sent from my HTC Glacier using xda premium

Very nice; I like the logo and it works exactly as it should (guess this means I can stop trying to understand the uboot source myself for the time being lol)

Is this flashable in TWRP?

AustinFire said:
Is this flashable in TWRP?
Click to expand...
Click to collapse
As noted in this thread, fastboot flash shall be used.
Sent from my Amazon Kindle Fire using Tapatalk

I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
You may use KF utility to boot into fastboot, then use fastboot flash mentioned in the header of this thread, then reboot to normal using KF.
Sent from my Amazon Kindle Fire using Tapatalk

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I saved this from somewhere on XDA, not sure who or what thread:
Code:
Howto flash by hand
1 Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. "adb shell idme bootmode 4002"
2 flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
2b at <waiting for device> press power 30 seconds to power down, then power up
3 disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
4 reboot: "fastboot -i 0x1949 reboot"

it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.

Pkt_Lnt said:
I saved this from somewhere on XDA, not sure who or what thread:
Click to expand...
Click to collapse
b63 said:
it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related
Click to expand...
Click to collapse
Thanks for those crib sheets. I was hoping there was something out there that starts off answering the question, "What is fastboot?" and working up from there. While KFU and other press-this-button utilities do a good job of getting the beginner started, it's like teaching someone how to run without walking first. Then when the user gets into a bind because something went wrong, they have no idea what to do next. The General section seems to be filled with these kinds of problems. A while back, I started writing a general knowledge, FAQ style post, but it seemed too rudimentary once I got into it. When I glance at the General section from time to time, I have second thoughts about having shelved it. Maybe I'll dust it off again.

twa_priv said:
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.
Click to expand...
Click to collapse
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.

kinfauns said:
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.
Click to expand...
Click to collapse
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.

twa_priv said:
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.
Click to expand...
Click to collapse
I understood the part about you using KFU to change the bootmode and the part about you reinstalling drivers. My comment wasn't about either of those things. My point was that there's not a way to reinstall a new FFF from within the KFU menus. You used KFU to change bootmodes, quit out of KFU, then used the fastboot executable to do the actual installation... just as my installation instructions described. Although the fastboot executable is packaged in the tools directory of KFU, it is entirely separate from it. My intent was to clarify this point so that some other reader of this thread in the future doesn't get confused and say, "But he said I could use KFU to install it!"

I just used cmd and fastboot from the adb-sdk (winXP) to install this. Very nice! Great work.

Pkt_Lnt said:
I just used cmd and adb (winXP) to install this. Very nice! Great work.
Click to expand...
Click to collapse
Thanks for the feedback, I'm glad you like it. Did you use dd to write directly to the bootloader partition?
Edit: Nevermind, I see that you changed your post to say fastboot.

if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
first, connect your device to your computer and make sure USB is not mounted
make sure you already downloaded the new fff1.3 and copy it to your sdk folder where fastboot is located
open a cmd prompt if you on windows and cd to the sdk directory where fastboot is located, for me i typed
cd c:/sdk_tools
than go ahead and pre-initiate the fastboot command to install the new fff1.3
fastboot flash bootloader u-boot.bin
you should see a message saying, <waiting for devices>, now go ahead and reboot your kindle.
at startup fastboot is automatically detected and your cmd prompt should say something like
c:\SDK_tools>fastboot flash bootloader kinfauns_u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)... OKAY [ 0.057s]
writing 'bootloader'... OKAY [ 0.188s]
finished. total time: 0.246s
at this point, its still in fastboot. so issue
fastboot reboot
and u should see something like this
c:\SDK_tools>fastboot reboot
rebooting...
finished. total time: 0.002s
no need to change bootmodes, no need to use KFU, nothin.
if your pc has driver issues, avoid fastboot entirely and use my gscript method posted in the OP

smirkis said:
if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
Click to expand...
Click to collapse
Thanks to smirkis for the mini-guide on how to update FFF from a previous version. I've edited the OP to point to his post so others can find it easily.

That is good. Just for info, I used the commands in my post 9 above (note the "take out "-i 0x1949" if FFF is already installed" in step 2) and it works fine.
I used that to install FFF 1.0 and update 1.1, 1.2, and now 1.3 clean and quick.
The really short version is saved now for the next version.

How to restore from this menu

My Mac is not seeing the Kindle device and it is stuck at the FFF yellow triangle.
(update)
Now I have recovery options seen below. What is the best and easiest way to go back stock from here? I have downloaded the kindle fire update from Amazon.
{
"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"
}
So I took the update from amazon, renamed the bin to zip, and put it on the SD card. In recovery I hit update from SD card. Now it is stuck on the OEM kindle fire logo. Is this where I HAVE to have a factory cable?

No, you need to use the mount function in recovery to mount your sdcard. When mounted it will show up as an external drive on your computer. Transfer a new rom and the latest version of firefirefire from your computer to your sdcard. FFF 1.4 now comes in a flashable "Flash.zip" that can be installed in recovery.
Read about the new FFF and how to use it here: http://forum.xda-developers.com/showthread.php?p=25598837
Make ABSOLUTELY SURE that you have done an md5check on FFF before installing in recovery.
Install a new rooted rom in recovery and if you need to, use the new FFF to change your bootmode to normal (fixes stuck at boot logo)
Then, read this guide in it's entirety: http://forum.xda-developers.com/showthread.php?p=23747567

soupmagnet said:
No, you need to use the mount function in recovery to mount your sdcard. When mounted it will show up as an external drive on your computer. Transfer a new rom and the latest version of firefirefire from your computer to your sdcard. FFF 1.4 now comes in a flashable "Flash.zip" that can be installed in recovery.
Read about the new FFF and how to use it here: http://forum.xda-developers.com/showthread.php?p=25598837
Make ABSOLUTELY SURE that you have done an md5check on FFF before installing in recovery.
Install a new rooted rom in recovery and if you need to, use the new FFF to change your bootmode to normal (fixes stuck at boot logo)
Then, read this guide in it's entirety: http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thank you , but how am I going to use recovery if I am stuck at the kindle fire OEM logo after hitting update in recovery as seen under the picture? The only way I can see the kindle is to mount breakdroid and do an ADB check, but it still doesn't mount the SD card.
I've been staring at this for 12 hours.

iphonedownload said:
Thank you , but how am I going to use recovery if I am stuck at the kindle fire OEM logo after hitting update in recovery as seen under the picture? The only way I can see the kindle is to mount breakdroid and do an ADB check, but it still doesn't mount the SD card.
Click to expand...
Click to collapse
Okay it seems as there is a breakdown in communication here, so let's try to figure this out.
The OEM Kindle Fire logo that you see is the bootloader. The bootloader has several bootmodes to boot from. You want it to boot into normal bootmode (4000) but instead you're booting into fastboot (4002). When the new update tried to install itself it saw that you were using a modified system and caused the error. Installing the new FFF will fix your bootmode problem, but you still need a working rom to boot into (preferably a custom rom). If you like the stock rom, MoDaCo is a good alternative until there is enough information about the 6.3.1 update.
If you can't mount your sdcard in recovery you should still be able to boot into recovery and "adb push" a rom.zip and the FFF Flash.zip to your sdcard for flashing in recovery.

soupmagnet said:
If you can't mount your sdcard in recovery you should still be able to boot into recovery and "adb push" a rom.zip and the FFF Flash.zip to your sdcard for flashing in recovery.
Click to expand...
Click to collapse
Thank you very much for the info. This is pretty much where I am stuck as I do not know how to do what you described. Even as long as I have been here I still haven't been bothered with terminal commands on my mac until recently. New world for me. Gotta learn sometime.
I have tried every way possible to "boot in recovery" and nothing is helping. If I can just get it back stock I'll start from scratch, but I'd need a few instructions if you would mind saving my butt here and telling me how to do as you describe. I'm hung at the logo and the mac doesn't see the Kindle SD card so can I get maybe an A, B, C recovery explanation from you this once? I'm sure I'll return the favor one day.
I can't mount the SD, but I do have some power over the Kindle.

With Mac it should be fairly easy (I'll try to make it as easy as possible).
First and foremost, turn off your device while I write up a tutorial so your battery doesn't die and leave you in a worse place than you are now.

soupmagnet said:
With Mac it should be fairly easy (I'll try to make it as easy as possible).
First and foremost, turn off your device while I write up a tutorial so your battery doesn't die and leave you in a worse place than you are now.
Click to expand...
Click to collapse
Thanks a bunch! it's plugged in and fully charged. It was at 75% when everything went bad and it had an orange light, now it has green so I believe it went ahead and charged to 100%.
At the moment this is all I seem to be able to do. Mostly limited to my lack of knowledge of command. (tried it other ways too, just not doing it right)

Find copies of the following files and place them on your desktop.
TWRP 2.1
FireFireFire 1.4 Flash.zip
fastboot
adb
Rename the openrecovery-twrp-blaze-2.1.1.img to twrp.img (just to make it easy) Make sure FireFireFire is named Flash.zip
Open a new terminal window and enter the following commands
Code:
cd desktop
...and because you are already in fastboot mode (4002)...
Code:
fastboot -i 0x1949 flash recovery twrp.img
When you get a prompt that says "waiting for device" turn your Kindle on. You should see that the image was installed.
Now you have to change your bootmode to recovery
Code:
fastboot -i 0x1949 oem idme bootmode 5003
Code:
fastboot reboot
If the device doesn't reboot automatically, hold the power button until it shuts off then restart. The device should boot into recovery.
While in recovery you can only enter adb commands.
Code:
adb push Flash.zip /sdcard
Then use the same command to push whatever custom rom you want installed (not pure stock for now)
...when finished select install, and on the right-hand side of the screen select and install Flash.zip If you dont see the files you pushed to your Kindle, reboot and they should show up. That will install FireFireFire1.4
Use the same steps to install custom rom. Before installing custom roms, make sure you perform a "factory reset" (wipe data), wipe system, wipe cache, and wipe Dalvik cache.
Then reboot
Your Kindle Fire splash screen should now be blue. As soon as you see it for the first time press and hold the power button until it turns orange. There will be options on the bottom. Hold the power button for a second to cycle through the options. You want to change your bootmode to "normal". It will select automatically after a few moments. If the "normal" selection doesn't work try "reset bootmode"
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
iphonedownload said:
Thanks a bunch! it's plugged in and fully charged. It was at 75% when everything went bad and it had an orange light, now it has green so I believe it went ahead and charged to 100%.
At the moment this is all I seem to be able to do. Mostly limited to my lack of knowledge of command. (tried it other ways too, just not doing it right)
Click to expand...
Click to collapse
OMG You're lucky you didn't hard-brick your device with that.

Thank you so much, it's not going past waiting for device.
Open a new terminal window and enter the following commands
Code:
cd desktop
...and because you are already in fastboot mode (4002)...
Code:
fastboot -i 0x1949 flash recovery twrp.img
When you get a prompt that says "waiting for device" turn your Kindle on. You should see that the image was installed
Click to expand...
Click to collapse
Path to desktop
Video:
(the kindle logo is not actually oscillating, just appears that way)
http://www.youtube.com/watch?v=xplRRqUgv78

Keep trying it, sometimes it doesn't work right away. You could try entering the command with the device turned on to see if that works. Keep at it. It will work.
If after a few tries, it still doesn't work, make sure you are actually in fastboot:
fastboot -i 0x1949 oem idme bootmode 4002
[Edit:] ignore
[Edit2:] It's hard to tell from the video but, is the Kindle Fire logo actually flashing? Nevermind, you already answered that.

Thank you, I am actually getting waiting for device on that as well

Okay hold on a second. How were you able to get adb to connect? What happens when you type:
Code:
adb devices
If it returns a string of numbers, then try:
Code:
adb shell idme bootmode 4002
adb reboot
...and that will put you in fastboot so you can enter fastboot commands

soupmagnet said:
Okay hold on a second. How were you able to get adb to connect? What happens when you type:
Code:
adb devices
Click to expand...
Click to collapse
Well I have been booting in Snow Leopard and when I do I get:
When I boot in Lion I get:
soupmagnet said:
If it returns a string of numbers, then try:
Code:
adb shell idme bootmode 4002
adb reboot
...and that will put you in fastboot so you can enter fastboot commands
Click to expand...
Click to collapse
When I do that in Snow Leopard (the only OS I have been using for this) I get the same error any shell command gives me.

That sucks...It looks like you messed up your shell somehow. If that's the case, you need a factory cable before you can go any further.

Well it's ok electronics is what I do. I can have one made up in less than ten minutes. What do I do once I make it?
(and THANK YOU!)

You need the command for installing FFF1.4 with adb. I know most of it but I forgot which partition the bootloader is on. I'll look around to see if I can find it.
[Edit:] Nevermind, you need a shell for that as well.

Thank you, I'll make the cable.

The factory cable will force you into fastboot mode. You need it to flash recovery and firefirefire.

OK so when I make this cable (I'm going to use a 1k resistor since that seems to be the recommendation) and plug it in, turn the kindle on, it will look the same, but be in fastboot mode, then from there I'll do whatever I need just let me know.

When you get it into fastboot mode start over from...
Code:
fastboot flash recovery twrp.img
[Edit:] let me know if you succeded in installing twrp

[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&A] [GUIDE][ROOT] Smartwatch 3 KNX01V

Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"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"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.

Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.

I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on

I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.

Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader

XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?

Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)

A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.

Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.

I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated

Hello, any idea to make it work on lollipop? Thanks!

I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"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"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying: