Database Develop

[ROM][UNOFFICIAL][10.0] Pixel Experience 10 for Lenovo Tab 4 8 Plus (TB8704F/X/N)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience for Lenovo Tab 4 8 Plus
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
What's working?
Wifi
Mobile data
GPS
Camera
Bluetooth
FM Radio
Sound / vibration
Facelock
Fingerprint
Known issues
You tell me.
December 2020 security patch
Android 10
DON'T FLASH GAPPS, ALREADY INCLUDED
Download ROM​
Android OS version: 10
Security patch level: December 2020
Build author/Device Maintainer: ChasTechProjects
Kernel Source: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
Device Source code: https://github.com/ChasTechProjects/android_device_lenovo_TB8704
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

To install you should be running stock firmware, you can restore using the Lenovo Rescue and Smart Assistant (LMSA) tool on a PC, then follow the instructions in the app to rescue the device. Make sure to unlock the bootloader as well.
Now grab a copy of TWRP recovery from here. Install fastboot and adb on your PC by following this tutorial on XDA.
Boot your device into fastboot mode (power + volume down). You should know when you are in fastboot mode as it will show on the screen.
Open up the terminal or command prompt and run:
Code:
fastboot flash recovery <path to twrp.img>
Now turn off your device by pressing power until the screen is black, then boot into recovery (power + volume up).
TWRP should boot up. DO NOT ERASE SYSTEM, OTHERWISE YOUR DEVICE WILL HANG ON THE GOOGLE LOGO. Go to Advanced, tap ADB sideload, then run the following on your PC.
Code:
adb sideload <path to rom.zip>
Once it's finished sideloading, reboot back into recovery, then swipe factory reset. Now reboot into system.
It will take a couple of minutes to load and then you should see setup. You can now setup your device. Enjoy Pixel Experience and Android 10 on your Lenovo Tab 4 8 Plus!

Great work man, thank you

Thanks, I am looking forward to try this ROM out.
Now I am running Lineage 16, and trying to back to stock with LMSA but it just fails during the flashing process. Is there any preparations that needs to be done before using LMSA to go back to stock?

dape16 said:
Thanks, I am looking forward to try this ROM out.
Now I am running Lineage 16, and trying to back to stock with LMSA but it just fails during the flashing process. Is there any preparations that needs to be done before using LMSA to go back to stock?
Click to expand...
Click to collapse
Have you tried this?
1. Turn off the device.
2. Plug the USB cable into the computer, but NOT the tablet.
3. Press the volume up button (just that button, no others) and connect the tablet at the same time.
4. Keep pressing the volume button for a few seconds and then release.
5. Check if the device is recognised in Windows device manager, it should say something like "QCom QDL mode".

Thanx a lot, it's great!!
Everything is working beautifully and smoothly.
Just FM radio does not start.
Any help about the radio please..

Followed your instructions and everything worked well. Very happy with this one, I came from the other PixelExperience (Android 9) and this is a great upgrade. Keep up the good work!

Thanks.. This rom make my tablet like brand new.

thank you for the firmware, but there is one bug in the "about the Tablet" menu that does not show imei and serial number and does not show the firmware of the communication module.

I installed this on my TB-8704F and am getting no Wifi, and Bluetooth force closes. I installed it twice using the provided procedure. Can someone help please?

mr.inter said:
I installed this on my TB-8704F and am getting no Wifi, and Bluetooth force closes. I installed it twice using the provided procedure. Can someone help please?
Click to expand...
Click to collapse
Have you tried other custom ROMs?

I originally had Lineage OS 17.1, flashed stock Nougat with Miflash, and attempted installing this, where my issue was encountered. Wifi works if I flash stock once again.

mr.inter said:
I originally had Lineage OS 17.1, flashed stock Nougat with Miflash, and attempted installing this, where my issue was encountered. Wifi works if I flash stock once again.
Click to expand...
Click to collapse
Try flashing Oreo using the LMSA instead.

Unfortunately I'm having issues with LMSA.
Driver in Windows 10 seems to be ok. I even tried with an older version.
Given that LMSA did not work, I restored an official untouched Oreo image through TWRP and then installed Pixel Experience, however issue persisted.

mr.inter said:
Given that LMSA did not work, I restored an official untouched Oreo image through TWRP and then installed Pixel Experience, however issue persisted.
Click to expand...
Click to collapse
There's your problem. The TWRP image is likely missing proprietary drivers, etc. Follow the tutorial here https://android.stackexchange.com/q...image-lenovo-tab-m10-tb-x605l-lte-android-8-o using QDL on Linux and the official stock firmware.

I used official stock firmware (Android 7 QFIL - since this does not seem to exist for Oreo), and have just performed OTA update from Nougat to stock Oreo, however I still have no Wifi or Bluetooth on this ROM. I still came from an untouched Oreo image even though I did not follow the above procedure as of yet.

mr.inter said:
I used official stock firmware (Android 7 QFIL - since this does not seem to exist for Oreo), and have just performed OTA update from Nougat to stock Oreo, however I still have no Wifi or Bluetooth on this ROM. I still came from an untouched Oreo image even though I did not follow the above procedure as of yet.
Click to expand...
Click to collapse
Do other ROMs continue to work? Like, can you install LOS 17 on this and get back to me on that?

Yes everything else was working prior attempting to flash Pixel Experience. Will continue troubleshooting tomorrow.

Today I did the same thing as I was intending to install LOS 17 over this ROM without wiping anything, and Wifi and Bluetooth worked. Very strange but at the same time I am happy that now I have a chance to try this ROM.

Nice ROM . For those coming from another custom ROM: For moving over to Pixel Experience it was sufficient to boot into the recovery, wiping cache, dalvik and data and then installing PE (via adb sideload in my case). After a reboot PE loaded and could get set up.

[ROM][12][blueline/crosshatch] PixelExperience [AOSP][OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Pixel 3 / 3 XL [blueline/crosshatch]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website (blueline)
Download from PixelExperience website (crosshatch)
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
​
Android OS version: 12
Security patch level: December 2021
Build author/Device Maintainer: ReallySnow
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

Installed on my crosshatch, running great so far

Many thanks for bring PE to Pixel 3 XL.
Hopefully it will be official.

what's the difference with the android version we officially got? It would be great for the next updates that will not be on the pixel 3

Gustavo_s said:
Installed on my crosshatch, running great so far
Click to expand...
Click to collapse
Hi Gus,
is the VoLTE & VoWiFi working ???
In my country Pixel is not in the list of the supported device from the carrier, therefore i am unable to get them working. But i have Mi A1 with official PE 11 (no root) both volte & vowifi work like a charm.
Since Google had stopped updating pixel 3 xl from Nov 2021 might as well go for the custom rom.

edkmho said:
Hi Gus,
is the VoLTE & VoWiFi working ???
In my country Pixel is not in the list of the supported device from the carrier, therefore i am unable to get them working. But i have Mi A1 with official PE 11 (no root) both volte & vowifi work like a charm.
Since Google had stopped updating pixel 3 xl from Nov 2021 might as well go for the custom rom.
Click to expand...
Click to collapse
My carrier doesn't support VoLTE too, so it never worked for me even on stock rom

Gustavo_s said:
My carrier doesn't support VoLTE too, so it never worked for me even on stock rom
Click to expand...
Click to collapse
Thanks for your respond.
Actually my carrier support VoLTE & VoWifi but not the phone model. As mentioned when using the same sim card with Mi A1 with PE 11 it works.

Gustavo_s said:
Installed on my crosshatch, running great so far
Click to expand...
Click to collapse
How do you compare this with stock on crosshatch?

Sorry for asking this as it seems I should probably a already know but....
What is the procedure for fishing this?
Is it a fastboot installation method?
Or does it require a lineage boot image?
Sorry if these questions are noobish.

shaemasa said:
How do you compare this with stock on crosshatch?
Click to expand...
Click to collapse
Same features, a bit smoother and better memory management. Most important for me is up to date security patches.
rhewins2268 said:
Sorry for asking this as it seems I should probably a already know but....
What is the procedure for fishing this?
Is it a fastboot installation method?
Or does it require a lineage boot image?
Sorry if these questions are noobish.
Click to expand...
Click to collapse
download latest twrp for crosshatch
unlock your bootloader
in your PC using fastboot: fastboot boot twrp.img
in twrp, select adb sideload, connect phone to your PC
in your PC using adb: adb sideload lineage.zip
do not reboot, in twrp do a factory reset (it was probably already reset when unlocking bootloader)
reboot
done
BTW safetynet and cts are ok using latest magisk stable, selecting all apps on magisk hide allowed me to use banking apps and microsoft intune portal

Good to hear that and how about the bugs: notification shade and notification dismiss? Are you able to dismiss notifications with single click? I know those do exist in official A12 (stock) but since you have been in to this, I thought ask about those bugs.

One more question...again i believe i know the answer....
Should I be on the latest firmware 12.0.0 (SP1A.210812.015, Oct 2021)?

shaemasa said:
Good to hear that and how about the bugs: notification shade and notification dismiss? Are you able to dismiss notifications with single click? I know those do exist in official A12 (stock) but since you have been in to this, I thought ask about those bugs.
Click to expand...
Click to collapse
There is a "dismiss all" button in the notification shade. On my pixel 4a on stock rom the notification shade sometimes gets bugged colors, i haven't noticed this issue yet on 3XL with this ROM. Might be because i haven't used it enough for the bug to show up.
rhewins2268 said:
One more question...again i believe i know the answer....
Should I be on the latest firmware 12.0.0 (SP1A.210812.015, Oct 2021)?
Click to expand...
Click to collapse
yeah i think so, flash the latest stock then this one

Gustavo_s said:
There is a "dismiss all" button in the notification shade. On my pixel 4a on stock rom the notification shade sometimes gets bugged colors, i haven't noticed this issue yet on 3XL with this ROM. Might be because i haven't used it enough for the bug to show up.
yeah i think so, flash the latest stock then this one
Click to expand...
Click to collapse
Is it daily drivable and what about the SOT?

So i tried getting Twrp to boot but it just kept hanging on the twrp splash screen. So i downloaded the latest LOS 18.1 recovery and flashed it. Then rebooted into LOS recovery. Did a factory reset and ADB sideloaded this rom and it seems to have worked.

Great job! Love this rom! Definately daily drivable! Safetynet passes out of the box and still after magisk root. (Flashed Magisk v23.0 23000 zip in recovery)

Cool!
Thank you for PixelExperience build based on Android 12!

This error was later fixed. Skip down to the numbered list in this post to see method to switch from stock A12 and perform upgrades.
Error 21 when sideloading the zip. TWRP also would not proceed past splash screen and other thread sources suggested recovery. Method I just tried:
Recovery mode (Power + Volume down to enter Fastboot mode - volume keys to scroll and power button to select Recovery Mode - Power + Volume up (reovery mode shows after approx 10 seconds hold)) > Apply update from ADB > "adb sideload PixelExperience.zip"
Running A12 already via OTA so attempting this really for the security patches. TWRP 3.5.2.10-0-crosshatch.img. ADB 31.0.3-7562133.
Could I just dirty flash using another (earlier) verion of TWRP or do I actually need to wipe data/factory reset in recovery mode? Or am I missing something else entirely?
EDIT: after all the helpful responses from others here, this is what got this ROM installed on my crosshatch device which was previously running A12 factory image SP1A.210812.015.
1. adb reboot bootloader (I did this via commandline. It is hardware accessible too but not what I used this successful time)
2. fastboot flash boot --slot b lineage-18.1-XXXX.img (this step not required when later updating PE)
3. on the device used up/down hardware keys to switch to recovery mode and select the option using the power key
4. device then shows android laying on its back and required power + up key held down (after several seconds release the up key) to enter recovery mode. This in particular required several attempts before the lineage recovery kicked in. It's jazzy purple so was quick to spot when successful. (this step not required when later updating PE)
5. factory reset device - other users mention not doing this is problematic and was also my experience. You won't be sad for long trust me. (this step not required when later updating PE)
6. update via adb on device recovery mode (when later updating PE it will have switched to its own recovery instead)
7. back in computer commandline "adb sideload PixelExperience-XXXX.zip"
8. (this step is no issue when simply upgrading PE) at around 47% progress the device then complained about signature being unsigned and that the install would be a downgrade. Had to do this to gain ADB sideload access. Switched answer to YES for both. Progress % didn't change but eventualy 2/2 steps completed. I had to do this step several times too. No idea why but across all devices over the years it's a shared experience when installing a new ROM. No gain with pain!
9. final step on the device was to remove the USB cable and choose to restart via the lineage recovery menu (or if upgrading PE it's of course "Reboot system now") - if you updated check the new security patch date in settings >> about phone >> android version >> note the android security update details.
So far everything working but just neeed to understand getting Magisk back for my workflow. EDIT: Got magisk working using the payload-dumper-go method as outlined here https://www.xda-developers.com/how-to-install-magisk/

I used the l later LOS
rossmurray said:
Error 21 when sideloading the zip. TWRP also would not proceed past splash screen and other thread sources suggested recovery. Method I just tried:
Recovery mode (Power + Volume down to enter Fastboot mode - volume keys to scroll and power button to select Recovery Mode - Power + Volume up (reovery mode shows after approx 10 seconds hold)) > Apply update from ADB > "adb sideload PixelExperience.zip"
Running A12 already via OTA so attempting this really for the security patches. TWRP 3.5.2.10-0-crosshatch.img. ADB 31.0.3-7562133.
Could I just dirty flash using another (earlier) verion of TWRP or do I actually need to wipe data/factory reset in recovery mode? Or am I missing something else entirely?
Click to expand...
Click to collapse
I used the latest LOS 18.1 recovery.

Thank you!

General A11 | Stable | Pixel Experience - A GSI ROM that works!

Alright guys,
I'm not a developer, nor am I a tester. I was just looking for something AOSP. While I found what I was looking for, I was not completely satisfied. Though the following GSI rom is extremely stable.
So, what I'm going to do in this thread is, document my process and how I got it working. I will however revert back to miui after documenting it. So cannot help you further with any issues and you're on your own.
Now let me start by stating my requirements, which will explain why I went with Android 11 rather than 12.
Requirements that must be satisfied:
1. Daily Driver
2. Stable Camera
3. No Throttling
4. No general issues with sensors
5. Sound should works great
6. Customization goodies like those of crdroid/rr/havoc (important)
7. Wifi,Bluetooth,mobiledata should all be working smoothly including 5G
8. Vibration should work
9. Good battery life
10. No over heating
11. TWRP support for android 11
Mind you, the GSI rom out of the box was ticking everything above. Which got me excited, so I quickly transferred the necessary data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it was completely stock Pixel Experience Android 11. Now the reason I chose this over android 12 was so I could use GravityBox along with this. Once the root was up and running, quickly installed Gravitybox. This allowed me to customize a number of things which I really needed:
Once all the customizations were done, I was getting closer to my final goals. Also, the gravitybox customizations did not cause any issues and were super stable with no heating issues etc.
I downloaded sensor testing apps, went through each and every single setting and option in the phone and figured all the major problems that I could see.
Problems in the rom:
1. Whatsapp call has echo (for the other person) when you use it on speaker phone
2. Fingerprint Sensor stays awake all the time, which means, if you touch it accidentally, it will get unlocked/wake the screen.
3. Viper4android does not seem to be getting installed but this seems more of an v4a issue.
4. Yup, thats about it, literally everything else works perfectly.
Links:
MIUI 12.5.10 [Global]: https://bigota.d.miui.com/V12.5.10.0.RKDMIXM/miui_VILIGlobal_V12.5.10.0.RKDMIXM_c6ffabfb05_11.0.zip
vbmeta file: [ Attached under the post ]
Pixel Experience GSI: https://github.com/ponces/treble_bu...ence_arm64-ab-11.0-20211009-UNOFFICIAL.img.xz
TWRP Android 11: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download
LSPosed Zygisk Build: https://github.com/LSPosed/LSPosed/releases/download/v1.7.2/LSPosed-v1.7.2-6379-zygisk-release.zip
Gravitybox: https://repo.xposed.info/module/com.ceco.r.gravitybox
Installation:
The install is similar to what @bhammler mentioned in his post, so I will just copy paste the instructions.
Here are my new steps:
1. fastboot flash_all vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
2. let it reboot to the setup screen and turn it off
3. fastboot boot twrp.img (no need to install)
4. update through twrp to miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12.0.zip [ Use miui 12.5.10 fastboot instead ]
5. it shows some errors, but it's still booting up to the setup screen. Turn off
6. From now on: everything in FastbootD (fastboot reboot fastboot)
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (see attached extracted vbmeta from MIUI 13) [ Extract from miui 12.5.10 (attached below) ]
8. fastboot erase system
9. fastboot flash system PixelExperience_arm64-ab-slim-12.0-20220221-UNOFFICIAL.img [ pixel experience android 11 instead ]
10. fastboot reboot recovery
11. wipe data in Mi Recovery
12. reboot and done
Click to expand...
Click to collapse
After doing the above process, we can further go ahead and install twrp as well for which the guide from @TheRomFan can be followed:
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
Click to expand...
Click to collapse
1. Once the twrp is installed as well. Go ahead and root the system as you would normally. (make sure to reboot into system after flashing twrp to check if everything is going good).
2. Flash lsposed zygisk build.
3. install Gravitybox for R.
Conclusion:
Overall, the experience for daily driver is extremely stable and with no issues. But unfortunately, the ocd maniac inside me is annoyed by the fingerprint waking up issue. So i will be going back to miui and patiently wait.
But if you guys dont mind that issue, the entire process i did is neatly presented above. And this can be used as a really good daily driver!
Hopefully this post helped.
Thats all, enjoy your phone!
~ NoUsernameSorry

Great thanks for that. I was wondering, how is the infamous xiaomi proximity sensor behaves in that rom? Did you tested?

Pichulec said:
Great thanks for that. I was wondering, how is the infamous xiaomi proximity sensor behaves in that rom? Did you tested?
Click to expand...
Click to collapse
It seems to work fine from my testing. With gravitybox, you have further proximity settings you can tinker with, so thats an advantage.

nousernamesorry said:
It seems to work fine from my testing. With gravitybox, you have further proximity settings you can tinker with, so thats an advantage.
Click to expand...
Click to collapse
Can you shed some light on gravity box? Never heard about it.

Pichulec said:
Can you shed some light on gravity box? Never heard about it.
Click to expand...
Click to collapse
Its basically a collection of tweaks for the rom.

Hello, I would like to install recently I learned to install by adb this gsi method is the same? I have the 11t pro

Follow instruction and tested the GSI.
First thing I noticed, that there is no 120hz even under phh tweak setting, only forced-60hz.
Secondly, DT2W is not working either.
Else, everything else seems good. The rom is extremely lightweight.

When you say stable Camera do all 3 camera's work?
How is battery life in general? How much SOT do you get on average every day? Does the device heat up at all compared to stock?

lethallunatic said:
When you say stable Camera do all 3 camera's work?
How is battery life in general? How much SOT do you get on average every day? Does the device heat up at all compared to stock?
Click to expand...
Click to collapse
Everything is absolutely stable. You need the gcam xml config to use all the three cameras. You can find that in the telegram group.
Battery life is similar, if not better. Like i mentioned. I am not using it, due to minor issues I was having. If you dont mind those issues, its stable and good as a daily driver.
Please read the thread, theres no heating as well. All the information is mentioned in the thread.

Trocxel said:
Hello, I would like to install recently I learned to install by adb this gsi method is the same? I have the 11t pro
Click to expand...
Click to collapse
If you follow the steps correctly, you should be good.

Does this have a working OTA?

gsus said:
Does this have a working OTA?
Click to expand...
Click to collapse
no this is the last android 11 release

How To Guide How to flash a GSI on Oneplus 10 PRO/T

MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA!​Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT!​
What does not work?​Fingerprint
face unlock
native camera app(Use gcam)
no notification slider
no modular refresh rate
no auto brightness(Not yet will be implemented)
no 5g(no worry no one uses it yet so)
maybe more let me know if you found a solution so i can add it under this post
I'm working on a overlay to fix some things for this device
What do I need?​A Unlocked bootloader Follow below.
Stock zip download this with oxygen updater(enable advanced mode and download your version)
Oneplus drivers Here
Latest Fastboot Enhance Here
And a GSI of choice you can get Here or Here dot os works good with this phone
Choose AB GSI and you don't need slim(Low system volume device's) or vndklite(For older device's)
Unzip and put all the things in a folder.
Start with installing the Usb drivers
and connection device to your computer. (no need to disconnect till your set)
If your in windows use
Code:
cmd
Unlocking Bootloader (This will wipe device)​
Go to Settings/About device/Version and tap the build number/version until you see your already a developer.
Spoiler: screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to Settings/Additional settings/Developer options and enable OEM unlocking
Spoiler: screen
On your Computer open fastboot tool folder and open a terminal there and type
adb devices
Accept on your phone
adb reboot bootloader
wait till boot
fastboot flashing unlock
device will ask you to confirm if you want to unlock Confirm this
Spoiler: screen
Gathering your assets​On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Spoiler: screen
Preping device for GSI​On your computer open fastboot tool folder and open a terminal there and type
adb reboot bootloader
Wait till boot
fastboot reboot fastboot
you will see a screen with Chinese and languages as options don't do anything here.
On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
than click on your device and go to partitions
Spoiler: screen
To make space for our new OS we need to make space so we are going to remove the old firmware left after update's
In the petitions tab type -cow and delete these volume's, Yes all volumes this will not affect your device
Spoiler: screen
Skip all above if you already on a GSI​The flashing of the GSI ​Make sure your GSI is a .img Unzip if its a xz/zip file
Now open fastboot tools folder and start a terminal there
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system Gsi.img
Spoiler: screen
wait till finished than on the phone click English and Format data and wait till it boots.
Spoiler: Pixel experience
Spoiler: CherishOS
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader
fastboot boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.

reserve

Back to stock
Very simple aslong you dont mess around with other partitions
Open the fastboot tools folder and start a terminal.
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system
fastboot flash system THE_SYSTEM_IMG_BACKUP_YOU_EXTRACTED
fastboot flash vbmeta vbmeta.img(Will remove gsi flash ability)
fastboot flash boot boot.img(Will remove root)
wait till finished than on the phone click English and Format data and wait till it boots. and your back to ****ty ColorOs

Absolutely what we need

Have anyone tried GSI on OP 10 T. Wanted to get a sense of this before I jump on.

Good man
I'll flash in the morning.
Cheers.

dladz said:
Good man
I'll flash in the morning.
Cheers.
Click to expand...
Click to collapse
Which one you took? Working fine so far?

I'm gonna make a overlay for our device this may box some issues and bugs

MrScarl3t said:
I'm gonna make a overlay for our device this may box some issues and bugs
Click to expand...
Click to collapse
Overlay?

lovesetcpu said:
Which one you took? Working fine so far?
Click to expand...
Click to collapse
I actually updated to beta 2, I couldn't help myself..tbh it's really good I'd recommend it.
Proximity sensor doesn't work for me or auto brightness but everything else is superb.. you can update directly from 12 to 13 using the update APK..
If you check the beta update thread on xda in this 10 pro section and you'll see it.. look for post #55

Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T

alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.

dladz said:
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
Click to expand...
Click to collapse
Honestly it was pretty good overall. As mentioned in OP, finger print, DTW, face unlock, auto brightness, VOLTE (my requirement as my network works on that for voice), doesn't work.
Besides these fairly good, passes safety net without root, (may pass even with it), fast charging ( didn't exactly time it or measure, but was fairly close to the stock ultra fast charging experience), and the beautiful fluid AOSP experience, 120 hz rr and the performance was somewhat better than stock, at least for gaming. Got 2800+ on 3d mark extreme and got 95% stability on the stress test. FYI - OP 10 T

alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why

MrScarl3t said:
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
Click to expand...
Click to collapse
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus

alanzaki073 said:
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
Click to expand...
Click to collapse
The name is org.codeaurora.ims don't know where it's located

I wish that it became more stable!
I can't stand with ColorOS 13 [OxygenOS 13] !!

Any luck on VOLTE?

Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well

yo-less said:
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
Click to expand...
Click to collapse
How was the experience?
Why you back to OxygenOS?

[ROM][13][amogus] AOSP 13.0

AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.​
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.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants​
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch

Nice finally something other than Android 11

Good work, it works for now.
Is there any Gapps available for this Android version ?

I look forward to giving this a try when Gapps is available.

I decided to give it a try and it's working well with the exception of what has already been declared to not be working:
USB Mode Switching​
Speakerphone on sofia variants​
I can confirm that these are broken on Sophia, and I can also confirm that the Speakerphone also doesn't work in video calls made using Signal.
I know it's ASOP but including a browser that can download would help greatly with getting F-DROID (especially with USB Mode Switching being broken). The Webview browser can't seem to download anything. You can browse with it but not download.
Thank you very much for the hard work.
Matthew

matthewadie said:
I decided to give it a try and it's working well with the exception of what has already been declared to not be working:
USB Mode Switching​
Speakerphone on sofia variants​
I can confirm that these are broken on Sophia, and I can also confirm that the Speakerphone also doesn't work in video calls made using Signal.
I know it's ASOP but including a browser that can download would help greatly with getting F-DROID (especially with USB Mode Switching being broken). The Webview browser can't seem to download anything. You can browse with it but not download.
Thank you very much for the hard work.
Matthew
Click to expand...
Click to collapse
USB Mode switching does not impact the function of ADB, you can use that to install any third party apps. Thank you for the review

GApps would be nice. Also, would flashing this and later trying to flash an Android 11 ROM trigger anti-rollback protection?

kotchama said:
GApps would be nice. Also, would flashing this and later trying to flash an Android 11 ROM trigger anti-rollback protection?
Click to expand...
Click to collapse
No it will not trigger anti rollback protection, I'll consider adding gapps but eh

Going to check it out and see if I can acquire root access to check what is messing with the speakerphone and USB. Nice to see something new to test on these phones!

Tried this on my SofiaR and I guess the radio files just didnt flash or it didnt keep the original ones but yea I have no cell service, is this normal? Tired installing it again and had the same issue.

killahrey said:
Tried this on my SofiaR and I guess the radio files just didnt flash or it didnt keep the original ones but yea I have no cell service, is this normal? Tired installing it again and had the same issue.
Click to expand...
Click to collapse
I suggest you flash stock and verify that cell service works there and then reflash this rom on top. It is verified that cell service works on this build

Electimon said:
I suggest you flash stock and verify that cell service works there and then reflash this rom on top. It is verified that cell service works on this build
Click to expand...
Click to collapse
I flashed a stock rom and the phone rebooted, everything seemed fine. I turned off the phone to reflash this rom but before I had the chance to the phone would not boot to anymore. Seems completely bricked, but its probably my own doing.

killahrey said:
I flashed a stock rom and the phone rebooted, everything seemed fine. I turned off the phone to reflash this rom but before I had the chance to the phone would not boot to anymore. Seems completely bricked, but its probably my own doing.
Click to expand...
Click to collapse
Ok since it bricked before you had a chance to flash the rom, the issue is most likely with how you flashed stock. Can you show me the process you took todo that? Also if you plug in the device to a Windows machine, in device manager does it show QUSB_BULK?

The only thing different from stock was the twrp recovery img. I'm guessing I may have accidentally flashed the wrong boot.img some how, honestly I'm not sure. There is no response from the device on windows or Kali. Does not indicate it's charging in anyway and all restart processes do nothing. Wanted to use this as a backup before I got my new phone in a few days but it is what it is. I highly doubt it was any of your img's.

killahrey said:
The only thing different from stock was the twrp recovery img. I'm guessing I may have accidentally flashed the wrong boot.img some how, honestly I'm not sure. There is no response from the device on windows or Kali. Does not indicate it's charging in anyway and all restart processes do nothing. Wanted to use this as a backup before I got my new phone in a few days but it is what it is. I highly doubt it was any of your img's.
Click to expand...
Click to collapse
There is one way to revive it but it involves disassembly, would you like me to tell you about it? I know not much have the tools for it.

Electimon said:
There is one way to revive it but it involves disassembly, would you like me to tell you about it? I know not much have the tools for it.
Click to expand...
Click to collapse
I was considering disassembly to see if a battery unplug would help but if there is something else you think I should do I'm all ears.

killahrey said:
I was considering disassembly to see if a battery unplug would help but if there is something else you think I should do I'm all ears.
Click to expand...
Click to collapse
Yes the device has testpoints on the motherboard, if you bridge them it will enter EDL mode. From there you can use a blankflash to restore the bootloader and hopefully unbrick. Unplug the battery and bridge those pads, while bridged plug in the USB cable and with any luck you will be in EDL. From there you can plug the battery back in so it can flash successfully. You can find the blankflash on https://mirrors.lolinet.com/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Electimon said:
Yes the device has testpoints on the motherboard, if you bridge them it will enter EDL mode. From there you can use a blankflash to restore the bootloader and hopefully unbrick. Unplug the battery and bridge those pads, while bridged plug in the USB cable and with any luck you will be in EDL. From there you can plug the battery back in so it can flash successfully. You can find the blankflash on https://mirrors.lolinet.com/
View attachment 5699785
Click to expand...
Click to collapse
Awesome, thanks for this info. I'll mess with this tonight and see if I can bring it back to life.

Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS

Question why is it that the built in file manager is unable to install apps? I understand we can use ADB to install apps, still this seems like abnormal behavior .
As always, thanks for the ROM.