Xiaomi 12X custom rom requested - Android Q&A, Help & Troubleshooting

Hi everyone, I've been trying to find a custom rom for Xiaomi Mi 12X, but none found so far. I tried to port Pixel Experience rom using the Xiaomi Mi 11X (alioth) device tree and changed accordingly, since the SOC and almost all specs are the same except Camera. Can anybody shed some light in how to correctly port the ROM for my devices without official device tree from LineageOS or Pixel Experience? Thank you.

Anybody has any suggestions?

JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....

Voodoojonny said:
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Click to expand...
Click to collapse
Thank you but I don't see it on crdrood website, did you build it yourself?

JChanMe said:
Thank you but I don't see it on crdrood website, did you build it yourself?
Click to expand...
Click to collapse
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!

Voodoojonny said:
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Click to expand...
Click to collapse
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?

JChanMe said:
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
Click to expand...
Click to collapse
Yes, especially the sound makes problems... When usung videocall, it's awfully distorted. I'm using stock for now. With Lawnchair and some modifications it's ok for now.
Do you know, why there's no thread for our phone here?

Just seen, you are forking some repositories... Have you been successful in building?

Voodoojonny said:
Just seen, you are forking some repositories... Have you been successful in building?
Click to expand...
Click to collapse
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.

JChanMe said:
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
Click to expand...
Click to collapse
Did you flash with vendor or system only?

Voodoojonny said:
Did you flash with vendor or system only?
Click to expand...
Click to collapse
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.

JChanMe said:
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
Click to expand...
Click to collapse
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?

Voodoojonny said:
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Click to expand...
Click to collapse
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11

JChanMe said:
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
Click to expand...
Click to collapse
But you used the lineage device tree. And PE is aosp not lineage. Might that be the problem? Would you try to build crdroid? Or instruct me how to setup a build environment?

No, I used the PE device tree, not Lineage. I used the build instructions provided by Pixel Experience for Alioth.

JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles

Maxletsplay_1 said:
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Click to expand...
Click to collapse
Didn't they release the kernel when the phone was released?

JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Technically yes, but i've checked GitHub(about month ago) and I didn't saw kernel for this phone, just an empty folder

JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Did you replaced vendor libs with libs from 12x and other stuff like fstab, bins, rc files..configs? Attach logs from boot if you decide to build again. My advice is to build as eng and disable encryption, put selinux to minimal mode, nuke livedisplay, import vendor modules if you build with stock prebuilt kernel. Always look for F Linker errors in log and resolve them.

I'm waiting for AOSP rom too.

Related

[ROM][Pixel-XL][7.1.2_r33][Unoffical] PureNexus Project [18/8/17]

G'day guys and girls
I haven't seen PN source code updated for a while on the r33 side, seems they are focusing on the kernel a little bit
So I merged the tags myself and add some features to the ROM
I'LL TRY TO KEEP THE THREAD UPDATED, BUT THERES NO GUARANTEE ON THAT, THE REPO WILL PROBABLY BE UPDATED, IF YOU WANT TO BUILD YOURSELF, GO TO THE REPOSITORY DOWN BELOW
PLEASE NOTICE
This version was NOT signed by the PureNexus's certificates, please do a FULL FACTORY RESET if you are from the offical build.
I'm sorry for the inconvenience, but this is compulsory
Features
Built in GAPPS (no gmail, Google News and weather and play magazines, don't find them useful since I've got outlook and other replacement)
Built in Greenify
Android 7.1.2_r33 August security level
VoLTE tested
Lineage Terminal
ElementalX 1.15 Kernel (NTFS rw, exFAT, High Brightness Mode, Digital Gain control)
USB Patch for using the phone as a USB HID keyboard/mouse see here
All PureNexus Features
Untested
Since I am in Australia, there's no actual way to test whether Wi-Fi calling works, but it should work considering Project Fi was prebuilted. Please tell me if I need to add anything.
Magisk
https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262
Goodwin_c's magisk seems to work very well, thanks @goodwin_c
Known Bugs
OK Google detection is known to be not working in some languages (eg. Japanese)
MusicFX don't seems to open
Screenshots
https://ibb.co/m9XXz5
https://ibb.co/fL0Ke5
Downloads
https://drive.google.com/file/d/0B5ns3qw5ULWhTkZMQ2dVN0Z3LUU/view?usp=sharing
Flashing - How to
Please unzip the zip file, flash using fastboot commands
fastboot flash system_a /path/to/system.img
fastboot flash system_b /path/to/system.img
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
GitHub Source
manifest
patched kernel
Credits
the PureNexus Project https://github.com/purenexusproject
LineageOS https://github.com/lineageos
Pelya https://github.com/pelya/android-keyboard-gadget
flar2 (aka. Aaron Segaert) https://github.com/flar2
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Sent from my Pixel XL using Tapatalk
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Ok Google works fine for me but I still haven't updated the vendor image. I'm worried I'm gonna screw up the rom. I'm gonna test it now after flashing the correct vendor image.
Ok vendor has been updated and everything is working fine.
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Delete.
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
If the official PN doesn't have a feature that a user wants, they are within their rights to build a version that incorporates that feature.
And in most cases, if the builder marks it as Unofficial (as is the case here), they are welcome to share it others, on the understanding that no support will likely be given from the official builder.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Hey, there, actually I'm also having this problem. What language are you using? I am using Japanese and this problem presents, I thought it was Google's problem so I didn't care, I'll try figure it out.
EDIT: fixes typo
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
No, they aren't dead. they seems to focusing on other things especially the kernel and they are preparing for O since all the repos are being moved to the PureNexus-Legacy repo now. So I just built myself also add things for my own use.:fingers-crossed:
Pøîñtßlåñk said:
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
Click to expand...
Click to collapse
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
cydia2020 said:
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
Click to expand...
Click to collapse
Worked fine thx.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Do you see the same thing here
Pøîñtßlåñk said:
Worked fine thx.
Click to expand...
Click to collapse
Can you get OK Google to work? What language are you on. Cheers.
cydia2020 said:
Can you get OK Google to work? What language are you on. Cheers.
Click to expand...
Click to collapse
Works fine here English.
I was using English...
Sent from my Pixel XL using Tapatalk
BHermes211 said:
I was using English...
Click to expand...
Click to collapse
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Thank you. I'll be more than happy to give it a try again
Sent from my Pixel XL using Tapatalk
MusicFX don't seems to open in case you're concerned.
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Question... Is there a way to remove system apps on this rom? I've tried to remove the YouTube app even with magisk installed it gives apps that are able to remove system apps root permission but in the app remover app itself it says that I'm not rooted

AOSP 9.0 GSI October security - A and AB Arm and Arm64 Legacy - No Modifications

I compiled the GSI overnight, its aosp_arm64_a Legacy GSI, because the ones I keep downloading are all August security patch and I wanted it a little more up to date. I got the source directly from google and built it myself. AB is now uploaded as aosp_arm64_ab. A only is also up as aosp_arm64_a-aosp. I ran it on my One Plus 5, NFC was buggy but the camera, ril, Bluetooth, wifi, and everything I tried out worked. this is vanilla, so its bare bones. no apps besides the basics, no mods or any customizing. As this is a GSI it should be useable on many devices, I can only help you with the devices that I own, pixel XL and one plus 5. If you have a device other then that, you will have to find help from someone knowledgeable about that device. I have had success using twrp and fastboot to flash the system image. I was told doing it via fastboot is the best, so you can disable verified boot, then flash, then format all in one shot. My device did not require me to disable the verify boot. From my end it was literally as simple as 3 commands via fastboot and then restart the device and I was in. I flashed a 50mb gapps package from xda here, and magisk. took some photos, connected my Bluetooth speaker, made a call. sent some texts, installed a few apps. I will be staying on stock. But only because my device has stock pie, and the theming from one plus far trumps google.
aosp_arm_a-userdebug and aosp_arm_ab-userdebug added
https://mega.nz/#F!Xh4g2KSB!EJIGQtvLFKzHzqKXmZI7tg
Sources: https://source.android.com/setup/build/gsi
Do you find it smoother than HOS Pie Beta ?
Thanks for your share! Awesome, I don't need/use NFC.
korm85 said:
Do you find it smoother than HOS Pie Beta ?
Click to expand...
Click to collapse
It's very fast. install and boot was very fast. but I just discovered my home button does not work. however I don't assume that would be a difficult fix. the back and pages button are working. its very bare tho, you need to install everything you want manually. Which I prefer, it gives me more control over my phone I find. Hydrogen works ok too, it just requires a bit of work to get play store going and remove all the bloatware. GSI camera worked fine from boot.
Dzol Cp said:
Thanks for your share! Awesome, I don't need/use NFC.
Click to expand...
Click to collapse
upload is at finished now
can a mod change the title to reflect that this will have the AB and A GSI not just A? Please and thank you.
Thanks! Any chance of an arm build?
Got no boot ......?!
Device's nubia z17 sd835
91egt said:
Thanks! Any chance of an arm build?
Click to expand...
Click to collapse
yea, it will be up in the morning. I did A and just about done AB for arm64, then will do A and AB arm
aljoscha81 said:
Got no boot ......?!
Device's nubia z17 sd835
Click to expand...
Click to collapse
how did you flash it? I didnt use trwp, I used fastboot from the pc
godkingofcanada said:
how did you flash it? I didnt use trwp, I used fastboot from the pc
Click to expand...
Click to collapse
Maybe thats the matter i always use twrp but got..... So far never problems ....?
Make it a difference?
aljoscha81 said:
Maybe thats the matter i always use twrp but got..... So far never problems ....?
Make it a difference?
Click to expand...
Click to collapse
It shouldn't. But its twrp. Weird things happen. Use fastboot. Its only 3 or 4 steps. The tutorial is on the google gsi website. I tried via twrp and had no issues however. It started to launch then rebooted, second boot it loaded OK
Cracked screen. But you can see the build info
godkingofcanada said:
Cracked screen. But you can see the build info
Click to expand...
Click to collapse
Ok.. will test out with fastboot thanks a lot!
aljoscha81 said:
Ok.. will test out with fastboot thanks a lot!
Click to expand...
Click to collapse
No problem
AB will be posted in about 2-3 hours. After that I will build A only Arm. It should be available by morning.
a/b please
irfaniphank2 said:
a/b please
Click to expand...
Click to collapse
Aosp_arm64_ab-userdebug will be on the link in post 1 in about 90 min. Its 90% done building.
godkingofcanada said:
Aosp_arm64_ab-userdebug will be on the link in post 1 in about 90 min. Its 90% done building.
Click to expand...
Click to collapse
:good::good::good::good::good::highfive::highfive::highfive:
AB arm64 legacy is now uploaded to the link in post one. Arm A and AB will show up over night. Starting with a in the morning. It takes about 4.5 to 5 hours to build

Project Treble - GSI Roms after Pie update

So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Riskypedia said:
So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Click to expand...
Click to collapse
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
arslancn said:
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
Click to expand...
Click to collapse
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Riskypedia said:
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Click to expand...
Click to collapse
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
arslancn said:
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
Click to expand...
Click to collapse
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Riskypedia said:
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Click to expand...
Click to collapse
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
which version of gcam works?
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
did you have same bug on XZ1?
the battery level always in 20%.
arslancn said:
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Click to expand...
Click to collapse
Sadly, it seems it's impossible to use AOSP based system because of its stability. It's way too unstable to use, but I think I can share the built images to make progress! Again, thanks for your help
gacky1601 said:
did you have same bug on XZ1?
the battery level always in 20%.
Click to expand...
Click to collapse
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Riskypedia said:
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Click to expand...
Click to collapse
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew the methods to the image step by step from Sony's source.
Maybe we should build the kernel by ourselves
The problem you mentioned about disconnecting network, does it happens on wifi or mobile data?
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
gacky1601 said:
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew how to build the image step by step from Sony's source.
Maybe we should build the kernel by ourselves[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel
Click to expand...
Click to collapse
lilbrat said:
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
Click to expand...
Click to collapse
I think you can just try it with stock boot , vendor and oem.
I will works perfectly.
Don't forget to report if there is any problem or it work properly.
---------- Post added at 04:37 PM ---------- Previous post was at 04:20 PM ----------
[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel [/QUOTE]
Yeah. I think there are a few developers work on XZ1.
Have .
The working perfectly rom will be our target, like the thread below.
https://forum.xda-developers.com/xperia-xz1-compact/how-to/xz1c-g8441-lilac-aosp8-1-t3762581
Share your all files so that i can work with gcam to be installed properly to latest pixel experience.

[ROM][GSI] MSM Xtended XP9 Release v19 [UNOFFICIAL][ARM64 A-A/B/ARM32A]

:silly:
Thank you for the build, @luisgonzales1977
Waiting for A/B build.
ZainBilq said:
Thank you for the build, @luisgonzales1977
Waiting for A/B build.
Click to expand...
Click to collapse
when you finish testing :good::silly:
Will it include Mi9 in-display FP like in phhusson's AOSP?
luisgonzales1977 said:
when you finish testing :good::silly:
Click to expand...
Click to collapse
Yeah I know...just like that....
This Rom work in Lenovo k5 pro? Is a device arm64 aonly.
any AB love ?
TheUndertaker21 said:
any AB love ?
Click to expand...
Click to collapse
they are soon testing it...:good:
luisgonzales1977 said:
when you finish testing :good::silly:
Click to expand...
Click to collapse
I am a few hours on your rom and is working bugfree for me everything i need arcore also working very nice job:good:
Excellent work !
Booted successfully on Huawei p10 lite after changing selinux/mapping/26.0.cil .
Except I have faced settings FC when opening Decor room in X-Tensions and I'm not able to make logcat due to ADB unauthorized
Thanks
android q activity animation available sir?
won't be able to bootup on mate 10 lite
flamedrops said:
won't be able to bootup on mate 10 lite
Click to expand...
Click to collapse
you test?
successfully booted up on my Lenovo S5 (K520/Seoul), but on the first setting screen after boot it shown missmatch vendor notice (it recommend to flash vendor img). i still could skip it and continue by the way.
So about the missmatch vendor, will it hurt if i don't flash it? because i don't know which file of vendor img i should flash.
update : same as reported from other user several posts before, Decor room in X-Tensions FC when open
luisgonzales1977 said:
you test?
Click to expand...
Click to collapse
yes, i use to try every other rom, now im on havoc and it works.
Boots up in Blu Vivo XI. Can't seem to get magisk to work with any gsi's. Thanks for the rom.
aljoscha81 said:
I am a few hours on your rom and is working bugfree for me everything i need arcore also working very nice job:good:
Click to expand...
Click to collapse
Hi pal. Any specific steps to flash this rom on Z17? What rom as base do you have? Any nfound vendor or something else?
surfer30 said:
Hi pal. Any specific steps to flash this rom on Z17? What rom as base do you have? Any nfound vendor or something else?
Click to expand...
Click to collapse
I am on mokee as base installed as ever no further steps
Is there a chance to get an ARM32-A build? I would like to try this rom. Looks promising!
khuy21 said:
So about the missmatch vendor, will it hurt if i don't flash it? because i don't know which file of vendor img i should flash.
update : same as reported from other user several posts before, Decor room in X-Tensions FC when open
Click to expand...
Click to collapse
not need change vendor
just need set right fingerprint values in build.prop, some magisk modules may this
or search info and change it by hand
on short - fingerprint from system build.prop need to match values from vendor build.prop

so i found a afh (Android File host) user named cookie.....

[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Some random said:
[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Click to expand...
Click to collapse
NO luck,stuck at G logo :crying:
lookmanns said:
NO luck,stuck at G logo :crying:
Click to expand...
Click to collapse
Me 2
Even with A CRAP TON
Of patches
Some random said:
Me 2
Even with A CRAP TON
Of patches
Click to expand...
Click to collapse
btw I found this dev in galaxy s2 plus forum,and his name is ud4
lookmanns14 said:
btw I found this dev in galaxy s2 plus forum,and his name is ud4
Click to expand...
Click to collapse
Oh
Nice!
UPDATE:
I was able to contact him and got an answer
He stated that he did not have an Xperia x to test this ROM
But told that I could test and send feedback if it works or not.
Maybe you can write a PM asking if you can test too! (Anyone who reads this can ask!)
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
iH8Ecchi said:
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
Click to expand...
Click to collapse
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
If not.....extract kernel and see what's wrong I guess
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
it will not boot with android 8.1 an 9 oem..you just got infinity restart
I think oem already include in this rom,you can check oem file after flash the rom in /root/oem using twrp file manager
Someone needs to take some logs without patches of any sort
On the 4.4 kernel Version
(Got private message about this 45 minutes ago)

Categories

Resources