[Q] KF Stuck on FireFireFire 1.3 - Not Recognized by ADB

---

Edited OP to be shorter to the point:
I am stuck in fastboot but can not establish an adb connection to set the boot mode back to 4000.

Originally Posted by Xplorer4x4

I was tired and trying to update my KF to FFF1.3 and TWRP 2.1.0. I am now stuck at the new FFF boot logo(green android guy with KF text under neath). The update to FFF1.3 went smooth. Then I moved on to TWRP. So I tried flashing the img file via terminal emulator rather then using ADB over my computer. So first I set the boot mode to 4002. Success! Then I tried to flash the img file, but was getting errors(I think it was because I forgot to cd in to the downloads folder so Terminal Emulator knew where the file was). Well Due to not being able to flash I had to set up my PC again for the KF to use ADB as I had a system crash since then. So I got hung up with not being bale to use ADB and decided to reboot the KF, thinking it needed a reboot before the PC would recognize it. After rebooting I for stuck on the FFF 1.3 logo. I know ADB is fully functional now(forgot to install an API) but the KF Utility will not recognize the device to be able to reset the boot mode to 4000.

Any suggestions?

can't use term to flash like adb, gotta use the dd if= method.

might be I'm fastboot if its stuck at the startup logo.

Sent from my HTC Glacier using xda premium

Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"

I think thats right... not 100%

Should be in normal boot mode now =D

Originally Posted by DeadChex

Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"

I think thats right... not 100%

Should be in normal boot mode now =D

You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.

Originally Posted by Xplorer4x4

You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.

opps, I lied... you cant issue idme from fastboot.... nor can you issue fastboot shell...

so, no adb at the very beginning of the KF boot? Does fastboot notice it


Try "Fastboot Reboot" if fast boot works... or 'Fastboot continue"

Originally Posted by DeadChex

so, no adb at the very beginning of the KF boot?

Nope, not at all.

Does fastboot notice it?

If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.

One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?

Originally Posted by Xplorer4x4

Nope, not at all.

If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.

One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?

the boot process goes... Bright LED (first turning on) > Dim LED (Fastboot and Button input) > Bright LED (Normal Boot)
Where is it stuck?

Use "fastboot devices" to see if its listed in the beggining (when bright green)
but, if its going Bright, that means its not trapped in fast boot


(Fastboot is a diffrent program from ADB completly, just throwing that out there, I've attached it if you need it)

Something very enlightening I found somewhere around this great place:

"
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface

here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot

the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001

and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO

then you only have to count 1 and 1 together and can master nearly each hanging situation !
"

Edit: You do need the file in the above post when doing this over usb.

Sent from my Amazon Kindle Fire using XDA

Originally Posted by freefaling

Something very enlightening I found somewhere around this great place:

This is great information but totally useless with out a working ADB.

Originally Posted by DeadChex

(Fastboot is a diffrent program from ADB completly, just throwing that out there)

I am aware, but thanks anyways.

fastboot devices does give an out put after the dim. Did not test before the dim.

Good News: I tried the "fastboot -i 0×1949 oem idme bootmode 4000" command again and got an unrecognized vendor ID. So despite following the instructions to modify the 2 .ini files, and accept the install driver warning, and selecting the location for the ini manually as you should, I realized something was wrong with adb. So I used the install driver bat from the KF Utility zip,and got adb working. Issued the 4000 boot command and back in business.

Thanks for all the help guys! I think you guys managed to provide the fastest responses to help I have ever needed, and it is rare I ask for help, so that makes the experience that much better.