View attachment 5438975
" #DroidOnTime "
ROM Version: 5.2.1
Device: PAYTON
Maintainer: AADITYAZEO
Build Status: OFFICIAL
View attachment 5438991
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Click to expand...
Click to collapse
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."
View attachment 5438997
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
View attachment 5438999
CLEAN FLASH/First Time Installation :
01. Download the ROM, Firmware and GApps from the links above.
02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.
03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
04. Create backup. i.e. EFS
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##
05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
06. Flash the ROM and TWRP installer.
07. Choose Reboot -> Recovery
08. Install GApps & Magisk.
09. Reboot -> Bootloader
10. fastboot -w
11. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-2: Firmware's
* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)
DIRTY FLASH :
1.Download the latest build.
2.Reboot to recovery.
3.Flash the latest build along with the twrp.
4.reboot to recovery. (very Important)*
5.flash optional packages like gapps and magisk.
6.Wipe Cache.
7.Reboot.
Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
View attachment 5439003
CLICK ME
View attachment 5439005
COMPLETE CHANGELOG : https://changelogs.droidontime.com/
View attachment 5439007
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
View attachment 5439009
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd
dot OS source
dotOS-Device Sources
{
"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"
}
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
View attachment 5439011
Contributors: AadityaZeo
Source Code: https://github.com/DotOS
GitHub : - https://github.com/aadityazeo
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 23-11-2021
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Same problem be my.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Which Verison of twrp you're using?
Aaditya ZeO said:
Which Verison of twrp you're using?
Click to expand...
Click to collapse
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, booting to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Randy Power said:
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, boring to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Click to expand...
Click to collapse
There're quite few things which you need to remember.
1st
2nd
If you were stuck on boot logo, you should perform fastboot - w in bootloader.
3rd - as per your comment u want vanilla edition. So i suggest u to stick with two 3.5xxx (latest prior to version 3.6xx) and follow the steps as stated below
a) completely wipe the phone
b) rom + twrp
c) reboot to recovery
d) wipe data in twrp
e) reboot to system.
This should work as I've also installed vanilla Verison with same process.
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Randy Power said:
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Click to expand...
Click to collapse
I don't think it matters, I've use twrp 3.2 and 3.6 to install gapps and had no issues in either case.
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Randy Power said:
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Click to expand...
Click to collapse
Can you try to install gapps version for once?
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
After the above, I formatted data from twrp. It completed without errors, so I rebooted to system.
Result: Still stuck on spinning planets.
Randy Power said:
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
nope this shouldn't be the output after the fastboot -w.
Aaditya ZeO said:
nope this shouldn't be the output after the fastboot -w.
Click to expand...
Click to collapse
I appreciate that. I've tried many combinations of formatting data in TWRP, which seems to work. Resizing the partition and fsck on the partition work fine, all in TWRP. I can even copy files from /externalsd to /sdcard, and the fs survives a reboot.
However, fastboot -w always fails (error shown above), and booting the system gives spinning planets animation forever.
I'd be grateful for pointers on fixing the fastboot -w problem, if that is what's needed.
Hello
I installed dotOS 5.2.1 and when it's time to enter the PIN code it says that the sim card is locked. Tried both PIN and PUK, but none works. What should I do?
OK, so I solved it by basically following these instructions:
However, I now have a new problem. If I power off the phone while the USB charger is connected, it restarts the phone instead. And if it's powered off and I connect the charger, it turns itself on. This didn't happen with Android 9. How can I fix it? I do not want my phone to switch itself on when charging.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Are you flashing to the appropriate slot?
For those having problems with the phone rebooting after a few seconds after upgrading from an Android 9 rom:
You might need to upgrade the modem firmware. That happened to me while upgrading from Lineage 16.0 to Lineage 18.1. After investigating a bit, I figured out the problem happened when connecting to the mobile network or (sometimes) wifi.
This is (roughly) how I solved the problem:
- flash your choice of recovery/system (not needed if already done - if you do this later your updated firmware might be overwritten)
- download the latest payton stock rom from lolinet's obsolete phones archive
- unzip and cd to unzipped folder
- connect phone and reboot to bootloader
- make sure you have fastboot and run the following commands (adapt to your OS as needed):
mfastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata (I did it after backing up my data, but I think it was not necessary)
fastboot erase ddr
fastboot reboot
- have fun!
Notes:
- you might just flash a subset of the binaries above, I flashed what I thought was needed. The original reddit thread mentioned only NON-HLOS.bin and fsg.bin
- after having tried many things I ended up with dotOS 5.2.1 and will try it for a while
References
- this reddit comment
- Method 2 at rootmygalaxy
rodrigopitanga said:
Are you flashing to the appropriate slot?
Click to expand...
Click to collapse
I think yes. It's been a few weeks now, so my memory on the details is fuzzy. But I'm familiar with the A/B monkey business, copy partitions, etc. And flashing lineage worked out successfully. Thank you for the reply.
Does adoptable storage work?
Related
Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"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"
}
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.
*/
About Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.
{
"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"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!
XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22
Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA
reserved
reserved3
reserved4
reserved5
reserved6
Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support
And I'll take this one, just for the kicks.
I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.
First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs
it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)
This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk
Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!
issue has been fixed
JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.
neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots
JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.
{
"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"
}
« Disclaimer & INFO »
Code:
# include <std_disclaimer.h>
/*
* Your warranty is... Still valid??.
*
* 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 KERNEL
* 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.
*/
Note: I'm just a library man all works saved to their owners this kernels made by love check credits. All copyright saved here with developer premison
Click to expand...
Click to collapse
Name of Kernel: LegionX
Version of kernel: 2.0 NEW
Lates stable Update: 2021/sep/03
Supported Roms: MIUI & AOSP
Status: Stable
UNIFIED = MOJITO / SUNNY
« Changelogs »
[ Latest Release Changelog ]
Check Post #2 (click number) for changelogs
« NOTES »• In MIUI / MIUI based ROMs, kernel version will show "Unavailable" because MIUI doesn't support long names (because I used proton clang and lld) but kernel working perfectly you can see name in FKM tough.
• It's AIMING on Performance, stability,..
• If you can't flash with TWRP , use FK manager to flash it "root required".
• KCAL works fine .Everytime you changed value in KCAL just screen off (Don't power off) and open screen .
New value will apply.
• If your device not booting to system just bootloop or fastboot only. Don't panic. re-flash your rom file without wiping data. And please report here with the name of rom and any details.
• If you update TWRP recovery, reflash the kernel again too.
• You don't need to Wipe data ! Only cashe and Dalvik.
• Report for any bugs/issues with logs if available.
« DOWNLOADS »Latest Stable Build (LegionX V2.0):
• Click here to download LegionX V2.0 (MIUI/AOSP)
Previous Stable build:
• Click here to download V 1.0-LTO (AOSP Only) Build
« INSTALLATION »1- Download Kernel & save it on internal storage.
2- Boot to recovery (TWRP).
3- Flash the kernel zip file.
4- Wipe Cashe & Dalvik. “Don't Wipe Data”
5- Reboot to system.
NOTE: For pixel experience rom, use this Guide:
Spoiler: GUIDE FOR Pixel experience Rom
IT'S can safely installed on Pixel experience. Just follow this:
1- Boot TWRP recovery with this command:
Code:
fastboot boot twrp.img
2- Don't Install ramdisk or anything just go to LegionX Kernel on your storage and flash it.
3- Wipe Cashe & Dalvik.
4- Power Off then power on your device.
Done.
« CREDITS »• Kernel by: @venom_stark , Thanks
• Thanks to @ZIDAN44 , @CloudedQuartz ,@cyberknight777 & @Shararti1 .
• Thanks @AnomYT for Banner
• XDA-OP: @Abdullah.Csit
• #All testers.
• GitHub Source Link: https://github.com/venom-stark/mojito...
SHOW YOUR SUPPORT BY HITTING LIKE
Click to expand...
Click to collapse
#Kernel Changelogs 2021/9/03:
Code:
LegionX v2.0:
-schedtune_assist: Cleanup and update
-sched/tune: Only force UX tasks to big cores
-f2fs: Enlarge min_fsync_blocks to 20
-diag: Add timer to make sure wakelock no stuck
-fs: Reduce cache pressure
lib/string: optimized memcpy,memmove, memset
-arm64: Import latest memcpy()/memmove() implementation
-ARM64/dts: qcom: Disable CoreSight DT entries for sdmmagpie
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-msm: adreno: Relax CPU latency requirements to save power
-sched/fair: fix misfit with PELT
-qos: Don't allow userspace to impose restrictions on CPU idle
-mmc: Disable SPI CRC
-iommu: msm: Rewrite to improve clarity and performance
-PM: sleep: Don't allow s2idle to be used
-rcu: Speed up calling of RCU tasks callbacks
-Enable JUMP_LABEL and added some jump lebel patches
Spoiler: Old changelog
Code:
➡️ 2021/8/4 |
• MIUI not supported in this update ( On V2.0 will get update)
• Used LTO binary optimization
• Complied using proton clang with lld linker.
• Performance improvement
• Battery backup improvement
#Thread Changelog:
// 2021.august.4 //
- Introduce the new LOGO
- Kernel Updated ! 2021/8/4
- Added new note about MIUI in new update To «NOTES» section (IMPORTANT)
//
Can i flash this for MIUI EU rom?
lakshmish said:
Can i flash this for MIUI EU rom?
Click to expand...
Click to collapse
Yes
Abdullah.Csit said:
#Thread Changelog:
// 2021.july.22 //
- Added new note To «NOTES» section about KCAL (IMPORTANT)
//
Click to expand...
Click to collapse
Okay, lets try flashing this one
IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.
Pachunko said:
Okay, lets try flashing this one
Click to expand...
Click to collapse
Glad to know if it success
Anish Louis said:
IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.
Click to expand...
Click to collapse
Which rom?
Abdullah.Csit said:
Glad to know if it success
Click to expand...
Click to collapse
Unfortunately it wasn't, fastboot too. I quit kernels for good I guess.
EDIT: Maybe I need to flash latest stock firmware? Just an idea.
You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.
Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.
StaryMuz said:
You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.
Click to expand...
Click to collapse
Reported to developer
Developer answer : “Ok I will flash PE+ now and test camera.”
Tested : Camera working perfectly on PE+.
Pachunko said:
Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.
Click to expand...
Click to collapse
At less test flashing Latest firmware it won't be hard and it's good for your device anyway.
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Just use fastboot recovery OTA tool flash CRdroid with it. Then wait till you boot in TWRP
Wipe data
Flash kernel
Reboot system
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
It's a dynamic virtual A/B phone traditional way of flashing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Edit: Don't need to flash TWRP in rom in which it pre-installed.
venom_stark said:
It's a dynamic virtual A/B phone traditional way of fishing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Click to expand...
Click to collapse
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
the critical error is, you don't start the ROM after installing the rom.
flash the rom, start the rom, create a password/pattern so you get /data encryption key (you can disable it right after, but let system set it up once)
then, start flashing the rest. (installing gapps however might be necessary before booting it up for the fist time, idk)
if system can't decrypt /data, you will end up in a bootloop and/or fastboot loop.
I
Abdullah.Csit said:
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards
Click to expand...
Click to collapse
Yeah I forgot. But flashing through LOS or PE recovery will give 100% success boot.
I can't flash stock now at all... I get this error in mi flash:
error: Writing 'metadata'
FAILED (remote: 'Flashing of metadata is not allowed in snapshotted state')
so phone is bricked, not sure what to do. I can only get to fastboot currently
{
"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"
}
Code:
/*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.6.0_11
For device: gta4lwifi
Device tree: https://github.com/pazos/android_device_samsung_gta4lwifi
Maintainer/Authors build: paziusss
Known limitations
FBE encrypted storage (Internal Data) not able to be decrypted in TWRP.
Changelog
2021-12-08:
Added: exfat support
Added: mass storage support
Fixed: USB composition rules
Supressed audit messages in logcat
Misc changes (see device tree for details)
2021-12-05: Initial release
Motivation and credits.
AFAICT there're two TWRP builds on xda for the SM-T500, made by ragarcia87 and agreenbhm
The main motivation for Yet Another TWRP build was getting fastboot working, so we can follow official instructions to flash GSI builds on our devices.
Credits to u/agreenbhm for the device tree: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Credits to u/ragarcia87 for the thread, which I used as a template for this one
Installation Instructions
Spoiler
From computer:
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
From TWRP:
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Flashing system/vendor/product/odm partitions
Spoiler
Logical partitions are read only from TWRP. If you want to flash them you'll need to reboot in fastbootd.
Boot in TWRP
Go to reboot and select fastboot.
Wait until you see a TWRP dialog saying "entered in fastboot"
Once you flashed all desired partitions reboot to recovery
In recovery wipe -> format data.
Notes on GSI flashing:
/product partition is unused in GSI builds. You can flash an empty image to gain 1GB for other logical partitions.
/system partition will be resized to the size of the GSI image you're flashing.
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Hi Magendanz. Thanks for your feedback.
I have no issues mounting the MicroSD card. Do you have some logs?
Updated DT link!
About the device tree: I'm having trouble pushing the changes to github because my slow connection. Will see if I got them pushed somehow. If not I will revert blobs to agreenbhm version.
Magendanz said:
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Click to expand...
Click to collapse
paziusss said:
I have no issues mounting the MicroSD card. Do you have some logs?
Click to expand...
Click to collapse
Here's the log...
Hi!
Indeed, I didn't test with exfat. Should be fixed soon. Also adb sideload don't work in the version attached.
I will make the changes ASAP and give a better commit history in device tree
Hi. Device tree updated with support for exfat and ADB sideload fixed.
Will upload the binaries in a few hours!
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
stompysan said:
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
Click to expand...
Click to collapse
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Hi. I've updated recovery binaries and added a changelog.
Please report the issues you find.
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
Will it work with Pixel Experience?
EdwardTCM said:
Will it work with Pixel Experience?
Click to expand...
Click to collapse
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
paziusss said:
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
Click to expand...
Click to collapse
Alright Thanks
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Edit: Maybe this is happening because of the ROM being A only
EdwardTCM said:
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
Click to expand...
Click to collapse
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
thank you for twrp and fastboot but i noticed that most gsi images are bugy no brightness or randemly rebooting
paziusss said:
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
Click to expand...
Click to collapse
OOOH I thought it was A Only
EdwardTCM said:
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
EdwardTCM said:
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
Click to expand...
Click to collapse
Btw the wifi doesn't work
One Issue when downgrading to TWRP 3.5 is that it will boot loop
{
"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 Mi 11 Lite 5G [renoir]
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 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
You tell me
FLASH GUIDE
Note that if you can't use bluetooth audio. Try to follow here.
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download
thirteen : [ SourceForge | Selfhosted ]
thirteen_plus : [ SourceForge | Selfhosted ]
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Maintainer Channel
Maintainer Chat (CN/EN)
Changelog:
Apr, 04, 2023 Update
Hoya~ Greetings! Here is Hana. Bring you latest PixelExperience update. Here is a berif introduction to this update.
Notice:
1. Since there are a lot of changes in kernel side. You must to flash boot, dtbo, vendor_boot manually to make sure use latest aosp recovery that can correctly flash the update package.
Improvements:
1. Improved memory performance: The available memory has been significantly improved, and the average usage has been reduced by 15-20% compared to the previous version.
2. Move to erofs: Five partitions switched to erofs, which helps to improve performance.
3. Power saving optimization: The kernel uses a series of patches to reduce power consumption
4. Overall system smoothness improvements
5. Merge March 05, Security Patch.
Fixes:
1. Bluetooth issue has been fixed.
2. Google Recorder has been fixed.
3. Alipay/WeChat fingerprint payment has been fixed.
Details:
1. Sync latest source code ( Android 13 QPR2 )
2. Initial PixelExperience Plus Edition build.
3. Move to OSS aptX audio ( Also fixed bluetooth )
4. Move { system | vendor | system_ext | product | odm } partitions to erofs
5. Backport latest erofs features from linux-6.1
6. Enable erofs per cpu decompression feature ( with high priority kthread )
7. Backport Data Access Monitor ( DAMON ) from linux mainline
8. Enable DAMON-based reclaim and lru sort.
9. Backport MutliGen LRU from Chromium Project
10.Enable MutliGen LRU support by default.
11.Kang zram driver from linux-5.15
12.Enable ZRAM WriteBack && Deduplication.
13.Port LZ4 1.9.x FAST_DEC_LOOP and enable it.
14.Set zram compression algorithm and erofs decompressor to lz4 by default.
15.Backport Lazy RCU feature and enable by default.
16.Backport a series of userfatalfd/mm changes from upstream kernel.
17.Switch to new mm locking api to ensure memory safety.
18.Fixed Google Recorder.
19.Update blobs from renoir CN V14.0.8.0.
20.Disable a series of log spam.
21.Move to power effiency workqueue.
22.Label more selinux denieds
23.Kernel components merged to CLO tag 'LA.UM.9.14.r1-21300-LAHAINA.QSSI12.0'
24.Provide both sourceforge and selfhosted mirrors
Android OS version: 13
Security patch level: March 2023
Build author/Device Maintainer: EndCredits
Device Source code: https://github.com/EndCredits/android_device_xiaomi_renoir
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
the photos taken with any camera application show different tones than usual and in certain cases of lighting shows certain black lines only in this rom
spotify crashes instantly not working
RichyValents13 said:
spotify crashes instantly not working
Click to expand...
Click to collapse
For me it's working ( From Play Store )
RichyValents13 said:
the photos taken with any camera application show different tones than usual and in certain cases of lighting shows certain black lines only in this rom
Click to expand...
Click to collapse
Will integrate a new Camera App in the next version
Hello! Flashed the rom yesterday and so far, it's very smooth! I haven't noticed any major stutters or issues so far. The only thing that doesn't work is the Android easter egg. Whenever a cat tries to appear, the program just crashes.
You've done a great job, so keep it up!
MrDoctor175 said:
Hello! Flashed the rom yesterday and so far, it's very smooth! I haven't noticed any major stutters or issues so far. The only thing that doesn't work is the Android easter egg. Whenever a cat tries to appear, the program just crashes.
You've done a great job, so keep it up!
View attachment 5884621
View attachment 5884377
Click to expand...
Click to collapse
I recommend doing the clean installation, installing the bto vendro files and others, formatting everything
Great optimization work in the new version 04/04/2023, but if for the previous version it had something better why at least Skyline Edge opened me and ran the games wonderfully and now it crashes only when opened
Guillermo55 said:
I recommend doing the clean installation, installing the bto vendro files and others, formatting everything
Click to expand...
Click to collapse
That's what I did when I first flashed, so I don't think it's just a personal problem
I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.
Which firmware version is recommended for this rom & can one dirty flash from eg Banana droid rom 13/3/23 pls? I'm finding the latter doesn't fully unlock the screen on my Mi 11 5G Lite. I get a strange vigentting type effect quite often, before tapping home button again fully opens up the screen.......its like the fingerprint sensor is not always repsonding on banana droid & that was installed with a clean install with all dtbo, rom & vendor files....
Hammerlig said:
I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
As far as I knew & always read the adb sideload process always shows as getting to 47% but after a pause, the abd etc program goes to the next line and on rebooting the phone, the new rom is present & working...
TheDon13 said:
Which firmware version is recommended for this rom & can one dirty flash from eg Banana droid rom 13/3/23 pls? I'm finding the latter doesn't fully unlock the screen on my Mi 11 5G Lite. I get a strange vigentting type effect quite often, before tapping home button again fully opens up the screen.......its like the fingerprint sensor is not always repsonding on banana droid & that was installed with a clean install with all dtbo, rom & vendor files....
Click to expand...
Click to collapse
I have the 14.0.6.0 firmware and I have no problems with the rom. Also it's the best if you always clean flash if you're moving from another rom
TheDon13 said:
As far as I knew & always read the adb sideload process always shows as getting to 47% but after a pause, the abd etc program goes to the next line and on rebooting the phone, the new rom is present & working...
Click to expand...
Click to collapse
But as far I could see, the transfer just stopped? My phone said there was an error, and when I tried to reboot the phone, it came up with the MIUI logo and then went into Fastboot.
MrDoctor175 said:
I have the 14.0.6.0 firmware and I have no problems with the rom. Also it's the best if you always clean flash if you're moving from another rom
Click to expand...
Click to collapse
Isn't a clean flash just booting the boot.img, vendor_boot.img and dtbo.img?
Would it be better to flash the MIUI rom and then follow this process once again? I must have done something wrong, since it's working for everyone else.
Hammerlig said:
But as far I could see, the transfer just stopped? My phone said there was an error, and when I tried to reboot the phone, it came up with the MIUI logo and then went into Fastboot.
Isn't a clean flash just booting the boot.img, vendor_boot.img and dtbo.img?
Would it be better to flash the MIUI rom and then follow this process once again? I must have done something wrong, since it's working for everyone else.
Click to expand...
Click to collapse
As long as I know, a clean flash is flashing the mandatory files, format data and then flash the rom. How I did it is flash boot_ab "boot.img", flash vendor_boot_ab "vendor_boot.img", flash dtbo "dtbo.img", boot to recovery, format data, flash from adb, adb sideload the package, wait and then reboot.
will this rom be continued after Xiaomi abandones the beta/dev rom's after the 21st of april ?
my bluetooth isnt working... do i need to update firmware?
Does this rom have call recording built in?
Hammerlig said:
I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I tried to install Pixel Experience Plus, which is also what I tried to install last time. After the same thing happened again, I tried installing the normal Pixel Experience and that was successful. Don't know if it was just me having issues installing the Plus version.
j0k1n9 said:
my bluetooth isnt working... do i need to update firmware?
Click to expand...
Click to collapse
My Bluetooth isn't working either. I turn it on and then it just turns off right away. I flashed boot.img, vendor_boot.img and dtbo when installing. Happens for me on the regular version of PE.
Hammerlig said:
I tried to install Pixel Experience Plus, which is also what I tried to install last time. After the same thing happened again, I tried installing the normal Pixel Experience and that was successful. Don't know if it was just me having issues installing the Plus version.
My Bluetooth isn't working either. I turn it on and then it just turns off right away. I flashed boot.img, vendor_boot.img and dtbo when installing. Happens for me on the regular version of PE.
Click to expand...
Click to collapse
I installed MIUI 14.0.6 EEA, and then went over the process with this version of PE Plus. Flashed succesfully and seems to be working. Nice!