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
Related
OTA for German Retail version from 4.4.2 to 4.4.4 started to roll out finally.
Download:
http://d-h.st/gUF
The name of the file is Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip - as always - it is named after the firmware being updated not after the target one.
Were you on stock recovery but rooted when you got this OTA?
I got this Update today too.
BaghiXDA said:
Were you on stock recovery but rooted when you got this OTA?
Click to expand...
Click to collapse
You can always GET an OTA but you won´t be able to install it in some scenarios.
Your system partition has to be mostly untouched, but root and Xposed Framework won´t cause any problem. You can use stock or Philz Recovery.
Also got the update but the installation is failing due to unexpected changes to build.prop. I have removed xposed and anything else I can think of that may have changed the system partition but still no go.
Any ideas? Maybe someone could post their build.prop?
I'm also getting the update in The Netherlands. Bought my phone online amazon.de :laugh:
patient81 said:
Also got the update but the installation is failing due to unexpected changes to build.prop. I have removed xposed and anything else I can think of that may have changed the system partition but still no go.
Any ideas? Maybe someone could post their build.prop?
Click to expand...
Click to collapse
Here you go. Obviously remove the .txt extension.
Bec de Xorbin said:
Here you go. Obviously remove the .txt extension.
Click to expand...
Click to collapse
Thank you kindly.
drfr said:
OTA for German Retail version from 4.4.2 to 4.4.4 started to roll out finally.
Currently uploading it ....
Here we go:
http://d-h.st/gUF
The name of the file is Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip - as always - it is named after the firmware being updated not after the target one.
Click to expand...
Click to collapse
Can you go to About Phone > Status and tell me what your first 4 numbers of your Imei is? Thanks!
NextGenGTR said:
Can you go to About Phone > Status and tell me what your first 4 numbers of your Imei is? Thanks!
Click to expand...
Click to collapse
Well, I can, but can you tell me why are you asking?
I'm rooted and installed the stock recovery then tried doing the Ota (I'm on stock rom if it matters) and it gives an error, just "error" no more information during the installation process.
Anybody can help?
Sent from my XT1032 using XDA Free mobile app
./.
bad1080 said:
hi, i have an error with the ota update to 4.4.4 myself, my phone is unlocked and rooted (mostly for xframework, xprivacy and gravity box). now i would like to know if i can use the version you have posted?
do i need to reinstall anything after the update? also i would like to know where that version you posted is coming from (is it clean)?
thanks in advance!
Click to expand...
Click to collapse
Yes, you have the right version of firmware for this OTA, don´t know why it´s failing for you, there´s too much variables, it´s hard to tell.
As to where the file I posted comes from - it´s right from my phone. Until today morning I was on French 4.4.4, then I flashed the German 4.4.2 firmware to look if I could catch the OTA and it really came, I pulled it from my /cache and posted here. Check out the MD5 sum: d289331e52d0f79d2bcc4b9b390ff338
It´s the same on my local copy, on the cloud copy I posted and also look here:
http://www.android-hilfe.de/7843052-post301.html
drfr said:
Well, I can, but can you tell me why are you asking?
Click to expand...
Click to collapse
Apparently the update rolls out depending on that 4 numbers, i think it started from something like 3550 and mine is 3593 so i wanted to see if it is close to my number if you get what i mean.
NextGenGTR said:
Apparently the update rolls out depending on that 4 numbers, i think it started from something like 3550 and mine is 3593 so i wanted to see if it is close to my number if you get what i mean.
Click to expand...
Click to collapse
I see, so mine is 3549.
I have 3549 ....en.GB ,no update
Sent from my XT1032 using XDA Free mobile app
drfr said:
I see, so mine is 3549.
Click to expand...
Click to collapse
loungedogg said:
I have 3549 ....en.GB ,no update
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
I am from the UK too, i still dont have any sign of update for 4.4.2, i hope i'm not waiting for a update that is going to make the phone worse...
NextGenGTR said:
I am from the UK too, i still dont have any sign of update for 4.4.2, i hope i'm not waiting for a update that is going to make the phone worse...
Click to expand...
Click to collapse
Why so sceptical? Apart from a different dialer GUI, there´s not much difference you can really feel on 4.4.4, basically there are just some bug fixes.
bad1080 said:
hi, i have an error with the ota update to 4.4.4 myself, my phone is unlocked and rooted (mostly for xframework, xprivacy and gravity box). now i would like to know if i can use the version you have posted?
my phone:
do i need to reinstall anything after the update? also i would like to know where that version you posted is coming from (is it clean)?
thanks in advance!
Click to expand...
Click to collapse
Perhaps you need to uninstall and remove the modules and the xposed from the system before updating. Xposed and the modules add / modify system files and other sources in the device. Make sure you unroot as the last step as well. Stock recovery is required to install the OTA successfully
drfr said:
You can always GET an OTA but you won´t be able to install it in some scenarios.
Your system partition has to be mostly untouched, but root and Xposed Framework won´t cause any problem. You can use stock or Philz Recovery.
Click to expand...
Click to collapse
I just wanted to know, did you also had stock recovery or custom?
Hi All,
Please forgive me if this sounds like a noob question...
Here is the situation:
Rooted verizon galaxy s5 with towel root.
Cannot install the new OTA update they just released, the update downloads and fails on the attempt to install. Shows the little green android with red ! in his belly:cyclops:
Please help! You guys are awesome! I really want this update
nickd1976 said:
Hi All,
Please forgive me if this sounds like a noob question...
Here is the situation:
Rooted verizon galaxy s5 with towel root.
Cannot install the new OTA update they just released, the update downloads and fails on the attempt to install. Shows the little green android with red ! in his belly:cyclops:
Please help! You guys are awesome! I really want this update
Click to expand...
Click to collapse
First, plug phone into computer, and install updater software from the phone that is on the device in 'Installer Mode'. Take the download on the PC, then follow directions below, and you can still have root after.
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For more information, read through this thread as well.
http://forum.xda-developers.com/verizon-galaxy-s5/general/verizon-ota-rolling-t2834027
Thank you so much!!!
Sent from my SM-G900V using XDA Free mobile app
Some reason the upgrade button is greyed out
kprice8 said:
First, plug phone into computer, and install updater software from the phone that is on the device in 'Installer Mode'. Take the download on the PC, then follow directions below, and you can still have root after.
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For more information, read through this thread as well.
http://forum.xda-developers.com/verizon-galaxy-s5/general/verizon-ota-rolling-t2834027
Click to expand...
Click to collapse
Hi again,
I installed the upgrade assistant in installer mode but for some reason it is not picking up the new NE9 update on my computer. See attached print screen. Very strange.. It sees the update on my phone to download though.:cyclops: Do you know why this is and how I can get it to see the update on the upgrade assistant as you mentioned?
Kind Regards
Can you explain why you want the update so bad? You do realize that rooting and accepting official otas is completely contradictory, correct? OTAs are generally what fix things like what towelroot exploits. If you accept official OTA, you will likely lose root.
But can't I just re root after the ota? I guess the reason I want the Ota because I heard of camera enhancements and stability fixes
Sent from my SM-G900V using XDA Free mobile app
nickd1976 said:
But can't I just re root after the ota? I guess the reason I want the Ota because I heard of camera enhancements and stability fixes
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
edit: in this case I believe folks have figured out a work around for keeping root with the update. In general though, if you value root and what it provides you do not accept official releases.
ks3rv3rg said:
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
Click to expand...
Click to collapse
@ks3rv3rg I believe the links mentioned above provide a workaround for the Root to be kept after updating.
As for the problem nick, I can't help you there. I haven't personally take it as I see taking OTA's is silly with a rooted phone you can modify to be much more. Perhaps someone else who has done it will chime in...
Thank you both for your perspectives.. Plus, I can always just wait for a ROM that currently has the update installed.
ks3rv3rg said:
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
edit: in this case I believe folks have figured out a work around for keeping root with the update. In general though, if you value root and what it provides you do not accept official releases.
Click to expand...
Click to collapse
kprice8 said:
@ks3rv3rg I believe the links mentioned above provide a workaround for the Root to be kept after updating.
As for the problem nick, I can't help you there. I haven't personally take it as I see taking OTA's is silly with a rooted phone you can modify to be much more. Perhaps someone else who has done it will chime in...
Click to expand...
Click to collapse
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
nickd1976 said:
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
Click to expand...
Click to collapse
I just saw that JasmineROM came out and it's updated to NE9 and all you do is flash the stuff. Check it out.
http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-jasminerom-v1-0-bases-t2836387
nickd1976 said:
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
Click to expand...
Click to collapse
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
ks3rv3rg said:
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
Click to expand...
Click to collapse
Me? Directly above you? XD lol
ks3rv3rg said:
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
Click to expand...
Click to collapse
I think you are referring to my safestrap flashable OTA zip file. I'm going to keep that one in my back pocket for the next OTA since the kernel swap worked.
I'm happy to say I installed this rom and the firmware and it rocks!! Thank you .plus I got my download booster and my overclock settings!!
Sent from my SM-G900V using XDA Free mobile app
I have a similar question but reversed. How do I stop it from updating and it from asking me to update? I have the free version of titanium backup and can't freeze it. Is their another way? I can't turn off SDM that runs the ota upgrade i can only force stop it.
jpcloudsurf said:
I have a similar question but reversed. How do I stop it from updating and it from asking me to update? I have the free version of titanium backup and can't freeze it. Is their another way? I can't turn off SDM that runs the ota upgrade i can only force stop it.
Click to expand...
Click to collapse
Remove it. Won't hurt anything.
TiBu
Buying the pro version of TiBu was the best money I ever spent!!!!
What is tibu?
Sent from my SM-G900V using XDA Free mobile app
nickd1976 said:
What is tibu?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Titanium Backup
Hey guys- success! I updated my wife's phone from the 4.1.2 via RSD Lite to 4.4.2 rooted it via towel root and unlocked my bootloader thanks to motopocolypse.apk Thanks for all the help!
So I have a new issue though being that this is my wife's phone see will no doubt try to install this update- I just want to remove the temptation all together! See the attached pic. No sooner than when I updated this I get this update nag- I am sure this is a patch to .10 to .15 as I am a noob o this phone. I do not see a stock debloated rom for this- maybe a little help to remove this nag-
Thanks!
EDIT- use root explorer root/cache/ delete update Go to /system /priv-app find ConfigUpdate.apk and rename to ConfigUpdate.apk.bak no more nag
rwcasto said:
Hey guys- success! I updated my wife's phone from the 4.1.2 via RSD Lite to 4.4.2 rooted it via towel root and unlocked my bootloader thanks to motopocolypse.apk Thanks for all the help!
So I have a new issue though being that this is my wife's phone see will no doubt try to install this update- I just want to remove the temptation all together! See the attached pic. No sooner than when I updated this I get this update nag- I am sure this is a patch to .10 to .15 as I am a noob o this phone. I do not see a stock debloated rom for this- maybe a little help to remove this nag-
Thanks!
EDIT- use root explorer root/cache/ delete update Go to /system /priv-app find ConfigUpdate.apk and rename to ConfigUpdate.apk.bak no more nag
Click to expand...
Click to collapse
You could also delete or rename 3c_ota.apk.
Code:
/ system / priv-app / 3c_ota.apk
You're unlocked, so why not take the update?
ATTACK said:
You could also delete or rename 3c_ota.apk.
Code:
/ system / priv-app / 3c_ota.apk
You're unlocked, so why not take the update?
Click to expand...
Click to collapse
I was worried that it would bork the bootloader- did not realize it would be ok
rwcasto said:
I was worried that it would bork the bootloader- did not realize it would be ok
Click to expand...
Click to collapse
Yup, As long as your bootloader is unlocked, you can take any and all updates.
Sent from my Scorpion Mini
Anyone know what the new update does?
Sent from my XT907 using XDA Free mobile app
ATTACK said:
Yup, As long as your bootloader is unlocked, you can take any and all updates.
Sent from my Scorpion Mini
Click to expand...
Click to collapse
Thanks bro!
mrkhigh said:
Anyone know what the new update does?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Moto still has not posted a changelog for .15 > https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/87530/p/30,6720,8577
But what I do know is that they patched FakeID, Futex & TrustZone. Also SMS/MMS fixes.
I'll pass on the update then it took me a while to get stock kitkat to not kill battery life.
Sent from my XT907 using XDA Free mobile app
Hello,
I popped into the Sammobile website today and noticed a new firmware for our beloved Note 10.1 (2013 edition.) The build number is N8013UEUCOI1 and was released on 10/1/2015, but unfortunately it's still on Jellybean 4.1.2. It's a 1.1GB download and looks like it's made for the Americas. I haven't seen any posts about it online. Has anybody tried it out to see what it is? What new changes/improvements there are or if it contains KNOX? I would try it out myself but I'm currently using my Note for work and I can't risk any negative outcomes since I'm in the middle of an important project.
Thanks in advance!
Use the report button and ask a mod to move your question to the Q&A section.
I updated my N8013 to COI1 using Kies with no issue from CMI3 that was rooted. I did need to re-root using method here: http://forum.xda-developers.com/showthread.php?t=1831152, I used the 2nd method. I didn't wipe any data and haven't seen any issues with apps or Superuser. It does appear to have fixed Stagefright issues but is still vulnerable to CVE-2015-6602, the rest are covered though.
firestorm126 said:
I updated my N8013 to COI1 using Kies with no issue from CMI3 that was rooted. I did need to re-root using method here: http://forum.xda-developers.com/showthread.php?t=1831152, I used the 2nd method. I didn't wipe any data and haven't seen any issues with apps or Superuser. It does appear to have fixed Stagefright issues but is still vulnerable to CVE-2015-6602, the rest are covered though.
Click to expand...
Click to collapse
CM13?
kurokeita said:
cm13?
Click to expand...
Click to collapse
n8013ueucmi3
ah, i thought you said cyanogenmod 13
Sent from my HTC One using Tapatalk
firestorm126 said:
I updated my N8013 to COI1 using Kies with no issue from CMI3 that was rooted. I did need to re-root using method here: http://forum.xda-developers.com/showthread.php?t=1831152, I used the 2nd method. I didn't wipe any data and haven't seen any issues with apps or Superuser. It does appear to have fixed Stagefright issues but is still vulnerable to CVE-2015-6602, the rest are covered though.
Click to expand...
Click to collapse
Was thinking of taking the ota, but concerned for root. Thanks for the details and links!
BBB
Someone 4 everyone
Sent from my XT1254 using Tapatalk
Kies 2.6 installed latest on my rooted note 10.1. After ran through the method 2 to restore root and all is good.
Loving it. Seems faster and much more responsive.
BBB
Eat @ Moe's
Sent from my XT1254 using Tapatalk
firestorm126 said:
I updated my N8013 to COI1 using Kies with no issue from CMI3 that was rooted. I did need to re-root using method here: http://forum.xda-developers.com/showthread.php?t=1831152, I used the 2nd method. I didn't wipe any data and haven't seen any issues with apps or Superuser. It does appear to have fixed Stagefright issues but is still vulnerable to CVE-2015-6602, the rest are covered though.
Click to expand...
Click to collapse
Can you rehost the file on google drive or somewhere that is faster than 40 kbps? These paywall data caps are annoying..
Gladpants said:
Can you rehost the file on google drive or somewhere that is faster than 40 kbps? These paywall data caps are annoying..
Click to expand...
Click to collapse
Rehost what file?
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'?