Database Users

What ROM ?

Hello,
I've a liquid with 2.00016 ROM
What is for you the best ROM for the Liquid ?
For best I mean faster and that work well without crash.
Thanks a lot

Well, if it comes to stability, I would recommend ACR 1.5.1
But now I'm using eVil 1.8.1 and I love it

Piter1225 said:
Well, if it comes to stability, I would recommend ACR 1.5.1
But now I'm using eVil 1.8.1 and I love it
Click to expand...
Click to collapse
ACR 1.5.1, is pretty stable..unless you are really into the liquid tweaking modding, i don't recommend upgrading to 2.1 leaked version..
i had lots of random reboots, phone getting stuck on standby issues and reverted back to ACR 1.5.1, really happy with it.
Flash the ACR on 2.000.16 and you have a pretty satisfied liquid with you..

a question
hello guys.
there's something I don't understand in the rooting process.
when I go to superboot and double click install-superboot-windows.bat
all I get is <waiting for device>
it stays there for hours then nothing happens!!
I was trying to update to 2.1
I downloaded the acer download tool 3.10
then the 2.1 firmware BIN file.. all that was done successfully.
then I went to the third step where I have to do the superboot i got stuck there..
can someone help me please?

Thanks ..
I've see that now there is LCR 1.2
Maybe I trial this rom ...
Thanks

Ninlour said:
hello guys.
there's something I don't understand in the rooting process.
when I go to superboot and double click install-superboot-windows.bat
all I get is <waiting for device>
it stays there for hours then nothing happens!!
I was trying to update to 2.1
I downloaded the acer download tool 3.10
then the 2.1 firmware BIN file.. all that was done successfully.
then I went to the third step where I have to do the superboot i got stuck there..
can someone help me please?
Click to expand...
Click to collapse
Type cmd: adb reboot bootloader
after run .bat file.

anzo said:
Type cmd: adb reboot bootloader
after run .bat file.
Click to expand...
Click to collapse
even if the characters don't show?
should I press enter after typing?

Ninlour said:
even if the characters don't show?
should I press enter after typing?
Click to expand...
Click to collapse
PC/Andriod-sdk-windows/tools/ run cmd type "adb reboot bootloader" if liquid change bootloader after run .bat file PC.

anzo said:
PC/Andriod-sdk-windows/tools/ run cmd type "adb reboot bootloader" if liquid change bootloader after run .bat file PC.
Click to expand...
Click to collapse
sorry forgive me for being such a noob.. so i understand that it requires me to download android sdk tools software?
it wasn't mentioned in the instructions for rooting though.

Ninlour said:
sorry forgive me for being such a noob.. so i understand that it requires me to download android sdk tools software?
it wasn't mentioned in the instructions for rooting though.
Click to expand...
Click to collapse
You have to make sure you are in the bootloader mode in order to flash the recovery and boot roms.
For that you can enable debugging on your liquid and then navigate to the sdk directory as mentioned earlier for running the adb command.
Also make sure that you have the drivers installed.

umair9001 said:
You have to make sure you are in the bootloader mode in order to flash the recovery and boot roms.
For that you can enable debugging on your liquid and then navigate to the sdk directory as mentioned earlier for running the adb command.
Also make sure that you have the drivers installed.
Click to expand...
Click to collapse
ok let me put everything from the beginning because it's still not working and you guys tell me where did I do wrong.
I got the acer brand new. opened the box. used 1.6 android, and didn't like it.
so after surfing the web i was able to know that my rom was
ROM 1.001.05 AAP CSL.
so I used alternate superboot to root it the one provided in this pagehere
I followed the steps just like it was described but i have no small idea that it went successfully because I didn't see any confirmation of any kind that I had root.
well I don't know if there's any anyway
then I followed these steps here
I downloaded the drivers on my desktop.
then flash tools, and the 2.1 firmware liquidE "whatever it was provided in the link."
then I downloaded superboot and unzipped it.
I was able to find install-superboot-windows.bat I would get a window says flashing superboot
<waiting for device>..
and stays like that forever.
so I decided to take an action by turning off the device and tried to do the following:
removed battery
unplugged cable
re plug cable
put battery back
press camera+power then nothing happened I just got a regular boot.
so I did it one more time and this time I did
volume down+camera+power
still nothing happened ..normal boot.
I tried the same thing but volume up.. still nothing. so i gave up.
but after contacting you guys.
I downloaded SDK tools for windows
I opened android SDK windows folder then tools folder but I can't find any CMD file that I can run and type my commend in it.
I honestly don't know what this Android SDK is for.
so I got stuck with a liquid E rom without doing any recovery or anything.
I don't even know how to get the bootloader mode to run.
what should I do?
no I have ROM LiquidE.0.004.01 EMEA GEN1
it seems to run fine though..
but I don't know if there's anything missing
why am i not able to do the recovery step and flash system.img ??

Getting into bootloader mode when liquidE rom installed
Do this and you will get into bootloader mode when liquidE bin installed:
1. turn off your phone (and unplug usb if plugged)
2. press "camera + volume up +power" together at the same time (phone will vibrate 2 times) then release buttons
3. take the battery out and put it back (don't touch any buttons on the phone)
4. connect the usb from your computer to acer liquid and you will see the acer logo and then bootloader will pop up

mhmm
what he said: I always run into issues when someone says run superboot as the next step then install lickon's recovery. I skip the install lickon's recovery b/c it never seems to work for me. I just go to recovery mode after superboot is installed and after I put the .zip rom file on root of sd. Once in recovery i wipe, wipe, install from any .zip and i'm good to go. I probably lose out on being able to hard reset to the rom i installed but i have no idea what lickon is for and no search came up with a decent answer. I'll keep reading.
BTW, i ditched the acer neotouch for s100 and couldn't be happier.

Well finally I figured it out.
You dont actually have to press any hard button combinations because that actually never worked out.
So here is what I did.
I just enabled the debugging mode by going to setting>application>development>enable debugging
By doing that superboot worked just fine
Now I have Evil 1.9
To be honest non of the 2.1 leaked seems to function completely. . But still trying

don't forget to restart
After installing 2.1 and playing around with it for a bit, don't forget to restart it. Its horribly laggy the first go around, but after you reboot it (once you sync and all that), its pretty quick (though nowhere near 1.6). I have an issue with evilD's 1.9 where after having downloaded like 20 apps from market, when i open an app from the launcher, sometime when closing the app i get a black empty unresponsive launcher pop up instead of the homescreen and i have to click home button. (high-five for the run-on sentence... yeahhhh). Probably b/c of the DL rampage i went on.
Either way, i'm happy with it so far. I wish there was a 1.6 version with voice input in all text fields or a 1ghz 2.1 but that will come once liquid e is released officially.

Need Help: Updating CM, Stuck

[Edit] I got the CM 1.4 recovery to flash and updated CM from sd card... Then hit reboot. It's been sitting on G1 screen for like 10 minutes. Do I need to wait longer or is this a bad sign? What should I do?
Please help!
THank you!
------
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.

arsieiuni said:
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.
Click to expand...
Click to collapse
A couple of things:
5.0.7 IS the latest stable build. If you want 4.2.15.1, you're going to have to search the forum for it because Cyanogen is no longer working on Donut (1.6) builds.
However, if you want the latest CM, its very simple.
First, download either the latest clockwork recovery or amon_ra recovery. follow the instructions to flash recovery. to check if it installed correctly, you dont power on while holding X, you power on while holding the home button. (alternately, grab the "quick boot" app from the market and you can one-touch boot to recovery or bootloader from your home screen)
Next, download the latest radio and appropriate SPL. In order to install these, follow the instructions here:
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream#Prerequisites
Note: MAKE SURE YOU FLASH THE RADIO FIRST OR YOU WILL BRICK YOUR PHONE.
Once you follow those steps, you'll have CM 5.0.7 installed.
EDIT: I noticed you grabbed CM recovery 1.4. That recovery is old and outdated, also no longer supported. You need to grab one of the recovery files I mentioned.

Crap...
So trying to follow the instructions at Cyan WIki...
And like I said above, it's now sitting on G1 screen indefinitely...
Have I lost my phone?
Is there any way to fix this?

power off the phone by pulling the battery. boot into recovery by holding home+power. plug your phone into your computer. once there, use ADB from your computer to flash the new recovery, then power the phone off again. power it back on into recovery again (home+power) and then follow the steps in the wiki page i linked you to.

OMG that's wonderful I thought I had ruined it!
But I have no idea how to use ADB. I have never used it before. I found the site but I'm totally lost at that point o_o
If I plug phone into my computer it doesn't recognize to let me access the folder so I can't add files there since I can't Mount it.
How do I add the recovery from ADB?

ok, first things first, make sure you have your drivers installed and adb working (for this, youre going to need the adnroid SDK installed, which can be found here: http://developer.android.com/sdk/download.html?v=android-sdk_r06-windows.zip). to check and see if adb works, open a command prompt on your computer(start>run>cmd), navigate to the sdk tools directory (for example, mine is C:\android\tools\ yours might be different depending on where you install the sdk) and then type "adb devices" without the quotes. if it shows your device connected, proceed to the next step:
Copy the recovery image you're going to install to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your computer and type the following commands into the command prompt
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/custom-recovery-name-here.img
once that's done, you will have your new recovery going, then proceed with the steps to upgrade the radio and SPL from the wiki page i linked earlier. after you have the radio and SPL done, flash CM and you're all set!

Okay... I tried to use the SDK to install the drivers (it says in INstalled packages: Drivers r3) but It's not showing up under ADB devices when I check it in CMD.
It just says List of Devices: then there's nothing.
I think maybe because my phone won't go past recovery right now, I can't get the drivers working?
Is there a place I can manually download the drivers so I can manually install them?
I went in and followed the instructions here; http://developer.android.com/sdk/win-usb.html to install or upgrade and either way my computer is telling me I have the best driver installed for the HTC android phone. I don't SEE a place exactly like they say that says ADB Interface device.. that doesn't even appear on my list.
I really, really wish I could find my sd card adapter. That would make this considerably easier.

Please could someone help with the last question above?
I'm trapped at this point and can't figure out how to go onward.

For starters, don't flash your radio or SPL. FASTBOOT them.
Setting up adb is very useful. Download the sdk and extract it to where ever you want it and add the "tools" folder to your windows Path. There and HUNDREDS of tutorials on how to do this. Google it. Fastboot is just as easy as using adb, and safer than flashing.

[Q] Really could do with some help from those with experience... Please.

Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..

No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G

Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...

Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..

Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.

Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App

Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox

Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny

I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!

Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium

draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.

[Q] [HELP] How to root LG optimus L5 E617G WITH Jellybean 4.1.2

I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell

bennatpjose said:
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
Click to expand...
Click to collapse
have you tried to flash a pre-rooted JB?

Sabyn said:
have you tried to flash a pre-rooted JB?
Click to expand...
Click to collapse
is there a guide somewhere

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
to flash a version of JB? come on my page , i can give you a link to my dropbox , there is anything you need

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
i also have an e617g on 4.1.2 bell network id like to root and unlock the bootloader so i can install cwm and finally swap roms, this is a nice phone but it barely exists on the web any help would be greatly appreciated, thanks in advance

Never mind figured it out myself. I may post a guide here soon. Seeing as any help I ask for is ignored. I'd rather help than hold back

Turn your lG-e617g into an LG-e610 then root it and install cyanogenmod.
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz

I had already tried that but i keep getting the bloody error in KDZ
03:58:19 : Launching SW update
03:58:19 : Unpacking KDZ
03:58:21 : KDZ file extraced
03:58:21 : Extract file error
03:58:23 : ===FINISHED===
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

That happens when the kdz file is corrupted. Redownload the firmware and try again

its more than likely a bad connection causing a bad download also are you starting off with an e617g or e610?

Will all app data, contacts, etc. be lost using this method? Thanks in advance!
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

yes definitely back up

r4nd0m14m said:
yes definitely back up
Click to expand...
Click to collapse
Does this method actually unlock the network too? Can I use fido sim card? would it work?

[Q] Installing Custom ROM on Wrong OS Version, Looking for Solutions

I apologize if this question has been answered already, but I just spent 15 minutes using the search button and could not find a response.
I just installed Matr1x v10.5 (http://forum.xda-developers.com/showthread.php?t=2007231) onto my Nexus 4 but it had JB 4.2. Based on the version notes of the thread, I assumed that it was backwards compatible with my phone and therefore installed the new version on my Nexus 4. Now every time I turn on my Nexus 4 the screen is blank. What can I do to fix this issue? Will it require a reset so that all my data is lost? Thanks.

What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app

failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.

pooq said:
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
Click to expand...
Click to collapse
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.

failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Chromium_ said:
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
Click to expand...
Click to collapse
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?

pooq said:
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
Click to expand...
Click to collapse
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app

failly said:
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?

pooq said:
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
Click to expand...
Click to collapse
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app

failly said:
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.

pooq said:
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
Click to expand...
Click to collapse
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app

failly said:
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with. I am presently trying to find a way to copy the downloaded Nexus image files provided online into my internal storage so I can install them.

pooq said:
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with.
Click to expand...
Click to collapse
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app

You just have to do the following :
A) flash a recovery via fastboot (fastboot flash recovery recovery.zip)
B) now go ahead and boot from your recovery, and push the rom of your choice, in case you don't have one already inside your sdcard (adb push ROM.zip /sdcard/ROM.zip)
C) flash your recently copied rom of choice to your phone. (if necessary, wipe data, cache and dalvik cache)

failly said:
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just spent a couple of hours reading through the guides (and trying them out) which led me to several other guides. To be incredibly honest, I am completely confused as there is a plethora of new information thrown at me. I have to pose several questions before I continue:
1) When you say bootloader, are you referring to the fastboot bootloader screen that pops up after holding the volume down button and the power button? I just wanted to confirm this as I am starting to feel you are referring to something different after reading several guides.
2) Is the scenario 2 guide you posted basically a method to "sideload" the JB 4.3 into the storage of my Nexus 4 so I can install it via Recovery Mode?
I tried installing the drivers but I cannot seem to do it successfully as I do not even have a starting OS for my phone in the first place. I can not access a theoretical "Developer Mode" either from when I first rooted my phone.
So basically, I do not understand how I can get the direct downloads from Google (the JB 4.3 files) and get them into the internal storage of my Nexus 4 to install the OS.
Is there a simpler way to do this? If not, here is my current progress. At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.the OS[/B]. Is there a simpler way to do this? At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.

Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.

wammie said:
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
Click to expand...
Click to collapse
The first thing I'd like to do before reporting my progress report is to thank you and failly for taking the time to help me out. You both have contributed tremendously in trying to help me out with this, so I would like to thank you both for that.
1) I had installed the sdk program and changed the adb path (following this guide http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/)
Following wammie's guide:
2) Booted into bootloader
3) Downloaded and installed NEXUS 4 TOOLKIT V2.0.0 (had used it before but it didn't work for me so I relied on a different program to root my phone). Renamed fastboot-toolkit to fastboot
4) Typed fastboot devices in in cmd, does not recognize phone
5) Uninstalled current usb drivers and installed usb drivers provided. The driver I chose to install for was titled "Android". The other ! mark was "Base System Device" which was something I had never seen before until today when I had reinstalled usb drivers
6) Typed fastboot devices in cmd again and still nothing has changed
I am unable to continue any further as fastboot does not recognize my phone when I have it under bootloader. I had downloaded all the files that were recommended in your post. I think the reason why I cannot access fastboot devices is because there is literally no OS running in my phone. I could be wrong though.
I guess I'll take a break and call it a night since I've been trying to fix this problem the past 13 hours or so. Any additional feedback and support is appreciated!
Additional Notes: I have tried this both on my laptops (Windows 8) and on my desktop PC (Windows 7)

Luckly, if windows doesn't recognize your device while in fastboot it isn't because you don't have a OS installes but because not correctly set up drivers.
I posted a link some posta ago about a toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
When opening the program at the top there is a button called full driver installation, press it and follow the instructions.
Sent from my Nexus 4 using xda app-developers app

http://i.imgur.com/sOT7FGh.png
http://i.imgur.com/WNEKb0z.png
http://i.imgur.com/vUmTDcZ.png
http://imgur.com/da7NGwB
http://i.imgur.com/bjmhXZv.png
This is what you should do when you are updating the drivers, its imperative you get those drivers working. Otherwise, you won't get access to fastboot.

Oh I would recommend using a Windows 7 PC.
Windows 8 can also do the trick but you maybe need to disable driver signature enforcement, so you better go with windows 7 for now.
Sent from my Nexus 4 using xda app-developers app

Status Update:
I had spent a whole day reformatting my Windows 7 machine and am back at it. I have made a bit more progress than before.
1) After typing in fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img in command prompt, under the "List of devices attached" it is blank (i.e. there is no device attached). http://i.imgur.com/TnyBCKS.png
2) I have successfully installed the usb driver on my PC the first time when the only explanation mark was titled "Android", however the only Android option at the moment now is labelled "Android Bootloader Interface". No such thing as ADB (or any variations including Android ADB Interface) exists.
3) In TWRP Recovery mode, I see an exclamation mark titled mako but I believe that is irrelevant. I have tried installing the drivers to this just in case but failed. I then tried it again in Bootloader mode and mako is gone and Android Device pops up again with "Android Bootloader Interface"
4) I have tried restarting my PC and repeating the above steps.
Edit:
5) The only time I see an Android Composite ADB Interfaces is when I boot normally to the "Google" screen. However, I cannot move any of my ROMS over into my phone. When I typed "adb devices" it shows a bunch of characters with offline beside it. I do not have any options to reinstall any drivers for this.
From my understanding,I should be able to access the Android Composite ADB Interface while in recovery mode, which should let me transfer my ROMs over... but the issue is I cannot access Android Composite ADB Interface while in recovery mode.
Also, is there any reason why I shouldn't use the official JB 4.3 img as the ROM I want to install on my phone?