Database Develop

Help remove Retail Mode Samsung Tab S2 SM-T810

Hi to everyone. I have a Samsung Tab S2 SM-T810 with Android 5.1.1 / Kernel 3.10.9 that has retail mode on, it was a demo in a store. Is there anyway to remove this from the device? I already try doing a factory reset with stock firmware and odin and it stills the same. I think it has some kind of software installed on the ROM memory that prevents it to fully restore and wipe the retail mode app. Thanks in advance.

Please do a search this has been covered plenty of times already. There is no need to repeat over.

ashyx said:
Please do a search this has been covered plenty of times already. There is no need to repeat over.
Click to expand...
Click to collapse
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.

huntejes said:
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
Click to expand...
Click to collapse
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.

ashyx said:
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
Click to expand...
Click to collapse
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?

huntejes said:
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
Click to expand...
Click to collapse
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.

ashyx said:
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
Click to expand...
Click to collapse
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.

Ok so ive got the Sm-810 and i was experiencing the same issue of it not letting odin flash to stock OR install twrp etc. etc. and i was going to give up and i **** you not i was trying to get into the recovery to see if i could jostle some solution loose and it fixed itself !! It was booted into download mode and i unplugged the cable and pressed and held power+vol down and as soon as the screen went black i did the same thing again and then i mustve messed up cuz it booted into the os but i repeated the process from there and no kidding after 2 or 3 cycles of power+vol down i got a blue screen with an android on it and it flashed and showed a dead android with the caution! sign and the next screen showed the regular android with the word "erasing" underneath and vio'la no more retail mode. After this Odin worked and let me autoroot and so on an so forth. sorry for my long post i just though i should share

I think the major issue is that OEM is disabled and there is no way to turn it on. So most of the solutions are a no go... So any other suggestions on make this work?

huntejes said:
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Click to expand...
Click to collapse
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\

My husband and I also ran into the problem of having our Samsung Tablet E nook 2017 model stuck on Retail Mode.. we tried EVERYTHING we could possibly think of after the 5444 password didn't work. We rooted, we downloaded "easy uninstalled" apps, did the hard reset with the 3 button deal.. nothing! Then we finally came across a few passwords we were willing to give a try.. so when you go to the retail mode bar and it prompts you for a password to uninstall try blue. The word BLUE but in lowercase.. and it worked! We were then given tons of options and finally got that crap off our paid for device. I'm 100% sure that any device purchased from Best Buy and stuck in retail mode will use the password blue. A few other passwords we came across that might be worth a shot if blue doesn't work are: galaxy and unlimited. (Each by themselves as one password) Well good luck, we know how frustrating this has been!!

Skapino said:
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
Click to expand...
Click to collapse
Dude, I have a SM-t560nu and I feel your pain. For months I was trying to find a solution and had to deal with obnoxious fools who couldn't get it thru there heads that this was NOT the usual Samsung Retail Mode but a special piece of software that puts the tablet into a rolling cycle of 2-10 minutes, shuts off all developer options, locks frp and basically makes anything you do null and void. I tried every password Imaginable including "BLUE," "5444" and the oft repeated "M729Q16K8546" all to no avail.
Here's the deal: this IS unique software and you'll find it at retailsamsung.com. (I can't post the actual url because of the new user rules, which is kind of funny because I've been a member for about 10 years but I don't think I've ever posted anything.)
Go there, search your device and download 2 items: One will be your installation package (for instance "Samsung_Retailmode_Global_Common _141006.apk") and the other will be called "RetailMedia.main." Download both to na sd card, put the sd card in your device, move the programs from the sd card to the download area ON the device. Now start your device, got to the download area and tap on the first program, the apk. Enter 5444 as your password, follow the instructions. the second password will be "M729Q16K8546." This will remove the Retailmode software and most likely trigger a Samsung lock. Go to Sammobile, download the original firmware and congrats, your new tablet is finally working right.
I was wary of downloading software from such a plain site, especially one I've never heard of but I figured after 6 months of no luck and my new tablet just sitting in a drawer, unusable, what did I have to lose? Well, it works, i'ts awesome and it's like new.
Hope this helps.

Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.

I hope I'm not posting on a dead thread. I saw a good deal on a T813 in retail mode (will provide link if needed, it's on a very popular and legal south american online store). The thing is, as explained by the vendor, someone attempted to remove the retail app and now is stuck on a countdown in the lock screen. After some time it reboots itself. I've been reading a lot about the topic and the main problem seems to be the OEM unlock off. Now apparently I won't be able to access any feature of the device at all. I thought maybe I could reinstall the retail mode and get back the app or just boldly odin flash twrp and a stock rom risking myself to an FRP lock.
However I thought better ask advice first, so what do you think? Any help is greatly appreciated.

Well, I bought it and first day has been no success. I can access guest user, could log in to my ggl account and downloaded some apps. OEM, third party apps and developers are out of reach and cannot access main account. No sign of retail app.
Flashed new stock rom, FRP asks for a password, tryed 5444 Mz$%"#$%& blue galaxy unlimited with no luck. Attempts to flash twrp via odin fail due qst (?) error. I guess because is OEM locked. Flashed some older rom and still a countdown that doesn't let me in in main account.
So far, this is my progress with it. Any advice to flash twrp, remove frp lock and/or remove retail mode? Thanks in advance

_Iffer_ said:
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
Click to expand...
Click to collapse
Did the same, although I had to use the older ap_SamsungRetailMode_Global_Tab_A_L_v1.0.4_15031100_M15031100_P0.apk with my SM-T550 (Galaxy Tab A (2016) 9.7") - I also had to stop the existing RetailMode Service from running by opening applications, swipe across to Running Applications, and tap on the Retail Mode executables to disable the "Sta" service. Annoyingly if you accidentally get the password wrong then it'll reset itself and delete the newer APK and you have to start the whole process over again

Could anyone at least point me in the right direction please? I can't access the main user of the tablet because there's a lock on the screen saying "Try again in 1440 minutes" which is a day. It self reboots every 5 minutes and each time the 1440 minutes thing resets. I booted in safe mode, now it doesn't reset and countdown is set for the next 4 hours.
Please, any light on the matter will be great. I have 4 days to return and I wouldn't like to do it cause it was extremely cheap unless, but I don't want to end with an expensive brick either.

Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.

Hi guys,
I have a galaxy tab and sm-t561, which presents the problem of retail mode that you can not remove in any way even with odin, I wanted to ask, how do I install a version of retail mode via apk? I downloaded the new version of retail mode but how do I install it?

whchapma said:
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Click to expand...
Click to collapse
i just follow your instructions and awesome mine is unlock now and downloading the update to android 7.0 thanks bro

[Q] Update unlocked SM-G925A

Hey, I can't update my SM-G925A to marshmallow 6.0.1, probably because it's unlocked. I thought about Odin but I couldn't find the right ROM online. Can someone help me find the right ROM or help me update it in another way? Thanks

Marshmallows is not available yet for G925A. Maybe will get it 2 years from now.
Sent from my SAMSUNG-SM-G925A using XDA-Developers mobile app

Marshmallow was just released for the G925A today, G920A yesterday. I've been calling AT&T every ****ing day for the past three weeks. FINALLY, the update is here. I'm still waiting for it to hit my region though. I would love a firmware file.

If that's true, super happy here.
Sent from my SAMSUNG-SM-G925A using XDA-Developers mobile app

At this point, I'm honestly not sure. Probably called AT&T over 20 times just today and each rep seems to be more stupid than the last. Some say it's out, others have no clue. As a new member, I'm not allowed to post the link, but it says on samsungs website that the AT&T S6 (non edge) is running Android 6.0.1 Marshmallow. If you'd like to see for yourself, go to samsung.com, in the search box type "g925a marshmallow" and click on the one that says something like "what software is my Galaxy s6 running?"
I am so done with this carrier. Never will I buy a phone locked to AT&T again.
Sent from my SM-T710 using Tapatalk
---------- Post added at 04:01 AM ---------- Previous post was at 03:55 AM ----------
Just got off the phone with a rep that seemed to know what he was talking about. He did confirm that the S6 has started rolling out, but the edge has not. He also said that if the s6 is out, the edge shouldn't be more than a week behind. He told me he'd call me as soon as it's released and as soon as I get the news, I'll update you guys. I know how frustrating this is!
Sent from my SM-T710 using Tapatalk

G925AUCU3CPC2 saw it on a site called thunderztech but no link yet...

vicobh said:
G925AUCU3CPC2 saw it on a site called thunderztech but no link yet...
Click to expand...
Click to collapse
Saw the same page you're talking about. Sounds like the OTA should be rolling out in the next couple of days.

Instructions on how to get 6.01 on G925A
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!

Tried both ways (Instructions on thread and attached to file) and no luck as of yet. I will retry this afternoon. has anyone else tried this yet?

Seems dumb but the only thing that I needed to do to get it to accept the ota.zip was to reboot. My guess is that windows has to be rebooted after installing adb/fastboot.

gmccowan1 said:
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!
Click to expand...
Click to collapse
For some reason it doesnt work for me
like its still stuck in 5.1.1

Worked perfectly for me had no problems what so ever........Thanks a bunch

if i do this update, will my phone be still remain unlocked or it will get locked again after this update ?

Hi, would like to know if this will lock my phone back to AT&T?

G925AUCU3BOI2 flash with G925AUCS5DPJ1
adrianneedshelpplease said:
For some reason it doesnt work for me
like its still stuck in 5.1.1
Click to expand...
Click to collapse
my s6 edge build number G925AUCU3BOI2 with Android V5.1.1, but i want to have Marshmallow update for this build. this is AT&T unlocked phone so OTA not available. and i have not found any stock files for this build. can i flash with build G925AUCS5DPJ1 stock files? will that works in my phone?
Reply ASAP. i am waiting on this

Samsung Experience Kiosk is a No-Go
AT&T unlocked my Samsung S6 Edge, at my request. They offered me an out last February when
they changed the DATA plan pricing structure. When Marshmallow was released I took my phone
the AT&T store where I purchased it (with the receipt) for the update. They would not touch my
phone since I was no longer a customer. So I called Samsung Corporate several times and was told
that since the phone was out of warranty, there was nothing they could(would) do. The last
Samsung rep I spoke to suggested that I take it to a Samsung Experience Kiosk in Best Guy for the
update. I took it to Kiosks in two different states and both refused to touch the phone for fear of
being sued should they "Brick" it. I finally got it updated by refusing to let them service any other
customers until it was done. It seems that the Kiosks are sub-contractors and not store employees.
The store manager got involved because I was costing him sales. To make a long story short, I now
have Marshmallow but have not gotten any security patches in a year. If you decide to try a Samsung
Experience Kiosk, be prepared to stand your ground - even then its a coin toss whether you get the
update.
.

Mixed Results when ROOTING

Hi Gents,
ok so we all know by now that waiting 7 days unlocks the OEM option for the N8 950F, i want to root, my concern is that i have been reading and see that results are mixed, i have seen that flashing a custom FW has soft bricked some phones and you will have to flash back to official FW and wait yet again for 7 days for OEM to show up in dev options....
what i want to know is whats the sure fire way to get it to work (ROOTand CFW) because i dont wanna end up losing the OEM option and then have to restore OFW?
please let me know your thoughts and what you did to have a successful first time flash, my note model is N950F/DS.

mafioso345 said:
Hi Gents,
ok so we all know by now that waiting 7 days unlocks the OEM option for the N8 950F, i want to root, my concern is that i have been reading and see that results are mixed, i have seen that flashing a custom FW has soft bricked some phones and you will have to flash back to official FW and wait yet again for 7 days for OEM to show up in dev options....
what i want to know is whats the sure fire way to get it to work (ROOTand CFW) because i dont wanna end up losing the OEM option and then have to restore OFW?
please let me know your thoughts and what you did to have a successful first time flash, my note model is N950F/DS.
Click to expand...
Click to collapse
You don't gain anything anymore from rooting that you used to. The phones are already lightning fast.
- R. Kruse Ludington:
Galaxy Note 8<-5<-3<-S3<-Nexus; Droid X; HTC HD2<-Touch Pro 2<-Tilt<-8525; O2 XDA II<-XDA

mafioso345 said:
Hi Gents,
ok so we all know by now that waiting 7 days unlocks the OEM option for the N8 950F, i want to root, my concern is that i have been reading and see that results are mixed, i have seen that flashing a custom FW has soft bricked some phones and you will have to flash back to official FW and wait yet again for 7 days for OEM to show up in dev options....
what i want to know is whats the sure fire way to get it to work (ROOTand CFW) because i dont wanna end up losing the OEM option and then have to restore OFW?
please let me know your thoughts and what you did to have a successful first time flash, my note model is N950F/DS.
Click to expand...
Click to collapse
That's cause no one knows exactly why it disappears yet or has a valid fix for it. So far it seems like people are having luck with krabman's method.
KruseLudsMobile said:
You don't gain anything anymore from rooting that you used to. The phones are already lightning fast.
- R. Kruse Ludington:
Galaxy Note 8<-5<-3<-S3<-Nexus; Droid X; HTC HD2<-Touch Pro 2<-Tilt<-8525; O2 XDA II<-XDA
Click to expand...
Click to collapse
In the past, people mainly rooted for speed tweaks & themeing but those aren't the only reason for root. Speed tweaks & themeing were never the main reasons why I rooted.

Like many I spent time in jail waiting for my OEM unlock. How I spent that time was trying to work around not having root and it was a miserable failure. When talking about the need for root I think it's best that the conversation first be understood to be subjective. A person that doesn't do anything that requires root will feel that it is unnecessary, those that do will consider it vital as a means to get where they're going.
There are many, many, people who said "you don't need to do that" in regards to getting root on these devices who went down in flames. No timer on OEM unlock and not a big deal, you try again until you get it right. We get one try and getting it wrong means you have reset your timer and you're waiting a week. Wait that week and you get one try, failure means another week. A person can repeat that cycle as many times as they want, I'd suggest going all in the first time because no one knows exactly which steps are not needed yet although we have ruled a few out. One thing that is apparent is once you have the first rom install in the rest can be done following normal rom installation procedure so long as they're clean flashes. I haven't tried any dirty flashes but for the same rom I'm thinking it will work, of course when the time comes I might be proven wrong. I'm hoping someone else will get there first and I can take advantage of their experience.
That being said in general the process begins by flashing TWRP in odin. You must leave odin and go directly to TWRP, failure to stop the boot at recovery means a certain binaries error and a week wait. Once you are in recovery you must stay there until you have finished installing a rom that has been de-knoxed. Pay attention to holding the buttons on the phone while you start the TWRP flash as described in the TWRP thread. If you untick reboot in odin then the only way out is to hold volume down/ power which will tell the phone to reboot into system. You must then quickly switch to volume up/bix/power during a small window in order to get the phone to go to recovery. If you miss it nothing can stop the phone from continuing to boot and you have just got a week wait before your next try. If you don't untick restart you can try the same thing when odin automatically reboots the phone after the flash. If you miss it you will get the binaries error and be waiting a week. People have missed it both ways. There is a reason that the TWRP instructions specifically state to prepare odin, hold the vol up/bix/power buttons and continue holding them while you press the button in odin and keep right on holding those buttons all the way through until the phone boots into TWRP. This makes it a sure thing, the other way you may or may not succeed. Lastly we've proven you don't need to remove your SIMs on subsequent rom installs but it remains a question with the first install as there are conflicting reports. If it were me I'd pull them and not put them back until I was fully up and running on the other side. You will need to pull at least Sim 2 in order to put in the micro SD with your rom, verity, and root firmware for use in TWRP no matter what. Feeling frisky and you want to leave Sim 1 in then please report your results in the OEM unlock thread.
So... To install a rom you will begin by following the TWRP instructions to the letter including the format all the way through the process until the end. Some will say you don't need to flash the no-verity, ordinarily I'd agree with them as it is flashed as a part of both the SU and magisk flash but in this case we know that following those instructions in exacting detail works as a first step but not doing so has been a failure for many. Because few have followed the same steps plus or minus a detail from the known working method we don't know exactly which things are unneeded so if it's me I would just follow the known working method. As always those wanting to advance our knowledge by trying something else should report their results in the OEM unlock thread. When you reach the end of the TWRP installation instructions you will remain in recovery and flash your rom and then factory reset. Then flash either magisk or SU again depending on which rom and which root method you're using. Once root has been reflashed you can go ahead and boot to system. Finish the setup before you put the sims back in the phone.
There is a longer throw the kitchen sink method in the OEM unlock thread for those that wish to search, that is what I would do if I wanted absolutely no risk as it seems to work without fail. I've done what I describe here a good ten or more times now as I was the first reported rom install here using the first method and I've been flashing away since then and dropping some of those original steps as I went. I'm thinking it should work for others too but I cant prove it until someone does it. It may be you need the kitchen sink for the first flash, I simply cant say because I would have to go stock to try and I'm not harboring much of a hankering to do that. This being XDA and we being adults please understand that I'm sharing the information based on actual practice on my own phone but there is no guarantee. You make your choices and what happens, happens.

Galaxy Note 9 stuck at bootloop after update Magisk

I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.

Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.

If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?

user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.

Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?

I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:

user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!

N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..

As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:

summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!

Gdhhs

Samsung galaxy Note 8 Doesnt Bootup after flashing to fix frp block

I rooted my Samsung Galaxy Note 8, and accidentally turned off OEM-unlock. Because of that, when my phone restarted it couldn't load because it was blocked by frp-lock . So I looked up and all I needed to do was to flash my device, so I did. Now when it is supposed to startup and factory reset, its stuck on the Samsung logo and wont start. Any ways to fix this?

Wrong device forum.

nsfxpython said:
Wrong device forum.
Click to expand...
Click to collapse
Moved.
Welcome, @Dandisou! Make sure to post in the correct section to get better support
Your Note 8 isn't Sprint or Verizon or anything, is it? In that case I'll have to move it once more.

Never mind i fixed it (for those who are interested: hold volum up+bixby+power, then wait until android settings pop up, then factory reset)