Database Develop

[Q] Please help w/bootloader

Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:

TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?

Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader

Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??

TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.

rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process

TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB

TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:

Soft bricked - Not showing in ADB Devices

I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:

htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything

I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.

htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.

htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices

That's encouraging. Any idea how to get past the system.img file is too large error?

htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?

My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html

I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".

htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk

htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?

Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....

htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053

Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!

htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.

Lost OS after mistaken wipe/format now I am stuck on the Google logo

Long story short I just picked up my Nexus 6 and was trying a few ROMs. Having come from a OnePlus that was stolen I wanted a similar feel. I tried a few, Bliss, Cyanogen and then finally decided after some more research that Pure Nexus was going to be my choice. I have using the Nexus Root Tool kit since I have little knowledge of adb other than what I read if needed. Pure Nexus loaded with the pure-nexus gapps that were suggested seemed to not load properly, I was either getting stuck booting up, a bootloop or when i tried loading it without the gapps it just booted to a blank screen. So I read a littel more and was under the impression I need a clean slate. I think I cleaned it too good. After wiping system, cache and dalvik cache I may have formatted by mistake.
So here I sit with a new phone that with not work. I feel there has to be an easy answer. I tried pushing the ROM to the sdcard with adb push using THIS METHOD HERE but I keep getting 'device closed'.
I feel if I can just get the file on the device I can flash it. I have also tried the 'Flash Stock Unroot' in Nexus tool kit.
HELP!

tjlmbklr said:
Long story short I just picked up my Nexus 6 and was trying a few ROMs. Having come from a OnePlus that was stolen I wanted a similar feel. I tried a few, Bliss, Cyanogen and then finally decided after some more research that Pure Nexus was going to be my choice. I have using the Nexus Root Tool kit since I have little knowledge of adb other than what I read if needed. Pure Nexus loaded with the pure-nexus gapps that were suggested seemed to not load properly, I was either getting stuck booting up, a bootloop or when i tried loading it without the gapps it just booted to a blank screen. So I read a littel more and was under the impression I need a clean slate. I think I cleaned it too good. After wiping system, cache and dalvik cache I may have formatted by mistake.
So here I sit with a new phone that with not work. I feel there has to be an easy answer. I tried pushing the ROM to the sdcard with adb push using THIS METHOD HERE but I keep getting 'device closed'.
I feel if I can just get the file on the device I can flash it. I have also tried the 'Flash Stock Unroot' in Nexus tool kit.
HELP!
Click to expand...
Click to collapse
I'm assuming you have twrp installed? If you do, you can just plug your device in to your pc and you should be able copy files to the phones storage, and then flash them. Or you can goto Advanced, ADB Sideload and "adb sideload purenexus.zip"

you dont need adb to push anything to your phone. you can transfer any rom, gapps, and supersu just using twrp recovery.

obtained said:
I'm assuming you have twrp installed? If you do, you can just plug your device in to your pc and you should be able copy files to the phones storage, and then flash them. Or you can goto Advanced, ADB Sideload and "adb sideload purenexus.zip"
Click to expand...
Click to collapse
I do have TWRP installed but I do not see my phone in my Windows files system.
I tried the sideload and this is where I am met with the device close message. I do see my device when I do a 'adb devices'
simms22 said:
you dont need adb to push anything to your phone. you can transfer any rom, gapps, and supersu just using twrp recovery.
Click to expand...
Click to collapse
Assuming you mean what obtained just suggested, how do I do this if I cannot see my phone in my PC's file system?

tjlmbklr said:
I do have TWRP installed but I do not see my phone in my Windows files system.
I tried the sideload and this is where I am met with the device close message. I do see my device when I do a 'adb devices'
Click to expand...
Click to collapse
When you do "adb devices", does it show recovery or sideload next to the serial?

Sideload. This is what I am not sure how to resolve.
Sorry, I should have mentioned that.

tjlmbklr said:
Sideload. This is what I am not sure how to resolve.
Sorry, I should have mentioned that.
Click to expand...
Click to collapse
The only time I know of sideload showing "error: closed" is when recovery isn't in "sideload mode". Using Windows? Do you see any errors in Device Manager?
Edit: Maybe when you put twrp in "sideload mode", you're waiting too long to send the sideload command before it times out? Maybe get the command ready before you enable sideload in twrp?

obtained said:
The only time I know of sideload showing "error: closed" is when recovery isn't in "sideload mode". Using Windows? Do you see any errors in Device Manager?
Edit: Maybe when you put twrp in "sideload mode", you're waiting too long to send the sideload command before it times out? Maybe get the command ready before you enable sideload in twrp?
Click to expand...
Click to collapse
No errors

tjlmbklr said:
No errors
Click to expand...
Click to collapse
In twrp, do "adb usb" and see if your storage shows up on the pc, if it doesn't, enable sideload and do "adb usb" and the "adb sideload purenexus.zip" again

Quick update. I was using an out dated version of adb. I updated, side loaded the ROM and it booting up now.
Fingers crossed!

tjlmbklr said:
Quick update. I was using an out dated version of ad. I updated, side loaded the ROM and it booting up now.
Fingers crossed!
Click to expand...
Click to collapse
Of course it would be something so simple!

obtained said:
Of course it would be something so simple!
Click to expand...
Click to collapse
I am just happy it was. I recently Hard Brick a Galaxy Tab3 when I failed at loading a custom ROM on it. If I would have ruined this device I would never hear the end of it from the wife.

Disconnects from computer after entering bootloader

I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?

In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.

Have you tried unplugging and plugging in the usb again after entering recovery?

Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.

Yay!

ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.

I need some help unbricking my fire...

Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!

Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.

Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740

hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36

blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.

blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.

I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..

blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!

Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.

drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.

I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.

I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!

So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!

drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?

thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip

drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.

thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.

What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.

blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery

watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4