51.1.2.0_user_512073320 Source Code Uploaded - Fire TV General

Amazon has already made the current "root blocking" software update's source code available. This is a bit strange since for the previous version, 51.1.1.0_user_511070220, they didn't upload the source until the update was "official" (i.e., their documentation page listed it as the latest version).
I've created a page at AFTVnews.com/software to keep track of all the Fire TV software versions. Feel free to comment on the page or in this thread if I'm missing any information, or I have something listed incorrectly.

AFTVnews.com said:
Amazon has already made the current "root blocking" software update's source code available. This is a bit strange since for the previous version, 51.1.1.0_user_511070220, they didn't upload the source until the update was "official" (i.e., their documentation page listed it as the latest version).
I've created a page at AFTVnews.com/software to keep track of all the Fire TV software versions. Feel free to comment on the page or in this thread if I'm missing any information, or I have something listed incorrectly.
Click to expand...
Click to collapse
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.

rbox said:
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.
Click to expand...
Click to collapse
perhaps puts to the kernel build tree is frozen. it may be a simple file change which breaks it. They released the code to show you where it wasn't so you could undo. I'm sure there is a smart developer who knows leaving it open to towelroot means more device sales. he just has to appease his boss who was given the call "shut it down"

rbox said:
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.
Click to expand...
Click to collapse
That's very interesting. So you're saying it looks like they explicitly blocked towelroot without patching the exploit that towelroot uses?

AFTVnews.com said:
That's very interesting. So you're saying it looks like they explicitly blocked towelroot without patching the exploit that towelroot uses?
Click to expand...
Click to collapse
No. I think they patched the kernel but didn't include that change in the source drop.

Is it possible that towelroot may still work on the latest update with some tweaks to the modstrings?

rbox said:
No. I think they patched the kernel but didn't include that change in the source drop.
Click to expand...
Click to collapse
Ah, ok. That does make more sense.

{ParanoiA} said:
Is it possible that towelroot may still work on the latest update with some tweaks to the modstrings?
Click to expand...
Click to collapse
If I put trust in Amazon that they didn't slip a change in the kernel without putting it in the source drop, then that's a possibility. I don't really know much about towelroot, but I did notice about the modstrings when I was reading about it.

I guess the only way to tell would be to diff the firmware update instead of the source?

Related

Source Code, get your Source Code here

Amazon has published the source code for the Fire TV at http://www.amazon.com/gp/help/customer/display.html?nodeId=201452680
Please code responsibly.
35395596831
elmerohueso said:
Amazon has published the source code for the Fire TV at ...
Please code responsibly.
Click to expand...
Click to collapse
PSA: I've tracked the kernel part of the code drop back to the closest msm-3.4 tag, so we have a partial git history. Please use that as a starting point rather than importing the kernel src into a new git tree without history:
git://github.com/freedreno/kernel-msm firetv
robclark said:
PSA: I've tracked the kernel part of the code drop back to the closest msm-3.4 tag, so we have a partial git history. Please use that as a starting point rather than importing the kernel src into a new git tree without history:
git://github.com/freedreno/kernel-msm firetv
Click to expand...
Click to collapse
This does not appear to match the binary... wth Amazon
*EDIT*
Your source was for the first release they did, the initial OTA came with a new kernel, and numerous fixes, including fixing the get_user/put_user vuln (CVE-2013-6282) which was what caused the confusion. Binary not vuln, but your source was.
My bad for not pulling their latest source.
jcase said:
This does not appear to match the binary... wth Amazon
Click to expand...
Click to collapse
hmm, well no guarantees amazon actually posted the correct kernel dump.. that could be an extra headache. I'm a bit new to the android side of things so don't really know what Amazon's track record is like.
fwiw, the src drop I grabbed kernel from was firetv_src_51.1.0.1_user_510055620.tar.bz2 (md5sum: 0cba752bd8e6154667120718efe619b2)
---------- Post added at 12:15 AM ---------- Previous post was at 12:05 AM ----------
jcase said:
This does not appear to match the binary... wth Amazon
*EDIT*
Your source was for the first release they did, the initial OTA came with a new kernel, and numerous fixes, including fixing the get_user/put_user vuln (CVE-2013-6282) which was what caused the confusion. Binary not vuln, but your source was.
My bad for not pulling their latest source.
Click to expand...
Click to collapse
oh, whoops, should have read your later reply first
when I get my fire-tv tomorrow, should I take steps to avoid OTA update?
robclark said:
hmm, well no guarantees amazon actually posted the correct kernel dump.. that could be an extra headache. I'm a bit new to the android side of things so don't really know what Amazon's track record is like.
fwiw, the src drop I grabbed kernel from was firetv_src_51.1.0.1_user_510055620.tar.bz2 (md5sum: 0cba752bd8e6154667120718efe619b2)
---------- Post added at 12:15 AM ---------- Previous post was at 12:05 AM ----------
oh, whoops, should have read your later reply first
when I get my fire-tv tomorrow, should I take steps to avoid OTA update?
Click to expand...
Click to collapse
hmm you sure? firetv_src_51.1.0.1_user_510055620.tar.bz2 is not vulnerable, but the source you linked to is
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Blocking the server providing the OTA alone won't allow it to boot, intercepting it and telling the unit that no ota is available probably would.
so is the OTA gonna patch the vuln that allows root ?
jcase said:
hmm you sure? firetv_src_51.1.0.1_user_510055620.tar.bz2 is not vulnerable, but the source you linked to is
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Blocking the server providing the OTA alone won't allow it to boot, intercepting it and telling the unit that no ota is available probably would.
Click to expand...
Click to collapse
hmm, can you check md5sum on the file you got and see if it matches what I have. There were two files available to download when I grabbed the src drop..
fwiw, it is no problem to update the kernel to a newer src drop.. the only thing that will take any time is actually downloading the src drop
robclark said:
hmm, can you check md5sum on the file you got and see if it matches what I have. There were two files available to download when I grabbed the src drop..
fwiw, it is no problem to update the kernel to a newer src drop.. the only thing that will take any time is actually downloading the src drop
Click to expand...
Click to collapse
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
jcase said:
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
Click to expand...
Click to collapse
damn.. well, I'll go ahead and download the other tarball (will take a while, on slow network connection at the moment) and import it on another branch and see what the difference is..
btw, if anyone else has downloaded firetv_src_51.1.0.1_user_510055620.tar.bz2 more recently, could you check md5sum to see if file has changed since the day of the announcement?
bkdg100 said:
so is the OTA gonna patch the vuln that allows root ?
Click to expand...
Click to collapse
OTA patched at least two that would have allowed root. Doesn't patch the one I am working with right now.
robclark said:
damn.. well, I'll go ahead and download the other tarball (will take a while, on slow network connection at the moment) and import it on another branch and see what the difference is..
Click to expand...
Click to collapse
I can redownload it if it is a bother, no big deal.
jcase said:
I can redownload it if it is a bother, no big deal.
Click to expand...
Click to collapse
well, if you have a good network connection, you can probably get it faster than I can..
I'm keeping all the files I download (not out of disk space yet).. tomorrow when I have a good connection I'll grab firetv_src_51.1.0.1_user_510055620.tar.bz2 again to check (if no one has confirmed before then)
just got mine tonight , figured i would hold off on the updates until a secure root exploit id posted,. anyone script a network mitm to spoof the update for now?
bkdg100 said:
just got mine tonight , figured i would hold off on the updates until a secure root exploit id posted,. anyone script a network mitm to spoof the update for now?
Click to expand...
Click to collapse
I believe it force updates OTAs, so no holding off
jcase said:
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Click to expand...
Click to collapse
btw if anyone else did get a packet trace of it contacting the ota server, I'd be interested to see it. (Well, if no one replies before tomorrow when my box, then don't bother, I can get the trace myself. I'm just impatiently waiting now )
is your root exploit secure enough to outlive the updates ? any chance a virgin box can be spoofed later to limit the OTA from patching everything ?
robclark said:
btw if anyone else did get a packet trace of it contacting the ota server, I'd be interested to see it. (Well, if no one replies before tomorrow when my box, then don't bother, I can get the trace myself. I'm just impatiently waiting now )
Click to expand...
Click to collapse
Not to my knowledge, possibly if you can feed it a low version number then you can boot without taking the OTA, and then use public roots
bkdg100 said:
is your root exploit secure enough to outlive the updates ? any chance a virgin box can be spoofed later to limit the OTA from patching everything ?
Click to expand...
Click to collapse
Amazon updates reflash everything, they don't do delta updates. No ota survival
jcase said:
OTA patched at least two that would have allowed root. Doesn't patch the one I am working with right now.
Click to expand...
Click to collapse
just ran the bluebox app for the heck of it - it claims my firetv is safely patched for 8219321, 9695860, and 10148349 (those are the only 3 it tests for) - yes, I do have the ota update.
are there other recent ones android-using peoples of the world should be aware about? 9950697?
tarvoke said:
just ran the bluebox app for the heck of it - it claims my firetv is safely patched for 8219321, 9695860, and 10148349 (those are the only 3 it tests for) - yes, I do have the ota update.
are there other recent ones android-using peoples of the world should be aware about? 9950697?
Click to expand...
Click to collapse
I checked all of the zip parser bugs first, obvious choice considering it runs 4.2.2.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
jcase said:
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
Click to expand...
Click to collapse
I've pushed firetv-0 branch which is from firetv_src_51.1.0_user_510047320.tar.bz2 ... definitely looks like some additional error checking, etc, between the two. Maybe what I thought was the original src drop was the update and visa versa. Not what I'd expect given the file names, but it would explain...

Software Update version 51.1.3.0_user_513011820

Amazon has posted the source code for version 51.1.3.0_user_513011820 on their US source code page. So far, I've only heard of German Fire TVs receiving this update, so it's a bit odd for it to be posted on the US source code page but not on the German source code page.
I was thinking this version wouldn't get pushed to the US, but I may be wrong. My guess is it's an insignificant update from the previous version, 51.1.3.0_user_513011520, but it's always good to be aware of it and see if anyone gets it.
AFTVnews.com said:
Amazon has posted the source code for version 51.1.3.0_user_513011820 on their US source code page. So far, I've only heard of German Fire TVs receiving this update, so it's a bit odd for it to be posted on the US source code page but not on the German source code page.
I was thinking this version wouldn't get pushed to the US, but I may be wrong. My guess is it's an insignificant update from the previous version, 51.1.3.0_user_513011520, but it's always good to be aware of it and see if anyone gets it.
Click to expand...
Click to collapse
And the results are in... the two 51.1.3.0 archives are identical.
One of my Fire TVs just got this new version, so I guess it isn't just for German devices. I'll report back any changes I can find shortly.
@rbox The download URL is http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.3.0_user_513011820-signed.bin for your pre-rooted making needs.
Edit: My sacrificial Fire TV that I let update to everything hasn't gotten it yet, so it may be a bit before I can uncover the changes.
AFTVnews.com said:
One of my Fire TVs just got this new version, so I guess it isn't just for German devices. I'll report back any changes I can find shortly.
@rbox The download URL is http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.3.0_user_513011820-signed.bin for your pre-rooted making needs.
Click to expand...
Click to collapse
Excellent. I'll whip it up tonight.
Interesting thing I have 513011820 since 26.09.2014 according to the Infopage at Fire.
Kindle-Fan said:
Interesting thing I have 513011820 since 26.09.2014 according to the Infopage at Fire.
Click to expand...
Click to collapse
Yeah, they started pushing it around that time. But it wasn't a widespread deployment.
I've combed through the interface and all the menus and haven't found a single difference between 51.1.3.0_user_513011520 and this new version, 51.1.3.0_user_513011820. Seems like whatever this update brings is completely behind the scenes.
Received this update last night on my one that is not rooted. Didn't find any changes.
I'm running this version and my FTV isn't rooted, when I try to root, it TowelRoot says my phone isn't supported. Am I SOL for the time being?
krakn3dfx said:
i'm running this version and my ftv isn't rooted, when i try to root, it towelroot says my phone isn't supported. Am i sol for the time being?
Click to expand...
Click to collapse
this post is epic fail!
Krakn3Dfx said:
I'm running this version and my FTV isn't rooted, when I try to root, it TowelRoot says my phone isn't supported. Am I SOL for the time being?
Click to expand...
Click to collapse
See AFTVnews.com/software to know which software versions can be rooted. The latest version, 51.1.3.0, cannot be rooted.
AFTVnews.com said:
See AFTVnews.com/software to know which software versions can be rooted. The latest version, 51.1.3.0, cannot be rooted.
Click to expand...
Click to collapse
Cannot be rootedhttp://cdn3.xda-developers.com/images/smilies/crying.gif ? Or will be able to root someday?
Lightman62 said:
Cannot be rootedhttp://cdn3.xda-developers.com/images/smilies/crying.gif ? Or will be able to root someday?
Click to expand...
Click to collapse
No one knows. It will require a new exploit to be found. I imagine one day it will be rootable again but that is just a guess.
Sent from my SCH-I545 using Tapatalk
My amzon fire tv is still on pre-order and will be delivered on 26th this month so I was wondering if it will most likley have a software version which cannot be rooted? If so should I cancel the order since it seems unlikley that there will ever be a root available for the newer versions.
Shinigami_Ryuk said:
My amzon fire tv is still on pre-order and will be delivered on 26th this month so I was wondering if it will most likley have a software version which cannot be rooted? If so should I cancel the order since it seems unlikley that there will ever be a root available for the newer versions.
Click to expand...
Click to collapse
If it's a german version there is no "most likely". The German units ship with 51.1.3.0. As for being unrootable... there might be another kernel exploit, there might be an android exploit. No one knows.
rbox said:
If it's a german version there is no "most likely". The German units ship with 51.1.3.0. As for being unrootable... there might be another kernel exploit, there might be an android exploit. No one knows.
Click to expand...
Click to collapse
I am in the UK so I would think that it would be shipping from the UK and not the German version I suppose?
Shinigami_Ryuk said:
I am in the UK so I would think that it would be shipping from the UK and not the German version I suppose?
Click to expand...
Click to collapse
Version 51.1.3.0 added support for UK Amazon acounts so it is very unlikely that UK Fire TVs will arrive with a software version older than 51.1.3.0. In other words, it is very unlikely UK Fire TVs will be rootable at this time. Like rbox said, theres no way to know what the future will bring as far as new roots.
AFTVnews.com said:
Version 51.1.3.0 added support for UK Amazon acounts so it is very unlikely that UK Fire TVs will arrive with a software version older than 51.1.3.0. In other words, it is very unlikely UK Fire TVs will be rootable at this time. Like rbox said, theres no way to know what the future will bring as far as new roots.
Click to expand...
Click to collapse
Thank you for the info, I guess I could simply hold on to it and see what the future holds especially since I got it at the disscount price of £49.
I got this version pushed OTA sucks because I had root and didn't know had to disable OTAs but on the other hand I noticed this update lets you enable install apps from unknown sources so can we still get play store if I push the necessary files to the fire and I can install through ES File explorer????
No, play store won't work correctly without xposed. Xposed needs root.

Firestick 1st gen update

Will 1st gen firestick get the 5.0.5 update? Stuck on 5.0.3 atm
I'd like to know that as well.
Sent from my iPhone using Tapatalk
fach1708 said:
Will 1st gen firestick get the 5.0.5 update? Stuck on 5.0.3 atm
Click to expand...
Click to collapse
patt2k said:
I'd like to know that as well.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
yes I have gotten it on ver 1 of stick and tv and have rooted both already
timezone12 said:
yes I have gotten it on ver 1 of stick and tv and have rooted both already
Click to expand...
Click to collapse
but how did you get it on beta firmware 5.0.3?
everyone who seems to have received the update was not on 5.0.3. I have yet to see anyone on 5.0.3 confirm they were able to update to 5.0.5.
I'm on 5.0.3 myself.
apparently we can root with kingroot on 5.0.3... so depending on how soon things get figured out related to custom recovery... rooting on 5.0.3 then using a custom recovery and pre-rooted 5.0.5 rom may be quicker than waiting on Amazon.
autoprime said:
everyone who seems to have received the update was not on 5.0.3. I have yet to see anyone on 5.0.3 confirm they were able to update to 5.0.5.
I'm on 5.0.3 myself.
apparently we can root with kingroot on 5.0.3... so depending on how soon things get figured out related to custom recovery... rooting on 5.0.3 then using a custom recovery and pre-rooted 5.0.5 rom may be quicker than waiting on Amazon.
Click to expand...
Click to collapse
I'm still waiting on the update URL for the stick. I need either the url from os3 to os5, or the url for beta to 5.0.5.
rbox said:
I'm still waiting on the update URL for the stick. I need either the url from os3 to os5, or the url for beta to 5.0.5.
Click to expand...
Click to collapse
I've been actively logging in hopes to grab the FTV Stick 5.0.3 -> 5.0.5 URL but at by the looks of it someone going from 3.x -> 5.0.5 should be able to grab it first. We shall see... :fingers-crossed:
autoprime said:
I've been actively logging in hopes to grab the FTV Stick 5.0.3 -> 5.0.5 URL but at by the looks of it someone going from 3.x -> 5.0.5 should be able to grab it first. We shall see... :fingers-crossed:
Click to expand...
Click to collapse
5 to 5 updates are all incremental, and I have them already. I need the 3.x -> 5.0.x update to get the full system image.
I have another stick on it's way from Amazon.co.uk, if it comes with 3.x how do I get what you need?
D-an-W said:
I have another stick on it's way from Amazon.co.uk, if it comes with 3.x how do I get what you need?
Click to expand...
Click to collapse
I just received the URLs from @AFTVnews.com
rbox said:
I just received the URLs from @AFTVnews.com
Click to expand...
Click to collapse
Is there any chance these will be urls will be posted, or is it worth posting, or some risk if they are posted? Couldn't we use the url to copy the image and force the update? I guess now that you have the URLs the best things will come, but I definitely want to get my stick to a rootable place =)
ImCoKeMaN said:
Is there any chance these will be urls will be posted, or is it worth posting, or some risk if they are posted? Couldn't we use the url to copy the image and force the update? I guess now that you have the URLs the best things will come, but I definitely want to get my stick to a rootable place =)
Click to expand...
Click to collapse
AFTVNews used to have a list of software updates and their URLs. Dunno if it still does. Unfortunately you can't force the update, as you need to be able to write to /cache to do it.
rbox said:
AFTVNews used to have a list of software updates and their URLs. Dunno if it still does. Unfortunately you can't force the update, as you need to be able to write to /cache to do it.
Click to expand...
Click to collapse
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times
ImCoKeMaN said:
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times
Click to expand...
Click to collapse
The software talks to the update server over ssl and sends it encrypted data. Can't be faked.
Just got the update on the firetv stick today. I guess I can kingroot it now, but is there any chance that there will be another root method for these?
Update: used kingroot 4.1 and it said it failed, but after a reboot it was in fact rooted. Next used adb with su command to pm disable dcp and ota
ImCoKeMaN said:
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times
Click to expand...
Click to collapse
I've been meaning to update that page for some time now. It needs to be completely redone since there are now newer devices and forks due to the dev preview and the voice vs non-voice Fire TV Stick split.
The URLs are no secret. I hope to get around to updating my software page next week. For the time being, here is everything missing from that page for those interested.
Fire TV Update URLS
2nd-gen: 5.0 to 5.0.2.1
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-521044920-to-531006320.bin
2nd-gen: 5.0.2.1 to 5.0.2.2
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006320-to-531006420.bin
2nd-gen: 5.0 to 5.0.2.2
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-521044920-to-531006420.bin
2nd-gen: 5.0.2.2 to 5.0.3
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006420-to-532011220.bin
2nd-gen: 5.0.2.1 to 5.0.3
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006320-to-532011220.bin
2nd-gen: 5.0.3 to 5.0.3.1
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-532011220-to-534011720.bin
1st-gen Dev Preview - v5.0.3 (previous one is 5.0.0)
http://amzdigitaldownloads.edgesuit...te-kindle-bueller-51.5.3.2_user_532008220.bin
2nd-gen: 5.0.3.1 (534011720) to 5.0.4 (536116920)
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-534011720-to-536116920.bin
2nd-gen: 5.0.4 (536116920) to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-536116920-to-537174420.bin
1st-gen: 51.1.6.3 to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-kindle-bueller-51.5.3.7_user_537174420.bin
—————————————————————————
Fire TV Stick Update URLs
Production (non-voice) 54.1.2.3 (123067020)
http://amzdigitaldownloads.edgesuit...6fbe3/montoya-ota-54.1.2.3_user_123067020.bin
Dev Preview 5.0 (530042950)
http://amzdigitaldownloads.edgesuit...evpreview_montoya-54.5.3.0_user_530042950.bin
Dev Preview from 5.0 (530042950) to 5.0.3 (532008220)[54.5.3.2]
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.2_user_532008220.bin
Production (voice bundle) 5.0.3.2 (535062120) to 5.0.3.2/3 (535062420)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-535062120-to-535062420.bin
Production (voice bundle) 5.0.3.2/3 (535062420) to 5.0.4 (536116920)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-535062420-to-536116920.bin
Production (voice bundle) 5.0.4 (536116920) to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-536116920-to-537174420.bin
Production (non-voice) 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin

Rooted, surprised not on here:

Hope some XDAers are able to get it rooted before it gets patched.
http://www.androidheadlines.com/201...te-available-for-android-root-access-bug.html
This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.
But, can we just load an older build using an auto-loader ?
Artemis-kun said:
This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.
Click to expand...
Click to collapse
I haven't.
santimaster2000 said:
But, can we just load an older build using an auto-loader ?
Click to expand...
Click to collapse
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader
Tipika said:
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader
Click to expand...
Click to collapse
This is not BB10, this is Android, and yes, I can downgrade, I've tested it.
can root using this exploit?
A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.
Seeing all those one click root apps i was thinking it was going to be easier to root the priv once an exploit was found
Sent from my Nexus 5X using XDA-Developers mobile app
FrankenDroid said:
A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.
Click to expand...
Click to collapse
Could you link me to that post please ?
Boom, right here: https://github.com/dosomder/iovyroot
So does this mean one can downgrade and then root using iovyroot?
Shani Ace said:
So does this mean one can downgrade and then root using iovyroot?
Click to expand...
Click to collapse
Theoretically, yes, you would need to add the absolute kernel addresses of the Priv to the source code, then compile it, but still, you would only get temp root, that's only good for using Titanium Backup and the like.
Ah okay, I understand.
So this root is only temp then? Still hoping something comes out but the community seems very small.

New exploit available for LG G5: QuadRooter

A set of exploits has been found by Check Point, allowing malicious apps to get root privilege.
blog.checkpoint.com/2016/08/07/quadrooter/
I'll turn off OTA from now on and wait for tools that make use of this exploit.
QuadRooter is a set of four vulnerabilities affecting Android devices built using Qualcomm chipsets. Qualcomm is the world’s leading designer of LTE chipsets with a 65% share of the LTE modem baseband market. If any one of the four vulnerabilities is exploited, an attacker can trigger privilege escalations for the purpose of gaining root access to a device.
Click to expand...
Click to collapse
How do you turn off ota ? I can't find it
there are 4 exploits that are already patched
might be a way if you have pre-April firmware installed
https://gwolf2u.com/quadrooter-android-security-bugs-affect-over-900-million-devices/
I have 3 of the 4 exploits. I have Sprint
I have the latest v10d firmware on my H850 and the app shows me 4 of 4 vulnerable.
2016-06-01 security patch
fsi09 said:
I have the latest v10d firmware on my H850 and the app shows me 4 of 4 vulnerable.
2016-06-01 security patch
Click to expand...
Click to collapse
mine as well
on v10d
H868 reports 4/4 with the latest security patch.
For those who want to root their G5, search for "update" in Settings and turn off auto update.
Is this what we've been waiting for? Ridiculously excited if so, will this help rs988?
muppetmaster916 said:
Is this what we've been waiting for? Ridiculously excited if so, will this help rs988?
Click to expand...
Click to collapse
Download the Quadrooter Scanner and see if 4/4 vulnerabilities. If so, hope is right there.
cdiscrete said:
Download the Quadrooter Scanner and see if 4/4 vulnerabilities. If so, hope is right there.
Click to expand...
Click to collapse
I have 4/4, will this lead to development for our phones?
muppetmaster916 said:
I have 4/4, will this lead to development for our phones?
Click to expand...
Click to collapse
Yes. The last step is a tool that makes use of these vulnerabilities. That's what we are waiting for.
I've looked,searched and looked again.I can not find the turn off automatic updates. Can some one screen shot please. I posted a picture,there is no option for it
On Latest OTA installed, on sprint. I have 3 of the four
4/4 south América H840 variant here, i hope we do get root
AT&T H820, 4/4 shown here with April 01 security update. Will pledge $50 towards the bounty if someone can make use of this.
RS988 with 2016-06-01 Android security patch level. 4/4 vulnerabilities. If this is what we were waiting for, I'm excited!
It's not, I spoke to jcase earlier and he pretty much stated that until a solution to the locked bootloader is found we're screwed. No bump possibility either.
muppetmaster916 said:
It's not, I spoke to jcase earlier and he pretty much stated that until a solution to the locked bootloader is found we're screwed. No bump possibility either.
Click to expand...
Click to collapse
But at least we can get some xposed stuff right?
BR7fan said:
I've looked,searched and looked again.I can not find the turn off automatic updates. Can some one screen shot please. I posted a picture,there is no option for it
Click to expand...
Click to collapse
Seems your Settings is different from mine.
We need a great hacker for this exploit to work..
I will patiently wait

Categories

Resources