I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks. adb wont connect at all even in fastboot.
Miilkman said:
I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks. adb wont connect at all even in fastboot.
Click to expand...
Click to collapse
if you can't get adb working then you need an OTG cable.
Related
OKAY NEED HELP!!! Computer won't recognize phone. Working on a Windows Vista, installed HTC Sync Manager which brought it to where it says that my HTC driver installed when I contact the phone. However won't recognize on computer. Installed ADB drivers but still won't recognize. I need help asap this is my only phone. Installed clcckwork recovery on phone.
have you tried booting into recovery yet ?
1stpravenz said:
OKAY NEED HELP!!! Computer won't recognize phone. Working on a Windows Vista, installed HTC Sync Manager which brought it to where it says that my HTC driver installed when I contact the phone. However won't recognize on computer. Installed ADB drivers but still won't recognize. I need help asap this is my only phone. Installed clcckwork recovery on phone.
Click to expand...
Click to collapse
Try booting in recovery, or download the tool to side load a working rom for your htc one
atlzonly89 said:
Try booting in recovery, or download the tool to side load a working rom for your htc one
Click to expand...
Click to collapse
I have done this 2x, logobricking my tmo HTC One. I think, the first time I deleted the system directory in recovery. Second time was a firmware update and i buggered that as i nuked my system partition and recovery. Both times, sideloading recovery and rom is the only way that I was able to recover. I didn't lose any sdcard files, but it was a PITA to do. The only other way you might be able to do anything is boot to recovery, mounbt sdcard, and let Windows see the mount, push a rom to the card and install in CWM.
Sideloading will work though, read read read and you should be good to go.
I've had the same Rom for a while and I decided I want a new one. I remembered how to do everything from last time so I went and tried flashing the pacman rom. That worked but I unable to flash the boot.img because everytime I am in fastboot usb my computer doesn't see my device. .When ever I am in recovery or just on the phone normally my computer actually reconizes my phone. Some things to note are when I'm in fastboot it says waiting for device,I'm using a different computer then when I first rooted my device, fastboot off, usb debugging on
I could really use some help.
Thanks in advance!
Pokoloko4 said:
I've had the same Rom for a while and I decided I want a new one. I remembered how to do everything from last time so I went and tried flashing the pacman rom. That worked but I unable to flash the boot.img because everytime I am in fastboot usb my computer doesn't see my device. .When ever I am in recovery or just on the phone normally my computer actually reconizes my phone. Some things to note are when I'm in fastboot it says waiting for device,I'm using a different computer then when I first rooted my device, fastboot off, usb debugging on
I could really use some help.
Thanks in advance!
Click to expand...
Click to collapse
You could use flash image GUI from the play store to flash the boot IMG.
Sent from my EVO using XDA Premium 4 mobile app
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145
Hi guys,
So I installed TWPR recovery, but now im looking to get my device back to stock or at least to Android M.
But in Fastboot devices it shows "???????????????? Fastboot"
I cannot push the stock recovery it just hangs. Does nothing.
If I boot the tablet it shows adb devices correctly.
Is there any way I can fix this so that I can reflash my device back to stock?
It is still Unlocked, but just cant get fastboot to work.
Bump anyone?
Fastboot displays that when you don't have enough permission to access the device. Try again, but as root.
Thanks for the reply, but could you help me with how to try again as Root?
Thanks
they mean you need to run the fastboot command as root from your pc.
Im running on Windows, and ran fastboot with Admin rights...
Can anyone help me further?
Im only stuck with this ???????????????? in fastboot devices.
In android if I run ADB Devices it shows correctly:
And I can run adb commands and they work, its literally just fastboot.
I would like to remove TWRP and go back to stock bootloader.
I can tell you I had the exact same problem as you. I tried every goddamn piece of advice I found on Google. After about a week, you know how I fixed it? I tried other USB ports on my laptop. It worked on only the USB2.0 ports. The USB3.0 port I tried it on it came up as all ????????????
Dang thanks for the reply.
My issue is my laptop doesnt have USB 2 on it at all
SavellM said:
Dang thanks for the reply.
My issue is my laptop doesnt have USB 2 on it at all
Click to expand...
Click to collapse
Try your other USB 3.0 ports. I only have one on this laptop. Maybe my 3.0 port is borked? You never know until you try
When I "Swipe to wipe" in twrp, twrp instantly resets.
I can not swipe to wipe.
I successfully had rooted access and twrp installed with Slimroms on Nexus 9 running correctly.
I Tried to install an 8.0 Oreo rom but it crashes and resets on the google screen.
when i try to return to old roms I get "Error 7" in Twrp.
and I can no longer swipe to wipe or factory reset.
Anyone know how to fix this issue so I can return to 7.1.2 SlimRoms?
the nexus 9 no longer shows up in windows or under ADB Devices.
So i cant access adb functions.
did my bootloader have a problem?
it seems twrp is crashing when its trying to format or wipe mounts ?
Have you tried flashing the latest firmware from Google with fastboot? That's where I would start.
Sent from my SM-T820 using XDA-Developers Legacy app
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
RecIV said:
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
Click to expand...
Click to collapse
No, can't do it in TWRP. If you're having trouble, try wugfresh toolkit. It's no longer updated but you can use it to flash a factory image that you download yourself. Toolkit might help with your issue of not being recognized by your PC.
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
RecIV said:
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
Click to expand...
Click to collapse
I've had to do it few times to get it to recognize device. That's the only reason I suggested wugs. It has quick options to retry driver install. But manually is better of course. Windows 10 gave me a heck of a time with driver's.