yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Ibuprophen:
I believe that the following thread should be of assistance for your specific issue.

https://xdaforums.com/showthread.php?t=3378035

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Moto G5 Plus Questions & Answers] mongoose96:
My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.
[Moto G5 Plus Questions & Answers] acejavelin:
You must be PURE stock to take an OTA update, or it will fail and bootloop... Flash a rom if you wish.
[Moto G5 Plus Questions & Answers] oscar1823:
What i did was make a back up of everything just incase and then look up the ota version on your phone and get it in the rom section and look up twrp flashable OTAs and just flash it. you might lose root but its easy to get back if you flash magisk again.
[Moto G5 Plus Questions & Answers] manos78:
You can found the right guide here:

https://xdaforums.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
[Moto G5 Plus Questions & Answers] Outfield303:
does anyone have fastboot stock rom?
[Moto G5 Plus Questions & Answers] acejavelin:
Of the current version? lol, no, we wish... we are averaging 3-6 months behind OTA releases for full ROM images, if we get them at all. Moto does not officially provide them, so they have to be leaked somehow, and sources are completely dried up yet, but it's getting there. :/
[Moto G5 Plus Questions & Answers] mortadelax:
Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.
[Moto G5 Plus Questions & Answers] Wolfcity:
You can't be rooted with a locked bootloader so your question is obsolete.

You can apply to OTA with an unlocked bootloader.

You can't if you're rooted or changed anything else in /system or /vendor.
[Moto G5 Plus Questions & Answers] mortadelax:
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.

I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.

If someday I want it, maybe will install some rom.

Thanks bro.

EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?

EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?
[Moto G5 Plus Questions & Answers] Wolfcity:
Oreo ist absolutely fine, no problems with it.

I haven't heard of any issues like increased battery drain, for me nothing changed at all regarding battery and the rest is also working flawlessly.

It would be a lot of action to unlock and root the device just to stop the updater service.

If you don't have any other plans that need root privileges I recommend just taking the OTA (s).

If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
[Moto G5 Plus Questions & Answers] mortadelax:
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.

Cheers

EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?
[Moto G5 Plus Questions & Answers] Wolfcity:
Yes I am.

Just check some of the custom ROM threads, there are some that need stock Nougat as base but the most of them need Oreo. For custom ROMs there are no up/downgrading problems, that's only the case for stock firmwares.

And as said above, there are TWRP flashable stock builds that doesn't have these problems too and will bring you to whatever stock firmware you want, not just pseudo. (Here:

https://xdaforums.com/g5-plus/development/oreo-twrp-flashable-stock-builds-coming-t3830482 )

So if you're on stock Oreo after unlocking the bootloader and flashing TWRP all options are open for you. Just don't forget to make a full nandroid backup incl. EFS and persist before you flash anything.
[Samsung Galaxy Note 8 Accessories] gingi999:
Just ran some numbers and something seems odd.

The ad claims 115% more battery - that's 3795 mah

The battery also says it's 5500 mah

So that totals 69%

Are most batteries that low. I thought that 80% was the average u get from most batteries. I understand there is loss from resistance/heat, but I didn't think it was 31%. I really don't know much about the science but can someone explain?
[Samsung Galaxy Note 8 Accessories] borijess:
Just got this in the mail. Looks exactly like the zerolemon without the name. I paid 16 bucks for it.
[Samsung Galaxy Note 8 Accessories] pyraxiate:
It's likely a 3.7V 5500mah battery. They didn't lie on the cell rating but what they don't tell you is that it's being converted into 5V vs the 3.7. Do the math on a 5 V cell and convert. It's probably more like 90%

I hate how they use trickery in their advertising. That's how all the cheap Chinese manufacturers claim that high output on battery banks even though it's no where near what's expected.
[Samsung Galaxy Note 8 Accessories] Jammol:
Where did you buy it from?
[Samsung Galaxy Note 8 Accessories] skinnytoo2:
Yeah where you get it? Itlooks exactly the same.
[Samsung Galaxy Note 8 Accessories] swaters3:
I paid 50 like a fool and it came from China. Works well but why so darn heavy. I used to carry a battery for my note 4 and it weighed nothing. Also did anybody get a chance to try the note 7 battery backpack from Samsung. Was it a normal weight?
[Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti] shaolin95:
Hello!

I am trying to decide if I should get one or not as my phone to replace my current monster, the Mediapad X2. The main reasons are the issue with GPS not working until reset very often and the lack of NFC.

But of course, there are issues I see with the Xperia too...no way to make calls without a headset other than speaker phone. The very small internal memory. The screen to body ratio is not that good but I understand that having those front speakers are nice.

Anyways from my understanding I get about 11GB of usable space so without a way to use my SD card as internal , this could be a deal breaker.

Thanks
[OnePlus 3T Guides, News, & Discussion] Siddk007:
[MENTION=7874870]Xennet[/MENTION] that was quick, thanks. However i have already flashed and booted OB 16. can i still flash?
[OnePlus 3T Guides, News, & Discussion] Xennet:
Of Course..

No problems in that...

Did you trigger Dm Verity and is your phone encrypted?
[OnePlus 3T Guides, News, & Discussion] Siddk007:
i successfully rooted OB 16 without trigerring DM Verity and yes phone is encryptyed
[OnePlus 3T Guides, News, & Discussion] Xennet:
No problems still you can flash...
[OnePlus 3T Guides, News, & Discussion] Hinoy:
Thanks !

Too late for me brothers, I've fallen, I triggered dm verity and now my phone partition was wiped and it won't let me install a ROM.

Still have access to fastboot and adb tho. (Restore not working due to the dm-verity)

I'll try to flash this and play around, hopefully it will resolve my issue.

Thanks for helping everyone anyway ;)

EDIT : Ok so I think it allowed me to restore an old old old backup so probably props to you for giving my brick a second chance.

It stills shows me the "dm-verity not enforced" message when booting up tho.

And TWRP still won't let me install a ROM. Even the officiel beta

I get an error 7 saying my build.pro ro.product.series is " " instead of "OnePlus 3T" but I checked it's OnePlus 3T...

If I remove the update script part about checking my series it just fails to update system image.

This update really ****ed up my phone because of the dm-verity when I tried to flash TWRP and Magisk (I had no issue before and was full stock)

Can anyone help ?
[OnePlus 3T Guides, News, & Discussion] Isus <3:
I triggered dm verity with oreo rom but I went and installed backup PA Nougat as I didnt like the OOS Oreo, can I still flash this zip on nougat to disable dm verity or is it only for oreo?
[OnePlus 3T Guides, News, & Discussion] Xennet:
This is only for Oreo

For Nougat go to my thread here..

https://xdaforums.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232
[OnePlus 3T Guides, News, & Discussion] Xennet:
Install nougat ROM OOS 4.5.0 STABLE and remove DM verity by following instructions from my thread here...

https://xdaforums.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232

Then after removing DM verity if needed you can reflash Oreo beta zip after removing the first line in updater script and then immediately flashing the DM verity and force encryption disabled zip from this thread...
[OnePlus 3T Guides, News, & Discussion] akhilnarang:
Can anyone confirm it works? (disabling forced encryption)

I had changed the flag in fstab manually (forceencrypt to encryptable), and I still got encrypted.
[OnePlus 3T Guides, News, & Discussion] cezarvrabie:
At least for me I couldn't get it to not be encrypted. I've tried for a few hours and had no luck.
[OnePlus 3T Guides, News, & Discussion] Mr_Q:
Nope it does not. Mine started the encryption process as well.

[EDIT] correction; it does seem to work. Because the first boot took really long and the device ran hot, just like the first time when I did have encryption, I thought it was the case this time as well. Although I had to reflash the TWRP-recovery (it was replaced by stock) but it did not tell me /data was encrypted, so I think we're good!

Thank you Xennet!
[OnePlus 3T Guides, News, & Discussion] Xennet:
Hope you will not lose twrp if you had rebooted back to twrp before rebooting to system..

Can you confirm that the phone is not encrypted...

See the encryption status in settings, security..
[OnePlus 3T Guides, News, & Discussion] Mr_Q:
I did boot TWRP -> TWRP, it become stock after I did a normal boot.

But the sad news is, it does state it's encrypted.. :(

So I thought encryption always required a PIN or Pattern when accessing the phone and/or Recovery, am I wrong?
[OnePlus 3T Guides, News, & Discussion] Xennet:
Just sent you a PM..

Check it...
[OnePlus 3T Guides, News, & Discussion] Xennet:
Yup but that's right...

To access an encrypted phone data you need a pin in TWRP

Can you check in TWRP again and are you able to see your data and copy and move around files..
[OnePlus 3T Guides, News, & Discussion] Mr_Q:
Yes I can, but I did notice something interesting in the logs of TWRP:

Data successfully decrypted, new block device: '/dev/block/dm-0'

Updating partition details...

... done

Succesfully decrypted with default password.

So yes it's encrypted, but I don't have to enter any password...
[OnePlus 3T Guides, News, & Discussion] Xennet:
You have not triggered DM verity I suppose??

So my zip file does protect from triggering DM verity but not force encryption that's weird...

Did you use any root methods..?
[OnePlus 3T Guides, News, & Discussion] BillGoss:
Mine's an A3010
[OnePlus 3T Guides, News, & Discussion] BillGoss:
I did a clean install (system reset in stock recovery, flash stock OOS 5.0 zip), boot system, boot bootloader, flash TWRP, boot recovery, restore modified system, boot system, ...

And I'm back in bootloader mode without any warning messages (other than unlocked bootloader).

So it seems my phone (A3010) handles dm-verity problems by sending me back to bootloader.

I'm happy with this as an outcome because I now know what's going on and how to fix it (flash stock image, flash custom kernel, or flash su).

Thanks for your suggestions.
[OnePlus 3T Guides, News, & Discussion] boggleboggle:
Oneplus 3 not recognised

It tried to flash the 4.0.2 firmware on my Oneplus 3 phone, but I get the following error:

E3004: This package is for "OnePlus 3" devices; this is a "".

What should I do?

Update:

After checking the zip it seems that it checks for the ro.display.series, but when I check this for my phone it reads as Oneplus 3. Very strange the script is not picking this up. I'll keep working on it, but if anyone has any ideas, I would be grateful!

Update 2:

Thanks to Xennet for pointing out that this is due to the modified TWRP problem and it will work with the official TWRP.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Has been mentioned multiple times in this thread itself...

Use the official Twrp to flash the zip and after getting rid of DM VERITY you can reflash the custom Twrp back...

I have inserted the assert line so that the zip will confirm the device before flashing so that accidental damage can be avoided...

It's the problem with the custom Twrp that doesn't return the value for ro.display.series..
[OnePlus 3T Guides, News, & Discussion] boggleboggle:
Thanks for your help. Sorry, I did have a look through the thread but didn't see that. My bad!

I will delete my explanation in the previous post as obviously your solution is better.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Major changes are made to the OP...

Please go through it carefully. As it was rightly pointed out by [MENTION=2464043]rk2612[/MENTION] who pointed out the fact that indeed the system entries are hashed out in the fstab file and the kernel takes care of the system loading procedure in OREO, I have been working on it. Indeed it is true. After unpacking the boot image into kernel, ramdisk and device tree blobs (dtbs), I came accross 12 entries in the dtb that reference directly to mount the system after triggering the DM-Verity flag. So I patched the dtb binary to clear of the DM-Verity flags and repacked the Boot images.

Hence, from now on there will be 100% stock Boot Images which have been patched for DM-Verity in the dtbs for disabling DM-Verity checks. And for getting rid of force encryption use the Force Encryption disabler zip given in OP.

All Details updated in OP...Read through it..

Thank you all for having patience..
[OnePlus 3T Guides, News, & Discussion] crian:
When I flash a custom kernel on top of your stuff I get build number and model display as "unknown".

What is causing this and how can I fix this?
[OnePlus 3T Guides, News, & Discussion] Xennet:
That shouldn't be happening....

Build number and model is taken from build prop file in /system...check it...

My stuff is just boot image...it has nothing to do with it...

Snipet of my build prop file...

#

# autogenerated by oem_buildinfo.sh

ro.frp.pst=/dev/block/bootdevice/by-name/config

ro.build.product=OnePlus3

ro.build.user=OnePlus

ro.build.flavor=OnePlus3-user

ro.build.description=OnePlus3-user 7.1.1 NMF26F 136 dev-keys

ro.common.soft=OnePlus3

ro.display.series=OnePlus 3T

ro.build.oemfingerprint=7.1.1/NMF26F/10122113:user/release-keys

persist.sys.oem.region=OverSeas

ro.build.date.Ymd=171012

ro.build.date.ymd=171012

ro.build.date.YmdHM=201710122300

persist.sys.assert.panic=false

..............
[OnePlus 3T Guides, News, & Discussion] Anghirrim:
I had the same, but I don't know where it's coming from. What is your root method?

Anyway, after a reboot, correct model # and build # will appear just fine.

Don't know why it behaves like this.

Edit' I've just checked, it disappeared again...but it randomly comes back and forth. I just rebooted and it's back.
[OnePlus 3T Guides, News, & Discussion] Xennet:
[MENTION=4766140]crian[/MENTION]

No problems in my phone with bluspark kernel and in [MENTION=2911853]BillGoss[/MENTION] phone with derp kernel screenshot which he sent me..

May be some mods or root methods.
[OnePlus 3T Guides, News, & Discussion] Anghirrim:
Let's see. I am using Magisk 14.5.

If [MENTION=4766140]crian[/MENTION] is using Supersu then... I don't k'ow.
[OnePlus 3T Guides, News, & Discussion] crian:
Build.prop is fine but about is not showing it.

I'm only using your boot.img and disabler zip.

Tested it with derp kernel, flash kernel, Magisk, SuperSU and is disappearing.
[OnePlus 3T Guides, News, & Discussion] crian:
And if I flash a custom kernel Magisk doesn't pass safety net.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Can you or [MENTION=4027505]Anghirrim[/MENTION] test whether it's happening without magisk...just my boot image and force encryption zip file only...

Edit1:

[MENTION=4027505]Anghirrim[/MENTION] complained about this issue even before I rewrote the thread and uploaded my patched boot images...he had the issue after he decrypted the phone with my zip and flashed magisk...so it's not my patched boot images that has problem...

Can you check and paste the fstab entries in vendor/etc...

Edit2:

My phone is encrypted and I did rooting with magisk..I restarted many times and no error in safety net or about screen..

Don't worry we will try to work it out..

[MENTION=6972080]elmer_fudd[/MENTION] [MENTION=4954690]Siddk007[/MENTION]

Hope you have your phone's in decrypted mode...Are you having problems in about screen on passing saftey net?
[OnePlus 3T Guides, News, & Discussion] Siddk007:
no such issues
[OnePlus 3T Guides, News, & Discussion] crian:
Are you using a custom kernel?

I only can't pass safety net with a custom kernel. With patched stock kernel everything is fine.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Do you have stock kernel or custom kernel?
[OnePlus 3T Guides, News, & Discussion] Xennet:
[MENTION=4766140]crian[/MENTION]

Thats just weird...

As everything is fine with stock, there is nothing wrong with my zip file...

But what happens when custom kernel flashes is what intriguing...

Can you check the fstab entries in vendor/etc folder and check whether it's same as in my zip file after flashing custom kernel...
[OnePlus 3T Guides, News, & Discussion] crian:
I think it's an issue with Magisk.

I changed my flash order from (rom, boot.img, disabler zip, Magisk, kernel) to (rom, boot.img, disabler zip, kernel, Magisk) and in both situations the about issue and safety net fault is appearing.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Hmmm..

Really messy..

The only final way of testing it is by not flashing my disabler zip and testing with magisk...

But I won't advice it as in case your data gets encrypted it will be a mess...

By the way did you check the fstab file???

Or else flash my disabler zip as last in the order...that's a way to check it ..

Or else don't flash magisk at all and boot to system with my boot IMG disabler zip and custom kernel..
[OnePlus 3T Guides, News, & Discussion] Anghirrim:
I just flashed AOSP Extended, so did not need your disabler file. But I did flash Magisk 14.5 and don't have the problem.
[OnePlus 3T Guides, News, & Discussion] Xennet:
That's not entirely right...

AOSP Extended is a custom ROM built entirely different from OOS....It can't be compared to problems on OOS...

Moreover [MENTION=4954690]Siddk007[/MENTION] clearly stated with screenshots that he has whatsoever no problems with my zip and magisk 14.5

There's something fishy...But can't get it...
[OnePlus 3T Guides, News, & Discussion] crian:
Don't have the time to test it. maybe somebody else can do it.
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
I'm decrypted.. All ok in About screen. I do not pass safety net but I have no intentions to do it.

Rooted with SuperSU 2.82 SR5.

FrancoKernel r33.
[OnePlus 3T Guides, News, & Discussion] TheVic!:
Im on latest open beta, with derp kernel and magisk 14.5. I did the flash before the rewrite, and no problems with version, build number or passing safety net in magisk... Im on OP3 - a3003.
[OnePlus 3T Guides, News, & Discussion] crian:
I'm now encrypted and got no issues with "unknown" and safety net not passing while using a custom kernel and Magisk.
[OnePlus 3T Guides, News, & Discussion] Xennet:
So now are you able to pass saftey net with custom kernel on magisk now with my patched boot image?

Still...what happening when you were decrypted and with custom kernel??? Still unable to correlate..
[OnePlus 3T Guides, News, & Discussion] crian:
What was happening is that model and build number turned into "unknown" and Magisk wasn't able to pass safety net.

Magisk is modifying dtb during the flash process. Maybe this give these issues.
[OnePlus 3T Guides, News, & Discussion] Xennet:
That isn't true...once you flash my boot image...while you flash magisk...the line telling that "patching dtb" will not appear as dtb is already patched... I am having my boot IMG bluespark kernel magisk and no issues
[OnePlus 3T Guides, News, & Discussion] dusman13:
Working for me. :)
[OnePlus 3T Guides, News, & Discussion] MoHed:
Not working here...

I have followed the steps meticulously (simple img flashing after reflashing ROM) on my ob19 oneplus-3t.

I failed to achieve the required result (dm still shows) and furthermore the connectivity of the phone was lost.

Reflashing the ROM solved the connectivity problem.
[OnePlus 3T Guides, News, & Discussion] BillGoss:
Did you flash anything else after flashing the patched kernel?
[OnePlus 3T Guides, News, & Discussion] Xennet:
Once DM VERITY is triggered you need to follow the steps in post 2...simple flashing the patched boot IMG won't do any good...
[OnePlus 3T Guides, News, & Discussion] MoHed:
Will try

Thank you for the clarification. I have followed this procedure before (OB13) and it worked. I just thought yours was a much simpler procedure.
[OnePlus 3T Guides, News, & Discussion] Xennet:
But once you get rid of it...

From next time on you will never trigger DM VERITY if you just flashed the patched boot IMG each time you upgrade.. so it becomes as easy as that...
[OnePlus 3T Guides, News, & Discussion] Anghirrim:
Quick update on the "unknown" model and baseband issue.

I just clean installed FreedomOS 3.2.1 (Stock debloated OOS) and the guy tweaked the kernel to remove the dm-verity flag as well as force encryption, so did not need to flash anything from this thread.

And... The "unknown" issue still appears.

So no idea what generates that.
[OnePlus 3T Guides, News, & Discussion] pijen:
Hello,

I flashed stock OOS 5.0 but I forgot to flash disable encryption (it was decrypted previously) because I got random reboot recently

which procedure should I follow to get my phone to decrypted state like before? and is it possible to get it back without losing my userdata (specifically the /sdcard)?

I don't have any password or anything setup on my phone and I did try use 'default_password' when I entered twrp but I still can't access /data

I'd like to just get my data back and don't mind to factory reset

thanks
[OnePlus 3T Guides, News, & Discussion] Xennet:
If you can't access data via Twrp, the one thing you can try is to boot to the oxygen os system with the encrypted data and access the data and if possible copy and make a backup...

Other than that I think there is no way...

To get data partition decrypted again follow PROCEDURE 2 in the OP...But you will lose your sdcard data if you can't backup...
[OnePlus 3T Guides, News, & Discussion] pijen:
if I do factory reset, and flash stock oxygen OS, is /sdcard will be accessible?

I did try boot stock OOS but the encryption is not successful
[OnePlus 3T Guides, News, & Discussion] Xennet:
Cannot tell for sure...you can try...

Once I had this issue..at last I flashed a custom ROM just to get into system and copy files from sdcard to PC and then wiped everything and reflashed OOS..
[OnePlus 3T Guides, News, & Discussion] pijen:
Custom ROM? Ok I'll try,

I've stock OOS 5 previuosly, can I use LOS 14.1 or should I get unofficial LOS 15?

Thanks for your help
[OnePlus 3T Guides, News, & Discussion] Xennet:
Anything would be good. Better go with unofficial los 15...is Oreo and hence no firmware issues and moreover it's just for retrieving the data and not for using the os..
[OnePlus 3T Guides, News, & Discussion] megaslx:
do I need to flash ENCRYPTION disabler zip everytime after I flash stock rom?