Is it dead, Jim? (no fastboot, no recovery) - Nexus 10 Q&A, Help & Troubleshooting

My Nexus10 only goes to bootloader and is not detected by fastboot.
Other devices are detected by fastboot and i tried it on 2 different PCs.
I guess that's it then?

schmolch said:
My Nexus10 only goes to bootloader and is not detected by fastboot.
Other devices are detected by fastboot and i tried it on 2 different PCs.
I guess that's it then?
Click to expand...
Click to collapse
what got you there in the first place? could try uninstalling/re-installing drivers or using a different usb

Related

[Q] softbrick

hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
I apologise for potentially getting your hopes up, but I am in the exact same situation. I am very much interested in this thread.
Google 15 second adb drivers xda. You probably need to get adb and fastboot setup for the pc to recognize your device. In order to fix it you'll meet to use fastboot or adb commands
Sent from my Nexus 5 using XDA Free mobile app
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
nicknc said:
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Going to try that now.
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Ihsahn_ said:
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Click to expand...
Click to collapse
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Ihsahn_ said:
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Click to expand...
Click to collapse
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not at the moment. I have had this appear in the past but this is the point I'm trying to get back to. Unfortunately I can't work out how to get it to appear here. My device is in the bootloader.
---------- Post added at 10:23 PM ---------- Previous post was at 10:13 PM ----------
Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
honorguard said:
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
Click to expand...
Click to collapse
Did you do a clean install?
Have you used a different USB cable? Some cables are charging-only, with no indication otherwise. Internally damaged cables can also turn into charging only cables. Ironically, I just replaced one hooked into my daughter's phone today that would only charge intermittently.
There is no reason that wiping partitions in recovery would prevent your phone from being recognized by your PC at all.
Try a clean install of the drivers on a fresh pc with a different cable.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
Ihsahn_ said:
[Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
Click to expand...
Click to collapse
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
nicknc said:
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
[/COLOR]
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
If it Works with that cable please give me a headsup
Verstuurd vanaf mijn ST25i met Tapatalk
Ihsahn_ said:
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
Click to expand...
Click to collapse
OK.
Sent from my Nexus 4 using Tapatalk
Well, I had similar issues when I bought this phone (coming from a HTC one s) connecting to fastboot.
What I did was:
Delete all drivers related to adb/fastboot/android (use a software to completely clean the files).
Booted my phone into fastboot mode.
Connect to PC and wait for windows to show the new hardware dialog.
Install the correct drivers (which i had downloaded and extracted) using the dialog box.
Profit.
Sent from my Nexus 4 using XDA Free mobile app
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
honorguard said:
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
Click to expand...
Click to collapse
Did you try on a different PC, installing the adb and fastboot drivers before connecting the phone for the first time?
Have you tried a different USB cable?
Sent from my Nexus 4 using Tapatalk
A brief update
I remembered I have a second Android phone knocking around. I plugged this in with one of the cables from earlier - perfect installation with all drivers, etc. This has further convinced me that the hardware of the USB port on the phone is the issue.
Thanks for all help - I'll update again if the hardware change works, or doesn't.
ok, ive installed a new windows and installed all the drivers and then i connected the phone.
Nothing.
i'm getting desperate here..

ADB doesn't see the phone in fastboot mode (although windows sees it)

Hello,
I'm trying to flash a TWRP, but for some reason the phone doesn't show up any more in adb when in fastboot mode (at the bottom of the phone screen it tells me to connect a USB cable). It was showing fine until yesterday. I have tried several different USB ports. The cable is definitely working (in fact plugging and unplugging it causes Windows to notice and make a sound, and also it works fine in ADB when the phone is booted up.
The only thing that I can think that happened since I had last connected to it in fastboot mode (to unlock the bootloader) is that I connected my PC to a couple other phones (Galaxy S3 and Nexus 5) using them in MTP mode. I have reinstalled Google and universal drivers several times, deleted the device from device manager, etc etc. No good.
Any ideas?
We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode
Simer03 said:
We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode
Click to expand...
Click to collapse
Arghhhh :-|
that was it, I was using adb devices. Thanks! (I feel dumb now)

Bricked moto x pure that wont connect to computer through usb

Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
enochthegreat said:
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
Click to expand...
Click to collapse
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
I used the hiensberg guide https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
What do you think is the best option from here?
Are you trying to get into fastboot with it connected to computer?
Iceburn1 said:
Are you trying to get into fastboot with it connected to computer?
Click to expand...
Click to collapse
No im already in fastboot mode. Im just trying to restore my devioe so that it works. When i power on my phone it displays the unlocked bootloader warning then goes into fastboot mode. The screen reads-
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
On top of this my device will not connect to my computer through usb and all my data is deleted included twrp. I really dont know what to do
acejavelin said:
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
Click to expand...
Click to collapse
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
enochthegreat said:
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
Click to expand...
Click to collapse
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
acejavelin said:
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
Click to expand...
Click to collapse
The response is no devices attached. I am android 6.0
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
Have you tried rsd lite it might recognize your device?
acejavelin said:
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
Click to expand...
Click to collapse
My pc operating system is windows vista and my device used to show up on device manager. I used to be able to plug the usb and be able to look at my phone saying device connected
enochthegreat said:
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
Click to expand...
Click to collapse
Do you have this when you boot into bootloader/fastboot mode?
Power off, vol - & power?
I think you can't repair it in home.
It looks like you flashed something wrong or something in wrong place.
F.e.: twrp into boot partition.
jonomods said:
Have you tried rsd lite it might recognize your device?
Click to expand...
Click to collapse
Hmm i just tried that and no device showed up. I think after this im just gonna buy a fresh usb cord and if that does work i am scarping this phone. I overall had a very bad experience with this phone anyways. Ill get back to you once i try.
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
acejavelin said:
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
Click to expand...
Click to collapse
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
enochthegreat said:
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
Click to expand...
Click to collapse
Hmm... Sounds like bad luck, hopefully a new, quality cable will take care of it for you
Looks like it was all bad luck. A day after I bricked my phone my charger port broke

ADB cannot detect after reboot to bootloader menu

ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.

Bootloader no longer seen in 'adb devices'

After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.

Categories

Resources