Hello.
After googling around for a few hours, I've still not found a solution to my problem.
I have an HTC One M7, unlocked version bought directly from HTC. Some time ago, I wanted Lollipop on my phone, so I installed the GPE Kernel on it.
I think I used this: http://forum.xda-developers.com/htc-one/orig-development/kernel-stock-reset-kernel-m7-gpe-t2963290
That worked fine, but some things didn't work, like FM radio, or the back/home button lights.
Also, it turns out my USB port doesn't work. I'm not sure if it was because of the new kernel, or if it physically broke inside. The phone still charged though.
I wanted to revert back to Sense kernel, so I used http://forum.xda-developers.com/htc-one/development/kernel-stock-reset-kernel-m7-sense-t2957343
I installed TWRP, booted into TWRP, and installed that kernel without backing anything up, foolishly. After everything did its thing, my phone became soft-bricked.
I don't have any other kernel files, nor rom files on my virtual sd card, so I cannot get out of the soft-brick.
It's still running the GPE kernel (because I see the Google logo when the phone boots).
My USB port still doesn't work. I tried three different cables, different USB ports on my computer (including USB 2), a USB-OTG cable: none of those work. (Device manager does not detect any changes.)
Therefore, I can't adb or fastboot into anything.
My phone is unlocked and S-off, btw.
All it seems that I have is the TWRP terminal command and WiFi/cellular connection.
Is there anyone out there who can balance out my foolishness?
Thank you.
Related
Hi guys, hoping someone can help ?
As you see from the title, my HTC One fails to connect to the computer, Here's what ive done to try and remedie the problem.
Removed and clean installed latest HTC Sync and drivers
removed SDK and ADB, updated
rebooted phone
switched on and off
tried several roms
tried 3 different usb cables
tried 5 different usb ports
tried 2 different PC's
My phone sounds like it tries to connect to the pc - with the typical windows noise, then disconnects almost immediaetly, then reconnects then just keeps doing that, my pc comes up with installing drivers, then fails to instal drivers, saying phone not connected, once ive tried this once the phone need to be rebooted before it will attemp to connect to the pc again ---- but fails again
software wise the phone runs perfectly , other than the usb connection problem and charge problem with pc.
The phone charges first time, every time with all my usb cables and htc chargers
im trying to downgrade or reflash hboot 1.55000, just incase this has somehow went corrupt on the usb commands side, but without adb ect it seems almost impossible,
have any of you guys experienced anything like this or could offer solid ideas on how to re-flash hboot from the file located on my phone ???
all help appreciated
running ardh 13.4/22.0, hboot 1.55, cid = supercid, unlocked, s-off
I would simply go back to stock and return via shop in uk - to see if i could get a replacement, but getting there seems impossible - if i can simply get the pc usb problem sorted - all will be fine
dayze0 said:
Hi guys, hoping someone can help ?
As you see from the title, my HTC One fails to connect to the computer, Here's what ive done to try and remedie the problem.
Removed and clean installed latest HTC Sync and drivers
removed SDK and ADB, updated
rebooted phone
switched on and off
tried several roms
tried 3 different usb cables
tried 5 different usb ports
tried 2 different PC's
My phone sounds like it tries to connect to the pc - with the typical windows noise, then disconnects almost immediaetly, then reconnects then just keeps doing that, my pc comes up with installing drivers, then fails to instal drivers, saying phone not connected, once ive tried this once the phone need to be rebooted before it will attemp to connect to the pc again ---- but fails again
software wise the phone runs perfectly , other than the usb connection problem and charge problem with pc.
The phone charges first time, every time with all my usb cables and htc chargers
im trying to downgrade or reflash hboot 1.55000, just incase this has somehow went corrupt on the usb commands side, but without adb ect it seems almost impossible,
have any of you guys experienced anything like this or could offer solid ideas on how to re-flash hboot from the file located on my phone ???
all help appreciated
running ardh 13.4/22.0, hboot 1.55, cid = supercid, unlocked, s-off
I would simply go back to stock and return via shop in uk - to see if i could get a replacement, but getting there seems impossible - if i can simply get the pc usb problem sorted - all will be fine
Click to expand...
Click to collapse
Are the chargers working fine? or are they giving you intermittent charge/no-charge cycles as well? in which case it could be your USB socket is damaged or dirty, try cleaning it with a compressed air tank (or whatever it's called )
Are you also facing the problem in bootloader mode (ie fastboot)?
hmm, will give the usb socket on my phone a clean. Im charging completley fine with chargers and usb cables from mains, when i install htc sync(latest) it installs no problems, then i plug phone into pc, the usb connected appears on phone and then disappears almost imediaetly, the pc sees ive plugged something in and straight away tries to instal drivers - but then comes up with drivers were no installed correctly, also then the phone fails to charge from pc, if i reboot phone - and plug in it will run through the same install cycle again , as described above., basically all drivers fail to install when i plug phone in, its like the phone connects then instantly disconnects.
I ll clean port and post back, could make a difference if a pin has a high resistance contact , thx for info will give it a go
Hey Guys,
you are my last resort of hope as i have given up to fix this problem by myself.
I have an HTC One M7 that i have done a bigger repair on (=new camera, battery, display, backcover). Phone had worked fine so no hardware issues.
After that i decided to set up a new rom to also have a 'clean' system, but after i wiped via TWRP as usual (only data and sdcard...) i accidentally flash an M8 ROM which i had stored on the internal SD card after the wipe.
Of course the installation failed and i was not able to mount my USB-OTG or connect the device by fastboot-USB or ADB. Windows only lists my phone as "Unknown Device".
I am still able to acces TWRP and bootloader, but i cant connect anything to the device to set up a new rom.
Drivers are not the problem in this case, as the HTC One of my friend will enter fastboot-USB and will be found by fastboot just fine. Mine will always show just "Fastboot" and wont be recognized.
After that i have tried several 'fixes' found in other threads, but i think i messed up even harder, as now windows wont recognize anything at all. Also have no luck with linux.
Herei is my data:
*HTC One m7 Unlocked + S-OFF
*CID-02__102
*HBOOT-1.44.0000
*RADIO-4A.14.3250.13 *OpenDSP-v26.120.274.0202
*TWRP 2.8.5.0
*Rom was the lastest Venom Rom
Any idea on how to solve this problem? I run out of ideas and think i am stuck with a bricked phone...
Would be so easy if TWRP would just let me boot my USB
Thanks in advance to everyone willing to give me a hint!
Greetings to you all!
Dont you have a nandroid backup?
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
Hello guys,
Recently I bricked my Oneplus 2 by trying to flash a custom Kernel. That would all be no problem, however my PC doesn't recognize my phone. Tried multiple USB ports (multiple PCs) and got the official oneplus drivers installed, still no connection (tested on Windows and Linux) . That got me believing that my USB port was broken (charging still working), so I replaced the USB module however still not working. (Could it be the cable?)
The current state is that I can boot into recovery (TWRP) and fastboot, however trying to boot normally just shows me the android logo forever.
So well my questions are:
1. What could possible be broken at my phone, that the USB connection is not working. (It worked before)
2. Is there any way to push a rom towards my phone without using a USB connection? So without adb?
Thanks a lot in advance!
EDIT: It was the cable ... I think the data pin broke somehow ... and me stupid as a was replaced the USB module 2 times ... Well transferring CarbonOS right now and will flash real so so thread closed!
I was trying to upgrade from A9 to A10 and phone booted into bootloader. probably because i didn't clear internal memory. but it didn't even let me boot back into twrp recovery, which i upgraded to be compatible with android 10.
i have done all that before and never had problems that my pc didn't recognise the phone. tried on linux, not just windows - same story. tried on different windows machine - again the same. doesn't even show it as unrecognised device under device manager. tried cleaning usb ports, still no difference. even cahnged the battery as i've read somewhere that low battery can cause phone not being recognised.
now i don't know what else to try. could be loose data pins at side usb c port that would cause this?
any help is appreciated
edit: i disassembled the phone and checked all the pins from side port. now i can't say for sure, but it seems like few pins are be shorted to ground. i'm not sure if i accidentally poked with multimeter shielding instead of pin, but i tested few times on continuity and last three pins all beeped on ground. can't really see inside the port that good, but it looks all untouched. could it be that damage is already done when they shorted for the first time or is there any hope?
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
VarDes said:
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
Click to expand...
Click to collapse
ofcourse i used side port. how to switch active slot if i can't access recovery nor connect phone to the pc to boot up twrp?
i updated through twrp with full android 10 zip downloaded from asus