Related
I have upgraded to an S3 from having a Vibrant for years. I rooted and flashed several OS's to my Vibrant in those years without an issue ever. I have been trying to get files transferred to my S3 from my computer for 2 weeks now. The computer has the drivers installed correctly. It is recognized by name when I plug it in (it comes up as SGH-T999, Kies will recognize it too). whenever i try to transfer ANYTHING it stops in the middle of the transfer. just sits there with no further progress to be achieved. This is insanely frustrating. I am unable to root this thing because of the inability to actually transfer.
Things I have tried:
Uninstalling/reinstalling Kies multiple times
Uninstalling all USB device drivers multiple times
Reinstalling drivers through Kies and through Samsung's website multiple times
Factory reset on the phone multiple times (****ing aggravating btw)
Using my old Vibrant cable
Changing between MTP and camera mode... several times
Yelling at it
I have been trying to research how to fix this garbage for weeks now. there is no concrete way to remedy this problem that i have found. every thread about this is littered with the usual "uninstall your driver and reinstall it" nonsense that is the most generic response to anything tech related ever.
What I can tell you is that my phone is definitely getting recognized by anything that can do so. Odin, Kies, My computer, etc etc... it appears that the issue lies in the actual data transfer. As I mentioned, transfers initiate but will lock up mid-process and just hang there infinitely. Same goes with Odin when I try to get it to flash into CWM recovery.
Please, help. any time spent trying to fix this issue is greatly appreciated.
Are you uding the usb cable thst came with the phone?
Have you tried different cables? Or on another computer?
Im guessing your not rooted then?
Try installing the drivers ONLY. get them here:
http://forum.xda-developers.com/showthread.php?t=1728605
Uninstall previous versions of everything first.
What version odin are you using? Use 3.07 from above post if you're not already.
Also try this app
http://forum.xda-developers.com/showthread.php?t=1711009
If you are rooted try SwiFTP or another wireless transfer app.
Sorry to mention drivers again but if you're relying on kies to do that for you it could be the issue.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
Sorry I missed the part where you mentioned drivers and cable. Damn choppy xda app!
Sent from my SGH-T999 using xda app-developers app
Since you've tried everything else might as well follow this guide and install the drivers through the toolkit.
http://forum.xda-developers.com/showthread.php?p=28175575
I'd also run windows update and check if there's a new bios/drivers for your mobo and usb controller.
If you plug another "foreign" usb device does it install fine?
May not have any bearing whatsoever here but do you have usb debugging checked? And I think I mentioned it in the other post but try a different computer if possible.
You said that this happens when using odin too? As in you start the flash with Odin but it doesn't complete? Or it wont even start? Does it give you any message?
When plugged in in download mode, does Odin show your COM port in the upper left?
Plug in the phone and open device manager. Does it show any errors or anything?
Sent from my SGH-T999 using xda app-developers app
I recommend an app called airdroid. I had issues transferring stuff to and from my Mac and haven't had any problems since I started using the program. Besides it's wireless so I don't have to worry about the wires being a problem
psykhotic said:
Since you've tried everything else might as well follow this guide and install the drivers through the toolkit.
http://forum.xda-developers.com/showthread.php?p=28175575
I'd also run windows update and check if there's a new bios/drivers for your mobo and usb controller.
If you plug another "foreign" usb device does it install fine?
Click to expand...
Click to collapse
everything else works fine from my 6 USB ports (2 USB 3.0 ports as well). The tool kit solution still needs Odin to root. The problem is not detecting the device. it is the transferring of data. Data transfers begin but that's about it. Odin gets to "firmware update start" and then "boot.img" and just hangs there forever. no change. nothing else.
Is there a wireless way to do this? I have purchased Rom Manager but since i can't achieve root it is just useless now. The phone is brand new from the Tmobile store. Not once has it been dropped (to put into perspective how careful i am with my devices, I managed to drop my Vibrant once in ~3 years, which caused no damage, what a great phone that was). I have not been able to read about this same issue anywhere else either...generally its an issue with the PC not recognizing the device but when someone gets it to link up correctly, it works. this is the opposite.
thank you for your ideas so far.
DocHoliday77 said:
May not have any bearing whatsoever here but do you have usb debugging checked? And I think I mentioned it in the other post but try a different computer if possible.
You said that this happens when using odin too? As in you start the flash with Odin but it doesn't complete? Or it wont even start? Does it give you any message?
When plugged in in download mode, does Odin show your COM port in the upper left?
Plug in the phone and open device manager. Does it show any errors or anything?
Click to expand...
Click to collapse
Odin shows the "0:COM" like it should, which means it is able to read that the device is there, it just is unable to do anything after "boot.img", everything that is needed for this to work via the toolkit method is checked (USB debug and unknown sources).
I just got the s3 and had transfer issues too. Turns out my s2 drivers wasn't perfect for it even though it recognizes the device. I used the s3 drivers instead and that helped things a bit with accessing my phone's storage. So i ended up formatting my internal storage and that seems to do the trick for me.
If that doesn't work and odin still gets stuck then try different usb ports also try different wires
Sent from my SGH-T999 using xda app-developers app
Try connecting without the external sdcard in.
What build are you currently on. Since you haven't roited or anything im assuming you're still on either UVALEM or UVALG1. If so try initiating the software update. It should download the ota thatll take you up to UVALH2. Maybe that'll help.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Try connecting without the external sdcard in.
What build are you currently on. Since you haven't roited or anything im assuming you're still on either UVALEM or UVALG1. If so try initiating the software update. It should download the ota thatll take you up to UVALH2. Maybe that'll help.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Currently do not have an external SD.
Baseband version T999UVLH2 is what i have running after a fresh phone reset.
Teo032 said:
So i ended up formatting my internal storage and that seems to do the trick for me.
Click to expand...
Click to collapse
Did you do that through terminal? doesn't the single partition mean that it would wipe everything?
Make sure the drivers you are using are the same ones that are in my comment (version).
What are you trying to flash through Odin? If the permissions of the files inside the tar file are not correct, the transfer will hang, and do nothing but give a timeout message after a couple minutes. I learned this the hard way.
In summary:
Use a different USB cable.
Download drivers, Odin, and CWM from my signature. After uninstalling the old drivers manually through devman (be sure to delete them during uninstall), reinstall them from the package you downloaded. Then use Odin to flash CWM. All three of these packages are tested and known to be 100% working. Please don't ignore this step. If I can't verify the validity of your installation sources, I can't rule this out for troubleshooting purposes.
If this doesn't work, it is most likely your computer. Are there any BIOS firmware updates that improve USB compatibility, or USB controller driver updates? The USB 3.0 isn't natively supported on =< Win7, so those are third party drivers. But I will assume you are connected to a USB 2.0 port.
Aerowinder said:
Make sure the drivers you are using are the same ones that are in my comment (version).
What are you trying to flash through Odin? If the permissions of the files inside the tar file are not correct, the transfer will hang, and do nothing but give a timeout message after a couple minutes. I learned this the hard way.
In summary:
Use a different USB cable.
Download drivers, Odin, and CWM from my signature. After uninstalling the old drivers manually through devman (be sure to delete them during uninstall), reinstall them from the package you downloaded. Then use Odin to flash CWM. All three of these packages are tested and known to be 100% working. Please don't ignore this step. If I can't verify the validity of your installation sources, I can't rule this out for troubleshooting purposes.
If this doesn't work, it is most likely your computer. Are there any BIOS firmware updates that improve USB compatibility, or USB controller driver updates? The USB 3.0 isn't natively supported on =< Win7, so those are third party drivers. But I will assume you are connected to a USB 2.0 port.
Click to expand...
Click to collapse
None of that worked. I did find a BIOS upgrade for my mobo that i didnt know was released, flashed it, and transfers still hang. i tried everything from your sig to no avail. i DON'T have access to another computer... BUT i do have Ubutnu running on my comp in conjunction with Win 7 Ultimate 64. can't seem to find too much on non-international S3 stuff for linux.
this has consumed my entire day and i am so frustrated.
Try in safe mode? This sounds really frustrating. I gave up when this happened with my mac. I think someone said it already but I always recommend Airdroid. It's just simpler.
psykhotic said:
Try in safe mode? This sounds really frustrating. I gave up when this happened with my mac. I think someone said it already but I always recommend Airdroid. It's just simpler.
Click to expand...
Click to collapse
airdroid for music transfers, got it. im screwed on the root thing though.
I didn't do it through terminal. I just connect it to the computer. Right click phone's internal storage and clicked format. It was a very quick format.
Sent from my SGH-T999 using xda app-developers app
Teo032 said:
I didn't do it through terminal. I just connect it to the computer. Right click phone's internal storage and clicked format. It was a very quick format.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
so let me get this straight... you plugged the phone in, right clicked on it in a browser window, clicked on format, selected yes to the "hey, this is going to erase everything on the device" warning pop up, and you were able to transfer files no problem after that? no adverse side effects came from this? it sounds like it would brick the phone...
Spaldino said:
so let me get this straight... you plugged the phone in, right clicked on it in a browser window, clicked on format, selected yes to the "hey, this is going to erase everything on the device" warning pop up, and you were able to transfer files no problem after that? no adverse side effects came from this? it sounds like it would brick the phone...
Click to expand...
Click to collapse
Yep that's what i did. That's only the storage partition. There's a system partition that isn't viewable on window explorer
Sent from my SGH-T999 using xda app-developers app
Teo032 said:
Yep that's what i did. That's only the storage partition. There's a system partition that isn't viewable on window explorer
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
didn't work either. i give up. MTP is garbage.
Different computer?
Sent from my SGH-T999 using xda app-developers app
I had these frustrations as well. I finally move where I was connecting the cables. First instinct was the easiest access on my computer. It always failed. I finally decided to try my back usb and it worked it also picked up as a mass storage as well.
Sent from my SGH-T999 using xda app-developers app
Yeah I'm starting to think you might need to use a different computer. Odin detects so it's not drivers.
From my experience with the hangs when i was on the s2. Many also reported this but what helped was different usb ports, wires, or an entirely different computer.
Sent from my SGH-T999 using xda app-developers app
Okay i have seen similar posts around, and I apologize if this bothers anyone but when I post a thread asking for help, its because I've tried most solutions and have gotten nowhere. I recently bought one.of.these devices and I have to say for an old 1GHz device, its pretty darn smooth! (Got it for my girl who broke her phone. Cost $20 MINT screen, and some scuffs.on the trim believe it or not, fully functional, clean ESN)
I love for all devices in the house to be rooted and off that dreaded Gingerbread android. I have been stuck since i got it trying to use ODIN to flash CWM, and root it to flash a JB based rom. Problem is i installed the drivers, got the ODIN version required, have the CWM tar file, etc, the phone gets detected while on in ADB, normal file transfer way and so on. BUT Download Mode? Nope, i get the dreaded "Unknown Device" issue.
Now as I always read before annoying others, I read that switching the USB cable helps. I've tried 8 USB cables, and no go. 2 Samsungs (i read those are #1 NO GOs), 3 LG cables (device doesnt appear at all), and 3 non brand. No good.
I know Mobile Odin wont work, I rooted it using Framaroot.apk for now, but I need CWM for the rom flashing part.
So now that its 2013, is there really no other way other than ODIN? I tried using ROM Manager, it flashes but doesnt do a thing except boot into stock recovery (miracle no bricks or bootlooping). If I had Linux on my PC, will it get detected or its just the darn cable?
OR is there a specific USB cable brand I should go for that is guaranteed to work? I dont mind buying it just have been waiting to make sure.
Any help or advice is greatly appreciated.
Most people recommend using a BlackBerry cable
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Most people recommend using a BlackBerry cable
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Thank GOSH I read your response in time! I am currently at BestBuy and was going to buy a totally different brand USB. Hopefully they have them here.
Crossvxm said:
Thank GOSH I read your response in time! I am currently at BestBuy and was going to buy a totally different brand USB. Hopefully they have them here.
Click to expand...
Click to collapse
I use this cable and have had zero issues. http://www.monoprice.com/products/p...=10303&cs_id=1030307&p_id=5458&seq=1&format=2
Well there's good news and bad.
Got an official BlackBerry USB cable.
Bad is the device is STILL not recognized.
The drivers have been properly installed, there is no updating the drivers manually, effing Windows won't let me. What the hell can I do now?
If only Mobile Odin worked, or there were other methods, I wouldn't be going thru this mess...
Like where did I go wrong?
I would swap out Windows to Linux, but I don't see how that will get the device detected.
Matter of fact I was trying to install a Linux based OS from my flash drivd, and it corrupted it. Theres 8gb Ill never see again...
Any other ideas? Will Linux pick up the device?
EDIT: This USB unlike the others BRIEFLY detects it as a USB Device, then goes back to unknown when I uninstall it thru Device Manager
Crossvxm said:
Well there's good news and bad.
Got an official BlackBerry USB cable.
Bad is the device is STILL not recognized.
The drivers have been properly installed, there is no updating the drivers manually, effing Windows won't let me. What the hell can I do now?
If only Mobile Odin worked, or there were other methods, I wouldn't be going thru this mess...
Like where did I go wrong?
I would swap out Windows to Linux, but I don't see how that will get the device detected.
Matter of fact I was trying to install a Linux based OS from my flash drivd, and it corrupted it. Theres 8gb Ill never see again...
Any other ideas? Will Linux pick up the device?
EDIT: This USB unlike the others BRIEFLY detects it as a USB Device, then goes back to unknown when I uninstall it thru Device Manager
Click to expand...
Click to collapse
Are you plugging into a port directly on the motherboard? (IE: A port on the back of the machine.) Using an emulated port or hub can cause this at times.
FYI, there are 2 drivers. One is for when the phone is fully booted in Android. The other is the driver when in download mode. Have you tried using another machine?
Sent from my Nexus 7 using Tapatalk 2
I think your issue is driver related. I had similiar issues and updated the wiki with the drivers that ended up working for me.
Sent from my SPH-D700 using xda app-developers app
I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?
jconway1968 said:
I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?
Click to expand...
Click to collapse
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
bmg002 said:
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop
If you flashed TWRP 2.6.3, that's your problem.
Flash 2.6.1
This is the wrong section because it has nothing to do with ROM development.
With that being said if you can still boot into twrp you still have hope. Try loading a different ROM into an SD card using a converter and slide back in the phone to properly wipe first then re flash.
I don't understand why you can't get a proper USB connection going but above suggestion may solve it.
Sent from my SGH-T989 using xda app-developers app
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
jconway1968 said:
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop
Click to expand...
Click to collapse
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.
bmg002 said:
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.
Click to expand...
Click to collapse
Thanks for your help. Here are the answers to your questions:
I think there is something wrong with the micro USB input on the phone. I have reinstalled the drivers several times. I have tried different cables and different computers. I even tried the toothpick trick. No luck.
I do have a GN2. The SG2 is for my daughter...
It is a genuine SGH-T989 I checked under the battery.
soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...
jconway1968 said:
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...
Click to expand...
Click to collapse
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?
soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.
jconway1968 said:
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.
Click to expand...
Click to collapse
In twrp settings change it to use rm instead of formatting
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
jconway1968 said:
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?
Click to expand...
Click to collapse
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app
soupysoup said:
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???
jconway1968 said:
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???
Click to expand...
Click to collapse
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.
bmg002 said:
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.
Click to expand...
Click to collapse
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.
jconway1968 said:
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.
Click to expand...
Click to collapse
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.
bmg002 said:
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.
Click to expand...
Click to collapse
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.
jconway1968 said:
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.
Click to expand...
Click to collapse
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.
bmg002 said:
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.
Click to expand...
Click to collapse
You were great!!! Thanks again...
UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaĐ–)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...
msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app
Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.
msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?
i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.
Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol
In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4
Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.
Hi, Mates,
anyone can help to solve my problem ?, the problem is
My Note 2 is not dictating in comptuter but it is charging, I have tried the below solutions but none solved my problems
1. Cables changed - Not dictating
2. Connected in Different PCs (Window 7 & XP) - still not dictating
3. Kies - uninstalled and installed, different type of Samsung to PC software used - still not dictating
4. Flashed with full wipe - all top ROMS for note 2, - not dictating pc in any ROMS.
5. Flashed original stock firmware through ODIN - still not dictating phone with computer
Pls help to me solve my problem for pc connecting, except the above.
please share your knowledge for this matter
I think you mean "detecting", not "dictating".
I'm a little confused though... You say it's not detected on any PC, but you're able to flash with ODIN? If so, then your phone IS being detected or that wouldn't work either...
So what exactly is the problem?
If you flashed a rom through odin there is nothing wrong with your usb, check your drivers in device manager on windows if it was installed properly.
Sent from my SGH-T889 using XDA Premium 4 mobile app
FloatingFatMan said:
I think you mean "detecting", not "dictating".
I'm a little confused though... You say it's not detected on any PC, but you're able to flash with ODIN? If so, then your phone IS being detected or that wouldn't work either...
So what exactly is the problem?
Click to expand...
Click to collapse
Sorry for misspelled, phone not detecting in computer for normal mode but it is charging. And also download mode it is connected with computer in ODIN and flashed stock firmware as well as different types of recovery (Philz, Cwm, twrp ) . I Think some internal usb settings file erased ?. Is any internal setting in phone except rom cause all the rom I tried. In all rom it is not detecting. No problem in computer because all other Samsung phone works well. I have formated and reinstall all the drive for my computer.
waiting for u r solution
sak
express21 said:
If you flashed a rom through odin there is nothing wrong with your usb, check your drivers in device manager on windows if it was installed properly.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In computer all other phones are detecting. and tried different versions of Samsung usb driver. Also computer formated and re installed all the drives, so I think nothing problem with computer
sakkir said:
In computer all other phones are detecting. and tried different versions of Samsung usb driver. Also computer formated and re installed all the drives, so I think nothing problem with computer
Click to expand...
Click to collapse
My only guess is your usb flex is damaged.
Sent from my SGH-T889 using XDA Premium 4 mobile app
sakkir said:
In computer all other phones are detecting. and tried different versions of Samsung usb driver. Also computer formated and re installed all the drives, so I think nothing problem with computer
Click to expand...
Click to collapse
Well, I was going to suggest that you have a USB driver conflict, but if you reinstalled Windows, that's less likely.
When you reinstalled, did you install ANY other USB drivers first? What version of Windows are you running? Is it up upgrade install, or clean?
express21 said:
My only guess is your usb flex is damaged.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry I could not get USB FLEX what is it . ( if it is cable then I have tried in other cables)
FloatingFatMan said:
Well, I was going to suggest that you have a USB driver conflict, but if you reinstalled Windows, that's less likely.
When you reinstalled, did you install ANY other USB drivers first? What version of Windows are you running? Is it up upgrade install, or clean?
Click to expand...
Click to collapse
it was detecting in my 3 computers ( Windonws XP & 7 ). now in these computers phone is not detecting.
sakkir said:
it was detecting in my 3 computers ( Windonws XP & 7 ). now in these computers phone is not detecting.
Click to expand...
Click to collapse
OK, that's a little clearer. So your phone won't detect in any computer you've tried, but others do? Are you using the same cable for all?
Sounds to me like you might have a problem with the USB port that just isn't affected by download mode.
sakkir said:
sorry I could not get USB FLEX what is it . ( if it is cable then I have tried in other cables)
Click to expand...
Click to collapse
This is what im talking about, seeing that you have exhausted all your options im guessing this is the only thing that could be causing your issue.
Sent from my SGH-T889 using XDA Premium 4 mobile app
FloatingFatMan said:
OK, that's a little clearer. So your phone won't detect in any computer you've tried, but others do? Are you using the same cable for all?
Sounds to me like you might have a problem with the USB port that just isn't affected by download mode.
Click to expand...
Click to collapse
yes same cable using for other phones
sakkir said:
yes same cable using for other phones
Click to expand...
Click to collapse
I concur with express21, it's likely your USB port.
Are you still within warranty? if not, and you're feeling up to it, it's not an expensive repair...
http://www.ebay.co.uk/itm/USB-Charg...K_Replacement_Parts_Tools&hash=item2a3ecbf234
express21 said:
This is what im talking about, seeing that you have exhausted all your options im guessing this is the only thing that could be causing your issue.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so is it hardware problem in usb port ?. sorry, I think it not hardware problem, because, while flasing from one rom to other rom it happened.
FloatingFatMan said:
I concur with express21, it's likely your USB port.
Are you still within warranty? if not, and you're feeling up to it, it's not an expensive repair...
http://www.ebay.co.uk/itm/USB-Charg...K_Replacement_Parts_Tools&hash=item2a3ecbf234
Click to expand...
Click to collapse
As you know I am a flashing lot of roms, so it happned in that time, Now my latest cwm 6.0.4.3 is not able to flash rom, but it is possible to flash through TWRP and old version of CWM. so is it any connection with it.
sakkir said:
so is it hardware problem in usb port ?. sorry, I think it not hardware problem, because, while flasing from one rom to other rom it happened.
Click to expand...
Click to collapse
Note that each pin on the usb flex carries out a different function so its your choice if you want to change it.
Sent from my SGH-T889 using XDA Premium 4 mobile app
express21 said:
Note that each pin on the usb flex carries out a different function so its your choice if you want to change it.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi, mate
thank you for effort to solve my problem, anyway I solved it now. I have installed USB Tether software from play store and it worked. now phone is detecting in computer,
Thank you,
Best regards,
Sakkir.
FloatingFatMan said:
I concur with express21, it's likely your USB port.
Are you still within warranty? if not, and you're feeling up to it, it's not an expensive repair...
http://www.ebay.co.uk/itm/USB-Charg...K_Replacement_Parts_Tools&hash=item2a3ecbf234
Click to expand...
Click to collapse
hi, mate
thank you for effort to solve my problem, anyway I solved it now. I have installed USB Tether software from play store and it worked. now phone is detecting in computer,
Thank you,
Best regards,
Sakkir.
Ok good ?
Sent from my SGH-T889 using XDA Premium 4 mobile app