yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Q&A, Help & Troubleshooting] K3n H1mur4:
So, after a few months on Oreo I clean flashed DotOS Pie last night, got the whole thing set up and tried to encrypt phone. It now bootloops, but I can get to TWRP, which shows me a pattern to decrypt data, even though my phone had PIN lock. I did the trick to "translate" between PIN and pattern grid. TWRP shows me "data successfully decrypted, new block device: '/dev/block/dm-0'", but I can't mount /data (consequently can't mount /sdcard), though I can mount /system. TWRP's console shows "Failed to mount /data (Invalid argument)".

I know I can just format /data on the wipe menu to get rid of encryption, but since I don't have a backup of /sdcard, I would like to know if there is any way to get /data mounted again so I can backup my internal storage before formatting /data.

If it makes any difference, my TWRP version is 3.2.1-0, latest one available at twrp.me. I heard that 3.2.1-1 handles encryption better (even better than more recent versions on some devices), but it's not available on the official site.

--Other details that might be relevant, but I'm not sure:

1. I do have TiBu's backup on my computer, so if I must restore my apps I'm fine with it (though I don't have a backup of the whole internal storage);

2. I also have a Nandroid backup of /system, /data and /boot, but it's on the phone storage only;

3. Last, but not least, I have flashed latest Magisk just before encrypting the device.

I saw some stuff related to a no-verity encryption zip file to be flashed via TWRP in some discussions regarding other devices, would it be of any help in my case?
[OnePlus 2 Q&A, Help & Troubleshooting] K3n H1mur4:
[MENTION=5842226]anupritaisno1[/MENTION] sorry to bother you, but you're the one person to ask for help with TWRP on OP2. Could you lend me a hand here? Would your enhanced TWRP help in my case? I know one shouldn't restore backups made with one version of TWRP within another version, and also that the tempcache stuff needs to be set up to flash ROMs. My plan here, if this could help, was to see if your enhanced TWRP can successfully decrypt my /data and internal storage, then I would back up my internal storage to my computer and either set up tempcache or reflash official 3.2.1-0 to format data and flash the ROM again.

Thanks in advance.
[Android Head-Units] OwnageWOT:
Hi guy's,

I have an Android headunit noname,only know info in About Device are this :

Quad T3

1gb ram

16gb

Android version 7.1.

Everything's work on it without problem but there's a bug or a software problem,i dont have Mobile Network in settings to set APN.

I go to setting-more- and here is missing Mobile Network.

There are all settings except this.

I dont have a sim card slot but i have 2 USB port and headunit is compatible with 2-3-4g network and i have a modem.

I try with ppp widget but i cant use widget's to connect is instaled but dosent appear if i plong press screen. No widget's.

Know somebody other solution to bring Mobile Network settings ?!
[Android Head-Units] Dr.Dimes:
Have the same problems with an Tristan Auron HU BT2D7018A. It is on Android 8.1.

THE hU is a Xrross HU. maybe there is a Rooting possibility?

Greetings
[Android Head-Units] Tbizzness:
Mobile internet can only be used through a 3 or 4G Dongle or Mobile router. To make phone calls you need to be connected via Bluetooth to your phone. Only way to give the command to call using voice command and using MTC dialler or install FCC Launcher and default the launcher and use the phone dialler within the app.
[Moto G6 Questions & Answers] groston:
The phone that I would like to update is a Moto G6, type M390A. The phone is currently running Android 8.0.0, build OPS27.104-92. The phone is rooted, stock ROM, and has TWRP and Magisk installed.

Earlier today, I followed the instructions here https://highonandroid.com/android-howtos/how-to-ota-update-rooted-pixel-phones-without-computer/ to update my Pixel 3XL. The instructions were almost flawless – the only two minor ‘gotchas’ were 1) having to first update to the most recent version of TWRP (when I tried the version that was a few months old, I received a kDownloadPayloadPubKeyVerificationError) and 2) I had to reinstall Magisk after the reboot mentioned in Step 9. Bottom line – the process went quickly and easily. Needless to say, all of my apps, settings, and data were unaffected by the upgrade.

I am hoping that the experience with the Moto G6 might be as smooth and easy. However, there are three differences of some concern:

The OTA zip file is not from the Motorola site – I found what appears to be the proper file here: https://www.skyneel.com/moto-g6-pie - I selected the ‘Download Moto G6 Pie Android 9.0 OTA ROM’ link.

The TWP file is only available as a .img file, not a zip file.

For the Pixel 3XL, the OTA was a minor version upgrade as it was already running Android 9; for the Moto G6, this would be a major version upgrade.

My question for the group is simply this: Using the files mentioned above, if I follow the procedure described in the first link; namely copy ota.zip, magisk.zip, and twrp.img to the phone; reboot to TWRP and install, in order, OTA, TWRP, and magisk; and then reboot; will I likely succeed in updating the phone while not messing up my data, settings, and data?

Thank you.
[Moto G6 Questions & Answers] madbat99:
There are a bunch of g6's. Trying to apply an OTA at random will fail. Your pixel has a/b partitions, g6 does not. A only.

The best way I know to update a Moto is, make sure you know your exact model number, and update channel. Both can be found in about phone section in settings. Download a full firmware package (not an update zip) and either

1. Extract it and flash every partion with fastboot

Or

2. Use RSDlite (windows PC program) and flash the firmware with that. Then flash TWRP again (or just boot it) and flash magisk.

I prefer option 2. Easy peasy. And RSDlite will ask if you want to use flashfile.xml (wipes data) or the servicefile.xml (doesn't wipe data.

RSDlite basically performs all of the fastboot flashes for you, and the servicefile skips the data format.

Even if you restore 5je stock recovery, most attempts at trying to flash an OTA zip will fail. You may have made some changes to the system at some point which will trigger an assert prop failure.

Plus the OTA would have to be for your specific g6.

Someone else may chime in with different instructions.

But this is not a Pixel. There are like 20 something different g6's and update channel combos.
[Moto G6 Questions & Answers] groston:
madbat99 - I appreciate your taking the time to provide a thorough reply, thank you. Sadly, I still have questions: Following is a screen grab of the About Phone tab.

View attachment 4739963

You indicated that I need:

Exact model number: It appears to simply be moto g6

Update channel: I see a 'Software channel' - is this the same thing?

When I went looking for firmware, I found this page https://www.getdroidtips.com/moto-g6-plus-play-stock-firmware/, but

Android 9.0 is not shown as being available (but other sites suggest that at least a beta version has been released)

I do not see the existing build listed, thus I am worried that none of these are correct

Would you please be so kind as to point me directly to an appropriate source of firmware files for this phone?
[Moto G6 Questions & Answers] madbat99:
So your software channel is fi. Not sure where to get that one. Clicking on hardware in that menu gives you your model number. Under SKU. See in screenshot. I'll look for a firmware for you.
[Moto G6 Questions & Answers] madbat99:
Forgot screenshot
[Moto G6 Questions & Answers] madbat99:
You have a Google fi device. It doesn't appear pie is available for yours yet. It will be, I would wait if I were you.

here are the currently available firmwares for your model. There are ones that have been updated to pie, and one or more of those may be able to be flashed to your phone. I don't know what that would do to your fi eligibility/connectivity. So someone else will have to chime in on that.

The 2 firmwares on that page are newer than what you are on. Newer security patch updates than you have now. Good.

Now if you want pie, skip to the bottom of your thread here!
[Moto G6 Questions & Answers] madbat99:
[MENTION=2718072]groston[/MENTION]

I found this post, where a member with the fi version of the g6 that says he flashed the pie firmware for the retail g6 and all went well. I will also link the post that he mentions which contains the flashfile.
[Moto G6 Questions & Answers] groston:
madbat99 - again, thank you! The version for this phone is PVT1, SKU XT1925-6.

In your opinion, can I use the zip file linked in the post your cited with the RSDlite process you outlined, specifically using the servicefile.xml approach? The SKU for the phone the poster mentioned is XT1925-5 reteu - close, but the same?
[Moto G6 Questions & Answers] madbat99:
Here is the post with instructions and links to everything you need. It's official Moto firmware, so no "need" to even have an unlocked bootloader (but I'm sure yours is already unlocked).

So now you have a couple options. you can either update to the newest Oreo security patch for your device, or update to pie if you like.

---------- Post added at 09:16 PM ---------- Previous post was at 09:06 PM ----------

Yes you can use RSDlite to flash it if you want.

But... With the jump from Oreo to Pie, and switching software channels, I would recommend a data wipe. Meaning the flashfile in RSDlite.

You can try without the data wipe, then if something doesn't work properly for you you can always wipe data afterwards.

[MENTION=2718072]groston[/MENTION] do you have RSDlite?

Guess I might as well grab you link for that too, lol

I realize that the bulk of that post was from a RETEU version, but the person quoting it said they have the fi version and it worked.
[Moto G6 Questions & Answers] madbat99:
Here is the RSDlite I use (plus a bunch of other useful programs). Check my screenshot, I circled the one you want.

One last thing, you might want to pop in to the thread I linked and ask others about flashing it on the fi version. Just so you cross all the t's and dot all the i's.
[Moto G6 Questions & Answers] madbat99:
This is the part that I saw that related to your phone.
[Moto G6 Questions & Answers] groston:
I asked Google Fi tech support if they could point me to a firmware version for the fi software channel. Here is there (not terribly helpful) reply:

I will follow madbat99's suggestions...
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Updated: OP contains instructions for Android Pie and below, post #5 has current instructions for Android Q.

Saw a couple Viper4Android threads, did not see much in terms of profiles for the 2 XL specifically. Just got the 2 XL coming from a 6P and there was a great profile to optimize it's internal speakers so decided to try out the mod for the 2 XL's speakers. Working very nicely.

Not sure if this will work with every ROM but works nice on Bootleggers (should work on any Pie ROM including stock) and thought I would share so more people could enjoy much improved sound quality. Makes rooting the phone well worth it.

Instructions:

After installing Magisk 18.1

Install BusyBox and run the set-up

Download the Viper4Android V4.1 (used Material theme) via Magisk manager

run the install process, select 2.5.0.4 material theme, install as system app, grand root access then reboot

Load the DorianX profile taken from the 6P. Just unzip then look over the extracted files.

Edited to explain further: You will probably need to individually place the "SRS Audio HD" IRS file in the Viper4Android Kernel folder and put the Profile folder in the Viper4Android Profile folder (using a file explorer to copy/paste the files). Once that's done, in the Viper4Android app under "Convolver", tap it and choose "impulse response file", You should see the "SRS Audio HD" IRS file that you placed in the Kernel folder, select it, tick the box next to Convolver to enable it. Under the main app settings you should be able to select and load the profile. If you did it correctly the DorianX profile folder should be visible to select it. It depends which version of Viper4Android you install. If you do materialized (2.5.0.4) the above should work. Let me know if any problems

Play some music. Toggle Viper4Android master power on and off under the phone speaker tab within the app then back to on once to enable it. Usually you have to do this to "officially" enable Viper4Android. If it's working you will hear the difference. Under the app settings you can verify that the app is processing as well under "driver status". Working with the latest Poweramp, Youtube, etc.

Credit to DorianX who made the profile. There are 4 profiles included to optimize specific bluetooth devices, headphones,etc but just using the internal speaker one (for now). Unable to locate the past post in the 6P forum containing the profile and which other devices were optimized to link to it.

Works very well and thought it was worth posting and making a small contribution so for now enjoy! Profile attached.
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Have Viper4Android working nicely on Android Q Beta 4.

Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.

Looking at the speaker xml file can see some of the settings but probably not all.

Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.

Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
[Google Pixel 2 XL Guides, News, & Discussion] libracez:
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
See below
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Ok I got it. No need to PM me the profile. Took most of the night but done now.

Would be unable to stay on Q without Viper4Android as well...

Make sure to uninstall all previous versions of Magisk and modules to start fresh.

Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.

On Pie in Magisk you should see Viper4Android 2.7.1 module as available

On Q it's not listed (for me at least) so get it from XDA labs.

Install Viper4Android:

https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)

Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.

Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.

Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://xdaforums.com/pixel-2/help/viper4android-driver-installation-fails-t3766362

Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app

Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)

Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.

For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:

Master limiter: On

Playback gain: moderate or 2, max gain 4x, output threshold -1.9db

FIR Equalizer: On. EQ is flat

Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0

Profit.

You can set or disable the viper4android notification icon in the statusbar within the app's settings.

Let me know how the 2 XL's speakers sound :) Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.

Thanks to [MENTION=9073985]Team_DeWitt[/MENTION]

And Dorianx for his profile originally created for the 6p
[Google Pixel 2 XL Guides, News, & Discussion] libracez:
succesfuly, ty

for my 2xl It was

1. installation from xda lab - reboot

2. install audio modification library - reboot

3. open viper (still asking to install driver - just close app, don't choose nothing)

4. go to Magisk switch off audio modification library - reboot

5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Our 2 XL's can be temperamental, lol.

Glad you got it working. Not sure how the driver installed and the viper app fixed itself with the audio modifications module switched off. It's like you didn't need that module at all. Whatever works.

Just happy we have viper for Q. Played games, music, youtube and running stable here.
[Google Pixel 2 XL Guides, News, & Discussion] Mr. Blanco:
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated :D
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
No problem. You are looking for the viper4android folder not the app. See attached screen
[Google Pixel 2 XL Guides, News, & Discussion] Mr. Blanco:
I figured that and searched and searched through internal storage and root directory and i cannot find that app anywhere in my file explorer ..lol this is crazy :eek: im using Mixplorer and have attached pics , not sure if i should erase everything and start from scratch again ..lol

Edit: Okay after multiple reboots it magically showed up and was able to put file in correct place but now Driver Status Enabled = no (message) strange ....gonna start over and see if i can get everything working ..lol Thank you for your help @ powerserge1

Edit: Everything up and running and working ... Profit :cool:
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Good stuff. To anyone else installing viper just to note if you click on driver and see it as processing = no this does not mean you did anything or the install went wrong. Play a video or music, driver should show as processing yes. When nothing is playing then processing will be no.
[Google Pixel 2 XL Guides, News, & Discussion] serialkillazzs:
Does this enable dual speaker for calls/message alerts?
[Google Pixel 2 XL Guides, News, & Discussion] joedajoester:
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:

https://xdaforums.com/showpost.php?p=79682444&postcount=477
[Google Pixel 2 XL Guides, News, & Discussion] joedajoester:
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Someone in the Android Q discussion thread might be able to help better. Google pulled the beta so it's tough to say whether in your case it's a magisk or android issue. Or both.
[Google Pixel 2 XL Guides, News, & Discussion] zxspectrun:
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.

I had to port the userprofile to the new version, if someone want it, PM me
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
[Google Pixel 2 XL Guides, News, & Discussion] zxspectrun:
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles

attached dorian ported to v2.7.1.0
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Yes it did the same for me. The first time, almost forgot. I did not find the sound to be the same, not even close. Ultimately I still had my Nexus 6p and was able to retrieve the settings and input them manually. Then the sound was as it should be.

Do you find the sound identical with the ported profiles? It might be hit and miss.
[Google Pixel 2 XL Guides, News, & Discussion] zxspectrun:
Unfortunately I never tried the original sound, so, can you please share the one you manually retrieved? ??
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Posted the settings in post #5. The profile was originally for the 6P's stereo phone speakers and now using for the Pixel 2 xls.

You have a pixel 3, not sure if the profile is optimized for it. Have not tested. Try the settings in post #5 and let us know what you think vs stock.
[Google Pixel 2 XL Guides, News, & Discussion] zxspectrun:
All Right, I'll, and who's or where can I find the original creator?
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Dorianx, his//her profile but was unable to find the posts in the 6p forum.
[Google Pixel 2 XL Guides, News, & Discussion] lonton:
ViperFX app keep forceclosing on my 2XL. Is there anyone encountered the same thing ?
[Google Pixel 2 XL Guides, News, & Discussion] greyhd:
No issues here. Which viper version are you running?
[Google Pixel 2 XL Guides, News, & Discussion] LeifAlbor:
Thanks so much for the walkthrough in Post 5!!! It's made music on Android Q sound good again!
[Google Pixel 2 XL Guides, News, & Discussion] lonton:
Just got viperfx running in my 2xl Q now. I think the problem was magisk. Latest magisk canary is working fine.
[Google Pixel 2 XL Guides, News, & Discussion] 1dopewrx05:
Which canary version are you using? I cannot get V4A installed for the life of me. I have tried OP's directions as well as the directions in post #5. I would like to see which version you were successful with. Thanks man
[Google Pixel 2 XL Guides, News, & Discussion] Xdevillived666:
Can confirm this works on pixel 3 as well. Thanks!