[Q] so sad - Kindle Fire Q&A, Help & Troubleshooting

I have just bought kindle fire and I found that I will not be able to use free games and books as I am not an American citizen
is it right?

Its true. but thanks to hashcode and all the developers you can make your tablet incredible more functional just go to the development section and read all you need to know about changing the rom of your kindle fire and forget about Amazon and his restrictions
Sent from my flying dragon

Thanks
Thanks Mao
glad to hear that

moataz_a7mad said:
Thanks Mao
glad to hear that
Click to expand...
Click to collapse
I don't want to contradict what Mao_anguita said, but new users are much better off learning a little bit about their Kindle Fire before jumping in to modify their devices.
http://forum.xda-developers.com/showthread.php?t=1552547

Thank You
thanks kinfauns
is there any clear steps to download and install any version of Android on my Kindle Fire?
Is it better to install ICS or GB ?

moataz_a7mad said:
thanks kinfauns
is there any clear steps to download and install any version of Android on my Kindle Fire?
Is it better to install ICS or GB ?
Click to expand...
Click to collapse
Install ICS. It's stable enough to use as a daily rom.

moataz_a7mad said:
thanks kinfauns
is there any clear steps to download and install any version of Android on my Kindle Fire?
Is it better to install ICS or GB ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1638452
I would vote for GB for now. I still use it on my KF. Even the developer for the ICS kernel says it's "not a daily driver" for now, but others will have a varying tolerances for what they find acceptable for daily use. Besides, I don't see any must-have feature in ICS that makes it the "go to" platform.
In any case, it's really not that difficult to backup and try out whatever you want. I suggest you get your new bootloader and recovery installed, then try out a few things to see how they fit you.

kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1638452
I would vote for GB for now. I still use it on my KF. Even the developer for the ICS kernel says it's "not a daily driver" for now, but others will have a varying tolerances for what they find acceptable for daily use. Besides, I don't see any must-have feature in ICS that makes it the "go to" platform.
In any case, it's really not that difficult to backup and try out whatever you want. I suggest you get your new bootloader and recovery installed, then try out a few things to see how they fit you.
Click to expand...
Click to collapse
ICS is definitely ready to be a daily driver. If you flash everything correctly there are absolutely no problems except for the charging light.

ICS is ready for daily use. You just have to charge it with the stock wall charger. Install FFF 1.4a, TWRP, a ICS ROM, and/or the latest kernel. The actually hard stuff can easily be done with KFU.
Sent from my Kindle Fire using xda premium

My post wasn't meant to start a religious debate. I said it's a matter of your own tolerance for outstanding issues and there are still things to be worked out and tested. Just in the last post, Hashcode is asking for testing on random reboots and USB problems in Win7. There's still the charging problem (which is more than just the LED) and Hashcode has said that requires a driver rewrite. If you can live with those potential problems, then that's great, but there's no real reason to push a brand new user into a work-in-progress.
Like I said before, I have yet to hear a real argument for needing to go to ICS. Is there some feature in there that you can't get from GB? I get the whole latest/greatest thing, but I don't see a compelling reason for jumping onto the bandwagon. The only real feature I'm looking to get from the 3.0 kernel is the OTG support, but that's more than half broken and not slated to be worked on for a while.
Once again... YMMV.

kinfauns said:
Is there some feature in there that you can't get from GB?
Click to expand...
Click to collapse
Not so much of a feature, but for me it's the looks. I think ICS looks gorgeous in comparison. Dunno about the other people.

kinfauns said:
My post wasn't meant to start a religious debate. I said it's a matter of your own tolerance for outstanding issues and there are still things to be worked out and tested. Just in the last post, Hashcode is asking for testing on random reboots and USB problems in Win7. There's still the charging problem (which is more than just the LED) and Hashcode has said that requires a driver rewrite. If you can live with those potential problems, then that's great, but there's no real reason to push a brand new user into a work-in-progress.
Like I said before, I have yet to hear a real argument for needing to go to ICS. Is there some feature in there that you can't get from GB? I get the whole latest/greatest thing, but I don't see a compelling reason for jumping onto the bandwagon. The only real feature I'm looking to get from the 3.0 kernel is the OTG support, but that's more than half broken and not slated to be worked on for a while.
Once again... YMMV.
Click to expand...
Click to collapse
Eh, I guess so. I'm not having any of those issues though.

look...really this is black and white...night and day...the kindle fire sucked on Amazons fork...and i had no problem ditching all of Amazons "stuff". the kindle fire was usable and tolerable on CM7...it was normal but you had to execute more effort and work at it. CM9 or any of its cousins on ice cream make the kindle fire absolutely awesome. I'm not even talking about aesthetics or any cosmetics or anything superficial. Once our Messiah... Hashcode gave us HWA and i could have my Google chrome...that should have put all of these petty arguments to rest forever. nuf sed.
no ifs and or buts about it.
anyone remember cupcake? if you do....then notice how much more work you had to do to update apps?
Sent from my Amazon Kindle Fire using xda premium

androidcues said:
look...really this is black and white...night and day...the kindle fire sucked on Amazons fork...and i had no problem ditching all of Amazons "stuff". the kindle fire was usable and tolerable on CM7...it was normal but you had to execute more effort and work at it. CM9 or any of its cousins on ice cream make the kindle fire absolutely awesome. I'm not even talking about aesthetics or any cosmetics or anything superficial. Once our Messiah... Hashcode gave us HWA and i could have my Google chrome...that should have put all of these petty arguments to rest forever. nuf sed.
no ifs and or buts about it.
anyone remember cupcake? if you do....then notice how much more work you had to do to update apps?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire using xda premium

kinfauns said:
I don't want to contradict what Mao_anguita said, but new users are much better off learning a little bit about their Kindle Fire before jumping in to modify their devices.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
that is why i said to "read all you need to know"
really READ all you need to know, ande decide by yourself when youre comfortable with changeing roms and kernesl and know how to do it with out fail, then test every room till youre comfortable
i PERSONALY have tested every rom in development seccion (cm7 cm9 ) and im happy as hell with gede rom with hashcode kernel, but then again every kindle is "diferent" and react diferent to the diferent roms (i can Oc the procesor to 1200 without any truble, other kf have reported trouble with this)
So read all and if youre comfortable root , chage room, etc etc , if not you can Root with out changeing room and still have a pretty funccional tablet (just like a phone with really big screen )
(sorry for the english its not my primary language xD )
Sent from the end of the world (chile)

androidcues said:
look...really this is black and white...night and day...the kindle fire sucked on Amazons fork...and i had no problem ditching all of Amazons "stuff". the kindle fire was usable and tolerable on CM7...it was normal but you had to execute more effort and work at it. CM9 or any of its cousins on ice cream make the kindle fire absolutely awesome. I'm not even talking about aesthetics or any cosmetics or anything superficial. Once our Messiah... Hashcode gave us HWA and i could have my Google chrome...that should have put all of these petty arguments to rest forever. nuf sed.
no ifs and or buts about it.
anyone remember cupcake? if you do....then notice how much more work you had to do to update apps?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Well, I got "Google chrome" out of all that. So, if you need chrome, you need ICS.
My whole point of all this is that ICS is just a little short of being declared THE choice for the everyman. It also seems like your Messiah agrees with me to a certain extent as he states in this post...
http://forum.xda-developers.com/showpost.php?p=24665970
WHAT CAN I EXPECT IF I TRY OUT THE NEW KERNEL/ROM?
LOT'S OF BUGS -- It's for development at this point. Not a daily driver.​
Like I said before... this is not a religious debate.

ICS
i need a url to download ICS to be able to install it on my Kindle fire
thanks in advance

Check dev section. Would give but on the app so its too much of a pain
Sent from my Kindle Fire using XDA

Related

Cyanogenmod Security changes

http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
mauricehall said:
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
CM9 will come with root access turned off (from the rom) by default. There is a new option so that you can turn root on be it for
Disabled,
Enabled for ADB only
Enabled for Apps only
Enabled for both.
That's all this really is.
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
CharlyDigital said:
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
You CAN enable ADB root using ADB which almost seems like a security flaw ADB root access is off by default as well.
But from what I have read ADB will not be required to set this. It just has to be changed by the user from the development options.
I have been wondering about this for a looooooong time. When we root our devices we are voluntarily opening up the biggest hole possible. I'm glad to see it addressed in such a practical manner.
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
....maybe it's just the devices you've owned?
Ask someone with an OG droid, or someone with an Evo, or a Hero, or a GSM Samsung Anything....Hell, CM7 is fantastic on my Nook Color....Cm9 is too, though--I don't remember--I think It's a kang....
The only issue I've had has been with CDMA Samsung handsets...
EDIT: I guess what I mean to say is, there is so much to support that unless you have one of the heavily supported (or easily supported) devices then the fact that it boots up and works at all should be impressive enough.....On all the above mentioned devices I had a nearly flawless experience far preferable to stock....and even with the CM7 kangs (though I haven't tried the CM9s yet). I'm not so sure we'll ever get official support at this rate, though I'm not convinced that's a death sentence. Bubby's Cm7 was working nearly flawlessly for me, aside from a scant few mildly irritating bugs....
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
I saw nightlies left and right on my OG Evo and though the E4GT may not get official CM7 support, We'll surely get offical CM9.
They couldn't get much done for a while because they were using older servers that couldn't keep up. Now they have nightlies going on the Galaxy Nexus, Nexus S, Xoom, Asus Transformer, Asus Transformer Prime, and the HP Touchpad.
I'm sure we'll get nightlies soon enough and you'll be seeing official functioning ROM's everywhere.
We already have functional CM9.
What is AOKP built on anyway?
Ophois said:
http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Click to expand...
Click to collapse
I think they're trying to go mainstream, maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
phatmanxxl said:
maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
Click to expand...
Click to collapse
Problem is the root is still easily accessible. You would see them providing rooting methods for their own software before you saw that. The carriers would also want nothing to do with it. The manufacturer still has the concern of warranty while the carriers have the concern of tethering etc. Carriers likely would never reject an entire manufacturers line, they will always have to cave to some things they do not like.
Though selling unlocked devices with CM much as PC manufacturers will sell hardware with alternative operating systems isn't outrageous. As for the concern of warranty and software caused damage. Routers for example have set a precedent in the support of custom firmware while maintaining warranty. There is plenty of unbricking support in routers. Though providing accessible jtag interfaces in devices that would be sold both retail and unlocked would probably be interesting. Thats just a need in a worst case scenario though not required.
They do seem to be moving in that direction for whatever intent or purpose.

Firefox OS on SGH-T989

The Samsung Galaxy S2 is actually listed by Mozilla as a supported device for Firefox OS....
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites
... with one important note:
Samsung Galaxy S2
The only model that works is the i9100; no other variants are officially compatible. (i9100P might work, since the only change is a NFC chip added)
Click to expand...
Click to collapse
Does this mean our SGH-T989 will not be compatible? Has anyone actually tried Firefox OS with our model?
If someone tried it, there would probably be a thread on it somewhere. About it working on our devices, just take a step back and think, can we run i9000 roms? Our phones and the i9000 are pretty different and I doubt Mozilla would go out of their way to get a t989 and do the work themselves, since our phone isnt International and only sold in a handful or markets. Can it be made to work on our phones? Possibly, with a knowledgeable Dev doing the work, and even then who knows.
The OS as a whole seems to be still in a "beta" form so its not ready yet for the consumer so I doubt anyone would do all the work to port it over to have a half assed OS on their phones, but possibly with time, when the OS is good to go for the market someone will do the leg work to port it over to our phones, but I probably wouldnt hold my breath.
RXDriv3r said:
If someone tried it, there would probably be a thread on it somewhere. About it working on our devices, just take a step back and think, can we run i9000 roms? Our phones and the i9000 are pretty different and I doubt Mozilla would go out of their way to get a t989 and do the work themselves, since our phone isnt International and only sold in a handful or markets. Can it be made to work on our phones? Possibly, with a knowledgeable Dev doing the work, and even then who knows.
The OS as a whole seems to be still in a "beta" form so its not ready yet for the consumer so I doubt anyone would do all the work to port it over to have a half assed OS on their phones, but possibly with time, when the OS is good to go for the market someone will do the leg work to port it over to our phones, but I probably wouldnt hold my breath.
Click to expand...
Click to collapse
Still to this day android is still a beta imo
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Redsmurf said:
Does this mean our SGH-T989 will not be compatible?
Click to expand...
Click to collapse
Is
The only model that works is the i9100; no other variants are officially compatible.
Click to expand...
Click to collapse
not clear enough?
don728871 said:
Still to this day android is still a beta imo
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
You could say that. I personally think it was beta back in the Gingerbread days, and ICS was a huge improvement and JB is the topping to the ice cream sandwich lol, imo JB is like rc, its a finished product, it can only get better.
RXDriv3r said:
You could say that. I personally think it was beta back in the Gingerbread days, and ICS was a huge improvement and JB is the topping to the ice cream sandwich lol, imo JB is like rc, its a finished product, it can only get better.
Click to expand...
Click to collapse
Then sooo were iOS 1,2 and 3 lol. You guys just say that because even in the 2.x days android was faaaaar lagging behind iOS in both the software AND hardware requirements. Jellybean was the first rendition to properly render GUI elements using the GPU (ICS started it, wasn't complete though) hence the notorious "android lag.". IOS was smooth from the start, powervmr .
That being said, I personally dislike Apple products, go figure
RXDriv3r said:
If someone tried it, there would probably be a thread on it somewhere. About it working on our devices, just take a step back and think, can we run i9000 roms? Our phones and the i9000 are pretty different and I doubt Mozilla would go out of their way to get a t989 and do the work themselves, since our phone isnt International and only sold in a handful or markets. Can it be made to work on our phones? Possibly, with a knowledgeable Dev doing the work, and even then who knows.
The OS as a whole seems to be still in a "beta" form so its not ready yet for the consumer so I doubt anyone would do all the work to port it over to have a half assed OS on their phones, but possibly with time, when the OS is good to go for the market someone will do the leg work to port it over to our phones, but I probably wouldnt hold my breath.
Click to expand...
Click to collapse
don728871 said that Android is still a Beta. In a sense, that is true. It's a work in progress that will probably not end. Ever. In that sense, it is still a beta as it also takes in data and user submitted reviews about their issues, likes, dislikes and the such to make it better and better and better.
Now, for Firefox OS, I'd consider it more of a pre-release alpha. They've got the concept down, they've got a working-ish OS for the most part but yes, like you said, it's a half assed ish OS for the most part and probably, nobody would use this as their daily driver until a stable beta (after extensive testing, updates and stuff) is released.
So for now, nothing to expect here. Let's move along shall we?
Wait a sec, let's look at iOS.
Now, yeah, people say it's lag free. True-ish for the most part...
but let's look at it from another perspective. Has iOS 6 changed in any way?
Yeah, I guess in optimization and whatnot but come on, what OS has changed so dramatically?
Evolved in such a way that it's already awesome but it just keeps getting better and better?
That, as we all know, is android. From Cupcake, we've come a long way to Jelly Bean.
That was 4 years ago. Took a while...
Now knowing how other OS's evolved,
it is now safe to assume that Firefox OS isn't going anywhere far for now.
Ooshi said:
don728871 said that Android is still a Beta. In a sense, that is true. It's a work in progress that will probably not end. Ever. In that sense, it is still a beta as it also takes in data and user submitted reviews about their issues, likes, dislikes and the such to make it better and better and better.
Now, for Firefox OS, I'd consider it more of a pre-release alpha. They've got the concept down, they've got a working-ish OS for the most part but yes, like you said, it's a half assed ish OS for the most part and probably, nobody would use this as their daily driver until a stable beta (after extensive testing, updates and stuff) is released.
So for now, nothing to expect here. Let's move along shall we?
Wait a sec, let's look at iOS.
Now, yeah, people say it's lag free. True-ish for the most part...
but let's look at it from another perspective. Has iOS 6 changed in any way?
Yeah, I guess in optimization and whatnot but come on, what OS has changed so dramatically?
Evolved in such a way that it's already awesome but it just keeps getting better and better?
That, as we all know, is android. From Cupcake, we've come a long way to Jelly Bean.
That was 4 years ago. Took a while...
Now knowing how other OS's evolved,
it is now safe to assume that Firefox OS isn't going anywhere far for now.
Click to expand...
Click to collapse
Excellent point! Android Evolution has been gradual and drastic ... but still, when it did pick up, it was different. I think if Firefox OS can include a captivating element right from the start, it can make an impact. However, I don't see it being too radically remarkable.

[Q] Porting Android TV to Amazon Fire TV

Does anyone know how this can be done?
Not yet. AFAIK android tv isn't released.
The fact of the custom recovery doesn't get around the locked bootloader, either. There are approaches to the problem which have been used on other devices, but last I looked this device was rootable (in its early generation) but not yet upgradeable.
roustabout said:
Not yet. AFAIK android tv isn't released.
The fact of the custom recovery doesn't get around the locked bootloader, either. There are approaches to the problem which have been used on other devices, but last I looked this device was rootable (in its early generation) but not yet upgradeable.
Click to expand...
Click to collapse
its just getting someone with the know how and want to take it on. Someone has ported it to the ouya.. the port uses cm11 as a base then u flash the android tv package over top, i read its buggy as heck tho and a wip to get things functioning.
http://forum.xda-developers.com/ouya/general/rom-android-tv-ouya-t2895293
nhumber said:
its just getting someone with the know how and want to take it on. Someone has ported it to the ouya.. the port uses cm11 as a base then u flash the android tv package over top, i read its buggy as heck tho and a wip to get things functioning.
http://forum.xda-developers.com/ouya/general/rom-android-tv-ouya-t2895293
Click to expand...
Click to collapse
I did try a quick and dirty port of ADT-1 and it was a massive failure. I may take a look at this at some point.
nhumber said:
its just getting someone with the know how and want to take it on. Someone has ported it to the ouya.. the port uses cm11 as a base then u flash the android tv package over top, i read its buggy as heck tho and a wip to get things functioning.
http://forum.xda-developers.com/ouya/general/rom-android-tv-ouya-t2895293
Click to expand...
Click to collapse
buggy as heck and wip - and on a device with an unlockable bootloader and a lot of folks who bought via kickstarter intending to mod it.
no disrespect to the folks who are working their butts off on the ftv, but you rarely
get a solid cm11 daily driver even with an unlocked device right away, with only one dev working - and that's with cm, where there are a lot of good build guides and a userbase ready to help test and get logs.
with the ftv, look at the number of folks complaining about xbmc on the box.
xbmc works extremely well and with root makes a viable launcher replacement. its my launcher on the system, and I'm beyond pleased with it, given that the system is completely different in use than what the vendor intended.
does it get stuck now and again? yep.
I paid how much for xbmc? for root?
some of the tone here would be fine in a vendor's support forums, but posting about how there's trial and error and glitches in a dev forum?
now, think how much fun it'd be to have a wip rom posted here and need to patiently wade through folks acting like they were entitled to bug-free consumer grade software at no cost and with zero elbow grease involved in setting it up...
No tones or complaining here.. Just was answering the question. Is it possible? Yes. How? I stated how it was done on the ouya. The unlocked bootloader is irrelevant since we have a workaround from rbox, who I'm greatly appreciative of.

Boot Loader

Hello all,
Given that Amazon has just slashed the price on what is in reality a powerful phone, what is the likelihood that we could see an unlocked bootloader (from the community) in the near future. CM would really make this phone fly.
I got the Fire Phone, as it was a $100 for me (i consider the 99$ amazon prime that comes with it, like renewing my existing one that expires on Jan 1st anyway).
As an excited developer, I actually am planning to devote time to trying to flash Custom Recoveries (or at least boot them), and getting Android Lollipop on it. Those are my 2 goals. I have no clue if I will achieve them, as this is my first strong attempt at making something custom, but I will try. I have android 5.0 and fireos sources downloaded. I will try to pull all the system level stuff on my phone from it (incase I need drivers or something), and take a stab. If I can get Lollipop stock working, I will then move to CM 12 and do that.
My goal is for 5.x support. If I can pull it off, I don't want to foray into anything less than Android 5.0.
Wish me luck.
As for bootloader unlock, I haven't checked, but it might be as simple as fastboot oem unlock. Here's to hoping.
Great to hear! Thank you for dedicating your time, I am hopping after end of this semester I will be able to join in this endeavor.
Best of luck!
funkybassplayer said:
Great to hear! Thank you for dedicating your time, I am hopping after end of this semester I will be able to join in this endeavor.
Best of luck!
Click to expand...
Click to collapse
Just a heads up, the bootloader is locked down pretty tight. Unlocking it will require finding and using an exploit. there is a guy on the HDX forum that found an exploit for that Tablet that would work for the Fire Phone, but he decided for legal reasons to not release it anywhere, so both devices are in limbo. Wish i knew even at which exploit to look into and I would do the rest myself.
if it is locked so tight, what is the point of giving away as open source
Daegalus said:
As for bootloader unlock, I haven't checked, but it might be as simple as fastboot oem unlock. Here's to hoping.
Click to expand...
Click to collapse
lol, you must be joking.
dimex said:
lol, you must be joking.
Click to expand...
Click to collapse
Umm, no, not at the time of that post. If you read the post i made after that, you would have seen that I actually checked and found out it wasn't the case. Way to jump the gun.
Daegalus said:
Umm, no, not at the time of that post. If you read the post i made after that, you would have seen that I actually checked and found out it wasn't the case. Way to jump the gun.
Click to expand...
Click to collapse
If it was as simple as a 'fastboot oem unlock' we wouldn't be here half a year later discussing this to begin with. All I'm saying, of course that wasn't going to work.
Glad you're attempting this. If I can help, please let me know. Unless people smarter than me can unlock the bootloader, you might be creating one great virtual machine that won't make it to this nice piece of hardware.
I bought this phone to learn more about the same things you plan to do. I dislike the fireos (and the glitches in the use of the side-loaded gapps) enough to return the phone, but the cheap price, dreaming of a decent OTA update in January, and folks like you working on it makes me think I'll hang on to it as a backup.
I just got a fire phone as well. Hope this forum will get more traction as Amazon release its FireOS source...
"My name is 4.1chan, I will hack this device because I am great developer. Trust me, I took a Jawa class in Kindergarten and passed."
Seriously though, can't see this happening any time soon. You need experienced people, not someone who says they can do it even though they don't even know the boot loader is locked like Ford Knox. Big talk has always led to big disappointment in my experience on xda-developers. Don't get your hopes up, the phone is basically rubbish as it is (even more with simlock), so don't just buy because it is cheap.
Agreed, I am not expecting much on the unlocking front. If it happens great, if not oh well. But I would not call this phone rubbish, it's fast cheap and runs everything I need perfectly. Sure it doesn't have that perfect Android feel, but who cares. Plus the auto scroll feature is pretty handy.
The phone's spec is great for the $200 unlocked price but NO ROM, NO BUY MAN.
funkybassplayer said:
Agreed, I am not expecting much on the unlocking front. If it happens great, if not oh well. But I would not call this phone rubbish, it's fast cheap and runs everything I need perfectly. Sure it doesn't have that perfect Android feel, but who cares. Plus the auto scroll feature is pretty handy.
Click to expand...
Click to collapse
Agreed! An excellent phone for $100! Can't beat that price. Runs what I need as well once you install Google framework, services and play store.
Sent from my Nexus 6 using XDA Free mobile app
*sigh* nevermind, I just leave this here, since THIS is a thread about the bootloader (thanks for trying, Mod. ^^)
Viperise152 said:
http://www.xda-developers.com/kindle-fire-hd-6-and-7-receive-bootloader-unlock-and-twrp/
Will this help us Fire Phone users?
Click to expand...
Click to collapse
Eiermann78 said:
I already tried this and CuberHDX.py, too but it fails with Unlock Code is NOT correct
Maybe the Steps would be right, but i don´t know how to figure out the correct code for the fire phone.
Tested at Fire OS 3.5 and 4.6.1
Click to expand...
Click to collapse
@ Viperise152 & Eggmän78 Sadly: No, it won't help. The unlock for the 6" and 7" is based on the HDX bootloader unlock method. This vuln. was already fixed for the FirePhone by Amazon.

New root exploit soon?

https://android-review.googlesource.com/#/c/117742/
There's no exploit example, but maybe there's a new hope for getting root on the Fire TV Stick and newer Fire TVs. Can anyone confirm the Fire TV has the vulnerable code?
This is very exciting! Crossing my fingers!
Oh boy. This one is BIG. If the Fire TV uses this library, it's just a matter of time.
http://www.cvedetails.com/cve/CVE-2015-1474/
Exciting news!!!
Sizzlechest said:
Oh boy. This one is BIG. If the Fire TV uses this library, it's just a matter of time.
http://www.cvedetails.com/cve/CVE-2015-1474/
Click to expand...
Click to collapse
But if I read this right this affects only 5.0 devices. And AFTV is not 5.0 AFAIK.
Ultraschorsch said:
But if I read this right this affects only 5.0 devices. And AFTV is not 5.0 AFAIK.
Click to expand...
Click to collapse
You didn't read it right. It affects 5.0 and below.
Sizzlechest said:
You didn't read it right. It affects 5.0 and below.
Click to expand...
Click to collapse
Yes, I read through the Android 4.4 sourcecode. The bug is already there. Unfortunately I am no CXX and security expert, so I hope someone else writes an exploit. Should not be too hard.
Not to discount any other dev, but rbox seems to be the guy that would know if its poossible. He seems to be the man when it comes to the Fire TV. Why not just ask rbox? He can probably give you a straight foward answer and you wouldn't have to speculate anymore. Just ask rbox, cause I am pretty sure he would know if it would work.
porkenhimer said:
Not to discount any other dev, but rbox seems to be the guy that would know if its poossible. He seems to be the man when it comes to the Fire TV. Why not just ask rbox? He can probably give you a straight foward answer and you wouldn't have to speculate anymore. Just ask rbox, cause I am pretty sure he would know if it would work.
Click to expand...
Click to collapse
You mention @rbox so many times, but you don't really mention him at the same time. Want his attention? Mention @rbox
its still not going to fix the efuse. amazon really lost my support when that happened.. fireTV is a bedroom box now and i've moved to the 100$ M8 amlogic box running openelec.. if you want something for pure XBMC this is a much better option and fully supports different refresh rates.
Right it won't fix the efuse but I'm pretty sure that I'm not the only one still using the old firmware without efuse and hoping for software root...
gamer765 said:
You mention @rbox so many times, but you don't really mention him at the same time. Want his attention? Mention @rbox
Click to expand...
Click to collapse
I do not want his attention at all. I was simply informing people that if they wanna a quick reliable answer that rbox would probably be the one to ask. I have said several times that I could care less about rooting my Fire TV. I just know how these threads pan out, they usually end up in arguements over wheather or not its possible, so I was trying to give them a quick solution to their question. If they wanna now if its possible they could probably get an answer from rbox and there would be no more speculation and nobody would have to eventually get mad when someone says it won't work. He is a reliable source so why wouldn't they wanna ask him? If I mention him it means I mentioned him period. Yes I mentiond him, cause without a doubt he is probably considered the top dev for the Fire TV. No harm in mentioning him or trying to point people in the right direction to ge an answer. If they ask him today and he responds with a definative answer today, they have their answer and there will be no more wondering.
From what I read, this alone isn't enough to gain root. You need to combine this with other exploit(s) to get it. I've read that there is a forthcoming proof of concept that uses it. So we just have to wait and see. But... hope is not lost totally for people with the fire tv with the fuse blown. Before I had the unlock working, I was working on safestrap for the fire tv. Safestrap allows you to boot to recovery with a locked bootloader. So if this results in root for the newer firetvs with the blown fuse, making a safestrap package is a possibility. No promises on when or if it would actually happen. As for that happening with the stick... highly unlikely (from me) because it's a completely different architecture from the Fire TV.
rbox said:
From what I read, this alone isn't enough to gain root. You need to combine this with other exploit(s) to get it. I've read that there is a forthcoming proof of concept that uses it. So we just have to wait and see. But... hope is not lost totally for people with the fire tv with the fuse blown. Before I had the unlock working, I was working on safestrap for the fire tv. Safestrap allows you to boot to recovery with a locked bootloader. So if this results in root for the newer firetvs with the blown fuse, making a safestrap package is a possibility. No promises on when or if it would actually happen. As for that happening with the stick... highly unlikely (from me) because it's a completely different architecture from the Fire TV.
Click to expand...
Click to collapse
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
E--Man said:
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
Click to expand...
Click to collapse
I had googled the CVE number and found a thread on one of the samsung forums here that they were discussing it.
E--Man said:
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
Click to expand...
Click to collapse
This thread is full of Samsung Note 4 users salivating for a new root exploit: http://forum.xda-developers.com/note-4-att/general/galaxy-note-4-root-progress-t2961974/page111
Sizzlechest said:
This thread is full of Samsung Note 4 users salivating for a new root exploit: http://forum.xda-developers.com/note-4-att/general/galaxy-note-4-root-progress-t2961974/page111
Click to expand...
Click to collapse
Ahh yes, because the AT&T ones come with a locked Bootloader I heard about that... They (we) all deserve it too because we paid for the device!
If the method to root is similar *and* it is possible, then its just a matter of time...
Watch defy. Closed bootloader is sad.
But no Problem at all.
2nd init is long time happened
We need the right dev.
Quarks is the superman
Sent from my Nexus 4 using XDA Free mobile app
E--Man said:
Ahh yes, because the AT&T ones come with a locked Bootloader I heard about that... They (we) all deserve it too because we paid for the device!
If the method to root is similar *and* it is possible, then its just a matter of time...
Click to expand...
Click to collapse
Just because you buy a device does not mean that you deserve to be able to do something that the makers of it never intended it to do. Its like someone goin out and buying an RX7 and saying it deserves to go faster than a Lambo. Any mildly intelligent person would have never bought the Mazda if they wanted it to outrun a Lambo, cause they would know ahead of time its not made to outrun a Lambo. I can understand why people wanna root. I even have rooted devices, but to get mad because you cannot root a device makes zero sense. You knew Amazon did not want you to root it before you bought it, so why complain now? You deserve many things in life simply by being human, but a rooted Fire TV is not on the list of things that anyone deserves. Look at it like this, if root never comes too the newer firmwares, you will forget about when you buy your next device. I must admit I was kinda irked when I read that some Fire TVs cannot be rooted, but i took my chances and bought it anyway, and now I have a nonrootable device, and its absoluely not a big deal. I knew ahead of time what I was getting into and if I get root one day that will be fine, but if I don't I am still fine wiith that too. My Fire TV does everything I need it to do without root so its really not a big deal. I have noticed after I got a little older that the alure of cool apps and cool mods have worn away. I no longer care how cool my Android devices look or what cool tweaks I can use, I simply just want a device that does what its supposed to do. I have done so much "cool stuff" on Android devices that I am actually burnt out. I don't even carry my cell anymore. I have a Galaxy Note that has never been outside except for when UPS dropped it off. Trust me, not having root for your Android device is not gonna have any negative effects on your life if it does not happen.
porkenhimer said:
Just because you buy a device does not mean that you deserve to be able to do something that the makers of it never intended it to do. Its like someone goin out and buying an RX7 and saying it deserves to go faster than a Lambo. Any mildly intelligent person would have never bought the Mazda if they wanted it to outrun a Lambo, cause they would know ahead of time its not made to outrun a Lambo.
Click to expand...
Click to collapse
That is a terrible example. Since we buy the devices we should be able to do what we want with them, similar with cars. We buy cars and since we bought them, we can customize them as we wish. Last I checked, there was nothing in place from stopping me from popping the hood open and doing what I wish with the engine or interior.
Your poor example is akin to saying I bought a cheap outdated phone like an Alcatel and saying it deserves to be faster than an HTC One M8. Learn to troll better.

Categories

Resources