GTVHacker has announced on their blog (http://blog.gtvhacker.com/2014/google-nest-exploiting-dfu-for-root/) that their upcoming talk at Def Con 22 will feature unreleased exploits for 20 devices, including the Chromecast, being released in a 45-minute period. Hopefully their unreleased exploit won't be patched between now and then.
Lets hope this is true and Google doesn't figure out how it is done and patch it before we get it!
That have had this root method for awhile according to the link you posted...
It's there any benefit to having your chromecast rooted, anyways?
tooandrew said:
It's there any benefit to having your chromecast rooted, anyways?
Click to expand...
Click to collapse
Yes, depending on your wants/needs.
https://forum.xda-developers.com/showthread.php?t=2621784
tooandrew said:
It's there any benefit to having your chromecast rooted, anyways?
Click to expand...
Click to collapse
I was one who argued earlier that there was no real need for it....
But at that time Developer support was limited and scarce!
Now I would have to argue that Rooting (and flashing Eureka) is a desirable thing to have as the Whitelist is becoming more of a hinderance than it once was.
Where there was once maybe 20 developers working on support and Goggle was quick to update the whitelist to get as much support to the public as possible....NOW there are probably 100's (maybe even 1000's) working on Apps that support CCast and waiting for Google to whitelist their projects and as we have seen recently, Things like Mirroring have been around and working for close to two months yet many are denied from using it due to the Whitelisting restrictions.
As time goes on...Having Root will be much more worth having than it was back in December and January.
So this is good news if you ask me! and YES rooting is becoming much more worth having than it used to be!
Asphyx said:
I was one who argued earlier that there was no real need for it....
But at that time Developer support was limited and scarce!
Now I would have to argue that Rooting (and flashing Eureka) is a desirable thing to have as the Whitelist is becoming more of a hinderance than it once was.
Where there was once maybe 20 developers working on support and Goggle was quick to update the whitelist to get as much support to the public as possible....NOW there are probably 100's (maybe even 1000's) working on Apps that support CCast and waiting for Google to whitelist their projects and as we have seen recently, Things like Mirroring have been around and working for close to two months yet many are denied from using it due to the Whitelisting restrictions.
As time goes on...Having Root will be much more worth having than it was back in December and January.
So this is good news if you ask me! and YES rooting is becoming much more worth having than it used to be!
Click to expand...
Click to collapse
Is there a list of apps that Google won't support yet and are added to custom whitelist? I do have Eureka ROM but chose to run official whitelist because the updates to popular or prominent apps gets there faster. I wouldn't mind having a look at some of the smaller developers and what features they offer, you can always find a gem or two there.
jasenko said:
Is there a list of apps that Google won't support yet and are added to custom whitelist? I do have Eureka ROM but chose to run official whitelist because the updates to popular or prominent apps gets there faster. I wouldn't mind having a look at some of the smaller developers and what features they offer, you can always find a gem or two there.
Click to expand...
Click to collapse
I could be wrong but I thought the "lag" was addressed a couple of builds back and there should be near-zero "lag" between a Google whitelist and Team Eureka whitelist now.
bhiga said:
I could be wrong but I thought the "lag" was addressed a couple of builds back and there should be near-zero "lag" between a Google whitelist and Team Eureka whitelist now.
Click to expand...
Click to collapse
I think you are right, I went to the project's file repository and noticed a whitelist-sync script. I guess it is safe to go back to Eureka provided whitelist.
jasenko said:
Is there a list of apps that Google won't support yet and are added to custom whitelist? I do have Eureka ROM but chose to run official whitelist because the updates to popular or prominent apps gets there faster. I wouldn't mind having a look at some of the smaller developers and what features they offer, you can always find a gem or two there.
Click to expand...
Click to collapse
Well Google's Mirroring app is the first one I'm sure about....
Not sure what else Team Eureka has included that is not on the official Google list....
The benefit isn't so much the MORE you can do it is the fact that when a MORE is found that Google is dragging it's feet on Eureka can add it to the list provided someone else has access to that feature.
And any developer who wanted to, could ask Eureka to whitelist their app should Google decline to do so...
Not many of those have popped up yet that I know of but in the future it will happen at some point.
ahecht said:
GTVHacker has announced on their blog (http://blog.gtvhacker.com/2014/google-nest-exploiting-dfu-for-root/) that their upcoming talk at Def Con 22 will feature unreleased exploits for 20 devices, including the Chromecast, being released in a 45-minute period. Hopefully their unreleased exploit won't be patched between now and then.
Click to expand...
Click to collapse
Any news, new insights regarding the Def Con exploits? Chromecast still on the list?
Bazzz66 said:
Any news, new insights regarding the Def Con exploits? Chromecast still on the list?
Click to expand...
Click to collapse
No and the LESS NEWS the BETTER if you ask me....
I don't want Google getting even the slightest hint at what it may be for fear of them Patching it before we get our hands on it!
Bazzz66 said:
Any news, new insights regarding the Def Con exploits? Chromecast still on the list?
Click to expand...
Click to collapse
The talk is Saturday at 10am. We'll find out then.
Everyone is anxious
I'm a Brazilian without English Course, sorry and be comprehensive
Everyone worried about Google patching your unit before the exploit comes out... Do what I did.
UNPLUG IT!
Your unit can't update if it has no power.
Well, it's Saturday and it's past 10AM in Las Vegas. Is there any news about the root exploit? I haven't seen anything on XDA or /r/chromecast about it.
obsama1 said:
Well, it's Saturday and it's past 10AM in Las Vegas. Is there any news about the root exploit? I haven't seen anything on XDA or /r/chromecast about it.
Click to expand...
Click to collapse
Well unless they are posting from the venue you are not likely to get any reports until about 8 or 9 PM Eastern.
Saw a recap on another website of the talk, but they didn't mention the Chromecast at all on the post. I hope it's real. I guess we'll have to keep waiting.
Information from defcon is up on http://dc22.gtvhacker.com, but there is no mention of any new root exploits, same old info from what i can see?
fldc said:
Information from defcon is up on http://dc22.gtvhacker.com, but there is no mention of any new root exploits, same old info from what i can see?
Click to expand...
Click to collapse
They're still in the process of updating the content on the site it looks like. Other devices haven't had their root methods released yet either.
Someone asked them on Twitter if new info on the Chromecast was out and they replied with "not yet " which leads me to believe they may not be releasing it just yet? Or perhaps like you said r3pwn, they haven't added it to their page yet.
Related
This is taken from engadget.com
HTC is legendary for its tacit support of the Android ROM cooking community. Motorola... not so much, thanks in large part to the company's policy of locking down the bootloader as a means to prevent unapproved software from running on its Droid handsets. An annoyance recently exacperated by a moderator of Moto's YouTube channel who suggested that customers looking to install custom ROMs should "buy elsewhere." Ouch. The resulting public relations kerfuffle then prompted Motorola to publish a clarification to its bootloader policy on Facebook:
We apologize for the feedback we provided regarding our bootloader policy. The response does not reflect the views of Motorola. We are working closely with our partners to offer a bootloader solution that will enable developers to use our devices as a development platform while still protecting our users' interests. More detailed information will follow as we get closer to availability.
Obviously, we'll have wait for said details to get official before calling this a shift in strategy. It's certainly an improvement over Moto's previous approach of lawyering-up with cease and desist orders. Perhaps Motorola is taking a cue from Microsoft who seems to have recently discovered that it's better to embrace than to annoy a motivated hacking community -- customers who tend to be a company's most dedicated fans and evangelists.
Good news?
Direct Link: http://www.engadget.com/2011/01/21/motorola-ready-to-make-sweet-love-to-rom-devs-and-rooters/
its a maybe. maybe they will launch our froyo locked, maybe it'll be open. we never know.
i just read this also. this could be great news or another terrible taunt whih leads to nothing.
im not gonna get my hopes up just yet.
available Q1 of 2046, stay tuned! lol
Sent from my Milestone using XDA App
Sounds like a PR stunt to quell the immediate situation before waiting for it to blow over.
Sent from my Milestone using XDA App
I dont believe in manufaturer, i believe in XDA dev's..... this a "cold water" not a hope for us.
I hope this isn't just some PR bull and moto actually enables us to load custom kernels.
That press release says nothing about unlocking the bootloader, only that they will help devs which could mean anything!
DummyPLUG said:
available Q1 of 2046, stay tuned! lol
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
LMFAO!!!
i dnt believe motorolsh!t will do that(unlocking the bootloader)
I so love my new HTC Desire! couldnt stand this situation anymore....! sorry guys...
It is just the usual PR crap which companies like them give when they screw up on the social networking front. The "..buy elsewhere.." was just a such screw up. A Royal one I would say!
They are now trying to calm down the situation by giving us this crap..
I think it's just a excuse about the bad comments in youtube video, nothing more than that.
DummyPLUG said:
available Q1 of 2046, stay tuned!
Click to expand...
Click to collapse
2046???
...that seems a little too soon... dont ya think?
Menelkir said:
I think it's just a excuse about the bad comments in youtube video, nothing more than that.
Click to expand...
Click to collapse
That seems most likely but perhaps the fallout and bad press from that will push them to do what they should have done long ago, free the bootloader in some form so we can get custom ROMs on it.
Dyonas said:
That seems most likely but perhaps the fallout and bad press from that will push them to do what they should have done long ago, free the bootloader in some form so we can get custom ROMs on it.
Click to expand...
Click to collapse
Yes, I really want to see this happening, but I don't have any hope about Motorola opening the bootloader.
If they do, ok, excelent news to the community, to all developers that will make even better ROMs and for all of us that have a Motorola phone. We can see the quality of alternative ROMs for Motorola Milestone today as example. It's obvious that the only limitation is the bootloader, so the quality can be massively improved if we can change and optimize the kernel.
But I think all people here are already tired from Motorola's position about his costumers: Censorship on comments (youtube and motorola forums), censorship on criticism (even the very good ones, Motorola does not seem to care about the opinion of his costumers), cease and desist in community cases like the ROM of Droid X and sites with roms (that its very stupid IMHO)... and the list goes on...
By the way, my only hope is, if that happens and I have not exchanged my phone yet, good.. I'll make good use of it. But honestly? I have now my last phone from Motorola.
Am I missing something? Forgive my ignorance, but what is "locked up" about the bootloader? I'm running CM6 along with the overclocked CM6 kernel, and there are tons of other custom ROMs out for the Droid as it stands. What is restricted by Motorola?
vapor63 said:
Am I missing something? Forgive my ignorance, but what is "locked up" about the bootloader? I'm running CM6 along with the overclocked CM6 kernel, and there are tons of other custom ROMs out for the Droid as it stands. What is restricted by Motorola?
Click to expand...
Click to collapse
Milestone users cannot use custom kernels. All the AOSP ROMs still have to use the SAME kernel, supplied by Mot. They lock it to the bootloader. This means problems trying to compile modules and customer kernels and no way to patch bugs.
It is much more work for devs to get stuff done for the milestone than other phone (htc comes to mind).
Examples of issues: battery life, phone sleeping, waiting for compatible kernel or hack for new android versions, swap support, vpn support, other filesystem support... the list goes on.
But you allowed to be happy with your phone. Not everybody needs these things...
Sent from my Milestone using Tapatalk
He has a very good point. Where other android device builders seem to be promoting development (Huawei excluded, theyre miser's just like Motorola), this company seems to be more prominent on the restriction of development on their devices.
One very good reason for this is that Motorola has been such a huge phone developer for such a long time, that they have probably let it go to their head. Now instead of saying "our consumers said they need this", they're sayin "we think they really only need this." I've used Motorola phones for about 8 years now, and I would DEFINITELY say someone forgot that their customers put them where their at.
I agree. Someone needs to get out there and give them a taste of Good Customer Service. I dont think restricting dev's is a great marketing idea, or revenue booster anyways. BUt then again, to each, his own.
This is PR.Nothing more.
Know motorola they do not update РСТ(Russian legal)Milestone, they do not
need to unlock this crap bootloader.
I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
Thank you for contacting Google!
Warranties and RMA are still covered *regardless* if a device was rooted.
We are not trying to prevent customers from unlocking the bootloader and installing a new operating system that allows for "rooting".
Android has always provided customers the ability to do that on Nexus devices, and encouraged other OEMs to do the same. So in that sense we are not against "rooting."
This being said, we can't guarantee full advertised/promised functionality if the source code for the Android OS has been modified as the functionality may have changed.
Click to expand...
Click to collapse
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
EDIT: Just to clarify, this about Google's North American policy - it appears that they follow this throughout Europe as well, and that European law probably reinforces this. Still, it can't hurt for anyone to check with Google themselves. Also, as per the thread title, this is about Google. If your warranty is held by anyone else this info may have no relevance at all.
NotFromMountainView said:
I've...
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?
aooga said:
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?
Click to expand...
Click to collapse
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.
This is fantastic. Thanks for sharing.
NotFromMountainView said:
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.
Click to expand...
Click to collapse
Cool. Good to know.
They provided us with the tools to unlock/lock our bootloader and set up a website to show us exactly how to do it. I think it couldn't be anymore obvious that they don't care that you stuck some binaries on the /system partition so you could run Titanium Backup
NotFromMountainView said:
I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app
monkeypaws said:
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
It never hurts to be wary. And it anyone managed to overclock the device so astronomically that it burst into flames there may be some pushback from Google. But the email is, as I said, unambiguous.
As to the suggested edit, I never said anything about advertising, but certainly you can tap 7 times and be rewarded with "Congratulations, you are now a developer!" That, as well as well as crachel's point seem to weigh towards it being referred to as a developer's device -- at least casually.
yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.
simms22 said:
yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.
Click to expand...
Click to collapse
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.
NotFromMountainView said:
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.
Click to expand...
Click to collapse
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.
simms22 said:
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.
Click to expand...
Click to collapse
That is just great! And just one more reason that I find it really hard to become overwrought over rattling buttons.
An obvious extension of this is that on support calls (or email) one can mention root/kernel/ROM without fear. Heck, Google might even want to know how mods perform.
But this is till the time we can RMA it which google is handling but when our warranty will expire we will have take it to Lg service center and I doubt that they will also give the same reply.
Policies for both of them must be different.
LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.
gee2012 said:
LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.
Click to expand...
Click to collapse
LG wont be understanding, period. Its only google that will except rooted devices.
If you bought another/extended warranty from your carrier or if your carrier import and service your phone then I think you have to keep hands in yr pockets they may not have a user friendly policy as Google's seems to ...
simms22 said:
LG wont be understanding, period. Its only google that will except rooted devices.
Click to expand...
Click to collapse
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of in selected country`s only?
Besides the obvious $$ reason for LG making more money
gee2012 said:
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of selected country`s only?
Click to expand...
Click to collapse
there could be many, most likely legal though. maybe even something with taxes or the currency being used in that country.
Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points):
Google traduction D):
Thank you for contacting the Google team about your Nexus 5. My name is and I'm Rozenn your contact today.
I understand your desire to rooter your phone because it is of course one of the benefits of owning the Nexus 5 and the android system.
However, if you need to claim warranty, we will ask you to return the phone to the Android version of Kitkat.
Also, be aware that we can not guarantee the functionality of the device if it is Roote.
If your phone is a concern and you need to claim warranty, from the moment he received no trace of shock or been in contact with water, simply contact us. If we can not resolve your concern, we will offer you an exchange. Your product is guaranteed for 2 years.
Click to expand...
Click to collapse
But the general idea seems the same as the reply from Google in the OP, less detailed.
viking37 said:
Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points
Click to expand...
Click to collapse
If I'm not mistaken there's an European law about that. Basically if we have bought a device in Europe the manufacturer must repare our device even if the software has been modified. (Instruction no. 1999/44/CE of E.U.)
Does anyone know how to fix this from happening? I'm running stock odexed rom with faux123 Kernel. It happens with any wifi network. Thanks!
Sent from my XT1060 using Tapatalk
I am also having this problem on stock. I have installed various Xposed modules, as well as Pry-Fi, but nothing seems to be related to the problem.
Edit: Looking at the reviews for Pry-Fi specific to the Moto X, it seems to have some stability issues with this phone. Turning it off has fixed my issue.
Linked Review
I'll try contacting the developer.
Edit 2: Looks like I won't be using Pry-Fi anymore. The app is dead in development. Looks like the project was not enough of a success.
Drakonas said:
I am also having this problem on stock. I have installed various Xposed modules, as well as Pry-Fi, but nothing seems to be related to the problem.
Edit: Looking at the reviews for Pry-Fi specific to the Moto X, it seems to have some stability issues with this phone. Turning it off has fixed my issue.
Linked Review
I'll try contacting the developer.
Edit 2: Looks like I won't be using Pry-Fi anymore. The app is dead in development. Looks like the project was not enough of a success.
Click to expand...
Click to collapse
You might try "WiFi Inspect" if you are looking for an alternative to Pry-Fi. It is a root app, but I haven't experienced any issues with it.
Good Luck
samwathegreat said:
You might try "WiFi Inspect" if you are looking for an alternative to Pry-Fi. It is a root app, but I haven't experienced any issues with it.
Good Luck
Click to expand...
Click to collapse
I don't think you understand what Pry-Fi did, because WiFinspect does NOT do what Pry-Fi's main feature was.
From WiFinspect's Play Store page:
...the app is a security audit tool and not a hacking tool.
Click to expand...
Click to collapse
Pry-Fi is a hacking tool. That is, it hacks your Android.
From the Pry-Fi Play Store page:
While you are not connected to a Wi-Fi network, the MAC address will constantly be pseudo-randomized, following a pattern that still makes the trackers think you are a real person, but they will not encounter your MAC address again. This will slowly poison their tracking database with useless information.
When you do connect to a Wi-Fi network, unless you specify otherwise, your MAC address will also be randomized - the same MAC address will not be used the next time you connect to this or any other network.
Click to expand...
Click to collapse
Try to find another app like that. I dare you.
Drakonas said:
I don't think you understand what Pry-Fi did, because WiFinspect does NOT do what Pry-Fi's main feature was.
From WiFinspect's Play Store page:
This statement would appear to be correct. My reply was a genuine attempt to help you by sharing an network penetration app that has been useful to me.
Pry-Fi is a hacking tool. That is, it hacks your Android.
From the Pry-Fi Play Store page:
I don't think I would consider changing my MAC address to be 'hacking my Android'. But even if you do, there are multiple MAC address changers available on the market. While they wouldn't randomize your MAC as often as Pry-Fi, they are still useful at concealing one's identity temporarily.
Try to find another app like that. I dare you.
Click to expand...
Click to collapse
You seem to have gotten -really- excited about this. Looks like similar functionality will be integrated into the next version of iOS:
http://www.theregister.co.uk/2014/06/10/ios_wi_fi_mac_address_trick/
The Pry-Fi app was created by one of our most Senior and respected developers here at XDA. It was just released in 2014, and was only ever released as a "proof-of-concept". To call his app "dead in development" and "not enough of a success" is rather insulting. Probably, like many of us, Chainfire only has 24 hours in his day and with family and work, has limited time to spend on such "proof-of-concept" projects.
samwathegreat said:
You seem to have gotten -really- excited about this. Looks like similar functionality will be integrated into the next version of iOS:
http://www.theregister.co.uk/2014/06/10/ios_wi_fi_mac_address_trick/
The Pry-Fi app was created by one of our most Senior and respected developers here at XDA. It was just released in 2014, and was only ever released as a "proof-of-concept". To call his app "dead in development" and "not enough of a success" is rather insulting. Probably, like many of us, Chainfire only has 24 hours in his day and with family and work, has limited time to spend on such "proof-of-concept" projects.
Click to expand...
Click to collapse
Why do you think I was saying it wasn't a success? I loved the app. It is well made.. But the discussion was closed, and people were saying "it's dead", so I thought that development had stopped. I wasn't mad at you, or anybody for that matter. Sorry. I need to think about how I'm saying things before posting... seems I was misunderstood.
I didn't mean to insult anybody. I also believe Chainfire is a very respected developer. He made SuperSU, for goodness sakes, not to mention many other heavily successful apps.
And yes, maybe "hacking" is saying too much. I was too quick to reply, and I apologize.
Drakonas said:
Why do you think I was saying it wasn't a success? I loved the app. It did well.. But the discussion was closed, and people were saying "it's dead", so I thought that development had stopped. I wasn't mad at you, or anybody for that matter. Sorry.
I didn't mean to insult anybody. Man, I need to learn to think about what I say.
Click to expand...
Click to collapse
I may have mistook your edit for the dev bashing we see all too often in some of these forums. It seems clear now that wasn't your intention. I apologize for the misunderstanding.
samwathegreat said:
I may have mistook your edit for the dev bashing we see all too often in some of these forums. It seems clear now that wasn't your intention. I apologize for the misunderstanding.
Click to expand...
Click to collapse
Don't worry about it. I know there's a lot of that out there. My brain explodes on threads I see on the internet where the OP author asks for help with a stupid question, the helpers try to tell them that it isn't possible or doesn't work that way, the author responds with insults and stupidity thinking they know everything, and then flaming ensues... It's dumb.
N00bs will be n00bs, I guess.
I do apologize, myself. I was probably a bit harsh with my first reply to you. I thought you were pointing me to WiFinspect to be a replacement for Pry-Fi. (you said "there are many apps like that, so I thought you were talking about Pry-Fi)
I probably should've looked at your username. If I had, I would've known that you knew what you were talking about. I've seen you around. I would recommend not red-fonting in the future, though. That might make some people think you're yelling at them, to be honest. Just some advice.
I, personally, own everything I love. I know freelance developers don't make much off their apps generally, so developers can count on my contribution, as well as bug reports instead of a Play Store review (honestly, does nobody know the developer can't fix the problem if he/she doesn't experience it themselves?).
I'm ranting here, but I'm just saying that I share your views.
But in any case, was I wrong in assuming that Pry-Fi is dead? I would hope it isn't, because it is an awesome app that also didn't eat that much battery while running in the background. I want to file a bug report, if it isn't dead.
Drakonas said:
But in any case, was I wrong in assuming that Pry-Fi is dead? I would hope it isn't, because it is an awesome app that also didn't eat that much battery while running in the background. I want to file a bug report, if it isn't dead.
Click to expand...
Click to collapse
Thanks for the reply. The most recent comment Chainfire has posted regarding Pry-Fi suggests that it is definitely not dead, but that because of other commitments/projects, it probably won't get worked on this summer, unless other Devs wish to develop it further. Good news is that although Chainfire himself admits it had "virtually no interest" (as you mentioned before), the new iOS feature that mimics some of the functionality has somewhat 'renewed' interest in it. I look forward to seeing updates possibly by this Fall. I've heard Chainfire rant about how much of a headache "SELinux" is causing to root app devs. It would seem your speculations about interest level were spot-on, but thankfully Chainfire suggests that he is not giving up on it.
I agree on the red-fonting. I often use red to highlight important steps in many posts, but in this case I do believe it was inappropriate.
And finally, I should apologize to @Swimboy46163 for somewhat 'hijacking' his thread...
Swimboy46163: Are you still having issues? Let us know if you would like to continue troubleshooting.
If you would like to read Chainfire's recent comments regarding Pry-Fi, see here:
http://forum.xda-developers.com/showpost.php?p=53266853&postcount=382
https://plus.google.com/+Chainfire/posts/Y4fjP6cH45v
If we were somehow able to unlock the bootloader and install custom ROMs, would this solve the Google ban problem or is the device itself banned?
fach1708 said:
If we were somehow able to unlock the bootloader and install custom ROMs, would this solve the Google ban problem or is the device itself banned?
Click to expand...
Click to collapse
You should, in theory, be able to install opengapps if it came down to it.
There isn't an issue though as Google has already, on multiple occasions now, stated that current devices will not have their access revoked.
If people could read the news stories it would help...
NJ72 said:
There isn't an issue though as Google has already, on multiple occasions now, stated that current devices will not have their access revoked.
If people could read the news stories it would help...
Click to expand...
Click to collapse
If you could read news you would know that current devices will lose support after 90 days
No, Google has said that all existing devices will be supported with security patches.
BBC News - Huawei's use of Android restricted by Google
https://www.bbc.co.uk/news/business-48330310
"Existing Huawei smartphone users will be able to update apps and push through security fixes, as well as update Google Play services."
This has been reiterated by Google themselves. So please, read before trying any one-up-manship thanks.
NJ72 said:
No, Google has said that all existing devices will be supported with security patches.
BBC News - Huawei's use of Android restricted by Google
https://www.bbc.co.uk/news/business-48330310
"Existing Huawei smartphone users will be able to update apps and push through security fixes, as well as update Google Play services."
This has been reiterated by Google themselves. So please, read before trying any one-up-manship thanks.
Click to expand...
Click to collapse
Now let us talk about the difference of OS-Updates/Fixes and Application-Updates/Fixes.
It is a fact that newer Android Releases aswell as Security Updates for the P30 Pro are in jeopardy - not currently but atleast after the temporary license has been withdrawn.
Also Google removed the Mate 20 pro from the Android Q Beta:
https://9to5google.com/2019/05/21/huawei-mate-20-pro-android-q-removal/
Please read the post you've quoted, as well as all the other websites reporting on this.
ALL EXISTING HUAWEI DEVICES WILL BE ABLE TO RECEIVE SECURITY FIXES NOW AND IN THE FUTURE AS PER EXISTING AGREEMENTS.
Beta access is completely different.
https://9to5google.com/2019/05/19/google-existing-huawei-phones/
Read the tweet in the link above from the official Android Twitter account.
NJ72 said:
Please read the post you've quoted, as well as all the other websites reporting on this.
ALL EXISTING HUAWEI DEVICES WILL BE ABLE TO RECEIVE SECURITY FIXES NOW AND IN THE FUTURE AS PER EXISTING AGREEMENTS.
Beta access is completely different.
https://9to5google.com/2019/05/19/google-existing-huawei-phones/
Read the tweet in the link above from the official Android Twitter account.
Click to expand...
Click to collapse
In those links my Browser wasn't able to find the Text which you typed in while your Capslock was active.
And the tweet from Android only tells something about Apps and the Playstore, aswell as all other sites. They don't mention that Huawei Users will be able to get Android Q or further Android Versions <-- but that is the biggest point!
Nobody can guarantee if Huawei will provide us with a stable Android Q version. Especially since they announced that theywill provide/are working on their own Operating System.
Let's tackle things in the order you've posted them:
1- I didn't put them in quotation marks, as such it is not lifted directly from a website linked or otherwise (apart from now this one I supposed). It was a paraphrase of all the other websites reporting on the issue.
2- The tweet (along with other sites) state that all future security patches and updates will be made available.
3- Android Q is irrelevant at this point. Security patches are not equal to future OS versions. Android Pie will be supported up to a point, and will continue to receive security patches. The P30 Pro may never get Android Q, I don't recall it ever being promised that it would receive Android Q. If I'm incorrect, and it was promised, then please provide the information. As an extension of this, however, Android Q can still be provided to the P30 Pro through the AOSP which has also been stated in numerous articles and news stories - both linked above and not.
Finally, to reiterate for the people at the back (and this is a direct quote):
"Huawei will continue to provide security updates and after-sales services to all existing Huawei and Honor smartphone and tablet products, covering those that have been sold and that are still in stock globally."
This isn't from a particular link, but is from Huawei themselves. (a copy of this can be found at this link, as well as many others: https://www.standard.co.uk/tech/huawei-google-ban-mean-for-huawei-phone-owners-a4146211.html )
I don't know what is hard for people to understand about this, I really don't. This ban (until it is lifted, which is a whole other discussion) will only affect currently unreleased devices, all existing devices will continue to function as intended, with no disruption to service from either Google, Android or Huawei - something that has been directly stated by all 3 separate entities.
Would you like me to provide any more direct quotations on the matter? Alternatively please contact Huawei directly, as they will forward you on their official statement, as they have done to me and likely everyone else who has contacted them about their P30 Pro.
Regarding Android Q, although it was not technically 'promised', I think that it is expected when you purchase a flagship phone for a lot of money. I expect a lot of people would not have purchased the device if they knew that it would never be updated to newer future versions of Android. I certainly would not have.
I'm just hopeful that if it comes to it, Huawei will be able to use the AOSP code to provide us with Android Q.
Ultimately this is all irrelevant speculation (IMO) as Lord Trumpington is just using this as a power-play to try and strong arm a trade deal with China. Once the trade deal is finalised all trade blocks will be lifted and things will go back to normal.
NJ72 said:
Ultimately this is all irrelevant speculation (IMO) as Lord Trumpington is just using this as a power-play to try and strong arm a trade deal with China. Once the trade deal is finalised all trade blocks will be lifted and things will go back to normal.
Click to expand...
Click to collapse
Hopefully you're right
So I'm surprised this isn't Priority One across the board for development with Android.
Now that it looks like John's gone, I'm actually shocked that no one is tried to take over or step forward to try and come up with an alternative. This should be all hands on deck Priority One as not having root is far sh1tt1er than having it. Maybe I just I'm not up to the newest dev news. Does anyone have any information on possible development about that?
The vvb2060 Alpha builds are still getting updated, and as that had been a trusted collaborator with John, that seems to be the current path for continued development.
Why does everyone assume that development of Magisk has stopped? Until we hear anything from John there's zero need for "fear mongering" and speculation...
FUD is what keeps forums running
Theraze said:
The vvb2060 Alpha builds are still getting updated, and as that had been a trusted collaborator with John, that seems to be the current path for continued development.
Click to expand...
Click to collapse
Yes I've been running the alpha build since earlyJune. However I worry/sneaking suspicion and inclination that his intention or competency level is to tweak existing technology rather than flat out create compatibility for Android 12 for example. These are my fears.
Burt Squirtz said:
Yes I've been running the alpha build since earlyJune. However I worry/sneaking suspicion and inclination that his intention or competency level is to tweak existing technology rather than flat out create compatibility for Android 12 for example. These are my fears.
Click to expand...
Click to collapse
You need to step back, take a chill pill, and unclench
73sydney said:
You need to step back, take a chill pill, and unclench
Click to expand...
Click to collapse
trying to look cool? Not sure why you bothered to type this - as absolutely nothing in my post would indicate that I'm not calm.
Surprised more people are asking this question about having root in the future.
Well.
It is better to think ahead but it may happen that demand will create supply.
It is basic market rule.
I hope & pray that current Magisk will continue to work even if site where it checks updates and modules disappears.
Burt Squirtz said:
trying to look cool? Not sure why you bothered to type this - as absolutely nothing in my post would indicate that I'm not calm.
Surprised more people are asking this question about having root in the future.
Click to expand...
Click to collapse
Because the FUD was boring a month ago
The only prospecting you should be doing should involve a gold pan
p.s. My default setting is humour, sometimes people get it, some dont, the clue would have been the 2 smilies i put in to try and make certain it was taken that way
p.p.s. Casting doubt on someones abilities (vvb2060) isnt cool, just saying, they guy is working largely on his own to add features/fixes from the original Magisk repo issues, so maybe cut him some slack? or help out?
i really like vvb2060 magisk lite approach
i hop he adds control to it throw a terminate
Didgeridoohan said:
Why does everyone assume that development of Magisk has stopped? Until we hear anything from John there's zero need for "fear mongering" and speculation...
Click to expand...
Click to collapse
Back in May, topjohnwu had already confirmed that Google is forbidding him from working on Magisk.
misterlink said:
Back in May, topjohnwu had already confirmed that Google is forbidding him from working on Magisk.
Click to expand...
Click to collapse
Since that screenshot is taken out of context from a longer conversation, that was private and not shared by John himself, it doesn't show the whole truth.
My statement still stands: wait until we hear anything official from John...
Game Over.
State of Magisk: 2021
Ever since my employment at Google, crazy speculations has been spreading like wild fire all over the Internet. The out-of-context private…
topjohnwu.medium.com
Game over? I think we read that text and came to two very different conclusions...
It's far from game over.
So as far i understand he is allowed to continue working on magisk but is not allowed to do any work on magisk hide or any hide module he claims that is just 5% of the work so if he does magisk and someone else adds magisk hide function it is all good right ?
mstrnemo said:
So as far i understand he is allowed to continue working on magisk but is not allowed to do any work on magisk hide or any hide module he claims that is just 5% of the work so if he does magisk and someone else adds magisk hide function it is all good right ?
Click to expand...
Click to collapse
This sounds simple enough, but Magisk without MagiskHide will be relatively useless since most apps that aren't a web browser will refuse to run because they detect root and/or an unlocked bootloader. This is the core problem that Magisk solves. The rest of the Magisk modules are nice to haves.
Until the apps try to detect modifications to themselves rather than simply seeing if there is a possibility of modification they are not doing anything for security but instead further locking users into their ecosystem.
l7777 said:
This sounds simple enough, but Magisk without MagiskHide will be relatively useless since most apps that aren't a web browser will refuse to run because they detect root and/or an unlocked bootloader. This is the core problem that Magisk solves. The rest of the Magisk modules are nice to haves.
Until the apps try to detect modifications to themselves rather than simply seeing if there is a possibility of modification they are not doing anything for security but instead further locking users into their ecosystem.
Click to expand...
Click to collapse
I would imagen magisk would not be useless as i would assume magisk and a hide module would be in development in paralell to each other so magisk by the creator and hide by other developer who is kind innof to help out so yeah.
unless people ditch magisk alltogether and fork it and do it difrently who knows
i just read the article about this on the xda homepage and read through the comments people seem to be freaking out and spell doom to custom roms and everything about it pretty funny though but i geuss the signs are on the wall....
mstrnemo said:
I would imagen magisk would not be useless as i would assume magisk and a hide module would be in development in paralell to each other so magisk by the creator and hide by other developer who is kind innof to help out so yeah.
unless people ditch magisk alltogether and fork it and do it difrently who knows
i just read the article about this on the xda homepage and read through the comments people seem to be freaking out and spell doom to custom roms and everything about it pretty funny though but i geuss the signs are on the wall....
Click to expand...
Click to collapse
Ok, useless might have been too strong. If a hide module is developed and maintained then things will largely stay the same. That said, until that materializes, it is the end of Magisk as we know it. Anyone who claims that nothing will change is going to give rise to a lot of disappointment. Don't get me wrong, there are lots of talented developers and one could very likey pick up where TJW leaves off but I certainly wouldn't bet on it.
IMO rather than fight with the our small community, Google/Android should provide us a way to self sign our devices and absolve themselves of any responsibility to keep our devices "secure".
l7777 said:
Ok, useless might have been too strong. If a hide module is developed and maintained then things will largely stay the same. That said, until that materializes, it is the end of Magisk as we know it. Anyone who claims that nothing will change is going to give rise to a lot of disappointment. Don't get me wrong, there are lots of talented developers and one could very likey pick up where TJW leaves off but I certainly wouldn't bet on it.
IMO rather than fight with the our small community, Google/Android should provide us a way to self sign our devices and absolve themselves of any responsibility to keep our devices "secure".
Click to expand...
Click to collapse
Yeah agree on your first part
now about that second part..
never going to happen why ? because what do you think we are to those companys? what do you think they would call us people who dont buy a new phone every year and keep older phones working for a couple years with the latest software huh ? we cost them money it is in their best interest that none of all this works and or is capable because if it wasnt everyone here would have to get a new phone ergo bringing in the bacon for those said companys...
I wish we could send out a message a reqeust to all the developers on this site and be like oke guys lets ditch android it is not worth the ffort anymore lets get together all of us and work on alternitives of wich we have 2
ubuntu touch linux os for phones (there are otheres but noone as far developt as this one) also it is stil not entirely their yet but it is very close.
sailfish wel basicly also linux this is next best thing to android it is based on nokia/intel meego project it is like i said linux based and open source this is what the developers should work on it is just rough araund the edges but works great one downside while it is opensource the ability to run android apps is properity software so developers would have to come with their own thing forexample maybe try and get wine to work on sailfish so u can use android apps as normal phone.
what do you think? developers unite in a avengers style and the ones who cant do code like myself help by donating ?
mstrnemo said:
Yeah agree on your first part
now about that second part..
never going to happen why ? because what do you think we are to those companys? what do you think they would call us people who dont buy a new phone every year and keep older phones working for a couple years with the latest software huh ? we cost them money it is in their best interest that none of all this works and or is capable because if it wasnt everyone here would have to get a new phone ergo bringing in the bacon for those said companys...
I wish we could send out a message a reqeust to all the developers on this site and be like oke guys lets ditch android it is not worth the ffort anymore lets get together all of us and work on alternitives of wich we have 2
ubuntu touch linux os for phones (there are otheres but noone as far developt as this one) also it is stil not entirely their yet but it is very close.
sailfish wel basicly also linux this is next best thing to android it is based on nokia/intel meego project it is like i said linux based and open source this is what the developers should work on it is just rough araund the edges but works great one downside while it is opensource the ability to run android apps is properity software so developers would have to come with their own thing forexample maybe try and get wine to work on sailfish so u can use android apps as normal phone.
what do you think? developers unite in a avengers style and the ones who cant do code like myself help by donating ?
Click to expand...
Click to collapse
Oh I would never expect #2 to happen either, that is why it's only my opinion.
A phone OS not managed by a large corporation would be great, but it couldn't survive without the app stores of the large corporations. That is what they are making money off of, not the devices. I think most of us already realize that so I'm just stating the obvious.