Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research about modifying your android system before flashing this!
* YOU are choosing to make these modifications, and if you point the finger at
* me for messing up your device, I will laugh at you. Hard. A lot.
*/
(if you expected the Resident Evil references to stop, you just got gnomed)
What is this?
T-Virus (for treble-virus) is a tool that takes a stock Nokia 8 firmware and "infects" it with various parts from the Nokia 8 Sirocco firmware, generating a firmware bundle that is compilant with Project Treble and that can be flashed to a Nokia 8 using NOST.
Firmware Sources
The base of T-Virus is the stock Nokia 8 firmware image (5150 / April Security patch at the time of writing). When being run, the build script takes those files and replaces the partition table with the one from Nokia 8 Sirocco. This required for creating a vendor partition that the stock Nokia 8 does not have. The vendor image is taken from the Sirocco firmware as well. During the build, the vendor image is mounted as rw, and various files are copied over from the stock Nokia 8 system image, or get patched to properly support the minor hardware differences between the two phones. Those actions are defined through very basic scripts inside of the vendor folder in the repository.
The boot image is a modified version of my umbrella kernel, which has support for early mounting vendor. It also includes a TWRP build with full support for Project Treble.
SELinux Hell
Because Android does some very weird stuff with SELinux contexts, you cannot launch a service file when it has an unknown context. We have to fix that by force-setting the SELinux context manually, but due to how SELinux works, this is only possible on a Linux system without SELinux. This means, that you cannot build this on a distribution with SELinux (Fedora in my case). I fixed the problem by building the images in a Ubuntu VM.
How to build?
First you have to download the latest firmware image from https://tmsp.io/fs/xda/nb1/firmware, and the exdupe tool from https://www.quicklz.com/exdupe
Extract the firmware into a folder and then clone the repository, like this:
Code:
$ mkdir firmware
$ ./exdupe -R ~/Downloads/NB1-5150-0-00WW-B03.qlz firmware/
$ git clone https://github.com/resident-nokia/t-virus
$ cd t-virus
The build script has two options you have to set: a version and the path to the extracted firmware. This means you have to run it like this:
Code:
$ ./build.sh --version v0.1 --firmware ../firmware
Leave it running and when it asks you, enter your sudo password. This is required to mount the Android ext4 partitions and edit the files that are only accessable by the (Android) root user, and retain their permissions.
When the script has finished the flashable firmware image will be inside of the out folder. You can optionally package this as a .qlz file again using exdupe.
What works?
It boots
Data decryption in recovery
Flashing GSIs / OpenGApps in recovery
WiFi
Mobile Data
Bluetooth
Sound
Vibration
Calling
Hardware buttons
Fingerprint
Camera
GPS
NFC
SDCard
Multi SIM
4k Video
What doesn't work, or isn't tested
Haptic feedback for Hardware buttons
Bluetooth headphones don't get registered properly
Nokia OZO audio support is missing
Fingerprint sensor is reported as being on the back of the phone
There might be issues with USB transfer under Windows
VoLTE (untested)
How to install?
WARNING: This might not be useable as a daily driver. Continue only if you are able to troubleshoot things if neccessary (bootloops, bricking the phone, causing the alarm app to declare nuclear war)
You can download the latest release from the releases page on the repository. It is a .qlz firmware, so you will have to flash it through NOST. You will need a completely unlocked bootloader. When flashing, make sure to select the "Erase Userdata" option, not doing this will most certainly bootloop the phone.
After the installation completed, your phone will reboot into phh's AOSP GSI. If you want to use a different GSI (you most likely will), follow these steps:
Download your favorite GSI
Unpack every form of compression, so you end up with a .img file
Boot into recovery
Copy the .img to the internal storage of your phone, or to your SDCard
Select "Install" -> "Install .img", select the image file you copied and flash it to your system partition
Then install OpenGApps or any other modifications you like.
Wipe /data to allow the new system image to boot properly and then reboot
To update to a newer version without having to erase userdata, download the zipped vendor image from the release page, and flash the image inside in TWRP.
If you want to go back to stock, simply download the 5150-revert firmware and flash it with NOST, with the "Erase Userdata" option enabled. It will revert all changes T-Virus made to your phone. Firmwares from https://tmsp.io/fs/xda/nb1 will not work.
Links?
Repository: https://github.com/resident-nokia/t-virus
Download: https://github.com/resident-nokia/t-virus/releases
Reverting to stock: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert
What if I have a bug?
Upload a proper bugreport. This means logcat and dmesg. If you don't know how to get them, google it. Also, describe the issue and provide steps to replicate it. Everything else will be ignored.
I don't daily drive this phone anymore. I am doing this just because it is an interesting technical challenge. I don't have as much motivation to fix bugs than someone who daily drives it.
I want to say thank you!
I usually don't do this, but since this involved a lot of work on my side, I would be grateful if you would want to say thank you by buying me a coffee (or two): https://paypal.me/thmsp
Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?
kosmatyj said:
Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?
Click to expand...
Click to collapse
The ability to install GSIs (Generic System Images). Basically everything from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Oh! Sounds pretty good! Thanks. Will think about it. Really expands posiibilities and needs to be tested.
---------- Post added at 10:54 ---------- Previous post was at 10:29 ----------
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?
kosmatyj said:
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?
Click to expand...
Click to collapse
It could work, since it is a modified firmware for reflashing, but just to be sure, update to Pie through OTA. That's what this has been tested with and you won't update your bootloader in the process which eliminates some possible incompatibilities.
What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?
kosmatyj said:
What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?
Click to expand...
Click to collapse
It's all in the instructions. There is no password on the qlz file. You can't extract it, you have to flash it using NOST. The zip is for updating from previous versions and not for the initial installation.
Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.
kosmatyj said:
Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.
Click to expand...
Click to collapse
Yes. Just follow the instructions in NOST and select the T-Virus .qlz when it asks you to. Also, make sure you select the "Erase Userdata" option in the drop down menu that appears after selecting the .qlz.
Thank you for this - hope you enjoy the couple of coffee's
Amazing work. Can the current Android Q GSI be used?
comatrices said:
Amazing work. Can the current Android Q GSI be used?
Click to expand...
Click to collapse
When I tried it it didn't boot. Your mileage may vary, but you probably have to wait until the source code for Q has been published and people can build real phh GSIs from it.
Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.
kosmatyj said:
Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.
Click to expand...
Click to collapse
Just flash an Oreo GSI? I know you can run Pie GSIs on Oreos vendor, so it should work fine the other way around.
Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).
kosmatyj said:
Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).
Click to expand...
Click to collapse
I am not exactly sure if I understand you correctly, but Nokia 8 is not an A-only device, it is an AB device. You need to flash the AB image of AOSP, not the A one.
Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.
kosmatyj said:
Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.
Click to expand...
Click to collapse
Ok, then it probably doesn't work the other way around (Oreo with Pie vendor). An Oreo-based T-Virus is unlikely to happen though, because Siroccos Oreo vendor has some problems (calls not going through properly), and I dont want to maintain two versions of it because, as said in the OP, I don't use my Nokia 8 anymore. It seems like Pie is all you can get with this for now, sorry.
Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i miss something? Whats with Security Enabled Linux?
just4me12 said:
Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i missed something? Whats with Security Enabled Linux?
Click to expand...
Click to collapse
That's right. Don't forget to add "erase data" option while flashing t virus with NOST otherwise you'll end up in a bootloop.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
What's working?
Everything as far as I can tell...
Installation
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads: http://1pwn.ixmoe.com/android/ginna/los-18.1/lineage-18.1-20210621-HOMEMADE-ginna.zip
Notes
This ROM comes with Google Apps!
This ROM comes with Customizations that are not apart of LineageOS
Sources: https://github.com/motoe7
Credits: @electimon, @RohanHasabe8, betaxab
Jan 27 2021: Fix Safetynet, fix touch issues, fix some other issues
Jan 28 2021: Fix PIP mode
Jan 30 2021: Fix Hotspot
June 2 2021: Fix touch for ginna models with the new panel
June 15 2021: Fix touch for focaltech panels
June 20 2021: June Patch, fix safetynet and other little stuff
Awesome, been waiting for this, thanks very much! Had some errors while loading copy-partitions.zip but the image flashed and seems to be working well. Look forward to future versions with SELinux enforcing and also without gapps (but maybe that's not likely with no opengapps for 11?)
Would be great if there was a way to remove the obtrusive "device can't be trusted" message at boot. It can be just as trusted as my desktop PC ffs. At least moto allows the bootloader unlock without much trouble.
anthony.d said:
Awesome, been waiting for this, thanks very much! Had some errors while loading copy-partitions.zip but the image flashed and seems to be working well. Look forward to future versions with SELinux enforcing and also without gapps (but maybe that's not likely with no opengapps for 11?)
Would be great if there was a way to remove the obtrusive "device can't be trusted" message at boot. It can be just as trusted as my desktop PC ffs. At least moto allows the bootloader unlock without much trouble.
Click to expand...
Click to collapse
hi, selinux is enforcing also there will be no version without gapps sorry
Electimon said:
hi, selinux is enforcing also there will be no version without gapps sorry
Click to expand...
Click to collapse
No worries about the gapps, i'm grateful to have a lineage rom for this device.
I tried flashing again. Pardon if the details below are excessive, I don't fully understand the process, and the dual-slice device config. Here's what happened:
copy-partitions gets to 47%, then fails with the following error:
Partition vendor_a
dd: /dev/block/dm-4: write error: No space left on device
installed lineage again, this time went to slot B. rebooted back into TWRP and tried copy-partitions again (to see if it was different after lineage had been installed in both slots) and this time it succeeded. Installed lineage again, this time to slot A. Wiped the device, rebooted, and I still get the selinux error. If it's relevant, the device model is XT2052-1.
Also want to add: I applied disable-verity both times, and cmd line output indicated writing to vbmeta_a and vbmeta_b.
weird, how are you checking for enforcing?
android_device_motorola_ginna/BoardConfig.mk at efea8269c9a6a232d8ba38b0629a61eb590b2db5 · motoe7/android_device_motorola_ginna
Contribute to motoe7/android_device_motorola_ginna development by creating an account on GitHub.
github.com
you can see here that permissive is commented out, the rom is enforcing.
I installed the rom mainly as a reference against the no speaker (except in calls) issue I'm having with 17.1. Also I'll note there the issue isn't jacksensing as I had guessed. A soundfile playback autopauses on headphone removal. With 18.1 here I do get speaker output, however one bug I noticed for me (boostmobile-sku:mot20526anb/xt2052-6) (also present in 0206 17.1) is that in-call volume adjust doesn't work. The indicator moves, but the actual volume does not. I'll send some logcats. Seems to be stuck at what is probably supposed to be max volume.
Electimon said:
there will be no version without gapps sorry
Click to expand...
Click to collapse
Is there a standard/safe way to uninstall gapps via scripted adb commands immediately after install? I experimented with a crude attempted pm uninstall/disable/disable-user of all com.google.* packages but was not too surprised when the result failed to boot past the lineageos boot animation.
Cyb3rSl4v3 said:
Is there a standard/safe way to uninstall gapps via scripted adb commands immediately after install? I experimented with a crude attempted pm uninstall/disable/disable-user of all com.google.* packages but was not too surprised when the result failed to boot past the lineageos boot animation.
Click to expand...
Click to collapse
I'm unsure of that
I finally figured out how to build 18.1 on my 8g-ram system such that I don't have to worry about uninstalling gapps (amongst other motivations). I'll post details once I've done another less manual build. The trickiest part was that the 17.1 workaround of setting JAVA_TOOL_OPTIONS/_JAVA_OPTIONS to -Xmx6g wasn't getting used by metalava in 18.1. I ended up editing the last line of out/soong/host/linux-x86/bin/metalava and putting it in there which finally worked. Perhaps tools/metalava/gradle.properties is the right place. My first pass doesn't have carrier data/call service working, but that may be because I did something with TimeService to get it to compile. In any event, I think the 16g minimum warning from the build system is more than a bit confusing combined with the metalava java heap issues. I may try a 4g-ram build sometime just for amusement... It just seemed inconceivable that there really was a 16g-ram requirement. I know even phones come with 16g these days, but still. Of course my hope is to see a cheap phone of mine self-hosting one of these days. Perhaps with some high end microsd card or an otg drive for swap partition and build tree...
Cyb3rSl4v3 said:
I finally figured out how to build 18.1 on my 8g-ram system [...] The trickiest part was that the 17.1 workaround of setting JAVA_TOOL_OPTIONS/_JAVA_OPTIONS to -Xmx6g wasn't getting used by metalava in 18.1. I ended up editing the last line of out/soong/host/linux-x86/bin/metalava and putting it in there which finally worked. Perhaps tools/metalava/gradle.properties is the right place.
Click to expand...
Click to collapse
I haven't quite done a fully automated build yet, but tools/metalava/gradle.properties didn't work for me. Then I found that the metalava (wrapper) script was build/soong/scripts/jar-wrapper.sh, and adding a next to last line of-- javaOpts+=("-Xmx6g") --seems to work. I also now better understand device/motorola/ginna/lineage.dependencies and seem to be able to reproduce this image sans gapps (though an selinux issue i haven't looked too much at yet). I may focus more on 17.1 until 18.1 becomes more generally official. I also seem to be getting occasional sigsegvs with jre/metalava dumping hs_err_pid*.logs. However thus far a simple rerun of brunch/ginna has never reproduced the problem.
Camera apps have quite a lag related to camera apiv2. Haven't had time to debug, but Open Camera works perfect as it defaults to the old api.
Do we have system read/write on these builds and does magisk work?
Idk about system r/w, but Magisk works fine. This is also a really good rom. Stable and nearly everything works.
fddm said:
Idk about system r/w, but Magisk works fine. This is also a really good rom. Stable and nearly everything works.
Click to expand...
Click to collapse
I checked, it has system rw. I can't believe how fast my LTE speeds are too. 7-10MBs vs 50kbs on stock. The only thing holding me back is no full screen toggle for apps, and the in call volume is stuck at the maximum at all times. Soon as those get fixed I'm running this 24/7.
2+ months now with 18.1 on my daily driver.
No hardware issues.
Ofox recovery.
Magisk 21.4 thru the latest canary build have worked as far as I can tell.
No volume troubles.
Can mount system RW.
My only setback is that I don't have access to around 9Gb on /data and /sdcard, including /sdcard/Android/obb
I can set perms any way in terminal and in recovery terminal 0777, 0655, etc., but upon reboot, I cannot read or write.
Can read and write to /system and /system_root, no problem.
This is possibly due to me forgetting to wipe encrypted /data after first flash? I wiped after first boot, no change.
Then, started the flash process from scratch and wiped before first boot, but must have missed something.
The file and folder names are not random characters.
One of those things I thought will work out when I get around to it, but now just found my pics are being saved to a folder in the mystery space, and I need to place a .zip in *./obb.
Im learning, A/B is new to me.
Maybe my mistake will help someone when I find a solution.
I am open to suggestions, lessons, and any other info, even if I should already know it.
I will report when something changes.
RaceyMcRacerson said:
2+ months now with 18.1 on my daily driver.
No hardware issues.
Ofox recovery.
Magisk 21.4 thru the latest canary build have worked as far as I can tell.
No volume troubles.
Can mount system RW.
My only setback is that I don't have access to around 9Gb on /data and /sdcard, including /sdcard/Android/obb
I can set perms any way in terminal and in recovery terminal 0777, 0655, etc., but upon reboot, I cannot read or write.
Can read and write to /system and /system_root, no problem.
This is possibly due to me forgetting to wipe encrypted /data after first flash? I wiped after first boot, no change.
Then, started the flash process from scratch and wiped before first boot, but must have missed something.
The file and folder names are not random characters.
One of those things I thought will work out when I get around to it, but now just found my pics are being saved to a folder in the mystery space, and I need to place a .zip in *./obb.
Im learning, A/B is new to me.
Maybe my mistake will help someone when I find a solution.
I am open to suggestions, lessons, and any other info, even if I should already know it.
I will report when something changes.
Click to expand...
Click to collapse
I never had this issue so I'm guessing it's something to do with encryption. I would try clean flashing LOS to both slots then formatting data using the type "yes" option to remove encryption. Are you using adoptable storage by chance?
How can I install this rom via recovery, I have never used side load. Why is it not booting? What is wrong. I flashed rom in slot B with twrp in slot A sorry still a little new with this device. But regardless it is not booting whatsoever and I am confused as to why
Mr.Conkel said:
How can I install this rom via recovery, I have never used side load. Why is it not booting? What is wrong. I flashed rom in slot B with twrp in slot A sorry still a little new with this device. But regardless it is not booting whatsoever and I am confused as to why
Click to expand...
Click to collapse
Flash it to both slots and format data before booting up.
Spaceminer said:
Flash it to both slots and format data before booting up.
Click to expand...
Click to collapse
Is there any benefit of having it flashed to both? Cause I did get it working. There's not currently anything on slotB
Mr.Conkel said:
Is there any benefit of having it flashed to both? Cause I did get it working. There's not currently anything on slotB
Click to expand...
Click to collapse
Not that I'm aware of. I've never got it to boot without flashing to both slots though. Did you use the zip, or fastbootd images?
First You Need an unlocked bootloader there are many guides to unlock the bootloader on Samsung devices I recommend this one Unlock Guide
Once you have an unlocked bootloader we can proceed
1: Flash Twrp if you don't have it already: Snapdragon Twrp Or Exynos Twrp Download The Twrp For your device Model And Also Download Vbmeta Disabled, Reboot Into Download Mode By Pressing Volume Up And Volume Down When Booting The device
Download Odin and Samsung Drivers On your Computer Odin And Samsung Drivers
After You have Odin And Samsung Drivers, Open Odin and On the AP Section Select The Twrp You downloaded And On the Userdata Section Select The Vbmeta Disabled You Downloaded , GO TO OPTIONS AND DISABLE AUTO REBOOT!!!, Press The Start Button and once it Finishes, You Should Press The Power Button And Volume Down And When It Starts To Reboot Press The Volume UP And Power Button If you Did it right you Should Boot Into Twrp
2:
On Twrp Go to Wipe > Format Data > Type Yes (This will WIPE ALL DATA ON THE DEVICE!!!)
Then Go to Reboot > Recovery
After It reboots Go to Reboot > Fastboot
Download Adb On your Computer Adb Download And extract it into a folder, Then Press Shift On your Keyboard And Right Click At the same time Select The "Open Command Prompt Here" Option, You should see A command Prompt
Now You need To Download The Gsi You want to flash, (You can Find Many Gsi In the s20 fe Gsi's Group Here) Or you can Also Check Treble Gsi's Group
(Roms Based on Older PHH Patches than v303 Will not work)
Once You have the Gsi you want to flash Copy it into the adb folder And Also RENAME THE FILE to sys.img
Now On the Command Prompt You can Run > fastboot flash system sys.img
(If You Cant Get Your Drivers Working i recommend Trying ubuntu Because it has Drivers Pre Installed)
If you Dont get any errors then you are Good Reboot your device and you should see the gsi is installed
Fixing Rounded Corners:
Reboot Into Twrp And Open Adb On your computer
Download The Overlay and place it in the adb folder
Run ( adb shell mount /dev/block/dm-1 /vendor )
Then Run ( adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk )
Then ( adb push treble-overlay-samsung-rq8.apk /vendor/overlay )
Bootloop Problems:
You may have a bootloop If you are using A newer Vendor
This Was Tested On the one Ui 3.0 Vendor I Recommend Downgrading to 3.0 Vendor If you can
!!! I am not sure if its working on one UI 3.1 Vendor !!!
(Vendor is the one UI version you have)
Magisk:
To flash magisk you need some special Instructions, !!!Without them flashing magisk will result in a bootloop!!!
They are a bit complicated and you can find them Here (I don't recommend Using Magisk With Gsi's)
Issues?
Current issues are: 60fps Video Recording, Fingerprint Sensor And MTP
Fingerprint Might be fixed On android 12!!!
IF YOU ENCOUNTER PROBLEMS JOIN THE S20 FE HELP GROUP Here
(THIS WAS ALL TESTED ON SNAPDRAGON I AM NOT SURE IF IT WORKS ON EXYNOS)
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
3mel said:
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
Click to expand...
Click to collapse
no, you can fix magisk but its a bit hard, And yes you can pass safetynet with magisk, Some roms like pe+ Can pass safetynet without it tho
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Kolyei said:
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Click to expand...
Click to collapse
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
3mel said:
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
Click to expand...
Click to collapse
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
any hardware OEMs add has supposed to have been functional for the last 3 years. they control their vendor layers which should work seamlessly with the OS layer. I'm paraphrasing the xda page that introduces treble and Phhuson.
OEMs have little interest in making treble work as it does nothing for them (they think). if google support was the reason 60fps would work for video recording but it doesn't.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
it was android 11 that broke it lol, on a10 it was fine
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
3mel said:
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
Click to expand...
Click to collapse
i never had any issues in one ui and i also dont on gsi
Does doing this guide trip Knox on the phone?
pOLLYpOCKET said:
Does doing this guide trip Knox on the phone?
Click to expand...
Click to collapse
yes, if you unlock your bootloader it trips knox
how can i found vbmate file for fold 2 ?
rowihel2012 said:
how can i found vbmate file for fold 2 ?
Click to expand...
Click to collapse
Do not install a gsi on the fold, it will be horrible as stock android has bad support for folding devices
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
sounds like a question for the mighty phhuson and friends
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
try this instead adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk
For me fixing round corners disabled nav buttons and when choosing gestures as nav keys only swipe up for home gesture works back button is broken
are you using a 3rd party launcher ? navigation gestures are or were supposedly broken on 3rd party launchers regardless of which rom you're running.
no, im using quick step. But even with gestures disabled i dont have any buttons
Android 13 Developer Preview 1 horror story: If you can't unlock your bootloader, you shouldn't run especially so early in development versions of Android, because there's nothing you can do to fix it once you've "upgraded" to a newer version of Android, except wait for the next Developer Preview or Beta (or closer to release, Stable).
Deep Dive on Twitter:
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
Click to expand...
Click to collapse
Deep Dive in BLOG format:
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Here there be dragons. I am not responsible for anything at all.
Note the warning in the article:
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
Click to expand...
Click to collapse
TL;DR:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
The recommended way to flash Android 13 to a Pixel device is to use the Android Flash Tool.If you'd rather flash your device manually, you can get an Android 13 system image for your device on the Pixel downloads page. See the general instructions on the downloads page for how to flash a system image to your device. This approach can be useful when you need more control over testing, such as for automated testing or regression testing.Be sure you're using the latest SDK Platform Tools and Google USB Driver.For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
How to install Android 13 on Google Pixel and other Android devices:
February 10, 2022 1:00pm Skanda Hazarika
How to install Android 13 on Google Pixel and other Android devicesAndroid 13 is making its first appearance today. The flashaholics will be delighted to know that Google has already made the system images available for download. You can give it a shot right now if you’ve got the right hardware, but there aren’t as many supported devices this time around. All you’ve got to choose from are the Google Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, and the Pixel 6 Pro.
The first developer preview of Android 13 is, of course, rough around the edges, so Google doesn’t want to make it too easy to install it on your daily driver. You’ll need an eligible Pixel smartphone with an unlocked bootloader to flash the system image using your computer. There are also OTA files, which update your Pixel to the Developer Preview without an unlocked bootloader. However, you still need to manually sideload the OTA package.
Apart from device-specific firmware packages, Google has also published the first Developer Preview build of Android 13 as a Generic System Image (GSI) that can be flashed on a much wider range of devices. Google validated them on the aforementioned Pixel smartphones, but they should technically boot on any Project Treble-compatible device.
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
The three methods to install the update are:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
Method 1: Sideload Android 13 via Recovery and ADBTo install the Developer Preview, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader.
Download the update .zip file on your computer from here. For convenience, you can rename this file to a simpler name and place the file in the directory where ADB is located on your computer.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run the command:adb reboot recovery
Your phone should now be in Recovery mode.
On your phone, select the option Apply Update from ADB.
On your computer, run the command:adb devices
This should return a device serial with the “sideload” next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:adb sideload "filename".zip
The “filename” part is to be replaced with the name of the file downloaded in Step 1.
The update should install on your phone. Once the installation is complete, choose Reboot system now on your phone to reboot into Android 13.
Method 2: Flashing full Factory Image via FastbootIf you have an unlocked bootloader on a Google Pixel device, you need to flash the factory image of the Android 13 Developer Preview via Fastboot. Usually, this is done through a flash-all.sh or flash-all.bat script file that is included in the downloaded file, but its default configuration also wipes the device completely. You can, however, retain your data by deleting the “-w” wipe attribute from the command within the script.
Download the factory image .zip file on your computer from here.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files onto your ADB and fastboot folder on your computer for convenience.
Optional: The resultant files would contain a flash-all.sh or flash-all.bat script file. Using a text editor, open the flash-all.sh if you’re on macOS/Linux or the flash-all.bat script file if you’re on Windows. Find and remove/delete the -w flag in the fastboot update command. This will skip the data wipe for your phone. To avoid compatibility issues, a data wipe is recommended though.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
On your Mac/Linux PC, run:flash-all
This command executes the flash-all.sh script file, which will then install the necessary bootloader, baseband firmware, and operating system. If you are on Windows, you can simply double click the flash-all.bat file.
Once the script finishes, your device will reboot into the new OS.
Method 3: Install Android 13 GSIEven if you don’t own a compatible Pixel smartphone, you can still install Google’s official GSI binaries to test Android 13, provided your device is compatible with Project Treble. You also need an unlocked bootloader. The last thing that we need to say is that flashing a GSI will require you to factory reset your device, so be sure you’re prepared to lose app data before you proceed with this! We recommend you make an off-device backup (such as on your PC or an SD Card) in case anything goes wrong.
Download links for the official Android 13 Developer Preview GSIs can be found here. You should download the appropriate version based on your device’s architecture. To see which architecture your device has, run the following command:adb shell getprop ro.product.cpu.abi
Optional but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files (system.img and vbmeta.img) onto your ADB and fastboot folder on your computer for convenience.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
As mentioned earlier, the bootloader of the target device must be unlocked beforehand.
Next, we need to disable Android Verified Boot (AVB). To do that, run the following command:fastboot flash vbmeta vbmeta.img
Optional but recommended: Enter the following to wipe the system partition:fastboot erase system
Flash the Android 13 GSI:fastboot flash system system.img
Allow the image to flash, it could take a few minutes. Once that’s done, wipe the userdata partition:fastboot -w
Finally, reboot your device:fastboot reboot
Hopefully, your device should boot into the new build of Android.
Click to expand...
Click to collapse
How to download Android 13 for Google Pixel and other Android devices:
February 10, 2022 1:07pm Skanda Hazarika
How to download Android 13 for Google Pixel and other Android devicesGet ready to dig into Android 13! While we are still waiting for Android 12L to be officially released via stable channel, the next major release of Google’s OS is now available starting today in the form of the first Android 13 Developer Preview. For lucky owners of the Google Pixel 6, Pixel 6 Pro, Pixel 5a, Pixel 5, Pixel 4a 5G, Pixel 4a, Pixel 4, or Pixel 4 XL, you’ll be among the first users to see what Android 13 “Tiramisu” has to offer.
Notably, existing Android beta participants won’t automatically get the first Android 13 Developer Preview as an over-the-air update. The preview release must be manually sideloaded. You can learn how to install Android 13 on Google Pixel smartphones and other devices by visiting our dedicated guide here.
Keep in mind that the initial build won’t give you the full Android 13 experience as it’s very much a work-in-progress. This first preview is aimed solely at developers, since they need to test their apps against new Android platform APIs months before the next Android version becomes available for the general public. Installing the Developer Preview on your daily driver isn’t recommended, as you might face various system instabilities. Do back up your data before proceeding.
This page will serve as a one-stop download index for every Android 13 build released by Google. We will keep the page updated with the latest OTAs and factory images for the supported Pixel smartphones.
Navigate this page:
Download Android 13:
Developer Preview 1
Download Android 13 for Google Pixel devicesAndroid 13 Developer Preview 1For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
Additionally, Google offers ready-to-use Android 13 Developer Preview system images under the Android Emulator in Android Studio.
Click to expand...
Click to collapse
Three separate branches in a single week. Wow.
Time to check the modem again lol. Probably older than 12L and we flash on top.
LLStarks said:
Three separate branches in a single week. Wow.
Time to check the modem again lol.
Click to expand...
Click to collapse
Good luck! As always, please let us know your thoughts (goes for anyone who tries it). I'll likely be sticking to regular 12, at least until closer to when 13 releases, unless I hear about some stupendous new feature that I want to try.
Edit: Maybe I misremembered which release was going to be Android T (so great, both 12 and 12L are S). Old: Now, I thought I heard reference to 12L being Android T (as it should be since it's a new API level), so 13 should be U. My wife suggests Upside-down Cake. Any other better ideas? I'm sure someone's got to have a better idea.
Modem is newer than Feb but older than 12L. Bootloader is version 1.2 compared to 1.1 in 12L and 1.0 in Feb.
Mixed bag. Need to see what 13 modem is capable of (i.e. VoNR, C-Band, etc).
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
LLStarks said:
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Click to expand...
Click to collapse
Are you using the latest stable Magisk?
As for root, just flashing a patched boot image?
I always use the latest alphas for Magisk and patch my own files.
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
Click to expand...
Click to collapse
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Thanks! Adding to the OP.
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
hooutoo said:
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
Click to expand...
Click to collapse
Good question or observation. Indeed, it appears XDA's article references things that don't seem to be available, or at least their link to where it claims it is available doesn't lead to anything obvious. But I think it's just confusing, at least to this non-developer (me).
I think they're merely reflecting the official information Google gives, which also leads to a dead-end regarding GSI versions:
This search https://www.google.com/search?q=and...69i57j0i390.4224j0j7&sourceid=chrome&ie=UTF-8
led me to the 3rd or 4th search result "The first developer preview of Android 13" at https://android-developers.googleblog.com/2022/02/first-preview-android-13.html#:~:text=For even broader testing, GSI images are available, and their statement is the same:
If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. For even broader testing, GSI images are available.
When you’re set up, here are some of the things you should do:
Click to expand...
Click to collapse
The link at "set up" leads to Set up the Android 13 SDK, which includes the step of using Android Studio.
Since at the first search I give above, the 2nd or 3rd search result Generic System Image releases doesn't have anything for Android 13 (but it does mention 12L), in the end I believe that one or both of the following are true:
GSIs are only available for Android 13 through the Android Studio - i.e. to emulate a device running the Android 13 GSI.
and/or
They goofed up and included language that made it sound like GSIs are available to actually download and flash on physical devices, perhaps in preparation for when they do intend to have the GSIs available later in the development process - maybe once it progresses from Developer Preview 2 to Beta 1?
Ya, I was thinking the same thing. A lot what was mentioned in the OP is just copy/paste material for when the gsi rom drops.
https://twitter.com/i/web/status/1493335334125379586
Already got dp1 running on my lg v60.
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
hooutoo said:
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
Click to expand...
Click to collapse
I wish I knew what to tell you. Perhaps someone else can help. I know nothing about GSIs, much less GSIs on LG devices, and I'm not stepping into the Android 13 (or even 12L) pool just yet.
Have you asked about this aspect in the LG V60 section?
Given that the bootloader is unlockable, has anyone tried a GSI Rom on the OnePlus 11? I know generic images are missing device specific drivers but could provide a better experience for those not running this as a daily driver. Also, there are quite a few GSI's to chose from, are there any recommendations?
Guyinlaca said:
Given that the bootloader is unlockable, has anyone tried a GSI Rom on the OnePlus 11? I know generic images are missing device specific drivers but could provide a better experience for those not running this as a daily driver. Also, there are quite a few GSI's to chose from, are there any recommendations?
Click to expand...
Click to collapse
Not too sure anyone would be willing to try until OP decides to release an MSM tool
kevp75 said:
Not too sure anyone would be willing to try until OP decides to release an MSM tool
Click to expand...
Click to collapse
For flash a gsi (when you make any worng no problem you can it repare with fastboot/fastbootd)
I am currently on GSI.
Things which are not working.
Finger print.
Only Main camera working i think ( single Lense no ultrawide) ( I dont use camera exepect for barcode scanner anyway)
Rest is good.
Installation steps I took.
Unlock bootloader.
Install Dsu sideloader https://github.com/VegaBobo/DSU-Sideloader ( version 1.3 ) non root.
Setup dsu with 60 GB storage and use the image from
Andy Yan's personal builds // GSI - Browse /lineage-20-light at SourceForge.net
sourceforge.net
reboot
It boot into GSI without any issues. enable 5G, set refresh rate to 120.
reboot but it reboot into default Oxygen OS as expected.
click on restart in DSU from the notification.
Booted into GSI again.
5G working ( Volte)
Refresh Rate working.
Restore google apps and settings.
Connect phone to ADB
use this command on adb: adb shell gsi_tool enable ( this is to reboot in GSI by default on every reboot)
This is all like a dual boot ( safe method to try GSI without any fastboot and MSM tool worries.
Note : Whenever i want to reboot into Oxygen OS connect phone to adb and only give command - adb shell gsi_tool disable. It will reboot into default OS.