yashsingh1/xdaforums huggingface dataset:
[Fire TV General] KLit75:
I'm not sure which device drivers? Amazon would supply them, right? And I can't think of a reason why they would....

Actually, USB debugging is now an option on aftv but I've never tried connecting that to my PC. I have adb setup on all my computers. Adb recognizes it but there are no drivers I'm aware of.

Kingroot doesn't give a fail message or anything. Is this what's supposed to happen if it can't root? Or does it just keep running like it did for me?
[Fire TV General] Calibaan:
You don´t need ADB drivers for the stick. You can connect via network with "adb connect xxx.xxx.xxx.xxx" where xxx.xxx.xxx.xxx is the actual IP of the FireTV stick.

If you´re still interested in connecting via USB have a look for this topic:

http://xdaforums.com/fire-tv/general/adb-usb-fire-tv-stick-t2952214
[Fire TV General] dk1keith:
I thought for the pc root it had to be a usb connection? I know how to connect through regular adb connection, just not the direct usb connection using the A to A usb cable. I think you need the device drivers to connect straight usb. btw I'm on the Fire TV not the Stick.
[Fire TV General] Calibaan:
Official Amazon ADB HowTo and where to get the ADB driver:

https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-over-usb

There is IMHO no relevant difference between a USB or ethernet ADB connection. Both offer the same functionalities.

It´s just more simple via USB since you don´t have to be in the same network subnet and you don´t have to search for the IP address with a system configuration menu of an Android device, so many PC tools just offer the USB ADB connection.

Concerning root on the other hand there are also in general Android devices out there which independent from ADB need also to be brought into special loader or recovery modes etc. which do only support USB and no network connection, so many root scripts are only done for USB since network connection would only work for the ADB part of the rooting procedure and not for all other stages. So it doesn´t make sense for these cases. But if for a root process only ADB is needed it is normally also possible to be done via network.
[Fire TV General] dk1keith:
Good point. I'll try it. I wasn't sure if the pc root had to be done via usb connection. I'll connect through adb and give it a shot.

---------- Post added at 09:07 AM ---------- Previous post was at 08:29 AM ----------

I ran the pc root using just adb and it appears that it didn't see the device. Hard to tell what it was doing though since it is in Chinese. It does seem that it has to be connected via usb for kingroot to see the device.
[Fire TV General] KLit75:
Just for my own knowledge--how would you run this PC program over adb to the aftv?

Thanks for the info. It sort of supports my thought that this version of kingroot won't work. The PC version supposedly reboots your device several times during the process. Doesn't it need fastboot to do that? If so we don't have it on devices over 51.1.4.1 because amazon took it away.
[Fire TV General] Calibaan:
I´m not certain what do you ask exactly but I personally don´t use KingRoot for several reasons whether the PC tool nor the regular one so I can´t help you with that. But at the end it´s up to the KingRoot PC tool itself if it can use a already (manual) established ADB connection or when it tries to control or establish the ADB connection on its own to offer the network option additionally to the standard USB way.

If it´s concerning installing the ADB driver for USB connection this is done just like every other driver installation on Windows.

ADB is just more or less a sort of transport layer for some minimal action (ADB = Android Debug Bridge) like file copy, APK installation and a bash like shell etc. Not really a complicated big deal for a PC tool or even BASH/BATCH scripting for programming a ADB control via network or USB.

So its just up to the PC tool to do it right and there should be nothing special done by the user except installing a correct ADB driver if connection is done via USB but also this could be done by the PC tool itself...

At least I would be glad if KingRoot would work to see how its done and which would allow to create an alternative (open and easily comprehensible) root but I don´t believe for a root solution from this corner.

I don´t know what the PC Tool exactly does but I wouldn´t be surprised if it just does install the regular Android KingRoot APK and runs it silently from ADB shell so the root mechanism would be exactly the same regardless if started manually on the device itself or launched from PC.

My bet is that KingRoot will only work from the day on with the aTV (stick) when already a free (open) root is found by others. Just my2pence.....
[Fire TV General] dk1keith:
All very good points. I'm still holding out hope that kingroot may give us root or as mentioned give us an alternative root method. Seems weird that the Fire Phone, HD 6/7 and the HDX all have gained root from kingroot. I do understand that they are different devices on different firmware. Just seems so close...lol The one thing I haven't seen is where someone did a Factory Reset on the Fire TV and tried the apk root. I know they have tried and failed with the Fire Stick.
[Fire TV General] Calibaan:
Although it is called "FireOS" for every Amazon device and although its based on Android I don´t think they´re runnig completely on the same base. Generally FireOS and Vanilla Android do differ since Amazon has another scope for their products so they did more than just fork Android and replace the launcher and appstore with their own variants.

The FireOS is my opinion splitted in at least two branches: phone and tablets is one branch and FireTV/Stick another one. There might be even more branches of Android for other product families like the Echo or the newer Kindle devices.

That might be the reason why phones and tablets are rootable since their OS branch still has the default android vulnerabilities and the FireTV(Stick) not since maybe this fork is already too different to Vanilla Android and therefore the default (known) vulnerabilities do not show up here and thats one strong point why I think KingRoot will also fail in future achieving a root here.

I´ve seen many topics where people show up with new root exploits for other Android devices but no surprise that until now all of them do not work on the FireTV due to the big differences to Android. So a working root must be found especially for these FireOS versions or with very much luck a generic root eploit shows up which is also still in FireOS not fixed.

Despite of a software based root the hardware root is of course still possible and chapeau for the idea to access the flash filesystem directly.
[Fire TV General] Sizzlechest:
FYI, there's a new kingroot (4.1). No idea if it matters.
[Fire TV General] Calibaan:
I don´t think so since there are no real release notes or infos regardig FireTV on their homepage.
[Fire TV General] dk1keith:
I tried 4.1 multiple times and got the same result as previous versions. I guess for me if I reset my Fire TV and try 4.1 with no success that will be all I may be willing to try. Great explanation of the differences by the way. Thanks for that.
[Fire TV General] bradwatson:
Thanks! This worked for me.
[Fire TV General] Diet-Coke:
Since when does this method work on the FireTV?
[Fire TV General] gamer765:
Efuse was about downgrading after upgrading to a new bootloader. When you upgraded, the fuse was blown and downgrading would cause a brick. Or something along those lines. Idk
[Fire TV General] bradwatson:
It worked on the Razer Forge TV.
[Fire TV General] Calibaan:
That doesn´t mean this works also for the FireTV or FireTV Stick and of course it doesn´t work. As I said before a working root should be especially confirmed for the actual FireTV FireOS versions so reports of other devices getting rooted with this whatever KingRoot stuff isn´t really helpful in the FireTV forum section... So please folks stay on topic.
[Fire TV General] porkenhimer:
If you would take 20 seconds to go read my first post on this thred, I said Kingroot didn't work on the Fire TV. I only made this thread because I kept hearing about Kingroot for a few weeks, and I knew people on the Fire TV forums were eventually going to hear about it because it seemed like every tech artical I was readiing was commenting on Kingoot so it was just a matter of time before others heard about it as well. So I informed them that it did not work to save them time and heartache. Like with all threads, they sometimes turn into something they were not meant to turn into. I did not intend to turn this thread into what it has turned into, but at the same time, I am glad it has turned into a place for people to talk about how we can get newer frmwares rooted. Thats what forums are for, to share ideas and opinion. I know the mods on here like to constantly tell people to stay on topic, but the true meaning of a forum is to take things in all directions as long as it goes with the essence of the thread. You can't talk about peanut butter for too long without mentioning jelly, and you can't talk bout Kingroot not working without what we can do to get it to work. I think we have established that Kingroot does not work, and I for one think it will never work on the Fire TV, but I hope this thread sparks some devs to get interested in achieving root on newer firmwares for the Fire TV. This thread is as welcome on the Fire TV forums as any other thread on the Fire TV forums. And for reasons I stated before, this thread is hugely helpful, cause I do not see anyone else even talking aout getting the Fire TV rooted. You do not have to like this thread or the content involved, but all comments are welcome here, including yours. If you want to mention another device on this thread, feel free to do so as long as it has something to do wiith Kingroot or getting the Fire TV rooted. I say this because theres proably a 99% chance that the method we use to root newer firmwares is gonna come from an exploit found on another device.
[Fire TV General] Calibaan:
Why do you think my last post was especially related to you as thread starter? It was related to the LAST topics and not to the BEGINNING because it´s irritating now to read again and again that root does work (which is more than confirmed that it doesn´t) but it is meant for other devices. Again, this isn´t helpful and at least people should add the information for which device the root did work to be more clear.

So would you care about your own advice and take 20 seconds of time and read the topics in a chronologically way...
[Fire TV General] porkenhimer:
I know exaactly what your post said and what you were trying to convey, but this site nor this thread does not revolve around you. If people want to talk about Kingroot working on other devices its totally fine, cause it may end up helping in the long run. Don't you realize that most devices are rooted off of exploits found on other devices? Like I said, all comments are welcome on this thread as long as they are about Kingroot or rooting the Fire TV. If you do not like the things being said on this thread and are tired of hearing it, there are thousands of other threads for you to go to. There is no reason for you to get mad at anyone on this thread, cause nobody is harming you or being rude to you. We all don't like to hear that Kingroot works on other devices and not the Fire TV, but most of us are mature enough to not say rude things about it or even get mad about it. Yes it sucks that Kingroot does not work for the Fire TV, but there is nothing wrong with anyone saying it works on other devices, cause they were not being rude in the least when they said it, they were just stating the fact that it works on their device.

Kingroot will proably never work on the Fire TV, at least while we are stuck with Android 4.2.2, and I think that is what most people do not get, Amazon has our devices tightly secured cause they have locked down Android 4.2.2. They have fixed any exploit or security breach that could have been used to obtain root. I honestly think our best hope of getting a newer firmware rooted is by Amazon moving away from Android 4.2.2, but until then I do not see it happening, and II think that is the reason that devs do not seem interested because they know its not gonna happen as long as we are stuck with Android 4.2.2. We gotta be patient and see what Amazon gives us to work with, cause they wil eventually have to upgrade to Android 4.4+, and I believe thats when we will get root back. Wait and see, when we finally get upgraded to 4.4 you will start to see devs commenting on rooting again.
[Fire TV General] Calibaan:
I saw already some other topics where you "discussed" with other folks this way, so yeah, whatever you think...

And concerning a FireOS migration to Android 4.4+ this might be still not the solution since it is not a guarantee that Amazon does not fix all already known root vulnaribilities as they already did on their actual Android base for FireOS for the FireTV. There is no reason for them not to fix the leaks and Amazon seems very interested in preventing root. So the best chance would be a real (until now) unknown new vulnaribility but this could also happen with Android 4.2.
[Fire TV General] porkenhimer:
I am not sure what way you think I "discussed" something with you, but I apologize if you took it wrong. I was not mad in the least, you just took it that way. I actualy thought it was funny for you to get mad at someone for saying Kingroot worked on their device. I got more to worry about then your feelings or anything you say to others, cause to me you're a pee-on. I was simply letting you know that people are free to express their opinion and give comments as they choose, on this thread.

Also, I never said that 4.4 was a guarantee, I said it is our best chance of getting devs interested again, and the best chance we have of obtaining root again. When devs are not interested its not gonna happen. If 4.4 or higher would come along it would breathe new life into our devices and gets devs interested in trying new things. Sure it could happen with 4.2.2, but its not likely. Go back and look through the forums, devs used to comment all the time on the Fire TV, but that slowly stopped a couple months back. There are still devs doing little things like making modules for exposed, and getting things like wallpapers working, but nothing major like working on root. That will change if we can get Amazon to upgrade to 4.4+. I already messaged Amazon a while back and they basically said Android 4.4 come in the future. Maybe we can get a lot of people to message them about 4.4 and it might speed things up.

If you keep trying to start an argument I will have this thread closed. I am not mad at you, I did not say anything wrong to you. Now leave me alone and as you said "stay on topic". There should never be anyone getting mad over having or not having root, period.
[Fire TV General] Calibaan:
Whether did I get mad since I argued based on facts nor did I get impolite and insulting like you (I will quote you here with your "pee-on" insult ) which is exact that what I meant with your way to "discuss".

Of course you can "discuss" further this way, and I quote again, by "I will have this thread closed" (ask a moderator for that) but I will be still here in forum hanging around to discuss issues about the FireTV in an objective manner without getting insulting or impolite. ;)
[Fire TV General] porkenhimer:
I am not on XDA to argue over nothing. I told you what was gonna happen if you did not leave me alone.

Mod, I AM USING MY OP RIGHTS, PLEASE CLOSE THIS THREAD.
[Fire TV General] dk1keith:
Finally.....Maybe now we won't have to listen to your ignorant bs. And yes it is me....the one you suggested should "grow up" I tried to be the bigger person and not respond, but for you to suggest that you will close this thread because people refuse to tolerate your ignorant rambling crap was just too much for me to ignore. You seem to be on this forum to do nothing more than get into conflict with people. I for one am not one of those people. Then you have the audacity to act like you're a victim. How laughable.

To the moderators I say my humble apologies for what I'm sure is a violation of the rules. What ever action you take as a result of this post is understandable and respected.
[Fire TV General] captainjapan:
Can we get an XDA mod in here to shut this thread down?
[Fire TV General] KLit75:
I second that! I'd say this thread took a bad turn but actually it veered off the tracks awhile back...

I don't have time (nor the patience) to sort through all this but I think it's ridiculous. I keep coming back because people keep posting (hoping there's something relevant) but it always dissapoints.

Kingroot does not work on aftv or stick. If that changes somehow maybe someone could start a new thread with a simple guide (probably necessary since its not in English.) At the risk of sounding hypocritical... can we please stop with the comments that bring no new info? If people want drama and petty insults there are plenty of other sites to go off to...
[Fire TV General] Mr. Clown:
Can we stop the bickering? [MENTION=1694289]porkenhimer[/MENTION], please be careful about your language and how you address other members.

I will not like to see another argument between both of you. Consider this as a friendly warning.

Thread closed by OP request.
[Galaxy S III Q&A, Help & Troubleshooting] versatileengr:
I had Samsung Galaxy S3. I have an issue in volume controlling from left side button. Lowering volume button is functioning but volume highering button is not functioning. Is it any problem with hardware or its an issue of software. The volume controls through touch system.
[Galaxy S III Q&A, Help & Troubleshooting] Beaner:
It's a hardware problem,

Replace the buttons.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rockky:
hey

I bought a W6 Cavalier as a second phone to my Hermes

.....same hardware as the 'Breeze'...whose wiki suggests compatability with Hermes upgrading tools.

To what extent do you surmise can I upgrade radio's, spl, and customized roms.

thanks.

to what extent can I
[Nexus 5 Q&A, Help & Troubleshooting] doyinosin:
Hi,

I woke up yesterday to find out my Nexus 5 screen was not displaying properly. The only possible clues I have to what may have caused this are either:

1. Magnet damage from my laptop after leaving the phone on my laptop all night

2. The drop the night before. It was barely a two-foot drop that was not so bad. I'm hazy on whethe I looked at a good screen display after the drop.

I doubt it's a software issue because I also tried a factory reset and it's the same. Besides, even the bootloader is distorted. Just in case, I am running Android 5.1.1.

Please can anyone help me figure out what might be the issue hee and if I need to replace the screen?

I'll also need info on recommended places to order a new screen online, preferably, an Amazon seller.

I have attached images.

Thank you. Cheers
[Nexus 5 Q&A, Help & Troubleshooting] AndreIrawan97:
Yap, same thing happens to me... It seems that MY problem was the logic board.. But they told me that it's because of damaged bootloader...

When it's clearly not...

Try to send it to LG service center... BUT, to claim your warranty, re-lock your bootloader, reset your tamper data, and flash stock rom
[Samsung Galaxy Core.] vova82:
Hello everyone,I have installed root and supersu with framroot and now I want to do a factory reset.How should I do it.Do I need to uninstall root with framaroot and then do a FR,or just simply do a FR?
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicoE.:
hi, i have a question, i hope you help me. ok, i back up my pit file when my phone is on kitkat firmware, im wondering if this pit file i back up before in kitkat is compatible with lollipop firmware? :confused: because im getting fail(size) in odin. it is possible to flash kitkat pitfile together with a lollipop firmware? thanks.
[One (M8) Q&A, Help & Troubleshooting] micks_address:
Hi folks,

Got notification for the above update on my m8 last night. So downloaded and rebooted. Went into custom recovery and asked about a system file.. and selected ok.... with the power button but update didn't install just rebooted phone..

My phone was rooted and i converted it from stock sense to GPE edition rom.

Had to unroot to get work email app working on the phone..

Any suggestions on how to get this update installed?

Cheers,

Mick
[One (M8) Q&A, Help & Troubleshooting] ceyhunca82:
Hi, i have similar problem. My phone is rooted Twrp. My current rom is official 5.01. When i tried to download and install updates, twrp console is appearing and update doesn't install. How can i delete this Twrp console? I think many user have same problem.

Thank you.
[One (M8) Q&A, Help & Troubleshooting] larry419:
Android L-MR1 Upgrade won't install

Same problem here. Keep getting the notifications. When given permission to install it reboots into TWRP. Unable to install the update.zip from within TWRP as expected. Guess I'll watch for somebody to figure it out. :rolleyes:
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
OTA updates require stock recovery to install. Find your stock recovery in the thread sticky at the top of General forum and flash with fastboot.
[One (M8) Q&A, Help & Troubleshooting] larry419:
stock recovery

Does flashing the stock recovery erase contents or just change the recovery app ?

Thanks
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Recovery isn't an app. It's a partition that contains the recovery console. And no, flashing a recovery won't wipe anything, except the old recovery console.
[One (M8) Q&A, Help & Troubleshooting] larry419:
Recovery Console

I have rooted and used a few phones and roms but am no expert by any stretch of the imagination. This issue is perplexing.

I understand that the L-MR1 OTA update will not install with TWRP and requires the stock recovery. I downloaded what I thought was the correct recover image and have successfully flashed it but the update will still not install.

Here is what I have...... Is there a specific recovery image that is needed and if so which one ??

Model: HTC6525LVW HTC M8

VERSION 5.01

BASEBAND: 0.89.20.0321

KERNEL: 3.4.0-Elite-g06e8525

Build: Digitalhigh GPE LRX22c.H5 release-keys

Unlocked S-Off

CID-VZW__001

HBOOT 3.19.0.0000

RADIO 0.89.20.0321

I used 2.23.631.2 recovery.img.

Thanks in advance for any help.
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Dude...

Besides the fact that you are S-off, and can just flash a Verizon firmware package to update the easiest way there is (that's my favorite part of being s-off), there are RUUs available for all US carriers.

Search for a verizon firmware.zip and enjoy the freedom of S-off. Download it and flash it and don't lose any data. S-OFF FTW!
[Galaxy S 4 Themes and Apps] HplarIV:
I found this and it really works so im sharing it here.

Please make a back up before Flashing/replacing your File.

You can either flash via custom recovery or just copy paste the file

in system/etc folder

ORIGINAL Thread :

http://xdaforums.com/galaxy-s4/i9506-develop/mod-volume-boost-tw-lollipop-t3106106#post60688242

TESTED on Galaxy S4 E330L LTE-A 5.0.1

If you are having issue with your Mic after flashing the file in the original thread try my newly moded file attached below. It will fix your mic enjoy Playing Music!

Im not the owner/creator of this MOD so Thanks to the real creator.
[Galaxy S 4 Themes and Apps] erikasnoske:
Thanks, buddy. I would suggest to give a try to Viper4Android, which can increase speaker volume and headphones volume separately. Only for Android L, AOSP and AOSP based ROMs :good:
[Galaxy S 4 Themes and Apps] HplarIV:
Thank you for your suggestion but i dont think it will work on E330L

* Uploaded newly moded File with microphone fix.
[Galaxy S 4 Themes and Apps] kimiraikkonen85:
The thread link given in that thread seems closed due to microphone failure.

An other working patch for S4?
[Galaxy S 4 Themes and Apps] leboreiro:
Hola