Ok here's the deal...
Im running XP 32bit, and ever since I installed 5.0.2h my ADB Interface entry is missing from the Device Manager.
I'm constantly getting error: device not found when trying to connect through the command prompt and the device is showing up as a "disk drive" and under the USB Controllers as a "mass storage device" in the device manager.
No matter how many times I uninstall these, and delete the entries from the registry, it automatically adds it as a disk drive every time I connect.
I then successfully try to manually add the ADB driver and it constantly comes up saying the "device cannot be started"
Anyone find a solution to this problem?
Thanks.
Hmm. Rebooting, then disabling and re-enabling Debug Mode did the trick.
Weird.
when im trying to push font do i got into fastboot mode? because when i do then go into cmd and type adb remount it keeps sayin device not found
Ok.
I was running Ubuntu 11.04 64 bit.
Because of this, I wiped the system and am now running Ubuntu 12.04.
The issue persisted.
I did install the lib file, I forget the name, but it did install successfully.
I have an android rules file, labeled 51-android.rules, with +w+r+x access
{
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",MODE="0666",OWNER="root"
}
I have fully updated my SDK
I have set the path correctly for ADB.
When I plug in either my G1 or a MyTouch 3G, and run the command adb shell I get:
error: device not found
When I run the command $ adb devices I get:
List of devices attached
Debugging is enabled on both phones. I tried only the MyTouch 4G on another computer but am getting the same result.
My goal, as a noob, is to try my hand at App development. I know the AVD is a good resource but trying it live is nice.
I have rebooted the handset and restarted debugging.
The handsets are charging when plugged in.
Probably need to download the proper drivers
Sent from my HTC Vision using xda premium
I did not think Linux needed drivers.
Where you meaning that you sent me the drivers? Sorry friend.
I really appreciate the help.
to my understanding all operating systems need drivers, they just tend to come with them. im guessing you may have the wrong ones being recognized when you plug in your phone. try manually installing the right ones from the sdk website or updating all the drivers found in your sdk manager
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
well felt like checking on this, here is the first link i found in a google search, looks like you will find your answers here
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
@ demkantor
Your the MAN! Thank you sir. To be honest I am running out now to class, but I did skim through it and it looks very good. I am pretty sure my answer is in this list somewhere.
Now, I did a QUICK google search, and ill get back to it sometime this weekend, but off the top of anyone's head, do you happen to know the 51-android.rules line for precise pangolin? It refers to different ones, but I know its new and its not on that list. I have an HTC device so I know to use 0bb4 as the vendor ID.
This is a great forum, thank you guys.
http://www.joescat.com/linux/android_rules.html
This has been great information. I think I am getting closer to an answer.
I ran through both documents. Good information in there big time, Ill be keeping them handy.
Still, even after setting the rules and everything, I do not show a device. In fact, I tried even my very old G1 and am getting the same results
When I run lsusb (as root) I am getting no devices beyond the usual:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 04f2:b090 Chicony Electronics Co., Ltd
Bus 006 Device 002: ID 04d9:1203 Holtek Semiconductor, Inc. Keyboard
Bus 006 Device 003: ID 0461:4d42 Primax Electronics, Ltd
Keyboard/Mouse/Hub. Even after plugging and unplugging the handsets I get the same result. This is the 2nd cable I have tried and both phones actually do charge, though even still I am not getting the SD option either, much less debugging. I tried this on another computer at work that I test other devices on and I am getting the same results.
Thank you again.
---------- Post added at 03:14 AM ---------- Previous post was at 03:07 AM ----------
Oh man.... 2 bad cables....
After writing my last response, I said "What the hay" and threw in another cable... Boom Bam there she blows!
I really appreciate everything though. Believe me, these docs will not go in vain. I still need to read through them THANK YOU dudes a great deal!
Related
I'm having problems with adb finding my device. I have installed the SDK and the adb command works. I followed the cyanogen wiki for setting up .bashrc (commands work) and /lib/udev/rules.d/11-android.rules
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="scott" #Normal
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666", OWNER="scott" #Recovery
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="scott" #Fastboot
I tried changing the 11 to 50 and 51 as I have seen in other posts. I have tried running adb as root. I can mount the file system. I have tried using adb with the file system mounted and unmounted. Usb debugging is enabled. lsusb shows my device:
Code:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 0bb4:0c01 High Tech Computer Corp.
But when I run adb devices I get:
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:~$
Any suggestions on what I'm doing wrong?
have you tried windows? why must you use kubuntu?
pr0cl1v1ty said:
have you tried windows? why must you use kubuntu?
Click to expand...
Click to collapse
Why must you have Android?
While my reasoning shouldn't really mater, here it is. I don't have Windows on my machine. It ran like crap when I had it. I tried Kubuntu on it and it ran perfectly fine. I don't use my computer often any more as my phone has become my primary source for online access. I'm not about to go out and spend $$$ for an operating system that doesn't run as well as the one I have on the computer I use primarily a backup and storage device. I also can't use the recovery CD that came with my computer since I don't have it any more.
ha ok bro, have fun with your problem, i know the answer im just not going to give you it for being a F*** face about it. I came to help you and thats what you say to people ha have fun.
Questioning my choice of OS is neither relevent nor constructive. To me it seemed more like a "just use windows" answer. I'm sorry if i came across as a f*** fase as that was not the intent. Tone isn't something that is easy to convey while typing and can sometimes be misinturpreted.
spullar said:
Questioning my choice of OS is neither relevent nor constructive. To me it seemed more like a "just use windows" answer. I'm sorry if i came across as a f*** fase as that was not the intent. Tone isn't something that is easy to convey while typing and can sometimes be misinturpreted.
Click to expand...
Click to collapse
I still haven't figured a sure fire way out for sarcasm
hi guys i could use andriod 4 in my htc shift
i get my 3g working after i did lsus in my terminal in android and i get that connection
bus 003 device 002: id 0bb4:0303
so how can i make that connection work in android to use internet
thanks ,,,i am not well developer so i need some detalis
thanks
I installed Ubuntu 13.10 on my Laptop and deleted the old Ubuntu 12.04.
Now Novacom didn't work anymore.
I installed it, but:
Code:
sudo novaterm
unable to find device
The Tablet is connected with the recovery mode:
Code:
lsusb
Bus 002 Device 003: ID 0830:8071 Palm, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0c45:640f Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I tried to install novacom on the Ubuntu 12.04 of my father but there is the same problem...
I don't now if i am doing something wrong...
Where can i find an intruction for installing novacom on Windows (8) (64 Bit) or Ubuntu 13.10 (64 Bit) /Ubuntu 12.04
Did you use the universal installer?
https://code.google.com/p/universal-novacom-installer/
It supports windows and Ubuntu but I dont know about the newest versions.
I tried both...
jokergermany said:
I tried both...
Click to expand...
Click to collapse
Well I have always heard people having issues with Windows 7 and 8. I'm not sure about Ubuntu. My computer still runs Windows XP. lol
Ok, i used the Windows 7 32 Bit from one of my fathers pcs...
jsgraphicart said:
Well I have always heard people having issues with Windows 7 and 8. I'm not sure about Ubuntu. My computer still runs Windows XP. lol
Click to expand...
Click to collapse
Perhaps because Windows 7/8 is mostly used with 64 Bit and Win XP mostly with 32 Bit
By the way: I wouldn't use Win XP after April
Sorry for reviving an old thread. I haven't had to do this for a long while, and I no longer have the Windows laptop where I first installed novacom. So, I'm trying to do this on an Ubuntu 16.04 machine.
My TP has moboot and CWM. It currently has Kit-Kat on it. I don't remember if I still have webos on it.
I have installed novacom using the universal installer on Ubuntu and was able to run novcomd. However, after rebooting into recovery, when I tried to run novaterm, I got the errors in OP. lsusb did not show the TP device.
Any ideas how to fix this?
tsoheq said:
Sorry for reviving an old thread. I haven't had to do this for a long while, and I no longer have the Windows laptop where I first installed novacom. So, I'm trying to do this on an Ubuntu 16.04 machine.
My TP has moboot and CWM. It currently has Kit-Kat on it. I don't remember if I still have webos on it.
I have installed novacom using the universal installer on Ubuntu and was able to run novcomd. However, after rebooting into recovery, when I tried to run novaterm, I got the errors in OP. lsusb did not show the TP device.
Any ideas how to fix this?
Click to expand...
Click to collapse
Considering the fact that you're running on 16.04, ADB might be the way to go in order to see and interface with the tablet.
I updated my 'Nix tower to 16 and _all_ my utilities that I use for working on devices failed. Had to go back to 14.04.x
_Dan
Hello,
I bricked my phone doing something quite silly... upgrading to stock firmware using OTA from custom ROM. Yes, I used to be an Iphone user, and with Iphones, a recovery would make the phone stock, no matter what state it was in previously.
Anyways, my HTC One Google play edition now has no OS, and no recovery available. I am also unable to use ADB commands to connect to the phone from my Windows 7 PC. However, if I load up my Linux CENTOS through Vmware (VMplayer), the OS recognizes the phone.
Can anyone provide details on the next steps? I don't care what version OS (stock or custom) the phone is fixed to, I just want to fix it and be able to use it again.
On a side note, I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully. I can also provide remote desktop connection via Teamviewer or Cisco WebEx, if you prefer to just work on it remotely.
Thanks!
J
ca12bon said:
I am ... unable to use ADB commands to connect to the phone from my Windows 7 PC.
...I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully.
Click to expand...
Click to collapse
You can keep the $100, just see if you can run fastboot getvar all and post the results here and I'm sure plenty of folks will be happy to chime in for free.
If you got adb working on windows 7, presumably you have a working install of the latest android SDK. Also you say you can get into HBOOT.
If so, you're not completely "bricked".
You should still be able to run some fastboot commands. That will be your way out.
Just to spell this out, connect the phone to your PC, boot into the bootloader, select fastboot (on the phone) and try running some of the fastboot commands (from a terminal window in the PC). Start with 'fastboot devices' to see if you are even talking. If your phone's serial number appears, proceed to 'fastboot getvar all' and post the results (edit out your imei and serial number) here.
You can do a lot from fastboot, such as flashing a fresh recovery or even an RUU.
"Brick" is a pretty extreme state. You're not bricked.
Sent from my HTC One using xda app-developers app
NxNW said:
You can keep the $100, just see if you can run fastboot getvar all and post the results here and I'm sure plenty of folks will be happy to chime in for free.
If you got adb working on windows 7, presumably you have a working install of the latest android SDK. Also you say you can get into HBOOT.
If so, you're not completely "bricked".
You should still be able to run some fastboot commands. That will be your way out.
Just to spell this out, connect the phone to your PC, boot into the bootloader, select fastboot (on the phone) and try running some of the fastboot commands (from a terminal window in the PC). Start with 'fastboot devices' to see if you are even talking. If your phone's serial number appears, proceed to 'fastboot getvar all' and post the results (edit out your imei and serial number) here.
You can do a lot from fastboot, such as flashing a fresh recovery or even an RUU.
"Brick" is a pretty extreme state. You're not bricked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey man,
Thanks for the help, really appreciate it. My Windows is unable to recognize the phone via ADB, so I cannot run any fastboot commands. I will go home tonight and try again for the exact readout, but I couldn't perform any commands whatsoever.
However, when using CENTOS (through vmware), the OS recognizes the phone:
[[email protected] Desktop]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 003: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Screenshot of HBOOT:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My "main" problem, is I do not know how to get ADB/fastboot installed to my CENTOS mounted on Vmplayer. I think if I can use ADB and fastboot commands, I can push a custom recovery to my phone and install a working ROM.
Regards,
John
Ah, I see, yes it looks like getting the computer to recognize the phone is the main obstacle at this point.
Not an expert on Linux, but I did just run across this reminder about windows 7:
matanlevanon said:
Well, being able to fastboot is crucial... next time you can just install HTC Sync which will update your drivers and then un-install it.
Click to expand...
Click to collapse
Do you have the latest drivers from HTC?
Sent from my HTC One using xda app-developers app
@nkk71's guide has some commands for Ubuntu that may help
Look at step 5
http://forum.xda-developers.com/showthread.php?t=2541082
ca12bon said:
Hey man,
Thanks for the help, really appreciate it. My Windows is unable to recognize the phone via ADB, so I cannot run any fastboot commands. I will go home tonight and try again for the exact readout, but I couldn't perform any commands whatsoever.
However, when using CENTOS (through vmware), the OS recognizes the phone:
[[email protected] Desktop]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 003: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Screenshot of HBOOT:
My "main" problem, is I do not know how to get ADB/fastboot installed to my CENTOS mounted on Vmplayer. I think if I can use ADB and fastboot commands, I can push a custom recovery to my phone and install a working ROM.
Regards,
John
Click to expand...
Click to collapse
Try this first:
1. install HTC Sync on your computer (this will install the latest drivers for you)
2. Create a folder in your C:\ drive naming it 'adb' or something like that.
4. Place the content of this folder (4 files) in your adb folder
5. when in bootloader hit "fastboot" (wait until all the drivers are installed on your PC, give it a good 5 min while the phone is connected and in fastboot mode) you should see at one point "fastboot usb" like in the attached photo:
6. if you don't see it, reboot your computer and try again.
7. your fastboot should work now, use the following guide to flash recovery (Section 3) and you can transfer your ROM and install it.
Use the $100 to buy your phone some nice accessories and remember me by them
I have often heard people recommend adding an additional step between 1) and 2) , let's call it step 1.a) uninstall the actual HTC Sync app (drivers will remain installed)
Is it still necessary?
Sent from my HTC One using xda app-developers app
ca12bon said:
Hello,
I bricked my phone doing something quite silly... upgrading to stock firmware using OTA from custom ROM. Yes, I used to be an Iphone user, and with Iphones, a recovery would make the phone stock, no matter what state it was in previously.
Anyways, my HTC One Google play edition now has no OS, and no recovery available. I am also unable to use ADB commands to connect to the phone from my Windows 7 PC. However, if I load up my Linux CENTOS through Vmware (VMplayer), the OS recognizes the phone.
Can anyone provide details on the next steps? I don't care what version OS (stock or custom) the phone is fixed to, I just want to fix it and be able to use it again.
On a side note, I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully. I can also provide remote desktop connection via Teamviewer or Cisco WebEx, if you prefer to just work on it remotely.
Thanks!
J
Click to expand...
Click to collapse
uninstall all HTC drivers and software, then try these http://forum.xda-developers.com/showthread.php?t=2261088 drivers
Thanks very much for the input everyone, unfortunately I forgot to bring my phone to work today, I will try out all the suggestions at home tonight.
Hope you all have a great day
Okay I've tried all the methods posted above... but still having the same issue.
Although the phone had USB debugging mode enabled before I bricked it, not really sure if it's on now. Also, I read that I need to have S-OFF, but in order to do that, the phone needs to be recognized by the PC.
Anyone know how to install or download ADB to CENTOS Linux? (or any other Linux)? Since the Linux VMware OS recognizes the phone perfectly, I think that's my only chance at pushing a custom recovery and ROM to the phone.
Are you definitely in fastboot when you try to connect in windows? Also, make sure you disable any antivirus and windows firewall, as I have found them to cause connection issues.
HTC One, Unlocked, S-off, Super CID, ARHD ROM, ElementalX Kernel
i did "fastboot oem unlock" and get fastboot bootloader unlocked code 3. i flash twrp, open revovery and reboot the bootloader to recovery. then when i reboot the os, twrp is gone and i get the recovery robot. is this because the phone is encrypted and code 3? i can load twrp and backup, then the next time i load twrp it finds the backup in restore. it seems that twrp works i just need to flash load it each time i want to use it, like when lineage comes out with 15.1 for the nex6. i am a novice at this and will this situation work to load a custom rom? thanks
The stock ROM is replacing the custom recovery with the stock recovery on boot. To prevent this, you must follow the TWRP install instructions found on the device page at the TWRP website (twrp.me).
The site appears to be down so basically, after flashing TWRP in fastboot, use the power button to turn off the device. Then reboot to bootloader using the key combination; power + volume up simultaneously. Use the volume buttons to find "recovery" then use the power button to select and enter TWRP. Once TWRP is launched, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP again.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
The stock ROM is replacing the custom recovery with the stock recovery on boot. To prevent this, you must follow the TWRP install instructions found on the device page at the TWRP website (twrp.me).
The site appears to be down so basically, after flashing TWRP in fastboot, use the power button to turn off the device. Then reboot to bootloader using the key combination; power + volume up simultaneously. Use the volume buttons to find "recovery" then use the power button to select and enter TWRP. Once TWRP is launched, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP again.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
i flash it, when i go to fastboot, recovery, twrp loads it asks for a password, i put my pin # in i get get in red "unable to mount storage" then it loads the twrp interface. i tick reboot then power off. power key + volume down loads fast boot and i navigate to recovery and twrp repeats the the cycle. now i power down and boot the os. after that no more twrp in fastboot. so yes i did open twrp log off fastboot, log back into fastboot, log off and then reboot the os.
Did you change the encryption password from the default for your storage?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Did you change the encryption password from the default for your storage?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
it is a used phone from ebay. encryption in settings is on.
from what i read that encryption is part of the kernel. i was thinking to flash 15.1 unofficial which should give the phone a new kernel?
No, not like that. The kernel has "flag" that determines if it's possible to decrypt the device. But even if the kernel is "no force encrypt", you must wipe the internal storage (user data partition) to then have a decrypted device.
Doing a Wipe -> Format data ->Yes from within TWRP should fix the problem. It will lose everything on the internal storage though.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
not much in there i just got it up. so i will flash twrp an then wipe with format. data. just double checking before i go ahead.
i did the format, it showed a lot of red print. in the end i am back to the same place "unable to mount storage" and twrp does it's disappearing act.
There's not much to go on in that statement.
It's important to have the latest version of TWRP installed (twrp-3.2.1-0-shamu.img).
Without better information to help you, I would suggest fastboot flashing the last stock release from Google (Factory Images for Nexus and Pixel Devices ). The instructions on that page are good and accurate. The N6 is considered an older device and uses the command: "fastboot oem unlock"
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
i did the fastboot oem unlock that is where i got bootloader unlocked "code 3". thanks for the help i will head on over to the factory image. during the format command it reported, if it helps
unable to mount storage
formatting data failed to mount data device or resource busy
unable to recreate /data/media/folder.
i am a never at this and i plan to install factory on my linux pc with the following.
fastboot oem unlock
cd /home/ [where i put the zip]
flash-all.sh shamu-n6f27m-factory-bf5cce08.zip
any problems? thanks
have i got it right? thanks
dr1445 said:
i did "fastboot oem unlock" and get fastboot bootloader unlocked code 3. i flash twrp, open revovery and reboot the bootloader to recovery. then when i reboot the os, twrp is gone and i get the recovery robot. is this because the phone is encrypted and code 3? i can load twrp and backup, then the next time i load twrp it finds the backup in restore. it seems that twrp works i just need to flash load it each time i want to use it, like when lineage comes out with 15.1 for the nex6. i am a novice at this and will this situation work to load a custom rom? thanks
Click to expand...
Click to collapse
I had similar problem:
install twrp and used it,
reboot the os,
launch again the recovery mode and twrp was gone.
I solved it by rooting the phone (with SuperSU) immediately after twrp installation (before the OS reboot!!)
in one attempt to install twrp i dropped back to v 2.8, it asked me if it wanted su, clicked ok and it failed, so did kingoapk. after looking at the factory google roms i see verizon has one. This phone was from ebay with an unknown carrier but it did come with a verizon sim card. that maybe what the code 3 comment next to "bootloader unlocked" is about. verizon likes to make boootloaders unlockable. if so, i may not not be able to do a factory reset with the code 3 in place.?
The code 3 is a status that the bootloader is unlocked. It's normal.
Dropping backwards to an old recovery is a mistake and the fact you tried to install su through it complicated the problems.
You need to follow a set of instructions without impatience and completely or you'll be stuck in this loop forever.
No N6 bootloader is unlockable, including Verizon. Use the newest release from Google as I stated before and return to full stock.
Go to this thread/post and read to the end: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. There is good information and old, incorrect information in the OP of that thread. It's why I'm sending you to the middle.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
not sure about that but then i am the one asking the questions. i first installed the latest twrp-3.2.1-0-shamu.img, logged off fastboot, logged back on fastboot then rebooted the os. did this several times each time i went back to fastboot twrp is gone. then i tried the older version. the "unable to mount storage" has persisted each time. if i have the code for my linux pc right i will give the factory install a try. thanks. edit; from the the link you sent it looks like i can use twrp from my pc an install either lineage 15.1 unofficial or wait for the official version without a problem. i would be ok with that?
Remember, you need to power off the phone then use the previously mentioned key combination and go straight back to recovery after flashing the TWRP image. Anything else and the stock ROM will overwrite recovery.
Here are the udev rules for an Ubuntu based PC.
Code:
/etc/udev/rules.d/99-android.rules
# Google Nexus 6 16 Gb
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1:4ee7", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev" TEST=="/var/run/ConsoleKit/database", \RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0666", OWNER="" # MTP media (multimedia device) nexus 6
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666", OWNER="" # MTP media with USB debug on(multimedia device) nexus 6
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666", OWNER="" # PTP media (camera) nexus 6
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee6", MODE="0666", OWNER="" # PTP media with USB debug on (camera) nexus 6
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666", OWNER="" # Bootloader nexus 6
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="" # Recovery nexus 6
Then restart the service
Code:
sudo service udev restart
or just restart the computer.
If you want, you can double check the vendor id and product id using "lsusb".
The script method of flashing is fine. If you run into problems, these next steps outline a manual method of flashing each partition. You need to extract the images from the compressed stock file first.
It's easiest if the stock rom is in the same directory as where place you put the fastboot binary. But you can just use the entire path to the location of the stock images. It's also less error prone to rename the stock images to just bootloader.img, radio.img, recovery.img, boot.img and system.img.
reboot to the bootloader
./fastboot reboot-bootloader
First flash the bootloader:
./fastboot flash bootloader /[PATH TO IMG]/bootloader.img
Again reboot the bootloader by typing
./fastboot reboot-bootloader
2nd flash the radio:
./fastboot flash radio /[PATH TO IMG]/radio.img
Again reboot the bootloader by typing
./fastboot reboot-bootloader
3rd flash stock recovery:
./fastboot flash recovery /[PATH TO IMG]/recovery.img
enter
Again reboot the bootloader by typing
./fastboot reboot-bootloader
4th flash boot partition:
./fastboot flash boot /[PATH TO IMG]/boot.img
Again reboot the bootloader by typing
./fastboot reboot-bootloader
5th flash the system: ( the -w cause the partiton to be wiped before flashing the new system image)
./fastboot -w flash system /[PATH TO IMG]/system.img
In your case (but probably not for everyone who stumbles on this post!)
6th wipe the user data partition: ( ** this clears internal memory!! **)
./fastboot erase userdata
Then clear the cache:
./fastboot erase cache
Finally, restart to the OS to make sure everything is working correctly.
./fastboot reboot
Now you can go back to flashing TWRP recovery, using the latest release and make sure to power off the device then use the key combinations to restart straight back to recovery.
Personally, once you achieve this point, I strongly recomend doing a back up of the EFS partiton in TWRP. If that partition is corrupted in any future process, you'll need that backup and it's specific to your device.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I used to have the same problem, i.e. twrp disappearing and stock recovery overwriting it.
I did exactly what quizzina did, flashed twrp then entered twrp using volume buttons, flashed SuperSU in order to gain root access, then flashed twrp again and presto...
bare with me here @73 the mind works slow on the learning curve. i ran lsusb with my nex6 set for file trans and adb devices showing the nex. isusb reports it as a nexus 4 not 6. perhaps that is the problem. see below. also which su should i flash?
[email protected]:~$ lsusb
Bus 002 Device 004: ID 03f0:8911 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
Bus 006 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 043: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
dr1445 said:
bare with me here @73 the mind works slow on the learning curve. i ran lsusb with my nex6 set for file trans and adb devices showing the nex. isusb reports it as a nexus 4 not 6. perhaps that is the problem. see below. also which su should i flash?
[email protected]:~$ lsusb
Bus 002 Device 004: ID 03f0:8911 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
Bus 006 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 043: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Click to expand...
Click to collapse
Yes, that appears to be a nexus 4.
The N4 is made by LG where the N6 is made by Motorola. The N4 is 2.7" wide by 5.25" tall. The N6 is 3.25" wide by 6.25" tall.
Edit:
Sorry, I missed the question about rooting. I would recommend getting to the point where the basics are working before worrying about rooting. Yes, you can use that as a way to block stock from overwriting recovery, but you are currently in an indiscriminate state and you really should get things stable before introducing more stuff. On an N6, the steps I've outlined above work every time. It's probably similar on an N4 but the TWRP image your using is wrong, as well as the stock image.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers