This is becoming the hardest way to root apparently -_-
I`m trying to get z4root on to my Galaxy S Captivate from Rogers (SGH-I896)
I`ve downloaded the apk file and placed it on my desktop, when trying to copy the file to my phone I get this error message.
(I tried to post a picture here but apparently I need to post 8 times?*fail)
It says an unexpected error is preventing the operation.
Error 0x80070057: The parameter is incorrect.
clicking try again just prompts the message again.
Phone is connected in USB mass storage mode.
USB debugging is on.
It appears the app is no longer available in the market so is this the only way to get it on my phone?
I've literally tried downloading the apk 5 different times from different places and they all give the same message when I try to copy, also tried copying the file pretty much everywhere possible on the phone. any help would be greatly appreciated.
Phone is rooted, Cognition 4.1.1. I downloaded LCD Density, tried it and it caused TouchWiz to force close repeatedly so I rebooted through recovery and no problems with TouchWiz. When I mount my phone onto the computer, the computer recognizes its there but will not do anything.
At first I couldn't copy files to back up but not I can't open up the folder. Can anyone offer some help?
I've seen a few posts which noted that after re-installing the drivers, and re-setting the phone to usb debugging, it typically fixed this issue.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
i'm trying to help a friend out. he has a mesmerize, running froyo 2.2.1, and its on page plus (originally on us cellular). hes having a lot of problems with it, its very laggy and he can't install programs from the play store (package error) and the screen comes on at random times by iteself. few more problems but you get the idea. i too have a mesmerize that i've been flashing for over a year so it isn't nothing new to me. however, i can't seem to root or flash his phone for nothing. all of the versions of superoneclick hangs (not responding") on "waiting for device" step, i have samsung drivers installed and i can mount the sd card with no problem but adb cannot find device either, i've tried on three different computers. i tried un-checking usb debugging and re-enabling it, and i've put the usb settings on "ask on connection" and neither of them worked. i looked in the device manager, i don't have an "adb interface" category but my "samsung usb composite device" is listed under universal serial bus controllers category. i even tried the old z4root and it doesn't hang it just runs for about 30 seconds, vibrates twice and goes back the the app draw. no su app and busybox installer says the device is rooted but i can't install busybox. i can however browse the system files with root explorer and no superuser request pops up. i hate not being able to figure this out.
i was wondering if i can go ahead and odin cwm on it being that i can see my system files with root explorer. the last thing i wanna do is brick it being that it isn't mine.
How about starting from scratch?
Odin back to stock with this:
https://www.dropbox.com/sh/mpnagnzh1vckqqw/VuhLjOcqE7
Flash CWM for CM7
https://www.dropbox.com/s/ya0cwxp7b7k8840/cwm4_fixed_for_cm7-ODIN.tar
And this is what I flashed to gain root when I had my mez:
https://www.dropbox.com/s/ey979jdlwv4v2vg/UPDATE.zip
I was messing with my galaxy core prime (android 4.4.4) using a app to remove system apps that you can't with the stock app manager.. (no reason for crap like smartcard manager, bluetooth, wifi sharing..etc to be running when i haven't authorized such things, seems like security risk imo)
Was also editing the autorun list and messing with Norton applock and phone encryption settings to try to further secure it.
Welp, I f'ed things up because phone crashed and now can't do anything.. can't access home screen, settings, call/txt, nothing. So I booted into the stock bootloader and tried formatting the entire thing including cache..
Didn't fix the problem, can't finish the setup wizard without it crashing, get message saying setup, hangouts, and keyguard stopped working and then my phone bricks and can't do absolutely anything. No backup either.
I have been googling and googling for solutions but everything I read says to either:
-Reformat from bootloader (tried a 100 times)
-Wipe with TWRP or CWM (don't have either and can't access play store)
-Use Kies (won't detect my device since I can't enable MTP)
-ADB sideload twrp or cyanogen (cant, usb debugging probably not enabled since I formatted and no way to enable it since setup of android fails)
Odin can't detect anything either.. probably due to same reason. (Cant enable MTP or usb debugging)
So am I totally screwed? What are my options here?
I noticed the stock bootloader has a option to install from external storage.. can I put my sd card in a phone that does work and download twrp, cyanogenmod, (or ANYTHING else to fix this) to that, then put it back in my bricked phone and re flash it that way? That way I wouldn't need mtp or usb debugging... or won't that work?
Wasted so much time trying to fix this guys, googling and even formatted my pc removing Linux and reinstalling Windows hoping suddenly my pc would detect it.. atleast on linux when I used "adb devices" command it detected my device (trying to sideload anything didn't appear to work though, phone says error about verifying it and tries again and says completed and reboots but no sign of the rom I just supposedly sideloaded anywhere)
removing Linux and installing Window seems to have been a mistake because on windows using "adb devices" returns a blank list.. Tried different cords, ports, kies 2 and 3, reinstalling drivers, disabling firewall..etc but like I said even if I do get adb to detect it, what can I do from there without mtp or debugging?
Sorry for wall of txt, just want to be descriptive as possible so I don't get all replies telling me to try stuff that I've tried 100 times or just flat out won't work for my particular problem because of the above reasons..
will be sincerely grateful to anyone that took the time to read this and try to help me.