Database Users

[SOLVED by Linux method by pokey900] Yellow triangle, pc doesnt detect my kindle fire

Hey everybody.
I have tried all options regarding kindle fire utility and no success.
Here's my story:
I have rooted 6.2.1 firmware. ALl worked fine for the past month. Yesterday went online on my kindle fire for about ah hour. Today I tried to turn my device on and twrp screen appeared (though i didnt hold power button for no second) and started installing updates (updates within twrp). But I was very stupid by holding power button and the device was turned off.
When I tried to turn it on again yellow triangle came on and nothing happens. The PC doesn't recognize my device, kindle utility doesn't help.
SO I think nothing will help until my PC detects the KF. In device manager i see no question marks, KFU cant detect the KF.
Please help me somebody

Your KF can be bootable. First you need to connect your KF to your PC and use a general adb Android Composite driver for Windows to communicate to your KF. Once you are able to communicate I.e
advanced devices and you see the SN of the KF, then follow the instruction given in the fastboot thread available under development ofKF.
Regards
Sent from my GT-S5830 using XDA App

how can I "use a general adb Android Composite driver for Windows to communicate to my KF"???
Thank you

me.biturbo said:
how can I "use a general adb Android Composite driver for Windows to communicate to my KF"???
Thank you
Click to expand...
Click to collapse
Plug your device into PC, then follow the instruction from the link below to install and connect your KF
http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/

Hi, firstly I have Windows XP, following the link provided I cannot complete these steps:
Click on Windows (Start at bottom left).
Select Devices and Printers.
I don't see that "Select Devices and Printers. "
I try to right-click on my computer-properties-hardware-device manager.
I don't see kindle there, I don't see any question marks.
So, any ideas?

cruel91 said:
Plug your device into PC, then follow the instruction from the link below to install and connect your KF
jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/[/url]
Click to expand...
Click to collapse
Previously I installed drivers and everything, I gain root access ect, I have TWRP installed. I connected my kindle to PC multiple times without any issues, but...
everything changed yesterday. I guess my device got updated without my knowledge. Amazon is very unfair. They should have implanted an option if people wanted to update automatically or manually, like every Windows or any other OS has got.

Here is what happening now:
I open KFU go to boot mode, then connect my kindle fire and press 1 (normal mode) very fast (it looks like the computer recognizes the device for a couple of seconds only) then triangle disappears and...... I see kindle fire words. I start jumping of joy (for 2 seconds maybe) then the triangle shows up again and nothing happens.
So sad

would try to follow this thread starting at post #2:
http://forum.xda-developers.com/showthread.php?t=1455501
here the prerooted stock roms:
http://forum.xda-developers.com/showthread.php?t=1451747

My issue was solved via LINUX solution found here http://forum.xda-developers.com/showthread.php?t=1430038
To be short:
1. Download Ubuntu 11.10 - Latest Version (about 700MB)
2. On the same ubuntu website foolow step to to create bootable USB stick and follow the steps provided
3. Download file from the buttom of the post http://forum.xda-developers.com/showthread.php?t=1430038 and copy it to the root of your bootabel USB.
3. Now boot your pc from USB
4. Now you should be in Linux
5. Now I quote: "When Ubuntu desktop shows up, press the Windows key on your keyboard and type "term". Hit enter to run the terminal.
In the terminal window, type "sudo /cdrom/fk".
You should now have a prompt that says "[email protected]:~/firekit#"
Now the most important part. SInce my pc recognized my kindle fire for 4-5 seconds only I needed to be very quick. SO this is what I did next:
I typed in the terminal "install_fff_twrp_from_stock" and didn't click ENTER.
Then for the first time during this process I connected my kindle to PC, waited one second and then hit enter for the above command to take effect. A couple of seconds was enough and Now I've got working KF.
Thanks to the guy who wrote LINUX SOLUTION, e.g. pokey9000

stuck on yellow triangle after miui4.0//on mac

I have read the write up on how to restore the Kindle after being bricked by miui4.0
I however am on a new macbook pro, have downloaded KFU for mac, have everything installed and where it should be, (i suppose. I have done this on my parents windows machine but this mac is new to me.) I have all files needed in the same folder as dab.exe and fastboot.exe.
When I run either script it just pops up in the terminal and really doesn't run through the script like it does on windows. And definitely nothing happens.
When I open the terminal and start putting in the commands in the thread about restoring the kf, every command just says "command not found"
So now I'm stuck, and would very much like to use my kindle fire. I will get back to my parents house to use the windows machine in a few weeks and can def. get it restored then, seeing as how I know how to do it on windows, but this is my first mac.
Thanks guys!!!
Chad
EDIT: SOLVED.
after spending about 20 minutes with "b63" on TeamViewer, I was able to get the commands correct for a mac. mainly just newbie stuff due to the os change.

just took a look to the linux/mac version
if you open a terminal and cd to the tools directory of kfu then there are the commands
for mac it's:
adb.mac and fastboot.mac
that means you have to adapt the commands like eg:
fastboot.mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
edit: attached corrected run.sh - just rename (remove .txt)

trying to cd to the folder but says no such directory.
even though when I go through the hd, its right there.
the terminal doesn't make sense to me like it does with a PC.

Need Assistance Via Teamviewer to Fix Kindle
Hi
My Kindle is stuck into the yellow triangle blinking when I link it via usb.
The Kindle run flat and when I tried to get it going again it was stuck in this loop.
I tried unsuccessfully to get it out.
If there's someone willing to assist me via teamviewer please let me know.
I am on a mac.

when the yellow triangle is blinking it is booting constantly
means the battery is dead - try to charge it with the wall charger
for some hours - best over night - if you don't use the original charger
be shure it has ~2A - most replacement chargers have only 1A - that is
too few to charge when the battery is so low

wall charger
Hi b63
I have no wall charger. I will check with the friend who brought it into South Africa if he got one with.
If not. You are saying that I can get such a wall plug micro USB as long as it has ~2A.
Thanks for that.

wotandsdwys said:
trying to cd to the folder but says no such directory.
even though when I go through the hd, its right there.
the terminal doesn't make sense to me like it does with a PC.
Click to expand...
Click to collapse
On a Mac, type:
cd <space> and drag the folder you want to change to, into the Terminal window.
You can only cd directly into the next folder in the tree. Otherwise, you need to type the full path.
i.e. $ ~/Users/JohnDoe/AndroidSDK/platform-tools
Sent from my Kindle Fire using xda premium

johanhorak said:
Hi b63
I have no wall charger. I will check with the friend who brought it into South Africa if he got one with.
If not. You are saying that I can get such a wall plug micro USB as long as it has ~2A.
Thanks for that.
Click to expand...
Click to collapse
every replacement usb charger will work as long it mets the specifications

I am currently working on a Mac, and do not have access to Windows.
My Kindle Fire was running v6.3, and I rooted it using BreakDroid v0.6.
And now I'm stuck at the yellow triangle. Pressing the power button during this phase won't bring me into recovery mode.
While the device is powered on, and plugged into my Mac, at the yellow triangle screen, I opened a Terminal window and typed "adb shell", but am receiving "error: device not found."
Also, wotandsdwys, where is the post on how to restore the Kindle after being bricked by MIUI 4.0? A link would be very helpful.
And is this the Kindle Fire Utility you are referring to? Is the script that user b63 attached to this thread supposed to convert that to be able to be used on a Mac?
Anything at this point would be helpful. I keep finding solutions that require a PC, but not so much when you're on a Mac.
Thanks!

STuck on Yellow Triangle with Mac
cocco3 said:
I am currently working on a Mac, and do not have access to Windows.
My Kindle Fire was running v6.3, and I rooted it using BreakDroid v0.6.
And now I'm stuck at the yellow triangle. Pressing the power button during this phase won't bring me into recovery mode.
While the device is powered on, and plugged into my Mac, at the yellow triangle screen, I opened a Terminal window and typed "adb shell", but am receiving "error: device not found."
Also, wotandsdwys, where is the post on how to restore the Kindle after being bricked by MIUI 4.0? A link would be very helpful.
And is this the Kindle Fire Utility you are referring to? Is the script that user b63 attached to this thread supposed to convert that to be able to be used on a Mac?
Anything at this point would be helpful. I keep finding solutions that require a PC, but not so much when you're on a Mac.
Thanks!
Click to expand...
Click to collapse
I am in the same boat. I used Breakdroid, and was stuck at the kindle fire boot screen. Stupidly turned the power off and have been stuck on the yellow triangle. Could someone help me out? I am a total noob at this stuff

Bump?

cocco3 said:
Bump?
Click to expand...
Click to collapse
Don't own a mac but consider this link for how to input adb commands
http://forum.xda-developers.com/showthread.php?t=1443071
and this link for the necessary commandlines:
http://forum.xda-developers.com/showthread.php?p=24129239

If you are stuck at the boot logo then you are in fastboot mode. ADB commands will not work here, only fastboot commands.
Read this thread: http://forum.xda-developers.com/showthread.php?p=23747567
It will tell you what you need to know about the difference between the two.
If your boot logo is simply a Kindly Fire logo without an android above it then you need to install FIREFIREFIRE, else you will not be able to enter recovery with the power button.
Find the FIREFREFIRE development thread for instructions on installing.
Mac is not much different from PCs when using adb and fastboot other than driver installation, but you should already have that taken care of.
In some cases you may need to type ./fastboot ... rather than just fastboot but other than that the commands are the same.
Sent from my Amazon Kindle Fire using xda premium

TF101 Won't Enter APX Mode

If you want to offer help PLEASE read through the thread, or at least the initial post. It seems like I'm repeatedly answering the same questions that were already answered.
I've tried to boot in APX and all I get is the black screen, yet neither Windows 7 64bit/Linux Mint 64 on one PC and Windows XP on another don't detect it at all. I know the cable works because when I had CWM installed I could see it attached via ADB. I'm a b30
Edit: I managed to get the stock ROM back on it, but it still doesn't want to boot into the bootloader/APX mode. I know it's not necessary but I would like to have it as a failsafe for the future.

brando56894 said:
This all started with me wanting to go back from AOKP to stock, I flashed a rooted version of 9.2.1.17 and it kept telling me to update, but when I did it failed because CWM was installed. It also wiped my system. I found 9.2.1.24 but couldn't flash it because TWRP wouldn't stick. I tried to install the stock recovery, which worked in a sense that it removed CWM but left me with just the Android and the exclamation point (I can't seem to get past that no matter what I do [vol +, Vol -, power or any combination of those] ) I decided to use NVflash to get back to complete stock and start over.... The only problem is that Windows 7 doesn't even detect the TF when its in APX mode, hence it doesn't ask me to install the drivers, nor will they install manually.
So my TF is soft bricked and nothing works. I'm going to reboot into Linux now to see if I can get nvflash working. Any other suggestions?
Edit: Linux Mint didn't detect it either I know it's not the cable since I was able to see the TF via ADB when I had CWM installed. Also the major thing that is worrying me is will the TF be recoverable if the battery dies? I have no way of knowing if it is actually off or just in APX mode, I obviously can't do a battery pull and I can't power it down from the recovery or the OS. IIRC it also won't charge when it is in recovery and I'm assuming the same is true for boot-up and APX mode.
Click to expand...
Click to collapse
Same to me-- win7 does not recognize my tf 101- apx is installed-works with another transformer well- if i do vol down and then vol up i see the laying android with exclamation mark.
no solution till now- hope you had more luck-
By the way- try to load it normal - in my case it works.
kind regards
gandalf

I just tried connecting it to an older Dell with a P4 in it and it doesn't detect it either, it just seems like the TF doesn't want to boot into APX mode. I'm doing Vol + and Power from both the recovery and from the initial splash screen, then it reboots to a black screen which I'm assuming is APX mode. From the black screen I've tried Vol + and Power for as long as 30 seconds and still nothing. There were also times when it would sit at the initial splashscreen and then go to a black screen, then I'd try to enter APX mode from there but it would be the same thing.
I've been contemplating getting a Nexus 7, partially because I lightly stepped on the screen of my TF one night and damaged it enough to cause the LCD crystals to break (there about two or three grayish "lines" where I stepped on it) but not hard enough to crack the glass. The screen will also flicker some times on that side and will also randomly shut the screen off. Maybe this is a sign telling me to get a N7?

Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html

Rumbleweed said:
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Debug mode is for ADB, not APX. Debug mode is set in Android and with APX no Android is loaded.
I have used the live cd of Ubuntu 11.10 without installing any driver by myself. It recognized the TF with APX in my case.

There is no debug mode considering that the OS isn't installed. AFAIK debug mode is only necessary to use ADB while booted into Android. APX is something that is built in to the device. I downloaded the drivers from android.mobi which has an "unroot/unbrick" package, that doesn't matter though because Windows never asks me to install the driver so the drivers don't seem to be the problem, considering Linux (which doesn't require any drivers) doesn't see the device either.

I had the same, downloaded the drivers, but couldn't install.
After I made sure I had the correct drivers, I clicked in hardware settings on the thingy with the exclamation point, I choose manual search and had Windows search the entire c:\ drive, after a while it installed
Sent from my Transformer TF101 using xda premium

That's my problem guys. APX mode/unknown device doesn't show up in device manager

oi, than I cant help you, sorry

I think it's F'ed because I took it apart to make sure it was turned off by disconnecting the battery and then did the power and Vol+ combo but the PC still doesn't detect it.

1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok

vista1984 said:
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
Click to expand...
Click to collapse
1 & 2 It boots up to the initial splash screen and to the android recovery so the battery is ok
3. The Vol + does work unless it suddenly died because I was using it moments before I bricked it
4. I would say 30+ seconds is long enough
5. The cable does work because it charges the unit and when I had CWM installed I could see it via ADB
6. Tried another port, nothing
7. The sound is definitely noticeable and it's kind of obvious if it's not in the device manager list
8. I tired two different computers, and three different operating systems. Including Linux.
I know you are trying to be helpful but ALL of these were answered in previous posts, if not the OP.

I'm having the same issue with my pad not booting into APX, might I ask how you got the stock ROM back on it without APX?

Luckily I had the stock recovery installed and I was able to place the OTA on A MicroSD card and named it so that it would flash automatically once I booted into the recovery.
Sent from my Transformer TF101 using Tapatalk 2
Edit: here's how to do it
baseballfanz said:
Download the latest official firmware from Asus.
Extract the zip from within and rename it to "EP101_SDUPDATE.zip" (without the"" )
Put it on the root of your sdcard
Boot into stock recovery and it should flash it
Click to expand...
Click to collapse

I have to go with #5. My Transformer would charge when using my cord and so I thought it was good. Plugged it into the computer and nothing. Switch to my wife's cord and the computer saw it instantly. It was then able to see APX mode.

Yea it was actually the cord being stupid, when I got back to my house I tried my other cord and it connected just fine. I actually just sold my TF yesterday to a friend for $250 so that I can get a Nexus 7
Sent from my ADR6425LVW using Tapatalk 2

So this is making me thing that my cord is the issue, but I tried 3 different cords and none of them recognized. Is it possible the device itself has a faulty connection?

It's entirely possible, have you tried a different computer/different USB ports first though?

Tried every port on two machines as well as in linux. My HTC G2 connects just fine to everything.

You may be screwed Do you have the dock? Does it connect and charge fine with that?

[HOWTO] How to restore frimware on your device + Amazon Frimware

So if you been messing around with your fire and got to the point that it wont want to get past the loading screen or something or you may have messed up during the root process you can use these steps to restore your Fire
MOD EDIT: THE FIRMWARE LINKED HERE IS NOT SAFE AT THIS TIME, LINK REMOVED AND THREAD CLOSED.
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.

I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:

Darkside1984 said:
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Click to expand...
Click to collapse
Try installing ADB drivers in Device Manager while the Fire is in recovery. If you do it correctly, when you do ADB Devices, it should come up as Sideload.
Sent from my KFFOWI using Tapatalk

Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522053820.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)

sd_shadow said:
recheck device manager, drivers are not correct, Fire should be listed adb composite interface, when in recovery mode
Click to expand...
Click to collapse
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Looking for a miracolous hard factory reset...
EDIT: I see that the battery is low. Does this have something to do with Recovery troubles?

i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Darkside1984 said:
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Click to expand...
Click to collapse
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
Darkside1984 said:
I see that the battery is low. Does this have something to do with Recovery troubles?
Click to expand...
Click to collapse
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.

sd_shadow said:
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
Click to expand...
Click to collapse
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...

Darkside1984 said:
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Click to expand...
Click to collapse
try
Code:
adb version
---------- Post added at 12:38 PM ---------- Previous post was at 12:38 PM ----------
should get
Code:
Android Debug Bridge version 1.0.32
Revision d15680a64678-android

sd_shadow said:
try
Code:
adb version
Click to expand...
Click to collapse
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?

Darkside1984 said:
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Click to expand...
Click to collapse
try link in my Using adb post

Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!

Darkside1984 said:
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Click to expand...
Click to collapse
great
care to post some details about what worked?
Drivers version?
adb method?
Sent from my KFFOWI using Tapatalk

after side loading I needed to switch off the device and restart in order to start the final "Installing the latest software"-sequence

sd_shadow said:
great
care to post some details about what worked?
Drivers version?
adb method?
Click to expand...
Click to collapse
Sure!
I deleted my adb folder and follow the steps in your thread here. So it got the right adb version (1.0.32) and I finally could sideload properly the bin file. I think that the point is that PC just recognizes the Fire (as ADB composite) when you are into 'adb sideload' option, not in the recovery main menu.

5th Gen Kindle Fire - MT65xx Preloader problems
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.

hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238740
[HOWTO] How to restore firmware on your device + Amazon Firmware

hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.

fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
Following your comment, I ran the .BAT while watching Device Mgr. Prior to running it, I had the Android device apparently successfully installed. It had its own folder in Dev Mgr without any [!]. Running the .BAT, that disappeared and Android migrated down to Other Devices. It's now next to the same Unknown Device that I haven't been able to update drivers for.
I tried pointing both to the latest_USB_drivers zip from Shadow's recommended thread. According to Win7, it's 'unable to install' from that unzipped folder or any of the others I've pulled from various threads.

fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk

sd_shadow said:
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
With the Fire disconnected, I booted to recovery (Volume Down + Power) and got a list. Not knowing what to pick, I chose the Bootloader option. It started to boot in FASTBOOT mode. Plugged it in, went to Dev Mgr. Both Android Device and Unknown Device showing in Other Devices. Pointed the Android Device driver to the latest_USB drivers from your other thread. Windows says unable to install your Android. Tried same thing with Unknown Device. Unable to install.

q about current root method on shield tv

the current method to root the shield tv requires that you need to use a micro sd card in twrp to install root, the only problem with that is the new 16gb models do not have a micro sd card slot will it make these new models unrootable?
it seems only the new pro 500gb models will only have root at this point unless the devs can think of a work around to avoid this issue with the micro sd cards.
using a memory card reader and putting the micro sd card in there won't work either because i tried this when i attempted to root the mad catz mojo and it didn't work.
should i hold out and wait and see what the root situation is going to be for the new models first before i order the 16gb model? just incase i need to get the 500gb model instead, it would be a pain to return and refund to do that.

Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.

The slim doesn't have a micro usb port anymore either. Can adb be run through the regular usb with a male to male cable?

You don´t need a micro sd-card. Only need twrp to flash su.zip. In twrp you can use usb-drive, adb push file to internal flash oder adb sideload.

Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv

unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
Thanks for that. I am picking mine up in a few minutes and going to try and root it with a USB M/M.

unsatgoua said:
Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.
Click to expand...
Click to collapse
i'm assuming the nougat android update will have a new bootloader so all the root methods out there right now do not work with the new 2017 model.
please try and report back the results, i'm holding off buying this till we get more info on the root status.
unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
i've googled for 2 days straight to see if any new root methods have popped up but nothing so far.
will the usb a be good enough for root i wonder?

Usually nvidia has developer images available that are already rooted so maybe just flash that on the new shield when it becomes available.

Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.

So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.

You installed the drivers? Don't forget, they said one port, so try both.

unsatgoua said:
You installed the drivers? Don't forget, they said one port, so try both.
Click to expand...
Click to collapse
When you put it into ADB mode it tells you what port to use. And when I plug it into my pc it never comes up under device manager so I can't install the drivers.
Edit: That is why i'm trying a new cable since I know the port work with my mouse.

I'm surprised they didn't provide a cable to flash images.
Sent from my SM-G935T using XDA-Developers Legacy app

unsatgoua said:
Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.
Click to expand...
Click to collapse
excatly, this is why I'm holding out for now.
yojoe600 said:
So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.
Click to expand...
Click to collapse
not a good start but let us know how it goes anyway.

I have the old 16gb version and I wont be upgrading until there is a root method.

Slayerkodi said:
I have the old 16gb version and I wont be upgrading until there is a root method.
Click to expand...
Click to collapse
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.

yojoe600 said:
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.
Click to expand...
Click to collapse
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.

aVlkaFenryka said:
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.
Click to expand...
Click to collapse
Hey did you try this bit?
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
https://twrp.me/devices/nvidiahshieldandroidtv.html

If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Edit
I just retested this again, pressing the combination once, and letting the shield bootup, instead of pressing again, on boot logo image, to go to recovery, and it looks like it removed root for some reason, so bare that in mind, just incase thats normal behaviour. Ive just used the method again to boot to recovery this time to flash supersu zip in twrp, everything seems back to normal

banderos101 said:
If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Click to expand...
Click to collapse
theirs no power button on the 2017 shield.