ResurrectionRemix v6.1.0[8.1.0_r43] - Nexus 5X Android Development

{
"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"
}
Resurrection Remix Oreo​
Installation Files​
ROM Download Links​
Unofficial Open GApps 8.1​
Resurrection Remix Github Source​
Big thanks to:
XDA developers
LineageOS team
Dirty Unicorns
Omni team
AND OF COURSE TO ALL THE SUPPORTERS, DONATORS AND USERS
XDA:DevDB Information
ResurrectionRemix v6.1.0, ROM for the LG Nexus 5X
Contributors
markakash
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Beta
Created 2018-02-11
Last Updated 2018-08-28

Is this official release??? Have this any bugs?

Zdrpkamil said:
Is this official release??? Have this any bugs?
Click to expand...
Click to collapse
Yes this is official release. And so far I didn't find any bugs.
Regards,
Akash

Wow, thanks for your work. I have a question. Why are you choose AFH instead of Source Forge?
Sent from my Nexus 5X using Tapatalk

Feb vendor etc?

retr0gr4d3 said:
Feb vendor etc?
Click to expand...
Click to collapse
Propably yes.

retr0gr4d3 said:
Feb vendor etc?
Click to expand...
Click to collapse
Yes, you need the February vendor.
---------- Post added at 02:14 AM ---------- Previous post was at 01:32 AM ----------
The rom is very responsive, fast and smooth.

Its my new daily, soz aicp. RRO is absolutely amazing. Hands down the best rom ever used. Good work

Thanks! Like it so far. Any plans to add notification customization?
Sent from my Nexus 5X using Tapatalk

great.
some bugs:
dark ui theme not work.
music app not work.
thanks.

i've been using it since yesterday.. It's amazing to see RR again ! Thanks @markakash

Went back to stock approx 2 months ago and swore I'd stay there now this dropped and I'm bout to flash asap lol. Thanks man!

Smooth, awesome n stable af ?

I noticed big consumption of the battery while using RR.

AFK269 said:
I noticed big consumption of the battery while using RR.
Click to expand...
Click to collapse
Overnight, my "Idle Use" was 0.3%. I can't complain about that...

jbaumert said:
Overnight, my "Idle Use" was 0.3%. I can't complain about that...
Click to expand...
Click to collapse
On idle is ok or when it's standby. I mean when you use the phone.

Finally:laugh::good::fingers-crossed: thank you

Not working with Feb 2018 images?
Which factory image is this supposed to work with? Tried installing this RR build on bullhead 8.1.0 (OPM3.171019.014, Feb 2018) and 8.1.0 (OPM5.171019.015, Feb 2018) with the same result: installed fine in TWRP, then after installing OpenGapps Nano, wiping dalvik/cache, and rebooting to system shows the RR startup animation, but after idling there for a while it just reboots to recovery. Wiping and re-flashing the images and booting into stock works just fine though. Any thoughts?

rjdang said:
Which factory image is this supposed to work with? Tried installing this RR build on bullhead 8.1.0 (OPM3.171019.014, Feb 2018) and 8.1.0 (OPM5.171019.015, Feb 2018) with the same result: installed fine in TWRP, then after installing OpenGapps Nano, wiping dalvik/cache, and rebooting to system shows the RR startup animation, but after idling there for a while it just reboots to recovery. Wiping and re-flashing the images and booting into stock works just fine though. Any thoughts?
Click to expand...
Click to collapse
Okay so what you wanna do is wipe everything but internal storage on twrp. You need the bootloader, radio and vendor from OPM3 Feb. Make sure it's OPM3. Install OpenGapps, flash Magisk 15.3 and then boot. DO NOT WIPE CACHE&DALVIK AFTER GAPPS AND MAGISK.

retr0gr4d3 said:
Okay so what you wanna do is wipe everything but internal storage on twrp. You need the bootloader, radio and vendor from OPM3 Feb. Make sure it's OPM3. Install OpenGapps, flash Magisk 15.3 and then boot. DO NOT WIPE CACHE&DALVIK AFTER GAPPS AND MAGISK.
Click to expand...
Click to collapse
Thanks for the advice! It put me on the right track. Here's what ended up working (albeit probably not the cleanest) in case it helps someone else:
1) Re-ran ./flash-all.sh from OPM3 Feb 2018 factory images.
2) fastboot flash recovery twrp-3.2.1-0-bullhead.img
Boot into TWRP:
3) Installed RR oreo zip
4) Wiped cache/dalvik
5) Installed OpenGapps Pico zip
6) Installed Magisk 15.3 zip
7) Reboot to system (no cache/dalvik wipe)
Then from here it booted back to TWRP. Then I did
8) Wiped everything but internal storage
9) Installed RR oreo zip, OpenGapps Pico zip, Magisk 15.3 zip
10) Reboot to system without wiping cache/dalvik at any point
Then from here it got stuck on the RR animation. I waited about an hour, and it was still showing the animation so I decided to hold down power and reboot. From there it got stuck on the Google splash for about 20 min before I got impatient again and held down the power button to reboot. Then it booted into RR! Went through the setup and restored basic settings, and so far so good...
Anyway, not the cleanest start, but at least it works for now. Thanks again!

Related

[ROM][LineageOS13.0][UNOFFICIAL] LineageOS13.0 for Galaxy S4 VE (GT-I9515/GT-I9515L)

Hi guys!
It's unnoficial LineageOS13.0 for Galaxy S4 Value Edition (GT-I9515).
I strongly recommend to perform a backup of your current rom before installation.
To all people - do not try to update rom manually with jfltexx nightlies - i9515 is jfvelte!
Valid updates are only in my threads (at least for now).
Working:
bluetooth
wifi
nfc
camera
RIL
IR
sensors
portable wifi hotspot
wifi 5GHz
Known issues:
Possible issues with bluetooth headsets
small issues with sound
Screenshot:
{
"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"
}
Changelog:
20170924:
updated fingerprints
latest security patch
gps might lock a little faster
changes same as those on www.cmxlog.com/13/
20170206:
changes same as those on www.cmxlog.com/13/
20170113:
fix /data encryption
rebrand to LineageOS
20160930:
Sync wifi configs with msm8930
Enable AUDIO FEATURE ENABLED HWDEP CAL
Possible temps and power drain reductions
20151109:
First build
Downloads:
Link to folder with all builds: Mega and AFH
Recovery (TWRP 2.8.7.0 and newer; *.tar is odin-flashable) download link: Mega and AFH
XDA:DevDB Information
CM13.0, ROM for the Samsung Galaxy S4
Contributors
sombree, srisurya95
Source Code: https://github.com/jfvelte-dev/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-11-10
Last Updated 2017-09-24
Installation instruction
If you're coming from stock ROM or want to have clean install:
1. Boot to recovery (i recommend to use TWRP)
2. Format /system, /data, /cache and dalvik cache
3. Flash ROM and then flash gapps (but remember - you have to install gapps before first boot of the system - otherwise they won't work properly!)
4. Reboot to system and voilà - you have installed CM13 and gapps
If you're coming from CM12.1 and want to keep your installed apps and settings:
1. Boot to recovery (i recommend to use TWRP)
2. Format /system, /cache and dalvik cache
3. Flash ROM and then flash gapps (but remember - you have to install gapps before first boot of the system - otherwise they won't work properly!)
4. Reboot to system and voilà - you have installed CM13 and gapps
Reserved
Oh my god! Finally! Marshmallow is here fornour pretty abandoned device! Love you sombree!
Btw: Can you receive calls with this build?
Is this rom work for s4 19505:what:
So anyone tried it? Can it be used as daily driver?
Wow, not even a month we already have marshmallow with our device ! Keep it up sombree, ur the best !
I'd love to try it but if I flash it, can I flash CM12.1 back ? And do I have to factory reset before updating ? Or downgrading if it's possible ?
Thanks Sombree i will give it a shot Btw do we need to do a full wipe or can we flash over 12.1 and clear chache/dalvik?
Anyway thanks for what you do we really appreciate youre work and what you do for us!
---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------
Are there any kernels available to flash to tweak the GT-i9515 ??
aidaz said:
Oh my god! Finally! Marshmallow is here fornour pretty abandoned device! Love you sombree!
Btw: Can you receive calls with this build?
Click to expand...
Click to collapse
I think yes - i've tried to make call and had no problem with that. Still you may test by yourself
abdullahxda said:
Is this rom work for s4 19505:what:
Click to expand...
Click to collapse
No, this rom is for i9515 - not i9505!
k0spwn said:
Wow, not even a month we already have marshmallow with our device ! Keep it up sombree, ur the best !
I'd love to try it but if I flash it, can I flash CM12.1 back ? And do I have to factory reset before updating ? Or downgrading if it's possible ?
Click to expand...
Click to collapse
Make backup of current rom; wipe everything and install this. Yes, you can flash back to CM12.1 - you'll have to wipe everything again. Or you can simply bring up backup of CM12.1 that you've made before installation of CM13 - then there is no need to wipe anything
Joe_DOW said:
So anyone tried it? Can it be used as daily driver?
Click to expand...
Click to collapse
You can try by yourself and tell us
does it have gapps preloaded?
Joe_DOW said:
does it have gapps preloaded?
Click to expand...
Click to collapse
It's pure CM, so no
You can download them for example from http://opengapps.org/
Probably a NooB question.
Is there a need to root the device prior to flash CM 12 or 13?
Sent from my lake
molchmolch said:
Probably a NooB question.
Is there a need to root the device prior to flash CM 12 or 13?
Sent from my lake
Click to expand...
Click to collapse
Nope
sombree said:
I think yes - i've tried to make call and had no problem with that. Still you may test by yourself
No, this rom is for i9515 - not i9505!
Make backup of current rom; wipe everything and install this. Yes, you can flash back to CM12.1 - you'll have to wipe everything again. Or you can simply bring up backup of CM12.1 that you've made before installation of CM13 - then there is no need to wipe anything
You can try by yourself and tell us
Click to expand...
Click to collapse
Hi, thanks for the answer, I will wait for root ro be available to use titanium backup since I need to perform a full wipe,
I trust you sombree, you're the best !
isnt your apps reinstall automatically? for me it worked when a factory reset on cm12.1. i dont know if it is a CM thing or a google account thing. Nevertheless its amazing.
Keeps Boot-Looping
Hi, I just installed the cm13 update. TWRP told me , that installation was sucessfull.
But after wipeing cache it keeps boot-looping
Additional Information:
TWRP reminded me, that the device seems to be unrooted and asked, if I want to root it.
I press yes and the installation log appeard for 0.5 sec and then my gt-i9515 rebootet into boot-loop again
EDIT::::::
Installtion worked with doing a factory reset first
MisterEvo said:
Hi, I just installed the cm13 update. TWRP told me , that installation was sucessfull.
But after wipeing cache it keeps boot-looping
Additional Information:
TWRP reminded me, that the device seems to be unrooted and asked, if I want to root it.
I press yes and the installation log appeard for 0.5 sec and then my gt-i9515 rebootet into boot-loop again
Click to expand...
Click to collapse
did u do a factory reset?
Joe_DOW said:
did u do a factory reset?
Click to expand...
Click to collapse
No, I just installed it, as an update like it was in cm12.1
Do I need to factory reset it first?
MisterEvo said:
No, I just installed it, as an update like it was in cm12.1
Do I need to factory reset it first?
Click to expand...
Click to collapse
well i havent tried it yet, ill try it tonight, but thats what i read, that we need to do a factory reset, and than install cm13
Joe_DOW said:
does it have gapps preloaded?
Click to expand...
Click to collapse
No it doesn't. I use gapps from here: 6.0 Gapps
Also, lock screen shortcuts does not work.

[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

LineageOS 20.0 for Lenovo Xiaoxin Pad 2022 (China) (4/64 and 6/128)

{
"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"
}
OS:
LineageOS 20.0
Devices supported:
Lenovo Xiaoxin Pad 2022 (China) (4/64 and 6/128)
Means no radio support and no haptics.
Kernel:
4.19.275, Source @ GitHub
Bugs:
Not found
Installation:
Flash via TWRP as zip, if any troubles with installation, please format super and flash super_1.img from ZUI firmware to super partition.
FLASH ON YOUR RISK!!!
lineage-20.0-20230521-UNOFFICIAL-tb128fu.zip
Please donate if you want to support my work.
Can you provide kernel source, device trees and vendor trees?
after flashing and testing for a bit i noticed that Shim level is way higher than on stock or any gsi i have used
the higher the brightness, the worse the situation is.
after opening and closing any app, its back to normal a bit better but shim is still very high and noticable compared to any gsi or stock
turned off the device (didnt shutdown) after a minute or so, turned on, it flickered and shim is back until opening any app
if you are interested in more details or logs, let me know
i will have this build flashed for at least few days to test
hi! thank you for feed back.
brightness value are default. not device related. pls check vendor overlay.
Atm dont have pbty to share device/vendor.
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.
you may want to add direct github kernel link to main post since its required by xda gpl rules, your post may get banned and we definately dont want that xD
heineken78 said:
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.
Click to expand...
Click to collapse
Hi! Thanks for sharing your work on the forum. As per the post above, we require a direct link to the kernel source in the first post to ensure GPL compliance. As a courtesy, I've edited the first post and added that for you (from the source link you have mentioned in your other thread), so you're good to go. But please remember to do so in the future whenever you're creating threads sharing your development work.
Regards,
shadowstep
Senior Moderator
any updates?
LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip
uhhhh
Psyl0w said:
LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip
Click to expand...
Click to collapse
i kinda "semi-hard bricked" the tablet... not with the ROM, but in some other way, can you pm me on telegram if you could help?...
and i cant properly flash lineage now, it crashes the moment i start flashing it.., flashing super_1 to super doesnt fix it
welp, after flashing all the partitions manually, i ended up in crashdump, thats my "semi-hard brick", only stock flobal fw kernel works, any other kernel, zui, CAF, crashdump...
flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...
oh **** and i dont have wifi unless i flash stock vendor with stock kernel :| and the display doesnt rotate at all, even if i force landscape, it stays in portrait.. bug of stock kernel. please help, i just dont know what to do, flashing zui from qfil doesnt help too...
tqmatvey said:
flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...
Click to expand...
Click to collapse
actually before flashing stock vendor, it doesnt lag
Hi!
Thank you for your work! I wanna flash Lineage OS in this tablet but I dont know how to do it. Can someone tell me where I can find TWRP and how to flash it?
Thanks
Hi everyone! Hope you are fine
I tried to flash Lineage OS today and I couldnt do it. I flashed TWRP (no root) but it couldnt flash zip. It just said It couldnt do it.
I tried to flash super.img but i dont know where are the super partition to format. I went to wipe menu of twrp and there wasnt a super partition, just “ART/Dalvik”, “SD card”, etc, but nothing called “Super”.
Anyway I tried flash super1.img from original firmware with twrp flashing image menu and after reboot I saw black screen with Qualcomm Crashdump text. In flash menu I could see a “super_…” partition but there wasnt it in wipe menu.
After that I prayed to all Saints to restore global rom and I had good luck and thats all.
As can you see I need a little tutorial to do it, If any caritative person wanna share his knowledge please thank you
PD: i dont flash any rom since I had my last android device five years ago. I just used CWM, zip files and thats all. I see that this procedures are more difficult nowadays
@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu
tqmatvey said:
@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu
Click to expand...
Click to collapse
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes
ajesushn said:
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes
Click to expand...
Click to collapse
as i clearly mentioned, my issues were caused by another thing, not lineage related, latest lineage 20 works perfectly
Thank you. Install LineageOS successfully. Everything works great and very fluid. I haven't found any problem so far.

Categories

Resources