Develop Bugs

Potentially bricked Desire...

Hey everyone, I'm sad to say that earlier I dropped my beloved Desire and it's not booted properly since e.g. I can only get onto the dialer.
The long and short of it is that I can't mount my SD card, clockwork won't allow it and says it has:
E:can't mount /dev/block/mmcblk0p1
no such file or directory
E: can't mount /sdcard
And ADB doesn't find my device when I type adb devices.
I've come across a few posts but I'm pretty clueless as to what they actually mean...
I've heard this particular command fixes it in Linux...
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
But how would I go about doing that, and is there a way of doing that in Windows? I assume that because adb can't see my device then that's a no... It knows it's plugged in because it makes the connection sound and I can see it in device manager.
It's currently S-OFF'd with AlphaRev 1.8 running a Cyanogenmod nightly that I had running for a few days without problem so I assume it's not that. I can get into Fastboot (not much good if Windows doesn't see my device), bootloader and Clockwork.
I feel really stuck right now and would really appreciate the help of one of you knowledgeable lot.
Bearing in mind I'm not very knowledgeable so anything you explain would really have to be explained well!
Thanks guy's.

http://forum.ppcgeeks.com/archive/index.php?t-125093.html

Thanks for that, but ADB doesn't see my device so I can't use that.

DesireRoss said:
Thanks for that, but ADB doesn't see my device so I can't use that.
Click to expand...
Click to collapse
When your on bootloader screen and you plug your usb in does it change to say that you have plugged in usb ? because fastboot isn't adb
Hboot has an option for fastboot
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
read up on http://forum.xda-developers.com/showthread.php?t=691187

BigMrB said:
When your on bootloader screen and you plug your usb in does it change to say that you have plugged in usb ? because fastboot isn't adb
Hboot has an option for fastboot
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
read up on http://forum.xda-developers.com/showthread.php?t=691187
Click to expand...
Click to collapse
When I plug it in, all the drivers get installed and it changes to 'HBOOT USB PLUG' on the bootloader. The problem is when I type in 'adb devices' it doesn't show my Desire. I can't fastboot that command because it can't find the phone itself..?

DesireRoss said:
When I plug it in, all the drivers get installed and it changes to 'HBOOT USB PLUG' on the bootloader. The problem is when I type in 'adb devices' it doesn't show my Desire. I can't fastboot that command because it can't find the phone itself..?
Click to expand...
Click to collapse
You have to boot your phone into fastboot.
Code:
fastboot devices
does not work in hboot mode.

MatDrOiD said:
You have to boot your phone into fastboot.
Code:
fastboot devices
does not work in hboot mode.
Click to expand...
Click to collapse
It says 'fastboot' is not recognized as an internal or external command, operable program or batch file.
Arghh!

Are you trying this in fastboot mode? You have to start it with the back button and power button pressed until you see the white screen with the three androids at the bottom, Fastboot highlighted in red letters

BigMrB said:
Are you trying this in fastboot mode? You have to start it with the back button and power button pressed until you see the white screen with the three androids at the bottom, Fastboot highlighted in red letters
Click to expand...
Click to collapse
Yeah, that's what I'm doing. I'm just clueless as to why ADB can't see it? If it could, it would solve my problem... So frustrating.

DesireRoss said:
Yeah, that's what I'm doing. I'm just clueless as to why ADB can't see it? If it could, it would solve my problem... So frustrating.
Click to expand...
Click to collapse
Driver issue?? Try downloading HTC sync to get them...

BigMrB said:
Driver issue?? Try downloading HTC sync to get them...
Click to expand...
Click to collapse
And then uninstall only htc sync, not the drivers. Then reboot computer to apply changes.
To avoid the firmware issue from unrevoked, it's recommend to use unrevoked 3.21:
http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe

Tried what you said and I got 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"
}

Installed android sdk correctly:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

I think you might be right... Trying to install the Google USB drivers and it says 'failed to fetch URL' is there anywhere I can manually download it off the net?

http://dl4.htc.com/RomCode/Source_and_Binaries/USB_driver_20101122_release.zip
You can get them through SDK manager you know?!

BigMrB said:
http://dl4.htc.com/RomCode/Source_and_Binaries/USB_driver_20101122_release.zip
You can get them through SDK manager you know?!
Click to expand...
Click to collapse
This is the Google usb drivers from the SDK... And it says I can't download that repository because of a bad URL..?

Managed to get the USB drivers, but still not being found in ADB... Is this a lost cause?

Booted into recovery and ADB found it...
Any ideas on what to do from here?

DesireRoss said:
Managed to get the USB drivers, but still not being found in ADB... Is this a lost cause?
Click to expand...
Click to collapse
- Check if ONLY HTC SYNC DRIVERS where installed.
- Checked "unknown sources" in applications?
- Set phone to "charge only" and "never ask?"

MatDrOiD said:
- Check if ONLY HTC SYNC DRIVERS where installed.
- Checked "unknown sources" in applications?
- Set phone to "charge only" and "never ask?"
Click to expand...
Click to collapse
Yeah that was all that was installed. Can't check unknown sources or the other as I can't actually get into anything past the first setup stage and then there's nothing... Just need to re-enable my SD card. Fffffffffff.

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

[HOW TO][UNBRICK][KF2][RED SCREEN] You have a red screen? Try this!

How to fix your bricked KF2/otter2 with a red screen​
Preparation:
Amazon recently fixed the secruity hole, that was used to flash second bootloader and TWRP recovery.
After you flashed TWRP recovery/second bootloader and rebooted the device you will see a red screen. You can do nothing at this point withoud a pc.
So to reopen the secruity hole you have to downgrade the bootloader via fastboot.
In order to enter Fastboot mode you have to have a fastboot/factory cable. The fastboot/factory cable is not the cable that came with your Kindle Fire!!! For more information about the factory cable visit this thread: http://forum.xda-developers.com/showthread.php?t=1392693
Also you should set up all drivers and the Android SDK.
You can find the right drivers here!
Your device is not turning on? No sign of life? Then check this thread for hard bricked KF2s': http://forum.xda-developers.com/showthread.php?t=2415870
Steps:
1.)Hold the power button for 20 sec. Your device will shut down
2.)Plug in your Fastboot cable and power on the device. Your Kindle should now be in fastboot mode (a green light should blinking)
3.)Download the Bootloader file: otter2-u-boot-prod-10.2.4.bin
md5sum: 5b03a7b428325de8d360ec201a745498
4.)Copy the file in to the same directory where the fastboot.exe is located
5.)Open a CMD window, navigate to your fastboot directory and type:
##############################################################
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
##############################################################
6.)Disconnect the device and hold the power button for 20 sec again.
7.)Your device should now be working fine.
Support Me:
If I helped you please press the thanks button and rate this thread
{
"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"
}
!
Thanks to @Hashcode for providing the bootloader file.

Thanks for the info. Saw this in one of the HD forums an d assumed it would work for us (not that my device will ever see stock again lol)
Good to see some sharing here.
--
Sent from my mind to your screen.

flopower1996;42062477
4.)Copy the file in to your fastboot directory
[/QUOTE said:
This may be a dumb question, but where is the fastboot directory? I'm reading this as a directory as in filesystem, i.e Device/sys/fastboot, something like that, but from glancing around, I'm failing to find anything remotely similar. Am I missing something or just misunderstanding the instruction?
Click to expand...
Click to collapse

I believe he meant the directory in which the fastboot application is located on your PC, which is typically your Android SDK folder / platform-tools.
Sent from my Amazon Kindle Fire2 using xda premium

bjoswald said:
I believe he meant the directory in which the fastboot application is located on your PC, which is typically your Android SDK folder / platform-tools.
Sent from my Amazon Kindle Fire2 using xda premium
Click to expand...
Click to collapse
That's what I too assumed, but wasn't sure, thanks!

Thanks. I will try this when my fast boot cable is arrived . it got a red screen ad soon as I installed TWRP.
Sent from my Nexus 7 using Tapatalk 2

My kf2 is on 10.4.1 but its still rooted after i fixed the red screen the first time. used kffaid to recover it to 10.2.4. Its working as a normal kindle with root now. So if i flash twrp again. Get a red screen. And then do what the first thread says. TWRP will be installed and i can install a custom rom then ?

lost
flopower1996 said:
Amazon recently fixed the secruity hole, that was used to flash second bootloader and TWRP recovery.
After you flashed TWRP recovery and rebooted the device you will see a red screen. You can do nothing at this point withoud a pc.
So to reopen the secruity hole you have to downgrade the bootloader.
In order to enter Fastboot mode you have to have a fastboot/factory cable. Buy or build one.
Also you should set up all drivers and the Android SDK.
1.)Hold the power button for 20 sec. Your device will shut down
2.)Plug in your Fastboot cable and power on the device. Your Kindle shout now be in fastboot mode (a green light should blinking)
3.)Download the Bootloader file: otter2-u-boot-prod-10.2.4.bin
4.)Copy the file in to your fastboot directory
5.)Open a CMD window and type: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
6.)Disconnect the cable and hold the power button for 20 sec.
7.)Your device should now be working fine.
If i helped you please drop a like thank you!
Thanks to hashode for providing the bootloader file.
Click to expand...
Click to collapse
attempting to do this i have not gotten a blinking green light. the screen stays red and i can't get my computer to recognize it again to do the fastboot cmd. what else should i try or do?

snoogens79 said:
attempting to do this i have not gotten a blinking green light. the screen stays red and i can't get my computer to recognize it again to do the fastboot cmd. what else should i try or do?
Click to expand...
Click to collapse
That means you either don't have a factory cable or the factory cable you made doesn't work. BTW, a "factory cable" is not a standard USB cable.

soupmagnet said:
That means you either don't have a factory cable or the factory cable you made doesn't work. BTW, a "factory cable" is not a standard USB cable.
Click to expand...
Click to collapse
i have the cable that came with the kindle and a few other cables and it worked before this 10.4 update.

snoogens79 said:
i have the cable that came with the kindle and a few other cables and it worked before this 10.4 update.
Click to expand...
Click to collapse
Once again, a "factory cable" is not a standard USB cable. When people say "factory cable", they are referring to a factory programming cable. If you don't know what it is, you don't have one.

This has truly saved my tail. Thank you very much. You are a life saver.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta

Need some help!
I just got my fastboot cable in the mail, did all the steps up until the typing the command into the prompt. I put the .bin file into the exact folder where fastboot.exe is located and everytime I run the command, it says: "error: cannot load 'otter2-u-boot-prod-10.2.4.bin'".
Can anyone help me please?!

Sry guys, my server is atm down. I contacted my hoster so it should be up soon!
EDIT: Ok everthing is up now again

Pandasaurus12 said:
I just got my fastboot cable in the mail, did all the steps up until the typing the command into the prompt. I put the .bin file into the exact folder where fastboot.exe is located and everytime I run the command, it says: "error: cannot load 'otter2-u-boot-prod-10.2.4.bin'".
Can anyone help me please?!
Click to expand...
Click to collapse
Umm...did you check the md5 sum of that file before trying to flash it in fastboot?

Hello, sorry for the English, but I am an Italian boy.
I have red screen on my Kindle second generation.
I just got the factory and I CLABE fastboot with green light.
Unfortunately in my Windows 7 Ultimate, is recognized as the Kindle I otter2 - prod - 04.
Can you tell me where to download the drivers to be able to run my Kindle?
Thank you.

I know i will sound stupid for asking this, but i need your help. Which drivers do i set up because i am not sure if i have the right one (Device manager says Kindle fire: android adb interface) also i have a android sdk with fastboot and they on the same page but when i type it in on the cmd it says it does not recognize fastboot. Is your version of fastboot the same as mine? And how will i know when it is done or when to disconnect. thank you!
:good::highfive:

controguerra said:
Hello, sorry for the English, but I am an Italian boy.
I have red screen on my Kindle second generation.
I just got the factory and I CLABE fastboot with green light.
Unfortunately in my Windows 7 Ultimate, is recognized as the Kindle I otter2 - prod - 04.
Can you tell me where to download the drivers to be able to run my Kindle?
Thank you.
Click to expand...
Click to collapse
Davis6050 said:
I know i will sound stupid for asking this, but i need your help. Which drivers do i set up because i am not sure if i have the right one (Device manager says Kindle fire: android adb interface) also i have a android sdk with fastboot and they on the same page but when i type it in on the cmd it says it does not recognize fastboot. Is your version of fastboot the same as mine? And how will i know when it is done or when to disconnect. thank you!
:good::highfive:
Click to expand...
Click to collapse
Use this driver: http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
It's for the Kindle Fire HD 7'' but works fine for our Kindle Fire 2 as well.

flopower1996 said:
Use this driver: http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
It's for the Kindle Fire HD 7'' but works fine for our Kindle Fire 2 as well.
Click to expand...
Click to collapse
Thank you, now my kindle in Fastboot is recognized by the PC as a Kindle fire.
I inserted the file otter2-u-boot-prod-10.2.4.bin in the directory where there is' fastboot.exe (in the platform-tools). I typed CMD and then fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin but I received an answer: fastboot-i not recognized as an internal or external command, operable program or batch file
I do not understand where I'm wrong ....

There must be a space between fastboot and -i
So the comand is:
Fastboot -i
Gesendet von meinem Optimus 2X mit Tapatalk 2

[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

No succes trying to unlock my Swift 2x

Hi, I spent several hours trying to unlock my phone. Tried following steps:
* I made a full backup
* I did full reset to original settings: Androïd 8.1.0
* I got myself developers rights
* in settings turned on 'usb debugging' , 'OEM unlock' and 'advanced restart'
After turning off device and restart ('power/vol up' buttons), device started in recovery mode
* downloaded 'ADB + Fastboot-package' on Win10-PC and tried in every conceivable way to install but phone would not not connect; recovery boot indicated device was locked; PC did not recognize phone
and impossible to flash TWRP-recovery
* I installed Magisk-manager on phone with succes to avoid having to use a PC; but then flashing TWRP did not succeed
What did I wrong, what do I wrong? Suggestions VERY welcome. after all this I had rather not return to original OS. Thanks for your help.

With the phone in fastboot mode issue "fastboot devices" make sure you get a response.
Then "fastboot oem unlock - go"

Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.

hepkeb said:
How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
First you select Fastboot
Spoiler: Fastboot
{
"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"
}
Then you get in Fastboot Mode, then connect your cable to your Pc
Spoiler: Fastboot Mode
THIS IS FASTBOOT !

Thank you for trying to help. Of course I know how to get in fastboot mode. My problem is that in 'every' mode my telephone is locked, and I do not succeed in unlocking it. I cannot connect to another device, Magisk installation not complete etc. Again: I have developers right, I unlocked OEM, I did allow USB-debugging but no unlocked device!? What is going wrong, or has Wileyfox blocked the normal unlocking-procedure?

hepkeb said:
Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
That is fast boot mode

robin0800 said:
That is fast boot mode
Click to expand...
Click to collapse
I have exactly the same problem. I do not have access to the phone and a hard reset leads me to having to enter a googe account synced with the device which I do not have the details of. I can enter the mode that you describe above and the FASTBOOT MODE is in red below. Now when I'm here and plug into my laptop wth USB and fire up fastboot.exe and issue 'fastboot device' it just says '< waiting for device >'.
Did you manage to make any progress on this issue at all, I'm really stuck!

download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.

robi0800 said:
download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.
Click to expand...
Click to collapse
Thanks robi0800 but I don't have access to the phone so I can't enable USB debugging which means I can't use adb. I am trying to use fastboot but when I issue the command 'fastboot device' it can't connect to the phone and just displays '< waiting for device >'. Any other advice on how to make my Win10 laptop recognise the device when I plug it in so I can use fastoot successfully?

Sounds like you are missing a driver you could try the driver from the package in post #8 above?

Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.

Bermudan said:
Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.
Click to expand...
Click to collapse
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode

robin0800 said:
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode
Click to expand...
Click to collapse
Thanks - and to put it in recovery mode is this just Powebutton + Vol Up for several seconds or Vol Down, I can't recall...