yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 5 Questions & Answers] SoundAdikt:
Xperia 5 J8210

Hi there, so as a newbie, I've got myself into a right mess!

I wanted to enable Ethernet over USB but Android 9 that came with the phone doesn't support. I couldn't immediately see any standard custom roms (should have looked harder!) so I unlocked the boatloader, compiled AOSP from scratch following the instructions on developer.sony.com. Flashed the resulting images across and it resulted in the phone not booting. I've managed to install TWRP but I'm unable to install any custom ROMs such as Lineage and PixelOS. When I go to install in TWRP it always immediately fails with "Error installing zip file '....unofficial.zip'. When I put TWRP into ADB mode and use adb sideload the transfer fails immediately.

This seems to be the same for any zip file I care to install. Any suggestions, I've a feeling something underlying is wrong, not least the opening statement on the custom rims along the lines of "Make sure you come from Official Android 11.0 from Sony".

Oh boy... help would be most appreciated.

Many thanks.
[Sony Xperia 5 Questions & Answers] NickDFR:
Do you use an SD card? There seems to be an issue with transferring files through MTP (at least on my device), whether it's from the system or the recovery, that renders seemingly good files unusable for flashing.

If you have an SD card or your phone supports USB OTG, I would suggest transferring the file from your PC to the external storage, then plugging it into the phone and flashing from there.
[Sony Xperia 5 Questions & Answers] SoundAdikt:
Thanks. I think there is something more fundamental: if I follow the instructions here to install PixelOS based on Android 11:

https://xdaforums.com/t/rom-11-unofficial-pixelexperience-11-for-sony-xperia-5-aosp.4381405/

I can't even get the recovery to work, it just says your device is corrupted it can't be trusted and will not boot. To get to this stage, I:

1. Downloaded software binaries for AOSP Android 11.9 - Kernel 4.14 Kumano

2. Installed in fastboot via fastboot flash oem_a SW_binaries...._kumano.img and fastboot flash oem_b SW_binaries...._kumano.img

3. Dowloaded and extracted pe-recovery.zip and PixelExperience_bahamut-11.0-20211229-1823-UNOFFICIAL.zip

4. Extracted pe_recovery and installed in fastboot via:

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash --disable-verity --disable-verfication flash vbmeta vbmeta.img

Unplugged USB booted into recovery mode via power and volume down only to briefly see Sony logo and then corruption message.

Given I can't get this to work, can you suggest any other things I need to do to at least get the PixelOS custom recovery to work?

Many thanks.
[Sony Xperia 5 Questions & Answers] bobbyamarthaa:
why are you using sony binaries for that rom?

didn't you read the instructions?
[Samsung Galaxy S22 Plus] iSean03:
Anyone from our friends in India who can capture the link of the beta update for S906E? Thanks guys!
[Samsung Galaxy S22 Plus] joaovictor.me:
Why is so hard to get a link of Indian version?
[Samsung Galaxy S22 Plus] iSean03:
I don't really know. Maybe there are less people who got s22+. Rn we only have s906B. Hopefully someone with s906E will get the link and share it with us.
[Samsung Galaxy S22 Plus] agentsandy007:
I just bought S22 plus. And yes not too many buy Samsung flagships here bcoz of atrocious pricing. People just go for iPhones, which is ironic since iPhones are even over priced.

I'm on OneUI 5.0 beta.

What can I do?

We have Dual Sim tho
[Samsung Galaxy S22 Plus] iSean03:
OMG you're a life saver bro. Can you maybe capture the FOTA link of the update? I think someone posted it how to capture it. Thanks a bunch.
[Samsung Galaxy S22 Plus] agentsandy007:
Guide me. I joined beta via samsung members app.
[Samsung Galaxy S22 Plus] iSean03:
Here try this.

How to capture the update.zip file to share with other people:

1. Download HTTP canary app

2. Open HTTP Canary app

3. Start the update by pressing "download" and don't pause it

4. Go back to canary app and start it and it will grab the link for you
[Samsung Galaxy S22 Plus] agentsandy007:
Will try.
[Samsung Galaxy S22 Plus] iSean03:
Thanks dude.
[Samsung Galaxy S22 Plus] agentsandy007:
Apk pure is not opening. Blocked in india? I can try with vpn but speed will be low.

Will vpn even work.
[Samsung Galaxy S22 Plus] iSean03:
For downloading the APK. Yeah VPN should work and the file is small. Let me check for another link.
[Samsung Galaxy S22 Plus] iSean03:
I mirrored it, try here. https://drive.google.com/file/d/1-4JyKQ0PuObl6J2nZA1wvehxR1S0THU6/view?usp=sharing
[Samsung Galaxy S22 Plus] agentsandy007:
I downloaded it in laptop.

But encountered this problem while setting up.View attachment 5704071
[Samsung Galaxy S22 Plus] iSean03:
Can you check this link. It's a guide to set it up. https://www.droidwin.com/capture-samsung-one-ui-5-0-beta-update-ota-download-link/
[Samsung Galaxy S22 Plus] agentsandy007:
I need http.canary.pem file

Its a ca certificate file located in installed folder or something which I'm unable to access.
[Samsung Galaxy S22 Plus] agentsandy007:
Omg dude I'm sorry.

I already installed Beta and now it shows you are up to date. How tp capture it then?View attachment 5704093View attachment 5704093View attachment 5704095
[Samsung Galaxy S22 Plus] iSean03:
Awww. That's too bad. Only options are reverting to 4.0 then enroll back to beta to start the update again. Or capture the link on the next update. Anyway thanks bro. I'm happy to know someone has an s22+ who's willing to share the link.
[Samsung Galaxy S22 Plus] agentsandy007:
Everyday I opened S22 plus Thread on Xda but never opened your thread. I thought someone from India must be asking a random question about update and I didnt open.

Dam I just installed this update like 5 hours ago.
[Samsung Galaxy S22 Plus] agentsandy007:
So just to be clear, if I get beta 2 update and capture it, will it work for you?

And This capturing process is tedious. I'm not even sure If I've set it up correctly and it seems like only one shot at capturing.

In the above image it still says ca certf not installed in blue heading.
[Samsung Galaxy S22 Plus] iSean03:
I honestly don't know if that will work. Since we lack people who uses s22+, we can't test it. About the certificate, it can be installed from settings. I'm trying to replicate it myself.
[OnePlus Nord N10 5G Questions & Answers] nixcamic:
Hey I have a N10 that I'd like to update to a newer version of Android, it looks like GSI are the only way to do that, but I have a few questions:

What is a recommended Android 12 GSI?

I saw that there are problems with biometrics, have those been solved?

What camera app are people using?

Has anyone tried the Android 13 GSI from Google, and if so is everything working?

Thanks!
[OnePlus Nord N10 5G Questions & Answers] Artesna:
From the ones I've tried, I'd recommend Ancient OS or CrDroid if you want customization or maybe DescendantOS or Pixel or something like that if you want less stuff. It's pretty easy and fast to take a look and flash one then switch so try some out and see which one you prefer. All of the ones I've tried have booted and worked fine except SparkOS, though wasn't on newest patch and I let the developer know of it so might be fixed. I've tried out majority of them.

I haven't had issues with biometrics. I use BSG's gcam mod for camera.

Haven't tried it yet since my phone broke and I'm stuck with a really old backup phone, but I'd expect it to be pretty buggy still, might have to wait for phh patches to be able to use it as a daily OS.
[Samsung Galaxy Z Flip 3] NguyenHuu:
Like the title says, is this possible and can it be done without wiping user data? Thanks.
[Samsung Galaxy Z Flip 3] blackhawk:
Probably not worth the trouble. Always assume you will lose the data and back it up redundantly.

I thought there be a night and day difference when I got the unlocked N10+ N975U1 vs the AT&T variant N975U. There wasn't. The unlocked version actually had some bloatware not on the AT&T variant🤣

Easiest and safest thing to do is package blocked the carrier bloatware. Verizon does some screwy modes to their devices so getting rid of that be nice. AT&T does not, that surprised me. Some users might like some of the AT&T apps.
[Samsung Galaxy Z Flip 3] NguyenHuu:
It was successful, thank goodness. See my follow up here https://xdaforums.com/t/f721u1-firmware-now-available.4484639/
[Samsung Galaxy Z Flip 3] blackhawk:
Notice much difference?
[Samsung Galaxy Z Flip 3] NguyenHuu:
Yeah the main stuff are:

1. Rcs with jibe server works now. Before it used att server so it wouldn't connect properly with other users

2. System updates come directly from Samsung instead of att
[Samsung Galaxy Z Flip 3] blackhawk:
Don't use either.

Updates is one of the first things I disabled on my N10+'s. One's on Pie, the other 10, I prefer Pie though. Once Google started rolling out scoped storage I bailed.

&

AT&T/Samsung have a nasty habit of screwing up older devices with firmware upgrades. Just had a pair of Buds+ screwed up like that a few months back, now they need the firmware rolled back*. S4+, same deal a few years back, but bootloader was updated too, no rollback.

If an OS is running fast, stable and fulfilling its mission... I let it be.

*I have 2 new pairs of Buds+, they sound identical and like my original pair use to, grrrrr.

Went with them because Samsung's newest release lack the features I want. Rather annoying.

The Buds+ have a 11 hr run time, light, don't fall out and sound good.
[Samsung Galaxy Z Flip 3] boxface:
Sorry I should've posted my question here, instead of creating a new thread.

I recently purchased a flip 3 and am on a payment plan, tmobile won't unlock my phone unless I pay it off in full. Is it possible to flash the default software of the unlocked model so I can get updates from Samsung and still have my sim work? I'm not switching carriers, do I need the tmobile version of firmware for data/phone to work if the phone isn't unlocked?
[Samsung Galaxy Z Flip 3] iBowToAndroid:
Phone service will still work perfectly fine on U1 firmware, but you may lose lose some carrier-specific features like wifi calling etc. But.... the U1 models don't always necessarily get faster updates than the carrier models. For example, with the most recent update, the carrier model got it 2 weeks before the unlocked model. So if that's your only reason for wanting to change firmware, I'd advise against it.

Notify Update

- U model update history

Notify Update

- U1 model update history
[Samsung Galaxy Z Flip 3] boxface:
What I'm concerned about is tmobile eventually stopping the updates way sooner than Samsung. The carriers don't usually update a phone as long as the vendor so to avoid that I would rather not use T-Mobiles version. Thanks for the reply, it was very helpful.
[Samsung Galaxy Z Flip 3] iBowToAndroid:
Incorrect. Every single model's lifespan for updates has always been the exact same, whether U or U1
[Samsung Galaxy Z Flip 3] thesm4rt1:
I downloaded the unlocked firmware via Frija for SM-F711U1 / XAA and flashed it onto my At&t unit using patched Odin. Lost my data since the install didn't work without flashing CSC but booted up and working just fine now. No At&t bootscreen or bloat
[Samsung Galaxy Z Flip 3] blaze2051:
have you ever tried from flashing one carrier to another by using the pit file or by using the combination file and then flashing the full firmware?
[Samsung Galaxy Z Flip 3] thesm4rt1:
Hmm, no I haven't. Would be curious if it works. I don't have that device anymore but best of luck!
[Touch Pro, Fuze General] thehyecircus:
close this. but why is there no manual?
[Touch Pro, Fuze General] bigb252:
Its on the disc provided.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DEM0N Assissan7:
How did you manage to update your firmware to OOS12? I tried the instructions on the lineage wiki page for the device and it led me to links that downloaded OOS11 firmware.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Head over to this thread and grab the OTA package for IN2013_11.C.33 to run the latest EU fw on your OnePlus 8. I would say that the oldest you can run on your OnePlus 8 is maybe 11.C.16?

(Also, note that you can run EU fw on devices from other regions.)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DEM0N Assissan7:
So, for some odd reason, whenever I try to do any of the "fastboot flash __ ___.img" commands, it says "Flashing is not allowed for Critical Partitions," but I have already unlocked my bootloader and done `fastboot flashing critical_unlock` and it was unlocked (when i try to do that command it says "Device already : unlocked!"). I have been totally puzzled by this. Is there something I have to do in particular or am I plum out of luck?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mvmike:
Just upgraded from 18.1 to 19.1 following the manual upgrade guide and the suggested IN2013_11.C.33 OTA package. No data loss and everything working at the first try, kudos for the great work :)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
If you're following the instructions at https://wiki.lineageos.org/devices/instantnoodle/fw_update, you will notice that it tells you to "Go to “Advanced” -> “Enter fastboot”", along with a warning that "it cannot be substituted with “Reboot to bootloader”". The fastboot implementation in OnePlus's bootloader blocks you from flashing critical partitions no matter what, hence why the instructions tell you to tap on "Enter fastboot", which launches fastbootd instead.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DEM0N Assissan7:
Thank you so much man. I totally forgot about the fastbootd thing. I will flash the LOS 18.1 recovery and do that from there. That step totally flew over my head.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] thattechguy_69:
Awesome that OnePlus 8 finally has official 19.1, but why can't you flash on IN2017 if IN2017 to IN2015 firmware conversion is possible? You know what I'm gonna test this on my IN2017 and I'll tell you guys if it works or not.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DEM0N Assissan7:
Update: It worked, I'm sending this message using my One plus 8 using your ROM. Thank you so much for your work on this and I cannot thank you enough. Do you have a place to receive donations or anything like that?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
EDIT: my apologies... I confused IN2017 (T-Mobile) for IN2019 (Verizon). In that case... my 2nd post mentions that I am in fact running this on an IN2017 w/ IN2013 fw. However, it should be noted that even then, my phone reports itself as project number 19855 instead of 19821.

Original message is as follows (now corrected):

The main reason is that for the OOS 12 kernel source, OnePlus didn't release kernel dts for project 19867, which corresponds to IN2017 IN2019. The dts in the OOS 11 kernels sources included some changes that were specific to the IN2017 IN2019, so that worked fined, but there is none for the OOS 12 kernel source.

I could look at the OOS 11 kernel dts and try to figure out what IN2017 IN2019 changes there are, and then create a new 19867 dts directory in the OOS 12 kernel source source with those changes (if any). However since I don't have an IN2017 IN2019 (and neither does anyone else in LineageOS), I can't test to see if my changes would work. As such, I can't even declare unofficial support for IN2017 IN2019.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That's good to hear! I don't accept any donations at this time.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Jeeves-2:
I have an IN2019 and was able to get it to boot by following the instructions on the wiki for the other models. However, RN it barely functions at all, the sim card isn't detected and if you disconnect it from power while in lineageos it shuts down because it can't tell how much juice the battery has. If you could revert those sensor changes, I'll give it a shot asap. hopefully that will at least let battery charge and mobile network function because otherwise it seems to work fine, similar to 18.1 where you could just flash the ROMs for other models and the only thing you lost was mmWave, which IDK about anyway.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
When I say sensors, I'm talking about accelerometer/gyroscope and magnetometer showing the wrong orientation without the configs from Verizon Oxygen OS. If battery percentage cannot be detected, then that's a whole 'nother issue entirely.

That being said, try reflashing the modem from VZW OOS 11 and seeing if that helps for detecting the sim card. I can't do much for fixing battery detection unless I spend the time to trawl through the OOS 11 dts, which, given that I don't have a VZW OnePlus 8 to test against, that's kinda low on my priority list.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KerbalNo15:
I've been using LineageOS for years now; thanks for bringing 19 to the OP8. Have you tried installing magisk yet? I can't seem to get it working. Neither flashing in recovery nor booting a patched image (extracted from installation zip) works.

Thank you!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I have not tried installing Magisk yet actually, and well, technically, that would be out of scope of LineageOS anyway. But since I'm curious, I'd like to know what you end up seeing whenever you try to sideload the Magisk zip in Lineage Recovery or flash the patched boot image.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KerbalNo15:
The phone gets stuck on the boot animation. Not exactly a bootloop because it doesn't restart, but pretty close.

As was likely the case, it was my fault. All my old magisk modules were still installed and some of them are now incompatible. I was able to install magisk after using the ADB instructions here: https://topjohnwu.github.io/Magisk/faq.html
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Jeeves-2:
actually I used an app called "Sensors multitool" to figure out the battery issue, and it showed the acclerometer and gyroscope working perfectly, as well as the magnotometer. GPS didn't appear to work though, so I think you're right about needing some of the drivers from the verizon oneplus 8 rom. However, I'm struggling to find where to download them. Oneplus doesn't offer downloads for the IN2019, and as far as I can tell, neither does verizon except through their OTA updater. is there any way you know of to find a image, or am I sol?

Edit: nevermind, may have found it in the guide for unlocking the bootloader for the IN2019. thank you so much for the advice
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] RogueVisual:
im sure im doing something wrong. everytime I install the new recovery, I get stuck on the warning "your device is unlocked" page, I cant even get back into bootloader. Had to use MSM tool. I have to be on OOS12?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Just to note: The OOS 12 bootloader no longer shows that unlocked bootloader warning. As such, if you're still seeing that warning, it means you actually didn't flash OOS 12 firmware. Please grab the European IN2013_11_C.33 OTA from here and try again. Or, since you're back on stock, keep OTA updating until you get to your region's 11_C.33 firmware.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
I was wondering how long it would take for Lineage based on A12/12.1 :) - always good news to hear about this project. I'll be installing this soon and give it a try, share some feedback, etc.

Before I do so, OP, what GAPPS do you recommend installing on this?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I follow what LineageOS recommends: https://wiki.lineageos.org/gapps

In particular: MindTheGapps-12.1.0-arm64
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Appreciated :) I was wondering if you tested out Bluetooth as well, I've found that for some other A12 OP8 ROMs Bluetooth can be turned on but it doesn't ever connect to any devices.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Yes, I've been using Bluetooth LE to connect to my Mi Band 3, along with using Bluetooth to connect to an Aukey EP-B40S, AirPods Pro, and some FM radio transmitter that connects to my OnePlus 8 over Bluetooth. I've checked to make sure many things I use daily actually worked, along with reading the Evolution X OP8 series Telegram chat to catch any bugs people encountered there (since AnierinB's device tree + kernel is very similar to LineageOS's and we share device-specific bugfixes). The only major bug is the one I've outlined in the 3rd post in this thread.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mvmike:
Confirming too that bluetooth works in multiple devices i've been testing (headphones, car...).

Regarding Gapps, NikGapps are also running without any issue
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Seems like the suggested MindTheGapps package isn't supported because the recovery is complaining it's made for SDK 32 and the current OS SDK is 31.

Edit: After a reboot into recovery post flashing Lineage it worked. tldr: nvm!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That would certainly be concerning if the GApps package that LineageOS links to on their wiki isn't compatible, lol. But yeah, the installation instructions state that to install addons like GApps, you need to reboot into recovery again after sideloading LineageOS so that any addon zips you sideload would write to the slot with LineageOS 19.1. Since you didn't do that, MindTheGapps attempted to install itself into the slot that has OxygenOS 12 instead. OxygenOS 12 for the OnePlus 8 is based off Android 12 (API level 31) and not Android 12L/12.1 (API level 32), so fortunately, it errored out early on the API level check.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Funny enough I actually had ColorOS 12.1 installed haha. Anyway, ROM installed properly and everything is working so far. Big thumbs up and thank you for your hard work! Something that I'd love to see is AOD fingerprint working, so far it tells me to clean the sensor but I'm pretty sure it's just not a supported feature as of now.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That's odd... that's supposed to be working as expected, at least on my OnePlus 8. Won't respond until maybe 8-ish hours from now as I'm heading to bed, but do you see the UDFPS circle glow really brightly (as opposed to glowing at the same brightness as everything else on the screen) when you try putting your finger on it?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Weird, it didn't work until I manually went to the ambient display settings under display in the settings app. I didn't see the ambient display option at first so I thought it hadn't been implemented in this build yet. I enabled "AOD" through QS and the AOD would pop up as expected but it would tell me to clean the sensor. Right after that I unlocked the phone using the same finger through the lockscreen with no issues. Seems like it's working fine now after checking the ambient display menu in the settings as I just mentioned although the ambient display doesn't wake on pick-up, it goes straight to the lock screen instead so I guess I'll just have AOD always on for now :)

Edit: Also is there any way to get themed icons on this launcher? Loving the ROM so far btw, great work. Glad to report Magisk and the modules I have installed all work wonders including Substratum lite! Here's a screenshot:
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Also has anyone managed to get CTS profile matching to pass on SafetyNet on this build? I've tried some modules on Magisk but none of them work.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mvmike:
Passing with universal safetyNet fix and magiskHide props config modules