yashsingh1/xdaforums huggingface dataset:
[Moto G5 Questions & Answers] TheFixItMan:
Flashing an oero stock rom firmware image is exactly the same as flashing a nougat stock rom firmware image (although there's a few more img_sparsechunks to flash)

You won't brick your phone if the firmware you are flashing the the same or newer

You will brick your phone if you try and flash a gpt & bootloader that is lower than the version currently on your phone

You can downgrade by flashing everything except these parts

There's no difference to flashing an ota via stock recovery to doing it via system update - however you must be on a fully unmodified stock rom else it will fail and potentially brick your phone

Don't confuse flashing an ota with flashing a complete stock rom firmware image

And ota must meet certain requirements - eg must be on a certain stock firmware version

A stock firmware image (complete stock firmware) can be flashed on any device (to which the image is for) that has the same or older bootloader version
[Moto G5 Questions & Answers] G5-User7080:
Thank you!

It took me some time to find out that OTA's only apply from one specific version to an other (the post from "tfwboredom" with all OTA's he was able to catch was a big help) and when i didnt get any OTA's (after flashing stock Nougat) i did an OTA update via adb. After that, my phone offered me OTA's again and i could upgrade until Oreo --.13 i guess. I rediscovered a thread with the full fastboot stock Oreo firmware --.16 then (forgot i already had downloaded it with my phone to my sd ^^) and flashed this then with the computer.

My Problem right now is the thing with the auto encryption.

Im on OPP28.85-16 now with TWRP64bit installed and was also able to get root by flashing newest Magisk (18.0) and the f2fs-loopback-bug-workaround (I dont really know for what that is) and installing MagiskManager v6.1 after booting system.

However, when i return to twrp after booting into system it asks me for a password to disable encryption and also wont flash things properly until i format data or do a factory reset. But after booting into system this encryption will be applied again. Flashing no-verity-encrypt didnt solve the problem.

What i want to find out now is:

1. Why is it automatically encrypting again and how can i disable that?

2. When i disabled that, can i encrypt my phone in the settings and use that password then to unlock twrp?

3. Where is the difference between this auto encryption and when i click in system settings on encrypt phone?

As far as i understood, in Nougat no-verity-encrypt was to prevent the dm-verity...thing to encrypt your phone but i could still enable encryption in the system settings.

(4. what is the purpose of f2fs bug fix?) - and has it enything to do with encryption?
[Moto G5 Questions & Answers] TheFixItMan:
You need to format data to remove encryption

Wipe - option on the right

If you encrypt again once booted you need to use a twrp that supports encryption - the 64bit version posted in most rom threads don't support encryption but I did post the source code to my test version which someone compiled which may have encryption support

You can try it

https://drive.google.com/file/d/1kgFyYfjEyqAEXOGjg_UfeedlQwaLVF1F/view

All you should need to do is flash magisk - try version 17

You probably will need to change the device fingerprint to pass CtsProfile

Use this module

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Moto G5 Questions & Answers] G5-User7080:
- Yes, i did that, but when i boot system after it and return to twrp its again encrypted, but ill try a clean stock oreo flash -> twrp -> format data -> reboot -> return to twrp

- Oh ok, i switched to 64bit version because of efs backup when still on Nougat, but i read somewhere that the 32bit version has that now, too, so could i also go just back to 32bit twrp?

As far as i remember, i never had a Problem with encryption on Nougat with 64bit.

- What does that mean that twrp supports encryption, when data gets encrypted every time, how should twrp be able to read that then?

- why 17 and not 18? i mean 18 worked when i tried it?

- I have currently no lock enabled, because i want to do a twrp backup after everything is done, what is the problem with fingerprint and what is CtsProfile?

I'll try that things out, thank you, and edit this when i find some things out

What i want at the end is a rooted Oreo (done) with a working twrp, where i can still flash and backup and restore without wiping data every time and if possible i want to use the normal encryption (the one when i boot system and set it up in settings).

I still dont really get what this auto encryption is.
[Moto G5 Questions & Answers] TheFixItMan:
As far I was aware the 64bit twrp cannot decrypt data apart from the test one I posted

If you don't have a twrp that supports data encryption your phone will still work, you just won't be able to use/flash zips to the data partition or backup/restore that partition

If you get a decrypt data when you boot your phone normally and it doesn't decrypt then you must remove encryption and boot the rom first before applying encryption again

My official 32bit twrp does support data encryption and will work on any 32bit rom including stock oero

Use any version of Magisk that works for you - I no longer own this device & only tested with magisk 17
[Moto G5 Questions & Answers] G5-User7080:
Everything worked pretty well until i wanted to restore an older backup, I tried to format data before doing the restore but it failed.

After i flashed twrp (official 32bit this time) i did a factory reset to remove decryption and rebooted recovery to prevent the system fromr eplacing it. But when i use format data after that (or already in first place, could be that i tried that, too) it fails, it sais data successfully decrypted and continues and then theres an error. And when i try then a factory reset, too it fails, too.

However, after changing file system to ext4 and than formatting again (i dont remember exactly) i endet up with a working f2fs data partition and was able to use format data and restore backup,...

I am very confused now, because i dont get at all what the heck is the problem, should i not format data and do factory reset or does this happen when i flash the f2fs bug workaround before or is it because i booted the system and begun to change the settings, i have no idea,.. but ill try out and write you when i find something out!

EDIT:

Ok i found some things out, still dont understand at all, but it seems that

format data fails after booting into system

but works after rebooting twrp again

factory reset fails after format data fails

but works after format data works

works not after rebooting twrp, only if format data was successfull before (bec that works again after rebooting twrp)

rebooting system after format data failed will result into a bootloop into recovery with error when trying to enter recovery after manually going to bootloader -> recovery it works

It may help to see it in a table:

After flashing Oreo(boots up) and then twrp:

format data	failed

factory reset	failed

After flashing Oreo(boots up) and twrp and rebooting twrp:

format data	successfull

factory reset	successfull

reboot system

reboot twrp

format data	failed

factory reset	failed

reboot system results in bootloop into recovery with error

reboot twrp

factory reset	failed

format data	successull

reboot system

reboot twrp

factory reset	successull

format data	failed

factory reset	failed

reboot twrp

factory reset	failed

format data	successull

factory reset	successull

Output when format data fails:

[CODE]Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled

I guess thats the log from twrp start and what followes is the one for format data

Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount Storage

[/CODE]

And for factory reset after it:

Failed to mount '/data' (Device or resource busy)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
[Moto G5 Questions & Answers] TheFixItMan:
Try a

fastboot erase userdata

Type this in cmd on pc with phone connected via USB in bootloader mode

This will erase everything on internal
[Moto G5 Questions & Answers] G5-User7080:
when should i do that?

Instead of using frmat data?

So when i flash twrp and boot into it first thing i should do is format data right? So i should just after flashing erase userdata and THEN enter twrp or what?

I'll copy in my reply from an other thread where 2 ppl tried to help me.
[Moto G5 Questions & Answers] Wolfcity:
As I rooted the device it was on Oreo OPS28.85-13-3 by OTA and I did it like this:

flash latest official twrp 3.2.3.1

make a backup of EFS and persist

boot recovery (now it prompts you to give in a decryption code, just press skip)

format data (F2FS)

don't reboot now

flash magisk 18 (I flashed 17.2 and updated later, no clue why)

reboot to system

install magisk 6.1 apk (if it's missing, in my case it was present)

if you reboot to twrp now it shouldn't prompt you to give in a decryption key anymore
[Moto G5 Questions & Answers] TheFixItMan:
It's the same as format data in twrp
[Moto G5 Questions & Answers] G5-User7080:
To have it all in one Thread:

hmm, i did as follows:

flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed

let phone start and turn it off again

flash twrp

boot recovery and factory reset

reboot recovery

flash magisk 18

reboot system

install magisk 6.1 apk

The thing is, when i dont reboot recovery after its installation the system will overwrite it with stock recovery and as far as i understood i need to reboot twrp for that.

I just did as i did for Nougat there regarding the post from 'Johny Cipeli':

6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"

7. Go to WIPE, then "Swipe to Factory Reset"

8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL

So should i do then:

flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed

let phone start and turn it off again

flash twrp

boot recovery

reboot recovery

format data

flash magisk 18

reboot system

install magisk 6.1 apk

or is this irrelevant if i first format data, then reboot twrp and then flash magisk?

Why do you flash no-verity? I tried that out earlier but it made no difference on the standard encryption.

As far as i know from 'TheFixItMan', he said that the 32bit twrp is able to surpass the encryption somehow.

But i guess this is kind of a standard encryption and not the "real encryption" could that be?

Because, i thought encryption means, you have to enter a password on boot to decrypt it.

When you set up your password under security you can choose to enter it on boot and then it will ask you for this password everytime BEFORE booting your system, and this will also be your password to decrypt data for twrp then. But i dont know if thats the "real encryption" or that standatd thing is, too, but just decrypts automatically on boot.

Thank you for helping me, I just get totally confused by the Oreo process,.. worked so easy on nougat :(
[Moto G5 Questions & Answers] woozie.2007:
in security option, the phone appear to be encrypted, in nougat after flash no verity the phone was decrypted. In oreo i dont know why is appear encrypted and i cant decrypt with no verity....
[Moto G5 Questions & Answers] G5-User7080:
I dont have the option to backup efs,.. im using twrp 3.2.3-0 (the latest i could get from official twrp site) but i already did backup efs and persist in nougat, isnt that enough? DO i have to do that again on Oreo?

Also its not asking me for a decryption code, are you using 64bit twrp then?

And i remember that twrp got overwritten 2 or 3 times by stock recovery, and i thought that was because i didnt rebooted twrp again, since i rebooted twrp after formatting data it didnt happen again.

Also it did work for me using the 1. method i wrote earlier, i successfully rooted my phone, im just wondering now which is the "better" or "correct method to either

boot recovery, reboot recovery, format data and flash magisk

boot recovery, format data, reboot recovery, flash magisk

boot recovery, format data, flash magisk, boot system (but i guess next time you enter twrp it gets overwritten by stock recovery then)

boot recovery, format data, flash magisk, reboot recovery and boot system

or stay in bootloader (after flashing twrp) fastboot erase userdata, boot recovery, -data, -magisk, -system

or -recovery, -bootloader fastboot erase userdata, -recovery, -magisk, - system,.... you get the idea
[Moto G5 Questions & Answers] G5-User7080:
Because theres some sort of auto encryption which everytime reencrypts your phone.

I just dont get the sense of formatting data if it gets reencrypted anyway and twrp can surpass encryption.
[Moto G5 Questions & Answers] G5-User7080:
Had to correct that!

So in general after booting system, formatting data fails, maybe it works with fastboot erase userdata (didnt test it, cause i dont want to reflash Oreo again, i wanna go to bed.

But just rebooting recovery after booting first time in twrp works, so after that format data works. Works not..

Now im confused,.. after being in system and returning to twrp format data fails, but it seems when you fail it and then reboot recovery then it works...

So boot recovery, reboot recovery -> format data wont work BUT

boot recovery, format data fails, reboot recovery, format data will work WTF

So i guess either do factory reset instead of formatting data (thats also fine, or not?) or use fastboot erase userdata after flashing twrp in bootloader (i mean i do this while flashing oreo,.. so i dont really get why i have to do that again but i also dont really get why i have to format data a all)

Good night guys, thank you for your help,.. ill continue tomorrow.
[Moto G5 Questions & Answers] Wolfcity:
Latest official TWRP recovery is 3.2.3.1 for potter:

https://eu.dl.twrp.me/potter/

It has the ability to backup EFS and persist (see attached screenshot). I would make a backup just to be on the safe side.

To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box in magisk manager).

Also I hadn't any problems to make TWRP stick.

Edit: A factory reset won't reformat data.

If you want your data partition decrypted or not depends on your needs. Encrypted is safe but you're not able to access it to make any changes unless you decrypt it again....
[Moto G5 Questions & Answers] G5-User7080:
I have the G5 not plus, theres no 3.2.3.1 yet. (Aber lustig, dass du auch aus deutschland bist (denk ich mal) :D).

Ahh so i have to flash magisk right after decrypting by formatting data? But i cant successfully format data when i come from system as i wrote earlier so the question is if it works when i fastboot erase userdata to decrypt data and if data doesnt get reencrypted when i boot then twrp.

I guess if the force encryption reencrypts when i boot recovery, too it wont work, then i guess the only way is to enter recovery, do a failed attempt, reboot recovery, and successfully format data.

Edit:

Also after installing magisk and booting system it still says encrypted in settigns so i thought its not removing the force encrypt. And i dont have found that switch yet..
[Moto G5 Questions & Answers] woozie.2007:
Hi,

If i already have the phone encrypted and rooted with magisk, "keep force encryption" is tick, if I will untick the option will booting decrypted?
[Moto G5 Questions & Answers] Wolfcity:
Ah ok, I thought your device is a potter.

The checkbox is found inside magisk manager but it is unticked by default so the device should decrypt.

Have you tried the official twrp instead of the 64bit unofficial version?

Maybe try magisk 17.2 too as I did.

And yes, I'm from good old Germany too.;)

I think you will have to decrypt data by formatting it, unticking the checkbox just prevents the device from encrypting itself again. You should find some additional informations:

https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
[Moto G5 Questions & Answers] G5-User7080:
Oh dear.... well, ive found some things out by eeeeendless testing and im now able to root my device with or without encryption although i still dont understand it completly (f.e. why activating encryption manually would take hours according what is written in the settings, but force encrypt is able to reencrypt every boot???!?!?!?!), but ill write you more when i have time for a detailed post.

What checkbox are you both talking about?! I searched in my Magisk settings again and i dont see an option to "keep encryption". Also, should it look like this? Im missing the "rooted" sign (i have root, apps prompt me for it).

I tried both, 64 and 32 bit twrp, there are a few differences but 64 bit or any twrp which isnt able to decrypt automatically works better because it doesnt mess up with the format data...

Thank you for your link, i disabled force encrypt by flashing an additional zip, but ill try again using the commands, although i have no idea how i should do that, because everytime i boot system directly after flashing magisk, it shows "magisk not installed" and after 2-3 minutes heavy lag appears and system crashes. Then it reboots and everything works fine, also magisk says then its installed...

I guess ill write a guide once ive set up my phone...
[Moto G5 Questions & Answers] woozie.2007:
its strange what is happen with your phone, my opinion is to start from zero with stock, twrp and magisk 18
[Moto G5 Questions & Answers] G5-User7080:
Why, what happened to it? Because of Magisk is so empty? I found out that when i activate wifi it shows the rest, too (see Attachment).

And yes to be sure everything i tested is not caused by whatever, i did a clean oreo flash everytime.
[Moto G5 Questions & Answers] woozie.2007:
oh...you had the internet turned off, i didnt know that, so seems to be ok isnt? Your phone is encrypted now or decrypted? Can you make a screenshot in security please?
[Moto G5 Questions & Answers] Wolfcity:
Magisk needs internet connection to work properly.

So what's the problem you still have? That the device is still encrypted?
[Moto G5 Questions & Answers] G5-User7080:
Dont have any Problems atm, device is decrypted but ill reencrypt it once my settings are done, i can send you a screen and more detail later,.. i really have no time, since i have to go now, sry.
[Moto G5 Questions & Answers] G5-User7080:
Here you go.

Now the only Problem i have is finding out how to install Viper4Arise in Oreo.. it doesnt work with the Aroma installer i used in Nougat.

OK, now the details i wanted to tell you:

So at first i flashed clean STOCK Oreo, then TWRP, and there is already the first Problem:

Firstly using the 32bit TWRP and the one 'TheFixItMan' sent me, i ended up having problems formatting data like i described earlier (wouldnt work after coming from system). I flashed TWRP 64bit then, booted recovery, formatted data, rebooted recovery (data still decrypted), everything fine so far.

Then i tried to flash MAGISK deliberately to gain root and disable force encryption. Not only was my phone reencrypted when i booted SYSTEM afterwards, MagiskManager App also said 'MAGISK NOT INSTALLED' and i got heavy lags after 2 min leading into CRASH and REBOOT of the system. After the reboot everything was fine, MagiskManager App said Magisk is properly installed and i had no lags, etc, only my phone was still encrypted.

I tried around for quiet long until i found out that on every first boot after flashing Magisk it ended up like this and after a SYSTEM REBOOT (automatically after ~2min or manually at any time) the problems were gone and it worked like it should.

In order to remove encryption then i tried out NO-VERITY-opt-encrypt (v6) which didn't work, but i found Universal DM-Verity, ForceEncrypt, Disk Quota Disablers (DISABLE-ENCRYPT) and using that worked fine.

Remembering the procedure from rooting NOUGAT i firstly flashed DISABLE-ENCRYPT (after format data and rebooting recovery) and REBOOT SYSTEM.

After that i flashed MAGISK (wipe cache/dalvik if you want) REBOOT SYSTEM AND IT WORKS, no lags, Magisk installed, not encrypted, root.

I also can reencrypt phone manually in system settings now and will do after everything is done. (You can use your password then which you use to decrypt on boot in twrp64bit to decrypt data there aswell.)

In short:

flash oreo -> flash twrp64(or any not decrypting twrp) -> format data -> reboot recovery -> flash disable_encrypt ->

reboot system -> flash magisk (& wipe cache/dalvik) -> reboot system and install magisk manager

Last question remaining for that: How can standard encryption be applied on every boot when it takes like 5min when i activate encryption manually in system settings??! And is there any difference?

At last:

I searched for a Kernel to disable the One-Button-Nav vibration, i wanted to use Alize, but its only for 64bit Oreo, so i tried Flyhigh, but somehow it didnt boot (was stuck in bootlogo for around 5 min i guess). BUT i tried out ExKernel Manager and found out by accident, that it disables the vibration when i use the Powersave mode, which is pretty cool, but i wonder if the Powersave mode just sets some options like a preset and theres actually a setting for that where i can disable that vibration alone?

And now im searching for a way to install Viper4Arise (:

On one picture you should see how it was like testing out,.. it sounds so easy once you've found out XD
[Moto G5 Questions & Answers] woozie.2007:
Thanks, I will try next time when I reflash stock, now its difficult to me to reset all the phone again
[Moto G5 Questions & Answers] Wolfcity:
For me the Viper4android FX magisk module works perfectly. The only problem is that it won't work with Dolby Atmos. But Viper + Ainur Sauron +AML gives you a nice sound too.

So my advice would be flash within magisk manager

-Ainur Sauron

-Viper4Android FX

-Audio Modification Library

Reboot.
[Moto G5 Questions & Answers] G5-User7080:
- Thank you, works :D

I made a Guide now to how i rooted and so on, i hope that will help some ppl and save them some days of trying around :)

https://xdaforums.com/g5/how-to/root-how-to-flash-root-g5-opt-remove-t3884992

Would you mind reading it and telling me if i forgot something, a step or maybe something important like that thing that you shouldnt flash bootloader when youre already at b.8.31?
[Moto G5 Questions & Answers] Wolfcity:
Sure, just tell me where you posted that guide or if you haven't until now send me a PM.
[Moto G5 Questions & Answers] G5-User7080:
wow, im smart,.. forgot to paste the link...

here you go
[General Topics] MichaelWade:
Hey everyone. I'm new here, and I'm hoping you all can help me.

I just upgraded to WM6, and I'm having difficulties personalizing a few things. On WM5 I used to make complete custom skins for the phone and the today screen. Complete with custom buttons for the phone that changed colors when you pressed them. Now that I "upgraded" (HA!) to WM6, it says I'm not allowed to change those bitmaps to ones of my own!

I've read thread after thread, and found a few that said something about Total Commander letting you change the files, but I just couldn't get that to work either.

Does anyone have an answer for this? I would be forever grateful.

Thanks.

Michael
[General Topics] hchavarria:
Have you tried to soft reset and then changing file if not they maybe rename the old file and copy the new file. I suggest first to soft reset and before opening any other app replace your files.