Related
Hello everyone,
I've been tinkering around with Generic System Images since the Oreo Developer Preview 1 came out for the Razer Phone. I'm glad to say I got it to work, with lots of help from @MishaalRahman, @P4Block and indirect help of @phhusson and @TheCrazyLex.
What's working as of right now:
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
What needs further testing:
- 4G/LTE FIXED check out post #77!
- Once the above is confirmed to work => VoLTE on any carrier, and also testing on certain carriers like 3 UK (since they sold a version with different software).
What's broken:
- Audio in phone calls (works properly in VoIP/3rd party apps) FIXED check out post #48!
What ROMs can be booted with this (as of 30-03-2018):
AOSP 8.1
Lineage OS 15.1
Resurrection Remix
More to come...
Setting up your device:
You'll need:
Code:
To [URL="https://forum.xda-developers.com/razer-phone/how-to/guide-to-unlocking-bootloader-t3706462"]fully unlock your bootloader[/URL] and [URL="https://forum.xda-developers.com/showpost.php?p=74607352&postcount=8"]unlock flashing capabilities[/URL] on your device.
[URL="https://eu.dl.twrp.me/cheryl/twrp-3.2.1-0-cheryl.img.html"]TWRP image[/URL] + [URL="https://eu.dl.twrp.me/cheryl/twrp-installer-3.2.1-0-cheryl.zip.html"]TWRP injector[/URL]
[URL="http://tiny.cc/latestmagisk"]Magisk flashable zip[/URL]
A GSI of your preference from the ones listed [URL="https://forum.xda-developers.com/project-treble/trebleenabled-device-development"]here[/URL]. PS: Use the Gapps+SU one if you choose AOSP ;)
0. Make sure you're running the Android O DP1 from Razer, or any future update to it.
THIS WON'T WORK ON NOUGAT
1. Properly install TWRP on your device: (I'll be using @Dees_Troy's guide with a few modifications to make very sure everything will work as intended)
- fastboot flash the twrp image as explained by him, in your currently active boot partition. PS: After flashing the Android O DP1, it will always be A.
Dees_Troy said:
Once you have adb working, run this command: adb shell getprop ro.boot.slot_suffix
It should say: [ro.boot.slot_suffix]: [_a] Or: [ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this: fastboot --set-active=_b Or on slot B type this: fastboot --set-active=_a
You should see something like this: Setting current slot to 'a'... OKAY [ 0.042s] finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Click to expand...
Click to collapse
2. Once you're in TWRP, DO NOT SLIDE to allow modifications, but tap on Mount as Read Only. Plug in your USB cable, and adb push the boot image from the Android O DP1 factory image to your sdcard, as well as the TWRP injector and the Magisk zip. That can be done with the following commands:
Code:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
Code:
adb push path/to/the/factoryimage/boot.img /sdcard
Code:
adb push Magisk-16.0.zip /sdcard
3. Go into Reboot, then make sure you're on partition A. Else, tap on the button to set A as the active partition.
Now go back, tap Install, then tap on 'Install Image' then choose the boot.img you just pushed, and flash it as boot image.
Now go back, into Reboot, and move to partition B and repeat the step above.
Once you're sure both partitions only contain the unmodified boot images, set the partition A as active, go into Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
Once it finishes, do the same with the Magisk zip file.
4. Go into Reboot, press on Bootloader.
5. Connect the usb cable, and flash the GSI system image onto your system_a partition through fastboot from your pc. This can be done with the command:
Code:
fastboot flash system_a system-arm64-ab.img
5.b If you wish, you can install a different GSI onto your system_b partition, and that can be done with the following commands:
Code:
fastboot set_active b
Code:
fastboot flash system_b system-arm64-ab-gapps-su.img
5.c If you wish to go back to the system_a partition, you can execute:
Code:
fastboot set_active a
6. Reboot and enjoy.Prebuilt boot image:
If doing the steps from 1-4 seems messy or you don't get it to work properly, I've published the image I made following them with the latest Magisk and TWRP versions available as of April 20th 2018.
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
Code:
fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
SHA-2: 2f0c7348ac906f2f81fa39df7b24b69392783bd2379d5da357777be444c67d97
Old version (from ODP1 - may experience the bootloader issues):
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180330_cheryl_odp1.img
Code:
fastboot flash boot_b boot_linuxct_20180330_cheryl_odp1.img
SHA-2: 8f763162415167b2e919a450654f9a46f69b81f6853013bcabf362dfeb2a115e
Many thanks to everyone that helped me today to get this to work properly!
Want some screenshots?
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
PupPupG said:
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
Click to expand...
Click to collapse
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
This is awesome!!!
I'd love to have a fully working resurrection remix build working on my cheryl!!!!! =D <3
KEEP UP THIS AWESOME WORK!!!!!!!!!
linuxct said:
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
Click to expand...
Click to collapse
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
PupPupG said:
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
Click to expand...
Click to collapse
Flash the Oreo DP1 image and start over.
linuxct said:
Flash the Oreo DP1 image and start over.
Click to expand...
Click to collapse
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Flashing the Oreo DP1 image actually flashes an empty, non-encrypted userdata image. That's why I requested to start over.
That can also be another solution, bit messier than starting over but it's good.
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
M1cky said:
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
Click to expand...
Click to collapse
I do. Try installing the latest beta of Magisk and then, if that didn't solve it, try setting a new Build fingerprint with a tool like MagiskHide Props Config (PS. Just to be sure, set the Google Pixel 2 XL one since that's the only 8.1.0 build fingerprint provided by that tool).
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Happy to see people making use of Treble on Razer Phone this quickly.
Good job! @linuxct
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
RUNNERX said:
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
Click to expand...
Click to collapse
Yes, it happens sometimes. Let me explain this briefly:
1. This bootloader seems to forget what the active partition was when it was told to reboot the device instead of turning itself off, and I don't know why yet. It happens 1/5 times I press on "Reboot", more or less.
2. You need to re-set the active partition to the one you were using, in my case A, so with a cable and my pc I run
Code:
fastboot set_active a && fastboot reboot
Tired of typing, I made myself a script named razer in my /usr/bin
Code:
#!/bin/zsh
fastboot set_active a && fastboot reboot
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
el4nimal said:
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Click to expand...
Click to collapse
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
linuxct said:
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
Click to expand...
Click to collapse
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Resurrection Remix Intensifies
el4nimal said:
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Click to expand...
Click to collapse
Unless you have overwritten it, boot to download mode and use fastboot to switch to the other slot which will allow you to boot into TWRP and install Magisk. If you have overwritten TWRP, flash it on the other slot (for example if you have LOS installed in A, flash TWRP into B).
linuxct said:
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
Click to expand...
Click to collapse
It has happened after a power off also, would putting the same rom in a&b slot stop it? system_other is not bootable so the phone enters download mode? I don't understand the working of the a/b system.
And THANK YOU so much for working on this, so nice to be back on custom roms!
Motorola Moto G7 Play
Codename: CHANNEL
Boost Mobile Variant
Model No. XT1952-4
OBSOLETE THREAD
IMPORTANT NOTE:
At the time this thread was created, Motorola Mobility had not yet released the official stock Android 10 update for this variant of the CHANNEL. Because this variant has long since received the official Android 10 update, this thread is beneficial only for experimental or educational purposes. While you may certainly install RETAIL Android 10 firmware on the Sprint compatible xt1952-4, it is recommended always to install the latest official Android 10 firmware package released exclusively for this variant. Official Motorola stock firmware packages are available for the Boost Mobile/Sprint variant here https://mirrors.lolinet.com/firmware/motorola/channel/official/Sprint/
COMPATIBILITY:
Although this guide specifies the Boost Mobile (xt1952-4) variant of the CHANNEL, device owners have tested and confirmed that this Android 10 firmware is compatible with other variants/models. Namely, the MetroPCS xt1952-6 and the T-Mobile xt1952-T are confirmed. It is safe to assume that, because this is a RETAIL based official firmware build, compatibility should be universal for all region based retail models.
DISCLAIMER:
By proceeding further, you are assuming full responsibility for the operability and integrity of your device. Although this is an official firmware package, installation of firmware has an inherent risk of damaging your device or otherwise rendering it inoperable if the instructions are not followed carefully. Follow this detailed guide carefully and concisely and the installation should go smoothly. However, I am absolved of any liability in the event you break something. If you do mess something up, either myself or one of the many knowledgeable members herein will try to assist you.
OFFICIAL ANDROID 10:
For owners of the Moto G7 Play, it's no secret that the official Android 10 OTA update has already began rolling out to device owners in Brazil. As such, it probably will not be long before device owners in the US begin seeing a notification for the Android 10 update. In the meantime, for owners of the Boost Mobile variant (xt1952-4) who want to manually update to Android 10 by flashing the official Android 10 retail firmware package, I have put this simple guide together to assist you. In essence, to update manually, you will need to install the Android 10 firmware package via fastboot or RSD-Lite. This guide is premised upon the fastboot mode method. This Android 10 firmware is stable and may be used for your daily driver ROM. Look to the end of this guide for reported bugs.
BUILD INFO:
Android Version: Android 10
Build Region: RETAIL
Build No. QPY30.52-22
Kernel Version: 4.9.206-perf+
Radio Version: M632_41.178.01.156R
FSG Version: FSG-8953-25.163
Bootloader Version:2.1-channel_retail-315bc626c6-200423
System Version: 30.1.24.channel.retail.en.US
Build Date: April 13, 2020
Security Patch Level: April 1, 2020
ANDROID 10 UPDATE FEATURES:
• Optimized Fast Charging
• Bug Fixes for Battery Drain Issues
• Power Optimizations
• System-Wide Dark Theme
• Gesture-Based Navigation
• Privacy & Location Controls
• Sound Effects -- Stock Equalizer & Amplifier
• Smart Reply w/Messaging Apps
• Incognito Mode w/Google Maps
• Focus Mode
• Live Caption
• New Parental Controls
• New Moto Actions
INSTALLATION:
For those members who are not familiar with installing official firmware via fastboot mode, I will outline the exact steps below, including links to the files you'll need for the job. This guide requires a Windows PC or laptop, running Windows 7, 8.1 or 10 (32 or 64-bit). While fastboot can be used with other operating systems, this guide is outlined for Windows based systems only:
1. First, on your Windows PC or laptop, you will need to download and install the latest version of Motorola Device Manager, to ensure installation of up-to-date USB device drivers. Motorola Device Manager can be downloaded here: https://support.motorola.com/us/en/solution/MS88481
2. Next, download and install the latest fastboot and ADB utilities for flashing the firmware to your device. We will be using the Minimal ADB & Fastboot tools, version 1.4.3. On your PC or laptop, visit this link https://mega.nz/file/dVR3xCJL#GjcIXtNcCoB7R9DJtyqJ3dfOmeuGuPUvx6FKgp23yrc
3. Now download the official Android 10 retail firmware package from the Downloads section below;
4. Extract the contents of the firmware package zip you just downloaded to your Minimal ADB & Fastboot directory;
5. Boot your Moto G7 Play into AP Fastboot mode. With the device powered off, hold the power button along with the volume down button for around 8 seconds or until AP Fastboot mode appears on your device display;
6. Connect your device to your PC or laptop using the OEM supplied -- or quality equivalent -- USB to USB type C charging/syncing cable;
7. Open a command prompt in the path of your Minimal ADB & Fastboot directory. Execute the following command: fastboot devices
If your PC/laptop & device are properly synced, the command window will return an alphanumeric string synonymous with your device serial number. If you are not properly synced, try another USB syncing cable, change USB ports on your computer, or try reinstalling the USB device drivers.
**NOTES: by following these installation instructions, you will wipe your device of all userdata. Before proceeding further, make a backup of any important files and media.
Once you have confirmed proper syncing between your device and PC/laptop, execute the following fastboot commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fb oem config fsg-id boost
fb oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your Boost Mobile Moto G7 Play will be running stock Android 10. During setup, select the "Use Mobile Data" option instead of using WiFi. This will allow your device to establish its initial 4G/LTE data connection on the Boost Mobile network. Once setup is complete, your cellular data, voice and messaging services should be functioning normally. Make a test phone call and send a test text message to confirm.
DOWNLOADS:
Android 10 Retail Firmware:
•Build No. QPY30.52-22 (April 1 SPL): https://mega.nz/file/YIZnwAAZ#17HH-vbEsbxQVPNLjvgNqdTHFI4Ow2ah6SNC4Nnw9ec
•Build No. QPYS30.52-22-2 (June 1 SPL): https://mega.nz/file/lB5gkaqK#BD-r7dSTw8dgZAfI90pJq7LB_XJvqcvSVshXbLo-yic
Android 9 Pie Stock Firmware:
• Official Firmware Builds: https://mirrors.lolinet.com/firmware/moto/channel/official/Sprint/
BUGS:
• PRL/Domestic Roaming:
When roaming outside of the home network, the device may give a mobile IP registration response error (MIP Error 67-- Mobile Node Failed Authentication), and the cellular signal may become unstable. This is most likely due to the lack of an integrated PRL (Preferred Roaming List) provisioning service within the retail firmware. I am looking for a workaround: possibly implementing the Boost Mobile radio firmware from Android 9, or including the SprintDM mobile provisioning service as an add-on;
• Gesture/Navigation Features:
As XDA Member @JohnSmith8786 has pointed out, some of the native Gesture Navigation features in the RETAIL Android 10 firmware are somewhat unstable and buggy at times. This bug has been reported to Motorola Mobility via official bug report. Since this issue does not appear to be specific to a particular variant/model, and has been reported on various different models, this issue is likely unique to the RETAIL Android 10 firmware builds, and will likely be resolved by stability improvements/bug fixes in a future OTA(s).
Please report any bugs or instabilities in comments below. Also, please provide confirmation regarding compatibility of this Android 10 firmware on specific Moto G7 Play models. In theory, this firmware should work on any model with an unlocked bootloader. As all Android enthusiasts, modders and devs know, confirmation is always better than theory.
Could it work on XT1952-6 from MetroPCS?
mickem said:
Could it work on XT1952-6 from MetroPCS?
Click to expand...
Click to collapse
Can confirm working on XT1952-6 & XT1952-T
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
mickem said:
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
Click to expand...
Click to collapse
I used RETAIL, only issue is the baked in gesture navigation gets squirrely sometimes
JohnSmith8786 said:
Can confirm working on XT1952-6 & XT1952-T
Click to expand...
Click to collapse
Thank you very much. I will add that to my OP heading. Yeah I've noticed some slight buggy behavior on the RETAIL Android 10 gesture navigation features too. Motorola Mobility has been notified of this issue, so perhaps a future OTA will fix this.
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
GRiZZ91 said:
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
Click to expand...
Click to collapse
Correct. Flashing this firmware to a device active on the Boost Mobile network will continue to function normally. I have noticed some buggy behavior when roaming outside of the home network. Other than that, your device should function just as if you were using the Sprint firmware build.
Sorry I was rusty
Does anyone know if in this Android version call recording goes back to our Motorola? On Android 9 I had to root phone for enable call recording. How is it now?
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1. For anybody needing it, I will try to post a link for the entire firmware package this weekend. Here is a link to the latest full firmware package for the Sprint/Boost Mobile xt1952-4 https://mega.nz/file/SmAEwRZL#M4KP8hHHEtBw5fOtHGRuGfDV8F0SUkFENVGctzJagFw
Viva La Android said:
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1.
Click to expand...
Click to collapse
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
veryspecialagent said:
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
Click to expand...
Click to collapse
I have a patched boot.image that will root your device.
Viva La Android said:
Ill have a patched boot.image that will root your device.
Click to expand...
Click to collapse
Correction I mean a patched recovery image
Viva La Android said:
You can I stall it via TWRP or fastboot
Click to expand...
Click to collapse
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk.
Viva La Android said:
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk
Click to expand...
Click to collapse
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
veryspecialagent said:
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
Click to expand...
Click to collapse
Cool. Yeah let me know. Follow the install instructions for LOS 18.1 directly from the Lineage WiKi. The install is not standard TWRP like most Lineage builds. This has to be done using.adb sideload in TWRP mode with a PC.
That should have posted 2 hours ago.
This is what I f'ing loathe about this process because it happens virtually EVERY time regardless of the device or OS or mod that I'm doing.
The first thing I did was make sure sdk tools were updated. There were updates for Android 6 and 10, as well as two new modules to install. It took about a half hour to go through them all, but everything is updated.
Downloaded LoS, latest version, and the recovery image.
Go to the first step on the LoS install, which is to sideload a specific zip file. kay...
-reboot into bootloader, then from there to recovery
-adb sideload <the file>
-on computer: error:closed
-on phone: Error 21, footer is wrong
This nearly ALWAYS happens, and I have yet to find a fix. I google for an answer, keeping results to just within the last year, and someone on Reddit had suggested a fix that worked for the poster. His problem was that he was in stock recovery. He needed to be in LoS recovery.
I think "well, they give you a recovery image separate with the OS download, maybe it's to boot with, like TWRP." So I boot into the bootloader and try to fastboot boot <lineage recovery.img>..........and it just starts up normal. I go to settings and check the build, and it's still the Android 10 version I started with. Tried it again, same results.
So then I get the bright idea to stay where I'm at in stock OS and adb reboot <lineage recovery.img>
Now, on my phone it's in a weird Android Recovery screen. "Can't load Android system. Your data may be corrupted. If you continue to get this message...." Then it gives me two options: Try again or factory reset.
Well, my mama didn't raise no quitter, so I hit Try Again. It goes to the black screen with "N/A" on it (which is what it would do back when I had this thing rooted and everything was peachy until I forgot the lock screen pattern), but then I get that error message again.
I'm going to factory reset and see what happens. Anyone with a solution, feel free to chime in anytime.
Factory reset complete. Now I'm.....still in Android 10, build QPYS30.85-18-11.
Lol, just to clarify where we're at: The process I'd "be much better doing" took three hours to implement just half of the first step, and it led to me having to factory reset because it wouldn't boot.
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T
It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.
pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.
Hello everyone, I'm porting LineageOS to Xiaomi 12, but I haven't unlocked the bootloader.
Can someone help me testing my port? I'll be appreciated if you could help me.
Requirements:
A Xiaomi 12 with unlocked bootloader.
Have enough time to test.
Know how to use logcat.
Speak English or Chinese.
Please contact me at Link deleted or Link deleted if you are willing to help. Thank you very much.
If you have a Deleted, just add my account ID Accound deleted please.
Edit moderation - Unauthorized links - Sib64 - moderator
awsome！kuan brother niubi！
Hey, i still have to wait some 120-ish hours to get my bootloader unlocked, but once I do, I can give it a try
fygesser said:
Hey, i still have to wait some 120-ish hours to get my bootloader unlocked, but once I do, I can give it a try
Click to expand...
Click to collapse
could test the ROM?
Hi, do I need to build it from source, or do you provide the binary?
do you provide the binary?
Is there a QQ group for this?
I compiled a rom from this device tree. But I don't know what's wrong. Boot into recovery mode only once.Then keep looping into fastboot.
NothingToHere said:
I compiled a rom from this device tree. But I don't know what's wrong. Boot into recovery mode only once.Then keep looping into fastboot.
Click to expand...
Click to collapse
how to compile bro
Are there any tutorial on how to compile a rom from device tree?
roesip said:
Are there any tutorial on how to compile a rom from device tree?
Click to expand...
Click to collapse
Find a phone you like from the lineageos official support list, where there is a detailed compilation process
Using already LOS!
ydd0ras said:
Using already LOS!
Click to expand...
Click to collapse
On Xiaomi 12? Which Build from which source?
Check here
Release LineageOS 19.1 for Xiaomi 2201123G (cupid) · arian-ota/ota
📅 Build date: 2022-06-19 🛡️ Security patch: 2022-06-05 💬 Variant: VANILLA 🗒️ Changelog SHA-256 checksum 4b31804abcd9fc54afb8b89ec2ed2bde3aab49e78065b31bd02321281677c161
github.com
ydd0ras said:
Check here
Release LineageOS 19.1 for Xiaomi 2201123G (cupid) · arian-ota/ota
📅 Build date: 2022-06-19 🛡️ Security patch: 2022-06-05 💬 Variant: VANILLA 🗒️ Changelog SHA-256 checksum 4b31804abcd9fc54afb8b89ec2ed2bde3aab49e78065b31bd02321281677c161
github.com
Click to expand...
Click to collapse
I, i Will be pleased if you upload a flashing guide.
Therazorsedge said:
I, i Will be pleased if you upload a flashing guide.
Click to expand...
Click to collapse
OK, I have wrote a flashing guide for Windows users, tho I don't use Windows so I hope all steps are correct:
Flashing LOS on Cupid
Xiaomi 12 LOS ROM flashing
Prerequisites:
Your bootloader must be unlocked.
You should use latest platform tools on Windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Your device should be charged above 50%. Well, it doesn't have to be, but this is just for your phones safety.
Download all required files - ROM, boot, vendor_boot, dtbo and recovery.
Make a proper backup if needed and push it to another storage.
First steps:
After you have unlocked the bootloader, device will reboot automatically. Finish the setup, enable developer settings and finally enable USB-Debugging in developer settings.
In Windows open the folder in which you have unzipped the platform tools.
Hold left shift and press right click
click "open powershell window here"
Type in Terminal for example "adb devices" and grant the permissions for this PC on your device.
Reboot your device to fastboot and connect it with your PC.
The flashing procedure:
Flash boot, vendor_boot, dtbo and recovery:
Type in Windows Terminal:
fastboot flash boot lineage-19.1-20220617-UNOFFICIAL-cupid-boot.img
fastboot flash vendor_boot lineage-19.1-20220617-UNOFFICIAL-cupid-vendor_boot.img
fastboot flash dtbo_ab lineage-19.1-20220617-UNOFFICIAL-cupid-dtbo.img
fastboot flash recovery lineage-19.1-20220617-UNOFFICIAL-cupid-recovery.img
and finally
fastboot reboot recovery or
reboot to recovery by holding volume up and power buttons until you see Mi logo on your screen (on device).
In LOS recovery:
do a factory reset first
go to "Factory reset" and perform "Format data / Factory reset"
all data will be erased. Then....
go to "Apply update", followed by "Apply from ADB"
Now sideload the ROM:
type in Windows Terminal
adb sideload lineage-19.1-20220617-UNOFFICIAL-cupid.zip
You can also drag ROM zip file into your terminal window, instead of typing the full name/path to file.
When finished, reboot simply your device.
ydd0ras said:
OK, I have wrote a flashing guide for Windows users, tho I don't use Windows so I hope all steps are correct:
Flashing LOS on Cupid
Xiaomi 12 LOS ROM flashing
Prerequisites:
Your bootloader must be unlocked.
You should use latest platform tools on Windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Your device should be charged above 50%. Well, it doesn't have to be, but this is just for your phones safety.
Download all required files - ROM, boot, vendor_boot, dtbo and recovery.
Make a proper backup if needed and push it to another storage.
First steps:
After you have unlocked the bootloader, device will reboot automatically. Finish the setup, enable developer settings and finally enable USB-Debugging in developer settings.
In Windows open the folder in which you have unzipped the platform tools.
Hold left shift and press right click
click "open powershell window here"
Type in Terminal for example "adb devices" and grant the permissions for this PC on your device.
Reboot your device to fastboot and connect it with your PC.
The flashing procedure:
Flash boot, vendor_boot, dtbo and recovery:
Type in Windows Terminal:
fastboot flash boot lineage-19.1-20220617-UNOFFICIAL-cupid-boot.img
fastboot flash vendor_boot lineage-19.1-20220617-UNOFFICIAL-cupid-vendor_boot.img
fastboot flash dtbo_ab lineage-19.1-20220617-UNOFFICIAL-cupid-dtbo.img
fastboot flash recovery lineage-19.1-20220617-UNOFFICIAL-cupid-recovery.img
and finally
fastboot reboot recovery or
reboot to recovery by holding volume up and power buttons until you see Mi logo on your screen (on device).
In LOS recovery:
do a factory reset first
go to "Factory reset" and perform "Format data / Factory reset"
all data will be erased. Then....
go to "Apply update", followed by "Apply from ADB"
Now sideload the ROM:
type in Windows Terminal
adb sideload lineage-19.1-20220617-UNOFFICIAL-cupid.zip
You can also drag ROM zip file into your terminal window, instead of typing the full name/path to file.
When finished, reboot simply your device.
Click to expand...
Click to collapse
Is there a list of what's not working? That's be helpful for people who wants to know if the rom is suitable for daily drive.
Thank you!
Actually SMS don't come in. And D2W doesn't work. Maybe LOS needs to be polished a little. But I am using it for more than a week as daily driver. Put my Mi 11 lite 5G in the drawer.
ydd0ras said:
Actually SMS don't come in. And D2W doesn't work. Maybe LOS needs to be polished a little. But I am using it for more than a week as daily driver. Put my Mi 11 lite 5G in the drawer.
Click to expand...
Click to collapse
Your Info is really a great help! Thanks a lot!
Hi ! Do you have an idea of how I could contact the Dev of lineage for Xiaomi 12 ? I'd like to develop for Oneplus 10 pro and since they share the same soc he could be really useful
Hi everyone, new custom rom for POCO C40?? I cant find any available
gsi roms are working. android 13 roms have some issues with the camera tho. 11 and 12 roms are fine according to my initial testing.
lineage android 12 https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
crdroid android 11 https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
you can check these...
zenfone selfie said:
gsi roms are working. android 13 roms have some issues with the camera tho. 11 and 12 roms are fine according to my initial testing.
lineage android 12 https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
crdroid android 11 https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
you can check these...
Click to expand...
Click to collapse
Thank you so much!!!
and here's a pixel experience 12.1 https://sourceforge.net/projects/meowice-gsi/files/Pixel Experience 12/
i'm still testing. 11 roms feels a bit faster but that might be placebo lol ill test today and tomorrow and choose between the two. either pixel experience plus 12.1 or crdroid11
you can find the full list here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
there are some minor issues. like not having adaptive brightness... and screen recorder app crashes the system. but the general experience is pretty good so far.
zenfone selfie said:
and here's a pixel experience 12.1 https://sourceforge.net/projects/meowice-gsi/files/Pixel Experience 12/
i'm still testing. 11 roms feels a bit faster but that might be placebo lol ill test today and tomorrow and choose between the two. either pixel experience plus 12.1 or crdroid11
you can find the full list here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
there are some minor issues. like not having adaptive brightness... and screen recorder app crashes the system. but the general experience is pretty good so far.
Click to expand...
Click to collapse
I want to change my stock rom of my POCO c40, which one do you recommend?
currently the stock rom has a lot of Bloatware API calls
Phantom_KNA said:
Thank you so much!!!
Click to expand...
Click to collapse
have you tried any?
mahshadows said:
I want to change my stock rom of my POCO c40, which one do you recommend?
currently the stock rom has a lot of Bloatware API calls
Click to expand...
Click to collapse
android 13 roms have a problem with the camera. makes it look green
android 12 roms can't use the screen recorder
didn't test 11 roms extensively. but screen recorder was working on it.
since screen recording is not important for the user of this device, i installed pixel experience plus 12.1
this is the most recent android 11 gsi release if you wanna try it: https://sourceforge.net/projects/meowice-gsi/files/LineageOS/
and here's the android 12.1 lineageos https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i feel like pixel experience is better but you can try and compare it yourself.
i only noticed 3 issues on pe-plus so far
screen recorder as i mentioned.
status bar notification icons are bigger.
touching the fingerprint sensor while the screen is on registers random clicks on the screen. tho fp sensor works fine to unlock the phone.
and in the phh treble settings app you have to be careful, don't mess around with random settings... enabling "use alternative camera profile" option will cause a boot problem. it'll stuck on the boot animation screen and requires data wipe.
zenfone selfie said:
android 13 roms have a problem with the camera. makes it look green
android 12 roms can't use the screen recorder
didn't test 11 roms extensively. but screen recorder was working on it.
since screen recording is not important for the user of this device, i installed pixel experience plus 12.1
this is the most recent android 11 gsi release if you wanna try it: https://sourceforge.net/projects/meowice-gsi/files/LineageOS/
and here's the android 12.1 lineageos https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i feel like pixel experience is better but you can try and compare it yourself.
i only noticed 3 issues on pe-plus so far
screen recorder as i mentioned.
status bar notification icons are bigger.
touching the fingerprint sensor while the screen is on registers random clicks on the screen. tho fp sensor works fine to unlock the phone.
and in the phh treble settings app you have to be careful, don't mess around with random settings... enabling "use alternative camera profile" option will cause a boot problem. it'll stuck on the boot animation screen and requires data wipe.
Click to expand...
Click to collapse
thanks,
Is this the pixel experience plus 12.1 rom? https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
or do you have any other link?
mahshadows said:
thanks,
Is this the pixel experience plus 12.1 rom? https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
or do you have any other link?
Click to expand...
Click to collapse
meowice-gsi - Browse /Pixel Experience 12 at SourceForge.net
This repo includes newly built low-maintained GSI ROM...but with the latest security patches and sources.
sourceforge.net
PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi
zenfone selfie said:
meowice-gsi - Browse /Pixel Experience 12 at SourceForge.net
This repo includes newly built low-maintained GSI ROM...but with the latest security patches and sources.
sourceforge.net
PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi
Click to expand...
Click to collapse
excelent, thanks!!
mahshadows said:
excelent, thanks!!
Click to expand...
Click to collapse
you unlocked the bootloader and know how to install gsi roms, right?
it's my mother's phone and she's not tech savvy, so if she had any other problems she would've told me. using as a daily driver with no issues.
her apps were being killed in the background, couldn't do any multitasking on miui. that problem is now fixed with pe plus.
zenfone selfie said:
you unlocked the bootloader and know how to install gsi roms, right?
it's my mother's phone and she's not tech savvy, so if she had any other problems she would've told me. using as a daily driver with no issues.
her apps were being killed in the background, couldn't do any multitasking on miui. that problem is now fixed with pe plus.
Click to expand...
Click to collapse
I already have the bootloader unlocked, I just need to know how to install the GSI ROMS, can you please explain it to me?
mahshadows said:
I already have the bootloader unlocked, I just need to know how to install the GSI ROMS, can you please explain it to me?
Click to expand...
Click to collapse
if the bootloader is unlocked, first i'd recommend updating to the latest official firmware.
download it from here https://xiaomifirmwareupdater.com/miui/frost/stable/V13.0.20.0.RGFMIXM/
you need the fastboot rom, 5.7gb one. extract the files to a folder, boot to fastboot mode and run flash_all.bat
boot it once and check if the rom is updated properly. your version should be V13.0.20.0.RGFMIXM now.
download platform tools https://developer.android.com/tools/releases/platform-tools and extract it to a folder.
extract the pixel experience rom, place it in the platform tools folder. extension should be .img
copy the vbmeta.img and vbmeta_system.img files from the official rom and place em in the platform tools folder.
open the cmd in the platform tools folder, boot your phone into fastboot mode again.
run these commands:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot reboot fastboot
now you should be in the "fastbootd" mode.
fastboot erase system
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot flash system PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi.img
fastboot reboot recovery
then perform a factory reset from the recovery.
you can always go back to the miui by flashing the stock rom with flash_all.bat again.
@mahshadows did you install it?
zenfone selfie said:
@mahshadows did you install it?
Click to expand...
Click to collapse
I'm away from home without access to my laptop with the tools, as soon as I do, I'll confirm the result, thank you very much!
zenfone selfie said:
if the bootloader is unlocked, first i'd recommend updating to the latest official firmware.
download it from here https://xiaomifirmwareupdater.com/miui/frost/stable/V13.0.20.0.RGFMIXM/
you need the fastboot rom, 5.7gb one. extract the files to a folder, boot to fastboot mode and run flash_all.bat
boot it once and check if the rom is updated properly. your version should be V13.0.20.0.RGFMIXM now.
download platform tools https://developer.android.com/tools/releases/platform-tools and extract it to a folder.
extract the pixel experience rom, place it in the platform tools folder. extension should be .img
copy the vbmeta.img and vbmeta_system.img files from the official rom and place em in the platform tools folder.
open the cmd in the platform tools folder, boot your phone into fastboot mode again.
run these commands:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot reboot fastboot
now you should be in the "fastbootd" mode.
fastboot erase system
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot flash system PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi.img
fastboot reboot recovery
then perform a factory reset from the recovery.
you can always go back to the miui by flashing the stock rom with flash_all.bat again.
Click to expand...
Click to collapse
I am trying to install it, however, when entering fastboot it does not detect it, did you have a similar problem?
mahshadows said:
I am trying to install it, however, when entering fastboot it does not detect it, did you have a similar problem?
Click to expand...
Click to collapse
probably you should manually point the driver from device manager, but how did you unlock the bootloader if you didn't fix that issue in the first place? bootloader unlocking requires fastboot as well... i'm not on my windows environment rn so can't help but its a simple thing. if u need, i can try guiding you when i'm back to windows but it might take some time.
zenfone selfie said:
probably you should manually point the driver from device manager, but how did you unlock the bootloader if you didn't fix that issue in the first place? bootloader unlocking requires fastboot as well... i'm not on my windows environment rn so can't help but its a simple thing. if u need, i can try guiding you when i'm back to windows but it might take some time.
Click to expand...
Click to collapse
I did the unlocking from another PC, I had to manually load the drivers, and I'm already loading the new software.
zenfone selfie said:
@mahshadows did you install it?
Click to expand...
Click to collapse
I am already installed and it works very well so far, thank you very much for the support!
mahshadows said:
I am already installed and it works very well so far, thank you very much for the support!
Click to expand...
Click to collapse
now in phh treble settings:
you can enable dt2w in xiaomi settings tab
and fix bluetooth audio by enabling "Force-disable A2DP offload" in misc settings.
i didn't touch other settings, as i said before, some of those settings can cause a problem and would require a factory reset from the recovery again. these 2 are safe.
also if you root the phone please tell me how it goes... i didn't try that yet but might need root to customize some stuff then unroot it back. since its my mother's phone i don't wanna give a rooted phone to her. she might accidentally grant root access to unknown apps and she's using banking apps.