Related
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app
I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium
From bootloader use fastboot commands, from recovery use adb commands.
You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
biggyk said:
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Boot your Nexus to the bootloader by first powering down the phone then simultaneously press and hold the volume down and power buttons for 2 seconds. Once in the bootloader connect the USB cable from the Nexus to your computer. Open a command prompt in the folder where you have installed fastboot, type "fastboot devices", and press enter. If you see a deviceID listed, you will be able to flash TWRP with the command "fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img" (assuming you are installing TWRP v2.6.0.0); otherwise, you will need to reinstall the Nexus drivers.
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Chromium_ said:
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Click to expand...
Click to collapse
Thank you. Worked fine!!:victory:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks, that was pretty much what I did. The trick was to get it working in boot loader mode. I kept trying to reboot it, and in the end holding down power plus both volume up and down all at the same time for 2 beeps made it work.
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Click to expand...
Click to collapse
I have the same problem, however I can't access my Nexus 10, fastboot devices and adb devices gives back an empty line, so I can't access the N10 with fastboot or adb, to lash a ROM. Factory reset from CWM doesn't work, ˛internal card can't be accessed from CWM ("E: Can't mount /sdcard).
How can I get out of this trouble? (Solutions in forums usually involve reflashing with fastboot or formatting the external SD card. These solutions don't work here...
Any idea would be highly appreciated...
Csaba
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
---------- Post added at 05:17 PM ---------- Previous post was at 05:00 PM ----------
ixxion said:
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
Click to expand...
Click to collapse
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
ixxion said:
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
Click to expand...
Click to collapse
Glad you have managed to make the device visible again (it's really scary when you can't, I know from yesterday!).
Go into bootloader mode (not recovery), and follow the fastboot instructions demkantor gave earlier in the thread.
Get your factory image from https://developers.google.com/android/nexus/images#mantaray.
Get TWRP recovery from http://teamw.in/project/twrp2/128.
At least, that's how I did it.
demkantor said:
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I check md5sum?
Use this for windows
http://www.microsoft.com/en-us/download/details.aspx?id=11533
Or terminal for Linux
md5sum nameoffile.extention
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
ixxion said:
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
Click to expand...
Click to collapse
That means you don't have twrp installed. That's the stock recovery. You can download twrp and use fastboot yo flash it or try the app twrp intaller which dies or fir you
Sent from my VS980 4G using xda app-developers app
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.
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?