After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?
Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache
nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!
Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?
Any other ideas to get communication to the phone?
Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.
Related
hi everyone
last week i flashed a KK rom, and i saw in recovery "can't access internal sorage" when i wanted to backup the rom. BUT i could download and flash other roms from the phone.plus, fastboot was not showing anymore "fastboot usb" but "fastboot ac" only, and my PC shows "unknown device" and doesnt see the phone.
i downloaded another rom, and to install it, i wiped data, cache, dalvik, and BY MISTAKE i wiped "internal storage".
and the result is.....: no rom inside the phone, i can't boot because i wiped system, i am still "fastboot ac", so i can't use adb commands....
i tried several cables, computers, tried to reinstall drivers etc....
my one is unusable ::// ....if some experts have an idea, i'd be fan
THANX!!!
i'm s-off
super CID
H Boot 1.56
KK firmware
durbangs said:
hi everyone
last week i flashed a KK rom, and i saw in recovery "can't access internal sorage" when i wanted to backup the rom. BUT i could download and flash other roms from the phone.plus, fastboot was not showing anymore "fastboot usb" but "fastboot ac" only, and my PC shows "unknown device" and doesnt see the phone.
i downloaded another rom, and to install it, i wiped data, cache, dalvik, and BY MISTAKE i wiped "internal storage".
and the result is.....: no rom inside the phone, i can't boot because i wiped system, i am still "fastboot ac", so i can't use adb commands....
i tried several cables, computers, tried to reinstall drivers etc....
my one is unusable ::// ....if some experts have an idea, i'd be fan
THANX!!!
i'm s-off
super CID
H Boot 1.56
KK firmware
Click to expand...
Click to collapse
download the latest HTC Drivers and TWRP recovery , rename the recovery file to "twrp.img"
connect your device, remove the previous drivers from Device Manager
disconnect your device
reboot your PC
install the latest drivers, don't let Windows to install your drivers from the Internet
go into bootloader and connect your device
flash the recovery using fastboot method:
"fastboot flash recovery twrp.img"
"fastboot erase cache"
reboot into recovery and try side loading your ROM
Sent from my HTC One using Tapatalk
kamilmirza said:
download the latest HTC Drivers and TWRP recovery , rename the recovery file to "twrp.img"
connect your device, remove the previous drivers from Device Manager
disconnect your device
reboot your PC
install the latest drivers, don't let Windows to install your drivers from the Internet
go into bootloader and connect your device
flash the recovery using fastboot method:
"fastboot flash recovery twrp.img"
"fastboot erase cache"
reboot into recovery and try side loading your ROM
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
thanx for the reply!
i managed to reflash twrp+erase cache
but every time i go into recovery, the phone is not recognized anymore by the PC and ADB....
iam now in "fastboot usb" mode, even if the computer doesn't recognize it as a "hard drive"
durbangs said:
thanx for the reply!
i managed to reflash twrp+erase cache
but every time i go into recovery, the phone is not recognized anymore by the PC and ADB....
iam now in "fastboot usb" mode, even if the computer doesn't recognize it as a "hard drive"
Click to expand...
Click to collapse
LOL
dude when your phone is in fastboot mode or in recovery, you will not see your device hard drive in My Computer
which drivers are you using?
did you followed my instructions?
kamilmirza said:
LOL
dude when your phone is in fastboot mode or in recovery, you will not see your device hard drive in My Computer
which drivers are you using?
did you followed my instructions?
Click to expand...
Click to collapse
sorry for the mistake, i meant when i enter recovery, i hear the sound that means the phone is disconnected, and unknown in my device manager.
i downloaded the latest htc manager (i'm on win7)
durbangs said:
sorry for the mistake, i meant when i enter recovery, i hear the sound that means the phone is disconnected, and unknown in my device manager.
i downloaded the latest htc manager (i'm on win7)
Click to expand...
Click to collapse
remove any previous drivers from Device Manager, like i mentioned in previous post
and uninstall HTC Sync Manager
restart your PC
download and install these drivers: http://www.mediafire.com/download/e21a0cc4268dg9d/HTCDriver_4.10.0.001.msi
kamilmirza said:
remove any previous drivers from Device Manager, like i mentioned in previous post
and uninstall HTC Sync Manager
restart your PC
download and install these drivers: http://www.mediafire.com/download/e21a0cc4268dg9d/HTCDriver_4.10.0.001.msi
Click to expand...
Click to collapse
well, thanx again for the answer
my htc is recognized in device manager with those drivers
but i have the same problem: when i press bootloader, my device disconnect, and i can't adb sideload....
durbangs said:
well, thanx again for the answer
my htc is recognized in device manager with those drivers
but i have the same problem: when i press bootloader, my device disconnect, and i can't adb sideload....
Click to expand...
Click to collapse
i have 2.0 usb and 3.0 usb on my pc. when i connect the phone in fastboot mode on my 3.0 port, it says "htc drivers installed" but when i click on bootloader, adb is not working. and when i'm on my 2.0 usb port, in bootloader, my pc says "driver install failed" (and i see "unknown device" in device manager), and theres noway to update it
//
i removed the google usb drivers rev8 from the android sdk. maybe i was wrong?
durbangs said:
i removed the google usb drivers rev8 from the android sdk. maybe i was wrong?
Click to expand...
Click to collapse
adb will only see your phone in recovery or in a booted phone fastboot will see your phone in fastbootusb mode when you are in just bootloader it wont see it to usb sideload you need to be booted into recovery
---------- Post added at 03:27 PM ---------- Previous post was at 03:22 PM ----------
here is a guide that should help you
http://forum.xda-developers.com/showthread.php?t=2318497
jerrycoffman45 said:
adb will only see your phone in recovery or in a booted phone fastboot will see your phone in fastbootusb mode when you are in just bootloader it wont see it to usb sideload you need to be booted into recovery
Click to expand...
Click to collapse
that's what is weirdo, my phone just see fastboot in fastboot usb. but nowhere else...FTW
durbangs said:
that's what is weirdo, my phone just see fastboot in fastboot usb. but nowhere else...FTW
Click to expand...
Click to collapse
when you plug your phone into your computer while your phone is on the bootloader screen fastboot does not change to fastbootusb
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
what version of hboot do you have and what operating system is on your computer
jerrycoffman45 said:
when you plug your phone into your computer while your phone is on the bootloader screen fastboot does not change to fastbootusb
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
what version of hboot do you have and what operating system is on your computer
Click to expand...
Click to collapse
no it does not. it does disconnect from pc when i go from fastboot to bootloader, to enter recovery
i'm on 1.56 HBOOT
S-OFF
last TWRP
CID 11111111
thanx!
durbangs said:
no it does not. it does disconnect from pc when i go from fastboot to bootloader, to enter recovery
i'm on 1.56 HBOOT
S-OFF
last TWRP
CID 11111111
thanx!
Click to expand...
Click to collapse
only thing I can think off is it is a driver problem try different cables and usb ports
jerrycoffman45 said:
only thing I can think off is it is a driver problem try different cables and usb ports
Click to expand...
Click to collapse
i'm worried about something: i flashed a KK rom, that i downloaded in my htc one, and after i installed it and wanted to store the backup of the rom in twrp, it said "no storage available". when i came back home, my phone was not recognized by my pc, whereas it was before.
thats where it comes from i think.
i'm a heavy flasher since i had the nexus one!
durbangs said:
i'm worried about something: i flashed a KK rom, that i downloaded in my htc one, and after i installed it and wanted to store the backup of the rom in twrp, it said "no storage available". when i came back home, my phone was not recognized by my pc, whereas it was before.
thats where it comes from i think.
i'm a heavy flasher since i had the nexus one!
Click to expand...
Click to collapse
could be have you tried on anouther computer to see if it see,s your phone only time I have had this happen was with a older hboot and wn8.1 hopefully @nkk71 will show up and help
jerrycoffman45 said:
could be have you tried on anouther computer to see if it see,s your phone only time I have had this happen was with a older hboot and wn8.1 hopefully @nkk71 will show up and help
Click to expand...
Click to collapse
thank you sir, i'll try this in a few minutes
jerrycoffman45 said:
could be have you tried on anouther computer to see if it see,s your phone only time I have had this happen was with a older hboot and wn8.1 hopefully @nkk71 will show up and help
Click to expand...
Click to collapse
hey jerry, how's everything in 2014
i'm off in a few minutes, so can i get a brief summary, in particular: OS: Win7, Win8, 8.1? Ubuntu?
nkk71 said:
hey jerry, how's everything in 2014
i'm off in a few minutes, so can i get a brief summary, in particular: OS: Win7, Win8, 8.1? Ubuntu?
Click to expand...
Click to collapse
cold 10 degrees f. here freezing are butts off hope all is good with you
jerrycoffman45 said:
cold 10 degrees f. here freezing are butts off hope all is good with you
Click to expand...
Click to collapse
pretty cold here too 13C (at night).... feels like close to 0~3 in most other countries for me
hi everyone,
i am having a really bad day.
I had incredible s stock 4.0.4 installed, unlocked, s-on, hboot 2.002
I've tried to download the latest 4.4.2 rom i found in the forum, the device showed the update is completed, then the device restarted and froze on HTC screen.
I've tried to install other roms and it didn't work as well, moreover, the device can not be detected by pc without a reason.
I've cleared all caches by the way.. any one can help !
install this Hboot
[/COLOR]http://forum.xda-developers.com/showthread.php?t=1270589
OR
flash boot manual
what if my USB slot is broken into my pc, can i do this using an SD card?
micho119 said:
what if my USB slot is broken into my pc, can i do this using an SD card?
Click to expand...
Click to collapse
No.
072665995 said:
No.
Click to expand...
Click to collapse
Since you are telling device is not detected in PC,
I can safely assume that you are not flashing boot.img through fastboot from PC.
If you are S-ON, you need to flash boot.img file of ROM you want to install through fastboot command...
fastboot flash boot boot.img
google it for more info.
And connect your phone, go to fastboot mode and check with command
fastboot devices
your device should be listed in fastboot mode
and if still not detecting by PC, then must be driver issue and it should have nothing to do with phone.
RmatriX1218 said:
Since you are telling device is not detected in PC,
I can safely assume that you are not flashing boot.img through fastboot from PC.
If you are S-ON, you need to flash boot.img file of ROM you want to install through fastboot command...
fastboot flash boot boot.img
google it for more info.
And connect your phone, go to fastboot mode and check with command
fastboot devices
your device should be listed in fastboot mode
and if still not detecting by PC, then must be driver issue and it should have nothing to do with phone.
Click to expand...
Click to collapse
I just reread his post. Then reread yours. And I realized that the other guy's post doesn't really make much sense. I don't know if he is saying if his computer's USB port is broken. If so then use another one. Then I could also read it as His phone's USB port is broken, and in that case, he really is out of luck.
072665995 said:
I just reread his post. Then reread yours. And I realized that the other guy's post doesn't really make much sense. I don't know if he is saying if his computer's USB port is broken. If so then use another one. Then I could also read it as His phone's USB port is broken, and in that case, he really is out of luck.
Click to expand...
Click to collapse
Hey, lt's lot of guess work here and we need to hear from actual victim...
but let me put my basis..
from 1st post, I can assume that he doesn't know of fact that he need to flash boot image through fastboot.
Hence, I believe that he may even doesn't know what if fastboot.
And without any ROM installed, device can only be detected in fastboot.
So, I strongly believe, he need to try to detect device in fastboot mode and very less chances USB is broken.
Now lets wait to hear from OP guy.
in htc sunsation 4ext recovery there is a way to flash boot.img
try it :
1- go to 4ext recovery
2- select Tools
3- the last one is ( enable smart flash)>> click it once then flash ROM
I don't know if our 4ext recovery support this feature or not
yep. because this is development and all that.
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?
Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2
lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.
Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.
Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.
lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.
I was on my phone and an app closed. Then it closed again when I tried to re-open it. Third time's the charm, it closed again and then google services stopped. Then my phone shut off. I wouldn't turn on, so I had to do the power button+volume down to get into the bootloader menu. I tried to boot up and was stuck with a bootloop. I downloaded a factory image and the latest android sdk.
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
melgibson666 said:
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
Click to expand...
Click to collapse
My idea is that the bootloader is locked.
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
NLBeev said:
My idea is that the bootloader is locked.
Click to expand...
Click to collapse
It is not.
danarama said:
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
melgibson666 said:
It is not.
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
Click to expand...
Click to collapse
Please screenshot the error.
melgibson666 said:
. . .Bootloader unlocked
. . .reinstalled the drivers to be sure,
. . .used the original USB cable. . .
. . .tried 3 different USB ports . . .
. . .fastboot detected the device.
Still not working.
Click to expand...
Click to collapse
The quotes from you posts gave me the impression that the hardware is OK.
Probably the drivers on your PC are also OK.
I assume the command 'fastboot devices' responded a device ID.
Other issues could be:
- the dosbox and fastboot commands on the PC are not started as administrator;
- the driver on the pc is an adb-driver and not an adb combined driver;
- the version of fastboot is obsolete;
- images flashed before were corrupt;
Possible actions:
Make sure the fastboot and also adb files including the dll's are up to date.
Check if the command 'adb devices' works.
Try to adb sideload a (stock) rom.
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon