GSIs on A60/M40 - Samsung Galaxy M40 Guides, News, & Discussion

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?

Related

How do you update a Project Treble GSI image ?

Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
xzyk said:
Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
Click to expand...
Click to collapse
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Fredin_ said:
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Click to expand...
Click to collapse
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
xzyk said:
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
Click to expand...
Click to collapse
Good to hear that you updated successfully. I also love the theme engine in Omni rom but had to switch to stock for the camera

GSI Questions

sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do
Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie
Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen
ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done

[GUIDE] Install GSI on U.S. Snapdragon S9/S9+ [U/U1 Variants]

So...
The U.S. variants finally have root, this is a very exciting moment for S9/N9/S9+/N9+ users that always wanted to do more with your device. I wanted to create this thread separate from the root thread as I think GSIs are a whole different thing. It's actually pretty simple once you've read, understood and even tried the root method running Oreo Samsung Experience. The steps are very similar but you just swap out the system image.
So please, take the time to read the thread for the Extreme Syndicate root method here: https://forum.xda-developers.com/ga...pment/root-t4041815/post81608559#post81608559
I am going to quote some of the stuff in that thread directly as all of it still applies here.
Please take your time and make sure you follow the instructions carefully.
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
​
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
The Adventure!:
I will not get into any technical details here. Just know that this method has taken me ~1 year from start to finish. I also went through a number of devices during this time (at least 7 devices), even sold my original N9 then somehow ended up with another one before this root method was found. Some of us devs might be a bit burnt out so don't get upset if we are not in here all day every day answering everyones questions. We hope users will help eachother, that is what XDA is all about! Also, if you want more real time conversation/support then please join our Telegram group (link posted below) as this is easier for us to moderate and allows discussion to be had in real time. I don't always check XDA messages or PM's as it can be a lot and very tiresome so your best bet is Telegram!
Also, donations/money is not expected or required but if you feel obliged to share what you can then that would be greatly appreciated! Donations keep me on the grind and sometimes can even help me in acquiring other devices to work on. I had issues with Paypal a while back (SamPWND days) and do not have a Paypal account. I do however have a Venmo and Transferwise accounts that work in most situations.
Venmo - http://www.venmo.com/Thomas-Huntington-10
Transferwise - PM @elliwigy for info to donate using Transferwise.
Now Let's get into the files/method!
Click to expand...
Click to collapse
INSTRUCTIONS:
1. Download the following:
- Root files from Extreme Syndicate that belong to your device
- The GSI you want to download (for these devices you need arm64 a-only. With gapps included should be your priority)
- Sh remover zip uploaded here.
- Alternative: ODM nosu zip
2. In odin folder flash the combo firmware
3. Once combo is booted up run the root bat. When done phone will reboot to download.
4. In odin flash the bootswap.tar.md5 file. What this does is swaps the boot and recovery images which allows system to be mounted rw.
5. Now when done flashing you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
6. Now put your phone in airplane mode. This must be done whenever using Flashfire. Copy the system.img (your GSI img) , vendor.img, Sh remover.zip and ODM zip files to your phone.
- NOTE: Flashfire doesn't let you chose the partition on where it's going to flash any image. It decides on where to flash based on the name of the image. So if your gsi is named GSIName-arm64-a-nosu.img then flashfire will have no idea where to flash it. I would rename the img to something like system-GSIName-arm64-a-nosu.img.... or just system.img lol
- NOTE 2: I uploaded a ODM NOROOT.zip. Reason being that some gsi come preloaded with supersu. In theory, using the regular ODM_ROOT.zip from the Extreme Syndicate method should work fine even if the GSI comes prerooted, I just didn't test it with that lol. You should definitely use the root variant if the GSI doesn't say it comes rooted.
7. In Flashfire, choose zip and select the odm zip (root or unrooted, your choice. Read note above). Make sure you select "Mount /system read/write" when the Options pop up. This is necessary or else it will not boot, always chose this on everything. Then choose firmware and choose the system.img and the vendor.img. Then choose data wipe and wipe user and system data (the default choices). Make sure inject super su is NOT enabled. Disable it. Do not let flashfire inject root!!. Then choose zip again and select the Sh remover.zip (select to mount system read/write)
- NOTE: I added the Sh remover zip because some GSI (particularly Android 9 GSI) have a track record of having some problems booting up in Samsung devices. This zip should remove the system/bin/rw_system.sh file. There's no bad side of not having this file on GSI's that don't share this problem, so I'm making it a mandatory step to avoid as much problems as possible
8.. Now click flash. When finished you will have to hold buttons to reboot to recovery until you see boot animation. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
9. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
10. Biometrics do not work so don’t try to setup fingerprint or face recognition.
And that's it, you should have your GSI up and running.
Let's keep all the GSI talk on this thread please. I will do my best to keep this thread updated with fixes, compatibility and news. For now, take a look at the confirmed working GSI:
Confirmed working:
- PHH Android 9 GSI
- HavocOS 2.9
- PHH Android 10 GSI (Added bug: WiFi is broken, working on a fix)
Confirmed not working:
- Pixel Experience Android 9
- OxygenOS (Erfan's GSI) (I wouldn't recommend GSI from other OEMs anyway)
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@jrkruse - For all the help and support for S9 variants
@everyone else I am forgetting!
ENJOY!
Join is in Telegram where we can discuss GSI and help with problems more quickly
Link: https://t.me/joinchat/HYvgAlUgyqKq9__Y5yg1uA
Reserved 2
Nice guide! I'm sure you'll have plenty of input from others that have tested various gsi.
klabit87 said:
Nice guide! I'm sure you'll have plenty of input from others that have tested various gsi.
Click to expand...
Click to collapse
That's the plan. To hopefully fill this thread with GSIs that work, the ones that don't and any additional fixes to get some to boot.
Great news. Seems HavocOS 2.9 (Android 9) boots pretty well. This is great! Udating post to add link.
EDIT: Also added PHH Android 10. It boots!
just so everyone knows, so far the bugs with the PHH 9 GSI is that no mobile data,messaging and calling will work.
Root on "U" variants! Wahooooo!! Ooo! Ooo!
Anyway, I've been doing this since the galaxy s3 and jailbreaking iPhone since the 3gs... but it's not a every day thing for me and I would assume the same for many others. I do it full tilt "all of my personal time" for a few months get stuff working, backup and then go about my business. I have been forced to switch from my beloved note 4 to this corporate controlled piece or Samsung stuff for $1K and finally someone hacked it! Well done and thank you soooooo very much!!
Anyway, this GSI thing is entirely new to me. I dont know what it is, how it works, what is means etc... it seems to be a relatively new thing. Maybe within the past year or so?
So what I would recomend and ask for is a brief history and explanation of what it is and what is does, where it came from etc... does it make my touchwiz phone like stock android? What aspect of the rom does it replace? System.img I assume but why is it needed? What is the reason it's not needed for Android 8 but is needed for 9 and up?
Of course all of us can google it and and wade through all the documentation on it which I will do and eventually figure it out but I noticed on telegram there are a ton of questions about it since, well, almost everyone has Android 9 on their devices. So it might help in reducing the repetitive questions if there was a quick but detailed write up on GSI from some of you ultra smart type peeps that know about it. My guess is most people won't spend the necessary time required to research GSI which can take days, weeks, months... some of us have kids and demanding jobs and have to cook, clean, repair, work, doctors, school, etc etc.. while others such as myself have opted to go the route of a professional career with no kids and can spend the time researching... Just a suggestion...
Again thank you to all the super smart type fellas and ladies aka DEVs that continue to fight the good fight and make this entire thing possible for the rest of us that are less capable in this area of expertise . You guys rock! Like kick serious @$$ kinda rock!
Zaileion said:
Root on "U" variants! Wahooooo!! Ooo! Ooo!
Anyway, I've been doing this since the galaxy s3 and jailbreaking iPhone since the 3gs... but it's not a every day thing for me and I would assume the same for many others. I do it full tilt "all of my personal time" for a few months get stuff working, backup and then go about my business. I have been forced to switch from my beloved note 4 to this corporate controlled piece or Samsung stuff for $1K and finally someone hacked it! Well done and thank you soooooo very much!!
Anyway, this GSI thing is entirely new to me. I dont know what it is, how it works, what is means etc... it seems to be a relatively new thing. Maybe within the past year or so?
So what I would recomend and ask for is a brief history and explanation of what it is and what is does, where it came from etc... does it make my touchwiz phone like stock android? What aspect of the rom does it replace? System.img I assume but why is it needed? What is the reason it's not needed for Android 8 but is needed for 9 and up?
Of course all of us can google it and and wade through all the documentation on it which I will do and eventually figure it out but I noticed on telegram there are a ton of questions about it since, well, almost everyone has Android 9 on their devices. So it might help in reducing the repetitive questions if there was a quick but detailed write up on GSI from some of you ultra smart type peeps that know about it. My guess is most people won't spend the necessary time required to research GSI which can take days, weeks, months... some of us have kids and demanding jobs and have to cook, clean, repair, work, doctors, school, etc etc.. while others such as myself have opted to go the route of a professional career with no kids and can spend the time researching... Just a suggestion...
Again thank you to all the super smart type fellas and ladies aka DEVs that continue to fight the good fight and make this entire thing possible for the rest of us that are less capable in this area of expertise . You guys rock! Like kick serious @$$ kinda rock!
Click to expand...
Click to collapse
I can sort of give a very brief explanation of sort of how I see it.
And I say sort of because I really don't consider myself an expert, just read a few things here and there
I'm going to go over what "Project Treble" really is, I don't know if you've heard this term thrown around when talking about GSI.
Google made "Project Treble" much more simple with the intention that OEMs would hurry up and release updates faster lol
What happens now is that there is a new partition of where the Android OS takes its resources, and that's the "/vendor" partition. Everything from the drivers to the bluetooth, wifi, sensors, camera, etc.... is found here
Every device that are "Treble" enabled means that they have this "/vendor" partition
So why the S9? Why not the S8, S7, etc...?
Google made it mandatory for all the devices that released with Android Oreo to be "Treble Enabled" out of the box and made it up to the manufacturer to make old devices Treble compatible
But let's not kid ourselves, we all knew that Samsung wouldn't go back on the S8, S7, Note 8, etc... and treblelize them, that's not their style. Though most OEM's didn't do that anyway, there are a very few that actually did.
From the S9 and onwards, all these devices have Project Treble.
So, now we get to what the GSI actually are.
Think of it as ROMs, pretty straight forward.
Now the AndroidOS takes all its hardware resources from "/vendor", these GSI can work on almost all devices out there. Sure there may still exists some compatibility issues here and there but it's much easier to fix them.
So in theory, even if Samsung stops development on the S9 with Android 11, which of course we're all expecting, we can still flash Android 11 GSI when they start coming out because the S9 is Treble enabled
I hope this sort of gave you an idea of what the whole GSI and Project Treble situation is.
PHH Android 9 GSI - Calls no Volume Fix
Just to add onto that, I would like to say that If you are to flash PHH Android 9 GSI and HavocOS 2.9. It doesn't have the calling feature working from the get go. You would be able to make a call to a person, but you won't be able to hear them or they won't be able to hear you. This is an ongoing problem with that GSI. A possible work around for that would be found on
https://forum.xda-developers.com/as...-to/guide-call-fix-patch-gsi-testing-t3791660
Although, I haven't tried it. I am in the process to try and fix this. Will update once done. I cannot thank enough the author and everyone else involved in getting this root to work and along with that being able to flash custom Roms. This is amazing.
What about AOSP 9.0 and 10.0? Do those work?
Mogster2K said:
What about AOSP 9.0 and 10.0? Do those work?
Click to expand...
Click to collapse
I personally haven't tested any more, been busy. You are free to test them yourself and post links to which work. The one consistent bug we did find on Android 10 GSI is broken WiFi.
This works on the 965U, the locked ATT version? This does work on the 965U, I answered my own question.
EDIT: this does not trip knox, sorry for the question. I am RTFM now
Which vendor.img should we use if flashing PHH's GSI 9 or 10?
Mogster2K said:
Which vendor.img should we use if flashing PHH's GSI 9 or 10?
Click to expand...
Click to collapse
The latest Oreo one included in the Syndicate root method
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Mogster2K said:
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Click to expand...
Click to collapse
Huh... so now we know that a rooted GSI + the ODM_ROOT zip DOES cause a problem.
Yeah it sucks that on some GSI, the devs don't disclose it's got SU binaries already
What I would do is to look inside one (or both) of your SU apps and see if Flashfire has requested for SU access and it's got it negated for some reason.
If not, then I would just start over with the whole rooting process
Mogster2K said:
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Click to expand...
Click to collapse
Also clear the data for flashfire and force close it. I. The past we had to just grant all su permissions to get it to work flashfire has been real buggy on s8 and up sometimes
Safe strap possibly.
ShaDisNX255 said:
Huh... so now we know that a rooted GSI + the ODM_ROOT zip DOES cause a problem.
Yeah it sucks that on some GSI, the devs don't disclose it's got SU binaries already
What I would do is to look inside one (or both) of your SU apps and see if Flashfire has requested for SU access and it's got it negated for some reason.
If not, then I would just start over with the whole rooting process
Click to expand...
Click to collapse
Yeah, that's what I ended up doing. I managed to get the rooted Oreo image installed. Another note: PHH 10 v213 does not work with Spectrum Wireless (code CHA). I had no wifi and no mobile data and was stuck on the Google setup for a long time. Anyone here have Spectrum working on a GSI?
Just confirmed that Spectrum Wireless data doesn't work on PHH 9.0 v123 either.

LINEAGE OS 18.1/FOD WORKING /EXPERIMENTAL GUIDE

Hi guys, I've dug around the forums everywhere in the internet for very long time, and found out that there is actually custom roms which will work on our devices, with fingerprint working (the only reason why I'm still on stock rom)
So basically there is a cool guy called phhusson which does aosp treble in which he make fixes and patches for all kind of devices, and to our luck it looks like he already did a fix for our fingerprint half year ago
Here is an issue in which we can see that fingerprint specifically for our devices was already fixed
https://github.com/phhusson/treble_experimentations/issues/1370
Here is where you can get the original Phh aosp treble (his work)
GitHub - phhusson/treble_experimentations: Notes about tinkering with Android Project Treble
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Here is lineage os 18.1 based on his(Phh) aosp treble, which means fingerprint there should be working too
[UNOFFICIAL] LineageOS R Mod //LiR
L i R < Your warranty is now void! > We're not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in...
forum.xda-developers.com
P.S: I'm not developer and did not take any part in development of roms in link above, also I do not take any responsibility for your device, shall something happen to it, I'm just a guy trying to people who has been stuck on stock rom (only because of God **** Fingerprint and uncertainty if custom rom from device forum will be receiving any update)
Let me know if anyone tries the lineage os in the link above and if everything is working
It was a bit complicated but I got it working. I have not tested the fingerprint reader which is what you are concerned about but the ROM works without any obvious issues.
TWRP was flashed with Odin after I flashed stock firmware. I used ianmacd's TWRP to flash the GSI. I had to use faizauthar12's BUB5 kernel to get past the stuck LineageOS logo.
This thread for how to make the GSI usable for TWRP: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
Adding system.img to the zip file instead of creating a new zip file seemed to work better. Multidisabler fork with encryption appears to work.
Hope that helps anyone.
After instaling the .img i ended up with a samsung bootloop
and installing the img using the zip method literally did nothing so yeah
2344534574542433237923447 said:
It was a bit complicated but I got it working. I have not tested the fingerprint reader which is what you are concerned about but the ROM works without any obvious issues.
TWRP was flashed with Odin after I flashed stock firmware. I used ianmacd's TWRP to flash the GSI. I had to use faizauthar12's BUB5 kernel to get past the stuck LineageOS logo.
This thread for how to make the GSI usable for TWRP: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
Adding system.img to the zip file instead of creating a new zip file seemed to work better. Multidisabler fork with encryption appears to work.
Hope that helps anyone.
Click to expand...
Click to collapse
can you specify how exactly did you install the gsi?
AirAustin said:
can you specify how exactly did you install the gsi?
Click to expand...
Click to collapse
I used the zip method. Renamed the GSI .img file to system.img and put it in the right directory in the zip file. You have to use the tool I linked for TWRP to read the GSI. I flashed the zip through TWRP.
2344534574542433237923447 said:
I used the zip method. Renamed the GSI .img file to system.img and put it in the right directory in the zip file. You have to use the tool I linked for TWRP to read the GSI. I flashed the zip through TWRP.
Click to expand...
Click to collapse
I had to use another ZIP method with twrp to get lineage os to work. And the fingerprint isn't working properly. It's really bugged.
AirAustin said:
I had to use another ZIP method with twrp to get lineage os to work. And the fingerprint isn't working properly. It's really bugged.
Click to expand...
Click to collapse
There's a setting for Samsung in the Phh Treble Settings for the broken fingerprint reader. It might work
2344534574542433237923447 said:
There's a setting for Samsung in the Phh Treble Settings for the broken fingerprint reader. It might work
Click to expand...
Click to collapse
Can you send a screen shot of the settings and check if it works? I no longer have the GSI on my phone
AirAustin said:
Can you send a screen shot of the settings and check if it works? I no longer have the GSI on my phone
Click to expand...
Click to collapse
There seems to be no difference with it on or off. It's not working
I see that it's not working out for other people, sorry for late answer, so anyway moderators feel free to delete this post, as for everyone else feel free to try this urself and experiment a bit, Good luck
its cool that you have fod fixed but does face unlock work as well. I have used a couple of gsis and roms that are not one ui based and i found that aosp face unlock works much better than one ui
MariyanGOD said:
its cool that you have fod fixed but does face unlock work as well. I have used a couple of gsis and roms that are not one ui based and i found that aosp face unlock works much better than one ui
Click to expand...
Click to collapse
It should work, like any gsi
raftomas88 said:
It should work, like any gsi
Click to expand...
Click to collapse
have you tried booting it?
just tried it and the fod doesnt work
RFS3000 said:
just tried it and the fod doesnt work
Click to expand...
Click to collapse
you have to use q vendor for it to work
MariyanGOD said:
you have to use q vendor for it to work
Click to expand...
Click to collapse
Can you link it?

How To Guide Development status of Legion Y700 as far as I know

WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the crDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while crDroid will start.
Click to expand...
Click to collapse
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group.
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
FIERA03 said:
WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Telegram, so I share the link.
https://t.me/poncesgsi/98843
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
Click to expand...
Click to collapse
What do you mean by Project Elixir is officially certified?
gogitossj said:
What do you mean by Project Elixir is officially certified?
Click to expand...
Click to collapse
Project Elixir GSI is an "official" GSI because its maintainer, Mr. UGLYKID24, is certified by the Elixir development team. On the other hand, crDroid is an "unofficial" GSI because Mr. Nazim is not certified (Ancient OS, which is also certified under Nazim's ROM, is considered an official GSI).
FIERA03 said:
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
Click to expand...
Click to collapse
I wonder if Konabess working for this
FIERA03 said:
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
Click to expand...
Click to collapse
Hey FIERA03, I see you removed the LPDDR and Cache module. Did they have issue?
- can you show me how to install
"By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group." ???
- No double taps, no lift to wake, always use the power button is not convenient
- thank you
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
you486jsm said:
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
Click to expand...
Click to collapse
I think the title said: to all samsung
Mrxyzl said:
제목에 이렇게 적혀 있었던 것 같아요: 모든 삼성에게.
Click to expand...
Click to collapse
I heard that this ROM can be installed and used on P11 and P12. Then, wouldn't it be possible on Y700? I don't have the skills, so I'm asking.
I can't seem to flash the system file, I get this error:
C:\Users\Mike\Desktop>fastboot flash system C:\Users\Mike\Desktop\crDroid-8.13-arm64_bgN-Unofficial.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
I unlocked my bootloader using the "fastboot oem unlock-go" command because I couldn't get the SN.img file to work. It does show my bootloader as unlocked. Could this be my issue? Also, my tablet is 12GB 256GB, not sure if that changes which crDroid file I should flash...any help is greatly appreciated.
I figured it out, I was using an outdated version of fastboot. Downloaded this and worked like a charm!

Categories

Resources