yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Same as doing it through fastboot: I get a system corrupted error, then it powers off/reboots to bootloader. Reflashing stock fixes this, and sets up for the next experiment.
[Upgrading, Modifying and Unlocking] V0latyle:
Are you wiping data when installing the GSI?

Are you talking about the dm-verity screen?

Or the Rescue Party screen?
[Upgrading, Modifying and Unlocking] ieatabiscuit:
When I tried it via fastboot, I did do the -w to wipe data, and dm-varity came up. However, I did forget the vbmeta.img first. Time to go back, and tinker again!

UPDATE: Flashing vbmeta, then system.img results in booting to fastboot mode. I'm posting my findings as I go so I can beter recall what I've done, and for posterity.
[Upgrading, Modifying and Unlocking] V0latyle:
I think there's a guide to using TWRP to flash GSIs somewhere. DM-verity issues typically mean there's a problem with verifying the boot image. You could try disabling verity and verification: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification

You're not doing anything to /boot or /vbmeta when you're installing the GSI, yes? Which GSI are you trying to install?
[Upgrading, Modifying and Unlocking] ieatabiscuit:
for the pixel 2/2xl you need to flash a vbmeta.img to handle the corrupt screen. It worked as advertised. I can't get the GSI to boot, it flashes fine (from a clean flash-all.bat process, so full wipe), but will only boot to fastboot mode. I never touched /boot or /vbmeta aside for flashing the vbmeta.img as I said.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I'm using the a13 beta image from your link in op
[Upgrading, Modifying and Unlocking] V0latyle:
With the stock kernel from the last factory update?

TBH I don't know enough about this to know exactly what is going on or what you need to do
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I'm learning too, so no worries. What I have done now is tried flashing the boot.img from the GKI link in op, but I get an error talking about not having enough space to flash it. Otherwise, I THINK you're on to something, and there has to be a matching kernel. For my pixel 2xl, I'll need to resize more partitions, but which one for boot? and isn't that how you bricked your pixel 2, messing with /boot?
[Upgrading, Modifying and Unlocking] V0latyle:
Mmmm, I don't think so...GSIs are designed to be used with a separate kernel. Kernel version shouldn't matter too much

I bricked my Pixel 2 because I wiped all the B partitions trying to make it a slot A only device. But since the bootloader still contains code to switch slots if the boot fails, it tried to switch to a bootloader slot that is no longer there.

As long as you're using TWRP and you only mess with "system" partitions such as /boot, /vbmeta, /system, /product, /vendor etc you should be OK.

Speaking of, you have to have an intact vendor partition because this contains all the stuff that is specific to the device. I don't think that is the problem here though, it seems to be an issue with the boot image.

Describe exactly how you're installing the GSI?

We need to get a real expert like @AndyYan or @phhusson in here who has more experience with Treble architecture.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Steps

Steps taken:

Factory reset with flash-all.bat from last official release. success

Flash vbmeta.img via fastboot (no options to flash it in twrp) success

Flash system.img (tried via twrp, and fastboot with same results) success

Tried to flash boot.img for kernel fail: not enough space on partition

End result is the device booting directly into fastboot mode. Repartitioning is scary, and I'm not sure how to proceed.
[Upgrading, Modifying and Unlocking] V0latyle:
By fastboot mode, do you mean bootloader?

Here's what I would try:

Restore device to stock using factory image

Live boot TWRP from bootloader screen: fastboot boot twrp.img

Format /data

Wipe /system and /product

Install GSI image to /system

You can also try using TWRP to flash the GKI to /boot. I am not sure if TWRP automatically resizes partitions or not
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Yes, fastboot mode is bootloader. I did everything you suggested verbatim. Same results, and TWRP does not seem to resize /boot for me. The error states "Size of image is larger than target device." End result is booting back to bootloader/fastboot mode. The dm-vrity screen is not a problem with the vbmeta.img having beenflashed at some point. It doesn't seem to matter if it was flashed before or after system.img though. So EVERYTHING flashes EXCEPT the boot.img. Stock boot doesn't seem to play nice with the GSI at all.
[Upgrading, Modifying and Unlocking] V0latyle:
Hmm. There's got to be a way to get it to work, but I'm not as much of an expert as I'd like to be.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I think you are half right on being able to piece-meal the GSI and other parts like you theorize, bhut I really think it's got an a11 /boot and may need to have it updated to actually boot. I reached out to @PixelBoot about their product partition extender and what not in an effort to learn more about partitioning. My hope is that if Icanget the boot.img to flash, it might boot since everything available to be changed matches up. Also, I like screwing around with electronics, so this is fun times for me.
[Upgrading, Modifying and Unlocking] V0latyle:
I mean, I'm going on some pretty generic information, but Android Source seems to be pretty clear:

Requirements for flashing GSIs
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Just basing it on what I've read on people getting a11, and a12 to work on the 2/2xl and their problems along the way hint that the kernel has to be at least of the same android version, so I figure the boot.img is looking for the proper system.img, and finding the new flashed one, and just quitting after that. So a GSI may need a proper GKI to work in this case. SO that's why I'm chasing this partitioning option. At the very least it's something to pass boredom and fails, or at best it works and I make a write-up to post for others.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Got a boot.img file from LOS that was in the 40mb range as opposed to 64mb. Flashed successfully, and did not boot, it just boots to the bootloader/fastboot.
[Upgrading, Modifying and Unlocking] V0latyle:
Error message at the bottom?
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Nope, everything worked as expected, then after the Google screen, I got a fastboot screen instead of a splash screen.
[Upgrading, Modifying and Unlocking] V0latyle:
Look at the very bottom line of text, it should have a message saying why it reverted to bootloader. Example:

boot slot: A
Enter reason: no valid slot to boot
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Nope, no text, no info at all.
[Upgrading, Modifying and Unlocking] TheMystic:
How did you take these pictures? They look so clear like screenshots. 😀
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I was trying to upload a clip of it trying to boot... didin't work out so well
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I give up trying to upload my video of the phone, XDA just isn't having it today.
[Upgrading, Modifying and Unlocking] V0latyle:
The first one is from the Android Source page on Boot Flow

The second one I googled, I don't think it's actually from a phone

Just post a photo of the bootloader screen after it fails to boot. Make sure you blur/cover your serial number and IMEI
[Upgrading, Modifying and Unlocking] ieatabiscuit:
That's just it, there is no error shown. I can send a pic of the bootloader page that comes up, but it's just like any other time. There's just no error.
[Upgrading, Modifying and Unlocking] V0latyle:
It's supposed to tell you the reason it's in bootloader again. Weird.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
I'm going to brush up on my logcat skills later today, see if I find anything there.
[Upgrading, Modifying and Unlocking] ieatabiscuit:
Unless there is a way to get a log of some sort via fastboot, it reboots to go into recovery so that I CAN get logs, giving me nothing useful to work with. Any suggestions?
[Upgrading, Modifying and Unlocking] V0latyle:
Sorry I missed this. Moderator stuff usually gets in the way.

I don't have any helpful suggestions, sorry. Have you already talked to @badabing2003 ? If he doesn't know how to help he probably knows someone who does.
[Upgrading, Modifying and Unlocking] badabing2003:
You cannot get logs via fastboot,

In recovery, you can do adb shell, but what you get access to is questionable, /data if encrypted, which would usually be, then you would need custom recovery like twrp to decrypt it.

Perhaps there is a way, I'm just not aware of.

If I would think of a person who would be expert at this, it's probably @osm0sis
[Upgrading, Modifying and Unlocking] osm0sis:
Are you able to get the device working at all at this point? What device is it? Does Lineage support it? If so, I'd suggest following their instructions to install Lineage as shown on their wiki and if all is successful go from there.
[Upgrading, Modifying and Unlocking] V0latyle:
Forgive my ignorance, I don't see how LineageOS would help? He's trying to figure out why his device won't boot, which means that he probably wouldn't even be able to install LOS
[Upgrading, Modifying and Unlocking] osm0sis:
But seems like he broke it with an untested GSI or GKI or something right? So doing something that's known working like flashing Lineage boot, dtbo and vbmeta, then trying to use Lineage Recovery to flash Lineage would be a worthwhile exercise to see if the device is returnable to a working state.

Then, maybe, the GSI might work better over Lineage's vendor, etc. than it did over stock or whatever was on there before.
[Upgrading, Modifying and Unlocking] V0latyle:
Thing is, if he flashed the factory image in post 32, the device should have at least booted because it overwrites anything in those partitions

Or maybe I'm misunderstanding where the problem is
[Upgrading, Modifying and Unlocking] V0latyle:
So, my wife's 5a died a few weeks ago, and I purchased a refurbished Pixel 3 to use in the meantime. Now that she has a replacement 5a, I've started tinkering.

With stock boot image from SP1A.210812.016.C2:

Flashed Android 14 Preview GSI. Bootloops a few times then stops in bootloader: "No valid slot to boot"

Flashed Android 13 TQ3A, successful boot, seems to run just fine

Tried 13-5.10, 13-5.15, and 14-5.15 GKI boot images, all result in "Error boot prepare" in bootloader
[Upgrading, Modifying and Unlocking] gentle_giant:
Very interesting indeed. My Pixel 4a has reached the end of OS & Security support so I hope more people jump in. At this point in time I cannot start experimenting as it is still my daily driver. Also, I'm a big NooB but willing to take risks.
[Upgrading, Modifying and Unlocking] V0latyle:
Using Android Flash Tool to flash GSIs is pretty safe. If something doesn't work you can just flash back to stock.
[Upgrading, Modifying and Unlocking] V0latyle:
@badabing2003 I forget, is your Pixel 5 your daily driver?
[Upgrading, Modifying and Unlocking] badabing2003:
No, that is my test device.

My daily driver is p7p
[Upgrading, Modifying and Unlocking] V0latyle:
Have you given any thought towards future updates, now that our phones are officially EOL? I know we can flash GSIs (and potentially GKIs) but to get the actual Pixel experience, I wonder if we could just use the system images from newer Pixels...? I don't know how much is in /vendor and /product
[Upgrading, Modifying and Unlocking] badabing2003:
I haven't mainly because this is a test device, and my daily driver is still supported.

Once that gets to EOL, or I need to "hand me down" mine to a family member and upgrade, I'll get the next Pixel.

That's what I've been doing.

I love experimenting and learning new methods, finding enough time is always the barrier.
[Upgrading, Modifying and Unlocking] mark7807:
Really hoping to try this out in the next few days. Just tuning in.

On Pixel 4 XL, what is a version I should easily be able to upgrade from my current Android v13 setup to?

I would like to test the next version after that once I have surpassed the current public standard. I read the OP, and skimmed through most and I think I have enough BG knowledge to not worry about creating a bricked device *knock on wood*.

I don't care about having access to the newest Pixel Features and am mainly interested in pushing simply past Android 13 if that is stable and won't push me to have basic incompatibility problems. 🙂🙂

Any feedback and fast-tracking would be really appreciated
[Upgrading, Modifying and Unlocking] V0latyle:
Currently the easiest way to run something reasonably up to date is to install a GSI, but even then, there's some problems. I was able to run an Android 13 GSI on a Pixel 3; Android 14 would not boot.

You can install GSIs using the Android Flash Tool:

Generic System Image releases | Platform | Android Developers

developer.android.com
[Upgrading, Modifying and Unlocking] mark7807:
Do you need testers? Is there a chance higher versions will work?

Edit: this is my daily driver but I'm feeling risky
[Upgrading, Modifying and Unlocking] R9_Dev:
So this doesn't work? I am just curious to see how this project concludes.
[Upgrading, Modifying and Unlocking] V0latyle:
Well, the threshold for officially supported devices increases with each update. For example, Google only officially supports the Pixel 6 and newer for Android 15. I don't know what it would take to get it working on newer devices.

I haven't been actively working on it because life. My daily is a Pixel 5 running the last official update (UP1A.231105.001.B2, Feb 2024). I have a Pixel 3 I can test on but I've only been able to get Android 13 to boot on it. I myself don't have any experience or knowledge in porting kernels.

Supposedly every device released with Android 8 and since already supports Treble (modularized Android). Installing a GSI seems simple enough; getting a GKI to work seems to be a bit more involved. I'm not a developer myself so I am looking for people who are able to troubleshoot a lot of this stuff.

The bottom line goal is to develop and streamline a method by which people using EOL devices can potentially stay reasonably up to date.
[Android Head-Units] the_moom:
Hi everyone,

I've got an Junsun V1 Pro head unit with the latest firmware (8259P_军灿UI02v1280x720-国外_v50_20221226) installed in my car. Now I‘m facing an issue with my sim card for the car. When I install the sim card the first time everything works as expected. Internet is working and connection is 4G (even VoLTE). But when I turn on the head unit after standby, the connection is reestablished only with 2G (at the exact same location). The sim card is from sim.de and is operating in the O2 network and as multi card.

Tested with klarmobile sim card (Vodafone network): Every time 4G

Tested sim.de sim card in Huawei Gigacube: No problems

Checked and adjusted APN settings: No effect

Disabled VoLTE: No effect

Changed setting between 2G / 3G / 4G: No effect

Are there any known issues with Junsun and the O2 network?

kind regards

Markus
[Android Head-Units] TorstenH:
I'm using the same firmware and today I ordered an O2 SIM. I will let you know if I will run into the same problem.
[Android Head-Units] TorstenH:
You could try after sleep mode:

Disable and enable mobile data.

Enable and disable flight mode (maybe via search function in settings app).

Does it help to bring 4G back?
[Android Head-Units] the_moom:
No, unfortunately not.

Yesterday I tried to increase the pressure on the sim and added a small piece of cardboard. It worked the whole evening, even after standby. But today it stopped and is back to 2G.
[Android Head-Units] TorstenH:
Unfortunately my SIM card still not arrived so I can't tell you if it works on my device / with my O2 SIM.

I can't imagine that it's a topic of bad electronically contact because the issue only occurs after sleep mode.

One possibly could be to compare the units processes before and after sleep mode.

1. Stop all apps to avoid unneeded programs occure in the list

2. List all processes running

3. Put the unit in sleep mode and wake it up

4. If you only have 2G list all running processes again

Maybe a service doesn't comes up after sleep mode which is relevant for 4G data connection.
[Android Head-Units] TorstenH:
I added the SIM card today and two reboots were required to get 4G.

I put the device into sleep mode (just a few minutes) and had still 4G.

Let's see how it is after a long sleep...
[Android Head-Units] the_moom:
Does it work?
[Android Head-Units] TorstenH:
It works (not always).

This morning after wakeup the head unit displayed "no sim card" on the bottom of the mobile data icon in status bar.

After reboot it worked fine, so it was not a contact problem of the sim card holder...
[Android Head-Units] TorstenH:
I found this:

Post in thread 'Auto-toggle SIM card (e.g. with Tasker, adb shell)' https://xdaforums.com/t/auto-toggle-sim-card-e-g-with-tasker-adb-shell.3656963/post-73482775

This may be an approach to disable/enable the Sim. If you're willing to test I can write a small app doing the job.
[Android Head-Units] TorstenH:
After serveral days usage I have exactly the same issue:

After (longer) sleep only EDGE or even message "no Sim".

Changing mobile data settings or changing to flight mode not bringing back 4G. Reboot is the only way to get 4G again.

I don't think it's hardware related because it works after reboot without touching the Sim card dongle.

I will investigate the Android log. @the_moom you may want to do the same?! Four eyes may see more that two.
[Android Head-Units] TorstenH:
I compared the running system services after sleep and after reboot. Found no difference...

So next step is to check logcat...
[Android Head-Units] TorstenH:
It may help to restart the RIL daemon...

adb shell stop ril-daemon

adb shell start ril-daemon

I will test this tomorrow...
[Android Head-Units] TorstenH:
Restart of vendor.ril-daemon-mtk isn't sufficient.
[Android Head-Units] le_mi:
Is the SIM protected by PIN?
[Android Head-Units] TorstenH:
I switched off the "pin required" setting. Or is there are way to remove the pin from the card?
[Android Head-Units] le_mi:
I had put the SIM in the smartphone at the beginning and disabled the PIN.
[Android Head-Units] TorstenH:
As it's done in this video? Or is there another way?
[Android Head-Units] le_mi:
Correct in this way.
[Android Head-Units] TorstenH:
I used this setting - but directly on the head unit.
[Android Head-Units] le_mi:
Well then i think this is not the reason for the issue.
[General Questions and Answers] TheMystic:
The Google recorder apk (v2.0.335078816) with offline transcription installed and runs fine on my Samsung Galaxy S22 Ultra.

However, the same apk refuses to even install on my OnePlus 8T.

I tried installing with SAI, and this is the error I get: see attachments.

Both devices are running on Android 13 (OneUI 5.0 and OOS 13 respectively).

The older version (v1.0.271580629) of the same recorder installs fine on the OP8T. This version doesn't have the transcription feature.

Can anyone point out what this error is and how to solve it?

Or is there another version of Google's Recorder that works on OnePlus devices? If so, please provide a safe link.

Thanks.
[General Questions and Answers] TheMystic:
Tried disabling both Google Play Services (and Google Services Framework) and Google Play Store and rebooted the phone. But still same error.
[LineageOS Questions & Answers] MrSundei:
Hey!

I previously found my old Huawei Y6 (2018). How can I install LineageOS to it?
[LineageOS Questions & Answers] SigmundDroid:
Generally, find (or build) the ROM for it.

You might find one here:

https://xdaforums.com/f/huawei-y6-roms-kernels-recoveries-other-devel.6520/

(Had a brief look but couldn't find anyhting newer than LOS15/A8)
[Windows 11] jenneh:
Hello Friends,

Today I wanted to write a guide about how to use the LSPosed Github Repo on a linux machine to build your desired flavor of WSA with GAPPS and Root.

If you do not already have a Linux machine or WSL, I have a fully built and ready to go machine for you here. See the prebuilt spoiler. I am using this exact machine in the video and begin the video by showing how to add the machine to VMWARE WORKSTATION 17

On your linux machine, run these commands

sudo apt-get update
sudo apt install git adb
git clone https://github.com/LSPosed/MagiskOnWSALocal.git
cd MagiskOnWSALocal/scripts
./run.sh

When the machine is finished downloading the dependencies, you will be greeted with a series of choices, you may choose what you like

Spoiler content hidden.

When it is finished building the zip file for us, it will be located in the output folder. Copy that zip to your Windows desktop.

Make sure to Uninstall your old version of WSA if you already had one installed. then extract the new WSA and execute run.bat. You may have to execute run.bat another time if your machine requires reboot.

The playstore should appear after the windows dependencies are installed, and allow you to login at this point

Spoiler content hidden.

Now open windows subsystem for android and select the developer tab, turn on developer options.

Spoiler content hidden.

Spoiler content hidden.

Now go into the same folder as your magisk apk or any apk you want to install and open command prompt, run:

adb connect 127.0.0.1:58526
adb install magisk.apk

or change magisk to your apk's name.

Now you have full root with playstore on WSA!

If you want a copy of the Rooted WSA I built in the video, it can be located here (This copy is Retail - Android 12 w/ Playstore):

wsa.zip (839M)

If you download this you can skip the Linux steps and jump right to the run.bat step (skip to 2:39 in the video)

If you need to run more than 1 Android emulator at a time -- using Nox (they are still at android 9 and you can choose 7)
[Windows 11] xXx yYy:
WSA with Android 13 is already available.
[Windows 11] jenneh:
@xXx yYy The post was made to show how to make the wsa of choice (android 13 included) and I only shared a premade android 12 image for choice since android 13 premades are everywhere and some people need certain firmware for certain reasons. Cheers To choices!

--Dunno why my phone bolded that
[Windows 11] jenneh:
As an update-- the installing magisk apk part is redundant. I didn't realize it already literally had the apk installed too and not just patched the boot. The devs of this repo did a good job! I'll just leave that info up in the post for knowledge's sake (ie those that didn't know how to install apks on wsa to begin with) but know that you're done after you make your zip and run the batch file
[Windows 11] Scholeggo:
If I run all these commands again when a new Android version releases, will it preserve my data or wipe it?
[Windows 11] jenneh:
@Scholeggo I am not sure, but you could ask on the discussion tab of the lsposed repo and maybe one of the developers could answer for sure. They seem to be active in answering community questions https://github.com/LSPosed/MagiskOnWSALocal/discussions
[Windows 11] tithitoy:
I have problem when build WSA. Please help! thanks

View attachment 5906443
[Windows 11] supermansaga:
A great tool for sure, but have yet to support choosing diff pixel devices. Default is pixel 5. I was told that is just cosmetics, but I have to wonder if they have ever experienced Pixel 7 Pro which only has 64 bit.

The tool can't pass safety net, even if one later applies Displax tool, Shamiko etc. Unfortunate.

It's also hard to feel what Android 13 is like there. The only thing I was told was look at the WSA number. 2305 has got to be Android 13 now, but I still can't feel it
[Windows 11] supermansaga:
Does 2308 WSA work these days? I can't seem to finish the whole execution. There is always some sort of errors. Thx
[Windows 11] supermansaga:
solution: https://ahaan.co.uk/article/top_stories/google-play-store-windows-11-install, though installing Magisk module no longer seems to work
[Windows 11] Badger50:
@jenneh

Thread closed at the OP's request