Develop Bugs

Accidentally deleted everything, Kindle Fire stuck in TWRP

Hi,
I accidentally deleted everything through TWRP. I wanted the kindle fresh for my new ROM, and thought that deleting everything would make for a cleaner install. I was wrong and now all my kindle is good for is TWRP.
When in TWRP, windows doesn't recognize the kindle. Because of this, I cannot mount it. Windows and the kindle fire utility recognizes it as adp when i boot regularly (which is just a black screen) but cannot do anything since it will not enter normal or fast mode.
I don't know what to do, nothing is working. When I restart the kindle it says superuser is not installed, and asks if I would like to install it. I say yes, and it fails. Super user WAS installed before I deleted everything.
Any ideas?

Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading

I'm making some progress, I'm in fastboot command prompt and have access. But what do I do from here?
How can I install a system from fastboot? It looks like all the guides say to install twrp and go from there but I have twrp and it wont communicate with my pc!!!

ADB
llmercll said:
Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading
Click to expand...
Click to collapse
Do you have adb and fastboot intstalled on your PC??

lj50036 said:
Do you have adb and fastboot intstalled on your PC??
Click to expand...
Click to collapse
Yes, I've been using them at the command level

Feedback
llmercll said:
Yes, I've been using them at the command level
Click to expand...
Click to collapse
Boot into recovery and type
adb devices
copy and paste the output of this so I can see!!!

I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.

llmercll said:
I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.
Click to expand...
Click to collapse
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp

lj50036 said:
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp
Click to expand...
Click to collapse
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?

Admin
llmercll said:
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?
Click to expand...
Click to collapse
Or maybe you did not open you CMD window as admin....but twrp should see your devices in adb and let you push things to the /sdcard for sure... I have one right in front of me, but I am running linux which is much better for these kinds of things... Here is my output of that command and than a push of a zip file
Code:
[email protected] ~ $ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected] ~ $ adb push cmb_kkgapps_20131209.zip /sdcard
6121 KB/s (126216099 bytes in 20.135s)

I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>

feedback
llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
Move everything to the root of your c drive fastboot.exe, adb.exe, update.zip, all of it and than when you open your CMD windowas admin type
cd /
This will move you to the root of your c drive in you CMD window... Than type dir to make sure u can see your fastboot and adb and your update zip
than type
adb push update.zip /sdcard

llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
It's been a long time since I looked at this, but I seem to remember the windows adb client wanting a trailing slash if the push destination is a directory. That is... you want to use "/sdcard/" instead of "/sdcard" in that command to indicate that you want to push a file into that directory rather than replace the directory with a file (which it won't allow). Alternatively, you can use "/sdcard/update.zip" to remove any ambiguity from the command.
The output of your "adb devices" command is also a concern. It doesn't look to me as if you've booted the device into TWRP because it should output "recovery" and not "device" at the end there. One way or another, you'll have to get it to boot into TWRP if you want to flash that update.zip.

I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
C:\>adb devices
List of devices attached
0123456789ABCDEF device
C:\>adb push update.zip /sdcard
failed to copy 'update.zip' to '/sdcard': Is a directory
C:\>adb push update.zip /sdcard/
failed to copy 'update.zip' to '/sdcard//update.zip': Permission denied
C:\>adb push update.zip /sdcard/update.zip
failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied
C:\>
Click to expand...
Click to collapse
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?

llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
Try to use the "mount" function in TWRP to mount the /sdcard partition on your computer. It should work with the generic drivers already on your Windows PC and you can copy the update.zip over to it that way. If you can't get that to work, you are going to have to try reinstalling the drivers to get your PC to recognize TWRP. There are detailed instructions on how to do this in my guide.
The only other thing I can think of is to try reflashing an older version of TWRP. Those directions are available in one of my guides as well.

Recovery
llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
I would if it were me, install a recovery you dont plan on using... Than flash the one you would like to us.... I know it sounds funny but.. Ive be here before and that seems to work everytime... Than flash ROM and Gapps....
Here is the link to TWRP the first gen fire is an 'otter'... Make sure you get the otter.img....Than rename the .img file to twrp.img than put it with fastboot.exe and open CMD window as admin...and type
Code:
fastboot -i 0x1949 flash recovery twrp.img
Than
Code:
fastboot -i 0x1949 reboot
Let me know if that works for you or if you have any questions along the way... Thx as always lj

I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?

llmercll said:
I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?
Click to expand...
Click to collapse
2.6.3.1 Give that one a try!!!

I was able to get TWRP recognized by windows by using the earliest blaze edition. I mounted, copied the files, and then flashed back to 2.6.3.1 otter.
Then I wiped whatever data may have been in system data and cache and installed a new rom...
Only problem is it seems to be hanging on "updating partition details.."
I have the option to reboot, but am not sure if I should...

I think I got it!!

Can you ADB push files to the sd card without an OS installed???

I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much

You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.

DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...

mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.

DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles

Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps

You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5

Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.

EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5

[Q] Only Fasboot menu after flashing rom

Hi,
I have searched the forums but could not find an solution.
I have unlocked my m8 via htcdev.
installed SU and twrp recovery
flashed ViperOneM8 Rom using twrp recovery and now i am only getting the fastboot menu
*** TAMPERED ***
*** UNLOCKED ***
MB_UL PVT SHIP S-0N
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA14G
I have retried several times but no succes
Please advice

rvwoezik said:
Hi,
I have searched the forums but could not find an solution.
I have unlocked my m8 via htcdev.
installed SU and twrp recovery
flashed ViperOneM8 Rom using twrp recovery and now i am only getting the fastboot menu
*** TAMPERED ***
*** UNLOCKED ***
MB_UL PVT SHIP S-0N
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA14G
I have retried several times but no succes
Please advice
Click to expand...
Click to collapse
You have tried what several times?
Can you still get into recovery(TWRP)? If so, have you tried reflashing the ROM? Perhaps download a fresh copy incase it got corrupted and flash a new copy of Viper. If your device is still connected to PC and the PC can pick it up ... check with: fastboot devices ... it'll show serial number. Type in: fastboot erase cache then try again, booting into system or flashing copy of Viper.

BerndM14 said:
You have tried what several times?
Can you still get into recovery(TWRP)? If so, have you tried reflashing the ROM? Perhaps download a fresh copy incase it got corrupted and flash a new copy of Viper. If your device is still connected to PC and the PC can pick it up ... check with: fastboot devices ... it'll show serial number. Type in: fastboot erase cache then try again, booting into system or flashing copy of Viper.
Click to expand...
Click to collapse
Hi Bernd, thanks for your quick response.
I can still get into recovery and have tried reflashing several times. Don't know how to copy a fresh copy to my phone.
Fastboot devices does show my serial number but phone does not show in windows explorer (pc win 8.1).
Tried to mount phone in recovery but no succes

When connected in TWRP, use the following command to push the ZIP to the phone
adb push <filename>.zip /sdcard (e.g. adb push rom.zip /sdcard)
Once complete, you can then flash the ROM as usual

deleted

BerndM14 said:
If you can still get into recovery then you can sideload the ROM through adb(While in recovery).
Just copy the ROM(Fresh download preferably just in case the old one was corrupt) into the adb folder.
Boot phone into recovery again, then select Advanced, make sure device is connected to PC.
Type: adb devices to see if PC command prompt picks up device(Again it'll show serial number). If it doesn't try typing: adb kill-server then adb usb and again adb devices to see if it picks up device.
Next tap on ADB Sideload in TWRP then type: adb sideload nameofzip.zip It'll then sideload and install it automatically, when it's finished you can restart device. :fingers-crossed:
Click to expand...
Click to collapse
adb sideload doesn't work in TWRP (or at least not for me). adb push works fine, tho

EddyOS said:
adb sideload doesn't work in TWRP (or at least not for me). adb push works fine, tho
Click to expand...
Click to collapse
Ok I deleted my comment there, even if it might work on a 50/50 it'll probably just be better to go with something that'll work 100% so the push solution will be better then.
:good:

How to tell that adb push rom.zip /sdcard is ready?
EddyOS said:
When connected in TWRP, use the following command to push the ZIP to the phone
adb push <filename>.zip /sdcard (e.g. adb push rom.zip /sdcard)
Once complete, you can then flash the ROM as usual
Click to expand...
Click to collapse
C:\android-sdk-windows\sdk\platform-tools>adb devices
List of devices attached
SH45HWM05074 recover
How to tell that adb push rom.zip /sdcard is ready?
It keeps blinking

rvwoezik said:
C:\android-sdk-windows\sdk\platform-tools>adb devices
List of devices attached
SH45HWM05074 recover
How to tell that adb push rom.zip /sdcard is ready?
It keeps blinking
Click to expand...
Click to collapse
It's supposed to show the transfer rate xxx kb/s along with file size transferred and the time it took.
Does your command prompt show "active" again? Can you type commands into the prompt again?
Maybe try adb push romzipname.zip /sdcard/
Can also perhaps try adb ls /sdcard/ to confirm file was pushed

Fixed!
It's working now, according to twrp SU wasn't properly installed twrp fixed that

adb reboot bootloader - device not found

I've installed ADB/Fastboot/USB Drivers from http://forum.xda-developers.com/showthread.php?t=2588979 (tried both 1.3 and 1.4.2 versions.
Booted my SW3 into Fastboot (whitescreen, with fastboot written on it) - attached to the PC, Device shows up as SAMSUNG Android Phone > Android ADB Interface
Ran CMD as an Administrator.
Typed, adb reboot bootloader.... Error: device '<null>' not found.
Typed adb devices... not listed.
Okay, so using a driver stripper (and windows program uninstaller), removed all Samsung phone USB drivers, KIES and existing ADB drivers. Re-ran the top tool to re-install everything. Repeated process, still showing up as SAMSUNG Android Phone > Android ADB Interface. Still not detected.
No idea at all what's going on here. I've tried cleaning the drivers multiple times. Other USB ports (2.0 & 3.0). Tried manually updating the driver to Google Inc. driver variants (9.0-11.0)
Really appreciate any help here.

if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode

woschirmer said:
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
Click to expand...
Click to collapse
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.

Sideburnt said:
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Click to expand...
Click to collapse
Okay progress, I see what you mean now adb reboot bootloader doesn't work. But fastboot reboot bootloader does. This is allowing me to move through the necessary TWRP and img steps. Thanks.

Stuck in Bootloader - adb no devices - can't boot into system or recovery

Hey guys I'm stuck in bootloader on my taimen and I hope someone can help me.
I tried to update my OS from latest Android 9 factory image to Android 10 via bootloader, as I always do.
After executing the command
Code:
./flash-all.sh
I got a message that said that I should download and install the latest platform-tools from googles dev site, what I did. And I think that was my mistake. I downloaded the updated tools and replaced the old ones, while beeing in bootloader on my phone and connected to my MacBook.
Now I have a problem that whenever I try to boot in recovery or system I get the dead android Icon with 'No commands'. That wouldnt be a problem for me, if I could install a new .img to boot into system and start again. But unfortunately I cant find my device via adb. The List of attached devices is always empty.
What I have tried so far to solve this issue:
- tried 2 different cables and all USB ports I have - no success
- restarted adb several times - no success
- added vendor Id to /adb_usb.ini file like described in this post https://stackoverflow.com/a/7136003 - no success
Does anyone have a suggestion what I could try next? Any help is appreciated

Download Homebrew. And install adb in terminal, and try if that works . https://brew.sh/index_sv .
https://stackoverflow.com/questions/31374085/installing-adb-on-macos/32314718#32314718

I'm no expert but I thought that you should use fastboot commands from your MacBook terminal if you are in the bootloader and not adb commands. But I guess the fastboot commands don't work either since you wouldn't have a problem then!
Tips on getting to recovery mode from 'no command' screen:
https://youtu.be/P1RGEle3qN0

Hey guys thanls for your suggestions.
Fortunately I was able to resolve my issue. The problem was that I was on the wrong partition.
After setting the partition back to a with
Code:
fastboot --set-active=a
my device id appeared in the list of attached devices
Code:
fastboot devices
So I was able to reflash the flash-all.sh and now I'm on Android 10.