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.
Related
{
"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"
}
Thank u to the Liquid Team for continuing this project!
Many credits go to CyanogenMod for their device trees and their code that was incorporated into this project.
Downloads and installation
+ Download the ROM
+ Download the (Recommended) GApps
+ Copy the ROM to the SD
+ Copy the GApps to the SD
+ Install the ROM and the GApps
+ If you are already in LiquidSmooth, do a cache wipe and dalvik cache wipe
+ If you come from any other ROM, do a wipe data / format system
+ Reboot
CREDITS
LIQUIDSMOOTH TEAM and everyone they are involved with!
chainfire for root!
MEET THE TEAM
Liquid0624
Deadman96385
jsnweitzel
Somber73
TheBr0ken
Cdub50
Sat this one out
Donations are always appreciated
Liquid0624
XDA:DevDB Information
LiquidSmooth, a ROM for the HTC One S
Contributors
phoenixita
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.15
Version Information
Status: Testing
Created 2013-12-19
Last Updated 2013-12-29
Reserved
http://www.androidfilehost.com/?fid=23269279319197376
I've not tested it!
Let me know! Use Flemmard's recovery.
BUGS
Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways
Click to expand...
Click to collapse
You beauty!. Thanks will test
Sent from my One S using XDA Premium HD app
is for hboot 2.16 or 2.15?
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
2.15! Building for 2.16 is like building for another device i don't know if i have all this time! I'll try for 2.16 right now.
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
You are either joking or to lazy to read at least the OP.
Tell you what...regardless of which hboot is for, it is surely not for you
Sent from nowhere over the air...
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
Pmsl....Read op its hardly a novel...
Sent from my One S using XDA Premium 4 mobile app
Any feedback?
Download is slow, so no report yet....
The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4
Hai96 said:
The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
LS is only in english you can use morelocale2 but you won't hve full traslations! I'm italian and searching the net and asking To teamliquid they won't support other languages cause they have no time! Language pack were available for LS 4.2.2 and $doryd$ joined the teamliquid to port languages but it was just for 4.2!
Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4
Hai96 said:
Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways
Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Click to expand...
Click to collapse
could you try dirty flashing over a cm11 nightly?
phoenixita said:
could you try dirty flashing over a cm11 nightly?
Click to expand...
Click to collapse
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well
Rapier said:
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well
Click to expand...
Click to collapse
lemme know!
phoenixita said:
lemme know!
Click to expand...
Click to collapse
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.
Rapier said:
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.
Click to expand...
Click to collapse
You and phoenix are a great duo together. Phoenix always building and supporting our device and Rapier always tests and provides quality feedback. Thanks to you both for your contributions, very much appreciated. I had those systemui errors constantly on the BeanStalk build, as well, so I reverted back to a 4.3 ROM until the issues are more ironed out. This is expected considering KitKat is still in some infant stages and our device needs a lot of pruning to get it right. Is it true that the battery life is horrendous in 4.4? Thanks to you both again, keep it up! Very eager to try 4.4 again when there is no more systemui errors.
phoenixita said:
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!
Click to expand...
Click to collapse
Didn't worked, I still have the same problem with the display...
Sent from my HTC One S with Tapatalk 4
{
"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"
}
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
TOP TIP "For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed." Thanks go to tobitege for this.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
+1. I also flashed the latest official CM nightly, booted it and checked if everything was working and then flashed the latest unofficial Temasek's rom. Everything works fine.
Cheers
@zaphodbeeb: thanks for having created this!
This morning I tested an extended version of the CM-12 flashable zip containing more partitions of the current nightlies.
First test brought me a jackpot in that it flashed without an error message, but soft bricked my phone (black screen, no adb nor fastboot), but power button rebooted in a special mode "HUSB_BULCK" (viewable in device manager). Takin' up the challenge, so after plenty of searching/reading and multiple tries to install the right drivers, I got it going through Color OS installation with special phone flashing tool, then flashing X44 again, unlocking, custom recovery+rooting... that was (deserved) fun!!
Though in the first moments it scared me s***tless!
Long story short, totally agree to just flashing the full nightly and directly clean on top any LP rom you want, if you want to be sure to have it right.
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
cam30era said:
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
Click to expand...
Click to collapse
I dirty flashed SlimSaber-bacon-5.0.2-20150110 build on top of SlimSaber-bacon-5.0.2-20150102 and then flashed alpha modem everything works fine.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
That weird baseband version is the correct one, no worries.
radium22 said:
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
Click to expand...
Click to collapse
Good idea. Done. Now this really is the end of my contribution on this subject.
zaphodbeeb said:
Good idea. Done. Now this really is the end of my contribution on this subject.
Click to expand...
Click to collapse
So first flash the 3rd zip (cm12 nightly)
Then dirty flash the main Rom or whats the next step?
Thank you
The full nightly should be flashed first, then wipe clean in recovery and install your actual rom (or restore).
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
losthilien said:
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
Click to expand...
Click to collapse
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
I went for number 3. Did a backup of my temasek ROM. Did a full wipe and installed cm nightly. Had full signal and thought great, this is the right modem. Restored my temasek and signal is gone again.
Any idea why? Did I restore too much of my temasek? Boot, system and data.
Thanks
It might just need another reboot after initial restore to reconnect.
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
VQ30DE said:
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
Click to expand...
Click to collapse
Not sure what to tell you. I have no WiFi problems. SlimLP ROM
So I just recovered from a hard brick with a dead battery.... it was brutal. I'm looking to do things more carefully going forward. I'd like to keep CM11S as primary. But obviously I want lollipop asap. If I backup CM11S nandroid... wipe clean, flash CM12 nightly for the modem and such, and then clean wipe and restore CM11S to primary from nandroid... will the modem changes that CM12 nightly made persist? I'd like that.... then I could flash some lollipop roms as secondaries and benefit from the modem changes that cm12 made?
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
tobitege said:
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
Click to expand...
Click to collapse
Top Tip man. I like.:good: I'll include in the OP.
timmaaa said:
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
Click to expand...
Click to collapse
You will notice the subtle message added to my sig also, using simple large letters for those with limited reading abilities.
CyanogenMod is officially dead... so, this project is also discontinued. The web links to ROMs may not be available anymore. Please do not expect any replays from me on this thread. Thanks for all the support. You may try LineageOS, the successor of CyanogenMod, as an alternative.
Here are some useful links
LineageOS
LineageOS kltekor
LineageOS XDA thread for all the klte variants
These are official CyanogenMod-13.0 (Android 6.0.x Marshmallow) builds originally developed for the international S5 (klte) with modified boot.img specially designed for Korean Galaxy S5 variants. Team CyanogenMod deserves all the credits for developing this wonderful ROM.
/* Warning */
Warranty of your device is now void.
I am not responsible for any damage to your device. Everything you are doing on your mobile is on your own risk. Please don’t point your finger at me in case you brick your device or lost SD card.
The boot.img file is specially designed for Korean Galaxy S5 SM-G900S/K/L (klteskt – kltektt - kltelgt). Do not try to flash this file on any other S5 variants (and also other devices).
The ROM alone (without the provided modified boot.img) only supports the international variant SM-G900F (klte).
/* Supported devices */
Samsung Galaxy S5 SM-G900S (klteskt): tested
Samsung Galaxy S5 SM-G900L (kltelgt): tested
Samsung Galaxy S5 SM-G900K (kltektt): tested (thanks to @Cm_RoX)
/* Requirements */
Samsung Galaxy S5 SM-G900S/K/L (klteskt – kltelgt -kltektt) device with more than 80% battery charged.
Windows PC/Laptop
ODIN software (for Rooting and flashing Custom Recovery)
A high quality USB cable
/* Downloads */
CyanogenMod 13.0 for klte
Google apps (GAPPS) for CyanogenMod 13.0 (open GAPPS / A-GAPPS).
cm-13.0 boot.img
Rooting
SM-G900S (klteskt)
SM-G900L (kltelgt)
SM-G900K (kltektt)
TWRP Recovery
/* Recommendations */
Back up your contacts, photos and any other data that you considered as valuable.
Probably you can make a Nandroid backup (if you wish to back up your present operating system along with all the data including apps).
/* Important */
You can use official ROM updates from CyanogenMod. However, it is necessary to re-flash the modified boot.img after each update to avoid boot failure.
The modified boot.img files will be updated and posted in this thread in a regular basis (please see second post).
/* Installation */
1. Root your device
2. Install TWRP recovery
3. Wipe data/factory reset
4. Flash ROM
5. Flash GAPPS
6. Flash cm-13.0 boot.img (important for Korean Galaxy S5)
7. Wipe Cache/Dalvik Cache
8. Reboot
/* Known Issues */
1. No important bug other than some issues related with ‘Media audio’ and ‘Phone call audio’. (Fixed in SM-G900S and L: not conformed in SM-G900K)
2. Please report if you find bugs
I appreciate the suggestions and fixes for bugs.
/* Screenshots */
{
"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"
}
/* Acknowledgements */
CyanogenMod (for this wonderful ROM)
Team Win Recovery Project
Our Korean Galaxy S5 Facebook group member’s
Chainfire (for CF-Auto Root)
Ljzyal (for fingerprint lock)
Many other XDA developers
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based on: CyanogenMod
Boot-loader: Lollipop
Created: March 17, 2016
Updates
/* Updates */
----------------------------------- -----------------------------------
Boot.img version ------------------------------------ Date
----------------------------------- -----------------------------------
cm-13.0_boot.img for kltexxx -------------------- 2016-07-17
----------------------------------- -----------------------------------
marvelous its functionnaly my korean s5
After the update its important dont forgoten flash cm-13.0_boot_img_SM_G900S_K_L
Yes... It is important to flash that custom boot.img... Otherwise, it will not boot on Korean S5
sunilpaulmathew, where u find update boot.img?
syapk said:
sunilpaulmathew, where u find update boot.img?
Click to expand...
Click to collapse
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.
unlocked verizon s5, using t-mobile sim card.. need help rooting and updating
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow
ilovemyhoohaw said:
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow
Click to expand...
Click to collapse
Unfortunately, SM-G900V is not ab officially supported device of cm-13.0 (Marshmallow). Rooting guides are however available. If you are really like to try marshmallow, try this unofficial build (select the unified version). Since ur device is very similar to SM-G900F (klte), the recovery (like twrp) and custom ROMs for klte variant might work on ur device. But not guarantied. So, please do everything in your own risk. No one else will take the responsibility of any damage caused to ur device while doing these experiments. I recommend you to back-up every valuable data from mobile and download the stock ROM of your device (from sammobiles) before starting the experiments. Good luck.
sunilpaulmathew said:
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.
Click to expand...
Click to collapse
wwooww, Can you explain how to make this?
syapk said:
wwooww, Can you explain how to make this?
Click to expand...
Click to collapse
It is basically easy in Linux. Download mkbootimg from here. 1) Decompress the stock and cm-13 boot.img (check read me file for the commands). 2) Replace the device tree file of the cm boot.img with the file from stock boot.img. 3) repack and flash into device.
greats !!
thanks ^^
Root and erro for device sm-g900s
hello, xda and chainfire first congratulate you all for great works in molhoramentos developments and to structure our plataforna android! recently bought a galaxy galaxy sm-g900s of a friend who went to korea I am Brazilian and I have residence in Rio de Janeiro and see what by Brazilian forum è not given much value to ess magnifico device what in my opinion is better what Brazilian version sm-g900m and I perdir a big favor '' xda and chainfire family. '' which take a little but sevirços this magnificent galaxy s5 device sm-g900s thank you in advance! now let my problem recetemente did root in my sm-g900s with CF-Auto-Root first time it worked perfectly but after a day just vanished and saying that recently your device has been updated to 5.0 porfavor redo the root and asked also update '' su binary '' but how? I am currently with some financial difficulties and can not contribute donations will not lie I'm paying this amazing handset even with great difficulty! Only then ask for help and support in the galaxy s5 sm-g900s and remember and thank also those involved in progeto cynogenmod for sm-g900s I was very happy to know what is' rom cynogenmod '' want to install but wanted to know whether to take root both 5.0 and 6.0 lollipop good marshmellow now comes I have spoken
Boot loop
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1
BlackMonoch said:
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1
Click to expand...
Click to collapse
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.
sunilpaulmathew said:
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.
Click to expand...
Click to collapse
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160330-NIGHTLY
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
After couple of minutes waiting, still stuck at "Android is starting... Starting apps."
........edit.......
Yay! After taking sometime waiting, I rebooted my device and now starts normally.
Thanks for this tut, now I can finally enjoy CM13 on my phone.
Thanks OP.
Audio Jack Bug
3.5mm audio jack does not work.
BlackMonoch said:
3.5mm audio jack does not work.
Click to expand...
Click to collapse
That is a know bug... and sometimes you may face issues with caller volume. There is no permanent solution at this moment . You can temporarily solve these issues using SoundAbout although it is bit inconvenient. Suggestions are most welcome.
Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,
obosaleh said:
Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,
Click to expand...
Click to collapse
I also face similar issues with the recent nighties... I tested nighties till 20160323 and found no issues. I'm not sure whether this issue exists in klte too. Anyway, thanks for testing and posting your tips.
i have same problem with new update 31-03 01-04 02-04
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
{
"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"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer
Reserved
Screenshots by Android 10 ????
I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
@justasic What version of the camera program?
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,
Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data
muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.
Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.
ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.
Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11