General F-16/A13 oxygen os for LE2115 Na op9 - OnePlus 9

Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here

mattie_49 said:
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
Click to expand...
Click to collapse
Do you have boot.img? i don't have good internet for download full ota and extract it :/

franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
Do you have full ota link?

franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot flash this then go into magisk let it reboot if it asks to continue setup. Rooted an A13 stock

mattie_49 said:
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot boot this then go into magisk and direct install to backup stock for you.
Click to expand...
Click to collapse
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd

@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66

AxelM said:
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
Click to expand...
Click to collapse
Oxygen updater

mh, I only receive 11_C.66 maybe I have to wait

after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?

franko_m19 said:
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
Click to expand...
Click to collapse
{
"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"
}
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.

fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
It's the official 16 patched. Just fastboot flash it or ask guy above . He got working with it.

AxelM said:
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
Click to expand...
Click to collapse
No sir I carried it over with magisk from 11 originally. MSM,unlock bl. Patch boot . Then disable modules and carry from A11 to A12 then so on.

fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
fastboot flash boot *boot_name*.img

franko_m19 said:
fastboot flash boot *boot_name*.img
Click to expand...
Click to collapse
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool

_MartyMan_ said:
Do you have full ota link?
Click to expand...
Click to collapse
No but flash one of the open betas. That's how I received so fast. Was on ob2 and it's getting it first.

fhedeitx said:
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
Click to expand...
Click to collapse
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?

franko_m19 said:
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
Click to expand...
Click to collapse
Global (I believe) LE2115 in US

mattie_49 said:
Oxygen updater
Click to expand...
Click to collapse
I was on open beta 2 is why I received very first. That's the order they put rollout in. To ob 1& 2 before stock devices.

Install in inactive slot (after ota) in magisk is working for upgrading from android 12 to 13 (using oxygen updater zip file) ?Edit: this doesn't work because the device reboots when the installation starts.
Remove magisk boot image from magisk app, update and turn off the device...boot to fastboot and do a fastboot boot magisk_patched.img (you have to extract the boot image with payload dumper and patch it before or after the installation with magisk. Then do a direct install from magisk (on the temp root boot image).
On android 13 you will have this warning on every reboot: Orange state, Your device has been uplocked and can't be trusted.

Thanks for this! I have not had root on my Oneplus 9 for a while and it was driving my _crazy_. Had to do fastboot flash boot boot.img instead of fastboot boot boot.img to get magisk to work properly.
I had to jump through some extraordinary hoops to get it done including breaking out an old Win10 laptop since I could never get my new Win11 laptop to recognize my phone in fastboot, despite hours of work trying to install the drivers to no success.

Related

Bring to life and not delete all

I was rooted on 9.5.4 with the Patched Boot Image. I had 2 modules enabled in magisk (call recording and substratum). Wanted to update to 9.5.5 and did this:
1. Download and install update
2. No reboot
3. Open Magisk and disable the modules
4. Select Install install and then Install to Inactive Slot (After OTA)
5. Rebooted
6. Phone booted so I opened magisk and enabled my modules
7. Rebooted
Now the phone doesn't boot up properly. It goes all the way to first screen asking for my passcode and then turns off and does to stock recovery. Please someone tell me what to do so I don't lose my data!!
Install TWRP, install stock image.
"Bring to life and not delete all" - Are you Thanos?
djsubterrain said:
"Bring to life and not delete all" - Are you Thanos?
Click to expand...
Click to collapse
If I was I would turn a lot of people to ash...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
eltarod said:
If I was I would turn a lot of people to ass...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
Click to expand...
Click to collapse
"I would turn a lot of people to ass..."
{
"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"
}
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
djsubterrain said:
"I would turn a lot of people to ass..."
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
Click to expand...
Click to collapse
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
I updated the same way as you (didn't disable my Magisk modules though). Everything went OK, kept root, but something borked in my /system folder and now can't make any changes in it (buildprop, hosts).
I'm not installing any unofficial TWRP, going to reflash the patched boot.img again to see if that works. If not, will go for a clean install. Worth a try?
eltarod said:
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
Click to expand...
Click to collapse
Rooted boot image : https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Follow that guide but, as I said, your rom is a later version so your wifi will break until you flash a compatible kernel, I'm using ElementalX with 9.5.5 and it's fine.
You would be best installing TWRP as soon as you can from here : https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 since you'll be best using this to flash ElementalX
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Flash stock boot IMG and uninstall substratum overlay themes, u will always want to do that before u update, then reflash patched boot image, then u can reinstall your themes
---------- Post added at 01:17 AM ---------- Previous post was at 12:55 AM ----------
larsdennert said:
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
No he said he was able to boot after the update, it was when he enabled his modules, more than likely its a substratum theme issue

[ROOT][Magisk][10] Root Galaxy A7 2018/A750x Running One UI 2.0

{
"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"
}
Tested Working on A750F, A750FN, A750G and A750GN - 22/03/20
This Guide is outdated now..
It "ONLY" works on the initial One UI 2 update that started rolling out in March 2020
It has issues on the june patch. So "DO NOT" report bugs if you are on the june patch.​
Use this at your own risk. I am not responsible for any damage that may happen to your device.
Make sure to have the official firmware downloaded for your device in case anything goes wrong.
This will void your warranty
This will also trip the knox counter.​
Installation Guide
1. Unlock The bootloader
2. Boot into download mode
3. Using Odin, Flash Magisk_patched_boot.tar in the "AP" Slot.
4. Reboot download and flash Twrp recovery using odin in AP slot.
5. Reboot to TWRP and "FORMAT" , not wipe the data.
6. Flash Magisk-v20.3.zip
7. Reboot to download and flash Officialrecovery.tar in "AP" slot.
8. Reboot your device.
DOWNLOADS
Magisk Boot Img - http://www.mediafire.com/file/m9dwiww6i492xl6/Magisk_patched_boot.tar/file
Official recovery - http://www.mediafire.com/file/nhrj8060rbv43rm/Officialrecovery.tar/file
Notes:
1. Only Magisk v20.3 is tested, other versions may/may not work. Report if other versionswork, I will update OP.
2.This "WILL NOT" install Twrp on your device as Twrp is not updated and it will cause bootloops.
3. Failing to follow and steps mentioned above, you will end up in a bootloop.
Please DO NOT Share direct link to these files, Share The link to this post. ​
Feedback is Highly appreciated
Hit the Thanks Button
Credits:
Me for finding this method
@ashyx for Building Twrp
And Teamwin
Download link ??
Kumarranveer_RK said:
Download link ??
Click to expand...
Click to collapse
I just realized that xda did not upload the files due to size limit, I have updated OP.. Check it
These files work on the A750G/DS. Or they're just for the F version
JHAM2005 said:
These files work on the A750G/DS. Or they're just for the F version
Click to expand...
Click to collapse
They are confirmed working on A750F and A750GN, if possible, try and report for A750G
Thanks bro .. rooted my a7 2018 (Android Q) .. No issues Till now
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
nanodroid.cyberbot said:
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
Click to expand...
Click to collapse
Its mentioned in the op please read it carefully format it by typing yes. And install magisk zip from sd card
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
sameermanas said:
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
Click to expand...
Click to collapse
No other twrp is available for our device.. So, yes this one
thanks! work like a charm
I downloaded the Indian version and installed it on an a750 FN and it works ....
I will keep trying more things
good job
Delete
The Root works perfectly on the A750G/DS, the only thing that does not work properly is the TWRP, does not recognize the internal memory, only recognizes the SD card
PD... An Official Recovery query is only for version F and GN or also works in G/DS versions
how could I return my battery at the original state? Im having fast drain ..
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Equinoxx17 said:
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Click to expand...
Click to collapse
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
KChoudhry said:
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
Click to expand...
Click to collapse
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Equinoxx17 said:
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Click to expand...
Click to collapse
You need to start from scratch then
KChoudhry said:
You need to start from scratch then
Click to expand...
Click to collapse
I guess I'll be staying at Android Pie for now. I think I'll be waiting for other alternatives that doesn't boot into download mode when restarted. Somehow, I thank you for sharing info on how to root Samsung Galaxy A7 2018.

OxygenOS C.36 out but DON'T INSTALL THIS UPDATE FOR NOW!

I got a KB2003 - ONeplus 8T EU
Oxygen Updater told me today there's an update avaliable, version C.36.
I donloaded it via the app and updated manually.
Phone did not boot up.
I was able to boot into recovery once where it said the system is corrupt.
I managed to enter fastboot mode. It was recognised on my PC by fastboot but no fastboot command are not accepted. I couldn't even turn it off again.
About 2 hours passed.
Then I managed to turn it off and it booted up like nothing happened, but I cannot download the data from it. Nothing is showing up in my browser via cable connection.
I am not feeling safe anymore ... I think I will roll back to C.35 if possible ASAP.
You need to keep an eye on https://community.oneplus.com/wap/circleDetail?id=1034260458221338626
C.36 is an IN only version at the moment of OOS 12
Update: since I first wrote this post there have been reports of C.36 being available now for both EU and NA.
Thanks.
Can I download C.35 and install simply install it?
The C36 is rolling out to other versions now. See https://forum.xda-developers.com/t/updates-thread.4188149/
I've just received the KB2005 (NA/global) version when I checked in Settings>About device. Normally the EU version takes longer to roll out.
I don't think the system updater will let you downgrade to C35, but you can try.
After 1 night everything seems to work well. I did not try to Rollback or did anything.
Fastboot is back.
Still do not understand the issue. LOL
I updated it earlier. Now it's stuck on reboot loop :/
VarunAgw said:
I updated it earlier. Now it's stuck on reboot loop :/
Click to expand...
Click to collapse
You updated via OTA or Oxygen Updater app ?
neopbm said:
You updated via OTA or Oxygen Updater app ?
Click to expand...
Click to collapse
Oxygen Updater
Long story, I have reset my phone (I was planning to anyway), so all good now.
VarunAgw said:
Oxygen Updater
Long story, I have reset my phone (I was planning to anyway), so all good now.
Click to expand...
Click to collapse
Oh ! Even if formating is a good thing sometime to restart from scratch, i hope you didnt lost any important data
neopbm said:
Oh ! Even if formating is a good thing sometime to restart from scratch, i hope you didnt lost any important data
Click to expand...
Click to collapse
Yeah, I was able to fix the boot loop temporarily and was able to boot once. It gave me enough time to retrieve all the important data
i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great
ecompton59 said:
i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great
Click to expand...
Click to collapse
how did you get the boot.img ?
i cant because i cant find the stock flash file for C.36
build number : KB2005_11_C.36
oxygen updater
{
"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"
}
dont forget disable magisk mods
ecompton59 said:
oxygen updater
dont forget disable magisk mods
Click to expand...
Click to collapse
i am on c.36 , and on oxygen updater , i can only download flash file for c.33 , can i extract the boot img from it and root ? sorry for bad english
yes its in the 8t threads. payload dumper is what i use on pc its easy
ecompton59 said:
yes its in the 8t threads. payload dumper is what i use on pc its easy
Click to expand...
Click to collapse
so to be precise , i can extract boot.img from c.33 file and root my c.36 , right? ty btw
MevishL said:
so to be precise , i can extract boot.img from c.33 file and root my c.36 , right? ty btw
Click to expand...
Click to collapse
ecompton59 said:
i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great
Click to expand...
Click to collapse
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.
MevishL said:
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.
Click to expand...
Click to collapse
Look at this great guide.
Rootk1t said:
Look at this great guide.
Click to expand...
Click to collapse
thnks !
MevishL said:
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.
Click to expand...
Click to collapse
long as you know how to recover from brick with msm tool. but steps i use is oxygen updater to download full ota. (not incremental update) .put the 3gb zip on pc. use payload dumper to dump the zip (only for boot.img) take boot put on phone use magisk Canary to patch that boot. put boot on pc, reboot to recovery and fastboot boot magisk.img. once phone boots use magisk to directly patch boot and its rooted

[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

Categories

Resources