Hello,
I have a problem with my device. When ever I try to connect it to the computer I get an error, and it doesn't recognize the device.
The only connection I can achieve is via fastboot. I had to go back to stock RUU and rom because I had a few issues with the last rom. Is it possible to re-root using only fastboot ?
Can I use fastboot somehow to push files to the phone ?
Thanks,
Tom
7omahawk said:
Hello,
I have a problem with my device. When ever I try to connect it to the computer I get an error, and it doesn't recognize the device.
The only connection I can achieve is via fastboot. I had to go back to stock RUU and rom because I had a few issues with the last rom. Is it possible to re-root using only fastboot ?
Can I use fastboot somehow to push files to the phone ?
Thanks,
Tom
Click to expand...
Click to collapse
no, you must use adb to push files.
Code:
adb push <local> <remote>
i.e:
Code:
adb push something.zip /sdcard/
you can use adb from the OS or from custom recovery.
Thanks for the reply, but as I said there isn't any other connection beside the fastboot.
Any other suggestions ?
7omahawk said:
Thanks for the reply, but as I said there isn't any other connection beside the fastboot.
Any other suggestions ?
Click to expand...
Click to collapse
You can use fastboot just for flashing certain partitions of your device (like recovery). As alray suggested, you can push/pull files to/from the device only by using adb, I think your problem is with drivers for your device, which OS are you running on your computer?
Related
So I bricked my HD7 last night as it will stay on the blue logo and not go past that. This is because I tried to flash an OC kernel but i think it didnt play well with kinology, so now i have the stock rooted os on my computer and am in TWRP, but when I try to transfer files via ADB Sideload my computer doesnt recognize adb as a command so any help on this issue would be greatly appreciated.
th3lawmak3r76 said:
So I bricked my HD7 last night as it will stay on the blue logo and not go past that. This is because I tried to flash an OC kernel but i think it didnt play well with kinology, so now i have the stock rooted os on my computer and am in TWRP, but when I try to transfer files via ADB Sideload my computer doesnt recognize adb as a command so any help on this issue would be greatly appreciated.
Click to expand...
Click to collapse
You mean the "adb push" command? Make sure your ADB is working by first entering "adb" and Enter. Then go "adb devices" and Enter, if you see characters, your ADB works.
diripedi not
th3lawmak3r76 said:
So I bricked my HD7 last night as it will stay on the blue logo and not go past that. This is because I tried to flash an OC kernel but i think it didnt play well with kinology, so now i have the stock rooted os on my computer and am in TWRP, but when I try to transfer files via ADB Sideload my computer doesnt recognize adb as a command so any help on this issue would be greatly appreciated.
Click to expand...
Click to collapse
There was someone having the same problem (it was me). The solution was HERE
Moreover: obviously the custom (OC) kernels aren't supporting the stock roms
th3lawmak3r76 said:
So I bricked my HD7 last night as it will stay on the blue logo and not go past that. This is because I tried to flash an OC kernel but i think it didnt play well with kinology, so now i have the stock rooted os on my computer and am in TWRP, but when I try to transfer files via ADB Sideload my computer doesnt recognize adb as a command so any help on this issue would be greatly appreciated.
Click to expand...
Click to collapse
"doesn't recognize adb as a command" sounds like you're not opening your cmd window in the right location (assuming you're on windows). You need to be in the platform-tools directory when running the adb command (or set up the PATH variable correctly...search around for how to do this)
Seems like I updated my driver software and set it to composite I think. I read it fro another post on here somewhere. But it worked for me.
Sent from my Kindle Fire HD 7 using xda app-developers app
hey after trying to flash a rom i needed to use the adb commands to get files to my phone and i said wipe all and there is nothing on my phone even android is not installed i only have my bootloader and recovery any one there can help me please it wont insatll anything keeps rebooting when i get the adb push comand to work and indstalling the rom
Never mind after trying many times i got it to work
feel free to delete this post
Alting900 said:
hey after trying to flash a rom i needed to use the adb commands to get files to my phone and i said wipe all and there is nothing on my phone even android is not installed i only have my bootloader and recovery any one there can help me please it wont insatll anything keeps rebooting when i get the adb push comand to work and indstalling the rom
Never mind after trying many times i got it to work
feel free to delete this post
Click to expand...
Click to collapse
I've been running into this problem as well. I can't seem to use adb sideload or push commands. First off, adb sideload reaches 100% and then nothing happens. (trying to install ARHD ROM) No aroma or anything. Secondly, adb push gives me a protocol failure everytime I try to initiate it.
Any help would be appreciated.
Reflash your recovery, and use adb push command or adb sideload.
Maybe use the hansoon2000's tool if you don't know how to use adb sideload
Ok guys I went to wipe my htc one using twrp and I accidently wiped my internal storage so there nothing on my device to boot up I can get into twrp but I dont have any zips on there to flash I also tried to sideload but adb wont recognize my device which is weird because fastboot works fine I went to bestbuy Walmart radioshack to by an otg cable and try it with flash drive but no one has one so I ordered one from ebay but it will take a week to get it can someone please help with any other sugestions please pleasee I need my phone back
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
SaHiLzZ said:
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
Click to expand...
Click to collapse
What will switching recoverys do?
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Novasunshine said:
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Click to expand...
Click to collapse
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
maxtcee said:
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
Click to expand...
Click to collapse
Try it in recovery and also check to see if the device is being detached while in recovery by typing in "adb devices" in the command prompt.
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
maxtcee said:
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
Click to expand...
Click to collapse
So when you type in "adb devices" while in recovery it shows nothing? No device attached? Also what version of windows are you on?
Yea it shows nothing I'm using windows vista
maxtcee said:
Yea it shows nothing I'm using windows vista
Click to expand...
Click to collapse
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Novasunshine said:
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Click to expand...
Click to collapse
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
Click to expand...
Click to collapse
Takes about 1 - 5 minutes depending on rom size also adb wont say anything till its finished
---------- Post added at 05:21 AM ---------- Previous post was at 05:16 AM ----------
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
Click to expand...
Click to collapse
Your welcome glad its working finally
So today I attempted to install CyanogenMod, and everything was going smoothly right up to when I actually tried to flash the rom. I flashed the international rom instead of the AT&T and after that I was stuck in Team Win Recovery mode. Now every time I turn off and then on my phone, it goes through the htc one screen, then it turns black, and then it goes again in htc one screen but now with the words entering recovery mode in pink letters. I'm not sure if it was me flashing the wrong rom or if it's because it was on android 4.4.
I hope that makes sense.
dreamingrevenge said:
So today I attempted to install CyanogenMod, and everything was going smoothly right up to when I actually tried to flash the rom. I flashed the international rom instead of the AT&T and after that I was stuck in Team Win Recovery mode. Now every time I turn off and then on my phone, it goes through the htc one screen, then it turns black, and then it goes again in htc one screen but now with the words entering recovery mode in pink letters. I'm not sure if it was me flashing the wrong rom or if it's because it was on android 4.4.
I hope that makes sense.
Click to expand...
Click to collapse
so can u access fastboot and recovery ??
raghav kapur said:
so can u access fastboot and recovery ??
Click to expand...
Click to collapse
Yes.
I've tried adb sideload through twrp but I think it never fully "attaches". I tried to push files into the sd but it doesn't seem to work. I think it might be S-On problem, but I can't make the romrunner to work when it's in recovery mode. I can't seem to find a way to make it work, but maybe Im just overlooking something.
dreamingrevenge said:
I've tried adb sideload through twrp but I think it never fully "attaches". I tried to push files into the sd but it doesn't seem to work. I think it might be S-On problem, but I can't make the romrunner to work when it's in recovery mode. I can't seem to find a way to make it work, but maybe Im just overlooking something.
Click to expand...
Click to collapse
Use a USB OTG cable nd put the rom of ur choice into the usb. Flash the rom of ur choice through the /usb otg directory
raghav kapur said:
Use a USB OTG cable nd put the rom of ur choice into the usb. Flash the rom of ur choice through the /usb otg directory
Click to expand...
Click to collapse
You mean put a rom into a usb and then through twrp select it to flash? Can I just flash a stock rom to start over? Will the S-On be a problem?
dreamingrevenge said:
I've tried adb sideload through twrp but I think it never fully "attaches". I tried to push files into the sd but it doesn't seem to work. I think it might be S-On problem, but I can't make the romrunner to work when it's in recovery mode. I can't seem to find a way to make it work, but maybe Im just overlooking something.
Click to expand...
Click to collapse
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
To push you simply put the phone in recovery
then from PC adb / fastboot folder
adb push name-of-rom.zip /sdcard/
again, be sure name-of-rom.zip is in the same folder
clsA said:
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
To push you simply put the phone in recovery
then from PC adb / fastboot folder
adb push name-of-rom.zip /sdcard/
again, be sure name-of-rom.zip is in the same folder
Click to expand...
Click to collapse
Okay so when I sideload on the cmd.exe it shows it's 100% and then my phone turns off. When I turn it on it goes directly to twrp and when i try to install the ROM that i just sideloaded it's nowhere to be found.
dreamingrevenge said:
Okay so when I sideload on the cmd.exe it shows it's 100% and then my phone turns off. When I turn it on it goes directly to twrp and when i try to install the ROM that i just sideloaded it's nowhere to be found.
Click to expand...
Click to collapse
The file will be named sideload.zip in the root of the sdcard
Same thing happened to me a couple of days ago. No ROM on earth would install. I did not make a backup. I just got a new phone. I lost 2 days of sleep reading the complete www and tried everything and nothing worked. If you managed to figure it out please share. Also a weird thing that be as happening was that fastboot would work buy not adb and when I fix permissions it would fail.
Sent from my HTC One using Tapatalk
rbreban said:
Same thing happened to me a couple of days ago. No ROM on earth would install. I did not make a backup. I just got a new phone. I lost 2 days of sleep reading the complete www and tried everything and nothing worked. If you managed to figure it out please share. Also a weird thing that be as happening was that fastboot would work buy not adb and when I fix permissions it would fail.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Well I actually have a backup I just cant seem to make adb work properly. Im going to try usb otg, hopefully it will work with it.
I am in the process of updating the FW on my HTC ONE M7 and trying to install a custom rom. Seeing as i have updated the FW which completely wipes the phone, i have managed to unlock the boot loader and install the latest TWRP recovery image, and now im at the process of trying to push the custom ROM zip file over to the phone via adb.
But adb isnt playing ball and when i type adb push rom.zip /sdcard/rom.zip i get the message error: device not found. I understand that you cannot flash a .zip extension with fastboot, so the only option is to push this custom rom over via adb. I have tried to search for a solution but everything seems to point to enabling USB debugging but i cant do this as there is no working OS on the phone to get into the phone setting, i have tried mounting the SD card inTWRP but it doesnt appear to want to enable this setting either. Does anyone have any suggestions please?
Ah sorted the problem. TWRP has a nice feature called ADB Sideload which worked a treat!
BlockABoots said:
Ah sorted the problem. TWRP has a nice feature called ADB Sideload which worked a treat!
Click to expand...
Click to collapse
how did you do that? im having the same problemas i keep getting no device found error when i try to adb sideload
mystery said:
how did you do that? im having the same problemas i keep getting no device found error when i try to adb sideload
Click to expand...
Click to collapse
install these drivers and reboot your PC and try again
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
This driver can work on X527 leeco?
I have the same issue