When I tried to flash my recovery, I got a lot of "mtd: read error at 0x00000000 (Out of memory)" errors. Problem is, using CM5.0.7-test2, now my phone isn't being recognized via my computer. It charges just fine, but it isn't showing up. (seems to be fairly reoccurring in test2)
Fastboot mode -> "fasboot devices" yields nothing.
Any suggestions, ideas, thoughts?
Neejay said:
When I tried to flash my recovery, I got a lot of "mtd: read error at 0x00000000 (Out of memory)" errors. Problem is, using CM5.0.7-test2, now my phone isn't being recognized via my computer. It charges just fine, but it isn't showing up. (seems to be fairly reoccurring in test2)
Fastboot mode -> "fasboot devices" yields nothing.
Any suggestions, ideas, thoughts?
Click to expand...
Click to collapse
For the device not being recognized, I did a fix_permissions, and a reboot on both my computer and device and that seemed to clear it up. Haven't had a problem since.
Hope that helps
DirectMatrix said:
For the device not being recognized, I did a fix_permissions, and a reboot on both my computer and device and that seemed to clear it up. Haven't had a problem since.
Hope that helps
Click to expand...
Click to collapse
Thanks man, I figured out the fix permissions (fix uid mismatches) via recovery, AFTER I remembered to enter "mount -a" and was able to flash the recovery.
Thanks for at least replying/offering help though!
I tried the fix permissions thing by putting it in the console but that didnt work, what worked for me was that I had to go into the system settings and turn off debugging mode while connected and it worked perfectly.
Related
So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
ldunn said:
So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
Click to expand...
Click to collapse
I had the same problem. I'm not sure how to get ADB back, but I can help you with the MicroSD mount problem. Go into Fastboot on your phone, with it plugged into your computer. In the cmd prompt navigate to the folder where adb devices is and type fastboot oem enableqxdm 0
Let me know if you figure out the adb bit. I'm still trying to fix it.
First let me get the stats out of the way in case it's a compatibility issue (doubtful):
Mytouch 3g 32b
Hboot 1.33.2005
Radio 2.22.23.02
Running on the last cm6 nightly (307, i believe)
Using this kernel: http://droidbasement.com/db-blog/?p=1531
All flashed through recovery.
Ok, so the problem..
Following this guide, http://forum.xda-developers.com/showthread.php?t=532719, I successfully got the ADB to work properly (calling "adb devices" on a terminal returns my device). However when I boot the phone into fastboot, connect it to the PC via USB and call "fastboot devices" through the terminal (yes, I first cd to the android-sdk/tools folder), it returns nothing. Calling something like "fastboot reboot" simply returns "<waiting on device>" indefinitely.
I googled for HOURS last night searching for a solution but to no avail. I uninstalled the drivers via the Device Manager and tried the PDANet method, but nope. Uninstalled drivers again, rebooted everything, and reinstalled using the method posted in the above guide again, pointing it to the google/usb_drivers folder, just in case I had f*'d up somewhere along the way. I just ended up with the same problem. ADB works. Fastboot doesn't. What am I doing wrong? :/
Basically, I'm stumped. While it's not completely necessary to get this working, I'd like to free up some ram on my phone (http://forum.xda-developers.com/showthread.php?t=831139) and for this I need fastboot. I'm not that noobish so I'm willing to experiment. Any help is appreciated.
Nobody? :/
Thanks to my persistence I finally got it working. I'll share in case anyone else has the same problem.
Apparently there were still old HTC related devices under the Device Manager that would not show even when I clicked on "Show hidden devices." I fixed this by adding a new system variable.
Variable name: devmgr_show_nonpresent_devices
Variable value: 1
This allowed me to see a bunch of HTC labeled grayed out devices under 'Disk drives' and under 'Universal Serial Bus controllers,' some grayed out USB Mass Storage Devices and one USB Composite device which I believe was also a culprit. Uninstalled all of them.
I then restarted the process of setting up ADB using these drivers, mediafire.com/?wzdjcmowziw, which I got from the guide I link to in the first post. Then when I hooked up the phone to the PC under fastboot mode, I used the drivers supplied by PDANet. Worked immediately.
Thanks for all the help. (sarcasm)
So I'm trying to install TWRP through ADB, but every time i reboot my phone into bootloader, adb disconnects and my computer does not recognize it. This problem only recently started. I am on the official version of Nougat. Does anyone else have this problem and know a solution? Thanks!
asadabbas95 said:
So I'm trying to install TWRP through ADB, but every time i reboot my phone into bootloader, adb disconnects and my computer does not recognize it. This problem only recently started. I am on the official version of Nougat. Does anyone else have this problem and know a solution? Thanks!
Click to expand...
Click to collapse
ADB is only supposed to work while the phone is loaded into the OS or in sideload mode. In bootloader mode, only fastboot will work.
So the correct command to flash the recovery would be:
Code:
fastboot flash recovery recovery-name.img
Example:
Code:
fastboot flash recovery twrp-3.0.2-1-angler.img
DJBhardwaj said:
ADB is only supposed to work while the phone is loaded into the OS or in sideload mode. In bootloader mode, only fastboot will work.
So the correct command to flash the recovery would be:
Code:
fastboot flash recovery recovery-name.img
Example:
Code:
fastboot flash recovery twrp-3.0.2-1-angler.img
Click to expand...
Click to collapse
sorry my mistake, I meant fastboot. The problem I'm having is that i cannot even enter these commands. It disconnects as soon as it goes into bootloader mode.
asadabbas95 said:
sorry my mistake, I meant fastboot. The problem I'm having is that i cannot even enter these commands. It disconnects as soon as it goes into bootloader mode.
Click to expand...
Click to collapse
Uninstall and then reinstall the drivers by connecting the device. Also, try switching ports.
as weird as it may be, try changing the cable also
I was getting fastboot errors when flashing recovery few days ago, and just by curiosity,I tried with another cable.. it worked with no errors
one more thing.. if you send an adb command to reboot in bootloader, then you have to physically unplug your phone from the computer and plug it back again
only after that, fastboot devices command will show your phone in fastboot mode
ciocu said:
as weird as it may be, try changing the cable also
I was getting fastboot errors when flashing recovery few days ago, and just by curiosity,I tried with another cable.. it worked with no errors
one more thing.. if you send an adb command to reboot in bootloader, then you have to physically unplug your phone from the computer and plug it back again
only after that, fastboot devices command will show your phone in fastboot mode
Click to expand...
Click to collapse
I tried all of this but it still doesn't work. It was working just a few weeks back when i installed nougat, but now it doesn't work. It's so strange. Any other suggestions?
asadabbas95 said:
I tried all of this but it still doesn't work. It was working just a few weeks back when i installed nougat, but now it doesn't work. It's so strange. Any other suggestions?
Click to expand...
Click to collapse
Does charging work fine? And did you try using a different computer? Try charging the phone with that cord that you're using. (even though it's really short, see if it charges steadily)
TnT_ said:
Does charging work fine? And did you try using a different computer? Try charging the phone with that cord that you're using. (even though it's really short, see if it charges steadily)
Click to expand...
Click to collapse
Any other suggestions?
sharmilasingh said:
Any other suggestions?
Click to expand...
Click to collapse
Try updating adb drivers. and make sure you're using data transfer cable, there are many charging cables out there.. those will not read your phone in transfer mode, I've faced this, solved by purchasing new data cable.
Sent from my angler using XDA Labs
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
mobileman88 said:
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
Click to expand...
Click to collapse
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
CyberZeus1977 said:
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
Click to expand...
Click to collapse
Yes, USB debug in development menu, even turning it on/off, revoke does not seem to make it work again. it just does not show up on my PC.
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
mobileman88 said:
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
Click to expand...
Click to collapse
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Shall give it a whirl. Previously it was incorrect driver issue years ago but everything has been working fine on all my Android devices till yesterday when I can't seem to ADB to my 6P. I have the latest USB drivers installed via Android SDK Manager.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Still no go. There's no device at all where I need to change/delete/update driver if I turn on ADB USB mode. Phone is only seen by Windows Device Manager when I turn off USB debugging in developer menu. I still feel it might well be something in the developer menu causing this issue.
I am checking on the folder /data/misc/adb . Permissions is rwxr-s--- . What's the permissions you have for this folder?
Using USBDeview (trying to compare between 2 sets of 6P, both with the December 7.1.1 roms)
6P that works over ADB
Reported VID and PID is 18d1 / 4ee2
6P that does not work over ADB
Reported VID and PID is 18d1 and PID is 4ee1, 4ee5 and 4ee8 depending on which mode (PTP/MTP/MIDI).
Nothing gets reported to be connected at all when I used USBDeview while the 6P that does not connect over ADB USB has USB debugging turned on.
Problem fixed. No idea what was the cause. Hopefully it will help someone else who gets this down the road.
Steps performed
- Clean up SU
- Reboot
- No go
- Reboot to Recovery
- Reflash EFS backup
- Reboot
- No go
- Reboot to recovery
- Clear cache, clear dalvik
- Reboot
- No go
- Reboot to fastboot
- Reflash System, Vendor, Boot
- Reboot
- Works
- Reflash Magisk and PHH
- Still works
Puzzling.
Glad you got it fixed.
v12xke said:
Glad you got it fixed.
Click to expand...
Click to collapse
Yeah, would have done a full factory reset if all else fails since the hardware was indeed able to connect to my PC properly. Glad the various flashing worked out.
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Having the same exact issue here, hope someone has a way to fix it.
sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.
I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.
Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.