Database Users

[Q] Kindle fire totally dead

Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
Make/buy a factory cable and fastboot the proper bootloader from the stock update package.
Sent from my myTouch_4G_Slide using XDA App

I was a little confused about this myself at one point... There are a bunch of 'low-level' partitions that are really important not to mix up.
'bootloader' contains the basic bootloader, which loads everything else and you should pretty much never touch it, except to install FireFireFire.
'recovery' is the partition where TWRP or ClockWorkMOD should go.
Finally, 'boot' is what launches Android.
I almost made the same mistake last night installing CWM (it was 2am and my brain+fingers were being stupid)
Anyway OP, it sounds like a factory cable would be your best bet, unless that just tells something to the bootloader, in which case getting a warranty replacement from Amazon might be your only option...
Just remember next time that you want to flash recovery ;-)

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
I have had a similar situation on my KF. I used a factory cable to solve my issue. Send a private message to SkOrPn with Factory Cable in the subject. His cable is well built and arrived very quick via USPS. Not to mention he sells them at a good price.

Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...

Try adding the device ID 0bb4:0c01 to your USB configuration
Sent from my Amazon Kindle Fire using Tapatalk

dietomant said:
Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...
Click to expand...
Click to collapse
I think you've gotten somewhat misleading information from the previous posters. The factory cable will always put the KF into fastboot mode if (this is a HUGE if) the device has a working bootloader. The bootloader is the piece of software that will put the device into fastboot mode, so without that the factory cable cannot do its job.
I'm quite surprised you were able to break the bootloader by trying to flash that image onto it. In my experience, fastboot flash checks for the size and would fail when I tried to give it something > 256KB for the bootloader... but that's neither here nor there...
If you cannot get a "kindle fire" or the "yellow triangle" to come up on the display, your bootloader is broken. Your last hope is to open up the case and use usbboot to temporarily load a bootloader into memory via USB and use that to flash a permanent bootloader. You'll probably need a case pry tool to do this fairly safely and linux installed because I don't believe usbboot was ever ported to Windows.
Additional information: http://forum.xda-developers.com/showthread.php?t=1405052

Arrow [Q] Kindle fire bricked, adb : device not found

Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...

When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.

linuxsociety said:
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
Click to expand...
Click to collapse
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?

I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?

superbomb17 said:
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
Click to expand...
Click to collapse
So KFU is reporting unknown device? Sounds like you need to install the kindle fire USB drivers again. Is this on linux or on windows? unknown device means that it is recognizing a device, just doesn't know what device it is.. You need the correct drivers installed for the Kindle Fire, be sure to re-install those and try again.

When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.

Hausschuh said:
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Click to expand...
Click to collapse
Did you try plugging it into another PC to see if that PC detects it?

superbomb17 said:
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
Click to expand...
Click to collapse
The fact that it goes black right after the kindle fire logo makes me think it's not stuck in fastboot (would be unlikely in a build prop edit) which is why you can't get fastboot to recognize; at the same time depending on where it's failing during the boot init adb won't load either.
superbomb17 said:
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
Click to expand...
Click to collapse
First off; I seriously doubt you would be able to mount the sd from your PC properly. Rather than cracking the device I would try booting it from a factory cable, it should hopefully force fastboot mode at which point you should be able to resolve your issues.

KF stuck in TWRP 2.0 boot loop

Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari​
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)

If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.

Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again

nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium

[CLOSED] Help! Nexus 10 stuck on Google logo after Rooting attempt

Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance

Have you tried using a different usb port on the PC, and rebooting the PC?

bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.

When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!

Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)

I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm

bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.

bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:

Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out

I know it's the wrong forum, but....please take a look

I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end

Try fastbooting a recovery like TWRP thati s updated then flash a rom.

disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse

Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.

As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.