Database Info

CyanogenMod 12 for HTC One XL (Evita)

CyanogenMod 12.0 is a free, community built distribution of Android 5.0 (LolliPop) which greatly extends the capabilities of your phone.
This is the official Nightly Build of CM12.0 for the AT&T HTC One XL.
To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
Code:
#include
/*
* 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.
*/
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
Update to latest 5.18 OTA firmware
Flash a custom recovery (TWRP/CWM with SELinux capabilities).
Download latest nightly from http://download.cyanogenmod.org/?device=evita.
Locate 5.0 Gapps via a quick Google search.
Wipe factory/data reset in recovery before installing CM12.0 (unless you are already on a CM12.0 build).
Reboot into recovery and install nightly and gapps.
List all Questions and Off-Topic discussions here
Huge thanks:
h8rift,intervigil, deck, mdmower, invisiblek, flyhalf205 - Great team to work with for the HTC MSM8960 device family.
XDA:DevDB Information
CM12.0 Official, ROM for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: hboot 2.14 or higher
Version Information
Status: Nightly
Created 2015-01-07
Last Updated 2015-01-07

Fantastic! Nice to see some official support still going on for this device.
Have the limited space issues with ART been worked around at all? I've been wanting to use 5.0 but I have too many apps and run into problems storage-wise on ART which is the only option now on Lollipop. I know devs on many phones/tablets have switched to a unified partition layout to circumvent increasing OS and app sizes. Is that possible here?
Thanks for all your work!

Not working SMS and Dialer
It's fantastic news, all works properly and very smooth, BUT:
When I want to cancel call - Dialer app freezes at calling state with missed finish call button. And when i want to send SMS "send" button is inactive.
Latest nightly - cm-12-20150107-NIGHTLY-evita.zip, HBOOT 2.15, RADIO - 1.31a.32.45.16_2

ThisWasATriumph said:
Fantastic! Nice to see some official support still going on for this device.
Have the limited space issues with ART been worked around at all? I've been wanting to use 5.0 but I have too many apps and run into problems storage-wise on ART which is the only option now on Lollipop. I know devs on many phones/tablets have switched to a unified partition layout to circumvent increasing OS and app sizes. Is that possible here?
Thanks for all your work!
Click to expand...
Click to collapse
There's not much we can do because Evita never got the update to the /data/media/ sdcard layout like jewel/ville got.
However app2sd is native now and can move a goof portion of some(but not all) apps over to your internal sdcatd partition which should help some. Any app2sd app from market can show you what apps can move and its also available in the systems app manager pictured below
{
"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"
}

Phone stuck at Cyanogen logo
I tried to install CM12. I am coming from CM11. Can anyone tell me why my phone is stuck at boot logo. I am using the same recovery i used for CM11, unofficial TWRP 2.8.

sanimagus said:
I tried to install CM12. I am coming from CM11. Can anyone tell me why my phone is stuck at boot logo. I am using the same recovery i used for CM11, unofficial TWRP 2.8.
Click to expand...
Click to collapse
If this is your first foray into 5.0 lollipop land expect first boot to take 15-20 mins or so. Be patient. Also I'm grabbing the official build now just to confirm no wonk creeped in overnight.

jrior001 said:
If this is your first foray into 5.0 lollipop land expect first boot to take 15-20 mins or so. Be patient. Also I'm grabbing the official build now just to confirm no wonk creeped in overnight.
Click to expand...
Click to collapse
Thanks jrior001. I held the power button for a few seconds and it came out of the boot screen into system.

niihelium said:
It's fantastic news, all works properly and very smooth, BUT:
When I want to cancel call - Dialer app freezes at calling state with missed finish call button. And when i want to send SMS "send" button is inactive.
Latest nightly - cm-12-20150107-NIGHTLY-evita.zip, HBOOT 2.15, RADIO - 1.31a.32.45.16_2
Click to expand...
Click to collapse
Is anyone else having this problem with the 1/7 nightly?

droydr said:
Is anyone else having this problem with the 1/7 nightly?
Click to expand...
Click to collapse
In addition I have huge problems in CM 10, 11. Cellular network connection disappears every 5-7 minutes and if I try to place a call.
Can someone, who have stable system share his firmware, bootloader, radio, recovery etc. versions. I would be very thankful to you.

Is h8rift working on this instead of cm11 now? Will cm11 see a final build?

buradd said:
Is h8rift working on this instead of cm11 now? Will cm11 see a final build?
Click to expand...
Click to collapse
H8rift is still around working on other HTC devices but his Evita has long ago bit the dust so I've been handling the testing on evita. The rest of the HTC msm8960 team has kept this going along with ville/jewel/fireball and the m7 series.
As for cm11 they have moved to weekly builds and I believe 1 more "M" build is scheduled before all focus moves to cm12 exclusively.

niihelium said:
In addition I have huge problems in CM 10, 11. Cellular network connection disappears every 5-7 minutes and if I try to place a call.
Can someone, who have stable system share his firmware, bootloader, radio, recovery etc. versions. I would be very thankful to you.
Click to expand...
Click to collapse
What are your bootloader details ? Maybe running an RUU might help

Does someone see any Wifi problem?
My wifi icon gets stuck and cannot enable at all.

For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.

jrior001 said:
For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.
Click to expand...
Click to collapse
Maybe we can just use 5.18 RUU from this post(last under AT&T USA spoiler): http://forum.xda-developers.com/showpost.php?p=37227608&postcount=1

niihelium said:
Maybe we can just use 5.18 RUU from this post(last under AT&T USA spoiler): http://forum.xda-developers.com/showpost.php?p=37227608&postcount=1
Click to expand...
Click to collapse
That will work too, I wasn't aware that RUU existed. I'll update my OP with those links as well

htc one x evita
i was happy with this lollipo very well. current running version cm12 20150108. my battery was draining heavily... is there any solution for this.

jrior001 said:
That will work too, I wasn't aware that RUU existed. I'll update my OP with those links as well
Click to expand...
Click to collapse
Finally! Everything worked perfectly after updating 5.18 DOC. But faced with some difficulties. Decision under the spoiler.
I flashed 5.18 RUU and after this my phone run into loop [white HTC csreen] -> [standart recovery(with green arrow)] -> [restart].
So, my following actions:
0. Hold down 'Power' button for ~10 sec. This reboots phone, but after screen turned black press 'Power'+'Vol. Down' and it goes into bootloader.
1. Go into fastboot mode through bootloader and flash latest CWM recovery with PC:
Code:
fastboot flash recovery recovery.img
2. After this reboot into recovery, mount USB. Download latest nightly and GApps, put them on SD and flash with recovery.
3. Reboot. All works perfectly well.
After all I gues that my problem was older than 2.18 hboot version.

howgeet said:
Does someone see any Wifi problem?
My wifi icon gets stuck and cannot enable at all.
Click to expand...
Click to collapse
None at all here, I'm using this device on Wi-Fi only and it hasn't skipped a beat.
Sent from my Evita

jrior001 said:
For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.
Click to expand...
Click to collapse
I can't update to RUU 3.18 or firmware 5.18 because I'm on a Windows 8.1 machine and adb/fastboot USB doesn't recognize my Evita from this machine.
If I just do a clean flash from TWRP without doing either of those "required" steps, will CM12 still run ok?
My bootloader details are below. Thanks for any help.

[ROM][MM 6.0.1] Unofficial Cyanogenmod 13 - Lenovo A850

{
"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"
}
Unofficial Cyanogenmod 13 / Android 6.0.1 - Lenovo A850​
This is a CM13 rom for our Lenovo A850. This is NOT MY WORK, I found it on this russian forum/post. Unfortunately, i couldn't find further information about the developer since I read the forum through google translate
This is a pure android 6.0.1 and not a looklike rom.
Code:
#include
/*
* 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.
*/
Photos:
Bugs: My problems are...
• I have tried installing Magisk and SuperSu without success (because CM13 is already rooted)
• Lattest Xposed libraried are not working (old may not too)
• Can't always get into recovery using both volume and power buttons (go through the power menu)
• When in the recovery and rebooting into system the phone closes (unplug the batery and reboot it)
• Default (CM) file-manager sometimes craches (for no reason)
• Reboot just powers down the device
• DO NOT INSTALL GRENIFY, you will get into bootloop
• Did you found anything else? Do you know how we can fix the above?
Instructions:
0. MAKE A NANDROID BACKUP! This ROM doesn't do well with you NVRAM... You will probably need to restore your IMEI, your Serial Number would be lost, your Mac Address etc. So... backup.
1. Download the "Lenovo A850 cm13.rar" file from here (there is also a CM12 version, i haven't try it)
2. Google Apps are not installed so you can download them from the Open Gapps Project (ARM->6.0->Any version) or from the above link.
3. Un-rar the "Lenovo A850 cm13.rar" file. The TWRP recovery that is included is translated in Russian (can't change to English) so replace the "recovery.img" file with this View attachment recovery.img that i have cooked (English version).
4. Flash the rom to your phone (there are a lot of videosout there about this)
5. Boot phone and BOOM, CM13/Android 6.0.1!!!!
6. To enable root access or reboot to recovery, open Settings->About->Tap "Build number" many times to unlock Developer Options->go back->Developer Options->Check "Advance reboot" and change "Root access"
7. Keep pressing power button -> reboot -> recovery -> flash Gapps
IMEI Problems/Fixes:
You can fix the IMEI with:
- With MobileUncle (follow these steps)
- Tool Hero (the update of MobileUncle), after that uninstall it.
- Else... if you don't know that you can run IMEI&SN Writer V1.5.3, flash this ROM and try to run it (setup drivers etc). Then FORMAT the phone (with flashtool click format,auto), and flash (click download this time) this ROM(the same with the first link), and then change the IMEI etc with IMEI&SN Writer V1.5.3.
If you liked this topic, click the thanks button <--

did u try this already? is all firmware will work on this? if not, what firmware we need to use in order to flash cm13? thanks

anklesnakim said:
did u try this already? is all firmware will work on this? if not, what firmware we need to use in order to flash cm13? thanks
Click to expand...
Click to collapse
Yes I am already using it, well not daily since its not my main phone. Flashtool is included so it doesn't mater what rom you already have (ROW or CN), you just flash it. I think the ROM is CN though. Additionally, i have tried installing Magisk or SuperSu without a success because CM13 is already rooted. I couldn't change it. What is more, lattest Xposed libraried are not working too (phone freezes and reboots on apk open). Also, i couldn't get into recovery using volume and power button, i am accessing it through the power menu (reboot into recovery). To conclude, when I am in the recovery and I choose to reboot into system the phone closed but I have to unplug the batery and reboot it.

how about battery life?

GreatApo said:
Yes I am already using it, well not daily since its not my main phone. Flashtool is included so it doesn't mater what rom you already have (ROW or CN), you just flash it. I think the ROM is CN though. Additionally, i have tried installing Magisk or SuperSu without a success because CM13 is already rooted. I couldn't change it. What is more, lattest Xposed libraried are not working too (phone freezes and reboots on apk open). Also, i couldn't get into recovery using volume and power button, i am accessing it through the power menu (reboot into recovery). To conclude, when I am in the recovery and I choose to reboot into system the phone closed but I have to unplug the batery and reboot it.
Click to expand...
Click to collapse
I'm also using it (also not my daily device) and overall seems to work no major issues at the moment. I'm happy with the default root and options so I have no conflict with magisk/xposed. I just use the root to remove bloatware and to "tabletize" the phone (freeze sms/telephone/mobile data functions, but can be unfreezed if I need phone functions back again)
I have flashed gapps (pico/customized) version and there is FC if you replace stock clock and messenger with gapps version.
Also battery, this phone without network and screen working (and several apks) disables use to work for some days. Now the battery goes off in 1 day, even if not using. I will try to troubleshoot the culprit.
In lenovo's firmware it had an auto power on-off function that dissapears on this new rom.

Just some further investigation on this rom:
IMEIs are gone, and I am unable to restore them with the typical methods. I will keep on trying
It seems that the battery is drained by "Cell standby" (phone contacting telephony antennas) which is weird, because it has no sim, it's on airplane mode and I have frozen all apks related to phone/mobile data. But looking at the log and at the battery statistics, it's trying to do something with cell data. Also if I go to Phone test and try to "turn radio off", it ignores the click on the button.
I'll try a couple more things but my feeling is that something is wrong on the data system that is linked to the battery drain.
By the way, I have read on the russian forum (source of this post) that cm12 seems to work ok, but I don't want to go to an older version. I'll keep it as a last resource.

sooperior said:
Just some further investigation on this rom:
IMEIs are gone, and I am unable to restore them with the typical methods. I will keep on trying
It seems that the battery is drained by "Cell standby" (phone contacting telephony antennas) which is weird, because it has no sim, it's on airplane mode and I have frozen all apks related to phone/mobile data. But looking at the log and at the battery statistics, it's trying to do something with cell data. Also if I go to Phone test and try to "turn radio off", it ignores the click on the button.
I'll try a couple more things but my feeling is that something is wrong on the data system that is linked to the battery drain.
By the way, I have read on the russian forum (source of this post) that cm12 seems to work ok, but I don't want to go to an older version. I'll keep it as a last resource.
Click to expand...
Click to collapse
I do not have problems with the battery. DO NOT INSTALL GRENIFY, you will get into bootloop. You can fix the IMEI with Tool Hero (the update of MobileUncle). CM12 didn't work for me but there seems to be more users there...

I have tried all the common ways to restore IMEI: Hero, Mtk Droid tools, flashable zips (with/without nvram clear), imei generator and replacing files, changing permissions on /data/nvram, dd from a backup nvram.bin... nothing seems to work. I'm considering reflashing full rom again, just in case something went wrong during flashing.
I have also found a flashable modem firmware, doesn't work either.
Not quite fan of hero though, asks for too many permissions. Don't really get the point of the permissions to read contacts.
Regarding greenify I tried to install but it FC every time. Uninstalled without rebooting, so thanks for the advice. If you have no problem with battery and IMEI, I'm even more convinced that both problems are related.

sooperior said:
I have tried all the common ways to restore IMEI: Hero, Mtk Droid tools, flashable zips (with/without nvram clear), imei generator and replacing files, changing permissions on /data/nvram, dd from a backup nvram.bin... nothing seems to work. I'm considering reflashing full rom again, just in case something went wrong during flashing.
I have also found a flashable modem firmware, doesn't work either.
Not quite fan of hero though, asks for too many permissions. Don't really get the point of the permissions to read contacts.
Regarding greenify I tried to install but it FC every time. Uninstalled without rebooting, so thanks for the advice. If you have no problem with battery and IMEI, I'm even more convinced that both problems are related.
Click to expand...
Click to collapse
I don't like tool hero too, but it did fix my IMEI problem. (I always deny most of the permissions it ask, and then uninstall). Nothing else worked (terminal, recovery, adb).
Battery seems fine here. I have to mention that my charging circuit has major problems. I use the phone daily now and I have 2 batteries charging them with cables.

Well, finally I have decided to re-flash, following the instructions of greatapo at the first post (I'm pretty sure I did the same last time).
In the middle I also flashed lollipop as suggested in the russian forum but I have little confidence that this had any impact.
The point is that phone has "magically" recovered IMEIs (like they were hidden somewhere) and battery usage is back to normal. Before, I had a slope of power comsumption due to cell network even on plane mode. Now, when the phone is idling consumption is flat.
I can recall that this phone (at least my device) had a strange behaviour: When it has been powered off for a while it didn't power on. But if I boot for recovery or keep it on, then it boots perfectly. This time I had it "heating up" before flashing (just in case something similar happens to any of you).

Booting taking too long!
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!

Maevinarsh said:
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!
Click to expand...
Click to collapse
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled

sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
im in the same situation,stuck on the boot logo for more than half an hour and nothing happened,any help would be great

sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
Nah Its ok now it works. I am just unable to flash GAPPS. Thats all

Krosbit said:
im in the same situation,stuck on the boot logo for more than half an hour and nothing happened,any help would be great
Click to expand...
Click to collapse
Now is working after flashing the mod above a official rom,now i have 2 errors,i cant see any file when plugged in the pc and the imei one (i tried tool hero but when i apply the apk stopped working),again any help would be great
PS:how can i enable root in the cm12 rom?

sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
Did you flash ROM+GAPPS successfully? I recently successfully flashed ROM. I tried to flash GAPPS using TWRP but after powering on my Lenovo a850, i always get 2 error message which is (Unfortunately, Setup Wizard has stopped working" (the most) and "Unfortunately, Google play services has stopped working". What now? Did I flashed it wrongly? Can you state how you flash GAPPS please?

Maevinarsh said:
Did you flash ROM+GAPPS successfully? I recently successfully flashed ROM. I tried to flash GAPPS using TWRP but after powering on my Lenovo a850, i always get 2 error message which is (Unfortunately, Setup Wizard has stopped working" (the most) and "Unfortunately, Google play services has stopped working". What now? Did I flashed it wrongly? Can you state how you flash GAPPS please?
Click to expand...
Click to collapse
Yes, my process (the one that finally worked):
Clear (everything but sdcard, modem, etc)
Install android 5 (this might be not necessary)
Clear
Flash cm13
Flash gapps (pico version, the smallest, arm architecture)
Start... and works
I'm starting from a 4.2 CN rom

still invalid imei after using tool hero. please help.

google play store please
gapps on the link page 1 make device force close after flash it via twrp, i do step by step on page 1
and thanks for share
i hope my issue can be solve by anyone here

Maevinarsh said:
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!
Click to expand...
Click to collapse
same like me
how you solve the problem?
just wait it or do something?

[ROM][OFFICIAL] Omnirom for Oneplus7pro [10]

CLOSED PER OP REQUEST
{
"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"
}
Download:
DOWNLOAD Official
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS
MAJOR BUGS:
huh ?
Minor bugs:
flash on your own risk.
FLASHING
First Time:
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
reboot
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS 10
Version Information
Status: Stable
Created 2019-10-02
Last Updated 2019-11-19

amazing , thanks

The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?

Gordietm said:
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Click to expand...
Click to collapse
That should be ob obvious, but i will add it

[ROM][BETA] Omnirom for Oneplus7pro [10]
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Click to expand...
Click to collapse
Always nano

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Read OP : flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED

[ROM][BETA] Omnirom for Oneplus7pro [10]
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Sent from my iPad using Tapatalk Pro

paatha13 said:
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Click to expand...
Click to collapse
Yes

Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Good luck

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Probably you missed something, skipped one step etc.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.

gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
No, oos camera also works fine

I have no idea what it is. Had to boot a fastboot rom just to get back up and running after that last crashdump. going to go back to OOS for a little I think. I have never had a rom do this but this one has done it every time I have tried. Thing is I love Omni so I hope one day i can get it running properly.
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
Don't worry i didn't forget lol. That's why i'm going to keep trying after every release. It will work for me one day.

[ROM][BETA] Omnirom for Oneplus7pro [10]
Everything fine with installations no had any issue with first attempt.
Installing nano gapps not had any issue too this time at opposite with weekend build.
Seems this build more stable and I'm now charging the phone,download my usual staff from play store,will setup my device and will start to work on it later when phone full charge.
Thanks @darkobas.
darkobas said:
No, oos camera also works fine
Click to expand...
Click to collapse
Yes I can confirm OOS camera working fine.
Sent from my iPad using Tapatalk Pro

Does anyone know of an app or mod that allows the navigation buttons to be inverted? The custom navbar app doesn't work on 10 yet and that isn't integrated into the rom yet. I'll live but it is tough to try to retrain the brain, ha!

First impressions using couple of hours is solid.
Battery life look promising and satisfactory.
Very smooth experience so far.
Speaker loudness and quality is on par with oxygen just like with Pie version.
Brightness level seems on par with high oxygen levels although I haven't test it in sunlight, will do tomorrow [emoji14]
Stock(android 10) gesture navigation works great but prefer oxygen one and since using nova launcher I'm with vivid gesture navigation app since when using third-party launcher automatically stock gesture navigation are disabled.
There's dark mode but I'm not fan of it since it's dark gray and not black that prefer (will use substratum to apply truly black theme almost everywhere)
Vast majority Omni features working fine so far.
Wi-Fi, mobile data, so far all excellent, BT will test tomorrow intensively.
Almost all oxygen features are present and worked fine, except vibration need some tuning but that also appy to stable OOS 10 version.
On Pie vibration was better both Omni and OOS.
High brightness level is still present
I found some bugs though like dt2w not such reliable almost half of the attempts needed 2 and rare 3 times to wake up screen or even press the power button at end because not responding at all.
Aldo digital wellbeing to me every time try to open I'm getting fc.
Safety net not passing through magisk also.
I assume will improve in future build don't forget it's still beta.
More observations and safe conclusions will have after couple of days of using the new rom.
But so far general impressions after few hours is at good and satisfactory level and the build is safe to be daily driver for sure.
Sent from my GM1913 using Tapatalk

Just wondering why I can't download the Samsung wearable app in the Google Play Store on this. When I get it from the APK it tells me that this software which is on my phone is not compatible with the watch is there a way to fix this so I can connect my Galaxy watch to this amazing ROM this happens to me on every single ROM except CR Droid 9.0 don't know why:crying:

This is a pic of what the Samsung wearable app said

[CLOSED] Pie Stock ROM for US996

I am closing this thread as I've had a better idea. Those wising to have A9 on their non-F800 device (US996 compatible only currently) may flash the official hardware F800 system available here;
[Stock] [F800 L/S/K ] [A9 Pie] Debloated Modified Rom for F800 Hardware
Get it all here, I will update this opening post later. Mobile call and internet data working perfectly for me with my carrier here in Ireland. More on this later. https://www.androidfilehost.com/?w=files&flid=322402 Btw this is based on latest...
forum.xda-developers.com
You may or may not have to make a small adjustment yourself to get it to work. I may even make a flashable zip so you don't have to do anything. I just have to get round to learning how to make them
This will save me having to work on 2 roms at the same time which are virtually identical anyway, and will avoid confusion, and multiple uploading of large files.
====================================================================
Since this was requested on the Pie Experimental thread.
As per the title alas no data.
Instructions
Download both the system image and the boot image from here;
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
The system image is in 7z format for maximum compression and faster download.
Extract either on your device or on a PC. Extract with 7-zip on Windows.
It will expand to a 6GB system.img file.
TWRP>INSTALL>INSTALL_IMAGE (bottom right) and flash system.img to system partition.
Same for the boot.img, flash to boot partiton.
Flash Magisk, reboot.
edit: delete your google account before you flash this in case wifi doesn't work.
Notes
The boot image has my ezV2020 kernel already. And Magisk but you still have to flash Magisk again.
Calls appear to be working for me. Voicemail anyway is all I tested.
Keep data turned off or modem with continually reboot if you have sim card in.
I have debloated a lot of google apps and all the Korean carrier apps.
This may also work for original F800 Korean models. You would have to replace original F800 firmware files though for wifi and I'
I would be interested to know if my modifications have unlocked the carrier sim lock on the F800 if anyone tries it.
edit: I changed my mind about this recommendation until I test it on my own F800 which is on order from China. More experienced devs may of course go ahead.
edit:2 Will not flash on F800, prob due to differing partition layout between variants
You can flash this on other us996 compatible variants but I'm not sure if everything will work especially wifi. If not might be easy fix though.
Do not flash on H918 as I don't know if it's safe to do so.

Are you Serious!!!... This may be a breakthrough!!!

Hallo
I have a f800l now with WETA Rom vs995
Which recovery i can use for try your files?
Thanks

TarAntonio said:
Hallo
I have a f800l now with WETA Rom vs995
Which recovery i can use for try your files?
Thanks
Click to expand...
Click to collapse
Please read my updated OP.

ezzony said:
Please read my updated OP.
Click to expand...
Click to collapse
Ok thanks i will stay tuned

Hey i'm just a little curious, will the cellular and data issue be fixed at some point? I'd like to try this rom on my vs995 although those are important to me

Okay so my F800 arrived. This will not flash on it so sorry if anyone downloaded it and it didn't work. The img file is a TWRP system.img backup taken of my US996. Since partition layouts are different between Korean and non-korean variants that my be why it didn't work.
Can anyone confirm they did get it work at all or their non-Korean device?

duplicate

So sad read this. Today i tried to flash oreo kdz for f800l as upgrade for not Leave twrp but not booted. After some tests returned to nougat with superv20 rom

TarAntonio said:
So sad read this. Today i tried to flash oreo kdz for f800l as upgrade for not Leave twrp but not booted. After some tests returned to nougat with superv20 rom
Click to expand...
Click to collapse
I'm not clear on what you need. If you have an original F800L device then you don't need this. I actually have F800L Twrp version of what I uploaded here and that will flash on an original F800L device via TWRP. But it is just a debloated version of original F800 KDZ. It doesn't do much more than that as I had hoped. The main point to this thread was to provide a ready made US996+ Pie ROM.
Incidentally for me F800S works the best in my country (Ireland) I have discovered today. Because it has a 3G band L version does not have. I have 3G and LTE so I'm pretty happy with that. It's not working perfectly yet as it is currently stuck on 3G but I think I can sort that out eventually. So if I upload a working F800 it will be the SK Telecom (S) version. And the newest update as well. Working very nice btw Finally got pie!

ezzony said:
I'm not clear on what you need. If you have an original F800L device then you don't need this. I actually have F800L Twrp version of what I uploaded here and that will flash on an original F800L device via TWRP. But it is just a debloated version of original F800 KDZ. It doesn't do much more than that as I had hoped. The main point to this thread was to provide a ready made US996+ Pie ROM.
Incidentally for me F800S works the best in my country (Ireland) I have discovered today. Because it has a 3G band L version does not have. I have 3G and LTE so I'm pretty happy with that. It's not working perfectly yet as it is currently stuck on 3G but I think I can sort that out eventually. So if I upload a working F800 it will be the SK Telecom (S) version. And the newest update as well. Working very nice btw Finally got pie!
Click to expand...
Click to collapse
My idea was have the chance to change rom Android system in twrp but i didnt found any zip to flash in twrp so i tried to upgrade in download Mode the oreo kdz without recovery recovery. Bak, aboot abbot. Bak
But started and goes in twrp then restart ed from kdz nougat 10e and now on super v20. Sorry for English explatation

ezzony said:
If you have an original F800L device then you don't need this. I actually have F800L Twrp version of what I uploaded here and that will flash on an original F800L device via TWRP. But it is just a debloated version of original F800 KDZ. It doesn't do much more than that as I had hoped. The main point to this thread was to provide a ready made US996+ Pie ROM.
Incidentally for me F800S works the best in my country (Ireland) I have discovered today. Because it has a 3G band L version does not have. I have 3G and LTE so I'm pretty happy with that. It's not working perfectly yet as it is currently stuck on 3G but I think I can sort that out eventually. So if I upload a working F800 it will be the SK Telecom (S) version. And the newest update as well. Working very nice btw Finally got pie!
Click to expand...
Click to collapse
Do youa have a zip for pie or oreo to flash in twrp for f800l? Im habby if is debloated

TarAntonio said:
Do youa have a zip for pie or oreo to flash in twrp for f800l? Im habby if is debloated
Click to expand...
Click to collapse
Yes I will upload TWRP backup you can install. Give me a little time. Soon.

ezzony said:
Yes I will upload TWRP backup you can install. Give me a little time. Soon.
Click to expand...
Click to collapse
Many many thanks will you upload backup for oreo and pie? Have you perhaps also a flashable zip debloated in future?

TarAntonio said:
Many many thanks will you upload backup for oreo and pie? Have you perhaps also a flashable zip debloated in future?
Click to expand...
Click to collapse
I don't know how to make a flashable zip (yet).
The first F800 Pie will be a system.img file you can flash in TWRP anyway.
I don't see a reason to provide an Oreo rom. I thought I read WETA rom works on F800? You would have to read the relevant thread for information.
Now, I am having an issue with apps crashing on my ROM so there is slight delay. I have to fix it before I upload. I'm working on it.

ezzony said:
I don't know how to make a flashable zip (yet).
The first F800 Pie will be a system.img file you can flash in TWRP anyway.
I don't see a reason to provide an Oreo rom. I thought I read WETA rom works on F800? You would have to read the relevant thread for information.
Now, I am having an issue with apps crashing on my ROM so there is slight delay. I have to fix it before I upload. I'm working on it.
Click to expand...
Click to collapse
Thanks for answer. Actually i have Super rom f800 by dudeawsome and WETA both with nougat. Tried 2 days ago ALPHA OMEGA rom vs995 but boot only until logo. Have you tried some roms with oreo on your f800?

TarAntonio said:
Thanks for answer. Actually i have Super rom f800 by dudeawsome and WETA both with nougat. Tried 2 days ago ALPHA OMEGA rom vs995 but boot only until logo. Have you tried some roms with oreo on your f800?
Click to expand...
Click to collapse
No because I received my F800 only last week. I bought so I can have working Pie on the V20. I won't be wasting any time with Nougat or Oreo because Pie is awesome on the V20. You won't need Oreo! And Magisk apps works better on Pie as well!

So i flashed it on my us996 (vs995 converted to us996) and everything works fine although, every once in a while it crashes and goes to the green crash screen "apps watchdog bark"
with this error "init: could not find service hosting interface vendor.lge.hardware.dualscreen01.0::IDualScr" repeatedly showing up.
{
"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 know the picture isn't that clear but i forgot how to get a log after a crash so if you could tell me what it i'll try to get an actual log
Edit: This crash seems to only happen a couple of mins after a reboot, but after a while of the phone running fine it doesn't crash
Edit 2: while it becomes more stable after a while, it still crashes sometimes

xxseva44 said:
So i flashed it on my us996 (vs995 converted to us996) and everything works fine although, every once in a while it crashes and goes to the green crash screen "apps watchdog bark"
with this error "init: could not find service hosting interface vendor.lge.hardware.dualscreen01.0::IDualScr" repeatedly showing up. View attachment 5222891i know the picture isn't that clear but i forgot how to get a log after a crash so if you could tell me what it i'll try to get an actual log
Edit: This crash seems to only happen a couple of mins after a reboot, but after a while of the phone running fine it doesn't crash
Click to expand...
Click to collapse
Hi, unfortunately my US996 died last week. I only have F800 now, so it will be much more difficult for me to fix this.
To be honest I got this bug myself but it only happened after installing and then it seemed to go away. I am not certain about this though because I went back to Oreo.
Could you keep an eye on it and see if it goes away or happens repeatedly.
edit: I see now you said it happens every once in a while. I'll look at it eventually but I'm working on F800 at the moment so might be a while.

@TarAntonio I'm sorry to report I'm having problems with the F800 rom. The issues is when the phone is on LTE+ is won't receive calls. I've no idea what is causing this so It will probably take a while for me to figure out. I don't know if it's the Rom, my carrier settings, or my carrier network. It's very important for calls to work so I can't upload what I have until I figure this out.

Question Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"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"
}

It seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..