So, I've searched for multiple things revolving around the use of the snapdragon toolkit QCOM for the S3. Drivers have been installed, uninstalled, reinstalled, installed through Kies, installed through the toolkit, and just about every other way of doing it. Every single time my Samsung Galaxy S3 I-747 has been detected by the computer and "Drivers installed correctly."
Now, since I can't post to the developers section yet simply because I don't have 10 posts, I'm posting here. I've searched the forums and can not find anything regarding why my phone isn't being detected, as in the serial number showing up in the top left like it should. Rebooting the program, refreshing the program, going into every other phone type available, nothing works.
I'm kind of at a loss as to why I can't get the QCOM Toolkit to work. If anyone could post this in response to his thread for me that would be awesome because then perhaps he could assist me with it.
Thanks,
Aedaric
USB debugging checked?
Sent from my SCH-I535 using Tapatalk 2
sgtmedeiros said:
USB debugging checked?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Phaw! That's it. I had checked it on a previous flash before trying QCOM, I forgot to recheck it on the stock/rooted flash. Thanks and damn I feel stupid.
Related
I have been trying to root my gf's new epic 4G and after a few complications I am pretty sure I am facing the same issue I had with my Evo.
There were the instructions I used to fix it on the Evo: http://forum.xda-developers.com/showthread.php?t=695243
Would this same fix work on the Epic or would changes need to be made? Thank you in advance.
Idk and this belongs in the q and a form
Sent from my SPH-D700 using XDA App
What are you developing? Please post things like this in the q & a.thank you.
Idk what you did but I have never heard of those issues with this phone. Mod please move this tread.
Sent from my SPH-D700 using XDA App
For further clarification:
I was using the one click root after connecting the phone to the computer with win7 and getting drivers installed so that it was visible through adb with "adb devices". After beginning the rooting process it says it should take about 2 minutes but if it takes more than 5 to reboot the phone. After 20 minutes I rebooted the phone but now when it is plugged into the computer I go into devices manager and the phone no longer shows up with adb and mass storage, it shows up as a non-functioning device. When trying to update the usb drivers it says that they are already current and that the device is not functioning properly. After rebooting the computer and the phone I tried to connect it with adb and it identifies the device but shows it as offline no matter how many times I try killing or restarting the adb server. The only solution I have found to this issue once it happens is to go into recovery and wipe everything out and start from scratch.
After some searching it is clear there are tons of users out there that have apparently run into this same situation. Unfortunately all of the recommendations are "you need to update the usb driver" or "restart adb" and after the OP says that doesnt help then the thread goes dead and the OP typically resorts to using an sd card reader on their computer. This issue plagued the Evo for a long time until someone figured out that the recovery was setting the Evo into USB debugmode and fixed the issues for everyone with the above post. I am pretty android savvy and I am friends with a couple developers that I asked first but they said they werent sure and that I should ask the devs of the Epic. If I am in error mods please move or delete this post.
Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app
Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4
I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.
Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc
User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD
bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4
LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.
Yea, toolkit is the only way to go.
I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.
as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......
I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.
I have a galaxy s4 sph-l720. The phone will not connect to mobilego or kies over usb no matter if it is on the stock rom, custom-stock rom or a fully custom rom that has nothing to do with samsung. I have usb debugging enabled of course, tried using different cables and ports on the computer. I can connect to the phone in command prompt using adb and usb storage which makes me scratch my head in confusion of what could be going wrong. I am almost to the end of my rope with this and in hope came here for my last plee for help. I will answer any questions you all might have. Thank you - Jason.
Uninstall and reinstall drivers.
Brought to you by Sprint and the letters GS and the number 4
GiantJay said:
Uninstall and reinstall drivers.
Brought to you by Sprint and the letters GS and the number 4
Click to expand...
Click to collapse
I've done that probably 10 times now lol
I'm glad to have found out that it is something wrong with the computer and not the phone. It just worked with my laptop.
Hello.
I am having a problem with ADB and Bootloader drivers with my Nexus 4.
I've been sitting here the whole day trying to work it out but no luck (no tutorial helped me from google or xda)
Basically, the problem is ADB isn't working correctly and bootloader drivers are not recognized as well.
When I connect my device to my PC it finds the right driver (Android Composite ADB Interface) but when I try to use "adb devices" it returns "xxxxxxx(device serial number) offline"
When I go to bootloader mode the driver could not be found nor installed manually (when I direct to the directory with the driver it doesn't find it)
I want to downgrade 4.3 to 4.2.2 and cannot do it without the bootloader driver or ADB.
Strange thing is though, I have another Nexus 4 device with 4.2.2 (PAC Rom) and it's working flawlessly from the same computer.
1 more thing is, I've been trying to get to the point where I can approve my pc (RSA) without luck - been trying to delete the .android directory from my PC and also /Android/Misc/ADB directory from the phone, but nothing let me to that stage again.
I've tried 3 PCS, 1 Mac and no luck with anything.
Tried with Pac Rom and PA399 RC2 - AK KERNEL and regular ROM kernel.
No luck with anything.
What can I do that I haven't done yet?
Please Help.
Guy.
well i've been sitting and investigatin the whole day today as well without any luck.
already thinking about a malfunction with ths usb connection on the phone's side as the other nexus 4 device connects just fine with ADB, Fastboot etc.,
Can anyone shad some light?
Thank you!
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
GuyZapPa said:
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
Click to expand...
Click to collapse
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I am not sure that flashing the bootloader bypassed the problem, I am pretty sure it solved it.
I am saying that because I have deleted every possible driver, reinstalled, did not help.
Connected the phone to a new virtual machine I've created and was having same problem.
Tried it on a Mac, Same thing.
I've been dealing with this for quite some time, so I'm pretty sure flashing a bootloader solves the problem for people having it (not too many, as I've searched on the subject pretty much everywhere and no one ever said to flash a bootloader.)
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I thought just like you, and every tutorial or explanation on the web points to a driver problem.
It's all good, and as I said, hope it'll help others that suffer from the same problem
Good week.
Guy
Anybody know how to get my gs4 to recognize my pc. I have drivers installed through Samsung kies, and since my phone updated itself to mk2 im just trying to re root. But yes, usb debugging enabled, developer mode on, I can see the gs4 in the menu, but it wont tell me to authorize the computer with its rsa fingerprint
Try going and re installing the SDK from the website (I can't post links, sorry.)
The computer authorization feature is fairly recent and it is most likely that your version of ADB isn't new enough.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Could also be the usb cord your.using. also try different usb ports
don't use kies. i don't need safestrap, but keys caused me issues on the phone being recognized. never needed it on an i337, older mdl version.
Astrophysicist789 said:
Try going and re installing the SDK from the website (I can't post links, sorry.)
The computer authorization feature is fairly recent and it is most likely that your version of ADB isn't new enough.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yes! 15 Second ADB installer saved me. Our computer was having a hard time installing anything for the gs4, but the installer helped it finish. As soon as it did that it magically recognized each other and I authorized and rooted my device! going for battery life tweaks without changing the stock kernel as I can't...> Right now after 20% bat used I'm on track for 8.5hr theo. which will probably give me about 7+ on screen with about a 16 hour day. I'm excited. imagine that they say the new chips for next fall use 25% less power. One Of those devices rooted with a custom kernel would last a long time.