Database Info

[recovery][lm-g710em]twrp 3.2.1[persistent]

[UNOFFICIAL] TWRP 3.2.1 for LM-G710EM ONLY
{
"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"
}
​
NOTE
There are 2 versions for this recovery, SEMI-PERSISTENT & PERSISTENT.
1. Semi-Persistent Recovery
[Works on stock rom and custom rom] Not permanent, requires command in order to boot and needs to reflash it every time you need it and then reflash stock boot.img after using it in order to avoid bootloop.
2. Persistent Recovery
[Works only on custom rom] Permanent, you can boot on it anytime without a command and doesn't need to reflash it and stock boot.img.
Flashing TWRP Recovery
Downloads:
[SEMI-PERSISTENT] TWRP 3.2.1
[PERSISTENT] TWRP 3.2.1
1. You need to be rooted first. Root Guide: Magisk
2. Flash TWRP image (Download link above) using the following command:
Code:
fastboot flash boot_a pathtoimghere
and
Code:
fastboot flash boot_b pathtoimghere
Note: In this state, you will encounter bootloop when you restart your device and proceed to OS. So please, don't.
3. Boot to recovery using the button combination (VOLUME DOWN + POWER BUTTON).
4. Once you are booted in TWRP, you might notice that /date doesn't work. To fix it, you need to decrypt your phone.
For now, flash the vendor.img found here.
5. After step #4, Hit Wipe and Format Date on TWRP, type yes in the dialog, and then reboot to recovery (not system). TWRP will now be useful.
6. If you are on 10f or 10h stock rom download this TWRP then mount vendor and system, flash the zip through TWRP to enable semi-persistant.
SUPPORT
If you need any help for this or in general or if you just want to have a chit chat, feel free to join our Telegram Group:
LG G7 ThinQ XDA Community Telegram Group
Others:
Official LG G7 Subreddit
LG Community Discord
CREDITS
Me (for the initial G7 TWRP device tree)
Rashed97 (for his great help to make me understand how recovery works on a/b devices)
Skullpluggery (for polishing the thread)
I hope i didn't forgot anyone , if i did im sry , hit me up and i will add you here.

Why is this TWRP semi persistent
So The g7 is a a/b device meaning it has 2 system paritions etc , but it doesnt have a recovery parition anymore so recovery is now a binary inside of boot.img which gets executed when hitting the button combo , but to have to you need to flash the boot.img containing it , and thats the point the boot.img containig twrp isnt compatible neither to aosp nor to stock meaning your phone would probably stuck in a bootloop or a reboot loop , so only thing we can do for now is flashing back our boot.img after were done with twrp, im working on it and i was able to smack twrp into the stock boot.img but it doesnt work correctly anymore then , I've finished my work on a variant that works without a pc needed

Persistance reached us , YAY
This is ONLY for AOSP OREO AND PIE flash this bootimage using fastboot flash boot_a pathtoimg or fastboot flash boot_b pathtoimg
Then TWRP will be always present no annoying flashes anymore

Can I flash normal zip files with recovery? because not everything is supposed to go.

Sony92 said:
Can I flash normal zip files with recovery? because not everything is supposed to go.
Click to expand...
Click to collapse
yes you can do everything once your decrypted , this twrp just wont stick

can someone please tell me if i have the buttons before warning that the bootloader is unlocked or after the warning? it's about booting to recovery after flashing the recovery.img. Unfortunately, I did not manage it yesterday.
should you flash at step 4 the file on the recovery, or via adb sideload?

hello mate long time no chat lol thinking of getting the g7 got one plus 6 at min will the fix for the one plus that makes the recovery stick work on this ?

will the error be corrected over time? because after the first reboot into the system the recovery disappeared again. I would like to boot again into recovery after being in the system, it no longer exists. I followed everything according to instructions

strikerdj2011 said:
hello mate long time no chat lol thinking of getting the g7 got one plus 6 at min will the fix for the one plus that makes the recovery stick work on this ?
Click to expand...
Click to collapse
damn youre still alive good to talk again , no that is only for the op6 , but this is my first work for a/b but meanwhile i got a main idea what to do , all i need rn is a linux machine

Sony92 said:
will the error be corrected over time? because after the first reboot into the system the recovery disappeared again. I would like to boot again into recovery after being in the system, it no longer exists. I followed everything according to instructions
Click to expand...
Click to collapse
thats what non persisrant mean youi always have to flash the recovery boot.img first

Great to know development is picking up on this device. Waiting for supplies to hit the rest of the world so I can get an European variant. ** Thumbs Up **

stupid question but does the locked bootloader on usa versions disallow booting unsigned images over "fastboot boot" command also?

just got a g7 what we going to cook up this year

strikerdj2011 said:
just got a g7 what we going to cook up this year
Click to expand...
Click to collapse
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do

J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
**** that mate
---------- Post added at 07:49 PM ---------- Previous post was at 07:34 PM ----------
strikerdj2011 said:
**** that mate
Click to expand...
Click to collapse
J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
whats going rate for a linux server

J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
Hi.
As a developer, do you think it is possible enable HDMI out via kernel update?
https://forum.xda-developers.com/lg-g7-thinq/help/usb-c-to-hdmi-t3809408
Thanks.
Sent from my LM-G710 using Tapatalk

ricxgp said:
Hi.
As a developer, do you think it is possible enable HDMI out via kernel update?
https://forum.xda-developers.com/lg-g7-thinq/help/usb-c-to-hdmi-t3809408
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck

J0SH1X said:
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck
Click to expand...
Click to collapse
another year another ****ed up source from lg

J0SH1X said:
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck
Click to expand...
Click to collapse
Thanks.
It is a shame what LG does...
I am really thinking about sell the LG G7, I really like the phone but this kind of thing are shamelessl...
Sent from my LM-G710 using Tapatalk

ricxgp said:
Thanks.
It is a shame what LG does...
I am really thinking about sell the LG G7, I really like the phone but this kind of thing are shamelessl...
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
exactly my thought awesome device but zero support from lg even q6 with is mid/low got 8.1

How to verify flashed firmware version (when on custom ROM)?

I just flashed a custom ROM (Pixel Experience A11) originally starting from MIUI Global 12.0.4
Then I flashed the Global 12.0.7 firmware via TWRP (found here https://xiaomifirmwareupdater.com/firmware/surya/).
However, I forgot to check version numbers of anything before flashing, so I don't know what to look for to verify the new firmware is flashed properly?
Thanks!

@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
{
"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"
}

jeryll said:
@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
Click to expand...
Click to collapse
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.

uddinf said:
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.
Click to expand...
Click to collapse
please if you stick with the Orange fox recovery install the latest version, enjoy

jeryll said:
please if you stick with the Orange fox recovery install the latest version, enjoy
Click to expand...
Click to collapse
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have

uddinf said:
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have
Click to expand...
Click to collapse
look for the release row, it's there

jeryll said:
look for the release row, it's there
Click to expand...
Click to collapse
I was meaning the Xiaomi FW version. It doesn't show for some reason.

uddinf said:
I was meaning the Xiaomi FW version. It doesn't show for some reason.
Click to expand...
Click to collapse
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...

jeryll said:
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...
Click to expand...
Click to collapse
I appreciate all the input
Correct, I did not flash vendor so that is likely my problem.
I will follow your post and flash the MIUI.eu archive
One question though, you say "needed to be flashed before flashing custom ROM"...
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?

uddinf said:
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?
Click to expand...
Click to collapse
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...

jeryll said:
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...
Click to expand...
Click to collapse
Everything seems to be up and running. thanks for all the help!

How to check after getting to oragr fox mane page

[ROM] [UNOFFICIAL] DotOS 5.2 for Redmi 9C [angelica] [10/22/2021]

{
"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"
}
" #DroidOnTime "
ROM Version: 5.2
Device: Xiaomi Redmi 9C (angelica)
Maintainer: Mikazuuu07
Build Status: UNOFFICIAL
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.
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."
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.....
FLASHING INSTRUCTIONS:
Download the latest build
Reboot to recovery
Format data
Flash the latest build
Reboot to DotOS 5.2 (booting the ROM first is a must)
Reboot to recovery
Flash Gapps (preferably NikGapps - core)
Flash Magisk (optional)
Reboot
Mega
Google Drive
Complete Changelogs: https://changelogs.droidontime.com/
Known Bugs:​
Hotspot not working (use Magisk Module to fix)​
Double Tap To Wake not working​
Offline Charging​
Sound issue while making calls (you can barely hear anything)​
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
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
dot OS source
dotOS-Device Sources
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
Join Device Support group​Contributors: Mikazuuu07, ImFatF1sh, KangHexa, Naho2103
Source Code: https://github.com/DotOS
Kernel Source: - https://github.com/rama982/kernel_xiaomi_angelica
ROM OS Version: 11.x Android R
Version Information
Status: Alpha
Current Stable Version: v5.2
Stable Release Date: 10-22-2021

Thank you very much for contribution

I dont know if its just me having this problem but i flashed the ROM and it booted just fine, however I did not flash Gapps or magisk. I just loaded the ROM and everything was great. I rebooted into recovery to flash Gapps and magisk and got red letters error( See screenshot below). Something about a BLOCK??
I tried it 3 times thinking im doing something wrong but each time same result.
The last time I tried, I noticed that I get this error even when I just wiped Dalvik, Cache and Data. I then did not flash anything and rebooted into ROM and it booted fine. As soon I flash anything else I end up with either bootloop or it keeps booting into recovery.

Dawood99 said:
I dont know if its just me having this problem but i flashed the ROM and it booted just fine, however I did not flash Gapps or magisk. I just loaded the ROM and everything was great. I rebooted into recovery to flash Gapps and magisk and got red letters error( See screenshot below). Something about a BLOCK??
I tried it 3 times thinking im doing something wrong but each time same result.
The last time I tried, I noticed that I get this error even when I just wiped Dalvik, Cache and Data. I then did not flash anything and rebooted into ROM and it booted fine. As soon I flash anything else I end up with either bootloop or it keeps booting into recovery.
Click to expand...
Click to collapse
Oh yes, about that. You have to boot the ROM first before flashing GAPPS and Magisk, as per the instructions above. For GAPPS, I would recommend using NikGAPPS on a "Core" variant. I also tried flashing different GAPPS package before, but I think the ROM itself prevents me from installing some of my chosen GAPPS. Other than that, about the "red letters error", you just have to ignore them. I believe they've got to do something related to the Android 11 vendor cause we don't have one. Try flashing Android 10 ROMs (such as LineageOS 17.1), you wouldn't get the same error.

Dawood99 said:
I dont know if its just me having this problem but i flashed the ROM and it booted just fine, however I did not flash Gapps or magisk. I just loaded the ROM and everything was great. I rebooted into recovery to flash Gapps and magisk and got red letters error( See screenshot below). Something about a BLOCK??
I tried it 3 times thinking im doing something wrong but each time same result.
The last time I tried, I noticed that I get this error even when I just wiped Dalvik, Cache and Data. I then did not flash anything and rebooted into ROM and it booted fine. As soon I flash anything else I end up with either bootloop or it keeps booting into recovery.
Click to expand...
Click to collapse
Talking about the bootloop, there's a workaround for that. You just have to flash the stock recovery, boot into the stock recovery, and perform a factory in the stock recovery. That way, you will be able to boot it again.

LiaFourté said:
Oh yes, about that. You have to boot the ROM first before flashing GAPPS and Magisk, as per the instructions above. For GAPPS, I would recommend using NikGAPPS on a "Core" variant. I also tried flashing different GAPPS package before, but I think the ROM itself prevents me from installing some of my chosen GAPPS. Other than that, about the "red letters error", you just have to ignore them. I believe they've got to do something related to the Android 11 vendor cause we don't have one. Try flashing Android 10 ROMs (such as LineageOS 17.1), you wouldn't get the same error.
Click to expand...
Click to collapse
Oh wait, I knew this would happen. I apologize for the wrong steps, it's just, I got them from the Indo community. I will replace them with my own steps from now on.

LiaFourté said:
Oh yes, about that. You have to boot the ROM first before flashing GAPPS and Magisk, as per the instructions above. For GAPPS, I would recommend using NikGAPPS on a "Core" variant. I also tried flashing different GAPPS package before, but I think the ROM itself prevents me from installing some of my chosen GAPPS. Other than that, about the "red letters error", you just have to ignore them. I believe they've got to do something related to the Android 11 vendor cause we don't have one. Try flashing Android 10 ROMs (such as LineageOS 17.1), you wouldn't get the same error.
Click to expand...
Click to collapse
Ohk yeah cos I noticed that error only with the DotOs ROM cause I'm back on lineageOs. I'll just stick with the tried and tested. Cause I tried NikGapps core package but it also happens with magisk which is strange.

Nice trick
LiaFourté said:
Talking about the bootloop, there's a workaround for that. You just have to flash the stock recovery, boot into the stock recovery, and perform a factory in the stock recovery. That way, you will be able to boot it again.
Click to expand...
Click to collapse
Nice trick I'll definitely try it next time I'm stuck with bootloop

Dawood99 said:
Ohk yeah cos I noticed that error only with the DotOs ROM cause I'm back on lineageOs. I'll just stick with the tried and tested. Cause I tried NikGapps core package but it also happens with magisk which is strange.
Click to expand...
Click to collapse
It is working fine for me tho.

Dewltodin said:
It is working fine for me tho.
Click to expand...
Click to collapse
I found a work around to the magisk flashing problem. I installed the magisk APK first and then rebooted to recovery to flash magisk zip but I'm on pixel experience. Tried pixel and found I had the exact same error as with dotOS. Maybe it's my phone Lord knows I bricked it a couple of times already lol

At last you got it. Congrats man. Btw is this pixel ex.

Nice!

Dewltodin said:
At last you got it. Congrats man. Btw is this pixel ex.
Click to expand...
Click to collapse
Thanks yeah it's pixel experience and so far so good it's only hotspot and slower charging like the rest of roms but gaming is more fluid than lineageOS I feel. I still wanna try dotOS but I'm gonna give pixel n week or so. Kinda lazy now to flash and copy everything over again lol

Car parcing -

Wifi and Bluetooth don't work. HELP!

| AnthonyFararoni | said:
Wifi and Bluetooth don't work. HELP!
Click to expand...
Click to collapse
Use MIUI 12.0.10 global base

LiaFourté said:
Use MIUI 12.0.10 global base
Click to expand...
Click to collapse
Thank you so much!
Some apps like Rocket League Sideswipe cannot be installed; is there any solution? Maybe a 64 bit OS?

| AnthonyFararoni | said:
Thank you so much!
Some apps like Rocket League Sideswipe cannot be installed; is there any solution? Maybe a 64 bit OS?
Click to expand...
Click to collapse
Nope, no can do if you're asking for 64 bit. Sorry.

After flashing, it throws black screen and does not continue how do I fix it?

LiaFourté said:
Use MIUI 12.0.10 global base
Click to expand...
Click to collapse
How to "use" it? Isn't this official rom? Am confused...
Is everything working here? Will You include custom icons change possibility on each apk?
THANKS

[ROM][STABLE]LineageOS 20 [Early Builds][Unofficial]

{
"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"
}
I have finally been able to compile Android 13 for Mi Mix. I have been testing it for 3 days and no bugs found for now.
As if few of you are still using the phone as me, we deserve Android 13 so..here it is.
ROM LINK
ROM SOURCE
DEVICE TREE+KERNEL
Bugs:
*proximity sensor on calls , light sensor works perfect.​

Reserved for stuff

Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising

ducatisto said:
Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising
Click to expand...
Click to collapse
I will build pixel experience and few ROMS more, now that device tree is set up. I still remember the first ROM I built for this phone. I just had to change battery, phone is like new still.

ducatisto said:
Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising
Click to expand...
Click to collapse
Pixel Experience build will be ready for weekend, probably. Will be last build for this year until I come back from New York for holidays. I have a threadripper so builds finish within 1:10 hours.

I like it so far. I notice a bit of a battery drain. Could just be my device.

FateZero said:
I like it so far. I notice a bit of a battery drain. Could just be my device.
Click to expand...
Click to collapse
Kernel needs some adjustments still.

I think it might be the G apps as part of the issues. I am now using NikGapps core and the drain is not as bad.
The rom by itself is not too bad on the battery.

I got trouble installation failure.
E1001: Failed to update system image.
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
Before instllation it have LineageOS 17.
My twrp version is 3.5.2 fbe.
I tried to flash PixelExperience and DotOS, it worked.
Does someone have any idea?

Just out of curiosity gave it a try today: same twrp, same error msg, twice. Formatting data etc...nothing works. What's going on?

ducatisto said:
Just out of curiosity gave it a try today: same twrp, same error msg, twice. Formatting data etc...nothing works. What's going on?
Click to expand...
Click to collapse
Use recovery.img and adb sideload. Our twrp is outdated for Android 13.

YazumiWuHung said:
Use recovery.img and adb sideload. Our twrp is outdated for Android 13.
Click to expand...
Click to collapse
Thanks, that did it with the OS. What's strange is that after rebooting I don't succeed in adb sideloading any v13 Gapps package, i tried 5 different versions and after adb sideload starts sending the package and does start on the phone there's always "Error: recovery error in package..." Any ideas?

For gapps use twrp, its a bit messy having to change but it works.

YazumiWuHung said:
For gapps use twrp, its a bit messy having to change but it works.
Click to expand...
Click to collapse
after installing the rom, I flashed recovery back to official Twrp 3.2.1 to install gapps but when I boot to Twrp the touchscreen doesn't work. Which twrp do you use?

furiseto said:
after installing the rom, I flashed recovery back to official Twrp 3.2.1 to install gapps but when I boot to Twrp the touchscreen doesn't work. Which twrp do you use?
Click to expand...
Click to collapse
Use this one

YazumiWuHung said:
Use this one
Click to expand...
Click to collapse
thank you so much. you breathed new life to my old pal.
I've spent 1 hour with it and so far so good. Only bug I found is Night Light being glitchy but very minor.

Hello, where can I download the boot.img to root with magisk? I copy the one that is in the zip of the rom but it gives me a corrupt message. Thanks a lot!

fredferrer said:
Hello, where can I download the boot.img to root with magisk? I copy the one that is in the zip of the rom but it gives me a corrupt message. Thanks a lot!
Click to expand...
Click to collapse
It's in the sourceforge folder

Can anyone help me how to install this custom ROM on my Xiaomi Mix? This is my very first time on how to install a custom ROM. What are the basic things to do? What to download, where to download and how to download and install.
Thank you very much.

[UNOFFICIAL] RiceDroid v10.2 [Paella] [sunfish] [Android 13]

{
"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"
}
riceDroid for Pixel 4a [sunfish]
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
PIXEL build (only) - comes with full pixel gapps
Device specific changes
Initial build
Credits
Michael Bestas
Changelog
Source Changelog
Download link
Click Here!​
Android OS version: 13.0.0_r30
Security patch level: February 2023
Build author/Device Maintainer: xioyo
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team

Screenshots of ROM

If u like my work and willing to help me for paying the server feel free to donate here: https://www.paypal.me/sufiyan777
Boot image: https://drive.google.com/file/d/14HBlB-8ZZgOOA3bFG6fMnRX0i7b2855y/view?usp=sharing

Nice rom

Thanks for this rom, great phone control mods,,seems to run a full 7-10 degrees warmer then stock at 97f , I will give it a chance to settle down a little and then see where its at, also is it missing the camera app or Iam i just not seeing it? Thanks update,,,, i just installed stock gcam from the play store runs fine, update ,, temp settled down to 94-95 on idle, acceptable,, battery drain was pretty high in standby, I recorded 8 percent /hour . Anyone else have this?

Any firmware requirement prior to flashing (13.0 image from google)? Apply via ADB sideload method?

13 firmware for sure, and I don't recall if it's via adb side load or just a flash all bat file

hammered58 said:
13 firmware for sure, and I don't recall if it's via adb side load or just a flash all bat file
Click to expand...
Click to collapse
Thanks man. Unfortunately, I couldn't get it to flash. I did flash the latest factory image from google, then tried sideloading this. No-go. I also tried extracting the boot.img, flashing that, then trying to sideload. Still no dice. No biggie, I'll just wait until someone can clue me in

tnicko said:
Thanks man. Unfortunately, I couldn't get it to flash. I did flash the latest factory image from google, then tried sideloading this. No-go. I also tried extracting the boot.img, flashing that, then trying to sideload. Still no dice. No biggie, I'll just wait until someone can clue me in
Click to expand...
Click to collapse
Ok you could try this
Fastboot -w. This wipes data
Fastboot flash boot boot.img.
Reboot recovery and adb sideload rom
I think when you boot into the recovery it will be stock recovery
Hth

hammered58 said:
Ok you could try this
Fastboot -w. This wipes data
Fastboot flash boot boot.img.
Reboot recovery and adb sideload rom
I think when you boot into the recovery it will be stock recovery
Hth
Click to expand...
Click to collapse
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...

tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Don't forget the fastboot -w before all the other steps
I think that's the key,, but I have know to be wrong !! Lol

tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Factory reset done?

Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is coming

Unknownbitch said:
Factory reset done?
Click to expand...
Click to collapse
Yup.
I just used a payload extractor to grab the boot.img. I'll try again once the update drops

tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Try sideload with twrp, i got booted when install it trough twrp

Unknownbitch said:
Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is co
Click to expand...
Click to collapse
Hbmsvmanager fixed??
Unknownbitch said:
Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is coming
Click to expand...
Click to collapse

Hi guys! Anyone have a full customization list of this Rom?

M.E.A said:
Try sideload with twrp, i got booted when install it trough twrp
Click to expand...
Click to collapse
I didn't even think of TWRP because I haven't touched it in years. I thought it wasn't updated to work with the later Pixel phones. Sheesh....well, I'm up and running on stock, albeit rooted, so I kind of don't feel like starting from scratch again. But I'll definitely give it a go one of these days.

M.E.A said:
Hbmsvmanager fixed??
Click to expand...
Click to collapse
yep

Marcia8246 said:
Hi guys! Anyone have a full customization list of this Rom?
Click to expand...
Click to collapse
It have a lot of customisations if u want the ss of all join in the tg group i will share it there