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.
Related
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
DO NOT USE THIS METHOD ANYMORE DUE TO BRICKS WITH LATEST DEV PREVIEW. PLEASE FOLLOW ONE OF @DoLooper 'S GUIDES TO GET OS5.0
Warning: I am not responsible for any damage that may occur. Follow this video at your own risk
Just got an email about the Fire OS 5 developer preview. It's available for the fire HD6 and HD7. It runs lollipop.
developer.amazon.com/public/solutions/platforms/android-fireos?sc_channel=EM&sc_campaign=FireOSPreview&sc_detail=GetPreview
It's downloading now on my device. I'll let you know if I figure anything out.
Edit: Amazing update so far. Much closer to stock android! It even has wallpapers enabled by default. It has a few strange grapgical glitches but nothing to worry about. Many of the apps are stock instead of amazonified. For example the browser and even Launcher are stock aosp. Even the recents activity is aosp. I really do like this. If we never get a custom rom, this will be the best choice as an os.
DO NOT USE METHOD DESCRIBED IN THIS VIDEO ANYMORE DUE TO BRICKS ON LATEST DEV PREVIEW. INSTEAD, DOWNLOAD update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin FROM forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810 AND PLACE IT ON THE ROOT OF YOUR SD CARD. THEN GO TO SETTINGS>DEVICE>SYSTEM UPDATES AND PRESS UPDATE etc.
Downgrade Instructions:
1. Download firmware from http://www.amazon.com/gp/help/customer/display.html?nodeId=201596860
2. reboot device into recovery via "adb reboot recovery" or by holding power, volume up, volume down all at the same time on boot
3.use volume and power keys to select "apply update from adb"
4.sideload the firmware with "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
5.wipe data/factory reset
6.reboot
Did you install this via TWRP and kept root, or just the regular Amazon update?
How is the speed? Slower than 4.5.x, or about the same?
bibikalka said:
Did you install this via TWRP and kept root, or just the regular Amazon update?
How is the speed? Slower than 4.5.x, or about the same?
Click to expand...
Click to collapse
regular amazon update. Seems about the same speed
Sent from my LG-V480 using Tapatalk
powerpoint45 said:
regular amazon update. Seems about the same speed
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
So you just gave up on the whole root business ? Back to the Amazon empire for good ?
Amazon probably could not keep up with the changes required for Lollipop 5, and so they are switching to stock versions of stuff. Which is good news for us, those who manage to keep root going forward ! I see the light at the end of the tunnel!
powerpoint45 said:
Edit: Amazing update so far. Much closer to stock android! It even has wallpapers enabled by default. It has a few strange grapgical glitches but nothing to worry about. Many of the apps are stock instead of amazonified. For example the browser and even Launcher are stock aosp. Even the recents activity is aosp. I really do like this. If we never get a custom rom, this will be the best choice as an os
Click to expand...
Click to collapse
Sounds incredible! I don't know about developer previews, so just to clarify: Amazon has killed the carousel and is (finally) providing aosp-like launcher that allows wallpaper?!
Are you testing Kingroot yet? lol!
.
Some pics
bibikalka said:
So you just gave up on the whole root business ? Back to the Amazon empire for good ?
Amazon probably could not keep up with the changes required for Lollipop 5, and so they are switching to stock versions of stuff. Which is good news for us, those who manage to keep root going forward ! [emoji14] I see the light at the end of the tunnel!
Click to expand...
Click to collapse
ya pretty much at least as of now unfortunately. I made the mistake of updating to the 4.x version and lost root so I'm stuck for now
Sent from my LG-V480 using Tapatalk
DoLooper said:
Sounds incredible! I don't know about developer previews, so just to clarify: Amazon has killed the carousel and is (finally) providing aosp-like launcher that allows wallpaper?!
Are you testing Kingroot yet? lol!
.
Click to expand...
Click to collapse
Well at least in the preview. Also I need to check if the amazon Launcher is still disabled. Some reason pm unblock was not working for me earlier. That may have been changed to prevent that stuff.. No KingRoot does not work
Sent from my LG-V480 using Tapatalk
I put up a video if anyone is interested btw
Sent from my LG-V480 using Tapatalk
Kingroot
I tested, and Kingroot unfortunately does not work (which was to be expected).
would it be possible to remove the recovery and bootloader it comes with an flash it to a device with twrp and an unlocked bootloader?
siegesoldier said:
would it be possible to remove the recovery and bootloader it comes with an flash it to a device with twrp and an unlocked bootloader?
Click to expand...
Click to collapse
it is only plausible if we can either root this version so we can grab the partition we want, find the direct download to the bin update file, or somehow grab the update file once it's downloaded via otaverify
Sent from my LG-V480 using Tapatalk
All of the Amazon apps crash for me and an error message saying there was an internal error for third party apps is popping up for me. Is anyone else getting the same problem?
Bahamutmaster said:
All of the Amazon apps crash for me and an error message saying there was an internal error for third party apps is popping up for me. Is anyone else getting the same problem?
Click to expand...
Click to collapse
I'd sugest doing a factory reset
Sent from my LG-V480 using Tapatalk
considering doing that anyway - the screen is extremely twitchy and seems to react if you simply look at it wrong lol.
but I really like this, and probably won't even try to -> 4.5.3 -> root. agree with the comments about lollipop possibly being different enough they may never try to re-spamazon-ify this OS as hard as they have in the past. (but I'll still keep updates blocked if possible lol)
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
oh and good call on speeding up by hitting system update. although surprisingly my did it on its own within minutes of applying for 5.0 on spamazon.
(which is doubly-hilarious, because I had gone through their phone support in an effort to downgrade mine to 4.5.3, and after tens of minutes of trying to convince them that YES IT IS POSSIBLE, they agreed and said it would take up to 24 hours. naturally it never happened, and subsequent calls to try to make it happen were even more painful lol. trying to explain the whole thing again over and over, surprising since obvs they had records/logs of the initial request...)
tarvoke said:
considering doing that anyway - the screen is extremely twitchy and seems to react if you simply look at it wrong lol.
but I really like this, and probably won't even try to -> 4.5.3 -> root. agree with the comments about lollipop possibly being different enough they may never try to re-spamazon-ify this OS as hard as they have in the past. (but I'll still keep updates blocked if possible lol)
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
oh and good call on speeding up by hitting system update. although surprisingly my did it on its own within minutes of applying for 5.0 on spamazon.
(which is doubly-hilarious, because I had gone through their phone support in an effort to downgrade mine to 4.5.3, and after tens of minutes of trying to convince them that YES IT IS POSSIBLE, they agreed and said it would take up to 24 hours. naturally it never happened, and subsequent calls to try to make it happen were even more painful lol. trying to explain the whole thing again over and over, surprising since obvs they had records/logs of the initial request...)
Click to expand...
Click to collapse
You might wamt to do a factory reset as well. Seems to have fixed some of my issues i've had before in 5.0. Good thing you can downgrade without calling now
Sent from my Nexus 7 using Tapatalk
had definitely been considering the reset - thing was getting abominably super-hot and the screen was absolutely not behaving. but next day, it seems to have changed its mind lol. possibly just b/c it cooled down.
I wonder also if some of the weird behavior was due to some spamazon packages still remaining pm-blocked, even after the OS update? obvs a factory reset would clear this, although I could also just use the debloater tool to check. (well, whenever I get a chance to run windows)
also also, can you report any experience with the stock kindle-reader app in this version? (up until now, I have been using the hackified version that I believe you can be thanked for repackaging)
and getting some consistent failures on spamazon-appstore apps, but not all of them. instant video and mp3/music are fine, but xbox-smartglass and spamazon-echo always fail. probably also just indicates need to reset the whole thing...
ryanyz10 said:
I tested, and Kingroot unfortunately does not work (which was to be expected).
Click to expand...
Click to collapse
if kingroot didnt work on 4.5.4 why would it work on 5.0 at all. its not like they released 5.0 with the same vulnerable kernel as 4.5.3 and below
off topic, whoops.
ryanyz10 said:
LOL it's worth a shot. You get nowhere if you don't try. Why are you so mad about it??? It didn't affect you in any way, and you didn't have to reply either.
Click to expand...
Click to collapse
nobody said i was mad about it, that was just your own assumption, and you didnt have to reply either LOL
As the title states, what is a system less root ? This is my first nexus so I'm getting used to the mods, ROMs and bits n bobs.
Cheers in advance.
dladz said:
As the title states, what is a system less root ? This is my first nexus so I'm getting used to the mods, ROMs and bits n bobs.
Cheers in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125
XxMORPHEOUSxX said:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125
Click to expand...
Click to collapse
Previous chainfire supersu writes in the /system partion, specifically in /system/su directory. This makes some of the security conscience application to reject phones that has /system modified. The newer version of chainfire supersu relocate the files to /su directory, and can pass the security check provided the /su/xbin_bind symbolic link is removed.
dyingearth said:
Previous chainfire supersu writes in the /system partion, specifically in /system/su directory. This makes some of the security conscience application to reject phones that has /system modified. The newer version of chainfire supersu relocate the files to /su directory, and can pass the security check provided the /su/xbin_bind symbolic link is removed.
Click to expand...
Click to collapse
Would that mean that previously failed apps which require a non rooted system to work? That's amazing if that's the case.
dladz said:
Would that mean that previously failed apps which require a non rooted system to work? That's amazing if that's the case.
Click to expand...
Click to collapse
Yes. As long as you are on stock, android pay will work with systemless root. You just can't use xposed.
XxMORPHEOUSxX said:
Yes. As long as you are on stock, android pay will work with systemless root. You just can't use xposed.
Click to expand...
Click to collapse
I mean like my work email, (good for enterprise) barclays, Lloyds. Great about android pay.
Is there a workaround for getting Xposed to work or something similar that offers some tweaks?
A tip for someone new to ROMS and flashing. If you use Google Authenticator, or any other authenticator app, like Blizzard Authenticator, or Steam Mobile Guard, make sure you deactivate it before you flash anything.
dladz said:
I mean like my work email, (good for enterprise) barclays, Lloyds. Great about android pay.
Click to expand...
Click to collapse
Hi mate nice to see you finally got yourself a nexus
[emoji106]
Sent from my Nexus 6P using Tapatalk
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
Go Radio said:
Is there a workaround for getting Xposed to work or something similar that offers some tweaks?
Click to expand...
Click to collapse
Just install xposed installer apk then flash the framework no workaround needed mate
Sent from my Nexus 6P using Tapatalk
chubby65 said:
Hi mate nice to see you finally got yourself a nexus
[emoji106]
Sent from my Nexus 6P using Tapatalk
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
Just install xposed installer apk then flash the framework no workaround needed mate
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ello fella, long time no see, yea i bit the bullet, gave work back my HTC m9 and grabbed the 6p, all good up until now, still a bit big but i'm getting used to it.
It's a head turner for sure especially without a case on.
You alright yourself? Good crimbo etc?
dladz said:
Ello fella, long time no see, yea i bit the bullet, gave work back my HTC m9 and grabbed the 6p, all good up until now, still a bit big but i'm getting used to it.
It's a head turner for sure especially without a case on.
You alright yourself? Good crimbo etc?
Click to expand...
Click to collapse
Not bad at all mate a little quite if anything
How's yourself mate
The size won't be an issue after a week or two this really is a beast especially with elementalX
Sent from my Nexus 6P using Tapatalk
chubby65 said:
Not bad at all mate a little quite if anything
How's yourself mate
The size won't be an issue after a week or two this really is a beast especially with elementalX
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not rooted yet. I'll get to it this weekend
Have you got the 6P or the 5?
EDIT: I'm not rooted
dladz said:
I'm not rooted yet. I'll get to it this weekend
Have you got the 6P or the 5?
EDIT: I'm not rooted
Click to expand...
Click to collapse
I've got the 6p mate wasn't that keen on the 5x
I decided as soon as I'd seen both that the 6p was for me but I was unsure with the camera bump
But it's not as much of a bump as I thought it was gonna be
I really wanted the gold one but as it wasn't available I went for the aluminium
Sent from my Nexus 6P using Tapatalk
chubby65 said:
I've got the 6p mate wasn't that keen on the 5x
I decided as soon as I'd seen both that the 6p was for me but I was unsure with the camera bump
But it's not as much of a bump as I thought it was gonna be
I really wanted the gold one but as it wasn't available I went for the aluminium
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Graphite mate, it's enough for me.
How easy is rooting?
Bootloader, recovery, SU, for some reason i get a flag on boot, apparently i didn't decrypt my data partition? Do i need to do that?
dladz said:
Graphite mate, it's enough for me.
How easy is rooting?
Bootloader, recovery, SU, for some reason i get a flag on boot, apparently i didn't decrypt my data partition? Do i need to do that?
Click to expand...
Click to collapse
Encryption is totally up to you mate you don't need to do it
Rooting is very easy
Unlocking the bootloader gives a warning screen before the Google logo appears but is nothing to worry about
Sent from my Nexus 6P using Tapatalk
I went with systemless root but now when I go into recovery I can't see my files in the system. It's just blank and says 0mb. Anyone know why it's happening?
When rooted 'via' systemless root does the stock OTA work?
neisor said:
When rooted 'via' systemless root does the stock OTA work?
Click to expand...
Click to collapse
Apparently not with a custom recovery, afaik, sorry mate, still learning.
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'?
Does anyone know how unlock the bootloader for a Amazon Fire HD 10 (7th Gen)? Does it even need it?
I am going to try to make a custom rom for my Amazon Fire HD 10 (7th Gen) using the code from this. https://www.amazon.com/gp/help/customer/display.html?nodeId=200203720 And try to combine it with stock Android source. How would I install it. adb sideload? Flashfire?
Cannot unlocked the bootloader on 7th Gen Fires
Sent from my PH-1 using Tapatalk
sd_shadow said:
Cannot unlocked the bootloader on 7th Gen Fires
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
That is depressing. I thought I had a way of getting rid of the Fire's rom and move to a more stock version of Android.
I will still be hoping that something comes out.
wherkamp said:
That is depressing. I thought I had a way of getting rid of the Fire's rom and move to a more stock version of Android.
I will still be hoping that something comes out.
Click to expand...
Click to collapse
Provided Flashfire keeps working optimally on these devices then I see no reason why a custom rom couldn't be installed. I just got done moving and am almost set up again. When I am set up, I'll continue my work on a ported ROM.
DragonFire1024 said:
Provided Flashfire keeps working optimally on these devices then I see no reason why a custom rom couldn't be installed. I just got done moving and am almost set up again. When I am set up, I'll continue my work on a ported ROM.
Click to expand...
Click to collapse
Any progress on this since settling in after your move?
Agrajag27 said:
Any progress on this since settling in after your move?
Click to expand...
Click to collapse
So far no. Something is preventing the system partition from being flashed, at least in the HD 10. Since no one has written the exploit to unlock for the 10 yet, I can't see if doing it through recovery makes any difference. I can however flash the system directory with no problem as well as flash unmodified stock boot images and a direct pull of the system.img. anything else is a no go so far. At the moment, well more so tomorrow, I'm going to compile mediatek's fastboot binary. If I can do that, and it works, problems will be solved.
Sent from my MotoG3 using XDA Labs
---------- Post added at 05:00 AM ---------- Previous post was at 04:36 AM ----------
Agrajag27 said:
Any progress on this since settling in after your move?
Click to expand...
Click to collapse
Also tomorrow I'm going to try a few things differently and see if it makes any difference. If it does, I'll he surprised. I'll let you know what I find tomorrow
Sent from my MotoG3 using XDA Labs
@whercamp
See this:
https://forum.xda-developers.com/hd8-hd10/general/bl-unlock-twrp-hd-10-7th-gen-2017-t3904037
We could get an unlock &twrp, but need to get hd10 into the right hands first!