Related
Hi there,
I have a stock Captivate. I patiently waited for the Froyo update because I didn't want to do anything that might void my warranty that I'm paying for every month.
Very, VERY long story short: I believe my phone is has been "soft bricked" - that's a term I found on here after reading countless hours worth of posts. I've got the phone--!--cpu thing, can get to the download screen, but the Kies Mini won't recognize my phone in emergency recovery mode. My computer recognizes it *sometimes*.
I followed the official Samsung update directions to a T, but Kies is garbage and it booted me out of the installation and left my phone screwed up. I've tried using two different computers (Win7, a 32-bit and 64-bit) and three different stock USB cables. I've turned off firewalls and uninstalled IE9; basically, I've tried everything I could find while searching for about 10 hours. 0_0
So, I'm over it. I know that AT&T will be useless to me so I'm just going to try to fix it myself. I've installed Odin3 and would like to get my phone working again. Luckily I saved my pics and contacts, so I can live with a fresh start. The question is, which version do I "flash" (I hope I used that term correctly)? I consider myself tech savvy but there are a million versions floating out there and I don't want to screw up my phone any more than it already is. Apologies if this is easily found somewhere else, but I did read a ton of FAQ pages and am still not comfortable picking out something to download.
thej0nes said:
Hi there,
I have a stock Captivate. I patiently waited for the Froyo update because I didn't want to do anything that might void my warranty that I'm paying for every month.
Very, VERY long story short: I believe my phone is has been "soft bricked" - that's a term I found on here after reading countless hours worth of posts. I've got the phone--!--cpu thing, can get to the download screen, but the Kies Mini won't recognize my phone in emergency recovery mode. My computer recognizes it *sometimes*.
I followed the official Samsung update directions to a T, but Kies is garbage and it booted me out of the installation and left my phone screwed up. I've tried using two different computers (Win7, a 32-bit and 64-bit) and three different stock USB cables. I've turned off firewalls and uninstalled IE9; basically, I've tried everything I could find while searching for about 10 hours. 0_0
So, I'm over it. I know that AT&T will be useless to me so I'm just going to try to fix it myself. I've installed Odin3 and would like to get my phone working again. Luckily I saved my pics and contacts, so I can live with a fresh start. The question is, which version do I "flash" (I hope I used that term correctly)? I consider myself tech savvy but there are a million versions floating out there and I don't want to screw up my phone any more than it already is. Apologies if this is easily found somewhere else, but I did read a ton of FAQ pages and am still not comfortable picking out something to download.
Click to expand...
Click to collapse
What you will need to do is use Odin to flash back to stock 2.1 and then load a custom rom. To be honest you cant do anything here that cant be reversed for your warrenty. Now as for Odin that is the tricky part as some work for some and not for others. Do you remember what version was on your phone? JF6 or JH7? What build number is it? I have a odin one click that I use and would be willing to post a link but I dont want you to wind up in a worse spot then you are now. I would search for how to unbrick a captivate and if non of that works let me know and I will give you a link to what I have. Or you could call ATT and tell them what happened and return it to warrenty
Thanks for the reply. I didn't know any of the pertinent details regarding the version I had.
I ended up going to an AT&T DSC Center during my lunch break. They took one look at it and swapped it out under the warranty; it took about five minutes. The "new" phone didn't have the latest version but I was able to update it with absolutely no problems on Windows 7 32-bit (throwing out all the details in case someone stumbles upon this for help). I guess Kies is just a very fickle program. I'm pretty bummed but at least I have a functional phone and as added bonus, I stumbled upon this kick-ass website that I can browse in the future.
thej0nes said:
Thanks for the reply. I didn't know any of the pertinent details regarding the version I had.
I ended up going to an AT&T DSC Center during my lunch break. They took one look at it and swapped it out under the warranty; it took about five minutes. The "new" phone didn't have the latest version but I was able to update it with absolutely no problems on Windows 7 32-bit (throwing out all the details in case someone stumbles upon this for help). I guess Kies is just a very fickle program. I'm pretty bummed but at least I have a functional phone and as added bonus, I stumbled upon this kick-ass website that I can browse in the future.
Click to expand...
Click to collapse
Ok glad you got it resolved. Enjoy your time here and welcome. Thread closed
Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.
When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.
It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.
On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.
In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.
And in the notification shade (again, while plugged into my PC) no option is given. It just charges:
I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).
In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?
As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.
I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.
Any help would be greatly appreciated because I'm just sick of this problem at this point.
Zenamez said:
I'm just sick of this problem at this point.
Click to expand...
Click to collapse
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
NLBeev said:
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
Click to expand...
Click to collapse
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Zenamez said:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Click to expand...
Click to collapse
Wish you luck.
W10-updates are causing issues on my PC
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Strephon Alkhalikoi said:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Click to expand...
Click to collapse
Tried 3 different USB cables and no luck.
I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.
Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
electricpete1 said:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
Click to expand...
Click to collapse
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.
My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.
Dvoraak said:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Click to expand...
Click to collapse
Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).
Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.
Dopamin3 said:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
Click to expand...
Click to collapse
I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.
It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).
I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.
I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.
Thanks to everyone who's replied though! I'll see how the USB replacement works out.
Hello all, long time lurker 1st time poster....
I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.
I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.
My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.
I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.
So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.
I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.
NOW...........................probably a silly question but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.
Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me .
CHEERS
Some quick thoughts.
1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.
2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.
Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)
1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk
2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.
As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.
Many Thanks once again
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
qprjim said:
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
Click to expand...
Click to collapse
SBE repaired my nexus 5, when it was rooted/unlocked.
Is there any damage to the usb port? Never tell the customer service rep that your device.
Cheers for the reply JonesL
As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.
I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.
Oh well....
Hey folks,
So I have a completely unmodified, stock Canadian N920W8 on 6.0.1, and no matter what I do, I cant get it to be recognized by Odin on my Win10 or Heimdall on my Mac.
I've done everything I could think of. Different cables, different ports, even different computers. Reinstalled the USB drivers, everything.
Anyone have any ideas? My phone won't fast charge, and is lagging more and more. I can't even Odin back to stock because it won't recognize. Factory Reset just cleaned out everything but nothing has changed. OEM unlock and USB debugging on, it won't be seen by the computers.
Any help? It's past manufacturer warranty, but it's still a good phone and I don't wanna lose it.
ve6ay said:
Hey folks,
So I have a completely unmodified, stock Canadian N920W8 on 6.0.1, and no matter what I do, I cant get
Any help? It's past manufacturer warranty, but it's still a good phone and I don't wanna lose it.
Click to expand...
Click to collapse
Did you install the actual drivers or just the ones that Windows installs? I use the ones that Samsung smart switch installs and I have no issues. If it is not fast charging and your computer does not recognize the phone it may not matter what drivers you use.
I used the Samsung USB drivers for Mobile Phones from Canadian support page. And that's on a fairly fresh win 10 install, too.
ve6ay said:
I used the Samsung USB drivers for Mobile Phones from Canadian support page. And that's on a fairly fresh win 10 install, too.
Click to expand...
Click to collapse
If you can I would suggest installing smart switch and see if smart switch sees your phone.
CodeNameRedNeck said:
If you can I would suggest installing smart switch and see if smart switch sees your phone.
Click to expand...
Click to collapse
I tried it on the Mac, smart switch didn't see the phone booted up. Didn't get a chance to try it in Odin mode. I'll try that tonight. And also on the PC. Any other suggestions?
ve6ay said:
I tried it on the Mac, smart switch didn't see the phone booted up. Didn't get a chance to try it in Odin mode. I'll try that tonight. And also on the PC. Any other suggestions?
Click to expand...
Click to collapse
Unfortunately not. I was hoping smart switch would see it. I would not rule out a damaged USB port.
I hope not... this is way past warranty, and I wanted to flash the thing with Khongloi's new Nougat rom... if it won't be recognized, then I can't even back it up or re-flash it to stock. Which is not a good thing...
No other suggestions, @CodeNameRedNeck ? You've been a huge help otherwise.
ve6ay said:
I hope not... this is way past warranty, and I wanted to flash the thing with Khongloi's new Nougat rom... if it won't be recognized, then I can't even back it up or re-flash it to stock. Which is not a good thing...
No other suggestions, @CodeNameRedNeck ? You've been a huge help otherwise.
Click to expand...
Click to collapse
Just to be sure. Can you transfer files from your PC to your phone and vice versa? Do you have any USB 3.0 ports? My phone seems to work better on 3.0 but still works on other types. Do you still have the Samsung cable? I know you said you have tried other cables but I used to have two cables that would not do data.
I tried with a brand new from the box cable, into four different usb 2 ports on the Mac and 2 usb 3 ports on the windows 10 PC.
No luck with it even being recognized for file transfers either.
@ve6ay, I could be wrong but I would say you probably need a new port. You should be able to pick one up relatively cheap. Good luck.
That's my thought, too, and in that case, I'll forgo anything. The contract is up in October, and it got the OTA update to 7.0, so I'm okay with it for now. I'm not into opening up her phone (which hasn't even been rooted yet) to switch out a port that I'm not confident enough to switch out.
ve6ay said:
That's my thought, too, and in that case, I'll forgo anything. The contract is up in October, and it got the OTA update to 7.0, so I'm okay with it for now. I'm not into opening up her phone (which hasn't even been rooted yet) to switch out a port that I'm not confident enough to switch out.
Click to expand...
Click to collapse
Did you try going into Developer Options and then scrolling down until you see "USB Configuration" and setting it to MTP? Or open the dialing pad and enter *#0808# and then making sure it's set to MTP, ADB and then try again.. If that doesn't work then it really is your port connection and it's actually super easy to replace and cheap too! All you'd have to do is heat the back up so you can loosen the glue up and then slowly pry the back off and then remove like 16 screws(lol) and then at the bottom you just unscrew it and easily pull the thin connection out.. I've done it several times so far although trying not to break the back glass is super hard..
The back glass got shattered in a drop last summer. So that will probably be a problem. Like I said, new phone this fall, most likely the next Note series. Though I'm tempted to go with an Exynos variant from across the ocean.
I had previously setup my MI account and done the oem unlocking and everything got the wait screen for 168 hours, now I'm trying to get back to that screen but the flash tool won't detect the phone being plugged in. I can no longer access android USB debugging either, whenever phone is plugged in it just charges the phone and whenever I change the USB config in settings to midi or file transfer it does nothing.
Really want to unlock and start flashing new Roms, should I do a factory reset or what can be done?
After setting up my MI account, I accidentally updated to the latest global rom, as an update was available, I'm scared it may have affected the device permissions.
Any help would be much appreciated if anyone encountered this issue!
reboot your device to fastboot (power + vol down) and plug yout phone on your pc... nothing happens?
Nope nothing happens idk if it's phone cable or laptop yet, I'll try more cables soon and get back, but I've never accounted a problem like this before
You really have to try in another PC, with another cable... It's a hardware fault for sure...
I got it to work with another laptop but upon rebooting to fastboot it couldn't detect the phone anymore, same wire so I'm confused
fast9000 said:
I got it to work with another laptop but upon rebooting to fastboot it couldn't detect the phone anymore, same wire so I'm confused
Click to expand...
Click to collapse
It could be the USB cable.
Are you using the USB cable that came with the phone and is it in good condition?
Try and get a good quality data USB cable
I was using a third party cable, I'll wait the standard one week wait time before attempting to try to unlock it as it's pointless without waiting the specified time
Also, I just came to realize this but since Xiaomi doesn't sell in North America, I imported the phone from Hong Kong, and in the packaging it was intended for EU Markets. As such I'm running MIUI 10.3.3.0 (PFKEUXM), which I believe is the EEA version and not the Global Rom version, even though the settings say otherwise, could the fact that I'm located in Canada and trying to activate from here affect my chances of unlocking the phone in any way?
fast9000 said:
... As such I'm running MIUI 10.3.3.0 (PFKEUXM), which I believe is the EEA version and not the Global Rom version, even though the settings say otherwise, could the fact that I'm located in Canada and trying to activate from here affect my chances of unlocking the phone in any way?
Click to expand...
Click to collapse
Won't make any difference.
Hi, I really hate to make a new thread, but I just cannot get this darn thing to connect to my PC. I had a G900A (S5) for over 4 years, rooted w/custom rom. I had/have a G935F rooted with SMan custom rom on Android 8. They both work fine (well S5 died a bit ago...LOL). I downloaded the newest Samsung USB driver, which installed fine and the G935F still works. I tried it both on my W7 Pro desktop and W10 Home laptop.
But this damn S20 will absolutely not connect (using same cables on both, except of course the S20 uses USB-C). This THING is on Android 11 (sucks to holy hell). I enabled the Developers Option and enabled USB Debugging and then changed the USB Default config from Charge Only to "Transferring files" and still NOTHING (of course I can say that it Does charge).
I have looked Everywhere. Called useless T-Mobile and they did not know. I got it on Friday and going to the store Monday. Can anyone solve this and save me a trip or do you think something is wrong with the hardware (it's brand new out of the box)?
THANKS!
does windows recognise that a phone is plugged in or not. use the original cable if you're not and swap which USB ports you try on the PC/laptop.
there is supposed to be an issue where MTP screws up large file transfers but it still recognises the phone.
samccfl99 said:
I downloaded the newest Samsung USB driver, which installed fine and the G935F still works. I tried it both on my W7 Pro desktop and W10 Home laptop.
But this damn S20 will absolutely not connect (using same cables on both, except of course the S20 uses USB-C). This THING is on Android 11 (sucks to holy hell).
Click to expand...
Click to collapse
Was it v1.7.43 and did you remove 'any' old driver versions before installing -
- https://developer.samsung.com/mobile/android-usb-driver.html
And when plugging in the phone for the first time you may have gotten a prompt to allow access, if different/more annoying under Android 11 afaik.
And on a different but Android 11 front, can I ask what bits sucked or were different to 10 for you on this device?
b1k3rdude said:
Was it v1.7.43 and did you remove 'any' old driver versions before installing -
- https://developer.samsung.com/mobile/android-usb-driver.html
And when plugging in the phone for the first time you may have gotten a prompt to allow access, if different/more annoying under Android 11 afaik.
And on a different but Android 11 front, can I ask what bits sucked or were different to 10 for you on this device?
Click to expand...
Click to collapse
Hey, did you mean to quote without replying..?
Hi, I said I installed the newest (that is the version) and did it before I even got the phone and my 935F worked fine. But no, I did not uninstall the old one. It knew it was there and it did it. I have updated the driver the same way in the past and both the 900A and 935F always worked.
Also I think I said what versions I had on both phones, which were android 4 + 5 on the 900A and 7 + 8 on the 935F.
It NEVER asked me Anything Anytime I plugged it in.
I could actually live with this phone (made so cheap, by the way), if I could just get into it and complete putting my files on it. Also THIS phone is draining battery a bit Because I can't root it to get rid of whatever bloatware crap is on it (any suggestions on that?).
Plus I don't like all the crazy crap it displays and does. ALSO, CAN THEY KEEP MAKING THE CLEAR BUTTON EVEN SMALLER???
Attached is a pic of my beloved S5 BEFORE GOOGLEY SCREWED UP ANDROID, THAT THEY CREATED TO BEGIN WITH...Grrrrrrrrrrr...THOSE WERE THE GOOD OLE DAYS OF REAL ANDROID...LOL.
Thanks anyway for the reply!
PS, sorry I been away from the forum for a while. Things are a bit different now! Sorry, b1k3rdude!
3mel said:
does windows recognise that a phone is plugged in or not. use the original cable if you're not and swap which USB ports you try on the PC/laptop.
there is supposed to be an issue where MTP screws up large file transfers but it still recognises the phone.
Click to expand...
Click to collapse
Hi, I did try the same "extension" cables and ports that I used for the 935F, but I had a USB-C laying around for my bluetooth and used that and never thought to use the original cable that came with the box (still in the box). It Never recognized the phone ever. I will try that...If it works I am going to bang my head against the wall because I spent hours trying it and researching it and even uploaded certain files to my google drive just to get them to the new phone (I Was Determined)!!!
I will try it and edit this with the results. Thanks!!!
Son of a B*tch, that worked! The cable that came with the BT did not work, but the original one did right away. I did not know that it installs separate drivers for different phones! It installed all the drivers and the phone asked for permission and Voila! Even worked with my old USB extension cable. I never would have thought of that.
THANK YOU, THANK YOU, THANK YOU! See, when I got up I went to look to see if anyone answered before I even took my pills and etc...Now back to all the disastrous news. I am a H Andrew "victim" and feel bad for the people of LA, and of course what happened in Afghanistan. So off to the News...
Also may I ask what is so special about the cable that came with the phone as opposed to the one I used from my BT??? Thanks!
So on another note, any tips on how to get around all the crap of UNROOTED Android 11?
Also, do any of these rooting threads really work on this US version of the phone? For sure this darn BL is locked. I did find a procedure to tell. A bit complicated (for me), but now that I can get into the phone, I can surely try.
Also I miss my Viper for great sound. Anyone know how to replace it with something if I can't get this rooted? AND WHERE THE HELL IS THE HEADPHONE JACK??? LOL. Plus, do you know how long it took me to figure out how to just get a screenshot on this THING??? JEEZ!
We switched to T-Mobile from ATT and this phone cost me Only $99 over 24 months + $49 tax, while the other 3 on the family plan got their usual rotten apple (I-12's) for free plus tax. I Refuse to get one, but I am an old time programmer and can't see my way to a rotten apple...yet...LOL
Thanks, Sam in FL
Also, I must say that this 5G here actually works in spots (not in my condo though). I got over 500 Down and 49 Up near me, then got depressed when it did not do that in my condo, but I got wifi anyway and who really needs that much down anyway???
Samsung's cables designed for data transfer and flashing are not the same as off the shelf data transfer cables (unless it's made by a decent manufacturer like Anker).
for getting rid of the crap apps, look up ADB debloat threads for Samsung phones, the newer the better, one close enough like S20 or S21 will do.
3mel said:
for getting rid of the crap apps, look up ADB debloat threads for Samsung phones, the newer the better, one close enough like S20 or S21 will do.
Click to expand...
Click to collapse
There are some S20FE specific ones in this S20FE section.