{
"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"
}
Introduction:
UnicornHorn kernel is a v4.14 Linux stable based, trying to be upstreamed with AOSP Kernel Common , aiming to give a balance of performance to battery life.
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Supports:
- Any custom non CFW AOSP custom ROMs on Android 11 for AOSP
- Android 10 MIUI 11/12 for MIUI
Reporting bugs:
- If you want to report any bugs, please post a logcat and kernel log - I recommend syslog to give all the logs I need.
If this information is not provided, I cannot - and will not - help.
Features:
- CPU Masks and bi-cluster API support
- Disable and fix a lot of MTK debug spam
- Module for get current display framerate
- MTK modules builded
- O3 for clang and vDSO
- Overall improvement
- vDSO32 support
- Upstream to the latest Linux kernel 4.14 version available
Downloads:
Latest Release
All releases go under this format: UnicornHorn-[revision]_[codename]_[date]
Telegram Chat:
UnicornHorn kernel chat
Flashing Instructions:
- Be sure to be rooted before flashing this kernel
- Reboot to latest non CFW recovery, flash this kernel and reboot
Credits and thanks:
@m_vaisakh for cleaning MTK debugging
@Agent_fabulous for his kernel base
And everyone else that helped me and worked with me on the kernel! PM me if I missed anyone
Contributors:
TheMalachite
Source Code:
UnicornHorn Kernel github
Version Information:
Kernel version Linux 4.14.236
UnicornHorn Version R9
Kernel Compiler Google Clang 9.0.3
Based On AOSP Kernel Common
ROM Firmware Required: Any non CFW AOSP rom based on MIUI 12 for AOSP build and Android 10 MIUI 11/12 for MIUI build
Status: Stable
Created 2020-04-08
Last Updated 2021-06-11
Reserved #1
Reserved #2
Done flashing it.
Any bugs?
work normally miui?
[email protected] said:
work normally miui?
Click to expand...
Click to collapse
No, currently it only supports custom AOSPs, read the thread carefully
What the hell???
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Click to expand...
Click to collapse
Did you follow the instruction?
---------- Post added at 12:43 PM ---------- Previous post was at 12:42 PM ----------
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.[/QUO
SUPPORT ONLY AOSP CUSTOM ROM.
Click to expand...
Click to collapse
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
-Non-compatible ROMs with icecream kernel:
Stock Android 9 miui 10
Stock Android 9 miui 11
Stock Android 10 miui 11
-Compatible ROMs with icecream kernel:
AOSP based Android 10 custom ROMs (Los, posp, etc.)
All the aforementioned ROMs exist. This kernel was written though only for AOSP based Android 10 custom roms, as of today.
polfrank said:
-Non-compatible ROMs with icecream kernel:
Stock Android 9 miui 10
Stock Android 9 miui 11
Stock Android 10 miui 11
-Compatible ROMs with icecream kernel:
AOSP based Android 10 custom ROMs (Los, posp, etc.)
All the aforementioned ROMs exist. This kernel was written though only for AOSP based Android 10 custom roms, as of today.
Click to expand...
Click to collapse
Android 10 is virtually impossible to flash on RN8P. So I dissagree, Whenever I flash supposedly android 10 roms on it they turn out to be android 9.
all miui 11 for this cellphone is android 9.
The point is.
Anyone using yout kernel on a RN8P has a 99% chance of a hard brick like I now have as almost every rom version MIUI or AOSP is android 9.
That is not made very clear in your instructions which I misread
Bryceicle1971 said:
Android 10 is virtually impossible to flash on RN8P. So I dissagree, Whenever I flash supposedly android 10 roms on it they turn out to be android 9.
all miui 11 for this cellphone is android 9.
The point is.
Anyone using yout kernel on a RN8P has a 99% chance of a hard brick like I now have as almost every rom version MIUI or AOSP is android 9.
That is not made very clear in your instructions which I misread
Click to expand...
Click to collapse
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Click to expand...
Click to collapse
First, their Android 10 aosp roms for this phone and read op also, this kernel is only compatible with AOSP Android 10 roms so before say it's my fault you should read op first ;__;
And did I say this kernel is compatible with GSI ? I think no ;__;
So don't try to boycott my work because YOU didn't read carefully op ;__;
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
A GSI will not work with a custom kernel, unless you install a compatible dtbo image. This is because a GSI has not modified your boot and dtbo partition. All AOSP based ROMs (again, not GSIs) have the same kernel dtb and dtbo image at this point. If you try to run the compiled kernel against newer MIUI dtbo images, you will hard brick.
The only MIUI dtbo images I've found working with the compiled kernel are from the initial MIUI 10 Android 9 builds. Consider using the factory preloader, and reading the thread properly.
MTK not for me
polfrank said:
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Click to expand...
Click to collapse
Thanks I might do that. But Im pretty sure the cell is unfixable now without either a service center or ERP surgery. Its not following any of the rules for hard bricks.
The only way the computer seems to respond to it is if I hold all 3 buttons down. Then I get an error an a chain of numbers an letters an an 'error' message.
Ill apologise to the developer. I misread the instructions an it was late at night. I kind of went off at him lol.
I definitely think if I can fix it Ill give it away or sell it. The MTK processor is a funny beast. Ive never had a processor that needs an authorised account to fix?
I'm going back to snapdragon I think. Its more predictable an more forgiving when you make errors
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
Agent_fabulous said:
A GSI will not work with a custom kernel, unless you install a compatible dtbo image. This is because a GSI has not modified your boot and dtbo partition. All AOSP based ROMs (again, not GSIs) have the same kernel dtb and dtbo image at this point. If you try to run the compiled kernel against newer MIUI dtbo images, you will hard brick.
The only MIUI dtbo images I've found working with the compiled kernel are from the initial MIUI 10 Android 9 builds. Consider using the factory preloader, and reading the thread properly.
Click to expand...
Click to collapse
Hey just wanted to apologise for losing my temper at you. It was late at night an was the last thing I expeted would happen.
I think ill give it away if I can get it fixed.
MTK is not for me. Too unforgiving an wierd behaviour when it bricks if you make a simple mistake.
I still doubt the existence of android 10 for RN8P mate every time I think I installed it turned out to be android 9.
There are tons of youtubers seeking click bate over it. Promising android 10 wen it says in version 11.0.6.0 global that its android 9 in the version info.
This was my %$#@ up not yours ok.
Just frustrating :-|
Bryceicle1971 said:
Hey just wanted to apologise for losing my temper at you. It was late at night an was the last thing I expeted would happen.
I think ill give it away if I can get it fixed.
MTK is not for me. Too unforgiving an wierd behaviour when it bricks if you make a simple mistake.
I still doubt the existence of android 10 for RN8P mate every time I think I installed it turned out to be android 9.
There are tons of youtubers seeking click bate over it. Promising android 10 wen it says in version 11.0.6.0 global that its android 9 in the version info.
This was my %$#@ up not yours ok.
Just frustrating :-|
Click to expand...
Click to collapse
No worries and, yes there is Android 10 MIUI 11 for the device. Here are the archives we're using as reference for development:
Global
Indonesian
Indian
EEA (EU)
Russian
For more information and support of flashing these, you might wanna join the Telegram groups, or ask in relevant threads Let's not bloat this thread any further regarding A10 firmware.
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
Not going to lie, but all this sounds like you've been living under a rock for at least 3 months.
All jokes aside, please see the ROM section of this forum. There's five working Android 10 AOSP ROMs out for this device since about 2 months. Which is why this Kernel was released. You DID NOT have to flash GSI at all.
I've tried this kernel on the previous build of EvolutionX and LineageOS. The current version of EvoX also comes with IceCream Kernel by default.
Good luck on unbricking your phone. And hopefully you flash a REAL ROM on it next time ?
Helhound0 said:
Not going to lie, but all this sounds like you've been living under a rock for at least 3 months.
All jokes aside, please see the ROM section of this forum. There's five working Android 10 AOSP ROMs out for this device since about 2 months. Which is why this Kernel was released. You DID NOT have to flash GSI at all.
I've tried this kernel on the previous build of EvolutionX and LineageOS. The current version of EvoX also comes with IceCream Kernel by default.
Good luck on unbricking your phone. And hopefully you flash a REAL ROM on it next time ?
Click to expand...
Click to collapse
Hard brick was unresolvable. EDL reset points had no success. Its in the rubbish bin now. I dont get MTk mediatek has different rules an I'm used to snapdragon. I am thinking of stepping down to Redmi note 8 as it is snapdragon an has a number of roms that are bugless an work very well. Even finger print unlock an faceunlock.
I made mistakes yes. But am not used to mediatek.
And yes I failed once again to understand that Miui releases numbers are not sequential.
11.0.6.0 = android 9
11.0.2.0 = android 10
Miui releases are not released sequentially. Fools me every time. That was the rock I was under 3 months lol.
I have never to my knowlwdge tried a mediatek cellphone before. Too hard for me.
polfrank said:
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Click to expand...
Click to collapse
can i get your help?
i want to flash twrp on my begonia, currently unlocked bootloader, Android 10 Indonesia.
please help. :highfive:
Related
Hi Guys,
I have found cm12.1 and cm13 for our Xperia P in a Webstite.
Cm12.1 is really stable and works like a charm.But Cm13 has more Bugs like Camera,Wlan etc.
Lets start
Installation - CyanogenMod 12.1
Next, you need the CyanogenMod ROM.zip, the appropriate GApps, and the corresponding boot.img - which also contains the Custom Recovery TWRP to flash and successfully boot the Android 5.1.1 based ROM. Copy the CyanogenMod 12.1 ROM.zip to Euner Xperia P, and reconnect it to your PC in fastboot mode, as described in the previous section. For the next step, the boot.img must be in your fastboot folder. Opens the input prompt and returns there
PHP:
Fastboot flash boot cm121_boot.img
on. Next, you reboot your Xperia P by either turning the device off and back on again. Or the command in the input prompt
PHP:
Fastboot reboot
Or use Flashtool for flashing of kernel
. Once the SONY label appears with the graphic of the CyanogenMod STE project, press the volume down and power button several times to reboot the device. Swiped at the start in the query to the right to allow changes to the system partition. Now select the menu item "Wipe> Advanced Wipe" and tick "System, Data, Cache" and "Android Secure" and confirm the selection by swiping again. To complete the installation, go back to the Install menu and navigate to the location where you previously copied the ROM and GApps. Flashes them one by one and reboots the Xperia P.
The first boat takes up to 10 minutes, and ends in the menu for the initial setup, as you are used to with a new device. Congratulations, you have successfully installed CyanogenMod on your Xperia P! Bold among you, can also try the
Installation - CyanogenMod 13
It is same as CM12.1
CyanogenMod 13, which is based on Android 6, but is still in an early development phase.
Credits
@Xperia-STE Team
@smartphone-guru.
I tried_ this version of cm12.1 its most stable than any other version but not very fluent in use.
But almost perfect for dailyuse
GAPPS error
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
sz_ashik said:
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
Click to expand...
Click to collapse
You have to install Gapps via cmw again. The best one is open gapps
CM12.1 Works perfectly!, I have not yet seen the first bug
jao6622 said:
CM12.1 Works perfectly!, I have not yet seen the first bug
Click to expand...
Click to collapse
is it better than cm11 final (m12)?
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
sorry , I don't have tested that rom :s
This ROM is old and newer build are already out but latest is 20161002 i think . There is link https://drive.google.com/drive/u/0/folders/0B4AOy62JMc5gaUpYbUFMVkdGRUk those are build by @CBNUKE i will download cm12.1 source and compile at least the latest source if it will even compile since i tried to fix cm13.0 and cannot make it to compile but i will try harder and maybe one day i will do it but for now i have holidays so i will compile cm12.1 hopefully. For now use CBNUKE build.
Bugs
Meloferz said:
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Click to expand...
Click to collapse
Camera Recording is Sometimes not working
A2DP totally not working
NFC not even recognized by system
but other things work.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
Well its stable fast and usable for daily use but dont know if its faster but its good ROM.
---------- Post added at 10:32 PM ---------- Previous post was at 10:21 PM ----------
Dont expect that we will ever get CM13.0 on Nypon cause of hard building part and that BT is disabled because if its not u will get boot-loop.
i would need a dev that already ported a rom to help me with this.
Its not easy to port it.
Any help from a dev or porter is needed to make CM13.0 to work cannot do it on my own.
Good and bad news
First good news : i have managed to build lineage OS 13.0 and not bad news TWRP looks ugly bad text and the entire UI is not right how it should be and next problem rom is not bootable after kernel screen there is no boot animation just black screen forever . But i will try to fix it i updated TWRP to 3.0.2.0 and still the same UI problem so probably Kernel Issue but weird that i didnt even touch kernel source and still problem.
Thats it for now I will try to fix it.
And if anybody who have experience in this can help me i will be happy.
Maybe @CBNUKE will have spare time to help me with it.
Thanks.
Update on Development (Not yet working but close)
Found the problems source: I did forgot to patch the source on my first build so of course it cannot even boot. But now i little bit screwed my source code of lineage OS by trying to find solution to errors that popped out by applying patches.
So will re download source and hopefully after patches i will get working bootable ROM (Really Hopefully)
I will post a new Thread about it if i get at least basic stuff working.
And of course i will post the ROM itself if it will work.
And again any help from somebody willing to help and knows basic stuff about ROM porting will be Welcome.
OK not Working but here is it.
Test on YOUR OWN RISK.
IM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE OR IF YOU GET BOOTLOOP !!!!!!!!!!!
SO IF ANYTHING BAD HAPENS TO PHONE IM NOT RESPONSIBLE FOR IT !!!!
MAKE BOOT AND SYSTEM BACKUP BEFORE FLASHING !!!!
I have builded the ROM with patches but the same errors remain like bad UI in TWRP and not bootable system it will not even show Boot Animation but if anybody want to test it here is the ROM:
HTML:
https://ufile.io/un7oe
.
i have some patches that i havent applyed so will apply those and see what errors will it fix.
And if anybody flash it and know this errors then please tell me how to fix them
EDIT: added another patches like build patch and external_icu patch hwcomposer patch libhwui patch ste mutimedia patch (3 of them) and still not even a boot screen im woried that i will not even make this rom bootable
EDIT2: maybe found a way to fix it i probably need edited frameworks and system/core folder so going to do this few days later then will post and update if its was sucess or again a fail.
So i downloaded cm 12.1 source and will build daily build for this device until i figure out what the hell is wrong with Lineage 13.0 and cm 12.1 build will come out in few days need to configure the source for our device.
EDIT: I dont want you to be unhappy but there is like 1% change that i can fix all the problems in CM13.0 without a good team of devs and testers i cant do anything so dont expect ever daily runner baser on CM13.0 or even basic stuff working on it im student 17 years old yes i have a lot of C experience 9 years but thats doesnt change that i cannot do everything alone or with help of @AGONTUK its just lot of stuff to fix mainly boot so if anybody with some experience in this can help i will be happy.
i have all needed sources on my github so if anybody can help do it on github: My Github.
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Haxk20 said:
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Click to expand...
Click to collapse
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
jao6622 said:
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
Click to expand...
Click to collapse
Checked system/app and dont saw any odex files so yes i can make deodexed rom.
And also i have fixed TWRP error and tested just kernel and can boot rom with it now just to make system boot
Main issue with TWRP is FIXED even on CM13.0 and CM12.1 its fixed but both still dont boot up cm 12.1 atleast show me boot animation but cm 13.0 didnt do even that and its stuck at black screen i send few people message to help me with this and waiting for reply. Im looking trought my CM12.1 boot.log and i cannot find the error still what is causing it to not boot. And also i changed CM12.1 boot animation to the one included in LineageOS.
The problem was in TWRP that it choosed wrong PIXEL_FORMAT_BRGA_8888 instead of our PIXEL_FORMAT_RGB_565 so now it looks good now.
Here is link to this build: CM12.1 NOT BOOTABLE WITH FIXED TWRP FOR HELPING WITH FIX.
PLEASE IF YOU DONT KNOW WHAT YOU ARE DOING DONT INSTALL IT ITS STILL NOT BOOTABLE ROM.
Well cm12.1 still not booting at all but I'm going to delete the source and redownload by tutorial by friend (helping a lot Thanks) and if that fails I don't know then but hopefully we will get working build of cm12.1 and for now I'm deleting cm13.0 source since it needs a lot of work to be usable but will talk with SergeyL (he have device with same cpu) and will see how will that work if his work will be usable then if everything works perfectly (unlikely) then maybe cm14.1 but as I said unlikely so wait in few days for hopefully build of cm 12.1
Its working !!!
The best news i can tell you i want to share my Working build of CM12.1 !!! The build will be avaiable to download in few days in new thread (will tell the name later) but best of all is that working stuff is exactly like CBNUKE builds and the boot took 10 seconds Wooow.
Got new security patches 1.11.2016 (no newer since CM12.1 got no new updates.
Thats all i wanted to share.
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Its still build on CM source but will download Lineage Source and compile again but with cm source it was just test if i can build it and yes i can so after compiling Lineage will publish here
I see many tutorials talking about how to compile a rom from source (with an already existing device tree, vendor tree etc), but how do you go about making a custom ROM (and TWRP) from scratch? I already have programming experience with quite some programming languages (including Java, which I heard is important for custom ROM dev), but I can't figure out looking at device trees why people do certain commits.
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
ahmed.al said:
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
Click to expand...
Click to collapse
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
ahmed.al said:
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
Click to expand...
Click to collapse
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
zelendel said:
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
Click to expand...
Click to collapse
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
pvineeth97 said:
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
Click to expand...
Click to collapse
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
I along with many of the devs have been following this closely. Notice how not many are really working on it outside of remote devices. Things like honor and Xiaomi.
Only time will tell how useful it is. To be honest I have not seen anything major. It is pretty much the same as last year. Sure there is one image for some devices but that means nothing. Custom rom devs all will have to make their own anyway. So not a big deal.
zelendel said:
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
Click to expand...
Click to collapse
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
ahmed.al said:
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
Click to expand...
Click to collapse
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
I am not using his work so I am not sure. There are some that are doing it on our own.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
True that. Most of the Chinese companies don't release their kernel sources and it seems like FSF doesn't care much about it.
---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future,
https://forum.xda-developers.com/g4/development/rom-lineageos-15-1-t3768654
{
"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"
}
pvineeth97 said:
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future
Click to expand...
Click to collapse
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
ahmed.al said:
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
Click to expand...
Click to collapse
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
pvineeth97 said:
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
Click to expand...
Click to collapse
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
ahmed.al said:
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
Click to expand...
Click to collapse
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
My latest LOS 14.1 builds for March/April which are very stable (already tested by Paul, DonOleq and Anighirrim). Even Anghirrim flashed my AEX ROM on his wife's G4c phone because he liked it a lot and it is very stable with SELinux Enforced. It's their daily driver now. It's your loss if you didnt check my latest builds.
On heavy usage of Nougat ROM on G4c some lags are encountered because of limited RAM - 1 GB and slower flash memory.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
pvineeth97 said:
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
You keep telling me right - "Check before you speak". Don't be a hypocrite.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
Click to expand...
Click to collapse
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
ahmed.al said:
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
Click to expand...
Click to collapse
Again check my post xD. I am not at all mad/angry lol.
Hi folks, I'm here from the potter (G5 Plus) forums. For potter, I create the TWRP flashable builds of the stock rom. Whilst I'm waiting for the official Oreo for potter, I decided I'd have a go at creating a TWRP flashable build of Oreo for cedric. So here it is....
A few things to note about this:
Bear in mind that I don't have this device, so can't test it. The usual disclaimer applies a.k.a. try at your own risk.
Think of this as a custom rom that happens to be just like stock
It will install the updates to most partitions, except bootloader-related partitions and the partition table. The full list of updated partitions is:
modem
fsg
dsp
boot
system
oem
It does not include the commands to erase modemst1 or modemst2. Experience from the potter forums tells me that it is safest to leave those out, for the few that never backed up their EFS and / or Persist.
Normally I would disable dm-verity and forced encryption of the data partition, but I didn't this time - 1) I wanted to make sure it was bit-perfect with what you'd get with the normal OTA (aside from bootloader updates), and 2) I don't actually believe dm-verity is enforced in this build (although I could be wrong). I was wrong!
The second soak test uses the aroma installer. Much of the above is selectable, and I have managed to work out how to disable dm-verity and force encryption.
Refer to my Potter Oreo thread in the references below for further information. There is a good description and FAQ, much of which will apply to Cedric as well.
So how did I do it?
I used the key files from the OP of this thread:
[STOCK][OREO] Upgrade to Official Stock Oreo 8.1.0
I used the fastboot flashable of 137-93-2 to create an initial TWRP flashable zip, then applied the OTA over the top of the previously created zip (it's complex, but I have a guide on how to do it, one needs to be pretty adaptable on this one).
What you should do
Back up your phone - especially your data, EFS and Persist.
Clean flash vs dirty flash? Not sure, I don't have this device so don't really know. If you were on stock, a dirty flash may work, try clean if it doesn't. If you've come from a custom rom, clean flash is mandatory.
Going back to Nougat or Custom Roms / Problems with fingerprint
The stock Oreo roms update many of the files that are used for functionality such as fingerprint, connectivity, etc. These files are, in many cases, incompatible with stock Nougat and custom Oreo roms. Furthermore, a normal flash (of a custom rom) does not update these files. In order to safely downgrade, it is best to fully downgrade to stock Nougat. If you then wish to install a custom rom, do so after.
A TWRP flashable build of stock Nougat is available in these folders:
https://www.androidfilehost.com/?w=files&flid=280563
https://www.dropbox.com/sh/jwhbwo4kgim67hk/AAAREEIvVxTNq4VJtsL1BWLEa?dl=0
Problems with lost IMEI, missing VoLTE functionality, or no 4G?
As I state above, I haven't got this device, but I have found the underlying cause in potter. If you suffer from any of those issues, please send me a private message if you are willing to try something to restore. One word in advance - if you don't have your own persist partition, you're probably screwed
Links
All files for cedric will be placed here:
Android File Host
Dropbox
Developer help
If any developer out there is interested in maintaining this project, feel free to message me.
References
Here are the relevant threads of mine from the potter world, as I only own a potter (G5 Plus). Much of the information in these threads is applicable to cedric as well. To state the obvious, don't flash any of the linked files on your cedric device.
Creating TWRP Flashable Stock Roms
[Oreo]TWRP Flashable Stock Roms
[Nougat]TWRP Flashable Stock Roms
Fix Persist, resolve IMEI=0, Explanation, Requirements
XDA:DevDB Information
TWRP Flashable Oreo, ROM for the Moto G5
Contributors
NZedPred
ROM OS Version: 8.x Oreo
Based On: Stock ROM
Version Information
Status: Stable
Created 2018-08-11
Last Updated 2019-06-04
Reverting back to stock Nougat
Just a note about reverting back to stock nougat. As Oreo changes permissions on some key files and folders, you may get an issue of your IMEI becoming 0. In order to resolve this, you can do one of the following:
Download and install this zip through TWRP:
cedric-stock-nougat-persist-fix.zip
Execute the following commands within stock Nougat:
Code:
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
Then reboot.
The TWRP zip does the same thing as the code.
Reserved
For potter or cedric?
Kdemwa said:
For potter or cedric?
Click to expand...
Click to collapse
This is for cedric. I'm just stating that I'm a potter user, don't have a cedric device, but they're similar, and I can contribute
Everything works very well, battery life will be tested, it would be great if someone debloated it, thanks by the way!
---------- Post added at 02:18 PM ---------- Previous post was at 01:55 PM ----------
I made a short youtube video to show how the rom works, but cause i'm new here, it won't let me post links, so the title is "Moto G5 (2017) Flashable Oreo Stock Rom".
Sorry if I can not ask you this, you can do this for the G5s plus (sanders)
in my cedric worked perfectly thanks
topkee said:
Everything works very well, battery life will be tested, it would be great if someone debloated it, thanks by the way!
---------- Post added at 02:18 PM ---------- Previous post was at 01:55 PM ----------
I made a short youtube video to show how the rom works, but cause i'm new here, it won't let me post links, so the title is "Moto G5 (2017) Flashable Oreo Stock Rom".
Click to expand...
Click to collapse
Great, thanks for letting me know it all works. I'll check out your video.
jakson7474 said:
Sorry if I can not ask you this, you can do this for the G5s plus (sanders)
in my cedric worked perfectly thanks
Click to expand...
Click to collapse
I could do it if I had the right files. I'd need either the fastboot image for Oreo if available. Or, the fastboot image of the version prior to the Oreo OTA, and the Oreo OTA. If there's a thread that has those, pass it on to me and I'll have a look.
Sorry for asking but which twrp version i should use to flash this ROM 64-bit or 32-bit
Is the speaker bad like the other Oreo updates ? It seems to be the only problem about those updates if you read the other threads.
Working great, thank you
basem bebarse said:
Sorry for asking but which twrp version i should use to flash this ROM 64-bit or 32-bit
Click to expand...
Click to collapse
If one of the other successful users doesn't reply, I'd be looking at a 32 bit TWRP. I'm pretty sure that the rom is 32-bit (again my disclaimer, I don't actually own the device).
I had 64bit twrp installed, idk if 32bit works
Just flashed and working like a charm! Very good job @NZedPred. The only problem is the bad quality of the loudspeaker. Is there something you can do to make it better?
merlinolillo said:
Just flashed and working like a charm! Very good job @NZedPred. The only problem is the bad quality of the loudspeaker. Is there something you can do to make it better?
Click to expand...
Click to collapse
This is a completely stock rom, with no modifications at all (apart from the bootloader files being left untouched, and it's highly unlikely that has any impact on the operational side of your device). So this is what it is like for the Oreo soak testers as well. If there was another update to the soak test that happened to fix it, I'd need the OTA for that, but that would rely upon people on the soak test to capture the OTA(s).
i installed this ROM, but the "moto display" don’t show me messages (messenger, WhatsApp, etc). Does anyone have the same problem?. how can I solve that?
For me it works normal.
I went back to linage os 14.1 and i have a huge problem, fingerprint scanner doesn't show in settings or anywhere, therefor i can't accses it, anybody know the solution, or did someone have this issue?
topkee said:
I went back to linage os 14.1 and i have a huge problem, fingerprint scanner doesn't show in settings or anywhere, therefor i can't accses it, anybody know the solution, or did someone have this issue?
Click to expand...
Click to collapse
You will go back to Lineage 14.1, remove your firgerprints registers and unblock screen block, and go to Oreo. I had this problem. (sorry my english)
---------- Post added at 12:25 PM ---------- Previous post was at 11:55 AM ----------
It works normal for me. Good work, Thank you!
jonatas.matsunaga said:
You will go back to Lineage 14.1, remove your firgerprints registers and unblock screen block, and go to Oreo. I had this problem. (sorry my english)
---------- Post added at 12:25 PM ---------- Previous post was at 11:55 AM ----------
It works normal for me. Good work, Thank you!
Click to expand...
Click to collapse
I didn't understand that.. Sorry, can you write step by step instr. or something?
So the phone has been in the market for quite a while, and I'm still impressed by the monstrous specs it provided, but I'm surprised to see that there are NO custom roms or kernels for this phone, even the TWRP builds from shakalaca seem old, so I'm afraid to try them out on the latest version. Even the rooting process is complicated as compared to other phones because of no custom recovery. If any developer is interested in making a custom kernel or rom for this devices, they can head over to the official ASUS' website and get the source from here, and I'm willing to do the beta testing if the results seem promising. So, anyone?
ROG Phone 1 was not very popular and it is literally dead today. ROG Phone II and III are much more popular, have better specs (Much better battery, which is needed) and a solid community with everything a modder wants/needs.
Indeed you're right, but still the phone was a flagship.... It's sad to see zero development for it today
anandverma458 said:
Indeed you're right, but still the phone was a flagship.... It's sad to see zero development for it today
Click to expand...
Click to collapse
didn't u try any GSI rom? I believe this device is fully compatible.
m0bileb0y said:
didn't u try any GSI rom? I believe this device is fully compatible.
Click to expand...
Click to collapse
I don't know about a GSI rom, sorry ? Anyways what are they and where can I find one? I think I've seen some websites that offer a custom rom for this phone and I think that they mentioned GSI, but the websites looked kinda shady to me and they were even providing a link for TWRP for the phone....
anandverma458 said:
So the phone has been in the market for quite a while, and I'm still impressed by the monstrous specs it provided, but I'm surprised to see that there are NO custom roms or kernels for this phone, even the TWRP builds from shakalaca seem old, so I'm afraid to try them out on the latest version. Even the rooting process is complicated as compared to other phones because of no custom recovery. If any developer is interested in making a custom kernel or rom for this devices, they can head over to the official ASUS' website and get the source from here, and I'm willing to do the beta testing if the results seem promising. So, anyone?
Click to expand...
Click to collapse
accept the fact that rog phone 1 is beta for 2, the successor is 3 :laugh: . rog phone 1 user is like lab rat
With the source code / kernel available on asuses website there is no stopping a custom Ron being baked . Bake one flash it and try
---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------
Personally I was just gifted one of these phones and holy crap it's a nice experience
still no roms? we can't even use any gsi, and let an snap 845 device die at android 9 is a shame.
Henriqueceni said:
still no roms? we can't even use any gsi, and let an snap 845 device die at android 9 is a shame.
Click to expand...
Click to collapse
Agree, i can't even update mine to 9.0. I'm placing the update file as described at Asus website but it still doesnt update it .
You can try Project Treble if you don't have the ability to build a rom yourself.
I have successfully installed Android 12 based LineageOS and CorvusOS on my zs600kl using Treble, and it seems to work find. Noted that I just do it for fun cause it's not my daily drive now, any bugs would be possible, but at least it can boot just fine.
Rocky7842 said:
You can try Project Treble if you don't have the ability to build a rom yourself.
I have successfully installed Android 12 based LineageOS and CorvusOS on my zs600kl using Treble, and it seems to work find. Noted that I just do it for fun cause it's not my daily drive now, any bugs would be possible, but at least it can boot just fine.
Click to expand...
Click to collapse
I Actually sold it 3 weeks ago now .
Wrote a guide recently about installing gsi(Project Treble) on it. Hope this will help if anyone looking to install it!
[Guide][GSI][13] GSI Install Guide for ROG Phone zs600kl
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before...
forum.xda-developers.com
Hello.I installed pixel experience custom rom [android 11 verson] in my redmi note 10 about 2 years ago.After that i again installed stock miui rom,which is currently using.I decided to install pixel experience again.But i can't find pixel experience android 11 verson.all are android 12 and 13.I need android 11,not 12 or 13.can anyone please help me find android 11 verson?
You can still find the GSI image
Release Pixel Experience 11.0 v313 · ponces/treble_build_pe
Sync with Phh's AOSP v313 Sync with October sources of PE
github.com
spider1163 said:
You can still find the GSI image
Release Pixel Experience 11.0 v313 · ponces/treble_build_pe
Sync with Phh's AOSP v313 Sync with October sources of PE
github.com
Click to expand...
Click to collapse
can't understand clearly what are you saying. I have no idea about GSI image.Is it possible to get android 11 rom from there?tell me please?
I didn't find the classic ROM for this version
GSI is generic system image, you need to follow this procedure
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
spider1163 said:
I didn't find the classic ROM for this version
GSI is generic system image, you need to follow this procedure
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for helping.I studied about gsi and think that,it is not a perfect option for daily use.I need android 11 custom rom with stability.Please don't forget to share with me,if you ever find any way or link to get pixel experience older android verson rom. Again Thanks for reply.
AhmedRadowan25 said:
Thanks for helping.I studied about gsi and think that,it is not a perfect option for daily use.I need android 11 custom rom with stability.Please don't forget to share with me,if you ever find any way or link to get pixel experience older android verson rom. Again Thanks for reply.
Click to expand...
Click to collapse
I think i can find it but i will need to upload it. Wait.
AhmedRadowan25 said:
Thanks for helping.I studied about gsi and think that,it is not a perfect option for daily use.I need android 11 custom rom with stability.Please don't forget to share with me,if you ever find any way or link to get pixel experience older android verson rom. Again Thanks for reply.
Click to expand...
Click to collapse
https://sourceforge.net/projects/pixelexperiencerom/files/mojito/ here it is my friend. Plus and normal editions, vanilla and gapps variants. I need a favor if you can test, i dont have pc right now so i dont wanna risk it. See if you can flash this 11 version with the recovery from 13 version. Im on 13 but i want to test 11 and cannot sideload recovery or anything else because i dont have pc or otg either. Only have sdcard.
gabsvm1 said:
https://sourceforge.net/projects/pixelexperiencerom/files/mojito/ here it is my friend. Plus and normal editions, vanilla and gapps variants. I need a favor if you can test, i dont have pc right now so i dont wanna risk it. See if you can flash this 11 version with the recovery from 13 version. Im on 13 but i want to test 11 and cannot sideload recovery or anything else because i dont have pc or otg either. Only have sdcard.
Click to expand...
Click to collapse
Thank you very much brother.Take love.I will surely inform you if i can do it.
AhmedRadowan25 said:
Thank you very much brother.Take love.I will surely inform you if i can do it.
Click to expand...
Click to collapse
Your welcome! Let me know if it can be done and your experience in the rom, ill surely will install it too if it can be done