yashsingh1/xdaforums huggingface dataset:
[Micromax A106 Unite 2] WesleyV2:
:fingers-crossed:

Hey Guys Today I Present To You Vibe Ui V2.0 For Unite 2

:fingers-crossed:

[4.4.2] [KitKat]

FEATURES:

Lenovo's Vibe ui V 2.0

Change themes Using Theme Center

Lenovo Camera and Gallery

Vibe Lockscreen[swipe to change]

Lenovo Music

Lenovo Dialer+Contacts

Lenovo Power+Security Manager

Odexed for Increased Performance

Lenovo boot animation

And much more

:cool:

FLASHING PROCEDURE:

1.Reboot to Recovery

2.Wipe cache/Dalvik-Cache/Sytem/Data[CWM]

3.Wipe All Data Pre-Flash and wipe Dalvik-Cache[Ctr]

4.Select Rom From Storage/Install

5.After Finished Wipe Cache/Dalvik cache

6.Reboot And Come Press Thanks on Xda

CREDITZ:

Kishorer prem/All Time Hitz @fb

Needrom.com

All of You

Download Link: https://docs.google.com/uc?id=0BwH3-igQ5c52SFdUMllGMkk5UTA&export=download

Rooting[Flash This]:http://d-h.st/Gq9

Have Worked Hard On This Rom.To Release More Roms I Need Your Encouragement So Plz Hit :good::good:Thanks:good::good:
[Micromax A106 Unite 2] WesleyV2:
Screenshots
[Micromax A106 Unite 2] WesleyV2:
BATTERY TIPS:

Turn on all options in lenovo power manger

use in power saving mode

NOTE:

3G Works on 1st Sim Only

UI CUSTOMIZE:

After Rooting Open Xposed Installer app Go to Modules and tick VibeXpert

Go to Framework install

Reboot

Open VibeXpert App select Customizations

Reboot to Apply Changes
[Micromax A106 Unite 2] dkdas:
good rom thanks for hard wor

good rom thanks for hard work.........
[Micromax A106 Unite 2] WesleyV2:
Welcome Bro...

Please Brothers Provide Feedback after Installing....Will Help to Improve
[Micromax A106 Unite 2] trueamrit:
Any bug in this rom ?
[Micromax A106 Unite 2] WesleyV2:
None Reported
[Micromax A106 Unite 2] pankaj.jajoria:
titanium backup restoring working or not?

titanium backup restoring working or not? cz i tried many roms bt titanium backup stucks at restoring process...

titanium backup only works with cleankat rom :)
[Micromax A106 Unite 2] WesleyV2:
Titanium Backup is Reported As Working By A User...Use Rooting Zip Provided And Enjoy
[Micromax A106 Unite 2] pankaj.jajoria:
i mean no root issue.... it stuck on restoring apps....!!
[Micromax A106 Unite 2] dgattupalli:
Yes it is working and it did work in all kk ROMs (I tried all of them)
[Micromax A106 Unite 2] Debanyoti Biswas:
Good work bro. . .thanks

pls provie pureperformance zip link
[Micromax A106 Unite 2] WesleyV2:
http://xdaforums.com/showthread.php?t=2360670

use stock version also thank the dev:good:
[Micromax A106 Unite 2] saikiransama:
Well Good One.. Why can't we root directly via Kingroot App... ?
[Micromax A106 Unite 2] ameetpawar00:
system update is available but not able to do it .... plzzzz help
[Micromax A106 Unite 2] WesleyV2:
system update for lenovo devices only...since we own a mmx we have to port it
[Micromax A106 Unite 2] spavanraju:
Is there will be any problem to revert back to another custom rom?? as the zip contains a folder "root"

---------- Post added at 02:33 PM ---------- Previous post was at 02:25 PM ----------

I tried installing.! there is an error saying update script failed like...
[Micromax A106 Unite 2] spavanraju:
anyone really tried this rom??

---------- Post added at 06:15 PM ---------- Previous post was at 06:11 PM ----------

it is not at all working in any condition in twrp!!

there are errors in creating zip file.
[Micromax A106 Unite 2] kuzonov98:
Nice ROM! Love this UI! :) Thanks button pressed!
[Micromax A106 Unite 2] Menimeraj:
otg

Is the otg working????
[Micromax A106 Unite 2] rajan97:
:):):)

thanks for doing this great job

just continue
[Micromax A106 Unite 2] richard el renthlei:
Please can you tell me how to change icon for dialer and message and contacts app????
[Micromax A106 Unite 2] Sahadev Rathor:
Can flash on lollipop Better L ROM........?
[EVO Shift 4G Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM][JB][4.3][OFFICIAL] Evervolv || 3.3.0p1 || AOSP || Nightlies

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.

Before posting, please use the forum search and read through the discussion thread for [ROM][JB][4.3][OFFICIAL] Evervolv || 3.3.0p1 || AOSP || Nightlies. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy S III Q&A, Help & Troubleshooting] adi1443:
hi guyz..i have samsung i9003 its stuck on boot logo..when i get it to download mode its didn't connect to computer.i have replaced the usb connecter all print are okay 100%.. is there any solution for dat..plzz guyz help me..:(
[Galaxy S III Q&A, Help & Troubleshooting] KeTuRr74:
Hi

Have you installed the drivers for the i9300 ?
[Ascend Mate 7 Q&A, Help & Troubleshooting] tmorterlaing:
MT7-L09 - UK model.

I can't remember exactly how this has happened but basically I had a demo version of the device, so flashed it with a TL10 things (Huawei being unclear, I blame them), then reset it a bunch of times because (as expected) things were going wrong. I then Unlocked, rooted etc, and flashed another firmware. The phone reverted to Chinese, called itself JAZZ. I managed to get it back to british, flashed another firmware and everything is OK ish - BUT a factory reset wipes everything and does not theme it like 'out of the box'. There's also a few apps I don't think should be there, like 'Payment UICC'.

I've tried using the unpacker and flashing boot.img, recovery.img, system.img cust.img etc etc, but when I go to factory reset it still has the same issue.

To be honest, I don't even know which the latest UK firmware is - and I don't know if the UK firmware is different toe the EU firmware.

Please help, I'm totally stuck here :(
[Ascend Mate 7 Q&A, Help & Troubleshooting] lorenzw:
re cust fail

I am in the same case as you and so far I have not found solutions;

it would take a backup of the system.

I have the European model.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
guys flash appropriate recovery and force flash via adb ..
[Ascend Mate 7 Q&A, Help & Troubleshooting] edilmacbook30:
I have the same problem on the TL10 eu but do not know which and the procedure to do it via adb

not familiar with the commands!!!
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
can u upload pic how that cust fail looks like ? never had this problem..
[Ascend Mate 7 Q&A, Help & Troubleshooting] tmorterlaing:
I don't suppose anyone here with a UK model (L09) Can help me out there at all? Would I be able to do a nandroid restore from someone elses phone?

Ugh - some more help is needed! I have flashed EVERY RECOVERY that works, and you CAN'T just force flash via ADB because it doesn' let you on every partition.

-Where is the 'appropriate recovery' for the L09?

-Where are the latest firmware restore imgs?

HOWEVER, even in the few instances when I WAS able to flash the cust.img (as I said in the OP) it didn't help - it still says 'cust fail' during the factory reset. And then it's wiped and reset, but not 'out of box' - all theming is gone, apps all over the screen, apps I don;t even know if should be there, polaris office not installed etc.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
man if u search mate 7 forum ull find it ..
[Ascend Mate 7 Q&A, Help & Troubleshooting] Xybirium:
https://www.google.com.my/webhp?sou...on=1&espv=2&ie=UTF-8#q=MT7-L09V100R001C00B127
[Ascend Mate 7 Q&A, Help & Troubleshooting] tmorterlaing:
Update: so I downloaded the kindly provided firmware above, and doing a force upgrade gets the 'update' bar all the way to the end, where it just freezes. After about 2 hours I unplugged the phone, and that seems to trigger an 'update failed' message - so that didnt work.

Also th sim card isn't being recognised - which I assume is to do with my baseband? Its currently 21.213.00.00.031

But because I can't flash the modem (see below) I can't seem to do anything about it...

So, I tried to use the extractor, and try to flash each img it extracts from fastboot. I try to fastboot flash:

system: success

cust: success

modem: FAILED (remote: Command not allowed)

boot: success

cache: success

ptable: FAILED (remote: Command not allowed)

fastboot: FAILED (remote: Command not allowed)

recovery: success

userdata: success

When I made it Chinese by accident, is there a chance the partitions where somehow messed up, like resized or something? It's so frustrating that a factory reset doesnt put it how it should, because that means something isn't right... and it also means future updates probably won't work.

Is there anything I can do?
[Ascend Mate 7 Q&A, Help & Troubleshooting] Volgot:
Hi,

I have mt7-l09 french and the same situation (120->chinese->120->cust fail)

No ip calls, also

Tried: extractor, adb, shell commands (rooted)..
[Ascend Mate 7 Q&A, Help & Troubleshooting] deraiz12:
[MENTION=818222]Volgot[/MENTION]

Hi, you have a solution ?
[Ascend Mate 7 Q&A, Help & Troubleshooting] Volgot:
yes! and no..

lollipop instalation fixed it, but..

if you go back cust fail do it too )
[XDA Assist] XDA Visitor:
System version : 210.12.40.falcon_umtsds.AsiaRetail.en.03
[XDA Assist] Darth:
Yes it will, eventually. If your device has stock firmware, stock recovery and no system changes.

You will just need to wait til it gets to you.

?
[Samsung Galaxy Nexus] musical_chairs:
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.

Downloads

Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588232905721322

Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970093

All builds: https://www.androidfilehost.com/?w=files&flid=23530

Unofficial TWRP build: https://www.androidfilehost.com/?fid=24459283995311442

Google Apps: http://opengapps.org/

- Platform: ARM

- Android: 6.0

- Variant: pico (required due to system partition restraints)

Bugs

- No mobile data out of airplane mode - reboot to fix.

XDA:DevDB Information

UNOFFICIAL CM13, ROM for the Samsung Galaxy Nexus

Contributors

musical_chairs

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.0.x

Based On: CyanogenMod

Version Information

Status: Beta

Created 2014-12-30

Last Updated 2016-07-16
[Samsung Galaxy Nexus] musical_chairs:
Sources and such

https://github.com/CyanogenMod/

https://github.com/musical-chairs

This would not be possible without [MENTION=2633638]Ziyan[/MENTION] and [MENTION=3390093]MWisBest[/MENTION]. [MENTION=1048318]zzpianoman[/MENTION] has also been a tremendous help. Be sure to visit their threads, thank them, and support their work.
[Samsung Galaxy Nexus] TheYoz:
Sweet... can't wait to try this out! There is no download tab btw.
[Samsung Galaxy Nexus] musical_chairs:
Yeah sorry about that, my upload failed, trying again...

Edit: I'm having problems uploading to xda, trying another option...
[Samsung Galaxy Nexus] rippedwarrior69:
There is no download for this. Cannot wait to try this out.
[Samsung Galaxy Nexus] ERIFNOMI:
I might give this a try while I wait for my GNexus to die. I want to get my hands on Lollipop and can't wait for my N6.
[Samsung Galaxy Nexus] musical_chairs:
XDA keeps giving me a server IO error, after uploading the whole file. I'm still trying to get a good upload either to xda or to another hosting site.
[Samsung Galaxy Nexus] musical_chairs:
Finally a successful upload!

https://www.androidfilehost.com/?fid=95864024717073147

Now I can start working on the next build!
[Samsung Galaxy Nexus] musical_chairs:
New build up:

https://www.androidfilehost.com/?fid=95864024717073317

Synced with cm's latest sources as of 12-31-2014. I'll be working on toroplus for a bit, trying to get ril to behave properly there, so toro will be waiting for a maybe a week, unless there are any exciting new features or bug fixes.
[Samsung Galaxy Nexus] poo706:
[MENTION=4531957]musical_chairs[/MENTION], I'm the gnex maintainer for LiquidSmooth. I have LP maguro builds that are all good, but my toro builds don't have data, and my toroplus builds don't have voice or data. I think I have toroplus figured out and I'll know with a test build that'll be done in a few hours. With toro, though, MW and I are stumped. Would you mind sharing details on how you got CM12 toro data working?

[poo]
[Samsung Galaxy Nexus] musical_chairs:
Sure! I'm currently stuck with toroplus, ril is completely broken, no service of any kind. I'd be interested in knowing how you got that working.

For data on toro, I picked these commits from MWisBest's github:

https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af

https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978

I also added some stuff to system.prop, patch is attached to this post. Again, I take no credit for it, it's copied from MWisBest.
[Samsung Galaxy Nexus] poo706:
If I manage to get toroplus going, I'll certainly relay that back to you.

I've also applied those same commits from MW, and I'm pretty sure I'm using all the same build.prop entries. What was your starting point? device_samsung_toro from CM? What I did (at ziyan's advice) was start with the latest JB-era repo from google, apply like 5 commits from Ziyan's maguro repo, then the MW stuff.

[poo]
[Samsung Galaxy Nexus] musical_chairs:
device_samsung_toro is from cm, cm-11.0 branch. device_samsung_tuna and proprietary_vendor_samsung are from Ziyan, cm-12.0 branch.
[Samsung Galaxy Nexus] poo706:
Ok, that gives me something to try then. I'm also using the same tuna and samsung vendor repos. Are you using ziyan's omap kernel repo?

[poo]
[Samsung Galaxy Nexus] musical_chairs:
Yes.
[Samsung Galaxy Nexus] arigr:
waitin to see how this turns out...appreciate your work here...
[Samsung Galaxy Nexus] rippedwarrior69:
I flashed this just to try it out. It looks amazing. Is there no mobile data on this rom? I am on verizon i515. I flashed it had the signal bars but said disconneted. I did have a imei number. I flashed with cwm touch 6.0.4.3
[Samsung Galaxy Nexus] musical_chairs:
There is supposed to be mobile data, it works here. I don't think I did anything special to get it working, though I did mess around a bit with some settings (Testing menu settings, APN settings) on my first few builds and haven't done a clean flash real recently.
[Samsung Galaxy Nexus] rippedwarrior69:
I'm new to this phone. I thought you could just flash like I did on my note 2 i605. If mobile data works I want some 5.0
[Samsung Galaxy Nexus] musical_chairs:
It looks like I had the same issue as zzpianoman on his cm12 build. If you flash his APN fix, you should get working data:

http://xdaforums.com/showpost.php?p=57890624&postcount=17
[Samsung Galaxy Nexus] christianpeso:
On the 7/1 build, I also received the SIM card missing message. It installed fine, but no data. Shut down, removed and reinserted SIM card and still same thing.
[Samsung Galaxy Nexus] musical_chairs:
Now that you mention it, I have seen some weirdness with the unread messages thing. But I seldom get groups messages (other than from a few Apple users, but I try not to hang out with them too much - LOL)

Seeing 'No sim card' for fifteen seconds after boot is fairly normal. Persistent 'no sim card' is another story. One of the bigger changes in the 6-29 build was a switch to an open source libsecril-client, which didn't seem to cause any problems at the time, but who knows. Also, it's been a while since I poked around in the samsung/toro vendor tree, I should probably look around in there in case something is out of place.
[Samsung Galaxy Nexus] christianpeso:
No, it was persistent. Left it on for about 15 minutes and the message stayed there as well as saying "no signal" by the bars on the status bar. Put it in airplane mode and back same thing. Turned wifi on and off, same thing.
[Samsung Galaxy Nexus] musical_chairs:
A new build is up. Only differences from 7-1 would be syncing with cyanogenmod. Since I never announced the 7-1 build properly, I never got around to mentioning that it includes in-call mute fixes from MWisBest. In-call mute was working before thanks to a workaround from zzpianoman. It's a bit faster now though, and the mic icon correctly shows that it's muted. Also, it means one less forked tree for me to maintain.
[Samsung Galaxy Nexus] christianpeso:
7-7 build is good. Not getting the SIM card message as I did on the 7-1 issue.

I am seeing the phone drop 4G relatively quick down to 3G. And when it gets into 3G, it seems like it has a hard time coming out of it. And this is in places I used to get 4G service. A reboot usually gets me back to the correct signal. Other than that, keep up the great work!
[Samsung Galaxy Nexus] dalvear88:
So far I'm enjoying the 7-7 build, it's working smoothly so far. I do have a question, is there a way to get rid of the root usage icon (#) in the notification bar? I can't seem to find a way to get rid of it.
[Samsung Galaxy Nexus] musical_chairs:
I didn't build in any way to disable that, I opted to go with CyanogenMod's default behavior here. I know, it gets annnoying sometimes...

If you're using an app that needs root to get in and do something, and then it's done, it's not too bad. Just swipe away the app in recents after you exit, and the icon will go away. For a root app that sets stuff on boot, open the app, exit it, and swipe it away in recents, and the icon will disappear. If it's an app that regularly uses root (like a firewall that writes rules every time your network connections change) then it gets to be more of a pain, the icon will be there most of the time.
[Samsung Galaxy Nexus] zzpianoman:
If you're interested, I picked this from LiquidSmooth. Allows you to change the su indicator to a notification or disable it entirely.

fwb:

https://github.com/zzpianoman/andro...mmit/f06893540f6046b5b760289776ae8cc92e2f7ae7

Settings:

https://github.com/zzpianoman/andro...mmit/1978fc65f975a4bebbb0df09b917abd1ae836668
[Samsung Galaxy Nexus] musical_chairs:
New build up. I pulled in an open commit that gets rid of the spinner on the 'optimizing apps' screen - apparently the spinner animation was chewing up almost as much CPU power as dex2oat. So the initial boot should be a bit faster now.

Other than that, and the usual sync'age with the latest CM sources, not much to report.
[Samsung Galaxy Nexus] dumas777:
fsck the Encryption unsuccesful screen

First of all this rom really rocks and I greatly appreciate and love it. That said it seems after doing some googleing that Android's built in full disk encryption is garbage. In addition the big penalty on performance (willing to accept) its very flaky on a variety of platforms (plenty of horror stories out there about it) including sadly its seems my verizon gnex. I have done everything including going back to locking the boot loader and stock rom (And unlocking only installing this rom) and all to no avail. I have tried everything (am using settings>security>encrypt and setting patterns, passwords, pins, nothing, etc before, guess command line might be next) and rebooted at least 20x to the encryption unsuccessful (encryption interrupted) screen (although nothing seems to get encrypted so a reset is not necessary but have done plenty of times anyway). This includes doing so with nothing but a newly flashed rom and storage wiped. Has anybody else had problem or success with it on this rom? I am pretty sure its not rom specific as it is general Android functionality and I have the same problem with the other unofficial lollipop cyan rom on here. In general it seems lollipop is nice for an old cheap backup phone but have to say on my main iPhone phone one thing iOS does kicks Android's ass on is whole phone encryption in just about every way. Still it would be nice to have a working encrypted secure private backup phone (long live F-Droid and having nothing under settings>accounts) that I don't have to worry about any work stuff on.
[Samsung Galaxy Nexus] dumas777:
Oh the irony

Ok it turns out it looks like at least on my handset its a problem with the latest cyanogenmod and perhaps lollipop in general (may also be the interaction with the latest versions of TRWP and CWM). After another factory reset I tried the factory rom and voila it encrypted just fine. I then flashed both cyanogenmod lollipop roms on here (but not FML) with both Clockworkmod and TWRP and setting up encryption failed on both (after a data wipe obviously). Finally I gave up after the failures and without doing anything but a regular data wipe with TRWP and installed Omni 4.4.4 rom and again encryption worked right out of the box. I tried everything before including setting up the partitions by hand from the command line and all for naught. Its too bad really because Lollipop is a lot better (especially this rom) but no encryption is a deal breaker for me.
[Samsung Galaxy Nexus] musical_chairs:
There's a new build up. Headset controls should be working again, and the stagefright fixes are there as well. Actually, they were already included in the previous build, though I wasn't aware of it at the time.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Interesting changes are:

- Low ram tweaks from Ziyan

- Additional low ram tweaks from zzpianoman

(Ziyan's tweaks enable low ram optimazations, zzpianoman's tweaks promptly turn around and lie about it to your apps)

- Fixes for the stagefright fixes
[Samsung Galaxy Nexus] Zen_Man:
Downloading it now, can't wait to try it. Any plans on bringing Marshmallow to the Toro? I know it's very early, just curious and thanks!
[Samsung Galaxy Nexus] SynbiosVyse:
Are you sure zzpianoman's tweaks are good? Your ROM is a lot snappier than his (I'm not sure why).
[Samsung Galaxy Nexus] musical_chairs:
Well he's a lot more adventurous (and a lot more capable) than I am, there are definitely benefits to that but there is also the potential for drawbacks. In this case, the code I borrowed from him just hides the low ram flag from apps, so, for instance, panorama and photosphere will still work on Google camera. So it shouldn't negatively impact performance, not when compared to running without any of the low-ram tweaks

That being said, my phone has been lagging very badly this evening, especially when receiving phone calls, bad enough that it made me miss two calls. I may just take those tweaks out again if it keeps acting like that.
[Samsung Galaxy Nexus] SynbiosVyse:
I also noticed you dropped your Low Memory Killer (LMK) settings a little bit, I think your original aggressive settings were pretty good. It may be worth it to revert back to your old settings to see if that fixes that particular problem?

The lagging phone (mainly appearance of call-related buttons, etc) was something I definitely noticed on zzpianoman's build. Though I've matched your old LMK and CPU governor settings of your build to his build, and it was still noticeably more laggy for me so that's why I say I don't know what the problem was. It must have been another setting I haven't checked or something in the kernel. That's why I'm sticking with your ROM and original, aggressive LMK.
[Samsung Galaxy Nexus] christianpeso:
So far so good for me. Back trying LP ROMS. Been using Kit Kat as it has been more stable and faster for me. Installed this rom with newest TK Pico Gapps. Then installed Bsmittys newest LP kernel and overclocked to 152000. Then installed this mods apps from slaid480:

http://xdaforums.com/android/apps-games/app-fly-mod-app-alpha1-feel-smoothness-t3171503/page10

Turned everything on in the app which includes various tweaks to system and RAM management..

All animations turned off. Using Nova Launcher with all animations set to fastest.

Been running now for about 8 hours and it is definitely better than my previous experiences with LP. Will know better tomorrow when I take it to work and actually use it as hard as I would normally. Thats when the lag and stutters would normally start. But so far so good. Thanks!