Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-late...xploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
glitch3yf0x said:
Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-latest-on-stagefright-cve-2015-1538-exploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
Click to expand...
Click to collapse
Historically only one file needs to be renamed to effectively disable OTA without hampering other functionality. Also makes the block easily reversible. PM me for details. Not a secret but there are several similarly named files. Those who tinkered with the wrong file(s) on other device types earned a brick. Needs proper testing on this device with FireOS 5.1.1 (preferably w/5.0.1 bootloader) before being released in the wild. Obviously hiding/disabling components is not reliable.
glitch3yf0x said:
Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-latest-on-stagefright-cve-2015-1538-exploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
Click to expand...
Click to collapse
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
sd_shadow said:
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
http://www.kingroot.net/
Is this the right one?
glitch3yf0x said:
http://www.kingroot.net/
Is this the right one?
Click to expand...
Click to collapse
yes, here is xda thread
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from my KFFOWI using XDA Labs
Davey126 said:
Obviously hiding/disabling components is not reliable.
Click to expand...
Click to collapse
Is renaming the OTA apks failing to work? I know pm hide is not a reliable or preferred method but I was hopping that renaming the apks worked.
sd_shadow said:
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
It .apk version failed for me...
Is it the Windows version?
glitch3yf0x said:
It .apk version failed for me...
Is it the Windows version?
Click to expand...
Click to collapse
yes windows Version 3.2.0 Build 1128
Sent from my KFFOWI using XDA Labs
Why are we renaming or hiding? I'm confused. AutoRootScript just delete the components to OTA and OTACerts.zip. Is it frowned upon to completely delete the dependencies?
Not sure what SuperTool does.
glitch3yf0x said:
Why are we renaming or hiding? I'm confused. AutoRootScript just delete the components to OTA and OTACerts.zip. Is it frowned upon to completely delete the dependencies?
Not sure what SuperTool does.
Click to expand...
Click to collapse
SuperTool just uses adb hide command
if you delete it is harder to update if want to
Sent from my KFFOWI using XDA Labs
---------- Post added at 09:14 PM ---------- Previous post was at 09:10 PM ----------
adb hide has proven to be less than adequate to stop updates
Sent from my KFFOWI using XDA Labs
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
You guys are awesome, thanks for all the hard work!
blueberry.sky said:
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
Click to expand...
Click to collapse
renaming or deleting the update apps works or freezing with titanium backup pro
Sent from my KFFOWI using XDA Labs
blueberry.sky said:
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
Click to expand...
Click to collapse
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_Has this not worked for some people?
I also pm disable com.amazon.otaverifier (although I'm not so sure this is bullet-proof anymore).
The only (poor) option for unrooted is pm hide, which doesn't work on OS 5.1.1. Someone suggested using pm clear with this, but it didn't work for me.
DoLooper said:
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_
Click to expand...
Click to collapse
This is the GOLD standard. What you rename it to is irrelevant; just ditch the 'apk' suffix.
As well as original Stagefright vulnerability CVE-2015-6602 mentioned in the OP, FireOS 5.1.2 may also be vulnerable to the relatively new CVE-2015-1805
Google confirmed that CVE-2015-1805 was already being exploited by a "publicly available rooting application":
https://source.android.com/security/advisory/2016-03-18.html
Zimperium went further and confirmed that the "publicly available rooting application" is KingRoot:
https://blog.zimperium.com/zimperium-applauds-googles-rapid-response-to-unpatched-kernel-exploit/
Affected devices are unpatched Android devices on kernel versions 3.4, 3.10 and 3.14, including Google’s own Nexus 5 and Nexus 6 devices running the March 01, 2016 Security patch level or below.
Click to expand...
Click to collapse
Davey126 said:
This is the GOLD standard. What you rename it to is irrelevant; just ditch the 'apk' suffix.
Click to expand...
Click to collapse
Same as i do i just add a letter after apk and it isnt seen as a application until it is changed back. Very effective
DoLooper said:
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_Has this not worked for some people?
Click to expand...
Click to collapse
Thanks I just did this to stay on 5.1.1.
Here is a link to the original proof of concept files that were sent to Google for CVE-2015-6602:
https://code.google.com/p/android/issues/detail?id=182908
Also, Trend Micro have recently published a detailed blog entry about CVE-2015-1805:
http://blog.trendmicro.com/trendlab...lity-allows-permanent-rooting-android-phones/
Apparently I've missed something somewhere, what does the pm mean in 'pm disable'?
Related
No additional info yet
Exisiting method of root doesn't work.
No visible changes.
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.1_user_321093620.bin hdx 7
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.1_user_321093620.bin hdx 8.9
Still 4.2.2 according to build.prop, in spite of (unreliable) reports of a bump to 4.3 base
HDXPosed did NOT protect against the update on my device.
I am unrooted.
Root Broken
Same here, rooting process does not work as laid out on this update. Hopefully things will come together soon.
Oh no... I haven't even checked mine...
Sent from my iPhone using Tapatalk
I'm currently using Cpasjuste's Xposed stuff in Rom-slot #1 and when I've checked the Settings -> Device -> System Updates, I've still got "Your software is up-to-date" and my version is still in 14.3.1.0_user_310079820
So for me Xposed app still do a good job from the automatic update!
And I did do this too according to Faznx92 "Renaming otacerts.zip to otacerts.zip.old in /etc/security/ might do it but was never tested."
I'll try to update hdxposed as soon as possible I must have missed something.
Envoyé de mon GT-N7100 en utilisant Tapatalk
Cpasjuste said:
I'll try to update hdxposed as soon as possible I must have missed something.
Envoyé de mon GT-N7100 en utilisant Tapatalk
Click to expand...
Click to collapse
I guess I broke updates. I'm not running your program but this is my current HDX Thor setup.
I'm running from a safestrap rom slot
My stock rom has wifi disabled and android firewall blocking everything
From stock I renamed otacerts.zip to otacerts.zip.old in /etc/security/
From stock I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
My rom slot has thor-gapps-rom-2.zip installed on it and android firewall is not running on it
Cpasjuste how does your app block updates? Does it change filenames or what?
Does the update remove Safestrap as well. Mine is off and I will keep it off till we have more info.
Android Cowboy said:
Does the update remove Safestrap as well. Mine is off and I will keep it off till we have more info.
Click to expand...
Click to collapse
It screws everything. Yes safestrap breaks. The HDXPosed app Cpasjuste made doesn't block it. I think I blocked it from updates (read my above post). I think if it updates in a rom slot it updates the stock rom also but I'm not sure. Time for damage control.
As far as I can tell the rename of com.amazon.dcp.apk works. I did that along with Android firewall white list and the otacerts remove . Prior to the dcp apk rename I could go to device settings and do an update check. Renaming the apk stopped that immediately(it will report "Last Update Failed" if you check for an update) so I imagine that app is at least partly responsible for the update.
If this update changes the kindle to android 4.3 safe root should work theoretically.
Sent from my SCH-I545 using Tapatalk
Weirdly enough, the Amazon Kindle Fire HDX Software Updates webpage still listed the most up-to-date version as
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin
lionking2k said:
Weirdly enough, the Amazon Kindle Fire HDX Software Updates webpage still listed the most up-to-date version as
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin
Click to expand...
Click to collapse
They are always late in updating that page. I think they wait to make sure the update has no issues before posting it.
Sent from my Nexus 5 using Tapatalk
I've not even been offered an update yet, just keeps saying I'm up to date.
Maybe cos I'm in the UK, dunno.
I'm completely stock, no root, nothing. Which is surprising for me lol
Me neither.Any benefits of this update?
~Kindlefired~
Hi, could somebody explain how install this with safestrap installed?
Thanks
lionking2k said:
I'm currently using Cpasjuste's Xposed stuff in Rom-slot #1 and when I've checked the Settings -> Device -> System Updates, I've still got "Your software is up-to-date" and my version is still in 14.3.1.0_user_310079820
So for me Xposed app still do a good job from the automatic update!
And I did do this too according to Faznx92 "Renaming otacerts.zip to otacerts.zip.old in /etc/security/ might do it but was never tested."
Click to expand...
Click to collapse
Same here and did nothing with oat.certs. Meaning Xposed has worked fine.
I have safestrap installed but working from stock room.
Sent from my KFTHWI using XDA Premium HD app
What if we modify the build.prop file and put higher versions and date later than any of the new updates will come ? It will see there are no New updates ??
Sent from my KFTHWI using XDA Premium HD app
damianlph said:
What if we modify the build.prop file and put higher versions and date later than any of the new updates will come ? It will see there are no New updates ??
Sent from my KFTHWI using XDA Premium HD app
Click to expand...
Click to collapse
It may still download the update, but the update will not install, instead it shows that the update is older than the installed version.
Just FYI, from what I can tell so far, if you rooted & installed the HDXposed framework on BOTH the stock & working rom slots, the update will not work. I have tested this on at least half a dozen devices.
If you decide to mess with the build.prop, make sure your changes are consistent like they are for the instructions to reflash the current version, i.e. if you were staring anew with the existing firmware version. There are instructions on this in at least three places.
HDX - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.6_user_326001820.bin
HDX 8.9 - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.6_user_326001820.bin
Root possibility - yes, Towelroot.
ONYXis said:
HDX - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.6_user_326001820.bin
HDX 8.9 - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.6_user_326001820.bin
Root possibility - unknown.You can try and tell us)
But boot.img is totally similar to x.3.2.5 and changed files are apps, frameworks and trapz_scripts only. So towelroot must work.
Click to expand...
Click to collapse
2.5 won't let us downgrade currently. I wonder if 3.2.6 will. I really doubt it.
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
r3pwn said:
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
Click to expand...
Click to collapse
Towelroot still works on latest update but can't rollback.
Sent from my GT-N5110 using XDA Free mobile app
ptrsnshane said:
Towelroot still works on latest update but can't rollback.
Sent from my GT-N5110 using XDA Free mobile app
Click to expand...
Click to collapse
I am actually getting closer. I think there is something different in the permissions or something of build.prop. I finally have mine showing the older version. About to try a rollback and see if it works. This is from 3.2.5.
r3pwn said:
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
Click to expand...
Click to collapse
I compared both fw's:
ONYXis said:
But boot.img is totally similar to x.3.2.5 and changed files are apps, frameworks and trapz_scripts only. So towelroot must work.
Click to expand...
Click to collapse
And I think that this is not enough to prevent root possibility.
ONYXis said:
I compared both fw's:
And I think that this is not enough to prevent root possibility.
Click to expand...
Click to collapse
I don't know what you mean by "totally similar", but one small change in the boot image is all that is required to patch towelroot. Take every update with a grain of salt...
Ok. I'm new to bin files. How would one go about flashing a bin file?
Sent from my KFAPWI using Tapatalk
No Change to Kernel or Recovery
r3pwn said:
I don't know what you mean by "totally similar", but one small change in the boot image is all that is required to patch towelroot. Take every update with a grain of salt...
Click to expand...
Click to collapse
No change to kernel or recovery between 3.2.5 and 3.2.6--binary-compared those files within the BIN archive, and they're bit-for-bit identical.
There were noticeable changes to both kernel and recovery between 3.2.4 and 3.2.5 which probably accounts for 3.2.5---and 3.2.6--unable to roll back.
I can confirm that towelroot works.
So how would I flash a bin file?
I guess no one knows then?
Sent from my KFAPWI using Tapatalk
If you are speaking about the update bin file you simply copy it to your sdcard and go to settings/device/system update and check now.
Sent from my VK810 4G using XDA Free mobile app
The Kindle doesn't have an sdcard. Do you mean the emulate/0 folder?
exactly
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
btw kindle has partition named sdcard
Can we use safetrap for this version?
I didn't try
but pretty sure that safestrap would work
iattilagy said:
I can confirm that towelroot works.
Click to expand...
Click to collapse
Just another confirmation that towelroot does support/works to root the latest update ie., 13.3.2.6 :good:
I have not installed SU yet or attempted to block any future updates. I have read that renaming the proper odex file can stop future updates--any info on this method or other ways to accomplish would be appreciated. I would like to prevent losing root when another update comes along.
Thanks all.
kico42 said:
Just another confirmation that towelroot does support/works to root the latest update ie., 13.3.2.6 :good:
I have not installed SU yet or attempted to block any future updates. I have read that renaming the proper odex file can stop future updates--any info on this method or other ways to accomplish would be appreciated. I would like to prevent losing root when another update comes along.
Thanks all.
Click to expand...
Click to collapse
Download the HDX toolkit and use the option to block updates.
ONYXis said:
exactly
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
btw kindle has partition named sdcard
Click to expand...
Click to collapse
Yeah. Meant no physical external Sd card. Which btw, I have an OTG cable but can't get that to work.
Sent from my KFAPWI using Tapatalk
I've just noticed on the Amazon source code download page, Amazon FireOS 5.1.2.1 has been published:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Fire (5th Generation)
Fire_7inch_LC_5.1.2.1.tar.bz2
Click to expand...
Click to collapse
However, at the time of posting the download link currently displays an 'Access Denied' message.
m00head said:
I've just noticed on the Amazon source code download page, Amazon FireOS 5.1.2.1 has now been published:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
However, at the time of posting the download link currently displays an 'Access Denied' message.
Click to expand...
Click to collapse
Interesting - this poster claims Kingroot doesn't work. Wonder if he actually has 5.1.2.1 ...
my son's fire just took the 5.1.2.1 OTA (thought I disabled it...again...), and 5.1.2 root method did not work.
jco23 said:
my son's fire just took the 5.1.2.1 OTA (thought I disabled it...again...), and 5.1.2 root method did not work.
Click to expand...
Click to collapse
I'll simply reference this post for an effective way to block OTA updates. Time proven on multiple devices and multiple versions of FireOS.
How do I know if I have 5.1.2 or 5.1.2.1?
GambitK said:
How do I know if I have 5.1.2 or 5.1.2.1?
Click to expand...
Click to collapse
Settings>Device Options>Updates
Sent from my XT1060 using XDA Labs
sd_shadow said:
Settings>Device Options>Updates
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
It says 5.1.2, not 5.1.2.1 but the root method is still not working.
GambitK said:
It says 5.1.2, not 5.1.2.1 but the root method is still not working.
Click to expand...
Click to collapse
Tried the pc version?
Sent from my XT1060 using XDA Labs
sd_shadow said:
Tried the pc version?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
You mean the PC version of kingroot?
GambitK said:
You mean the PC version of kingroot?
Click to expand...
Click to collapse
yes
Sent from my XT1060 using XDA Labs
sd_shadow said:
yes
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Didn't work either, seems like I have the update even if it doesn't say. I guess I'll have to wait.
GambitK said:
Didn't work either, seems like I have the update even if it doesn't say. I guess I'll have to wait.
Click to expand...
Click to collapse
Could try factory reset and/or adb sideload 5.1.2 firmware in Stock recovery
Sent from my XT1060 using XDA Labs
sd_shadow said:
Could try factory reset and/or adb sideload 5.1.2 firmware in Stock recovery
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
I'm going to try a factory reset right now, and see if it works.
Sideloading 5.1.2 wont brick the device?
GambitK said:
I'm going to try a factory reset right now, and see if it works.
Sideloading 5.1.2 wont brick the device?
Click to expand...
Click to collapse
there have been a couple of reports, that it will not brick
downgrading from 5.1.2.1 to 5.1.2
Sent from my XT1060 using XDA Labs
sd_shadow said:
there have been a couple of reports, that it will not brick
downgrading from 5.1.2.1 to 5.1.2
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Confirming that downgrading and rooting afterwards works.
Thanks for the help.
King root app works on version 5.1.2. I was able to root it and change firmware with flashfire app. I downloaded it from XDA forum.
Kingroot takes few attempts to root. If nothing happens first time try reboot device even if it just rebooted and start app again. Also clear that app from recent menu before launching again.
It took me 4 attempts to finally root it so keep it up and don't give up.
Kingroot wasn't working for me at 5.1.2. What worked was maly82's suggestion.
* Unplug USB from device.
* Remove Kingroot from recent menu
* launch Kingroot again.
First run it rooted successfully. This after multiple attempts with no success, even tried the Kingroot desktop version. Maybe I just got lucky. Maybe removing it from the recent menu is important. IDK. Just throwing it out there.
On another xda thread, someone is reporting their Fire 7 has loaded firmware version 5.1.3.
http://forum.xda-developers.com/showpost.php?p=66436631&postcount=739
That probably why they didn't put up the 5.1.2.1 bin on their website. Probably a pre-released. I'm so glad that I turn off the updates on the 5.1.2 after went back to it.
Do not try to go back to 5.1.2 from 5.1.3.
sd_shadow said:
there have been a couple of reports, that it will not brick
downgrading from 5.1.2.1 to 5.1.2
Click to expand...
Click to collapse
GambitK said:
Confirming that downgrading and rooting afterwards works.
Thanks for the help.
Click to expand...
Click to collapse
Dunard said:
That probably why they didn't put up the 5.1.2.1 bin on their website. Probably a pre-released. I'm so glad that I turn off the updates on the 5.1.2 after went back to it.
Do not try to go back to 5.1.2 from 5.1.3.
Click to expand...
Click to collapse
On 2014 Fires 5.1.2 could be downgraded to 5.1.1 without bricking. Does the same work on 2015 Fire ? Has anyone tried ?
It'd be interesting to try to downgrade one of the newer versions (5.1.2+) back to 5.0.1. It'll probably brick, but if one wants to return Fire to Amazon because of some screen issues or something else, it's a good test to do.
The source code for FireOS 5.3.1.0 has just been released:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Fire (5th Generation)
Fire_7inch_LC_5.3.1.0.tar.bz2
Click to expand...
Click to collapse
Attempting to downgrade to an earlier version will most likely result in bricking your device (now confirmed).
Look like they skip 5.2.1.0.
Unless it a typo. https://en.wikipedia.org/wiki/Fire_OS
Dunard said:
Look like they skip 5.2.1.0.
Unless it a typo. https://en.wikipedia.org/wiki/Fire_OS
Click to expand...
Click to collapse
There has never been a public release of 5.2.x
I'm sure about that. Beta. Turn into Released with a number change.
Dunard said:
I'm sure about that. Beta. Turn into Released with a number change.
Click to expand...
Click to collapse
Yep - not uncommon.
It looks like only the Amazon Fire TV devices had a 5.2.1.0 release:
Amazon Fire TV Device Software Updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Amazon Fire TV
Latest Software Version: 5.2.1.0_user_550144920
Click to expand...
Click to collapse
Went ahead and installed 5.3.1.0 on the 8gb tablet since I don't use it very much. The other one still have the custom ROM.
Dunard said:
Went ahead and installed 5.3.1.0 on the 8gb tablet since I don't use it very much. The other one still have the custom ROM.
Click to expand...
Click to collapse
Did you get it via an OTA update? The binary release page is still on 5.1.4:
Fire (5th Generation) Software Updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Determine your software version
If you have the latest software update, it should look like this: Your device is running Fire OS 5.1.4.
Download Fire (5th Generation) software updates
Download Software Update 5.1.4
Click to expand...
Click to collapse
Know what. You right. Version 5.1.4. I thought it 5.3.1.0. I guest there no ROM yet. Just the source. lol
Kinda new here as I am looking to buy a Kindle Tablet.
When FireOS gets updated, do Amazon put in the latest android security patches? I think Google still releases it for Lollipop.
Reason for this is reading up, to sideload the Playstore you need to disable the OTA, but if the security patch is included then that is something I need to consider.
springy said:
Kinda new here as I am looking to buy a Kindle Tablet.
When FireOS gets updated, do Amazon put in the latest android security patches? I think Google still releases it for Lollipop.
Click to expand...
Click to collapse
yes
Reason for this is reading up, to sideload the Playstore you need to disable the OTA, but if the security patch is included then that is something I need to consider.
Click to expand...
Click to collapse
disabling updates is not necessary, for google framework
Sent from my XT1080 using XDA Labs
sd_shadow said:
disabling updates is not necessary, for google framework
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Ah that is convenient.
So in theory when 5.3.1.0 hits OTA, none of the Google Play Services, framework, Store, should be disabled and delete right if it is already installed?
springy said:
Ah that is convenient.
So in theory when 5.3.1.0 hits OTA, none of the Google Play Services, framework, Store, should be disabled and delete right if it is already installed?
Click to expand...
Click to collapse
sure, but Google framework will work better with a custom rom like cm12.1
Sent from my XT1080 using XDA Labs
springy said:
Ah that is convenient.
So in theory when 5.3.1.0 hits OTA, none of the Google Play Services, framework, Store, should be disabled and delete right if it is already installed?
Click to expand...
Click to collapse
sd_shadow said:
sure, but Google framework will work better with a custom rom like cm12.1
Click to expand...
Click to collapse
Keep in mind Google Framework (Services, Store, etc) compatibility is not assured across FireOS updates. Historically this was more of a problem with FireOS v4 which didn't play well with Google components. Even if it does break someone will likely come up with a fix in short order. That said, I fully agree with @sd_shadow: go with a custom rom for the most favorable experience.
Davey126 said:
Keep in mind Google Framework (Services, Store, etc) compatibility is not assured across FireOS updates. Historically this was more of a problem with FireOS v4 which didn't play well with Google components. Even if it does break someone will likely come up with a fix in short order. That said, I fully agree with @sd_shadow: go with a custom rom for the most favorable experience.
Click to expand...
Click to collapse
How to root a Kindle Kid's Edition that came stock with 5.3.1? I already bricked one following RootJunky's supposed foolproof way to unbrick or downgrade to 5.1.2 to be able to root the device.
fusion01k said:
How to root a Kindle Kid's Edition that came stock with 5.3.1? I already bricked one following RootJunky's supposed foolproof way to unbrick or downgrade to 5.1.2 to be able to root the device.
Click to expand...
Click to collapse
You can't.
fusion01k said:
How to root a Kindle Kid's Edition that came stock with 5.3.1? I already bricked one following RootJunky's supposed foolproof way to unbrick or downgrade to 5.1.2 to be able to root the device.
Click to expand...
Click to collapse
5.3.1.0 cannot be downgraded or rooted
Sent from my XT1080 using XDA Labs
What are the chances that a work around will be realeased? Are they at least greater than zero?
jmorlin said:
What are the chances that a work around will be realeased? Are they at least greater than zero?
Click to expand...
Click to collapse
Please don't cross post. Annoying finding the same inquiry in multiple threads: http://forum.xda-developers.com/ama...pdates-5-1-4-to-5-3-1-0-t3419849/post67865926
Dave and Shadow. Some of the Google Play Store games will crashes on custom ROM's. Wonder 5 Masters works better on FireOS with Google Play Store installed with less crashes. Just pointing this out.
As of August 25 or 26, 2017, the current updated FireOS version is 5.4.0.1. Last build date prior to this was on May 31, 2017. As of this post, the updated OS is not yet available on Amazon's site.
Please comment if you receive any errors when attempting to 'uninstall' Amazon Apps, whether automatically or manually. Some users report errors.
Please download Droid Examiner or Droid Hardware Info or a like minded app (these types of apps vary from developer to developer. I use these two primarily).
Droid Examiner: Tap build and look at the time. It will have the date of the last build updated to your tablet.
build.prop (/system/build.prop): Look for these values. Please post dates and versions if possible. Last Kernel patch for 5.4.0.0 was for June 2017.
Does anyone know if it can be downgraded back to 5.4.0.0?
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
Does anyone know if it can be downgraded back to 5.4.0.0?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Unknown. But 5.4.0.0 CAN be downgraded to 5.3.2.1.
DragonFire1024 said:
Unknown. But 5.4.0.0 CAN be downgraded to 5.3.2.1.
Click to expand...
Click to collapse
I downgraded mine from 5.4.0.0 to 5.3.2.1 today. It was time for a reset anyway. I did as you said and uninstalled the ota junk so it will stay at 5.3.2.1.
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
I downgraded mine from 5.4.0.0 to 5.3.2.1 today. It was time for a reset anyway. I did as you said and uninstalled the ota junk so it will stay at 5.3.2.1.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
I haven't done a reset in a while and I too think I am needing one now that I have most of the system function apps worked out. I think it's time to start experimenting again before I flash my Fire 7 and my phone with custom ROMs.
It's absolutely ridiculous to me that in waning stages of 2017, Amazon is still clinging onto Android Lollipop.
Technocian said:
It's absolutely ridiculous to me that in waning stages of 2017, Amazon is still clinging onto Android Lollipop.
Click to expand...
Click to collapse
Why? It is their Fire OS and they don't want you accessing Oreo or Nougat features, besides, Amazon has there own security patches it it makes no since for them to use a different version, right?
savvytechwinner said:
Why? It is their Fire OS and they don't want you accessing Oreo or Nougat features, besides, Amazon has there own security patches it it makes no since for them to use a different version, right?
Click to expand...
Click to collapse
Between Nougat and Lollipop, there are barely any visually noticeable differences.
Sent from my KFFOWI using Tapatalk
Technocian said:
It's absolutely ridiculous to me that in waning stages of 2017, Amazon is still clinging onto Android Lollipop.
Click to expand...
Click to collapse
What advantage would an Android 6/7/8 base bring to this device given how it is marketed? Newer is not always better depending on objectives. These aren't positioned as generic Android gizmos.
Davey126 said:
What advantage would an Android 6/7/8 base bring to this device given how it is marketed? Newer is not always better depending on objectives. These aren't positioned as generic Android gizmos.
Click to expand...
Click to collapse
The option to use to use the external storage as adopted storage for example.
Hallo32 said:
The option to use to use the external storage as adopted storage for example.
Click to expand...
Click to collapse
Well wait for FireOS 6 I guess. It doesn't seem like anyone wants to make a ROM for the device that uses 6+.
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
Well wait for FireOS 6 I guess. It doesn't seem like anyone wants to make a ROM for the device that uses 6+.
Click to expand...
Click to collapse
Doesn't really care if you have root.
By the way, is there a diff available between 5.4.0.1 and 5.4.0.0?
Hallo32 said:
Doesn't really care if you have root.
By the way, is there a diff available between 5.4.0.1 and 5.4.0.0?
Click to expand...
Click to collapse
I'm assuming that like with 5.3.2.0 and 5.3.2.1, it's a bootloader update possibly with an anti-rollback feature. I may be proven wrong, but we'd need someone running 5.4.0.1 to take the risk and try downgrading.
Sent from my KFFOWI using Tapatalk
Hallo32 said:
The option to use to use the external storage as adopted storage for example.
Click to expand...
Click to collapse
Apps that utilize symbolic linking (eg: Apps2SD; Link2SD) accomplish this while allowing a portion of the SD card to still be used for sharing files with other devices. Adopted storage is great until you pull the SD card or it goes bad. Then things get interesting (as in lost). That said, adopted storage does has an advantage in setup and usability. Pretty much forget about it once established.
---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------
Jake1702_ said:
Well wait for FireOS 6 I guess. It doesn't seem like anyone wants to make a ROM for the device that uses 6+.
Click to expand...
Click to collapse
As you are probably aware talented volunteer contributors can not build a 6.x based ROM for a device with a locked bootloader -and- restricted 5.1 kernel base. "Want" is not the issue ...
@Davey126
I know the risk and as always, don't forget the backups or don't cry.
Apps like Apps2SD and Link2SD are an alternative. But hasn't there been any problems widgets?
Davey126 said:
Apps that utilize symbolic linking (eg: Apps2SD; Link2SD) accomplish this while allowing a portion of the SD card to still be used for sharing files with other devices. Adopted storage is great until you pull the SD card or it goes bad. Then things get interesting (as in lost). That said, adopted storage does has an advantage in setup and usability. Pretty much forget about it once established.
---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------
As you are probably aware talented volunteer contributors can not build a 6.x based ROM for a device with a locked bootloader -and- restricted 5.1 kernel base. "Want" is not the issue ...
Click to expand...
Click to collapse
I'd say as soon as root is made for anything 5.3.2.1+, the main focus should be shifted towards unlocking the bootloader.
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
I'd say as soon as root is made for anything 5.3.2.1+, the main focus should be shifted towards unlocking the bootloader.
Click to expand...
Click to collapse
Unlocking the bootloader is not a trivial job.
Jake1702_ said:
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Is this line really necessary?
Hallo32 said:
Unlocking the bootloader is not a trivial job.
Is this line really necessary?
Click to expand...
Click to collapse
It's possible if we try.
I don't know if you've ever used Tapatalk, but I can't do anything about that line showing up.
Sent from my KFFOWI using Tapatalk
Hallo32 said:
Unlocking the bootloader is not a trivial job.
Is this line really necessary?
Click to expand...
Click to collapse
A lot of time and work has been put into trying to unlock the bootloader. If it were not 'trivial' I'm sure someone might have done it already. Even the rooted HD 7s with custom ROMs have a locked bootloader.
Jake1702_ said:
It's possible if we try.
I don't know if you've ever used Tapatalk, but I can't do anything about that line showing up.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Any ideas how it can be done?
Yes, I had used Tapatalk in past and there has been an option to deactivate the line.
DragonFire1024 said:
A lot of time and work has been put into trying to unlock the bootloader. If it were not 'trivial' I'm sure someone might have done it already. Even the rooted HD 7s with custom ROMs have a locked bootloader.
Click to expand...
Click to collapse
I know it, and that is the point why I wrote, that it is not trivial.