i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Asilns said:
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Click to expand...
Click to collapse
adb only works within android since it's a debugger if I'm not mistaken. Try using fastboot to flash the system images of the stock rom back to their respective partitions. (ie. fastboot flash system system.img; fastboot flash boot boot.img; etc.)
You must be unlocked for that to work however.
problem solved
after almost 10 hours of research the solution was really easy.
1.download "recovery-RA-nexus-v1.6.2.img" and fastboot it using this commend:
fastboot-windows flash recovery recovery-RA-nexus-v1.6.2.img
2.flash a rom from SD card and everything should work fine
Hi i want to install clockworkmod recovery in my is from adb but when i type in cmd the commands fast boot etc it says that this commands are not valid...The other adb commands such as adb device works perfectly .Why this happens?please heelpp
Anoubis282 said:
Hi i want to install clockworkmod recovery in my is from adb but when i type in cmd the commands fast boot etc it says that this commands are not valid...The other adb commands such as adb device works perfectly .Why this happens?please heelpp
Click to expand...
Click to collapse
Do you have the fastboot.exe in the same directory as adb.exe?
Hello
I have done all many researches in forum, and made sure all of below are done but just can't get adb working on my device in fastboot mode...
- Installed USB driver
- Debugging mode is on
- Not using 3.0 USB port
- Using Win 7 64 bits
Fastboot is working fine but adb can't find my device at all. It shows blank list after I typed "adb devices"
Funny thing is when I boot into TWRP recovery and use the adb sideload function, adb can find my device correctly!
Anyone got a clue what's happening on my One? I really want to make adb works so I can make it s-off.
Thanks.
adb doesn't work in fastboot mode.
BenPope said:
adb doesn't work in fastboot mode.
Click to expand...
Click to collapse
Thanks and sorry for my noobiness.
I always think I need to boot into fastboot mode for adb.
:fingers-crossed:
try an custom recovery witch support adb like teawin
I use TWRP for ADB. TWRP > Advanced > ADB Sideload.
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
adb sideload
b0gd4n said:
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
Click to expand...
Click to collapse
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
rpmccormick said:
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
Click to expand...
Click to collapse
clsA said:
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
Click to expand...
Click to collapse
BenPope said:
adb sideload
Click to expand...
Click to collapse
thank you all!!!
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
b0gd4n said:
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
Click to expand...
Click to collapse
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
b0gd4n said:
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
Click to expand...
Click to collapse
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
b0gd4n said:
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
Click to expand...
Click to collapse
yup.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
Same Problem here. No Solution?
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
BlockABoots said:
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
Click to expand...
Click to collapse
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
b0gd4n said:
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
Click to expand...
Click to collapse
Hmmm, maybe try uninstalling all HTC drivers on the PC and then reinstalling.....
HTCDriver_4.2.0.001.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi (or x86 version if on win 32)
SyncManager_2.0.61.0.exe
found here, http://forum.xda-developers.com/showthread.php?t=2217396
http://www.mediafire.com/?o10b16j5b3r3o
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
I deleted os
Hello brother pls help me . I am sorry but i deleted is of htc one. Now can't anything . Here is the details
Twrp - yes
Hboot- unlocked tampered.
S-off
T-mobile htc one 4.4.2
Please help me . Here I saw many many expert so brother pls help me how to solve it & I can use my htc one .
Pls brother........
If someone can mail me in [email protected]
The details what to do. As I am really new & don't know what to do.
So again brother pls help.
windieboss said:
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
Click to expand...
Click to collapse
Whooo this worked!! Finally!!!
So I uninstalled all HTC stuff I had installed (drivers, sync manager, everything), then installed the stuff in the link.
Plugged in the HTC One in sideload mode and did
Code:
adb sideload filename.zip
and it worked!! Thanks again mate!
Someone please.help...
tott2003 said:
Someone please.help...
Click to expand...
Click to collapse
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use . before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with . in the beginning.
Click to expand...
Click to collapse
Cheers mate ?
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Click to expand...
Click to collapse
HOLY. ****ING. ****.
I have spent the past two days trying to figure this out. Not *one* other person on the internet, so much as I have seen, has mentioned using the side port. Seriously, you just made my day. Thank you so much! :good:
Created a new topic, disregard