Database Users

Dreaded Samsung Retail Mode on Galaxy s5

Anyone out there willing to help guide me through the process of getting the retail mode removed form a samsung galaxy s5? Of course Im willing to compensate you for your time if we can get it to work.
Ive got no experience with Rom's and or installing a rom and the basic passwords have not worked on getting the software removed. Any help would be appreciated.
PhoneDoctor1

Which S5 model have you got?
Make a free account on sammobile dot com (Links are not allowed here)
Type your model S5 into the firmware section and download a ROM
Grab ODIN 3.09 or later (Easy to find with a quick google)
Extract the ROM from the zip, should end up with .MD5 file
Install Samsung drivers (Easy to find with a quick google or Installing KIES3 will also install them)
Put phone into download mode (Power off, then hold Vol down & Home & power, release when the warning appears and hit volume up when asked)
Connect phone to PC USB and wait for drivers to complete installing
Load .MD5 ROM into AP or PDA section of ODIN
Make sure only 'F.Reset Time' and 'Auto Reboot' options are selected in ODIN
Hit START on ODIN and wait for it to complete
All being well, your phone should reboot into the ROM, take a while for first boot, especially if you flash a Lollipop ROM (give it 15 mins+)
Some people find it hangs on first boot, and need to boot into recovery mode and factory reset after flashing the ROM

Same results.
*Detection* Thank you so much for your prompt response and help with this. Unfortunately the steps you provided didn't work for me. I was able to Get Odin, download the correct ROM, drivers, and everything. I installed the ROM on the phone (Took 4 minutes) though ODIN and it stated that it succeeded. Phone restarted and retail mode was back on the phone.
Any other options to get it removed?
PhoneDoctor1

Some instructions here on how to disable retail mode
http://www.naldotech.com/how-to-disable-exit-galaxy-s5-demo-live-unit-retail-mode/
How to delete, disable and exit Demo Live Unit Retail Mode on the Samsung Galaxy S5
1. The first thing to do is to disable the retail mode of the firmware.
2. Go to the app drawer and open an app called Samsung Retail.
3. Go to Configuration Settings and enter the password 5444 to unlock it.
4. Then uncheck “Disable the factory reset” and enter the following password M729Q16K8546.
5. Turn your Samsung Galaxy S5 off and boot into Recovery.
6. Go to Wipe data & factory reset and press OK.
7. The phone will reset and all the applications will get removed.
8. Flash a stock firmware with ODIN (tutorial).

There must be something different about this retail mode. It looks different than the others shown in previous posts or youtube videos. I can't seem to disable the app and the passwords don't work. Ive seen a few youtube videos on how to remove it and the one I see doesn't look like the one thats on this galaxy s5. Any other workaround to your knowledge?
PhoneDoctor1

Not that I know of off hand, I`ll post back here if I find anything, it might be quicker to take it to a phone shop and ask them to disable it for you

PhoneDoctor1 said:
There must be something different about this retail mode. It looks different than the others shown in previous posts or youtube videos. I can't seem to disable the app and the passwords don't work. Ive seen a few youtube videos on how to remove it and the one I see doesn't look like the one thats on this galaxy s5. Any other workaround to your knowledge?
PhoneDoctor1
Click to expand...
Click to collapse
Which version S5 have you got?
Just noticed this thread for the G900X to disable Retail Mode
http://forum.xda-developers.com/showthread.php?t=2733083

Ive got the t-mobil version here in the states. I did see that thread before I posted mine but that wont enable me to make calls. It will most likely turn the phone into a wifi capable phone without cell service.

Sorry, I meant which model S5, mine is the G900F
I take it you bought the phone second hand? Unless someone else can help I think taking it in for repair would be the best bet if those tutorials are not working

I would like to know how you got into retail mode!
And, of course, your model. Its in the system informations.

I had a similar issue with a laptop once (purchased the display model).....
The only thing that fixed it was formatting the hard drive and re installing everything from the recovery discs......
I guess the equivalent for Android would be to flash a PIT file (I think this will reformat the memory) then the firmware (both) with odin........
If you DO go this route, be EXTREMELY careful to flash the CORRECT pit file as flashing the wrong pit will irrevocably brick your phone.........
Sent from my rooted kn0x0 stocKK SM-G900F S5

I appreciate the help and responses. From my understanding the retail mode can not be removed. It seems that Samsung specially designed these phones with software that can't just easily be flashed.

Successfully removed Retail Mode from AT&T Samsung Galaxy S5 SM-G900A
PhoneDoctor1 said:
I appreciate the help and responses. From my understanding the retail mode can not be removed. It seems that Samsung specially designed these phones with software that can't just easily be flashed.
Click to expand...
Click to collapse
I had just about given up on a straightforward fix, and was about to resort to some major firmware manipulation that would have likely led me to all sorts of confusion. It turns out the password was "rethink" as is listed in multiple places across the web. (AT&T SM-G900A Galaxy S 5) It is applied to the Samsung Retail Mode app which has a "burger" icon in top right corner of the screen that must be selected first to lead towards password entry. This is not the "Retail Experience" app, but the other similar one. Once the Retail Mode app is uninstalled, there are intuitive steps leading to uninstalling of the "Retail Experience" one next, with no new passwords.

Back from Windows Phone, what ROM to use?

Thinking I'll post the TLDR up top:
What ROM should I use for the most basic (no extra "features") for my phone? Perhaps I'm too soon for such a version? I have the Exynos S8+.
So ~4 years ago I decided to move to Windows Phone (xperia 1020 -> Lumia 950XL). I'm not a big Facebook guy, so my phone is mainly for notes, texts and calling. I have however become a "fan" of Microsoft products, and I managed to change everything from "Samsung all the way up your ass" to "Microsoft when you desire it" on my S8+, including remapping the bixby button to Cortana. I have turned of all permissions possible for all Samsung apps I could, the only reason I want to root/change ROM is because I hate the "always active, **** up your battery and start all apps lockscreen home button".
I don't want any fancy stuff, I just want a clean android version for my Phone, with the option to disable the Home button on lock screen... And perhaps a point in the right direction for how to root/ROM my phone correctly. I believe it's 7 years since I've looked into rooting, hell, might even use the wrong terms here... That's what not looking into tech like I did 7 years ago does to a man
Edit: My 950XL basically went to hell, so I had to more or less impulse-purchase my S8+, without looking into what I really bought.

I've had this Samsung phone for maybe a month and a half. So please take this with a grain a salt. Information that was scattered around and I had to go searching for when I bought this phone. Here is my brain dump...
There isn't an AOSP or Vanilla Android ROM, they're all touchwiz based. Most of the ROMs give you an option during installation of certain apps you can remove. I dabbed around making a very clean and minimal ROM, but turns out if you remove too much the setup wizard falls apart and the phone basically freezes before even selecting your language. So I resorted to installing someone elses ROM and after setting it up, using ROM toolkit to remove random system apps and hoping it doesn't crash after a reboot. haha
This is my first Samsung phone (exynos S8) so getting around to using ODIN and the different files you need to flash was a headache. The general rules to follow are.
1. Enable Developer Options and turn on OEM Unlock. Then never again change that option. If you are not running 100% stock the bootloader will prevent the phone from turning on correctly and kick you into Download mode basically forcing you to flash a stock ROM. So once you turn on OEM Unlock, just leave it turned on. I was messing around in Dev Options and without knowing turned it off. Next time I restarted my phone I was forced to flash stock rom again. Custom ROMS tend to remove that option entirely so someone doesn't mistakenly turn it OFF.
2. KNOX is Samsungs security in stock ROMs. The moment any kind of custom recovery or anything is installed. KNOX will be tripped and stop the phone from completing boot up. It'll basically tell you that theres something that wasn't signed by Samsung and to reset the phone. An endless cycle unless you, 1. Install a Custom ROM or 2. Flash a stock ROM to undo whatever you did.
3. Keep your firmware (modem bootloader etc) as recommended by the ROM Dev. AQF7 is the last known stable and developed for firmware.
Right now there a new update AQG5 that has an updated Bootloader that will softbrick your phone. People have tried installing the entire Stock ROM and ran into issues. It worked for some, but avoid it for now. If you do find the need to play with it. For the time being flashing just the modem (CP file) and keeping or using the previous AQF7 Bootloader (BL file) should keep your phone usable.
4. The S8 and S8+ are very much identical except the obvious size difference. Cross Development allows Devs to create a single ROM for both devices. With only the Kernel being the difference. Which is some cases both are in the ROM zip and automatically selected for you. So if they state its compatible with both. If not just focus on S8+ only ROMS.
5. ODIN is a program that's used to flash files. Either to flash custom recovery or stock files. Samsungs SmartSwitch program is like Windows Phone Recovery Tool. It'll detect the phone you have connected and download the latest stock ROM it can find and flash it. ODIN is a stripped down program that we use to flash individual files. Its only really used to either flash a stock ROM or custom recovery. In some cases bootloaders and modem updates, but id avoid those for now.
6. ROM/Firmware structure. Samsung stock ROMs and Firmware zips are available all over the place. Basically its a .zip file with more tar files in it.
Lets say you download a stock ROM.
The name is normally Model|Region|Version.zip so for me I have G950FXXU1AQF7 that tells you. G950F is the Euro S8 Exynos, XXU1 is basically just New Zealand and some carrier, AQF7 is the firmware version. The file name might have multiple regions. Theres more into what means what. I personally just focus on the Model and the Firmware. I can delete carrier apps or flash my carriers CSC later on. From what I've seen version numbers increase with the next letter in the alphabet and a number. So obviously an update with AQF7 is newer then one named AQD6 etc.
If you where to extract a stock firmware/ROM zip to use in ODIN etc. It normally gets broken down to these tar files. If stock files are renamed ODIN will not accept them. It happen to me
BL** - Contains the Bootloader, partition layout etc.
AP** - Actual ROM. Kernel, System, cache, userdata (for some), recovery
CP** - Modem files.
CSC** - Preloaded carrier apps, settings. This comes in two files. If you flash HOME_CSC your data is kept if you decide to do an update. CSC file without HOME will format the data partition.
These files are flashed in their prepacked files. You wont flash individual system, kernel files etc with odin.
7. TWRP the go to recovery for Android. You'll use ODIN to flash it. On twrps website just find the S8+ (dream2lte) and download the .tar file. Using ODIN it will be flashed as an AP file.
8. Once you have TWRP installed it will trip KNOX if using a stock ROM. The button combination to get you into recovery from a fully turned off phone is,
PWR + Vol Up + Bixby
Vol Down is Download Mode, also used as the button combo to force the phone to restart. If you restart it this way, quickly move your finger and hit Vol Up and if done right will go into recovery.
9. CSC is carrier bloatware, but in the forums its what gives you VoLTE & WifiCalling. As long as your carrier supports it and in an area/wifi network that will allow it. Some ROMs have it included, if not you can find a forum thread which offers a flashable zip that will give you all the carriers around the globe. If selected correctly should give you those features for your carrier on your phone.
___________
The jist of all that is. Enable OEM unlock > use ODIN to flash TWRP > Boot into TWRP and flash a custom ROM. You'll use TWRP to flash ROMS, Mods, Custom Kernels. ODIN/SmartSwitch would be used to revert to 100% stock. If you ever some how turn off OEM unlock while using a custom ROM. FAP will be turned on and block you from using your phone until you flash a stock ROM and turn on OEM unlock again.
I'm personally using Renovate ICE on my S8 and have removed ALOT of system apps. Windows Phone has a special place in my heart, but Microsoft is just terrible about it now. I had a 950XL for a bit, but always had HTC phones when it came to Android. For me HTC was so much easier to work with when it came to ROMs. Now I'm rocking an S8 so had to learn fast.
Always do your research before flashing anything. Make sure multiple sources say the same thing or risk flashing something that might break your phone. If any other user finds something I mention to be wrong, PLEASE correct me. I will learn and so will others.
What I missed from HTC forums was the sticky threads. The go to threads that broken everything down and explained it. All the HTC phones I had while using XDA had these sticky threads in each devices forums. I was and still am reading threads from other Galaxy phones just to get a better understanding of how it all works since they aren't in this devices forum.
Not to talk bad about long time Samsung users, but yall need to get organized haha. Once I'm confident with Samsungs inner programming workings I'll try to make an actual knowledge thread with links and where credit is do. But dam it's like sink or swim around some galaxy phones.

Samsung FRP Bypass

Hi, I'm a total noob on this but I don't know where to start to looking for an answer.
My girlfriend went on vacation (from Chile) to the united states, her mother gave her a cell phone (her cell phone at that moment) an almost new Samsung Galaxy S7 Edge (SM-G935P) from the Sprint Network.
Before returning to Chile the cell phone was unlocked (or so they said at Spring), so here in Chile she put her local carrier SIM but the cell phone never recognized the Sim Card.
So she hard reset the cell phone. Everything went well until he had to enter the original Gmail account for the cell phone. Her mother did not remember the password so after som trial and error, they manged to reset the Google Account. But now when I try to enter de Gmail and password give me this error: Unable to sign in device due to a recent password change. try again in 24 hours, I have waited more than 24 hours and still can't activate the account.
The cell phone is still showing at her known devices in her mother's Gmail account, and the password is correct but I can't by pass the Gmail Activation, I was reading that I can downgrade to a firmware that allowed me to by pass the Samsung FRP but I don't know wich firmware I can use.
Can someone plase guide me how can I activate this cell phone.
Thank you!

edit: You were right I apologize.
If you want to get your password then whoever knows the best information will need to tell google over the phone what that information was when initially set up...birthdays, time of creation,etc-when they ask and %100 will ask. If she/you don't know it..you may never get it back... but calling their --> Customer Support <-- is your best option.

For s7 edge Android 7.0
So I found a way to bypass Google frp on Android 7.0 for the s7 edge and couple other model, it's an old way but modified. First enter into the Google account login screen where it says verify your account. All you do is simply over load it with characters. Tyler a bunch misc letters and number until you have a long good string then begine select all copy paste do this until your phone seem like it going to freeze up. I did it until it took about 2-5 mins to go through. Doing this will send you to a screen says error something went wrong. Hit enternor continue and if you notice this time when it goes back to verify your account the screen should have a black background at the top where's your notifacatioons are . Repeat 2-3-4 times overloading it and getting the error message I'm not sure exactly how many time think it suffers a on phone and Android build I just know once isn't enough to do it so do it a fewbtime it'll take awhile to get the first error but after that you should have the character line copies and ready to paste. After a couple time hit back arrow on your phone clear to where it ask to select language or start screen and emergency call if done correctly it should now give you the accessibility menu also enter into the accessibility option and modify your set up. Mess with stuff a little be careful with setting up universal switches as you can really mess yourself up. At some point in time you should be able to get your notification menu to drop down and open. When this happens hit the little setting menu button long click it and it should shortcut you to system settings. Bypassing for temporarily. Set up your setting and movie your app permissions as much as possible. Now the trick is getting my Knox downloaded open and set up on your phone. Once you do this make sure you click on both my Knox and regular device administration for know to have some control and make sure you say yes for Knox to be able to reset wipe your phone . After device administration is set and that all done go to your pc or another phone tablet whatever and log into know online and you hold re your phone connected on it white a button that says wipe this phone. Click it make sure the phone has Wi-Fi or service connected and wait for phone to wipe this should reset frp and Google verification back to being a new phone. There ya go merry Christmas

Is this fix legit?^^

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
Fцck no it ain't legit. Dude probably got baked & strung up that nonsense to laugh at folks who tried it. You could string up a petrabyte worth of miscellaneous characters so long that your phone would be permanently frozen... & you wouldn't get an error message to pop up, let alone one that would change your notification bar background color or whatever else he said
☆KØŁØЯΛĐØ☆

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
No, It's not.
I still can not remove the Samsung FRP, I've tryed all the methods I found online, but still nothing.

S7 & S7 Edge FRP [SOLVED]
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Hi ☆KØŁØЯΛĐØ☆, I think I ****ed up.
I follow your instructions, but after the first step (flashing boot.tar) the phone whent on a endless reboot.
Please can you help me.

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?

jazzdglass said:
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?
Click to expand...
Click to collapse
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?

keiichitroncio said:
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?
Click to expand...
Click to collapse
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.

jazzdglass said:
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.
Click to expand...
Click to collapse
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you

keiichitroncio said:
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you
Click to expand...
Click to collapse
Just downgrade to marshmallow.. Try PJ2.. I used that. Flash the boot file provided, run Qualcomm.bat via adb.. Then flash again 6.0.1... If phone reboot after flash boot file, you'll have to be very fast, after phone boot to welcome screen, before it reboots, keep running the Qualcomm.bat till u see adb recognize device. It will say error. About phone storage. Just ignore. It has been unlocked

Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ

☆KØŁØЯΛĐØ☆ said:
Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ
Click to expand...
Click to collapse
Do you happen to have the exynos adb bypass code?

OMFG this freaking worked!!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
You sir are a genius. I tip my hat to you.... The only method out of....pretty much the entire internet...that actually works. To all other modders, if you follow the instructions carefully, this will work. Thank again man.:good::good::good:

I have a G935V that is stuck with FRP. I reset my password today and then happened to try to flash a new ROM (didnt know about FRP at the time).
Been trying this all day, but cant get the S7 & S7 Edge QUALCOMM.bat to run on the phone... a flashed back to MM and the Boot.rar pushes fine, but when the phone gets to the welcome screen its like my computer doesn't recognize the phone is connected. Any ideas?

This worked great on my VZW s7 (just had to get the right VZW firmware)...
@KjK89, you have to run the .bat file before the welcome screen. I basically kept running it over and over during boot and it took before th welcome screen.

Check my post about SAMSUNG S7 Nougat 7.0 frp remove

Thanks So much, the only thing that actually worked!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Anybody looking for a fix for Galaxy S7 and S7 Edge Factory Reset Protection Bypass needs to follow these steps and you'll get past this pesky protection.
The only step that wasn't clear was this:
- Flash the boot.tar file that corresponds with your device (enables ADB)
On Odin you have to choose the boot.tar file corresponding to your model number. This is done by selecting the BL button and only that one then in Odin click Start. This might be clear for veterans to flashing phones with new firmwares but it wasn't clear for me, being the n00b that I am. Thanks again. This worked great!

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!

Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?

Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.

JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.

https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965

JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.

Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.

https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.

I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.

zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.

JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously

Good luck.

Deleted

Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.

JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...

sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.

sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you

Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082

Please help me, I am SAD😭😭😭: It will not boot after installing Titanium Backup (root) to uninstall Samsung DM service

This question may contain some irrelevant information, but I wanted to give as much detail as possible. I can tell you basically everything I did to the phone from the factory state before I ran into the problem with not being able to boot. If it is too long to read, you could skim it and skip to "(now we are getting to the horrific part)" below.
I rooted my Samsung Galaxy Note 4 SM-N910P (Android 6.0.1) using the method described here:
[SM-N910*] CF-Auto-Root
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) ! CF-Root is the root for "rooting...
forum.xda-developers.com
It is not my main phone. It is a 2nd, used phone which I purchased recently, and it was apparently in factory state or factory-reset state when I removed it from the envelope. It had Android 6.0.1 on it. The phone does not have any SIM card in it, nor does it need one, as I was planning on using it as a tablet connected to WiFi. I rooted it. This was my first time rooting a phone, but I didn't have any problems. Everything was OK, root successful
I installed the following "SCR" app because I wanted to screen record with internal audio and simultaneously hear the internal audio through earphones (which was the reason I rooted the phone):
[APP][4.0+][ROOT] SCR Screen Recorder
Official SCR Screen Recorder thread Check out SCR Screen Recorder, the Android most comprehensive screencast recording app. SCR Screen Recorder supports all Android versions since 4.0 and utilizes the best encoding method available on each...
forum.xda-developers.com
But it did not work. Even though it was advertised as working with Android 6, the app would immediately crash after pressing the record button. It gave the SR135 error mentioned here:
[APP][4.0+][ROOT] SCR Screen Recorder
Official SCR Screen Recorder thread Check out SCR Screen Recorder, the Android most comprehensive screencast recording app. SCR Screen Recorder supports all Android versions since 4.0 and utilizes the best encoding method available on each...
forum.xda-developers.com
The SCR app did give a warning when I enabled internal audio from the settings menu, but I think that this is (probably?) not the source of my boot problems, because I had since rebooted the phone several times with no trouble. I don't think the internal audio plugin even installed; it seemed to just silently fail to initiate the installation. It wasn't until I installed Titanium Backup that I had trouble booting. I had stopped attempting to use SCR, and was planning on uninstalling it.
The next thing I tried was installing some APKs for the Samsung Game Launcher, because supposedly that app allows recording of internal audio. I got the APKs following these links:
Game launcher for Note 4 without Root
Samsung release s7 game launcher for s6 and note 5. Its also working with our note 4. Just downland Game launcher and game tools and install. Game launcher -...
forum.xda-developers.com
These earlier versions of the Samsung game APKs were not suitable because they did not allow me to add arbitrary apps to the launch menu (so that I could screen record). Something about a requirement to request to register the app as a game, and it would not go through. So I tried some later versions (the latest that I could find on APK mirror that were compatible with Android 6), and those did allow me to add arbitrary apps, but I had problems with these later versions crashing before I could actually launch anything.
So, following my inspiration in my quest to screen record with internal audio while also listening to internal audio, namely, this detailed reddit post,
https://www.reddit.com/r/AndroidQuestions/comments/81vhvm
I then proceeded to install RecMe screen recorder and its internal audio plugin (the latter requiring root, which I had):
RecMe Screen Recorder - Apps on Google Play
Screen Recording - No time limit, HD, with Audio, no Root required
play.google.com
Internal Audio Plugin (ROOT) - Apps on Google Play
Internal Audio Plugin app for mobZapp (Screen Stream Mirroring, RecMe, ...)
play.google.com
This was an improvement over Mobizen for Samsung, which I had tried on my other, unrooted phone, and which could record internal audio on Samsung devices but which could not also simultaneous allow the internal audio to play on earphones/speakers (you hear only silence when recording, but the audio is in the recorded MP4). RecMe with the plugin could actually play internal audio while also recording the internal audio, although the sound quality in the earbuds was poor, and it needed more testing.
I rebooted successfully after installing RecMe and the plugin, so I think it (probably?) did not cause my boot problems.
I was planning on doing some more testing with RecMe after installing AFWall+ to block RecMe from accessing the Internet for security purposes, but I never got to installing AFWall+, because this happened (now we are getting to the horrific part):
So this Note 4 phone, SM-N910P (Sprint), every time you boot it, it tries to go through this Hands Free automatic activation process to connect to the Sprint network that takes a long time (I think 5 retries, taking like 60+ seconds each). This isn't going to work because there's no SIM card (as I said, I'm using it as a tablet, I don't need cell service). So I go to the App Manager -> Show System Apps and then stop the Samsung DM Service. This stops the annoying automatic activation attempts, but I have to do it every time I boot.
So, to avoid doing this after every single boot, I followed the instructions here to first back up, and then uninstall, Samsung DM Service:
How to Delete & Manage Unused Apps on Android: 2 Easy Ways
This wikiHow teaches how to disable or remove apps from your Android device that cannot normally be uninstalled, which may require root access for your device. Open your Android's Settings. If your device is not rooted you'll only be able...
www.wikihow.com
Per the instructions, this required installing Titanium Backup (root needed):
Titanium Backup (root needed) - Apps on Google Play
EXTREMELY powerful tool. Backup ALL apps, Market links, remove bloatware & MORE!
play.google.com
When I installed the app, I granted root or superuser or whatever it's called to it, and it prompted me to also install "Titanium Backup Add-on," which I did.
Titanium Backup Technical FAQ | Titanium Track
www.titaniumtrack.com
Then I used Titanium Backup to (first) back up Samsung DM Service, and (second) uninstall Samsung DM Service. After that, I got some messages that said "Unfortunately the process com.samsung.syncservice has stopped." OK, I'll deal with that later, I thought. I proceeded to reboot the device, because I wanted to test and see if the annoying Hands Free automatic activation thing would be gone.
Now, when I try to boot the phone, it briefly says "installing system updates" (which doesn't make any sense because it should already be on the latest possible security patch [I checked] for Android 6.0.1 for this past-end-of-support-lifetime Note 4 phone — I forgot to mention earlier that I updated the Android security patch level before I did the root, and the Play store updated after I did the root [and I successfully rebooted — no boot problems until Titanium Backup]).
And then, no matter how many times I try, the phone always just boots to Android Recovery. It says samsung/trltespr/trltespr 6.0.1/MMB29M/N910PVPS4DQF1 at the top, and at the bottom it says "dm-verity verification failed". It does NOT explicitly say anything about failed "drk" which I saw mentioned in some Google search results.
I tried repeating the root steps which had earlier allowed me to successfully root the phone:
[SM-N910*] CF-Auto-Root
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) ! CF-Root is the root for "rooting...
forum.xda-developers.com
But no change. Same thing. Android Recovery. Tried reboot to system, to boot-loader, tried Wipe Cache, nothing works. Always boots into Android Recovery.
1) Can I fix this without doing factory reset?
2) Will factory reset fix this?
3) What did I do to provoke this? (so that I may avoid doing it again) It was caused by installing Titanium Backup? I thought this was a safe app? It has almost 400K reviews; I thought it was one of the most popular apps that require root? Or was it caused by uninstalling Samsung DM Service? Really? I did not think it was a super essential service; I had force-stopped it many times without any problems. (If so, in that case, how do I get rid of the annoying Hands Free Activation thing?)
4) Is it possible to access the filesystem (though USB?) to retrieve a screen shot? (The phone is not encrypted.) It's not a super big deal, but I made another Google account for this 2nd phone, and instead of memorizing the password, I took a screenshot of the random characters I had typed. I planned to learn it later. I know that was foolish, I guess, but I didn't think anything bad would happen. I had already successfully rooted the phone, and I didn't think I was doing anything super risky at this point. Literally all I did was install a few apps including Titanium Backup. And I uninstalled Samsung DM Service. Now I can't boot the phone. What is this horror?
[I am not an Android expert. I have used adb a few times, following other people's instructions. I don't have all the command memorized, I am not an expert, but I've used adb on my Oculus Quest (to change resolution) and also on my main phone that is unrooted (not on this rooted, boot-troubled one) in the course of installing Island on that other phone (it was never installed on this boot-troubled one). I don't even know if it's possible to use adb on a phone that cannot boot. But if you tell me adb commands I can paste them into the command window, assuming I am able to connect to an unbootable phone...]
If anyone can help me escape this horror, I will be forever grateful....

I think the phone is bricked. I tried factory reset and it is still always booting to recovery. This is my first time rooting. I didn't realize it was so easy to brick a phone. I never bricked a PC. I didn't think I did anything very risky. I didn't even try installing anything fancy like xposed or magisk — just an app from the Play Store. I thought people were just being dramatic when they talked about "bricked" phones....
Can someone tell me how to recover it with Odin3 v3.14.1.exe or Odin3 v3.14.1_3B_PatcheD.exe? I can still get to download mode on the phone.
What files do I download to recover a Note 4 SM-N910P?
Odin says "Changing the partition without unlocking will cause problems." Does the fact that I successfully rooted it using the "CF-Auto-Root" mean that it is unlocked?
I have the file twrp-3.6.0_9-0-trlte.img.
The SHA-256 hash is 2a5394313e1afe1c92576a5ceeba5cea462706bfc01e2da3d836fc381a119967.
Can I use this file to un-brick the phone?
Odin says:
Tips - How to download HOME binary
OLD model : Download one binary ".tar.md5"
NEW model : Download BL + AP + CP + HOME_CSC
There is also a button for USERDATA.
I don't know what any of this means — Which buttons do I press? When I used the "CF-Auto-Root" method I used a .tar.md5 file with an older version of Odin. For that, I used the AP button.
Or should I flash a stock Samsung ROM instead of twrp-3.6.0_9-0-trlte.img? Should I use the old version of Odin (Odin3-v3.10.6.exe) instead of Odin3 v3.14.1.exe or Odin3 v3.14.1_3B_PatcheD.exe?

Hey, you guys, can someone please help me? I am trying to fix this on my own without help, but I am not succeeding.
I followed the instructions here:
[Stock TAR][Full Restore] Odin flashable N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3
QB3 Marshmallow TAR: N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5.zip md5: e77d93930ec3c8593c18f0c3638ca726 Odin: Odin_3.12.4_4 -Download file, unzip file to extract full tar.md5 file -Load PC Odin (right-click on file, select "Run...
forum.xda-developers.com
to flash N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5
I thought this would work, because before it bricked I looked in my phone settings and recorded the following information in Notepad on my computer:
N910P.05
MMB29M.N910PVPS4DQB3
But Odin fails with error "FAIL! (Auth)". I will paste the log below.
Please help me...
Code:
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin engine v(ID:3.1401)..
<ID:0/014> File analysis..
<ID:0/014> Total Binary size: 3634 M
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> NAND Write Start!!
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> sbl1.mbn
<ID:0/014> FAIL! (Auth)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I noticed that it said on the download-mode screen:
SW REV CHECK FAIL : [aboot]Fused 5 > Binary 4
So I am going to try to find and flash N910PVPS4DQF1, which I think is a later version than N910PVPS4DQB3. I think either I or the aforementioned Auto-Root had updated from N910PVPS4DQB3 to N910PVPS4DQF1.
Does this sound like it will work to you? I hope so.
I hope I can find it — an authentic, malware-free original version.
And I PRAY that it works when I flash it.

It still fails with the same error message "SW REV CHECK FAIL : [aboot]Fused 5 > Binary 4", even though the firmware exactly matches what is shown on the recovery boot screen, N910PVPS4DQF1. Why does this happen? How the f. did my aboot get to such a high version number?
Is this site legit?
Download SM-N910P / GALAXY Note 4 SM-N910P XAS in Samfw - Samsung firmware download
SM-N910P / GALAXY Note 4 SM-N910P XAS samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
I guess I should try the most recent one from 2020, N910PVPU5DQI5? Or maybe the temporally penultimate one, N910PVPS4DQH1, which is from 2017-08-16? I don't remember having any updates from 2020 on this old Note 4 phone.

Hey,
I don't know if the website you posted is legit or not, but apparently, this one is:
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Updato - largest online firmware archive, fast and totally free
[CENTER] [SIZE="4"]www.updato.com lets you download any firmware for your Samsung device, completely free with download speed restrictions. We offer an option for premium download speeds for a minimal cost. Visit the website -...
forum.xda-developers.com
To be honest, jumping from 2017 to a sudden 2020 update does look a bit fishy so wouldn't download anything from there.
Also, I don't have a Note 4 personally, so I don't exactly know how to root it, but when you open the page of the firmware you want on updato, it gives you instructions on how to flash it.. (tho it seems like you already know how to do that) - and the XAS (Sprint) carrier is already filtered.
After taking a look on the CF Autoroot website, it says that it's based on the build ID "MMB29M.N910PVPS4DQF1" for your SM-N910P.
So, yeah the ...F1 should be good, try this one:
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Regarding TitaniumBackup - the app itself shouldn't be able to brick your phone and I'm pretty sure something got messed up after deleting / uninstalling the Samsung DM Services app.
Instead of deleting it, you should just try to freeze it with Titanium.
Hope that kinda helped and good luck.

crmbz said:
Regarding TitaniumBackup - the app itself shouldn't be able to brick your phone and I'm pretty sure something got messed up after deleting / uninstalling the Samsung DM Services app.
Instead of deleting it, you should just try to freeze it with Titanium.
Click to expand...
Click to collapse
Thanks for the reply. Yeah, I think you're right when you say it was caused by uninstalling the Samsung DM service. I was worried that the problem was caused by dm-verity blocking the boot, but I read somewhere that dm-verity does not block boot until Android 7. Android 6 will warn about corruption, but will not block booting, if I understand correctly. So the bootup process apparently actually needs the Samsung DM service for whatever reason.
I ended up getting the phone working by flashing N910PVPU5DQI5_N910PSPT5DQI5_N910PVPU5DQI5_HOME.tar.md5 from 2017, which can be found here under "PREREQUISITE" as well as other places. I inspected the other, supposedly-2020 archive, and the only difference is the modem.bin is N910PVPU5DTI1 (supposedly from 2020) instead of N910PVPU5DQI5 (2017). I don't think I need the new modem, as I'm not using cell service, but if I want to, I think I can install it later with the stand-alone file "MODEM_N910PVPU5DTI1_REV00_CL_2079268.tar.md5" using the CP (modem) slot in Odin, if I understand correctly.
I think the CF Auto Root is not very good. I tried the Mobi .firmware site for an updated version, but I had the problem described here. So instead of CF Auto Root, I used the method described in the link below to root the phone, which involves TWRP and SuperSU:
[Simple] Guide - How to root Note 4 Marshmallow (Qualcomm) [Similar for other models]
I have observed that some peoples are still confused about rooting marshmallow, So I am writing this just overall process, this is very obvious process for rooting and I have tried it on Note 4 Marshmallow and found working, this may work on...
forum.xda-developers.com
I had earlier found that guide in the Google search results for rooting, but as a newcomer I was turned away by technical jargon like "flash TWRP through Odin" that does not elucidate on what TWRP/Odin are or how to use them. But many days later, I now know what those words mean, and it is in fact very easy to "flash TWRP through Odin" once you know how to do it. (I think aspects of this website would work better as a wiki, so that people could add those details into the guide to improve it. The forums also have problems with information rot, like for example a link to release notes for SuperSU pointing to defunct Google+ (lol).)
Rooting it this way was much better, because when I soft-bricked my phone again by trying (again) to uninstall Samsumg DM Service with Titanium Backup (to confirm that that was what had caused the soft brick the first time), I was able to easily restore the system partition I had earlier backed up to SD card with TWRP. Doing it with TWRP backup/restore avoids the need to re-flash the stock firmware through Odin, and it also leaves installed apps (Titanium Backup, etc.) and data intact. If I had TWRP the first time I think I could have recovered that PNG image of my password from the filesystem and avoided orphaning a brand new Google account (but Google kindly allowed me to create another one). The stock recovery is really useless. The so-called "factory reset" didn't do anything for me.
The only other thing I could do is maybe install Magisk, but I'm not sure I really need Magisk — I just want to be able to run apps that require root, and I think SuperSU will be good enough for that. And the guide for installing Magisk goes over my head lol...
"if your device utilizes the A/B partition scheme" = I don't know
"If your device doesn’t have a boot ramdisk" = I don't know
So I think I will maybe avoid Magisk unless I find an easier-to-follow guide that is specifically written for my exact phone model.
Other than that, I just need to shut off the annoying Hands Free Activation that starts every time I reboot the phone. I will try to freeze the Samsung DM Service as you suggested, although it seems strange that that would work, because it seem like it would stop it from being available during boot in the same way that uninstall does. But I will try it. Now that I have TWRP and Odin and the stock firmware, I know that I can unbrick the phone if something goes wrong; I think it is unlikely to be permabricked, so I can safely experiment with more possible methods to shut down the Hand Free Activation . I think Titanium Backup requires the premium version for freezing, but I might be able to do the same thing for free with Island or Greenify or some other app.
So yeah, I'll try to freezing it. In the meantime, if anyone has any other ideas about how to stop the "Hands Free Activation" / Samsung DM Service from running after every boot, feel free to reply...

crmbz said:
Instead of deleting it, you should just try to freeze it with Titanium.
Click to expand...
Click to collapse
Yeah, your suggestion to freeze instead of uninstall definitely seems to have worked — thanks again.
I didn't want to pay for Titanium for something that wasn't guaranteed to work, so I installed Island, thinking I might be able to use that to freeze. I had to set it up manually because of some complaints about a modified system or custom OS preventing creation of a work profile, but I had done that before on my other phone to avoid some encryption requirement. (Island offered to automatically set itself up with root privileges, but it just crashed after I granted it such privilege 🫤 (Face with Diagonal Mouth emoji).) But I couldn't use Island to freeze apps in mainland without God Mode, and the instructions for setting up God Mode, unfortunately, went over my head (e.g., "Destroy Island space" = how?).
So what I did instead is use this adb command:
Code:
adb shell "su -c 'pm disable com.samsung.syncservice'"
Now when I look at Samsung DM Service in Titanium Backup, it shows the option "Defrost," meaning that it is frozen. So this adb command apparently does the same thing that the paid version of Titanium Backup will do for a fee.
And now the phone can reboot, and the Hands Free Activation doesn't show up. It's weird how the boot process freaks out about an uninstall, but is cool with disablement. Lesson learned: If I have an annoying system app, I should freeze it instead of uninstalling it.