[Q] P600 - Unable to load FASTBOOT driver in WIndows - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Hello...
First, the environment: P600 32GB US version. Running Windows 8.1 on my laptop, SDK installed fine. ADB drivers working with no problem.
Here's the problem: I was running the stock ROM with root for a very long time, but I decided to try the unofficial port of Cyanogenmod 12. It installed just fine, but in the process it whacked my TWRP installation on the tablet. When I rooted the tablet I had been running Windows 7 and the Samsung drivers worked without any issues, both ADB and Fastboot.
No matter what I try now, I can't get the Fastboot driver to load - the tablet is recognized as a Samsung USB composite device, but Fastboot does not see it and whenever I try to change to most any other driver, the install succeeds but the device can't start (the dreaded Code 10).
Of course, the stock recovery won't let me load anything that isn't signed by Samsung, and I can't find a stock signed image anywhere, so I can't even get back to the stock ROM. And Windows 8.1 on multiple machines seems to be working the same way, so unless I can get the right driver installed and working I can't flash anything from my laptop. Mobile ODIN doesn't support the tablet, Goo.IM Manager installed, but it apparently does not recognize the tablet either, so I can't flash anything on the tablet side, either.
Does anyone have any ideas on how I can get this to work short of throwing up a Windows 7 VM and trying that?
-Dave

Have you tried installing Kies and using the drivers it provides? Or if you already had Kies installed, going to Tools > Reinstall device driver?
Different USB cable?

blindmanpb said:
Have you tried installing Kies and using the drivers it provides? Or if you already had Kies installed, going to Tools > Reinstall device driver?
Different USB cable?
Click to expand...
Click to collapse
Thanks. I tried Kies and three different cables as well. Nothing doing. I think because the Knox counter was tripped Kies connects to the tablet and then says it is unsupported and disconnects. ADB driver works fine independently, but when running Kies it does the same thing - connects, recognizes the tablet as a P600 but then disconnects because it is unsupported.
Because of the Knox thing I am pretty sure Samsung will charge me an unspeakable amount to reflash this thing, so I would love to find my own solution.
-Dave

da_ferreira said:
I think because the Knox counter was tripped Kies connects to the tablet and then says it is unsupported and disconnects.
Click to expand...
Click to collapse
I doubt this is the issue, the Knox counter has been tripped on my P600 since a week after I got it, and I've taken every firmware update via Kies.
Does it give you this message only when the device is in download mode, or do you get it with the tablet powered up normally?
AFAIK Kies won't recognize your tablet unless it's been started normally with Android running, and if it's still got anything other than a stock ROM on it, that message isn't surprising.
I'm also running Windows 8.1 on both my laptop and desktop and have never had any connection issues
If all you want is TWRP back, have you tried Flashify?
https://play.google.com/store/apps/details?id=com.cgollner.flashify

blindmanpb said:
I doubt this is the issue, the Knox counter has been tripped on my P600 since a week after I got it, and I've taken every firmware update via Kies.
Does it give you this message only when the device is in download mode, or do you get it with the tablet powered up normally?
AFAIK Kies won't recognize your tablet unless it's been started normally with Android running, and if it's still got anything other than a stock ROM on it, that message isn't surprising.
I'm also running Windows 8.1 on both my laptop and desktop and have never had any connection issues
If all you want is TWRP back, have you tried Flashify?
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
I've been pretty much throwing anything at the problem - I did try Flashify, and it tells me that it does not recognize the device. The tablet boots, it runs fine (no weirdness), I have root but no ability to flash anything.
As far as Kies goes, even when running normally (meaning not in download) Kies tells me the device is unsupported.
My goal is to be able to get to something so I can flash stock in case I decide to sell the tablet. I love it, but it already feels like an orphan and not because of my screwing things up. Kinda feels like Samsung abandoned it not long after release in favor of the Tab Pro line. Just my opinion, I could be wrong.
-Dave

Related

Stuck recovery

I was preparing to flash the stock EC05 rom with odin and did a full wipe of everything. But it seems I can't get odin to recognize the phone is plugged in (I can get to download mode, but it never shows up in Odin).
Not I'm stuck in recovery with no backup, and can't do anything.
I also can't get windows7 or adb to recognize the device.
I have the drivers I used when rooting the phone, and they don't seem to work.
Windows says "usb device not reconized... the device has malfunctioned" etc.
I have tried many cables and many computers, and nothing seems to work.
My last resort is to buy yet another cable, one recommended in another thread, but I have already bought a few cables designed for this phone, blackberry, and one just for data.
Is there anything I could flash from recovery to at least allow me to boot?
Souzhi said:
I was preparing to flash the stock EC05 rom with odin and did a full wipe of everything. But it seems I can't get odin to recognize the phone is plugged in (I can get to download mode, but it never shows up in Odin).
Not I'm stuck in recovery with no backup, and can't do anything.
I also can't get windows7 or adb to recognize the device.
I have the drivers I used when rooting the phone, and they don't seem to work.
Windows says "usb device not reconized... the device has malfunctioned" etc.
I have tried many cables and many computers, and nothing seems to work.
My last resort is to buy yet another cable, one recommended in another thread, but I have already bought a few cables designed for this phone, blackberry, and one just for data.
Is there anything I could flash from recovery to at least allow me to boot?
Click to expand...
Click to collapse
Have you tried downloading the drivers fresh from Samsung? How about different USB ports? Sounds like bad drivers though. The first time I used Odin, Windows used the drivers I installed plus got some others from Windows update. Took about 10 minutes for it to find my phone.
Which version of Clockwork are you on? If not stock you can go here and flash the EC05 stock ROMS:
http://forum.xda-developers.com/showthread.php?t=1027904
Classic sign of bad drivers or a bad cable. Don't waste your time on the stock cable - get another, and plug it into a different port. Reinstall the drivers if you need to.

Odin doesn't recognize my Samsung Galaxy Note II GT-N7100

Ok, so my problem is the next one:
I have rooted my phone now 6 months, from then I haven't used ODIN. Now I want to install android 4.2.2 so I want to unroot my device, when it's turned on, it is recognized by computer and I can share files, photos etc.
Short version to the problem: ODIN doesn't recognize my Samsung Galaxy Note II when it's in download mode, even if I followed all the steps correctly.
I tried:
- Using another USB cable
- Using another USB port
- Followed the instructions - 1. Turn off the device 2. Enter download mode 3. Connect it 4. Open ODIN
None of above helped me. It's not from the drivers or kies, because my phone is recognized by computer.
I really try from a week to solve the problem from tutorials or internet, but I couldn't find any solution so I hope someone could help me.
Try to uninstall Kies. It really messes things up. Leave only the drivers, or uninstall everything Kies related and put these drivers. Then try again.
Experienced much the same symptoms today, not having updated recently, phone would be recognized by Kies, by the PC, but not in download mode by Odin. Tried removing Kies, Kies Air, previous drivers, reinstalling drivers mentioned above. Nothing. And then I happened to click on an older version of Odin accidently and it recognized my Note 2 SGH-i317m almost immediately. Odin3 ver 1.82. Have no idea why but for your information in case it helps you.
Makes sure kies is not running in background. End the process from Teal manager and try again.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Note note not recognosed by Note 2
I rooted My note 2 about a month ago and now i want to install the stock ROM back. but then i connect my Note 2 to my PC and run Odin, its not recognised. i have removed kies from my PC and installed the drivers as mentioned.
i restarted m PC and disable the antivirus as well. Still then, no change.
Can some one please help me out with this issue
Hi,
I have similar problem with my Note II. When I had rooted phone, computer didnt recognize my phone. I tried to reinstall drivers, using Toolkit or manually, but nothing works. Samsung Kies I havent installed on my computer, I tried to install Kies too, but Kies doesnt recognize phone too. So I installed mobileOdin into my phone and unrooted it, but "force root" was checked. So now I have "unrooted" phone with no working superuser because some binaries are missing, I have stock recovery, my computer still doesnt recognize my phone. So I cant install mobileOdin because I havent root permissions, and I cant do anything else. So what I have to do if I want to make my Note II working well with computer? I have no ideas.
Btw, another usb cabel I tried too...
Thanks for reply

[Q] Nexus 7 won't connect to Windows, can't root, can't flash - stuck?!

So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
darnocs1 said:
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
Click to expand...
Click to collapse
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
darnocs1 said:
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
Click to expand...
Click to collapse
Cool. Glad it worked out for you. :good:

[Q] Kies 3 Unsupported device alert

Does anyone else get an error with Kies 3? when I connect my Edge Kies gives me an error! I want to perform a device recovery via Kies that's my last hope. I tried to root my Edge and now I'm stuck with a bricked phone and yes I have tried Odin 3.10.6 and regular s6 Auto Root from Chainfire as well. nothing works for me, I've looked everywhere to find the G925t firmware but no luck again. I'm really screwed.:crying:
Same
I'm guessing kies wont recognize it til after 4/10 since technically nobody is supposed to have it yet. Just a guess though.
dcmtnbkr said:
I'm guessing kies wont recognize it til after 4/10 since technically nobody is supposed to have it yet. Just a guess though.
Click to expand...
Click to collapse
same issue here. Had to use smart switch which is not as efficient from my old galaxy to the new one. Transfer stopped and had to restart 2nd time which did seem to complete.
Helium is much better for transferring data to new phone..
Same issue here. New Galaxy S6 and Kies 3 won't allow it: Unsupported device alert. WFT?
acana79 said:
Same issue here. New Galaxy S6 and Kies 3 won't allow it: Unsupported device alert. WFT?
Click to expand...
Click to collapse
Do the following: open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Use Samsung Smart Switch instead. It has replaced Kies for the newer phones.
Here is my video showing it being used to flash Stock Firmware to the Edge.
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Supersport, I have a SM-G900A (Galaxy S5 ATT) and Kies 3 and Smart Switch says it is an unsupported device. I got to the part to enter the model and serial and it comes up unsupported again. I tried a different USB cable and also tried Smart Switch on a Mac. The white USB3 Samsung cable does not allow the phone to be recognized by the Mac so I used an old USB2 cable and it hangs on "connecting to your device".
I tried downgrading to Android 4.4.2 so I could root it and it is in the "firmware encountered an issue" screen with the yellow triangle. Ack!
Boysterload said:
Supersport, I have a SM-G900A (Galaxy S5 ATT) and Kies 3 and Smart Switch says it is an unsupported device. I got to the part to enter the model and serial and it comes up unsupported again. I tried a different USB cable and also tried Smart Switch on a Mac. The white USB3 Samsung cable does not allow the phone to be recognized by the Mac so I used an old USB2 cable and it hangs on "connecting to your device".
I tried downgrading to Android 4.4.2 so I could root it and it is in the "firmware encountered an issue" screen with the yellow triangle. Ack!
Click to expand...
Click to collapse
It sounds like the MAC had issues with installing the driver. I'm not positive if your model is supported by Smart Switch yet, but I would suggest using Smart Switch as KIES has stopped official support for most of the newer models. If it's not supported yet, it should be soon. They keep adding devices. When I got my S6 Edge, it took about a week for it to be supported, but that's when Smart Switch had just come out too. Wish I was more help.
Anyone else have success getting this model to flash???
Bootloop
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
I seem to be having the same issue. Tried to manually update my phone via Odin but nothing has worked so far.... Now I just get an error on my phone that says
"An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
What am I missing here?? It's a Samsung phone, and it's been around for over a year (S6 Edge T-Mobile)...
ieatcalcium said:
I seem to be having the same issue. Tried to manually update my phone via Odin but nothing has worked so far.... Now I just get an error on my phone that says
"An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
What am I missing here?? It's a Samsung phone, and it's been around for over a year (S6 Edge T-Mobile)...
Click to expand...
Click to collapse
If nothing else is working, you can try this for the T-Mobile S6 Edge. ONLY the T-Mobile S6 Edge is supported, so PLEASE verify it's the correct one.
https://mega.nz/#!H0hz2AQJ!iDzw_SwCL7qpJnZ8Y_8EDSrSgvAHK_hT93igXHOlm3A
It's a known working version of Odin, the Samsung Driver Package, and Firmware. Place your phone into Download Mode before using.
If any issues, let me know and we'll work through them.
SuperSport said:
If nothing else is working, you can try this for the T-Mobile S6 Edge. ONLY the T-Mobile S6 Edge is supported, so PLEASE verify it's the correct one.
It's a known working version of Odin, the Samsung Driver Package, and Firmware. Place your phone into Download Mode before using.
If any issues, let me know and we'll work through them.
Click to expand...
Click to collapse
No worries, I got it working! Thank you!
SOLUTION FOR ANYONE HAVING ISSUES STILL
1. Make sure you have Samsung Smart Switch Downloaded
2. Make sure Smart Switch is updated.
3. Click "more" across the top
4. Click "Emergency software recovery and initialization"
5. Click "Device initialization" across the top
6. In the model name box, type in exactly your model number. It is case sensitive. (for me, it was located on the back of my phone on the bottom named "SM-G925T)
7. It will then ask you for your serial number which can be found by holding POWER, HOME, and VOLUME DOWN
8. PROFIT$$$$$$$
Will this wipe the data like recorded audio and video files? This phone belongs to a friend with cancer and I'm trying to unload message he recorded for his family. I need to recover the data first and foremost and then getting the phone operation is secondary. I've got conflicting reports of what a firmware flash will do to recorded media files. I'm hoping the SDcard area will be unaffected but I need to know beyond a shadow of a doubt before I do anything.
Yes it will, it will behave like a factory reset. It will ask you to backup your storage content if it recognizes your phone you may be able to fix it.
Pp.
samanbabah said:
Do the following: open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
Thank you so f much!! I avoided waiting 8+ hours to download just the firmware. This method took less than half an hour!
*I dont know if doing something against the rules for replying to this really old thread but I am just thankful for this easy, simple method; I miss using the spen

Device descriptor failed after bootloader update

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.
In what way have you been flashing stuff have you been doing anything on trwp or oden......
stinka318 said:
In what way have you been flashing stuff have you been doing anything on trwp or oden......
Click to expand...
Click to collapse
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.
Mace73 said:
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.
Click to expand...
Click to collapse
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........
stinka318 said:
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........
Click to expand...
Click to collapse
Yeah, but ur not me
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)
Mace73 said:
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)
Click to expand...
Click to collapse
Bootloader can only be updated with oden only any thing else won't work.......
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.
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).

Categories

Resources