Hi all,
So, I'm trying to get the SGS3VZW unlock going, and I'm running into a real noob issue. I'm on my MBP running 10.7.4, I run the script, connect my phone and . . . nothing. It says it's still disconnected. What am I missing? I've got debug mode on, and I've tried a few different settings. Really confusing. I don't need to be in Odin mode right?
Jason
tnofuentes said:
Hi all,
So, I'm trying to get the SGS3VZW unlock going, and I'm running into a real noob issue. I'm on my MBP running 10.7.4, I run the script, connect my phone and . . . nothing. It says it's still disconnected. What am I missing? I've got debug mode on, and I've tried a few different settings. Really confusing. I don't need to be in Odin mode right?
Jason
Click to expand...
Click to collapse
I have 2 methods in my guide, section 1 and 7...pick whatever is easiest for you. Link in sig
Trouble is I'm running an MBP and Step 1 is what I'm doing, I just am not seeing the connection happening. Gonna try Ubuntu.
Related
Hi xda-dev..
Earlier this day, i was about to flash my lg gt540... But suddenly i got this problem. I followed a guide from here. Amazing guide, i just get stuck at an sertain point.
The "kdz_fw_upd tool" does not work! I have tried on 3 diffrent computers, and yes the program is running as administrator.
I get and error that say, i dont have the right/nessasary rights to run this program.
I can't see what i am doing wrong?
Any other that got this problem?
are you running windows enabler?
Yes i run windows enabler, i also ran it as administrator, and still nothing is happening.
Yes i run windows enabler, i also ran it as administrator, and still nothing is happening.
So what actually happening are you getting to the point were the phone is connected and its goes into download mode or can you not get the kdz flasher top open?
the kdz flashing tool wont work at all! Not with phone connected or disconnected. I simply wont open.
here i a picture.
h*tp://imageshack.us/photo/my-images/545/kdzerror.png/
Im danish to i translate it for you, as good as i can.
"Windows could not get acess to the device or file. You might dont have to right permissions to get acess to this element."
Same message on three diffrent Pc's....
Update!
I rebootet my PC in safemode, and there i am enable to open kdz_up_fwd, but because of safemode i dont load the drivers, and so my pc cant find the phone then....
Never heard of a problem like this.
First thing i suggest you do is put clockwork on and swiftdroid.
Heres a vid http://www.youtube.com/user/Tech2Tuts
That is the problem! I can't follow this guide because my rom dosent have fastboot. And i need fastboot to flash it to swiftdroid and that, but im still stucked, because i cant flash it with a rom with fastboot, when that bloody tool isnt working! :S
Problem: Cannot get my Samsung T959V to connect to the computer in order to flash/root. Always gives the same "USB Device Not Recognized" error when I plug it in to the computer.
My Progress: Before you guys throw this questions out, let me tell you what I have tried so far. I have been trying to get this damn thing connected to the computer for about 3 weeks now. I have sat down on my computer going through the xda forum in detail trying to find an answer. I know the process of flashing and the xda contributors have some great guides to help us along the way, a big thanks to all ur hard work, but no matter what, I cannot get the phone in download mode or get it connected to the computer.
* I have read the Download Mode post and tried all 5 ways without luck.
* Have read all things related to Keis Mini and how it sucks when it comes to the T959V and other ppl have had the same problem.
* Have tried connecting in Keis mode, usb debugging mode but still the same error.
If someone can help me get my phone connected to the computer, I am sure I can take of the rest since everything is available on the SGS4G Bible, thanks for that also.
Is there anything I have missed or not tried yet? Please help. Thanks in advance for anyone who reads this post as it is my first. Usually I don't have to post since all the documentation is always up-to-date and available but this problem is killing me
Additional Information: Bought the phone from a cell-phone store I use to work at. Has Android 2.3.6 on it. Have done the factory reset and tried to get it to connect, no luck. Not sure if it has been flashed before, pretty sure it hasnt but the flashed download mode method didnt work also. Have android-sdk installed and have tried pointing the .inf file to the google usb-drivers in the sdk, no luck. Download both 32-bit and 64-bit drivers for this phone from multiple locations, still no luck trying to connect. Have also tried multiple computers and multiple v9 cables, no luck.
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
hechoen said:
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
Click to expand...
Click to collapse
Yup tried both 32-bit and 64-bit drivers on multiple computers. Tried the download mode method u said also. Trust me have tried everything I have read about and know, but no luck.
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
hechoen said:
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
Click to expand...
Click to collapse
Yup it charges fine. Both when I plug it into the wall and the computer. What's a jig? Don't think I have tried that yet. If something can let me know for sure its a hardware problem, then I will stop obsessing over this, hahaha. Thanks for ur help btw.
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
hechoen said:
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
Click to expand...
Click to collapse
Awesome bro. I will see if I have time to make the jig, if not i will just order it.
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Seems like a driver error have u tried one of the heimdall one clicks http://forum.xda-developers.com/showthread.php?t=1358498
They will put u back to stock with a modified rooted kernel .
If anything try and manually point to the drivers in device manager. Or download android sdk and use the google drivers ?
rangergiya said:
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Click to expand...
Click to collapse
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
hechoen said:
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
Click to expand...
Click to collapse
As requested,
Build number: GINGERBREAD.VUVKJ6
Baseband version: T959VUVKJ6
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
hechoen said:
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
Click to expand...
Click to collapse
Will do. Thanks for ur help.
I downloaded the terminal emulator app and tried doing 'reboot download' but says 'operation not permitted,' any way to get around that? Or any other non-button or non-adb way to get into download mode? Other than the jig? Or is it possible to get su privileges on an unrooted device for the 'reboot' command to work in the terminal emulator app?
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
hechoen said:
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
Click to expand...
Click to collapse
Im trying it now but for SOC to work, i have to have the proper drivers to get my phone connected. Will see whether the drivers that come with SOC work for my phone.
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Have you tried using this DRIVER SWEEPER to remove the drivers?
eollie said:
Have you tried using this DRIVER SWEEPER to remove the drivers?
Click to expand...
Click to collapse
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
rangergiya said:
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
Click to expand...
Click to collapse
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
eollie said:
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
Click to expand...
Click to collapse
Thanks for that link. I will try it out and give an update here.
rangergiya said:
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Click to expand...
Click to collapse
Just to make sure you had usb debugging and allow non market apss both CHECKED right?
Hello
I picked up my S3 from VZ the other day and obviously the first thing I want to do is unlock the boot loader and root it. And it looks like CASUAL is the easiest way but I'm having some trouble with it..
CASUAL starts fine but I can't for the life of me get it to recognize the phone. It always says 'Link Status Disconnected'. Windows does recognize the phone (both as 'Media device (MTP)' and 'Camera (PTP)'). I enabled USB debugging mode but that didn't help either. I tried several USB ports and USB cables but that didn't help; and to rule out the PC being the issue I tried it on a different computer but had the same problem.
Either I'm missing something or the update that came over the phone when they activated it in the store isn't compatible with CAUSAL?
I'll keep trying different things but any help is appreciated.
Thanks!
quake3god2004 said:
Hello
I picked up my S3 from VZ the other day and obviously the first thing I want to do is unlock the boot loader and root it. And it looks like CASUAL is the easiest way but I'm having some trouble with it..
CASUAL starts fine but I can't for the life of me get it to recognize the phone. It always says 'Link Status Disconnected'. Windows does recognize the phone (both as 'Media device (MTP)' and 'Camera (PTP)'). I enabled USB debugging mode but that didn't help either. I tried several USB ports and USB cables but that didn't help; and to rule out the PC being the issue I tried it on a different computer but had the same problem.
Either I'm missing something or the update that came over the phone when they activated it in the store isn't compatible with CAUSAL?
I'll keep trying different things but any help is appreciated.
Thanks!
Click to expand...
Click to collapse
I used Adams casual over Ububtu 12.04 and it worked flawlessly. Do you have a Linux computer?
Update on CASUAL
joebob296 said:
I used Adams casual over Ububtu 12.04 and it worked flawlessly. Do you have a Linux computer?
Click to expand...
Click to collapse
I found out what the problem was... it was with the drivers (I kinda figured it was something mundane like that). I noticed the Windows Device Manager didn't have proper drivers loaded for all the devices associated with the phone. I went on VZ's website and downloaded/installed them. After that CASUAL recognized the device and I was able to unlock the bootloader, flash Clockworkmod, and get root access. :victory:
Thanks!
I have a recent thread ' A real amateur'
But I have started a new one as I have delved deeper into the depths of a dead phone
This is a slight continuation from the previous thread but what I've done now is more worrying.
I had wanted to put pie os on phone, updated twrp the wrong way and wouldn't go into recovery.
Tried to use guides on fastboot and I have had no luck at all with it. Tried SDK downloads and my pc wouldn't run the files( winrar and 7zip didn't show .exe files, just 'emulators'. Even right clicked to run as administrator but still, no luck.
Pc wouldn't recognise my phone also, even turning debugging mode on and alsorts.
So I thought i could run factory reset..? And as you'd of guessed, I have TOTALLY wiped the lot so there's no OS (was using resurrection remix) and now I can't turn phone on and no recovery and the only option available for the phone is fastboot but my pc won't recognise the device, nor can I get SDK, ADB or fastboot to work on my phone.
Have I completely killed my phone now???
I hope not and thank you in advance for the tremendous amount of help in advance and previously.
Someone help me
Hi
Have you tried this? it detects and installs a new rom by scaning the com ports, worked for me in the past.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
ricardopt78 said:
Hi
Have you tried this? it detects and installs a new rom by scaning the com ports, worked for me in the past.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Hi ricardopt78.
No I haven't tried this as I never knew about it but I will give it a go and let you guys know how I get on.
Thank you very much!! ?
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.