Related
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
Hi xda,
I was unlocking and installing AOKP ROM this week and I've hit a problem that I can't get past. I apologise that this seems like so many other questions already posted, but I haven't found a solution in the threads I've read. I also apologise that I write verbose explanations; I just want to be as clear as possible.
My new TF201 was on ASUS firmware .21 so I used bpear's viperMod/Wolf849-based tool to downgrade to ASUS firmware WW .15.
I then used bpear's tool to root it after downgrading, and then unlocked the bootloader using ASUS' tool. Before anyone asks why I bothered to root if I was going to unlock, I didn't entirely understand what was required to flash a custom ROM on the TP; the process was much simpler on my HTC Desire.
After unlocking the TF201 I used bpear's tool to flash CWM. I downloaded AOKP (aokp_tf201_build-38.zip) and put it on the internal space - I don't have an SD card in it. I rebooted the device into CWM and wiped Dalvik cache, reset factory settings, then went to "Install from zip" and selected the AOKP zip. It ended successfully (i.e: no errors, all messages on the screen appeared normal), so I reboot the device.
And after rebooting it hangs at the splashscreen. I tried to reflash AOKP but there was no change, so I rebooted into the bootloader menu and, without thinking about the consequences, selected to wipe the device. Now I can't reflash AOKP because I wiped the device, and I can't restore a nandroid backup because I didn't take one before flashing AOKP.
I rebooted to the bootloader and selected Fastboot mode while the device was connected to my computer (Windows 7 x64). In Windows, I can see in the taskbar that a device is recognised as "fastboot", and drivers are installed successfully, so I type in the command 'fastboot devices' which simply returns a new line. I reboot into CWM and try to use adb to connect to the device, but there is no device detected in Windows and the command 'adb devices' indicates there is nothing found.
At this point I'm unsure what step to take next. Any tips would be useful.
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
there is no 'adb fastboot' command
@OP, you have to reinstall/point windows again (while in recovery) to the drivers manually. it's the same drivers, yes.
Hi xda,
I got everything sorted a couple of days after this thread was started.
I followed the same procedure described in the OP, with two changes:
1. I swapped AOKP for Virtuous Prime.
2. I installed the Universal Naked Drivers .
My TF201 is functioning very well on Virtuous Prime ROM. I am pleasantly surprised with the battery life but sufficiently annoyed with the wireless that I set up an AP at the other end of the apartment just for the TF201.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
While I was searching for a solution, I read on several sites that it was possible to push files to the tablet while in recovery mode/CWM. An example is this thread. I have to wonder: am I misunderstanding the steps being provided, or is the information being provided is incorrect or incomplete?
With regards to fastboot, I did mention in the OP that fastboot wasn't functional.
Cheers.
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
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