[Q] Can the Kindle Fire be rooted without using a computer? - Kindle Fire Q&A, Help & Troubleshooting

Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!

No

Thanks for the info

I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.

soupmagnet said:
I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.
Click to expand...
Click to collapse
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."

kinfauns said:
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."
Click to expand...
Click to collapse
Well, if you have adb on your device and you enter "adb root" from a Terminal, it will start the adbd server as it would on a computer but returns "error: device not found", obviously because it doesn't detect a device connected to the USB.
Presumably, if you had another device tethered to the one you want rooted, you could, with USB debugging enabled, start an adbd server from the first device and "adb root", "adb remount", etc.
The problem with that is the "adbd cannot run from stock devices" garbage. I'm sure there's a way around it though.
[Edit:] Oh and...it was the egg.

Duplicate post. Deleted. Damn XDA app!

soupmagnet said:
[Edit:] Oh and...it was the egg.
Click to expand...
Click to collapse
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
[Edit:] Besides, who's to say it can't be done with fastboot?

soupmagnet said:
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
Click to expand...
Click to collapse
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.

kinfauns said:
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.
Click to expand...
Click to collapse
Hitler.
Hey, you were right!
Back on topic...If only I had a USB micro to USB micro cable to test it out with...
I think fastboot is the way to go.

soupmagnet said:
[Edit:] Besides, who's to say it can't be done with fastboot?
Click to expand...
Click to collapse
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!

kinfauns said:
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!
Click to expand...
Click to collapse
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi

soupmagnet said:
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi
Click to expand...
Click to collapse
"Exponentially" is reaching a bit, but point taken. He doesn't explicitly exclude the possibility of attaching another android device. I'll concede that point.
However, he does say he tried using some app and asks if there's another app that would do something similar for the Kindle Fire... and that at least implicitly supports my view of the OP.
Whatever the case may be... I don't think this debate needs to go much further. We've already invoked Godwin, so it should have ended already.

kinfauns said:
We've already invoked Godwin, so it should have ended already.
Click to expand...
Click to collapse
I secede to your geekiness

there is a way
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.

of course it can!
Yes.. just download rootmaster

Of course it can!!!!
thacoolestnerd said:
Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!
Click to expand...
Click to collapse
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.:laugh:
---------- Post added at 02:06 AM ---------- Previous post was at 01:58 AM ----------
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process. Use rootmaster first(the one that is not ceskas,) it will start rooting the device until it gets to 50 percent and says you need to finish the root with te computer.. but when you use the other app.. it finishes the rooting process. But every time you open an app that requires root permission.. it asked for root permission to run the app. Just press the right button when the ceskas menu pops up..( it will be in a different language)[email protected]
This will also work on the s4 and any kindle base platform including hd, hdx, and it should work on the paper white.

Related

[Solved] Question: How to root MyTouch Slide using OSX?

wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed

Found why adb not recognizing some 6.2.2 kindle's

My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
THANHVO31 said:
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
Click to expand...
Click to collapse
That link you posted doesn't use my same ids
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
EDIT: and I made a huge mistake and i had not put in the bootloader (FIREFIREFIRE) on my bricked kindle, however, I took extra precaution and put it on my working kindle and to prevent it even further I am not using any roms and only using GoLauncher EX, googleframework, Superuser(root), and Market
as some roms are unstable and ALWAYS have a problem that something is not working correctly!
umarsl said:
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
Click to expand...
Click to collapse
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Th3-Chronikk said:
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Click to expand...
Click to collapse
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\Vid_1949&Pid_0006&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006
Click to expand...
Click to collapse
And try again.
Goodluck
THANHVO31 said:
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
And try again.
Goodluck
Click to expand...
Click to collapse
Didn't work
Th3-Chronikk said:
That link you posted doesn't use my same ids
Click to expand...
Click to collapse
The hardware IDs in that link look identical to yours, and I think every other Kindle Fire I've seen. Yours don't look unusual.
I'm having the same damn issue, my 6.2.2 kindle is not recognized by adb. The weird thing is that sometimes it does see the device and then it disappears? The driver ID's that are posted are identical to the ones that are included with KFU.
If anyone figures this out please let me know!
Troy.
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
p-niiice said:
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
Click to expand...
Click to collapse
android update adb
add 0x1949 on its own line to adb_usb.ini in C:\users\<username>\.android\adb_usb.ini
save the file
adb kill-server
adb start-server
adb devices
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
jcc2z said:
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
Click to expand...
Click to collapse
Thanks - doing this plus the hardware ID lines earlier in the thread got me further, but adb still isn't picking up the composite device.
androidcues said:
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Click to expand...
Click to collapse
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
K3nDroid said:
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
Click to expand...
Click to collapse
Interesting that you had such an issue with getting windows to work. I have rooted 2 Kindles(took an hour total to get them set up, rooted, recovery and Gapps installed), Samsung Epic 4g, Multiple Evo 4gs, Optimus M, Hauwei Ascend, and HTC Hero and never had an issue with drivers or having to uninstall them. I am running Windows 7 and each one I plug in it recognizes.

[Q] KFU :( Just don't get why??

OK.....
Read all the posts, stickys, and other relevant info, and have NO IDEA why I cant get KFU to see my KF!!
Finally got the Computer to see KF as "KINDLE (E)", shows as "Android Composite ADB Interface"...
KF goes to the USB screen very nicely...
Still getting "ADB Status: Offline;Boot Status: Unknown..... (0.9.6)
Pretty sure SDK is configured correctly...
Really dont want to have a dual boot machine JUST to use "Soupkit"..
Is there anyone out there in XDAland who can help me accomplish getting access to this KF so that I can free this machine??
:crying:
http://forum.xda-developers.com/showthread.php?t=2179748
Oh and you don't need a dual boot setup to run Linux for the SoupKit. All you need is a USB flash drive and the ability to follow instructions.
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Oh and you don't need a dual boot setup to run Linux for the SoupKit. All you need is a USB flash drive and the ability to follow instructions.
Click to expand...
Click to collapse
Ya...... I'm pretty intelligent but not too technical. Reading the link just confused me more. I understand this is a developers site, however basic noobs like myself , don't really get what you are trying to point out.....sorry.
Is there a "KFU for DUMMIES" I missed somewhere? I just want to root this KF, don't even care if it is/is not a one-click solution. I just need clear, concise, easy to follow, non technical instructions from someone who is more informed about this process than me. PLEASE HELP!!
And please don't misunderstand, I have jailbroken iPhones, rooted other pads and phones, even turned a color Nook into a pad... This KF however, is........... frustratingly not so simple.....
If your looking to run a distro of Linux temporarily try this:
http://www.ubuntu.com/download/help/create-a-usb-stick-on-windows
Its a fairly straight forward guide on booting Ubuntu from a USB
mv1609 said:
Ya...... I'm pretty intelligent but not too technical. Reading the link just confused me more. I understand this is a developers site, however basic noobs like myself , don't really get what you are trying to point out.....sorry.
Is there a "KFU for DUMMIES" I missed somewhere? I just want to root this KF, don't even care if it is/is not a one-click solution. I just need clear, concise, easy to follow, non technical instructions from someone who is more informed about this process than me. PLEASE HELP!!
And please don't misunderstand, I have jailbroken iPhones, rooted other pads and phones, even turned a color Nook into a pad... This KF however, is........... frustratingly not so simple.....
Click to expand...
Click to collapse
In this particular case, though it may have come across differently from your perspective, I wasn't trying to be rude. Setting up a LiveUSB for booting Linux is really pretty easy. And like I said, the only requirement is a USB flash drive, and the ability to follow instructions. There's really nothing technical about it.
The problem with KFU on your end, is that you don't have communication with ADB, which is a necessary requirement for that, the SopupKit, and pretty much everything else. Setting up ADB in Linux with SoupKit is considerably easier than in Windows with KFU, but if you want to try and get ADB working in Windows, the thread I linked to in my previous post will hopefully show you how.
In either case, you are going to have to pay attention and follow instructions.

Fire Tv 3 4k root or downgrade

First I'd like to say Thank you to all of the people that help us that don't know how to create these mods. I have a new Fire tv 3 4k (at least I think thats what they call it) that has firmware Fire OS 6.2.1.2, Fire Tv Home Version 6.0.1.2-006. Is there a way to root or downgrade the firmware so I can start playing around with the new toy? Thanks in advance.
Nope.
Block updates, wait, and hope. I don't know if anyone is trying to root it. I have tried kingo / king root and no luck. What are you looking to do? You can still side-load apps....
Michajin said:
Block updates, wait, and hope. I don't know if anyone is trying to root it. I have tried kingo / king root and no luck. What are you looking to do? You can still side-load apps....
Click to expand...
Click to collapse
I haven't looked into how to block the updates, but will. I would like to try the v4 "LazyLeanback".
Except that wont work with FireTV 3 at all. Its also very dangerous and stupid to try to use a root tool for something it is not meant for. That's how you break things.
BRICK0044 said:
I haven't looked into how to block the updates, but will. I would like to try the v4 "LazyLeanback".
Click to expand...
Click to collapse
There are forums to explain how to block updates via adbshell. LazyLeanback won't work because it is on a different version of android. The LazyLeanback seemed buggy to me on my fire tv2. I would recommend a Android TV device if you want to go the google TV way.
I have never had an issue with attempting "Universal" root tools, but usually they don't work on updated devices. The fire stick and fire TV were both rooted via universal root tools. That being said there is risk of bricking when attempting root.
Thanks for the replies.
I can't seem to find how to stop updates on my fire tv 3rd gen. Can someone point me in the right direction? Thank you
BRICK0044 said:
I can't seem to find how to stop updates on my fire tv 3rd gen. Can someone point me in the right direction? Thank you
Click to expand...
Click to collapse
You'll need to connect with adblink first:
http://jocala.com/
Then run this windows batch file to block updates:
https://github.com/pwntrik/firetv/blob/master/scripts/ftv0_disable_ota_5242.bat
pwntrik said:
You'll need to connect with adblink first:
http://jocala.com/
Then run this windows batch file to block updates:
https://github.com/pwntrik/firetv/blob/master/scripts/ftv0_disable_ota_5242.bat
Click to expand...
Click to collapse
I tried to adb the bat file but get an error "ftv0_disable_ota_5242.bat: not found
I have tried dragging the bat file into the adb shell and get the error
also tried to apply each line separately but get the error.
could it be that the bat file is for an older firmware?
Open a shell from adblink (make sure you are connected to the fireTV) then run....
adb uninstall -k --user 0 com.amazon.device.software.ota
adb uninstall -k --user 0 com.amazon.device.software.ota.override
It is possible that these were blocked on the latest updates, i haven't tried the newest.
BRICK0044 said:
I tried to adb the bat file but get an error "ftv0_disable_ota_5242.bat: not found
I have tried dragging the bat file into the adb shell and get the error
also tried to apply each line separately but get the error.
could it be that the bat file is for an older firmware?
Click to expand...
Click to collapse
First you have to connect with ADBLink to your device. Then once you're connected you'll have to run the .BAT file from a Windows CMD.exe terminal. If you're not using a direct cable connect remove the -d flag from "adb -d"
self signed CA cert
is there any way to import on Fire TV 3 self signed CA Cert?
Just got one for $35 on the DirecTV Now deal. I wan't to put YoutubeTV on it but knowing the spat between Google and Amazon IDK if it is possible to sideload. Is it or is a full root the only way?
Sammy201 said:
Just got one for $35 on the DirecTV Now deal. I wan't to put YoutubeTV on it but knowing the spat between Google and Amazon IDK if it is possible to sideload. Is it or is a full root the only way?
Click to expand...
Click to collapse
Sounds like you did you not read in the prior posts that AFTV 4K isn't designed for that and if you're looking to root get a an Android set-top box instead... Rooting a AFTV 4K will prob brick the thing.
Michajin said:
Open a shell from adblink (make sure you are connected to the fireTV) then run....
adb uninstall -k --user 0 com.amazon.device.software.ota
adb uninstall -k --user 0 com.amazon.device.software.ota.override
It is possible that these were blocked on the latest updates, i haven't tried the newest.
Click to expand...
Click to collapse
Picked up a Fire TV 3. Connected via ADB, can't block the updates anymore.
Failure [DELETE_FAILED _INTERNAL_ERROR]
Fire OS 6.2.1.2
Now its possible to root fire tv needle!
Sinjz said:
Picked up a Fire TV 3. Connected via ADB, can't block the updates anymore.
Failure [DELETE_FAILED _INTERNAL_ERROR]
Fire OS 6.2.1.2
Click to expand...
Click to collapse
I presume you've found no way to block updates since? Perhaps Amazon finally won the battle?
I havent had any luck with any adb command methods
Michajin said:
Block updates, wait, and hope. I don't know if anyone is trying to root it. I have tried kingo / king root and no luck. What are you looking to do? You can still side-load apps....
Click to expand...
Click to collapse
I just want to TeamViewer or remote into it. Not seeing any way of doing that without root. Even a screen view from a computer will do it for me.

[FireTVStick4k] Updated Info November 2019

Hi everyone, it's been a long time! I used to be into this stuff back when I got my original Fire TV Gen 1 Box and rooted it etc. I still have been rocking it but it's slow and like half rooted ( unlocked but not root). Got a great deal on a FireTv4k stick on amazon for $25
Rumor has it that Black Friday will have this price as well and we can expect a LARGE influx of new firetv users posting. the same questions I had about the state of Rooting, KODI, Custom Launchers etc. This information is by NO MEANS exhaustive, and is just what I gathered in the last few hours of research and getting things up and running.
*Do I need to Jailbreak/Root my new fire tv?*
Honestly, probably not. Jailbreaking, or rooting as. we call in android world is really not AS useful as many think. It allows for much deeper customization however for what most people are looking for ie. KODI/Sideloading APK's a root/jailbreak _IS NOT REQUIRED_. This link will explain how to turn on developer tools and 3rd party apps. and how you can load KODI on to your fire tv without rooting.
https://www.tomsguide.com/us/how-to-install-kodi-fire-tv,news-25115.html
*2. Can I Root My Fire TV*
If you still want to root/jailbreak, for whatever reason. Some devices can and some devices cant be rooted. The firetv4k stick can be rooted. However it's not for the faint of heart and required removing the casing, shorting out some leads on the electrical board and having a linux machine handy. Not really worth it in my opinion.
3. Can I put custom launchers on my fire tv so I don't need to look at all the ads on the amazon home screen.
YES you can! the method that worked for me today ( 11/20/2019) was using Lean Back Launcher Instructions found in the first post here.
https://forum.xda-developers.com/fire-tv/development/app-leanback-launcher-fire-tv-t3750451
BUT on page 18 user @tsynik was kind to update a long dead project for 4k fire tv's at this link https://github.com/tsynik/LeanbackLauncher
the finally piece of the puzzle is to get it so that when you press the HOME button on your remote, it goes to this new , less cluttered launcher. To do that we need LauncherHijack. Also another app that seem's to have not been updated in a while. Thankfully I came across a post on git hub with instructions to get it working https://github.com/BaronKiko/LauncherHijack/issues/52#issuecomment-504738320
I personally ended up not even using Leanback Launcher in the long run. Instead I used the LauncherHijack and set it to KODI.....that way every time I press home I get put back to kodi. I then used the theme AMBER to create a custom menu in kodi that links out to the official NETFLIX/HBO GO,YOUTUBE apps.
I hope this helps a few of the newbies coming in here. Feel free to ask questions and I'll try my best to answer. But be warned im not super technical.
Thanks!
The whole bit about the launchers is outdated for the 4k stick at least. That method now results in a voice overlay on almost all streaming apps. No fix has been found yet.
JUSTINMARMER said:
The whole bit about the launchers is outdated for the 4k stick at least. That method now results in a voice overlay on almost all streaming apps. No fix has been found yet.
Click to expand...
Click to collapse
really? Can you give me an example of an app that does that? I haven't run into this error yet using KODI,Youtube APK, Netflix APK, and HBO GO Apk.
Are you sure you are using the updated leanback launcher for fire tv 4K that I linked to?
Sure, if you go back to the thread that's all about that LauncherHijack
https://forum.xda-developers.com/fire-tv/general/launcher-root-launcher-hijack-v4-t3877467
You'll see a bunch of us crying about it.
JUSTINMARMER said:
Sure, if you go back to the thread that's all about that LauncherHijack
https://forum.xda-developers.com/fire-tv/general/launcher-root-launcher-hijack-v4-t3877467
You'll see a bunch of us crying about it.
Click to expand...
Click to collapse
That's interesting. I have not had this issue. I seem to maybe used launcher hijack V 3? along wit hate git hub REPACK and Settings File.......can you try that and tell me if you get the same results?
I have attached the two files I use. Install Hijack, Then Install Debug, Launch Debug First, Then Launch Hijack
Dxfan227 said:
That's interesting. I have not had this issue. I seem to maybe used launcher hijack V 3? along wit hate git hub REPACK and Settings File.......can you try that and tell me if you get the same results?
I have attached the two files I use. Install Hijack, Then Install Debug, Launch Debug First, Then Launch Hijack
Click to expand...
Click to collapse
Do I need to run any ADB commands?
Dxfan227 said:
really? Can you give me an example of an app that does that? I haven't run into this error yet using KODI,Youtube APK, Netflix APK, and HBO GO Apk.
Are you sure you are using the updated leanback launcher for fire tv 4K that I linked to?
Click to expand...
Click to collapse
Can you confirm you have done this on the latest 4K firestick ? The one that has the ADB Shell as "mantis"
When the follow the process:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
All works great, except when i open Youtube / Netflix , i get the voice view / narrator telling me whats on the screen !
Please let me know
JUSTINMARMER said:
Do I need to run any ADB commands?
Click to expand...
Click to collapse
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
Intenti0n said:
Can you confirm you have done this on the latest 4K firestick ? The one that has the ADB Shell as "mantis"
When the follow the process:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
All works great, except when i open Youtube / Netflix , i get the voice view / narrator telling me whats on the screen !
Please let me know
Click to expand...
Click to collapse
That's interesting you're the second individual in this thread with this issue.
The firestick 4k was ordered from amazon directly just last week. I assume it's "mantis". I have been using YouTube and have no overlay voice. Just regular app experience.
JUSTINMARMER said:
The whole bit about the launchers is outdated for the 4k stick at least. That method now results in a voice overlay on almost all streaming apps. No fix has been found yet.
Click to expand...
Click to collapse
Hey man,
after suffering with the voiceview issues for weeks, i've finally managed to fix it !
All, I did was a factory reset of my 4K firestick and the repeated the install steps:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
and i have no more narrator nonsense !
Intenti0n said:
Hey man,
after suffering with the voiceview issues for weeks, i've finally managed to fix it !
All, I did was a factory reset of my 4K firestick and the repeated the install steps:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
and i have no more narrator nonsense !
Click to expand...
Click to collapse
I'm glad I could help ( What little I did LOL). Hopefully others will find this thread useful who had the same voice over issues as well as new fire TV 4k members coming from the BlackFriday Deals.
One other thing I did, and I'm not sure if it even does anything, is restrict amazon updates at the router level. It's pretty unreliable obviously but I figured it couldn't really hurt to do this.
Intenti0n said:
Hey man,
after suffering with the voiceview issues for weeks, i've finally managed to fix it !
All, I did was a factory reset of my 4K firestick and the repeated the install steps:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
and i have no more narrator nonsense !
Click to expand...
Click to collapse
I haven't factory reset yet, but I will try when I get off work and report back. Thank you for your help.
JUSTINMARMER said:
I haven't factory reset yet, but I will try when I get off work and report back. Thank you for your help.
Click to expand...
Click to collapse
there were some comments that you should uninstall the old version of LauncherHijack before the using the new one I linked. Maybe try that first before the full factory reset.
Intenti0n said:
Hey man,
after suffering with the voiceview issues for weeks, i've finally managed to fix it !
All, I did was a factory reset of my 4K firestick and the repeated the install steps:
1. Install debugfile (settingstest apk)
2. Install launcherhijack
3. Run adb command - adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
4. Start the settingstest app, which automatically starts hijackthis.
and i have no more narrator nonsense !
Click to expand...
Click to collapse
Dxfan227 said:
there were some comments that you should uninstall the old version of LauncherHijack before the using the new one I linked. Maybe try that first before the full factory reset.
Click to expand...
Click to collapse
Factory reset and using the files you provided in this thread worked. Thanks for your help.
So I stumbled upon a guide from way back of 2016, and was wondering if it's possible to connect an NTFS external HDD to the FireTV 4k stick. The guide in question concerned a Fire TV and used a side-loaded "Paragon NTFS & HFS+" app to mount the hard drive and Kodi to access it.
Has anybody have had experience with that? Could that be possible if a powered USB hub was used?
Update: Although the voice view nonsense is fixed, one problem remains.... The built in cursor for Silk Browser has disappeared. I'm having to use an air mouse or mouse toggle. Did two more factory resets and once the ADB command is entered this problem returns.
JUSTINMARMER said:
Update: Although the voice view nonsense is fixed, one problem remains.... The built in cursor for Silk Browser has disappeared. I'm having to use an air mouse or mouse toggle. Did two more factory resets and once the ADB command is entered this problem returns.
Click to expand...
Click to collapse
Yes, I'm having the same issue with the cursor in Silk – I'm currently looking at the source of LauncherHijack to find out if we can do something about that. Meanwhile you can use Firefox; there the cursor is still working...
TheRealQubix said:
Yes, I'm having the same issue with the cursor in Silk – I'm currently looking at the source of LauncherHijack to find out if we can do something about that. Meanwhile you can use Firefox; there the cursor is still working...
Click to expand...
Click to collapse
Yes, but video controls in Firefox are atrocious. Please keep us informed if you make any progress with the cursor fix.
JUSTINMARMER said:
Yes, but video controls in Firefox are atrocious. Please keep us informed if you make any progress with the cursor fix.
Click to expand...
Click to collapse
Yeah, I know But better than no cursor at all... I just got a wireless mini keyboard with touchpad which helps by providing a "real" mouse cursor in Silk but I'd really like to be able to use the standard remote... will keep this thread updated if I find a solution.
Btw, I've combined the functionality of the settingstest/debug apk into LauncherHijack so let me know if anybody needs this; then only LauncherHijack plus 1 adb command is required... (can I add files here?).

Categories

Resources