yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Pro Questions & Answers] dlads:
Not sure I can believe that tbh, QHD just kills the battery
[OnePlus 8 Pro Questions & Answers] Bruno41:
https://xdaforums.com/t/drain-oneplus-8-pro.4395691/
[General Questions and Answers] Masinissa:
Hello World

first let me stste, that I've bern a Linux/Unix admin for many years, so I know how to check a filesystem. ;-)

I am rumning a Samsung Tablet on LineageOS 7.1.2 and decided to format the external (physical) SDXC card to ext4. Once I did that the system booted normally and recognized the card just fine. But the Android System now pops up a notifaction at every start, complaining about a "Corrupted SD Card". Since that card's FS looks picture perfect (with the card itself being brand new), I just know this complaint is about me deviating from the holy grail of FAT32/exFAT.

I tried to suppress the error msg. via Xposed, but in vain. It just bothers me, that it comes up whenever I switch on the device. So how do I get rid of this false error message at boot time?
[General Questions and Answers] blackhawk:
Reformat using the device. If that doesn't take do a low level format/wipe then have the device format it.

If the card had data from another device on it that can cause file corruption. Seen it with Canon Cams. You can scramble a whole card and all it's images like that. While you can recover the images, all the metadata is juxtaposed rendering them next to useless.

If the low level format doesn't solve the issue there's a problem with the card, either specs or it's defective. I generally use Lexar cards when possible. Their low level formatting apk is excellent. Never had an issue with this brand.
[General Questions and Answers] Masinissa:
Did you even bother to read my original post? Judging from the canned nature of your "reply" I guess not.
[General Questions and Answers] blackhawk:
Yeah I did. It's an issue with the card unless you goofed up something in the phone's OS.

This isn't rocket science.
[General Questions and Answers] Masinissa:
Jeezus H. Christ - as I wrote the card is *brand new* and I tripple checked it on a PC. Even Android itself reports it as OK (when checked from terminal) - and I wrote, too, that I know how to verify a filesystem.

And I wrote right at the top, that this is a TABLET (not a phone).

And wtf good would reformatting the partition to FAT32 do, if I wrote that I specifically wanted it to be ext4?!

How clueless can one be??

You Mr.and a rocket engineer? You couldn't even qualify as a plumber. :O
[General Questions and Answers] blackhawk:
Used what to check on the PC?

All my sd cards work sweetie...
[General Questions and Answers] Masinissa:
Then go play with your cards and don't bother people who want get a *qualified* response from someone who knows how to check the consistency of an SD card partition.

Use your "sweetie" cards as sugar coating, but don't pretend for one second to know the inner workings of Android's storage management. You couldn't distinguish a FUSE mount from a firehose, for all the vold daemons in the world.
[General Questions and Answers] blackhawk:
I'm sure somebody here is more qualified than you🤣

For the next chump that replies you should specify what apk lead you to your dead end.

Maybe that's where your trouble lies... among other issues... including your unuseble card.
[General Questions and Answers] Masinissa:
OMG, he knows how to add three letters together and throws that in here to make it seem like he got some knowledge of something.

I wrote that the Android System complaimts about a corrupt SD card and I also stated that its a false error message triggered by the card being fornatted to ext4. So what in heaven's name should any Android Application Package (which is what APK stands for) have to do with that?

Please do what I want that error message to do: Just go away!
[General Questions and Answers] mrjuniork:
MOD INFO:

Please keep it civil and DO NOT throw insults or anything similar!

This is a development forum and not some place to blow off some steam.

Thx for your understanding.

@Masinissa

Please read the forum rules as you have clearly overstepped.

Now get back on topic 👍

Cheers,

mrjuniork (Forum Moderator)
[General Questions and Answers] Masinissa:
I had asked a *clear* question and I got nothing but BS from a member who wouldn't take NO for an answer.

I didn't overstep A THING - I just told a know-nothing - who wouldn't give it a rest - that he knows nothing.

A "development forum", where you get haunted to no end by someone who doesn't know the difference between an APK an a filesystem, is next to useless. :-(

I for one will not bother posting anymore in here anyway. I am a busy IT expert and don't have the time in life to waste my hours with trolls like that.

Jeez Louis, XDA used to be a platform by experts for experts. You've changed a lot more, than just its optical appearance.

PS: I am writing up the answer to my own question here, just to show that - sadly enough - extensive Google research nowadays is more productive, than seeking professional answers by posting on XDA.

https://review.lineageos.org/c/LineageOS/android_system_vold/+/225436

As vold handles all mounting of partitions on SD cards, the 7.x version of LineageOS requires a patched version of said daemon, to support boot mounting of ext4 partitions on external SD cards.

Unfortunately the OS doesn't accept mount instructions via vold.fstab either. So flashing a new ROM it must be.

PS#2: After some days of heavy use I can confirm that the ext4 partition is accessible w/o problems, so swiping away that faulty error message after boot is a small inconvenience (but I'll still upgrade my ROM).

To anyone else trying to format their external SD to something other than MS-FAT under an uncooperative vold daemon:

If you're root'ed, you can bind mount /storage/<UUID> (whereas <UUID> stands for the unique identifier - an insanly long number-letter-string - identifying the ext partition) to /storage/emulated/0/external_sd. That will make the card and its files accessible for most Android apps.

Do *not* bind mount from anywhere else (like /mnt/media_rw), lest you'll be forced to adjust permissions manually on FS level.

The "/storage/…" path is a virtual filesystem, via which Android enforces world access to the files on the card (while still allowing for some secure areas in reserved directories). Mount from anywhere else, and you're on your own permission wise.
[Android Head-Units] EDwardlefterica:
Hello everyone, I really need your help! I need unmodified software for stm32. after 5 installation attempts I still failed. My sound doesn't work and neither does my camera. My navigation model:

https://www.aliexpress.com/item/328...earchweb0_0,searchweb201602_,searchweb201603_
[Android Head-Units] EDwardlefterica:
somebody ?
[Android Head-Units] MrSchlumpf:
you have to enter the factory settings. Tap "kernel version" and "OS version" alternate for that. There you can activate/deactivate diffrent functions.
[Android Head-Units] marchnz:
Reported - not Android Auto. Requested Moderator move to (Android head-units) forum.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
Hiya. So, here's the story:

Xiaomi Mi 9T Pro EEA, bought from Amazon, not a shady reseller

I made a Google Backup of my apps, because I decided to try out some Android 11 roms.

After trying them out, I wanted to go back to Android 10, so I clean flashed my rom, GApps and disable force encrypt, the usual stuff. But the Google Backup, that I previously used on all the A11 roms was suddenly gone.

I thought, that wouldn't be a problem, since I still had my Android 10 TWRP Backup that I made, before I started experimenting with A11.

I restored that backup and couldn't unlock my phone. So I deleted /data/system/locksettings.db and finally my phone would unlock.

But: My sensors didn't work anymore. I searched the internet for info and found out, that my persist partition got corrupted.

tl; dr: I restored a TWRP backup and my Persist partition corrupted.

Until yesterday, I didn't even know, what the Persist partition was. I never touched it.

I know how to get my sensors working again. But I guess my Widevine L1 is gone now, isn't it?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] mauam:
Yes, it's gone. Share what you did to get the sensors working.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
Unfortunate. Oh well.

There's actually multiple ways. You could:

Flash persist from Xiaomi's full fastboot package

Flash persistbak to persist

Flash a working persist image from another Mi 9T Pro

All those things worked for me. In the end, I settled with the persistbak method.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
could you tell me how you flashed and dumped persistbak?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
It's almost been a year, so I don't fully remember what I did exactly, but there's some tutorials around you can find pretty easily.

The only thing I remember is going into fastboot and dumping and flashing my partitions via command line, I think.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
ive been searching for a month and im still not sure which tutorial to follow, all i want is to fix my sensors and get widevine l1 back in case it gets void when i flash persist, any help would be phenomenal!
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
Well if you didn't make a backup before, L1 is L Gone. I didn't get it back. Following any tutorial should get you your sensors back though.

And remember: The first thing to do when getting a new phone is to backup that persist partition, so you don't need to worry about something like this happening again.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
Oh, interesting. Definitely gotta try that, thanks. How do you download the certificate in MIUI? Does it happen automatically?

Since I flashed my persistbak, I didn't flash anything else and my sensors are still working, so I guess it sporadically happens... sometimes?

Btw, if you aren't already, you should use OrangeFox recovery instead of TWRP on Xiaomi devices. It usually doesn't kill itself by wiping partitions or flashing roms, especially when coming from MIUI. Also, you can make persist backups with it. For some reason they removed that feature from TWRP.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
in case you got it wrong xiaomi.eu is a custom miui based rom, not official, just to clarify that, and to download the certificate you must enroll fingerprint then go to fingerprint payments and youll find widevine l1 there, then click on certificate in widevine l1, pretty easy stuff, also how do i install orangefox?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Seki_:
Oh, I can't read. For some reason, I thought you said xiaomi.eu or stock, that's why I said MIUI. Anyway, thanks for telling me. I never heard of that.

To install OrangeFox, just download the zip, make backups if you want to be extra sure and flash the zip. Here's the thread: https://xdaforums.com/t/recovery-official-orangefox-recovery-project-r11-1.4308019/

The UI is different, so it took me a little while to get used to it, but ultimately, OrangeFox is a smoother experience than TWRP, at least on Xiaomi.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] zgfg:
No, you cannot get L1 through Magisk module - because you need a (paid) certificate for your hardware

To the contrary, there is a Magisk module that disables L1, dropping you to default L3.

Although I never understood who/why needs that
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] zgfg:
See here how to backup and/or dump Persist and restore/flash it back.

Of course, if you didn't backup a working Persist on time, you have nothing to restore:

https://xdaforums.com/t/extracting-stock-boot-recovery-and-persist-images.4058447/
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
its alright lol, thanks for your help btw have a nice day/night
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
that sucks man, thanks for the news anyway i might use xiaomi.eu rom to get it back that way at least
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] wavychris:
alright thanks i might try it out tommorow ill update you on the process if you want
[P3400 ROM Development] chigz:
people we can have the samsung omnia widgets on our Gene

just refer to this thread for all samsung related stuffs...

all appreciation for the original poster..i m just referencing the thread

here u all go..

http://xdaforums.com/showthread.php?t=418143&highlight=Omnia
[LG V40 Questions & Answers] sharpienation:
Having trouble installing TWRP.

I can fastboot and attempt:

`fastboot boot TWRP.img`

But it either fails or "succeeds" and then just hangs on the LG Logo.

`fastboot flash recovery TWRP.img`

-returns an error that recovery_a doesn't exist.

`fastboot flash abl_a TWRP.img`

-returns "Volume is Full"

Any ideas what I may be doing wrong?

Device is an ATT LG V40 with the V35 Engineering Bootloader if that helps.
[LG V40 Questions & Answers] AsItLies:
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?

Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.

The only thing about using fastboot is you want to save the original boot_a image first. At&t doesn't make their kdz available and if u want /need to go back to stock u need to save it first.

After flashing it (either way), you need to immediately go to recovery, don't boot the device, u have to format data and reboot to recovery and then flash magisk and no verity zip. Otherwise a backup of your data won't work as it will be encrypted.

just one point, don't every flash something to a partition when yer not sure what yer doing. The abl partition is only about 1 meg in size, it's the 'android boot loader'. You could, if unlucky, flash something wrong for that partition and end up overwriting the partitions that are next to it, and essentially (just about) brick the device.

cheers
[LG V40 Questions & Answers] sharpienation:
Sorry! It's Pie.

This gives me the following:

Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')

I receive a similar message for `abl_b`, `recovery`, and `boot_a`

If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
[LG V40 Questions & Answers] AsItLies:
Wow, so I don't think you understood some things. First, stop trying to flash an image to the wrong partition then what it's for. It is NOT for abl_a, and it is NOT for recovery (there is no recovery partition on a treble phone). STOP DOING THAT.

and second, because that boot_a (ONLY!!!) partition is for Q, as I said, you need one for Pie, and shouldn't even be trying to use it anyway.

and third, you can't fastboot boot these boot/twrp images, they have to be flashed to the partition and then you have to boot to recovery immediately after (don't try to boot the phone).

So if you can't flash the image with fastboot then the only option would be to use qfil, again, be sure to back up the original image first.

I'll look around and see if I can find one for Pie. We may have to create one if it's not around.

cheers
[LG V40 Questions & Answers] AsItLies:
Just checking, but u do know how to use qfil yes? And, how did u get fastboot on the device? Using qfil I'm guessing? and you deleted laf_a? or the engineering abl?

This info is important because 1) the fastboot you get when simply erasing the laf_a is not as powerful and full featured as the engineering abl. The actual capabilities of the (laf_a erased) fastboot varies by OS variant, but some of them are basically worthless.

2) you'll have to be able to use qfil to get this accomplished.

let me know and we'll go from there.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mattie_49:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KennyG9:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mattie_49:
Fair enough. Thank you for bringing this to the op8 community.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KennyG9:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mobile_sensei:
"Flash OOS 11 at some point"

What about upgrading from 17.1 ?

Also - Why no OOS 10 - 18.1?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KennyG9:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.

I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :

- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300

- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py

- reboot to bootloader (adb reboot bootloader)

- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)

- reboot into stock fastboot (fastboot reboot fastboot)

- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)

- follow LOS 18.1 flashing instructions from the first post
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] SUPERUSER:
Yes I agree here.

I and need step by step exact instructions how to flash any rom here.

I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.

I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.

The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool

https://xdaforums.com/t/op8-oos-21aa-ba-da-unbrick-tool-to-restore-your-device-to-oxygenos.4085877/

My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES

IN2010

Inspected 2020.06.18

As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.

Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.

It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.

Driver used

Developer framework ie fastboot, adb executable

Payload dumper

Readme File

Bat/sh file for automation

perhaps payload/img files

bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting

This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..

Spoiler content hidden.

Good information, I didn't finish my reply during breakfast and noticed you wrote one more.

The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.

Its one factor subject to being sourced from random google searches.

Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.

But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.

Is fastboot/adb bundle too old or driver not installed?

Did all of us follow the exact same installation steps in detail the rom developer did?

I hope you understand.

This device has been the most problematic I've ever dealt with
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KennyG9:
I don't have a definitive answer to everything, but here are some remarks:

- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.

- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).

- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.

- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is :) .
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] veridiam:
working great so far. any way to re-enable the 90Hz refresh rate?

edit: found it in display options!