Related
The official browser code name was called "Cloud9". Looking at what APK package dependencies are needed for self install on another Android device.
Nice. I would love to see this ported to say...the nexus s. The browser looks pretty nice on it.
From Degobah
I am actually trying to port the browser over to my Thunderbolt now. It needs some lib files moved over as well, not sure what else just yet.
I'll let you know if I get it to work, I'm kind of squeezing it into a complete ROM port though.
wouldnt doing something like this require a spoof on the amazon servers? being that they probably require authentication from the servers.
I had it working on my Thunderbolt, but now getting a crash and can't quite find the source, but I'm trying this on a half ported ROM I am working on so the environment may have something to do with it.
Here is what I have done so far if someone wants to try it or mess around with getting the browser to work on another android device. It may work as is due to how I was testing it.
EDIT : I tested this today and it works without crashing. But I think it needs some graphics work / resizing to be reasonable on a phone. But on another tablet...may be OK.
System/app
(2) cloud9 apks
system/lib
libCommonWrapper.so
libAuthenticationWrapper.so
libWebCoreViewerKRF.so
libWebCoreKRF.so
My wife just got the Kindle Fire yesterday, and from looking at everything I wish I had the time to root it and mess around with it, I don't see where it would be too bad to get a custom ROM going on this
romified said:
I had it working on my Thunderbolt, but now getting a crash and can't quite find the source, but I'm trying this on a half ported ROM I am working on so the environment may have something to do with it.
Here is what I have done so far if someone wants to try it or mess around with getting the browser to work on another android device. It may work as is due to how I was testing it.
EDIT : I tested this today and it works without crashing. But I think it needs some graphics work / resizing to be reasonable on a phone. But on another tablet...may be OK.
System/app
(2) cloud9 apks
system/lib
libCommonWrapper.so
libAuthenticationWrapper.so
libWebCoreViewerKRF.so
libWebCoreKRF.so
My wife just got the Kindle Fire yesterday, and from looking at everything I wish I had the time to root it and mess around with it, I don't see where it would be too bad to get a custom ROM going on this
Click to expand...
Click to collapse
I get an instant FC on my CM7 captivate with these, any ideas?
Hrm,
Am I the only one who thinks the silk browser works like anything but silk? I find slow and inconsistent.
But for what its worth I think you'd probably need to spoof a amazon ID for it to work properly.
straylight said:
Am I the only one who thinks the silk browser works like anything but silk? I find slow and inconsistent.
But for what its worth I think you'd probably need to spoof a amazon ID for it to work properly.
Click to expand...
Click to collapse
No. You're not the only one...
http://www.theverge.com/2011/11/19/2574059/amazons-kindle-fire-silk-browser-test
To me it is obvious that the person has a pretty good broadband connection.. plus the results are misleading because if both are connecting to the same router , the router is doing round robin on the two devices and the delay between the two devices renders could be due to context swapping..
The true test of cloud should be on a low bandwidth network, which is when the fast pipe on the cloud could give u a advantage..
Refot_Sirk said:
No. You're not the only one...
http://www.theverge.com/2011/11/19/2574059/amazons-kindle-fire-silk-browser-test
Click to expand...
Click to collapse
straylight said:
Am I the only one who thinks the silk browser works like anything but silk? I find slow and inconsistent.
But for what its worth I think you'd probably need to spoof a amazon ID for it to work properly.
Click to expand...
Click to collapse
I agree, plus mine keeps shutting down and restarting. This was the death knell for me to get one for my hubby for X-mas. He'll be getting an Archos 80 under the tree.
I feel really stupid on this forum. Everyone is so smart and knows what their doing most of the time. You all talk the lingo and I'm lost half the time. I'm trying to play catch up, read and learn as much as I can. How did all of you learn this stuff? I'm searching these forums and googling everything! I'm a new Android user(obviously)and I love my Nitro, minus the horrible battery life. I really like the fact that these phones can be modified a lot. So far I've rooted my phone and did the no carrier, blue icons and battery % mods.
Now that my 30 days is over, I can NOT screw up my phone. Basically I'm not going to do a thing to it till I have a clue. I guess there's a de-bricking write up, but that is CONFUSING as hell to me. I just need lots of detail, pictures, or better yet, a video to learn that kind of stuff. Reading how do the CWM doesn't look too bad, only because I googled it for the Nitro and there's already a few cites that made a clear write up. Installing a custom ROM doesn't look to hard either. However, all the modifications to these ROMS is overwhelming. Back to Google I go for all of that stuff stuff. I just figured out how to use Titanium Backup Pro, I think. What isn't clear is how to restore my phone with the apps/contacts after a custom ROM is installed. I know theirs more I'm forgetting, but that's enough for now.
I'm not ranting, just slightly frustrated don't understand it all. Not really sure what I want out of writing all this. Maybe some guidance, help, insight and or some answers to some of my questions. Thanks for reading!
It's not you, it's just like picking up on a computer, it takes time. I'm still a noob my most standards. I'm on my 3rd Android phone and know my way around my phones, but I don't know anything about development and don't really know my way around the Android file system that well. Here are some common terms that may help you out.
ADB - Android Debug Bridge, used for running commands to your device from your computer
Fastboot - It allows you to connect to your phone and run commands without booting entirely into your rom
CWM - ClockWorkMod, most common non-stock recovery tool
Bootloader - This partition loads your rom or recovery depending on what you need / select
If there's anything you're curious about just ask and I'm sure someone will help out. My ADB and Fastboot definitions are from my very limited understanding.
Check this out too, should be helpful. Found it on Google.
http://forum.xda-developers.com/showthread.php?t=619153
You'll do just fine so long as you don't try to do too much too soon.
I got started by simply rooting my AMOLED DROID Incredible, following some online guides. After that, I removed some bloatware. I kept reading about how to do more and once Cyanogenmod 7 came out for my phone, I used it. I've stuck with it ever since.
There are other things I'd like to know, too, like if I can get remove stock applications when I'm already using replacements (browser, email, messaging, etc.). But that might have to wait until I upgrade my device so that I can try it on this phone and not the new one.
Anyway, I hear ya when it comes to the steep learning curve. Baby steps, man. Baby steps. You'll get there in due time.
Sent from my AMOLED DInc using XDA App
Man, you haven't lived until you brick your brand new first android phone within a week and a half of purchasing it off contract I almost shat bricks, I thought my phone was a lost cause.
1st andoid device for me too but I love the customization that it provides and dont like the risks. The biggest mistake I have made so far is getting stressed about change. Consequently, I will lose some patience and not follow a direction properly or think through a step like I should.
I did start with TB pro aswell but still broke my phone by freezing the stock launcher then later doing a factory reset. But I would have avoided that if I had been more patient and doublechecked what I had frozen prior. The good news is that caused me to dive in to Malninion's debrick guide which forced me to learn the basics of accessing this phone through the computer and issueeing commands which are all pretty straightforward albeit uncharted territory for me.
Now that I have a basic idea of how to use the basic tool kit I will be installing the cwm but I am waiting a bit longer to let any issues reveal themselves and more importantly see how folks really o er from those issues. Then after getting a better understanding of wtf cwm is ! I will instaall/ flash one of the custom roms after giving them a bit of time to sort themselves out as well.
So basically my strategy is to go slow, don't jump right on with a new dev until those more knowledgeable about it do and give it a good going over.
So now I'm trying to read how to use Titanium Backup to restore your apps after a you install a new ROM.
I found this> http://www.androidtablets.net/forum/viewsonic-gtablet-technical/12513-howto-titanium-backup-restore-apps-system-data-new-rom.html I know not to restore system data though.
Now what is frustrating is this: (If you have the donate version, don't forget to save your TitaniumBackup_license that is in the root folder.)
I have the Pro version, that I am 100% sure and it all works. What I think is my root folder, there is NOTHING in there (/root). I tried a search using Root Explorer and looked in Astro. I can't find my TitaniumBackup_license.txt file. I've google searched trying to find where it is and apparently it's a big secret that everybody knows but me.
It's really easy once you do it a few time's, if you need help let me know.
Hello, I'm brand new here, and found my way here after purchasing my Kindle Fire last week, and upon receiving it, almost immediately did a Google search for "hacking the Kindle Fire".......just to see what people were doing to this device.
I was pleasantly surprised at how much more they are capable of. I've never owned a tablet of any kind, and I'm one of the half dozen people on the planet that doesn't yet have a smart phone, lol.
That being said, I did a few minor hacks on a couple different cell phones in he past, I just built my first computer, and it actually works, with no problems......so far anyway, lol.
What I'm getting at is.....messing around with a device doesn't intimidate me too much, and I'm not a complete stranger to tinkering with electronics, and I like the challenge, BUT, I'm far from an "expert" or as knowledgeable as a lot of you that post here.
Now, to the point.......
I saw this thread
http://forum.xda-developers.com/showthread.php?t=1399889
And that utility seems pretty straightforward, and after watching a youtube video on how to use it
http://www.youtube.com/watch?v=mwMHIkX20YI&feature=related
I think I will try it......maybe not right away, but in a couple weeks or so.
My Fire is being replaced by Amazon for a screen issue, and a couple other things, but anyway, I already tried just the Go Launcher Ex app, and that made quite a bit of a difference to me. Just getting rid of that stock carousal is worth it. Actually, If I could set a few of those Go wallpapers and make them stick, I'd be content for a little while anyway.
But...as far as rooting it, and please correct me if I'm wrong.....after using that utility, you're pretty much good to go, correct? I mean, as far as the Fire being able to do much more....more apps available, and getting more of a true Android OS out of the Fire etc.
If I follow that video carefully, how much of a risk is there of breaking my device, or anything really going wrong? Am I getting in over my head, or is this pretty simple stuff? I bought the Fire because it's as close to a full fledged tablet as I can afford, and now I'm learning that it can be much more of a tablet than it is, so is it worth the risk?
I'm just trying to get some kind of consensus from you people that know this like the back of your hand, if I may be biting off more than I can chew or??? And, what are the major benefits of rooting that I haven't already seen?
Thanks in advance for any input, and for reading my semi rambling post!
From my experience it has shown more beneficial to learn the command line methods first rather than going straight to a utility like the KFU.
Depending on what you want out of your Kindle Fire experience, it can be troublesome or very easy.
If you want to run a rooted straight stock interface it's slightly more work and you run the risk of Amazon's OTA updates reeking havok on your system, but there are ways around that.
If you want to run a custom rom the process is much easier as all custom roms come pre rooted. And if it's the stock Kindle Fire interface you want, there's a custom rom for that as well.
The biggest thing is installing custom recovery which, as of now, is the only thing you have to do via the command line.
Next would be installing a custom bootloader. The bootloader allows you to use the power button to enter recovery and the most recent version (1.4) allows you to change your bootmode, which will prove very useful in a pinch. Also the new bootloader is flashable via recovery, drastically reducing the possibility of "bricking" your device.
After that, installing and switching between roms is easy with recovery.
There is an immense knowledge base here but it isn't very organized and the search function has a bit to be desired. But if you look around, you'll see most of the same problems are repeated throughout (usually due to lack of experience or user error or both).
The guide posted at this link is a must for any Kindle Fire user so check it out. http://forum.xda-developers.com/showthread.php?p=23747567
Read through the second and third posts as well.
Good luck
And at the end of the third post Soup mentions above, is a link to a supplemental guide written by Kinfauns that puts all the previous info together to let you root and install roms via commands if you decide to go that route instead of using KFU or a similar utility.
soupmagnet said:
From my experience it has shown more beneficial to learn the command line methods first rather than going straight to a utility like the KFU.
Depending on what you want out of your Kindle Fire experience, it can be troublesome or very easy.
If you want to run a rooted straight stock interface it's slightly more work and you run the risk of Amazon's OTA updates reeking havok on your system, but there are ways around that.
If you want to run a custom rom the process is much easier as all custom roms come pre rooted. And if it's the stock Kindle Fire interface you want, there's a custom rom for that as well.
The biggest thing is installing custom recovery which, as of now, is the only thing you have to do via the command line.
Next would be installing a custom bootloader. The bootloader allows you to use the power button to enter recovery and the most recent version (1.4) allows you to change your bootmode, which will prove very useful in a pinch. Also the new bootloader is flashable via recovery, drastically reducing the possibility of "bricking" your device.
After that, installing and switching between roms is easy with recovery.
There is an immense knowledge base here but it isn't very organized and the search function has a bit to be desired. But if you look around, you'll see most of the same problems are repeated throughout (usually due to lack of experience or user error or both).
The guide posted at this link is a must for any Kindle Fire user so check it out. http://forum.xda-developers.com/showthread.php?p=23747567
Read through the second and third posts as well.
Good luck
Click to expand...
Click to collapse
Thanks for all that info. Much appreciated. I will read that guide thoroughly, and make a decision. I got my replacement Kindle Fire today, and I just found out you can't remove some of their pre loaded apps. Not the end of the world, but that kind of thing right there is why I will most likely root it.....to have control of the device to do with as I please. I'll see how I feel after I read the guide. Like I said, I like the challenge of stuff like this, and simply making the device more personal. I ended up getting a brand new one for $128, so that makes it even more worth the small risk of turning it into a paperweight. I doubt that would happen, but I'm not taking it lightly either.....I know it can happen.
leswgnr said:
And at the end of the third post Soup mentions above, is a link to a supplemental guide written by Kinfauns that puts all the previous info together to let you root and install roms via commands if you decide to go that route instead of using KFU or a similar utility.
Click to expand...
Click to collapse
And thank you as well.
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
soulweeper51 said:
And thank you as well.
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
Click to expand...
Click to collapse
There are many variables that can come into play to make the KFU a bad choice for beginners IMO. For a small majority of users, the KFU works flawlessly. But there are some, for a lot of different reasons, for which it has caused unforeseeable problems, without having the necessary knowledge to fix. And for that reason I suggest you research and learn how everything works beforehand so you will have a strong foundation to troubleshoot any problems that may, and likely will arise.
soulweeper51 said:
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
Click to expand...
Click to collapse
Soupmagnet sums it up well in the prior post. I haven't used KFU but have looked at it to see what it's doing, and seen all the instances where someone needed help after using it. When it works it works great, but if you really want "...to have control of the device to do with as I please ... like the challenge of stuff like this" -- then go for it!! The guides will help you get there.
While it's a lot to learn, it's not as much as it seems and will stand you in good stead for as long as you have the device.
leswgnr said:
Soupmagnet sums it up well in the prior post. I haven't used KFU but have looked at it to see what it's doing, and seen all the instances where someone needed help after using it. When it works it works great, but if you really want "...to have control of the device to do with as I please ... like the challenge of stuff like this" -- then go for it!! The guides will help you get there.
While it's a lot to learn, it's not as much as it seems and will stand you in good stead for as long as you have the device.
Click to expand...
Click to collapse
Yeah, I read through the guide once, and a fair amount went right over my head, lol. But, I'll read it a few times to let it sink in. Like I said, I'm not nearly as smart as a lot of people that post here, when it comes to this kind of thing, but I've attempted a few things like this with success, and I'm fairly brave, as far as taking the risk. It sounds like you really have to not be paying attention to brick this thing.
Hey, there's only one way to learn, right?
soulweeper51 said:
Yeah, I read through the guide once, and a fair amount went right over my head, lol. But, I'll read it a few times to let it sink in. Like I said, I'm not nearly as smart as a lot of people that post here, when it comes to this kind of thing, but I've attempted a few things like this with success, and I'm fairly brave, as far as taking the risk. It sounds like you really have to not be paying attention to brick this thing.
Hey, there's only one way to learn, right?
Click to expand...
Click to collapse
It's very difficult, if not impossible to truly brick this device. The worst thing you can do is kill the bootloader, but even that is not an irrecoverable mistake.
The first post is the most important of the three... you should at least have a good grasp of that one. What part of the guide gave you problems?
kinfauns said:
The first post is the most important of the three... you should at least have a good grasp of that one. What part of the guide gave you problems?
Click to expand...
Click to collapse
Not so much a "problem", as some of it is a little foreign to me.......I guess that's a good way to put it. As much as I want to just use the KFU and cross my fingers, I do want to understand as much of it as I can, so in the event of something going a little south, I hopefully know exactly why.
The Youtube video I watched makes it look so easy, but like I was told, doesn't help with understanding how it all works.
Not to question your capabilities, but what's the rush? You say you've never had a smartphone, so I take it you're unfamiliar with Android devices.
I see so much misinformation floating around about the Fire (you need to root to sideload apps, you need to root to change the stock UI, etc.).
Why don't you fool around with it for a week or two first, get familiar with Android, and see what it's capable of doing, and then root it?
grvthang said:
Not to question your capabilities, but what's the rush? You say you've never had a smartphone, so I take it you're unfamiliar with Android devices.
I see so much misinformation floating around about the Fire (you need to root to sideload apps, you need to root to change the stock UI, etc.).
Why don't you fool around with it for a week or two first, get familiar with Android, and see what it's capable of doing, and then root it?
Click to expand...
Click to collapse
I basically agree with you, as far as not rushing into it. Part of it is my personality......I started looking up what people do to this device as soon as I got it, and it doesn't take long to see how much you can do with it, if you choose.
I hated that carousel right away, so I got Go Launcher Ex, to get rid of that....then I discovered some of the Go wallpapers, and when you set one, it reverts back to the stock one every time it "wakes up" or is powered on, so I found a Youtube video that shows how to set the wallpaper you choose to stay, but it has to be rooted.......and so on and so forth. You get the idea. At the moment I'd be happy just to root it and do that, and then go from there. Like I said, part of it is "I want to do it, just because I can", and it will be more "mine". Maybe that sounds corny, but it's how I feel about it, for the most part. I want to do a few things that I want to do, and then learn more and do more, accordingly, if that makes sense.
That being said, I watched the Youtube video by Nat3mil on using KFU, but from what I can tell, he just goes through downloading the utility, installing the drivers on your computer, and then how to Install Permanent Root with Superuser(option 2)......but what about the other 5 commands?
Like
1 Bootmode menu
3 Install latest TWRP recovery
4 Install latest clockwork recovery
5 Install latest FireFireFire
6 Extras <Requires root>
I guess what I'm asking is....if a person uses KFU, is it best to use all the commands? I guess because the video I watched didn't cover anything other than Install Permanent Root, I'm a little confused.
I hope that made sense, and I'm pretty sure that may seem like a stupid question, but if I don't ask, I won't know.
I'm assuming I can just Install Permanent Root to start with, or like I said, do I go through all the commands?
Go easy on me.
Select install permanent root it should put on fff boot loader and twrp all in one shot clockwork mod recovery isn't needed at that point as for the extras Google market is nice. I say twrp if you want to try any of the new ics roms cwm won't flash them if you do you'll be bricked.
But it might be a little different since I tryed it maybe fff and twrp are seperate installs last time I ran it the first screen I came to after it rebooted was burrito root then it rebooted again I was greeted by the fff bootloader then it booted into twrp where there was a big reboot button so I hit reboot. It then rebooted to the fff bootloader screen then into the kindle os all done rooted new boot loader and recovery
---------- Post added at 12:40 AM ---------- Previous post was at 12:25 AM ----------
This may differ now the best person to ask is vashypooh himself
---------- Post added at 01:02 AM ---------- Previous post was at 12:40 AM ----------
Nat3mil is a great guy and he has done very good videos I just noticed on this last one he didn't show you what's going on on the kindle screen I really wish he would have. If you watch the others 6.21 and 6.22 they vary slightly from that of 6.3.
1. Get adb working
2. Check allow installation from unknown sources
3. Make sure that your USB mass storage drivers are still functioning( in an emergency you will need them)
4 never unplug your device until you are darn sure the process is finished.
Read the dialogue that happens in kfu you can see what is being pushed to your kindle
Ask lots of questions if your in doubt
---------- Post added at 01:25 AM ---------- Previous post was at 01:02 AM ----------
Oh and use the most recent version of kfu it has the very latest bootloader which is different from the original more features are added. To access recovery from this one when you see the blue kindle fire logo give the power button a few pushes small words will come up at the bottom of the screen.
-- normal--
Recovery
Change boot mode
The power button toggles you through these options.
If I had to choose of course root first second run twrp third run fff last Google apps/go launcher.
O.k. thanks!
Now that I've read that guide a couple times, and watched the video a couple times, I'm torn between the two. The idea of just letting KFU do everything, and hoping nothing goes south has an appeal, and the manual method is just more tedious, but you learn more in the process, kind of like when I built my first computer recently......I learned a lot, though it would have been easier to just buy one. Damn.....not sure what to do.
If I'm following all this correctly, if I use the KFU, and there is an OTA update, could I potentially have a problem on my hands that could be a PITA, or would I simply lose the root and have to do it again?
Also, it sounds to me like the custom ROM is the way to go, and actually a littler easier???
Hope my assumptions are at least fairly accurate.
Your correct but you will just lose root from an ota and yes custom rooms will solve this as long as your willing to live with some bugs. CM7 is stable but once you learn about the bugs of CM9 its not all that bad.
Thepooch said:
Your correct but you will just lose root from an ota and yes custom rooms will solve this as long as your willing to live with some bugs. CM7 is stable but once you learn about the bugs of CM9 its not all that bad.
Click to expand...
Click to collapse
Just to clarify......if I wait a bit on the custom roms, and just root it for now, and there is an OTA update, I simply lose the root...no other harm done. Just root it again, and back in business, correct?
Just making sure.
Not quite. OTA updates usually cause a lot of problems to rooted devices and if you don't know how to fix them, you may be looking at a lot of headaches. You can disable them for now but no one knows for sure if Amazon will try to get around it. The more we learn, the more they learn as well. Apple has an entire team whose sole purpose is to try to beat the jailbreakers and I think it's only a matter of time before Amazon follows suit. And at the rate some of these noobs keep sending their devices back with problems caused by modifying, I think that time will be a lot sooner than we think. But that's just my opinion.
soupmagnet said:
Not quite. OTA updates usually cause a lot of problems to rooted devices and if you don't know how to fix them, you may be looking at a lot of headaches. You can disable them for now but no one knows for sure if Amazon will try to get around it. The more we learn, the more they learn as well. Apple has an entire team whose sole purpose is to try to beat the jailbreakers and I think it's only a matter of time before Amazon follows suit. And at the rate some of these noobs keep sending their devices back with problems caused by modifying, I think that time will be a lot sooner than we think. But that's just my opinion.
Click to expand...
Click to collapse
Thank you.
That definitely all makes perfect sense. Like I said, I'd like to change a few things, and rooting it would allow the little changes that would make me content for a bit, but it's either just root it, and disable the updates(with fingers crossed they don't get around it for a bit), or go straight to the custom roms, and updates are no longer in the equation......am I on the right page with that?
Also, If I decide to just root it for now, and disable the updates, and Amazon finds a way around it in the not too distant future, how hard is to just go back to the stock device?
Yeah right page http://forum.xda-developers.com/showthread.php?t=1399072
Hello all, if this has been asked before I apologize, but I have thumbed through these forums for quite a while now and to no avail via Google searching I think I probably already have my answer but here goes anyway. I own the 2013 Kindle Fire HD 7". The one with 8GB storage and firmware 11.3.1 right out of the box. As per the root instructions in a different thread I was able to successfully root the thing. I understand there are no custom ROM's yet; however, has anyone here figured out a method of manually changing the date and time? I would very much like to do this for a few games I play. Yes I know this is a cheating method, but I suppose it bothers me I have virtually no customization options for the later model kindles. I'm debating about returning it to Amazon and perhaps upgrading to a Nexus 7. If anyone has the answer though to the date and time fix, I am all ears. Thanks
I'm a little late to the game here and missed rooting at 5.2.1.0, so now I seem stuck.
The last post from rbox on a recovery installer was 4th June 2016, and I couldn't find anything on that since, or any kind of downgrader.
Anyone have any news I've missed, or insider info?
What I really need is to mount CIF shares off my Synology for playing ROMs of various types. Any specific solution for that I may have missed?
Thanks bunches! :good:
MrPeach
MrPeach said:
I'm a little late to the game here and missed rooting at 5.2.1.0, so now I seem stuck.
The last post from rbox on a recovery installer was 4th June 2016, and I couldn't find anything on that since, or any kind of downgrader.
Anyone have any news I've missed, or insider info?
What I really need is to mount CIF shares off my Synology for playing ROMs of various types. Any specific solution for that I may have missed?
Thanks bunches! :good:
MrPeach
Click to expand...
Click to collapse
In the same boat myself, doesnt seem to be any developmennts yet.
With all do respect as someone who has managed to root his AFTV at unbox time. What exactly IS the benefit of rooting the AFTV2? And, no this is not a rhetorical question.
One of the big hopes I've had about rooting the AFTV2 was to get Google PlayStore, and Gapps working. Well if the ever had, it seems that I too may have missed that Boat. As they do NOT seem to work under 5.2.1.1.
The only other reason why I might have wanted Root, pairing a Sixaxis Dualshock 3 Controller with my AFTV2. 'Cause I'm too cheep for an Amazon Controller. Doesn't work either, and in fact will cause the AFTV2 to crash, and reboot itself.
As for AdAway, (My prime motivation for rooting anything!), well I've yet to find a use for it. It doesn't block anything in the Fire Launcher. Not that I think it should anyway. But nothing I've ran into yet even has any in-app advertising.
Side loading Kodi never really required root, and has otherwise worked fine.
IMHO root on the AFTV2 is a tad overrated, for all you can do with it, or actually what you still can't do with it.
Ichijoe said:
With all do respect as someone who has managed to root his AFTV at unbox time. What exactly IS the benefit of rooting the AFTV2? And, no this is not a rhetorical question.
One of the big hopes I've had about rooting the AFTV2 was to get Google PlayStore, and Gapps working. Well if the ever had, it seems that I too may have missed that Boat. As they do NOT seem to work under 5.2.1.1.
The only other reason why I might have wanted Root, pairing a Sixaxis Dualshock 3 Controller with my AFTV2. 'Cause I'm too cheep for an Amazon Controller. Doesn't work either, and in fact will cause the AFTV2 to crash, and reboot itself.
As for AdAway, (My prime motivation for rooting anything!), well I've yet to find a use for it. It doesn't block anything in the Fire Launcher. Not that I think it should anyway. But nothing I've ran into yet even has any in-app advertising.
Side loading Kodi never really required root, and has otherwise worked fine.
IMHO root on the AFTV2 is a tad overrated, for all you can do with it, or actually what you still can't do with it.
Click to expand...
Click to collapse
Well as noted, what I care about is simply mounting a network share. While somewhat interesting, your comment adds nothing to this particular thread.
Ichijoe said:
With all do respect as someone who has managed to root his AFTV at unbox time. What exactly IS the benefit of rooting the AFTV2? And, no this is not a rhetorical question.
One of the big hopes I've had about rooting the AFTV2 was to get Google PlayStore, and Gapps working. Well if the ever had, it seems that I too may have missed that Boat. As they do NOT seem to work under 5.2.1.1.
The only other reason why I might have wanted Root, pairing a Sixaxis Dualshock 3 Controller with my AFTV2. 'Cause I'm too cheep for an Amazon Controller. Doesn't work either, and in fact will cause the AFTV2 to crash, and reboot itself.
As for AdAway, (My prime motivation for rooting anything!), well I've yet to find a use for it. It doesn't block anything in the Fire Launcher. Not that I think it should anyway. But nothing I've ran into yet even has any in-app advertising.
Side loading Kodi never really required root, and has otherwise worked fine.
IMHO root on the AFTV2 is a tad overrated, for all you can do with it, or actually what you still can't do with it.
Click to expand...
Click to collapse
I want to be able to add a usb Ethernet adapter. The fire stick 2 allows usb devices to be added natively. Ive contacted the Fire tv support team about a possible update to allow fire stick first gen to allow this without root, they said they would take it under consideration so probably no.
@MrPeach
Surly you could add a network share from inside Kodi or? I kinda fail to see the point of it outside of Kodi otherwise.
@tylercheribini
Well I could imagine why some people might want to have two Ethernet Ports. I find little use for mine while on 802.11ac. But at least this is concept I can work with.
Ichijoe said:
@MrPeach
Surly you could add a network share from inside Kodi or? I kinda fail to see the point of it outside of Kodi otherwise.
@tylercheribini
Well I could imagine why some people might want to have two Ethernet Ports. I find little use for mine while on 802.11ac. But at least this is concept I can work with.
Click to expand...
Click to collapse
The Fire Stick has no ethernet port, it must be rooted in order to add one.
Sorry, missed that bit. Of course it (Firestick), doesn't.
Any news? Had an update mysteriously occur, moving it up to the latest firetv update. For some time, have been stuck without a solution. For list of what doesn't work at this date, neither the latest kingo root on pc with an a to a cable or the kingroot app work. Hoping sometime soon one of the remaining vulnerabilities is taken advantage of soon.
I've locked down my network in the meantime. Would recommend anybody that does care about root in the same boat as me do the same until a solution is found..
Sound advice... And BTW I do care about root. I just question the point of it on this Device. Which to my chagrin includes a bit more then the AFTV2... lol!
And, I concede their use cases aren't mine. And, at the moment the things I'd like to do on my AFTV2, which would otherwise require root as well. (i.e. PlayStore, and Dualshock 3 Support) have not brought me much joy even with root. So though I probably could have been less of a **** about it. I was generally interested in why others were so keen to root it. And I got my answer.
The only good news is that it's not a done deal with the FireOS, and eventuality another exploit shall be found, but you'll just have to hang on till then. Yeah sucks I know.
Lol. Yes it does suck.
I probably shouldn't have responded in that way either. It's hard to tell someone's intent based on a few lines in a thread. Didnt mean to come off bh.
Root has been good, was nice to be able to autostart the Kodi/spmc app and for me, using droidmote. that's a really great mouse keyboard app along with a ssh server and BusyBox... But then again, since I updated to the latest rooted ROM(5.2.1.1) in my other box, I've lost the autostart and some of the other bonuses. As much as I hate to do it, will have to start troubleshooting options maybe downgrade.
Til there's an option....
The Dirty Cow linux exploit was recently released (last week). This should allow root on the newer firmware versions (5.2.1.1, etc). Since it was just released last week people are working on it. This thread discusses the progress http://forum.xda-developers.com/general/security/dirty-cow-t3484879
and here is a post of someone who claims to have it working
http://forum.xda-developers.com/showpost.php?p=69299542&postcount=39
I am working on getting this going on my AFTV2 with version 5.2.1.0.
clarke.hackworth said:
The Dirty Cow linux exploit was recently released (last week). This should allow root on the newer firmware versions (5.2.1.1, etc). Since it was just released last week people are working on it. This thread discusses the progress http://forum.xda-developers.com/general/security/dirty-cow-t3484879
and here is a post of someone who claims to have it working
http://forum.xda-developers.com/showpost.php?p=69299542&postcount=39
I am working on getting this going on my AFTV2 with version 5.2.1.0.
Click to expand...
Click to collapse
Cool, looks promising, thanks.
I know that Android, is kind of a fork of Linux. But, isn't that kinda the point? Are we even sure that this 'ploit affects Android?
I'm in the same boat as you guys, i also wait for a 5.2.1.1 root
In my case i want to install the root-version of the moonlight streaming app which has native mouse support so i can finally play mouse/keyboard games on my home cinema (The non-root version is kinda buggy... scaling-problems, stuttering, no off-screen-movment, and so on..)
Ichijoe said:
With all do respect as someone who has managed to root his AFTV at unbox time. What exactly IS the benefit of rooting the AFTV2? And, no this is not a rhetorical question.
One of the big hopes I've had about rooting the AFTV2 was to get Google PlayStore, and Gapps working. Well if the ever had, it seems that I too may have missed that Boat. As they do NOT seem to work under 5.2.1.1.
The only other reason why I might have wanted Root, pairing a Sixaxis Dualshock 3 Controller with my AFTV2. 'Cause I'm too cheep for an Amazon Controller. Doesn't work either, and in fact will cause the AFTV2 to crash, and reboot itself.
As for AdAway, (My prime motivation for rooting anything!), well I've yet to find a use for it. It doesn't block anything in the Fire Launcher. Not that I think it should anyway. But nothing I've ran into yet even has any in-app advertising.
Side loading Kodi never really required root, and has otherwise worked fine.
IMHO root on the AFTV2 is a tad overrated, for all you can do with it, or actually what you still can't do with it.
Click to expand...
Click to collapse
The reason I am looking for root is to be able to run the firestick on a VPN, which requires root.
Ichijoe said:
I know that Android, is kind of a fork of Linux. But, isn't that kinda the point? Are we even sure that this 'ploit affects Android?
Click to expand...
Click to collapse
Yes the exploit effects Android.
FYI, the issue is a vulnerability in how the Linux kernel handles memory / files. Android is just a specific set of applications running on Linux, so it is exploitable. I have used the exploit to modify files in /system and /etc on my FireTV running 5.2.1.1.
Starting with FireTV 5.2.1.0 SELinux is enabled which is an extra layer of protection. It is good from a security stand point -- it helps protects your device from malicious apps, etc. However in our case the "attacker" is the owner of the device ... us. People are working on bypassing SELinux protections, and making progress.
See this blog for some really technical info on the current status: https://v-e-o.blogspot.com/2016/10/way-to-android-init-with-cve-2016-5195.html
drice72 said:
The reason I am looking for root is to be able to run the firestick on a VPN, which requires root.
Click to expand...
Click to collapse
Forgive my ignorance, but what is vpn used for on the ftv aside from accessing content from different countries like Netflix and to possibly make it safer for one to stream certain content?
Well IIRC... One could set up a VPN, to log back into one Network (e.g. Network Storage), from an outside source (i.e. a Hotel Room), to push, and pull Files p, at will. But I think you managed to cover most of the "uses" of a VPN already.
Emulator ROMs
Ichijoe said:
@MrPeach
Surly you could add a network share from inside Kodi or? I kinda fail to see the point of it outside of Kodi otherwise.
@tylercheribini
Well I could imagine why some people might want to have two Ethernet Ports. I find little use for mine while on 802.11ac. But at least this is concept I can work with.
Click to expand...
Click to collapse
As I implied in my original post - emulators generally do not support accessing network shares (where my extensive ROM collection is) directly. This leaves copying ROMs to the Fire TV itself to use them or copying my ROM collection to an external USB drive, neither option of which I find acceptable.
I want to access my extensive ROM collection directly via a SMB mapped folder on my Synology NAS, which research has informed me is only possible on a rooted device.
This isn't about Kodi, an extra ethernet port or any of the other stuff other people have mentioned in this thread.