Best way to unroot and factory reset my Samsung Galaxy Note 4? - General Questions and Answers

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

Related

Upgrade to KitKat -- too many guides

I have a N8010 with CWM and rooted stock.
To upgrade to the official Samsung KitKat, do I need to start from scratch?
As far as I know, when I perform the upgrade using Odin it will overwrite everything (system, recovery, cache etc) so I will need to reinstall CWM and reroot. I also understand thet the recovery will be overwritten by Samsung's upon every reboot, which is pain.
Or can I just flash the system, like I do with CyanogenMod and Omni?
sciurius said:
I have a N8010 with CWM and rooted stock.
To upgrade to the official Samsung KitKat, do I need to start from scratch?
As far as I know, when I perform the upgrade using Odin it will overwrite everything (system, recovery, cache etc) so I will need to reinstall CWM and reroot. I also understand thet the recovery will be overwritten by Samsung's upon every reboot, which is pain.
Or can I just flash the system, like I do with CyanogenMod and Omni?
Click to expand...
Click to collapse
Hey! Let's see if I can separate my answers:
1. Yes, all those things are overwritten, so you DO have to reinstall your recovery using Odin and then reroot if you want.
2. I just checked on what you said about the recovery and no, the recovery is not overwritten. I'm using Philz and it stays there no matter how many times I reboot. THE ROOT, however, is another story. I have found no way to leave it there permanently :crying: ...
3. From what I have seen (and unless you do that yourself) there are no deodexed official roms yet, so you would not be able to install the system alone. Or Mobile Odin, maybe? I haven't really used it on my N8010 so I can't say...
Hope that helps!
PhillipDSX said:
Hope that helps!
Click to expand...
Click to collapse
Thanks!
My main reason to investigate Samsung's KitKat for the N8010 was that I expected (hoped) they would still supply the TabletUI that Google removed from 4.3. According to the pictures I've seen there's no hope for the TabletUI on N8010, even with Samsung's KitKat. So for the time being I'll be a happy Omni user (which doesn't have the TabeltUI either, but at least allows for quick flashing without overwritinge everything, and for persistent root. And contains no bloatware.)
As for the persistent root, when you flash SuperSU using philz, and start SuperSU, you'll be offered the possibility to install a boot-time script that will restore root upon every reboot. Did you try that?

[Q] Factory reset doesn't unmodify so I can update my software

Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck
Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck

[Q] Two questions relating to fresh odin original FW flash, TWRP & encryption

I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Morthawt said:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Click to expand...
Click to collapse
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
LS.xD said:
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
Click to expand...
Click to collapse
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Morthawt said:
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Click to expand...
Click to collapse
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
LS.xD said:
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
Click to expand...
Click to collapse
Well I did get encryption working one time on a custom rom but I have no idea how I did it. What should I do to improve my chances of getting encryption working? I thought when I rooted the original rom it removed knoxx?

Encryption

A few questions about encryption on the S7:
Some threads, e.g., TWRP, refer to "Samsung encryption". Does the S7 use some sort of proprietary Samsung encryption, or does it use the standard Android encryption?
Since I have now disabled encryption after installing TWRP, can I re-enable it? If so, how?
Would FlashFire allow me to flash ROMs with encryption still enabled?
Thanks in advance.
dildano said:
A few questions about encryption on the S7:
Some threads, e.g., TWRP, refer to "Samsung encryption". Does the S7 use some sort of proprietary Samsung encryption, or does it use the standard Android encryption?
Since I have now disabled encryption after installing TWRP, can I re-enable it? If so, how?
Would FlashFire allow me to flash ROMs with encryption still enabled?
Thanks in advance.
Click to expand...
Click to collapse
1. Simply put, the method in which Samsung decrypts encrypted data isn't known
2. You can enable encryption but you must start from scratch. (As far as I am aware anyways). Means you must flash stock ROM in ODIN.
3. Not sure. You can certainly flash zips that modify /system. You can also use TWRP as long as you don't need to mount data. Switching ROM normally means a standard factory reset but if you are encrypted you can't use TWRP to factory reset and I am not sure if FlashFire can do it either.
Galactus said:
1. Simply put, the method in which Samsung decrypts encrypted data isn't known
2. You can enable encryption but you must start from scratch. (As far as I am aware anyways). Means you must flash stock ROM in ODIN.
3. Not sure. You can certainly flash zips that modify /system. You can also use TWRP as long as you don't need to mount data. Switching ROM normally means a standard factory reset but if you are encrypted you can't use TWRP to factory reset and I am not sure if FlashFire can do it either.
Click to expand...
Click to collapse
2. do you have to really start from the scratch?
http://forum.xda-developers.com/galaxy-s7/how-to/how-to-encrypt-device-custom-rom-knox-1-t3392301
3. is factory reset not just a kind of a wipe? why cant twrp just format the encrypted partitions?
I spent also several days to fully customize my S7 (cfw S7 debloated) and i am quite happy yet.
But if I lost once a phone long time ago.. So encryption is a must, root too.
I would accept definetely a non-working TWRP, if I could get an encryption?
any advices?
thx.
tefole said:
2. do you have to really start from the scratch?
http://forum.xda-developers.com/galaxy-s7/how-to/how-to-encrypt-device-custom-rom-knox-1-t3392301
3. is factory reset not just a kind of a wipe? why cant twrp just format the encrypted partitions?
I spent also several days to fully customize my S7 (cfw S7 debloated) and i am quite happy yet.
But if I lost once a phone long time ago.. So encryption is a must, root too.
I would accept definetely a non-working TWRP, if I could get an encryption?
any advices?
thx.
Click to expand...
Click to collapse
Yep, once you disable encryption in TWRP and flash the dm-verity zip, the option to encrypt the phone won't even be available in settings. In the rare case that it is, it will always fail.
Since you want root and encryption, it is pretty simple.
Flash stock rom in ODIN (Backup, backup, backup anything valuable)
Obtain root using CF-Auto Root method
Install TWRP, allow modifications, don't wipe /data
You can only flash zips from external SD card. Internal storage will be unavailable in TWRP
I did a make backups with TWRP and TitaniumBackup.
May I ask some more questions, i do want to understand the procedure.
Galactus said:
Flash stock rom in ODIN (Backup, backup, backup anything valuable)
Click to expand...
Click to collapse
I guess the stock ROM is already encrypted - is that the reason why TWRP doesnt have access to /data (as well to the internal /sdcard) till the encryption is disabled?
Obtain root using CF-Auto Root method
Click to expand...
Click to collapse
After flashing stock the bootloader is locked again, so I do have to unlock the "OEM unlock" per developer settings again? The phone wont be wiped afterwards?
Install TWRP, allow modifications, don't wipe /data
Click to expand...
Click to collapse
May i recover/restore here a formerly per TWRP backuped ROM? I guess, this want be possible, hence TWRP doesnt has access to /data, nor to /sdcard?!
Which partitions I am allowed to restore, respectively is there a chance to recovery somehow the TWRP backup (it was soo much work).
Or can i disable encryption and enable it again, after restore?
You can only flash zips from external SD card. Internal storage will be unavailable in TWRP
Click to expand...
Click to collapse
After everything went well, I am going to encrypt the ext-sdcard too. I guess, TWRP will be useless then...
tefole said:
I did a make backups with TWRP and TitaniumBackup.
May I ask some more questions, i do want to understand the procedure.
I guess the stock ROM is already encrypted - is that the reason why TWRP doesnt have access to /data (as well to the internal /sdcard) till the encryption is disabled?
After flashing stock the bootloader is locked again, so I do have to unlock the "OEM unlock" per developer settings again? The phone wont be wiped afterwards?
May i recover/restore here a formerly per TWRP backuped ROM? I guess, this want be possible, hence TWRP doesnt has access to /data, nor to /sdcard?!
Which partitions I am allowed to restore, respectively is there a chance to recovery somehow the TWRP backup (it was soo much work).
Or can i disable encryption and enable it again, after restore?
After everything went well, I am going to encrypt the ext-sdcard too. I guess, TWRP will be useless then...
Click to expand...
Click to collapse
Once you flash the stock ROM, the phone is encrypted before first boot
Once you OEM Unlock, it stays that way unless you attempt to re-lock it. Once you flash a stock ROM and go to developer settings, you'll see OEM Unlock is still on
Encrypted device = No restoring of any kind in TWRP, that is the trade off. Some people use FlashFire to back up and restore. I tried once a while back and it didn't work. Others seem to be ok
If external sd is encrypted also, then your only chance is to use FlashFire. TWRP is basically useless
Galactus said:
Once you flash the stock ROM, the phone is encrypted before first boot
Once you OEM Unlock, it stays that way unless you attempt to re-lock it. Once you flash a stock ROM and go to developer settings, you'll see OEM Unlock is still on
Encrypted device = No restoring of any kind in TWRP, that is the trade off. Some people use FlashFire to back up and restore. I tried once a while back and it didn't work. Others seem to be ok
If external sd is encrypted also, then your only chance is to use FlashFire. TWRP is basically useless
Click to expand...
Click to collapse
Thx for your reply
After I flashed stock and finally customized my installation, would this be safety feature to relock the OEM? Is a relocking wiping also the whole phone or only the unlocking?
So that means, that if go through this instructeres, i cant flash any CFW, neither i cant restore my TWRP backup?
Thats a pitty.
tefole said:
Thx for your reply
After I flashed stock and finally customized my installation, would this be safety feature to relock the OEM? Is a relocking wiping also the whole phone or only the unlocking?
So that means, that if go through this instructeres, i cant flash any CFW, neither i cant restore my TWRP backup?
Thats a pitty.
Click to expand...
Click to collapse
If you try to relock OEM, your device won't boot lol. I learned that the hard way months ago. Had to start from scratch.
What custom firmware are you trying to flash? If you mean custom ROMs then theoretically speaking you should be able to flash them using FlashFire.
Thank you for the hint - this will me spare the fate
I chose S7_extreme_debloated from @Battlehero.
I am quite happy with that CFW and i thought, i can install my apps and customize the system and start the encryption - didnt worked.
So, I will begin from the scratch too. It would be great, if I could start with this CFW after, flashing stock.

TWRP says no OS is installed, but I just flashed it. Can anybody help?

Hi,
Its been a while since I been attentive to my Pixel. I was a lucky one who managed to get a Verizon 7.1.2 with an unlocked bootloader. I unlocked the bootloader, flashed a ROM, and rooted and haven't had a single major problem since.
I was running Resurrection Remix from about March and I yesterday I wanted to try to use Android Pay, so I followed a tutorial I found in another thread here to install Magisk, and when it was all said and done I ended up in a boot loop where the phone would reset as soon as it reaches the Google logo, ramdump, and eventually boot back into TWRP.
In the attempts to delete out all kinds of caches and dalviks and factory resets and whatever else, nothing worked.
So in the end I decided to just flash a new ROM. Flashed the latest Pure Nexus, reflashed TWRP, flashed the vendor image... went to go reboot and it gives me the WARNING! NO OS INSTALLED! error. I thought that was odd and decided to just update to the latest Resurrection Remix - same problem.
At this point I am unsure what to do next. I don't care about any user data on the phone, I just want to get it back up and running with a new ROM.
I have a few questions and thank you in advance for all help you may be able to offer:
1) Why am I getting the NO OS INSTALLED issue directly after flashing a ROM? Logs indicate no errors whatsoever. /system/ is mounted. Every time I boot into TWRP it asks me if I want to Keep System partition read only. I always tell it to allow modifications and never ask me this question again - it asks every time. Is it possible that /system/ can actually remain empty even after a fresh ROM install that gives no errors in the log?
2) I believe that I am supposed to reflash to stock image that this phone shipped with to start all over. If I reflash back to stock, will my bootloader have any chance of locking again? I don't even know what version the stock image was, and I'm further confused/concerned about the fact that it was a 7.1.2 image I shipped with - from my understanding there were security updates which make unlocking/rooting impossible. I don't understand why you have to start that far back - is it even needed? The latest Resurrection Remix ROM install instructions assumes that I am on latest "Firmware" NOF26W. This is another issue I don't understand - what is a firmware? The full factory image? In any case, NOF26W is specifically for Rogers Google Pixel devices. Since I need to be on this "firmware" before I install latest, can I just flash the NOF26W Stock image despite the fact that I am using a rooted Verizon Pixel? The NOF26W image is 1.8GB: What exactly in this ZIP am I supposed to flash?
3) There were various weird things about this phone/flashing ROMs that I seem to recall such as having to boot an older TWRP before flashing ROM and then flashing the newer TWRP - is any of this stuff still relevant?
4) I also remember that many people were fastbooting TWRP rather than flashing TWRP for some reason - are there specific builds/non-standard stuff required for any of this to work on the Pixel?
I really appreciate all and any help that anybody can provide. If there's files that you're referring to, PLEASE send links. I need to get this phone back up and running ASAP.
Thanks again!!
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
rohitece06 said:
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
Click to expand...
Click to collapse
This. I just reboot anyway after seeing that message and I've never had any issues.

Categories

Resources