N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
fr0d0#2 said:
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
Click to expand...
Click to collapse
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks jd
I don't get anything no matter which mode I boot into
fr0d0#2 said:
Thanks jd
I don't get anything no matter which mode I boot into
Click to expand...
Click to collapse
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
fr0d0#2 said:
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
Click to expand...
Click to collapse
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have an exclamation mark next to N4
Driver re-installed - now recognised as Android Composite ADB Device
fr0d0#2 said:
Driver re-installed - now recognised as Android Composite ADB Device
Click to expand...
Click to collapse
Good, download a rom.zip to your pc if you don't already have one. Then you're going to want to boot into recovery and push the zip to your device using adb. Once there you'll be able to flash it in philz
adb push rom.zip /sdcard/Download. I might have the / backwards. I always forget which way they go. For rom.zip use the full name of the rom. You'll want to have the rom.zip in the same folder as adb.exe and open your command window in that folder too.
Sent from my Nexus 9 using XDA Free mobile app
Thanks jd
You had the slashes the right way around - back in a bit
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
fr0d0#2 said:
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
Click to expand...
Click to collapse
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
fr0d0#2 said:
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
Click to expand...
Click to collapse
Well,a good time to learn. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it recovery for simplicity. I'm going to have you re-install fastboot from, Google 15 second adb install xda. That'll simplify the path issues using fastboot and adb, it sets an environment variable so you don't have to worry about the path to adb or fastboot.
Then open a command window in the same folder as the twrp image is in. With your device booted into the bootloader and connected to your pc run the command
fastboot boot recovery.img.
That'll boot you into the twrp recovery. Go to mount and in the lower right hand corner you should see and option to mount mtp. Then you should see your device in Windows just like you normally would. That should make it easy to copy and paste the rom.zip to your device. Once it's copied just install it using twrp. You shouldn't have to reboot or anything.
Sent from my Nexus 9 using XDA Free mobile app
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
fr0d0#2 said:
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 9 using XDA Free mobile app
For future reference a USB otg cord and pen drive would of been very easy and cheap glad you got it fixed!!
Sent from my LG-VS985 using XDA Free mobile app
Related
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command
In twrp, it keeps saying starting adb sideload feature
i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!
Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
varem said:
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
Click to expand...
Click to collapse
Have you tried to install another rom on your nexus?
you can put it on with adb push command from recovery though a pc, and then wipe everything and try to install it.
Or you can download stock 4.2.2 rom here: http://forum.xda-developers.com/showthread.php?t=2147281
Here you can find your factory image directly from google: https://developers.google.com/android/nexus/images#occamjdq39
How do I adb push?
varem said:
How do I adb push?
Click to expand...
Click to collapse
you must enter into recovery, connect your phone to your pc with usb cable and then you should be able to see your device,
try
Code:
adb devices
on CMD and it can see your phone type
Code:
adb push **your-rom-from-computer** /sdcard/
then just install it from the recovery
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
http://forum.xda-developers.com/showthread.php?p=34674471
My bad I should have read.....you tried a tool kit already
Sent from my Nexus 4 using xda app-developers app
mmh i don't have twrp so i don't know, do you have the option to mount sdcard to usb?
varem said:
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
Click to expand...
Click to collapse
Ok, wait. I need some clarification. I'm going to try to be as simple as possible, to make sure we are on the same page. When you say your PC doesn't read the device, do you mean through adb or on Windows Explorer?
If you mean through Windows Explorer, then that is not where you need to be. You must get adb working as a bridge to your device. Use this sticky guide to get it set up. I would recommend reading that guide top to bottom anyway, it's extremely informative and new-user friendly. Anyway, the info you need is in the 'Setting up ADB for our device:' section.
If you have adb installed, you need to check to see if it recognizes your device. Do this by opening up cmd and navigating to the folder that adb.exe is located. After that, use 'adb devices' to see if adb recognizes your device. If so, move to the next paragraph. If not, your drivers aren't set up properly for recovery mode. Go into Device Manager on your computer and find your device (under something like 'Other devices', or 'Android device'). If you find it, then get these drivers and install them for the device. Do this by right-clicking, and selecting 'Update Driver Software...', 'Browse my computer for driver software', and browse to that folder. I may have missed a few steps on installing the drivers, it's been a while. If so, just search on how to do it, or post back here. I'm sure I can walk through it and get a more precise guide.
Assuming you have adb installed and it recognizes your device, you need to open up cmd and navigate to the folder that adb.exe is located. Then, use the adb push command as outlined above.
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
You can also use the toolkit for pushing a ROM in your SDcard, or backup your SD in your pc.
Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
The PC reads the device as it detects it but when I type in adb devices it doesnt show up. It only ever shows up when I enter the sideload menu in TWRP
atulalvenkar said:
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks man. This toolkit saved my nexus!
Sent from my Nexus 4 using xda premium
after i flashed the aospa 4.4 i lost custom recovery and my pc wont recognize my ohone , ive tried wugs toolkits and installed drivers but it still wont recognize the freaking phone lol
costarican said:
after i flashed the aospa 4.4 i lost custom recovery and my pc wont recognize my ohone , ive tried wugs toolkits and installed drivers but it still wont recognize the freaking phone lol
Click to expand...
Click to collapse
Do this.
download the exe file of fastboot and then goto to bootloader where it shows all thedetails of your phone and the in Pc
open cmd and type fastboot flash recovery recovery.img and enter
you should have a .img file of the recovery.
All done. :good:
my 4.4 is revognized in mtp so its not 4.4,install universal naked drivers. :good
:
Rohit02 said:
Do this.
download the exe file of fastboot and then goto to bootloader where it shows all thedetails of your phone and the in Pc
open cmd and type fastboot flash recovery recovery.img and enter
you should have a .img file of the recovery.
All done. :good:
my 4.4 is revognized in mtp so its not 4.4,install universal naked drivers. :good
:
Click to expand...
Click to collapse
can you link me up please ive been trying for days :/ or pm me please
cmd says fastboot is not recognized as an internal or external command
neither tpt or adb work , the phone only charges thorugh usb
costarican said:
can you link me up please ive been trying for days :/ or pm me please
Click to expand...
Click to collapse
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
dntipwn said:
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've tried in different PCs and it won't even recognize picture mode
Sent from my AOSP on Mako using Tapatalk 2
dntipwn said:
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
All I need is to get it to recognize to fastboot to install the recovery
Sent from my AOSP on Mako using Tapatalk 2
costarican said:
All I need is to get it to recognize to fastboot to install the recovery
Sent from my AOSP on Mako using Tapatalk 2
Click to expand...
Click to collapse
Make sure usb debugging is on.
then install universal naked drivers and then see if your phone is recognized and then install the exe file of fastboot and on cmd prompt in pc follow theinstructions. Profit.
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.
MTP works perfectly. ADB works great when the phone is turned on. However, when the phone is in recovery mode, ADB fails to recognize the device (when I type "adb devices" nothing is displayed).. I have previously flashed the OTA zips for 5.0 and 5.0.1 without any issue. I also have factory reset my phone. I tried the Wugfresh Nexus Root Toolkit Full Driver Text, and it gives a pass. However, this begs the question, why doesn't ADB work while my Nexus 4 is in recovery?
BTW my phone is completely stock and and is not rooted.
If your trying to sideload the of a zip just go ahead and do it. If you start sideload and then type adb devices it'll get recognized.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If your trying to sideload the of a zip just go ahead and do it. If you start sideload and then type adb devices it'll get recognized.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I want to be safe. If in recovery I click "apply update from ADB" and get the message "send the package via ADB sideload", I should be able to type adb devices and see my device? Also, how would I get out of the the sideload screen (ie. which buttons would I hold)?
When you start sideload then open device manager. Find your Nexus 4 an update driver.
Select to choose yourself.
Then List will popup select ADB service in google inc.
Then update driver.
Then type ADB device it will show your device.
Good Luck
Sent from my Nexus 4 using XDA Free mobile app