Database Users

No charge, no sync - loose MHL cable port.

Only had mine 3 weeks and its broken already. I have been using a desktop charger and have not been forcing it in at all, not once, I have always been very gentle inserting it it, anyway it no longer charges, it looks like the connectors have pushed themselves back so they are not flush anymore and thus no longer connecting to charge or sync.
Not happy about this at all, I had my desktop charger for my HD2 for 18 months with no problems at all, this suggest a very weak connector.
!!! BE CAREFUL !!!
Going to call in at Phones4you and see if they will swap it, I don't hold out much hope though.

Wow bad luck man, but really you don't need the F word to express your frustration.

stoolzo said:
Only had mine 3 weeks and its broken already. I have been using a desktop charger and have not been forcing it in at all, not once, I have always been very gentle inserting it it, anyway it no longer charges, it looks like the connectors have pushed themselves back so they are not flush anymore and thus no longer connecting to charge or sync.
Not happy about this at all, I had my desktop charger for my HD2 for 18 months with no problems at all, this suggest a very weak connector.
!!! BE CAREFUL !!!
Going to call in at Phones4you and see if they will swap it, I don't hold out much hope though.
Click to expand...
Click to collapse
was it an official desktop charger or 3rd party?

DO a factory reset using code *2767*3855#
(please not this will wipe everything including built in memory, so do backup before you proceed. Backup possible by moving content of internal memory to SD card by copy paste in file manager)
I had a problem when my phone stopped charging after I upgraded firmware, It would also launch Connected to computer screen when it wasnt . Thought its dead.
Did factory reset using this code and its working flawlessly ever since. Seems to be some kind of bug which happens out of nowhere as 2 people I know have experienced this after upgrading to KE2.

stoney73 said:
was it an official desktop charger or 3rd party?
Click to expand...
Click to collapse
I was going to ask exactly the same thing...

I think the OP means that the micro usb receptacle has come away from the board and has been pushed back into the body of the phone. I hope this is not going to turn out to be a common problem as it's something that seemed plague to the Nokia N900 and it took ages for Nokia to acknowledge a design/production fault.

great advice, now it wont boot at all, just goes round in circles....
F**cked.....

anyone got any ideas?

Hi, the charger isnt really the issue, i haven't had any problems inserting the phone into the charger, ie no resistance which suggests to me it was week or loose and has gradually pushed it self back over the last 2 weeks since I have had the charger. If thats the case it would have done this with any charger or cable.
Just spoke to phones4you, they are going to exchange it for me, they didnt even grumble after I told them what happened which I thought was odd, heading off now to pick it up.

Will be interesting to see if your wifi is any better on the new phone stoolzo. Maybe you could let us know. Thanks.

good old phones4you
got it already, yes I really have. Phones4you are just round the corner in PC world. Will check my wifi tonight and report back on the other thread.

Please change the thread title. All type of people view xda.
Sent from my GT-I9100 using XDA App

remove and reinsert battery
i had this issue when running custom kernels. somehow doesnt happen with stock.
issue happens like this:
u go to bed while charging
u wake up and the phoneis off or very hot with battery and temperature warning
u reboot and it doesnt reboot, doesn't boot, just goes in circle battery display/reboot cause it doesnt seem to charge neither have enough power to boot.
removing battery + cable then putting both back = it boots again and charge normally

stoolzo said:
Hi, the charger isnt really the issue, i haven't had any problems inserting the phone into the charger, ie no resistance which suggests to me it was week or loose and has gradually pushed it self back over the last 2 weeks since I have had the charger. If thats the case it would have done this with any charger or cable.
Just spoke to phones4you, they are going to exchange it for me, they didnt even grumble after I told them what happened which I thought was odd, heading off now to pick it up.
Click to expand...
Click to collapse
************************************************************
Yeah, did all the usual things, I have bricked phones before and always managed to turn them around but we have no CMR to flash anything from ROOT/SD so when it wouldn't boot after a factory reset I knew I was in trouble
The MHL port being loose was the tell tale sign of a fault as I hadn't misused it at all. When I compared it to my new phone I got today it was defo a little further back, just enough to prevent it connecting.
Good old phones4you, fault report to phone exchange in under an hour, impressive.
Just in case the charger had anything to do with this I am going to get rid, dont think it did but I don't want to risk it.
its this one:
http://www.mobilefun.co.uk/desk-dock-for-samsung-galaxy-s2-i9100-p29488.htm

OnePlus 2 Slow charging and data not working.

Hello folks!
I've recently bought the oneplus 2 second hand but sadly it didn't came in the state it would be, so no charger, no charging cable, no box and only lots of filth in the usb type c charging port (Couldn't even plug in the cable so bad). But I was convinced that it wasn't stolen and I also tried to find it but it wasn't missing by anybody so yeah.
When I cleaned out the port and got it to work it literally just took ages and mtp wasn't working sadly.
I've done some research and people have said that the slow charging might have been caused by a faulty cable/charger head. I've replaced the cable and charger head by one from ugreen and it should be working fine. But the problem is that sometimes it's charging as it should normally but 99% of the time it's just charging slow.
Also data transfer is not working, even in fastboot it's not working. I had gotten it to work after downgrading the first time but then after a day it stopped working again. I've also replaced the usb flex cable but that ofcourse didn't changed anything sadly.
I am out of options as my search results only delivered such kinds of answers also unlocking and relocking the bootloader and enable usb debugging etc are also all not working.
I hope someone could help me out with this who might have also faced the same issues as an flashaholic this is ofcourse a pitty especially since fastboot isn't working and probably qualcomm's recovery mode also not since data transfer is totally not working.
For the one's who are helping me already thanks in advance :good: and have a nice day further

wulsic said:
Hello folks!
I've recently bought the oneplus 2 second hand but sadly it didn't came in the state it would be, so no charger, no charging cable, no box and only lots of filth in the usb type c charging port (Couldn't even plug in the cable so bad). But I was convinced that it wasn't stolen and I also tried to find it but it wasn't missing by anybody so yeah.
When I cleaned out the port and got it to work it literally just took ages and mtp wasn't working sadly.
I've done some research and people have said that the slow charging might have been caused by a faulty cable/charger head. I've replaced the cable and charger head by one from ugreen and it should be working fine. But the problem is that sometimes it's charging as it should normally but 99% of the time it's just charging slow.
Also data transfer is not working, even in fastboot it's not working. I had gotten it to work after downgrading the first time but then after a day it stopped working again. I've also replaced the usb flex cable but that ofcourse didn't changed anything sadly.
I am out of options as my search results only delivered such kinds of answers also unlocking and relocking the bootloader and enable usb debugging etc are also all not working.
I hope someone could help me out with this who might have also faced the same issues as an flashaholic this is ofcourse a pitty especially since fastboot isn't working and probably qualcomm's recovery mode also not since data transfer is totally not working.
For the one's who are helping me already thanks in advance :good: and have a nice day further
Click to expand...
Click to collapse
Your usb port must have gone bad.

utkarsh102 said:
Your usb port must have gone bad.
Click to expand...
Click to collapse
Well I recently have replaced my usb port and I doubled checked the flex cables so that shouldn't be the issue, also I inspected the motherboard but couldn't see any oxidations or damages further. so it stays a mystery for me sofar.

Having the same issues : Slow charging, no data transfer and no usb otg.
Can you please tell me how you manage to downgrade.
Thanx

Shan_77 said:
Having the same issues : Slow charging, no data transfer and no usb otg.
Can you please tell me how you manage to downgrade.
Thanx
Click to expand...
Click to collapse
Use adb over network

Shan_77 said:
Having the same issues : Slow charging, no data transfer and no usb otg.
Can you please tell me how you manage to downgrade.
Thanx
Click to expand...
Click to collapse
If you want to attempt to downgrade you could download an older OOS firmware version and just flash it through the stock recovery as OOS supports downgrading in their recovery
But that probably won't solve the issue. I've done it and weird enough it worked for a slight moment so I could use fastboot but after that it didn't worked anymore.

wulsic said:
If you want to attempt to downgrade you could download an older OOS firmware version and just flash it through the stock recovery as OOS supports downgrading in their recovery
But that probably won't solve the issue. I've done it and weird enough it worked for a slight moment so I could use fastboot but after that it didn't worked anymore.
Click to expand...
Click to collapse
I tried it didn't solve the issue, maybe it's a hardware issue. Thanx for the answer

Shan_77 said:
Having the same issues : Slow charging, no data transfer and no usb otg.
Can you please tell me how you manage to downgrade.
Thanx
Click to expand...
Click to collapse
The same problem for me, I am using Lineage Os

Can't connect to PC, can't charge except when off

Yesterday, after a few hitches, I installed twrp 311 and then RR and immediately switched to AOSPE. Now in having the issues described in the title. It might be relevant that the handset got a little wet, but it's gotten wet before and nothing's happened. Could it be a software issue? A hardware issue? A coincidentally timed buildup of dust? Other people have similar issues, but as far as I've seen nobody has had a phone that seems to have a broken USB port except when the phone turns off. Also, the charging connection breaks when I jiggle the cable in the port, which might be relevant.
Halp

Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.

william.johhn7! said:
Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.
Click to expand...
Click to collapse
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.

westinator said:
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.
Click to expand...
Click to collapse
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.

william.johhn7! said:
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.
Click to expand...
Click to collapse
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?

westinator said:
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?
Click to expand...
Click to collapse
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.

william.johhn7! said:
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.
Click to expand...
Click to collapse
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?

westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flashlight doesn't work in miui roms but works for custom ROMs?! very odd. Try wiping battery stats through twrp. And the last hope to get it working is by fastboot flashing. If that doesn't help, the device needs to be serviced. There must be some local centers that services Xiaomi products.
Anyways forwarding your matter to others(A telegram group consisting of other users and developers). Lets see if they can help.

westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader

bekcicandrej said:
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader
Click to expand...
Click to collapse
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...

westinator said:
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...
Click to expand...
Click to collapse
Glad to hear the good news.
FYI I flash miui in edl on a bi-monthly basis, just to refresh the partitions

Screen dead + Front camera keeps trying to open

Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.

Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.

XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.

Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.

XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?

angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/

XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha

angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.

USB connection not seen at all, in system, fastboot or recovery,

Hi all,
Have just started to connect my device so i can pull the patched boot image for my thread and it won't see the computer, tried on several laptops and nothing, no adb, no fastboot.
It charges just fine but does not show the android usb system notification.
Really annoyed by this as i'm kind of stuck.
I'm on 7.7 but on a custom ROM / Evo X 5.9.1, doesn't look like anyone else has this issue besides me, have seen the odd user complaining about the same thing but haven't seen any fixes come up], if anyone has any ideas then i'd be grateful to get your two cents.
Will test MSM but it's not looking good, fearing a return to oneplus as i do have a good unit with none of the issues anyones ever listed like green screen and overheating problems.
It's usually me helping others but this time i need you guys help

Check USB cable / clean the Charging port? sometimes it helps.

dewa5227 said:
Check USB cable / clean the Charging port? sometimes it helps.
Click to expand...
Click to collapse
Aye I've cleaned it up mate.
Tried different cables, I think EDL mode is working.
Means I could maybe return to OOS but it wouldn't let me back up..
Shame, I'm just downloading MSM now... Really annoyed..will give the usb socket another clean

dladz said:
Tried different cables, I think EDL mode is working.
Click to expand...
Click to collapse
well, it's a good sign , hopefully, it will be resolved out.

dewa5227 said:
well, it's a good sign , hopefully, it will be resolved out.
Click to expand...
Click to collapse
Yea I'm dreading it being hardware. Never had this issue on OOS.
I think it may be Evo X but I don't know.
Bad luck I guess
Cheers anyway.

So MSM did indeed work, it's booting now, obviously couldn't back up any of the info on the device so i'm super annoyed at that but so long as usb connectivity works then i'll be happy with that.
USB Connectivity does NOT work now so i CAN connect to EDL mode but not normal usb conenctivity.
Anyone have any ideas???

Cannot root, install anything via ADB or even delete apps via ADB. Shocking problem to have man

I'm RMA'ing my phone, just getting it set up now.
Very painful process, they absolutely need the purchase order for warranty, things have changed with 1+
3-10 days apparently, used to be 5 when i've sent it in the past.

On connecting a USB hub i can read USB sticks and i can control my phone with an xbox pad??
Am i missing something? How is all this working yet i can't mount my phone?

Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?

dewa5227 said:
Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?
Click to expand...
Click to collapse
I did use the force USB charging yes.. wishing I hadn't now..
I also connected to a usb-c to hub to connect a screen.
Issues kind of started after that.
Physically I haven't damaged it from movement. But could be from the forced charging

UPDATE:
Erm ok this is confusing???
I just connected my phone to a charger that is clearly not rated for it, in the hope it would shock the device, i then connected my phone and made a cup of tea, when i got back my phone showed me this (screenshot attached)
??? Lol what the hell? I've already booked my RMA lmfao
anyway, i shall keep an eye on it, i'll thoroughly test it and get it back up and running.
Strange, very strange.