SO I did some research and found some very interesting info about the bootloader bull**** that is going on with Android.
read about it here.
This means good bye to un locking bootloaders... Mine is unlocked and because of android/google my dam phone keeps showing an aggravating massage that its not trusted when i turn it on ... Im pretty sure now after Nougat, people will be going to Apple in droves...
nickcaper said:
SO I did some research and found some very interesting info about the bootloader bull**** that is going on with Android.
read about it here.
This means good bye to un locking bootloaders... Mine is unlocked and because of android/google my dam phone keeps showing an aggravating massage that its not trusted when i turn it on ... Im pretty sure now after Nougat, people will be going to Apple in droves...
Click to expand...
Click to collapse
1) This is Sony's choice to allow the unlocking of bootloaders or not, there's no reasons that they don't allow it in the future.
2) Do you know that 90% of android users aren't rooted, so...
niaboc79 said:
1) This is Sony's choice to allow the unlocking of bootloaders or not, there's no reasons that they don't allow it in the future.
2) Do you know that 90% of android users aren't rooted, so...
Click to expand...
Click to collapse
Yes yes.. but...... Google is making it harder to root phones. Nougat will be even worse...
nickcaper said:
Yes yes.. but...... Google is making it harder to root phones. Nougat will be even worse...
Click to expand...
Click to collapse
Rooting devices with a locked bootloader can be seen as a security exploit, and the ability to do so means that Android is insecure.
What you basically complain about here, is that Google is trying to make Android more secure.
If you want to root your phone, just unlock your bootloader and flash SuperSU. That will always be possible.
The trick is, that unlocking your bootloader will wipe your data partition (hence securing your data from a potential breach when somebody stole your phone). The security warning at the beginning, is to let you, and potential reselling partys know that the bootloader is unlocked, and that with little to no effort all Android internal security measures can be worked around (flash a recovery and root it, and you're a happy data thief).
Of cause from an XDA-Users point of view it looks like that is something bad, but keep in mind that people like the ones you can find on XDA make up a roughly 1% of all Android Users. You need to keep in mind, there are also a lot of business users on Android, and these feel a lot better knowing that there secure company data is save on an Android device. Security used to be one of the major reasons why in the initial Android days nobody was using Android as a business device, and rather was sticking to Apple, cause iOS Devices were a lot securer by that time.
The message at the beginning is one of the reasons why I am still searching for a root exploit on my XP, so I can backup the TA partition and in case I resell it some day I can just relock the bootloader by restoring the partition, but after all, you need to admit that the warning itself is sensible, when you keep the above points in your mind
Myself5 said:
Rooting devices with a locked bootloader can be seen as a security exploit, and the ability to do so means that Android is insecure.
What you basically complain about here, is that Google is trying to make Android more secure.
If you want to root your phone, just unlock your bootloader and flash SuperSU. That will always be possible.
The trick is, that unlocking your bootloader will wipe your data partition (hence securing your data from a potential breach when somebody stole your phone). The security warning at the beginning, is to let you, and potential reselling partys know that the bootloader is unlocked, and that with little to no effort all Android internal security measures can be worked around (flash a recovery and root it, and you're a happy data thief).
Of cause from an XDA-Users point of view it looks like that is something bad, but keep in mind that people like the ones you can find on XDA make up a roughly 1% of all Android Users. You need to keep in mind, there are also a lot of business users on Android, and these feel a lot better knowing that there secure company data is save on an Android device. Security used to be one of the major reasons why in the initial Android days nobody was using Android as a business device, and rather was sticking to Apple, cause iOS Devices were a lot securer by that time.
The message at the beginning is one of the reasons why I am still searching for a root exploit on my XP, so I can backup the TA partition and in case I resell it some day I can just relock the bootloader by restoring the partition, but after all, you need to admit that the warning itself is sensible, when you keep the above points in your mind
Click to expand...
Click to collapse
No I still do not agree. Maybe they should just show it one time. Or a couple of times. not every friggin time I boot the phone. This is clearly to have people start to really consider NOT rooting there personal property.
When I buy a car. I can do what ever the want with it. Same with a house. But, these phone companies want us to use this device the way THEY want. Why? cause they want to track everything we do on it. Rooting stops that. Rooting enables me to delete apps that are totally useless and take up space and data on the phone. Rooting allows me to edit files, delete files, ad files the way I WANT THE PHONE to work. Not the way THEY want it to work.
It is super easy for these companies to let the new buyer know that the boot loader has been unlocked, let the person click a button to approve the unlock, then move on and let the person use the phone with no further warnings.
This warning is just about the same thing if you would change your cars radio or tires or engine parts, not use the factory parts, and the car would play a alert through the dash board or speakers every time you turn on the car that someone used there own parts, not the factory parts, to fix an issue.
NO I dont agree with you. Its no sensible....
If you think its sensible.... cool... Let people start doing this on every device, washing machines, microwaves, stoves, cars, TV,s stereos..... See how happy people get...
nickcaper said:
No I still do not agree. Maybe they should just show it one time. Or a couple of times. not every friggin time I boot the phone. This is clearly to have people start to really consider NOT rooting there personal property.
When I buy a car. I can do what ever the want with it. Same with a house. But, these phone companies want us to use this device the way THEY want. Why? cause they want to track everything we do on it. Rooting stops that. Rooting enables me to delete apps that are totally useless and take up space and data on the phone. Rooting allows me to edit files, delete files, ad files the way I WANT THE PHONE to work. Not the way THEY want it to work.
It is super easy for these companies to let the new buyer know that the boot loader has been unlocked, let the person click a button to approve the unlock, then move on and let the person use the phone with no further warnings.
This warning is just about the same thing if you would change your cars radio or tires or engine parts, not use the factory parts, and the car would play a alert through the dash board or speakers every time you turn on the car that someone used there own parts, not the factory parts, to fix an issue.
NO I dont agree with you. Its no sensible....
If you think its sensible.... cool... Let people start doing this on every device, washing machines, microwaves, stoves, cars, TV,s stereos..... See how happy people get...
Click to expand...
Click to collapse
Do you own a car? almost every state has safety inspections, you can't drive around with a compromised airbag/seatbelts/brakes. you'll get pulled over if even a lightbulb is broken. Sure you can do anything to your car, as long as it doesn't compromise its safety.
Do you own a house? every state has safety regulations when building one. Sure you can do anything you want to your house, as long as it doesn't compromise safety.
Android is securing their platform, there's nothing wrong with that. You're even given an OFFICIALLY supported method to root, just unlock the bootloader. You're crying about a warning you only see when you boot the phone for half a second? really? the ENTIRE world Android population needs to be held hostage by crippled security because you don't like a yellow exclamation point on a boot screen for a few milliseconds? Jesus christ the entitlement on some kids
/rant
Oh my... It reminds me of the time when I had an HTC with s-off, every time I booted the phone it showed the joker with the s-off message.
It destroyed my life.!
The phone still works fine though.
Sent from my F8131 using XDA-Developers mobile app
acme64 said:
Do you own a car? almost every state has safety inspections, you can't drive around with a compromised airbag/seatbelts/brakes. you'll get pulled over if even a lightbulb is broken. Sure you can do anything to your car, as long as it doesn't compromise its safety.
Do you own a house? every state has safety regulations when building one. Sure you can do anything you want to your house, as long as it doesn't compromise safety.
Android is securing their platform, there's nothing wrong with that. You're even given an OFFICIALLY supported method to root, just unlock the bootloader. You're crying about a warning you only see when you boot the phone for half a second? really? the ENTIRE world Android population needs to be held hostage by crippled security because you don't like a yellow exclamation point on a boot screen for a few milliseconds? Jesus christ the entitlement on some kids
/rant
Click to expand...
Click to collapse
Come on now... You really think that a phone should be treated this such ridiculous nonsense?
They can secure there platform without the stupid notification. Geez man.. you must really like being under control of corporations...
nickcaper said:
Come on now... You really think that a phone should be treated this such ridiculous nonsense?
They can secure there platform without the stupid notification. Geez man.. you must really like being under control of corporations...
Click to expand...
Click to collapse
Yes! unlike you some people do serious work with their phones. It's so important Blackberry is banned in some countries over security concerns. This is not a ****ing game.
A warning on your boot screen is not a restriction, it's a compromise. Learn the difference.
Mod Edit
Thread Closed and addressed. This thread and OP has ran it's course....
nickcaper said:
Ohhh ook..
Mod Edit.
!
Click to expand...
Click to collapse
Related
I was thinking if anyone knew about htcs and t-mobiles view on rooting
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app. So I would reasonible believe they don't want you to. Another thing is they do not warranty work on rooted devices
What do you mean they do not warranty work on rooted devices
Meaning a rooted device loses its warranty if its sent in rooted, if its been flashed back then it still has its warranty...
I doubt Google and HTC care if we root our devices, they don't loose out, and they sell rooted phones any way (ADP1 and I think the ION is rooted too). I guess the only reason google would care is app piracy...
M..N said:
What do you mean they do not warranty work on rooted devices
Click to expand...
Click to collapse
If you root your phone, kiss good bye to your warranty. It really doesn't matter though, if it's a hardware issue you can unroot and they'll never know, and if it's bricked you can say it was update that bricked it.
Has anyone in the uk replace their phone successfully
M..N said:
Has anyone in the uk replace their phone successfully
Click to expand...
Click to collapse
What do you mean?
I mean has anyone in the uk replaced a bricked phone caused by the new spl without any problems
HTC aren't going to bothered with what people do, neither are Google really. It's the network operators which want to tie people to their crap and have you pay for it.
The issue is with the warranty and if you broke it, Asus, for example, aren't bothered what OS you run on their hardware, but if you flash a bad BIOS then it's your fault. ATI, nVidia, Gigabyte etc encourage overclocking but won't honour warranty if it causes damage.
Google are likely to secretly want rooted phones as more network operators mangle the OS to suit themselves in the future and push their own services over Googles.
M..N said:
I was thinking if anyone knew about htcs and t-mobiles view on rooting
Click to expand...
Click to collapse
My guess is that T-Mobile doesn't want rooting because it allows tethering.
Tethering generally causes an increase in data usage, and an increase in bandwidth use by the phone. This can impact T-Mobile cell towers and other T-Mobile customers if too many tethered phones are sucking up bandwidth on a particular tower.
gridlock32404 said:
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app.
Click to expand...
Click to collapse
My recollection is that that bug was patched because it allowed any app to gain root access for itself, not just the end user. Hopefully I don't need to explain why that's a bad thing. The patch didn't specifically patch out root access for the user because root access for the user was never a design feature to begin with.
M..N said:
I was thinking if anyone knew about htcs and t-mobiles view on rooting
Click to expand...
Click to collapse
If you really want to know the official views of these companies, email or call them. Most of the members of xda-dev are not employed by/affiliated with either company, and as such it is impossible to tell if they're telling truth, passing along unverified rumor/hearsay, or just making bs up.
gridlock32404 said:
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app. So I would reasonible believe they don't want you to. Another thing is they do not warranty work on rooted devices
Click to expand...
Click to collapse
You can also look at it like they don't care if you do it but they don't want a one click solution that will allow every freakin retard out there to do it. Think about it how many stupid questions do we get from people who used the one click vs ones who did it manually.
Also having an app with that kind of access to the phone means ANY app can have that kind of access to your phone including the bad evil kind you dream of making gridlock.
The problem with rooting is this;
Some very small number of people understand the system and can be fully self-sufficient with full root access.
And then you have the others, who want root for whatever features come with it... and some of them start messing with things they don't understand and end up in a huge mess... and then send it back for warranty work because their device doesn't work right any more. This means MUCH more support from the retailer/manufacturer. The other side of this is that if you have a whole lot of people trying things like cyanogen's latest unstable mod and show it off to a whole lot of people, and it crashed like nuts, then the people who see it don't necessarily understand that it is due to running crazy experimental stuff and instead think that 'droid itself is junk.... which is incorrect.
So preventing root access means that you have a simpler, more consistent, and more reliable environment, which means a better platform reputation and lower overall support costs.
lbcoder said:
The problem with rooting is this;
Click to expand...
Click to collapse
There's another point of consideration. While I know I just wrote about the unverifiability of some posts on xda, i'm going to have to do a complete 180 and do just that. I can't confirm since I'm not a handset maker (nor do I work for one), but i'm quite confident in believing that in order to acquire Google's consent and software support to create a Google Experience phone, root access has to be restricted from the end user. Again that's all speculation.
lbcoder said:
The problem with rooting is this;
Some very small number of people understand the system and can be fully self-sufficient with full root access.
And then you have the others, who want root for whatever features come with it... and some of them start messing with things they don't understand and end up in a huge mess... and then send it back for warranty work because their device doesn't work right any more. This means MUCH more support from the retailer/manufacturer. The other side of this is that if you have a whole lot of people trying things like cyanogen's latest unstable mod and show it off to a whole lot of people, and it crashed like nuts, then the people who see it don't necessarily understand that it is due to running crazy experimental stuff and instead think that 'droid itself is junk.... which is incorrect.
So preventing root access means that you have a simpler, more consistent, and more reliable environment, which means a better platform reputation and lower overall support costs.
Click to expand...
Click to collapse
Good breakdown.
StanSimmons said:
My guess is that T-Mobile doesn't want rooting because it allows tethering.
Tethering generally causes an increase in data usage, and an increase in bandwidth use by the phone. This can impact T-Mobile cell towers and other T-Mobile customers if too many tethered phones are sucking up bandwidth on a particular tower.
Click to expand...
Click to collapse
I dunno about in the US, but this would most likely be T-Mobile UK's problem.
The terms of the contracts say that you can't tether with the standard net package, you need to upgrade to the next one (extra £10 instead of £5) to be able to use your 3G/HSDPA connection on the PC.
Problem is, with phones like the G1 how would they know? If it was something like an old Sony Ericsson W810 they would know straight away due to the amount you were downloading but on a G1 you can view full webpages anyway, download images etc and programs via the market. So really they have no way of knowing if you're tethering of not. Hence they want to try and stop tethering from being an option.
Fingerlicken, why would I Target a system I use, if I let out any kind of evil it would be against an Iphone.
Why does Linux have so little viruses, cause most of the hackers use linux
gridlock32404 said:
Why does Linux have so little viruses, cause most of the hackers use linux
Click to expand...
Click to collapse
Wha? I think you have your cause and effect mixed up. Also, this thread is getting off topic.
Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!
Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.
You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.
Jaywan, how about a simple root and s-off?
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.
BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.
also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567
Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt
For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.
jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse
I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!
ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.
jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.
I suppose this would most applicably be in the general android forum, but I've had such a nice response from the crew still hanging around in the hero forums I figured I'd post here...
Obviously there's some inherent risk to giving root access to certain apps, you should either trust your developer or be able to parse through potentially thousands of lines of code to find mismatched bits that could cause security flaws or intentionally be security flaws...
So what if you make a poor decision to install/flash some code that you know or think is malevolent?
Is it even possible to rid your phone of the situation? I would think if it's a ROM or app, just reflashing and building your customization from scratch would do there...
but what if you were flashing virulent code to the areas beyond where the roms go? Certainly there is some disk space that holds the recovery image, bootloader, etc...
If someone wants to tackle this topic by explaining what I imagine is a generic unix n00b question, I'd appreciate it. Thanks in advance.
this is a great little thought provoking idea, hopefully you get some constructive input..
im not sure of the exact ins and outs of where the roms install their components.. however, i do know that it is a good idea to have some sort of "virus" (for lack of a better term) protection, the program "Lookout Mobile Security" is really good.. its always on the top of its game as far as malware goes.. if i installed something that i thought was malicious and was unsure of how to get rid of it, i would just RUU and completly wipe the phone.. i dont know of anything that can withstand a RUU yet, but again i honestly havent seen too much malicious content either.. the worst i have seen is when people are trying to get paid apps for free by downloading them from other random people/sites.. some of the coders will put stuff in it.. there was one guy specifically i remember that tried to get a paid app for free, downloaded it and the app proceeded to fill his sd card with pictures of dongs.. which i thought was kind of funny, but it wasnt for him..
hopefully thats some of what you are looking for..
I have Lookout, and many reasons to appreciate it. Lookout was on top of the DroidDream virus thing the same day Google released a statement, they had informed all of their users via email. That doesn't completely comfort me though, I have no idea to what extent they scan for malware. Is it cloud scanning? is it a heuristics definition check? Even with giving Lookout 'device administrator' credentials on a rooted droid, does lookout use that ability to sift through /system and beyond for trojans, dialers, data-miners? I know that on windows systems, rootkits can easily evade detection by application-layer and even kernel-layer antiviruses. The only way to find them, and it's not even surefire, is to run a unix based liveCD AV with current definitions.
The sheer volume of apps available in the market and the fact that they're all updated very frequently makes it near impossible for a third party company like lookout to keep track of whats available. Herein lies what I would like to say is truly Google's responsibility. With the resources they have available to them, I can't understand why they don't have a significantly trustworthy preliminary check on anything uploaded to the market. Sure, the author signs a digital contract to assume liability, but then they quickly write it off in their own license.
Not to get completely off topic, but it's also concerning that there's no standardized way for a user to control the level of privacy breaching you want to allow an app. It's baffling at times to see a simple game app want access to location and see/edit contacts. Sure, there's most likely a good reason, but a single update from market and an 'oops didn't mean to do that' from the author lands him a fresh batch of thousands of live email addresses to spam.
I've torrented enough in the past to know to stay clear away from any cracked applications, unless you plan on running them on a device that has absolutely no sensitive data and/or never going to connect to the internet. running a keygen.exe is akin to deleting system32. That SD rabbit virus is unfortunately humorous.
Thanks for the tip about doing an RUU and starting from true scratch. That definitely makes the most sense if one is truly concerned. Tedious, but what about linux isn't?
Phone's ringing, dude
.
nandroids are for
sissies
pstevep said:
this is a great little thought provoking idea, hopefully you get some constructive input..
im not sure of the exact ins and outs of where the roms install their components.. however, i do know that it is a good idea to have some sort of "virus" (for lack of a better term) protection, the program "Lookout Mobile Security" is really good.. its always on the top of its game as far as malware goes.. if i installed something that i thought was malicious and was unsure of how to get rid of it, i would just RUU and completly wipe the phone.. i dont know of anything that can withstand a RUU yet, but again i honestly havent seen too much malicious content either.. the worst i have seen is when people are trying to get paid apps for free by downloading them from other random people/sites.. some of the coders will put stuff in it.. there was one guy specifically i remember that tried to get a paid app for free, downloaded it and the app proceeded to fill his sd card with pictures of dongs.. which i thought was kind of funny, but it wasnt for him..
hopefully thats some of what you are looking for..
Click to expand...
Click to collapse
Where can I find this "Dong" Virus? Did it originate from Anthony Weiner's Twitter account? I know a few people that I would love to have that "pop up" on their phone. My SD card is already filled with such displays.LOL
I just got my Moto X Pure Edition (THIS one) and I really want to root it and get all the things I had with my G3 and back when I had an JB'd iPhone 4s, but my experience with the G3 was terrible.
I ended up having to RMA it 4 times through my insurance because there was something I was using on the G3 that slowed it to a vista-esque pace, and despite lots of reading on this site and others I managed to brick it :silly: 4 times :silly: in 4 different ways just trying to put it back to stock. It cost me far too much money but I was stupid enough to keep trying before finally settling on stock to avoid more issues.
I love this new phone, but I know I could tweak it more to what I like and from what it looks like in Heisenberg's Guide it is fairly safe and simple as far as roots go. I feel so stupid having screwed up with the LG that I don't want to try it. I'm a CS major and I've spent so much time messing with all sorts of things I never thought it would be a problem.
So my question is, within the realm of using Xposed and a few root apps/functions (no custom ROMs or anything just because I can't afford not having a phone for a week if I ruin it again), is it relatively safe to root the X Pure and are these tools (Universal Tool, Restore to stock tool) or a manual set of steps a good bet for returning to stock and removing root? I just want to make sure if I end up over my head I can get back to stock and be happy with what is already a great phone. Sorry if I sound like a huge _____ but I'm still in school and I want to avoid further grief as best I can.
From what I've been hearing, the 808 is a tricky processor... Besides xposed and regular terminal code changes, such as screen density, you should be good. Although, if your going in and messing with code idk what to say, experienced devs are even having a tough time getting this thing to boot on their custom ROMs...
You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk
Another thing just to keep in mind when talking people about your qualifications, saying you are getting your Computer Science degree is pretty broad. First, we don't know what year you're in and second we don't know your concentration. I have a BBA for instance. A BBA in what though? If I went applying to random jobs, or trying to network that would leave more questions than answers. What do I have a BBA in? Well mine is in Management, so yes I can do basic accounting, financing, marketing, but my concentration is being able to interpret financial data and making decisions that would benefit a company or organization. Does that make me advanced enough to be an accountant, even though we both have BBAs? Hell no! Same goes for CS. You may be getting your computer science degree, but are you majoring in Network Security, Hardware, C++, Java, Oracle, etc... There is so much information missing that just stating "I'm getting my CS degree" isn't enough for anyone to give you a solid answer, especially not knowing what year you are in. If you are a junior, then you've just barely scratched the surface of what you will be studying for the next 2 years. Just a little FYI for future sakes :thumbup:
PiousInquisitor said:
You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Well that's helpful.
Didn't think to specify, my bad, yeah I'm just a junior and I feel like I haven't learned much in the way of things. I just want to get a few small things from xposed and others, no plans on changing anything myself
DrPhill94 said:
Well that's helpful.
Click to expand...
Click to collapse
You bricked 4 G3s. It's time to find a new hobby. I suggest one that doesn't include the destruction of expensive electronics.
Sent from my XT1575 using Tapatalk
I own Oneplus One and rooted immediately with blisspop rom. I can't use phn without root access coz almost all ma apps need root permission. Yes its risky to root a costly device but if u need it so desperately den u should definitely root it....
Again, thanks for the positive input. I bricked them following the stock flashing methods on this website, I wasn't just shooting in the dark. And out of another half dozen phones I've only ever had an issue with the G3. Can you not? I'd like to learn here, not argue.
U having plm installing recovery on ur g3???
When it comes to just simply rooting and installing xposed, I don't see how you can brick it following step by step instructions. I will say this. If you brick it and you can't figure out how to get it back to stock, Motorola has made it clear you're on your own. So there's that, but using a simple toolkit can make a worlds difference in preventing mistakes. Yes, you'll feel like an amateur, and let's be honest, you are right now, but it beats losing $400.
You also just got it and you have no idea if you have any hardware issues that many have had to RMA within the first week for. So maybe sitting on it for a week or 2 couldn't hurt to eliminate that possibility as well (Bad CPU/GPU, Speaker, Light Leakage, loose parts when shaken, excess battery drain/heat, and turbo charge randomly not working, etc.). Motorola/Lenovo were at first being lenient about replacing these even with unlocked bootloaders and even giving people a month to send these back, they are wising up and change the rules since people have been making such a big fuss about the bootloader thing, and posting about the one month holding time (now I've read recently it's 3 days?), so just be careful, that's all.
nikeman513 said:
When it comes to just simply rooting and installing xposed, I don't see how you can brick it following step by step instructions. I will say this. If you brick it and you can't figure out how to get it back to stock, Motorola has made it clear you're on your own. So there's that, but using a simple toolkit can make a worlds difference in preventing mistakes. Yes, you'll feel like an amateur, and let's be honest, you are right now, but it beats losing $400.
You also just got it and you have no idea if you have any hardware issues that many have had to RMA within the first week for. So maybe sitting on it for a week or 2 couldn't hurt to eliminate that possibility as well (Bad CPU/GPU, Speaker, Light Leakage, loose parts when shaken, excess battery drain/heat, and turbo charge randomly not working, etc.). Motorola/Lenovo were at first being lenient about replacing these even with unlocked bootloaders and even giving people a month to send these back, they are wising up and change the rules since people have been making such a big fuss about the bootloader thing, and posting about the one month holding time (now I've read recently it's 3 days?), so just be careful, that's all.
Click to expand...
Click to collapse
Sounds like a solid plan. With the G3 rooting was always easy but the only known way that I had found for the t mobile model was to use the LG flashing tool that looked a lot like the one they used in-house to restore it, and despite following a pretty straightforward guide there were 3 different errors I got right towards the end of the process that would lock the phone in a download mode state. After using TWRP to get it back to being usable I'd still be stuck with root, and trying a few other ways would screw me.
As far as using the tools, are the 2 I linked in the OP the proper ones to be using? I'll definitely hold off on it for a while to make sure nothing comes up, thanks for that info. I'm guessing the 2 year protection plan is moot if I'm stuck with no way to erase evidence of a software issue arising from root, so that's a thing to think about as well. Do you know if unlocking the bootloader voids that protection plan? I'm looking for the TOS.
PiousInquisitor said:
You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I could not have said this any better.
Judging from the attitudes of you two it's a wonder I stopped using this forum. Thanks fellas, really shows the quality of the community here.
I have always rooted my phones from my original HTC incredible, galaxy nexus, HTC DNA, and HTC ONE M8... that being said I am very familiar with HTC and how they work and I always had the HTC RUU file ready in case of emergency but never had to use it. I'm not sure if Motorola has a RUU file or a Fastboot IMG like Nexus devices that can bring your phone back from the dead as this is my first Moto because I never wanted to deal with the encrypted bootloader on the VZW moto phones.
I honestly can say that I have been finding root less and less needed since my M8 and I dont think I will unlock or root my Pure Edition.
The reason is that there is no bloat that I cant get rid of, I see no need for a custom kernel since the newer processors are really fast, it basically runs stock android so its not bogged down by Sense or touchwiz.
I honestly can say I like the minor additions Moto has made with the Pure Edition... I have used exposed and I really dont see the use for most of its functions for more than a week before its just gimmicky.
Once updates are stopped or the Development community is way ahead of OTA updates we will still have an easy OEM process to unlock root and flash. But for now I'm sticking with what I paid for... The Moto experience
My favorite XDA line in ages, "I feel I haven't learned much in the way of things"
Sent from my XT1575 using XDA Free mobile app
If you follow step by step instruction you will be ok.... I have rooted tons of phones and bricked a couple but was able to fix them. Its a chance you take but hey if you mess up it is a excuse to get a new cell lol. But honestly your streak with rooting is bad, maybe you shouldn't try anymore.
DrPhill94 said:
Judging from the attitudes of you two it's a wonder I stopped using this forum. Thanks fellas, really shows the quality of the community here.
Click to expand...
Click to collapse
I'm sorry I offended you. Based on your history I think it a bad idea for you to mess with your phone. Not what you wanted to hear but I honestly think it's the truth. Not all computer science majors can handle phone tech. How many of your classmates have iPhones? How many of them with Android phones root?
Sent from my XT1575 using Tapatalk
jiggyb21 said:
My favorite XDA line in ages, "I feel I haven't learned much in the way of things"
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
Come on, don't pigeon hole everyone on XDA. You had to have known you were going to receive some sarcastic replies. That's like Plaxico Burress asking what kind of gun he should buy next. The consensus here seems to be genuine. You shouldn't mess with root anymore but it's your money. Thing is, rooting is not hard and not dangerous if you follow directions closely, yet you've managed to brick several devices. I rooted my phone to install Xposed but due to battery issues I have stopped using it. Look in the Xposed thread for more info. I would say just wait, its not worth it now IMO.
IMO, the only reason to root is to install AdAway.
Can't stand Ads. But other than that, the experience that Motorola has set up for us is perfect. I won't be adding anything else like Xposed, or install a custom ROM until I get bored with my phone, which will probably be in another six months. I've set myself up with an unlocked bootloader and root for when the time comes though. But for now, I'm happy.
I gotta say that to me (sophmore in college as a Biology major, completely unrelated to compsci), it seems pretty hard to brick a phone just trying to root it. Especially with the very detailed guides that Hesisenberg has set up for us, thank that man.
You gotta decide if what you plan on doing with your root is worth it though. I spent about 1.5 hours rooting my phone, and I'm not even sure that the time was worth AdAway.
Will Sprint LGG6 Ever Obtain Root or Unlocked Bootloader?
Magic 8-ball says: Ask again later...
I hate these questions. They make me feel more doubtful, lol. Heck, if we knew that everybody would be buying one and waiting in anticipation.
Sent from my LG-LS993 using Tapatalk
The million dollar question. I hope it happens but this is the first phone stock I've had that doesn't annoy me. I actually barely notice at all but I love to flash so maybe one day
My phone runs great no issues so it's not a big thing to have it rooted in that aspect, however. I like to keep NANDROID backups in case something happens, and the ability to backup applications the way I want is very important to me. Just using apps to backup everything is one thing, but if something occurs on a system level, you are generally screwed unless you have ROOT to be able to tinker and fix it yourself. I was able to fix countless phones on my own when the stores would want to wipe to factory reset or give me a refurbished. Screw that mess, give me freedom. Besides, it's illegal for them to deny you insurance claims based on ROOT. They legally have to prove that you damaged the phone by modifying the software. Battled and won twice after threats of a lawsuit. I have that part of the consumer rights saved in multiple places, just need to remember where so I can post it.
It all depends on whether or not the bootloader is locked, dm-verity, restrictions, etc. I hope it's not something like the Galaxy S7 with its Qualcomm Secure Boot.
The bootloader isn't even accessible from any user accessable means from what I've encountered, I can't seem to get in, I have "Enable OEM unlock" in settings, but it just seems that fastboot has been entirely stripped from this device... Very weird.
source code for Sprint G6
enzeden said:
Will Sprint LGG6 Ever Obtain Root or Unlocked Bootloader?
Click to expand...
Click to collapse
dont know if this could help. i wouldnt know what to look for..
opensource.lge.com/osSch/list?types=ALL&search=LS993
Is this fake?
https://www.getdroidtips.com/root-install-twrp-recovery-sprint-lg-g6/
Sent from my LG-LS993 using Tapatalk
hoonigan43 said:
Is this fake?
https://www.getdroidtips.com/root-install-twrp-recovery-sprint-lg-g6/
Sent from my LG-LS993 using Tapatalk
Click to expand...
Click to collapse
yep
l33tlinuxh4x0r said:
yep
Click to expand...
Click to collapse
Figured ?
Sent from my LG-LS993 using Tapatalk
I'm guessing no one is even working on root or bootloader unlock. Seriously, disappointing. I just want bloat gone.
MikeDroid said:
I'm guessing no one is even working on root or bootloader unlock. Seriously, disappointing. I just want bloat gone.
Click to expand...
Click to collapse
Why dont you look for a bootloader exploit or donate your phone to someone who can do it?
Mr nerd said:
Why dont you look for a bootloader exploit or donate your phone to someone who can do it?
Click to expand...
Click to collapse
Because I like to go outside every now and then and I need a working phone. Don't care to go back to old Nexus.
MikeDroid said:
I'm guessing no one is even working on root or bootloader unlock. Seriously, disappointing. I just want bloat gone.
Click to expand...
Click to collapse
You can still anti bloat through android.. by disabling apps manually. But yeah I feel your pain.. I hate ads, I miss Xposed, I miss TWRP.. My note 5 i still keep around for that reason...
Truth is the LG G6 is a spectacular phone.. But the rooting community is getting smaller and smaller as android allows you to be more customizable and the average device life for people has gone from 2-3 years.. to every year now with leases and trade ins at carriers, and flagship phones coming out every 8-14 months.
WIth the G4 randomly dying, and the G5 having battery issues.. It took LG a while to get it right, and I love this phone more than the s8 and s8+ but LG jumped on the "apple/samsung" bandwagon by locking bootloaders... There are alot more people with Samsungs than LGs right now.. The reason behind all the companies going this route is because of Android Pay and proprietary security by phone manufacturers to push more sales through corporate and enterprise security..
At least LG is over time unlocking some variants ( albeit international) of the G6 its hopeful...
We used to have this luxury with HTC but they are still trying to stay afloat.
Those are just my observations... from working for an indirect dealer and rooting tons of phones for 9+ Years.
We just have to pray for an exploit- somewhere.. someone out there has turned it into an obsession... Lets just hope they emerge ....
chaosrecords said:
You can still anti bloat through android.. by disabling apps manually. But yeah I feel your pain.. I hate ads, I miss Xposed, I miss TWRP.. My note 5 i still keep around for that reason...
Truth is the LG G6 is a spectacular phone.. But the rooting community is getting smaller and smaller as android allows you to be more customizable and the average device life for people has gone from 2-3 years.. to every year now with leases and trade ins at carriers, and flagship phones coming out every 8-14 months.
WIth the G4 randomly dying, and the G5 having battery issues.. It took LG a while to get it right, and I love this phone more than the s8 and s8+ but LG jumped on the "apple/samsung" bandwagon by locking bootloaders... There are alot more people with Samsungs than LGs right now.. The reason behind all the companies going this route is because of Android Pay and proprietary security by phone manufacturers to push more sales through corporate and enterprise security..
At least LG is over time unlocking some variants ( albeit international) of the G6 its hopeful...
We used to have this luxury with HTC but they are still trying to stay afloat.
Those are just my observations... from working for an indirect dealer and rooting tons of phones for 9+ Years.
We just have to pray for an exploit- somewhere.. someone out there has turned it into an obsession... Lets just hope they emerge ....
Click to expand...
Click to collapse
Ditto on all that. For ads, I've used the all in one opt out which has eliminated lots of ads. Bloat is irritating, having to reset Google Voice after every update. Xposed was awesome. And I want all the Sprint badging and boot animation gone. Even temp root would make me happy.
Just everybody remember. Do not update. Usually root is achieved on lowest firmwares only in the last few history of lg series
Someone just messaged me this: Maybe some jtag process could work, or test point at qcom mode, dumping boot.img and rooting with magisk