pc error "device descriptor failed" - Galaxy S6 Edge+ Q&A, Help & Troubleshooting

my s6e+ (g928f) will not connect to my PC. I do not believe it to be a driver issue because i have tried uninstalling reinstalling etc and tried barebone drivers.
Also the other day my phone stuck at 0% and would not charge, either wired or wirelessly. After 2 days it started to charge again.....
I thought my usb port was bust but this seems like a software issue, right? I obviously cannot connect to odin because it doesn't detect my device.
Is there such a thing as flashable stock roms i can flash in CWM, instead of using odin?
Its worth mentioning i did a couple weeks ago update to MM and then downgrade back to LP so i believe my modem and bootloader were updated during the process, would they have been downgraded back to the LP versions after restoring my nandroid backup?
I know this is a tricky one but i'm in a mess, help

Related

J16 Download Mode USB Failure

Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den
go_l_den said:
Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den
Click to expand...
Click to collapse
First and foremost make sure your plugging the usb into a usb port that is connected directly to the motherboard. Should stablize the usb connection. ( I had the same issue) Second flash to JFD via odin, then you want to upgrade to J16 via the vibrant version of kies mini. OTA update is not the greatest.
The JI5/6 updates don't wipe all data and apps, as they were designed to be OTA updates and not complete new installs. Can't have people complaining that an update wiped their entire phone, right? Stock JFD is a full flash which wipes all user data.
And yes, try to have it plugged directly into the motherboard's USB ports, make sure the contacts on the microUSB aren't corroded, and try deleting the Vibrant drivers and reinstalling them.
which version of odin you using? try 1.3 if not already
Kies or ODin
Nevermind I found it here ars.samsung.com/customer/usa/jsp/faqs/faqs_view_us.jsp?SITE_ID=22&PG_ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559
All you hace to do is go to USB settings and with the OTA update for J16, there's an option to choose "Ask what to connect" either samsung kies, mass storage, etc. Happen to me, did unroot, factory reset and there you go, just need to go to that stupid settings.

[Q] Soft Bricked handset

Hello,
I've got (had) an SM-G900W8 running the XtreStoLite v2.0 LP BETA5 ROM on the XXU1BOA3 kernel. I installed TWRP 2.7 via Odin, and left the latest modem and bootloader updates I got through KIES3.
At which point I got the chance to sell the handset on Kijiji, provided I could get the stock ROM back on.
I downloaded the latest Odin (3.09) and the correct Firmware for my handset from sam mobile, and factory reset the device. I pulled the battery, let it sit, and tried to flash once I got it back up in download mode, and it wouldn't work.
This isn't too much of a surprise to me, because since I flashed TWRP, Odin hasn't ever worked for me. Regardless of how many times I've tried to flash the modem and/or BL that XtreStoLite asked me to use in their how to thread, it wouldn't work. I was willing to ignore it b/c the ROM worked with the modem and BL it was running.
My problem is that once I tried to reboot, the system hung at the BL animation. I went back into recovery, and tried to move my backups off my external storage (I had 2 back ups that were about 2 or 3 gigs each, too much for the local storage) to the local card and restore (b/c TWRP won't restore from the external card) and the back ups failed.
Now I've got the BL screen, but it won't advance to the animation, and it won't boot to TWRP either.
I tried to restore from KEIS, but it says my device isn't supported by KIES 3 (it is). I could really use a hand here. Every time I try something this gets worse. I'm no pro, but I've had no problem figuring this out on my old HTC handsets.

[Q] Can't Update to Lollipop

Hello,
I've done quite a lot of searches on my problem, tried a lot of things, but nothing worked, so this thread is my last destination.
I wanted to update to Lollipop, but this doesn't work on my phone because my Knox counter was set to 0x1 (I've rooted my phone once.) A few months ago, I unrooted via the SuperUser app, which went well, I guess. Now I'm trying to flash the new stock firmware onto my phone, but it won't work. It gets stuck at "Get PIT for mapping...". I've tried reinstalling the drivers, use a different cable, remove all other USB devices, tried other USB ports. I've disabled Kies and antivirus software. I've also tried to flash a new PIT file but this won't work because it gets stuck at getting the PIT for mapping. I don't know what to do. I hope someone can help me, I really want to update to Lollipop.
Thanks in advance.
It's mostly solved by a different cable/different usb port. Do you have acces to another pc? Try it on a different pc.
KYRAMEIJER said:
Hello,
I've done quite a lot of searches on my problem, tried a lot of things, but nothing worked, so this thread is my last destination.
I wanted to update to Lollipop, but this doesn't work on my phone because my Knox counter was set to 0x1 (I've rooted my phone once.) A few months ago, I unrooted via the SuperUser app, which went well, I guess. Now I'm trying to flash the new stock firmware onto my phone, but it won't work. It gets stuck at "Get PIT for mapping...". I've tried reinstalling the drivers, use a different cable, remove all other USB devices, tried other USB ports. I've disabled Kies and antivirus software. I've also tried to flash a new PIT file but this won't work because it gets stuck at getting the PIT for mapping. I don't know what to do. I hope someone can help me, I really want to update to Lollipop.
Thanks in advance.
Click to expand...
Click to collapse
Why would you want to update to stock lollipop? Many people are unhappy and have bugs.
You're sooo much better off on kitkat...

I need Signed Stock/Any Firmware ZIP

Hello all,
I need to help a friend with his Note 4 N910W. The devices has some software issues but has a bad USB. Can not be flashed with Odin.
Already replaced the complete Charging port Flex/Module but still not connecting to PC for data. It doesn't also fast charge as I believe it uses the data pin to detect the charger plugged in.
I have tried rooting without pc then flashing a custom rom but can't find a rooting method.
Can anyone help or point to where a can get a ROM/FIRMWARE which is signed and can flash via the Stock Android Recovery cos I think it's the only next thing that can work.
Thanks.

Trouble restoring stock FW on S4 (I9505)

Hi,
I'm having some trouble restoring the official FW on my old S4. The idea was that I wanted to give it to another family member, and would prefer to give them the stock FW rather than deal with whatever potential issues a custom FW offers (don't get me wrong, custom FW tend to be awesome, but I hope you get the picture).
I downloaded the latest, official FW for this phone and proceeded to try and flash it using Odin (MD5 file specified as PDA). Alas, this got stuck on flashing BOOT. So I tried to hook up the USB cable to a different USB port (I was using a hub before) and that went through BOOT, but failed with a write error later d.wn the line. This, alas, has been my experience thus far. I've tried other Odin versions and another FW version, all failing with the write error.
I've even tried to use KIES to restore, but now KIES fails to recognize the phone at all (neither normally, nor in the recovery mode as the phone suggests, nor can I "initialize" the phone, as apparently the GT-I9505 does not support it).
I do feel not all is lost, as I can get into the download mode without issues, but I'm unsure how to proceed. Please help.
OK, I think I got it.
It turns out my USB cable was sh*t. With a new USB cable it works fine.

Categories

Resources