Hi all im trying to get adb setup with my Evo 3D (came here as a noob the other day but its all really simple compared to other phones i've done)
anyhow this is the first time i've tried using adb and it just refuses to work, as many of the rom devs say when you install the firmware for the rom you reboot into recovery by either reboot and pull sd card then enter bootloader (works fine OFC) or use adb via
Code:
adb reboot recovery
but it just says error: device not found, fastboot works fine via usb, i can reboot bootloader fine just stuck for answers as to why adb isn't
EDIT: Nevermind i worked it out now lol adb doesn't work VIA bootloader lol! ADMIN PLEASE REMOVE
Related
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I'm in the middle of restoring an HTC One M7 Sprint phone to stock from CM11. Since I don't have S-Off, I tried using the minimal package from HTC1Guru, the Reset Download. I have TWRP Recovery, so I copied the Reset Download utility to the phone and ran it. That went ok, except the screen was unresponsive and I had to use a mouse. So, I tried to get an OTA (after relocking the bootloader) to get all current stock. A few minutes into the install of the OTA, it just locked up and there I sat, with the White HTC screen and nothing happening.
So I've tried several things. But a side effect of this condition is I could NOT run ADB. Now I do have a USB connection and it works; In Fastboot if I issue the FASTBOOT DEVICES command I get the device id back. But I could not get ADB to work at all, even though the cable is connected and all that (since Fastboot works). Oh, and ADB worked before this locked up. ADB Devices returns no devices. BUT (it gets weirder) I went back to Fastboot and flashed TWRP REcovery again, and if I enter RECOVERY, I can issue ADB Commands from recovery fine. But outside of recovery, I can't. And, more importantly, PROGRAMS CAN'T DETECT ADB. I tried Rumrunner's program to turn S-OFF, and I tried the ARUWizard RUU utility from Viperboy, and both said to check the USB cable, that ADB could not be found. But I went right to it, booted recovery, and there was ADB!
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen? since right now I can boot to REcovery but not to the ROM, I'm totally dead in the water.
Steve
Steve Thomas said:
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen?
Click to expand...
Click to collapse
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
_that said:
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
Click to expand...
Click to collapse
I thought I must be doing something wrong running ADB with the phone in Recovery since Rumrunner keeps failing with "No ADB Connection". But maybe it's something else.
Thanks!
Hello, I have unlocked bootloader and twrp installed. I used before a custom room from miui forums and it worked well but i wanted to try a new one so i wiped everything on the phone and tried to put the rom via adb sideload but it always fail at some point.
I can't adb push either because adb devices doesn't show my phone.
The last time adb push worked for me and my pc always recognized the phone before so I don't know why is not working this time...
Any ideas? Thank you!!
PS: Yesterday i could transfer the rom via adb push (adb devices showed recovery) but the install failed so today i wanted to try a new one but I just can't...
Windows Device Administrator shows the phone connected as Google Nexus ADB interface.
Ok, i made it.
I mounted only data on TWRP and then ADB devices recognized the phone.
I don't know if i can close the post!
Hey i have LG g2 mini (d620r) and fastoot cant see my phone but adb can. when i try to reboot through adb (i used adb reboot bootloader, adb reboot bootloader ,and even tried adb sideload) but it wont work. it just simply restarts. tried patched bootloader but still nothing goes.
The g2m does not support fastboot.
Just follow the instructions in the thread you want to flash.