Related
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For starters i can't imagine why anyone who is rooted and running a custom ROM would ever dream of installing an official OTA. By the time the carrier's have had time to update their own ROM and distribute the update it will have long been incorporated into most custom ROM's. Point and case is 4.3 (which i have been running thanks to Task650 for many months)...boom all of a sudden you are stuck with a bootloader that you cannot change, or how about the case of the S4's who blindly or unknowing installed an OTA that gives them a locked bootloader that cant be downgraded (in the case of those of us with carriers who are evil bastards). The only case where i would personally find it 'acceptable' to install official OTA's is someone who has no interest in rooting or installing any custom software to their device. Yes the current S3 bootloader is rootable but one day, probably the next (if there is one) update i would imagine it will be locked down like the new devices. Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
dntesinfrno said:
....Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
Click to expand...
Click to collapse
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
jack man said:
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
Click to expand...
Click to collapse
Yes currently its the manufacturers, at the behest of the carriers...hence why att and verizon are locked on the s4 and up samsung devices but not sprint or tmo. I was simply stating that if things continue to go the way they seem to be with googles decisions moving forward with android it could end up that way.
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
rumrnr62 said:
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True, but that can take months, and until then, you're stuck.
Can always buy a dev version or a nexus
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
ibuddler said:
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
Click to expand...
Click to collapse
Same here.
I wonder if for some reason another toy (Ooops, update) comes to this phone, will the rooters who OTA-ed, and then re-rooted or flashed another ROM (and tripped their new warranty bit counters in the process) be able to receive the new update, or will it be blocked because of the counter increment, and once again, will have to rely on custom ROMs, which they should already be doing?
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Click to expand...
Click to collapse
...Anything, except flashing back to stock for reflashing purposes or for warranty service or resetting the Knox warranty bit. OTA may also damage resale value, among other downsides.
shortydoggg said:
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive..
Click to expand...
Click to collapse
There are diverse camps among the rooters & other members here. Through my GS1, GS2 & GS3 I've used mostly debloated stock TW roms; for work, on the road constantly & needing a maximum stable daily driver; like other stock TW enthusiasts.
Apart from user (flashing) errors, the stability, the flexibility & connectivity complaints you cited are what I measured against when deciding to flash a 4.3 rom, kernel & modem from |ROM|Bootloader|Kernel|Modem| AT&T Official 4.3 MJB |24 Nov 2013| .
What designgears, upndwn4par, loserskater & the others have posted on multiple threads I read & reread here before flashing allowed me to attempt the 4.3 upgrade with a solid backout plan & maximum control, reaching my desired result:
Stable, debloated (by me, it's personal) permission edited (using App Ops) battery optimized 4.3 using the same bootloader as on 4.1.2.
The resources exposed in that one thread I linked, plus miles of reading in prep here on XDA showed me how to have the upgrade my way, so even stock a enthusiast can get a first class passage thanks to our devs. Buy them a drink when you can!
Did you pick up an unlocked Fire Phone from the recent sale at Amazon? You probably got a device running Fire OS 3.6.8.
It may be tempting to flash back to an earlier software version to attempt root, but you should hold off for now. I, and a few others it seems, are now stuck with phones that can't really do much. Registering with Amazon doesn't work, phones get hot, and we have no access to apps. The worst part is that we don't have the 3.6.8 image yet, so there's no way to go back.
Until we get a way to go back to 3.6.8, you should refrain from downgrading.
Has anyone downgraded from 3.6.8 successfully?
If we can't downgrade from 3.6.8, what does that mean for root access? Are we stuck with stock Fire Phone OS?
Downgrading the unlocked 3.6.8 to the ATT 3.5.0 without first clearing data and cache causes bootloops. If the cache and data is cleared the phone boots up but you will have no icons and no internet connection. You will basically be in a unfunctional state and phone keeps getting warmer and warmer.
Flashing back to 3.5.2 will get the phone functioning as a phone
but the Amazon server will not register the device
Cannot locate 3.6.8 file on their server (see download list topic)
Wow this explains a lot. In my efforts to mess with the boot loader and work on the phone, I downgraded to 3.5 and now have this problem. Got it to 3.5.2 which gives me a few apps, but I can't register and its unusable. I hope they release something soon. Might hit up Amazon Support to see if I can get them to help.
---------- Post added at 03:21 PM ---------- Previous post was at 02:38 PM ----------
An update: I just got off the phone with a knowledgeable rep (took 2 tries). She said that they can't pull any information, manuals, or reference to a version higher than 3.5.2.
She did take the time to escalate my issue with a trouble ticket that will go to the advanced IT and devs, which should at least bring the problem to their attention.
She said I will get a response or update in the next 5 business days. Until then, I will just keep trying to reverse engineer the bootloader and see if I can make any edits to it to allow unlocking, or maybe an exploit.
Man....thank goodness I let reason prevail! I thought that after this massive dump, there would be all kinds of devs going wild. 3.6.8 on mine. Mainly got it because my Prime is up this month, and I wanted a backup phone in case I burn up my Note 4 from flashing. Gotta say, it's a solid piece of hardware, and Amazon put some pretty cool fun stuff to play with. Thanks a ton for the heads up!
Thanks for the heads up, pretty sure you saved a few flashaholics from a headache
Have a question:
Is German 3.6.2 (you can choose english as language in it) working without getting hot? (Modem Version is same as in 3.6.8: ro.build.version.lab126.modem=PB_02_06_05)
Version 3.6.8:
ro.build.lab126.project= ???? not available
ro.build.product=juniper
ro.product.name=juniper
ro.build.version.lab126.modem=PB_02_06_05
Version 3.6.2 (German)
ro.build.lab126.project= ???? not available
ro.product.name=caraway
ro.build.product=caraway
ro.build.version.lab126.modem=PB_02_06_05
Version 3.5.2 (AT&T)
ro.build.lab126.project=duke-1.1_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
Version 3.5.1 AT&T
ro.build.lab126.project=duke-1.1_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
Version 3.5 AT&T
ro.build.lab126.project=duke-1.0_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
B1ackByte said:
Have a question:
Is German 3.6.2 (you can choose english as language in it) working without getting hot? (Modem Version is same as in 3.6.8: ro.build.version.lab126.modem=PB_02_06_05)
Version 3.6.8:
ro.build.lab126.project= ???? not available
ro.build.product=juniper
ro.product.name=juniper
ro.build.version.lab126.modem=PB_02_06_05
Version 3.6.2 (German)
ro.build.lab126.project= ???? not available
ro.product.name=caraway
ro.build.product=caraway
ro.build.version.lab126.modem=PB_02_06_05
Version 3.5.2 (AT&T)
ro.build.lab126.project=duke-1.1_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
Version 3.5.1 AT&T
ro.build.lab126.project=duke-1.1_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
Version 3.5 AT&T
ro.build.lab126.project=duke-1.0_release_lewis
ro.product.name=full_duke_kodiak
ro.build.product=duke
ro.build.version.lab126.modem=PB_02_05_17
Click to expand...
Click to collapse
The 3.6.2 software worked fine for me ... only thing was no activation with the amazon servers (which basically makes the phone useless. No Market / No video's / No Mayday / No Music nothing related to Amazon works without the activation.
The Phone made calls and sent / received txt no problem.
Thanks for the heads up. Will hold off and side load a few .apks that are a must for my life style. New phone will be here in a few hours.
Pleasantly, I hounded Amazon for 2 days via every support channel (chat, phone, email), hoping i would run into the one overqualified, underpaid 1st tier support guy who can work off script. No luck. Basically at the end of all of this mess, i have to wait 2-5 business days for an engineer to "get back to me". Fookin awesome. 3.5.2 is completely useless without device registration, everything but email is pretty much tied to that. *Sigh*. I really hope someone manages to get the firmware. At this point, im simply waiting out the next few days only to surely be told to RMA the device. I just find it horrendous that a huge company like Amazon does NOT have procedures in place for a potential interrupted OTA, at least one that doesn't require shipping the device back. Shame on me for jumping the gun without verifying that the download to the latest firmware was ACTUALLY for my device (who knew the had another sku?). Shame on Amazon for sucking so bad at every stage of their "shoppers phone" rollout.
Sess said:
Pleasantly, I hounded Amazon for 2 days via every support channel (chat, phone, email), hoping i would run into the one overqualified, underpaid 1st tier support guy who can work off script. No luck. Basically at the end of all of this mess, i have to wait 2-5 business days for an engineer to "get back to me". Fookin awesome. 3.5.2 is completely useless without device registration, everything but email is pretty much tied to that. *Sigh*. I really hope someone manages to get the firmware. At this point, im simply waiting out the next few days only to surely be told to RMA the device. I just find it horrendous that a huge company like Amazon does NOT have procedures in place for a potential interrupted OTA, at least one that doesn't require shipping the device back. Shame on me for jumping the gun without verifying that the download to the latest firmware was ACTUALLY for my device (who knew the had another sku?). Shame on Amazon for sucking so bad at every stage of their "shoppers phone" rollout.
Click to expand...
Click to collapse
I am in the exact same situation as you, waiting for Amazon to fix my phone, so I sympathize. Having said that, let's be fair and not blame amazon for this; they sold us a premium phone for 200 dollars, which I can attest worked very well out of the box. It didn't prompt me to update it or anything and with a few tweaks it was actually giving me a great battery life and performance, until I decided on my own to get adventurous and flash stuff on it. That is certainly not Amazon's fault. If we had used the phone as it was delivered none of this would have ever happened. So let's wait and see what they do to fix it. I am confident they will release the firmware or worst case they replace the phone with a new one.
najoor said:
I am in the exact same situation as you, waiting for Amazon to fix my phone, so I sympathize. Having said that, let's be fair and not blame amazon for this; they sold us a premium phone for 200 dollars, which I can attest worked very well out of the box. It didn't prompt me to update it or anything and with a few tweaks it was actually giving me a great battery life and performance, until I decided on my own to get adventurous and flash stuff on it. That is certainly not Amazon's fault. If we had used the phone as it was delivered none of this would have ever happened. So let's wait and see what they do to fix it. I am confident they will release the firmware or worst case they replace the phone with a new one.
Click to expand...
Click to collapse
Then lets also be fair and take note of the fact that the phone is being sold for 200$ because it was grossly overpriced for what was offered. That still has not changed. Regardless, as a good corporate citizen its quite standard to provide tools to enable their users to restore the phone to standard working order. Had i not downgraded the phone i would not be in this mess. I acknowledge that. But i would also like to point out that had they provided something as simple as a release firmware bin file, i would not be in this mess either. Just gonna have to wait this out, but I will not be an amazon apologizer if they can't be bothered to give power users the basic tools to resolve their own issues.
If Amazon didn't lock down the Fire Phone so much, maybe people wouldn't be bothered to attempt to root it and change things Amazon clearly failed to do. Why can't I even change my launcher to Nova without issue? Amazon block wallpapers and widgets, so it's just a black screen with icons. If I wanted that, I would have stuck with iOS 3. The Fire Phone is locked down harder than iOS devices, which I never thought would happen. If they would loosen up to the grip, the phone would probably sell better. People want a phone they can make theirs, and that doesn't mean just what their Amazon portfolio looks like.
Worse yet, they still haven't forked over the latest update. I'm glad I bought two Fire Phones, because I can at least use one.
Now I see why no one wants this thing.
Just a side note re: registration:
I got my device several weeks ago and I think it was an earlier version than 3.6.8 - I downgraded to 3.5.0 per the instructions, rooted, all that works.
Now I just tried to register for the first time to get Prime, and found that I can't. So that doesn't seem specific to having come from the newest version, they must have disabled activation of all old ones?
Given that I'm in a working rooted state, I'm just going to leave it like this for now and hope that I can eventually flash forward without losing features that are unlocked like this, and finally claim that Prime service.
got tired of waiting on amazon, returned the phone, bought an iphone 6 plus. Will be using my shield tablet for all my android specific needs. @#$% amazon.
Side loading apks still works correct?
Yes
B1ackByte said:
Yes
Click to expand...
Click to collapse
One more question if you don't mind, are you still able to create a wifi hotspot and tether with the phone?
Yes
Hey Guys,
as soon as i got my FireTV, i blocked all Updates, so im still on 51.1.3.0. The newest official Firmware looks tempting, but even more the Chance of beeing someday able to root.
Now im wondering how high the chance would be for a way to gain root with 51.1.3.0, but not with a newer FW.
What do you think? Of course, noone can be shure. im just wondering how high you'd rate the chance for a case like that, that i can decide if i should update, or better keep my feets still Thanks for your advices! Cheers!
dafunkydan said:
Hey Guys,
as soon as i got my FireTV, i blocked all Updates, so im still on 51.1.3.0. The newest official Firmware looks tempting, but even more the Chance of beeing someday able to root.
Now im wondering how high the chance would be for a way to gain root with 51.1.3.0, but not with a newer FW.
What do you think? Of course, noone can be shure. im just wondering how high you'd rate the chance for a case like that, that i can decide if i should update, or better keep my feets still Thanks for your advices! Cheers!
Click to expand...
Click to collapse
Just update. I assure you that while the Fire TV is running Android 4.2.2 there is very very very very very little chance of it being roote. No matter how much people hate hearing it, its the truth. Its not gonna happen. Amazon has locked down 4.2.2, and I think devs have given up on even trying to root newer firmwares. If they would upgrade to Android 4.4 it would renew interest in rooting, but root may not be accomplished on 4.4 either.
Even if newer firmwares were to be updated it is more likely that the latest update would be the one that gets rooted so there is really no reason not to updatee.
dafunkydan said:
Hey Guys,
as soon as i got my FireTV, i blocked all Updates, so im still on 51.1.3.0. The newest official Firmware looks tempting, but even more the Chance of beeing someday able to root.
Now im wondering how high the chance would be for a way to gain root with 51.1.3.0, but not with a newer FW.
What do you think? Of course, noone can be shure. im just wondering how high you'd rate the chance for a case like that, that i can decide if i should update, or better keep my feets still Thanks for your advices! Cheers!
Click to expand...
Click to collapse
If you hardware root, you can downgrade to 51.1.0.2 and then upgraded to the latest prerooted.
Thanks Guys for clarifing! Yes i hate hearing it But at least i can go updating.
I cant solder at all (i even mess up soldering odd headphonecables, so no way) So no hardware root for me
Anyway, thanks again
Hello.
11.11.2015 i recived a notification on phone that Elephone had released a new update to improve system functioning ect.
Keep in mind this is a stock p8000. nothing done with it.
I downloaded update, installed and it said phone will reboot.
After that phone is stuck in bootloader and simply wont boot.
Ive tried wiping cache and factory reset but PHONE WONT turn on.
So question is. What the hell do i do now?
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms. ?
This thread should be merged with other ones.
Have anyone found a solution?
pitrus- said:
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms.
This thread should be merged with other ones.
Click to expand...
Click to collapse
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
The Boards are full of Threads and solutions about this problem !
Why aren't you looking around a bit ?
How about the first post in Q&A section ???
http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203
StormiZMo said:
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
Click to expand...
Click to collapse
manually flash the stock rom .. i faced the same ****.. i followed the below steps and my elephone working fine
http://bbs.elephone.hk/thread-9229-1-1.html
hope this will work...
Fixed
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
StormiZMo said:
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
Click to expand...
Click to collapse
LOL, fired for what? it worked on most devices.
you get what you pay for! how are elephone selling a phone with decent specification for that price? they cut corners everywhere.
quality being 1 and skilled staff is the other.
with the given resources, their staff did they best they could with the test hardware they had.
StormiZMo said:
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
Click to expand...
Click to collapse
Also, most China phones don't even get updates, or even more exclusive, source code releases like this one. My guess is that there's likely only a one man show in charge of software development for this model, so give them some slack will you. [emoji1]
mine went off to after the OTA so i had to flash manually and like my friend said there trying, unlike most china phone company's so even though mine failed my father's and my friend's p8000 got there OTA np
It seems like the first 5000 batch delivered had no notification led,they seem to put in different hardware thats available.So end up with a hotch podge of slightly different devices.
So fingers crossed that a update works.Thankfully Elephone allows ,enables development.
It also looks like OTA update fails on rooted phones, which is not so different than what happens to most Android phones. When I used a Samsung phone long ago, OTA update notifications wouldn't even show up if you had rooted your phone, and on other phones I remember having a similar issue after I applied an OTA update with the phone rooted
I don't know how this will be able to help our situation with locked bootloaders, but I am sure the intelligent among us could somehow use this.
I suppose this would be possible. But I'm pretty sure LG will close that with the next security update (if they can be bothered to issue one, we're still waiting for the February update.)
xrad said:
I suppose this would be possible. But I'm pretty sure LG will close that with the next security update (if they can be bothered to issue one, we're still waiting for the February update.)
Click to expand...
Click to collapse
http://www.androidcentral.com/verizon-updates-lg-g3-and-g4-march-security-patch? now I wish H815 would get it. Amazing to see a carrier phone appear to get this first.
xrad said:
I suppose this would be possible. But I'm pretty sure LG will close that with the next security update (if they can be bothered to issue one, we're still waiting for the February update.)
Click to expand...
Click to collapse
Yes, that is true. But the choice of updating is in the hands of the user. I am sure a lot of people want to use MM on their G4 but cannot let go of root. This can/may provide a middle-ground for these people. They can have root and MM, albeit an outdated version, which in my opinion is better than nothing.
yash_bhardwaj said:
Yes, that is true. But the choice of updating is in the hands of the user. I am sure a lot of people want to use MM on their G4 but cannot let go of root. This can/may provide a middle-ground for these people. They can have root and MM, albeit an outdated version, which in my opinion is better than nothing.
Click to expand...
Click to collapse
I agree considering I'm still on LP because I will not let go of my root access. I'm in no rush to upgrade either but it doesn't hurt to not be too left behind compared to my brother
spartan268 said:
I agree considering I'm still on LP because I will not let go of my root access. I'm in no rush to upgrade either but it doesn't hurt to not be too left behind compared to my brother
Click to expand...
Click to collapse
I was foolish enough to update to MM, I've since stopped using the device completely except for answering calls, and I am really sad about that. With the leather back, curved screen, replaceable battery, and back buttons this is one of my top phones. Yes, I know I can downgrade, but I don't want to be bothered by that. I like the new MM features enough to not downgrade, yet I hate not having root, the ad-blocking, the tweaking of my phone to my liking. I've already decided on not buying any phones except nexus. But sadly I am stuck with this phone till the next nexus comes out.
Hello,
I was wondering if someone with the right skills could do it.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805
In the bug's description it's said that Linux kernels before 3.16 are affected by this, I'm using 20e which runs 3.10.84 so theoretically exploitable.
I work with software development but web/mainframe mainly, anyone with a few hax0r skills willing to work on this?
I would certainly donate for this cause.