TESTED GSIs:
1) Project Elixir (Bootable; Incoming/Outgoing Call Issues)
2) Pixel Experience (Bootable; Working with minimal bugs
Hi!
Having low amount of roms or even custom recoveries, I am wondering what GSI is a good choice for this phone?
I've had some bad luck while trying to run some, but It'd be nice to see what roms worked out for the rest of the people here.
So, what GSI, in your opinion, do you think is a good GSI for this phone which only ever received one major update and is only receiving security updates once a while?
My favourite GSI is Project Elixir. It works perfectly, has special Pixel features, and has official GSI support (minus updater; updating is done by dirty-flashing a new version). GSI downloads are here. Check it out!
Really?
Why, I'll have to test that one out, then! What version are you on, dch82?
Also, how's the calling as well as battery life on it? Does it last as long as the stock OxygenOS does here?
I tried it and it failed for me with the error: "not enough space to resize partition!"..
Well, I attempted it at least?
Thanks anyways for the suggestion, tho.
Try
Bash:
fastboot delete-logical-partition product_a
BTW look on the Google guide on doing so
dch82 said:
Try
Bash:
fastboot delete-logical-partition product_a
Click to expand...
Click to collapse
I did try that.. although to no luck, sadly.
dch82 said:
BTW look on the Google guide on doing so
Click to expand...
Click to collapse
Hey!
I managed to get this GSI up and running on my Nord N10!
All I did was reflash the stock back with the MSM tool, updated to recent version (11.0.13 as of writing this), unlock bootloader, flash the PIXELEXPERIENCE unofficial recovery on both slots, go to fastbootd and the following:
Bash:
fastboot erase system_a
Bash:
fastboot delete-logical-partition product_a
Bash:
fastboot delete-logical-partition system_ext_a
Bash:
fastboot flash system (GSI.img)
Bash:
fastboot -w
(I used the above steps from jamescable. Thanks man.)
The "not enough space" error doesnt happen and it works!
Then I factory resetted the phone from recovery while NOT rebooting just yet and after resetting, I then rebooted.
Lo and behold, I got Project Elixir up and running on my phone!
Will have to see where this goes!
EDIT 1: Successfully rooted the GSI via Magisk Delta! The GSI feels so fluid and responsive!
Also, I want to report back, Evolution X GSI by ponces also seems to be working with the above method!
It seems that Ponces' GSIs are a bit more stable for me.
During testing out Project Elixir, I noticed that Magisk Delta's MagiskHide mode would bootloop the phone until it automatically activated the bootloop protection setting to disable the setting.
However, in Evolution X, that sort of thing isn't happening at all.
Maybe could be due to some steps I took, or maybe due to this phone.
Either way, am happy that at least we can boot some GSIs and have fun with this phone almost entirely stuck on A11 despite being usable on A13.
Huh, interesting.
I don't use magisk (I use unsupported phones) so I don't know about those issues
A sad thing, though:
Apparently, on Project Elixir, incoming call audio is NOT working for me.
Even after doing all workarounds and even reflashing stock and trying again, didn't work.
Sadly, might go back to rooted stock but we'll see what happens in the future.
Anyways, gtg revive my phone xD
YAAP is a good gsi for this phone. Everything seems to work.
mouseracer said:
Apparently, on Project Elixir, incoming call audio is NOT working for me.
Click to expand...
Click to collapse
I just realized, that happens to me too... Have you tried communicating to the Devs through the telegram channel?
dch82 said:
I just realized, that happens to me too... Have you tried communicating to the Devs through the telegram channel?
Click to expand...
Click to collapse
I haven't yet; I'm on stock for the meantime.
Additionally, I don't have telegram as well.
Also, I just want to add that I'm using Pixel Experience GSI by Ponces and have been having a blast with it!
The battery life's good for me (although did need to do some optimizations to get it working), Less bugs and incoming as well as outgoing calls are working!
Whatsapp is also working and safetynet passes!
I've also rooted it and I STILL pass safetynet (although am using unofficial Magisk Delta instead of Magisk) as well as havin systemwide ad blocker and other stuff as well!
Alright, it's been a while.
I'm now installing @MeowIce 's LineageOS 18.1 (A11) GSI.
Why this? Simply because A) It's lineageOS and therefore is interesting to me and B) It has the newest security patches by @MeowIce
Time to see how far this goes.
mouseracer said:
Alright, it's been a while.
I'm now installing @MeowIce 's LineageOS 18.1 (A11) GSI.
Why this? Simply because A) It's lineageOS and therefore is interesting to me and B) It has the newest security patches by @MeowIce
Time to see how far this goes.
Click to expand...
Click to collapse
Well.
It did work well, however there were some issues that I had.
I'll maybe return back to it someday, but for now, flashing PE GSI.
I've been using EvoX A13 for a while now with pretty much no issues outside of minor ones that don't matter. It runs smoothly, and has a nice amount of cool customisations, magisk, volte, call sounds etc. work, only thing that sticks out for me is that the evox launcher is kinda buggy, some options do not work.
Would love to try AncientOS A13 but can't get it to boot. I will be trying RisingOS soon since a GSI came out a few days ago, will try as soon as I get my hands on a pc. Seems like a cool one.
Also, AOD worked for me on GSIs untill phh patches got to around A12.1 ones, since then AOD works while charging, but when not plugged touchscreen stops working after a while. Reboot gets it working again. Is it same for others with this phone?
Related
Hi to everyone here... Finally a MoKee ROM is relased for Xiaomi Mi 9 SE (grus) devices!
Developer: subdragonzj
This thread will be unofficial for testing of a AOSP-MoKee ROM builded from the source...
(and ROM based on MoKee with some mods builded by myself)
Stay tuned
I have to say that I was pleasantly surprised by this ROM. It doesn't have the existential issues of PE, so it has all those little useful features out of the box (instant face unlock, double tap to sleep on the lockscreen, etc.). It's not XenonHD based, so no freezing incoming calls. Performance is good (closer to xiaomi.eu). Fingerprint scanner is reasonably fast (I say reasonably because xiaomi.eu is always two steps ahead, in this department). And battery life is also optimized to best levels.
I had issues completing Google setup and with wifi, but I have to be honest: I installed the ROM on top of the latest xiaomi.eu (without sound issues, by the way). Now I have 10.3.4 eea vendor. Let's see how it performs on everyday tasks.
PS - Also, I didn't like the ads on MoKee Center, but Adway takes care of that, of course. I have several paid apps from Play Store, so if the ROM is really good, I have no problems with donation for some extra features.
Can you tell us which steps you made to install mokee properly?
Cheers
Gesendet von meinem MI 9 SE mit Tapatalk
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
elpaablo said:
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
Click to expand...
Click to collapse
Ultra-wide camera is broken due to missing some nodes at the kernel dtsi on Xiaomi side (their kernel source is too much broken stuff, even for MIUI itself, which is funny).
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.[/QUOTE]
does it support camera 2 API full
I'm using this ROM for now because it's more optimized than PE. Apart from color profiles that don't stick in any AOSP ROM and a dark theme with white notifications, everything else (except camera, as posted above) is working fine. Fingerprint scanner is reliable (although still a little slow), face unlock is instant and the only issue that needs to be solved asap is ultra wide lens not working. A custom kernel can deal with that, but the stock kernel performs better with this ROM. So, I think I'll wait for a fix or other ROM development.
Anyone getting this on any of your AOSP ROMs?
Been using for 3 days now, and by far it gives the ideal battery performance. Tried crDroid and although there were some improvements, couldn't last a day with barely 20% and high idle drain.
Will be staying with this ROM as everything that I expect from this device is provided for. Personally, no battery means no phone for me, so that's my baseline. Thanks to the other developers for their hard work and free time!
elpaablo said:
Anyone getting this on any of your AOSP ROMs?
Click to expand...
Click to collapse
For now, custom AOSP ROM have 177k-184k antutu score, and it's normal.
you can't expect it to be as close as miui (which can go between 185k-195k).
besides, antutu doesn't represent the true performance since anyone can hack it just like huawei before.
btw, this is from some unreleased custom rom that I use right now, no kernel mod, no nothing. typical custom aosp's score
Yes, but generally it gives you the right idea. The ROM is very fluid. I've installed all my stuff and it remains fluid. In fact, I think the latest nightly update has improved user experience.
Then comes maintenance and that's what worries me the most. We see ROMs (XenonHD and PE) that freeze on incoming calls. This is not just a little bug, it's a massive bug. It basically disables your phone. And it's not been solved yet? crDroid developer seems to think that SIM management is not important in a dual SIM phone. Instead, he tries to make fingerprint scanner work 0.1 seconds faster. Yes, camera is not fully working on MoKee and I really hope that this issue is solved, but at least I can receive calls and enable my data SIM card only when I use it, which saves a lot of battery.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
I installed latest xiaomi.eu version last week and it's way ahead in every aspect, except 2: MIUI (sucks) and SIM management. AOSP ROMs (except crDroid) handle SIM management in a much better (easier) way.
elpaablo said:
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Click to expand...
Click to collapse
Sorry for picking this up again, i´d like to give mokee a try.
which faceunlock.zip did you use?
https://forum.xda-developers.com/android/software-hacking/mod-fix-gapps-unlock-t3863509 The one from this thread?
Thank you, Cheers.
Sooo now i´m stuck on fastboot.
Tried flashing vbmeta using fastboot with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", but it just says "fastboot.exe: unknown option -- disable-verity"
Any ideas?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It's the exact phrase I copy/paste.
Maybe you added a space somewhere?
If you're using power shell type cmd first.
Face unlock: https://androidfilehost.com/?fid=11410963190603910002
i used copy/paste too.. i´ve attached a screenshot.
That´s really annyoing atm..
Type cmd or just use cmd instead of PowerShell.
Yes you should always use cmd in administrator mode in the same folder than vbmeta.img
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Humpfrey said:
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Click to expand...
Click to collapse
Can you tell us where is located fastboot and vbmeta.img on your pc?
For instance, i have all my files in c:\Android
So I launch the cmd directly in that folder.
Started by DL https://androidfilehost.com/?fid=962187416754459552
Copied on C drive and renamed into Android
Then I copy my files on it, and right click/launch as admin on "cmd-here".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
Havoc-OS 3.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI by @SKULSHADY.
So many features that you probably won't find in any ROM.
All you can dream of and all you'll ever need.
Just flash and enjoy...
Whats working?
Wifi
RIL
Mobile data
Camera
Flashlight
Camcorder
Bluetooth
Lights
Sound / vibration
VoLTE
Known Issues?
You tell me
Links
Rom
Installation
Remove your Google account.
Flash latest firmware with the set of commands attached.
"Fastboot boot" TWRP/OrangeFOX, flash copypartitions.zip and flash ROM.
Boot system..
Optional: boot TWRP/OFOX after the first boot, and flash recovery installer/Magisk/GApps.
Set of commands: https://forum.xda-developers.com/attachment.php?attachmentid=4955977&d=1582350851
If you face any boot loop issue kindly format data and cache.
Contact me on telegram
Credits
LineageOS ([url]https://github.com/LineageOS[/URL])
Crdroid ([url]https://github.com/crdroidandroid[/URL])
Pixel Experience ([url]https://github.com/PixelExperience[/URL])
Nitrogen Project ([url]https://github.com/nitrogen-project[/URL])
Omnirom ([url]https://github.com/omnirom[/URL])
MSM-Xtended Team ([url]https://github.com/Project-Xtended[/URL])
Skydragon ([url]https://gitlab.com/HolyDragonProject[/URL])
Syberia Project ([url]https://github.com/syberia-project[/URL])
And all the other Developers, Testers, Donators and Users.
Team
Lead Developer
SKULSHADY (Anushek Prasal)
ZeNiXxX (Viktor Hermann)
Support Team:
theo.j22 (Tushar Jain)
DankBoi (Apoorva Kr. Srivastava)
Contributors
Electimon
SyberHexen
Jleeblanch
Erfanoabdi
Source Code: [url]https://github.com/Havoc-OS[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest
Based On: Aosp
Version Information
Status: Stable
Created 2020-02-27
Last Updated 2020-04-12
Update Log:
12-March-20: Fixed VoLTE
Add MotoExtras to settings
Added KCAL to kernel and MotoExtras
Fixed a MotoCam Bug
Use Coral Fingerprint
10-March-20:
08-March-20: Update to Havoc OS 3.3 and fix some settings errors
03-March-20: Improve UI performance
29-Feb-20: Fixed calling audio issues, thank @erfanoabdi
You guys are bringing it to the G7 Power!! Awesome work!! [emoji16]
Sent from my mi mix 2 using XDA-Developers Legacy app
intalled from stock rom 9 and it goes great at this moment, thank you, keep the fantastic job
I have been waiting so long, GSI has been working really well on moto g7 power. I figured it wasnt too long before a rom was built.
Any Gapps package working?
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
I use these: https://forum.xda-developers.com/android/software/arm64-nikgapps-t3915866
Edit
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
I just downloaded the micro version off opengapps website its bare min and I am OK with that I just want the Google play store and that's it
So how is this rom Working for people is it good wanna try it but don't wanna have problems
XxRealSaltyxX said:
So how is this rom Working for people is it good wanna try it but don't wanna have problems
Click to expand...
Click to collapse
far as i can tell, everything works except my mic. probably something i did but you might wanna test it after first install. I mostly text so its not a huge issue for me honestly. and i use a bluetooth headset most of the time
UPDATE: fresh installed again and mic is working. must had just been a bug.
I use adaptive storage on my SD card and having issues running apps on the phone I have to switch the location for the apps to work
How to put TWRP on this custom?
eastyx said:
How to put TWRP on this custom?
Click to expand...
Click to collapse
I make this comment assuming that you already have installed factory image and flashed the copy-partition-ab.zip previous to doing anything I say here. I only say that because I wouldn't want you to brick. If you have already done all that then just flash rom and reboot system like it says in the op. Then boot recovery again: fastboot boot twrp.img and install your gapps, magisk, recovery installer zip or whatever because if you try and flash it ALL at once it may not boot. Also as the op says after you install the rom and reboot system your phone may boot into recovery (stock) and prompt you to factory reset. If so select yes and do it otherwise it will not boot. I use a USB stick and keep things on it for my phones just in case. Makes it so much easier!
If you're already using havoc just: sudo fastboot boot twrp.img Then in twrp flash twrp installer zip from twrp site and reboot system.
You should be good then and twrp should then be installed. If it freezes up on you (if touch screen quits working) just boot back into bootloader manually (holding volume down+ power buttons) and boot recovery again through fastboot again... If touch quits working on recovery it will eventually work again, always has for me, but that's what I did and it worked. I actually don't even install recovery now I just use fastboot to boot twrp (or orange fox recovery) when I need to and I don't pull fancy stuff when I'm nowhere near my house. lol. Seems like twrp works better and has no freezes if I don't install it but it does freeze up when I have installed it in the past.. ? Also if you aren't already a member of the Moto G7 Power telegram group definitely check that out. But I recommended using a free app to get another phone # to use for making telegram account because if you use your real one they will spam the ______ outa you! The app named Text Free worked for me for that and telegram accepted the VoIP #..
@Electimon You're awesome! Really appreciate your time spent on this!! Does Havoc have signature spoofing? Seems like i read that somewhere about Havoc having it.. Soon as I make this post I'll check and also see if the patch got updated here on xda for 10/Q to add spoofing if its not. If I find a way to make it spoof if its not spoofing I'll report back. ?? Thanks again!!! :good:
Yes It does
flash713 said:
I use these: https://forum.xda-developers.com/android/software/arm64-nikgapps-t3915866
Edit
Click to expand...
Click to collapse
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
I did all the steps and my g7 power is in hardbrick, model XT1955-2
toxinburn said:
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
Click to expand...
Click to collapse
I'm not sure whats up but the place to read up and learn or should I say another place to learn is telegram group for G7 power. I go read backwards there from most recent comment up for hours sometimes. I used to immediately rip my phones out the box when I got em and unlock bootloader and flash a Aosp rom but I've learned through killing a few to read everything I can first for a few weeks then operate. I was lucky to bring this one back all the times thanks to blank flash and the guys telling he keep trying it. I believe its all about the USB cable and having steady communication on the blank flash. I have no issues installing recovery but when i have it locks up on me so I just boot it when I need to and works good.
KUSANAGUI said:
I did all the steps and my g7 power is in hardbrick, model XT1955-2
Click to expand...
Click to collapse
I have a 1955 5 aka metro by tmobile g7 power and ever since I joined the Moto G7 power telegram group and learned about how to do things I've not bricked but when this phone came out I immediately grabbed it on day 2 and hard bricked it and bricked it a few more times and brought it back every time using blank flash. Sometimes it took a while to get the blank flash to run atw through but eventually it did and I was able to boot to bootloader and fastboot factory image.. if you aren't already on telegram group it has a TON of information and everyone is really cool and helpful. Best group I've ever been around! The group is @mg7Power
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
toxinburn said:
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
Click to expand...
Click to collapse
Try installing everything without a micro SD card I. It was culprit that gave me hours and hours of troubke
I'm interested in this rom to run as a daily driver, have the VoLTE issues been resolved?
flash713 said:
I'm not sure whats up but the place to read up and learn or should I say another place to learn is telegram group for G7 power. I go read backwards there from most recent comment up for hours sometimes. I used to immediately rip my phones out the box when I got em and unlock bootloader and flash a Aosp rom but I've learned through killing a few to read everything I can first for a few weeks then operate. I was lucky to bring this one back all the times thanks to blank flash and the guys telling he keep trying it. I believe its all about the USB cable and having steady communication on the blank flash. I have no issues installing recovery but when i have it locks up on me so I just boot it when I need to and works good.
I have a 1955 5 aka metro by tmobile g7 power and ever since I joined the Moto G7 power telegram group and learned about how to do things I've not bricked but when this phone came out I immediately grabbed it on day 2 and hard bricked it and bricked it a few more times and brought it back every time using blank flash. Sometimes it took a while to get the blank flash to run atw through but eventually it did and I was able to boot to bootloader and fastboot factory image.. if you aren't already on telegram group it has a TON of information and everyone is really cool and helpful. Best group I've ever been around! The group is @mg7Power
Click to expand...
Click to collapse
I sent my smartphone to the technical service because no method of his group served me, I will never root again, install rom, or twrp. To any smartphone that has a / b partitions, my moto x play has not given me headaches like this g7 power.
THANKS
KUSANAGUI said:
I sent my smartphone to the technical service because no method of his group served me, I will never root again, install rom, or twrp. To any smartphone that has a / b partitions, my moto x play has not given me headaches like this g7 power.
THANKS
Click to expand...
Click to collapse
I felt same at first. And not all A/B partitioned phones are like this one. My Pixel XL is A/B and I musta flashed it thousands of times and never bricked. I think with this forum there are a few different models of the same device and it can be confusing AF. Or the fact that my phone is a Metro G7 Power and it uses RETUS, retail US firmware and won't flash the metro firmware. I tried more than once early on. My other device is a xiaomi mi mix 2 I purchased off swappa a while back for $140 and it's a Aonly 64 bit device and flashes just like the last 39 or so phones and tablets I owned in the past. Maybe look at A only devices. There are tons of them. For some reason it took me a while to fully understand the whole A/B partitioning deal even though I read everything known to man on it here and other places. I've had to figure things out a few times through trial and error just because what seems to work for others doesn't for me. As soon as I get a tripod I'm going to throw some videos up on YouTube of how I install roms and flash firmware and things like that. I believe the big thing for this device that throws some people off is the different models idk... I hear you though. I bet money that maybe not all but most people who didn't get the blank flash to work didn't do it enough. It's a tedious mission. While im grateful that we have the blank flashes I'm definitely not trying to do it all again because it was a very long process for me every time I did it. Lol.
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
Click to expand...
Click to collapse
YES! Thank you very much for supporting this tablet!
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
Click to expand...
Click to collapse
As a follow up to my original post I wanted to mention that for anyone who wants a new ROM on their SM-T290 until this is finished development, use the Nexus Rom by Magendanz. I was able to do a fresh stock firmware install and retry the rom and my opinion has changed. I have noticed that these Tab A 8.0 tablets have been used a lot for like Uber/Door Dash and other POS terminals. I am pretty sure a lot of them have modified or customized firmware for these reasons and when I mine second hand it was from a pizza store. I think that messed up the upgrade.
Overall Magendanz did a great job, when you install it properly. I have zero issues with functionality now, TWRP recovery set up, as well as Magisk installed and everything is running extremely well.
As far as instruction on how to install. Take a look at some of the comments further down on the Nexus thread. That is what I did this time around and it worked perfectly. Last thing I did was copy Magisk.Apk to my SD, change extension from .APK to .ZIP, then boot into TWRP and install that ZIP.
Going to update progression on a monthly basis as far as the LineageOS 18.0 build
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
Click to expand...
Click to collapse
Do you have a github with your source code and manifest? I just got this tablet (used) yesterday and I would like to see if I can help. I have built LineageOS roms for a number of older Samsung Tab A devices, but will have to do some research on the "new to me" T290. Thanks.
Just got this tablet, how's the beta coming along? And what can I do to help?
Thank you my guy I had lost all hope for custom roms on this tablet. It's quite relieving to know that I'm not alone.
Also, has anyone experienced severe lag on one ui 3 while doing basic tasks? The thing literally gets 5 fps while watching youtube and surfing the web but it plays 3d games at 20 fps on low settings. wtf
HaveSomeRubicon said:
Thank you my guy I had lost all hope for custom roms on this tablet. It's quite relieving to know that I'm not alone.
Click to expand...
Click to collapse
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
As per the Nexus Post;
Unlock Bootloader
flash TWRP
Wipe data
Install Andy Yan's Lineage OS 19 GSI
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
Install Magisk
Reboot
Cheers!
SniperFox
SniperFox22 said:
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
...
SniperFox
Click to expand...
Click to collapse
Good advice But which of Andy's GSIs did you use exactly ?
Thanks so much dude
The GSI is a .img.xz will it work or does it need to be .gsi
HaveSomeRubicon said:
The GSI is a .img.xz will it work or does it need to be .gsi
Click to expand...
Click to collapse
You download the .img.xz file and unzip it.
Inside this will be the .img file
This is what you need to flash (.img)
2faraway2 said:
Good advice But which of Andy's GSIs did you use exactly ?
Click to expand...
Click to collapse
Sorry
Use this one
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
It has Gapps built in as well as super user through SSH, dont install Magisk as it will error that there is already SU tool installed.
@SniperFox22 , did you make a github for the code or didn't even start since you are happy with GSI?
SniperFox22 said:
You download the .img.xz file and unzip it.
Inside this will be the .img file
This is what you need to flash (.img)
Sorry
Use this one
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
It has Gapps built in as well as super user through SSH, dont install Magisk as it will error that there is already SU tool installed.
Click to expand...
Click to collapse
My OS didn't have an option to unzip it at first glance. I haven't been able to install gapps so I'm gonna try that gsi. Also, am I supposed to wipe internal storage before flashing or not?
I got it working but games just crash which is worse than before
Came across this while trying to root my sm-t290. Just want to add that Andy Yan has upgraded to a 19.1 version that appears to work just fine. Flashed to system partition using twrp after I had flashed the Nexus rom. Wifi works, sound works, sd card, bluetooth keyboard works just fine.
SunSlide said:
Came across this while trying to root my sm-t290. Just want to add that Andy Yan has upgraded to a 19.1 version that appears to work just fine. Flashed to system partition using twrp after I had flashed the Nexus rom. Wifi works, sound works, sd card, bluetooth keyboard works just fine.
Click to expand...
Click to collapse
Link to it???
I like the link above because it has all the versions but lineage-19.1-20220320-UNOFFICIAL-arm64_bgS.img.xz is the one that I used. The page has the naming convention. Ill mention that even though it says that it's supposed to be rooted, I couldn't get it to work right. The nexus rom had an option in the 'phh treble' menu to activate root and this lineage image should also but the option wasn't there. It kept saying the supersu binary was busy but that was after I flashed a supersu.zip(it may have worked before then i don't know). I played with it a little bit but ended up just flashing back to the Nexus rom.
Hey guys!
Installed "lineage-19.1-20220320-UNOFFICIAL-arm64_bgS.img"
Everything starts up, but something is weird with my installation and my storage, it freezes when i go into storage and i cant download anything without apps start to crash.
Im not sure if i flashed it correctly, i did a wipe in TWRP before installation.
Really hope i can get this to work since it waaaaay faster then the bloat samsung ships
Edit:
Tried flashing another rom (nexus) and had the same issue!
trying to reflash and wipe everything except internal storage.
Where should i flash image? i get: "select partition to flash image", never seen that before (might be because you flash img and not zip)
SniperFox22 said:
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
As per the Nexus Post;
Unlock Bootloader
flash TWRP
Wipe data
Install Andy Yan's Lineage OS 19 GSI
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
Install Magisk
Reboot
Cheers!
SniperFox
Click to expand...
Click to collapse
Hi Sniperfox,
could you please provide a link to the correct Nexus post, I would like to make sure i follow the correct one as I have a tab A (2019) and want to nstall lineage.
thanks in advance
rgds Acsum
After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time.
So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER
SMINORI GSI TOOL RELEASE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO USE:
1. DOWNLOAD & EXTRACT SMINORI GSI AUTO INSTALLER
2. DOWNLOAD YOUR FAVORITE GSI ROM HERE (choose arm64 a/b)
3. EXTRACT GSIROM.IMG TO SAME FOLDER WITH THE TOOL FOLDER
4. RENAME THE GSIROM.IMG TO SYSTEM.IMG
5. REBOOT YOUR PHONE TO FASTBOOT MODE AND CONNECT TO PC
FILE ORDER IN FOLDER SHOULD BE LIKE THIS
6. OPEN SMINORI GSI TOOL.bat
7. FOLLOW THE INSTRUCTION & JUST PRESS ENTER
ENJOY YOUR FOCO WITH GSI ROM
SOME EVIDENCE:
NEED TO REMEMBER:
I've used this tool several times to install gsi rom and it worked without any problem.
almost all roms from the link above can be installed and can run stable on foco m4 pro.
DON'T FORGET TO HIT THANKS IF I HELPED YOU
NO NEED TO DONATE ME, JUST SAY THANKS TO ENCOURAGE ME
Awesome!!!
Please update the post with more info like: whats necessary to make this process (UBL, custom recovery...) And How to revert this to stock state
This is really helpful, thanks! Could you give us a review of how well the GSI you've chosen works for this device? Any particular bugs etc?
nairaldo said:
Awesome!!!
Please update the post with more info like: whats necessary to make this process (UBL, custom recovery...) And How to revert this to stock state
Click to expand...
Click to collapse
because until now there is no stable custom recovery for this device so just use stock recovery. and because this tool requires the process in fastboot mode so it requires unlocking the bootloader.
aricooperdavis said:
This is really helpful, thanks! Could you give us a review of how well the GSI you've chosen works for this device? Any particular bugs etc?
Click to expand...
Click to collapse
later i will make a thread how to install specific gsi rom.
now i'm trying to use pixel experience last update for daily use.
I will tell my experience at least after using it for 2 weeks and create a thread for how to install it.
and about particular bugs, after fixing some bugs at the beginning now what I feel is just a general bug in the camera.
Good tool. Guys, are you satisfied with your GSI installs? (no bugs?). There is echo during phone call (I hear myself) for me and automatic brightness is also broken a bit.. Did you noticed these bugs too?
Are you facing any bugs ?
Like volte , camera , calling , sound , 90 hz display ?
Aj_$tyle$ said:
Are you facing any bugs ?
Like volte , camera , calling , sound , 90 hz display ?
Click to expand...
Click to collapse
volte , camera , calling , sound , 90 hz display it all can be fixed in the phh treble setting.
let me explain what is meant about stable in my thread. what I mean by stable is the installation process. in the script that I made not only to install gsi, the scrit will also disable verification and delete partitions that are not needed by the gsi rom.
for the GSI ROM itself, until now I am still comfortable using it for daily needs.
just a general problem that is not only in the fleur device. but all devices are the same.
common gsi issues : Auto brightness, bluetooth audio(android13) thats only for me. and yaa camera off course is different with stock. but not problem at all.
NOTE: if you want to install gsi with minimum bugs and stable. use vendor from android 11.
because of my experience when using a vendor from android 12 when installing gsi android 13 there was a compatibility problem. like in AOD, Bluetooth, and can't boot in pixel experience.
soutaminori said:
volte , camera , calling , sound , 90 hz display it all can be fixed in the phh treble setting.
let me explain what is meant about stable in my thread. what I mean by stable is the installation process. in the script that I made not only to install gsi, the scrit will also disable verification and delete partitions that are not needed by the gsi rom.
for the GSI ROM itself, until now I am still comfortable using it for daily needs.
just a general problem that is not only in the fleur device. but all devices are the same.
common gsi issues : Auto brightness, bluetooth audio(android13) thats only for me. and yaa camera off course is different with stock. but not problem at all.
NOTE: if you want to install gsi with minimum bugs and stable. use vendor from android 11.
because of my experience when using a vendor from android 12 when installing gsi android 13 there was a compatibility problem. like in AOD, Bluetooth, and can't boot in pixel experience.
Click to expand...
Click to collapse
Can you tell me if you are able to use the camera properly? Like sometimes some lenses don't work in some roms, like the macro or wide.
Is something like that happening or it's all stable.
And installing a android 11 gsi wd be the most stable for daily usage right?
I tried a few gsi's, out of them corvus os (android 12 ver) was the most stable. However, I was unable to make or receive calls on all of the gsi's that I flashed. Also the gcam modules that I tried to install kept crashing everytime I tried to open them. Due to a lack of a stable recovery, I wasn't able to install gapps. Corvus OS didn't have inbuilt gapps. And I cant think of ways to install them.
It's a bummer, really. I really liked how corvus os looked. I guess I have to revert back to old annoying Miui.
If there are ways to fix some if not all the issues, please do post.
Eagerly waiting for the fixes )
warhead1721972 said:
I tried a few gsi's, out of them corvus os (android 12 ver) was the most stable. However, I was unable to make or receive calls on all of the gsi's that I flashed. Also the gcam modules that I tried to install kept crashing everytime I tried to open them. Due to a lack of a stable recovery, I wasn't able to install gapps. Corvus OS didn't have inbuilt gapps. And I cant think of ways to install them.
It's a bummer, really. I really liked how corvus os looked. I guess I have to revert back to old annoying Miui.
If there are ways to fix some if not all the issues, please do post.
Eagerly waiting for the fixes )
Click to expand...
Click to collapse
Hello, I recommend the gsi roms that come with the gapps included. You can also install the gapps with magisk, I use the pixel android 13 on the redmi note 11s. I don't use custom recovery if it's not stock.
post the CherishOS android 13 rom everything works and is very good.
ped1609 said:
Hello, I recommend the gsi roms that come with the gapps included. You can also install the gapps with magisk, I use the pixel android 13 on the redmi note 11s. I don't use custom recovery if it's not stock.
post the CherishOS android 13 rom everything works and is very good.
Click to expand...
Click to collapse
are you able to make calls and recieve them? internet and wifi works fine but i just cant seem to figure out the calling problem
warhead1721972 said:
are you able to make calls and recieve them? internet and wifi works fine but i just cant seem to figure out the calling problem
Click to expand...
Click to collapse
No he tenido problemas,bluetooth conexión con pc funciona para transferir archivos,llamadas funciona,nfc no uso,auriculares tambien,doble toque,led pantalla puedes poner el color que quieras.whasspap se olle bien.
Tried several GSI (almost all of them ) on M4 pro 4G phone. I don't have any specific demands from phone - just calls, internet, so didn't try bluetooth or else.
+ : Everything kinda worked. 90Hz is in Phh's settings. Calls worked (at least with that rom i tried to call), internet also worked. Android 13 is nice, i liked Pixel Experience and, of cource, endless possibility to tweak in some roms.
- : Well, what surprised me was sluggish desktop/menu scrolling, even with 90Hz screen enabled. Not so smooth like in MIUI, and that was maybe the main reason i got back to default OS.
Camera (even didn't try all those cam tweaks, i remember from other phones that you always end up with "not that quality" feeling when using not a propieritary camera). Not that i use it a lot, so it was not really a game changer, but anyway.
Also, if i understand correctly, to install Magisk you have to flash some additional img file (product_gsi.img to logical partition, without deleting it), but i installed GSI roms on top already rooted boot img, so that was not necessary - root was found when i installed magisk manager.
Roms that loaded:
SuperiorOS
crDroid-8.5
SparkOS
PixelExperience
CherishOS
Bootloop:
RD-A13
ArrowOS
crDroid-9.0
Excellent ! IIRC all A13 are bootlooping, while A12 are not, or i missread through the name of the roms you tested ?
Did you come from A12 or A11 ? I'm currently on A11, and i'm wondering if direct use of GSI A12 is working
Thank you !
Graveen said:
Excellent ! IIRC all A13 are bootlooping, while A12 are not, or i missread through the name of the roms you tested ?
Did you come from A12 or A11 ? I'm currently on A11, and i'm wondering if direct use of GSI A12 is working
Thank you !
Click to expand...
Click to collapse
All of listed (except CrDroid 8.5 - it is Android 12) are Android 13 GSI roms. And yes, my MIUI is European, so it's Android 11.
keturidu said:
All of listed (except CrDroid 8.5 - it is Android 12) are Android 13 GSI roms. And yes, my MIUI is European, so it's Android 11.
Click to expand...
Click to collapse
Ok, just starting with M4 Pro, i was not aware EU firmware was implying A11 Thank you
I don't understand the difference between fastboot and fastbootd.
Anyone can help me understand ? Thank you ! i can fastboot flash system with fastbootd, while not under fastboot. Is it similar for boot.img ?
Graveen said:
I don't understand the difference between fastboot and fastbootd.
Anyone can help me understand ? Thank you ! i can fastboot flash system with fastbootd, while not under fastboot. Is it similar for boot.img ?
Click to expand...
Click to collapse
fastbootd flashes in a different partition afaik. dont try flashing anything there unless you know what you're doing. Fastboot generally is the answer.
warhead1721972 said:
fastbootd flashes in a different partition afaik. dont try flashing anything there unless you know what you're doing. Fastboot generally is the answer.
Click to expand...
Click to collapse
Thank you. I can't flash system (no such partition) if i'm not in fastbootd. I think there is virtual partition. The script to go back to stock flash a big bloc superseding everything.
Basically, fastboot is only for boot / vbmeta, and once i switch to fastbootd, i can find the correct A/B partition scheme. This is whati discovered while reading the script, but i'm surprised never see this mentionned here (or i did not read enough, or this is something related to recent updates).
But damn. Stock is so bloated, it would benefit an EvoX or RRemix GSI, but there are nice things on MIUI.
Ok, after really painful week trying to adopt MIUI once again, i gave it up and looked seriously at GSI roms. Luckily, newest updated in list was Evolution X. Pixel with some tweaks options. Gave it a try and this time i tried to configure it better to my needs.
So, sluggish performance (scrolling etc.) is gone by enabling "disable HW overlays". I'm not a power user, so didn't notice of faster battery discharge. Installed "Version Green 5000mah/30W" (to be precise, i don't know if it's necessary). Phh treble settings also lets you to repair backlight. Got google camera from another thread.
All in all, much better experience (and visual feeling) than MIUI, even with all miuizers, debloating and 3rd party apps. Android13, no stupid MIUI intrusions into my space, no battery saving policy, that disables my usable apps by random. Easy way to use FNG gestures.
Latest rage i got was when i changed something with tweaks and screen won't turn off by pressing power off button, except from launcher screen. Could not find for several days, what and where i changed. That was last drop that convinced me to go deeper the rabbit hole.