yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] sfoslino:
I used the "[New][A/B] LineageOS 16.0 Treble system-as-root" from "https://xdaforums.com/t/treble-unofficial-lineageos-16-0-treble-for-oneplus-3-3t.3830455/" and there the lineageos from 20190826 (lineage-16.0-20190826-UNOFFICIAL-oneplus3.zip: Support system-as-root, flash A/B GSIs instead of A-only).

And I did not wipe system on my last try. Because, if droidian do not need it, why should I wipe it and have an empty system partition. And on 1st boot after doing that, lineageos was booted, not droidian. Thats why I thought something is missing and flashed haluim-boot.img to boot. Something is missing in the oneplus3-snapshot26, it should write a boot partiton too.

I think: With lineageos boot partition I can boot into lineageos and with halium-boot I can boot droidian now.

Your Steps on an unlocked device:

1) ok

2) trebelize ok: you need it only the 1st time

3) does it fill and populate the vendor partition? You should make a clean flash. What I did: I wiped caches, system, data, flashed firmware+modem OOS 9.0.6 for my device(maybe optional if you are sure you have the right fw version, but do not flash fw for the op3 to the op3t or vice versa, it will brick the device). Right after that I flashed lineage-16.0-20190826-UNOFFICIAL-oneplus3.zip, it should tell something about vendor partiton at the end.

4) ok: reboot to twrp. First I checked if the vendor partition was filled: select mount->vendor and advanced-filemanager, look into /vendor there should be many folders and build.prop, default.prop and ueventd.rc. After that I unmounded vendor again and did the advanced wipe (except vendor, usb-otg and system). And I took a backup of boot, maybe I can use it to boot lineageos again.

5) flashing droidian-snapshot26 is ok, but do not reboot, I you reboot now lineageos will start again, because system is not wiped. Thats why I think someting is missing, it tries to boot the wrong OS and if it is wiped the screen stays black.

6) flash halium-boot.img to boot and reboot, after some time you should see the droidian logo (debian in green).

flashable firmware can be found here for example: https://xdaforums.com/t/op3-3t-flashable-firmware-modem-zips.3816066/
[OnePlus 3 & 3T Cross Device Development] bdlc794:
Honestly thanks I would not have been able to do it without your guide.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
Today I did a setup from scratch on a oneplus3 with 'droidian-OFFICIAL-phosh-phone-oneplus_oneplus3-api28-arm64-nightly_20230822.zip' and the boot partiton was patched on sideloading the zip file. It was not needed to flash halium-boot.img, it is fixed!
[OnePlus 3 & 3T Cross Device Development] Marcyvee:
No way to fix camera on Oneplus 3?
[Asus Zenfone 9] AzimBahar:
anyone have -

QMSCT_ForCSC_DefaultFuseLock_AI2202_SM8475_31.1902.1902.55.zip​
[Asus Zenfone 9] NisseGurra:
I think you will be out of luck, the edl files was more or less non existing for Zenfone 8 and 9 will most likely be the same.

You need to send it to asus service to unbrick it
[Asus Zenfone 9] AzimBahar:
I got it on ROMDevelopers Thanks
[Asus Zenfone 9] craznazn:
Do you happen to have a link?
[Asus Zenfone 9] gingerjoa:
QMSCT_ForCSC_DefaultFuseLock_AI2202_SM8475_31.1902.1902.55.zip | Rom Developers

romdevelopers.com
[Introductions] Wabbajackw:
Hi everybody, im Wabbajackw (usually wabbajack but for obscure reasons it's was already taken :p) im passionate about retro gaming, retro tech and new techs. I was working for few brands as Samsung and Xiaomi. I'm here to share, ask and resolve :)
[Introductions] Wabbajackw:
Thank you!
[Google Pixel 5 Questions & Answers] kdrkdr:
I use the minimed application from Medtronic to check my blood sugar. Does anyone know if the Minimed app works on Android 13? If not, upgrading is a showstopper for me.

If the app just starts without saying it is impossible to run it will be fine. If someone wants to check I will appreciate it very much.
[Google Pixel 5 Questions & Answers] canadiancow:
It does not work. It blocks you at startup (ask me how I know 🙄).

I was trying to manipulate the APK last week to bypass this, and while I succeeded at bypassing the version check, I couldn't get it to actually pair with my pump, so I gave up.
[Google Pixel 5 Questions & Answers] Capsymot:
Hi. I'm in the same situation as you both are. I have Android 13 now and the app doesn't work. How did your try to manipulate the APK? If i knew how to do it I could also try to get it to work. Thanks in advance!
[Google Pixel 5 Questions & Answers] Capsymot:
Hi. Sorry for spamming you now... Can you send me the APK? I could try to get my pump to pair. Don't know if there's any difference but it could be worth a try.

Thanks, Tommy
[Google Pixel 5 Questions & Answers] canadiancow:
apktool and smali manipulation.

If you get it working, I'll have to try again 😂
[Google Pixel 5 Questions & Answers] Capsymot:
Ok. Haven't been working so much with APK:s and how to mod them but I will have a try sometime. But unfortunately it didn't work. It cannot connect. It doesn't find any network. Too bad. But thanks anyway.
[Google Pixel 5 Questions & Answers] Jakiemabee:
Does not connect to Medtronic servers on my end as well. I did the stupid thing and updated without even thinking about the Medtronic app... The alarms and notifications were really handy on my pixel 6. (780G)
[Google Pixel 5 Questions & Answers] Capsymot:
Same here. I knew about the app not working but wanted to try anyhow. But now I'm back with Android 12 and have disabled the notifications about new update. Guess it will take some time before Medtronic update the app.
[Google Pixel 5 Questions & Answers] kdrkdr:
Today I received an update of the MiniMed app. Can someone who already upgraded to Android 13 check whether the app is working now?
[Google Pixel 5 Questions & Answers] canadiancow:
It's been working for a while. It didn't need the app upgrade.
[Google Pixel 5 Questions & Answers] kdrkdr:
Thanks. Working for me too
[Google Pixel 5 Questions & Answers] nothing94:
is it really working for you on android 13? when I open it i'm welcomed with the splashscreen informing me that o.s. version is not compatible.

are you running version 1.2.1 or what?
[Google Pixel 5 Questions & Answers] canadiancow:
I'm on 1.3.1 and it works fine.
[Google Pixel 5 Questions & Answers] kdrkdr:
YES. Works fine on Pixel 5 Android 13
[Google Pixel 5 Questions & Answers] nothing94:
oh okay, so I think that it's a combo between o.s. version and device. I have S22 oneui beta 5 and I have the splashscreen on 1.3.1
[Google Pixel 5 Questions & Answers] corradofrez:
MOD Translation by andybones:

has anyone found a solution for samsung?

qualcuno ha trovato una soluzione per samsung?
[Google Pixel 5 Questions & Answers] anthondutch:
Wanneer je de versie 1.1.1 installeert werkt het wel
[Google Pixel 5 Questions & Answers] corradofrez:
hi guys, does anyone have any news on this application for samsung s 22, samsung A 53 or xiaomi note 9?

a thousand thanks
[Google Pixel 5 Questions & Answers] kcurrie65:
Hello. My Samsung S20 5G upgraded to Android 13 yesterday and the Minimed mobile stopped working Unsupported Android Version unfortunately the app does not work with Android 13. I found this thread and followed the link and now have a working version on my phone perfect and thank you! the next question is my wife same phone also upgraded and she uses carelink connect to follow my ups and downs but it now shows the not available on Android 13 message. Does anyone have a solution for carelink connect app we are based in Scotland UK thanks
[Google Pixel 5 Questions & Answers] Troxelke:
Hi guys, maybe you can help: I have a Sony Xperia 5ii that is on Android 12 and the Minimed Mobile app does not work. I did however work 2 updates back + my phone on Android 11.

What I already tried: installing the first (1.1.1 version, and actually all versions I could find), where the app continues after version check (yes!), but then the pump cannot connect Bluetooth (had this issue already at the first release).

Also tried the above "patched" APK but there the error that the app does not work on A12.

Since my phone will not get an upgrade to A13 (and no stable A13 AOSP versions available), I am stuck... Any suggestions? I am amost that far to buy a new phone ONLY for getting Minimed Mobile to work again (especially with the link to Xdrip and my Garmin devices during mountain biking and trail running).

Thanks for your help!! Appreciated!!
[Google Pixel 5 Questions & Answers] Troxelke:
For me this does not work, I get past the version check but at the screen of connecting pump, the pump is not able to find the phone.

Any suggestions, also see my above post?
[Google Pixel 5 Questions & Answers] Troxelke:
Small update, I got it to work, have downgraded to Android 11 (no big deal since A12 is not really better). Followed this guide:

https://www.reddit.com/r/SonyXperia/comments/tjpkgx
[Google Pixel 5 Questions & Answers] sonykill:
is there a way to get it to work without downgrading??

i have a Nothing Phone (1) running android 13 and the app says my device is not compativle... with apk tool i cant see much on how to remove the device lock
[Google Pixel 5 Questions & Answers] Troxelke:
I don't know, I am now in the same situation with my new phone, Xperia 1 v with Android 13. Also the splash screen that my device on A13 is not compatible. Horrible :(. Do I decide to ditch a 1400 euro device for only the medtronic app ....??

See also here some thread with work going on:

https://xdaforums.com/t/help-getting-an-app-to-work-on-a-rooted-phone.4516299/

https://xdaforums.com/t/cgm-app-bla...s-and-android-versions.4569881/#post-88344629
[Google Pixel 5 Questions & Answers] dpishta:
Is there a newer modded version. This one doesn't connect to the servers anymore
[Google Pixel 5 Questions & Answers] canadiancow:
The official app is working fine for me on a Pixel 7 Pro running Android 14.
[Google Pixel 6a] badabing2003:
View attachment 5692225

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.

For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 6a] chopt51:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
[Google Pixel 6a] badabing2003:
If you don't choose wipe data, or force in flash options, then you should keep your data.
[Google Pixel 6a] tlxxxsracer:
I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.
[Google Pixel 6a] ctfrommn:
USB debugging turned on?
[Google Pixel 6a] badabing2003:
Explain what you mean by that?
[Google Pixel 6a] tlxxxsracer:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
[Google Pixel 6a] badabing2003:
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.

There is no reason for it not to be detected if you're command detects it.
[Google Pixel 6a] badabing2003:
New Release:

Aug 24, 2022 v3.6.0 release

When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.

Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.

Improved tooltips.
[Google Pixel 6a] jpdurand31:
Hello,

I have a pixel 6a on A12 rooted with Magisk.

I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.

I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.

The weird thing is that I still have the message that said the bootloader is unlocked...

Any ideas?
[Google Pixel 6a] badabing2003:
If you can post support.zip file from help menu I can take a look.
[Google Pixel 6a] jpdurand31:
If you want more info, i'm 100% available!
[Google Pixel 6a] badabing2003:
Hmmm ...

I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?

I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good

I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)

You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)

On next attempt (one hour later) your device was in bootloader mode.

Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.

You cannot create a patch file in fastboot mode, it needs to be in adb mode.

And please please don't dare to lock your bootloader, I see you attempted and then cancelled,

2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!

NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!

Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.

2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...

If you lock your bootloader before fixing your device, you will be locked out forever (bricked)

So at this point what are your choice and how can you fix this?

1- get the latest Android Platform Tools

2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.

Select the firmware, process it, this will show the boot.img file

Select the boot.img file and choose keep data and hit Flash.

Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.

Alternately, what happens if you select in PixelFlasher to reboot the device into System.

Does it reboot? and if it does, does it end up in adb mode of fastboot mode?

One other option you have is to flash OTA in sideload mode.

Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.

PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.

Good luck
[Google Pixel 6a] jpdurand31:
Thanks for your response and the detailed process.

I was fooled by the version of the package that was in 33...

By upgrading the Android Platform Tools to the latest version, I could update to Android 13.

Thanks a lot for the help and the reactivity!
[Google Pixel 6a] badabing2003:
New Release:

Sep 04, 2022 v3.7.0 release

New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.

New Feature: Install compatible apk file onto the device from PixelFlasher menu.

Check Android Platform Tools version and warn if it is old.

Block flashing when stock flash_all.bat file is tampered with.

Don't bother with flashing if bootloader is locked.

More validations and exceptions handling.

Improved logging.
[Google Pixel 6a] JudasD:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
[Google Pixel 6a] badabing2003:
Thanks for reporting and sorry for your troubles.

Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.

Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?

It should capture the error PixelFlasher 3.7.0 encountered.
[Google Pixel 6a] JudasD:
Thank you for the help. The issue has now been resolved after reboot.

Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
[Google Pixel 6a] badabing2003:
No need for apology, happy to hear that the issue now resolved.
[Google Pixel 6a] mike.s:
Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):

2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)

Everything seemed to work fine, though.
[Google Pixel 6a] badabing2003:
New Release:

Sep 24, 2023 v5.8.0.1 release

Bug fix: #99 Settings not opening on linux/arch based distro
[Google Pixel 6a] badabing2003:
Update Release:

Oct 06, 2023 v5.8.0.3 release

Improved debug messages for troubleshooting.
[Google Pixel 6a] badabing2003:
Update Release:

Oct 11, 2023 v5.8.1.0 release

Added data for Pixel 8, Pixel 8 Pro

Build workflow update, sha256 checksums are now published along the binaries.
[Google Pixel 6a] badabing2003:
New Release:

Oct 18, 2023 v5.8.2.0 release

Added `Wipe` option (only available in custom flashing), this will wipe userdata after flashing, required for first time vbmeta verification disabling.

Added validation checks to make sure A and B slot vbmeta verity / verification states match.

Added a warning when toggling `Disable Verification` to inform about the the potential wipe implications.

Display both slots verity / verification states when displaying device details.

Extract vbmeta.img if found to easily select it for patching.

Improved paste button which now dynamically selects what to paste based on the custom flash option selection.
[Google Pixel 6a] penpex:
Hello,

Concerning the update to A14 (from the August update if that matters) on my P6a, is there any reason the double Full OTA flash would not work ?

I am still using the Platform Tools 33.0.3, and saw some discussions about people successfully updating their P6a with the 34.0.4 version on the main thread. Should I change to that ?

I don't remember why specifically, but I remember I stayed on 33.0.3 until now because there were some bugs with versions >33.0.3...
[Google Pixel 6a] badabing2003:
No

Windows : stay on 33.0.3

Mac: use the latest 34.x
[Google Pixel 6a] badabing2003:
New Release:

Nov 12, 2023 v6.0.0.0 release

More verbose logging and additional debug messages for troubleshooting.

Renamed the Verbose label to Debug.

Improve UI responsiveness when running background tasks.

Automatically detect vbmeta state for both slots, and warn if the selection would have wipe implications (this is for verity / verification disabling).

Removed Check Verity button, (verity / verification), replaced with vbmeta state reporting for both slots as part of device details.

Show Bootloader version as part of device details.

Show slot related details such as slot-retry-count, slot-unbootable, slot-successful as part of device details.

Added Reboot to Sideload option.

Graphical display of device's slot and root status.

In most cases long background processes are automatically killed with proper timeouts (when possible) and reported to unfreeze PixelFlasher.

Reworked device detection / update / refresh, reboots, PixelFlasher now automatically detects device state changes and waits exactly the time until the device state changes to the expected state. Less dependency on arbitrary timeouts.

Improved support logs sanitization.

Detect free space on the computer and block flashing if less than 5G of storage is available.

Refactor flashing function.

More response console widget log messages.

Detect currently installed OS version and block flashing older OTA (Android by default allows flashing but fails to boot).

Detect, warn and block flashing if bootloader is locked for flashes that require bootloader to be unlocked.

Added wipe option for custom flashing to easily wipe the phone when flashing vbmeta to disable verity / verification.

Report if the device is unlockable.

Bug fixes, lots of changes under the hood and miscellaneous improvements.

Added option to delete specified libraries from the PixelFlasher bundle, to let the system library be loaded instead. Needed for newer OSes that require updated libraries. See Symbol Lookup Error #109, and After a large system update (manjaro), do not work now. #111

Additional support for Scrcpy of non-Windows platforms.

Updated XDA links
[Google Pixel 6a] badabing2003:
New Release:

Nov 13, 2023 v6.0.1.0 release

Added settings option to enable / disable free storage space check.

Improve storage check to follow symlinks and return the partition free space where the data resides instead of where the symbolic links resides.

Added command line support for specifying PixelFlasher config json file, use -c or --config flag followed by full file path of configuration json file.

Added command line --console (only useful on Linux / Mac) to display all PixelFlasher output to console, useful when troubleshooting.

Further improved handling of large file extraction on low memory computers.
[Google Pixel 6a] badabing2003:
Update Release:

Nov 14, 2023 v6.0.1.1 release

Bug fix: Make sure Low memory settings are loaded at startup.

After flashing factory or OTA, on last reboot to system, increase the wait from 60 to 90 seconds to make sure the device loads all the way to system and does not timeout PF. Although the error message is benign, it creates unnecessary anxiety seeing an error message in the console and thinking that something is wrong.

Bug fix: Available storage was not computed correctly on Linux platform.

Fix and speed up MacOS platform build.
[Google Pixel 6a] badabing2003:
Update Release:

Nov 15, 2023 v6.0.1.3 release

Cleanup temporary created files when using low memory option.

Don't wait for device to be available in adb when wipe option is selected. (The user would need to setup the phone for the first time, enable developer options and enable debug, which could take a while)

Add more debug messages for troubleshooting.

#117 psutil is not reporting free storage correctly on Linux platform, use shutil module instead.

Print available memory when processing Image.