Encryption and custom rom - Samsung Galaxy S7 Questions and Answers

Hi, how does encryption and root get along?
I rooted, flashed TWRP and flashed a custom rom (decent rom) and now that I can install the email client to check work mails it asks me to encrypt the phone.
Will I be able to update the current rom if the phone is encrypted? And how about flashing a different rom?

https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
It's possible. Not sure if he figured out how to update.

Related

got a question

I was on a custom build of android 6 and had twrp and then I got an update and installed it. Now I have lost TWRP... Is that even possible? Also when in recovery it says can't mount sdcard!
Was it a custom ROM based on stock 6.0? If it is, it's possible that the update was pushed to the phone because Google sees the phone as running a stock ROM and only a stock recovery can install a stock recovery.
What I don't get is how and why users running custom roms receive and accept stock OTA notification updates.
If you had twrp installed, then the OTA would not install - it would fail.

Updating firmware with rooted phone and custom kernel

I rooted my OnePlus when it first came out and had a custom kernel on it, and since then I haven't updated it. I want to update to CM13 but am not familiar with the process that needs to be done without losing any data or risk bricking my phone. I believe it has TWRP recovery and Franco kernel (I don't have the phone with me so can't verify).
Do I simply unlock the bootloader, backup data and then flash the new custom ROM? Would I be able to flash a custom ROM without losing root? I want to keep the root but go back to stock kernel.
Thanks
When you unlock your bootloader you'll lose all your data. However if your bootloader is already unlocked, proceed to flash this TWRP version (unofficial TWRP 2.8.6.0.6 by kumajaya): www.androidfilehost.com/?fid=23991606952609056
Other versions of TWRP have bugs not updating the firmware properly.
You'll lose your root but CM13 nightlies have their own root in the developer settings. Or you can flash SuperSU 2.67 on top after you flash the ROM if you prefer SuperSU.
Oh and make a TWRP nandroid backup first before you do anything. Backup the firmware partition too if it's not checked by default.

Samsung S4 SGH-I337 Safestrap not working rom

Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
[R]ainbow[D]ash said:
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
Click to expand...
Click to collapse
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
[R]ainbow[D]ash said:
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
Click to expand...
Click to collapse
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The stock slot remained intact. But if I take the kernel from OC3, then the device will also not boot up and the recovery will become non-working.
Send me the stock ROM for flashed the custom ROM through the Safestrap. And send me the version of the Safestrap for custom ROM
I understood what the problem is. I installed another ROM NB1 and it all worked for me.

Questions about kernel, custom rom and flashing/Ota updating.

I have an OnePlus5 with latest Oxygen Os android 7.1.1, rooted with magisk and with TWRP recovery. I flashed yesterday a custom kernel (blu spark), cause i wanted better battery stats. But i dont see any changes. Nor more advanced options, neither visual changes. What does exactly a kernel change to the phone? How does it differ from a custom rom? Do i need extra programs or programming in order to make full use of the kernel?
Now that i have the custom kernel, what actions should i take if :
1) I want install a custom rom
2) I want install stock rom
3) I want install another or stock kernel
When should i take full backup and why? (Nandroid via TWRP or backup with TITANIUM BACKUP??) What about OTA updates? How can i update to newest rom in each case? Each time a new rom update occurs should i take full backup, flash the rom and install them all from the start??
Someone help me please?
Sent from my ONEPLUS A5000 using Tapatalk

Flashing custom rom and data preservation

I've unlocked the bootloader and installed a custom rom and installed magisk. I know that the data is encrypted but I wanted to know if the data will be removed if a custom rom is flashed on top of it again via TWRP?
Will it also be the case for a rom OTA or will data be preserved?

Categories

Resources