So, I wanted to root my s7 edge, from sprint, and I used odin and I did it all mainly right, except. It never installed supersu because of some disk error? Im not very sure. The phone worked perfect before now the fingerprint wont work, and samsung pay wont. When I boot the phone up it says custom. How do I get rid of this and unroot it? Im not very tech savvy at this and I would reallt appreciate the hell because I havent even had the phone for a day and I can hardly use it now because of the root.. Please help me
clayisgod said:
So, I wanted to root my s7 edge, from sprint, and I used odin and I did it all mainly right, except. It never installed supersu because of some disk error? Im not very sure. The phone worked perfect before now the fingerprint wont work, and samsung pay wont. When I boot the phone up it says custom. How do I get rid of this and unroot it? Im not very tech savvy at this and I would reallt appreciate the hell because I havent even had the phone for a day and I can hardly use it now because of the root.. Please help me
Click to expand...
Click to collapse
When you root your phone, most roots will break Knox (the security app that is used for the finger printers samsung pay and many other apps that require security verification) You will have to reset to stock or find an unroot to fix it. Here is a link to a stock room it was the newest I could find on the sprint S7 edge forum: https://forum.xda-developers.com/sprint-s7-edge/how-to/sm-g935p-g935pvps4bqg1-stock-odin-t3660973
Considering i need 935p not 925 I dont think it'd work, how would I reset to stock? And or how would I unroot? I tried using kingoroot to unroot but that did nothing
Related
Hello all,
This is my first Samsung device, the Galaxy S7 Edge Dual sim (SM-G935FD) bought from UAE.
I used to install TWRP and root every android phone I had before, so I am still not sure whether to root this one. I already have the files required for rooting, but I noticed that there are 2 ways of rooting:
1. Using Odin to install TWRP and then from there install SuperSU.
2. CF-Auto-Root.
What is/are the difference(s) in both methods?
My other question is: I read that rooting will trip Knox, and there is NO WAY to get it back to normal even flashing the original ROM. Is that the case?
One last thing, I am now stuck in the download mode (turned off the phone, pressed "Volume down", "Home" and "Power"), I did that just to check the info on the top left (model and warranty void...) but I cannot seem to restart the phone even by pressing the power button for more than 20 seconds, how can I turn the phone off then back on?
Thank you
*****EDIT*****
Regarding my last question (stuck in Download mode), pressing the same combination got me back to start the phone normally
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot.... As of right now I haven't rooted because there aren't to many Roms available... I'm sure I will cause I miss titanium backup and the ability to get rid of all the bloat ware (especially Facebook & Microsoft ****).... The phone runs great without root and battery is excellent.... The last reason I was waiting was Samsung pay won't work with tripped Knox counter.... I live in the US but have the international 935F... So it doesn't look like this variant will support Pay anytime soon.... Probably gonna root when development picks up a little....
*edit*... Always have a stock rom just in case saved to your computer just in case... That would of saved me lots of freak outs and headaches years ago... Now it's the first thing I do before Rooting or flashing anything to my phone
Galaxy S7 edge
Kjc99 said:
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot
Galaxy S7 edge
Click to expand...
Click to collapse
Thank you for the detailed reply.
I made a research yesterday on Knox (as I said, this is my first Samsung device), and I just wanted to make sure that I understood things properly.
So now after reading, tripping Knox will disable Samsung Pay (I do not have it in my country) so that is not going to make any difference. But, what about paying using the fingerprint sensor in Google Play, will it stop working if Knox is tripped? I also use the fingerprint sensor to login to my mobile banking app (instead of typing the password every time I want to login), will that stop too? I guess not but again just to be sure.
Thanks a lot once again.
I know when I rooted my S6 all the fingerprint stuff still worked so I dont think it will make a difference... Im not sure with the S7 edge but I would think it would still work cause all of those require a typed password before you use your fingerprint(1st setup only) Then use your fingerprint there after... .. Doesn't have anything to do with Knox
Galaxy S7 edge
yep, it all still works. just Samsung pay & private mode.
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Mal-0 said:
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Click to expand...
Click to collapse
Make sure samsung kies or samsung usb drivers are installed on your pc.
Download stock marshmallow firmware and flash through odin .this method does not require root.
After flashing dont let the phone boot just go to recovery and wipe cache+wipe data factory reset then reboot.
Wait 10 to 15 minutes.
Stock rom link.
https://www.androidfilehost.com/?fid=24651430732238073
Extract file and choose AP tab in odin.
Upload firmware file then connct device via usb cable to pc.
Hit start in odin.
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Mal-0 said:
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Click to expand...
Click to collapse
Thanks for the compliment. you just made me feel like i am a Hercules :victory:
If you want my advice dont ever take ota updates.
Just go to www.sammobiles.com/firmwares and grab latest rom for your model and flash in odin as you did.
Latest rom comes with the same security patch update the 1 comes in ota.
I personally do this way all the time.
Hope that helps and have a good day.
I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.
Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.
So since I had OEM unlock enabled after disabling it, it passes and safetynet now.
I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???
Very weird. Working just fine on my rooted s8+ with magisk.
I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk
I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe
xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?
Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it
Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?
mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?
I recently have rooted my s6+ G928C with build number G928CXXS3CQH1.
Everything work fine except for secret mode in Samsung internet that I knew not working with rooted device.
Although, I didn't find anypost that said samsung pass also not working, I just want to ask thak anyway to make
samsung pass working along with root? Thanks in advanced.
Please help me, any custom kernal or way to fix this?
As far as I know it will never work... but you could try magisk hide but dont get your hopes up.
Flash the superuser uninstall zip when you want to use it and reroot when you need root? Or get magisk set up so you pass safetynet
Hi everyone,
Straight to the point, I bought Samsung S7 Edge second-hand and I get trouble in lagging and always show notification of "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes."
This problems also tangled me when I'm using Samsung Health...:crying::crying::crying:
As basic situation, I know it had been root and unroot before I bought this phone.
Is anyone can help me to get rid off?:crying::crying:
samsung health, android pay and secure folder won't work on device that has root or have been rooted. firstly, to get rid of the annoying notification, install titanium backup,grant root rights if you are still rooted, locate the apk "security log agent and freeze it. If not, install latest twrp and root with magisk or supersu, just search online how to do so. lastly , to get rid of the lagging and notification . flash latest stock rom via odin and everything would be fine ..just remember that your knox is tripped forever so don't expect samsung health would work after removing root or getting back to latest stock ..hope this helps and good luck
CrankyOutlaw said:
samsung health, android pay and secure folder won't work on device that has root or have been rooted. firstly, to get rid of the annoying notification, install titanium backup,grant root rights if you are still rooted, locate the apk "security log agent and freeze it. If not, install latest twrp and root with magisk or supersu, just search online how to do so. lastly , to get rid of the lagging and notification . flash latest stock rom via odin and everything would be fine ..just remember that your knox is tripped forever so don't expect samsung health would work after removing root or getting back to latest stock ..hope this helps and good luck
Click to expand...
Click to collapse
Hi, I finally solve my problem by Upgrade my phone Android version. And my phone status now show OFFICIAL and all Samsung Official Application are able to use now!
RichardGuyz said:
Hi, I finally solve my problem by Upgrade my phone Android version. And my phone status now show OFFICIAL and all Samsung Official Application are able to use now!
Click to expand...
Click to collapse
You gotta be kidding me. All Samsung Official apps are working you say? Samsung Pay, Health etc?