You will need to get an app from the playstore called build prop editor and change ro.build.type to user. Also, you might have to reboot after doing this.

Titanium Backup- backs up app data as well as apps (without SU control Android does not allow communication between apps/screening app data).

Titanium Backup also allows you to clear all bloatware (although Package Disablers can do most of this nowadays without root)

Custom Roms (if Samsung releases source code) > Touchwiz

Xposed- SO much you can do even without custom ROMs

Viper4Android- Controls music playback more than stock android could ever do

Increased Tasker Functionality (such as triggering Airplane Mode)

Overclocking device for more performance/underclocking device for more battery life

AdAway- systemwide ad blocker to get rid of apps (won't work without root due to host file blocking/scanning)

Creating custom boot animations :)

Editing the build prop- https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en Great possibilities but can be hard to perform.

LOTS of aesthetic changes you could never think of doing with stock android

Greenify- great root app, automatically hibernates programs in the background (doesn't work automatically without root)

At the end of the day- rooting is about having full control over the device you paid for. For those who aren't android enthusiasts it won't be appealing due to triggering SafetyNet/Knox, loss of warranty, etc. but there are many, many possibilities with root.

http://forum.xda-developers.com/galaxy-s7

Head here for more root help with your S7. Remember that the Snapdragon 820 Version does not have an unlockable bootloader and all changes are made at your own risk. Rooting can have significant security implications (hence why Android Pay/Samsung Pay is disabled when you root).

TLDR; no

I use this one personally https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Also just editing the file in something like Solid Explorer works too (Located at /system/build.prop)

If you are going to edit the build.prop be careful as changing things in here can result in your phone no longer booting so make a backup just in case.

That said, the location is /system/build.prop or I would recommend using an app if you have root.

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en

Have you tried changing the Product model to SM-G920K? If not, try this: Download Build Prop Editor and change the "ro.product.model" value to "SM-G920K" (without quotes), save and reboot. Also write down the original value so, if it doesn't make a difference, you can restore it to its default.

Edit: Mostly the problem derives from a difference in the rom base and the product model in the build.prop. I'm not sure if above works because I don't know your current situation, but I'm pretty sure you'll find your answer in that direction. Check out this if you're still on XtreStoLite Deo-Mod Edition 2.3

If rooted using BuildProp Editor for example & adding in the bottom of /system/build.prop: qemu.hw.mainkeys=0 and rebooting enables the on-screen Navigation bar on the S5.

It will also add > Settings > System > Buttons > Buttons & layout menu with Navigation bar preferences.

Deleting the line or replacing the value 0 by 1 removes it.

This mod will not survive a LineageOS update & needs to be redone afterwards.

On my S5 G900M running 16.0 I also tried the Soft Buttons app > Virtual keys menu and it works by modifying the build.prop for you.

I don't use the on-screen Navigation bar on my S5 because of the loss of screen real estate & rather use the capacitive & hardware buttons.

Probably need to invoke the "su" command before this line.

Or use Build.prop editor to set the flag and reboot the device.

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en

No problem. If you have root, install this app: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Add persist.camera.HAL3.enabled=1 to the build.prop like this: https://gfycat.com/ImmaterialDazzlingAiredaleterrier

After that, reboot your phone and enable Camera2 API in OpenCamera settings.

Sure, I had the same problem with genymotion ( my phone is more OP than my PC).
First, if at all possible make a nandroid backup, just to be safe. I did't need the backup but I have a different phone than you (#nexusmasterrace).
Then install this app.
Open the app and backup your build.prop in the slide out menu, we'll need it later.
Then you can make the edits described here in step 6 and save. Some might already be the same as your phone already is a samsung.
Reboot, launch hearthstone and profit.
If it worked and you got your packs then restore the build.prop backup we made earlier and reboot.

The easiest way to change your DPI would IMO be to download the BuildProp Editor and edit (decrease) the "lcd_density" setting. The value that is set when you first try to edit this setting will be the default of your phone. You should notice the effects immediately after saving the change and rebooting.

I just went through all of this an hour ago with my Sony Xperia XA2 Dual (H3114).
Please note the exact versions I am using. I have tried and failed multiple times before this.

./fastboot boot twrp-3.3.1-6-pioneer.img
Wipe data, then advanced wipe and clear System as well.
./adb sideload lineage-17.1-20200415-nightly-pioneer-signed.zip
When this is finished, it is important NOT to boot the phone. Send the next command to sideload OpenGApps first, then whatever else you might need. I installed Magisk.
./adb reboot sideload
./adb sideload open_gapps-arm64-10.0-pico-20200415.zip
./adb sideload Magisk-v20.4.zip

Then you can reboot the phone going through the first boot.

I flashed Lineage 17.1 because I wanted Wifi Calling, which was not in Android 9 (50.2.A.3.22). This should be enabled with these commands, with an app like Build Prop Editor (requires root).

Bingo!.
I edited my build.prop with an app just before the camera stopped working (was fooling around trying to get the lockscreen clock to rotate to landscape). What should the permissions be (I guess it would work with 777, available for everybody, but it seems overkill)

So first of all it works fine on Marshmallow and I'm not sure why the other guys in this thread said otherwise. All you need to do is change one line and add one line to your buildprop. If you are rooted then you can use this app. If you have any questions or problems don't hesitate to ask.

http://androiding.how/enable-google-assistant/amp/

ok well the one in rom toolbox works, so I guess that solves my problem.

For anyone else looking to edit the build.prop, not by hand,

This app doesn't work

This one or it's paid version, does work.

I have used the build.prop hotspot method on 5.1.1. IMO editing the build.prop was the easiest method for getting a hotspot working on the verizon network.

Hotspot on Verizon Instructions [Root Required]

http://pocketnow.com/2015/01/01/nexus-6-tethering
Scroll down to build.prop.
I used the app Build Proper Editor It was suuuuper easy.

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

But be very careful. You can easily bork your device editing the wrong thing so make sure you backup before poking around in there

Maybe found another solution.

Download Build prop editor and in the app click on the plus icon scroll to the bottom and add "ro.debuggable=1".

it doesn't show if the parts are genuine or not though... heck, half of the info it shows can be modified with root and some app like https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

This is what I do on Verizon. For me it's blocked because I have unlimited data (grandfathered).

Download & Open Build.Prop Editor
Add line: net.tethering.noprovisioning=true
Save
Reboot

Keep in mind you'll probably need to do this anytime you take an update. It's a quick and easy fix though.

This is what I use:

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

I know. You need to root it and change it's ID in buildprop. Just search how to change device id in buildprop. Even your device will think it's something else. I know because I did this to my Lenovo tablet to spoof a Note 9. It brings a lot of advantages like downloading incompatible apps from the Play store. I know, rooting is dangerous and may void your warranty, but you'll be able to actually USE a Huawei phone. Here's a link to the buildprop editor: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Install something like this: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US (but any build.prop editor will do).

Open it, grant it root access, then search for the entry

>ro.mot.android_one=true

and change it to

>ro.mot.android_one=false

Save build.prop, reboot, and voila, in your Moto app you should now have One Touch Nav and Attentive Display (can keep the phone screen on while you're looking at it, regardless of your timeout settings).

Magisk modules don't work for me to enable Camera2 API. Use BuildProp Editor from the Play Store and add the entry:

Name: persist.camera.HAL3.enabled Value: 1

to enable Camera2 API. If you are on the MIUI Pie Beta, it has changed to persist.vendor.camera.HAL3.enabled

>... installed LineageOS 15.1 on a Moto Z2 Play... I don't find the option to restore the navbar so I can use the soft buttons...

Edit: Tested in both LineageOS 15.1 (S5 klte) & 14.1 if rooted using BuildProp Editor for example & adding in the bottom of /system/build.prop: qemu.hw.mainkeys=0 and rebooting enables the on-screen Navigation bar for both S3 i9300 14.1 & S5 klte 15.1 which do not have that option in Settings.

It also adds in 14.1 a Settings > Buttons > Buttons and layout panel to customize it.

In 15.1 it's Settings > System > Buttons > Buttons and layout.

Deleting the line or replacing the value 0 by 1 removes it.

This mod will not survive a LineageOS update & needs to be redone afterwards.

I also tried on both phones the Soft Buttons app > Virtual keys menu and it works great by modifying the build.prop for you by adding this in the bottom of it:

# added by Soft Buttons

qemu.hw.mainkeys=0

ro.show.navigationbar=yes That line is not necessary for S3 & S5

u/CesarDemi: Some feedback would be appreciated.

I had the same problem. It turns out the only way it works for me is to install this Build prop editor and manually add the line persist.camera.HAL3.enabled and assign the value "1" to it. Reboot the device and install gcam apk and that should do it.

I don't believe it will affect safetynet. Just download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor and copy the edit scroll to the bottom of the list and paste it reboot and it should fix your issue.

If you download buildprop editor and scroll down till you find

persist.audio.fluence.voicecall

Just set that to false. Some in the forums say it hasn't worked for them and others say it has so who knows!!

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

https://forum.xda-developers.com/nexus-6p/help/disabling-noise-cancellation-t3254276

This root app is probably the easiest way to edit it.

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Yes, you need to change the line "ro.product.model=" to something else.

I think next update will revert it back to the real device, but you can always change it back. You can always copy the build.prop as a backup before making changes if you are worried about screwing something up. Honestly, if you are very careful, editing build.prop is not such a big deal.

If you don't know, then maybe you shouldn't be doing it. Google it for answer.

But on a rooted device you could use: - https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en

I just noticed the following in the build.prop of a rom I'm looking to use, would this be the same or should I still copy & paste your provided command?

Yes=1 Add Hotspot Mods #

No=0 Leave Stock

hotspot.rom=1

EDIT: Or should I just use an app like BuildProp Editor to accomplish this?

source: http://forum.odroid.com/viewtopic.php?f=60&t=9869

To get Bluetooth work set in build.prop CODE: SELECT ALL config.disable_bluetooth=false

To get Wifi work set proper module name in build.prop

for Ralink RT33XX/RT35XX/RT53XX set

wlan.modname=rt2800usb

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en

or

Open & edit /system/build.prop

they both work. For Droid4x you have to make some changes to make it work though.

Edit:
Steps for Droid4x and using the store.
1. Download the Build Props Editor in Droid4x
2. Use it to change ro.product.model to SM-G920F, it's currently set to Droid4x
3. Use it to change ro.product.brand to Samsung, it's currently set to Android
4. It should now show up in the Play Store. It'll make you download Google Play Games so you can pre-download this if you want. I think this is a requirement on the phones/tablets anyways.

Well, I don't know of any app that changes the build.prop automatically to a specific device, but there are plenty of build.prop editors on the Play Store. Here's one that I found with a quick Google search, and a video showing how to change the Android version/model number of your phone (doing what you're talking about).

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor Will fix your dpi and double click power button from any screen will activate the camera which easily replaces the circle gesture

THANKS, worked perfectly on my Nexus 5 (Stock Android 5.1.1), i used the first app that came up when searching "build.prop editor", meaning this one:

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Thank you!

PS: Don't forget you need ROOT people and that root-ing a Nexus device will wipe it :)

Instead of that, I used this XDA post to enable softkeys by adding them to the build.prop file with this app. I now use them more than the hard buttons!

Tutorial.

(Must have twrp installed and phone rooted)

Download Havoc OS 2.7 7/10 build:
1. https://forum.xda-developers.com/lg-v30/development/rom-havoc-os-t3908402
Download Aroma Gapps (and do bare minimum functionality you need)
1. https://opengapps.org/
Download Magisk 19.3 flashable zip
1. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download Modded 5xx adreno drivers:
1. https://forum.xda-developers.com/mi-mix/development/driver-adreno-530-540-gpu-driver-t3815853
2. Follow the instructions in renaming the files using WinRar according to the device model. LG V30 is "msm8998". Use the non treble newest release for pie, and the Vulkan 1.1 folders. Rename the lib and lib64 (.so) files according to the instructions or you will probably brick your phone.
Put all files (all 5 being: Havoc, Gapps, Magisk, and 2 zip files (adeno 5xx - v331 and vulkan_1.1 renamed zips) for both OpenGL and Vulkan) into the phone's sd card.
Do a complete wipe in TWRP of everything minus the sd card, then restart, MAKE SURE TO MOUNT (CHECKMARK) THE SYSTEM PARTITION USING THE MOUNT OPTION IN TWRP immediately after restart and in the same session used for flashing (or you will break your phone with Aroma, and might brick your phone).
Flash (WITHOUT EVER RESTARTING. DO THEM IN THE SAME SESSION) in this order and clear cache/dalvik after each flash:
1. Havoc zip
2. Magisk zip
3. Aroma zip (choose what is needed using prompt (but don't restart))
4. adreno 55x -v331 rev 1 non treble zip, and then
5. vulkan_1.1 non treble zip
Start your phone and set everything up.
1. Open Magisk
  1. Flash Ram management Fixes by crok
  2. Flash LKT by korom43 (choose turbo mode)
2. Download and magisk flash GPU Turbo Boost 3.0 by EmperorEye1993: https://github.com/EmperorEye1993/GPU-Turbo-Boost/releases
3. Go to gltools.app in the browser and get GLTools, flash this using magisk, and with the TEXDecode Package... Only do default options as Optimize GLSL shaders, and Adreno driver half float Hack.
4. Download BuildProp Editor: Place the following from pastebin ( https://pastebin.com/SGQTRBd7 ) in at bottom of build prop file (best app to use is https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor for this. Save and reboot:
Install https://play.google.com/store/apps/details?id=inc.trilokia.gfxtool. Turn on auto settings and then apply settings to 3Dmark.
Go to developer Settings in Android (click build number 7 times and it will say you're a noob. LOL)
Turn off animations by selecting them to be 0.0x scale. Force GPU Rendering on. MSAA buffer GL 2.0 on. Use GPU for HW Overlay Composition On. Turn on gaming mode in Havoc OS in the settings
Plug in your phone to charge it, put your phone on some Otter Pops for a few minutes to cool down.
Let the fireworks commence. Reboot one time, run with gfx tool, and voila.
Questions? Beat me and tell me how you did it (with the same model H932 specs)

if you can't download magireco, even with a vpn, there's another way to get it, but it involves root: WARNING:SAVE THE PASSCODE FOR FGO, IF YOU PLAY IT
it should start when you unroot the phone, but i had some False-positive errorcode 60, rerotting and unrooting solved the problem

1.Root your phone(there are tons of tutorial on how to do that, a quick google search should do the job, i personally like magisk, since it's so quick to install)
2.Download build.prop editor https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
3.Modify this vaules into that app:
ro.product.model=SM-N9005
ro.product.brand=samsung
ro.product.name=hltexx
ro.product.device=hlte
ro.product.board=MSM8974
4.Download Tunnelbear https://play.google.com/store/apps/details?id=com.tunnelbear.android
5.Force close the play store and delete his data
6.Restart your phone
If you did everithing right, your phone will think that it's a Galaxy Note 3, search some samsung apps on the play store if you want to be sure you did everithing right.
Now you need to follow this guide to use tunnelbear: https://github.com/SchoolIdolTomodachi/SchoolIdolAPI/wiki/How-to-install-Japanese-apps%3F
6. Unroot your phone
If you don't chance back your build.prop, you don't need to do that every time the game updates, now it works like a normal app downloaded from the play store.

RN4X with MIUI 9 here.

After enabling enabling camera2api (through build.prop editor), the camera works fine

if your rooted install

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_GB

add the line "persist.camera.HAL3.enabled=1" (without quotes) save reboot, install

https://play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en_GB

all tests should pass then install Gcam_6.2.030_Advanced

https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/

this should also work on the a2 lite but untested

I'm using this build prop editor with success, the variable in question is called ro.sf.lcd_density.

Try Buildprop editor

You can get Google Assistant right now by editing build.prop, no need to change device model now.

Just add or replace this line on your build.prop

ro.opa.eligible_device=true

If you have root: you can edit BuildProp with:

(Easy and fast) Using BuildProp Editor.

To add it in BuildProp Editor, three dots in top right, New Name: ro.opa.eligible_device Value: true

If you don't have root or prefer not to use that app, there are two methods you could use: This method. Download page from the page this XDA page by a senior XDA member. The guy in the video is using an older TWRP version.

However, I would prefer to just edit build.prop in TWRP (potentially safer, and takes away the possiblity things might mess up when Google Assistant rolls out automatically):

If you uninstalled the drivers for some reason: Install ADB, Fastboot and Drivers

Download your device USB drivers: e.g. For Motorola devices.

Boot your Android device into TWRP recovery. 1. Select Mount » and then select System from the list of partitions to mount the system partition and then go back. 2. Connect your device to the PC with an authentic USB cable. 3. Open a command window on the PC and issue the following command to pull build.prop file from the device: adb pull /system/build.prop 4. The above command will download the build.prop file to your PC in the same directory where your command prompt is running from. └ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file. 5. Download and install Notepad++ software on your PC. 6. Open the build.prop file on your PC using the Notepad++ program. 7. Edit the build.prop file as per your requirement and save it on the PC after making the changes. 8. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command: adb push build.prop /system/ 9. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one): adb shell cd system chmod 644 build.prop 10. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option. That’s it. You’ve now successfully edited build.prop

Edit: Method without root. Details.

if youre rooted use buildprop editor and find "ro.sf.lcd_density" and change it to the DPI you want then reboot.

Some people over at XDA also had the same issue.

A fix is to get Build Prop Editor, and then go ahead and find ro.build.type from there change it from whatever it is to user. From there it should be working and not showing Miscellaneous anymore!

You can also use this app: Build Prop Editor by JRummy. It's what I use and I recommend it.

1) Root phone

2) download a build prop editor

3) change the "persist.audio.fluence.voicecall" value to FALSE.

This will disable the background noise cancellation for phone calls. This improved my voice quality on calls 10 fold. I was so sick of people telling me I sounded muffled or like I was breaking up and having to use a headset for every call. I don't think this effects the camera mic or anything else but this should be prominently displayed for all N5 users to see because it finally allowed my phone to be used as a phone.

Edit: Build Prop Editor also requires BusyBox. Both are bundled with Rom Toolbox.

I lost my second OPO last week, my international invite for OPT is like around 350,000^th, so here I am with a Chinese OPT :)

Flashing is straightforward, find the Oxygen OS file and you can do it through the stock recovery. There's an OTA update after (for Stagefright, so it's a must-do), not sure if they have an updated flashable file though.

Mind you, outside of China, if it breaks, there's almost no chance of RMA, so you gotta like living on the edge a little bit. My unit's home button is a bit wonky, perhaps I've been touching it the wrong way, but I'm crossing fingers that it's not a manufacturing issue.

Edit: Just saw that OP is new to flashing, so here are the steps:

Charge the phone, better be safe than sorry
Download the Oxygen OS file while charging, transfer it to the main folder of the phone, grab a non-alcoholic drink
Hit recovery, turn off the phone and hold the Power button + Volume up button (a bit awkward on the OPT with the buttons on the same side :P)
Choose English, then backup everything
Choose Install by SD, browse to the .zip file, flash it
Wipe cache
Reboot the phone, cross your fingers
If the phone boots (it should), grab an alcoholic drink, celebrate, set it up, enjoy
If you'd like to venture a little bit more, I'd recommend this guide on unlocking the bootloader, installing custom recovery, and rooting

Bonus: Oxygen OS ships with 480 dpi as default and you have to add a new parameter to the build.prop file. Once you are rooted, get the build.prop editor and add a new parameter ro.sf.lcd_density and set the value to 380 or 400 or 440, do experiment and find your sweet spot!

Worked perfectly with this app and an LG-G3 on CloudyG3 2.5

Wanted to stay on A10 for TWRP, but made the jump to A11 and it's fine, currently not rooted as i OTA updated though the UI and assumed i could grab the Boot.img file from the Unihertz Google Drive, but the files there are older versions, and using one might cause a Soft-Brick, losing all my Data & configuration, so after backing up my Data & configuration i could try it & if it Boot-Loops Flash it, then Download the OTA update BUT this time grab the URL & keep a copy of it, but i''m lazy & my life is busy. just waiting for Unihertz to release the next security update, based on there update history that might take a while...... i Emailed them() about it but they just told me the same thing the PDF's say ignoring my request for them to upload the latest OTA, so yeah totally useless regurgitation.

i have experience & knowledge of most of the subjects around this phone, feel free to tag me like /u/Vencen-Hudder

If you do every have time & want to experiment i do have a few things i could not quite get a satisfactory answer to my self.
Note that Root fiddling with your phone can cause Data loss, Back up First! don't be stupid like me and assume it's safe..... that data is never coming back :(

Power on phone when plugged in. https://www.reddit.com/r/UnihertzJelly2/comments/rhcgm8/boot_up_on_power_jelly_2_as_car_dash/ i tried to set the Prop fastboot oem off-mode-charge 0 but it didn't work for me.
Volume steps. only 16 Volume steps! i bricked my Phone Trying to change it, see below. see this post for details

If you or any one else does Update Please Get the OTA URL, How to the one i'm looking for is (see below) or Newer

UI

>Setting > About Phone: Build Number
Unihertz_Jelly2_20211229
Setting > About Phone > System update
Unihertz_Jelly2_20211229_20220225-1415

Jelly 2 brick Round 2!

i Tied to edit build.prop with a granted Root File managers editor but it says it was read only, so i edited build.prop with https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor but once i did when went to check & opened build.prop with an text editor it was empty. so stupidly i just rebooted, to a loading screen boot loop :(, i was able to get the recovery & fastboot CMD's working & planed to do an OTA update from SDcard but i tried to boot TWRP first, got a black screen so i flashed it to Recovery, after that the device only showed a Red LED when plugged in with on other signs of life. no surprise really as These is no TWRP compatible with A11.

So when to trying to flash it with out erasing the User data, as i din't have a resent backup.......

On linux with SP flash tool V???? i used download only mode(given) & checked all options but 'Cache" & "user data" & it ended with the error "STATUS_DOWNLOAD_EXCEPTION"
but the Jelly 2 booted! with an error DM-verity, see pics so i got it to the recovery screen(yay!) and side loaded the latest OTA from my Fat23 32GB SDcard & it give an error about Cache, so i wiped it (used the menu option) & mounted /system & retried with this error(see pics)

redid the flash, this time leaving only Userdata unchecked.... ended with "downloaded succeeded" (green check mark), it booted with the error "error DM-verity" but after pressing power we booted to the set up screen (Hi there), no user data was left.... now back to the beginning, again not that it reset the Bootlaoder back to locked just like Uniherts Flash Tool

it gives the error about Dm-verify some time still, disabled Dm-verify using fastboot(see TWRP section of LOS ROM) wiped cache & that seems to have fixed it, but not after the OTA?
Here's a CMD log

Here is some Pics https://imgur.com/a/Q7vD9o4

maybe useful links

some help on fastboot & bootlaoder mode https://source.android.com/setup/build/running
https://www.droidwin.com/flash-stock-firmware-via-fastboot-commands/
https://android.stackexchange.com/questions/210441/can-user-data-be-recovered-after-formatting-and-flashing-stock-rom
https://technastic.com/turn-off-safe-mode-android/#:~:text=your%20Android%20device.-,method%203%3A%20using%20adb%20command%20(root),-We%20saw%20how
https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/#:~:text=enter%20safe%20mode%20with%20device%20buttons // enter safe mode with buttons

Maybe Restore build.props app through fastboot & related link once you soft-brick your headset

https://androidforums.com/threads/i-had-a-boot-loop-after-i-edit-the-system-prop-files-can-somebodya-help-me.558947/
https://www.reddit.com/r/AndroidQuestions/comments/3sxafz/buildprop_bootloop/
https://nerdschalk.com/edit-build-prop-without-root-using-adb-in-twrp-recovery/
https://androidforums.com/threads/how-to-repair-build-prop-with-recovery-through-adb.945407/
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it?share=1
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US&gl=US&showAllReviews=true /// WARNING! you can Soft-Brick your Device with this APP, Make a full back up & use at your Own Risk. don't lose all your data like me & the 100's of other reviewers who have no choice but to leave a one star review because the dev did bot care enough to warn them.
https://forum.xda-developers.com/t/guide-recovering-from-a-bootloop-without-twrp-or-kdz-tot.3167361/#post-62083159
https://forum.xda-developers.com/t/bootloop-after-editing-build-prop.3719769/

What's the best way to edit that file? I tried this but I get an error saving: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Use this app and you'll be fine https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

BuildProp Editor – Android Apps on Google Play - https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

In your sytem partition, use root explorer to modify it, or just use this (you need root for this)

I used a build prop editor from the play store (https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor) not sure if this automatically does this or not.

You can get Google Assistant right now by editing build.prop, no need to change device model now.

Just add or replace this line on your build.prop

ro.opa.eligible_device=true

If you have root: you can edit BuildProp with:

(Easy and fast) Using BuildProp Editor.

To add it in BuildProp Editor, three dots in top right, New Name: ro.opa.eligible_device Value: true

If you don't have root or prefer not to use that app, there are two methods you could use: This method. Download page from the page this XDA page by a senior XDA member. The guy in the video is using an older TWRP version.

However, I would prefer to just edit build.prop in TWRP (potentially safer, and takes away the possiblity things might mess up when Google Assistant rolls out automatically):

If you uninstalled the drivers for some reason: Install ADB, Fastboot and Drivers

Download your device USB drivers: e.g. For Motorola devices.

Boot your Android device into TWRP recovery. 1. Select Mount » and then select System from the list of partitions to mount the system partition and then go back. 2. Connect your device to the PC with an authentic USB cable. 3. Open a command window on the PC and issue the following command to pull build.prop file from the device: adb pull /system/build.prop 4. The above command will download the build.prop file to your PC in the same directory where your command prompt is running from. └ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file. 5. Download and install Notepad++ software on your PC. 6. Open the build.prop file on your PC using the Notepad++ program. 7. Edit the build.prop file as per your requirement and save it on the PC after making the changes. 8. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command: adb push build.prop /system/ 9. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one): adb shell cd system chmod 644 build.prop 10. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option. That’s it. You’ve now successfully edited build.prop

Edit: Method without root. Details.

This app worked for me: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

That's what I do. And if you don't want to do it manually, there are apps that will do it for you. https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

yes. it requires some tweaking, but i've been on it since release with no issues other than no visual voicemail. there is a thread in here with great info. let me see if i can find it. it reallly ought to be stickied. couldn't find the thread, but here's what you need to know:

first: clean flash from stock. here's the rom itself. http://forum.xda-developers.com/lg-g3/development/rom-cloudyg3-1-0-t2917467

this page has the build.prop edits necessary. http://forum.xda-developers.com/verizon-lg-g3/general/cloudy-g3-rom-t2920418/page4

and this is the app i recommend for doing so. this is the best blend of ease of use and features i've found. don't forget to backup! https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

after all this you just gotta go into the network settings and switch from global to lte/cdma and enable roaming. you won't actually be roaming, but the status bar may indicate that you are. if that bothers you, you can use this to hide the notification and all sorts of other cool crap. requires xposed which is an option in the rom installer. https://play.google.com/store/apps/details?id=it.ptoti.g3_tweaksbox

Look into build.prop files - you can do things like spoof devices, increase responsiveness, improve audio/video quality, etc. Check out this list for example: http://geekyogi.com/post/24692879082/android-build-prop-tweaks-root-only

It's got a ton of tweaks for build.prop files. To do this though get a build.prop editor, like https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor, and get a build.prop backup, like https://play.google.com/store/apps/details?id=com.caffinegeeks.buildpropcloudbackup . Make sure you back it up though, otherwise if you screw everything up, it's nice to have a stock or almost-stock build.prop file.

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Yes, i was trying that but you need rooted android device, app for editing it here : https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en
if you mean that your phone is too old to run these apps then you cant do anything

by the way, this is windows 11 subreddit, not android subreddit

Get if from here https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

What is Reddit's opinion of BuildProp Editor?
From 3.5 billion Reddit comments

BuildProp Editor

Popularity Score: 60

Best Comments

No=0 Leave Stock

UI

Jelly 2 brick Round 2!

maybe useful links

Maybe Restore build.props app through fastboot & related link once you soft-brick your headset

What is Reddit's opinion of BuildProp Editor? From 3.5 billion Reddit comments

BuildProp Editor

Popularity Score: 60

Best Comments

No=0 Leave Stock

UI

Jelly 2 brick Round 2!

maybe useful links

Maybe Restore build.props app through fastboot & related link once you soft-brick your headset

What is Reddit's opinion of BuildProp Editor?
From 3.5 billion Reddit comments