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.

Unable to install Recovery on streak..will not boot. completely lost.

Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.

Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.

I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?

On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps

Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.

yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.

This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again

im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.

FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!

Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.

running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).

Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.

Thank you for everything

No problem. Did you get it working?
Sent from my Dell Streak using xda premium

Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.

Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.

lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!

dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak

Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?

Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks

SOD and no root and unable to connect to a pc!

Ok so I was running taboonay 3.0d and I thought I'd have a go at Thor's rom. Flashed it wasn't really into it few things missing that I like in taboonay. So I then restored my back up. All hunky dory.
I then flashed a zip for scrillax v8 bootloader. It seemed to work fine, tablet boots up and rom running fine. I then tried to get to recovery and it's just not happening. Acer recovery says it cannot get root access. When I reboot I can get into the bootloader menu but none of the commands work. I can't get into the recovery menu at all no matter what I do. So then I figured I'd give Blackthund3r's root tool a go. Got everything ready on the pc including latest acer drivers. Now the tab isn't showing up on the pc either. I know some others have had similar problems but no solution was found in the other threads and considering that I probably screwed up badly somewhere along the way I thought I'd start this thread where you can all point out my ignorance and stupidity without bothering anyone else :silly:
Any help?

Any advice at all would be great, I have reinstalled drivers for tab but still no go! I'm on a old xp pro laptop. Everything else connects to the usb port and the cable is working fine

If you can't get to Recovery, you will need to reflash that.
But first thing is first. And that's the driver issue.
With the tab plugged into the PC, go to Device Manager, and see if it reflects there. If not, you will probably have to reload the drivers. You have a choice, which is the Acer Driver installation, or you can try the Google USB Android drivers. Generally I have had not much luck letting windows search the PC, so I usually install them manually. You can either;
a. Direct device manager to look in a specific folder for the google drivers, or;
b. In Device Manager, when you choose update drive, use "select from list" and see if the acer drivers show up there.
Generally, when you install the acer drivers, you should "right" mouse click the install file and select "run as administrator".
MD

Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.

irishmoe said:
Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.
Click to expand...
Click to collapse
Ok, now I run Win 7. But XP should be similar.
Are you saying in device manager, you do not have a device with an exclamation mark when you plug the tab in???
If you do, then right click the exclamation mark, select properties. Then the Tab "driver". Next, select "update driver". Then, "browse my computer for drivers". You should get the option to "select from a list".
If your PC does not detect the tablet at all when you plug it in, then it';s a different issue. It's what we call a USB Brick. At first guess. Usually easy to fix on the 500.
Can you start your tablet in APX mode? hold the pin reset, press and hold pwr. Count to 3, and release pwr, then 1 second later, release the pin reset. You should have a black screen with the pwr lite on.
I'm thinking you might want to do the manual flashing of the bootloader + 1.7.3 recovery. Obviously the bootloader V8 flashed, or it wouldn't work at all. Civato has instructions for manual flashing of the bootloader and recovery. Note that I HOPE you wrote down your UID number somewhere. As you will need to convert it to the SBK.
MD
EDIT. One more note. When you boot to the bootloader menu, in your case, probably the only option that will work is "fastboot mode". When you select it, the menu should go away, and it should say "fastboot mode". Then plug into PC and see if windows detects it in device manager. If so, you can fastboot a recovery image to it. Note, that for fastboot to work, you must have the Android SDK installed on your PC. Because you will have to run the fastboot commands from a command window. But for now, check to see if you get to fastboot mode on the tablet.
Sorry I can't spend a lot of time, as it';s late in moscow. Job tomorrow. But Skirlaz_CZ can give you the commands to fastboot a recovery in his bootloader thread.

Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
Ouch! No UID numbers. That hurts. Look in your old CWM recovery backups (if you have) on your EXT SD Card. If you were at one time running a more recent version of CWM, You might have them in the recovery folders. The more recent recovery programs in the backup folders, it's called UID.txt. You have to have this if you use NVFlash. No way around that.
With Fastboot, you don't need it, as you will fastboot the recovery image. If successful, that should allow you to boot to recovery, and flash one of the custom roms. Make sure you do your wipes as in the Rom install instructions. I use CWM 1.7.3 (I've been too busy to try EZTerry's or the TWRP versions. But CWM works good so far.
If not, well, there;s always the update.zips to get a stock ICS on your tab.
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD

Moscow Desire said:
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD
Click to expand...
Click to collapse
You're not wrong there! I'm doing the whole ikea/home improvement thing with the family today. I'll try the fastboot later
Again I really appreciate the help.

Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl

irishmoe said:
Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl
Click to expand...
Click to collapse
HA HA! Yep, gotta have the SDK for ADB and Fastboot. I posted some instructions yesterday about flashing recovery via fastboot.
http://forum.xda-developers.com/showpost.php?p=29294671&postcount=6
You should be able to do it if you already have V8 Bootloader.
MD

Nice one MD going to try it out.

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388

irishmoe said:
Nice one MD going to try it out.
Click to expand...
Click to collapse
Waiting for an update

blackthund3r said:
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388
Click to expand...
Click to collapse
Ha ha cheers mate! Like I said I'm a simpleton but not quite that bad.
Thanks for all the good work. I was actually following another thread stupidly when I should have been following yours.
MD - was away for a few days, just back but have had a few beers so not doing anything stupid tonight. Got sdk installed.

MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device

irishmoe said:
MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device
Click to expand...
Click to collapse
Sorry I was away. Did everything work ok for you? All running? (been trying to chase down my rom issue)
If it says "waiting for device", then you need to check your device manager, and make sure the correct driver is recognized. (APX, Fastboot, Recovery, Download, etc). Usually, I can change drivers while this is happening, and the process will complete.
MD

ok I don't mind admitting that I'm totally lost here. Nothing resembling the tab is showing up device manager so how can I check the drivers?I've been playing around with device manager for a while now and I can't find any way to do what you suggested
I've uninstalled and reinstalled the drivers again and again. Nothing! Could it have anything to do with me having a gateway? I wouldn't think so because they're the same inside.

Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do

irishmoe said:
Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do
Click to expand...
Click to collapse
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.

dibb_nz said:
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.
Click to expand...
Click to collapse
Ok ok boot/recovery driver? You've lost me there chap! Xp device manager is showing nothing tab related. Tell me what to do and I'll give it a blast.
I'm using the regular usb slot as opposed to the mini cause I've no mini cable. That should be ok right?

Nexus 7 stuck on fastboot screen/bootloop...bricked?

Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help

voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R

shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.

voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?

shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?

voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.

shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.

You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.

You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....

Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.

[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.

shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers

I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.

http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium

Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED

voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..

Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.

Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )

brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!

[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?