Develop Bugs

[Q] Stuck at boot!

My Kindle is unable to be detected on Kindle Unbrick and I reinstalled the drivers 9999 times and Kindle is stuck at bootlogo ! , Any Ideas how to flash the original firmware or at least bootup ?
I messed with the libandroid_runtime.so file

Can you see it in device manager?
Probably easiest to use this:
http://forum.xda-developers.com/showthread.php?t=1430038
But please, this thread should not be in the Dev forum.

Have you tried using "fastboot -i 0x1949 oem idme bootmode 4002" to enter fastboot mode when KF boots ? when it boots,there is a short time when you can use fastboot.
After entering fastboot mode,everything is so easy to save.

Gang_Jordan said:
My Kindle is unable to be detected on Kindle Unbrick and I reinstalled the drivers 9999 times and Kindle is stuck at bootlogo ! , Any Ideas how to flash the original firmware or at least bootup ?
I messed with the libandroid_runtime.so file
Click to expand...
Click to collapse
If it's a driver problem, use different drivers.

yumcax said:
Can you see it in device manager?
Probably easiest to use this:
http://forum.xda-developers.com/showthread.php?t=1430038
But please, this thread should not be in the Dev forum.
Click to expand...
Click to collapse
Thanks alooot for your response, & Sorry about the Dev forum
about the link you gave me , it needs Ubuntu and unfortunately I got Windows 7
adam900710 said:
Have you tried using "fastboot -i 0x1949 oem idme bootmode 4002" to enter fastboot mode when KF boots ? when it boots,there is a short time when you can use fastboot.
After entering fastboot mode,everything is so easy to save.
Click to expand...
Click to collapse
The adb pauses at "waiting for device" & it never pass
Disconnected it & reconnected many times but the same ;\
Zombiepiratez said:
If it's a driver problem, use different drivers.
Click to expand...
Click to collapse
3 different copies and still the same ;\
-----------------------------------------
Ugh I really feel very bad I didn't use this device only for 1 day and that happened
I have been rooting and installing custom roms on my X10 & SGSII for along time but never happened such
Please if anyone got another suggestions help ;(
Thanks everyone!

Gang_Jordan said:
Thanks alooot for your response, & Sorry about the Dev forum
about the link you gave me , it needs Ubuntu and unfortunately I got Windows 7
The adb pauses at "waiting for device" & it never pass
Disconnected it & reconnected many times but the same ;\
3 different copies and still the same ;\
-----------------------------------------
Ugh I really feel very bad I didn't use this device only for 1 day and that happened
I have been rooting and installing custom roms on my X10 & SGSII for along time but never happened such
Please if anyone got another suggestions help ;(
Thanks everyone!
Click to expand...
Click to collapse
Same happened to me. I was freaking out when it did. All you have to do is select ADB Device as the driver instead of ADB Composite Device.
Sent from my myTouch_4G_Slide using XDA App

jmcoffey said:
All you have to do is select ADB Device as the driver instead of ADB Composite Device.
Click to expand...
Click to collapse
and how can I do that ?
(I am a noob)
I found the ADB Composite Device but I don't know how to select ADB Device only ;\
I will donate if it worked

Gang_Jordan said:
and how can I do that ?
(I am a noob)
I found the ADB Composite Device but I don't know how to select ADB Device only ;\
I will donate if it worked
Click to expand...
Click to collapse
Does your computer see your kindle in device manager? If so what does it say?
Sent from my Kindle Fire using xda premium

http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506

pete_kowalski83 said:
Does your computer see your kindle in device manager? If so what does it say?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I did same as this
b63 said:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
Click to expand...
Click to collapse
I did it and still can't detect my device!
Sorry for being late to replay but I have exams these days :\
Any help ? ;(

that's only a loose description that you see how it is done:
if you' asked for a driver:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
if you'r not asked and want to update the driver:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok

i to am stuck at boot, adb worked before this, fastboot never has.
i even deleted android sdk and re-installed it, still same thing. adb works, fastboot does not.
Devices and printers in normal power on: (adb working)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Devices and printers in fastboot mode: (fastboot not working)
[Update] I ran the "Tweaked KFU", option 1 and it got me out
http://forum.xda-developers.com/showthread.php?t=1454913

[Q] KF drivers work but still cant get ADB working?

I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
Which version of KFU did you try running.. suggest you try the KFU 0.9.6

my drivers are working. when i plug my KF in i see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im also using 0.9.6
i plug my kf into my pc, that above screenshot is what i see so i dunno whats going on?

Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2

kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.
Click to expand...
Click to collapse
kishorev said:
Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
no i never did that...how do i got about that? im horrible at this, apologies.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
I'll see if I can help. The description of what you are seeing in the device manager "android adb interface" matches the picture in the upper right box in the table you posted. That is the fastboot driver, look at the description in the left column of the table. ADB doesn't work with the fastboot driver. You need to keep playing with drivers until you get the "normal" ADB driver working, see the listing in the lower right box of the table. The word "composite" must appear in the driver description for your computer to recognize your KF as an ADB device. KFU includes and installs both drivers but windows is easily confused and frequently uses the wrong one. Personally I think it is because the KF goes through different modes as it boots up and windows isn't accustomed to a device changing modes, but that is just my guess.
Sent from my Amazon Kindle Fire using xda premium

xXezmacXx said:
no i never did that...how do i got about that? im horrible at this, apologies.
Click to expand...
Click to collapse
Have uploaded some screenshots for you on checking your driver and also how to run ur KFU
Let me know if u were able to succeed

i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?

xXezmacXx said:
i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?
Click to expand...
Click to collapse
Yes, you have to disconnect mass storage to enable debugging.

soupmagnet said:
Yes, you have to disconnect mass storage to enable debugging.
Click to expand...
Click to collapse
sorry for the stupid ? but how do i do that?

edit: i got rooted following this guide: http://forum.xda-developers.com/showthread.php?t=1638452
for some reason KFU doesnt work for me.

No OS, OTG not recognized. Am I bricked?

Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it

I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.

Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562

Tried it on a full battery, still no luck.

tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here

Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.

Have you tried adb/fastboot?

Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.

-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.

CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.

DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?

Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.

I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1

CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4

The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?

Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1

The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.

Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.

zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.

Can't enter fastboot + unusual screen - bricked?

Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.

MaRkuS_538 said:
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?View attachment 3659595
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
Click to expand...
Click to collapse
I have that same line running down mine, looks like twrp.
hope someone chimes in...

It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.

r3t3ch said:
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
Click to expand...
Click to collapse
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...

You have a driver problem. If it gets listed under anything, uninstall the drivers for it from device manager. It should show up as something like "jem-pvt-prod-04" under other devices with a yellow triangle. You can then try to install its driver as adb composite interface or try using the driver from this thread. If you don't see "Android Composite ADB Interface" when you try manually installing the driver, reinstall adb/fastboot.

MaRkuS_538 said:
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
Click to expand...
Click to collapse
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry

sullytrny said:
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
Click to expand...
Click to collapse
Hey hope all went well with the storm for you, now can u do a write up on how to fix the issue please.

Yeah, hopefully. But it would be very nice to tell what you've done exactly (especially driver setup)
Gesendet von meinem Nexus 6P mit Tapatalk

Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?

MaRkuS_538 said:
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
Click to expand...
Click to collapse
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs

It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk

monster1612 said:
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Can you tell me how you did this? I disabled driver signature enforcement (running windows 10), but I have no clue where to go from here.
---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------
MaRkuS_538 said:
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Can you by chance explain what you did? I've got mine stuck at that screen (no recovery or anything) and can't go anywhere.

I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk

MaRkuS_538 said:
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?

kslonkey said:
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
Click to expand...
Click to collapse
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.

Bootloader driver issues on Windows 10?

I made this post to hopefully help me help you help us.
My Razer Phone is currently unable receive any commands while in fastboot mode/bootloader.
This seems to be a fairly common problem that I see some people are running into without having any concrete solution. I have tried numerous suggestions and then some. Therefore, I want to provide as much information and background to the problem to try and help anyone with more experience that is willing to get to the bottom of this.
So for some background, I successfully rooted my Razer Phone with help from both of these threads:
Rooting Android 9 December Update With Magisk (No TWRP)(Global)
and
[TWRP + MAGISK] FULLPROOF Guide for all Razers! Wifi Fix!
I primarily used the first thread listed to achieve root.
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I am trying to revert to stock and relock my bootloader using Razer's guide HERE. When using the 'flash_all' script that the guide references, the script fails, because the phone cannot receive fastboot commands.
I followed Razer's installation guide PDF to install the adb/fastboot drivers.
I have also tried using ClockworkMod's Universal ADB Driver.
EDIT: I also tried using [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I'm pretty sure I have installed the adb drivers correctly. I can use adb commands while android is running. It's listed when using the "adb devices" command. It successfully restarts and enters the bootloader after typing "adb reboot bootloader", but after typing "fastboot device", it only outputs "< waiting for any device >" and waits. I have also tried using the command "fastboot -i 0x1532 devices" as suggested in a related thread, but this just returns "fastboot.exe: unknown option -- i" and fails.
I have also tried selecting "Android ADB Interface", as well as "Android Bootloader Interface" when installing the google usb driver. I even tried using the third option, no luck.
Now here's why I say that I'm pretty sure that I have the drivers installed correctly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what is displayed in Device Manager when the phone is in fastboot mode and connected to my PC after installing the drivers.
It displays normal when android is running with or without USB debugging enabled.
I have tried this on a few Windows 10 PCs and get the same result. So, I wouldn't be able to tell if this is a Windows problem or if it is my phone:
This is what my bootloader shows. Besides the serial number I blocked out, notice how some data is missing? Could this be the problem?
I'm curious to know the method of root everyone else having this problem had used and whether their bootloader looks like this.
I understand the community for this phone isn't as active as it used to be.
So, thank you to anyone in advance for the help and your time.

This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.

tys0n said:
This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.
Click to expand...
Click to collapse
I forgot to mention that I had also tried this tool to install the drivers on a few different PCs. I did all of this (including other methods) after making sure to uninstall any drivers that were previously installed. The installation succeeds, but still has no effect on the phone being detected when it's in fastboot. Everything else, like file transfer and adb commands does.
Thank you for your time and for replying.

I've had the same problems you've had Waffle. I tried everything I could read in the forms, what ended up fixing the driver issues for me was to use Linux. I owe it to Linux's superior driver support that fixed the issue for me.

Well, I finally got it to work. I decided to try the tool tys0n mentioned again, and it worked. Not sure what I did differently this time, but I am thankful that it is now connecting properly.
Sorry for piggybacking onto my own post but now, after using the razer file to factory reset and lock the bootloader, the screen says "Your device has loaded a different operating system." on boot and some apps still say that the phone is rooted. When accessing the bootloader it says that everything is locked and the OEM Unlocking switch is disabled in developer options. Not sure what I may have done wrong, since it's just running a script for the most part or if it's just stuck like this since I rooted the phone in general.