Device descriptor failed after bootloader update

[Mace73]

Hi all, learning fast, not there yet, so forgive me if I ask something less than brilliant here
I can't connect my Tab S 8.4 wifi to any pc anymore (tried 4 different PCs and 4 different cables) after upgrading bootloader with Odin last year.
I keep getting "device descriptor failed" in Device Manager (both win7 and win10).
My son did drop and break the usb/power port which I replaced myself. Could be a hardware error, but everything worked before and after my repair, just not after bootloader upgrade. Forgive me, I don't know which bootloader is currently installed, in any case one which works with android 5.1 and not with 7.1, which I unsuccessfully tried to flash.
COderbear was so kind as to direct me towards the bootloader, which I thought TWRP was.
Since I cannot connect to a PC, I cannot update the bootloader....catch 22...

Thx for ur input.
Ps Hardware failure is a possibility, but not conclusive guys. Tablet is working fine.

 

[stinka318]

In what way have you been flashing stuff have you been doing anything on trwp or oden......

 

[Mace73]

In what way have you been flashing stuff have you been doing anything on trwp or oden......

I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.

I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.

I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.

Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.

 

[stinka318]

I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.

I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.

I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.

Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.

I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........

 

[Mace73]

I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........

Yeah, but ur not me

 

[Mace73]

I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.

There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....

Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)

 

[stinka318]

I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.

There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....

Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)

Bootloader can only be updated with oden only any thing else won't work.......

 

[eugenblack]

It is not issue of fleshed software. I have this issue during last 2 months. Official service center didn't find any clue during 2 weeks so i get back my Tab. All story starts, i suspect, after 1 month using magnet cable. Then suddenly charging current start to be lower then usual (Galaxy Charging Current App) and i decide to check different chargers and PC. I found that tablet cannot connect to any PC - "device descriptor failed". During playing with "USB debug" on/off and USB modes i connected tablet to PC once. But during Odin flash it stuck in "Getting PIT file..." and i still didn't update anything.
I suspect that it is some hardware issue in part that responsible for USB communication.

 

[eugenblack]

Issue solved. Tried on different ports with combination USB-hub. On some ports it completely invisible, on some "usb device not recognized". But after two weeks once i get connected and Tab was detected - then immediately flash stock CQB1 with TWRP 3.1.0. Now it still detected by PC.
I suspect micro-crack in motherboard or some HW issue on some SW combination (modem SW).