[guide] Repair bootloop wrong recovery flash Huawei G750-u10 / honor 3-u10 topic

this tutorial, is for repairing the huawei g750-u10 in case you flashed the wrong recovery and now you're stuck in a bootloop.

First of all you will need (it's all in the link to download, make shure you have a sdcard on your phone before starting):
-Adb install setup
-Adb toolkit
-vcom drivers

mega.co.nz/#!gURHXDoZ!QNmv7LaK8r4WIQBGaUyoNho3TPX0YZp9jwHaEHg DmII


-Installation of the phone mediatek drivers:

-Start with installing th vcom drivers i provided on the rar file, type HDWWIZ on the windows search tab:

Install the hardware manually>Ports(com&lpt)>Have a disk>select the file wich corresponds to you windows>mediatekpreloader usb vcom port> restart your computer. (if this method doesn't work for you try to search for vcom driver installation tutorials)

-Installing adb


-double click on the adb-setup.exe file provided and install it including drivers.
-the adb tool kit doesn't need installation just run the Adb toolkit Gui

on adb toolkit, type the command fastboot continue as shown in the picture

s13.postimg.org/yuauaawpj/Untitled.jpg

Remove the battery from your mobile phone, wait 5s plug it in again and push the power button till it turns on but keep your finger in the VOLUME DOWN, it may reboot 2 times but then you will get the fastboot/repair mode image.

When you are in fastboot, connect your phone to the usb in the computer (the mediatek drivers will install wait for installation to complete).
Now return to the Adb GUI and press the execute command, it will appear something like and wait a few seconds then your phone will restart it self and boot normally.

You're allmost there:

-When your phone boots, select the usb connection to usb mass storage device.
-copy the recovery.img provided to the root of your sdcard, safely unplug the phone from your pc.
-download and install the mobile mtk uncle tools app from the playstore.
-turn off wifi and mobile data, start the app and give it root permission.
-press the recovery update, select the chinese character file that you copied to your sd before and proceed, VERY IMPORTANT when it asks if you want to reboot into recovery select NO.
- get out off the app and restart your device normally, it's all done you have your phone back. :D


this is my first tutorial on xda, hope it is easy to follow and i'm thankfull for any suggestions to improve it.

[ROOT] Tab 4 SM-T230 [GUIDE] topic

Firstly i have spent the best part of 5 days searching for a root method on the sm-t230 tab 4 and got no where until about 5 mins ago and just for reference and others i am going to put this guide here..

*** I AM NOT RESPONSIBLE FOR YOU DAMAGING YOUR DEVICE IN ANY WAY. THIS METHOD OF ROOT IS TESTED BY ME ON THE DEVICE SM-T230 IF IT WORKS FOR OTHER DEVICES THEN PM ME AND I WILL MAKE A LIST OF SUPPORTED DEVICES.. ***

THINGS NEEDED

> TAB 4 WIFI SM-T230 WITH USB DEBUGGING ENABLED AND DRIVERS INSTALLED
> ADB TOOLS FOR INSTALLING SUPERSU
> ODIN 3.07 + TWRP + SUPERSU ALL WHICH CAN BE FOUND IN THIS ZIP FILE >> DOWNLOAD

THE GUIDE

1. Download and extract the above zip to an easy to access location.

2. put the device into download mode by holding power+vol down+home and connect to computer with usb cable.

3. now run odin 3.07 and select AP and then select the twrp_2.7.1.0_SM-T230.tar.md5 file

4 .hit start in odinand as soon as odin is finished the device turns off for reboot DONT let android boot quickly press power+vol up+home to boot into twrp recovery

5. now goto advanced > adb sideload

6. now open a cmd on computer and use adb to sideload the SuperSU.zip file
eg, adb sideload location/of/zip/SuperSu.zip

7. twrp will now install supersu and binarys

8. reboot as normal to android and download rootchecker form gplay and check for root also granting root access when asked..

9. now also download busybox and install..

you now have rooted your tab 4 sm-t230

dont forget to use the thanks button :P

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system topic

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system

Under Fastboot
- fastboot flash boot bootll.img (From http://forum.xda-developers.com/g-wa...tch-r-t2956964)
- fastboot flash recovery twrp.img (From http://forum.xda-developers.com/g-wa...wrp-r-t2960511)
Go to Recovery and format all twice with TWRP recovery

Flashing back stock recovery :
- fastboot flash recovery recoverll.img (From http://forum.xda-developers.com/g-wa...tch-r-t2956964)
Back to stock recovery, format twice

Regenereting system step :
- fastboot flash system systemo.img (From http://forum.xda-developers.com/g-wa...ooted-t2981075)

Go back to stock recovery, Choose apply update from ADB (adb sideload)
- adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip (From http://android.clients.google.com/pa...R.149e0c34.zip)
Reboot system now. Choose langage, etc.

Pushing SU, autorize adb debug on the watch
- adb push supersu.zip /sdcard/su.zip
- adb reboot bootloader
- fastboot flash system system.img (from http://forum.xda-developers.com/g-wa...ooted-t2981075)
- fastboot flash recovery twrp.img

Restart watch and go to TWRP recovery, install/flash su.zip from sdcard

Et Voilà ! :cool:

[Q&A] [GUIDE] Recover From Soft Brick ! S-On Unlocked ! topic

Q&A for [GUIDE] Recover From Soft Brick ! S-On Unlocked !

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 [GUIDE] Recover From Soft Brick ! S-On Unlocked !. 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! :)

[GUIDE]Newbie Guide for How to Root/Flash Recovery on Canvas A111 topic

Hi good day to all am RJ am going to guide how to ROOT / FLASH RECOVERY in Micro max Canvas A111 jb4.1.2
WARNING: If your Micromax Canvas A111 smartphone gets bricked or gets damaged while following the tutorial given below, we shouldn’t be held responsible. Proceed at your OWN RISK.

I will try to keep this guide up to date. Please let me know if you find something wrong or missing

Content:
1) Introduction
2) How to root
3) How to flash recovery
4) FAQs (ADB, Loki, Download Mode, Go to Recovery etc.)
5) Troubleshooting (unbricking)

1) Introduction:
Micromax Canvas Doodle a111 is a 3G Android smartphone with a 5-inch TFT HD Touchscreen display. The phone is powered with 1.2 GHz Quad-Core Processor and it runs on Android 4.1.2 Jelly bean OS. With 8 mega pixel rear view camera, the phone offers high quality image capturing. If you are looking for a smartphone under 10000 INR with good features, then Micromax Canvas A111 would be the ideal choice!
If you are a user of Micromax Canvas Doodle a111 and would like to gain root access for installing rooted apps or custom ROM’s, then the following tutorial will help you. I have given step by step instructions for rooting A111 smartphone below

2) How to root:

Prerequisites To Root Micromax Canvas A111 Smartphone

1. Take complete backup of your personal data in the Micromax device using appropriate apps. Although the root process won’t affect them, its safe to keep a backup.
2. Remove all the Antivirus applications installed on your smartphone for virus protection since sometimes they will cause trouble while the rooting process is going on.
3. Charge your phone battery and keep its backup level above 80% as the rooting process drains the battery. If you don’t have enough battery backup and your device gets switched off during the rooting, then surely it will get bricked. Avoid it by having a good battery backup.
4. ***Enable USB Debugging mode in your device by following the path: Settings -> Developer Option -> USB Debugging.
5. *** Make sure you have drivers for your phone Download from here http://www.androidrootguide.com/micr...ax-smartphones
Once you have done all the above mentioned tasks, you can move on to the rooting tutorial given below.

download any one application from bellow links

1. For VROOT :: click here
2. For Root Genius:: click here
Tutorial To Root Micromax Canvas A111
> To get started, download VROOT / Root Genius from bellow link and install it on your computer. Once installed, open the application.
> Now connect your Micromax Canvas A111 smartphone to the computer using the “USB Debugging Mode”. If you have installed the required USB drivers for your phone on the computer, then the VROOT application will automatically detect your smartphone.
> Now just click on the “Root” button shown on the VROOT / Root Genius window and let the rooting process begin. The smartphone will get restarted several times during the process. So, don’t panic. Once the rooting process is finished, the device will reboot for one more time.
> Thats it. Now you have successfully rooted your Micromax Canvas A111 smartphone. If you want to confirm whether you have successfully rooted or not, use the “Root Checker” app. If you encounter any issues while following this rooting tutorial, do let me know via comments.
****** if u not able to understand the above please click on the Link it will more easy http://rjpraveen.blogspot.in/2014/08/how-to-root-micromax-canvas-doodle-a111.html

[Guide] How to play HD games on Xperia E3 topic

Hello guys!!
I am creating this thread as seeing so many of question about running and installing HD games (only Obb folder Games) on our Xperia E3/dual So here it is :-
Requirement :-
1- Root (see Tutorial on forum)
2- Install Xposed installer ( Download from attachments )
3- Install Obb to Sd Module for Xposed Framework ( Download from attachments )
4- Good Sd card( recommended class10 )

Instructions:-

1- First your phone should be rooted.
2- After Rooting install Xposed installer ( install according to its instructions ) and reboot your phone.
3- Again after rebooting install Obb to Sd module apk and reboot your phone.
4- Now just Install Your Game apk and directly move data from your Pc to External Sd>Android>Obb>here
5- Don't be upset mainly most of the games are of OBB files:fingers-crossed: ;)
6- Woillaaa Enjoy Gaming on this Superb performence Phone.:fingers-crossed:

Hit Thanks if you liked it :)

Attached Thumbnails

 


 

Attached Files

	xposed.installer.apk - [Click for QR Code] (711.8 KB)
	Obb on SD.apk - [Click for QR Code] (12.1 KB)

looking for guide when converting 'google-api-java-client' to android studio project topic

looking for guide when converting 'google-api-java-client' to android studio project.

i have found google android api for android.
you could search on google 'Google APIs Client Library for Java'.
but this is outdated.
having trouble when converting to current version of android studio.

[GUIDE] CPU Governor's Explained topic

Many basic android users must be confused about what are Governors...what to they do.
So in this thread Each & Every governor is well explained..to clear all of ur doubts.


Link to another thread where Android Kernel/Governors/Tweaking well explained by @droidphile

http://forum.xda-developers.com/show....php?t=1369817

Most of us are flash maniacs, and we do it a lot. But after a kernel flash, we wonder: what actually are governors :what:



Android CPU governors explained



1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
22: BadAss
23: Wheatley
24: Lulzactive
25: Pegasusq/Pegasusd
26: hotplugx
27: AbissPlug
28: MSM DCVS
29: IntelliActive
30: Adaptive
31: Nightmare
32: ZZmove

Info on I/O Scheduler go here:

http://forum.xda-developers.com/show....php?p=7649851



1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to bitch about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.


2: OndemandX:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.


3: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).


4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.


5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.


6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.


7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.


8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.


9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.


10: Smartass
Is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"


11: SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.


12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.


13: Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.


14: Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL


15: Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery


16: SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.


17: Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.


18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.


19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.


20: Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.

25: Pegasusq/Pegasusd

The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging.

Press Thanks :thumbup: If I Helped U :)

[GUIDE] I/O Scheduler's Explained topic

I/O SCHEDULERS

Thnx to @droidphile for clearing the concepts.

Here each & every concept of I/O Sched. is very clearly explained.

After reading the post i can assure u that will have sufficient knowledge about I/O Schedulers & u will be able to choose I/O schedulers easily which suits ur needs & and the phone best depending upon the type of work load u put on ur Android Smartphone.

Q. "What purposes does an i/o scheduler serve?"

A. Minimize hard disk seek latency.
Prioritize I/O requests from processes.
Allocate disk bandwidth for running processes.
Guarantee that certain requests will be served before a deadline.
So in the simplest of simplest form: Kernel controls the disk access using I/O Scheduler.

Q. "What goals every I/O scheduler tries to balance?"

A. Fairness (let every process have its share of the access to disk)
Performance (try to serve requests close to current disk head position first, because seeking there is fastest)
Real-time (guarantee that a request is serviced in a given time)

Description, advantages, disadvantages of each I/O Scheduler?

List of I/O Schedulers:-
1) Noop
2) Deadline
3) CFQ
4) BFQ
5) SIO
6) V(R)
7) Anticipatory

1) Noop

Inserts all the incoming I/O requests to a First In First Out queue and implements request merging.

Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives).

Advantage here is that flash drives does not
require reordering of multiple I/O requests unlike in normal hard drives.

Advantages:

Serves I/O requests with least number of cpu cycles.
(Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.

Disadvantages:

Reduction in number of cpu cycles used is proportional
to drop in performance.


2) Deadline

Goal is to minimize I/O latency or starvation of a request.
The same is achieved by round robin policy to be fair
among multiple I/O requests. Five queues are
aggressively used to reorder incoming requests.

Advantages:

Nearly a real time scheduler.

Excels in reducing latency of any given single I/O.

Best scheduler for database access and queries.

Bandwidth requirement of a process - what percentage of

CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.

Disadvantages:

When system is overloaded, set of processes that may miss deadline is largely unpredictable.


3) CFQ

Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests.

Each per-process queue contains synchronous requests from processes.

Time slice allocated for each queue
depends on the priority of the 'parent' process.
V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.

Advantages:

Considered to deliver a balanced i/o performance.

Easiest to tune.

Excels on multiprocessor systems.

Best database system performance after deadline.

Disadvantages:

Some users report media scanning takes longest to complete using CFQ.

This could be because of the property that since the bandwidth is equally distributed
to all i/o operations during boot-up, media scanning is not given any special priority.

Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.


4) BFQ

Instead of time slices allocation by CFQ, BFQ assigns budgets.

Disk is granted to an active process until it's
budget (number of sectors) expires.

BFQ assigns high budgets to non-read tasks.

Budget assigned to a process varies over time as a function of it's behavior.

Advantages:

Believed to be very good for usb data transfer rate.

Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)

Considered an accurate i/o scheduler.

Achieves about 30% more throughput than CFQ on most workloads.

Disadvantages:

Not the best scheduler for benchmarking.

Higher budget assigned to a process can affect interactivity and increased latency.

5) SIO

Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests.

No priority queues concepts, but only basic merging.

Sio is a mix between noop & deadline. No reordering or sorting of requests.

Advantages:

Simple, so reliable.

Minimized starvation of requests.


Disadvantages:

Slow random-read speeds on flash drives, compared to other schedulers.

Sequential-read speeds on flash drives also not so good.

6) V(R)

Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness.

The next request to be served is
based on it's distance from last request.

Advantages:

May be best for benchmarking because at the peak of it's 'form' VR performs best.

Disadvantages:

Performance fluctuation results in below-average performance at times.

Least reliable/most unstable.

7) Anticipatory

Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.

So anticipatory prioritize read operations over write.

It anticipates synchronous read operations.

Advantages:

Read requests from processes are never starved.

As good as noop for read-performance on flash drives.

Disadvantages:

'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.

Frequently asked questions

Q. "Best I/O Scheduler?"
A. There is nothing called "best" i/o scheduler. Depending
on your usage environment and tasks/apps been run,
use different schedulers. That's the best i can suggest.
However, considering the overall performance, battery,
reliability and low latency, it is believed that
SIO > Noop > Deadline > VR > BFQ > CFQ, given all
schedulers are tweaked and the storage used is a flash
device.

Q. "How do i change I/O schedulers?"
A.Voltage Control or No Frills from market.
Or init.d script:

echo "scheduler-name" > /sys/block/mmcblk0/queue/
scheduler


------------------------------------++END++---------------------------------------

Press Thanks :thumbup: If I Helped U :)

[Guide] [Unbrick] Moto G XT1033 on Android 5.0 Lollipop [Brazilian Update] topic

First of all don't panic. :laugh: There is a solution for your soft bricked moto ;)

NOTE- This method is used for soft bricked moto g.
Soft Brick- When your device is in a bootloop and it can boot into bootloader or fastboot.
Hard Brick- When your device is complete gone and it doesn't even boots.

Now flash the Brazilian Kitkat 4.4.4 using this way :-
NOTE- Dont flash or restore your previous backup of 4.4.2! It will brick your device!
Brazilian kitkat 4.4.4 link- http://www.mediafire.com/download/5c...FF_SVC.xml.zip
Download mfastboot - https://docs.google.com/file/d/0B4PT...9EV2lGcWs/edit
Extract mfastboot and the brazilian 4.4.4 in the same folder and open command prompt in that folder. ( press ctrl+shift+right click- open command line here)

Connect your moto g to pc in fastboot mode.
In the command prompt flash 4.4.4 using the following commands :-

mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

Remember- Flash using the following commands only as they have skipped bootloader and partition table file of kitkat or you would HARD-BRICK your device.

Now let it boot. The screen would be flickering after the boot. Dont panic :p . Now after the boot has finished. Transfer moto g brazilian update to your phone and reboot into recovery. Place in on the root of your sdcard.

Link - http://www.mediafire.com/download/w1...asil.en.BR.zip

Now reboot into recovery and apply update from sdcard. Wait for 10-15 mins.

Congratulations! You have unbricked your moto g!! :highfive: :laugh: :D

If i helped you. Please be Kind Enough to press the Thanks Button. ;) Not just say thanks press thanks. ;)

[GUIDE] how to deodex any app without pc(fully working)(any android) topic

Hi guys,
This is my first guide here on XDA
it's about deodexing any app without pc and with mobile apktool







Requirements:
Root
Busybox installed
Mobile apktool properly installed (link below)










How to deodex any app:
1. Root your device
2. Install busybox
3. Install mobile apktool properly
4. Now copy the apk and the odex ob that app to the same folder
3. Make sure that the name of the apk and odex are the same
4. Decompile the odex
5. Now do nothing and just recompile it
6. It will recompile in dex format
7. Again make sure that the name of both the apk and dex(not odex) are the same
8. Now click on the dex and select "add to apk with same name"
9. All done, follow this and you can deodex any app in minutes









Link:
https://code.google.com/p/apktool/do...4.4_armhf.zip&











Credits:
All the credits goes to the developer of mobile apktool









It will definitely work on any android, post here if you face any problem while following this guide

Surface Pro 3 WIMBoot ROM + guide + discussion topic

TEST BUILDS:

December build [please search in surfaceforums, as I couldn't post links here]
(for next uploads, which one do you recommend: Box sync, Google Drive, MEGA, or OneDrive?)


Features:
1. Only 1.2 GB footprint on C: drive (54 GB free out of 55.2 GB C: drive on the 64 GB model. Free space increases accordingly on larger models) excluding hibernation and pagefile
2. August, September, October, November, and December update rollups slipstreamed
3. Surface Pro 3 specific updates included (KB2978002, KB2969817)
4. Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again)
- Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store
- Trial Office removed
- Speech data removed (who uses that anyway?)
5. Pen Pairing OOBE appears and working
6. Languages included: Dutch, English, German, French. Since it is Windows 8 Pro, you can download any other language later.
7. WinRE from vanilla Windows, 200 MB saving (working so far, please report if something wrong happened)


I have been using this build for 2 days, as well as the previous, similar build for a week. No issues experienced from my side.


This *might* also work on the Surface Pro 2 since they have similar components. Not tested.






How to install:
0. Get a keyboard and USB hub (Type Cover might also work, but I don't have one to test)
1. Download and extract the package with WinRAR
2. Set up the ISO image on a CD or USB stick.
- If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part43.txt (part43.txt means the recovery partition is 4300MB. I tried 4200MB, it didn't work)
6. Enter applywim D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.





____________GUIDE____________

First of all, I would like to thank murphy78 from mydigitallife.info forum for creating the noob-friendly guide for creating WIMBoot image (friendlier than Microsoft's version, at least).

Here I tried doing it using Surface Pro 3's recovery image instead of clean Windows which is used on his/her guide. I recommend this especially for 64 GB model users, or if you want to deploy 64 GB Surface Pro 3s. 128 GB users can benefit too.

I don't really recommend this for 256 or 512 GB SP3s, since the additional free space is not worth the effort IMO (of course, youre free to do it, its YOUR SP3, after all).

(I copied most of the steps from murphy78's, unless changes are necessary)


(use elevated cmd when necessary)
Preparing the Windows PE files (only for applying the image, NOT installed on the SP3)

1. Run the ADK commandline shortcut from start menu


2. Run the following command: copype amd64 c:\WINPE_AMD64


3. Mount the boot.wim from c:\WinPE_AMD64\media\sources\ and add the update msu packages


4. Extract the 7z from the link in this post to the c:\winpe_amd64\media\Scripts folder (create folder if you need to)

Preparing the WIM image to be applied
(Surface Pro 3 has Windows 8.1 Update 1 included. If youre doing this on the Surface Pro or Pro 2, you might need to update it.)

1. Download SurfacePro3_BMR_20_3.4.1.zip recovery image from the official site


2. Copy install.swm, install2.swm, and install3.swm from SurfacePro3_BMR_20_3.4.1\sources\ to \Deployment Tools\amd64\DISM\ where imagex.exe resides (inside ADK)


3. Open cmd in that directory and run the following command:
   imagex /ref install*.swm /check /export install.swm * install.wim "SurfacePro3"


4. Mount the WIM image using the following command, change the directory if necessary
   Dism /Mount-Image /ImageFile:"C:\SurfacePro3_BMR_20_3.4.1\sources\ins tall.wim" /Index:1 /MountDir:C:\mount\


5. Move the winre.wim from the windows\system32\recovery\ folder to c:\winpe_amd64\media\Images\ (might need to turn on see system files)


6. Remove the system file attribute by running: attrib –s -h c:\winpe_amd64\media\images\winre.wim


7. Optimize the image for WIMboot using the following command:
   Dism /Optimize-Image /Image:C:\mount\ /WIMBoot


8. Capture the optimized image using the following command: DISM /Capture-Image /WIMBoot /ImageFile:" C:\WINPE_AMD64\media\Images\install.wim" /CaptureDir:C:\mount\ /Name:"SurfacePro3_WIMBoot"
   (create folder if needed)

Creating the WIMBoot ISO

1. Move the captured install.wim to c:\winpe_amd64\media\Images


2. Edit the partition size in D:\scripts\CreatePartitions-WIMBoot.txt. It is the combination of install.wim and winre.wim + 50 MB (no idea why, it refuses to copy the Windows RE image if I didn't give 50 MB additional space)
   The row to be edited is “shrink minimum=xxxx”


3. Create your wimboot iso by running the following oscdimg command in a directory with oscdimg (I use e:\waik5\amd64\)
   E:\waik5\amd64\oscdimg.exe -u1 -be:\waik5\amd64\efisys.bin -pEF -bootdata:2#p0,e,be:\waik5\amd64\etfsboot.com#pEF,e ,be:\waik5\amd64\efisys.bin c:\winpe_amd64\media\ c:\temp\WinPE_5.1_AMD64.iso

Now, move to the SP3

1. Boot from the iso
   (I do recommend to this on a VM first before messing with your SP3. Make sure your VM supports virtual SSD and EFI firmware)


2. Navigate to the disk's scripts folder in the winpe command prompt. For me it was cd /d D:\scripts\


3. (If you click on the command prompt at any time and it seems to pause, just press enter and it will come back to life - learned hard way on vm)


4. Run from the scripts folder: diskpart /s CreatePartitions-WIMBoot.txt


5. After the diskpart script is done run: ApplyWimBootImage d:\Images\install.wim d:\Images\winre.wim


6. And then just reboot and let the system finish setup. You can powerdown at the user creation screen if you are setting this up for a customer. (At least it says it's safe in the chm file)

[Q&A] [GUIDE] How to root and install CWM for Galaxy V SM-G313HZ topic

Q&A for [GUIDE] How to root and install CWM for Galaxy V SM-G313HZ

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 [GUIDE] How to root and install CWM for Galaxy V SM-G313HZ. 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! :)

[Q&A] [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data topic

Q&A for [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data

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 [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data. 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! :)

[Q&A] Definitive guide to Rooting the Gear S topic

Q&A for Definitive guide to Rooting the Gear S

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 Definitive guide to Rooting the Gear S. 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! :)

[LINK] to a [GUIDE] Disable Knox and Ota without root ATT. topic

http://forum.xda-developers.com/show....php?t=2976386

I've been lurking the ATT note 4 forums and found this little guide. It doesn't Uninstall the apps just disables some that you can do normally.

For now it's at least something to help for us unfortunate ATT folk.

I tested it on my edge and it worked. Frees up a bit of ram.

Sent from my SAMSUNG-SM-N915A using XDA Free mobile app

(GUIDE) XT1097 to XT1095 Nextel and others. topic

Friends, reading a lot I was able to convert my beloved brand new (2 days old) XT1097 Nextel Mexico Moto X 2014 to the Pure edition XT1095. A lot of people says that the XT1097 bought from Motorola is Pure edition but thats not true, the only pure edition is and only will be the XT1095.

So, taking this as a start we can say that the XT1097 from a carrier is "locked" and in Nextel is almost impossible to get an update.

THIS IS NOT A FULL CREDIT TUTO... IS AN ALL-IN-ONE GUIDE AND TAKING MY OWN EXPERIENCE SHOULD BE WORK IN ANY MODEL, 1097 AND 1092..

If you are in XT1097 Android 4.4.4 and you have not received yet the OTA for Lollipop or if you tried to sideload the OTA via ADB and did not worked this is for you!!!!

WARNING!!!!
By now you should have installed the ADB drivers and the Motorola USB Drivers as well. I do not take responsability if you do not know when I am writing those commands.
Unlocking your bootloader and taking this guide is your OWN responsability and I am not responsable for bricked devices, ebola, nuclear wars of if your girlfriend leaves you for being such a nerd like me...

STEP 0. DRIVERS
A PC with Moto drivers, ADB drivers and fastbooot, mfastboot installed.

STEP 1. UNLOCK BOOTLOADER
You should unlock your bootloader, yes or yes. Sorry guys but this is the only way to get the sweet.
To unlock follow this guide.
http://forum.xda-developers.com/moto...-2014-t2876773
Although says "ONLY FOR XT1095" actually is working for any model device... thats how I unlock my moto X.

STEP 2. ROOT.
This part is essential to backup your modem (baseband) and if you do not want to loose your phone signal you definitely should root your device.
To root your device follow this guide.
http://forum.xda-developers.com/moto...motox-t2889264
Again... the post says "only for XT1095" but it is working in XT1097.

STEP 3. FIRMWARES
To convert XT1097 to 1095 and then to Lollipop you should download those two files.
The first one is the XT1095 Pure Edition 4.4.4 and this is the link. (for respect, the original uploader is @SolarTrans)
https://onedrive.live.com/?cid=227f1...MWPTB3ICDtezYs
Is the middle one.
Extract the firmware in the same carpet where the ADB and mfastboot files are.

The Lollipop file is the right one...

STEP 4. CUSTOM RECOVERY.
This step is optional, and is because if you want to keep the original firmware. You should make this step later in this post, but I leave the original thread.
http://forum.xda-developers.com/moto...overy-t2911523

Ok. Lets go.

1. Unlock your device as step 1
2. Root your device as step 2
2.1. After rooting your device you have to make a backup of your modem (baseband) and here is how.
Plug your phone to your PC, and open the carpet where the ADB drivers are, push and hold "shift" and right mouse click on open space, select "Open promp commands here"...

adb shell
su (after this you have to grand SU permissions to ADB on your phone)

dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin

dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin

After those commands you should be able to see two files on your phone internal SD. " NON-HLOS.bin" and "fsg.bin". Copy and paste to a carpet on your computer. Those files are the backup of your modem/baseband.

3. As Step 4, (optional) make a full Nandroid Backup of your firmware and save it on your computer. You maybe this need later...

4. After making all those backups we proceed to flash the XT1095 firmware.
4.1 Go to he carpet where you extracted the 4.4.4 XT1095 firmware and type these commands

adb reboot bootloader ( your phone should reboot to bootloader)
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot

Wait till your phone reboot and you will see that now you are in 4.4.4 XT1095 Pure Edition BUT with the Baseband of you own device.

5. After the reboot save the Lollipop OTA file to your internal SD memory.
6. Enter bootloader of your phone, select recovery and you will see the android robot lying down with the cheast open, press volume up and power at the same time, release the power button after at least three seconds and you will be enter the stock recovery... choose "install from SD card", select the file of Lollipop you saved before and wait till the magic happens.
6.1 After the reboot you will be on Lollipop.. but not so fast, do not enter any account and skip all the proccess, go to "settings" and make a "factory reset" just to be sure that all traces of KitKat are erased.
6.2. Let the phone reboot...
6.3. This is where the magic happens... Wait till you phone reboots and you will be on Android 5 Official, but you will not be able to get any signal, even entering to "settings" and trying to choose the signal manually, the phone will be refused to connect to any signal. So this is where we use the backup of our modem/baseband we did before (guide 2.1). If your phone is able to get signal CONGRATULATIONS!!! you only have to enter the Access points manually, but if you do not...
7. Copy the files "NON-HLOS.bin" and "fsg.bin" to the carpet where "mfastboot" is. Rename "fsg.bin" to "fsg.mbn"
7.1. BE VERY PATIENT WITH THIS, because according to some people, flashing only these files WITHOUT erasing modems you should be able to get signal, so
7.1.2 with your phone in bootloader and in mfastboot mode type

mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot reboot

After this, your phone should reboot and get signal... but if do not happen (like me) try this.
7.1.3 with you phone in bootloader and in mfastboot mode type

mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot reboot

After the reboot you should have signal yes or yes.. REGARDS!!!! you are now enjoying the sweet of Official Lollipop. :laugh:

[Q&A] [GUIDE] Compile CWM Recovery topic

Q&A for [GUIDE] Compile CWM Recovery

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 [GUIDE] Compile CWM Recovery. 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! :)

(GUIDE) Unlock Bootloader On Any Xperia Device (Video) topic

Hi guys Sony released a video how to unlock bootloader on any Xperia device. Im not a dev so i can understand what or how we do this. I hope someone find the way from this video and finally unlock our Xperia C device and bring life to our phone.

INFO+VIDEO

[Guide] How to build your own Cyanogenmod 11 for d850/d851/d852/d855/vs985/ls990 topic

Now model vs985 and d850 can get official version at download.cyanogenmod.com

Support model for this method are d850/d851/d852/d855/vs985/ls990
Thank you for source code from @invisiblek (https://github.com/invisiblek)
Thank you for original thread from @Raum1807 (http://forum.xda-developers.com/nexu...od-11-t2515305)
Thank you for original manifest from @Skin1980 (https://github.com/Skin1980/local_manifests)

Overview

I. Preparation
II. Installation of the required packages
III. Installing Java
IV. The sources
V. Building the ROM
VI. Rebuilding with newest sources


I. Preparation

Things you need for building:

A computer
An internet connection
An open mind
Time
Patience

First of all, you need a running up-to-date Ubuntu/Linux system. I am using Ubuntu 14.04 64-bit.

Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.

IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!


II. Installation of the required packages (Ubuntu 14.04 64-bit)

Install packages:

Code:

---

$ sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
openjdk-6-jdk openjdk-6-jre pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev

---

III. Installing Java

You need a version 6 Java Development Kit for building CM11.0. Usually, the SUN JDK 6 is recommended. But there is another way: you can use the OpenJDK 6. When you installed the required packages as described above, you will just need to configure your Java installation.

Check your Java version:

Code:

---

$ java -version

---

Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the right Java location and version:

Code:

---

$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar

---

If they are pointing to the wrong versions you have to change that to OpenJDK6.

Select the default Java version for your system:

Code:

---

$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar

---

That's it.


IV. The sources

Install repo:

Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.

Code:

---

$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

---

Create the working directory:

Code:

---

$ mkdir ~/cm11
$ cd ~/cm11

---

Initialize Repo:

Code:

---

$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

---

and enter your credentials.

Download the sources:

Code:

---

$ repo sync

---

Wait until it's finished - takes some time to download the hefty 12 GB of source code!

Have a break, have a KitKat!

If the process hangs use Ctrl+C to break out of it and resume the download with another

Code:

---

$ repo sync

---

If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using

Code:

---

$ repo sync -j1

---

Initialize the environment

Code:

---

$ . build/envsetup.sh

---

Obtain the proprietary files:

First get two missing repositories for the Nexus 4 by running

Code:

---

$ breakfast <your model>

---

Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.

Use this code

Code:

---

$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml

---

Please make sure you copy and paste code with your correct model
Paste the following lines to the editor

D850

Code:

---

<manifest>
  <!-- D850 -->
  <project path="device/lge/d850" name="invisiblek/android_device_lge_d850" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

D851

Code:

---

<manifest>
  <!-- D851 -->
  <project path="device/lge/d851" name="invisiblek/android_device_lge_d851" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

D852

Code:

---

<manifest>
  <!-- D852 -->
  <project path="device/lge/d851" name="invisiblek/android_device_lge_d852" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

D855

Code:

---

<manifest>
  <!-- D855 -->
  <project path="device/lge/d855" name="invisiblek/android_device_lge_d855" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

VS985

Code:

---

<manifest>
  <!--VS985 -->
  <project path="device/lge/vs985" name="invisiblek/android_device_lge_vs985" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

LS990

Code:

---

<manifest>
  <!--LS990 -->
  <project path="device/lge/ls990" name="invisiblek/android_device_lge_ls990" remote="github" revision="cm-11.0" />
  <project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
  <project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
  <project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
  <!-- CyanogenMod -->
  <project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" /> 
  <project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
  <project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>

---

Save the file.

Run

Code:

---

$ repo sync

---

again to get the files needed.

Download the necessary prebuilts from cyanogenmod by running

Code:

---

$ cd ~/cm11/vendor/cm
$ . get-prebuilts
$ croot

---

And you're done!


V. Building the ROM

Now build it:

Code:

---

$ brunch <your model>

---

change <your model> to d850/d851/d852/d855/vs985/ls990
And the building process starts. Now have patience. Building takes around half an hour on fast systems and a lot more on older and slower machines.
When everything worked as it should you will find your new ROM-image in ~/cm11/out/target/product/<your model>

It is called cm-11-DATE-UNOFFICIAL-<your model>-zip.
Before you flash you need to bump it first!
you can get bump from https://github.com/CyboLabs/Open_Bump
go to /cm11/out/target/product/<your model>/
copy boot.img and open_bump in same folder and run

Code:

---

python open_bump.py boot.img

---

you will get boot_bumped.img rename it to boot.img and push into "cm-11-DATE-UNOFFICIAL-<your model>-zip"
Now You can flash it via CWM/TWRP as usual.


VI. Rebuilding with newest sources

Whenever you like to update your sources and build a new version you have to run these four simple commands:

Code:

---

$ cd ~/cm11
$ repo sync
$ . build/envsetup.sh
$ brunch <your model>

---

Compiling takes less time than it took for creating the ROM the first time because it's only building new parts while reusing old parts that haven't changed.
and don't forgot bump boot.img



Happy building!