Database Users

I believe I left out the line "fastboot oem idme 5009"

I missed it I believe and just "fastboot reboot"
after installing twrp recovery in th 6.3 root by jcase.
Now I'm stuck at the yellow fire and adb does not recognize my device any more and fastboot says waiting for device.
Did leaving this line out brick it? I got too excited after seeing the recovery screen I must have missed the line. I'm scared to do anything. Please help.

KennyCap said:
I missed it I believe and just "fastboot reboot"
after installing twrp recovery in th 6.3 root by jcase.
Now I'm stuck at the yellow fire and adb does not recognize my device any more and fastboot says waiting for device.
Did leaving this line out brick it? I got too excited after seeing the recovery screen I must have missed the line. I'm scared to do anything. Please help.
Click to expand...
Click to collapse
connect it and hit normal boot in kfu and when it says waiting for device turn the kindle off by holding the power button then turn it right back on and it will connect during boot

KFU utility? or unbrick? I tried to use the utility to root option 2 but I believe I had the path wrong. I had adb set up correctly cuz it recognized my device and I made it all the way to flashing the recovery img.
I'm not that command line savy any help would be greatly appreciated thanks

KennyCap said:
KFU utility? or unbrick? I tried to use the utility to root option 2 but I believe I had the path wrong. I had adb set up correctly cuz it recognized my device and I made it all the way to flashing the recovery img.
I'm not that command line savy any help would be greatly appreciated thanks
Click to expand...
Click to collapse
Oh I thought you had fff and twrp installed already where are you in the process and what's going wrong
Sent from my Hellfire Kindle using Tapatalk 2

i was rooting using the 6.3 method I made it through the first set of command lines. I installed the twrp.img. i saw it on my kf's screen. I got excited cuz I've been at it for a few hours typed fastboot reboot without the idme oem 500 something(sorry from memory I know thats not right) So the device rebooted into fast boot(yellow triangle with fire) and immediately tried to download drivers as the device was no longer recognized by fastboot(waiting for device) or adb (daemon started but no connected device) although after reinstalling the driver through kfu its now recognized in fastboot but not kfu. i think it has something to do with putting kfu in platform tools. So I know I'm not bricked just not sure where to start I'm gonna try the command line I believe I missed or a couple right before it.

KennyCap said:
i was rooting using the 6.3 method I made it through the first set of command lines. I installed the twrp.img. i saw it on my kf's screen. I got excited cuz I've been at it for a few hours typed fastboot reboot without the idme oem 500 something(sorry from memory I know thats not right) So the device rebooted into fast boot(yellow triangle with fire) and immediately tried to download drivers as the device was no longer recognized by fastboot(waiting for device) or adb (daemon started but no connected device) although after reinstalling the driver through kfu its now recognized in fastboot but not kfu. i think it has something to do with putting kfu in platform tools. So I know I'm not bricked just not sure where to start I'm gonna try the command line I believe I missed or a couple right before it.
Click to expand...
Click to collapse
OK cool so you have twrp and fff flashed.... do like I said before hook it up in kf utility hit the number for normal boot and it will say waiting for device.. turn your kindle off by long pressing the power button and then turn it back on and it will connect and switch to normal boot wile the kindle is turning on
if our using just adb in a command promp type this
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Sent from my Hellfire Kindle using Tapatalk 2

Thanks for the advice. The problem was I had the wrong path for kfu. I have rooted an Evo an epic and my transformer all fairly easy. That actually took me around 4 hours. I really should use adb more. That was my sister's KF I was rooting. I couldn't stand to see her using it stock like that. I got Hell Fire up and running. Thanks for trying to help.
Sent from my PC36100 using xda premium

KennyCap said:
Thanks for the advice. The problem was I had the wrong path for kfu. I have rooted an Evo an epic and my transformer all fairly easy. That actually took me around 4 hours. I really should use adb more. That was my sister's KF I was rooting. I couldn't stand to see her using it stock like that. I got Hell Fire up and running. Thanks for trying to help.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
No problem glad you got it going and good choice for a rom

[Q]Bricked ?

This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:

Bump

Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2

Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?

brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .

have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options

Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.

yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?

Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7

Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD

i've had good luck with mskip's toolkit in a similar situation

veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post

rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!

veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?

rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...

TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!

OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!

TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:

I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!

From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!

shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.

I have a problem

I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.

Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.

saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.

dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.

Just uninstall the kindle driver and replace it with the generic fastboot one

hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks

I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.

there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?

hw = hardware?

MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.

Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?

uhg
Facepalm

just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...

In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?

here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608

I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?

I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

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.

Magisk attempt gone horribly wrong on Pixel 3a, haven't found the answer

So I tried to root my Pixel 3a, long story short it went into a boot loop, I got it back into fastboot mode, but now my pc can't see it. when using "adb devices" search comes up with zilch. when plugged into the pc it knows it's plugged in but I can't see it. Has anyone else seen this, or possibly know a way to at least get me to where I can flash the stock image on?

jedivulcan said:
You have to use "fastboot" commands in fastboot mode. Like ... "fastboot reboot bootloader" or "fastboot boot namearecovery.img" ... You might be able to boot into TWRP recovery and flash the Magisk uninstaller.
Click to expand...
Click to collapse
call me noob or insane, but it wasn't working, but then I typed that in and it rebooted into fastboot. Off to try to follow these steps and hopefully get this thing working again.

tcshaddix said:
call me noob or insane, but it wasn't working, but then I typed that in and it rebooted into fastboot. Off to try to follow these steps and hopefully get this thing working again.
Click to expand...
Click to collapse
It wasn't working because you were trying to use adb commands while in fastboot.

tcshaddix said:
So I tried to root my Pixel 3a, long story short it went into a boot loop, I got it back into fastboot mode, but now my pc can't see it. when using "adb devices" search comes up with zilch. when plugged into the pc it knows it's plugged in but I can't see it. Has anyone else seen this, or possibly know a way to at least get me to where I can flash the stock image on?
Click to expand...
Click to collapse
Should've checked connected devices when in bootloader mode:
fastboot devices