yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Lirannl:
I have an f2fs volume I want to mount. The problem is, every time I look up "Android" and "f2fs", what comes up is internal storage. I'd rather stick to ext4 storage for the time being. What I want is to mount my f2fs volume just like my Linux laptop can without any issues. I know if I want things to work with windows I need exfat, but I have no interest in windows functionality. I just need my storage drive to work on Linux based systems. Windows doesn't interest me.

I'm on a rooted OnePlus 7 Pro and am willing to flash. Oxygen OS 10 OB5. (latest beta)

If mounting f2fs volumes is impossible on Android - a system based on the Linux kernel, I'd love to know why is that so. I was considering building a kernel from source, as I've written a game in C and believe I'm experienced enough to build a kernel at this point.

Thanks in advance!
[Android Q&A, Help & Troubleshooting] namhoang235:
Nó information. sadly
[Android Q&A, Help & Troubleshooting] afridi.shahriar:
Check the below reply.

Instead of editing this message, i mistakenly replied again.

so, erased this message
[Android Q&A, Help & Troubleshooting] namhoang235:
thank for your suggest, but i use android 11 and sdcardfs and mnt/extsd seem like changed,

i try to replace by storage/sdcard1 but it doesnot work
[Android Q&A, Help & Troubleshooting] namhoang235:
also try to edit fstab from auto to f2fs but it not show my sdcard, my rom support f2fs alreadyView attachment 5491643
[Google Pixel 3 XL Questions & Answers] godzulu:
Pixel 3XL, stock rooted, no weird apps, just normal updates. My phone app keeps stopping and have to force close. Just tried to add number to create contact and app freezes up. Tried to end a call but no end button etc. Anyone else experiencing this? Any idea how to fix? Thanks a lot
[Google Pixel 3 XL Questions & Answers] spotmark:
Are you using any themes? If so you should check for updates. A few weeks back the My Verizon app was causing some problems with the dialer as well. If you have it, you can try uninstalling it.
[Google Pixel 3 XL Questions & Answers] godzulu:
Thanks, but no themes here :/
[Google Pixel 3 XL Questions & Answers] boe323:
Join the beta program and update, or go to apk mirror and install the 64bit no dpi
[Google Pixel 3 XL Questions & Answers] parakleet:
the ultimate solution will most likely be flashing factory image with wipe.
[Google Pixel 3 XL Questions & Answers] godzulu:
Thanks, I downloaded the beta....lets see how it performs
[Xiaomi Mi 9 Questions & Answers] AZ_Miss_Murder:
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.

I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off

I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.

I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.

Same happens for my SO's Mi 9 too as well.

Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....

Hardware test shows Main and Top as PASS.

Any tips would be appreciated! I feel like I've tried everything possible.

Thanks in advance~
[Xiaomi Mi 9 Questions & Answers] Laptapper:
Your TWRP is right.

Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.

If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
[Xiaomi Mi 9 Questions & Answers] AZ_Miss_Murder:
I'm actually going to follow the Evolution instructions (just missed the part about flashing EEA)

So i'm using MiFlash with the MIUI11 EEA boot rom file, then I'll do the normal TWRP -> format data -> install Evolution ROM and test.

Thanks!
[Xiaomi Mi 9 Questions & Answers] AZ_Miss_Murder:
So it seems like I'm completely out of luck at this point - I've tried basically everything I can think of, and I think something big must be wrong with the phone's file system.

I've followed Evolution's steps to a T (minus MiFlash having an error at the end of the EEA flashing, but the firmware seeming to load fine) and still run into the no Mic issue.

"Flash MIUI11 eea with miflash

Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (Download here)

Flash TWRP

Wipe (dont wipe system/vendor)

Format data

Reboot recovery

Flash rom

Reboot system"

Wipe (don't wipe system/vendor) I assume means just a normal factory reset wipe via TWRP, which I've tried.

I've tried both fw+vendor files (the newest for Android 10 and newest from Xiaomi.eu)

Any other last suggestions before I assumed the phone is broken?
[Xiaomi Mi 9 Questions & Answers] Laptapper:
Try to flash xiaomi.eu_multi_MI9_9.11.7_v11-10.zip

With miflash and after factory reset.

https://sourceforge.net/projects/xi...iaomi.eu_multi_MI9_9.11.7_v11-10.zip/download
[Xiaomi Mi 9 Questions & Answers] AZ_Miss_Murder:
SO! Update here

I was able to use Evolution X's Android 9 instructions to get everything working fine....but everytime I try to duplicate that for MIUI 11 it does not work.

Reboot to recovery

- Flash the latest 9.8.1 vendor image or full stock ROM.

- Reboot to twrp and format data

- Wipe cache/dalvik

- Reboot back to recovery and flash

I tested using the newest Xiaomi.EU Vendor for Android 10 and the stock one with no luck....more thoughts?
[Xiaomi Mi 9 Questions & Answers] antonio521:
Did you try turning off the VoLTE?
[One (M8) Q&A, Help & Troubleshooting] saiyansection:
My HTC one m8(16gb) emmc was replaced by 64gb..

But problem is that, after formatting.. My device only uses 16gb and the remaining partition is shown unallocated..

What would be the issue?
[General Topics] infernalshade:
Hi Guys...look at my Problem:

http://www.youtube.com/watch?v=6iOBZOdRgQM

Everytime i open the StartMenu, the 4 Items are doubled!

How can i fix this?!

greetz

infernalshade
[P8lite Q&A, Help & Troubleshooting] TechnicGeek:
Hello,

I have Huawei P8 Lite and I want to use general mobile charger for it.

I want to know if it is okay to use it with Huawei P8 Lite:

Here what original charger looks like:

Is voltage and amperage okay on general charger to use with my phone?

Thanks.
[P8lite Q&A, Help & Troubleshooting] zkoz:
Yes, you can use this, but output have to be 5V not 9V.
[P8lite Q&A, Help & Troubleshooting] Tim44t:
Yes it is ok 5v is the important thing. You get no problem with it
[Huawei Mate 9 Questions & Answers] daina:
So...

Just ran the following commands:

C:\beta-flashy_0.2>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.009s]
finished. total time: 0.011s

C:\beta-flashy_0.2>fastboot oem get-build-number
...
(bootloader) :MHA-L29 9.0.1.191(C432E7)
OKAY [ 0.010s]
finished. total time: 0.011s

C:\beta-flashy_0.2>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29 8.0.0.376(C567)
OKAY [ 0.010s]
finished. total time: 0.011s

C:\beta-flashy_0.2>fastboot getvar vendorcountry
vendorcountry: hw/usa
finished. total time: 0.008s

My device seems to be halfway stuck between PIE and OREO. I can only enter fastboot, and as you can see, my device responds to fastboot commands. As far as I can tell, I can even flash whatever I want. Bootloader seems to be unlocked (Red text, "PHONE Unlocked," and "FRP Unlock."

What happened...

I upgraded from Oreo (.376 build) to Pie (9.0.1.191 build) using the method outlined here. Success! Got greedy, decided to install Resurrection Remix OpenKirin Pie build. No problem. Didn't like the camera, tried to flash back to stock. Bootloop. Whoops. Flash RR again? Nope, that didn't work either. I *was* able, however, to successfully flash and boot OpenKirin's Omnirom Pie. I really should have left well enough alone at that point. But no, I thought, maybe I can get back to stock from here. Tried to flash SYSTEM.img from stock firmware, aaaand... bootloop. Re-flashing Omnirom doesn't work, either. Have been stuck like this since Friday morning.

Again, I have Fastboot, and it's unlocked.

I've tried the DLOAD method twice over the weekend, and once more this morning. It almost immediately says "Software install failed" every time.

I am out of ideas. Based on the fastboot responses above, does anybody have any ideas?
[Huawei Mate 9 Questions & Answers] daina:
Have been able to flash TWRP (Pie). Am trying to see if I can flash a custom ROM from here. Have my doubts.
[Huawei Mate 9 Questions & Answers] daina:
Results from DC-Unlocker:

DC Phoenix 0.0.0.118
user:daina

Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: 5RE0217927000170

Detecting recovery partition
File size: 5,476,648,324 bytes
Current version(CURVER): MHA_Global-CUST 9.0.1(C999)
ERECOVERY_KERNEL partition found
ERECOVERY_RAMDISK partition found
ERECOVERY_VENDOR partition found

11/18/2019 4:26:30 PM Starting to try Rescue Recovery...

Looking for a device in fastboot mode
Device found: 5RE0217927000170

Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

Build number: :MHA-L29 9.0.1.191(C432E7)
Model: MHA-L29
Vendor/Country: Vendor/Country: hw/usa
Battery state: 6812mv
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked

Process identifier:20538296

Getting build number...
Getting base version...
Getting cust version...
Getting preload version...

Erasing ver .. .
File size: 5,476,648,324 bytes
Current version(CURVER): MHA_Global-CUST 9.0.1(C999)
Writing rescue_recovery_kernel partition
RESCUE_RECOVERY_KERNEL partition update :FAIL image verification error

Cannot enter in Recovey mode
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] oriped:
Hey guys

I'm coming from a OnePlus One, Lineage OS 16.0. Rooted with latest Magisk.

Over the years I've encountered several apps that wont work on a modified system - now I want to start new with the Mi9T Pro and set it up in the right way.

To start with: Will a bootloader unlock alone be detected by anything? I'm not sure what ROM to use in the end, but this is always the first step.

And since Magisk can't hide everything (e.g. health insurance apps are really strict and clever), is it possible to have two systems parallel (like dual-boot)? One "unmodified" system for all the security-concerned apps.

Or are there any other solutions for this?

Thanks!
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Windroid-user:
OP status for the first time:cool:

I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?

I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?

Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.

Thanks, I appreciate it.

EDIT: Nevermind I think I did it.

System/System app settings

Then disable "Show update notifications"

EDIT 2: It did not work:laugh:
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] phtablet:
- With root I used this solution:

Edit the file: system/build.prop

copy / paste the line that contains the version number.

Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM

I have put a "#" for memo and changed v10 to v14 :

# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM

- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
[Samsung Galaxy J3 (2017) Questions & Answers] Flowchan:
Hi y'all, I have a Galaxy J3 2017 and I don't have a Windows PC and I only have a Mac. I am trying to flash twrp via JOdin3 and I installed the latest Heimdall tools too and I can't install it... It keeps saying in the logs that "/usr/bin/HEIMDALL ERROR: "-PIT" is not a valid argument however I can't flash it without a pit file...
[JASJAR, XDA Exec, MDA Pro General] djgaby:
hey guys im having this problem since i got my universal 2 years ago i tried all the roms available in the world and nothing worked, the problem is that if someone made me a fast misscall the phone will freeze, whats the problem? my battery is brand new
[Google Pixel 4 XL Questions & Answers] LLStarks:
Do any of the kernels properly support NSG's unreasonable requirements?

Haven't been able to get it working on any Pixel phone for months. What changed?

Edit: Dev says it's not supported yet.
[Google Pixel 4 XL Questions & Answers] troyhough:
Would love to get this working on a 4 XL.
[Google Pixel 4 XL Questions & Answers] cstark27:
I had it working on Pixel 2, 3 XL, and 3a XL. I am told the Pixel 4 is missing (or their methods can't see) the MPSS, modem peripheral sub system. I don't know how to enable this.

Also missing is diag mode and the older methods from the Pixel 2 don't work on the Pixel 4 because the modified Magisk doesn't patch the boot image correctly.

It would be nice to see if a userdebug/eng rom worked a little better.

Things I have tried: copy all diag libs from Pixel 3 XL; remove most selinux denials when opening NSG; spoofing as Pixel 3 XL and OnePlus 7 Pro.
[Google Pixel 4 XL Questions & Answers] cstark27:
Updated instructions for Android 11

Old instructions:

Here are instructions to get NSG working. You need to download the newest and re-apply the "userdebug" vendor.img every month. These instructions are given with the assumption you know that this app requires root, an unlocked bootloader, and that you know how to recover your device in case of flashing failures by using the factory images.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

1. Download the appropriate Vendor image from https://developers.google.com/android/drivers

To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab. Make sure your correct device variant is chosen.

2. Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)

3. Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools

4. If already rooted with stable Magisk, open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF. (Canary builds may not work.)

If OFF, skip to #13.

If ON, then uncheck Preserve AVB 2.0/dm-verity then press Install>Direct Install, reboot. Skip to #13.

5. If you are already rooted with Canary builds, or are having bootloop issues, remove -w flag from factory image bat/sh then re-flash factory image

6. Boot into OS, install latest stable Magisk APK

7. Open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF

8. Patch stock boot.img

9. adb reboot-bootloader

10. fastboot flash boot <magisk_patched.img>

11. Reboot

12. Open Magisk Manager, make sure dm-verity option is still off

13. Reboot to fastboot (adb reboot-fastboot) - you should see "fastbootd" in red at the top

14. Flash the vendor.img you extracted (fastboot flash vendor location/of/vendor.img)

15. When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again

16. If you cannot boot or get a corrupted boot message, start over at #5

If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app a couple times as needed, or clear app data as a last resort.

If you encounter an issue where LTE Band 71 does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then turn on Enable DSDS then reboot.

As of April 2020 patch or Android 11 DP3, you might be able to see your device in QPST with these commands:

adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst
[Google Pixel 4 XL Questions & Answers] troyhough:
---------

ohhhhhhhhh is the screenshot on the Pixel 4?
[Google Pixel 4 XL Questions & Answers] cstark27:
Yep, 4 XL :)

It seems on each reboot you will need to clear the app data, just FYI. And on successive launches of NSG, you will see some missing fields for 5-10 secs but if you start moving some data it should populate.
[Google Pixel 4 XL Questions & Answers] troyhough:
Sweet! My phone isn't rooted so hopefully you can tell me what the P4 XL is actually capable of! Is it capable of this:

FDD-TDD DL CA utilizing a 10 MHz B25 carrier as PCC for DL /UL with 20 MHz B41 aggregated on the downlink
[Google Pixel 4 XL Questions & Answers] cstark27:
Sorry I don't have any active Sprint sims.

But per the FCC filing, it should be able to.

PCC [B25 (20mhz)] + SCC [B41 (20mhz) + B41 (20mhz) + B41 (20mhz)]. It supports ULCA on B41. And it supports 4x4 MIMO on bands 2,4,66,25,30,41. But while CA with B41, you only get 4x4 on B25 not any B41. To get 4x4 MIMO on B41, it has to be CA of only B41.

Let me know if my interpretation of your question is wrong.
[Google Pixel 4 XL Questions & Answers] troyhough:
Im not into the technical verbiage, just would like to know if the 4 XL is capable of doing what the S9, S10, Note 10, etc can do on Sprint!

You can see below what the S9 is doing. You may have to read a little bit more of the thread to get all the info:

https://s4gru.com/forums/topic/6319...cussion-thread/?do=findComment&comment=549028
[Google Pixel 4 XL Questions & Answers] ryaniskira:
EDIT2: I got it working, but it seems to have an issue when DSDS is active, it jumps back and forth between the data from each SIM card.

Here is a screen recording of what I am talking about:

https://filebin.net/ddim8468plxx6otp/2020_01_07_22_10_35.mp4?t=82gimnzv
[Google Pixel 4 XL Questions & Answers] cstark27:
Technically, it can support such combos. But again, I can't confirm that it does it out of the box since I don't have an active Sprint sim.

You might reach out to the developers and see if they can help you out. I only use a single sim.
[Google Pixel 4 XL Questions & Answers] ryaniskira:
It was actually the devs who told me about this thread in an email. I did reply back to them with the issue though.
[Google Pixel 4 XL Questions & Answers] bigJbig:
[/COLOR]

I followed your steps, I got "failed (remote: command not available on locked devices)" after I entered "fastboot flash vendor vendor.img"
[Google Pixel 4 XL Questions & Answers] cstark27:
You need an unlocked bootloader. That step is assumed since this app requires root :)
[Google Pixel 4 XL Questions & Answers] bigJbig:
Thank you for your quick reply. I was on the customs kernel, then I went back to stock and all work!
[Google Pixel 4 XL Questions & Answers] loonix:
Used SE Linux switcher to set Permissive and flashed clean vendor image. NSG still doesn't seem to work for me "coral"/4 XL. I have tried clearing app data of course.
[Google Pixel 4 XL Questions & Answers] cstark27:
You won't need permissive so don't worry about that. Also make sure you're flashing the vendor image that is downloaded from the specific Driver Binaries page. These are built as "userdebug" images, which has less functionality stripped out compared to "user" images that are in the completely factory image download. If you're sure you've done that, reboot, open NSG, menu button>exit, reopen and repeat as necessary. If it still doesn't work after like 5 attempts, then check a couple props. The first one we can check is 'getprop ro.vendor.build.type' (run with su).
[Google Pixel 4 XL Questions & Answers] loonix:
Pretty sure I got the vendor image right. I am on January patch and the correct one for Google Fi is "Pixel 4 XL binaries for Android 10.0.0 (QQ1B.200105.004)". Unfortunately it still didn't work after trying the reopen 5/6 times workaround.

coral:/ # getprop ro.vendor.build.type
user
coral:/ #
[Google Pixel 4 XL Questions & Answers] cstark27:
Looks like it didn't flash correctly or you may have accidentally grabbed the wrong img file. Maybe download it again and rename it right away to "vendordebug" for example. The returned value should be "userdebug".
[Google Pixel 4 XL Questions & Answers] loonix:
I am doing all of this in macOS. The idea is same , extract google_devices-coral-qq1b.200105.004-b60dcbca.tgz to get vendor.img but oddly enough the timestamp shows vendor.img to be Jan 1, 2008 , 2 AM and weighs 710.2 MB, and that looks odd.

In macOS, it is the sh scripts when executed extracts all files in all folders recursively.

/Users/x/Applications/coral/coral-qq1b.200105.004/vendor/google_devices/coral/proprietary
MacBook-Pro:proprietary $ ls -lrt
total 1409680
-rw-r----- 1 x staff 710222032 Jan 1 2008 vendor.img
-rw-r----- 1 x staff 768 Dec 18 00:23 device-vendor.mk
-rw-r----- 1 x staff 815 Dec 18 00:23 BoardConfigVendor.mk
MacBook-Pro:proprietary $
[Google Pixel 4 XL Questions & Answers] cstark27:
The reported date is normal (same here). For the extracted image of that build (I used the same), I have a SHA-256 hash of: 32F5FA4EA6200DEE0D12F2848F63FE4A76B2963FD10586A3EB1065781678C638

What kind of output are you getting when you flash the image?
[Google Pixel 4 XL Questions & Answers] loonix:
Yes that matches what I have, thank you for confirming.

MacBook-Pro:proprietary $ shasum -a 256 vendor.img
32f5fa4ea6200dee0d12f2848f63fe4a76b2963fd10586a3eb1065781678c638 vendor.img
MacBook-Pro:proprietary $

It seems that these binaries from google are not built with userdebug but I am able to find several guides online that show how to compile the vendor images with userdebug flag. I haven't attempted yet, but I don't think a build.prop change will work. I attempted the following but it doesn't work (kinda expected) and wouldn't be sufficient enough I am guessing to make other changes necessary for a debug environment for the OS.

coral:/ # setprop ro.vendor.build.type userdebug
setprop: failed to set property 'ro.vendor.build.type' to 'userdebug'
coral:/ #

For the flashing, in fastbootd, I just issued fastboot flash vendor vendor.img and it was successful to "vendor_a". After reboot when I checked that the build type is still user, I did a fastboot flash -all vendor vendor.img, which was also successful (and to both vendor_a and vendor_b) but this resulted in a brick. I had to flash the factory images again (preserving data) and rerooted with magisk. I don't see how just flashing this downloaded vendor.img got you into userdebug. There seem to be guides floating around showing how to compile a debug version of the vendor image from sources.

I should add that in the past, a permissive SELinux is all NSG needed to get going. Something is broken with Android Q/Coral and I hope it is being looked at. I wanted to do some manual band and CA bond testing as I have moved to a new area.