Database Users

HELP! I think I bricked my nexus 7. [SOLVED]

After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2

Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium

This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.

The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium

I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium

El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader

kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2

On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2

OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?

Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium

El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2

Glad you got it working

nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster

Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2

Custom Recovery Gone?

I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!

Koopa777 said:
I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!
Click to expand...
Click to collapse
Assuming you're rooted...? Download and install goomanager from the Play store. Open it and tap the menu button (three dots at upper right) and select Install Open Recovery script. It will prompt for confirmation and then download and install TWRP for you.
... beamed from my Nexus 10 to your planet

Koopa777 said:
I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!
Click to expand...
Click to collapse
Use fastboot flash recovery openrecovery-twrp-x.x.x.x-manta.img to get TWRP back?

Wow I completely forgot about this. Exams happened and then I forgot to reply. I was a moron and was trying to flash the Toshiba Thrive TWRP(2.4.1.3) not reading that it was for the Thrive. Flashed 2.4.1.0 manta and it took no problem. Thanks anyhow! I'm going to leave this topic in case anyone else is as dumb as I am(I sure hope not ) so they don't freak out over TWRP disappearing.

Wow your fortunate you didn't do something worse lol. Becareful if you ever use fastboot, a few wrong commands and your fubard
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Wow your fortunate you didn't do something worse lol. Becareful if you ever use fastboot, a few wrong commands and your fubard
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
A few wrong commands? Huh no, only if you flash the wrong files...
Sent from my Nexus

Try fastboot erase bootloader and don't follow up with your write command... the show will end real quick
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Try fastboot erase bootloader and don't follow up with your write command... the show will end real quick
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Maybe on this Nexus... On Galaxy Nexus you still got OMAPflash.
Sent from my Nexus

bk201doesntexist said:
Maybe on this Nexus... On Galaxy Nexus you still got OMAPflash.
Sent from my Nexus
Click to expand...
Click to collapse
I've never personally done it, but I've heard alot of people having issues with omap flash and the partition tables
Sent from my Nexus 10 using Tapatalk HD

[Q] hard bricked and SOL it seems

I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
Can you get into the bootloader?

DaanJordaan said:
Can you get into the bootloader?
Click to expand...
Click to collapse
No. it's really gone. Just spoke with google and getting a replacement. I really can't do jack....bleep...with it.
all this for changing a font with Rom toolbox.

Yeah, bricked, but I'll buy it for 30

So it's permanently stuck on the Google logo and you can't access recovery or bootloader? No boot animation?
I wonder why something so trivial as a font change caused this... I've had font changes cause bootloops but never a bricked device.
Sent from my Nexus 7 using XDA Premium HD app

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
You aren't alone.
That app is made by the ROM Toolbox dev, lotsa complaining in the reviews about it bricking. You did connect it to your PC via USB and tried pushing the needed bits and starting from scratch didn't you? I'd even try one of the toolkits available for rooting and recovery.

After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks

As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.

I'm glad I was able to fix it. My computer was not able to recognize the device while I was on the fastboot screen (android laying down.) THe only other screen I ever was able to get was the bootlooping screen. By chance I realized the computer was connected to the device only if it was on the bootloop screen. When I saw that, then I was cooking with fire.

Sounds like you should install your fast boot drivers
Sent from my Galaxy Nexus

I've only just got my nexus (first tablet) had it for two weeks, decided to root mainly because I hate adverts popping up everywhere, anyway I digress. I purchased toolbox pro for my hox ages ago and even though I haven't installed it, for the last few days I've been thinking of it so cheers buddy for bringing this to my attention
Sent from my Nexus 7 using xda premium

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
Best. Idea. Ever.
Also, with a Nexus device at least that was a shot. Many others would keel over and die for good if that sort of stuff happened.

neiander said:
After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks
Click to expand...
Click to collapse
Cool, and agreed with the above. If you can see stuff on the screen, it's technically not bricked.
Bricked an N7 once, it was stuck in APX mode, the lowest recovery mode for tegra chips I believe.
At the time there was no way recovering from it using NVFlash, maybe there is now though.
Mind telling us how you got yours back to life? Just curious
Cheers

all nowellel
Was really luck. I was working on trying to get the computer to sees the device. Trying to load drivers. Anything I could do. The computer kept saying no adb device plugged in. Finally after deleting drivers and reloading drivers, I plugged in the device while it was bootlooping and heard the correct "connected" sound and saw the device in device manager. Then with toolbox, was finally able to reboot into recovery and wipe and reinstall rom. Didn't lose anything in the process.

Oh, the thing that was really the biggest mind blower was that there were 2 screens I could get to, bootlooping screen and what appeared to be the correct fadtboot screen, the computer would not recognize the device when I was on the fastboot screen. That was why I thought I was SOL.

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
What is this NVedit tool? I cant seem to find that anywhere. I'm working on my buddy's N7 32GB Wifi, he tried to revert to stock from having CWR and CM10.1 using the Nexus Root Toolkit and now there is that problem happening you mentioned, backlight wont light up and computer doesnt recognize the device and I cant get into the bootloader either. Already checked the Screen itself and it works (disassemble and connected to my N7) and the battery has power, just no luck.

Need Advise Before Sending Back To Samsung

Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks

socjdqcer said:
Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks
Click to expand...
Click to collapse
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.

socjdqcer said:
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.
Click to expand...
Click to collapse
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.

Username invalid said:
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.
Click to expand...
Click to collapse
Thanks man, Ill give it a shot!

socjdqcer said:
Thanks man, Ill give it a shot!
Click to expand...
Click to collapse
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices

Username invalid said:
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices
Click to expand...
Click to collapse
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!

socjdqcer said:
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!
Click to expand...
Click to collapse
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.

Username invalid said:
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.
Click to expand...
Click to collapse
Yeah man, thats what I thought, so I have tried it a few times and whenever I go to wipe cache....The tablet doesnt really do anything and then all of a sudden it restarts. What would cause that?

try to use the toolkit to flash a factory image of 4.2.2 (mind it formats all data, files, music etc). See if it works fine. then unlock, root the device and install a custom recovery (all with the toolkit). If everything works you will have a rooted 4.2.2. Try the tablet and the recovery to see if everything works. If it does you can upgrade to 4.3

Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Sounds good man! Thanks for the help!
Thanks EVERYONE! I tried everyone of your suggestions and the original issue still keeps happening. I can get the tablet to work for a little while, but the its back to bootloop.
Thanks

[Q] HELP!!! Nexus 4 stuck in what i think is "recovery mode"

Hello All,
About 2 days ago i tried to root my google nexus 4, I dont know what i did, but now when i turn it on it shows the google logo then goes to where it shows an android with a red exclamation mark, does anyone know how this can be fixed, any help would be much appreciated!!

Can you be a bit more specific on what you did? Or what guide you followed?
Rooting is quick and easy on a nexus
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
Then flash ROM of choice in recovery
Reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app

Ok, i had successfully rooted my phone, i then went to put on a new rom so i could use OTG storage. That got me completely stuck, i tried toget back to my normal phone but didnt know how. I foolishly went into recovery mode, and wiped everything off it. and just now i cant even do anything it just has a red light flashing at the bottom, i hope this has helpt in some way.

Do you have a custom recovery? Use adb sideload to flash the ROM, or if you have a working otg cable this should be fine too
Sent from my Nexus 7 using XDA Premium 4 mobile app

UPDATE: The red light has gone (was just low on power) But the phone is still stuck in recovery mode. i have tried to "apply update from ADB" with my mac but it doesnt work and im not sure if i am doing it propperly.

I am pretty new to this kinda stuff, so i dont know what a custom recovery is, and i honestly have no idea what to do, im not really bothered about the root anymore i would rather just have my phone back to normal.

Please dont take this the wrong way and I mean no disrespect, but maybe we should just get your phone up and running and then maybe a few months from now after you've done a whole lot of reading you can consider rooting again. The n4 isn't the most expensive phone in the world but it would still be a shame to brick it, as much as I believe all androids are best to be rooted the user really needs to understand fully what s/he is doing, 95% of "help my device is bricked" threads come from lack of homework, which is easily 100s of threads a day across xda alone
OK, sorry for the lecture I've just ran into this a lot lately, and I'd be glad to help
I try not to use apple products as a whole so I can't say for sure why its not connecting with adb, is this for sure set up properly? As in has adb or fastboot worked fine in the past? Also is device currently unlocked? By a custom recovery I mean nonstock, not an oem, like twrp or clockwork.
If you want root let's download the latest twrp image for the n4, if you want factory than download latest from here
https://developers.google.com/android/nexus/images?hl=de
Let me know how you want to proceed
Sent from my Nexus 7 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2010312
This will get u up and running.
Next time make sure u know what u are doing.
Credits: efrant
Sent from my Nexus 4 using Tapatalk