I only want to root my device, but the toolkit asked me to flash no_verity.zip after pushing systemless supersu, and I followed the instruction appeared on the screen to flash no_verity.zip.
Can anyone tell me if pushing disable DM-Verity - Encrypt is necessary after pushing systemless supersu and what it actually does?
If I have flashed no_verity.zip in twrp, how can I uninstall it?
Related
Recently developer topjohnwu has modded and released Systemless Xposed for lollipop and marshmallow for easier flashing of OTA's. I have actually tried it but unfortunately after flashing it with proper intructions, still I have lost private mode as well as dm-verity verification fails. Anyone who has successfully overcome these errors please POST THE STEPS HERE for me & others to use it.
Ruuu said:
Recently developer topjohnwu has modded and released Systemless Xposed for lollipop and marshmallow for easier flashing of OTA's. I have actually tried it but unfortunately after flashing it with proper intructions, still I have lost private mode as well as dm-verity verification fails. Anyone who has successfully overcome these errors please POST THE STEPS HERE for me & others to use it.
Click to expand...
Click to collapse
I'm not quite sure what dm_verity verification means but I'm able to use Android Pay with Systemless Root and Systemless Xposed as long as I turn Xposed off and reboot. See this post... http://forum.xda-developers.com/sprint-galaxy-note5/help/android-pay-systemless-root-t3391801
henderjr said:
I'm not quite sure what dm_verity verification means but I'm able to use Android Pay with Systemless Root and Systemless Xposed as long as I turn Xposed off and reboot. See this post... http://forum.xda-developers.com/sprint-galaxy-note5/help/android-pay-systemless-root-t3391801
Click to expand...
Click to collapse
Is your private mode working after flashing Systemless Xposed. If yes, please let me know the steps.
When you boot into recovery mode (stock and not twrp) Samsung will check if you have modded or not. If you're modded then dm-verity will fail. And with it failing OTA'S won't be installed. So how do you go onto installingredients OTA'S? Do you use flashfire instead?
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
Hey everyone. I just got my new OnePlus 3T a week back. I was loving it till today but I wanted to mess with my phone and I guess I did just that. Long story short, I was on 7.1.1 and unlocked OEM and installed TWRP. Phone booted up and i went into recovery and installed Super SU and the dm verity. After this step, my phone is stuck on the boot animation. I'm able to access TWRP as well as Fastoot ADB. I want to sideload the stock OxygenOS ROM into my phone through ADB, but i'm unsure which file to flash and the exact process. Could someone please help me out? :crying:
That's why you always make a nandroid back up
I figured out why the adb sideload wasn't working. I tried to do the sideload directly from the ADB cmd while my phone was in fastboot mode. So, I tried an alternate method by going into TWRP and doing the sideloading from the advanced menu. It worked and I'm setting up my OP 3T now Guess I jumped the gun by posting here without thinking.
On a side note, my device doesn't have root access now. Maybe it never got installed properly before getting bricked. I think it had to with the fact that I had updated to 7.1.1 by using a VPN. I'm pretty good at following instructions so i couldn't have gone wrong. Can anyone tell me if i can go ahead and root my device now that I'm back on stock OS?
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
kunal1540 said:
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
Click to expand...
Click to collapse
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Rahulsingh9367 said:
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Click to expand...
Click to collapse
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
fluster84 said:
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
Click to expand...
Click to collapse
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Azar_98 said:
Try the latest version of magisk, v11.6.
http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Worked perfectly and no hassle at all. Thank you so much!
Rahulsingh9367 said:
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Click to expand...
Click to collapse
Always flash the latest magisk, and you don't need to flash phh or anything else. Magisk now comes with magisksu that works great with OOS 4.1.1.
Check the link below for latest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless
If you don't mind losing your data, you can try this 100% clean but slightly painful install. It might be overkill for most but you can start from a clean slate. Backup your stuff to the PC before you do this.
1. Flash compatible stock recovery (stock recovery for android N) in fastboot
2. Now choose to wipe everything (even music, photos) from stock recovery. You will lose everything on your phone.
3. Sideload OOS 4.1.1 rom
4. Reboot and complete phone setup
You are now completely stock except with a unlocked bootloader. In order to gain root, continue further -
5. Enable developer options in Settings and then enable Advanced Reboot and USB debugging
6. Reboot to fastboot and flash twrp 3.0.4.-1
7. Reboot to twrp and flash Magisk v11. 1 zip
8. Reboot and install Magisk Manager from playstore.
Congratulations, you have a stock 4.1.1 with working root and it will even pass safety net check (enable magisk hide in magisk manager)
Hi,
Till this morning i had rooted Android 6.0.1 (MOB30O) in my Nexus 6. I hadn't updated before because i was lazy, i didn't want to un-root and re-root. But since I've been having battery issues, I decided to give 7.1.1 a try.
I always rooted my device using Wugfresh Nexus Root toolkit... and it always worked great. So, I basically un-rooted my device, using said tookit, and updated it thru OTA. Problem is... I ended up in Android 7.1.1 NGI55D. When I was about to root using NRT, i noticed that last supported version was N6F26U. Also noticed that NRT last version is from September 2016, so i don't know if it is deprecated or what...
So basically, i have a question here: Is it possible to root 7.1.1 NGI55D? If so, can anyone point me to the right direction? I have always used NRT, but i can follow a tutorial and do it manually. Just don't wanna mess things up.
Thanks in advance.
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
ktmom said:
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
Click to expand...
Click to collapse
i need unlock bootloader before to root?
Yep.
Hi, I want to install ArrowOS on my OnePlus 3T. Since I am a noob to CustomROMs I saw that when installing TWRP on OnePlus 3T there is an issue with dm-verity which can cause bootloop issue.
All of the install guides mention flashing SuperSU at time of TWRP installation to bypass dm-verity issue.
But since SuperSU project is now replaced with Magisk, should I flash SuperSU with my ROM installation then uninstall it and flash Magisk or should I flash Magisk instead of SuperSU from the get go, and will that cause any issues with dm-verity or bootloop.
Any help would be great. Thank you everyone.