Related
I saw a story on BoingBoing indicating that the G2 has a rootkit installed on it.
boingboing.net/2010/10/05/t-mobile-sneaks-root.html
I am wondering if anyone can confirm this? I haven't received my phone yet, but that would suck.
yeah, any changes you make are reversed upon reboot
It is a very loose use of the term "rootkit", but from the owner's perspective, it is technically correct.
So is that it. Game over?
sinistersai4d4d said:
So is that it. Game over?
Click to expand...
Click to collapse
I'd wait for some credible evidence first. I haven't seen any at all yet...
I'm hoping there is no real merit to this and that the XDA community finds a workaround. I have faith in the devs here. The first one to get a working, solid root will definitely get a donation from me, lol.
My question is.. if the phone always resets the firmware.. what happens when T-Mobile pushes out the next OTA?
They obviously have a work around that needs to be exploited.
you know, when Motorola was doing this ****...everyone was like "no need to worry, HTC doesn't do this kind of stuff, and they make great phones"
What now? Seems like this is the future for sure
hydrogenman said:
you know, when Motorola was doing this ****...everyone was like "no need to worry, HTC doesn't do this kind of stuff, and they make great phones"
What now? Seems like this is the future for sure
Click to expand...
Click to collapse
I think in cases like these, their hands are probably tied. It's hard to say who to put the blame on. The carrier could've requested the block or they would've rejected HTC. Either way, it leaves a bad taste in my mouth. The end user pays a monthly bill and has purchased the phone. Why are they now disallowed to alter their investment? I don't see how the carrier or HTC loses. Preventing us from tinkering will just make us grow to hate the carrier, the phone manufacturer or both.
Where are we supposed to go when Android gets completely locked down? That doesn't sound like open source to me and open source is what drove me to Android in the first place.
I'm sure the big difference with the OTA is the fact that it's:
1) a newer version
2) signed
Failing to meet these requirements probably prevents writing to the "permanent" memory.
Well this is quite irritating. Has this sort of thing been implemented on other devices? And if so, has XDA been able to root it?
I guess what im trying to ask is, if this is true, does that mean the G2 can not be rooted? Need to know because im purchasing one soon and if its impossible to root and get roms on, It would be a deal breaker for me.
Well, it can't really be impossible, but if it requires hardware mods or for the signature to be cracked...it may never happen.
Honestly, I'm happy enough with the phone that I wouldn't be upset it if it was never rooted, but of course I'd prefer that it was. I'm just keeping my fingers crossed that one of the expert rooters can get the job done.
Yellowfrizbee said:
Well this is quite irritating. Has this sort of thing been implemented on other devices? And if so, has XDA been able to root it?
I guess what im trying to ask is, if this is true, does that mean the G2 can not be rooted? Need to know because im purchasing one soon and if its impossible to root and get roms on, It would be a deal breaker for me.
Click to expand...
Click to collapse
Anything that can be engineered, can ultimately be reverse engineered. I'm sure once devs like Cyanogen and others get a G2 in hand, they'll have some sort of solution or at least a better explanation than what this website gives. One can only hope. If it turns out to be hardware-driven, that scares me a bit.
Wow, what a boneheaded move by Tmo considering that so many people considered the G2 to be the successor to the N1 as a dev phone.
Jorsher said:
I'm sure the big difference with the OTA is the fact that it's:
1) a newer version
2) signed
Failing to meet these requirements probably prevents writing to the "permanent" memory.
Click to expand...
Click to collapse
That shouldn't matter then.. remember the CLIQ and DROID were rooted by adding SU to a signed OTA w/o changing the signature bits in the compressed OTA.
iT cant be impossible cause then we would never be able to get updates so like everyone is saying im sure some Pro Moders / Hackers will find a way. Will it be as simple as other roots? Prly not but im sure at some point we will have it. I to am happy with the phone as is and rly the only thing that we are lacking (correct me if im wrong) is the built in teathering and becoming a WiFi hotspot. I can live without those things but some people might need them. At any rate my fingers are crossed =)
Kubernetes said:
Wow, what a boneheaded move by Tmo considering that so many people considered the G2 to be the successor to the N1 as a dev phone.
Click to expand...
Click to collapse
The G2 is not a dev phone and they dont have dev phones of the G2 available for purchase..not sure what your inferring? The G1 had dev phones as did the N1.. nothing on the G2 though as of yet.
Well, if this is the case, then the phone goes back today. *sigh* I really like Android 2.2 over 1.6.
genibus said:
The G2 is not a dev phone and they dont have dev phones of the G2 available for purchase..not sure what your inferring? The G1 had dev phones as did the N1.. nothing on the G2 though as of yet.
Click to expand...
Click to collapse
He wasn't referring to an actual "dev" G2 phone...he meant the G2 was perceived as the next big "open" phone for devs to have just how the N1 was widely accepted/perceived as a phone for devs (being able to root, load custom ROMS, etc. freely) (ie. moto's execs telling disgruntled X owners that if they wish to have custom roms and such they should buy a google n1).
Jorsher said:
... I wouldn't be upset it if it was never rooted, but of course I'd prefer that it was. ...
Click to expand...
Click to collapse
The problem with this position is if you have a need that T-Mobile refuses to meet, then you cannot override them.
But as others have pointed out, it can be reversed engineered. Physical access to the hardware essentially makes it vunderable to whatever security counter-measures you wish to invest in.
Im not a big developer or hacker of any sort and so i just have a quick simple question. Dont get mad at me for not knowing. But do we NEED a perm root to be able to use ROMS? What happens if we use a rom without perm root? A bricked phone? Erased data? Ive always been wondering this and never came across an answer or a similar thread
Sent from my T-Mobile G2 using XDA App
hawaiian.monzta said:
Im not a big developer or hacker of any sort and so i just have a quick simple question. Dont get mad at me for not knowing. But do we NEED a perm root to be able to use ROMS? What happens if we use a rom without perm root? A bricked phone? Erased data? Ive always been wondering this and never came across an answer or a similar thread
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Tmobile included the chip so it will revert back to stock if it is rooted, therefore eliminating the possibility of a brick. If you call cust support and tell them you are having issues because you tried to root your g2, all they have to say is "reboot your phone." I think tmo did this because of the slew of customers calling cust support when they bricked their g1/mt3gs. Therefore, it is the inexperienced user's faults that tmobile had to install the root kit. If noobs didn't brick their devices so prevalently and ask tmobile for help with their mess up, there wouldn't be a need for the chip.
Sent from my HTC Dream using XDA App
ad505 said:
Tmobile included the chip so it will revert back to stock if it is rooted, therefore eliminating the possibility of a brick.
Click to expand...
Click to collapse
Ugh. This is not only false, but has been repeatedly debunked. There is no chip, mechanism, or anything else that "reverts" the phone back to stock.
The NAND itself is set to be read-only at boot, and no one has yet succeeded in disabling this protection. When people root the G2 and make changes to the system, these changes only appear to be present because the Linux kernel is caching them. They are never written to the device, and so at next reboot (or earlier, when the caches are flushed) they disappear.
itp said:
Ugh. This is not only false, but has been repeatedly debunked. There is no chip, mechanism, or anything else that "reverts" the phone back to stock.
The NAND itself is set to be read-only at boot, and no one has yet succeeded in disabling this protection. When people root the G2 and make changes to the system, these changes only appear to be present because the Linux kernel is caching them. They are never written to the device, and so at next reboot (or earlier, when the caches are flushed) they disappear.
Click to expand...
Click to collapse
Ok, chip or not, the "reboot unroot" was because folks bricked their devices and asked tmobile for help, flooding their customer support and overwhelming their resources. It makes perfect sense to me why this was included in a flagship device like the g1's successor.
Sent from my HTC Dream using XDA App
Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2
luis86dr said:
Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2
Click to expand...
Click to collapse
More like "Unfortunate side-effect of being read-only but appearing as read/write to the OS."
In normal circumstances, it's not an issue (being that nothing needs /system to be r/w for normal operation.) Technically you are operating it out of spec, since you re-mounted /system as r/w.
Not that I agree with it, it's ****ty (and the main reason I returned my G2.)
To answer the OP, yes - two things need to happen before ROMs can be released:
1) Permanent NAND unlock
2) Recovery (Clockwork Mod or similar) to write the ROM to un-locked storage.
Until both of these happen, ROM development is at a standstill.
luis86dr said:
Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2
Click to expand...
Click to collapse
What on earth makes you think it's a bug rather than a deliberate HTC feature?
keenerb said:
What on earth makes you think it's a bug rather than a deliberate HTC feature?
Click to expand...
Click to collapse
One could argue that the controller lying about syncs to "disk" is buggy behavior. But it's clear that it's very much deliberate.
How is it clear that it's deliberate? It only serves to let us mess around with our phones through a temporary root. It doesn't add to the underlying cause that we haven't rooted the phone.
At least, thats what I gathered from the wiki.
Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Sent from my T-Mobile G2 using XDA App
You're only making changes to the cache, so after using the phone for awhile, parts of the cache get emptied out, and they just go away. This is why when you have temp root, after enough time, your phone will just restart.
I've seen that theres work to get ROMs loading from SD cards, I haven't checked into this myself, so it might just be a pipe dream, but still, do you really want to run everything from your SD card?
At this point, it works better (and longer) to have temp root, and make small changes here and there.
And please someone correct me if I'm wrong on any point.
hawaiian.monzta said:
Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Click to expand...
Click to collapse
In fact, there is no such thing as permanent root. There is only root, the problem is that anything you do while being rooted is not preserved, as the memory card where the system is is write-protected. So you can't modify the system and make the root available permanently.
And to your question - no, you don't need permanent root to use ROMs. But permanent root needs write access to system and custom ROMs also need write access to the system. So they don't depend on each other, but both depend on another feature - the write access to the system (the integrated memory card, eMMC). Once you get write access, both problems ("permanent root" and custom ROMs) will be solved.
faugusztin said:
And to your question - no, you don't need permanent root to use ROMs. But permanent root needs write access to system and custom ROMs also need write access to the system. So they don't depend on each other, but both depend on another feature - the write access to the system (the integrated memory card, eMMC). Once you get write access, both problems ("permanent root" and custom ROMs) will be solved.
Click to expand...
Click to collapse
Technically, you only need recovery. But the fact of the matter is, they go hand-in-hand. Once one is compromised, the other is as well. This has been the pattern with HTC thus far anyway...
hawaiian.monzta said:
Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Click to expand...
Click to collapse
I answered here
No roms until those two things happen.
ad505 said:
Ok, chip or not, the "reboot unroot" was because folks bricked their devices and asked tmobile for help, flooding their customer support and overwhelming their resources. It makes perfect sense to me why this was included in a flagship device like the g1's successor.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
If you think this is about anything but control, you're sorely mistaken. They do this because they can, and because they have commitments to Amazon, Photobucket, and every other pre-installed crapware provider they have a contract with to guarantee the user cannot remove their app.
If it's about bricked handsets, why not take the Nexus One approach: Make rooting trivially easy to do - anyone wishing to do so will likely take the path of least resistance. Once rooted, HTC/T-Mo can visually identify a rooted handset and decline warranty service. Problem solved.
franky1029 said:
How is it clear that it's deliberate? It only serves to let us mess around with our phones through a temporary root. It doesn't add to the underlying cause that we haven't rooted the phone.
At least, thats what I gathered from the wiki.
Click to expand...
Click to collapse
It's deliberate because of the whole history behind it. S-ON, write protection, read-only partitions, gold cards, subsidy unlocking, etc. This arms race has gone on for years. All of this is done deliberately.
T-Mobile has an interest in making it as difficult as possible to use the handset on a different network, or use apps they don't like (which, btw, they have not started revoking yet, just wait, it's a matter of time...) Likewise, HTC has an interest in making their customer (T-Mobile) happy.
HTC doesn't give a **** that you, the end user, are unhappy. Their client is T-Mobile.
None of this will change until we (as customers) stop putting up with it, stop buying subsidized handsets from the Provider channel, and start buying un-subsidized handsets straight from the manufacturer. Unfortunately, this isn't going to happen in the U.S. for quite a while - people are too dumb to know what they are doing...
It was no accident that the device is designed to make writing to /system difficult. It was no accident on any other HTC handset either.
Why would you want temporary root over persistent root? It doesn't serve us at all - it only makes it harder on them (HTC - in the long run) once someone like Unrevoked roots it forever.
Now that we have smaller ASOP/AOKP ROMs, is it possible to Re-Size the System Partition to fully leverage the extra space that before was being used by the Samsung ROM?, thanks
I remember someone saying that, due to the fact the internal memory drivers are proprietary, there wouldn't be a way to resize partitions. Hopefully I'm wrong, though.
What I'm really hoping for is a well-laid-out tutorial for reallocating your external SD card as internal storage.
i'm wondering the same, recently installed SlimBean, still only have 9.7GB free of Internal Storage, my system root indicates only 2.6GB, thats 12.3GB, is that all the 16GB models have after formatting?
i think someone will have to get us to an engineering hboot of sorts
This will likely never happen, period. The eMMCs used in most Android smart phones are only set up to allow partitioning once at the factory, and then never again. It's a hardware thing. You can partition and divide up more, but you can't reclaim or change what's already been partitioned(unless you did it).
What's more likely to happen is, just like with most other Samsung phones I've owned, someone will take the Internal-External-Swap script and modify/update it to work on the Galaxy S4. Basically what this script does is change the mount locations inside the phone so Android believes the SD card is the internal storage, and the former Internal Storage is the external.
EDIT: Example of the script being modified/updated for the Galaxy Note 8.0: http://forum.xda-developers.com/showthread.php?t=2276193
We did on the Nexus One to get ICS on it. Called Blackrose. S-Off was created, not true, but enough to allow a hex editor to resize partitions. I did this many times to make System larger and Data smaller to flash the bigger rom's like ICS that needed more System size to run properly.
It was developed because of a strong need. If the need is not big enough, no dev may waste their time. The One S got that capability too--
rugmankc said:
We did on the Nexus One to get ICS on it. Called Blackrose. S-Off was created, not true, but enough to allow a hex editor to resize partitions. I did this many times to make System larger and Data smaller to flash the bigger rom's like ICS that needed more System size to run properly.
It was developed because of a strong need. If the need is not big enough, no dev may waste their time. The One S got that capability too--
Click to expand...
Click to collapse
While I acknowledge those feats, from my quick research, I'll point out that those were both done with custom HBOOTs which changed the bootloader. As the Galaxy S4's bootloader is not only locked but encrypted, I still have my doubts about this being able to be done.
Were the Nexus One or HTC One S able to reclaim internal storage space for the user in the way that the OP is asking? I'm curious because while making System larger and Data smaller is an good example of re-partitioning, weren't you simply moving around space that was already reserved to the OS area and unavailable to the user... if that statement makes any sense. This is stepping outside my realm of expertise here, and I'll admit that my technical knowledge is very limited. The last time I heard these proposals were back when the T-Mobile G2 came out and folks were asking the same questions then.
EDIT: Ultimately you're right, and demand will drive innovation either way. IF the devs find a way to do this, I'll be pleased. If they find way to swap the internal/externals, I'll be happy with that too.
It was a moving around of sizes. Make one larger and one smaller. Total size had to remain same. Not sure if anyone will do it. But, may be possible. Outside of my expertise too.
Sent From My 32gb Samsung Galaxy S4 using Tapatalk 2
Awwww crap. In that case I think I'm refusing delivery of my AT&T GS4. Sucks...
the pit file for the gegs4 would resize it
HumanXv2 said:
the pit file for the gegs4 would resize it
Click to expand...
Click to collapse
You go first trying that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
You go first trying that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will when my phone gets here monday and the files are available. Really no reason it shouldn't work but I may be wrong. I odin'd Tmobile files onto my S3(bootloader,csc,rom) and it worked fine.
Im on Tmobile and would prefer to rid the phone of all traces of ATT =)
HumanXv2 said:
I will when my phone gets here monday and the files are available. Really no reason it shouldn't work but I may be wrong. I odin'd Tmobile files onto my S3(bootloader,csc,rom) and it worked fine.
Im on Tmobile and would prefer to rid the phone of all traces of ATT =)
Click to expand...
Click to collapse
Odin will probably error out if you try that, due to the locked bootloader.
I thought a full odin file had the bootloader?
mattdm said:
Odin will probably error out if you try that, due to the locked bootloader.
Click to expand...
Click to collapse
If he's lucky. I predict a brick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
If he's lucky. I predict a brick.
Click to expand...
Click to collapse
Maybe so. And if it bricks, it will be a hard brick.
HumanXv2 said:
I thought a full odin file had the bootloader?
Click to expand...
Click to collapse
Unless it is signed by Samsung with the correct authentication key, it won't matter. If you run across said key...you will be one popular individual.
Ok so there are keys on the phones non writable memory and when the phone boots up it has to match keys with the bootloader and all to boot?
Thank you. This is much better than "it wont work"
HumanXv2 said:
Ok so there are keys on the phones non writable memory and when the phone boots up it has to match keys with the bootloader and all to boot?
Thank you. This is much better than "it wont work"
Click to expand...
Click to collapse
Yea, but it runs a lot deeper than that. The "chain of trust" employed by this phone goes all the way down to the hardware not just NV. Loki sidesteps the process (again, there is more to it than that), but can be software patched by AT&T / Samsung. So far, the three best ways at getting at this bootloader seem to be:
1. Obtaining Samsung's encryption key. It would most certainly have to be released or leaked because it would be near impossible to break the encryption by other methods.
2. Somehow allow a secondary bootloader to run on the device. I think Devs are still waiting for the full release of KNOX to see if it would allow this or not.
3. Somehow disable the hardware fuses that are part of the chain of trust. This is very unlikely and would require the ability to re-press certain circuitry and develop new code. And if successful, every single phone would have to be done that way. So although I mentioned it, it's really not a viable option at all.
The bottom line is to NEVER take a software OTA from AT&T or Samsung until it is checked and cleared by Devs and (in the near future), if you need to send your phone for warranty repair or need to exchange it, you might be screwed.
This is not wise at all. We're talking hardbrick here.
Hi figured we could use our own separate thread to discuss the killswitch Nvidia supposedly put in place on our old Shield tablets and see what has worked for those who have received their replacement units. If you've gotten a replacement please share if your old unit has been destroyed or not...if not please let others know what the old tablet has on it or what you did to attempt to prevent the brick! Thanks for helping us all out here!
As I said in the other thread, I received my new one, and my old one is still usable on rooted latest stock, unlocked bootloader, with the only app missing being Chrome for some reason. Nothing else disabled or uninstalled. Maybe they haven't turned on the server that sends the kill signal yet.
If the company wants the other device back (dunno if that is true), why keep it? You are breaking a deal while making it less appeling for companies to do this type of thing...+its a saftey risk for you and others around you.
Nvidia said they do not need it back
ManualG on the Nvidia forum said they are not requiring you send it back
"We don't require you to send it back to us to receive the replacement and are collecting them only to make it less of a burden on everyone else who dont have drop off locations like that close by." So you can keep it if you want ?
16 gig tablet, got it this morning. My original is still functional, it was stock rom, rooted with xposed on it. That's as much modding as I've done with mine.
does anyone have more informations about this killswitch?
Is it a service that needs to be deactivated or deleted or a kernel feature?
I just want to make sure it doesn't kill my old tablet when I set up the new one.
Alternatively, I could just flash an older factory image or custom firmware.
From what I've read on other forums (i.e. reddit) most have indicated that the killswitch is embedded in the bootloader and will activated on the defective tablet once the replacement tablet is registered on the nvidia side. I of course cannot confirm for this to be the case but just sharing what others have reported.
yea but it must communicate with the server then and that only works when Android is booted up and all communication drivers loaded.
So there must be another service running in Android that gives this information to the bootloader to kill itself.
If it's bootloader based, flash a bootloader from one of the older recovery images.
Will try that. BL from Update 2.2.2 should be fine?
actually if I flash it back to 2.2.2 it should be fine too since the changes to 3.X aren't that big
That should work just fine.
big time noob question but where are you getting the old bootloaders from to flash?
Until somebody's tablet gets deactivated and a log is captured during the deactivation process, everything said here or anywhere else is just speculation.
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
chicodelta said:
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
Click to expand...
Click to collapse
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
bluegizmo83 said:
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
Click to expand...
Click to collapse
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
scorpionx said:
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Click to expand...
Click to collapse
No problem. As I said, I'm all for the discussion, I just wanted to make it clear to everyone that its all just speculation at this point.
I think the old bootloaders are in the old full OTA's someone correct me if I'm wrong. You can also extract them from the full OTA
chicodelta said:
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
Click to expand...
Click to collapse
To me, this is the most logical place to start at this point! Maybe it works, maybe it doesn't, but unlocking the bootloader, rooting, and installing a custom rom seem like a good starting place. If the stock devices are definitely getting wiped anyways, any changes we make now can't hurt the chances of keeping it alive!
Ever phone or tablet I buy is always the one that cant be rooted without a pc. Everytime Odin required, so sick of it. I thought they were supposed to make a universal platform that all androids adhered to. What happened to that?
smokeuout said:
Ever phone or tablet I buy is always the one that cant be rooted without a pc. Everytime Odin required, so sick of it. I thought they were supposed to make a universal platform that all androids adhered to. What happened to that?
Click to expand...
Click to collapse
Name a current device that doesn't need a PC to be rooted? Is that not universal enough?
ashyx said:
Name a current device that doesn't need a PC to be rooted? Is that not universal enough?
Click to expand...
Click to collapse
No thats not universal enough. Go through the compatability list for framaroot, or master root and that will give your answer. I just want my phones to be on the same level. All on that list or not but there shouldnt be an in between
smokeuout said:
No thats not universal enough. Go through the compatability list for framaroot, or master root and that will give your answer. I just want my phones to be on the same level. All on that list or not but there shouldnt be an in between
Click to expand...
Click to collapse
Ok humour me. Show me evidence of one device that either of those root exploits has been successful with since Android 5.
ashyx said:
Ok humour me. Show me evidence of one device that either of those root exploits has been successful with since Android 5.
Click to expand...
Click to collapse
Okay but how am I going to show proof? Those one click root apps wouldnt be around if they didnt work...Look at towelroot as well, and also kingroot. Lots of options even though I have no proof
smokeuout said:
Okay but how am I going to show proof? Those one click root apps wouldnt be around if they didnt work...Look at towelroot as well, and also kingroot. Lots of options even though I have no proof
Click to expand...
Click to collapse
Rooting a tablet is a security risk that manufacturers don't WANT users to take. They want rooting to be difficult. So, IMO, it is down right silly to think they'd intentionally let some apps, like the ones you mentioned, defeat their purpose. And NONE of those apps work on a high percentage of the tablets on the market today.
If having a tablet that can be rooted by one of them is that important to you, then I'd suggest you check the list BEFORE you make your purchase rather than whining about it when they don't work.
smokeuout said:
Okay but how am I going to show proof? Those one click root apps wouldnt be around if they didnt work...Look at towelroot as well, and also kingroot. Lots of options even though I have no proof
Click to expand...
Click to collapse
They DON'T work that is the point. The fact that you actually mentioned towel root implies that you've been trawling the Internet and you don't quite know where things are up to with root.
Those exploits have long since been patched. Pretty much no one click root's work on any recent device.
Google have patched all current exploits. Any decent manufacturer should have updated their firmware to include the patches.
Anything MM onwards is unlikely to work with one of these one click root apps.
Any device that does simply means the manufacturer doesn't care about security or has abandoned the device.
My point here is that pretty much no device works with any of these one click root's anymore.
You have a device made by a manufacturer that cares about security.
The very thing you seem to be whining about.
Millions of devices are currently using the only real root solution avaliable, Magisk, which requires a PC.
@lewmur pretty much nailed it.
If you want a device that works with one of these one click exploits, sell your up to date device and buy yourself an old banger running kitkat.
lewmur said:
Rooting a tablet is a security risk that manufacturers don't WANT users to take. They want rooting to be difficult. So, IMO, it is down right silly to think they'd intentionally let some apps, like the ones you mentioned, defeat their purpose. And NONE of those apps work on a high percentage of the tablets on the market today.
If having a tablet that can be rooted by one of them is that important to you, then I'd suggest you check the list BEFORE you make your purchase rather than whining about it when they don't work.
Click to expand...
Click to collapse
Oh but i do check before I make a purchase. But everytime for one reason or another things change or an update comes and all of a sudden, now you need Odin. That why im pissed kid.
Also im sure the companies arent letting anyone root by choice. They would rather have you pay $1200 for an official unlocked phone...lol...But yes those apps can and will work on many phones running 8.1 and before.. perhaps you should do your homework instead of sticking your head in the sand
ashyx said:
They DON'T work that is the point. The fact that you actually mentioned towel root implies that you've been trawling the Internet and you don't quite know where things are up to with root.
Those exploits have long since been patched. Pretty much no one click root's work on any recent device.
Google have patched all current exploits. Any decent manufacturer should have updated their firmware to include the patches.
Anything MM onwards is unlikely to work with one of these one click root apps.
Any device that does simply means the manufacturer doesn't care about security or has abandoned the device.
My point here is that pretty much no device works with any of these one click root's anymore.
You have a device made by a manufacturer that cares about security.
The very thing you seem to be whining about.
Millions of devices are currently using the only real root solution avaliable, Magisk, which requires a PC.
@lewmur pretty much nailed it.
If you want a device that works with one of these one click exploits, sell your up to date device and buy yourself an old banger running kitkat.
Click to expand...
Click to collapse
Hey cool story but it doesnt apply here. Im sure you can see the title, read it....t580....Hardly cutting edge stuff. If i could downgrade i would but i cant without a pc. I accidently upgraded my tablet and screwed myself. Those apps wont work on a galaxy S10 or galaxy 4 tablet but if i hadnt upgraded i would have used that and it woulda worked. Is chainfire around? He could shed some light if hes still on this
smokeuout said:
Hey cool story but it doesnt apply here. Im sure you can see the title, read it....t580....Hardly cutting edge stuff. If i could downgrade i would but i cant without a pc. I accidently upgraded my tablet and screwed myself. Those apps wont work on a galaxy S10 or galaxy 4 tablet but if i hadnt upgraded i would have used that and it woulda worked. Is chainfire around? He could shed some light if hes still on this
Click to expand...
Click to collapse
Not being rude, but you really have no idea.
If you actually understood anything about root and kept with the times, you would be aware why non of these exploits work on anything beyond Lollipop. Marshmallow if you're lucky and haven't updated.
Supersu stopped working with most devices at Nougat and not at all with Oreo or anything beyond.
Over and out.
ashyx said:
Not being rude, but you really have no idea.
If you actually understood anything about root and kept with the times, you would be aware why non of these exploits work on anything beyond Lollipop. Marshmallow if you're lucky and haven't updated.
Supersu stopped working with most devices at Nougat and not at all with Oreo or anything beyond.
Over and out.
Click to expand...
Click to collapse
I understand all of that just fine, thats not what i was talking about. I mentioned chainfire not because of supersu but because when I used to be on this site daily chainfire would help me out every now and then. Im going to assume hes not so active in here anymore, but maybe im wrong.
smokeuout said:
I understand all of that just fine, thats not what i was talking about. I mentioned chainfire not because of supersu but because when I used to be on this site daily chainfire would help me out every now and then. Im going to assume hes not so active in here anymore, but maybe im wrong.
Click to expand...
Click to collapse
Chain fire sold supersu to a Chinese developer who has since abandoned it.
Chain fire announced his retirement from development a while back.
Magisk is now the only true root solution and even Magisk is constantly having to evolve to keep in the game.
All the other solutions you refer to were simply exploits that leveraged a vulnerability in the running system and have long since been patched even on older devices.
Magisk is not an exploit that leverages a vulnerability, but is a chain of modifications to the running system which is implemented both at the installation stage and at boot time. Similar to how Supersu used to work, but in a more advanced way which creates its own environment.
smokeuout said:
Oh but i do check before I make a purchase. But everytime for one reason or another things change or an update comes and all of a sudden, now you need Odin. That why im pissed kid.
Also im sure the companies arent letting anyone root by choice. They would rather have you pay $1200 for an official unlocked phone...lol...But yes those apps can and will work on many phones running 8.1 and before.. perhaps you should do your homework instead of sticking your head in the sand
Click to expand...
Click to collapse
That's BS. I've had a T580 since 2016 and you've never been able to root one without Odin. There is NO WAY it is on a list for one of those apps. If you just bought the T580 and checked and found it on one, name the one. Put up or shut up.