Related
I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...
Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.
You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.
I'm not the lowest of the low, but I am the slowest of the slow.
I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
Sent from my EVO using xda app-developers app
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
joshnichols189 said:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
Click to expand...
Click to collapse
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!
I running recovery 2.3.2.1
tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..
Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
Sent from my EVO using xda app-developers app
While in recovery, type in the following:
Code:
adb push <name of ROM zip> /sdcard
You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.
EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:
Code:
adb push <name of ROM zip> /sdcard/ROM
This just shows that you can push a file into a folder on your sd card.
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:
Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app
My Nexus 10 was on Android 4.3 rooted and unlocked. Upgrade to 4.4 via OTA would not work.
I used WugFresh Nexus Rootkit 1.79, and was about to upgrade from Android 4.3 to 4.4, but first ran Flash Stock and unroot so I would be able to accept OTA updates. Unfortunately, the program halted when it completed the requested action, and I am left in fastboot. The tablet is stuck in fastboot mode, and no matter which option I try it always comes back to fastboot mode. Also I have tried to initiate custom recovery, via power and Volume up, but again to no avail.
USB debugging was active, and I had CWM recovery and root.
When I go to 'Restart Bootloader', (or 'Recovery Mode' or 'Start') the tablet immediately reboots back to 'Start'. Thankfully the 'Power Off' button does actually stop the tablet.
I have tried to see if I could get to Stock Recovery from fastboot, but that gives no response beyond going to the next tab.
Is anyone able to provide assistance in recovering from this dilemma?
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks for your response demkantor.
Although I tried to clearly describe the status of the tablet and the problem, I did not intend that I should come across as one who is familiar with the complexities of programming of either the tablet, or rooting around in the registry of a PC.
I can however follow clear instructions.
Your message appears to give a list of what to do, and presumably in the tablet from within fastboot. But I am lost after that.
By the way, the bootloader is unlocked.
Since the fastboot is currently inoperable, how do I initiate fastboot wipe, and then the following 3 commands 'erase system-w, boot & recovery'?
If you can spare the time and expand on your listing, I would certainly appreciate it.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Wow demkantor many thanks! The link you provided will take a bit of reading after I get back from the gym. A full afternoon ahead I suspect! I'll let you know how I go.
Just let me know if you get stuck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi demkantor,
All done and dusted. Many thanks for your help, My tablet is now running on KitKat 4.4.2.
Your contributions to XDA University are very well arranged and written, and logically guide us through the maze. I for one did not know XDA University existed, and it is a shame that you as the person who pulled your contributions together have to also point us to it!
Many thanks for your efforts!
Edit - I read somewhere that the [Q] at the start of the thread should be changed to something else when the problem is resolved. It certainly is! Can the moderator correct this for me please?
Demkantor, I think I may have screwed up big time. I am unlocked and rooted, running stock 4.4. I woke up yesterday and had a notification that a system update had been downloaded. I did a temporary unroot and took the update. Which failed. I went into twrp and wiped everything. Still no go.Then, like a dummy I rebooted after it gave me a warning about not having an os installed. It wont do anything now except go into bootloader. I must have wiped twrp, because it wont boot into that or stock recovery. When I plug it up to my computer,I get this message( fastboot status-failInvalid command). I've just about every option in wugs toolkit. I keep getting adb and fastbooterrors. Have I completely hardbricked my nexus 10? I would appreciate it if you could point me in the right direction or let me know if I'm just wasting my time. I've been messing with this thing since around midnight and I'm about ready to start pullnig hair out of my head. Thanks in advance my friend.
@63t061
Thanks for the kind words, ive been busy lately (finals and all) so normally i would helped more personally but im glad you were able to get it all working on your own through research, which is the best way as im sure you have learned much and will be able to share with the next! Great job! As for editing the thread title, just edit it in your first post @moejoe88
Can you post all input output from cmd/terminal as its easier to see the issue. And try not use tool kits
Start with
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my SGH-T699 using XDA Premium 4 mobile app
Thanks for replying so quickly. I've had to walk away from it for a little while and get some sleep. I'll get some rest and make a fresh start of it. Again, thanks for the quick reply.
I've tried running terminal and the computer wont even recognize the tablet. I believe the battery is drained because I can get it to the bootloader, but it shuts back off after a few minutes. I'm trying to charge for a while and I'll give it another shot. Thanks again.
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.
wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!
Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk
Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.
Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app
Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app
UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?
Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.