I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
djr83 said:
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
Click to expand...
Click to collapse
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Heisenberg420 said:
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Click to expand...
Click to collapse
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
djr83 said:
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
Click to expand...
Click to collapse
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Heisenberg420 said:
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Click to expand...
Click to collapse
Exactly, I'm not getting any devices.
djr83 said:
Exactly, I'm not getting any devices.
Click to expand...
Click to collapse
Have u enabled USB debugging in developer options?
Heisenberg420 said:
Have u enabled USB debugging in developer options?
Click to expand...
Click to collapse
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Edit: Tried another USB port on the computer and it's working now.
djr83 said:
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Click to expand...
Click to collapse
I'd say its the drivers. Try to reinstall
You can try adb over WiFi without the drivers, download an adb wireless app from the market, enable it, get the IP address of your phone in the app, then connect through adb
Adb connect <IP[emoji14]ORT HERE>
then try adb devices
Related
If you have a 2.73+ rom with the latest hboot you will need to follow This Post to boot the recovery image
1) restart into bootloader (switch on holding the back button)
2) Extract the latest GSM Hero recovery IMG into your android SDK/tools folder
(For SDK & CMD help reffer to Post 3 "The Basics" )
3) Download Superuser.zip and extract the contents to your SDK/tools folder.
4) Plug in USB
5) open a CMD prompt from the tools directory and type the following command> fastboot boot recovery-RA-hero-v1.5.2.img
(you should now enter a recovery console on the handset)
NOW PERFORM A NANDROID BACKUP from the recovery menu, once completre, continue..
6)then type the following commands in CMD exactly as they are here, hitting enter for a new line.
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
Congratulations you now have root access..
Download "Root Boot" from the app store (this will only work if you have root!)
Step 6 modified thanks to ENLIGHTENER, cheers, su whitelist working nicely now..
Recovery image updated to recovery-RA-hero-v1.5.2.img , thanks to Amon_RA
Please be carefull! I accept no liability!
FYI, To unroot you will have to either restore an earlier backup or flash a stock rom..... (reccomend the new official HTC Update via RUU to do a full reset)
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
The Basics
gaabrysz said:
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
Click to expand...
Click to collapse
1) you need to download the android software development kit from Here and extract it to yourhard drive.
2) (check) fastboot and adb should be located in the tools folder.
3) in tools right click>new>shortcut when asked enter CMD.exe
4) right click on cmd.exe shortcut, go to properties and clear the "start in" box.
job done, follow as above.
*Edit*
FYI
Verify you have root, go to app store> download Root Booter and test its functions if this works, you have root!
The G2 is the HTC Hero on T-Mobile.
The SDK includes all the drivers needed.
once you have booted the img via fastboot you should enter a recovery console, at this point you need to follow the instructions exactly as typed for adb,
I am running windows 7 Ultimate, should be the same for all windows platforms,
Cheers
__________________
Thank you
Oh and one more question. Do i loose any data doing this??
gaabrysz said:
Thank you
Oh and one more question. Do i loose any data doing this??
Click to expand...
Click to collapse
No, you will not loose anything but be sure to do a Nandroid incase you need to go back to "Stock"
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
Use a program that requires root access.
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
If by G2 you mean HTC Magic/Sapphire rather than HTC Hero you're in the wrong place...
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Just tried it and it works sweet... Took all of 5 minutes... Awesome work thank you
I now have root access on my Hero
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Have you installed the correct drivers? They are located in the SDK folders you downloaded.
If so try entering "adb devices" in the commmand prompt, Just incase the daemon didnt start.
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Having the exact same problem here.
gaabrysz said:
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
Click to expand...
Click to collapse
try entering adb devices see if that makes any differences
btw, when i done mine the phone was in the recovery console..
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Ok so lets clear something. after i type in cmd: fastboot boot cm-hero-recovery.img my phone reboots and goes to recovery console where i have some otions.... so now i have to type in cmd: adb shell, yes??
still nothing and the adb devices didn't help.
Mienaikage said:
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Click to expand...
Click to collapse
Can u share a link to the drivers?? Please
it sounds like a driver issue. Using the lastest SDK?
android-sdk-windows-1.5_r3
OK got it working. It is a driver issue. using latest sdk but i had to use older drivers just like Mienaikage sad.
gaabrysz said:
Can u share a link to the drivers?? Please
Click to expand...
Click to collapse
They came with the SDK I believe, in the android-sdk-windows-1.5_r3\usb_driver\amd64 folder.
If that's not it then it was this one: http://forum.xda-developers.com/showthread.php?t=446274
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2
Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250
no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff
getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3
[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app
pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722
Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250
Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Veid71 said:
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Click to expand...
Click to collapse
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Click to expand...
Click to collapse
I'm not sure either but i can't imagine it'll hurt to try a reboot command or to swap slots
How can this even work? ADB only works when the phone is in fastboot mode, which automatically means that Android isn't even running surely? Hence you can't run apps.
Sent from my Pixel XL using XDA-Developers Legacy app
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
NO
With two phones and adb over network you can send a command to another phone using Tasker (maybe other apps too, only ever used it while looking for an answer to your same question). I know I at least sent reboot from one phone to another... But I think fastboot won't work like this, only (simple) adb shell commands - I'm pretty sure I gave up on it once I realized that I think it is not possible to change boot slots using this method....
Other than that, FlashFire can be used I a rooted phone to change boot slot - wipe dalvik and reboot to other boot slot. I don't know a way on a non rooted phone - anyone know a way without using pc and fastboot?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
For fastboot and adb in recovery, you'll need the phone connected to to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely, but you won't be able to see the phone's screen.
For adb in normal boot, you can either use "adb over network" (LAN) (if WAN, you'll need to bypass firewall if any) or connect your phone to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely. You can see the phone's screen using tools such as AirDroid or TeamViewer.
Ok, I wanted to do a backup in TWRP and suddenly always received error 255. After some.searching I found a solution, but I need to look something up via ADB.
My 5T won't be recognized via ADB. My PC recognizes the phone without problem, USB debugging is on, file transfer is activated and I tried so many drivers (Google, Samsung, OnePlus of course and HTC). No change: when I get into CMD and say "ADB Devices" no devices are shown. Weirdly enough: the phone is recognized in fastboot mode.
Who can help me?
Big thanks in advance!
Download android terminal and type
su
pm remove-user 999
Then boot into twrp and backup
Make sure that u r not using parallel apps
Bradl79 said:
Download android terminal and type
su
pm remove-user 999
Then boot into twrp and backup
Make sure that u r not using parallel apps
Click to expand...
Click to collapse
Thank you very much for your advice. Worked perfectly :good:
But the ADB problem still persists. There is no connection possible via ADB although the PC shows no problem whatsoever to let me send and receive files from the memory etc.
Do u have the universal adb files installed on PC also did u allow the RSA key when it prompted u
Bradl79 said:
Do u have the universal adb files installed on PC also did u allow the RSA key when it prompted u
Click to expand...
Click to collapse
1.) Yes concerning the installation
2.) No because the OnePlus 5T doesn't prompt the RSA key. I did have ADB communication before without allowance of the RSA. I believe this RSA issue is a OnePlus specialty. I had the same issue with 5he OnePlus 5.
Dito13 said:
1.) Yes concerning the installation
2.) No because the OnePlus 5T doesn't prompt the RSA key. I did have ADB communication before without allowance of the RSA. I believe this RSA issue is a OnePlus specialty. I had the same issue with 5he OnePlus 5.
Click to expand...
Click to collapse
Hello Dito13,
I'm having the same issue you had. How did you finally fix it?