Database Users

JWR66Y Update Recovery No Command

I used the OTA recovery to update to JWR66Y, and this worked correctly. I flashed the update using clockworkmod, then clockworkmod asked if I wanted to also flash the recovery part of the update and I did. Now the phone will not boot into recovery mode. It now says no command with the exposed android and an exclamation rather than any recovery option. I attempted to use fastboot to reflash clockworkmod but the phone doesnt show up in adb devices after the adb reboot bootloader command, and when I use the fastboot flash recovery recoveryxxxx.IMG command, it just says waiting for device and nothing happens.
Anyone have any ideas? My apologies if this has already been covered but I did not find it trying to search.
Sent from my Nexus 4 using XDA Premium 4 mobile app

It now says no command with the exposed android and an exclamation rather than any recovery option.
Sent from my Nexus 4 using XDA Premium 4 mobile app[/QUOTE said:
This is the stock recovery which includes now the "no command". To access the menu of this stock recovery press power then press volume up while you keep pressing power.
Good luck.
Click to expand...
Click to collapse

Install the Universal Naked drivers then adb/fastboot will work.
You had the right idea.

Is there a Linux fix for this issue, or do I need to bite the bullet and do a windows install, eek.
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] windows wont recognize 4.4

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.

[Q] ADB sideload Issue

I wiped everything with no rom or backup on my device (d800 using cwm touch) I get a unauthorized mssg when I try adb devices while it bootloops& no device found when in adb sideload, I can't authorize it cause I can't get past the bootloop... Any ideas? Been reading all day/night...

I don't think anyone has gotten adb sideload working for our phone as far as I can tell, anyone know how to authorize adb from only recov or bootloop? Or if you could restore a recovery made using a diff recov?
Sent from my G2 using xda app-developers

Can you get into fastboot or download mode?
Sent from my Nexus 5 using Tapatalk

I get into download but then it says firmware update don't unplug usb n it says root in red at the bottom but it just hangs there at 0% ... And idk if fast boot works, the phone comes up unauthorized in adb.. Would fast boot still work with it not being authorized?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

How do you get into fastboot on this device anyway? I can only get to cwm recovery and a download mode that tries to download a firmware update every time I do..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Nexus 4 (4.4.2) not mounting after unlocking bootloader

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.

Bricked L5.0.2 No ADB or USB

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