I build the AOSP successfully but in my case the microphone is buggy ... everything else is working. Is there Anyone who build it with a working mic? I've build r30 and r32 with the same result :/
I have not yet. Ordered my XZ1c yesterday. Should be here Monday. Hoping for more developer colaberation. Thank You for working on this!
Because of Treble it should be possible to build Lineage OS without interfering with the fingerprint sensor and T-Mobile VoLTE functionality, no?
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
N1ghtr08d said:
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
Click to expand...
Click to collapse
It's still going to be bad. Until we get a proper DRM backup method all custom ROMs will take awful photos.
Issues Flashing Build
Hi there -
If you don't mind me asking, did you run into any issues when flashing the build? I was able to build android-8.0.0_r30 successfully. After flashing android-8.0.0_r30, my phone boots to a screen covered in distorted colors. There is a small message, but most of it is cut off. From what I can tell, it seems that something is corrupt, or so I believe the partial message said.
Did you run into any issues while flashing?
Could you please offer some insight into your process?
Thank you for your time,
Dominic
[Edit]
I am getting the same screen of distorted color after the Sony screen when flashing android-8.1.0_r7.
Before flashing again this time, I went to another machine and used Sony's flashing tool, Emma, to flash a stock Sony ROM back to the device. This allows me to boot to what I assume is Sony's most current build available. The phone boots no problem this way. I decided to try another flash.
My specific steps for flashing post build:
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_yoshino.img
[Edit]
I am able to successfully use Sony's Flash Tool, Emma, on a separate system to get the phone booting to the stock ROM. Emma shows the following under Software:
Application Software:
1307-7511 47.1.A.8.49
[(Delayed) Edit]
I rebuilt AOSP from source and was able to successfully boot into the OS after flashing the partitions.
Maybe a corrupt image was generated during the build process.
Either way, I am updating this in case anyone else comes across it. Downloading the source and rebuilding it resolved the issue.
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
irewer said:
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
Click to expand...
Click to collapse
Yes i do..
I unlocked bootloader and rooted
dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
sixtheninth said:
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
Click to expand...
Click to collapse
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
dmilz said:
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
Click to expand...
Click to collapse
Yeah, I am very interested. I tried RR, LineageOS, Viper for other montanas, all crashed after boot back into bootloader. Also I'd be interested getting Oreo based ROMs. So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
sixtheninth said:
So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
Click to expand...
Click to collapse
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
sixtheninth said:
Also I'd be interested getting Oreo based ROMs.
Click to expand...
Click to collapse
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
irewer said:
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
Click to expand...
Click to collapse
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
Click to expand...
Click to collapse
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
Click to expand...
Click to collapse
Hope this helps to unbrick
http://motog5szuirom.blogspot.com/2018/01/zui-31-for-moto-g5s-stock-rom.html
dmilz said:
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
Click to expand...
Click to collapse
I agree, a since it is a slightly different phone a independent section can be great. Now, I am not a developer, so things like porting ROMs is not in my skillset, but I understand that selfie cam and nfc will not work on any custom ROM even if ported simply due to driver issue. I have rooted my phone previously, so I was past unlocking. Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode, which was strange as it had stock ROM updated by reseller into a global version. Then I tried to flash various custom ROMs without any luck. Pretty much tried any Montana ROM I could find, but as I said, I don't know how to port so I got stuck in recovery loop. Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7 without me realising this. I found out nfc and selfie camera not working, so I wanted to downgrade to stock chinese firmware and just install gapps manually. After I fastboot flashed the nougat firmware - my phone hard bricked and won't even respond it seems dead. Thus your link will not help. Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Thank you anyway and if by chance you stumble upon some cool compatible ROM or to be honest a ROM that works really good - I don't really need NFC, but fingerprint scanner, turbo charger, selfie camera and reasonable battery management (some ROMs apparently drain it too quickly) would surely be features to keep. Also, if you have at hand a guide on how to port these roms which I can learn, I'd be very grateful.
Thank you
Six
sixtheninth said:
Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode ...
Click to expand...
Click to collapse
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
sixtheninth said:
... Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7* without me realising this ... I wanted to downgrade to stock chinese firmware ... my phone hard bricked and won't even respond it seems dead ...
Click to expand...
Click to collapse
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
sixtheninth said:
Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Click to expand...
Click to collapse
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
irewer said:
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
Click to expand...
Click to collapse
Well as irony had it, I did the operation literally seconds before I have read your warning. I was desperate of being stuck in either chinese rom or recovery loop. Anyway, I am amidst of transferring mmcblk0.img for XT1795 to my SD drive via Rufus. Problem is that it won't let me to choose GPT only MBR, so I hope that can still work. Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
sixtheninth said:
Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
Click to expand...
Click to collapse
The version of installed bootloader you can check in Fastboot Flash Mode (bootloader as actually, Power + Volume Down buttons pressing and so on).
The version of non-installed firmware you can find into special '.info' file, for example: file 'MONTANA_RETCN_NZS26.68-108_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC_montana_retcn.info' inside ZUI-based MONTANA_RETCN_NZS26.68-108 ROM has this line:
Code:
MBM Version: BC.06
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (
sixtheninth said:
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black
Click to expand...
Click to collapse
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
[/COLOR]
irewer said:
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1 . Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card. Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black. I downloaded your image file for 1799-2, but ended with the very same result. I have not found XT1794 Android 8.1.0-based mmcblk0.img, yet. Would you know anything about it?
1799-2
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
nikolaiderho said:
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
Click to expand...
Click to collapse
But did you recover it from hard brick by using mmcblk0.img based on Oreo?
Have you done with your RR port for xt1799 yet?
I have purchased the xt1799 Green Pomelo,unlocked bootloader,and installed the twrp. I tried to flash many 7.1 Roms that were intended for g5s and always failed. please notify me if you are still working on the port.
I've been having loads of issues with installing Treble ROMs. Currently I'm on the PRA-LX1's most recent update with EMUI 8, (C432) and have only recently found out that Askuccio's TWRP is around. Previously I've been trying and trying with TWRPs like Haky86's which couldn't have even worked because it's built for EMUI 5, I've tried Pretoriano's for the P10 lite, as well as some other random one which is Chinese. Pretoriano's is always unable to mount my /storage/ or /system/ and therefore I can't wipe or flash anything properly, and the chinese one just placed me in a bootloop after flashing the Treble RR ROM.
I now have the Askuccio TWRP and I need to know before I try again - will I get a bootloop, or get in a mess all over again? I can't back anything up beforehand because of encryption and inability to root before switching to a custom ROM. The last times I've tried I've had to keep booting and messing around until eRecovery manages to reproduce itself from seemingly nothing and then redownloads my system firmware again.
Has anyone had proper success? Do you recommend any ROMs to use? I'd prefer RR, Lineage or Omni but at this point anything is fine. Thanks
I'm in the same boat as you. I have had many phones and rooted them all, but somehow the help on this forum lacks detail and consistency. I also have the TWRP installed but can't get any further down the line - where is the root? Can't install custom roms, can't get adaptive SD, just got unlocked bootloader and FWP!
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
desertfoxtim said:
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
Click to expand...
Click to collapse
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
lolo9393 said:
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
Click to expand...
Click to collapse
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
WinBug2 said:
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
Click to expand...
Click to collapse
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
lolo9393 said:
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
Click to expand...
Click to collapse
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
WinBug2 said:
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
Click to expand...
Click to collapse
you need to flash the zip from here through twrp since the fastboot commands dont support zips
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
ANTROBAROTICS said:
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
Click to expand...
Click to collapse
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
gabtit7 said:
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
Click to expand...
Click to collapse
But custom rom can be installed without rooting. So then also safety net will not work ?
Google realeased a new update that checks if the bootloader is unlocked
and the only way to lock it after flashing ROMs is to do a complete format and reinstall the original ROM, it replaces twrp or anything else with the original ROM (miui in our case)
So dont install roms
Okay. Thank you. I just wanted a reason not to install. Now is the end of custom rom I think majority will now no more root or install custom rom because of safety net. Copyright, Security & Privacy are now priority in today's world.
Some other members just found the solution but it supports only Android 10 & 11
[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED
Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...
xiaomi.eu
Hi!
Recently updated my Moto G9 Plus to A11, but is laggy and buggy as hell in matter of emulation, when A10 doesn't have this problems. So I intented to downgrade to A10 but at the flashing moment (fastboot with stock rom A10) fails at some point (vbmeta). It boots anyway, but breaks NFC module, so can't use it until upgrade to A11 again.
Cause of this, tried some custom roms like Lineage that I found in Telegram room. Didn't realize that i've installed an A12 rom, that I do not knew how to add Gapps. So, when tried the A11 one, the recovery doesn't allow me to install it because of the Anti-RollBack function. Then I give up and tried to go back to A10 stock, and had a bootloop as a result. Then flashing A11 solve the problem, so I have to stay in that f***ing OS...
I'm kind of new in this, besides i've done some things like this before, but I do not have any clue on how to procede... Really want to switch to A10 or A11 custom like Lineage, but don't know how... Any help you can give me?
PD: Sorry, I'm Argentinian, gave the best of me to make this understable