Related
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Did you try mass storage or pc mode?
I had that issue with my USB cable. I used the one with my device and it didn't come up. I went grab another USB cable in the house and it worked.
yeah, tried them. Didn't mention that cause if I understand correctly, it should be in charge only.
thanks for the help!
I hope you figure something out good luck
Edit: have you tried running command prompt as administrator?
yeah. same result.
I read in another thread that you were required to us the cable that came with the phone for it to be detected. But also, I used a BlackBerry branded cable to do it on mine, and it worked.
come to think of it, i think i used a blackberry cable to root my first d3. will give it a shot and report back.
why the heck would it matter what cable you use? Though it doesn't make sense to me, it appears that the cable is indeed important.
SrulDog said:
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Click to expand...
Click to collapse
Download the USB and Charging Drivers off of Motorolas website, make sure your phone connects to USB mass storage after you do this, then switch to charging mode.
It took a blackberry cable *and* reinstall of the moto drivers, but im up and running and rooted. now, to figure out how to get my other d3 to stop bootlooping...
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
I had to use the cord that came with my phone. For some reason Motorola is bad about not using standards. For example there was an old 355 flip phone that is a Motorola I used to have and it wouldn't charge with anything but a Moto charger. It may be the same port but not the same compatibility. Thankfully it will accept a charge from any microUSB source.
Sent from my DROID3 using XDA App
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
LaZiODROID said:
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
Click to expand...
Click to collapse
yeah, to fiddle w/ any rooting, you need to have debug on
digitalsynner85 said:
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
Click to expand...
Click to collapse
Yeah, I was able to flash the SBF. It was really exhausted and couldn't figure it out when I originally posted, but after a nights sleep, I was able to do it just fine.
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
SrulDog said:
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
Click to expand...
Click to collapse
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
digitalsynner85 said:
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
Click to expand...
Click to collapse
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
SrulDog said:
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
Click to expand...
Click to collapse
oh ok, you said you couldn't get past the phone activation screen, i thought you were saying that your radio got botched in the process somehow lol, my bad
SrulDog said:
Now I want to know if the phone is still rooted or not. .
Click to expand...
Click to collapse
if you used rsd to sbf you are no longer rooted.
I have the International non-developer version and it came with the stock ROM with Sense 5. I rooted it and installed Google's 4.2.2 stock ROM, but when the 4.3 version came out I updated it via OTA (I know I shouldn't have done that, but I guess what's done is done). After the update, whenever I plug in my phone it still shows up but when I open it there's nothing in it no matter how many times I refresh it. Also, when I try to use Nandroid Manager it says that my phone is not rooted.
Now I also can't use adb and fastboot as they both say there is no phone plugged in when it is actually plugged in. How do I solve this? Any help would be appreciated
Btw, I have the drivers for the phone installed along with HTC Sync Manager.
Enable the USB debugging in the Developer settings > that enables ADB
I assume you know, that you need to tap on the build number 7 times to let the developer menu pop up
Since 4.3 there is multiuser, you must move your data with a file manager from data/user to data/user/0
davebugyi said:
Enable the USB debugging in the Developer settings > that enables ADB
I assume you know, that you need to tap on the build number 7 times to let the developer menu pop up
Since 4.3 there is multiuser, you must move your data with a file manager from data/user to data/user/0
Click to expand...
Click to collapse
Well I didn't know about the developer menu thing ._. I thought there was no developer settings for the ROM.
Anyway, I did what you said but adb/fastboot still can't detect it.
ickytc said:
Well I didn't know about the developer menu thing ._. I thought there was no developer settings for the ROM.
Anyway, I did what you said but adb/fastboot still can't detect it.
Click to expand...
Click to collapse
That is strange...
It wont recognize from fastboot either?
davebugyi said:
That is strange...
It wont recognize from fastboot either?
Click to expand...
Click to collapse
Exactly ._. Anyway to solve this?
Could it be due to different pc configuration or a faulty cable ?
I myself have a couple knock-off cables with them i usually have
To remove and resert a couple times before a big file gets transfered
alay_ said:
Could it be due to different pc configuration or a faulty cable ?
I myself have a couple knock-off cables with them i usually have
To remove and resert a couple times before a big file gets transfered
Click to expand...
Click to collapse
I've tried multiple devices and cables.
ickytc said:
I've tried multiple devices and cables.
Click to expand...
Click to collapse
If that case try a different pc / laptop, then ull at leadt be sure whether its the pc/ laptop or the mobile device which is causing troubles ...
alay_ said:
If that case try a different pc / laptop, then ull at leadt be sure whether its the pc/ laptop or the mobile device which is causing troubles ...
Click to expand...
Click to collapse
I meant to say I tried different PCs
Okay now fastboot detects the phone but adb still doesn't detect it. Help anyone?
Try flashing a new recovery. fastboot flash recovery recovery.img
Sent from my HTC One using Tapatalk
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
The phone has to be booted into the os for adb to work. Fastboot only until you get a rom flashed.
Sent from my HTC One using Tapatalk
Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
lumogox said:
Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
Click to expand...
Click to collapse
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Click to expand...
Click to collapse
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
My HTC showed the same message. Saying it can not charge into host mode.
HTC only charges powered off.
ferincr said:
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
Click to expand...
Click to collapse
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
lumogox said:
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
Click to expand...
Click to collapse
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Steps 8-15 of my guide show how to set up adb/fastboot in Ubuntu 32bit and to check if your device is recognized. You don't have to install Ubuntu just select to try it. I think that's what scares everyone off, is thinking they have to install the OS...It seems like a lot of work but it really isn't and compared to what you've gone through, it can't hurt....good luck
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
nkk71 said:
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
Click to expand...
Click to collapse
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
lumogox said:
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
Click to expand...
Click to collapse
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
I really haven't explored what steps are needed to get it back to stock, but mine connects to the pc as long as it's in bootloader so I can flash stuff like Fw but nothing that need to get into the sd card. (as far as I know).
nkk71 said:
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
Click to expand...
Click to collapse
Well, it's says nothing... doesn't appear anymore on Win 7 devices.
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
n1234d said:
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm thinking this a port issue, is damage somehow, however, I hope to find a software solution.
New Firmware
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Loading New Firmware
Also, for some reason, computer would not recognize phone with TWRP recovery yet I could push files through adb when using CWM recovery. So what happened for me was loading up CWM and pushing the files that I needed into the data folder and flashing TWRP to then install it or rebooting the phone as normal and finding the file with something like a root file explorer. I feel like I may not be very clear with this so post if there needs to be more clarification.
it's a strange issue ,i think it is a hardware problem,happen to me and i try everything possible,without success,than i charge phone when power of and it was the only way ,but led was flashing so it was intermittent charging,i was able to charge only to 97%..i use my phone and somehow next day i was able to charge phone,but then problem occur again...and wired thing is that fastboot devices list is not empty but adb devices list is empty,so phone is not fully recognized by computer,and i forgot to say that day when i was able to charge phone,adb command worked...that day i flashed firmware recovery and rom again ,because i thought it will resolve the problem...
---------- Post added at 11:35 PM ---------- Previous post was at 11:23 PM ----------
ricehoshi said:
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Click to expand...
Click to collapse
And do have same problem again after flashing new firmware?
The phone was a gift for my dad and it has been running fine since my last post. No charging issues and the phone does not go into host mode randomly anymore.
Well i also had the same problem...but i did factory reset on the phone and flashed it to completly stock ...and since then no problem..
Sent from my HTC One using XDA Free mobile app
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.
Okay so I am well aware that there are hundreds upon hundreds of articles in different Threads Online about a similar issue. That being pretty much what the title says... " USB device has malfunctioned", "USB device not recognized", "device descriptor has failed (43)" and, in Linux, "unable to enumerate USB device" and then it gives readers at different numbers every time I unplug and replug it.. okay so now for the fun part...
This is a customer's phone (SM-N920X) and they have an issue with the factory reset protection on the device. This device, to be more specific, is using the carrier c-spire and is the SM-N920R7 but at this point that really doesn't make a difference.
WHAT I'VE TRIED SO FAR:
The device fails in Windows 10 Pro 64-bit on every USB port front and back and even a USB 3.0 PCI port. I have uninstalled and reinstalled the drivers countless times on this particular machine and obviously to no avail. I have also tried this phone and a Windows 7 32 bit installation with the same issues. I then tried phone on my Linux box and when I run the DMESG command I get "unable to enumerate USE device, read failure at address XX"
So I then tried it in my Windows 8.1 Asus mini Netbook thingy with the exact same result as all the other windows installations. And just to be sure I tried it also on a Windows 10 32-bit installation with the same outcome. I have tried seven or eight different USB cables and tried all available USB ports on each of the machines listed above. The Note 5 charges just fine when you plug it in. I have tried cleaning up the charging port, adding a key in the registry with a binary that resembles this: SkipBOSDescriptorQuery 0000 01 00 00 00
I have try to use Smart Switch and Samsung Kies letting those programs uninstall and reinstall the drivers each time and again used multiple different cables. I know it is not the ports or the cables because my Galaxy S6 works just fine as did an S7 that I plugged in as well. I cannot reflash the stock firmware to the phone because it will not be recognized by my computer. The only thing I have access to is stock recovery and download mode do to the FRP lock. I have tried wiping data/ factory reset. Wiping cache apply update from Cache, apply update from external storage (cannot mount sdcard error), apply update from ADB (device null/not found when running tmadb sideload "package"..
What the hell can I do? I've never experienced such a pain in the ass phone issue than the one I'm dealing with currently. Please somebody help me LOL.:crying::crying::crying:
rip my balls off
!Led*Eyes! said:
Okay so I am well aware that there are hundreds upon hundreds of articles in different Threads Online about a similar issue. That being pretty much what the title says... " USB device has malfunctioned", "USB device not recognized", "device descriptor has failed (43)" and, in Linux, "unable to enumerate USB device" and then it gives readers at different numbers every time I unplug and replug it.. okay so now for the fun part...
This is a customer's phone (SM-N920X) and they have an issue with the factory reset protection on the device. This device, to be more specific, is using the carrier c-spire and is the SM-N920R7 but at this point that really doesn't make a difference.
WHAT I'VE TRIED SO FAR:
The device fails in Windows 10 Pro 64-bit on every USB port front and back and even a USB 3.0 PCI port. I have uninstalled and reinstalled the drivers countless times on this particular machine and obviously to no avail. I have also tried this phone and a Windows 7 32 bit installation with the same issues. I then tried phone on my Linux box and when I run the DMESG command I get "unable to enumerate USE device, read failure at address XX"
So I then tried it in my Windows 8.1 Asus mini Netbook thingy with the exact same result as all the other windows installations. And just to be sure I tried it also on a Windows 10 32-bit installation with the same outcome. I have tried seven or eight different USB cables and tried all available USB ports on each of the machines listed above. The Note 5 charges just fine when you plug it in. I have tried cleaning up the charging port, adding a key in the registry with a binary that resembles this: SkipBOSDescriptorQuery 0000 01 00 00 00
I have try to use Smart Switch and Samsung Kies letting those programs uninstall and reinstall the drivers each time and again used multiple different cables. I know it is not the ports or the cables because my Galaxy S6 works just fine as did an S7 that I plugged in as well. I cannot reflash the stock firmware to the phone because it will not be recognized by my computer. The only thing I have access to is stock recovery and download mode do to the FRP lock. I have tried wiping data/ factory reset. Wiping cache apply update from Cache, apply update from external storage (cannot mount sdcard error), apply update from ADB (device null/not found when running tmadb sideload "package"..
What the hell can I do? I've never experienced such a pain in the ass phone issue than the one I'm dealing with currently. Please somebody help me LOL.:crying::crying::crying:
Click to expand...
Click to collapse
Your problem is a hardware related issue.. I had this problem once before and I had to open the back of the phone using a heat gun to loosen the glue and then replace the charging port itself!! Nothing else worked and I mean NOTHING but replacing it!!
Replacement charging port
MrMike2182 said:
Your problem is a hardware related issue.. I had this problem once before and I had to open the back of the phone using a heat gun to loosen the glue and then replace the charging port itself!! Nothing else worked and I mean NOTHING but replacing it!!
Replacement charging port
Click to expand...
Click to collapse
Hey thanks for the reply . The phone had FRP triggered so I couldn't do much besides download and recovery mode but I did manage to bypass the FRP the old-fashioned way ! Good old trial and error/tinkering got the job done..You are absolutely correct though I updated the phone to no avail but after all the BS I went through trying to get it to work while FRP=on, I didn't try too hard after LOL.
Sent from my SM-G920T using Tapatalk
!Led*Eyes! said:
Hey thanks for the reply . The phone had FRP triggered so I couldn't do much besides download and recovery mode but I did manage to bypass the FRP the old-fashioned way ! Good old trial and error/tinkering got the job done..You are absolutely correct though I updated the phone to no avail but after all the BS I went through trying to get it to work while FRP=on, I didn't try too hard after LOL.
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
I'm going to assume it's not a Verizon or AT&T locked down pos and if that's the case, you probably could have just used "fastboot oem unlock" or just used fastboot to flash different firmware by going fastboot flash boot boot.img and fastboot flash recovery recovery.img and so on with the other files and wouldn't have had to much trouble lol..
When my charging port went out nothing could "see" it, not the desktop computer not the laptop not even my other phone using a wire to connect both phones together and it wouldn't even charge which is why I figured it needed to be replaced and after I did replace it everything worked fine again.
Enumeration, unfortunately, is a prerequisite in order for one to take full advantage of the fastboot commands...
Sent from my SM-G920T using Tapatalk
!Led*Eyes! said:
Enumeration, unfortunately, is a prerequisite in order for one to take full advantage of the fastboot commands...
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
HI, I have same problem here. Tmobile note 5 on latest firmware. Not rooted. Did you fix the problem?? if so how...???
I"m going crazy here too!!!
---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------
How do you flash anything if you can't connect the phone to pc????
Short answer: You don't.
Sent from my SM-G920T using Tapatalk
Having said that, there are alternative methods but you said you were not rooted currently so Flashfire is out of the question. I thought of searching for an app that will let you connect to ADB ever Wi-Fi without having to First connect to the computer via USB but I never looked into it. I was never able to flash anything I just bypass the FRP and took OTAs. You could try your luck at different one click root applications but I was unsuccessful with the new version of kingroot. If you can manage to get root access then you could use the official TWRP app to install recovery or use Flashfire to flash whatever you want but like I said it's a was a customer's phone so after I got the FRP done I didn't really didn't look into it anymore.
Sent from my SM-G920T using Tapatalk
**
!Led*Eyes! said:
**
Click to expand...
Click to collapse
How did you end up fixing this? same boat as you frp locked with it not being recognized - did you have to replace the port?
wilfred888 said:
How did you end up fixing this? same boat as you frp locked with it not being recognized - did you have to replace the port?
Click to expand...
Click to collapse
no. I bypassed frp the old fashioned way by connecting the frp locked phone to my mobile hotspot and then as soon as you see the phone switch from checking connection to software update kill your hotspot so it loses connection. the phone will give you an error that says it could not connect to network or something like that but then will allow you to Progress little bit further forward in the menus. when it asks you to set up a pin code for your lock screen do that. now when you lock and then unlock the phone you will have a lock screen and a camera icon in the bottom right corner swipe the camera to take a picture take a picture of anything and then choose to share the picture. there are many options in there and a couple of them will bring you to the screen to setup your Samsung account. either login to your Samsung account or create a Samsung account and then use it's application search feature to find the quick shortcuts application or any application that will allow you to go into the settings of the phone and I'm sure you can figure out the rest from there. it was a customer's phone so I just bypass the FRP and told him his phone won't connect to a computer didn't worry about the port
Sent from my SM-G920T using Tapatalk
So a month ago I purchased a used n920c and decided to root a few days ago. Come to find out I cant connect to pc in any way but will boot. So I have ordered a replacement usb board. A few mins ago I watched the how to video and must say this is not going to be fun. I did get the back off already (without breaking) and now just waiting on the part to come from china (no usa dealers had one for 920c).
Anyone here replaced the usb board yet? Got any hints besides watch videos.
I have one S7 930F like this too. I still have TWRP recovery, I can put custom ROM in CF card from computer. Then flash it in TWRP. The port still can do charge, seems it is low level USB firmware in the phone having issue.