Database Info

[Q&A] [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart

Q&A for [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Xoom cm11
Im currently running cm11 on xoom. Chrome freezes lots. Is there a fix or workaround.

eric1212 said:
Im currently running cm11 on xoom. Chrome freezes lots. Is there a fix or workaround.
Click to expand...
Click to collapse
At one point in time (around May) people were having issues with any version of Chrome newer than or including V34. People were reverting back to V33. I don't know if it has been resolved as I went back to using the stock browser.
I dug around - http://forum.xda-developers.com/showpost.php?p=52506042&postcount=920 - this post has/had a link to Chrome V33. I cannot vouch for the link. I ended up getting V33 out of a PAGapps package that I had backed up from the beginning of March.

How do I side load chrome v33. I am unable to do so. I keep getting the error , app not installed.
Xoom, EOS kitkat., EX2.1

The CM11 install messed up for me, could I please get some help at the thread I posted on this? Thanks! Just wish this ROM would work for me..

I have the same issue with Chroma and Opera -both crashing my Xoom (Everest, [4.4.4] CyanogenMod 11.0 ). When i tried to kill chrome, it kills also my battery - discharging takes about 4h from 100% to 0%.
Now I installed Chrome v32 and works fine

Frequent Freezes of Wingray requiring Reboot
In Aug-Sept 2014, there was a discussion in the thread: [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart, related to Frequent Freezing of Wingray requiring Reboots (see posts 595, 597, 599, 600, 611 and 615). I have been experiencing the same (or very similar) issues for several months. I have an MZ604 with Wingray and have been taking the monthly updates regularly since they have become available; I initially installed CyanogenMod about 7 months ago. I have been running with Xposed and Wakelock Terminator as described in http://forum.xda-developers.com/showthread.php?t=2697893.
The freezes almost always (with one exception) happen when the XOOM is sleeping; the exception was a crash that happened once while I was using the device, but it might be a different issue. Freezes were happening about once/day, but in the past few weeks had increased to almost every time I put the XOOM to sleep. The only way to recover from a Freeze is to completely reboot the device by holding both the power button and the Volume button simultaneously for several seconds. Freezes usually seemed to be accompanied with a significant battery reduction, so I suspect something was coming to life, using a lot of battery for a while and then killing the XOOM. My Battery Monitoring app would never keep data through one of these freezes, so it was useless in helping me understand what came to life, used the battery and then caused the crash.
For some reason, this week the XOOM has stayed alive for an entire battery cycle. I recharged it 4 or 5 days ago, and used it according to my usual pattern of 3 or 4 times per day for anywhere from 15 minutes to an hour each time. The battery went down by about 15-20% per day at a pretty consistent rate. I put it back on the charger this morning with 16% battery left. After the very frequent freezes prior to this week, I was very surprised to see it stay alive for a full 4-5 day period. For the rest of you who were experiencing these freezes/crashes, did your device start working without freezes this week too?

Hi ,
I'm new here, and I can't find answer by searching.
How can I change my lock screen orientation?
Thanks!

Which GAPPS for CM11 ?
Hi all,
just flashed cm-11-20140912-UNOFFICIAL-1551+0200-everest.zip on my MZ601, trying to get some of the google apps working. In my previous tests, with EOS-full_everest-20141110.083307.zip the chrome browser ( either beta than normal ) used to hang, and so it does google maps.
I've flashed pa_gapps-modular-full-4.4.4-20141110-signed.zip but I have the same behavior with maps ( crash when zooming ) and I suspect also the hang on chrome ( not tested yet ).
I have read on the thread <url> http://forum.xda-developers.com/showthread.php?p=56740906&highlight=maps#post56740906 </url> that on the latest version maps crash but seem to be working on some previous release.
So the question: which version should I install to get a working maps and ( eventually ) chrome ?
Thanks in advance
Pigi

Changelog
Hi!
Where I can find the latest changelog for this new version of CM11 for XOOM?
Thanks.

Pigi_102 said:
Hi all,
just flashed cm-11-20140912-UNOFFICIAL-1551+0200-everest.zip on my MZ601, trying to get some of the google apps working. In my previous tests, with EOS-full_everest-20141110.083307.zip the chrome browser ( either beta than normal ) used to hang, and so it does google maps.
I've flashed pa_gapps-modular-full-4.4.4-20141110-signed.zip but I have the same behavior with maps ( crash when zooming ) and I suspect also the hang on chrome ( not tested yet ).
I have read on the thread <url> http://forum.xda-developers.com/showthread.php?p=56740906&highlight=maps#post56740906 </url> that on the latest version maps crash but seem to be working on some previous release.
So the question: which version should I install to get a working maps and ( eventually ) chrome ?
Thanks in advance
Pigi
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=57207242
Sent from my GT-I9505 using XDA Free mobile app

Xoom Battery Issues with [ROM][4.4.4] CyanogenMod 11.0 - Wingray - bigPar
Gentlemen,
After flashing with this rom (http://forum.xda-developers.com/showthread.php?t=2596566) my xoom started dying in less than 24 hours(even with wifi off).
With the original rom it would last several days in stand by mode.
Any clues?
thx

Problem
com.android.systemui and Googles services Constantly restarts and makes tablet totally unusable.
change googles app???

affs said:
com.android.systemui and Googles services Constantly restarts and makes tablet totally unusable.
change googles app???
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=57188808

Mobile data not working
Hey everyone, my mobile data isn't working because when I flashed I lost my IMEI, for more details please look at my posts here http://forum.xda-developers.com/showthread.php?t=2596566&page=69
Thanks for your help.
-Mr_IceSlice

New guy here, i just installed the omni everest build for the xoom following these instructions http://forum.xda-developers.com/showthread.php?t=2593414
Everything works as expected except my verizon 3g i have explored all available settings and rebooted and reflashed several times. It registers verizon signal but under status it says network type unknown and status as disconnected. Is there something im missing? The tablet was stock before and all mobile signals worked as they should

Thanks!
Thanks for the guide mate.
At first, I had user issues with the TWRP. TWRP asked me to enter a password during initial boot. I just hit cancel. It then could not do any wipe per instructions on this page (page 1) including Advanced Wipe, Mount cache, etc. Perhaps, I was a bit lazy reading every word.
So I skipped this process and went ahead and flashed the [ ClockworkMod Recovery ], I't s a very nice familiar Interface during my Droid X days. The TWRP is also now quite familiar to me since I used it to install [ CyanogenMod Crombi-kk on my Asus TF700T ] (sloww device! My Xoom is faster!!! Believe it!) Anyhow the whole install including the ROM was a breeze. However, I noticed that the version says 4.2.2 or something like that. I wanted 4.4.4.
So here I was, back again.
Anyway, I re-flashed back the recovery to TWRP then decided to just go ahead and format the data (IIRC, that option is available)
Guess what, it worked! Installed the ROM and done! =)
Oh BTW, I also installed the PA_GAPPS. I don't remember where I got the link from, but I'll try to edit this if I find it.
PHOTOS:
{
"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"
}
Second Install after wiping out 4.2.2
4.4.4

No 3g or 1x fallback
Been having this issue with every big part ROM i have installed. Verizion 4g service or nothing. Something is not right with the baseband.

need to big partition my xoom 601
halo house am new here, you guys are really doing a great job(kudos). i have rooted my xoom, but having prob on how to big partition my xoom. pls i really need u guys assistance if there is a video to it pls send me the link. thanks

Bug?
I got this rom to run just fine, and most things seem to work well.
The biggest issue I am having with the latest posted CM11 with BigPart is with Plants vs. Zombies 2 which wont display anymore. I have tried a new install and restoring the backup from the old nightly CM 10.1 and nothing works.. Flashed this ROM to my second Xoom to verify the issue, noticed a handful of games that launch to a glitched or black screen. Thoughts?
Would hate to back-date as everything ELSE is running faster than it has in a while.

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] [AOSP] Candy7 -- Final v6.0 [7.1.2][OMS/DUI]

{
"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"
}
This is Candy7.1. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web The-Candy-Shop​
Candy 7.1.2 v6.0 Final
Dynamic GApps
FEATURES
Multi-window
OmniSwitch
Immersive mode
Clear all button
Memory bar
Slim Recents option
Advanced power menu:
On The Go Mode
Screen record
Adjustable dialog background shade
Sound panel
Expanded desktop
Lockscreen:
Battery charging current overlay
Adjustable shortcuts
Weather (OmniJaws)
Statusbar settings:
Ticker (disable heads up when in use)
Weather panel
Clock/battery configuration
Traffic indicators
Quick settings tile config
Immersive messages
Force expanded notifications
Carrier label
Tap to sleep
Buttons settings:
Long-press/double-tap actions
Volume rocker
Playback control
Volume key answer
Disable HW keys
Pie control
Navigation bar:
Adjust colors
Smartbar/fling
Pulse
Screenshots:
3 finger
Adjust framing
More to come, we are never done...
Steps:
1) Download ROM zip
2) Download GApps
3) Boot into Recovery
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash Candy7.1.zip
6) Flash GApps
7) Reboot.
BUGS:
1. same as lineage
2. first time registering finger print gives FC
3. flashlight works after 2nd reboot (for me)
Candy Source --
Device Tree
Kernel Source
Vendors
Special thanks to LineageOS, SlimRoms, Omni, TeslaROM, and all the rest who make their source open. We can't do this on our own.
XDA:DevDB Information
Candy7, ROM for the LeEco Le 2
Contributors
saurabh1234, saurabh1234, Candy Team
Source Code: https://github.com/candyroms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Created 2017-12-19
Last Updated 2017-12-19

screenshots

Download My Wallpaper App for More Hipsta Walls and some Nature Wallpapers...
its a free app with no ads...
Play Store Link

This ROM is how different from slimrom.....
Because slimrom doesn't have hardware keys off setting...
I am using from quit past time..

itsvikash said:
This ROM is how different from slimrom.....
Because slimrom doesn't have hardware keys off setting...
I am using from quit past time..
Click to expand...
Click to collapse
this rom has option to disable hardware keys...
and many more features...
slim rom is made to give users a full AOSP experiance.
Candy rom is also AOSP based but with different features

Can u give me
link of dynamic gapps

itsvikash said:
Can u give me
link of dynamic gapps
Click to expand...
Click to collapse
check op its there...bean gapps is called dynamic gapps

I'm facing some issues with dual sim. One of the sims just doesnt show up.
Downloaded and flashed rom just two days ago; so I guess must be the latest version.
Using it with Illusion kernel 3.1b.
Le 2 x522(or whatever the Indian version is)
Was on .19s stock eui before flashing candy rom.
Flashing sequence
Rom
Gapps
Magisk
Kernel(after booting into system, atleast once with stock kernel)

Ronnie_180808 said:
I'm facing some issues with dual sim. One of the sims just doesnt show up.
Downloaded and flashed rom just two days ago; so I guess must be the latest version.
Using it with Illusion kernel 3.1b.
Le 2 x522(or whatever the Indian version is)
Was on .19s stock eui before flashing candy rom.
Flashing sequence
Rom
Gapps
Magisk
Kernel(after booting into system, atleast once with stock kernel)
Click to expand...
Click to collapse
after setup...do a reboot..then a airplane mode turn on and then turn off...
it will work...
if setup is already done...then do reboot and then turn on airplane mode and then turn off...and wait ...
it will work

saurabh1234 said:
after setup...do a reboot..then a airplane mode turn on and then turn off...
it will work...
if setup is already done...then do reboot and then turn on airplane mode and then turn off...and wait ...
it will work
Click to expand...
Click to collapse
Actually I had both the Sims working initially after the whole setup. Even tried calling from both Sims with satisfactory results.
I was on wifi, so then for checking purposes, I tried to switch to mobile data. Didnt work at first. So I turned airplane mode on & off. Got data, but began facing the above mentioned dual sim issue.
I don't have the device with me at present. But I'll surely try your suggestions and report.
On a side note, I also have a Redmi Note 3 and many a times issues related to calls and sim cards in custom roms gets resolved by flashing latest firmwares, so I was wondering if even Le 2 requires flashing firmwares or something?
Also, I had queries about the bootloader unlocking process.
First of all, I'm new to Le 2 development, but I've had about enough experience with rooting and stuff. Not a dev myself, but I can say I've some basic understanding which shall make it easier for you to explain and help me.
I searched about stuff on google and xda, but kinda unable to get proper answers.
Anyways, back to the main topic here;
So for unlocking bl;
I rebooted to fastboot mode after enabling adb debugging and oem unlocking and unlocked bl via fastboot commands, flashed redwolf twrp and formatted the whole device via twrp.
Is that correct? And is that the only method available to unlock bl?
It seems like unofficial unlocking and if it really is so, then is there an "official" way of unlocking?

Ronnie_180808 said:
Actually I had both the Sims working initially after the whole setup. Even tried calling from both Sims with satisfactory results.
I was on wifi, so then for checking purposes, I tried to switch to mobile data. Didnt work at first. So I turned airplane mode on & off. Got data, but began facing the above mentioned dual sim issue.
I don't have the device with me at present. But I'll surely try your suggestions and report.
On a side note, I also have a Redmi Note 3 and many a times issues related to calls and sim cards in custom roms gets resolved by flashing latest firmwares, so I was wondering if even Le 2 requires flashing firmwares or something?
Also, I had queries about the bootloader unlocking process.
First of all, I'm new to Le 2 development, but I've had about enough experience with rooting and stuff. Not a dev myself, but I can say I've some basic understanding which shall make it easier for you to explain and help me.
I searched about stuff on google and xda, but kinda unable to get proper answers.
Anyways, back to the main topic here;
So for unlocking bl;
I rebooted to fastboot mode after enabling adb debugging and oem unlocking and unlocked bl via fastboot commands, flashed redwolf twrp and formatted the whole device via twrp.
Is that correct? And is that the only method available to unlock bl?
It seems like unofficial unlocking and if it really is so, then is there an "official" way of unlocking?
Click to expand...
Click to collapse
you did right..thats the way to unlock le2...
i would recommend you to install official twrp and use 19s bootloader...

saurabh1234 said:
you did right..thats the way to unlock le2...
i would recommend you to install official twrp and use 19s bootloader...
Click to expand...
Click to collapse
Okay, will shift to official twrp and since (luckily) i never updated my stock rom after 19s version, my bootloader shud still be 19s, right?

Ronnie_180808 said:
Okay, will shift to official twrp and since (luckily) i never updated my stock rom after 19s version, my bootloader shud still be 19s, right?
Click to expand...
Click to collapse
yes

Change Logs:
Latest Device Tree
Latest Kernel Source
Flash Magisk for Root
Link - https://drive.google.com/open?id=130nPA5sMlmv_moqGe1d5eF9oCx_ialTk

[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