Instead of stock firmware R16NW... - Samsung Galaxy S8+ Questions & Answers

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

Related

[Q] how to update a 5.0.1 rooted?

Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.

So im assuming i just messed up myself here

I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build
am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/
ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...
SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.
Very Informative

Android Pay & custom rom

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.

Phone no longer updates?

Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Same here. I rooted my phone, installed TWRP but battery drain and apps not working properly made me go back to stock. Now I cant get any updates. I flashed APEQ fw yesterday dated June 8 but still dont get the June 17 updates.
I used Smart Switch to do an Emergency Reinstall of the firmware. Had to start over from scratch with my phone... It installed the lastest firmware though.
Been researching as much as I can online and it seems the consensus is simply unrooting the phone does nothing. You have to factory reboot. Tripping Knox won't stop you from getting updates but an unrooted phone that wasn't factory reset still won't get updates. Fun times. Last time I root my phone... Things aren't the same since I last rooted in Android 4.0. Now too many apps and updates etc. check for root and stop working if they detect it.
Luuthian said:
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Click to expand...
Click to collapse
Did you use Odin to flash back to stock?
malek777 said:
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I used the Emergency Recovery function of Smart Switch which, from my understanding, is basically the same thing. I know how to use ODIN but it seemed a better idea to go with the official solution. Guess I'll find out if it worked once the June update is available in Canada.

Can I update my w200A (AT&T) to NXH21O?

I got a notification this morning saying google play services wanted to update. I thought the google play services app itself was wanting to update, so I went ahead plugged in my watch and let it start.
As it turns out, it was the official update from AT&T to android wear 2.0! Finally! I already had android wear 2.0 on my watch, I flashed it using a kdz that someone had uploaded that had already gotten it on a w200L.
Anyway, once I realized what it was doing I was worried it might brick since I had already updated it previously to a different android wear 2.0 version.
I'm happy to report that it updated successfully. I still had stock recovery so that remained the same. I had used TWRP before, but only booted twrp recovery to flash supersu. I never flashed TWRP to my device, I'm not sure if having TWRP recovery installed would've caused the update to fail.
Changes: I lost root access. That is OK because I only rooted my watch so I could add a new APN to use my watch with a Freedompop sim card. Actually it was a good thing because before the update Android pay didn't work because of my root access, and after the update android pay allowed me to add a credit card and looks like it will work, since I no longer have root, even though my bootloader is still unlocked!
Anyways, I just thought I'd bring this up in case someone else has a question about it. My experience may differ from yours, I am not responsible if you have different results.

Categories

Resources