Database Develop

Moto g5s xt-1799-2 rr

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.

Moto E5 XT1920-15 (PETTYL) unlock bootloader)root/flashing GSIs

Deleted

bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:

Deleted

bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.

Deleted

bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.

Deleted

Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing

did the op get it sorted

Deleted

bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work

Deleted

plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16

Deleted

I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash

Deleted

bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!

Deleted

bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs

bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.

GSIs on A60/M40

Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this - the command to use here is "setprop persist.sys.phh.samsung_backlight 2"), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.

As a m40 user it sounds me great and left hope for my device.. looking foreword to it

dear AndyYan, could you provide links(to twrp and GSI themselves) or something?
sorry. no need of providing. I misunderstood

Great!
Great Work buddy. Hope you make progress and soon have a smooth GSI on your device :good:
AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well. .....
.....With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse

Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB

MediaNik said:
Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB
Click to expand...
Click to collapse
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.

AndyYan said:
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.
Click to expand...
Click to collapse
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"

MediaNik said:
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"
Click to expand...
Click to collapse
Then probably dm-verity kicking in (weird, how come when we've unlocked BL already).
I installed Magisk beforehand (patch AP), try it yourself.

Can you make please more detailed guide how to flash it
Because when I try, it gives me error

AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse
can you please tell me how to do that?

deadinside322 said:
Can you make please more detailed guide how to flash it
Because when I try, it gives me error
Click to expand...
Click to collapse
tomznottomo said:
can you please tell me how to do that?
Click to expand...
Click to collapse
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).

AndyYan said:
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).
Click to expand...
Click to collapse
im noob bro can you give me your facebook or instagram please :<

@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
tomznottomo said:
im noob bro can you give me your facebook or instagram please :<
Click to expand...
Click to collapse
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.

AndyYan said:
@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.
Click to expand...
Click to collapse
Hello, I also tried to port TWRP three times already, it didn’t work out in any way.
The problem was that the firmware in Odin was infinitely loaded, and some simply did not want to boot.

Android 10 has released for both A60 (A6060ZCU1BTC9) and M40. I've switched to using it as base for GSIs, and it fixes the call speaker problem; other mentioned issues remain. The flashing process stays the same as well.

Changing firmware galaxy m40 to galaxy a60 open china
Hi, im using galaxy m40, if i flash the galaxy a60 firmware, my phone work or brick, has any one try that?

have anyone tried flasing android 12 gsi to m40?

[SHARE] Descendant os

Descendant os
I did not create this rom and I am not responsible for any result caused by flashing this rom.
A gsi custom os for any android phone, developers claims.
A very cool os, seems even better then oxyjen os.
Brave ones who want to try it on, download is in link below:
All relevant info is inside the youtube video, roms gapps, twrp, every thing needed to flash.
All that is left is to tell you again the usable disclaimer- I did not create this rom and I am not responsible for any result caused by flashing this rom.
If you do exactly what the guide tells you to do there should be no problem, all the info is the youtube video.
Enjoy.
And don't come crying about broken links, not my problem.
Now let's start the flashing!

Nice customize options

lionel8595 said:
Nice customize options
Click to expand...
Click to collapse
No twrp on OnePlus 7t Pro so can't install

jaythenut said:
No twrp on OnePlus 7t Pro so can't install
Click to expand...
Click to collapse
Wouldn't the adb enabled custom recovery thing work (by sideloading)?

Kevorex1 said:
Wouldn't the adb enabled custom recovery thing work (by sideloading)?
Click to expand...
Click to collapse
I think so too

Hi peeps has anyone installed this through adb? And if so can you share the steps? We don't have a working TWRP for OnePlus 7T Pro why make a thread for a ROM that uses this process?

Kevorex1 said:
Wouldn't the adb enabled custom recovery thing work (by sideloading)?
Click to expand...
Click to collapse
lionel8595 said:
I think so too
Click to expand...
Click to collapse
No, it wont work.

lionel8595 said:
I think so too
Click to expand...
Click to collapse
Why would you post to try this if you have not installed on a oneplus 7t pro yet?

Becuse what's the point of a community if you're able to share good information in it. In any other case there are two specific answers :
First- information is valuable even if you are not going to use it.
Second- since I'm have no computer to be able to flash with at all, I have not been able to even root my device.
But as soon as I can get my hands on a computer to flash with I will let you know first, OK?
Now as I already commented above this is not of my creation and I already mentioned that I'm not taking any responsibility for your actions with the information provided, have fun!

I flashed it, it works however the fingerprint scanner doesn't and the front facing camera is a bit iffy. Does boot though.
You can flash it via fastboot as it is just a system.img file.

Development [GSI][12] Unofficial LineageOS 19 SM-X200

Instructions:
Flash LineageOS for tab a8 sm-x200
Format data from TWRP.
And wipe all partitions, then just reboot into fastboot and flash your system image
fastboot flash system system.img
(system being lineage or google gsi or whatever)
then once i have created the folder select the .xz or .gz or .img
also a fastboot -w after flashing for additional wiping wouldn't hurt
make sure you have a unlocked bootloader and have twrp installed.
Download links:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/lineage-19.1-20220814-UNOFFICIAL-arm64_bgS.img.xz/download
Credits to:
Vinpinto​

Working so far with no issues!

how do i enter fastboot ? if i chose option to boot into fastboot through twrp fastboot does not work...

updated drivers and all works now..

keksas3 said:
updated drivers and all works now..
Click to expand...
Click to collapse
Ah okay good glad you got it fixed!

here's the full guide https://forum.xda-developers.com/t/...oid-12-android-13-treble-flash-guide.4497299/

Vinpinto said:
here's the full guide https://forum.xda-developers.com/t/...oid-12-android-13-treble-flash-guide.4497299/
Click to expand...
Click to collapse
perfect

HI,
I've entered fastboot mode with twrp and then did a fastboot flash system system.img,
After flash i can't boot on android, it bootloops,
Someone have an idea ?
thanks in advance

Is video still broken?
That (and anxiety about bricking it) are the only thing (s) holding me back from trying all of this.
Thanks

Droid_JD said:
Is video still broken?
That (and anxiety about bricking it) are the only thing (s) holding me back from trying all of this.
Thanks
Click to expand...
Click to collapse
According to @Vinpinto this only affects android 13 ROMs and lineage 19 is on 12, so should be no issues. I'm going to give it a try this weekend.
Thanks @WackyHacky1 and @Vinpinto for sharing!!
Edit:
Can anyone who's had a successful flash comment on any performance improvements? I want to update assuming that changing apps, navigating ui etc. will become more responsive

thicc_pp said:
According to @Vinpinto this only affects android 13 ROMs and lineage 19 is on 12, so should be no issues. I'm going to give it a try this weekend.
Thanks @WackyHacky1 and @Vinpinto for sharing!!
Edit:
Can anyone who's had a successful flash comment on any performance improvements? I want to update assuming that changing apps, navigating ui etc. will become more responsive
Click to expand...
Click to collapse
I've only noticed improved performance with vanilla aosp GSI and google GSI android 12 and 13 images, lineageos it's a bit laggy.
I'm working on my own recipe for a Pixel-like rom, I'll share when I get any progress

Hi, is there a gapps package that is recommended?

jonpjingleheimler said:
Hi, is there a gapps package that is recommended?
Click to expand...
Click to collapse
opengapps is still pretty good

WackyHacky1 said:
opengapps is still pretty good
Click to expand...
Click to collapse
Agreed. Reckon I will wait patiently until they support android 12

Does anyone know if selinux and encryption work with this gsi?

Could someone tell if MAC randomization works?

it works
nisfta said:
Could someone tell if MAC randomization works?
Click to expand...
Click to collapse

isahzbxfviccq said:
Does anyone know if selinux and encryption work with this gsi?
Click to expand...
Click to collapse
it doesn't

Has anybody tried this on a X205? Does mobile connectivity still work?

Nosepull said:
Has anybody tried this on a X205? Does mobile connectivity still work?
Click to expand...
Click to collapse
Confirmed working on SM-X205. LineageOS is choppy/laggy as hell for me, so I went with phhusson AOSP with GApps. Running buttery smooth.