Database Info

Best way to unroot and factory reset my Samsung Galaxy Note 4?

My problem is very simple at its core and I find myself resorting to extreme solutions such as factory reset to solve it. However, I am okay with this. I would like to know the best way to unroot and factory reset my Note 4 SM-N910U.
What follows is the original story and my attempts to fix it. It's rather long, so if you would like to skip this section there is a tl;dr at the end.
Originally, I had found myself unable to login to the app Snapchat because they had gone to extreme lengths to lock out rooted users (an infamous fact on online discussions).
A popular solution for this would've been to install the Xposed Framework with RootCloak to hide Root from Snapchat - this is where my first problem came along.
My Android phone is encrypted.
This means that I could not use TWRP to flash the Xposed Framework zip (because TWRP for my device does not support encryption, thus could not read /data directory.)
I tried using FlashFire to skip recovery and got the same result - /data encrypted.
I tried to flash with CWM to see if it would support decryption of /data partition, but CWM isn't even compatible with my device.
At this point I was running out of things to try (I had been after this problem for about three days) and I decided to just kick the bucket, unroot and factory reset, because apparently the only way to undo data encryption on Android is to delete everything .
Apparently, even this would be a challenge. To factory reset a rooted device, you apparently need a stock ROM.
I tried looking for stock ROMs for SM-N910U online but the sites that came up (there were about 9 hits on Google for my baseband) all seemed fake and potentially harmful.
Even then, I don't know how I would flash the ROM since my TWRP doesn't work but that's the least of my worries at the moment .
I'd be extremely grateful if anyone could offer any potential pointers on where to download a safe stock ROM for my device and how to flash this ROM when I have no working TWRP (since my /data partition is, again, encrypted).
It seems a bit like a paradox - to remove data encryption you need a TWRP stock flash, but for a TWRP stock flash you need to remove data encryption.
Please do help... thank you in advance.
TL;DR
- tried to install xposed to hide root.
- found out that i can't flash any roms from recovery, because my recovery (twrp) doesn't support android disk encryption.
- found out that to remove encryption, i need to factory reset.
- i can't factory reset, because I need a stock ROM and I don't know where to find said stock ROM.
- also, how would i even flash this rom without a working recovery (again, the recovery doesn't work because full disk encryption).
Device Details:
Phone: Samsung Galaxy Note 4​Model: SM-N910U​Android version: 6.0.1 Marshmallow​Baseband version: N910UXXU1DPL1​

qnxo said:
My problem is very simple at its core and I find myself resorting to extreme solutions such as factory reset to solve it. However, I am okay with this. I would like to know the best way to unroot and factory reset my Note 4 SM-N910U.
What follows is the original story and my attempts to fix it. It's rather long, so if you would like to skip this section there is a tl;dr at the end.
Originally, I had found myself unable to login to the app Snapchat because they had gone to extreme lengths to lock out rooted users (an infamous fact on online discussions).
A popular solution for this would've been to install the Xposed Framework with RootCloak to hide Root from Snapchat - this is where my first problem came along.
My Android phone is encrypted.
This means that I could not use TWRP to flash the Xposed Framework zip (because TWRP for my device does not support encryption, thus could not read /data directory.)
I tried using FlashFire to skip recovery and got the same result - /data encrypted.
I tried to flash with CWM to see if it would support decryption of /data partition, but CWM isn't even compatible with my device.
At this point I was running out of things to try (I had been after this problem for about three days) and I decided to just kick the bucket, unroot and factory reset, because apparently the only way to undo data encryption on Android is to delete everything .
Apparently, even this would be a challenge. To factory reset a rooted device, you apparently need a stock ROM.
I tried looking for stock ROMs for SM-N910U online but the sites that came up (there were about 9 hits on Google for my baseband) all seemed fake and potentially harmful.
Even then, I don't know how I would flash the ROM since my TWRP doesn't work but that's the least of my worries at the moment .
I'd be extremely grateful if anyone could offer any potential pointers on where to download a safe stock ROM for my device and how to flash this ROM when I have no working TWRP (since my /data partition is, again, encrypted).
It seems a bit like a paradox - to remove data encryption you need a TWRP stock flash, but for a TWRP stock flash you need to remove data encryption.
Please do help... thank you in advance.
TL;DR
- tried to install xposed to hide root.
- found out that i can't flash any roms from recovery, because my recovery (twrp) doesn't support android disk encryption.
- found out that to remove encryption, i need to factory reset.
- i can't factory reset, because I need a stock ROM and I don't know where to find said stock ROM.
- also, how would i even flash this rom without a working recovery (again, the recovery doesn't work because full disk encryption).
Device Details:
Phone: Samsung Galaxy Note 4​Model: SM-N910U​Android version: 6.0.1 Marshmallow​Baseband version: N910UXXU1DPL1​
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com this use your model number to search for your stock firmware, find the firmware for your region then flash that via Odin.
Sent from my SM-S903VL using Tapatalk

Would I first need to "wipe" anything in TWRP?

qnxo said:
Would I first need to "wipe" anything in TWRP?
Click to expand...
Click to collapse
It wouldn't hurt
Sent from my SM-S903VL using Tapatalk

I Am Confused About Recoveries

Please forgive my ignorance here. It's been 4 or 5 years since I last flashed a recovery. AB wasn't a thing back then, but it sounds like it obsoleted everything I used to know. Meanwhile, it seems like everyone around here has long since digested the changes and is carrying on conversations premised on a lot of background information I don't know. In short, I'm confused, and I need help.
What I Want to Do:
Flash the microG fork of LineageOS
Flash Magisk
Flash the Asus camera app
Install the unofficial port of the GCam app
Encrypt and divorce the boot password from the lockscreen as per this post (which I can't link to our XDA rejects my post, so I'm copy-pasting instead: https COLON SLASH SLASH forum.xda-developers.com/showpost.php?p=78699812&postcount=58 )
Question 1
Which recovery should I use? It sounds like there are three and each has problems. Is the following correct?
It sounds like the LineageOS has trouble flashing things other than LineageOS -- or is it just OpenGApps that's a problem? Can it flash the microG fork of LineageOS?
It sounds like mauronofrio's unofficial TWRP works generally, but can't flash LineageOS and can't decrypt the data partition if LineageOS encrypted it.
It sounds like bigbiff's official TWRP works generally, but there seem to be differing opinions about whether it can flash LineageOS; it can decrypt a data partition encrypted by LineageOS, but not if a password is set; and its permanent installation feature is currently buggy and might break the boot partition.
Question 2
Some posts suggest using different recoveries to flash different things. Is that advisable?
Question 3
Do I even need to install a recovery permanently? It sounds like it should be possible to boot a recovery using "fastboot boot something.img" and do everything I need to do. Is that right?
Are there any strong reasons why I should have a recovery installed permanently even if it's not necessary?
Question 4
What's the correct install order? LineageOS (microG fork), then Magisk, then Asus Camera?
Question 4b
How do I deal with the A/B thing?
Do I have to install everything to both partitions, or does the recovery install to both partitions automatically, or is stuff installed to just one partition and then somehow magically handled with the next update?
In particular, how do I get Magisk and Asus Camera to carry over to the other partition?
The instructions for the LineageOS recovery include an extra reboot right after installing LineageOS so that the remaining stuff ends up in the same partition. Does TWRP also need the same extra reboot?
Question 5
Do I understand correctly that the GCam port is just a regular apk that can be installed later through normal means -- no flashing required?
Question 6
About divorcing the boot password from the lockscreen:
Does that post apply to LineageOS?
Does the A/B thing complicate the instructions in any way? It sounds like the files to be backed up and restored are in the data partition, so I'm guessing not.
Do I need to remove the boot password to make a recovery work? It sounds like the LineageOS recovery can handle the password; the unofficial TWRP can't even handle the encryption format; and the official TWRP is currently bugged and needs the password removed. Is that right?
Question 7
So, OTA updates for Lineage OS are a thing now? Could someone explain how that works?

q1
- Just opengapps has problems but you can use lucas own opengapps build or mindthegapps. No idea about microG.
- True. There is some difference of opinion where it should be fixed (in lin or twrp).
- It played around with it a lot before giving up. In its current state i would not use it for any rom. As soon as pin/pattern/fp/stock rom/nandroid comes into play there will be problems.
q2
For convenience or if you have problems with stock lineage recovery it makes sense at the current time. Since there is currently no twrp out that fully supports lineage flashing + nandroid and encryption i would either not use twrp at all or wait for the official twrp to be fixed.
q3
This depends on your needs. Most recovery/rom combinations won't decrypt while only fastbooted. Especially when nandroid comes into play you will encounter problems.
q4
Depending on the weather, the build you use and the already installed build/addons you get different results. In general the order of those 2 should not matter but in my experience i get different/unexpected results/problems without beeing able to reliably reproduce the behavior.
q4b
I was in your shoes a year ago I'll try to keep it short. You have 2 slots. some partitions like boot exist in both slots (you will have them twice) while data only exists once. One slot is active. The phone boots from the active slot. You can manually change the active slot from fastboot and twrp so the next reboot will boot from the previously inactive slot (but you should rarely need to do that). Ah yes the most important change is there no longer is a persistent recovery partition. Recovery is embedded as a ramdisk in the boot partition.
Assuming the rom or whatever you are flashing is done right and the recovery you are using works correctly:
- flashing a rom from recovery will flash it to the inactive slot
- flashing an addon like magisk or asuscam or gapps will flash to the active slot (thats why you need to reboot after flashing a rom, so gapps will be flashed to your new rom)
- flashing a recovery installer flashes both boot partitions (at least that is the current state) and remove magisk
- flashing a recovery will install it on the active slot be it from twrp or fastboot
Due to this behavior you will have to install twrpinstaller + gapps+ magisk + asus cam every time you install a new rom (unless the rom has it already like asus cam in the next omnirom weekly) and you will have to reboot to recovery from twrp and lin recovery (active slot change to newly installed rom).
q5 yes
q6 no clue what that even does In general i had problems/errors with so many different combinations of roms/encryption/recovery and nandroid that currently i would advise to disable
pin/pattern/fp if you want to flash a rom and or take/restore a nandroid and reenable it after.
q7 It downloads the newest build and installs it in the backgroud but you still have to manage magisk, twrp etc. manually. So i prefer to just flash everythin from recovery.

A/B slot questions

I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..

dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..

Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?

dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..

I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?

dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..

Question PROBLEM INSTALLING ARROWOS

Hi
I installed ArrowOS and when I try to go back to TWRP, there isn´t any password even tho I have one on my device.
The thing is that when I enter it shows that there isn't any storage in the phone (0mb - imposible) so I can't wipe all data nor install other ROMS because it isn't reading the internal storage.
Does anyone know how to solve this problem? It doesn't matter if I have to factory reset or delete all data, or install another ROM, but knowing that it is not a cable problem, I would like to know if I should use other TWRP version (and how to do it) because I can't even seem to do that.
The tutorial I installed the ROM was this, but instead of ArrowOS11, the 12 in my POCO X3 PRO:

Most likely using incorrect / old TWRP. Use https://twrp.me/xiaomi/xiaomipocox3pro.html
Edit: Android 12 ROM's cannot be decrypted yet.

So should I just wait? Thanks for the fast reply!

No recovery can decrypt android 12 data yet.
You can still format the said data though and if twrp doesn't allow you to do so, try using orangefox instead.
You also can install or update rom and other stuffs (that doesn't access data) via sideload.
If you want to install magisk then you need to do the boot.img and related thingy.

Is there a recovery to decrypt android 12 data yet? I've been trying decrypting since 2 months ago and didn't find any answer.

Did you try Orangefox?

Toflamo said:
Is there a recovery to decrypt android 12 data yet?
Click to expand...
Click to collapse
No

borisku said:
Did you try Orangefox?
Click to expand...
Click to collapse
Wouldn't make a difference, it's a limitation faced by all custom recoveries and OrangeFox is based on TWRP.
@Toflamo You can try flashing a ROM from the SD Card or ADB sideload, but the SD card flash would less of a hassle. None of the recoveries as of now support decryption, might take a while to overcome that limitation.

Ngl I don't know how to ADB sideload and don't have any SDs rn to flashing it, so it seems I would have to wait until some recoveries can do it. From now on I'm staying with ArrowOS12 on my PocoX3Pro, even tho battery performance isn't as good as I expected.
Thanks so much everyone, you've been very helpful!
I will come back in some months to check if there is any tool to overcome the decryption problem of Android 12.

Upgrade to LineageOS 19.1

Hi All,
since a couple of days the new LineageOS 19.1 is available for the Moto g7 Power.
A manual upgrade is needed to get it onto the phone.
Since I did the installation but not yet a manual upgrade of LOS to a new major version I have some questions about it:
When reading the upgrade guide there is no info about .... :
will I lose apps or any data when simply sideloading the new version?
will I have to newly install/sideload Magsik?
are there any other important things to consider when doing such an upgrade?
Thanks a lot in advance.
Cheers

1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.

PhotonIce said:
1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.
Click to expand...
Click to collapse
Great, all worked fine, thanks!