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?
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
This is more or less a copy-paste from the same thread over the s9 section but whatevs. I thought you guys would like this too.
Pixel Experience ROM for the NOTE 9
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Click to expand...
Click to collapse
Semi-GSI? what's that?
a semi-gsi (at least by my own definition) is a gsi built from source, with heavy patches intended for a specific device that wouldn't make the gsi necessarily as universal as a gsi should be. so in terms: don't flash this on other devices.
How does this differ from any other gsis out there/what are the features?
Well this includes a number of fixes including:
Dual speakers are working.
Ui lag is no more (at least 99.99%).
Aod is working/enabled.
Auto brightness is kinda working.
MTP is working
Other performance fixes and improvments.
What's working/not working?
First up:
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS Pixel Experience. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS PixelExperience.
Click to expand...
Click to collapse
2ndly the semi-gsi has a few quirks of it's own. Nothing major or worth noting but you should check the "anything else i should know?" part in the FAQ. hence why HWC is broken
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build image and kernel linked below
Reboot to recovery
Wipe system, data and cache from the wipe menu
Select flash image in twrp, lower right side on the install menu
Flash the rom image as system (and gapps). DONT flash gapps. they are already included in the rom.
Flash the kernel image corresponding to your model as boot
Reboot and enjoy :victory:
Downloads:
Galaxy S9/S9+ Exynos semi-gsi image link: (G965/N960/F/FD/S/N): here
Kernel image link(important to use this. read more in FAQ):
S9 Exynos: here
S9+ Exynos: here
Note 9 Exynos: here
A pretty good (unofficial) mirror for (some of the) above files and more is this
Providing feedback:
You are more than welcome to provide any kind of feedback here.
(limited only to feature requests; it's called "pixel experience" for a reason and it should stay that way)
You can also msg me anytime on telegram @ Rainbow_Alex_Dash
Telegram group?
I usually like to hang around here . It isn't mine but hey.
For note 9 more specifically i hang around here too
Changelog:
12.10.2018:
Initial release Boi
Troubleshooting/FAQ:
Q:Can i use any other kernels with this gsi?
A:Nah, not really. I built this kernel specifically to work with this gsi and it includes a few major fixes (for example mtp won't work,major ui lag, no dual speakers etc if you switch to another kernel. But again. If you want to use other kernels, they should* boot. Endurance kernel even has my dual speaker patch and i confirm as working. But again expect bugs.
Q: Is there anything else i should know?
A: Ehhhhhhh, not really. I mean there are some stuff i'm really not proud of,for example to "fix" the ui lag i had to set the minimum gpu frequency to 455; this shouldn't create any issues(perhaps some battery drainage when screen is on) but afaik it doesn't impact sleep or anything else.
Q:Would this be preferred over a device specific rom?
A: Overall nah. The reason i didn't set on building device specific los16.....well actually i did and failed. But this is a pretty good placeholder until someone more skilled than me takes over and creates pie device trees.
Q: Safetynet doesn't pass?
A: Yeah, i guess that's a thing. Go into magisk and download some module called props hide or something. Don't forget to run it from terminal. It should work from there
Q: The rom isn't booting/camera doesn't work
A: Flash/make sure you have the BRI4 vendor, the linked kernel and try again.
Q: The rom is in a bootloop/google apps keep crashing
A: You did read the instructions and NOT flash any gapps riighhttt?? smh, wipe /system,/data and /cache and start over
Q: I have another bug; How can i tell it to you while slightly increasing my changes of it ever getting fixed.
A: You can tell me what's going on either here or on telegram WITH A LOGCAT attached(required);if rom isn't booting at all attach /proc/last_kmsg.
Q: I don't know what/how to logcat. Is it really necessary?
A: Logcat or gtfo
Q: How can i support you?
A: Awwww thanks; On most of my posts on the left side there's a "donate to me" paypal button; You can use that,donations are more than welcome, or if you don't have any $ to spare you can also post here about how awesome i am (this surprisingly helps very much)
Credits:
The lineageos team; device maintainers who did a wonderful job at creating device trees
The pixel experience team for creating the rom we so do enjoy
Many good people from the telegram group (linked above) that helped me create this project and spamming for etas
Big thanx to iqbal sareem best creationner ever; great help
XDA:DevDB Information
Pixel Experience 9.0 Semi-Gsi for the S9/S9+, ROM for the Samsung Galaxy Note 9
Contributors
Rainbow_Dash, phhusson,malinathani, eamo5, jesec
Source Code: https://github.com/rainbowdashh/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-10-12
Created 2018-10-12
Last Updated 2018-10-13
Thanks for sharing.
Wonder if this Kernal image will work with other GSI roms to get them running as smooth as this rom.
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen does work as a pointer and to tap and even draw..
The spen button does nothing though. And obviously, the spen settings and apps are all Samsung made so they won't be working here. Highly doubt Spen would work ever on aosp like stock due to Samsung apps incompatibility
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen went work without Sammy's framework but there are plenty of apps on play store that offered similar effects to Sammy's own. I used them on my note tablet when I ran any other rom then sammy roms.
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
s3xxt0y said:
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
Click to expand...
Click to collapse
I don't know what you mean by data but i do know the kernel is supposed to be flashed as boot
Problem with fingerprint here.
Only first touch for new finger is registered.
After that it's not working anymore.
Data as in mobile / cellular data as discussed in telegram.
For anyone who has no cellular manually add your APN info in network settings.
Fingerprint does work and adds, go to settings and add fingerprints the registration bit is a bit finnicky but it adds them and they work.
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
sam razzy said:
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
Click to expand...
Click to collapse
Quoting tylerrw from the Note 9 Telegram group...
tylerrw:
Wipe data, cache (not system) > reboot recovery > install semi gsi image > install kernel > install no verity > install magisk
Reinstall (ARH6) vendor image too
After installing semi GSI
Click to expand...
Click to collapse
AlfaM03 said:
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
Click to expand...
Click to collapse
No, there's no way to get these features to work in Aosp based roms.
Fingerprint is not working, too all other works fine thank you soooo much!
Dan_FFM said:
Fingerprint is not working, too all other works fine thank you soooo much!
Click to expand...
Click to collapse
Same Here
Do we have the gestures like the pixel 3?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
No, nur you can activate IT via ADB shell command
If I want to flash another rom after flashing this rom and kernel, can this kernel work well with other roms or should I flash another kernel instead?
My number 1 question is: does dual sim work?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
Yes - Go into gestures in settings and enable the swipe up gesture. It's under Settings>System>Gestures
Note: This is not a ROM based on the ROM shipped with your device. Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Features Overview:
https://www.xda-developers.com/lineageos-15-feature-list-overview-screenshots-video/
Screenshots:
View attachment 4491847View attachment 4491848View attachment 4491849View attachment 4492992
Device Info:
Galaxy Note 9 (Exynos): TBD
What's working:
TBD
This build is an official LineageOS build. Compliance with our device support requirements is enforced and guaranteed. That means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
Camera
Fingerprint Sensor
NFC
Etc. Check device support requirements for more.
What's not working:
Applicable exceptions granted in device support requirements.
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Instructions:
Make sure TWRP has been installed and functional
Download the latest build (and optionally gapps)
Download the compatible vendor image (https://androidfilehost.com/?w=files&flid=284041)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (and gapps)
Reboot
LineageOS updater will handle updates automatically (OTA).
If you upgrade manually from older official releases to newer releases, you don't need to wipe your data or reflash gapps.
Downloads:
Galaxy Note 9 Exynos (N960F/FDS/N): https://www.androidfilehost.com/?w=files&flid=284057
Root addon: https://download.lineageos.org/extras
Google Apps: https://wiki.lineageos.org/gapps.html
Reporting Bugs:
https://wiki.lineageos.org/bugreport-howto.html
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /proc/avc_msg.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Please use LineageOS BUG tracker to report BUGs. BUGs reported in the thread could be ignored due to large number of posts.
Channel and Group:
LineageOS Channel (News and Updates):
https://t.me/lineageos_star
AOSP-like ROMs (not limited to LineageOS) Group (Discussion, Quick Tech Support and Early Testing):
https://t.me/joinchat/DTrGs0ygFKxHhc3bb11YKw
XDA:DevDB Information
LineageOS for Galaxy Note 9, ROM for the Samsung Galaxy Note 9
Contributors
jesec
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-10-18
Last Updated 2018-10-18
Reserved
Reserved
Happy days! Thank you Jesse Sir!
Thank you soo much sir
---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------
And good luck for LOS 16! I'm sure you can give us a sweet slice of pie
I have been waiting for this, once my bootloader is unlock ill see to it, it will be my 1st try to note 9 cfw. Thanks jesec.
Flashed, stuck at bootlogo. Doesn't even loop?
Tried flashing with noverity, tried with magisk, without magisk. Maybe vendor is bad?
s3xxt0y said:
Flashed, stuck at bootlogo. Doesn't even loop?
Tried flashing with noverity, tried with magisk, without magisk. Maybe vendor is bad?
Click to expand...
Click to collapse
yeah i think vendor is broken, try stock vendor
malinathani said:
yeah i think vendor is broken, try stock vendor
Click to expand...
Click to collapse
Flashed with diff stock vendors still stuck @ bootsplash.
Edit: tried without gapps to be sure too. Still no joy.
Jesse - might be worth joining the Note 9 AOSP Telegram. There's 50 of us in there if you need us for testing etc;
https://t.me/joinchat/GnVMLU__5M8g5NaStUlbRg
s3xxt0y said:
Flashed with diff stock vendors still stuck @ bootsplash.
Click to expand...
Click to collapse
bootsplash stuck could be a kernel
Are you sure magisk script ran correctly? Try flashing magisk again and see.
Thanks brother
Hello,
Does S-pen features work?
Thx
how to fix bootsplash?
Well hot damn! :highfive:
muhyidin said:
Hello,
Does S-pen features work?
Thx
Click to expand...
Click to collapse
spen is for touch wiz aka Sam experience
for the rest if the android world it's a mouse pointer.
Thank you @jesec for the effort.. This is exactly what I was looking for.
I tested this on N960F/D got stuck on bootsplash as well, I tried both Stock Vendor and the provided Vendor Images, with or without magisk with no luck.
I tried restoring boot image from previous backup (this might sound stupid) but I got past the splashcreen into Lineage Loading screen, it would stay for a minute then reboot to recovery.
For people who got stuck in the bootsplash
To exit the bootSplash freeze use the download mode button combination: Down+Bigsby+Power until screen goes off then recovery shorcut Up+Bigsby+Power,
Did anyone manage to make this work?
that_same_guy said:
Thank you @jesec for the effort.. This is exactly what I was looking for.
I tested this on N960F/D got stuck on bootsplash as well, I tried both Stock Vendor and the provided Vendor Images, with or without magisk with no luck.
I tried restoring boot image from previous backup (this might sound stupid) but I got past the splashcreen into Lineage Loading screen, it would stay for a minute then reboot to recovery.
For people who got stuck in the bootsplash
To exit the bootSplash freeze use the download mode button combination: Down+Bigsby+Power until screen goes off then recovery shorcut Up+Bigsby+Power,
Did anyone manage to make this work?
Click to expand...
Click to collapse
Same problem here, Stuck on bootloop
Jesec is back
The ROM doesn't boot for anyone curious. I haven't heard of a report of one booting successfully anyway.
bober10113 said:
spen is for touch wiz aka Sam experience
for the rest if the android world it's a mouse pointer.
Click to expand...
Click to collapse
You maybe answer the sensitivity level but there is also the need to some kind of powering off the 500KHz signal send when not using the pen.
Then can we use the sensor to activate the pen ? What about the Bluetooth button ?
The wacom screen could be initialize from the begining with Project Trebble. What's the differences with LOS for S9s ?
{
"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:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
2) I also noticed that TWRP is not available for Moto G Power (2021), is there a good alternative or I have to use adb fastboot?
Thanks!
Edit:
I just found the thread:
[RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
I can try that for question 2
Efone said:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
Click to expand...
Click to collapse
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
1) unlock bootloader
2) flash twrp in recovery
3) flash blankflash.zip (or official?) through twrp
4) flash magisk through twrp
5) restore my old phone dotOS android 11 backup through twrp
and I should have all the apps and data as in the old device?
Efone said:
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
Click to expand...
Click to collapse
The blankflash is only if you can no longer flash anything by usual methods
Blankflash and EDL Mode
Is my device in EDL Mode?
How to boot into EDL Mode
Thanks for the info!
Should the reasoning above work if I use official instead of blankflash?
Efone said:
3) flash blankflash.zip (or official?) through twrp
Click to expand...
Click to collapse
Neither the blank flash nor official firmware are twrp compatible.
Thanks sd_shadow for the info, it is really helping me out.
I saw your post for using LSMA, but I couldnt find a Linux version. Is there one? Or the only other option I have is going through the fastboot process?
Can anyone tell me if there is going to be custom roms made for Borneo?
Hatrackman said:
Can anyone tell me if there is going to be custom roms made for Borneo?
Click to expand...
Click to collapse
Still the reason I cite in post 2 above, indeterminate, sadly.
Onoitsu2 said:
Still the reason I cite in post 2 above, indeterminate, sadly.
Click to expand...
Click to collapse
Mostly concerned because google has said they're going to stop their 'less secure app' thing at the end of this month and it might mean textnow will stop working outright for people that don't use play services.
Hopefully anyone working on making a custom rom for Borneo will see this thread and maybe give an idea if its going to happen.
Does this help?
If I wanted to start from scratch what would I need to know to make my own custom rom? Don't need a phone, will only ever use wifi. Just need microg basically.
The following statement is on the dotOS FAQs:
Q: My device is not supported! What should I do?!A: First reason can be that our development team doesn't have your device to support it or we no maintainer applied for this device. You can always use our GSI builds if your phone supports Treble Project.
Here we have this statement:
... Google requires every Certified Android device launching with Android 8.0 Oreo and above to support Treble.
Here borneo is listed as a supported device.
Does this mean dotOS GSI supports MotoGPower 2021 without the need of vendor blobs?
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
@sd_shadow
Two sites that potential rom developers may want to check out:
1) https://github.com/moto-common
check out: https://github.com/moto-common/andr...ernel/blob/12/dtb/bengal-moto-base-borneo.dtb
2) https://github.com/moto-sm6115
Scroll through the list of repositories, particularly in the moto-common site
@sdembiske that looks promising, I am willing to give it a shot and contribute to the community. Is there a good guide on how to build the kernel with vendor tree/blobs etc...?
Reference "Moto G Power 2021 XT2117-4 Firmware Extractions" - You will find the extracted kernel etc. in the boot.img extracted link that you can download - there are many other extractions that you hopefully can use to build a custom or AOSP rom.
Your best bet would be to add a pre-built kernel in the build - you can google that for how-to's.
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
The Xiaomi poco m3 has the same SoC and other innards as the Moto G Power 2021 and it also has unofficial Lineage OS 19 support. I am considering hitting them up and using their code as part of the build. I'm also requesting Motorola Mobility LLC to release the kernel source for Android 11. I already have a device tree for Borneo on my github. Me and Fazwalrus have a telegram chat set up for the ROM development here