Fastboot issue - Nexus 9 Q&A, Help & Troubleshooting

Just got my N9 today. When I ADB devices, i see the serial # of my device properly. If I go into bootloader, when I fastboot devices, it comes up as all question marks (??????????????? fastboot). Windows properly sees my device as "Android Bootloader Interface". I am able to do basic commands (oem unlock, reboot-bootloader, etc). However I cannot push any files (root or custom recovery.) My DOS window just hangs and nothing transfers.
I googled for three hours and can't find if this is fixable or if I have to RMA. (And if I do RMA, how would I? I can't say I am having issues pushing custom recoveries to the device LOL)
Thanks in advance!

Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way

PaisanNYC said:
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way
Click to expand...
Click to collapse
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.

PaisanNYC said:
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.
Click to expand...
Click to collapse
Bootloader surprised me too. Not like the other nexus devices
Sent from my Nexus 9 using XDA Free mobile app

I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?

JacKalPin said:
I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?
Click to expand...
Click to collapse
Don't plug it into a USB 3.0 port. that was my issue all along. Use a USB 2.0 port.

It's a cable fault. In my Redmi 3 on a cable from old Xperia P i've had question marks,
replaced the cable to a newer cable from Redmi Note 2 and voila - the correct number displays instead of the question marks.

Related

I think i bricked it..

So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
IceAzures said:
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
Click to expand...
Click to collapse
go into recovery and try turning adb sideload on then off and see if adb recognizes your device after that.
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
IceAzures said:
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
Click to expand...
Click to collapse
Then you didn't set adb up correctly
Edit: now that I think of it you may be typing in the command incorrectly.
Sent from my HTC6435LVW using xda app-developers app
Ill reinstall the sdk and drivers and ill report back.
This is the correct way right?
http://forum.xda-developers.com/showthread.php?t=2131284
edit1: so to use adb im using the windows vista cmd promt correct?
edit 2: okay so we are somewhere. Adb now works. I just need to get the dna to be able to be detected. Any way i can do this?
(double post accident)
IceAzures said:
(double post accident)
Click to expand...
Click to collapse
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
IceAzures said:
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
Click to expand...
Click to collapse
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
beaups said:
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
IceAzures said:
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
Click to expand...
Click to collapse
nope. Vista sucks and all, but it isn't the problem here.
IceAzures said:
Do you think vista might be an interference?
Click to expand...
Click to collapse
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
beaups said:
nope. Vista sucks and all, but it isn't the problem here.
Click to expand...
Click to collapse
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
AGoogleUser said:
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah and unfortunately its all i got
IceAzures said:
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
Yeah and unfortunately its all i got
Click to expand...
Click to collapse
I'd recommend you flash twrp then adb push your rom, then flash it
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
IceAzures said:
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
Click to expand...
Click to collapse
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
reaverclan said:
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
Click to expand...
Click to collapse
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
When in device manager , how is the unit listed? Does the listing have an yellow exclamation point in front of it?
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot but still having issues pushing or flashing rom
Click to expand...
Click to collapse
Might want to unplug from the net when installing them so it doesn't look for others which driver version you installing? EDIT: also if you have a otg cable then you can put the rom on a flash drive and flash it from that.
Sent from my VIPER DNA
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
What error is it giving you when you try to push a rom.
Sent from my HTC6435LVW using xda app-developers app

[Q] Sideloading when unauthorized?

Hi all,
I have a Galaxy Nexus. I accidentally wiped the SD Card trying to flash back to stock, and now I have no OS. So, I'm trying to sideload a file onto the device but I'm getting an unauthorized message, as seen in the photo attached. I'm on a computer I've previously authorized, and I've tried one I hadn't, but both give me the same message.
Is there any way I can bypass this to get this file on my phone? Since I can't sideload through this, I've basically hit a wall.
My recovery is CWM, if it helps, but I've gone through every option and nothing seems to allow authorization.
I'd really appreciate any help, my phone's basically a brick at the moment
Don't own a galaxy nexus, but its my understanding that all galaxy devices have fastboot capabilities, if this is true why not flash a recovery that doesn't require authorization
Or if there is a download mode like other Samsung's, try hiemdal to return to stock
If there isnt a download mode than I would assume there is a factory image that could be flashed through fastboot, I'm sure all this info and more is easily searchable in your devices forum
Best of luck
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Don't own a galaxy nexus, but its my understanding that all galaxy devices have fastboot capabilities, if this is true why not flash a recovery that doesn't require authorization
Or if there is a download mode like other Samsung's, try hiemdal to return to stock
If there isnt a download mode than I would assume there is a factory image that could be flashed through fastboot, I'm sure all this info and more is easily searchable in your devices forum
Best of luck
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I got it up and running, thanks for the help!
For anyone with the same issue in the future, my main problem was thinking I had to get past the unauthorized device message in order to sideload and use CWM to flash. I hadn't considered using fastboot to just flash stock. The Nexus Toolkit's back to stock option in softbrick/bootloop mode was able to reset to stock and get my phone up and running, after I reinstalled drivers.

[q] htc one wiped internal storage adb not working

Hi, everyone. I wiped the internal storage on my htc one on accident while trying to wipe the dalvik cache on twrp. Now when I turn on my phone it gets stuck on the splash screen. I hold down the volume button when turning it on and it goes to hboot where I am able to navigate to fastboot and my twrp recovery. Besides those two things all data on my phone is completely gone the storage only has about 16 megabytes on it now. In the cmd prompt typing in adb comes up with device not found and adb device shows an empty list. Fastboot devices in cmd however dpes find my phone which is odd. Updating my drives doesn't work and the mtp driver can not install for some reason. So I can not use adb to push or sideload anything. I could use twrp to sideload something maybe if I could somehow get something onto my phone. RUU won't work because I never turned my s-off and since I am now at this stage I don't know of anyway I can turn my s-off. Could someone maybe tell me how I could get my adb to find my device(updating drivers doesn't work). Really any way to solve this would be appreciated I tried so many things. I've unlocked and relocked bootloader so many times for different things. Basically there is no os on my phone. I can not use adb to put a rom on my phone. I only have access to hboot fastboot usb and twrp recovery. Please links and some instructions would be very much appreciated. If you help me fix my phone I will ofcourse give you thanks on your reply and when I can I will donate money to you(not saying any time soon as I do not have a job and am currently looking but I will remember you for saving my phone and I am the type of person to return favors).
No need for thanks or money, but if your device supports otg cable you may be able to load a ROM on there, don't have a one so I can tell you if it does
True, without s-off or super cid you can't flash older versions of an os than you're currently on but that doesn't mean in the future there won't be an ruu that is newer, of course that won't help you now but its something at least (and another reason why s-off is key for any HTC phone)
But If otg doesn't work than you need to find something that will flash in bootloader (double check if there are any stock ROMs, try them all - at least look into them all) and as for adb see if you need to update binaries on your PC, open the SDK and try to update. Also try to uninstall first then reinstall drivers
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
.
demkantor said:
No need for thanks or money, but if your device supports otg cable you may be able to load a ROM on there, don't have a one so I can tell you if it does
True, without s-off or super cid you can't flash older versions of an os than you're currently on but that doesn't mean in the future there won't be an ruu that is newer, of course that won't help you now but its something at least (and another reason why s-off is key for any HTC phone)
But If otg doesn't work than you need to find something that will flash in bootloader (double check if there are any stock ROMs, try them all - at least look into them all) and as for adb see if you need to update binaries on your PC, open the SDK and try to update. Also try to uninstall first then reinstall drivers
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just got my adb to recognize my phone however it only recognizes it while in twrp recovery.
That's normal, it won't work in bootloader ever, just recovery and os
So your good now right? Just need to adb sideload and your off to the next ROM!
Seriously consider s-off though, I highly recommend it when possible
Happy flashing!
Sent from my Nexus 4 using XDA Premium 4 mobile app
.
demkantor said:
That's normal, it won't work in bootloader ever, just recovery and os
So your good now right? Just need to adb sideload and your off to the next ROM!
Seriously consider s-off though, I highly recommend it when possible
Happy flashing!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload wont work it says unable to mount data and unable to mount internal storage and unable to mount everything else it is supposed to mount
Sounds suspiciously like corrupt partitions, hopefully formating within recovery will fix this, may need to flash recovery again from fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app

/system partition destroied

Hello.
I have a problem with friend's phone.
It's HTC Desire Z (Vision). I S-OFFed how it's described on CM wiki. Latest radio.
About month ago I installed CM 10.1 AlterNdromadus.
It worked until yesterday, when it unfortunately installed some system update.
After that phone didn't booted anymore. In recovery it says, that it can't access system partition and formatting is not possible.
I tried connect the phone via fastboot in bootloader, but it also doesn't work. Under windows I have it as unknown device and when I tried manually install drivers from google, it says that they are not compatible with the HW (under ROM it worked before).
I tried also install stock RUU rom (extracted the zip and deleted H-BOOT, radio and recovery) from SD-card (PC10IMG.zip). But it also got frozen on system update.
Here you can see error from 4EXT recovery and CRC images from bootloader.
Any suggestions? :crying:
Thanks
Well, I guess I meant to keep this thread in the desire z q&a thread but this works
I wish we could know what kind of system update was flashed as it may be easier to fix this
There shouldn't have been any system update as there is no ota associated with that ROM, but we can try anyway
http://forum.xda-developers.com/showthread.php?t=2348266
Here you will find links to get you proper drivers, being your on windows try using a free program called USBDeviw, I have had to use this a lot to erase drivers and then manually install the proper ones (windows is terrible at this)
Or if you can dual boot Linux you may find life easier as once you get fastboot working you should be able to quick fix this.
Otherwise try out the aio wipe tool and or superwipe script that is linked in the guide I sent you
But really, try to get the drivers working and we should be good
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tried both superwipes. Doesn't work :/
The problem with fastboot is, that windows totally doesn't recognize the device. So I'm not able to install any drivers (see attachment).
The reason why I posted it in this section is, that I found people with similar problem on other phones. But noting work to get it back...
Any recommendation for the linux?
I booted successfully SystemRescueCD. After a half hour I also went ADB but no devices were found...
The screenshot is blurry when looking at it from my phone but it looks like windows 8/8.1 which many have issues getting adb/fastboot to work right. Usually the fix involves using usb3.0 ports
Can you just dual boot a Linux distro? Ubuntu is a very simple one to work with and you will easily find guides how to get fastboot working on it, actually if you see the thread I linked you there is one on fastboot that walks you through the process
If you don't want to dual boot a live CD is fine, but you still need to get the adb/fastboot binaries installed and working from that disc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes, it's windows 8.1. I don't have USB3.0.
I have here also one really old desktop with windows 7, I will give it a try.
Otherwise last chance is the Ubuntu (I don't want to dualboot, so I will made live USB).
I downloaded from XDA two files - ADB and fastboot for Linux.
Downloading and installing adb from SDK from google doesn't look so easy as on windows...
Also should I use drivers from HTC sync or from google SDK?
Because through ROM it worked right with the google's drivers...
although this is not what you may want as an answer but why don't you copy a ROM to SD card n flash via recovery,, it'll regenerate system,, once it is regenerated,, you can connect to your PC and carry on to what you want.
Nope. It doesn't work. I tried it as first option.
I just forgot to write it here....
seems like you might have actual physical damage/bad sector on ur device.
this is what happens in hard drives, they can't be formatted, no read/write etc.
i don't know if there's any app that can help fix you this coz you can't connect to system/OS in first place to do so,
Best option seems like to dust off the warranty papers n get it to service center for repairs as it might need physical parts replacement.
I got working fastboot (not ADB) on Windows7.
When I tried fastboot format /system I got error "Uknown command".
When I tried fastboot erase /system I got error "No partition found"
Yes, it's probably problem with bad blocks...
The issue at hand depends on what this 'update' was as the ROM that was running on the phone at the time would not have had one which means something was flashed to it that shouldn't have been.
Being the phone had security flags removed (soff) a number of things that shouldn't be allowed to flash can be, so depending on what it was will determine how fixable it is
At this point the only way to fix it or at least dertimine if it is fixable is to get phone and PC to connect via fastboot and adb
So use the windows 7 or Linux, set it up with drivers found in xda wiki or write the android rules for Linux and work on this, its doubtful you can move forward until this is done
Sent from my Nexus 4 using XDA Premium 4 mobile app
As I wrote, I got Fastboot worked.
BTW isn't possible to acces ADB only from the ROM?
I tried to get it work without success. I tried HTC and google drivers...
Must have posted while I was posting and I missed that
Fastboot only works from bootloader and adb only works in os and recovery
The commands you were using isn't correct, I suggest you read again the two fastboot links from the link I sent you for clear instructions.
For right now I would grab the latest cwm, twrp or 4ext recovery (4ext still best for this phone)
Then
fastboot erase system -
fastboot erase recovery
fastboot erase boot
Then
fastboot flash recovery nameofrecovery.img
Then if all goes well grab a known stable ROM and flash it (along with gapps if needed) from new recovery
If things don't work as planned be sure to copy and paste all input/output from cmd
Sent from my Nexus 4 using XDA Premium 4 mobile app

Can't get past first update

This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)
Aleschio said:
This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)
Click to expand...
Click to collapse
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the fast reply!
It worked! Thanks a lot for you help! You saved my file

Categories

Resources