yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 Questions & Answers] bam099:
I was working on rooting my device, and had a working root successfully with Magisk. But then I wanted to remove it and relock my bootloader, that's when the trouble started.

I am able to boot the phone and it is working. I can boot to recovery (stock OEM not TWRP), can boot to bootloader, and can boot and use the Oxygen OS. But I cannot get fastboot to run to lock the bootloader. ADB devices comes up empty. These are the steps that I've tried:

-using it on my chromebook that was working with ADB before the unrooting mess

-installed fastboot and adb along with Oneplus USB drivers on a fresh Windows 8 copy

-2 different red OEM oneplus cables

My goal is to return completely to stock and a locked bootloader. Any help would be appreciated, it really seems to be a phone issue and not a driver issue. Thanks everyone!
[OnePlus 6 Questions & Answers] Deleted member 7671171:
Use the unbrick tool. That autolocks bootloader when it flashes stock.
[OnePlus 6 Questions & Answers] bam099:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
[OnePlus 6 Questions & Answers] iElvis:
Are you sure you have USB debugging checked in developer options?
[OnePlus 6 Questions & Answers] bam099:
Absolutely. Just checked again. I would normally say it was a driver issue, but it was working fine until I flashed a boot.img and also I used a windows pc and a Chromebook and chrome os pretty much comes ready to talk to android phones or of the box. I was wondering if adb could have been messed up during the flashing of boot images.
[OnePlus 6 Questions & Answers] Deleted member 7671171:
No fastboot needed, it's done with the phone off.
[OnePlus 6 Questions & Answers] bam099:
Even better! I will definitely try the tool and report back.
[OnePlus 6 Questions & Answers] bam099:
This was correct and it worked. Phone is restored back to stock with a locked bootloader and everything is working as it should.
[Vivo Nex Guides, News, & Discussion] Saloei:
Just installed update version PD1805_A_1.16.5 (2018.07.16)

Update states improvements with Bluetooth, fingerprint recognition, system performance, camera AI scene recognition, phone network adaptability, and other phone optimizations. Make sure to read the update notes.
[Vivo Nex Guides, News, & Discussion] t7gc7:
1.16.7 ? Did you get before the 1.16.5 ?
[Vivo Nex Guides, News, & Discussion] paatha13:
Update version PD1805_A_1.16.7 (2018.07.16)

Yes I got back to back both updates.

First one was 1.15.7 and second one 1.16.5

Haven’t got so far 1.16.7
[Vivo Nex Guides, News, & Discussion] t7gc7:
Are you sure about the .7 , it's not 1.16.5 ?
[Vivo Nex Guides, News, & Discussion] mercynight:
received the update today mine is PD1805_A_1.16.5
[Vivo Nex Guides, News, & Discussion] Saloei:
Don't know how I saw 7. I made corrections. The version i have ends in a 5.
[Vivo Nex Guides, News, & Discussion] rsjoxford:
Vivo nex S fails my company's device policy as there is no secure start up at reboot...as.phone not encrypted...will vivo fix this...any work around..any advice ..thank you
[Vivo Nex Guides, News, & Discussion] Saloei:
Don't know if this is what you need but in Settings\More settings\Security - near the bottom you see Credential Storage.
[Vivo Nex Guides, News, & Discussion] Co.okie4u:
Nope, on Vivo, Xiaomi and OPPO not possible.
[Vivo Nex Guides, News, & Discussion] paatha13:
Just received new software update

View attachment 4554088
[Vivo Nex Guides, News, & Discussion] Sudisudeep:
I'm have vivo, rev1.15.4 version but it has not smart split, easy touch, smart lock, app clone and other options
[LG G7 ThinQ  Questions & Answers] MeatyCoins:
Hey All,

Im trying to make my 128gb SD card part of the adoptable storage.

After following the guide it shows my SD card as double the size with half of it being storage, and I am unable to complete the last step to migrate data as settings crashes.

Has anyone successfully setup adoptable storage on the LG G7? I have the t-mobile variant.
[LG G7 ThinQ  Questions & Answers] Computerguy777:
Newer phones are meh..

Most newer phones do not allow for adoptable storage or upgrading the battery. It's sad but those money grubbers did it to punk the consumer. Maybe try an LG g5 or LG v20 if you are looking to use adoptable storage.
[Android Software Development] rippledrums:
Hi!

Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?

Thanks!
[Android Software Development] shadowstep:
[MENTION=6037748]Zackptg5[/MENTION] Thanks for the zip! :) I trust this will work for both -- Treble and non-Treble ROMs, yes?
[Android Software Development] Zackptg5:
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at

Yup :)
[Android Software Development] rippledrums:
I found this because I saw your post in [MENTION=7874870]Xennet[/MENTION]'s thread for OP3/3T Oxygen OS patched boot.img files.

Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough? :)
[Android Software Development] Zackptg5:
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
[Android Software Development] rippledrums:
Awesome, thanks! :laugh:
[Android Software Development] DEVILOPS 007:
[MENTION=6037748]Zackptg5[/MENTION] First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you:D
[Android Software Development] Zackptg5:
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).

Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
[Android Software Development] DEVILOPS 007:
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
[Android Software Development] Zackptg5:
I wouldn't call it more well done but rather more complete :)

And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
[Android Software Development] repey6:
[MENTION=6037748]Zackptg5[/MENTION] hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
[Android Software Development] bdwilk:
[MENTION=7494055]DEVILOPS 007[/MENTION] I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
[Android Software Development] Zackptg5:
You'll need to format data. Then flash rom and kernel, then this after

Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
[Android Software Development] DEVILOPS 007:
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
[Android Software Development] bdwilk:
I'll do it again and get a log for you another time.

ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)

Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.

Flashed dm-verity v2 and it booted fine.

OnePlus 5t

I believe he's just telling dude how to decrypt for the first time.
[Android Software Development] DEVILOPS 007:
Oh I thought he was responding to you. My bad lol
[Android Software Development] Zackptg5:
Ya, you just need to format data to decrypt
[Android Software Development] repey6:
This is a copypaste from Samsuyng Tab A thread:
[Android Software Development] johnb380:
Of course he's still encrypted this zip isn't going to decrypt your phone. It's for once your decrypted and flashing a rom it will not allow the rom zip to encrypt your device and will allow it to boot decrypted and without the insecure verity check blocking boot.
[Android Software Development] inpush:
what happens if I flash this zip without the previous data format ??

I don't copy the storage data in to PC

---------- Post added at 04:30 AM ---------- Previous post was at 04:23 AM ----------

what happens if I flash this zip without the previous data format ??

I don't copy the storage data
[Android Software Development] LttHckr:
Sorry about that.
[Android Software Development] Kireto00:
What is the difference between thus file and lazy flasher no opt encrypt zip ? What is difference or there is no difference ?
[Android Software Development] Zackptg5:
A lot. The zip your talking about only patches fstabs (and doesn't patch ramdisk fstabs if memory serves me correctly, only vendor fstabs for Oreo+). My zip patches all fstabs, dtbs, uses magiskboot to patch the rest of the boot img, creates .magisk and SuperSU files, and some other stuff I'm forgetting atm
[Android Software Development] repey6:
Sorry but no-verity-opt-encrypt-6.0.zip successfully works on Samsung Tab A SM-T585/580 firmwares 8.1 OS oficial but your builds(tried all, exclude latest) not work. Why?

Else. On 6.0-7.0 OS stock firmwares all used successfully no-verity-no-encrypt_ashyx.zip .
[Android Software Development] Zackptg5:
Couldn't tell you without logs and a description of the problem. Can you post recovery log after flashing, what room your on, and what the problem is/how you know it isn't working?
[Android Software Development] repey6:
I agree with you that need log. Sorry but i will not repite this expiriement because every time i must was to restore internal memory on my Tab. Every time i loose my data.

P.S. I am on RR 6.0 and have root and custom TWRP. And encrypted memory. When i tried install new stock based rom 8.0 OS every time i loose my data.
[Android Software Development] Zackptg5:
Finally got the time to figure out the problem with the last build and got it fixed so 11/18 is now rereleased!

Changelog: Updated all of the zips to magisk 17.3 tools! Also fixed fstab detection in ramdisk. People having issues with boot loops before should give this version a try (magisk v17.3 had some fixes for pixel 3's and some other stuff I forget)
[Android Software Development] sh0w 0f:
Hi I flashed this zip file through magisk manager but after flashing it through magisk manager It does not respond when I tap the reboot button and when I hit the home button everything goes black and I cannot do or see anything I can just force restart my phone
[Android Software Development] Zackptg5:
You need to flash this in twrp, this isn't a magisk module
[Android Software Development] sh0w 0f:
Oh ok ok haha sorry my bad
[Android Software Development] T3rm1:
There is one thing I haven't understood yet. I have a Xiaomi Redmi 4X with everything vanilla (bootloader is unlocked though). All I want is root with the stock rom. Do I need to disable dm-verity? If yes, why do I need to do this if I only flash TWRP? This doesn't change the system partition, does it?
[Android Software Development] Zackptg5:
Magisk/SuperSU should take care of that when you flash it so no need for this zip in that case
[Android Software Development] T3rm1:
I only flashed TWRP. I booted into recovery but couldn't do anything because it asked for a password. I never set one though. Then I tried to reboot normally but was stuck in boot loop. Can you think of any reason why the flashing of TWRP causes the boot loop although to my understanding nothing is changed on the system partition and so dm-verity schould cause no problem?
[Android Software Development] alecxs:
i have noticed checksum in /system/build.prop which may related to dmverify. flash back stock recovery for proof of concept, then you know

ro.expect.recovery_id=0x03f1aed461db9ca621b330ab01df9218d6c1422f000000000000000000000000
[Android Software Development] T3rm1:
I flashed stock rom with the MI flash tool. Bootloader is locked again, TWRP is gone and the phone boots. But that was to be expected, wasn't it? It's back to factory defaults.
[Android Software Development] Zackptg5:
The password prompt is because you're encrypted. You should be able to enter your password and then it'll be fine but if not, follow the instructions in the OP to decrypt
[Android Software Development] alecxs:
I am sorry i mean just flash stock recovery.img

Anyway, installing this zip will disable dm-verity, thats basically all you need for twrp, i guess

btw, you can keep stock recovery and boot twrp without flashing, if you dont want to change dm-verity for some reason

fastboot boot <twrp.img>
[Android Software Development] T3rm1:
That worked, thank you. I booted into TWRP, made a backup and installed Magisk. I created a .magisk file in /data (as mentioned here so Magisk doesn't change force encrypt or dm-verity. That worked. I was able to boot.

What happens if I install Adaway now? Adaway modifies the hosts file. Does this already trigger dm-verity and causes a boot loop?

EDIT: Ok, I wasn't even able to modify any file on the system partition. That must be because of dm-verity. What I did instead is check systemless hosts in Magisk Manager and installed Adaway after that. No settings needed to be changed, it worked just out of the box.
[Android Software Development] Zackptg5:
Yup :)

For future reference, this zip creates the .magisk file for you so as long as you flash it magisk, you're good
[Android Software Development] alecxs:
Adaway has systemless mode option, it just bind-mounts hosts over /system/etc/hosts without changing it
[Android Software Development] mordantly:
If 5.1 works, any reason to use the 11/2018 version?

If my boot img is patched, I never need to flash again unless I go to a dm enable kernel correct? Or does updating or uninstalling magisk need to flash this to maintain no dm?
[Android Software Development] SpockSpock:
Flashing a zip?

I thought I posted this question last night, but I don't see it, so here goes.

Odin won't let me flash a zip file. What am I missing?
[Android Software Development] wartomato:
The TWRP?
[Android Software Development] SpockSpock:
Zip file Disable DM-Verity

No, the download >>Disable_Dm-Verity-11.26.2018.zip<<

Odin doesn't let me flash zip files. Am I supposed to extract it first, then convert to tar, and then flash?

---------- Post added at 01:13 AM ---------- Previous post was at 01:05 AM ----------

I thought I posted this a second ago, but it is nowhere...

Not the TWRP

Disable_Dm-Verity-11.26.2018.zip

Am I supposed to extract it, then recompress as tar?
[Android Software Development] chooks06:
Use TWRP to flash the zip file.
[Android Software Development] SpockSpock:
TWRP won't go on my phone

So, I am actually worse off now than when I posted the original question. Phone is partially bricked, only goes to 'Software Update Failed', tells me to use the 'Verizon Software Repair Assistant', which also doesn't install correctly on my PC, lol. But that is a bootloader screen, Odin and Z3X detect it.

Verizon locked this bootloader pretty tight. Info on one forum suggested that if I downgrade from 6.x to 5.1.1 or so, I can then root etc. I was able to downgrade, but no love on the bootloader unlock.

Then someone else suggested downgrade to 4.4.4, but when I tried, it failed. Someone suggested Z3X, unchecking the boxes that it errors out on, and that I think it when I really messed it up proper.

I am desperate for any good ideas. Thanks!
[Android Software Development] chooks06:
Wow! That's a pickle you're in.

I have no experience with locked phones.

You could probably search for how to restore it back to original condition.

From what I understand, it's not straightforward to enable OTA update when phone is rooted.

I don't know whether you can get back to recovery to use the factory reset option and I'm also not sure if that can save the situation or make it worse.

If I can get into download mode, I usually flash latest stock firmware via Odin. Sammobile is one good source to get the correct firmware for any Samsung phones. But I don't know what phone you're using.

I'm assuming Samsung because you're using Odin.

Sorry, but I have no answers that can assure you of success.
[Android Software Development] SpockSpock:
Fail

Thanks. Got several eMMC read/write errors. I assume the phone is toast. It had too many random reboots for me even before I started modding. Returning to seller.
[Android Software Development] chooks06:
Best of luck mate!
[Android Software Development] Nwereonye:
Can I flash a stock rom through the TWRP????
[Android Software Development] chooks06:
I'm not an expert, but coming purely from an user's view, the answer should be "no" (or at least, not recommended). But then, it could also depend on device.

My understanding is that stock ROM usually has to be flashed via the method recommended by the manufacturer (or known methods).

Stock ROM wouldn't be able to run the way it's supposed to unless the bootloader is locked, original, and applies also to the kernel and baseband (otherwise, it wouldn't be "stock").

However, if you had TWRP flashed and the ROM is still the original, and a backup was made, the back up could be restored, which means I end up have the phone as is, running on the original ROM but with custom recovery.

Maybe I'm wrong. But, my practice is always to make a backup after installing custom recovery before I try flashing custom ROMs, kernel, root, etc.. So that, I can come back to square one to redo. But to get back to stock, it's wiping out custom recovery and relocking bootloader (to be done first on MTK devices and using fastboot, before SPFT to flash stock ROM, and all data wiped for clean start).

Maybe if you could provide more info, like, what device, exactly what you need/want to do, somebody with specific experience can help you, even somebody who has good knowledge may be able to help.

A general question will usually draw a generic answer.
[Android Software Development] Nwereonye:
Thanks.

What if I want to flash a global rom, cause am on the Chinese rom??

Still need to relock bootloader before flashing???
[Android Software Development] chooks06:
From my understanding, for stock ROM, it's better.. Else you may encounter problems like not getting the device updated to the latest OTA update..

Sorry if I'm long winded.. To get any ROM flashed, check with the Dev who created that ROM for that specific device and minimum required ROM version applicable in order for it to work correctly.

Read the thread carefully. Ask the Dev if you've specific situations that deviate from his required minimum.

Different OEMs setup differently.

Been playing around with MTK, SD, Intel and different brands do it different. Check that device OEM specific forums for a clearer picture..

Gung-ho if you're prepared to write off the phone.
[Android Software Development] srinivasvaka1985:
Can i use it for pixel experience rom android p gsi rom
[Android Software Development] sh0w 0f:
You can try but after flashing the zip file do a wipe
[Android Software Development] srinivasvaka1985:
Ok so when do i need to flash this file before or after flashing rom,since it has gapps already within the rom
[Android Software Development] sh0w 0f:
After flashing the rom flash the zip file then do a wipe
[Android Software Development] alecthenice:
Flashfire

I have no twrp recovery.img available to me. Can I disable dm-verify with flashfire?
[Android Software Development] sh0w 0f:
Maybe it will not work
[Android Software Development] an-_-dro:
my steps was:

1. Flashing pure boot.img then reboot back to TWRP.

2. Flash RMM prenormal etc. etc then flash your zip then followed by magisk.

device booted but why become so slow? so many lags :confused:

My device samsung A6+ (A605G/DS)

** Nevermind, back to normal after another restarting. Thanks a bunch
[Android Software Development] alecthenice:
That's what I was afraid of. Why is the format userdata first needed?
[Android Software Development] Spannaa:
If you're not encrypted, you don't need to.

If you are, formatting userdata before flashing your rom and the dm-verity & forceencrypt disabler will stop the rom encrypting your device and will allow it to boot decrypted without the insecure verity check blocking boot.
[Android Software Development] alecthenice:
do you think there's a protocol I could follow to do this with flashfire?
[Android Software Development] Spannaa:
You can format userdata via fastboot but I'm not sure about flashing zips via flashfire as I've never used it.
[Android Software Development] alecthenice:
That's where I'm stuck, booting back to android would be working against the end goal.
[Android Software Development] DoR3M3:
These are areas of Android I've never bothered with, until recently, and still working on understanding all the various reasons someone would want to do this.

What are some of the most common reasons to not want to use DM-Verity and ForceEncrypt?

For DM-Verity on a Stock ROM, will it still worked on a device that has the bootloader unlocked, and rooted with a custom kernel?

Thanks
[Android Software Development] alecthenice:
DM-verity makes it so you can't modify the system partition. Installing xposed modules would do this and cause the device to not boot and maybe self encrypt. It also secures the kernel (one may want to enable signature spoofing) force encrypt just makes your device boot slower and may make twrp be unable to decrypt user data partition in a lot of devices. If you are using a custom kernel to the best of my knowledge you must disable DM verity. Force encrypt as well so you can access the data partition. I hope this helps.
[Android Software Development] DoR3M3:
Not understanding what you meant from Xposed, also the signature spoofing?

Thanks
[Android Software Development] alecthenice:
These are just common mods that people would wish to perform
[Android Software Development] DoR3M3:
Sorry for not explaining myself better, I know what Xposed and Sig Spoof are, I didn't know what you meant by them in your reply?
[Android Software Development] alecthenice:
Oh, I understand! These edits to the system partition would trigger the partition to fail to boot due to DM verity detection.
[Android Software Development] DoR3M3:
More elaboration PLEASE... :)

Are you saying with Xposed or Sig Spoof failing to boot?

I have dm-verity, sig spoof patched and Xposed on a Rom with no boot failures
[Android Software Development] alecthenice:
Is this stock? Do you think you could share your boot.img with me? What's your device details?
[Android Software Development] DoR3M3:
I should of just spent more time reading, no worries, all good...
[Android Software Development] lee rock:
worked on Motorola E5 XT1944-4 android oreo rom stock without encryption Now Thanks