Hello guys,
Today I flashed the dm-verity disabler, however I had several problems and I would like to do the reverse process, I am getting a message at device startup and I would like to remove this dm-verity disabler.
Although my device is 64gb was showing only 24gb, and when trying to put a custom rom is asking for the decryption password, I tried to put my password but not right .. I would like to know how can I remove the dm-verity disabler that I flashed today .
Message that im getting when i boot the device: The dm-verity is not started in enforcing mode and may not work properly.
here the link that i flashed: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
i saw this file on: https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
If anyone can help me, I'll be very grateful.
Print message: https://uploaddeimagens.com.br/images/000/809/590/original/IMG_0087.JPG?1484344949
Very simple, follow this guide: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Chuck Bartowski said:
Very simple, follow this guide: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
Thanks!!! its worked !!
Related
After unlocking the bootloader, I installed the latest versions of TWRP and Magisk. It worked after a few reboots, but after installing the Xposed Magisk module the phone got stuck in a boot loop.
I tried to use the Magisk uninstaller, didn't work, tried to use eRecovery and HiSuite recovery, and then I get an error how my phone is unsupported or how there was an issue getting package information for my device.
I tried to flash the SYSTEM.IMG of the same version thinking how it will let me factory reset my phone... and it didn't work. Tried using HWOTA (Which in the end fixed my problems)*, but then I realised it only works for Mate 10 Lite (or maybe I'm just dumb)
I got my phone softbricked and cought in a bootloop, and I don't know how to unbrick it. So I'm asking You guys for help because I really f***ed up, and Your help would be very much appreciated.
Model BLA-L29 (C432) - Europe
*Edit: Fixed by following this guide https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Boot to twrp and flash install the same exposed module (you can find it in MagiskManager folder) it should uninstall and get you out of bootloop. Hope it works!
Read You dingus
Nevermind it turns out it was error on My part (which I think You guys all expected), because it looks like I suck at reading REAL easy instructions.
So the problem was I didn't pay attention to one of the prompts of this tool/guide: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
After downloading all 3 stock firmware/update files, dropping them, and then renaming them in the HWOTA8_Mate10\repack folder so I could run the repack.bat that would patch them. I did that part just easy, but then I managed to screw up a even easier thing, which was running the ota.bat and following the instructions.
What went wrong was I didn't press ENTER after opening the recovery, so My device never got to do the updating/installing part that all these previous steps were leading up to.
Lesson learned: Read, and follow the steps, it really isn't that hard
SOLVED
Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.
_hunter said:
Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.
Click to expand...
Click to collapse
Xposed oreo beta 4? Or an another version?
Sent from my HUAWEI BKL-L09 using XDA Labs
Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Dantes991 said:
Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Click to expand...
Click to collapse
You should have deleted "security log agent" in system/app before rebooting.
stonedpsycho said:
You should have deleted "security log agent" in system/app before rebooting.
Click to expand...
Click to collapse
Yes i detected log security agent
Dantes991 said:
Yes i detected log security agent
Click to expand...
Click to collapse
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
stonedpsycho said:
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
but I can not flash the twrp
Dantes991 said:
but I can not flash the twrp
Click to expand...
Click to collapse
I think you need to flash the stock rom with Odin and basically start again.
You could just flash the dev-base rom which is basically just the stock rom but with all the above disabled already.
Hi
*No one answered on respective forum so kinda had to open a thread*
Im trying to install pixel exprience caf... Twrp gives:
28 (ErrorCode DownloadOperationExecutionError)
then
Updater process ended with error 1
previously I had havoc os and I followed the usual procedure as I did for havoc..
I tried adb sideload too. Still same error.. Only thing I didnt do is wipe data(for removing encryption) which seems unnecssary.. Can anyone point me in right direction? Someone who was able to install? It seems Im missing something..
Update 2:
Temporary boot of twrp image 3.2.3 cause OpenDeviceError and twrp 3.3.1 cuause error 28 just like above..
I tried above guide from @firdausimbolon didn't help
https://forum.xda-developers.com/mi-a2/how-to/how-to-avoid-error-28-flash-rom-t3941024
I would really appreciate a proper solution, thanks
wipe all partitions and format data as well on both slots then boot into 3.2.3 if it still doesnt work go to stock oreo rom then follow this guide
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Stoopid Dickhead said:
wipe all partitions and format data as well on both slots then boot into 3.2.3 if it still doesnt work go to stock oreo rom then follow this guide
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I have twrp 3.3 already which was installed by Havoc OS, Should I just temporary boot into twrp 3.2.3?
Cause It possibly will cause OpenDevice Error.
Also I followed the guide already, fastboot -w doesn't work, says failed to get user data so I have to do wipe from twrp itself(system,cache,data) + flashing in both slots cause same error... I will try again more carefully, Maybe I missed some stuff, thanks for reminding me again, I might get it right this time!
update2:Simply downloaded file was corrupted, Now It's Installed
wasd588 said:
I have twrp 3.3 already which was installed by Havoc OS, Should I just temporary boot into twrp 3.2.3?
Cause It possibly will cause OpenDevice Error.
Also I followed the guide already, fastboot -w doesn't work, says failed to get user data so I have to do wipe from twrp itself(system,cache,data) + flashing in both slots cause same error... I will try again more carefully, Maybe I missed some stuff, thanks for reminding me again, I might get it right this time!
update2:Simply downloaded file was corrupted, Now It's Installed
Click to expand...
Click to collapse
temp booting 3.2.3 worked for me although i booted in different slot than 3.3.1, also glad that your device works.
Glad that your device is bootable again.
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
alfadyn said:
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
Click to expand...
Click to collapse
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Rooted.ndroid said:
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
alfadyn1 said:
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
Click to expand...
Click to collapse
Do you have twrp installed right now?
And did you flash RMM bypass?
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
yes i flashed rmm bypass v2 and i realized that there is version 3 i will try with it. and tell how it goes
---------- Post added at 12:02 PM ---------- Previous post was at 11:32 AM ----------
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
i didnt get the. only official relases error and it booted up. but i got a sweet bootloop right now . im done with it i ll never try to root again can u tell me how do i get rid of this bootloop
edit: got out of bootloop flashed official firmware. thank you for the help never gonna try to root again