Develop Bugs

[Q] P600 - Unable to load FASTBOOT driver in WIndows

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

[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

[Q] Odin bricked. Can get to DL but Kies won't identify my phone?

I am something of a long time XDA user, having been flashing since the time of the HTC Wizard. But I had never bothered rooting my S3 until I decided I need to install music on the SD card using doubletwist.​
I installed the toolkit and the drivers properly but SuperSU 2.48 doesn't download (yes, I paid a donation), -error messages such as 'couldn't resolve host skipsoft.net' or 'HTTP doesn't seem to support byte ranges'
Option 1 loads what seemed to be an old (2.42?) version of the Odin flash tool: if I follow the instructions, the S3 does to into Download mode (with a message 'do not turn off target) and after about five minutes Odin shows FAIL on the TWRP recovery operation it seems to be executing. It then tells me to be patient while (I assume) rebooting but after about 30 minutes of waiting, the phone doesn't come out of download mode.​
I then rebooted and tried to flash again and again, the flash failed completely, and the phone seems bricked, giving the error message 'firmware upgrade failed, use KIES recovery.
It does go into download mode but when connecting to (newly updated) KIES, the model isn't detected in the recovery procedure so it won't either recover itself or give me a code to do the KIES emergency recovery.
Currently showing in DL is:
ODIN MODE
custom binary downloads YES (1 counts)
curent binary: Custom
system status: Official
qualcomm secureboot:enable
warranty bit:0
bootloader AP SWREV:1​
What is a recovery procedure please? KIES? Some other flasher? Some newer version of Odin?

Oh, and when I plug the phone into the computer, it suddenly recognizes it as an MSM8960, whatever that is?? Before the computer recognised it as the more normal SGT999. Also (this is obvious), the device is no longer recognized in Explorer once the device is connected if you connect it in DL.
Is an MSM8960 the same as a SGT999 in DL mode?

Sorry no one posted any tips or tricks on this request! In default, I ploughed ahead with the normal instructions, remembering that often when flashing doesn't work for no apparent reason, trying again does get everything to work
Re-flashed stock with Odin from download mode, which worked fine and unbricked phone. Then tried TWRP again, which worked fine as well, always providing instructions are followed.
Eventually found myself back at what looked like stock, but with message that I haven't rooted but would i like to do so now using the SuperSU that the toolkit said it was using? If so, down load it from the Playstore, which I didn't understand at all. I thought the playstore was against things like rooting?
Anyway, everything ran to completion, though I am still working on how to use DoubleTwist to transfer albums to the SD card on the Galaxy. (error message, apparently from SGS3 Easy UMS: 'You Do Not Appear to Have Busybox Installed', followed by loop of preparing SD card for mounting, mounting Then nothing by way of D card shows up in DoubleTwist)

Don't use toolkits, they are not updated and have caused many issues. To root, use towelroot

serio22 said:
Don't use toolkits, they are not updated and have caused many issues. To root, use towelroot
Click to expand...
Click to collapse
is there a list anywhere of devices which work with towelrroot please or is it only flavours of s3? i have a curious MK 6571 S6 which seems to defy identification because it isn't an iPhone knockoff and it is having the hardest of times addressing its hard drive. Whatever i try to install on it results in the error message that there isn't enough hard drive space to install. Towelroot also gives this error message which i believe to be entirely spurious, and it is a really tiny!! something appears to be preventing it installing any app on it which can read or influence any hardware on it?
(I also tried installing framarooot 193 but it gave me the same out of space error message)

licensedtoquill said:
is there a list anywhere of devices which work with towelrroot please or is it only flavours of s3? i have a curious MK 6571 S6 which seems to defy identification because it isn't an iPhone knockoff and it is having the hardest of times addressing its hard drive. Whatever i try to install on it results in the error message that there isn't enough hard drive space to install. Towelroot also gives this error message which i believe to be entirely spurious, and it is a really tiny!! something appears to be preventing it installing any app on it which can read or influence any hardware on it?
(I also tried installing framarooot 193 but it gave me the same out of space error message)
Click to expand...
Click to collapse
So it is an S6 knockoff? I'm not sure if there is a list but the s6 definitely is not compatible
Sent from my SM-G920T using Tapatalk

s3 recovery my testimony
licensedtoquill said:
I am something of a long time XDA user, having been flashing since the time of the HTC Wizard. But I had never bothered rooting my S3 until I decided I need to install music on the SD card using doubletwist.​
I installed the toolkit and the drivers properly but SuperSU 2.48 doesn't download (yes, I paid a donation), -error messages such as 'couldn't resolve host skipsoft.net' or 'HTTP doesn't seem to support byte ranges'
Option 1 loads what seemed to be an old (2.42?) version of the Odin flash tool: if I follow the instructions, the S3 does to into Download mode (with a message 'do not turn off target) and after about five minutes Odin shows FAIL on the TWRP recovery operation it seems to be executing. It then tells me to be patient while (I assume) rebooting but after about 30 minutes of waiting, the phone doesn't come out of download mode.​
I then rebooted and tried to flash again and again, the flash failed completely, and the phone seems bricked, giving the error message 'firmware upgrade failed, use KIES recovery.
It does go into download mode but when connecting to (newly updated) KIES, the model isn't detected in the recovery procedure so it won't either recover itself or give me a code to do the KIES emergency recovery.
Currently showing in DL is:
ODIN MODE
custom binary downloads YES (1 counts)
curent binary: Custom
system status: Official
qualcomm secureboot:enable
warranty bit:0
bootloader AP SWREV:1​
What is a recovery procedure please? KIES? Some other flasher? Some newer version of Odin?
Click to expand...
Click to collapse
hey friend, your woes sound alarmingly familiar to my own not so long ago. I will start this post by saying I am not going to come out and declare myself as anything but what I am, an average guy with an interest and at one time identical dilemma as yourself.
that being said what exactly are you trying to achieve an are you willing to start from scratch? are you backed up? these are my questions. in answering or perhaps confirming what you may know is that once rooted and subsequently bricked kies ceases to be a friend to your device and it is with odin that your phones future if is to have one lies. I personally have enjoyed much success with the program but at this point ive only done a handful of operations with it.
If what ive written has given you any encouragement please feel free to respond and I'll gladly explain what i did to restore my s3 because i wouldnt want to advise outside of something I have tried myself and know to be safe and conclude with a desirable result for you

Bricked VZW Note 4 N910v, cannot flash through ODIN either

Hello folks, im kinda desperate about this situation. I think i bricked the phone and everytime i try to boot it up it goes straight to the bootloader showing the following message "SOFTWARE UPDATE FAILED: Your device didn't update succesfully. Use the verizon repair assistant on a computer to repair your device and complete the update" . I've been looking for that "Verizon repair assistant" software everywhere over the internet without any luck. (Seems to be included on a CD). The phone is on the latest BOG5 5.0.1 Verizon's official firmware. I bought the phone as a Manufactured refurbished "unlocked" on Ebay and it came with that software version. Surprisingly when i received the phone i could not get any network signal with any carrier, like if it was a locked device. Looking for a solution i found some people complaining about BOG5 firmware causing this issue and they downgraded to the BOAF lollipop's first release and solved the issue so i got that firmware, samsung drivers, odin 3.10.7 and tried to flash it, it didnt work, the operation FAILED and it returned the following message : SW REV CHECK FAIL: (tz) fused 2 > Binary 1. Booted up the phone and no changes were made. I downloaded the full BOG5 and try to flash it to see if it helps with the initial problem (No network with any carrier) but returned the same failed message but this time the phone didnt boot anymore at this point. It seems to be locked (The bootloader) since on it says "SECURE DOWNLOAD: ENABLE". I cant do anything to the phone to make it work and i dont know what can i do to fix the phone and get it back to life again. I need help, im lost and desperate with this dead shiny white brick

Try using Samsung kies 3, you should be able to recover your phone to stock.

Any update on this issue? Would like to root my note 4.

TXtaco956 said:
Any update on this issue? Would like to root my note 4.
Click to expand...
Click to collapse
Cant root retail note 4 yet. Need to unlock bootloader or hack kernel.
As for bricked phone:
Thats a typical problem when you flash either wrong firmware or using bad USB connection.
There are 3 things you need to know before you flash.
#1 Flashing with ODIN requires samsung drivers installed
#2 Flashing with ODIN requires USB cable connected STRAIGHT INTO THE MOTHERBOARD (not unto USB hub or not even into computer front panel) Ports behind the computer that go straight into motherboard are 100% guaranteed to work properly.
#3 Each version of ODIN is recommended to flash different versions of firmware. For example:
Odin 3.10 is for Lolipop 5.0.1 (Firmware N910VVRU1BOAF)
Odin 3.0.9 is for JellyBean or KitKat 4.4.4 (firmware built versions N910VVRU1ANI1 or N910VVRU1ANJ5)
Download Odin from droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions
Download firmware from galaxynote4root.com/note-4-stock-firmwares (Make sure you chose correct model)
Inside ODIN, uncheck "Reboot" option.
When flashing is done, unplug the USB cord/Remove battery.
Reinsert battery and enter recovery mode by pressing VolumeUP+Home+Power and hold all 3 untill you see recovery screen.
Then chose to "clear cache partition" and press Power to confirm.
Reboot
done.
should have nothing lost if flashed with exact same firmware (i think it doesnt even matter if you flash with newer or older, but some apps may need to be reinstalled if fail to work due to firmware swap, so just uninstall those and reinstall)

Odin stuck in "SetupConnection...", impossible flash problem in Galaxy S9+ G9650

Odin stuck in "SetupConnection...", impossible flash problem in Galaxy S9+ G9650
I've been trying to install TWRP on my Galaxy S9 + G9650 for several days, but I can't, I even tried to install the original ROM, to see if the problem was TWRP, but without success yet ... I need help with Odin, now I used all versions of it, new and old, I already changed the cable several times, I used the original and other different cables, and even the Micro-USB to Type-C converter and still without success. What should I do now? I really need to ROOT, whether with TWRP or not. I tried to modify the original ROM using the Magisk flash method directly on the ROM, then I tried to install via Odin and still giving the error. I put the images attached to the post.
OEM: Unlocked
USB Debug: Enabled

Help??

try to change the usb port
restart the computer
try another usb cable
see if you have the driver installed

apaxtc said:
try to change the usb port
restart the computer
try another usb cable
see if you have the driver installed
Click to expand...
Click to collapse
I've tried another USB port and even another PC, but it still doesn't flash, and the drivers are ok, I have reinstalled them too. And on my Galaxy S3 I managed to flash the Stock ROM and the TWRP on it too, only the Galaxy S9 + that doesn't.

strange problem, is twrp good?
https://dl.twrp.me/star2lte/
I really don't know what to do anymore, maybe someone else will help you with an idea

apaxtc said:
strange problem, is twrp good?
https://dl.twrp.me/star2lte/
I really don't know what to do anymore, maybe someone else will help you with an idea
Click to expand...
Click to collapse
Yes, i used the correct TWRP for my phone model.

Strange as it may seem, I got it on an old PC, but on two PCs here in my house, an Intel LGA 1155 and another AMD AM4 couldn't, they crashed at SetupConnection, but when I went to my cousin's house and tried on the old PC his, an Intel LGA 775, DDR2 motherboard, Windows 10 64 bits and everything went well, installed normally without any error. I believe that Odin has to have this bug fixed, on the other PCs here at home, even on the USB 2.0 port it didn't work, but as strange as it was, on a PC 10 (or more) years ago it did... Now my device is finally rooted with Magisk and TWRP.

S9+ ODIN stuck at "ConnectionSetup" ?
Has anyone figured out what the issue is yet?
I'm using a 2020 ASUS Vivobook with Windows 10 (64-bit).
I'm trying to flash the G965U1 Unlocked/Unknown Firmware.
I have successfully flashed the same to another S9+ I had, and know the process fairly well.
USB Debug is ON
Used several different Cables.
Rebooted PC
Factory Reset the device.
Reinstalled the Drivers
Reinstalled the Patched ODIN
Tried a different Version of Firmware.
Any thoughts, advice, or revelations?

Natan_Gameron said:
I've been trying to install TWRP on my Galaxy S9 + G9650 for several days, but I can't, I even tried to install the original ROM, to see if the problem was TWRP, but without success yet ... I need help with Odin, now I used all versions of it, new and old, I already changed the cable several times, I used the original and other different cables, and even the Micro-USB to Type-C converter and still without success. What should I do now? I really need to ROOT, whether with TWRP or not. I tried to modify the original ROM using the Magisk flash method directly on the ROM, then I tried to install via Odin and still giving the error. I put the images attached to the post.
OEM: Unlocked
USB Debug: Enabled
Click to expand...
Click to collapse
Same model, same exact problem. I tried a different PC, but stuck on SetupConnection.
Do you remember which Odin version and drivers you used where you were successful?

Yes which drivers did you use that work? Android file host? Also latest odin? I get my sm-g965u tomorrow need to be prepared.