Related
Greetings,
Yesterday I decided to root my Note 3 (sm-n900) mainly to remove samsung's bloatware and install afwall.
Just after I rooted my phone with Odin + "CF-Auto-Root-ha3g-ha3gxx-smn900" and went for the first reboot, I noticed that my phone wouldn't boot anymore. After some hair pulling, I decided to wipe the device and after that it booted fine.
Finally I managed to remove %[email protected]! Flipboard and My magazine (a lot of crashes with sms and regular email, but worth removing!). Total happiness and a faster phone!
When I tried to enable encryption on the device, the phone just crashed again (with the same droid logo that appeared on the boot before the wipe). I came here and found some other users talking about rooting + encryption with sm-n900 saying that it's not working. (some reported that kingo method would work, but I really don't feel comfortable with king).
Now I'm downloading the stock rom, and planning to flash the note3 back to original since I have the recipe for T virus on my phone and couldn't allow it to fall on wrong hands :laugh:
Is this a bug on cf-auto-root or encryption doesn't work with rooting at all? If it's a bug, any ideas of when a fix should be around?
Thanks!
Hi eduardogsilva,
I don't know your device, but I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. If you still have issues, please have a look at my thread and let me know, if it works for you...
Cheers!
bruzzy said:
Hi eduardogsilva,
I don't know your device, but I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. If you still have issues, please have a look at my thread and let me know, if it works for you...
Cheers!
Click to expand...
Click to collapse
Thanks again bruzzy
Encryption doesn't work (properly) on rooted Samsung devices.
radicalisto said:
Encryption doesn't work (properly) on rooted Samsung devices.
Click to expand...
Click to collapse
Hello radicalisto, following the guide that bruzzy wrote, I managed to activate the encryption on a rooted note3.
So I guess that it should be fine now... Or is there any other issues besides activating encryption?
thanks
eduardogsilva said:
Hello radicalisto, following the guide that bruzzy wrote, I managed to activate the encryption on a rooted note3.
So I guess that it should be fine now... Or is there any other issues besides activating encryption?
thanks
Click to expand...
Click to collapse
It'll work, just not 100% - don't be surprised if one day it freaks out on you and doesn't let you unlock it. Happens sometimes, Although, it may be that it'll stay fine for you (luck of the draw) - with root being an exploit, the system is designed to look out for changes and freak out if it spots them.
radicalisto said:
It'll work, just not 100% - don't be surprised if one day it freaks out on you and doesn't let you unlock it. Happens sometimes, Although, it may be that it'll stay fine for you (luck of the draw) - with root being an exploit, the system is designed to look out for changes and freak out if it spots them.
Click to expand...
Click to collapse
Well, the important information that I have on my mobile is in sync, the only bad thing would be reinstalling and reconfiguring everything again, so not a big problem in loosing my phone data.
I would love to use a custom rom and completely say goodbye to touchwiz and to the huge bloatware that comes with my phone, but unfortunately, CM for note3 exynos is not available yet.
thanks
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
russ18uk said:
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
dladz said:
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
Click to expand...
Click to collapse
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
juDGEY2k10 said:
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
Click to expand...
Click to collapse
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
dladz said:
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
Click to expand...
Click to collapse
Not sure larr, i dont care myself best ask about before you jump in
Try this...
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
solution..
dladz said:
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Click to expand...
Click to collapse
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
juDGEY2k10 said:
Not sure larr, i dont care myself best ask about before you jump in
Click to expand...
Click to collapse
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
fffft said:
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
Click to expand...
Click to collapse
Dude are you going to post on every thread i make? Just to tell me to search? You're offering nothing in the way of a solution, more to the point, both the threads i've created were for unique questions, not all my questions are answered in other threads.
Please stop just commenting to say search.
yash kariya said:
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
Click to expand...
Click to collapse
My Galaxy app's application hasn't been deactivated m8, it's always been on, the second i turn on S-Health it crashes, it's because my system says custom when in download mode i believe, problem is i've now updated my OS so i'd need to reflash a stock rom via odin and then re-root if i wanted to have access to the location that the user before you mentioned. Been away from home for a few days so not had the chance, might do it tomorrow.
Thanks for the suggestion, but if I turn on S-Health now i know it'll begin crashing again.
aguarello said:
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
Click to expand...
Click to collapse
Will need root access for that, need to downgrade the OS back to a prior version. Will do it tomorrow.
Thanks for your help and to anyone else who offered something constructive.
dladz said:
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
Click to expand...
Click to collapse
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
juDGEY2k10 said:
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
Click to expand...
Click to collapse
Cheers fella, an I moved to London about 7 years ago, met a girl in London, was in Liverpool last saturday for my Stag night, dressed up like a bee gee with an afro and silver stacks, had a boss night m8, well until i fell on some stairs an near ripped my leg out of my hip joint, just spent 4 hours in the hospital getting X-rays. Worth it though
An yea Liverpool is a gorgeous City, night life is amazing we smashed it the other night
In the past, you could have root and use pay apps by disabling root in Super SU.
Apparently disabling root this time still fails due to the custom flag.
Has anyone figured out a way to bypass this yet? Even if Samsung Pay won't work, at least Android Pay which seems to be a little more lenient in terms of security.
TehPirate_ said:
In the past, you could have root and use pay apps by disabling root in Super SU.
Apparently disabling root this time still fails due to the custom flag.
Has anyone figured out a way to bypass this yet? Even if Samsung Pay won't work, at least Android Pay which seems to be a little more lenient in terms of security.
Click to expand...
Click to collapse
(Gonna sound like one of those snobby tech support people) I genuinely understand your concern and desire to want to use mobile payment applications such as Android Pay and Samsung Pay while still retaining root . However , it is actually a very good thing that these applications do NOT work while you are rooted - as far as I know , if you were rooted and still were able to uee these , it's your information that would be in danger .
As for an alternative to "disable root" or something of the sort - maybe you can try using XTouchWiz to fake system Official , then disable root temporarily . Xposed will remain installed , so the framework will be there , so you might be able to fake Official , disable root and get Android Pay to work .
I still doubt my own little theoretical method up there though , as the framework would mean modified system files which would mean it may not work . It's worth a try though .
In the event that it doesn't work , maybe when TouchWiz gets a Systemless Xposed port , then it'll work out . :3
SkyAttacksX said:
(Gonna sound like one of those snobby tech support people) I genuinely understand your concern and desire to want to use mobile payment applications such as Android Pay and Samsung Pay while still retaining root . However , it is actually a very good thing that these applications do NOT work while you are rooted - as far as I know , if you were rooted and still were able to uee these , it's your information that would be in danger .
As for an alternative to "disable root" or something of the sort - maybe you can try using XTouchWiz to fake system Official , then disable root temporarily . Xposed will remain installed , so the framework will be there , so you might be able to fake Official , disable root and get Android Pay to work .
I still doubt my own little theoretical method up there though , as the framework would mean modified system files which would mean it may not work . It's worth a try though .
In the event that it doesn't work , maybe when TouchWiz gets a Systemless Xposed port , then it'll work out . :3
Click to expand...
Click to collapse
Thanks for the tips, I'll give them a try tonight. Though, do you happen to know of a way to do a full backup then restore on the S7 w/o root?
With root I could use Titanium backup or flashfire. SmartSwitch doesn't do app data
TehPirate_ said:
Thanks for the tips, I'll give them a try tonight. Though, do you happen to know of a way to do a full backup then restore on the S7 w/o root?
With root I could use Titanium backup or flashfire. SmartSwitch doesn't do app data
Click to expand...
Click to collapse
Don't know of any other method other than Smart Switch but like you said , it doesn't do App Data . I think you could manually copy the files from Internal > Android > Data/Obb for certain apps but other than that , nope . Sorry .
Not without root at least .
I'm afraid that to get pay apps functioning again you have to Odin the stock image. The custom flags prevent you from just un-rooting and useage...it's a catch 22
Sent from my SAMSUNG-SM-G935A using Tapatalk
android pay works on root. Worked on my note 4 and my s7 edge that was purchased and rooted yesterday
In short, Pokemon GO's new update is just taking a massive dump on it's rooted supporters and we can't play the game on the new update. Would our root be able to hide it and allow it to played on our phones with root, still?
Rooted s7 edge.... Pokémon go running strong. No issue. App is up to date.
ShadowyStorm said:
Rooted s7 edge.... Pokémon go running strong. No issue. App is up to date.
Click to expand...
Click to collapse
Are you on the new update with the buddy system? Cause the update didn't full rollout yet...
No, must not have rolled out in America. Are you running xposed?
ShadowyStorm said:
No, must not have rolled out in America. Are you running xposed?
Click to expand...
Click to collapse
Yeah I am, but I read somewhere that Magisk requires an unlocked bootloader, but I don't know if the Systemless portion is different.
Most people would say, forget the game, and keep root, but I'd like to keep both, as I've put a lot of time into the game to have this crappy company screw us like this...
If xposed and Pokémon is incredibly important to you I suggest trying the following. There's a work around for snap chat. Same scenario. You have to install and log into snap chat before installing xposed. Get it to build cache so it doesn't do the device check then install xposed. Profit. I'm not sure but it's worth a try.
I had it working then it ****ed my phone up couldn't get it again
ShadowyStorm said:
If xposed and Pokémon is incredibly important to you I suggest trying the following. There's a work around for snap chat. Same scenario. You have to install and log into snap chat before installing xposed. Get it to build cache so it doesn't do the device check then install xposed. Profit. I'm not sure but it's worth a try.
Click to expand...
Click to collapse
The problem is that the new version of poGo is using the same SafetyNet check that Android Pay does to check for root.
Apparently, the only thing that works for this is Magisk (at the moment).
The latest Pokemon Go app is using SafetyNet checks, so this goes far beyond the Snapchat workarounds.
Ah. I wasn't aware don't have the update yet
Just got it...
ShadowyStorm said:
Just got it...
Click to expand...
Click to collapse
And? You're screwed like the rest of them?
Squall429 said:
And? You're screwed like the rest of them?
Click to expand...
Click to collapse
Accurate.
So the question is can we flash magisk with flashf ire?
Or would something like rootcloak possibly work?
More and more every day I hate niansh*t and it feels like it's no different than if crapple themselves have made the app.
xdathekilljoy said:
So the question is can we flash magisk with flashf ire?
Or would something like rootcloak possibly work?
More and more every day I hate niansh*t and it feels like it's no different than if crapple themselves have made the app.
Click to expand...
Click to collapse
Root Cloak won't work. I tried that on 2 different Samsung phones :/
I'm on tekx rom and when I tried to unroot via SU my s7 edge would only boot into recovery... so I restored a backup.
It's awefully silly to keep rooted users from playing. Seems like they run out of ideas to find GPS spoofers lol
I have rooted my S7 Edge SM-G935F using chainfire-auto-root ODIN method
^ New Pokemon Go update does not work with this root method - I have used rootcloak from xposed - also does not work. You need to root using MAGISK so here is my question.
1. How do I unroot my phone that I rooted using ODIN Chainfire-Auto-Root file?
2. How do I root S7 Edge SM-G935F using "MAGISK" so i can play pokemon go after this new update?
has anybody tried rooting S7 Edge SM-G935F using MAGISK method yet? does it work? please reply and please give a guide or step by step i am a newb
JustSaif said:
I have rooted my S7 Edge SM-G935F using chainfire-auto-root ODIN method
^ New Pokemon Go update does not work with this root method - I have used rootcloak from xposed - also does not work. You need to root using MAGISK so here is my question.
1. How do I unroot my phone that I rooted using ODIN Chainfire-Auto-Root file?
2. How do I root S7 Edge SM-G935F using "MAGISK" so i can play pokemon go after this new update?
has anybody tried rooting S7 Edge SM-G935F using MAGISK method yet? does it work? please reply and please give a guide or step by step i am a newb
Click to expand...
Click to collapse
I'm afraid I have to tell you that over on reddit the developer of magisk said that Samsung devices are only supported if they're on a "custom" kernel.
Although I don't know at which point a kernel stops being stock :/
Source:
https://m.reddit.com/r/pokemongodev/comments/52j80f/hello_im_the_developer_of_magisk/
hoeni said:
I'm afraid I have to tell you that over on reddit the developer of magisk said that Samsung devices are only supported if they're on a "custom" kernel.
Although I don't know at which point a kernel stops being stock :/
Source:
https://m.reddit.com/r/pokemongodev/comments/52j80f/hello_im_the_developer_of_magisk/
Click to expand...
Click to collapse
I DID IT, I CAN PLAY POKEMON GO WITH A JOYSTICK ON MY S7 EDGE :laugh::laugh:
JustSaif said:
I DID IT, I CAN PLAY POKEMON GO WITH A JOYSTICK ON MY S7 EDGE :laugh::laugh:
Click to expand...
Click to collapse
So... You're using the NEW version with the buddy Pokemon and able to use Xposed/Joystick as well and... actually login!?!?
If so... How did you do it?
I'm curious as well. I had to reflash back to stock due to bootlooping so I'm a little more interested in this subject now that the icy plunge or returning to stock has already been made.
Hello, I just installed TRWP and custom firmware, so my knox obviously is broken. I was wondering is there a way to make samsung pay work yet? Or maybe Android pay? I really liked nfc payments.
If you have a gear watch you may be able to sideload an older version of SPay onto each and have a working SPay on your watch.
Not sure if that technique works for this device or only non Samsung devices though...
But otherwise, no you won't have working SPay on your 0x1 device. Android Pay probably, yes.
Magisk could be working I guess
Gesendet von meinem LG-D802 mit Tapatalk
murok9042 said:
Magisk could be working I guess
Gesendet von meinem LG-D802 mit Tapatalk
Click to expand...
Click to collapse
Can you explain please? Is there a special magisk module for nfc payments?
kazzaqov said:
Can you explain please? Is there a special magisk module for nfc payments?
Click to expand...
Click to collapse
The way Android Pay works is by using a check called SafetyNet. Magisk fools the system with root by being a systemless root so nothing is tampered with, and in a nutshell, SafetyNet passes its checks and such Android Pay works.
Samsung Pay uses a different set of checks which fail majority of the time. There's been a few instances where people have been able to use Samsung Pay with the use of Magisk but is patched rather quickly.
TehPirate_ said:
Samsung Pay uses a different set of checks which fail majority of the time. There's been a few instances where people have been able to use Samsung Pay with the use of Magisk but is patched rather quickly.
Click to expand...
Click to collapse
Samsung Pay stores info in KNOX, so blowing your e-fuse kills Samsung Pay for the life of the device. Doubt there's a way around it.
Can i still usee samsung pay with my rooted s8
will there be any way i can still use samsung pay with my rooted s8 plus
luke1517 said:
will there be any way i can still use samsung pay with my rooted s8 plus
Click to expand...
Click to collapse
*Face palm* >_<
luke1517 said:
will there be any way i can still use samsung pay with my rooted s8 plus
Click to expand...
Click to collapse
Nope
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
It's a fuse located on mainboard which is being "blown" after unlocking the bootloader / rooting. So there's no way to revert this unless you change the mobo on it.... Which I doubt ?
With Magisk, Android Pay is working flawlessly. I'm using it all the time on Note8 port.
jonny908 said:
It's a fuse located on mainboard which is being "blown" after unlocking the bootloader / rooting. So there's no way to revert this unless you change the mobo on it.... Which I doubt
With Magisk, Android Pay is working flawlessly. I'm using it all the time on Note8 port.
Click to expand...
Click to collapse
Ah, thought it wasn't a hardware thing and just code.
How are you getting that to work? I have magisk 15.2 on the s8+ and hidden from all the apps i can think of in magisk and it still tells me access denied blabla
Bresch said:
Ah, thought it wasn't a hardware thing and just code.
How are you getting that to work? I have magisk 15.2 on the s8+ and hidden from all the apps i can think of in magisk and it still tells me access denied blabla
Click to expand...
Click to collapse
It just works... Using 7.1.1 rom.
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
Nope and never will work. It's a hardware efuse on the main board of the phone. It's literally trips and burns out. You can't flash stock or anything to revert it.
The only way you can revert it is to buy a new motherboard.
Samsung Pay
callumbr1 said:
Nope and never will work. It's a hardware efuse on the main board of the phone. It's literally trips and burns out. You can't flash stock or anything to revert it.
The only way you can revert it is to buy a new motherboard.
Click to expand...
Click to collapse
I just rooted my S8+ with Party Cyborg it is a 955U1 and I did not like the fact it could not use health or Samsung pay with my S3 so I put back the orig factory rom and all is working now, Before I factory defaulted it the my device has been rooted and Samsung pay will not work was keeping me from using it but when I went back to factory it works great now. The phone was on V2 firmware not sure if they did away with the efuse or what but I was glad....
Jabercrombie1 said:
I just rooted my S8+ with Party Cyborg it is a 955U1 and I did not like the fact it could not use health or Samsung pay with my S3 so I put back the orig factory rom and all is working now, Before I factory defaulted it the my device has been rooted and Samsung pay will not work was keeping me from using it but when I went back to factory it works great now. The phone was on V2 firmware not sure if they did away with the efuse or what but I was glad....
Click to expand...
Click to collapse
Because rooting snapdragon doesn't trip Knox.
im sorry to necropost, but has anything developed in the 10 months since this was last discussed? i miss samsung pay on my gear s3 frontier
youdoofus said:
im sorry to necropost, but has anything developed in the 10 months since this was last discussed? i miss samsung pay on my gear s3 frontier
Click to expand...
Click to collapse
You can use samsung pay on your gear s3 on a rooted phone by hiding samsung pay (gear) in magiskhide and setting it up like normal, make sure you pass safetynet
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
Unfortunately, once you rooted your Sammy device you can't get features such as Samsung Pay back due to the blown e-fuse. However, rooting with Magisk will let you use Google Pay. I've been using it basically every day for the past 6 months and not once have I missed Samsung Pay. If by any chance your phone doesn't pass the SafetyNet check there is always modules such as MagiskHide Props Config which will let you change your fingerprint to a certified one, therefore passing the SafetyNet check.