HELP! Failed root on samsung galaxy player 4.0 - Samsung Galaxy Player 4.0, 5.0

Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?

Have you loaded an insecure kernel using Odin?

SusieGalaxy880 said:
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Click to expand...
Click to collapse
The easiest way to gain root would be to flash a ROM that has root already. Such as this stock ROM: http://forum.xda-developers.com/showthread.php?t=1512331

nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)

These kinda more difficul steps,, and i dont wanna mess any of those because if any step goes wrong, I duno how to fix it. Aren't most people use the easy way to superoneclick to root and successful? I just want to know which step I did wrong for my fail root. I dont wanna mess with any deeper or more diffiuclt stuff.

SusieGalaxy880 said:
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
Click to expand...
Click to collapse
You shouldn't have connected mass storage.

I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?

SusieGalaxy880 said:
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
Click to expand...
Click to collapse
From my experience just have Windows 7 doesn't ensure have framework 4+ so check for a download on that.
If your USB debugging mode is ON then you shouldn't get the "connect mass storage" option on the device at all, so double check that (uncheck and recheck it if necessary.
Personally I choose to skip Kies entirely and just download the drivers only, but the first time you plug the player in with Debugging on windows should do it driver search thing down by the clock and it installs (i think 3) different drivers for the player (different then the mass storage driver) if you jumped in to superoneclick before that finished that may have been part of the problem, if you didn't get those to install then sounds like a driver issue.

I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.

SusieGalaxy880 said:
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
Click to expand...
Click to collapse
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?

I didnt restart my device before rooting.
I got the superoneclick from XDA main page the offical one with 500+ page of posts and reply. "Superoneclickv2.2 -shortfuse.zip"

Try using doomlords rooting toolkit, it worked for me.
http://forum.xda-developers.com/showthread.php?p=18805532

thanks for info, but I duno how to use the DooMLoRD's Easy Rooting Toolkit. Any instruction? I have no idea why my device is so diffiuclt to root, as other people rooted very easy

I used version 2.3.3 to root mine.
Got to shortfuse.org and scroll down to the 2.3.3 download link.

I tired the 3rd time today, failed again, same outcome. This time I follow each step carefully, and I used superoneclick v2.3.3 Before ROOT, I make sure all the "READY TO USE" check mark on. But still hang at Shell Rooting device step #5. I patient waited for 20mins, still hang at this step.
I shoulda try root when I got it first day. Is there possible some mess up app might cause this? I never heard anyone have any diffiuclty Rooting their galaxy player 4.0 YP-G1 US version with superoneclick after so many tried. I officially give up. I only have this device for 1 week..............
Kernal Version 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build # Gingerbread.UEKI8
Firmware V2.3.5
Model Number: YP-G1

I found a very important issue might cause this failed. When I check the unzip folder, the Expoits folder IS NO FILE, EMPTY, but when I check the original zip file, it has 3 important files "GingerBreak,psneuter, zergRush" files (on the v2.2) I try unzip on desktop, pull out this Exploit folder, pull out the file, none work. I even uninstall winRAR and restall the newer version. These 3 files on the exploit folder in superoneclick v2.2 seem CANNOT pull out of the zip file no matter what I try. I think on shell Rooting device step #3 started the problem cuz cannot locate these few important exploit files. I just found out the unzip folder have no those file (psneuter,zergRush), while the original zip file has, and I cannoot pull out those file out of the zip folder NO MATTER WHAT I TRIED. Both superoneclick v2.2 and v2.3.3 exploit folder, i cannot get those file out of the zip folder.

Got rooted successful the 4th tired. Problem is my antiviurs always remove the psneuter & zergRush files in exploit folder when I extract everytime. And I didnt notice this problem. So I was rooting without these 2 important files in superoneclick folder. Now I disable antivirus, so i can extract those file and start rooting, after done rooting, i turn antivirus back on.

another problem
daniel644 said:
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
Click to expand...
Click to collapse
can someone help me i have the ``firmware uprade encountered....``
i can go to the the warning but
-if i press up to continue it return to firmware....
-if i press down the same thing
thanks.

Related

[Q] Can't get USB connection with Window 7 prof

I previously rooted my phone without difficulty. Using titanium backup and an number of other apps that required superuser/root acess. I am now trying to flash a Froyo rom. I had upgraded the home PC to a win 7 Pro (64 bit) machine and for some reason I can not get USB drivers to work. I have download drivers from several different threads. SOme fail to load while others seem to install. The Fascinate is recognized but not the modem and I can not get odin to see the device in software download mode.
Any thoughts?
Your best test of whether drivers are installed properly is to install adb and do 'adb devices'. If one shows up in the list you are installed correctly.
You may have an incorrect driver installed. The best place to download these is Samsung directly. If all else fails you can try a different computer and/or heimdall instead of odin.
Swyped w/ XDA App. A clean tie attracts the soup of the day.
get the drivers from samsung, or one of the noob threads, and be sure u mount then first go to setting/applications, make sure unknown sources is checks, and then go to development and make sure usb debugging is checked, then plug it in, and on ur phone u should get an option in notification bar that says transfer files.. click on it.. and then click mount.. n try again.. u should have to do this at least once on every phone to get the drivers properly installed.

[Q] SGS 2 Drivers (CDC Serial & SAMSUNG_Android)

Hi,
Does somebody know where I can get the drivers in title!!
I have a brand new SGS2 and would like to root the thing. But it's a bit more tricky the my old SGS
In my device manager win7 x64 - I get warning on "CDC serial & SAMSUNG Android"
I have Kies and Android SDK installed and it will still not find the drivers.
Thanks in advance.
have you plugged in the phone while kies is running mine wouldnt install the drivers till i did that.
Its the same for me on one of my computers. It was all done correctly, but no drivers are found. Ive tried repeatedly and have uninstalled and reinstalled Kies but it makes no difference.
Go to Kies directory in Program Files you will find a directory something like "USB Driver"
inside of it there's USB Driver for Galaxy S II, install it.
Problem solved.
MAJED.y said:
Go to Kies directory in Program Files you will find a directory something like "USB Driver"
inside of it there's USB Driver for Galaxy S II, install it.
Problem solved.
Click to expand...
Click to collapse
maybe this will help someone as well. I had the same problems as you above with these driver not installing. So what i did was the following
installed samsung kies V.2.2.2.11044 with the tel hooked up to the usb and the computer. I did not have USB debugging on in the : settings/applications/usb debug (unchecked)
then I let kies start did not find the drives, so I unhooked the tel. ( galaxy s2) and I enable USB debugging, plugged it in again, started kies and it found all rivers.. NOTE.. it found all drivers but I do not use kies other then to get the drives, I use Odin 1.8.5 which after this , Odin worked just fine.. so you can still upgrade, just without using this Samsung Kies. which sucks anyway
best
This worked for me:
Install kies and open it, connect you phone and let windows attempt to install drivers, then click tools drop down menu and click 'install driver', kies will then download the drivers for the phone.
kies v. 2.0.1.11053_99
Kies -> Tools -> Install driver
XD
it worked!
mojolive said:
maybe this will help someone as well. I had the same problems as you above with these driver not installing. So what i did was the following
installed samsung kies V.2.2.2.11044 with the tel hooked up to the usb and the computer. I did not have USB debugging on in the : settings/applications/usb debug (unchecked)
then I let kies start did not find the drives, so I unhooked the tel. ( galaxy s2) and I enable USB debugging, plugged it in again, started kies and it found all rivers.. NOTE.. it found all drivers but I do not use kies other then to get the drives, I use Odin 1.8.5 which after this , Odin worked just fine.. so you can still upgrade, just without using this Samsung Kies. which sucks anyway
best
Click to expand...
Click to collapse
This worked a treat - thank you dude!! lifesaver!
xtrememorph said:
Kies -> Tools -> Install driver
XD
Click to expand...
Click to collapse
i did this, then i get a Windows 7 popup on the bottom right saying installing drivers, but it fails and both CDC Serial and SAMSUNG_Android have a red X beside them. so frustrating
Kies
I have tried all of the suggestions above except turning on USB debugging. None have worked.
different attempts give me different messages
Installing drivers does nothing.
Sometimes plug in says missing MTP
Sometimes plug in says missing CDC
Sometimes device recognized completely.
All cases, first plug in while kies is running causes kies' "devicemanager.exe" to crash followed by infinite connecting loop.
Any ideas PLEASE PM let me know
Manually install drivers but instead of choosing Samsung MTP drivers choose Mass Storage Drivers.
Update Driver >> Install from PC >> First Browse to the Program Files/Samsung/usb drivers folder then >> I want to choose from PC >> Choose Mass Storag e Driver.
Worked for me just now.
not working
I have tried all solutions from this thread. Still have the CDC error in my device manager on the PC.
x86
W7
Anyone can help me?
Thank you!
Noonski said:
Manually install drivers but instead of choosing Samsung MTP drivers choose Mass Storage Drivers.
Update Driver >> Install from PC >> First Browse to the Program Files/Samsung/usb drivers folder then >> I want to choose from PC >> Choose Mass Storag e Driver.
Worked for me just now.
Click to expand...
Click to collapse
Great fix, worked for me. Thank you
I Solved the issue this way::
Issue: Samsung Galaxy SII didn't find driver after kies update.
Solution: Uninstall the old kies completely + Samsung USB Driver..... which is installed.
Delete the files completely from program files to make sure we get everything new during next install... U may need to use a safe mode boot sometimes for a full delete.
Download latest kies from samsung.com to get an original fresh one.
Then do the install.. Plug in phone...
Hi all,
I have the build 2.1.0.11095_121 and I can get my sg2 to be recognised anymore.
I have tried uninstalling and debug and off. No joy.
Does this mean I won't be able to root or load apps on from eclipse?
Any ideas to fix arggghh?
I have tried all above solutions but this what helped me was go to Kies directory -> USB Driver and start setup All problems gone and Kies is running now.
Always the simplest solution is the hardest to find
mmiesz said:
I have tried all above solutions but this what helped me was go to Kies directory -> USB Driver and start setup All problems gone and Kies is running now.
Always the simplest solution is the hardest to find
Click to expand...
Click to collapse
this worked for me ! big props
is there any alternative way to install drivers without kies?
i dont wanna install kies :S
sadicim said:
is there any alternative way to install drivers without kies?
i dont wanna install kies :S
Click to expand...
Click to collapse
Go to my 4shard, link in my sig, drivers are in there. (4icon) (its been updated to the newest one as of December 2011)
Thanks Veyka, your file on 4share did the job.

[Q] samsung fascinate driver install problems!!! hELP!!!

i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!

[Q] WHO's FEELING GENEROUS (ODIN,KIES ISSUES etc)

Hey gang, needing some help in regards to Odin and Kies.
Apologies if this has been answered but ive been all over the net trying to find a soloution and as Princess Leia says, "youre my only hope".
Ok the main issue im facing is ODIN doesnt recognise my phone when connected.
The installed software i have is as follows:
Android version: 2.3.5
Baseband version: I9100XXKI3
Kernel version: 2.6.35.7-I9100XXKI3-CL577579 [email protected]
Build Number: Gingerbread.XXKI3
Now i can put my unit into download mode but ODIN doesnt pick up on it.
I also have a connection issue with Kies not seeing my phone either, although when i connect my unit to my pc (alienware m11xr2) it gives me the option to connect as USB storage..?
What im wondering now is there any soloution to this?
Can i root from the unit directly as i cant get ODIN to see my unit?
Thankyou in advance for any help given to both issues
Uninstall/reinstall Kies on your PC (with a reboot of the PC after each step). Try different USB cables, try different USB ports. When you're using Odin, check Task Manager in Windoze & make sure Kies isn't running/kill it if it is running (Odin & Kies don't play well together tho you need Kies drivers to use Odin).
Try a different PC/different OS if all else fails.
You can't root directly from the phone as far as I'm aware. If you're using Odin 3 v1.85, try Odin 3 v1.3.
apanayis said:
Hey gang, needing some help in regards to Odin and Kies.
Apologies if this has been answered but ive been all over the net trying to find a soloution and as Princess Leia says, "youre my only hope".
Ok the main issue im facing is ODIN doesnt recognise my phone when connected.
The installed software i have is as follows:
Android version: 2.3.5
Baseband version: I9100XXKI3
Kernel version: 2.6.35.7-I9100XXKI3-CL577579 [email protected]
Build Number: Gingerbread.XXKI3
Now i can put my unit into download mode but ODIN doesnt pick up on it.
I also have a connection issue with Kies not seeing my phone either, although when i connect my unit to my pc (alienware m11xr2) it gives me the option to connect as USB storage..?
What im wondering now is there any soloution to this?
Can i root from the unit directly as i cant get ODIN to see my unit?
Thankyou in advance for any help given to both issues
Click to expand...
Click to collapse
Make sure USB debugging is checked under settings. If Odin worked before on your computer, try a different one. Install proper drivers and reconnect your phone to the different computer.
Are you using Windows 7? If yes then you should try installing Samsung Drivers in compatibility mode for Win XP and then go to device manager in PC and under USB Serial Controller dropdown, you'll see "USB Composite Device"(maybe 2)..Just update its driver, after update it should show "Samsung USB composite device".
Do it with phone connected to PC and USB debugging UNCHECKED. I'll post screenshots when i go home.
You can use mobile odin to flash and root. Use Kies Air to get the file onto the phone.
Edit: Disregard you need to be rooted to use the app.
Sent from my GT-I9100 using XDA App
thanks mistah bungle, ill have a go now and ill let you know how i get on
OK, tried all mentioned steps Mistah Bungle and no joy.
Uninstalled Kies,rebooted no change.
Rebooted tied Odin both 1.5 and 1.3 no change.
Rebooted tried all USB ports no change.
When plugging in the USB cables though and watching the laptop install the drivers i noticed that the 1st step was ticked and the 2nd (USB Driver) crossed, this occured on all USB ports on my laptop.
I managed to download the SAMSUNG USB Mobile Driver onto my laptop but still nothing changed.
Also have tried ODIN with USB debugging on and off just to be sure but still no change.
Just for your knowledge, my laptops running win7 64bit, 8GB RAM,icore 7 etc
Just seems strange how ODIN used to work before when flashing my device and suddenly this stops..?
lol thanks...well almost
looking forward to seeing if this helps, awaiting yr screen shots etc
Another PC looks like the only way you're going to get it done in that case. Yes it's strange, as to why, that's anyone's guess.
i am also running windows 7 64 bit and odin works great for me. One thing you can try is see if the phone is being detected under USB in Device manager and if you see it there right click on it and click uninstall and then right click and select scan for hardware changes and it should pick up the drives again. Also try disabling UAC(user account control) reboot then try. Let me know if it works.
...
ok went to Device manager as in picture 1 and deleted Samsung Mobile USB modem, unknown device and GT-I9100.
Then plugged phone back into USB and have now, as in picture 2
Thanks in advance people
Are you following the basics ,
Use the USB cable that came with the phone and only connect to a USB mainboard port .
jje
Can you obtain root through super one click or anything? If you can - do that - get modile odin - flash ...
http://forum.xda-developers.com/showthread.php?t=1321582 - doomlords zerg rush exploit
You state - Ok the main issue im facing is ODIN doesnt recognise my phone when connected.
So your PC can see your phone?
BigMrB said:
Can you obtain root through super one click or anything? If you can - do that - get modile odin - flash ...
http://forum.xda-developers.com/showthread.php?t=1321582 - doomlords zerg rush exploit
You state - Ok the main issue im facing is ODIN doesnt recognise my phone when connected.
So your PC can see your phone?
Click to expand...
Click to collapse
begining to think maybe the issue is a physical one as when i try to set USB debugging mode the handset is telling that the USB cable is connected!!!
BigMrB said:
Can you obtain root through super one click or anything? If you can - do that - get modile odin - flash ...
http://forum.xda-developers.com/showthread.php?t=1321582 - doomlords zerg rush exploit
You state - Ok the main issue im facing is ODIN doesnt recognise my phone when connected.
So your PC can see your phone?
Click to expand...
Click to collapse
OK god knows how i manged it but managed to get USB Debugging selected,used zerg exploit to gain root access to my phone (confirmed this using ROOT Check Basic from Android Market)
Now all i have to do is install clockwork mod again
????
Tried Clockwork aborts...
What does work right now?? U can boot phone? Access cwm but it reboots?
I had the same issue but very simple to resolve. First thing don't use usb netconnect at the same time when using phone data cable and if u r using front side slots for usb they may conflict with other usb devices drivers ...most commonly with usb netconnect... So use back side slots when phone is in normal mode..... Re- installing and unistalling will not resolve this... And be patience..... Be sure drivers are installed and if installed then no need to uninstalling and reinstalling... 100% it will work
Sent from my GT-I9100 using XDA App
BigMrB said:
What does work right now?? U can boot phone? Access cwm but it reboots?
Click to expand...
Click to collapse
Ok i can boot the unit on and have clockwork mod installed, i have checked that the unit has root access.
I put the unit into recovery with clockwork mod, this is what i get:
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
so i have to reboot.
Powers up showing no yellow triangle (yet when in download mode says 3rd custom binary and below samsung official).
powers on,seems to be ok then the voice talk app opens, i try and close and this goes on for minutes,on off,on off, i turn the phones screen off,it comes back on
This unit is very unstable at the moment for example:
The unit again is now not recognised by the USB ports allowing me to mke it seen as an external memory device from unit. ,its deffantly the unit,now that i managed to get root access i was going to transfer odin mobile accross from my pc and lightning 6.1 tar, then hopefully reboot,install odin flash lightning and viola problem solved....no such luck.
Voice talk is activating itself now continuesly opening as stated and putting the phone into car mode,just when i think i have 1 problem solved its giving me some thing else to contend with.
i admit im not the most technical at this and need step by step instructions but ive flashed over 50 ROMs/updates on this unit with no issues what so ever, maybe ive just pushed the poor lil bastard too hard for too long (since the day i got it, its been flashed) and possibly its getting revenge because it knows its just a matter of time until i get the SG3...?
I have the will and the patience to want to win this battle im having as i love the phone, but maybe the day is coming where phone meets wall,lol?
anybody?
OK managed to bluetooth ODIN mobile and lightning 6.1 tar onto the unit, hopefully have just flashed the phone....fingers crossed...
Well thats killed it, now unit is stuck on Samsung Galaxy s2 screen and wont boot up.
Can get to download mode but still not recognised by ODIN.
Vol Up, Power On, Home key gets me to clockwork Mod 4.0.0.2, go to install zip from sd card and wont select choose zip from sd card.
On screen says:
ClockworkMod Recovery v4.0.0.2
E: Cant mount /cache/recovery/command
E: Cant mount / cache recovery / log
E: Cant open / cache recovery log
E: Cant mount /cache recovery/last log
E:Cant open /cache recovery last log
E: Cant mount SD Card
E: Cant mount SD Card

[SOLVED] MTP device driver (code 10) Help!?

THE PROBLEM HAS BEEN SOLVED!
If you have the MTP usb device driver error (code 10), then scroll down and try what worked for me.
Sparrow245 said:
So, I used Odin to reset my vibrant back to stock 2.1. I then tried to get it to 2.2 using Samsung Kies, but when ever I try to use it, MTP Device fails to install. Anyone know how to get the driver to install / work correctly so that I can use Kies? Thank you in advance.
Click to expand...
Click to collapse
You should really avoid using kies if possible. It is notorious for hard bricking phones, meaning they become paper weights if something goes wrong. You should install clockwork mod recovery and install a custom 2.2 ROM, there are literally tons to choose from and they are pre-rooted. Some of the custom ROMs have odin images so you could actually skip the clockwork recovery step. I'll link you to the 2.2 ROM I'm using or you can search for something different. Here is Axura 2.2, use the odin image in the 3rd post http://forum.xda-developers.com/showthread.php?t=1787267.
EDIT- if you also need drivers for your phone then go here http://forum.xda-developers.com/showthread.php?t=728929
Sent from my SGH-T959 using Tapatalk
If you want 2.2 (Froyo) installed on your Vibrant, like the other poster said, there are literally tons of great builds.
Here is a link to one that I really liked, it had great battery life, and overall good performance. Bionix V - http://forum.xda-developers.com/showthread.php?p=21324042
As stated above, please avoid using the Kies software, it generally creates many more problems than it is worth.
I've used Kies many times, so I know what I'm doing. But apparently this time something about the MTP driver isn't going alright. Could be that I have this fairly new computer? I've already tried installing the vibrant drivers, but for what ever reason I keep getting a code 10 error for the MTP usb device. :/
Well if your not doing so already, try running the program as administrator.
However, not sure why you are so hell bent on running the stock Froyo via Kies, when there are so many other amazing Froyo/GB/ICS/and now JB custom ROMs that work MUCH much better, and have way better support than Samsung could ever provide.
However, to each his own. Good luck to you with your endeavors!
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
I know the thread is for a tablet, not sure which version of windows your running, but maybe something lime this is what you are looking for: http://forum.xda-developers.com/showthread.php?t=1150211
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Google code 10 error mtp
You should find a link that says fixed code 10 mtp error Samsung galaxy
It is a post on android forums or phandroid??? You should see it and it should fix your error.
sent from my magic box to yours
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Sparrow245 said:
I've used Kies many times, so I know what I'm doing.
Click to expand...
Click to collapse
When kies hard bricks your phone I'll be here to say I told ya so. Its really an unnecessary risk but its your phone, good luck.
Sent from my SGH-T959 using Tapatalk
@sparrow, that's exactly what I read but it was to much to type.
sent from my magic box to yours
Please Help
hey man did you ever get the MTP driver to start? I am still at a loss with this myself.
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
This is the steps used to fix.
Sent from my SCH-I535 using xda premium
Now is really solved.
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
Thanks a ton...saved my day.

Categories

Resources