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?
Related
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
Code:
Your warranty is now void.
I am 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 doing this to your device
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
This is an Android 9.0 GSI (Generic system image ) specific for the Samsung A6!
WARNING: The GSI is unstable and some things are not working. Let me know what is not working please!
FLASHING GUIDE:
1. Formata Dalvik, System, Data and Cache.
2. Install the GSI and click on system image.
3. Reboot to recovery.
4. Install latest Magisk. (Not necessary)
5. Reboot.
BUGS:
No Storage and SD Card access. (On FN Variant)
FIXES
The SIM card reading has been fixed.
Download Link:
https://github.com/phhusson/treble_...9/system-arm32_binder64-aonly-gapps-su.img.xz
Telegram Group:
https://t.me/joinchat/AAAAAEWK3LnN80mnvcTUtA
My telegram username: Paxa202
Credits:
@BlackMesa123
@phhusson
IF THERE IS SOMEONE WHO WANTS TO HELP ME TO MAKE THE GSI STABLE, SEND ME AN PM ON XDA OR AN MESSAGE ON TELEGRAM.
Hello. Is there a thread where we can see how this prosses if done?
ariber14 said:
Hello. Is there a thread where we can see how this prosses if done?
Click to expand...
Click to collapse
The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
phhusson said:
The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Click to expand...
Click to collapse
So is there a woring android p version for a6 plus or do we have to wait?
ariber14 said:
So is there a woring android p version for a6 plus or do we have to wait?
Click to expand...
Click to collapse
It probably works also with A6+
Shouldn't all GSI ROMs work with all devices with a or ab support or am I wrong?
DKzVeNgEnS said:
Shouldn't all GSI ROMs work with all devices with a or ab support or am I wrong?
Click to expand...
Click to collapse
Yeah but samsung A6 has something unusual, this commented phhusson earlier.
Phhusson: The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Because the 64bits CPU runs 32bits OS is the reason that normal GSI's doesn't boot on Samsung A6
Working on j6 too
sd card and working is j6.
camera not working and sim not working...
DaanDH12 said:
Yeah but samsung A6 has something unusual, this commented phhusson earlier.
Phhusson: The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Because the 64bits CPU runs 32bits OS is the reason that normal GSI's doesn't boot on Samsung A6
Click to expand...
Click to collapse
That's pretty normal for Samsung devices, especially lower spec variants.
A 64bit cpu is backward compatible with 32bit architecture, so shouldn't be an issue as long as the rom supports 32bit, built for ARM target as mentioned above.
ashyx said:
That's pretty normal for Samsung devices, especially lower spec variants.
A 64bit cpu is backward compatible with 32bit architecture, so shouldn't be an issue as long as the rom supports 32bit, built for ARM target as mentioned above.
Click to expand...
Click to collapse
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
ariber14 said:
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
Click to expand...
Click to collapse
Seems you've possibly disabled/removed a component required to facilitate update checking.
ashyx said:
Seems you've possibly disabled/removed a component required to facilitate update checking.
Click to expand...
Click to collapse
But i didn't change anything to the rom
There are some questions that i'm still not sure what to do.like
1.should i choose sparse,raw or permissive?
2. Should i incloude vendorn, odm and cache folder inside the rom?
ariber14 said:
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
Click to expand...
Click to collapse
Skip the whole setup thing! IMPORTANT! skip everything and setup wifi later, if you connect to wifi he goes searching for updates, but if you not connected to wifi, it skips the update part!
DaanDH12 said:
It probably works also with A6+
Click to expand...
Click to collapse
Working on A6+ with sd card but sim card not working
DaanDH12 said:
Skip the whole setup thing! IMPORTANT! skip everything and setup wifi later, if you connect to wifi he goes searching for updates, but if you not connected to wifi, it skips the update part!
Click to expand...
Click to collapse
I did it. Rom is working good. Everything looks great. About the glitch during the setup i just install gapps 8 ARM after flashin Rom and it's ok.
Adb also work for me
The thing is i don't understand why something on google account breaks even though i dont make any changes at all from stock rom. I also get a difference at menu. T mobile, mobile networks and service provider are visible at custom rom menu like in the pic below. Another thing is that i used superr's kitchen 1.1.9.5 to do the job. When i use 2.0.0.5 the custom rom does not boot.
ariber14 said:
The thing is i don't understand why something on google account breaks even though i dont make any changes at all from stock rom. I also get a difference at menu. T mobile, mobile networks and service provider are visible at custom rom menu like in the pic below. Another thing is that i used superr's kitchen 1.1.9.5 to do the job. When i use 2.0.0.5 the custom rom does not boot.
Click to expand...
Click to collapse
I think you should post in a own thread. Otherwise people will confuse your post with the Treble Rom posts
nebkas said:
I think you should post in a own thread. Otherwise people will confuse your post with the Treble Rom posts
Click to expand...
Click to collapse
you are right. i will make a new thread for this
Codelyoko2409 said:
Working on A6+ with sd card but sim card not working
Click to expand...
Click to collapse
I think some proprietary binaries are missing in the rom. But shouldnt be so hard to figure out why sim is not working. What do you think @ashyx ? Should be to solve with tracking the log's?
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
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?
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?