DELETE
DELETE
Reserved
For Indian Users +8.1 AOSP Users
If Jio 4g voice is offline Turn on Location and it will work
P.s Turn on location in Battery saver mode it will not consume more battery then.
Regards~
Great, I'll check this in few days Before this i have questions
Magisk works on this rom?
Can i return to nougat roms?
bohdankrulik said:
Great, I'll check this in few days Before this i have questions
Magisk works on this rom?
Can i return to nougat roms?
Click to expand...
Click to collapse
magisk is not working ? for now
---------- Post added at 01:49 AM ---------- Previous post was at 01:07 AM ----------
Treble Support Included
You can now flash any GSI Image on This TWRP
detailed Instructions on it will be added later ?
Regards~
Proximity sensor does not work
Earpiece volume is too low. Having trouble listening to calls.
And yes safetynet passes. I am able to use Google Tez and Snapchat.
mthepa said:
Proximity sensor does not work
Click to expand...
Click to collapse
it works just need to be calibrated
After installing this TWRP oreo, the screen does not work
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
stanislavskiy said:
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
Click to expand...
Click to collapse
there are some personal reasons for not opening device tree and vendors please understand also treble support is there so
any GSI image will bootup without issue so ahead from this I don't think no more roms needed also kernel sources are already there.
Regards~
murtaza1326 said:
there are some personal reasons for not opening device tree and vendors please understand also treble support is there so
any GSI image will bootup without issue so ahead from this I don't think no more roms needed also kernel sources are already there.
Regards~
Click to expand...
Click to collapse
My message was for Dinolek
And Treble support is good but not enough if you want to build a rom for yourself because Dinolek made changes for core system libraries/frameworks. And kernel is not a problem at all. The problem was to make everything working on system-level and Dinolek did it. That's awesome.
stanislavskiy said:
My message was for Dinolek
And Treble support is good but not enough if you want to build a rom for yourself because Dinolek made changes for core system libraries/frameworks. And kernel is not a problem at all. The problem was to make everything working on system-level and Dinolek did it. That's awesome.
Click to expand...
Click to collapse
i replied on his behalf only he have exams i was also there when he was bringing up this project now i openly say why sources are hidden you know lunik he charges money for developing roms also he didn't provided credits to patches owner dinolek did it for us i know other developers also want this but if all sources goes out i am damn sure lunik will copy his work and earn money from it so sources are not open tho kernel sources with modifications are out you can bringup with that kernel
stanislavskiy said:
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
Click to expand...
Click to collapse
Source will be uploaded when rom get to beta stage.
I'm not using clear aosp sources, I based on Mediatek alps 8.1 source code, that's why it's hard to share it in proper way.
Nothing is based on work from other contributors, except maintained ones.
Stuck at boot animation
Test results
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
SAM.J said:
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
Click to expand...
Click to collapse
Thanks for feedback.
About 2 and 3, install latest 6.2.0.0G from flyme site, not twrp one.
For 4 flash the fix from rom download link fix_alsps_mblu2_oreo.zip, it will be included in next update.
About 5, we don't have gyroscope, on other firmwares it is emulated from magnetometer.
What do you mean in 9?
To disable hardware keys and enable software flash zip from faq.
SAM.J said:
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
Click to expand...
Click to collapse
2nd,3rd and 9th option from not working are working fine on my device.
Thank you very much for the firmware!
Related
Hello everybody!
This thread will be dedicated to Android N developement. Since now the ROMs are not ported (we have a device tree to compile from source) we can get any Android N ROM working but with the same bugs.
From now on i will be working on fixing the bugs of the device tree/vendor tree and any help with it would be apreciated.
I will share my device tree so that people can help with it:
Device tree: https://github.com/end222/lineage_device_omega
Vendor tree:https://github.com/end222/lineage_vendor_omega
Want to help?
In the device tree in github I have opened some issues where I try to put as much relevant information as I can about the state of each bug and the errors I am getting. Please give it a look to see if someone can help
Bugs:
Working:
It boots up
Speaker sometimes
Network
Wifi
Bluetooth
FM Radio
Chargin while being off
Flashlight
Rear camera without focus
Mobile data
Sound
Not working:
Calls
Camera focus and front camera
Headphones
IR
Fingerprint sensor
It shows corrupted SD at boot but SD works good
Download links:
LineageOS: https://www.androidfilehost.com/?fid=817550096634793903
Old ones (To be updated):
AICP: https://www.androidfilehost.com/?fid=745425885120743786
Resurrection Remix: https://www.androidfilehost.com/?fid=817550096634781602
Dirty Unicorns: https://www.androidfilehost.com/?fid=817550096634782672
If you want to give a try to another AOSP like ROM just tell me and I can make a build
If you try the ROM and find any bug please tell me and I will add it to the bugs section in order to work on it and also to give other a clearer information about the ROM.
Do you like my work?
Offer me a beer here:
https://www.paypal.me/OrdunaLagarma
You forgot to add fingerprint sensor.
kristi6.9 said:
You forgot to add fingerprint sensor.
Click to expand...
Click to collapse
That's right
I recommend you to atach the sources below the rom and use devdb not just a regular thread
kristi6.9 said:
I recommend you to atach the sources below the rom and use devdb not just a regular thread
Click to expand...
Click to collapse
In the end I didn't use the device tree I had done. CM sources were giving me warnings about framework, something related to non-existent images for the resolution of the Redmi Pro (CM had already closed when I downloaded them).
Then I took the ROM compiled by andrianom for the RN4 and resized the system dat by hand. Then I modifyed the kernel to get it working on the RM Pro.
So in the end this is a port from the RN4, it is not compiled from source. However I will try to compile Lineage from source as it is almost the same and the device tree I had made should work with some modifications
OK
end222 said:
In the end I didn't use the device tree I had done. CM sources were giving me warnings about framework, something related to non-existent images for the resolution of the Redmi Pro (CM had already closed when I downloaded them).
Then I took the ROM compiled by andrianom for the RN4 and resized the system dat by hand. Then I modifyed the kernel to get it working on the RM Pro.
So in the end this is a port from the RN4, it is not compiled from source. However I will try to compile Lineage from source as it is almost the same and the device tree I had made should work with some modifications
Click to expand...
Click to collapse
If someone could fix fingerprint sensor and headphones, I'm sold
misterright1 said:
If someone could fix fingerprint sensor and headphones, I'm sold
Click to expand...
Click to collapse
I know there are many bugs but at least headphones are working
end222 said:
I know there are many bugs but at least headphones are working
Click to expand...
Click to collapse
HHahahah thats an advantage according to other roms.?????
when can you make this rom stable bro?not eta just asking
pou_gh2 said:
when can you make this rom stable bro?not eta just asking
Click to expand...
Click to collapse
I won't answer that question [emoji14]
I am still really new in the world of developing ROMs as Redmi Pro is the first device that I have used for developing. Then if I knew how to solve all the bugs maybe I could tell you more or less how long it could take.
However, the only thing I know is that I have to modify the vendor tree by mixing it with the vendor tree of other devices. So I cannot tell how long it can take and if I will be able to do it
pou_gh2 said:
when can you make this rom stable bro?not eta just asking
Click to expand...
Click to collapse
don't be a prick dude
Recommended resources
Hi end222 , I just got this phone. Love the specs / screen / performance. The only thing i hate is the OS. I had been using Nougat on a flashed Samsung S4. Just cant bear the older version of Android now, especially the notifications.
I am not new to the world of development but haven't developed ROMs before. Are there any recommended resources you have where I can learn the basics and add on to the work you have done so far. I would love to to be able to create version which can be used daily.
turbochild said:
Hi end222 , I just got this phone. Love the specs / screen / performance. The only thing i hate is the OS. I had been using Nougat on a flashed Samsung S4. Just cant bear the older version of Android now, especially the notifications.
I am not new to the world of development but haven't developed ROMs before. Are there any recommended resources you have where I can learn the basics and add on to the work you have done so far. I would love to to be able to create version which can be used daily.
Click to expand...
Click to collapse
I would really love to see more people working for this phone.
What I recommend you is to read some of the MTK porting guides that can be found on the internet, for example, on xda.
The most important thing you have to learn from those guides is how to port the boot.img.
Do not try to port the whooe ROM using those methods because I tried and they result in most of cases in bootloop. So to port to Redmi Pro you have to:
- From RN4 just by porting the boot.img (and resizing the system image in Nougat) is enough to get it booting.
- From Apollo Lite you will have to copy also hwcomposer from the stock ROM, located in lib/hw and lib64/hw. Also do not forget to port also the boot.img
If you find any problem or have any doubt do not hesitate to send me a message and I will do my best to help
Enviado desde mi Redmi Pro mediante Tapatalk
Thanks end222 for your work keep it up man
Sent from my Redmi Pro using Tapatalk
Lately, I have been always checking all the threads created expecting for any stable update to flash redmi pro but it seems everyone gave up from porting... Is there anyway to port an existing nougat ROM from other xiaomi model and getting stable ? At least the phone and the headset part... I am tired of MIUI ROM specially the weekly version...
Besides that I would to thank to all the people that had helped with this project without them I probably had sold my redmi pro already >.>
rijrg4 said:
Lately, I have been always checking all the threads created expecting for any stable update to flash redmi pro but it seems everyone gave up from porting... Is there anyway to port an existing nougat ROM from other xiaomi model and getting stable ? At least the phone and the headset part... I am tired of MIUI ROM specially the weekly version...
Besides that I would to thank to all the people that had helped with this project without them I probably had sold my redmi pro already >.>
Click to expand...
Click to collapse
The closest phone to the RM Pro is the Redmi Note 4 and this is the best I have been able to do by porting from that device. The main problem is that the phone isn't working in the RN4 either.
Whenever I have more free time I will keep trying things. It should be possible to get at least a good working non MIUI ROM based on Android 6. However it would be much harder to get Android 7 stable
I want to try this ROM, can i downgrade to 6.0 based miui rom safely after I try this ROM? ini
doripto. said:
I want to try this ROM, can i downgrade to 6.0 based miui rom safely after I try this ROM? ini
Click to expand...
Click to collapse
Yes, you should be able to flash MIUI with TWRP after using this ROM. I would also recommend you to do a backup of MIUI before flashing it and then you can come back to MIUI without losing any apps
I tried this rom last night and its great to experience CM again, btw when im insert my sd card it says that my sd card is corrupted but its not corrupted and working fine when I tried it with my sisters MiMax...
XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd
reserved
reserved 2
Does safety net pass with or without magisk?
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?
Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.
hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?
Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~
Lineage 15.1 for Xperia X Performance
Based on SODP
By Sjll
This is a stable and performance version
Download Link: AndroidFileHost
Choose the file named "dora"
OEM download : Link
How to flash:
Flash official 41.3.A.2.149
1. Wipe Data and flash in twrp
2. Flash oem in SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone.zip
3. Boot and Enjoy.
Feature: Performance, Stable, Gcam support.
Gcam recommend: MGC_6.1.009_MI8_A8.1+_V0_2.apk
For dual model
Add this in build.prop
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
Source code: Github
Also thanks to:
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Everyone involved in working and testing
XDA:DevDB Information
Lineage 15.1 for the Sony Xperia X Performance
Contributors
Sjll
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Created 2020-03-26
Last Updated 2020-3-26
will we have orange fox recovery for "dora" or "x performance"
This rom's stability is better than the project treble.The QuickCharge is work and battary life is quite long.But it still has random reboot(seldom).
---------- Post added at 02:34 PM ---------- Previous post was at 02:19 PM ----------
Thestardr said:
will we have orange fox recovery for "dora" or "x performance"
Click to expand...
Click to collapse
I think the TWRP is enough and OrangeFox is based on the TWRP
For my XP this rom stable
i like this rom. that's all
I like this ROM very much. It works more stably on my Xperia x performance than treble and can use GCAM, but the game performance is not good. I hope sjll can continue to optimize. How can I donate it to you?
Hi!
Does this ROM have support for dual SIM?
janvantonder said:
Hi!
Does this ROM have support for dual SIM?
Click to expand...
Click to collapse
Add this in build.prop
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
Thestardr said:
will we have orange fox recovery for "dora" or "x performance"
Click to expand...
Click to collapse
No plan this time, sorry.
ariwindarto said:
i like this rom. that's all
Click to expand...
Click to collapse
Thx.
LeafNic said:
I like this ROM very much. It works more stably on my Xperia x performance than treble and can use GCAM, but the game performance is not good. I hope sjll can continue to optimize. How can I donate it to you?
Click to expand...
Click to collapse
My paypal is in my old thread bottom, glad if you could donate for my VPN costs. Thx.
Thanks Sill - I'm still testing but this Rom looks very promising. The usual bugs encryption, WiFi direct, random reboots, battery drain, etc.. are not present here.
For GCAM I only got version 5.3 (without night sight) to work. Very few version 6.1 apk work and I have not found any 6.1 with working night sight.
Thanks also for the dual sim configuration. I'll give that a try in the evening.
janvantonder said:
Thanks Sill - I'm still testing but this Rom looks very promising. The usual bugs encryption, WiFi direct, random reboots, battery drain, etc.. are not present here.
For GCAM I only got version 5.3 (without night sight) to work. Very few version 6.1 apk work and I have not found any 6.1 with working night sight.
Thanks also for the dual sim configuration. I'll give that a try in the evening.
Click to expand...
Click to collapse
MGC_6.1.009_MI8_A8.1+_V0_2.apk
This version is OK.
Thanks - I found this version works too and has more options and modes:
Gcam_6.1.021_Advanced_V1.6-Fu24_5Lens-02b6.5-A10.apk
You need to disable "Sabre" under the "Fix" menu item otherwise Night Sight will crash after taking a picture
I have both the single SIM (F8131) and dual SIM (F8132) model of this phone and I've tried a lot of custom ROMs for this phone most of which have bugs which make it impossible to use any of these ROMs as a daily driver.
This unofficial version of Lineage looks promising - At least for the single SIM model of the Xperia X Performance. Based on my experience with other custom ROMS for this phone I tested this version of Lineage for around two days and here are my findings:
-) ROM is stable and has good battery life - I did not experience any random reboots at all.
-) Encryption works - No issues here either
-) For the single SIM Xperia X Perf. the only annoying issue is a frequent error message "Your device failed verification and will not work properly" before Lineage boots. The phone powers down after the message is displayed and several start-up attempts are necessary before the phone boots up. This also happens for the dual SIM model.
-) The biggest issue for the dual SIM model is that Radio does not work at all - The phone cannot connect to any mobile network. This is not an issue for the single SIM model where Radio works fine.
-) Selinux is disabled but can be enabled pretty easily - I used an app "SELinuxModeChanger".
-) WiFi direct does not work but at least there are no negative side effects like high CPU usage and battery drain caused by this broken feature.
Hi, is there a specific TWRP version to use with this rom?
I have tried the official TWRP but got a "could not mount /data and unable to find crypto footer" when attempting to back up.
dcemu said:
Hi, is there a specific TWRP version to use with this rom?
I have tried the official TWRP but got a "could not mount /data and unable to find crypto footer" when attempting to back up.
Click to expand...
Click to collapse
Try this:
https://www.androidfilehost.com/?w=files&flid=296600
janvantonder said:
-) The biggest issue for the dual SIM model is that Radio does not work at all - The phone cannot connect to any mobile network. This is not an issue for the single SIM model where Radio works fine.
Click to expand...
Click to collapse
For F8132, mobile network worked after turning the Airplane mode on and off, but need to do this every time the phone reboot. Hope this will be fixed in the future.
In the end I used this "MultiSIM Toggle" App for dual SIM functionality.
https://forum.xda-developers.com/android/apps-games/app-multisim-toggle-t2830647
Works!
Editing the build.prop file manually did not work for me.
---------- Post added at 11:49 AM ---------- Previous post was at 11:19 AM ----------
For GCAM try this version:
https://f.celsoazevedo.com/file/cfiles/gcm1/6.1_GCam_MJL_v3.5_Miniflex.apk
Works out of the box and has night sight and other advanced feature.
I've been using this ROM for for 3 days - No restarts or crashes, everything is running smoothly.
I think we have ourselves a daily driver here! A first for this friggin phone.
Another bit of advice - I rooted this ROM with Magisk - As I allways do - For reasons unknown to me this stops NFC from working. As I learned Lineage has it's own SU manager which can be enabled in the Developer Options.
To allow root management for Apps you need to flash this file with TWRP:
https://mirrorbits.lineageos.org/su/20190709/addonsu-15.1-arm64-signed.zip
One issue with this ROM is that USB OTG is unfortunately not working.
Serveral "OTG Checker" Apps report that USB OTG is supported by the OS but when I plug in an USB device (which is working on another phone) absolutely nothing happens. I can't see anything in the catlog either.
Does anybody have any ideas / advice on how to get USB OTG working or where I can start to debug this?
Here list several issues after 1 day use with me.
1. Sound not function after restart.
2. I cannot make a call include WhatsApp call.
Hi all,
I tried to find anything in regards of using lineageos with the Gigaset GS290, but unfortunately I was not able to find any note.
Do anybody knows if there is a possibility to install lineageOS on that device?
btw. I used also the google search but there was also no result.
Many thanks in advance for any hint.
BR
Martin
McT73 said:
Hi all,
I tried to find anything in regards of using lineageos with the Gigaset GS290, but unfortunately I was not able to find any note.
Do anybody knows if there is a possibility to install lineageOS on that device?
btw. I used also the google search but there was also no result.
Many thanks in advance for any hint.
BR
Martin
Click to expand...
Click to collapse
Nothing.
McT73 said:
Hi all,
I tried to find anything in regards of using lineageos with the Gigaset GS290, but unfortunately I was not able to find any note.
Do anybody knows if there is a possibility to install lineageOS on that device?
btw. I used also the google search but there was also no result.
Many thanks in advance for any hint.
BR
Martin
Click to expand...
Click to collapse
https://mastodon.social/@gael/104914516447228584
/e/OS has been ported to the GS290 by /e/ and Gigaset, they just announced it:
/e/ announces the /e/-GS290 as the latest device available with privacy friendly /e/OS pre-installed - e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data
/e/ announces the /e/-GS290 as the latest device available with privacy friendly /e/OS pre-installed December 17th 2020 - /e/OS, the privacy by design operating system is pleased to announce that the best-selling GS290 by Gigaset, the major European electronics company that produces smartphones...
e.foundation
They also sell it as /e/-GS290, already flashed: https://esolutions.shop/shop/e-os-gs290/
https://build.lolinet.com/file/lineage/GS290/
I decided to add some info:
- It automagically installs the latest Firmware.
- This has working VoLTE and stuff.
- This is an clean device tree (the /e/ one is hacked together based on Volla's Ubuntu Touch device tree)
- This has been developed by the a bit famous Erfan Abdi (erfanoabdi).
Deleted
nift4 said:
https://build.lolinet.com/file/lineage/GS290/
I decided to add some info:
- It automagically installs the latest Firmware.
- This has working VoLTE and stuff.
- This is an clean device tree (the /e/ one is hacked together based on Volla's Ubuntu Touch device tree)
- This has been developed by the a bit famous Erfan Abdi (erfanoabdi).
Click to expand...
Click to collapse
@nift4, I'm very impressed with your ROM lineage-17.1-20210318-EXPERIMENTAL-GS290. At first glance, it runs like clockwork. I can't tell you the details yet. Please continue. I would be happy to donate a coffee or more...
iodemos said:
@nift4, I'm very impressed with your ROM lineage-17.1-20210318-EXPERIMENTAL-GS290. At first glance, it runs like clockwork. I can't tell you the details yet. Please continue. I would be happy to donate a coffee or more...
Click to expand...
Click to collapse
Actually, it's not by me, but by @erfanoabdi. I wrote that in the post tho.
@erfanoabdi
I flashed the latest 17.1 rom but without flashing the firmware (mine was newer, had the february 2021 update installed before switching to your rom). Now the compass does not work, would it work if I would downgrade the firmware to what is included in the zip?
Second problem:
Recovery reboots when inserting an USB cable and connecting it to a linux pc. Had to flash though /e/ recovery then switch to the lineage recovery and refrain from inserting the USB cable.
Any ideas?
My Gs290 works now with the latest 18.1 rom. really happy this is made possible! thanks sir. Erfanoabdi ! i'll buy you a coffee too!
i did notice outgoing calls are not possible no sound and hang up after 8 seconds , receiver has no sound neither.
incomming calls work fine . putting phone on speaker does not work , still on earspeaker.
i did mannage to ring a person on 3G but no ringing and no sound afterwards.
strangely a helpdeskline of a company (fixed line ) did work
don't know if i would need to flash to 17.1 rom to have calling fully possible???
areshinakya said:
@erfanoabdi
I flashed the latest 17.1 rom but without flashing the firmware (mine was newer, had the february 2021 update installed before switching to your rom). Now the compass does not work, would it work if I would downgrade the firmware to what is included in the zip?
Second problem:
Recovery reboots when inserting an USB cable and connecting it to a linux pc. Had to flash though /e/ recovery then switch to the lineage recovery and refrain from inserting the USB cable.
Any ideas?
Click to expand...
Click to collapse
I did need twrp gs290 recovery for succesful completion , other wise it looped in to "smartphone in orange state. and when connecting the smartphone in fastboot to the pc it would reboot in orange state....
also need the right driver for the gigaset GS920 chip https://www.getdroidtips.com/install-mediatek-mt65xx-usb-vcom-drivers/
(don't know if it's trustworthy) and update it with driver booster 8 (easy )
(In win10 you need to restart in advanced startupsettings and push "7" disable drive signing enforcement before doing so)
Or update "android device " in device manager with the driver.
areshinakya said:
@erfanoabdi
I flashed the latest 17.1 rom but without flashing the firmware (mine was newer, had the february 2021 update installed before switching to your rom). Now the compass does not work, would it work if I would downgrade the firmware to what is included in the zip?
Second problem:
Recovery reboots when inserting an USB cable and connecting it to a linux pc. Had to flash though /e/ recovery then switch to the lineage recovery and refrain from inserting the USB cable.
Any ideas?
Click to expand...
Click to collapse
1- yep that should work
2- known bug and will be fixed sooner or later
FlashedMeself said:
My Gs290 works now with the latest 18.1 rom. really happy this is made possible! thanks sir. Erfanoabdi ! i'll buy you a coffee too!
i did notice outgoing calls are not possible no sound and hang up after 8 seconds , receiver has no sound neither.
incomming calls work fine . putting phone on speaker does not work , still on earspeaker.
i did mannage to ring a person on 3G but no ringing and no sound afterwards.
strangely a helpdeskline of a company (fixed line ) did work
don't know if i would need to flash to 17.1 rom to have calling fully possible???
Click to expand...
Click to collapse
Does this still happen?
UPDATED GUIDE FOR ANDROID 11[R]
Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI [ANDROID 11]
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla] | XDA Developers Forums (xda-developers.com)
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in, otherwise it is Vanilla Android.
CHONDOE FLASHER
ChonDoe_Flasher.zip | by androidhowto for Utilities (androidfilehost.com)
Twerp Recovery [ANDROID 11]
Twrp+vbmeta_A11.tar | by androidhowto for Utilities (androidfilehost.com)
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
EDIT
BEFORE YOU PROCEED
1. IT IS MANDATORY TO FOR THE DEVICE TO BE IN ONE UI 3.0, ANDROID 11. IF NOT DOWNLOAD ONE UI 3 FROM Model : SM-A515F - Galaxy A51 — Samfrew.com THEN PROCEED.
2. NOT ALL GSIs WILL WORK TO KEEP A LIGHT HEART ABOUT A GSI NOT WORKING.
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer. [IF IT WAZ THAT EASY]
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx. Go to options and disable auto reboot.
11. Now click on the AP button and select the twerp you downloaded. do not remove the usb cable and after it is installed press vol down and power, as the screen goes black hold with cable connected press and hold vol up and power until twerp boots up.
12. If you miss it repeat the process again but don’t let it boot to One Ui.
13. twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
14. Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
15. Now in your computer extract the Havoc os image and rename it as “system.img”.
16. Place the chondoe flasher zip and system.img in internal storage and then flash chondoe flasher zip
17. Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/
Does fingerprint works?
adrgmez said:
Does fingerprint works?
Click to expand...
Click to collapse
nah fingerprint is not supported in this one.
GrandmaGotGuns said:
nah fingerprint is not supported in this one.
Click to expand...
Click to collapse
The fingerprint will work when it works in the phh gsi, they are all based basically there, it is best to test directly in phh aosp or send logs to the dev
I have a problem with brightness. It's lower than on stock. Extended brightness range doesn't help that much
AlexHHHx said:
I have a problem with brightness. It's lower than on stock. Extended brightness range doesn't help that much
Click to expand...
Click to collapse
You can try another gsi such as aosp11
[email protected] - Browse Files at SourceForge.net
aosp with gapps also works great.
I currently have havoc Android 10 installed, I would like to update to Android 11, I am very happy with the battery life, as I read this version it has the same small bugs, but the battery lasts the same as the previous version?
darkshinigami said:
I currently have havoc Android 10 installed, I would like to update to Android 11, I am very happy with the battery life, as I read this version it has the same small bugs, but the battery lasts the same as the previous version?
Click to expand...
Click to collapse
Yeah havoc 10 is very good for battery life..
There is really not much difference between battery life as vendor for Android 11 Is optimized but u might see a small drop in battery. Make sure you install one up 3.0 first... you may test battery life with the stock one ui 3 11.0.. what really matters is the vendor, system image rarely makes difference ( unless its loaded with bloat).
So in conclusion vendor for Android 11 is pretty much optimized as that of Android 10 with minor difference and should offer almost same performance for different GSIs..
Thanks for answering bro, the truth with ui 3.0 the battery drained very quickly and the performance was terrible, but it was sure because it was updated via ota and it was not a clean installation, I will give it the opportunity, I am tempted by the one that goes better even if it loses a bit of battery life, thanks
GrandmaGotGuns said:
Yeah havoc 10 is very good for battery life..
There is really not much difference between battery life as vendor for Android 11 Is optimized but u might see a small drop in battery. Make sure you install one up 3.0 first... you may test battery life with the stock one ui 3 11.0.. what really matters is the vendor, system image rarely makes difference ( unless its loaded with bloat).
So in conclusion vendor for Android 11 is pretty much optimized as that of Android 10 with minor difference and should offer almost same performance for different GSIs..
Click to expand...
Click to collapse
darkshinigami said:
Thanks for answering bro, the truth with ui 3.0 the battery drained very quickly and the performance was terrible, but it was sure because it was updated via ota and it was not a clean installation, I will give it the opportunity, I am tempted by the one that goes better even if it loses a bit of battery life, thanks
Click to expand...
Click to collapse
I don't think clean install will really help.. didn't help me and I did mention unless , one ui is bloat city
But it's worth a shot...
darkshinigami said:
Atualmente tenho o havoc Android 10 instalado, gostaria de atualizar para o Android 11, estou muito feliz com a duração da bateria, pois li esta versão ela tem os mesmos pequenos bugs, mas a bateria dura o mesmo que a versão anterior?
Click to expand...
Click to collapse
The fingerprint run perfectly?
Thanks
hacker812c said:
The fingerprint run perfectly?
Thanks
Click to expand...
Click to collapse
Sorry dude.. it doesn't.
GrandmaGotGuns said:
Sorry dude.. it doesn't.
Click to expand...
Click to collapse
Great job i m using havoc in j7
Stsrting use a51 today
bro I already managed to install havoc 4.1 and I love the smoothness, and the battery is on the right track, it does not seem to be better than havoc 3, but better than the stock for sure, but I have a big problem and it is that the option of two taps to wake does not work, do you know if it is a matter of havoc or it is not yet implemented in the gsi code of android 11
darkshinigami said:
bro I already managed to install havoc 4.1 and I love the smoothness, and the battery is on the right track, it does not seem to be better than havoc 3, butbetter than the stock for sure, but I have a big problem and it is that the option of two taps to wake does not work, do you know if it is a matter of havoc or it is not yet implemented in the gsi code of android 11
Click to expand...
Click to collapse
Dude first of all if it has Android 11 in its name then it definitely has the Android 11 code. As far as these roms go.. they start from a very stock Android 11 from Google and they modify up to their requirements.. mostly they just cut and paste the code which they already have from previous versions to the same libraries as the new version without making any changes as Android is not drastically updating its small improvements and more polish.. more over the features like lock screen visualizer or double tap are installed as apk inside the rom. So there can be a lot of reasons something might not work when changing the Android version without optimization. Definitely it's a problem from their side or it can be incompatibility with the vendor of the device.. not all features will work as you expect them to unless it is specifically optimized for the particular device. And since we are dealing with GSIs here.. they are generic so the above scenario of optimization is really over the top as it is made for each and every device. They mostly focus on important features and leave the rest on the vendors.. if it works then yay if not then eh...
GrandmaGotGuns said:
Dude first of all if it has Android 11 in its name then it definitely has the Android 11 code. As far as these roms go.. they start from a very stock Android 11 from Google and they modify up to their requirements.. mostly they just cut and paste the code which they already have from previous versions to the same libraries as the new version without making any changes as Android is not drastically updating its small improvements and more polish.. more over the features like lock screen visualizer or double tap are installed as apk inside the rom. So there can be a lot of reasons something might not work when changing the Android version without optimization. Definitely it's a problem from their side or it can be incompatibility with the vendor of the device.. not all features will work as you expect them to unless it is specifically optimized for the particular device. And since we are dealing with GSIs here.. they are generic so the above scenario of optimization is really over the top as it is made for each and every device. They mostly focus on important features and leave the rest on the vendors.. if it works then yay if not then eh...
Click to expand...
Click to collapse
Ah then my guess was not bad, but thanks for clarifying it, for now I will play it with the option to activate the ambient screen when lifting, and sometimes I forget that I am trying a generic rom, rather it surprises me that it is not have so many things broken, rather it is to be appreciated that there are people who take their time to compile and share these roms, it will be to wait maybe later they will implement it
GrandmaGotGuns said:
Sorry dude.. it doesn't.
Click to expand...
Click to collapse
The problem is aosp phh or only havoc?
Goodnight from brazil
I send new thread for phh developer for correction fingerprint a51 natively
Eu send new thread for phh developer for correction fingerprint a51 natively
GrandmaGotGuns said:
nah fingerprint is not supported in this one.
Click to expand...
Click to collapse
What is the reason for using chondoe and not twrp to flash the rom directly?
Thanks 30+