Database Develop

dm verity (red)

I want do clean install so I evrything wipe expect user data. And there problems started. I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
I tried full wipe data - don't work. I was looking in the forum Oneplus any tutorial didin't work.
I tried this tutorial https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094 to remove warning. It works but after update from 4.0.2 to 4.1.6 warning screen again came back. It started after updating 4.1.6 to 4.1.7.
If you can slowe this problem I will be grateful. And i sorry for my engilsh

Wronko said:
I want do clean install so I evrything wipe expect user data.
Click to expand...
Click to collapse
If you want a "clean" install, user data is the most important thing to wipe; as it is the mostly likely thing to cause problem (on a new ROM, etc.).
Not related to the other issues you mentioned. But important to note, anyway.
Wronko said:
I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
Click to expand...
Click to collapse
I'm confused. If you haven't installed TWRP, how you are trying to root? You need TWRP, in order to root.
Also, sideload can be more problematic than just flashing a ROM in TWRP. My suggestion, would be to stop messing around, and just flash TWRP.

* I wanted to write that After installing update 4.1.6 as well as on the factory as a TWRP warning appears.
*On TWRP can't root device, TWRP think the su ZIP archives od broken.
*And TWRP by bluetooth Spark can't decrypt device (my old password od bot working )
Device works fine by In addition to the aforementioned problems

Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...

ilyr73 said:
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
Click to expand...
Click to collapse
Can you link for your SuperSU zip and TWRP?

Wronko said:
Can you link for your SuperSU zip and TWRP?
Click to expand...
Click to collapse
TWRP for Oneplus 3T
SuperSU 2.79 for Oneplus 3T

After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.

Wronko said:
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Click to expand...
Click to collapse
Have you flashed TWRP and 3.5.4 first? Have you used bootloader with "fastboot format userdata" before flashing supersu (remembering that after this, normal boot should not start before supersu is flashed)?
Also I am not sure if flashing 3.5.4 image will update the firmware as well, but for safety, you might try to flash that as well: Oneplus 3T Firmware collection

I didn't flash 3.5.4 at all, just 4.0.2. I used "fastboot format userdata" in bootloader. And then there was a problem (boot loop.). And after that i booted into recovery(I had then stock) asked me for password )At this point I did not have any) so I wiped my device again (recovery suggest it). The device turned on normally, but still i had dm verity. Finally I updated by OTA to 4.1.6 and dm verity screen was gone.
At this point I install TWRP and rooted, without any problem.
So i think fix for this situation was going back to full stock and use OTA. (Again sorry for my English, I trying my best)

absolute cluster**** after attempting to move from 4.5.0 to 5.0

So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?

I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!

Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.

Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...

Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip

I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0

Recover data from soft-bricked (bootloop) phone

Background:
Went to update Magisk via TWRP, phone now bootloops (and gets really hot when charging).
Before I go ahead with flashing an older firmware, to try and get it running again, I was wondering if there was any way of retrieving data from the phone?
I can still boot into TWRP without issue, although I did notice if i go to Install and select source, Internal Storage shows as empty, while External is fine.
Failing data recovery, any suggestions for unbricking it without wiping anything? I've tried un/reinstalling Magisk via TWRP, wiping data/cache/dalvik, but no luck so far.
Thanks

I know where i ****ed up now. By flashing Magisk directly from TWRP.
Tried reflashing it via the guide on page one:
"Instructions for Root Access"
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
Now getting past the warning screen, but not past the Huawei logo.
Going to try remove Magisk altogether, and see if it boots up. If so, will install Magisk again.

Flashed original ramdisk.img and it now shows the boot animation, but doesn't get past there....progress i guess.

After rooting G9+ & installing an unofficial LineageOS 18.1, root was lost & need help getting it back

I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.

Have u tested lineage, is
everything working fine?

UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.

doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?

Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.

UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)

Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)

Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.

doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel

There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro

The ROM in the O.P. works.​
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).

M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!

I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!