Has anyone actually had Verizon/Moto decline warranty work (root)? - Droid RAZR M Q&A, Help & Troubleshooting

So, here's the deal. I just got my RAZR M on Feb. 1st. I upgraded from a Droid X that was rooted and running a custom ROM for about 2 years.
Now, I know the ROM scene for the M isn't huge, but some apps I used do use root. I know Moto put in that root checker, but has anyone actually had a return/warranty declined because of it?
I know of course that it is a gamble and that it can always be declined, I am just curious if anyone has actually had that issue. Sucks to lose a year warranty to be able to run a few apps correctly.
Thanks!

Coronado is dead said:
So, here's the deal. I just got my RAZR M on Feb. 1st. I upgraded from a Droid X that was rooted and running a custom ROM for about 2 years.
Now, I know the ROM scene for the M isn't huge, but some apps I used do use root. I know Moto put in that root checker, but has anyone actually had a return/warranty declined because of it?
I know of course that it is a gamble and that it can always be declined, I am just curious if anyone has actually had that issue. Sucks to lose a year warranty to be able to run a few apps correctly.
Thanks!
Click to expand...
Click to collapse
cannot speak directly to that, but I did try contacting motorola for tech support the other day. in order to assist me further, they needed my cell number or ESN (which I gave them). within a few minutes, they determined that my phone was rooted. so I'm not sure if they could ping the device or whatnot, but it sounds like they've got measures to check for this.

jco23 said:
cannot speak directly to that, but I did try contacting motorola for tech support the other day. in order to assist me further, they needed my cell number or ESN (which I gave them). within a few minutes, they determined that my phone was rooted. so I'm not sure if they could ping the device or whatnot, but it sounds like they've got measures to check for this.
Click to expand...
Click to collapse
Well that's a little disconcerting. I wonder if that has to do with the persistent root checker or some other check in the system files.
Did they refuse to help any further after discovering the root problem? Was your question to them hardware or software related?

Coronado is dead said:
Well that's a little disconcerting. I wonder if that has to do with the persistent root checker or some other check in the system files.
Did they refuse to help any further after discovering the root problem? Was your question to them hardware or software related?
Click to expand...
Click to collapse
they said that they could not offer any more support that was software related. my issue was software related.

Related

T-mobile and HTCs view on rooting?

I was thinking if anyone knew about htcs and t-mobiles view on rooting
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app. So I would reasonible believe they don't want you to. Another thing is they do not warranty work on rooted devices
What do you mean they do not warranty work on rooted devices
Meaning a rooted device loses its warranty if its sent in rooted, if its been flashed back then it still has its warranty...
I doubt Google and HTC care if we root our devices, they don't loose out, and they sell rooted phones any way (ADP1 and I think the ION is rooted too). I guess the only reason google would care is app piracy...
M..N said:
What do you mean they do not warranty work on rooted devices
Click to expand...
Click to collapse
If you root your phone, kiss good bye to your warranty. It really doesn't matter though, if it's a hardware issue you can unroot and they'll never know, and if it's bricked you can say it was update that bricked it.
Has anyone in the uk replace their phone successfully
M..N said:
Has anyone in the uk replace their phone successfully
Click to expand...
Click to collapse
What do you mean?
I mean has anyone in the uk replaced a bricked phone caused by the new spl without any problems
HTC aren't going to bothered with what people do, neither are Google really. It's the network operators which want to tie people to their crap and have you pay for it.
The issue is with the warranty and if you broke it, Asus, for example, aren't bothered what OS you run on their hardware, but if you flash a bad BIOS then it's your fault. ATI, nVidia, Gigabyte etc encourage overclocking but won't honour warranty if it causes damage.
Google are likely to secretly want rooted phones as more network operators mangle the OS to suit themselves in the future and push their own services over Googles.
M..N said:
I was thinking if anyone knew about htcs and t-mobiles view on rooting
Click to expand...
Click to collapse
My guess is that T-Mobile doesn't want rooting because it allows tethering.
Tethering generally causes an increase in data usage, and an increase in bandwidth use by the phone. This can impact T-Mobile cell towers and other T-Mobile customers if too many tethered phones are sucking up bandwidth on a particular tower.
gridlock32404 said:
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app.
Click to expand...
Click to collapse
My recollection is that that bug was patched because it allowed any app to gain root access for itself, not just the end user. Hopefully I don't need to explain why that's a bad thing. The patch didn't specifically patch out root access for the user because root access for the user was never a design feature to begin with.
M..N said:
I was thinking if anyone knew about htcs and t-mobiles view on rooting
Click to expand...
Click to collapse
If you really want to know the official views of these companies, email or call them. Most of the members of xda-dev are not employed by/affiliated with either company, and as such it is impossible to tell if they're telling truth, passing along unverified rumor/hearsay, or just making bs up.
gridlock32404 said:
Well, if they wanted you to do it, than they wouldn't be patching off the root access or the app. So I would reasonible believe they don't want you to. Another thing is they do not warranty work on rooted devices
Click to expand...
Click to collapse
You can also look at it like they don't care if you do it but they don't want a one click solution that will allow every freakin retard out there to do it. Think about it how many stupid questions do we get from people who used the one click vs ones who did it manually.
Also having an app with that kind of access to the phone means ANY app can have that kind of access to your phone including the bad evil kind you dream of making gridlock.
The problem with rooting is this;
Some very small number of people understand the system and can be fully self-sufficient with full root access.
And then you have the others, who want root for whatever features come with it... and some of them start messing with things they don't understand and end up in a huge mess... and then send it back for warranty work because their device doesn't work right any more. This means MUCH more support from the retailer/manufacturer. The other side of this is that if you have a whole lot of people trying things like cyanogen's latest unstable mod and show it off to a whole lot of people, and it crashed like nuts, then the people who see it don't necessarily understand that it is due to running crazy experimental stuff and instead think that 'droid itself is junk.... which is incorrect.
So preventing root access means that you have a simpler, more consistent, and more reliable environment, which means a better platform reputation and lower overall support costs.
lbcoder said:
The problem with rooting is this;
Click to expand...
Click to collapse
There's another point of consideration. While I know I just wrote about the unverifiability of some posts on xda, i'm going to have to do a complete 180 and do just that. I can't confirm since I'm not a handset maker (nor do I work for one), but i'm quite confident in believing that in order to acquire Google's consent and software support to create a Google Experience phone, root access has to be restricted from the end user. Again that's all speculation.
lbcoder said:
The problem with rooting is this;
Some very small number of people understand the system and can be fully self-sufficient with full root access.
And then you have the others, who want root for whatever features come with it... and some of them start messing with things they don't understand and end up in a huge mess... and then send it back for warranty work because their device doesn't work right any more. This means MUCH more support from the retailer/manufacturer. The other side of this is that if you have a whole lot of people trying things like cyanogen's latest unstable mod and show it off to a whole lot of people, and it crashed like nuts, then the people who see it don't necessarily understand that it is due to running crazy experimental stuff and instead think that 'droid itself is junk.... which is incorrect.
So preventing root access means that you have a simpler, more consistent, and more reliable environment, which means a better platform reputation and lower overall support costs.
Click to expand...
Click to collapse
Good breakdown.
StanSimmons said:
My guess is that T-Mobile doesn't want rooting because it allows tethering.
Tethering generally causes an increase in data usage, and an increase in bandwidth use by the phone. This can impact T-Mobile cell towers and other T-Mobile customers if too many tethered phones are sucking up bandwidth on a particular tower.
Click to expand...
Click to collapse
I dunno about in the US, but this would most likely be T-Mobile UK's problem.
The terms of the contracts say that you can't tether with the standard net package, you need to upgrade to the next one (extra £10 instead of £5) to be able to use your 3G/HSDPA connection on the PC.
Problem is, with phones like the G1 how would they know? If it was something like an old Sony Ericsson W810 they would know straight away due to the amount you were downloading but on a G1 you can view full webpages anyway, download images etc and programs via the market. So really they have no way of knowing if you're tethering of not. Hence they want to try and stop tethering from being an option.
Fingerlicken, why would I Target a system I use, if I let out any kind of evil it would be against an Iphone.
Why does Linux have so little viruses, cause most of the hackers use linux
gridlock32404 said:
Why does Linux have so little viruses, cause most of the hackers use linux
Click to expand...
Click to collapse
Wha? I think you have your cause and effect mixed up. Also, this thread is getting off topic.

Our Fight Against Verizon

If you haven't heard all ready Verizon is tracking down root users and limiting there data or fully suspending it so watch out. But we have to fight back against them by hiding Verizon from seeing that we are proudly rooted and some people have said the would sue Verizon. Please do whatever you can to fight against this.
Also motorola and htc are going to start doing the same.
tyvallely said:
If you haven't heard all ready Verizon is tracking down root users and limiting there data or fully suspending it so watch out. But we have to fight back against them by hiding Verizon from seeing that we are proudly rooted and some people have said the would sue Verizon. Please do whatever you can to fight against this.
Also motorola and htc are going to start doing the same.
Click to expand...
Click to collapse
Wow... just... wow.... First off, they MAY be tracking phones. Second, there is NO proof they are limiting anyones data or suspending service. I only posted that because it's something that MAY be happening, and people should be aware. It wasn't meant for fear mongering.
If you would have read the whole article, you would have seen that this is an INDUSTRY WIDE thing. Not just Verizon.
There is no need for ANYONE to freak out right now.
IF its true, and they are tracking people who have loaded GB on their phones, there isn't a damn thing you can do about it now, so just sit back and enjoy your damned GB Droids.
I am about 80% positive they are tracking after I googled for 5 hours.
tyvallely said:
I am about 80% positive they are tracking after I googled for 5 hours.
Click to expand...
Click to collapse
It's very possible, and I wouldn't blame them too much. They should have a way to detect fraudulent warranty claims.
And for those of you who think rooting your phone and loading custom ROMs shouldn't void the warranty, your wrong. The carriers and OEMs put software on the phones they KNOW work. They DON'T know if the custom ROM you are using will work correctly.
I have no problem with rooting at your own risk (ie: Voiding warranty)....that's quite frankly, the way it should be, because if I'm overclocking my device I understand I'm increasing the chances of damaging the internal hardware in my phone. Nevermind, all the people who brick their devices because they don't know what they're doing.
I would hope that Verizon doesn't have the balls to try and go after people who are not doing anything illegal with their rooted device though (ie: Not tethering, regardless of how you feel about it). It's already been established that it's legal to root your device. Myself, while I've downloaded the tethering app, I've never used it for more then 30 seconds to try it out and see if it worked. I only downloaded it for emergency purposes, and I've yet to have said emergency.
Why would the carriers even care if we're rooted and using custom ROMs as long as we're not doing anything bad, like the aforementioned tethering? We paid for our phones and we pay our bills, so we should have the right to do as we please as long as we're not infringing on others.
As for me, I will stay rooted and if a class action suit is filed, will happily join in.
My question is' if we installed the non rooted version of gb, are they tracking that too?
Sent from my DROID2 using XDA App
phoenixus said:
My question is' if we installed the non rooted version of gb, are they tracking that too?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
They have been tracking root users long before the GB leak. From what I've read, they have been looking at who doesn't take updates. I don't know exactly if they put any snooping file in the GB leak or not.
Sent from my DROID2 using XDA App
Guys I really don't think they will be doing this. I understand that root should be a void in warranty, and totally agree with that, but if they shut off our services for having root, than a lawsuit should be made. They have no right to shut them down. Doesn't that breach that law made like a year ago about jailbreaking/rooting?
HerroMoto said:
Guys I really don't think they will be doing this. I understand that root should be a void in warranty, and totally agree with that, but if they shut off our services for having root, than a lawsuit should be made. They have no right to shut them down. Doesn't that breach that law made like a year ago about jailbreaking/rooting?
Click to expand...
Click to collapse
Well, you could argue that rooting your device is legal, but carriers don't have to let them on their networks.
Anyways, I highly doubt any carrier will be cutting anyones service.
I think what they might do is this:
They will send a notice to everyone that they are tracking root users, their meids will be flagged to ensure no warranty claims can be filed by them, and that if caught tethering without paying, they will be charged a fee.
That would be a logical way to go about it.
orkillakilla said:
Well, you could argue that rooting your device is legal, but carriers don't have to let them on their networks.
Anyways, I highly doubt any carrier will be cutting anyones service.
I think what they might do is this:
They will send a notice to everyone that they are tracking root users, their meids will be flagged to ensure no warranty claims can be filed by them, and that if caught tethering without paying, they will be charged a fee.
That would be a logical way to go about it.
Click to expand...
Click to collapse
Exactly what I was thinking. That might be a no go with root for me. I need my warranty. Tethering is honestly not a huge deal to me, but if my warranty is gone I don't know what I'd do. I'm sure if one carrier does this, they all will start rewriting their policies.
This thread seems a bit incendiary.
I'm not sure what lawsuit people intend to file against Verizon. It isn't clear that tracking rooted users violates those users' rights in any way.
As for denying warranty service, I have rooted every Android phone that I've had, and I have no problem if Verizon denies me warranty service on any phone that I have rooted (so long as the problems could logically be related to rooting). I also modified my car when it was under warranty, and if the dealership denied me service on the exhaust, that would have been fine (although they couldn't deny me service on, for example, the suspension).
If I brick my phone, then that is my fault - Verizon shouldn't have to give me a new one.
I have no doubt that they are tracking/logging rooted users. Maybe this is why GB got leaked in the first place? This is all a result of the community.
The ones that tether the 20ish gb of data a month, to the "noob" that roots and messes something up and instead of reading up on how to fix, they just return it to Verizon. I broke a D2 a few months back, but instead of returning it, I bought a new one at full price because I was rooted. Its just a moral thing to me.
As long as you don't tether alot or do anything else illegal, I believe that just being rooted will not result in a termination of contract. That's just my opinion.
Sent from my DROID2 using XDA Premium App
This is what I found out. They are tracking use to try and detect those who are tethering. AT&T is also doing this now to try and find out who is tethering w/o the appropriate packages. What they will do when they find the un-authorized tethering people is beyond me, that wasn't told to me. I was also told not to install the GB leak. This comes from a very reliable source within Verizon. I wasn't told much more than that or what they are doing with violators. I don't know what the deal is with the GB leak, I just know I will listen to my friend and not install it. Usually I am one who roots immediately and gets to town doing what they don't want us doing, but since this came from a really close friend, I will listen and take his advice.
I don't see why you shouldn't install the GB leak if you are just doing the non-rooted version. I mean what will verizon do? Block you're phone when the official OTA comes out? They can't do that.
I really don't see anything wrong with installing the GB leak, especially if you aren't tethering or anything to steal.
nixternal said:
This is what I found out. They are tracking use to try and detect those who are tethering. AT&T is also doing this now to try and find out who is tethering w/o the appropriate packages. What they will do when they find the un-authorized tethering people is beyond me, that wasn't told to me. I was also told not to install the GB leak. This comes from a very reliable source within Verizon. I wasn't told much more than that or what they are doing with violators. I don't know what the deal is with the GB leak, I just know I will listen to my friend and not install it. Usually I am one who roots immediately and gets to town doing what they don't want us doing, but since this came from a really close friend, I will listen and take his advice.
Click to expand...
Click to collapse
So much paranoia! I always like the "friend at Verizon" story with vague warnings of punishment from Verizon should we install the forbidden leak.
You'll forgive me if I'm a bit skeptical of your story.
I got a guy that has a friend that's related to the uncle of this chick that went to the same high school as this one dude that this other guy knew that said.....wait what were we talking about?
I think a lot of people are blowing this out of proportion. Most the people at Verizon haven't the slightest clue about what the head honchos are trying to do. They pass a lot of BS to their employees to see who leaks out information. Verizon tries to keep secrets the best they can, I doubt anyone knows what Verizon is trying to do. That's going for VZW reps and such. I don't know exactly how the GB leak was leaked out, but personally I'm glad it was, it is such an improvement for our phones and something we really needed. If this happens it happens, I don't know what I'd do (leave VZW, unroot, stay rooted) until the time comes to be honest.
First off.. wow.. with the Big Brother is watching stuff. And 2nd who cares if they are?! I will root every phone I get until I drop dead. And if you want to know why they leaked the GingerBread Rom.. it's called Research & Development! It's the old, "if we can't beat them -secretly join forces with them".
Sent from my "Rooted" Incredible using XDA Premium App
So basicly.. we are their FREE beta testers. So who's using who here? Lol
Sent from my "Rooted" Incredible using XDA Premium App

[Q] If i unlock then relock, can Moto tell that i unlocked?

I know this has been asked before but i just want to be sure, i just got the xoom and i want to know if i can send it in for repairs. I just want to kno if its like the ipod's/phones where there is a physical feature that is broken, so i can relock and my warranty will be valid.
Moto doesn't care.
K thanks
Sent from my HTC Thunderbolt running Das BAMF v1.6.1 remix.
Elysian893 said:
Moto doesn't care.
Click to expand...
Click to collapse
Wait, what makes you say that? Do you know something we don't know? As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.
slack04 said:
As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.
Click to expand...
Click to collapse
... yet they sold us a Google-Experience device with an unlocked bootloader.
You can't break anything seriously with software, which means any potential problems we'd have are either physical, user-abuse, or hardware defects. If you send it in and they determine that the problem is SW, they'll probably just wipe it back to stock and send it to you.
Fact does remain, however, that when you unlock that device you have to acknowledge you are voiding your warranty if you proceed. I'd like to think they would be reasonable - but at the same time, you have agreed to kiss off your warranty when you unlock.
That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.
Jiv3turk3y89 said:
That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.
Click to expand...
Click to collapse
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up
LNKNPRKFN said:
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up
Click to expand...
Click to collapse
Thanks everyone! I think im going to unlock it when I get the chance, the SD card slot is a BIG thing that I could use, also I want it overclocked just a lil (1.25 Ghz per core) so it doesn't lag much on the home screen. Also im not going to be flashing roms and stuff mainly kernels. This device is going to be used as a family computer so i can't mess with it as much as I can with my Phone . Anyways thanks guys!

[Q] Possible to COMPLETELY unroot I337UCUAMF3?

I have an AT&T Galaxy S4 running Android 4.2.2 I337UCUAMF3. I rooted the device using the method posted here:
http://forums.androidcentral.com/sa...-root-new-root-method-found-mf3-firmware.html
Everything was fine. No custom recovery, but I had root access. Well, my company is reclaiming all company-provided BlackBerrys and rolling out Good for Enterprise on personal devices. Without the ability to use ODIN to completely reflash the device, I tried other methods to remove ROOT -- Universal Unroot, and others that unfortunately I don't recall. I've done multiple factory data resets, and that does not help either.
These methods seem to work as I no longer have root access, however, Good thinks I do which causes my account to get disabled anywhere from 1 hour to 3 days after setting it up. My device is currently showing Device Status = Official and I no longer get the "custom" logo when rebooting. The people at Good sent me a Malware Test app that normally does not show anything, but occasionally will return something running a root shell, but no indication of what -- obviously this is what's causing my device to be flagged as rooted periodically and causing my account to be disabled.
So, in the absence of a stock MF3 firmware to install with ODIN, what else can I do to completely remove root?
You might consider going to best buy that has a Samsung kiosk. They can flash the stock mf3 firmware.
From reading around this forum it sounds like you can take it to Best Buy and go to the Samsung Experience there and they have the ability to flash the completely stock ROM on it (MF3). you just need to call around to your best buys stores to make sure they can do it before heading over there. Others have stated that Samsung sent them to the Best Buy Samsung Experience to do this. It also sounds like MOST of the Samsung Experience people had to call Samsung Support to be able to flash it. Hope this helps
Sent From My Spiderman Themed I337
Is there anything I need to tell them for them to do it? Do I say I rooted and need to reflash the stock ROM to completely remove root? I mean, I never would have gone into an Apple Store and said I need to unjailbreak my phone, just not sure what the protocol is to get your phone reflashed by Samsung.
Thanks in advance.
bpdunsta said:
Is there anything I need to tell them for them to do it? Do I say I rooted and need to reflash the stock ROM to completely remove root? I mean, I never would have gone into an Apple Store and said I need to unjailbreak my phone, just not sure what the protocol is to get your phone reflashed by Samsung.
Thanks in advance.
Click to expand...
Click to collapse
Just tell them your company is rolling out good for enterprise and something happened to your phone where it won't install and they suggested you return it to stock firmware. And you heard that best buy can do that and could you please help me.
Went to Best Buy yesterday. The Samsung rep only comes to the local store on weekends, but one of the other folks was able to help me. I couldn't see her PC screen, but based on what I saw on my S4 screen, it looked like she was flashing the ROM. So far, no issues with Good for Enterprise, so my issue may be resolved.
Thanks everyone for the help.
bpdunsta said:
Went to Best Buy yesterday. The Samsung rep only comes to the local store on weekends, but one of the other folks was able to help me. I couldn't see her PC screen, but based on what I saw on my S4 screen, it looked like she was flashing the ROM. So far, no issues with Good for Enterprise, so my issue may be resolved.
Thanks everyone for the help.
Click to expand...
Click to collapse
Glad it worked out for you.

Rooting for a purpose, then unrooting

So, I've been at this Android thing for a very long time, and had unofficially retired from the XDA world when I bought a GS7 because I never thought rooting would even be possible. Well, now that I've rooted the phone and experimented with a custom ROM, I've come up with a question I don't know that I've ever had or read before.
I'm struggling with whether or not to stay in the rooted universe because I had come to take advantage of Samsung Pay quite often, and I didn't realize the battery difference would be what it is.
I want my phone rooted for two primary reasons, 1) to hack the provisioning so that I can use the native hotspot feature without needing a special app like FoxFi, and 2) to be able to remove all the crapware these phones come with.
So.. Theoretically here..... Shouldn't it be possible to root my phone, remove the crap, hack the provisioning, and then unroot the phone, revert back to the stock kernel, get my battery life back, and use Samsung Pay again? I never did load Samsung Pay on this phone since I've rooted it.
I saw psouza's unrooting guide but if I recall it was a destructive process..... I'd like to see if there's a way to root, set things up, then unroot and restore the phone to a state that maintains the hotspot hack and makes Samsung Pay happy.
http://forum.xda-developers.com/verizon-galaxy-s7/help/magisk-t3462583/post68962510
I had the same question. Apparently if you alter the system the stock boot image/kernal will not boot.
You will get a verity error.
bart77 said:
http://forum.xda-developers.com/verizon-galaxy-s7/help/magisk-t3462583/post68962510
I had the same question. Apparently if you alter the system the stock boot image/kernal will not boot.
You will get a verity error.
Click to expand...
Click to collapse
well poo....I wonder....since the S7 is still relatively new to hacking....I wonder if someone can figure out a workaround that would allow for tampering first, and a successful unrooting afterward. Or maybe this is a Android-wide problem...I've never really thought about this particular approach before....I've always just been always rooted, or never rooted.
I also have this hope that someone will figure out how to spoof whatever is necessary in order for Samsung Pay to still work.
I am using stang5.0liter's ROM and the only slight issue is the battery.......phone runs smoothly for me.....if Samsung Pay worked on this ROM I wouldn't even care about my initial question here.
spearoid said:
well poo....I wonder....since the S7 is still relatively new to hacking....I wonder if someone can figure out a workaround that would allow for tampering first, and a successful unrooting afterward. Or maybe this is a Android-wide problem...I've never really thought about this particular approach before....I've always just been always rooted, or never rooted.
I also have this hope that someone will figure out how to spoof whatever is necessary in order for Samsung Pay to still work.
I am using stang5.0liter's ROM and the only slight issue is the battery.......phone runs smoothly for me.....if Samsung Pay worked on this ROM I wouldn't even care about my initial question here.
Click to expand...
Click to collapse
It will not work. The original kernel for the device checks system verity. This is a part of locked boot loaders and android M+. If one bit of information is changed the original kernel will not boot. The reason we can root with the engineer kernel is it does not do this. Due to being in a "custom" status and non original kernel Samsung pay will not work nor will it ever work with this root method.
You have ruined my life with this response
So, why is the performance so bad on the engineering kernal?
spearoid said:
You have ruined my life with this response
Click to expand...
Click to collapse
Just the messenger lol. But honestly I can live without root. If I desperately needed root I wouldn't have bought a Samsung device as they are not the best for it. If you NEED root next time look more towards Nexus Phones, now Pixel and WAY over priced imo. Or research which phones have good root with an unlockable BL. For that I would stray from VZW branded devices and buy an unlocked version from the manufacturer that is compatible with VZW
bart77 said:
So, why is the performance so bad on the engineering kernal?
Click to expand...
Click to collapse
It was used for internal testing for Samsung. This was an early version of the first kernel they had for the S7, I believe and correct me if I am wrong anyone. It was fine tuned and then released but the engineering kernel was left in the dust.
Illogi.xbone said:
Just the messenger lol. But honestly I can live without root. If I desperately needed root I wouldn't have bought a Samsung device as they are not the best for it. If you NEED root next time look more towards Nexus Phones, now Pixel and WAY over priced imo. Or research which phones have good root with an unlockable BL. For that I would stray from VZW branded devices and buy an unlocked version from the manufacturer that is compatible with VZW
Click to expand...
Click to collapse
I don't need to have root. I bought this phone fully expecting to never be able to root it again. After several months of non root usage, it was very nice to enjoy some of the luxuries of a rooted phone again. I'm still torn as to which direction to go. I use the hotspot feature daily, and it works much better now than in the unrooted world for me at least.
I just wanted to see if there was any hope for having the best of both worlds.
spearoid said:
I don't need to have root. I bought this phone fully expecting to never be able to root it again. After several months of non root usage, it was very nice to enjoy some of the luxuries of a rooted phone again. I'm still torn as to which direction to go. I use the hotspot feature daily, and it works much better now than in the unrooted world for me at least.
I just wanted to see if there was any hope for having the best of both worlds.
Click to expand...
Click to collapse
I was too until the pokemon update lol then I decided no root.

Resources