New rooting method for Fire TV? - Fire TV Q&A, Help & Troubleshooting

https://gist.github.com/PerceptionPointTeam/18b1e86d1c0f8531ff8f
Don't know if it works. But even on i7 it takes 30 minutes.
Got it from here (sorry, it's german): http://www.heise.de/newsticker/meld...anfaellig-fuer-Rechte-Trickserei-3076663.html
Edit: http://perception-point.io/2016/01/1...cve-2016-0728/ (thanks to T0m93 for the link)
Any comments?

Here the exploit in english:
http://perception-point.io/2016/01/...f-a-linux-kernel-vulnerability-cve-2016-0728/

veeroohre said:
https://gist.github.com/PerceptionPointTeam/18b1e86d1c0f8531ff8f
Don't know if it works. But even on i7 it takes 30 minutes.
Got it from here (sorry, it's german): http://www.heise.de/newsticker/meld...anfaellig-fuer-Rechte-Trickserei-3076663.html
Any comments?
Click to expand...
Click to collapse
The article also says:
Allerdings wird dies durch Intels Schutztechniken SMAP und SMEP sowie SELinux, beziehungsweise SEAndroid auf Mobilgeräten, erschwert oder auch ganz verhindert.
Click to expand...
Click to collapse
In english (quick and dirty translation ):
But through Intels scurity techniques like SMAP and SMEP and also SELinux, or SEAndroid on mobile devices, this can´t be done easy or is prevented at all.
Click to expand...
Click to collapse
Since Amazon did also secure the aTV1 very well I doubt this will be a root solution. But who knows.

Calibaan said:
Since Amazon did also secure the aTV1 very well I doubt this will be a root solution. But who knows.
Click to expand...
Click to collapse
This exploit seems to affect a lot of devices because it already exists for a long time within the kernels. I doubt that Amazon found this flaw themselves and patched their systems without notifying the linux community, so chances are high that this might work (provided the kernel in den aTV1/2 is not too old). Someone needs to compile this stuff (ideally into an APK) and try it

It was the same with all other critical vulnerabilities in the last time, unfortunately none of them worked for the aTV1.
I believe that a special aTV/FireOS 3 related exploit must be found but my personal bet would be that the coming switch to FireOS 5 might give better chances for a root exploit. We will see. I´m still hoping for a tailored root for aTV1.

I believe the kernel on the fire tv 1 is too old for this exploit.

rbox said:
I believe the kernel on the fire tv 1 is too old for this exploit.
Click to expand...
Click to collapse
Is the kernel updated to a vulnerable version in the FireOS5 update for AFTV1?

Ludacrisvp said:
Is the kernel updated to a vulnerable version in the FireOS5 update for AFTV1?
Click to expand...
Click to collapse
Pretty sure it's still the same version.

In the above linked article they say
The vulnerability affects any Linux Kernel version 3.8 and higher.
Click to expand...
Click to collapse
According to http://kernelnewbies.org/Linux_3.8 3.8 was released on the 18th of February 2013. So I don't think the kernel of AFTV1 is too old.

Does not look good: https://plus.google.com/u/0/+AdrianLudwig/posts/KxHcLPgSPoY
Further, devices with Android 5.0 and above are protected, as the Android SELinux policy prevents 3rd party applications from reaching the affected code. Also, many devices running Android 4.4 and earlier do not contain the vulnerable code introduced in linux kernel 3.8, as those newer kernel versions not common on older Android devices.
Click to expand...
Click to collapse

veeroohre said:
In the above linked article they say
According to http://kernelnewbies.org/Linux_3.8 3.8 was released on the 18th of February 2013. So I don't think the kernel of AFTV1 is too old.
Click to expand...
Click to collapse
The date a kernel is released is irrelevant when it comes to Android. Android devices only use specific kernel versions, it's not just whatever the latest is. In the case of the firetv 1, it is 3.4.0: https://github.com/androidrbox/android_kernel_amazon_bueller/blob/master/Makefile

Related

Cm-13.0 - development/discussion thread

Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.

Regarding Root and Android 7

So I read an Article
That states
Using a feature called verified boot, Android 7.0 Nougat will check the cryptographic integrity to detect if your device has been tampered with.
Click to expand...
Click to collapse
With that said, will there ever be root again for android 7 and up?
so, with cm14 at least, i believe root is included. If anything i think it will just disable certain features if the device has been rooted. although i suppose that it would depend on the manufacturer. It will certainly be more difficult with samsung, anyways. I'm done with samsung after this one, though. samsung has been bending root users over the table since knox was first included with consumer phones - since before then, but it was a minor inconvenience before then.
when they didn't include adoptable storage with their marshmallow update, i was OUT! looking at the lg v20 now, i sampled it for a bit and it literally made me want to throw my note 4 in the trash
Look at the Pixel, Android 7.1 + root, It's possible. We're not getting official Android 7.x more likely than not, but it's possible to root 7.x.
I'm running CM14.1 on this device and SuperSU is just fine.
RDChase said:
Look at the Pixel, Android 7.1 + root, It's possible. We're not getting official Android 7.x more likely than not, but it's possible to root 7.x.
Click to expand...
Click to collapse
Thank you this is the answer I was looking for.

No update since Feb 2021 on s10 + G975U1

No update since Feb 2021 on s10 + G975U1 It's still running on one ui 3.0 where as mostly all the other samsung devices got April security update with one ui 3.0
Use odin. Problem solved
NickosD said:
Use odin. Problem solved
Click to expand...
Click to collapse
How to download the UI 3.1 firmware for G975U1 ? It's not available yet by any website
How did you solve this problem?
NickosD said:
Use odin. Problem solved
Click to expand...
Click to collapse
There is no new update released by Samsung since feb 2021 for unlocked s10+ variant
Fantomass said:
How to download the UI 3.1 firmware for G975U1 ? It's not available yet by any website
How did you solve this problem?
Click to expand...
Click to collapse
Its not yet released by Samsung so it will not available yet
Update is available now , I've just updated via ota
Android 11 UI 3.1
Fantomass said:
Update is available now , I've just updated via ota
Android 11 UI 3.1
Click to expand...
Click to collapse
How's Google's Frankenstein OS treating you and your cpu cycles?
blackhawk said:
How's Google's Frankenstein OS treating you and your cpu cycles?
Click to expand...
Click to collapse
Try it yourself
Fantomass said:
Try it yourself
Click to expand...
Click to collapse
No. Still running happily on Pie
Karma Firewall loses it's very useful logging function starting with Q.
My trusted overlay apks get killed as well.
The cloud version of Package Disabler is all that will work on the latter OSs too. Found that out over the weekend. Not a fun 3 hours.
Samsung wasted no time in making Knox even worse in 10 and 11.
So my question is what good things did it bring to you?
Are you feeling mellow and protected or is your urge to kill rising?
blackhawk said:
So my question is what good things did it bring to you?
Are you feeling mellow and protected or is your urge to kill rising?
Click to expand...
Click to collapse
For me I'm looking for updates for security , but with UI 3.1 I see more ram available than before , everything else is still the same for me also I've heard about new camera options and optimization
Fantomass said:
For me I'm looking for updates for security , but with UI 3.1 I see more ram available than before , everything else is still the same for me also I've heard about new camera options and optimization
Click to expand...
Click to collapse
That's cool.
The scope storage though is overkill.
Even on my so unpatched Pie security hasn't been an issue unless I do something stupid.
Been waiting for over a year for the malware forced factory reset that never happened.
Just like the masks I'm not buying the hype.
No vaccine and no Android 11... kill me if you can virus, but you won't alter my base code by voluntary injection!

Does anyone check Mediatek's security bulletins for vulnerablities?

After lurking here waiting for updates on things, I know there's currently a big snag on gaining root on the latest firmware due to Amazon's locked down bootloader. I've been readng around, and it does seem like there are privelige escalation exploits out there for the Mediatek chip inside the latest Fire:
https://corp.mediatek.com/product-security-bulletin/January-2022 (do a find for MT8183)
Not sure how helpful that is, I'd be very surprised if that information wasn't already in the hands it needs to be, but I thought I'd try and be as helpful as possible by pointing it out.
@Datastream33 @diplomatic
badboy21102000 said:
@Datastream33 @diplomatic
Click to expand...
Click to collapse
Looks like there's a total of 5 exploits, and they're driver related. Hmm...

Question Android 13 - Developer Preview 1

There are OTA's available as well.
Is anyone brave enough to try it? Is anyone on it? I am considering side loading it.
https://www.xda-developers.com/how-to-download-android-13/
If they are planning on it being beta by April it shouldn't be all that bad but I'm probably gonna wait until at least the next build. 12 to 13 isn't as huge a leap as it was from 11 to 12 so I'm guessing/hoping it won't be as buggy as early 12 builds. I'm sure someone will take the plunge to determine if it can be rooted or not.
oh my god xD google is trolling us....android 12,android 12 L,now android 13...what the ****! xDDDDD
Well 12L comes out next month officially. No more Android 12 updates.
Hopefully someone takes the plunge. I don't mind doing installing it to do bug reports to ensure the beta is a fun experience.
I want to know if the OTA works, scared to be the first to try as google doesnt even offer the ota on their website. Who will be the brave soul?
I am going to do a factory reset to A13,give a few minutes
Ivixmax said:
oh my god xD google is trolling us....android 12,android 12 L,now android 13...what the ****! xDDDDD
Click to expand...
Click to collapse
According to some people, A12L has the best modem update, A13 has the newest kernel.
Maybe in the future we best just mix all three branches together, creating the best Android.
Morgrain said:
According to some people, A12L has the best modem update, A13 has the newest kernel.
Maybe in the future we best just mix all three branches together, creating the best Android.
Click to expand...
Click to collapse
It was already making me think of Windows 98 Millenium edition - the notorious user mix and match of the horrible Windows ME and the less horrible Windows 98.
ok root is working fine on A13, no problem. This is the kernel and baseband versions
Looking at the dates 220205 - Android 12L and 220114 - Android 13, it appears that this build of Android 13 is older than the 12L update. February 5th vs January 14th.. Thoughts? Anyone see how the modem works?
Doug8796 said:
Looking at the dates 220205 - Android 12L and 220114 - Android 13, it appears that this build of Android 13 is older than the 12L update. February 5th vs January 14th.. Thoughts? Anyone see how the modem works?
Click to expand...
Click to collapse
LLStarks said:
Modem is newer than Feb but older than 12L. Bootloader is version 1.2 compared to 1.1 in 12L and 1.0 in Feb.
Mixed bag. Need to see what 13 modem is capable of (i.e. VoNR, C-Band, etc).
Click to expand...
Click to collapse
LLStarks said:
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Click to expand...
Click to collapse
Is the modem decent? More capable than all but Android 12L? Can non root flash the newer modem you think?
Doug8796 said:
How is the modem working? did you do a speed test?
Click to expand...
Click to collapse
@LLStarks , just tagging you in this thread to see if you have any answer for @Doug8796.
Doug8796 said:
Can non root flash the newer modem you think?
Click to expand...
Click to collapse
With the bootloader unlocked you can flash anything you like. What happens when you do, no one call tell, though. Might work, might not, the possibility of boot loop...
ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja
Cant unlock the ole bootloader until I pay it off - on contract.
time to return to A12 L
Ivixmax said:
ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja
Click to expand...
Click to collapse
You sure it's build/A13 related? Have you tried out another phone at the same location where your A13 device is?
I've had a mountain of NordVPN connection problems in the most recent months and have troubleshooted so much, even though in the end it was just caused by bad/weak servers, meaning after connecting to new ones it was "solved" - so if you use a VPN, mind that.
Ivixmax said:
ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja
Click to expand...
Click to collapse
what was it before in the same spot on 12L?
Doug8796 said:
what was it before in the same spot on 12L?
Click to expand...
Click to collapse
40 or 60 mate xD
Patetic modem on A13.
Time to reflash A12 L

Categories

Resources