Related
Hey guys,
i got my TF300T now for about 4 Months. I already sent it back to asus once because my Touchscreen wasnt working correct. After i got it back my screen was okay again but all around it (not the Screen itself, the area around) is making noises. Just a little "klick Sound" and i can push the Display Glass in a few millimeters. Its really annoying when im playing Games or writing a Text on it. Im not sure... a Friend of mine sent his TF300T to Asus too (nearly the same Problem) but didnt got it yet. What would you say?
But i have another little Problem if ill RMA it; I unlocked the Bootloader 2 Day ago via the official Asus unlock app. Is it possible to relock the bootloader and get my warranty back?
Best regards
I hope you can understand what i mean, but sorry im German and only 14 years old
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
ReMiXxXeD said:
Hey guys,
i got my TF300T now for about 4 Months. I already sent it back to asus once because my Touchscreen wasnt working correct. After i got it back my screen was okay again but all around it (not the Screen itself, the area around) is making noises. Just a little "klick Sound" and i can push the Display Glass in a few millimeters. Its really annoying when im playing Games or writing a Text on it. Im not sure... a Friend of mine sent his TF300T to Asus too (nearly the same Problem) but didnt got it yet. What would you say?
But i have another little Problem if ill RMA it; I unlocked the Bootloader 2 Day ago via the official Asus unlock app. Is it possible to relock the bootloader and get my warranty back?
Best regards
I hope you can understand what i mean, but sorry im German and only 14 years old
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Sounds like Asus had done a shoddy job repairing your touchscreen. According to a number of accounts recounted here, unlocking provides no means to relock the tab. That however, is the software part - technically unrelated to hardware - especially in light of the fact that your tab, still under warranty, had exhibited symptoms of a similar, if not the same, problem. If you decide to RMA it and encounter difficulty with Asus refusing to honor warranty, the argument would be that above, where locking or unlocking the device software-wise does not affect or create or aggravate the touchscreen issue in any way, shape, or form. Since the warranty also covers the hardware, Asus MUST take it back and fix it.
graphdarnell said:
Sounds like Asus had done a shoddy job repairing your touchscreen. According to a number of accounts recounted here, unlocking provides no means to relock the tab. That however, is the software part - technically unrelated to hardware - especially in light of the fact that your tab, still under warranty, had exhibited symptoms of a similar, if not the same, problem. If you decide to RMA it and encounter difficulty with Asus refusing to honor warranty, the argument would be that above, where locking or unlocking the device software-wise does not affect or create or aggravate the touchscreen issue in any way, shape, or form. Since the warranty also covers the hardware, Asus MUST take it back and fix it.
Click to expand...
Click to collapse
Alright! Thanks mate
Sent from my Nexus 4 using xda app-developers app
One thing to take note of is the "cannot unlock bootloader issue after rma"
pjc21 said:
Ok I had a search through several post on the "cannot unlock" issue after rma and found what I think is the issue if you registered your tab before an rma.
When you first register your tablet online with asus - information about your tab is sent to asus including your tab's MAC address for unlock & ota verification.
It seems that some (not all) tab's that come back after getting rma'd now have a different MAC address and so now when you run the unlock tool the tab's MAC address & the one registered with asus no longer match and cannot be veriferied so the unlock tool cannot proceed, same goes for ota's here.
If this is the case I have only found one solution which is to send it back to asus and tell them the problem is with ota & unlock.
(I assume here they reset your mac address to match what they have or vice versa)
The link aerdely posted also looks like a good way to go. It's from member "Asus_USA" from the US office who is trying to help those with this issue of not being able to unlock after rma by gathering a list of users /device info to send to HQ.
http://forum.xda-developers.com/showpost.php?p=40408537&postcount=567
Hopefully asus will be kind here and I think having your device info (serial & current mac address) they should be able to reset the mac address on there end to match your current one so you will not have to send in your device - not sure here
Hope this helps
Click to expand...
Click to collapse
agt7575 said:
Well, I called Asus customer service/tech support and told them about the problems I was having with the bootloader unlock app. Their response was as follows:
"Unlocking the bootloader can cause serious damage to your tablet, and is not something that Asus recommends. Therefore, we can not comment or support anything dealing with unlocking the bootloader as Asus does not want to become liable for for any damage done to anyone's tablet".
So basically, Asus has no problems supplying its customers with the unlock app, but every problem with supporting it... makes no seance to me.. ., "The first rule of fight club is you don't talk about fight club" lol
Click to expand...
Click to collapse
The warranty is taken as a whole: both hardware and software. Unlocking the bootloader voids the warranty, and it doesn't matter which part of the tablet is being fixed/serviced. There is a big disclaimer right when you unlock the tablet. If you unlock it and then have issues with the touchscreen down the line, we would not be able to help, unfortunately.
We provided the unlocking tool at the request of all the users. Because unlocking it opens the door for a lot of modification, and a lot of "unofficial" ROMs and such, we cannot cover the device if anything were to go wrong. It's not something we recommend, but we do understand that there are advanced users out there who know what they are doing and know the risks.
With that said, the OP does have grounds to get the RMA done. If there was an issue, and it was caused by the RMA, then we should be able to correct it for you. CALL in for the RMA and let them know the situation. The warranty is voided once the bootload is unlocked, but it's not always that cut and dry. Explain to them what was done on the previous RMA and what is happening now. They should be able to pull up the previous one and see that work was done to the display. Of course, if the issue at hand now doesn't match up to the previous RMA, then there might be an issue.
Asus_USA said:
The warranty is taken as a whole: both hardware and software. Unlocking the bootloader voids the warranty, and it doesn't matter which part of the tablet is being fixed/serviced. There is a big disclaimer right when you unlock the tablet. If you unlock it and then have issues with the touchscreen down the line, we would not be able to help, unfortunately.
We provided the unlocking tool at the request of all the users. Because unlocking it opens the door for a lot of modification, and a lot of "unofficial" ROMs and such, we cannot cover the device if anything were to go wrong. It's not something we recommend, but we do understand that there are advanced users out there who know what they are doing and know the risks.
With that said, the OP does have grounds to get the RMA done. If there was an issue, and it was caused by the RMA, then we should be able to correct it for you. CALL in for the RMA and let them know the situation. The warranty is voided once the bootload is unlocked, but it's not always that cut and dry. Explain to them what was done on the previous RMA and what is happening now. They should be able to pull up the previous one and see that work was done to the display. Of course, if the issue at hand now doesn't match up to the previous RMA, then there might be an issue.
Click to expand...
Click to collapse
f you're speaking as an authorized agent of Asus, I'd like to thank you for your effort to help users with defective tablets. Your position, however, that software and hardware are the same thing when it comes to warranty is not necessarily tenable in the eye of a US court unless you can prove on a case-by-case basis that a user's act is the cause of a faulty operation in the tab – software affecting hardware and vice-versa.
Your warning having a chilling effect on people trying to cash in on their legitimate rights is ill-advised at best, unless you're from Asus's legal department and intend to equate such claims with testimonies. Again, if you don't actually represent Asus's legal position, please refrain from making sweeping statements. Believe it, you don't want your opponent to recite these should you ever find yourself in the midst of a class action.
Asus_USA said:
The warranty is taken as a whole: both hardware and software. Unlocking the bootloader voids the warranty, and it doesn't matter which part of the tablet is being fixed/serviced. There is a big disclaimer right when you unlock the tablet. If you unlock it and then have issues with the touchscreen down the line, we would not be able to help, unfortunately.
We provided the unlocking tool at the request of all the users. Because unlocking it opens the door for a lot of modification, and a lot of "unofficial" ROMs and such, we cannot cover the device if anything were to go wrong. It's not something we recommend, but we do understand that there are advanced users out there who know what they are doing and know the risks.
With that said, the OP does have grounds to get the RMA done. If there was an issue, and it was caused by the RMA, then we should be able to correct it for you. CALL in for the RMA and let them know the situation. The warranty is voided once the bootload is unlocked, but it's not always that cut and dry. Explain to them what was done on the previous RMA and what is happening now. They should be able to pull up the previous one and see that work was done to the display. Of course, if the issue at hand now doesn't match up to the previous RMA, then there might be an issue.
Click to expand...
Click to collapse
Thanks for your answer. Are u an official Asus customer ?
@ the rest - is it possible to relock the bootloader ?
Sent from my Nexus 4 using xda app-developers app
Yes I work for Asus and i frequent these boards to see if I can offer an help or insight for our customers. In my post, I did not say the software and hardware is the same thing. I said the warranty is taken as a whole, which is true. We do not have a separate software warranty and a separate hardware warranty. When you unlock the bootloader, you forfeit the warranty. There is a disclaimer before you accept.
And really, it's not just us. If you open up any device, modify the hardware or software, or you break the seal, you void the warranty. This has been the case for a lot of manufacturers. For example, if you unlock a cellphone and the display goes out, that would void the warranty, even if the display has nothing to do with the phone being unlocked to be used with a different carrier. This is a fact because I used to work on the services side for a major US carrier. I understand every region has their own rules and policies so I can only speak the US. I think in the EU, everything that I am saying would not apply, although I could be wrong.
I also said that it is not as cut and dry, and we do take things on a case-by-case basis. With that said, the OP does have a case if they call in and explain the situation. If you want, OP, shoot me a PM if you're located in the US and let me see if I can help you because it's not possible to re-lock the bootloader.
My original intent was to give advice to ReMixxxed and to let him/her know that they are not "screwed" with this current situation. I can sit and cite policy all day long,but that's not what I'm here for. My intention is to try and help and I apologize if the post came across the wrong way.
Asus_USA said:
Yes I work for Asus and i frequent these boards to see if I can offer an help or insight for our customers. In my post, I did not say the software and hardware is the same thing. I said the warranty is taken as a whole, which is true. We do not have a separate software warranty and a separate hardware warranty. When you unlock the bootloader, you forfeit the warranty. There is a disclaimer before you accept.
And really, it's not just us. If you open up any device, modify the hardware or software, or you break the seal, you void the warranty. This has been the case for a lot of manufacturers. For example, if you unlock a cellphone and the display goes out, that would void the warranty, even if the display has nothing to do with the phone being unlocked to be used with a different carrier. This is a fact because I used to work on the services side for a major US carrier. I understand every region has their own rules and policies so I can only speak the US. I think in the EU, everything that I am saying would not apply, although I could be wrong.
I also said that it is not as cut and dry, and we do take things on a case-by-case basis. With that said, the OP does have a case if they call in and explain the situation. If you want, OP, shoot me a PM if you're located in the US and let me see if I can help you because it's not possible to re-lock the bootloader.
My original intent was to give advice to ReMixxxed and to let him/her know that they are not "screwed" with this current situation. I can sit and cite policy all day long,but that's not what I'm here for. My intention is to try and help and I apologize if the post came across the wrong way.
Click to expand...
Click to collapse
Thanks ! But now i have a even bigger Problem... The right corner of my screen isnt working anymore. Now i really have to rma. Is there no way to relock the tab ?
Sent from my Nexus 4 using xda app-developers app
No. What's done is done. ASUS has a permanent record of your unlock. Even if you could relock they would know.
Sent from my SCH-I510 using xda app-developers app
Asus RMA'd my tablet for a bad digitizer and fixed it free of charge despite it being unlocked. As previously stated, this is likely done on a case by case basis.
Just to be on the safe side, I did the following:
1. Rolled back to stock ROM just to be sure the issue was present using ASUS-issued software
2. clearly marked the places on the screen that were acting up to be sure a tech could reproduce
3. Included, in the RMA, that the tablet was unlocked but that I perceived this to be a hardware issue, not affected by unlocking.
So, there isn't much to lose by contacting them and/or sending the thing in (except for the cost of shipping). One thing to note, however, is that the problem has returned for me and that my tablet is now beyond the one year warranty. It's unfortunate as I'm more than happy with it.
Good luck.
Okay. Thank you very much, i think ill send it back to them tomorrow.
Sent from my Nexus 4 using xda app-developers app
Hello,
I'm involved in trying to collect information regarding Knox, the illegal destruction of private property and possibility to run unknown code and I badly
looking certain configurations to get more answers.
If someone has root, not tripped Knox and preferably SELinux set to "Enforcing", please send me a message! Your help is needed!
I was too late. The "Rules update #16" that blocked "Root de la Vega" was pushed to my phone against my will. Other got it as well.
That means they already have some form of control and disregard your configuration. What can they do more?
With an SELinux they can control your device as they wish if they configure it to hide processes that run, as of today, unknown code.
I'm an "BOFH Unix kick ass consultant" by trade. I know how nicely you can do this. "Living in a box". Oh yes.
This is about our future, the right for privacy and the right to do what we want with out own private property!
The extreme measures taken against just obtaining root are disproportionately harsh. If they succeed, others will follow.
We might end up with iNdroid in a few years. I want to prevent that. But we need more knowledge. They destroy evidence if you trip Knox.
Rooting is not illegal, but the active action of destroying someones property with indent is, whatever cause, warranty claims or not.
There will be consequences. But we need more information, and you who have a Note 3, just as me, can help. The key can be your phone.
Knox is not "just a flag". It have attached code. It sabotages your system both software and hardware. Scrambled software. Wifi permanently
damaged, to name a few. I know, from my S4, and have it verified from source. But that code is run once and then gone. Are there more E-fuses?
Dumping hardware has made at least one device totally bricked. Not even the Power button worked. It was stone-dead.
Also:
If someone has a way of obtaining it without tripping Knox please contact me. I'm willing to take the risk of tripping Knox since this is more important then
some warranty.
I've been working in this for two months now and the more I learn the more I start to question if this isn't a bad movie with Kevin Costner...
No opt-out. Enforcement of this "Enterprise" solution. On your private phone? Think! The money this must cost? You want a return of investment!
Rooted phones cost that much? I don't buy that. You have an unique certificate that binds YOU to your phone. You and your phone are bound as one.
What if 3rd-party malicious code get hands of that? Viruses exist, even on Play. But your Antivirus can't run because it can't access the parts it must have
higher right to read check your programs. I rather run a firewall and deny permissions of programs that want way too much.
A "file manager" doesn't need to read your contacts. A game doesn't need to use your camera. But you can't prevent that.
Knox prevents that. Because you can place a document in a container... I rather use my freeware AES-program that encrypt documents on the fly.
Until we know more the device should be considered as not safe. Why is Samsung stonewalling the question so many have asked?
"What is the extent of the damage made?". I think we have the right to now that, don't you? Many has tried. "Heavy damage" is so far the best we got.
So please, if you still have root and not a crippled device, please contact me. Your help is the only way I see is possible right now.
All the best,
Abs (Yes, I need to update my tag, since I have so much new)
Hi. I've root, not tripped knox and with selinux set to enforcing.
Enviado desde mi SM-N9005 mediante Tapatalk
Absolon said:
Hello,
I'm involved in trying to collect information regarding Knox, the illegal destruction of private property and possibility to run unknown code and I badly
looking certain configurations to get more answers.
...
I was too late. The "Rules update #16" that blocked "Root de la Vega" was pushed to my phone against my will.
...
Click to expand...
Click to collapse
Sorry, if you missed the incredibly obvious checkbox in Settings / Security = Auto update security you really don't look like the right person to trust with full root access on my phone.
xclub_101 said:
Sorry, if you missed the incredibly obvious checkbox in Settings / Security = Auto update security you really don't look like the right person to trust with full root access on my phone.
Click to expand...
Click to collapse
It got pushed about the moment I turned on my phone the first time. So as I said. I missed the opportunity
But thank those who instead of making sarcastic comments, already sent a message and offered help instead. :good:
I'm sure that the large group who got their phones destroyed really value you and your opinion, Xblub
But be careful so you don't trip it. You would not believe how easy that is!
Would be sad if you also got your phone devastated by the unkindly spirits at Samsung.
Let's hope we find a solution before that happens, right?
And please, if more want to help out please mess me, there are so many who got their phones destroyed and Samsung will not stop itself.
It will only be worse. But you can help stop this while we still have a change.
Next phones will have Knox chipped and then even Xblub will be sad
/Abs
Edit: Of course I meant Xclub.
As noted, easy to make a mistake. Like wanting Xclub to write "ls" when I really meant he should run
#!/bin/bash
//usr/bin/tail -n +2 $0 | g++ -o main -x c++ - && ./main && rm main && exit
main(_){_^448&&main(-~_);putchar(--_%64?32|-~7[__TIME__-_/8%8][">'txiZ^(~z?"-48]>>";;;====~$::199"[_*2&8|_/64]/(_&2?1:8)%8&1:10);} (Please don't run it!)
Ahh @Absolon, Was wondering where you had gotten too.
To be honest, I just tripped mine soon as I got it. removed the Stock ROM and just went custom. However... What I have noticed is knox.eventsmanager runs regardless of ROM and IF KNOX is uninstalled.. So probably running /hiding somewhere in the bootloader (at a guess anyway)..
All this KNOX talk is getting complicated now, it's a 50-50 split I think with people tripping/keeping it. - Samsung have forced it upon us, and unless we custom flash (and lose warranty in parts of the world) we are screwed.
radicalisto said:
Ahh @Absolon, Was wondering where you had gotten too.
To be honest, I just tripped mine soon as I got it. removed the Stock ROM and just went custom. However... What I have noticed is knox.eventsmanager runs regardless of ROM and IF KNOX is uninstalled.. So probably running /hiding somewhere in the bootloader (at a guess anyway)..
All this KNOX talk is getting complicated now, it's a 50-50 split I think with people tripping/keeping it. - Samsung have forced it upon us, and unless we custom flash (and lose warranty in parts of the world) we are screwed.
Click to expand...
Click to collapse
I have not touched the Note 3 yet, but I tripped the S4 when they sneaked it in. My Wifi works though, Like a Us Robotics 56K modem, but well..
So what did you experience? I just got the reports from the S4.
The problem of tripping or not tripping is not if this would be a flag because it's not. It's a lot more and I have it confirmed.
But since I can't obtain root without tripping Knox on my Note 3 right now I won't do it until the holidays are over and then claim hardware warranty
and let that play itself out.
But pray tell, after you broke Knox. What did you notice? Still have that sticky bootloader? Any Wifi, gfx, other issues? Any issues with
programs that got removed or that Play stopped working?
All info is needed and I really need constructive people here. I don't need access to someones phone. But I need to collect things.
So even if you can't Android or the SEL that I'm after I can guide through. So let's stop this before we have it in a nice chip next year?
Doesn't that sound like a really good plan?
/Absie
Absolon said:
I have not touched the Note 3 yet, but I tripped the S4 when they sneaked it in. My Wifi works though, Like a Us Robotics 56K modem, but well..
So what did you experience? I just got the reports from the S4.
The problem of tripping or not tripping is not if this would be a flag because it's not. It's a lot more and I have it confirmed.
But since I can't obtain root without tripping Knox on my Note 3 right now I won't do it until the holidays are over and then claim hardware warranty
and let that play itself out.
But pray tell, after you broke Knox. What did you notice? Still have that sticky bootloader? Any Wifi, gfx, other issues? Any issues with
programs that got removed or that Play stopped working?
Click to expand...
Click to collapse
I don't think you can tell the difference once Knox is tripped. The only obvious thing that sticks out is you have more RAM/HDD available and the phone feels slightly faster. As for Play and Apps not working, I am yet to see any issues (only play issues I have ever had have been No connection, when there clearly is one. After a few refreshes it loads up. Now bear in mind, My connection isn't weak, I've been on the internet via the browser or on an app when I have switched to Play and experienced this) - Not to mention a stupid notification yapping at us telling us we are wrong to use something on a phone we legally own.
Absolon said:
All info is needed and I really need constructive people here. I don't need access to someones phone. But I need to collect things.
So even if you can't Android or the SEL that I'm after I can guide through. So let's stop this before we have it in a nice chip next year?
Doesn't that sound like a really good plan?
/Absie
Click to expand...
Click to collapse
Aww I dread to even think what Samsung will enforce on us next time. There should be an option when you purchase the phone, if you're gonna use it for corporate use, then have KNOX installed via a code they print out. - But to us the everyday user. All it's doing is
*Taking up space on OUR phones
*Running cheekily in the BG
*As you stated, banning access to certain parts of the phone, which IF exploited, our AV's etc cannot reach.
To say we (well most of us) live in a free world, when it comes to us being consumers... they like to shaft us several times over.
Absolon said:
If someone has root, not tripped Knox and preferably SELinux set to "Enforcing", please send me a message! Your help is needed!
Click to expand...
Click to collapse
I feel your frustration. I would much rather an open hardware platform with none of this KNOX business. It's starting to get ridiculous...
It sounds like you've already got help, however I too have an un-tripped KNOX, w/ SELinux enforcing and would be happy to help out.
lispnik said:
I feel your frustration. I would much rather an open hardware platform with none of this KNOX business. It's starting to get ridiculous...
It sounds like you've already got help, however I too have an un-tripped KNOX, w/ SELinux enforcing and would be happy to help out.
Click to expand...
Click to collapse
Not all have the same configurations and not all have the same level of knowledge. But that is not a problem.
As I said. I don't want into your phone, I want you to collect info. So I gladly take any help I can get. Send me a private message.
Because I need as many as possible to verify things. Don't be shy! I don't bite. That hard
Destruction of data INSIDE the knox container after gaining root (which is a vulnerability in itself) is not data manipulation of any sort.
Tripping the counter will just void your warranty (as you would expect anyway!) and disable the knox container completely - it will NOT cause any other issue whatsoever to your device.
The System Security Policy service resets with a factory reset (so you can now go to the security tab and disable auto update).
Security Policy blocks known vulnerabilities that can give access to unauthorised root permissions and potential malware attacks.
Knox as a container can be opted out by uninstalling the knox application.
Knox as a counter is an integrated security measure and in no way should you ever be able to turn it off.
Security Policy is an active security system and you should not have the option to turn it off - you can prevent updates to the policy however.
Tripping the counter will not cause any hardware/software damage (!! An E-FUSE triggering is not damage, it's doing the job it is designed to do in case of compromising the system !!) - it will prevent you from using the knox container which is no longer safe after root and prevent you from getting warranty because you void it by rooting since the middle ages anyway - WiFi issues, dead devices and whatnot are not related in any way as most N3 users here are already using the device with knox tripped.
If you want root privileges you automatically lose your warranty and access to knox, nothing more nothing less.
PS: Update 16 blocked kingoapproot and vroot (which are technically malware), not root de la vega, the new bootloader blocked root de la vega because it's an exploit to gain root.
Absolon said:
...
The problem of tripping or not tripping is not if this would be a flag because it's not. It's a lot more and I have it confirmed.
But since I can't obtain root without tripping Knox on my Note 3 right now I won't do it until the holidays are over and then claim hardware warranty
and let that play itself out.
...
Click to expand...
Click to collapse
While the first line falls close to what a conspiracy theorist would say the second one is an interesting point where more attention would be useful.
It can be argued that in the context of EU law the HARDWARE warranty is different than the SOFTWARE warranty, and that a manufacturer can not evade providing the first.
The thing is - to the best of my knowledge Samsung has never (so far) denied HARDWARE warranty based on knox flag status - so in that regard you might have a starting point in case you want to set some precedent - and I would LOVE such a precedent to be set (in a way that protects the consumer)!
Other than that all the stuff on how knox is used by Samsung to spy on you and follow your every move is really not helping anybody's cause (except maybe Samsung's).
My final point on this matter is that people with a LOT more technical knowledge on the subject than Absolon here (people like Chainfire or AndreiLux and plenty other) have commented on this, so people should really learn more about the subject before starting the wrong crusade born out of conspiracy theories. Don't get me wrong - I WANT my consumer freedom, but I would also like that when legal precedents are set on the subject to have them set the right way, for the right reasons and with the right evidence (which will not be destroyed in court by Samsung lawyers in a day or less).
I'm following a good advice and removing any further comments.
I really want to work in a constructive manner and I do not with to petty fight. So please.
If anyone else want to help explore, please message me. We are on different levels of knowledge but that is all what XDA is about. To learn and to help!
All the best,
Abs
If I trip KNOX and my phone will need a repair will this work?
[INFO][EU] Rooting and Flashing don't void the warranty
EdisDee said:
If I trip KNOX and my phone will need a repair will this work?
[INFO][EU] Rooting and Flashing don't void the warranty
Click to expand...
Click to collapse
As said, there are different views. Skander has one experience and that can be for one version.
For the I9505 the Knox did cause damage to the hardware and I did collect reports of findings and the majority was Wifi,
If this is the same for Note 3 I don't know. I write that I know, and what I think. We have free speech and I can have my thoughts and so can others.
It's rudeness and bluntness that should be avoided and I know that irony sometimes doesn't do as well on paper as in real life, but believe me, irony is the only thing that keeps me alive now days ;P
So when turning on a GN3 for the first time immediately disable updates before you DL the bad firmware/bootloaders?
Edbert said:
So when turning on a GN3 for the first time immediately disable updates before you DL the bad firmware/bootloaders?
Click to expand...
Click to collapse
On ANY MODERN PHONE (if possible - for instance you will not be able to do that on any iphone) you should:
- start the phone once without any SIM card and without entering/activating any form of WiFi - this will guarantee that your phone will not connect first to the Internet
- check/set any relevant settings regarding security and software updates - for instance on Note 3 those are two separate settings, and the security one seems to be activated "by default"; currently the firmware update is not really activated "by default" since it WILL ask you pick a country and agree to some EULA
- either way, once you have disabled things (I also disable mobile data at this point) you can then power-off and insert your SIM, then enable WiFi and do whatever else you want to do.
I am not saying that it is "normal" to be this way, but since it is then you better be prepared for it!
Tripping knox won't break your WiFi or anything on the Note 3.
If you break it yourself by messing with it that's another thing.
Do keep in mind that your warranty is void by rooting but this depends on the seller or carrier.
Skander1998 said:
Tripping knox won't break your WiFi or anything on the Note 3.
If you break it yourself by messing with it that's another thing.
Do keep in mind that your warranty is void by rooting but this depends on the seller or carrier.
Click to expand...
Click to collapse
Abit ridiculous though. Why they would want to avoid advance users like us to root our phones? Knox was implemented for corporate user or uses. But they jolly well know most of their customers are average users which are not completely working on highest intel in any agencies which require knox to be used. Their marketing strategy failed to the max. Focusing knox on both the corporate users and normal users. Secondly knox to them is both a security measures and a so called warranty tracker. By warranty rooting as does damage your phone software but not hardware unless extreme cases whereby people oc'd their phone to be rocket-ed out of their pockets. Hmm. Rarely i've heard root causes phone to be burnt or caused a crack to the screen or buttons alignment.
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 05:46 AM ---------- Previous post was at 05:39 AM ----------
MxFadzil92 said:
Abit ridiculous though. Why they would want to avoid advance users like us to root our phones? Knox was implemented for corporate user or uses. But they jolly well know most of their customers are average users which are not completely working on highest intel in any agencies which require knox to be used. Their marketing strategy failed to the max. Focusing knox on both the corporate users and normal users. Secondly knox to them is both a security measures and a so called warranty tracker. By warranty rooting does damage your phone software changing of roms baseband kernel etc but still baseband all those stuff are still needed by the original manufacturer release not by cyanogemod for example new baseband are aquired by new tw rom new builds except for kernels which are aquired by githubs made by respective developers... But not hardware unless extreme cases whereby people oc'd their phone to be rocket-ed out of their pockets. Hmm. Rarely i've heard root causes phone to be burnt or caused a crack to the screen or buttons alignment. Rooting are the only way for us to try a new android platform build release by google... To wait for manufacturer release maaan could be months down the road. Sigh.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N9005 using XDA Premium 4 mobile app
MxFadzil92 said:
.too long.
Click to expand...
Click to collapse
They do not stop you from rooting, they just re-affirm the million year old knowledge that rooting voids your warranty!
Bricking smartphones from rooting is very common, so does flashing kernels and whatnot, flashing kernels can actually allow someone to cause actual hardware damage to antennas, CPU's and GPU's and even kill the screen (in the note 2 for example, flashing an s3 recovery will burn the digitizer permanently)
Rooting also invalidates Knox's security completely, and any data there should be protected so they make it self destruct (the container) when rooted and the flag is there so after unrooting (and potentially having a still infected system) no one can activate a container anymore on the Smartphone.
This has side effects like the inability to root without detection, but the regular users you are talking about will not root their devices and so is 90+% of the users.
Knox is not an issue and nothing new, flashing anything from 2010 on any device voids your warranty, now it voids it with a permanent marker so you can't fool them and technically illegally get a repair from a broken warranty.
You break warranty terms even one of them, you don't get it.
xclub_101 said:
On ANY MODERN PHONE (if possible - for instance you will not be able to do that on any iphone) you should:
- start the phone once without any SIM card and without entering/activating any form of WiFi - this will guarantee that your phone will not connect first to the Internet
- check/set any relevant settings regarding security and software updates - for instance on Note 3 those are two separate settings, and the security one seems to be activated "by default"; currently the firmware update is not really activated "by default" since it WILL ask you pick a country and agree to some EULA
- either way, once you have disabled things (I also disable mobile data at this point) you can then power-off and insert your SIM, then enable WiFi and do whatever else you want to do.
I am not saying that it is "normal" to be this way, but since it is then you better be prepared for it!
Click to expand...
Click to collapse
And with a company that does fair play you don't have to worry that they push something you don't want on your phone.
And they do. Don't be too sure that just because you turned your settings off that it protects you, because if you read through posts you will see that people got updates pushed, disregarding whatever setting you had. And that is certainly not fair play
But to answer your question. First. Just dropping names here and there doesn't do it. To ride on someones "fame" to gain more authority and merit to your post is bad rhetoric.
You should be able to do that on your own.
Yes, there are many who are way better then me, but the nice thing is that when you asked them, they know they once been there themselves and don't feel the need to project personal problems and anger on some random person they never met.
Just that we passed the 100 post mark and XDA automatically put a "senoir" next to the name means nothing more then we are good at bull****ting online,
Doesn't tell if you are 1337 or a n00b. Even if you post 10000 post doesn't mean that you have any deeper understanding.
But new users don't know that, and treating others without respect scares them away. Makes them afraid to ask. Who wants a snotty answer back on their first post?
So please. Make this a constructive place. If you are angry I recommend Reddit/Imgur/Flashback. There you can project whatever you want or need.
I don't know how to code a single line in Java!
But I'm awesome in C64 Basic!! And I managed to write "Hello World" in BF!
And I know several Asm's and I coded mostly in C (and C++ when it was still readable) and did my VHDL/Erlang-hell period (and I tested like 20++ other languages, some enforced during my master but some just for fun. I can write "Hello World!" in Sun's start eeprom!) but that was looong time ago. So I'm "rusty". Old. There are so many nifty new things. But then. Mostly I use something invented 200 years ago - A stethoscope. But there is a new COOL one! BT! With noise reduction and spectrum analysis! No more things that hurt in my ears! For the little sum of 1500 € it's yours!..... Bleh.
But I'm not ashamed of that! I can learn if I want. XDA is a great place for that. Even have their own Android University!
I'm fairly good with Unix. Even made money of it. For over 8 years. And the good with that is that some things we still use today haven't changed since 1973!
And I worked some with hardware but I need a new JTAG. Know a good one? So many to choose and I don't know the quality or what is needed?
Do the board even have pins or do you have to weld them? I hate welding!
You say conspiracy. I say concern and worry.
Why are people starting to get worried?
It's not as much as conspiracy then more why they are behaving like they do?
The fact is simple - the unknown
The word SELinux has come to more people now since it's mandatory in 4.3. The "moblie magazines", M3, Android** talks about the "news in 4.3".
But what is SELInux?
So people turn to the trusty Wikipedia for answers: Wikipedia - SELinux
And the first lines they see are
Security-Enhanced Linux (SELinux) is a Linux kernel security module that provides the mechanism for supporting access control security
policies, including United States Department of Defense-style mandatory access controls (MAC).
SELinux is a set of kernel modifications and user-space tools that can be added to various Linux distributions. Its architecture strives to
separate enforcement of security decisions from the security policy itself and streamlines the volume of software charged with security
policy enforcement.[1][2]
The key concepts underlying SELinux can be traced to several earlier projects by the United States National Security Agency.
Click to expand...
Click to collapse
That is what people see!!
I can bet some even read "police" and not "policies". The see all this and that SCARES THEM.
With the recent scandals in mind of NSA hacking everything including the Germans Chancellors phone, an alley??
And here, the American spy-outpost towards Sovjet/Russia since 1947. We have also a 3-letter agency. And not many weeks ago there where front pages that they shared the databases with each other. So is that so hard to understand?
So to get from the unknowns they start to look
So you turn to Samsung for answers, And they treat you like cattle. And they stonewall you? No transparency whatsoever.
They reminds me of Nokia when they also went into "grandiose mode" and also through they could do whatever they please because of their total dominance. But they forgot one thing. The consumers got more and more unhappy. And they was their sole income. And when get got that in their heads it was too late. What are they now? Decimated to nothing. Trying desperately with a yet another attempt by Microsoft that is deemed to fail. How many times have Microsoft tried to get in on the hand-held market? I lost count.
And then they start to Google. XDA turns up like the first thing. Find their phone and see "Knox?"
(SELinux==NSA) --> Enterprise solution? On my private phone? Encryption? Damage? Container? What do I need THAT for?
"I don't want THAT on my phone! NSA. Enterprise. Container? Where is the opt out? There are none? I was NOT informed of this!"
That is what I find that worrying and I share that with many others.
Yes, some say it's just a flag. Not on S4. Look how many got problem with Wifi. I got them as well. And I knew when I broke my Knox.
Since SS goes all this trouble to hinder you to gain root access that they even had an E-fuse that does cause hardware damage.
To prevent "Triangle Away"? As your friend if he believes it's because of that?
I don't have to use SELinux to run code past your nose, root or not, but SELinux does it so much easier, since you can define it do hide processes from normal users and it has the possibility to run 3rd-party code. You know that, right?
Since we don't know what is run on the phone you can't be sure it's not something with some intent? So why not investigate it? What is going on in the phone?
Aren't you curious? I am. I would love to be able to root? Can I after #16 on MJ7?
But sure ask them, please. Give it a try
Ask them for example why Wifi stopped working after Knox was tripped on your S4?
Ask them what the extent of the damage they have done?
Ask them where this "Efuse data" is, on what address-range so you can avoid it? Data for a flag? Wasn't that just burned in?
Ask them why you can't update with Kies anymore? Wasn't that just a flag?
Ask them anything.
And I'm sure you will get a message back (if you get any) from "Steve". The poor overworked guy that serves the whole world and he always seems to write the same? We compared. He sits and write the same text over and over? "Sorry, we can't divulge this information at the moment".
Poor Steve!
Come back to the mother-continent! I promise, we've stopped flogging, guillotine, quartering and we changed the stake for a steak!
We have much more fun! 6 weeks of full paid vacation. Here in Sweden we have Polar bears! While we sit in our igloos and make watches.
And we have better beer as well!
If you see turning of a setting as a merit I think you should add that to your CV (and I was not alone in this).
I did as 99% of all do. Unpack the phone. Skip the instruction. Put in the sim and the sd-card and then turn it on.
BAM! I don't even think I had the time to enter my Gmail?
But you didn't. Great!
Here your knowledge would be useful! Help your fellow XDA members. In the spirit of XDA!
Can you dump the phone? Not block-wise but by reading the whole contact of the eeproms?
Can you compare your fstab and it sizes? Do they correspond to the space you have? If you dump them and compare it to the first, Do the differ much is size (a bit is natural)?
Can you use parted and list the partitions? Are all mounted? What rights do they have? Can you read them all?
The security policies in /system. What do they contain? See anything strange?
Can you compare what processes you see as a user and root?
Can you list the rules loaded in the kernel? MAC? (I think you need to compile the commands for it or get it from some Arm dist, they are not included)
Strace some processes that you don't recognize?
The kcryptd? What do they work against?
What files are open and locked? What does the stat say?
See kvm? Or are you in a kvm?
Here you can actually ACT and DO something constructive and concrete or is this just, as from my compressor, high pressured air comming from your side?
Time will tell I guess.
For the others that have messaged me: A BIG BIG THANK YOU!
And no, I don't have enough volunteers, if you do have this configuration, mess me. Or test sometime from test list. The dumping should be used by experienced users but you can do a lot on that list and you can zip and sent me some files. Rules, Pipe out the process lists.
I don't care how much you can or can't. Ask away! We started at the beginning somewhere and I will do my best, ask around, and TOGETHER, we might get some result, because we want to DO something and maybe we CAN help right? Either we find something or we don't. If we are sure and can say "The system seems clean". That would calm a LOT people down. Including me.
/Abs
And with this I won't go into more arguments about this. It's enough. I saw this as an excellent solution to see and check. Not to argue.
I already lost too much time on bla bla bla. I want to spend the time I have on things that matter. My friends that have their phones destroyed.
Use the list or make another! All seem to have their own experiences/views. Samsung must love this division.
Just DO something! Like in all research: Stipulate, challenge, prove, disprove, confirm, dismiss. Start over.
If you need to vent, you can PM me as well, Xblub.
Deleted...
Leaving Verizon.
Sharpie603 said:
Recently Verizon has shown their true colors. They do NOT want to give us control of a device that we bought and paid for. (That's like buying a radio that only plays Country).
In my eyes. If we pay you monthly then why do you care what we do with our device? We own it right?
However, after days of researching and very knowledgeable co-workers..... The solution is here.
ODIN 3.10. That's Correct. ODIN 3.10 has the ability to look past the locked bootloader and grant access to roll back. This was not made to be public but (Thank GOD) was leaked on Aug 26th.
You can download ODIN 3.10 here: http://www.theandroidsoul.com/download/download-odin-3-10-6/
I have not yet tried to root after rolling back to the BOA8 Kernel. Anyone want to test this out and let me know if you were able to root after downgrading?
Click to expand...
Click to collapse
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?
scadilla said:
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?
Click to expand...
Click to collapse
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
I'm definitely following this thread!!! Thanks for the info Sharpie603!!! Man... I really hope you're successful!!! I'm ROOTing for you! (Pun intended! Damn I'm funny! No?!?! Anyone???) LOL
Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.
scadilla said:
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.
Click to expand...
Click to collapse
Not looking very promising.
Can you downgrade APNHLOS?
Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.
In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.
Spartan117H3 said:
Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.
Click to expand...
Click to collapse
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...
KennyG123 said:
In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.
Click to expand...
Click to collapse
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Sharpie603 said:
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...
Click to expand...
Click to collapse
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265
Spartan117H3 said:
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265
Click to expand...
Click to collapse
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck
Sharpie603 said:
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck
Click to expand...
Click to collapse
The problem is, you just assume things without actually comprehending what people say. That's why you believe this is apparently a war. Ream you out? You miss the entire point, repeatedly. All it is is people telling you why your statements don't make any sense.
Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
As stated that is just YOU. 99.9% of people do not want their phone hacked or their identity stolen.
How is stating the facts slander? And I think I would know best what is encouraged here and what isn't. Now you are just lashing out for no reason and making no sense.
I guess we can close this as you wished. Thanks for trying.
Sorry if this question has been answered already, but I haven't found a recent (ie within a year) thread about this when I searched. I haven't rooted anything in years and I've just got a Galaxy Tab Pro and was looking into Rooting it. My friend who has an HTC One has also reached out to me asking me how to Root it.
When I started researching methods I kept running across articles that were stating that Rooting a device is now illegal? I've never heard of this before, is it true? Anyone have links to information that says otherwise?
No it's not but In most cases it will void your warranty. also most of the time you could always unroot your device. I used KingRoot to root my phone it's an app it was quick and simple.
Sent from my BLU STUDIO 7.0 II using XDA Free mobile app
It depends what you do with root. If you root it to "hack" or "snif" then you're doing a illegal thing. If you root it to costumise your Android then, you're not disturbing a privacy from another person or what else.
Hit the Thanks Button if I helped
You bought and own it. You can do what you like with it. Of course if it's a stolen phone and you're rooting it to mess with the IMEI, then that's another matter.
Does anyone have links to articles or information confirming this? Because all I can find are articles stating that it is illegal with the 2nd article below stating that "Tablets cannot be Rooted AT ALL" (*edit: apparently I can't post links yet)
godzillinois said:
Does anyone have links to articles or information confirming this? Because all I can find are articles stating that it is illegal with the 2nd article below stating that "Tablets cannot be Rooted AT ALL" (*edit: apparently I can't post links yet)
Click to expand...
Click to collapse
I don't know what you have been reading, but it's wrong. Root is perfectly legal. My Nexus 7 and Nexus 9 are both rooted.
Where are you getting this information? That part of the internet should just go ahead and die.
well like I said, I can't post links yet because I'm still 'new' but if you just Google Root and Illegal a bunch of articles come up (some contradicting the others, which is why I was looking for a definitive answer from somewhere.)
godzillinois said:
well like I said, I can't post links yet because I'm still 'new' but if you just Google Root and Illegal a bunch of articles come up (some contradicting the others, which is why I was looking for a definitive answer from somewhere.)
Click to expand...
Click to collapse
I think you don't quite get how search engines (google) works: you can google illegal and pineapples, and get a bunch of articles.
The only issue with rooting would be that it breaks/voids warranty in most cases, and if your device was obtained on contract i.e. still technically the property of your provider, then rooting might be against the terms of service - the consequence of which varying depending on the provider.
HypoTurtle said:
I think you don't quite get how search engines (google) works: you can google illegal and pineapples, and get a bunch of articles.
The only issue with rooting would be that it breaks/voids warranty in most cases, and if your device was obtained on contract i.e. still technically the property of your provider, then rooting might be against the terms of service - the consequence of which varying depending on the provider.
Click to expand...
Click to collapse
I wasn't searching for it outright, I was actually searching for the pros and cons of rooting since my buddy was interested, and a couple of the articles I kept running into kept mentioning the illegality part. Since I can't post links I just suggested that one Google Root and Illegal since someone actually asked where I got my information. I figured it would be easier than explaining all this and then telling him to Google "Pros and Cons."
Obviously I know how a search engine works, no need for the passive aggressive comments - especially when you provide no other help than what was already said.
godzillinois said:
I wasn't searching for it outright, I was actually searching for the pros and cons of rooting since my buddy was interested, and a couple of the articles I kept running into kept mentioning the illegality part. Since I can't post links I just suggested that one Google Root and Illegal since someone actually asked where I got my information. I figured it would be easier than explaining all this and then telling him to Google "Pros and Cons."
Obviously I know how a search engine works, no need for the passive aggressive comments - especially when you provide no other help than what was already said.
Click to expand...
Click to collapse
Sorry, wasn't meaning to sound that way, but your question is rather vague as there isn't one universal global law system - although arguably there should be for digital matters.
To fully answer there are several parts to look at; primarily does it violate local laws - in some cases it can be argued that it breaks copyright law. Additionally you need to question on if the 'broken law' is inforcable - inmost cases it is not and the said laws were made in a pre-digital age and haven't been updated to account for the current world. As an example - setting the wrong age (or a fake profile) on FB is technically illegal as it's against the TOS which is a legal document; but the proseccution of these lawbreakers isn't feasible or inforcable.
Although as i stated previously - this can be slightly different if the device isn't wholely owned by the user i.e. the device cost was covered by the network provider and essentially loaned to the user until the contract is over.
Fair enough - sorry to jump on you, so I guess to be more specific I was looking into the legality of Rooting devices that are out of contract in the US/Illinois. My friend's phone is older than 2 years well past his contract, and I bought a refurbished Wifi-only Galaxy Tab Pro which seems is stuck on Kit Kat for now.
I'm mainly looking to Root to turn off my back button and gain write access to my external SD card (as well as remove bloat) but the Wifi-tether I was finding in articles seems intriguing. Although that seems like if anything that came from Rooting would be illegal that would be it (and bootlegging paid apps of course.)
godzillinois said:
Fair enough - sorry to jump on you, so I guess to be more specific I was looking into the legality of Rooting devices that are out of contract in the US/Illinois. My friend's phone is older than 2 years well past his contract, and I bought a refurbished Wifi-only Galaxy Tab Pro which seems is stuck on Kit Kat for now.
I'm mainly looking to Root to turn off my back button and gain write access to my external SD card (as well as remove bloat) but the Wifi-tether I was finding in articles seems intriguing. Although that seems like if anything that came from Rooting would be illegal that would be it (and bootlegging paid apps of course.)
Click to expand...
Click to collapse
You can easily bootleg paid apps without root, so don't think that rooting is opening up the phone to the "dark side" of Android.
Rooting devices is not illegal anywhere in the US. It does, however, void your warranty and if you were to trade in the device for credit towards a new one they will likely not take it and force you to pay the difference.
But if you own the device outright (not on contract or paid full price), it is yours and you can do anything you like with it. You can root it, you can smash it with a hammer, or you can bake it into a cake. The possibilities are endless.
Even if you don't "own it" outright yet (i.e. are on a 2 year contract or pay monthly installments) you can still modify the device in any way as long as you finish your contract/agreement.
As long as you don't use root access to do illegal things, it's perfectly fine. Root itself is harmless.
LMFAO.... All I asked for was a system image. Essential phone is using XDA as their forums? I didn't know they had business ties with XDA. A moderator should check on this.
Erich T (Essential Products)
Nov 3, 6:07 AM PDT
Hi Shawn,
This is not something that we can assist with and a replacement will not be offered.
I had seen a forum posting you made yesterday where you had admitted to sending an ADB command that had potentially bricked your device. I had specifically asked you if you had done this in my previous email, and you had replied that you had not.
As you are probably aware, ADB is used at your own risk and your warranty is void if it causes the device to not boot correctly. Here is the applicable terms in your warranty:
This Limited Warranty does not apply to the following:
(g) defects or damage resulting from testing, operation, installation, alteration, adjustment, or disassembly not approved by EP, including but not limited to installation of unauthorized software and unauthorized root access (including jailbreaking)
You can view our full warranty terms here
From the forum post, it looks like you were able to recover the device, so hopefully you are all set. Enjoy your weekend.
Sincerely,
Erich
Essential Customer Experience Team
Atlantian said:
LMFAO.... All I asked for was a system image. Essential phone is using XDA as their forums? I didn't know they had business ties with XDA. A moderator should check on this.
Erich T (Essential Products)
Nov 3, 6:07 AM PDT
Hi Shawn,
This is not something that we can assist with and a replacement will not be offered.
I had seen a forum posting you made yesterday where you had admitted to sending an ADB command that had potentially bricked your device. I had specifically asked you if you had done this in my previous email, and you had replied that you had not.
As you are probably aware, ADB is used at your own risk and your warranty is void if it causes the device to not boot correctly. Here is the applicable terms in your warranty:
This Limited Warranty does not apply to the following:
(g) defects or damage resulting from testing, operation, installation, alteration, adjustment, or disassembly not approved by EP, including but not limited to installation of unauthorized software and unauthorized root access (including jailbreaking)
You can view our full warranty terms here
From the forum post, it looks like you were able to recover the device, so hopefully you are all set. Enjoy your weekend.
Sincerely,
Erich
Essential Customer Experience Team
Click to expand...
Click to collapse
Kudos to Essential tech support for doing their homework. Most companies I know would kill for people that good! Sure doesn't look like they're implying any business ties with XDA from that email.
Glad I gave my money to a great company. Warrantees are not "get a new phone whenever you want". They cover manufacturing defects. You obviously don't have a manufacturing defect and you got caught. Pretty embarrassing for you.
Well, good. If they're reading this, RELEASE THE FREAKIN' IMAGE FILES YOU SAID YOU WERE GOING TO RELEASE!
xxBrun0xx said:
Kudos to Essential tech support for doing their homework. Most companies I know would kill for people that good! Sure doesn't look like they're implying any business ties with XDA from that email.
Glad I gave my money to a great company. Warrantees are not "get a new phone whenever you want". They cover manufacturing defects. You obviously don't have a manufacturing defect and you got caught. Pretty embarrassing for you.
Click to expand...
Click to collapse
It's ok. I just returned it. Not my fault that they have no software support. Bought myself a pixel 2 XL. Yawn... Enjoy having no software system images. I was hoping they would have been the next one plus. Looks like just another HTC, samsung and apple.
Atlantian said:
Just sent this to Essential phone.
Sorry. And what forums are you referring to? Also, did you cross-reference my personal information to another website? You used my personal information on another website? Seriously?
Please give me your legal departments contact information so I can serve them with legal documents.
Click to expand...
Click to collapse
Nice come back. But I doubt you would go with what you said in the last paragraph...
Thread closed.
As the device has been returned and no further useful discussion is happening here.
There are no ties with Essential manufacturer by any means, but i am sure they would be searching in XDA platform as we have vast number of developers who almost gets their hands on any device and tweaks.
Peace.
Thanks
XDA Staff.