Database Users

[Q] ADB and recovery mode

Firmware JP9, power-on to recovery mode => install update.zip => error can't mount sdcard => try to using adb for mounting sdcard manually but adb did not active.
One more thing, root using one click 1.5.5 OK for apps but can not achieve SU @ adb (and adb only work while boot into normal mode)
Any suggestion for install the update.zip from sdcard?

No more recovery for me either (I didn't flash the bootloader althrough).
When you use adb and type "su", the phone should prompt you a window.

Gsam101 said:
No more recovery for me either (I didn't flash the bootloader althrough).
When you use adb and type "su", the phone should prompt you a window.
Click to expand...
Click to collapse
for the same reason I can not update gps.conf with european settings, it says error message when I try adb

nastyba said:
for the same reason I can not update gps.conf with european settings, it says error message when I try adb
Click to expand...
Click to collapse
root your phone using super one click 1.5.5 (Run the soft first, and click root wait until the software said that waitting devices... plug your phone to PC using usb cable and wait more 2'' or 5'' . DONE! It's safe and you can unroot as well)
you can using some missing command by busybox (the easiest way in install titanium backup and click the problems? button in the right bottom it will automatically install new busy box to your phone)
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
DONE
Good luk!

kenblat said:
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
Click to expand...
Click to collapse
Or you can install "Root explorer" - RO/RW mount in 1 click + file explorer

kenblat said:
root your phone using super one click 1.5.5 (Run the soft first, and click root wait until the software said that waitting devices... plug your phone to PC using usb cable and wait more 2'' or 5'' . DONE! It's safe and you can unroot as well)
you can using some missing command by busybox (the easiest way in install titanium backup and click the problems? button in the right bottom it will automatically install new busy box to your phone)
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
DONE
Good luk!
Click to expand...
Click to collapse
Thank you for your effort - I have rooted phone & Titanium backup installed and busybox installed after Titanium was launched first time.
I can not run Adb Shell
#su works OK
after "busybox..." it says error message
I cannot find root explorer on market
and finaly I was trying Terminal emulator and SUFBS and I still can not edit system/etc/GPS.CONF ((
any ideas please ?

angry_friend said:
Or you can install "Root explorer" - RO/RW mount in 1 click + file explorer
Click to expand...
Click to collapse
hi, where did you get it pls ?

nastyba said:
hi, where did you get it pls ?
Click to expand...
Click to collapse
google for blackdroid and there search for root explorer...

google for "android+ root explorer.apk download"

nastyba said:
hi, where did you get it pls ?
Click to expand...
Click to collapse
QR Code of the app:
{
"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"
}
yeah I forgot, it's not free, but it worth 3.90$ to pay, trust me

I'm going crazy here.

This has obviously been covered in DagentooBoy's thread - which is great.
http://forum.xda-developers.com/showthread.php?t=761045
But I tried it and it doesn't work, even with the SGS Unlocker, tried the WinXP (PC way) first.
The version I'm running is Android 2.1 update 1.
I get this when I try running it through the PC.
{
"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"
}
Sometimes when I turn my phone on I get asked to enter the SIM pin, but I hit DISMISS and get into the phone. The next screen says "Phone Locked", but I swipe and enter the phone.
Will buying an unlock code from one of eBay unlockers work or not?
I feel like I bought a brick here. lol
Anyways, any input would be greatly appreciated. I'm not looking to do anything else to it other than unlock and use it for now. While I'm fairly competent with doing this tech-stuff, the Android stuff is a step above for me, so I wanna take my time to learn this all.
It's my first smartphone after using a Nokia 6265i for the past 5 years.
http://en.wikipedia.org/wiki/Nokia_6265 lol
So for me this phone is a treat as is, if only I can get it unlocked.
Thanks for your help and input.

It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.

chui101 said:
It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.
Click to expand...
Click to collapse
Okay, I understand a bit. but I'm not sure what all the coding is all about and how/what to do. You copied nv_data.bin from your phone to a location on the computer?
I set my Vibrant to mass storage and while it's not showing on MyComputer anywhere, the only thing that pops up is the microSD card with the movie on it.

Correct... instead of androidsdk it would be wherever you saved it..

Having one hell of a time accessing my phone via the computer.
It's connected, but no icon to click open or anything of the sort (inside MyComputer)
Ok, this is what I have on my screen now.
No EFS folder, no nv_data.bin, anywhere in the folders.

You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.

lralexl said:
You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.
Click to expand...
Click to collapse
Wanna suggest a link to this almighty Vibrant Bible?

Well I just looked through it and there doesn't seem to be a thread specifically about adb file system actions.
Just open a command prompt and "cd" to your android sdk tools folder.
example: cd c:\sdk\tools
type:
adb shell
su
cp /efs/nv_data.bin /sdcard
exit
adb pull /sdcard/nv_data.bin /nv_data
that should get nv_data.bin into your tools folder under the folder nv_data. then just move the nv_data.bin into the sgux.exe folder

I'll try this now, thanks Iral.

Trying to type what you put, I can't remember for the life of me how to enter multiple command lines in command prompt. Hitting ENTER executes the first line. But I'm supposed to type all that out correct?

One line at a time

Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.

koooba said:
Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.
Click to expand...
Click to collapse
Post the output of ls err ...
Code:
dir

Not following LQ, sorry?

koooba said:
Not following LQ, sorry?
Click to expand...
Click to collapse
The screenshot you've taken when you executed adb, go to the same folder (tools) and execute dir in MS-DOS window.
Need to see if adb.exe is there.

I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder

koooba said:
I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder
Click to expand...
Click to collapse
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices

lqaddict said:
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices
Click to expand...
Click to collapse
This happens (seems like it's good)

Good,
now try
Code:
adb.exe shell
And what was the original post about ?

lqaddict said:
Good,
now try
Code:
adb.exe shell
And what was the original post about ?
Click to expand...
Click to collapse
lol ya.
Well it runs, but it seems to stop with a blinking cursor after the $

Basic ADB Functions -

Basic Commands :
++++++++++++++++++++++++++++
Following are the basic commands which we usually use :
pull - to copy file/dir from Xoom to computer
push - to copy file/dir from computer to Xoom , we will call it "X"
delete - delete file/dir from X
install – install apps on X [either on SD Card or internal storage]
reboot - reboot your X
ADB Shell command -
Code:
adb shell
In command prompt, just type
Code:
adb
list of all commands will show up.
Examples :
++++++++++++++++++++++++++++
The following command, (pull) takes the file avi.apk from the device and saves it as file.apk to the Android Tools directory of computer.
Pull
Code:
Code:
adb pull /system/app/avi.apk file.apk
Push
The following command will copy avi.apk file as happy.apk, from the computer Android tools folder to /system/app of the device
Code:
Code:
adb push avi.apk /system/app/happy.apk
Delete :
The following command removes file avi.apk
Code:
Code:
adb shell rm /system/app/avi.apk
Install :
adb can also be used to install apks. Place the downloaded apks in C:/ drive. for eg, I have placed angrybirds.apk in C:/ drive of my computer. To install it, just run the following command.
Code:
Code:
adb install angrybirds.apk
By above command it will install to internal storage.
*You can also install to SD card by -s switch. (example below)
Code:
Code:
adb install -s angrybirds.apk
Reboot :
The following command will reboot your (device)
Code:
Code:
adb shell su reboot
Quick tips :
++++++++++++++++++++++++++++
1. The commands are case sensitive.
2. Using adb you will be accessing system files, play commands safely or else you might end up making your device unusable.
RENAME : File or APK -
++++++++++++++++++++++++++++
Linux commands. You 'move' the file from the old name to the new one.
Make sure your phone or Tab has enabled USB debugging, connect it to your computer, on your computer type: adb shell
The command you can use is mv (move a file or rename a file)
mv - renames files, apk ...
Code:
Code:
[COLOR=Red]mv[/COLOR] filename[COLOR=Red].[/COLOR]old filename[COLOR=Red].[/COLOR]new
(If it's a system file, you'll will have to have superuser permission and have to make the file system read-write.)
Stubborn Folder Removal -
Intro:
++++++++++++++++++++++++++++
rm - remove files or directories
rm Does not work on directories (unless you use -r, but CAREFUL of this command)
rm -rf /foldername
(This is an example)
Code:
[COLOR=Red]rm[/COLOR] [COLOR=Red]-rf[/COLOR] /system/your stubborn folder
This will remove 'stubborn folder' and everything inside that bad boy)
-r = recursive -f = force
if rm -rf complains about the -rf part,
(Try to run):
Code:
busybox [COLOR=Red]rm -rf[/COLOR] /foldername
IMPORTANT: there is no warning to remove the entire folder, once you hit enter it's gone.
-f can also be used as an alternative
Manual RM: http://unixhelp.ed.ac.uk/CGI/man-cgi?rm
How To:
ADB Shell Removal - (we will use BT5 as an example)
++++++++++++++++++++++++++++
1. Connect Xoom
2. Boot into recovery
3. Toggle to internal storage as /sdcard
mount /data
Enter adb shell via pc
(cd to file location) in this case BT5, is in the sdcard directory
Code:
cd /sdcard #
(once typed, you will be at.... /data/media prompt)
Code:
rm -r stubborn Folder
*Side note ... This works for any other stubborn folder that you want to delete as well...
USE AT YOU OWN RISK - MAKE SURE YOU DO A BACKUP FIRST
If this was helpful Hit The thanks!
{
"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"
}

helpful!!
buddy tell me 1 thing...i need to delete an .apk from system/app/
should i do these:-
1)adb root
2)adb shell
3)adb shell getprop ro.secure
4)adb shell mount -oremount,rw /dev/block/system /system
5)adb delete /system/app/<filename>.apk
6)adb shell mount -oremount,ro /dev/block/system /system
is that it??
or the step 5 should be 5)adb shell rm /system/app/<filename>.apk
please....reply.thanks in advabce....i am a total noob in this case(knows a little bit of programming stuff so the commands seems understandable, copied steps 1-4 and 6 from a rooting device site)thought matching both of them shall do the thing...will it??

Your best bet since you say that you are unfamiliar with adb commands, is to remove the "apk" via an app named Root Explorer. As long as you are uzing a rooted device it will make any apk available for easy removal. Be Careful.

I made a mistake
actually I have copied the superuser.apk into system/app/ folder so that it gets automatically installed when i reset the device...and then the problem starts....SUPERUSER stopped responding(getting force closed automatically) and therefore no explorer/titanium backup....nothing is getting root access....so hav to do dis using adb...will hav to delete supeuser 3.1.apk and then reset the device again...
just tell me which step 5 should i use since u have mentioned two ways...

santy_sayantan said:
actually I have copied the superuser.apk into system/app/ folder so hav to do dis using adb...will hav to delete supeuser 3.1.apk and then reset the device again...
Click to expand...
Click to collapse
First and foremost, Superuser or Supersu MUST be installed in data/app directory otherwise you run into issues.
adb shell rm /system/stubborn.apk
Or (wherever directory you put the .apk)
adb shell rm /system/app/stubborn.apk

[Tutorial]How To -ADB- Logcat & Basic [NEW OR NOOB]

Well this my first own post on General Section
I am sharing how to use the (ADB)
which seem many of us should have some basic on it
(FASTBOOT) will be added later on.
-SIMPLE & EASY-
Is a proper way to tell what wrong's and bug you encountered by a log
Requirement :
Click to expand...
Click to collapse
-Adb Driver for Xperia X8 or This Universal_Naked_Driver
-Adb files (Repacked for you)
-Android Version 1.6-4.1.1
Click to expand...
Click to collapse
Set Up
Click to expand...
Click to collapse
Install the Driver For Adb for your device (Example :X8)
Unpack the Adb Files To A Folder (Named Whatever you like Example: Adb) on local disk C: (Recommend)
Turn on USB debugging on your phone: Settings>Applications>Development>USB Debugging
Go to Start Menu and Search for CMD (Command Promt) (Run as adminstrator)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Prompt CMD with the location you extracted the ADB Files (Mine at C:/adb)
Therefore key in this
Code:
cd c:/adb
{
"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"
}
Check Connected Device & Enable the Adb Server
Code:
adb devices
Wait for few seconds till the server is up and if you connection is working
Should show that the device name is there
If connection is offline should check whether build.prop has this line :
Code:
persist.sys.usb.config=mass_storage,adb
Add this line to build.prop if you need to do so
ADB Logcat
When able to have adb connection between device then you
can now do a pretty simple logcat
Code:
adb logcat > logcatfilename.txt
Replace "logcatfilename" with anything you like and shall log all over the text file
Can then stop logging just pressing Ctrl+C
Enable Access to System
If Encountered that your system not mounted
Code:
adb remount
If some still keeping error then need to boot cwm to adb
ADB Shell
Adb Shell Is A Little Advance So No Really Gonna Cover Up Here
Prompted by
Code:
adb shell
Checking Memory/Swap Progress
Code:
free
You can remove app/files by
Code:
rm -r /filelocation/filename.format
Replace " /filelocation/filename.format" with anything you want to remove such as latimime.apk so you replace with /system/app/latimime.apk
Adb Pull
Now You Should Know To Command using CMD
To Pull
Code:
adb pull /system/app/browser.apk
Replace "l/system/app/browser.apk" with location and file name you want to pull
Adb Push
Now You Should Know To Command using CMD
To Pull
Code:
adb push browser.apk /system/app
Replace " browser.apk /system/app" with file name(On the same folder of the adb files) & location you want to push that file into.
Adb Install
Should be same as pushing method but normally to data folder
Code:
adb install angrybird.apk /data/app
Replace "angrybird.apk /data/app" with file name(On the same folder of the adb files) & location you want to install into
Final :
I hope this Tutorial Is Clear Enough For Other's member which want to
learn adb.You can use this tutorial & i know there many more better adb tutorial
but i am just showing basic knowledge logcat and adb command that can easier
both developers and user.Any Comment & Suggestion can reply below.
I will fix/add if needed.Sorry for bad english & grammar
Credits :
Dev Whom Teached Me Basic Adb
1wayjonny For Universal Naked Driver

pswd
What password for ADB archive?

nikmaletz55 said:
What password for ADB archive?
Click to expand...
Click to collapse
steriod << Password Sorry for missed out
Fastboot tutorial when there's free time :cyclops:

I can't download the GingerLewa.

@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?

fastboot...i think we dont have fastboot

sgt. meow said:
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
Click to expand...
Click to collapse
fotak-x said:
fastboot...i think we dont have fastboot
Click to expand...
Click to collapse
i make this for adb for X8 & Other phone as well
i know there no fastboot but maybe usable for otheer phoness

Root Nexus 4 on Linux

I just rooted my Nexus 4 using Ubuntu 12.04.
The instructions I found weren't quite what I'd liked them to be, none of them were for Linux and I had to do quite a bit of trial and error.
I know that a few years ago I wouldn't have been able to do it with those instructions.
So I thought I'd write down what I did so others can do it easier and faster than me.
To be able to easily understand this guide you need to know the basics about using a terminal, but other than that I'm trying to not to require the reader to know anything.
If you use another Linux distro everything should work pretty much exactly the same, but for the additional packages I had to install, but their name should be easy to guess because they are usually similar across distributions and how you install them should be explained in the documentation of your distro.
Connect your Nexus 4 to your computer using an USB cable.
First I downloaded the ADT Bundle from there developer.android.com/sdk/index.html and unpacked it into a new folder. Doesn't matter where, I'll use ~/androidSDK in those instructions. The tools which you need to root your phone are ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb and ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/fastboot
"x86" means I downloaded the 32bit version and "20130514" is the date of when the version I'm using was published, that will most likely be different for other people.
Now most likely adb and fastboot won't run yet (if you run them it will tell you something like "~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"). To fix this you need to install the packages "lib32ncurses5" and "lib32stdc++6". You can run the following command to do that:
Code:
sudo apt-get install lib32ncurses5 lib32stdc++6
(got that from there: stackoverflow.com/questions/10005907/eclipse-android-plugin-libncurses-so-5)
For adb to work you also need to activate USB debugging: Go to Settings->About phone and tap "Build Number" until it says you are developer. Then a new entry will appear in "Settings", called "{ } Developer options". Check the box next to "USB debugging", confirm with ok.
Now you need to backup everything on your Nexus 4 because it will be wiped while rooting. You can do this by running:
Code:
cd ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools
(in the future I'll assume you stayed inside that directory)
Code:
./adb backup -apk -shared -all -system
Before this command can finish you need to confirm on your Nexus 4 that it's okay to do that backup (just do what it says on it's screen).
This will put a file named backup.ab in the current directory. You can change the name and location of that file using the -f paramter, if you want.
Run
Code:
./adb reboot bootloader
to boot into the bootloader. After a moment the Nexus 4 should display something like this:
{
"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"
}
(image stolen from reviews.cnet.co.uk/mobile-phones/how-to-root-your-google-nexus-4-50010361/)
Now the actual unlocking happens: Enter
Code:
sudo ./fastboot oem unlock
Maybe try without sudo first (just leave it out), but it only worked with sudo for me; without sudo it displayed "waiting for device" forever and I needed to abort with Ctrl+C.
Download SuperSU from there http://download.chainfire.eu/supersu (at the moment "CWM-SuperSU-v0.98.zip").
Put that file on your Nexus 4 any way you want, one possible way is to do:
Code:
./adb push ~/CWM-SuperSU-v0.98.zip /sdcard/
That assumes you downloaded SuperSU to your home directory. For that to work you need to activate USB debugging again (it was deactivated during unlocking).
Download the Nexus 4 "Touch Recovery" from www.clockworkmod.com/rommanager.
I guess you shouldn't need the touch version, but it's more comfortable for sure. When I downloaded it the file was named "recovery-clockwork-touch-6.0.4.7-mako.img" and that's what I'm going to use when I give you commands to run.
This "Touch Recovery" needs to be installed to the Nexus 4. To do this first boot into the bootloader again:
Code:
./adb reboot bootloader
And then flash the file using the fastboot utility:
Code:
sudo ./fastboot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
(if it needed sudo the last time it will need it again, if not, not)
Now go to the recovery mode (use volume buttons to navigate and power to confirm).
Tap "install zip from sdcard"
Tap "choose zip from sdcard"
Tap "0/"
Find the SuperSU .zip file you put on the phone earlier (tip: scrolling works as usual by swiping or if you want with the volume buttons) and tap on it.
Confirm that you really want to install it.
Boot into Android again and restore the backup you made earlier (if you made one).
Code:
./adb restore backup.ab
You need to confirm that command on the Nexus 4.
As you are now finished you can of course disconnect your Nexus 4 from your computer.
You should be finished now. Unless I remembered something wrongly when writing this because I mostly wrote this from memory, after rooting my Nexus 4. If something doesn't work as I claim then please tell me and I'll fix it (possibly eventually).
I myself followed those instructions http://forum.xda-developers.com/showthread.php?t=2018179 as far as possible and then googled what didn't work or just tried around for a bit.
Edit: As of now (18.8.14), those instructions should still work.