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.
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
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'?
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.
Does current root method work for Nov Tmobile update?
G935TUVU4APK1
I think is does, I'm on it and rooted, but I update ota
Sent from my SM-G935T using XDA-Developers mobile app
jarocho151 said:
I think is does, I'm on it and rooted, but I update ota
Click to expand...
Click to collapse
So when you do an over the air update does it update your bootloader?
Device runs hotter than before with this update, also got a overheated message after I came back to view if update was completed. Never had this before.
Check, another fail I guess.
Limeybastard said:
Device runs hotter than before with this update, also got a overheated message after I came back to view if update was completed. Never had this before.
Check, another fail I guess.
Click to expand...
Click to collapse
Mine was kinda hot during the update but afterwards it's nice and cool
nitroevo said:
Mine was kinda hot during the update but afterwards it's nice and cool
Click to expand...
Click to collapse
Yeah, I paniced, all seems fine now.
The update fixed the annoying YouTube randomly freezing 60 fps video with audio continuing issue :3
How did you guys update? SmartSwitch or via odin? I updated using smartswitch and lost root, not sure if I can re-root it again on the latest version.
I'm also curious If this update is rootable
black96ss said:
I'm also curious If this update is rootable
Click to expand...
Click to collapse
Yea it is
Good night, is there any way to make root sm-g935u t-mobile G935UUEU4API3? The truth at least to my this rom works smoother for me, I only make the root and ready
sirjakey2284 said:
So when you do an over the air update does it update your bootloader?
Click to expand...
Click to collapse
Yes it does.
Sent from my SM-G935T using XDA-Developers mobile app
nitroevo said:
Yea it is
Click to expand...
Click to collapse
Is the root method same as the original method?
Thank you in advance for your help :good:
unk2009 said:
Is the root method same as the original method?
Thank you in advance for your help :good:
Click to expand...
Click to collapse
Yes
Sent from my SM-G935T using XDA-Developers mobile app
Has anyone try using Magisk to root their s7edge?
10507 said:
Has anyone try using Magisk to root their s7edge?
Click to expand...
Click to collapse
Doesn't that only work with the exynos ones
10507 said:
Has anyone try using Magisk to root their s7edge?
Click to expand...
Click to collapse
You think you are gonna get a different answer if you post this question in different threads? If you read about Magisk, you would know it only works with unlocked bootloaders. Maybe in the future someone will get something to work, and as soon as that happens it will be posted here in the forums..
So is this version rootable with engboot or not? I cannot find a definite answer.
dldennis88 said:
So is this version rootable with engboot or not? I cannot find a definite answer.
Click to expand...
Click to collapse
Yea it is.
Has anyone captured the 28.85-17 ota that they can share? I upgraded to 28.85-13, and system update is saying I'm already up to date.
Thanks!
suprdave2 said:
Has anyone captured the 28.85-17 ota that they can share? I upgraded to 28.85-13, and system update is saying I'm already up to date.
Thanks!
Click to expand...
Click to collapse
Check this. Should take you from where you are now to 85-17. Credit to @NZedPred
Sent from my Moto G5 Plus using XDA Labs
??? Where is the link?
Must have forgotten to paste it, my bad.
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78031801
Sent from my Moto G5 Plus using XDA Labs
TargetedNuke said:
Must have forgotten to paste it, my bad.
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78031801
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Tried numerous times and mine will not update from -13 to -17. Sees the update but fails on the installation. Have done hard reset to see if an app was causing the problem. Stops with dead android and "ERROR" in red.
tomlogan1 said:
Tried numerous times and mine will not update from -13 to -17. Sees the update but fails on the installation. Have done hard reset to see if an app was causing the problem. Stops with dead android and "ERROR" in red.
Click to expand...
Click to collapse
Download the file again and try, your file might be corrupted
Ended up flashing updated stock rom with Oct security patch. Don't know why the -13 OTA would not update.
Has the OTA 28.85-17 full ROM (not the TWRP version) leaked yet?
goodjuju said:
Has the OTA 28.85-17 full ROM (not the TWRP version) leaked yet?
Click to expand...
Click to collapse
Look what's in here
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/