Hi all,
I am writing to ask for advice on what the next step should be with my S8+. I flashed TWRP and then SuperSu, made a huge fail because I voided the warranty by tripping Knox (0x1), there is no going back. The thing is that I do not care about Samsung Pass or Samsung Pay, I want the other apps not to detected that my phone is rooted, e.g. bank apps and Google Playstore to let me through the safenet, and etc.
I decided to wipe SuperSu and unroot completely the phone, but with no avail. TWRP throws an error when flashing Magisk, that the ROM is modified, fair enough. My next step was to flash a stock ROM, but Odin throws an error after "cm.bin" saying that it failed. Could it be possible that is it due a possible older ROM? And it interprets it as a downgrade?
My phone in question is SM-G955F, with the latest software update, unlocked.
Any ideas? Thanks in advance :good:
EDIT: Okay, found the solution, uploaded custom ROM with same version of build number to internal storage, flashed with TWRP and everything is working flawlessly. The ROM was "Alexega".
Banking apps working as well, used hide function from Magisk.
Hope this helps everyone who has this problem.
Related
So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.
Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?
Full unroot under the Cleanup section
Sent from my SM-G920F
think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.
Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what
After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F
Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now
I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.
K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
timonoj said:
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
Click to expand...
Click to collapse
I haven't touched my S7 yet so I can't answer you but this could answer some of your questions:
https://forum.xda-developers.com/galaxy-s7/how-to/debloat-galaxy-s7-services-safe-to-t3432967
You don't necessarily have to root, you have to install TWRP as a custom firmware, then get the script, edit it if you don't want some apps to be removed, apply the script and it's debloated.
But I'm sorry I can't tell you if you can install TWRP without tripping Knox, I can't tell you if installing a custom Firmware will disable Google Pay etc... But I guess you can easily find that information by searching, or someone knowing more than me will help you
Installing TWRP will trip Knox if it's like every other Samsung phone I have owned that referenced Knox or warranty bit in download mode.
Hey Guys,
To be honest I am completely new to rooting and I lately rooted my phone. I used TWRP and Magisk. Then I installed Renovate Ice.
My thought was that if I unroot my phone it would be back to stock, but well, it wasn't (unrooting = uninstalling Magisk). In my appdrawer the "Rice" was still there and as I did a normal factory set for a short moment the TWRP Screen came up. After the reset "Rice" still was installed. I got into tutorials how to get back to stock S8+ and downloaded the newest (I guess that is the fault) version available for SM-G955F DBT which is Android 8.0.0 released on April the 19th. Everything worked but I couldn't use Secure Folder and as I looked for the build number it said. R16NW.G955FXXU1CRD7.
My question is:
How can I get my stock Android again with everything working?
Thank you for the help,
Henrik
BirdOfJove said:
Hey Guys,
To be honest I am completely new to rooting and I lately rooted my phone. I used TWRP and Magisk. Then I installed Renovate Ice.
My thought was that if I unroot my phone it would be back to stock, but well, it wasn't (unrooting = uninstalling Magisk). In my appdrawer the "Rice" was still there and as I did a normal factory set for a short moment the TWRP Screen came up. After the reset "Rice" still was installed. I got into tutorials how to get back to stock S8+ and downloaded the newest (I guess that is the fault) version available for SM-G955F DBT which is Android 8.0.0 released on April the 19th. Everything worked but I couldn't use Secure Folder and as I looked for the build number it said. R16NW.G955FXXU1CRD7.
My question is:
How can I get my stock Android again with everything working?
Thank you for the help,
Henrik
Click to expand...
Click to collapse
If you roote, you can NEVER again make Knox (Secure folder) get working..... it trips Knox and that is the end because it physically burns the circuit and OS knows the phone has been rooted. Everything ELSE should be working. There are problems with couple of apps, i.e. Android (Google) Pay, Samsung Pay, Samsung health etc but as I understand, you can get those to work with some hacks. But Secure folder is simply gone
Well,
I should have informed myself better...
But still, Thank you!!
Regards,
Henrik
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.
my phone got flashed with custom rom and since then my samsung pass tries to work but as soon as it tries to fill passwords it says my phone is rooted and refuses to proceed.
when i go to knox in security it refuses to switch on.
so i cannot use any of the stuff linked to samsung for this and i have tried all kinds of solutions to try to fix, flashed different roms, magisk, even wiped with odin and all has pretty wel been tried and finally went back to factory android 8, so this includes samsung tied apps to it and i cannot use samsung services since the samsung pass says my phone is rooted, so i wish to fix it but finaly i wonder if it would just be better to change my rom and go with lineage 16.1 for my sm-a520w, but cannot find copy of it for an official version.
i would prefer to fix my phone and return back to how it was before i flashed custom rom on it but i cannot seem to be able to fix knox and the false fact of samsung pass describing my phone rooted while it is not.
so can anyone help me with all this please be kind and help me fix or get rid of these problems, joel.