yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 Questions and Answers] wide17z:
Hello everyone,

Good day for you all

I have Galaxy S8 SM-G950FD it run on a stock ROM and I love this phone, yesterday I was using WhatsApp until a company sent me a message asking when is the best time for me to attend their job interview.

Suddenly the screen phone broke, it went restart and boot looping, and on one occasion it will just be stuck on the "Samsung Galaxy S8 logo" until it restarts by itself.

Here's what I already did.​

1. I tried to get into recovery however it won't.​

2. I tried to force restart it by pressing Volume Down + Power Button.​

3. I already tried to drain the battery so I can enter the recovery and it also didn't work.​

4. At one time I succeeded to went into recovery, immediately wipe cache/partition and restart the phone. It passed the boot logo however it was stuck on the glowing "SAMSUNG" logo. I waited for it like 30 minutes with the charger connected.​

5. This morning I went to Samsung Service Centre they concluded that the problem was with the hardware internal memory and it has to be replaced along with the board and it will cost me around USD 275. And the data couldn't be saved.​

6. I'm planning to flash stock firmware with the youtube guide below by selecting HOME_CSC to avoid wiping any data however, I'm afraid it will erase completely my internal memory (please advise?).​

I'm trying to fix my phone but without wiping the data especially WhatsApp so I can continue my application, I have a very important job interview so I can have my first job. Since last year no company was willing to recruit a recent graduate and I don't want to miss this chance. I know this is stupid but the company was asking me to the point without giving me detail of which company was it, it's also my fault because I applied to so many companies, people here are just not used to email.

Foremost, I have some memories and media on my phone which are very important to me. My stupidity for not backing those up to the cloud is also because we don't have a decent internet connection.

I do really looking forward to your kind assistance, I appreciate any suggestions.

Thank you so much in advance.​
[Samsung Galaxy S8 Questions and Answers] It_ler:
Flashing stock firmware files with Home_CSC will not work your data.

But if it's really the internal storage ... hardware defect as suspected by Samsung support, then it might not work.

Good luck for rescuing your device, your data and to get the job.
[Android Q&A, Help & Troubleshooting] multimill:
Hello,

I am looking for an alternative to AutoShare.

My goal is to click the share button in any app (for example gallery) and click one icon/app to send that file via e-mail to a preconfigured mail adress with preconfigure subject. AutoShare seems to be the only app to do that but haven't been updated since 2014 and does not seem to work for me anymore. Do you know any alternatives?

Thanks in advance!
[Android Q&A, Help & Troubleshooting] meiser:
I'm using AutoShare and MailTask.

Here's my Tasker description:

Profile: E-Mail Privat (6)
Event: AutoShare [ Configuration:Command: E-Mail Privat
Sender: all
Subject: all
Text: all
File: all ]
Enter: E-Mail Privat (12)
A1: If [ %astext !Set ]
A2: Variable Set [ Name:%astext To:%asfile() Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:0 Structure Output:Off ]
A3: End If
A4: For [ Variable:%asfileitem Items:%asfile() ]
A5: Variable Section [ Name:%asfileitem From:21 Length:100 Adapt To Fit:On Store Result In:%asfileitem ]
A6: Variable Set [ Name:%asfileitem To::%asfileitem Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 Structure Output:Off ]
A7: Java Function [ Return:%asfileitem Class Or Object:Uri Function:encode
{String} (String, String) Param:%asfileitem Param: Param: Param: Param: Param: Param: ]
A8: Variable Set [ Name:%asfileitem To:content://com.android.externalstorage.documents/document/primary%asfileitem Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 Structure Output:Off ]
A9: Array Push [ Variable Array:%asfilenew Position:999999 Value:%asfileitem Fill Spaces:Off ]
A10: End For
A11: Send email [ Configuration:Send email from meiser <meiser@blahblah.com> Timeout (Seconds):0 Structure Output:Off ]

Only precondition: the file has to be in your internal storage.
[Android Q&A, Help & Troubleshooting] MultiKoopa:
So for the last year and a half or so, the Roku Android and iPhone apps just completely crash with "Operation Error" whenever you try to change Expert Picture Settings on them. Which makes HDR significantly worse on them, especially the 2017 models which need some serious calibration to look decent.

Roku keeps updating the TV software and the Android app, and the problem persists. They even have the gall to just close any topics made about this issue on their forums as "Resolved" any time they're made.

I'm guessing this is being done deliberately. Would anybody be capable of creating a custom version of the Android app that will let you use Expert Picture Settings?

Unfortunately, none of the older apps work. Any of them that don't immediately crash when opening Expert Picture Settings don't actually work with the newest TV OS updates.

No idea if this is the right place to post something like this. But since Roku is clearly not going to fix the problem...

EDIT: According to this Reddit thread

https://www.reddit.com/r/Roku/comments/jwg3rj

the problem appears to be the Android version. Android 11 devices will auto-crash. Older devices running Android 9 work fine.

I do not have a working Android 10 device so I can't test that out.

EDIT #2: Managed to raise my Pixel 1 XL from the dead. Android 10.... auto-crash.

Unlocked the Bootloader and flashed Android 9 to it. It works with even the newest Roku app! unbelievable that this would be the problem. Is it possible to fix this for newer Android versions, maybe?
[Android Q&A, Help & Troubleshooting] gyandoo:
Does anyone know if the official Roku Remote app works fine with an Official LineageOS ROM without Gapps, especially private listening

Thanks
[Android Q&A, Help & Troubleshooting] bulletbling:
Roku app version 6.0.7.241364-84 works for advanced picture settings and doesn't give the unavoidable "Roku app needs an update" message.

Roku v6.0.7.241364 APK Download

Download Roku v6.0.7.241364 APK - Roku is the official Android app that connects users to their Roku devices, no matter the generation or version.

mobile.softpedia.com

The Roku App (Official) v6.0.7.241364 (nodpi) (Android 4.4+) APK Download by Roku, Inc. & its affiliates - APKMirror

The Roku App (Official) v6.0.7.241364 (nodpi) (Android 4.4+) APK Download by Roku, Inc. & its affiliates - APKMirror Free and safe Android APK downloads

www.apkmirror.com

If the links above no longer work, I'd guess you can use any 6.0.7 version prior to the above ones.
[Android Q&A, Help & Troubleshooting] MultiKoopa:
I'll try this out on my Roku TV. I'd given up on this completely after several years, honestly. Will update after I try
[Android Q&A, Help & Troubleshooting] bulletbling:
I literally just calibrated one of the Roku TVs in my basement. I also checked and there are a few versions after this one that let you access advanced picture settings and these versions also don't prompt you to update. I skipped ahead to 6.0.15 and that does prompt for an update so definitely not that version or beyond.

Anyways, I found the advanced picture settings page may have a never ending loading icon when you click on it with Android 12 (at least on my OnePlus 9 Pro). I dug out my old Nexus 7 and it worked perfectly. Also, I had used this on Android/OxygenOS 11 many months ago on my OP9Pro and it worked with no problems, other than the app sometimes wanting to freeze, but you can still get your calibrations in.
[Android Q&A, Help & Troubleshooting] MultiKoopa:
ah yeah so I have Pixels. I didn't have an unlocked bootloader on my main phone, but I happened to have my old Pixel 1 XL laying around. the battery LITERALLY died in under 5 minutes when fully charged, so it was worthless, but I kept it plugged in and figured I might as well try it out with this since some people with older devices said older versions of the app still worked for them.

On a whim, I tried installing older Android versions, and eventually it worked! The older Roku apps only worked if I had Android 9 on it. Android 8 didn't work with versions of the app that still worked with my model of TV, and Android 10 had the same "Operation Error" issue.

I'll give the APK you linked to a shot, but I have my doubts it'll work on my Pixel 4a 5G with Android 12, and I'm definitely not gonna downgrade the OS on my main phone just to get this one app working for advanced picture settings lol
[Android Q&A, Help & Troubleshooting] bulletbling:
Why don't you just use the old Pixel 1 and keep it plugged in while tuning the TV?

And the version I linked is confirmed by me to work on Android 11 (well, at least on OxygenOS). I have no clue if it'll work on your Pixel 4a 5g, but it had an indefinite loading animation on the advanced picture page on OOS 12.
[Android Q&A, Help & Troubleshooting] MultiKoopa:
No, yeah, I can do that. I'm just worried the phone will literally stop functioning at some point. I'm not exaggerating when I say the battery lasts less than 5 minutes on a full 100% charge. And any repair shop charges like $200 to replace the battery.

So I'm hopeful that I can just.... use my main phone, y'know?
[Android Q&A, Help & Troubleshooting] bulletbling:
Yeah. And I can understand the concern. If it does get unplugged in the middle of calibration, I will say that everything you entered into the TV so far is already in there...you don't have to save anything.

Lmk if it works on the pixel with Android 12. That would be even better!
[OnePlus 8T Guides, News, & Discussion] coloneyescolon:
Is root with magisk possibe with an locked bootloader? Would that require signing the magisk

-patched boot.img or packing magisk into the boot.img at build time?
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
You would have to include magisk in the build process, if you tried to "patch" the boot image after signing it would fail to boot as it would no longer have the right hash and you'd get the "currupt OS" message.
[OnePlus 8T Guides, News, & Discussion] coloneyescolon:
Is it possible signing the boot image after patching it with magisk?
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Hello,

I followed the exact steps, and The build failed for OnePlus 7 Pro (guacamole), with this error:

error: device/oneplus/sm8150-common/fod/Android.bp:16:1: "vendor.lineage.biometrics.fingerprint.inscreen@1.0-service.oneplus_msmnile" depends on undefined module "//device/oneplus/

common:vendor.oneplus.fingerprint.extension@1.0"

error: device/oneplus/sm8150-common/fod/Android.bp:16:1: "vendor.lineage.biometrics.fingerprint.inscreen@1.0-service.oneplus_msmnile" depends on undefined module "//device/oneplus/

common:vendor.oneplus.hardware.display@1.0"

16:07:07 soong bootstrap failed with: exit status 1

#### failed to build some targets (10 seconds) ####
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
That looks like you're missing some of the proprietery blobs, did you verify LineageOS comipled successfully before making any changes? Did you use the extract files script or use the muppets repo?
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Hello,

I did extract the proprietary blobs from payload-based.

Do you mean I should compile LinageOS successfully first using:

source build/envsetup.sh

breakfast guacamole

croot

brunch guacamole

before i follow the steps listed here in this guide??

Thank You
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
Check the extraction script for errors or switch to the muppets, sometimes the extraction script isn't up to date.

In general, yes, make sure you have a version of LineageOS that compiles successfully, that way you know you have a valid base to start from.
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Thank You so much.

One last question if i may, can these steps applied on LinageOS 4 MicroG using the automated build by their docker image docker-lineage-cicd ?

Thank You
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
You'd have to modify the docker image from my understanding as it includes all the source and tools required to do the build.
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Hello,

Kindly Please, Could you clarify what do you mean by ~/.android-certs/releasekey.key and ~/.android-certs/releasekey.key/ ??

I created my own signing keys, and the output contains releasekey.pk8 and releasekey.x509.pem, that is why I'm confused.

Note: I did a successful build of LineageOS with OEM unlock support and its option show in development menu and I flashed it to my OnePlus 7 Pro, I used only that option:

cd ~/android/lineageos/device/oneplus/sm8250-common

sed -i 's/^# OMX/# OEM Unlock reporting\nPRODUCT_DEFAULT_PROPERTY_OVERRIDES += \\\n ro.oem_unlock_supported=1\n\n# OMX/' common.mk

Thank You
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
You might need to convert your pk8 in to plain text using openssl like so:
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Thank You for the help.

I'm sorry, it did not work, that's what i got:

Error reading key

139625476420992:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: ENCRYPTED PRIVATE KEY
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
I used the releasekey.x509.pem file, it is a PEM certificate text file, the build failed.
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Hello,

Kindly please, clarify what is releasekey.key stands for, is it the private key or the public ? Is it data file or text file.

the build fail to the same.

avbtool extract_public_key --key ~/keys/releasekey.x509.pem --output ~/public_key.key

/android/lineageos/out/host/linux-x86/bin/avbtool: Error getting public key: unable to load Public Key

140081520305536:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: PUBLIC KEY

avbtool extract_public_key --key ~/keys/releasekey.pk8 --output ~/public_key.key

/android/lineageos/out/host/linux-x86/bin/avbtool: Error getting public key: unable to load Public Key

140477081752960:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: PUBLIC KEY
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
What commandline did you use exactly?
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
You can't use that.
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
I'm trying to understand, What is releasekey.key file??, it contains private key or public key, or both, and is it a data file or text file??

I did this:

openssl x509 -in releasekey.x509.pem -pubkey -out releasekey.key

The outputfile is a text and contains the public key and the certificate

when i delete the certificate part and start the build, i get this error:

/android/lineageos/out/host/linux-x86/bin/avbtool: Error signing: unable to load Private Key

140394811372928:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: ANY PRIVATE KEY

if i delete the public key part, i get this error:

/android/lineageos/out/host/linux-x86/bin/avbtool: Error getting public key: unable to load Public Key

139655441114496:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: PUBLIC KEY

if i didn't change anything and used the output file releasekey.key and start the build, i get this error:

/android/lineageos/out/host/linux-x86/bin/avbtool: Error signing: unable to load Private Key

139736685180288:error:0909006C:EM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: ANY PRIVATE KEY

I did a successful LineageOS signed build with my own generated keys and flashed on my mobile and working fine.

So, Kindly please, Could you please just tell us, What is this releasekey.key file, and how can we generate this releasekey.key ?

Thank You
[OnePlus 8T Guides, News, & Discussion] WhitbyGreg:
Why did you delete anything?

releasekey.key is the plaintext private key for the release certificate.
[OnePlus 8T Guides, News, & Discussion] ahmed.elsersi:
Following the LineageOS signing build steps, these files are generated:

media.pk8, networkstack.pk8, platform.pk8, releasekey.x509.pem, shared.x509.pem, testkey.x509.pem, media.x509.pem , networkstack.x509.pem , platform.x509.pem , releasekey.pk8, shared.pk8, testkey.pk8

I'm sorry, for the last 2 days I'm spinning around myself to figure out how to complete your guide and get a successful build.

Could you please, if you do not mind, just tell me how to generate this releasekey.key plaintext private key for the release certificate?

Your help is highly appreciated, thank you
[MDA II, XDA II, 2060 ROM Development] kerdo:
Hello every body .. look i guess am all new to the pocket pc's stuff ... and i really need an upgrade to my PPC ... its actually running on WM3 .. and i need to upgrade it to WM5 !! i really need somebody to tell me the right way to do so ...

i saw different ways ... but i just dont knw what do ... frankly am kind of afraid to take a step ... Plzz Help me ...

and btw i've downloaded the WM5 rom ... its on my pc nw .. i just dont knw what to do with it ... and whats the safest way to Upgrade ...

and 1 last thing .. can i restore to WM3 once again if i didnt like the WM5 ?

Thanx in advance :)
[MDA II, XDA II, 2060 ROM Development] deedee:
In each ROM you download there should be a text file readme giving you instructions on what to do. Basicaly, put the device in bootloader mode, connect to Active Sync and run the ROM Upgrade Utility included with the image. Based on my own experience it will take about 30-45 minutes from start to finish.

Lots of ROMs to try for tthe Himalaya, try them all and see which one you like the best.

Latest WM2003 ROM from the O2 Ireland site can be found here.

Just remember that a new ROM will totally wipe your Himalaya so make sur eyou have anything important backed up first.
[OnePlus 9 Pro] Salilsarkar:
Any one noticing jerky and lagy scrolling on 9pro in youtube app?? I own a op7t it doesn't seem to lag in any where through out the UI and apps, but weirdly scrolling in 9 pro seems jerky and choppy in youtube.
[OnePlus 9 Pro] WatskeBart:
Why use the official youtbe app, when you can have YouTube Vanced? ;)

I don't experience any lag with yt vanced
[OnePlus 9 Pro] applyscience:
yep. i believe its the same issue this thread is talking about. I hate it so much and if its hardware related and/or not fixable, I will be extremely pissed to spend 1k$ USD and not even want to use the phone.
[Moto G Stylus (2021)] ShadowFox141:
So I bought a moto g stylus 2021 from Motorola it's unlocked but not bootloader unlocked I don't know why there is a difference but whatever how hard could it be to unlock so anyways if I can get the bootloader unlocked I need to know if this is where I start the process of rooting here is the link to what I believe is the correct boot image

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

I only ask because my phone matches up with the build number in this link So is that exactly what I need?
[Moto G Stylus (2021)] sd_shadow:
https://xdaforums.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
[Moto G Stylus (2021)] ShadowFox141:
Did I post in the wrong section?

But also I was looking at what you sent and where the whole code names I didn't see anything about the XT2115-1 but on lolinet I found it and according to it my codename should be retus but I'm at work when I get home I'm going to use that fastboot getvar all method to double check but I'm pretty certain it will come up with retus all sorry if I posted in the wrong spot I thought this was the right place for my phone
[Moto G Stylus (2021)] sd_shadow:
See my bootloader unlock thread, then see my root thread.

If you have questions ask here, in your thread.
[Moto G Stylus (2021)] ShadowFox141:
Alright thanks man much appreciated I'll let you know if I succeed
[Moto G Stylus (2021)] ThreexLoser:
Anyone get root on Moto g stylus xt2115dl using a root app without a computer? I've tried all of them and none of them

worked. Is it just me?
[Moto G Stylus (2021)] o.class.jav:
download the "lenovo rescue and smart assistant" plug your phone in, start to perform a rescue- it will download the latest firmware into C:\ProgramData\RSA\Download\RomFiles -

Extract the Rom it downloads and Copy Boot.img to your phone

download Magisk and install on your phone

open Magisk and select install magisk then select "Select and patch file" - browse to the boot.img file you copied to your phone and patch it

once patched copy back to your pc

download and install google latest platform-tools

reboot phone into fastboot mode by running this in cli: adb reboot-fastboot

then replace the bootimg with the patched one by using the command: fastboot flash boot boot.img

fastboot reboot

Oncre it reboots you should see magisk, click on it, itll auto update and reboot your phone

go back to magisk and click on install, but this time select (direct install)

reboot and done....
[Moto G Stylus (2021)] toxinburn:
I stand corrected worked likea charm now to find some modules! thanks bro now I got 11 at least and got the root working. I will also give credit where i was asking others how to do it so that others can figure it out I was making it was to hard, although I would like a permanent twrp for it, but if i get time and all the trees maybe we can get it built.
[Moto G Stylus (2021)] lexridge:
I tried for months to get a ROM and Recovery built for this phone. Never could get a workable device/vendor tree. It was missing a lot of things. Not sure why. I tried about 4 different extraction methods, all of which only partially worked. I ended up deleting about 80gb of build related files from my HDD in frustration. I may try again someday soon, but I would much rather just replace this phone.

Here is where my device and vendor trees are located, but doubtful they will do you much good.

lacojim - Overview

lacojim has 6 repositories available. Follow their code on GitHub.

github.com
[Google Pixel 2 XL Questions & Answers] neilth:
Does anyone know if there’s any way to eliminate the Google warning message that pops up every time you boot up a Pixel phone once you have unlocked the phone’s bootloader? I just saw instructions for doing this on a Samsung phone and I’m just wondering if it’s also possible on my Pixel 2 XL.
[Google Pixel 2 XL Questions & Answers] ineedroot69:
just disable dm-verity
[Google Pixel 2 XL Questions & Answers] neilth:
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.

Any additional help would be appreciated.
[Google Pixel 2 XL Questions & Answers] ineedroot69:
hex edit it 🙃
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
The warning message is independent of dm-verity and is triggered upon unlocking the bootloader. While hacking the bootloader to have the message not be displayed may be possible, that course of action could cause an unrecoverable brick. The easiest way to not have the message show is to lock the bootloader.
[Google Pixel 2 XL Questions & Answers] neilth:
Thanks for the bad news.☹️
[Google Pixel 2 XL Questions & Answers] xunholyx:
When the message comes up, tap your power button twice.

The first press pauses booting up, the second is to continue to booting up. I do this whenever I turn on or reboot my phone, and the message is gone in less than a second.
[Google Pixel 2 XL Questions & Answers] neilth:
Thanks, I guess that’s about the best solution available.☹️