I need root to restore from titanium
Is there a way to upgrade without loosing data when on 7.1 with unlocked bootloader and twrp?
I think you can just use the fastboot process to upgrade. I don't know if you will need to do a wipe before it will boot or not but once it boots, you should be able to flash TWRP again and install Magisk from there. I don't know if the modules will work until the kernel is modified. Keep an eye on this thread. https://forum.xda-developers.com/moto-g5s-plus/development/kernel-resurrected-kernel-t3716267/page16. Once the Kernel is updated, it should pass safety net and the Magisk modules should work. I haven't updated yet because I am waiting on the updated Kernel.
Edit: Be sure to do a full backup including the EFS partition in TWRP before doing anything... I have seen so many people lose their IMEI, including mine. Without the EFS backup, it will be very difficult to restore your IMEI.
Related
I'd like to encrypt my phone just to try it. But, being cautious I'd like to make sure I can restore the thing if I want to. By, "restore," I don't care about decrypting it, but I sure want TWRP to still be able to restore a previously saved backup.
If, after encryption, TWRP will not be able to restore then I think I will pass on the encryption as it will be too much work to reconfigure a new CM install.
So, the question is, if I encrypt, will TWRP (current version) still be able to restore a saved-backup or would I have to revert to ADB and a new install of CM12.1?
Thanks
hey guys, so I want to encrypt my phone but I want to stay rooted with magisk and xposed. (Using SuperSU 2.78 SR3). Device: OnePlus One running SultanXDA's CM13.
Are there any special steps I need to take before I start the encryption process? do I need to completely unroot and remove all traces of all these before going back or will it just work?
I haven't seen this question addressed before and this would help others with the same questions.
Thanks for any advice!
Since there was no support from anyone, I decided to just remove everything (xposed, magisk and supersu) then encrypt, and finally re-add everything back. I did this just to avoid any complications and all works fine without issue.
@Nomelas what version of magisk did you use? and did you sideload them or just flash with the cache work around?
I've been at this all day with no luck
@GbizzleMcGrizzle what phone are you using? I had to completely remove everything before encrypting. Also reflashed stock system
@Nomelas Galaxy S7 (SM-G930F) it wont encrypt with magisk installed and magisk wont install after it has been encrypted.
@GbizzleMcGrizzle are you flashing through twrp? (are you decrypting when you boot into twrp)
i've tried flashing in twrp and sideloading. I don't think I can decrypt in twrp but magisk says it has a work around for not beiing able to boot /data and supposedly put in in cache and then moves it to data after boot so IDK
First off, my apologies if wrong sub-forum or what-not, I'm new here.
Secondly, and my reasoning for this post - I was rooted with SuperSU, then read more into Magisk and realised Magisk was probably the better option. However, I was having SafetyNet Check issues and failing all tests so I decided to revert to EMUI 4.1 again (EVA-L09 C432B166) but still failing SafetyNet Checks. I'm wondering if flashing a previous ROM hasn't de-rooted my system or left some residue from the Magisk root. Any help appreciated greatly, thanks.
try to flash this : https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 , then update to latest, b390 if im corect, i got L19 and for me latest is b386.
unlock bootloader, instal this twrp (this is for nuget, dont instal this twrp on marshmalow) : https://forum.xda-developers.com/p9/development/twrp-t3565703 (important, after instaling twrp restart into twrp recovery, not os first time, duno way, but there are a lot who say need to do that)
reboot in system, reboot in recovery, backup boot in recovery (use sd card for backup storage, better than internal, why? if sometime you broke safetynet, you can restore it in twrp when restore boot (there is safety net info))
flash magisk v14 (dont use beta v14,3 or etc, there are safetynet bug, and not work it) here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
for busybox use https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=lv first, then you can https://play.google.com/store/apps/details?id=stericson.busybox&hl=lv if prefer this.
!doing all thease things you will delete all files in internal storage, backup all needet files!
There no other fix for safety net right now, this is best i found for myself
Arnys said:
try to flash this : https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 , then update to latest, b390 if im corect, i got L19 and for me latest is b386.
unlock bootloader, instal this twrp (this is for nuget, dont instal this twrp on marshmalow) : https://forum.xda-developers.com/p9/development/twrp-t3565703 (important, after instaling twrp restart into twrp recovery, not os first time, duno way, but there are a lot who say need to do that)
reboot in system, reboot in recovery, backup boot in recovery (use sd card for backup storage, better than internal, why? if sometime you broke safetynet, you can restore it in twrp when restore boot (there is safety net info))
flash magisk v14 (dont use beta v14,3 or etc, there are safetynet bug, and not work it) here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
for busybox use https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=lv first, then you can https://play.google.com/store/apps/details?id=stericson.busybox&hl=lv if prefer this.
!doing all thease things you will delete all files in internal storage, backup all needet files!
There no other fix for safety net right now, this is best i found for myself
Click to expand...
Click to collapse
Thank you, this worked for me (except I used 14.3 of Magisk, currently SafetyNet Checks are passing so until they fail, I'll stick with it). Many thanks!
Hi, I'm on Pie, rooted, Magisk, TWRP. I downloaded latest firmware through XperiFirm. If I remove file userdata_X-FLASH-CUST-C93B.sin from firmware, my apps will be intact. But can I also remove boot folder, to keep my current loader (TWRP)? Also will such upgrade remove root ?
Ideally I want to keep apps, TWRP, root (Magisk), not erase SD card. Is it possible?
Interested... I've think all time, to hold the user data, I just delete the sin file which contains the word user in front....
following this!
same situation, curious if a upgrade to new FW is able of keeping the userdata.
It's normal, that root is lost after update..... Supersu or Magisk must be flashed after update the system.
How to keep TWRP? It's the question, where TWRP is located and linked.... I must reflash also TWRP all time after new update.
On my phones I have always used the backup's function offered by TWRP's recovery .
I've always been able to restore the nandroid's backups without any problems.
However, whenever I try to restore a backup on my Note 9, the phone always goes into bootloop.
I've never had this happen with my other phones (S3 and LG G5).
I wouldn't want to have to do other things to do a successful restore.
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
XTrail02 said:
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
Click to expand...
Click to collapse
Thank you for your reply.
I mean, let me get a better understanding of what you did.
Did you first flash the "Disable_Dm-Verity_ForceEncrypt"'s zip and then restore the nandroid backup?
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
XTrail02 said:
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
Click to expand...
Click to collapse
I already do all this when I install the new rom. So, my phone should be decrypted.
Then after some time I make a nandroid backup. However, when I go to restore the backup the phone goes into bootloop.
So, it means that with the restore the phone comes back encrypted again. That's why it goes into bootloop.
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
XTrail02 said:
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
Click to expand...
Click to collapse
If I understand correctly, before restoring a nandroid backup you flashed 'disable_dm-verity_forceencrypt.zip' and then did the restore.
Right?