Related
did the RegawMOD root and rebooted phone now its bricked help!!
Define what you mean by "bricked"
Sent from my Android using Tapatalk
rooted phone, fine, restarted and stuck on htc screen pulled battery tried to put in recovery mode and its stuck on htc screen
did u make an ndroid bc if so u can just go back i do it all the time lol
no i didnt know how without root and rom manager wouldnt install
any advice???
is there a way i can still make a back up or am i going to have to unbrick the device?
tom2tone said:
rooted phone, fine, restarted and stuck on htc screen pulled battery tried to put in recovery mode and its stuck on htc screen
Click to expand...
Click to collapse
Well, I can tell you that if it turns on, it's not bricked.
As for a fix, look at oostah's thread : here to find out how to run the RUU via fastboot (.. Should be in that thread)
After you get the ruu to run, you'll be back to stock. Then you can try to root again.
Sent from my Android using Tapatalk
didnt find it
...ok
then read through this thread > here
get the zip in this thread > here
Sent from my Android using Tapatalk
will it erase my contacts cuz i didnt know how to save them???
tom2tone said:
will it erase my contacts cuz i didnt know how to save them???
Click to expand...
Click to collapse
it returns it completely back to stock. so yes, if they're not synced with google.
Sign into your gmail account and view your contacts > located right below the GMAIL icon on the left side. if they were synced then they'll all be there...if they're not then that makes this situation a little more difficult
Do you have adb installed? I'm not particularly familiar with the Regaw rooting tool, so I'm not sure if it's required
Sent from my Android using Tapatalk
no damn it wont even connect to the computer
Did you check to see if your contacts are backed up on google or not?
And you never said if you have adb or not...
Does booting into the bootloader work? VOL DOWN + POWER
As I see it, you have 2 options:
1) regardless of whether your contacts are backed up or not, you can try the RUU zip/fastboot method I posted previously. if it works, you'll at least have a working phone
2) if your phone is new, you can bring it into your service provider (sprint) and see what they can do
**note** with the 2nd option, I'm not sure whether they'll be able to tell if you're rooted/tried to root or not. Someone else would have to chime in for that.
Sent from my Android using Tapatalk
Edit: if you do have adb, you can have your phone connected to the computer and run "adb logcat" to see if it's actually doing something while it's hanging on the HTC screen
no google or adb can you help me do the logcat plz b4 i go back to stock?
Go here for information on how to install/setup adb > LINK
After it's set up, just boot your phone normally, have it connected to your computer and do the "adb logcat" command - just like you'll do "adb devices" on the adb link I gave you.
You'll be able to see if things are loading, or if it's just sitting there doing nothing.
Sent from my Android using Tapatalk
it wont connect my phone to my computer??????
cant get my pc to find phone
tom2tone said:
cant get my pc to find phone
Click to expand...
Click to collapse
:x what OS are you running? arch, ubu, win7, mac, etc.
if its win7 did you get the necessary drivers for it? > LINK/ get the 32bit or 64bit for the machine you have. Then try adb devices again.
Sent from my Android using Tapatalk
the drivers didnt work it still wont find the pc
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Ok, so, I made a bonehead move and flashed a rom that wasn't for the sprint htc one.
was able to get recovery back on the phone by using the command line.
I installed the android sdk and put google usb on there, reinstalled htc sync for those drivers too, still my pc doesnt see the phone, but my phone does show fastboot usb, and I can fastboot reboot the phone. When I goto adb push the zip file, it says error: device not found -- same thing if i try to sideload.
I have the rom, I just cant get it on the phone
fastboot commands work...is there a way to push a file using that (like I did with the twrp file)?
or another way?
thanks!!
DrRJE said:
Ok, so, I made a bonehead move and flashed a rom that wasn't for the sprint htc one.
was able to get recovery back on the phone by using the command line.
I installed the android sdk and put google usb on there, reinstalled htc sync for those drivers too, still my pc doesnt see the phone, but my phone does show fastboot usb, and I can fastboot reboot the phone. When I goto adb push the zip file, it says error: device not found -- same thing if i try to sideload.
I have the rom, I just cant get it on the phone
fastboot commands work...is there a way to push a file using that (like I did with the twrp file)?
or another way?
thanks!!
Click to expand...
Click to collapse
you can't use fastboot to push the file.
how about an OTG cable?
i'll order one just in case -- kinda hoping to get this thing up and running today though. Anything else I should try?
thanks!
DrRJE said:
i'll order one just in case -- kinda hoping to get this thing up and running today though. Anything else I should try?
thanks!
Click to expand...
Click to collapse
If fastboot is working, then so should adb in recovery. Can't really understand why it's not, are you sure you have the correct recovery? maybe check the Sprint forum: http://forum.xda-developers.com/sprint-htc-one
nkk71 said:
If fastboot is working, then so should adb in recovery. Can't really understand why it's not, are you sure you have the correct recovery? maybe check the Sprint forum: http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
I have twrp 2.6.3.0 touch recovery, which appears to be the right one. Its like the phone recognizes that it's connected, but the pc doesnt (tried my mac too)...except that when I go into command line, fastboot commands work fine -- so the pc must see it...and when I plug the phone in, htc sync launches, but then says no device is connected -- so it recognizes the phone enough to launch, but then nada.
i've uninstalled drivers and reinstalled them and they install fine. this sucks
DrRJE said:
I have twrp 2.6.3.0 touch recovery, which appears to be the right one. Its like the phone recognizes that it's connected, but the pc doesnt (tried my mac too)...except that when I go into command line, fastboot commands work fine -- so the pc must see it...and when I plug the phone in, htc sync launches, but then says no device is connected -- so it recognizes the phone enough to launch, but then nada.
i've uninstalled drivers and reinstalled them and they install fine. this sucks
Click to expand...
Click to collapse
do you actually use sync manager? i recommend uninstalling HTC Sync Manager, just keep HTC Drivers.
as far as i know, there are GSM and Sprint variants of TWRP, so you have the Sprint one right?
and remember, fastboot will only work in bootloader/FASTBOOT USB, and adb will only work in a ROM or RECOVERY, it will not work in bootloader.
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
DrRJE said:
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
Click to expand...
Click to collapse
Make sure it's SPRINT compatible!!
Hit the thanks button if I helped
DrRJE said:
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
Click to expand...
Click to collapse
thanks so much. adb push worked -- and have an OTG cable (which i didnt know about) on the way
DrRJE said:
thanks so much. adb push worked -- and have an OTG cable (which i didnt know about) on the way
Click to expand...
Click to collapse
No problem :good:
Would appreciate it if you hit the thanks button though
and also edit the main thread title to include [SOLVED] for others to know
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Have you tried Nexus Root Toolkit? I used that back in January to unlock and root my Nexus 6.
Sent from my Nexus 6 using Tapatalk
xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
Reboot the device. Set switches for USB debug and bootloader unlock. Plug in phone. If don't work there a driver problem. If see your drive on PC don't worry about it. If it sees adb and/or fastboot don't worry about it. Don't use toolkit unless already know how to fastboot. If it screws up you are screwed cause don't know what happened.
xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2948481
For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.
danarama said:
For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.
Click to expand...
Click to collapse
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.
prdog1 said:
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.
Click to expand...
Click to collapse
That's not my point.
I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack
ostap999 said:
I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
The NRT kit should be working! :good:
no luck...
cant figure out what i am not uninstalling...
ostap999 said:
no luck...
cant figure out what i am not uninstalling...
Click to expand...
Click to collapse
I know you said you already did, but uninstall every android driver you find on your PC. Then connect your nexus, while booted to android and let drivers install. Then disconnect, boot your nexus into bootloader, and reconnect again to install fastboot drivers.