So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.
Related
Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:
Somebody successfully flashed it ? It works ?
raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.
Anyone tried 20150119 build yet? is it working??
CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small
on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app
You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:
Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/
Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.
Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?
Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
It is AOSP based compared to LOS (CM) which the majority of the ROMs posted are.
DU is a great ROM. I found that it lacked some important features that I like, but a very solid ROM.
Yes i tried on Sprint but there was no data...even after entering the apn in
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
Encryption was not working, even with a full data format prior to flashing.
Any other opinions?
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
errikosd said:
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
Click to expand...
Click to collapse
It comes WITHOUT root. So you can choose your preffered method or no root at all.
I don't know about safetynet as I am not using android pay or anything that relies on it to pass.
Also I have not had any encryption issues as someone earlier replied
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Scutariu said:
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Click to expand...
Click to collapse
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
mrrflagg said:
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
Click to expand...
Click to collapse
I've tried several combinations, with older/latest firmware.
Every time, It would ask for the encryption password on bootup.
Even if I haven't set one up.. With data format prior to installing
Anyway, got sick of re-setting apps on my phone, just installed Maximus HD ROM, and that's that ?
Dirty Unicorns
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
I think it was the DU team's decision to close all and not allow any XDA threads. Someone correct me if I am wrong.
No idea why though.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Encryption
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
I have had that happen when switching from a sense based ROM to LOS or AOSP and it's a "pita"... Anything that I want to keep gets moved to my SD card before I reboot to recovery.
I read through several threads and tried several possible solutions so I can't remember exactly which one worked.
I am currently on Verizon, official Nougat with the flashed us unlocked "patch", TWRP 3.1.0-1. If you are on Verizon or Sprint you need to patch the image with a missing image that is found in the us unlocked model (there are threads discussing it where you can find the file).
LOS
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Here is another thread on twrp issues
https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438
morr22066 said:
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Click to expand...
Click to collapse
It was not related to the data partition.
The format user data was done prior and after flashing it.
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
errikosd said:
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
Click to expand...
Click to collapse
Yea I'm having that sane problem with the touch key lights not working n it bothers me a bit. I didn't notice if the led was working or not. Keep me posted if u figure out the the key problem plz.
HUGE thanks to @giri45 for actually providing the fix!
What's this?
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted
PE 9.0LOG is attached
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment
JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)
Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?
Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?
JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.
Working flawlessly on crDroid 9.
Thank you devs!
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands
Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.
I saw the link on AFH and it has been downloaded 67 times and I have never seen this rom before and was wondering if anyone knew anything about it for instance is it pie or android 10, what source it was bulit from etc.... Any info would be appreciated Thanks.
It's a degoogled offshoot of lineage 16 with microG included. It's a bit different, Similar to cosp without gapps. Something to play around with while we wait for a10 ROMs
Edmontonchef said:
It's a degoogled offshoot of lineage 16 with microG included. It's a bit different, Similar to cosp without gapps. Something to play around with while we wait for a10 ROMs
Click to expand...
Click to collapse
Have you flashed it? If yes then what factory img were you on in order to get it to boot properly,Thanks
bigmarv31 said:
Have you flashed it? If yes then what factory img were you on in order to get it to boot properly,Thanks
Click to expand...
Click to collapse
I was on August 9.0 I flashed nano gapps after rebooting twrp and it booted up. Didn't try without yet.
Hi! today i was thinking to post some gsi i used
1: Pixel Experience (https://forum.xda-developers.com/t/gsi-unofficial-12-pixel-experience.4354695/)
Android 12, i had a very nice experience. All the GApps, nice customization. 10/10
2: CrDroid (https://forum.xda-developers.com/t/rom-12-0-crdroid-8-official-miui-cam-included.4387221/)
Also nice, but no GApps 8.1/10
3: Caos: (https://forum.xda-developers.com/t/caos11-project-aosp-based-on-october-build.4338637/)
Also no GApps, but i saw that is AlwaysOnDisplay which was nice, since i use it very much
!!This is my personal opinion, no hate to anyone!!
(To mention, my phone has an problem, because hotspot and headphones won't work, anyone has an ideea what is the problem?)
Thanks for looking, hope i was helpful in finding something new for your phone.
Cheers!
How did you install these GSI I'm starting now, thanks
CallMeNico said:
Hi! today i was thinking to post some gsi i used
1: Pixel Experience (https://forum.xda-developers.com/t/gsi-unofficial-12-pixel-experience.4354695/)
Android 12, i had a very nice experience. All the GApps, nice customization. 10/10
2: CrDroid (https://forum.xda-developers.com/t/rom-12-0-crdroid-8-official-miui-cam-included.4387221/)
Also nice, but no GApps 8.1/10
3: Caos: (https://forum.xda-developers.com/t/caos11-project-aosp-based-on-october-build.4338637/)
Also no GApps, but i saw that is AlwaysOnDisplay which was nice, since i use it very much
!!This is my personal opinion, no hate to anyone!!
(To mention, my phone has an problem, because hotspot and headphones won't work, anyone has an ideea what is the problem?)
Thanks for looking, hope i was helpful in finding something new for your phone.
Cheers!
Click to expand...
Click to collapse
How did you install these GSI I'm starting now, thanks
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A22 SM-a225F/a225M Android 11+12
UPDATE Flash at your own Risk !!! Tested Working: Backup Flash zip Fastbootd support Flash gsi roms Not Working: Usb Otg You tell me How to Flash on Android 11 1. Reboot Device to Downloadmode 2. Unlock Bootloader 3. Install adb and...
forum.xda-developers.com
Here is a guide
Proximity sensor is broken on any GSI roms. Anyone is able to fix it? Did I flashed something wrong?
Rolimlucas said:
Proximity sensor is broken on any GSI roms. Anyone is able to fix it? Did I flashed something wrong?
Click to expand...
Click to collapse
Hi, the same thing is happening to me, could you find a solution?
dtlucillek20 said:
Hi, the same thing is happening to me, could you find a solution?
Click to expand...
Click to collapse
No, I couldn't find any fix or anybody who could help me. So I moved to stock ROM and rooted it