Most cameras have settings for 'shutter' or 'aperture' etc priority. They also have 'full auto' or 'full manual'. Our OEM app is limited to much fewer options, as many phone cam apps are.
To take advantage of the 20mp low light rear lens, you have to (of course) use the manual setting to select that lens, AND select the other (available) settings manually. The reason is that the OEM app AUTO is horrible in this area.
I used the AUTO (iso and shutter) for this pic initially. the result was really bad. The iso was auto set to 6400. It was a terrible low light result, very grainy.
Then I set them manually to iso 200 and shutter at 1/2 sec. You need a steady hand or rest the phone on something, and use the timer, it seems to help. Much much better result. I'd say more than acceptable, quite good.
So this isn't an ideal situation. It's time consuming to determine best settings manually, and some good shots don't wait around for you. But it's worth knowing it can be done.
edit; forgot to mention; I have cam2api, no matter though, it seems the Oem app is not using EIS in this situation anyway, the slightest movement meant significantly out of focus. Another negative for the oem app.
{
"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"
}
I do not think that EIS can be applied while you shoot pictures, it only applies when you record videos (in case of using our camera), nice pic though, very realistic.
Yep. EIS only stabilizes video from frame to frame so it's not applicable for still pics
I can't say that the stock camera app is that bad. In fact, compared to other solutions, it proved to be the less noisy option (after camera 2api, OpenCamera becomes terrible to me. GCAM shows too much dots and other apps, like Lightroom takes very noisy pictures too with A2).
When taking daylight or nightly long exposure, the stock camera app shines brighter to me.
Stock cam app makes too much blurry photos for me, like 5 out of 10 will be blurry or without good details, and it is easier for me to partially or completely remove noise from pictures with some external software then to add details.
kadu20es said:
I can't say that the stock camera app is that bad. In fact, compared to other solutions, it proved to be the less noisy option (after camera 2api, OpenCamera becomes terrible to me. GCAM shows too much dots and other apps, like Lightroom takes very noisy pictures too with A2).
When taking daylight or nightly long exposure, the stock camera app shines brighter to me.
Click to expand...
Click to collapse
Oh I agree, the oem app does a very good job in daylight, or manually adjusted exposure time low light.
But the 'auto' settings for low to medium lighting could be better. The Gcam port I have consistently uses a lower iso and longer exposure, using 'auto', then does the oem app under the same conditions.
Part of my reason for the post though is that the rear 20mp lens is much maligned. I think most of that reason is the oem app though, and it's faulty exposure values especially show up with the low light lens, although it's advertised for that scenario. But it turns out to do worse!
It's not the lens though, it's the app.
I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.
ki69 said:
I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.
Click to expand...
Click to collapse
Hey pal, I'm the noobest of the noobs from here, and still, I followed the tutorial and BAM! Got camera2API working.
I tried many times the Majisk with no success. Everytime I rebooted the device the module was gone and I had to patch and do everything again (and even got bootloop when tried to remove majisk), so I gave a chance to TWRP and it worked like a charm.
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
kadu20es said:
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
If you did not mess with any system files, and enabled camera2 over adb shell, you will have working OTA. :good:
kadu20es said:
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
minnuss said:
If you did not mess with any system files, and enabled camera2 over adb shell, you will have working OTA. :good:
Click to expand...
Click to collapse
I can report, Oct update applied, no issues. Cam2api still enabled
AsItLies said:
I can report, Oct update applied, no issues. Cam2api still enabled
Click to expand...
Click to collapse
Unfortunately didn't work for me.
Maybe I need to flash stock image and try again.
Or wait for Pie.
kadu20es said:
Hey pal, I'm the noobest of the noobs from here, and still, I followed the tutorial and BAM! Got camera2API working.
I tried many times the Majisk with no success. Everytime I rebooted the device the module was gone and I had to patch and do everything again (and even got bootloop when tried to remove majisk), so I gave a chance to TWRP and it worked like a charm.
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
For now i will not install the october update and wait to see if is released a new TWRP. I really want to enable camera2api. ( man installing Remix Firmwares in My xperia M dual was so more easy than just unlock bootloder and enable camera2api in this Xiaomi...)
ki69 said:
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
For now i will not install the october update and wait to see if is released a new TWRP. I really want to enable camera2api. ( man installing Remix Firmwares in My xperia M dual was so more easy than just unlock bootloder and enable camera2api in this Xiaomi...)
Click to expand...
Click to collapse
No no, I followed this one:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
For now, I think I'll wait for Pie. Maybe there's not thaaaat difference of x.x.6.13.
kadu20es said:
No no, I followed this one:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
For now, I think I'll wait for Pie. Maybe there's not thaaaat difference of x.x.6.13.
Click to expand...
Click to collapse
you put the same guide that i mention.
ki69 said:
you put the same guide that i mention.
Click to expand...
Click to collapse
Ops! Sorry
ki69 said:
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
...
Click to expand...
Click to collapse
Worked, I finally installed the update, however, in order to work, I had to flash boot.img and system.img.
The camera2api is still working after flashing and after update.:good:
kadu20es said:
Worked, I finally installed the update, however, in order to work, I had to flash boot.img and system.img.
The camera2api is still working after flashing and after update.:good:
Click to expand...
Click to collapse
That only means that they enable it by default in October update, I will confirm this today, because my brother has the same stock LOCKED Mi A2
EDIT: Nope, they did not enabled Camera2 by default !!! Just checked and confirmed.
How can u set iso 6400. The maximum limit is 3200 ??
ki69 said:
I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.
Click to expand...
Click to collapse
+1
schubeir said:
+1
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
After my post i use this guide and i´ve got Camera2api and all the OTa updates without root, only with bootloader unlocked.
Related
Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
StrangerWeather said:
Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?
Click to expand...
Click to collapse
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.
L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)
simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.
I'm on B132, is there a quick way to upgrade to B370? I've tried hi-care app but says no updates
Thanks
simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
sirjohnrl said:
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.
Click to expand...
Click to collapse
bghyt said:
L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)
Click to expand...
Click to collapse
Potato997 said:
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.
Click to expand...
Click to collapse
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...
StrangerWeather said:
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...
Click to expand...
Click to collapse
I updated to B370 but had to downgrade to mm because my camera wasn't working, but overall it was a great experience. Can't wait to get an update where my camera works.
Sent from my HUAWEI VNS-L31 using Tapatalk
I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly
JaccaPL said:
I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly
Click to expand...
Click to collapse
+1
I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone
kourkoubas1981 said:
I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone
Click to expand...
Click to collapse
Try the TWRP method.
zgomot said:
Try the TWRP method.
Click to expand...
Click to collapse
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
It's really not all that difficult and there are several guides around here. Unlocking the bootloader and rooting MM is pretty much without risks. I'd say go for it.
kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Looks like there is a majority of successful upgrades after all!
Well I did an upgrade and although at first I thought I 'borked it' - the build I have is 'NRD90M test-keys'
But I have to say after manually installing google keyboard and getting a few play store updates installed, it feels like an absolute rocket compared to the old EE B132 version
StrangerWeather said:
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Click to expand...
Click to collapse
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system
kourkoubas1981 said:
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system
Click to expand...
Click to collapse
Did you flash both files?
StrangerWeather said:
Did you flash both files?
Click to expand...
Click to collapse
If he made the same mistake as me then he didn't flash the second file, doh!:silly:
i'm thinking of trying to get twrp back on and having another go......
WARNING: Carriers in the US are shutting down 3G networks. This ROM does not have VoLTE capability at this time, so calls will not be sent or received if your carrier has disabled 3G.
If you are in the US and wish to use this ROM, please check your carrier's 3G support and if there are any dates set for a 3G shutdown. If you are outside the US, this is unlikely to affect you, but do a google search anyway.
At the time of writing this disclaimer (March 18, 2022) AT&T has already disabled 3G and T-Mobile will shut down 3G networks for prior sprint users by the end of the month.
{
"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"
}
LineageOS 18.1 (Android 11) for US LG G8 (G820*)
LineageOS (also known as “Lineage”) is a free and open-source operating system based on Android. It is the successor to the custom ROM CyanogenMod.
Code:
#include "std_disclaimer.h"
/*
* 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 features included in this ROM
* before flashing it! 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 unofficial build of Lineageos 18.1 (Android 11) for the US LG G8.
THIS IS NOT A GSI
This works on all carriers!
This will only work for the US LG G8.
This will only work for alphalm, not alphaplus.
This will not work on the 'G8s' or the 'G8x'.
This will not work on Korean models.
YOU HAVE BEEN WARNED.
Partition Backup:
Please backup all important partitions and data before installing this ROM. THis is very important for certain carriers including AT&T, as they do not provide the KDZ firmware files, so once you install lineage, you may not easily be able to go back if you haven't made a backup, though it's a good idea for anyone attempting to install any ROM on any device.
Important partitions are:
boot
product
vendor
dtbo
vbmeta
system
Make a backup of these in QFIL (both _a and _b slots of each, You will need to use QFIL during the following bootloader unlock guide so you can make this backup during that process.
Bootloader Must Be Unlocked
There's a guide for this linked below. This step is a must.
This must be installed from TWRP or other custom recovery on stock.
Please make sure latest stock firmware is installed. This may not be completely
necessary, but having an old firmware image installed has caused me
issues with call audio and such while developing this ROM.
What Works
Bluetooth
Wifi
Call/SMS (WARNING: Carriers in the US and perhaps other countries are disabling 3G, so no more calls and possibly even texts if this happens with your carrier!)
Data 2G/3G/LTE
Camera (GCam is required for wide angle back camera)
Audio
NFC
GPay Contactless Payments (Requires Magisk Hide)
Hotspot
Google Assistant Voice Match
Nearly Everything!
What Doesn't Work
VoLTE/VoWiFi/IMS - LG has a complicated proprietary IMS, so no VoLTE at all!
Assistant Voice Match while screen is off
AOD (I'm working on this)
Please let me know in the comments
Requirements
US LG G8 on any carrier
Latest firmware installed on device (may work with older firmware but results will vary)
Latest unofficial LineageOS zip (on github, linked in thread) and TWRP zip (attached to thread)
SD Card or adb for sideloading (see step 5)
PC with Windows (Linux is possible if you know what you're doing. Check out bkerler/edl on github, it works the same way as QFIL, but requires a small amount of Linux knowledge/experience.)
How to install
Unlock Bootloader and root with Magisk (Follow guide linked below)
Make a backup of all your data (I strongly recommend making a backup of your partitions with qfil (or EDL for linux users))
Download TWRP and the Lineage zip
Installl TWRP (Follow quick guide in attached archive)
Place Lineage zip and anything you want to install through recovery on external SD card (Can also be sideloaded with 'adb sideload', If so, skip this step)
Boot into TWRP or other custom recovery with volume and power shortcut
Install Lineage zip from sdcard or sideload (I always recommend sd, there's less to go wrong)
Once it completes, reboot into recovery again. There's an option for this in TWRP to skip the button combo. TWRP IS GONE. YOU WILL BOOT INTO LINEAGE RECOVERY. USE THIS FOR REMAINING STEPS.
Format Data (This is completely necessary. You will be returned to recovery on boot if you do not follow this step.)
Install Gapps, Magisk, and anything else from sd or with adb sideload. (If you don't want/need root, you can skip installing Magisk
Format Data Again (System will send you back to recovery to do it if you don't)
Reboot to system and enjoy!
A big thanks to SGCMarkus for everything he has done for LG devices on this platform. This wouldn't be possible without his work. Go buy him a coffee or something!
Big thanks to those I haven't named from the V50 G8 G8s Telegram group as well
Other Credits
J0SH1X
enforc
Links
Guide For Unlocking Bootloader
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose posted by Seasee606
GCam For Wide Angle Back Camera
GCam Hub MGC_8.1.101_A9_PV0i
Go to this link and download MGC_8.1.101_A9_PV0i_libs_MGC.apk
Others will work, but some not as well. I've noticed some issues with this version crashing. If you experience this, try other versions from the link above.
GApps
Only install GApps packages for Android 11!
NikGApps
Highly recommended. (Because I use it and I know it works, it doesn't necessarily mean it's best though.) Follow download buttons. Go to Releases > NikGapps-R. Packages will be here. Info about what each package contains is on the page linked above.
MindTheGApps
I've tried this once and It seemed alright, but it was a little minimal for my taste. It's linked by LineageOS so it's here.
OpenGapps
I haven't tried this at all, but it's also linked by LineageOS so it should be here.
Download
Release: LineageOS 18.1
Release Date: 2021-10-13
MD5: 8e63d765ea7fe90c6fe9ebf4975c2a35
Filename: lineage-18.1-20211013-UNOFFICIAL-alphalm-signed.zip
Size: 908 MB (951854628 B)
Device: LM-G820 USA
Android Version: 11
Download from Github
Release Page
Sources / Device Tree
https://github.com/xmusjackson/android_device_lge_alpha-common
https://github.com/xmusjackson/android_device_lge_alphalm
https://github.com/xmusjackson/android_device_lge_sm8150-common
https://github.com/SGCMarkus/android_device_lge_common/tree/76432f76c5994bd1033d01150433f081a8c6dee3
https://github.com/xmusjackson/android_kernel_lge_sm8150
https://github.com/SGCMarkus/android_hardware_lge/tree/64bef53ae00f0496e35bc59a61a07ad40537d706
https://github.com/xmusjackson/proprietary_vendor_lge_alpha
Screenshots
Spoiler: Screenshots
Screenshots from LM-G820QM7 (Open US)
Attached is a copy of the archive containing TWRP for the G8. I downloaded this from telegram and take no credits, there just isn't a thread about this here that I've seen. The instructions to install are included in the archive.
Please let me know of any bugs in the comments!
Thanks!
Downgrading and Crossflashing
This ROM requires your device to be on stock Android 10. Downgrading may be necessary, with some devices requiring a crossflash for the process!
Crossflashing
Crossflashing is only for those who own a G8 from a carrier that doesn't provide a KDZ (firmware image). There is no practical purpose to crossflash unless you really don't want the carrier bloatware, but there are easier ways to remove this.
There is a guide for crossflashing Here.
I haven't tried to crossflash personally but I've seen much success. The G8/G8X/v50 Telegram group (specifically the notes there) can definitely be a lot of help to anyone with an AT&T or Sprint G8 that wishes to go this route.
Downgrading
First, you have to download the appropriate firmware. You can select your preferred firmware here:
https://lg-firmwares.com/lg-lmg820qm-firmwares/
but this one is for the openus model and should work for sprint and at&t models:
https://lg-firmwares.com/downloads-file/25195/G820QM20f_00_NAO_US_OP_0402
Second, you have to use LGUP with some slight modifications to flash the firmware to your device.
NOTE: This works without an unlocked bootloader and will relock the bootloader on your device. If you've unlocked your bootloader previously, you'll have to repeat the process.
Here is a brief guide for downgrading taken from this post:
(DO NOT FOLLOW THIS GUIDE IF YOU NEED TO CROSSFLASH)
Quote from TheLoonyRebel:
...
And here's the software you will need to get the job done:
https://www.androidfilehost.com/?fid=8889791610682884898
1. Install the LG drivers if you haven't already.
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
2. Install LG Up
3. Install the LG Common DLL
4. Copy the UI confilg files to C:\Program Files (x86)\LG Electronics\LGUP\model\Common
5. Turn off the G8.
6. Once off hold up volume up then insert your USB into the phone.
7. Open LG Up. If you get an error message ignore.
8. Select REFURBISH in LG Up
9. Load the KDZ file by drag and drop where it says BIN file
10. Click start
11. Once the downgrade is done installing the phone will reboot...
...
Click to expand...
Click to collapse
Do not follow the bootloader unlock method in that thread as it will fail miserably and soft brick your phone, only follow the downgrade method quoted above.
If there are any questions, please ask in the comments.
Edit: I've attached the necessary files in case that androidfilehost link becomes dead in the future.
Thank you for your efforts!
Can i install rom for G820N Korea ?
Can you help me fix vibration for G820N ?
I using Los gsi rom but my phone hadn't vibration
minhthien0711 said:
Can i install rom for G820N Korea ?
Can you help me fix vibration for G820N ?
I using Los gsi rom but my phone hadn't vibration
Click to expand...
Click to collapse
I don't think this rom would work on your device, but I could be wrong. Either way, I do not recommend trying it. Also, I've never used a GSI but I've heard they're buggy in general.
After two days of use, I found that the functions of always on display are abnormal, and the side Google buttons cannot be customized
lufan said:
After two days of use, I found that the functions of always on display are abnormal, and the side Google buttons cannot be customized
Click to expand...
Click to collapse
There's a feature in Lineage called Ambient Display, alongside AOD. It's hard to find in settings, but if you go to your quick settings tiles and tap the edit button, there will be a tile for Ambient Display to add. Disabling this made the display behave more normally for me.
If this does not fix your problem, please elaborate
As for the side Google buttons, I'm not sure what you're referring to, please be more specific.
Thank you for your efforts!
I was about to get rid of my Sprint G8 for not receiving any software updates for half a year haha
Edit: Just installed and its working flawlessly on Sprint G8
Thank you!
I tested MindTheGapps, contacts and calendar couldn't sync, because google play service had no rights.
Just set the rights, it's perfect.
cheger32 said:
There's a feature in Lineage called Ambient Display, alongside AOD. It's hard to find in settings, but if you go to your quick settings tiles and tap the edit button, there will be a tile for Ambient Display to add. Disabling this made the display behave more normally for me.
If this does not fix your problem, please elaborate
As for the side Google buttons, I'm not sure what you're referring to, please be more specific.
Click to expand...
Click to collapse
Thank you for your reply. I tried to turn off ambient display and turn on AOD. After locking the screen, AOD information will be displayed for a second or two, then flash once and disappear
lufan said:
Thank you for your reply. I tried to turn off ambient display and turn on AOD. After locking the screen, AOD information will be displayed for a second or two, then flash once and disappear
Click to expand...
Click to collapse
It seems this is a bug. I will look into it and add it to the list. Thanks.
First of all Thank you for your great work you saved the life of my Lg G8, so I will tell my experience after 3 days of use, deactivate everything that would have to do with the AOD because it is not working correctly even though in my case It is not essential, the ROM is really smooth and everything else works correctly, I am using it with Open GApps and it has not given me problems, the truth is the ROM is on the right track, but I only had a problem and it is time to playing the device hangs it stays bibrando until it forces the closing of the app, it does not always do it but when it happens annoying, I also feel that it does not go so fluid in the games compared to the stock, but it is nothing serious perhaps with a better kernel you can get more out of the ROM but for the moment it is a great advance for the LG G8 and again Thanks for your work!.
Thank you for taking the time for making this ROM OP! Will install later today and report back.
I disabled time sync, reboot. System time back to compile time.
starboi4eva said:
Thank you for taking the time for making this ROM OP! Will install later today and report back.
Click to expand...
Click to collapse
Been using this rom for two days and it is amazing. Fast and barely any issues apart from what is mentioned above. My only personal gripe is the slight drop in gaming performance than stock.
hi. can i do this with lg lmg820um Android 9 pie version. I will be glad if you answer
Alrighty, So I've been using the ROM for 2 days and I have a minor grievance with the OS itself which I'm sure is out of your control, Wallpaper zoom is incredibly annoying and the most common work around is an app called KLWP which is compatible with stock rom but not this one. My current solution is an app called SB Wallpaper Changer, under portrait setting it to single and Fixed, fixes the problem. But this breaks any system function that bases colors on the wallpapers color.
That all being said TYVM OP, stock rom on my device was falling apart at the seams, and while it may have taken me 15 hours to get LOS working it's ages better than stock.
Also edit: MY Phone was a Model LM-G820TM but reported as a 850UM in LG Bridge, don't even wanna know why. Android Reports LM-G820 after unlock and LOS
orkhan96 said:
hi. can i do this with lg lmg820um Android 9 pie version. I will be glad if you answer
Click to expand...
Click to collapse
I don't think this would work. Your device's firmware should be updated to android 10. The ROM does not install this, it is retained from original stock ROM. This would probably result in a brick.
Ok so I'm about a week in, the fingerprint scanner is just, gone. It's not that it isn't reading, it's just not an option. The fingerprint scanner is completely gone from the system settings, any attempt to communicate with it fail immediately. it just, disapeared from the software. Restarting or factory reseting didn't do anything, it's still gone.
Edit: Gonna try and go through recover to update then reflash if needed, pain
Edit 2: reflashed, still gone
Skye_h said:
Ok so I'm about a week in, the fingerprint scanner is just, gone. It's not that it isn't reading, it's just not an option. The fingerprint scanner is completely gone from the system settings, any attempt to communicate with it fail immediately. it just, disapeared from the software. Restarting or factory reseting didn't do anything, it's still gone.
Edit: Gonna try and go through recover to update then reflash if needed, pain
Edit 2: reflashed, still gone
Click to expand...
Click to collapse
How strange I have been for 2 weeks and I still have not had that problem in relation to fingerprints, will the sensor of your device have been damaged?
Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards
hello
in first you need the right dongrading firmware for yoyr device :from asus server :
exemple :
{
"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"
}
firmware must be in root or sd card and follow step 3 here:
GUIDE: How to unbrick your Zenfone 6 (ZS630KL)
Hello. This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like. Note: Unlocked bootloader is not required to do any of the actions...
forum.xda-developers.com
regards
I have a correct firmware .zip file in root path however in Android Fasboot menu I have only following options:
- Reboot system now
- Enter recovery (it just takes back to the previosu menu)
- Reboot to bootloader
- Power off
How to use command adb reboot recovery without using a computer (as stated in first post)?
so maybe you have one of the lastest andoid 12 version and now you can't downgrade
if we don't know which version you have and you try to downgrade it's very hard to help you
My current firmware version is 31.1010.0410.72
I'm trying to downgrade by flashing firmware that is visible in the screenshot in post #2
I have the same problem, A12 firmware version is 31.1010.0410.72 , the phone doesn't pop up a message which detected a firmware update info.
maybe also interesting
(in recoverymode only :
Reboot system now
Reboot to bootloader
Enter fastboot
Wipe data/Factory reset
Run graphics test
Power off)
I do have a PC and adb
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link
eboelens said:
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link
Click to expand...
Click to collapse
Hi
yes , I did that and it worked
But keep in mind that the script used to downgrade will delete ALL files on your phone.
And as far as I know there is no other way to downgrade the OS from 12 to 11.
regards
Bernd
Thanks,
1.can you tell me when you did that that the bootloader was untouched and locked ?
2.can I do something wrong ?
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
4. I want install /e/ on it , /e/ expect A11 on it
I'm still scared:
I get an answer from Asus:
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
I will check internally for you what the possibilities are, but keep in mind that there is a chance that we no longer offer a downgrade for this version of Android 12.
Hi
1. can you tell me when you did that that the bootloader was untouched and locked ?
Click to expand...
Click to collapse
As far as I know the bootloader is not touched (I'm not sure if downgrading via that script works with a locked bootloader - but I did not test that)
2.can I do something wrong ?
Click to expand...
Click to collapse
Well, there is always the change that something goes wrong doing this kind of stuff. But regarding the script the only thing you do is starting the script - the script will execute all neccessary steps for the downgrade without user intervention and will only ask for confirmation for the last reboot from the new installed Android 11
But if the script fails for whatever reason you should know how to fix this kind of error before using it.
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
Click to expand...
Click to collapse
As far as I know you can not downgrade using the standard installation via TWRP or any other recovery ROM (but that might be wrong - you can try it before using the script ...)
4. I want install /e/ on it , /e/ expect A11 on it
Click to expand...
Click to collapse
I never tested that OS, probably you should wait for an A12 based version of the OS.
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
Click to expand...
Click to collapse
The installation of Android 11 here is only to prepare the phone for another Android 11 based distribution as far as I understand so this can be ignored. But if you stay on the original ASUS Android 11 you should update the OS to the latest version of Android 11 released by ASUS after downgrading.
regards
Bernd
sqfaaa said:
Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards
Click to expand...
Click to collapse
Yes, the instructions state to download the zip file into the root directory and wait for a few min after rebooting preferably, no need to unzip. However, the person uploading the files seem to be mixing up the file name format for various devices. You need to check which format is compatible for your device : UL-ASUS_I006D-ASUS or UL-I006D-ASUS. The file name has to be EXACT for the update for upgrade or downgrade to TRIGGER. Hope that helps.
Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.
Jgruar said:
Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.
Click to expand...
Click to collapse
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.
maxsterling said:
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.
Click to expand...
Click to collapse
It seems wanting to root your phones is harder and more inconvenient every year. It should really be a simple process that simply allows you to decide what is running or installed on your phone. I can understand the security implications, but that should be all be dealt with a disclaimer. It is now your responsibility to make sure you don't allow shady programs root access, that's it.
With every new phone I get it's more convoluted, there are less roms available, less people on the forums. Driven to extinction because god damned the manufactures don't care about you after they get your money.
Well anyway, my reason was simply that I really really dislike the UI in 12. Doesn't sit well with me at all, and can't get used to it.
I know I'm making things difficult for me but I refuse to accept that garbage and if I want to run 11 for the time being I should be able to. It's the principle.
I'm going to have to root in the end, but just for now I wanted to test drive the phone without too much work if it's going back.
@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).
sqfaaa said:
@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).
Click to expand...
Click to collapse
Hi
the instructions from the Beta Website will only work if the phone is connected via USB and booted into the bootloader (=fastboot mode).
USB debugging on or off should be irrelevant for this action (I did the reinstallation using this method with and without USB debugging enabled)
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
bnsmb said:
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd
Click to expand...
Click to collapse
I haven't unlocked and did the downgrade through fastboot mode with the A11 image file and instructions from ASUS beta program. If they provide the image freely and don't mention anything about voiding the warranty it has to work without unlocking. Just had to make sure my usb connection was stable, had a problem of corruption during install with one cable.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Make sure your device is visible to the computer (fastboot devices) and is in the fastbootd mode (like in your 1st picture).
You then should be able to excecute the "update_image.bat" file from the package, but I used "update_all.bat". Not exactly sure what the difference is, but someone at some post said to use that. I think the update_image.bat would have worked fine if I had a stable usb connection at the time.
Male sure to disable the update service via the method I posted, or else the Android 11 version will force an install of A12 as soon as it gets a network connection.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
HI
see the other reply - it seems to work without unlocking ( I did not test this -- all my phones are unlocked)
regards
Bernd
Thanks.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.
sqfaaa said:
Thanks.
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.
Click to expand...
Click to collapse
>>Neither of those modes is correct. For me mode from the below screenshot worked.
That 's the bootloader (with fastboot support)
regards
Bernd
As the title states, my auto brightness, compass and proximity sensors are all broken, I believe this is a failure of a partition similar to persist.img where the fingerprint used to be stored.
Had this issue a while back but I hadn't noticed the compass being broken
I've ran through the tests in engineer mode *#*#4636#*#* and the results are all null for the above sensors.
Factory wipe did nothing, moving between bases 12-13 did nothing, installing a GSI only affected only system.
I'd rather not RMA if I don't have to..
Any ideas anyone??
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
g96818 said:
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
Click to expand...
Click to collapse
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
dladz said:
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
Click to expand...
Click to collapse
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
g96818 said:
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
Click to expand...
Click to collapse
Have you used fastboot enhance to flash a rom?
AFAIK it's just a case of deleting the cows then extracting the payload then flashing it in fastbootd
I think the partition needs nuking then rebuilding.
On the 8 pro they used MSM, different ROMs and and fastboot, nothing worked.
Have you any idea where these sensors information is stored? What partition?
Anyone else have any idea?
Finding out where the proximity, compass and auto brightness sensor data is kept would help me
Answered my own question.
It is indeed within the persist partition.
How to Fix Android 10’s Sensors Bug Caused by Corrupted Persist Partition
A step-by-step guide on how to fix the Android 10 Sensors bug caused by corrupted Persist partition, on devices like Google Pixel, Xiaomi Mi A3, and others.
www.thecustomdroid.com
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
dladz said:
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
Click to expand...
Click to collapse
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
g96818 said:
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
Click to expand...
Click to collapse
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
dladz said:
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
Click to expand...
Click to collapse
yea it sucks, especially since oppo isn't releasing the msm tools.
hope the file works for you. it came out of my A.10 rom. hopefully A.10 shared more files than just the boot image.
It flashed and did affect the fingerprint but unfortunately didn't fix the other sensors.
Restored mine and my FP is working again but all other sensors are broken.
I think RMA is the only way at this point.
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
dladz said:
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
Click to expand...
Click to collapse
It didn't..
dladz said:
It didn't..
Click to expand...
Click to collapse
were you able to solve the problem?
crhistiandavidbonilla47 said:
were you able to solve the problem?
Click to expand...
Click to collapse
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
dladz said:
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
Click to expand...
Click to collapse
without a doubt my worst purchase was this device
crhistiandavidbonilla47 said:
without a doubt my worst purchase was this device
Click to expand...
Click to collapse
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
dladz said:
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
Click to expand...
Click to collapse
Yeah, you are right
{
"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"
}
So? Did it finish? It's your Pixel "better" now?
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher. Download the files here:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
And use PF...
Releases · badabing2005/PixelFlasher
Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.
github.com
No waiting for hours on the OTA, all work on PC, only dl time for the big files.
justDave said:
So? Did it finish? It's your Pixel "better" now?
Click to expand...
Click to collapse
Lol, I never see a difference
t-ryder said:
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher.
Click to expand...
Click to collapse
Pixel Flasher only works with unlocked bootloaders though.
justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
You can sideload the Full OTA with a locked bootloader with Pixel Flasher.
justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
IDK, but last time I offered a handful of Pixel owners a workaround that needed root (or at least an unlocked bootloader), I got no takers.
ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
Couldn't agree more. The ease of unlocking, flashing, rooting etc without warranty implications is my favorite Pixel feature.
gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher
simplepinoi177 said:
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher
Click to expand...
Click to collapse
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.
Does this update fix the AVRCP issues with this phone's bluetooth?
t-ryder said:
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.
Click to expand...
Click to collapse
exactly...
honestly...most of that "under 20 minutes" stuff is downloading the 2.6GB image, extracting it, copying it over to the platform-tools folder....
and that's me doing everything manually; i've never used PixelFlasher, but I imagine badabing2003 streamlined it so the GUI/program just points to the image files than needing it to be in the same folder....
Before I convinced my wife to allow me to root her P7P, I did the real OTA once with it and it was nails on a chalkboard as I was manually flashing my rooted P7P -- again, not that one needs a rooted device to sideload an OTA; which is still considerably faster than using the stock System Update...
Still haven't received the OTA update.
Pixel 7, purchased from Google, on AT&T.
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?
justDave said:
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?
Click to expand...
Click to collapse
It was GrapheneOS OTA of course =) , but update content is the same (QT3A)
Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Magisk works fine on June stock update.
Lughnasadh said:
Magisk works fine on June stock update.
Click to expand...
Click to collapse
Thanks.
Since it's a GrapheneOS specific issue, I started my own thread.