Related
Please forgive me if I've missed a post somewhere, I've been searching for weeks for an answer to my problem and I still don't see one (similar cases, but either a-no answer or b-solution for another problem).
Computers:
A Windows 7 (32-bit) system and a Windows XP (32-bit) system.
Phone:
Samsung Vibrant SGH-T959
Firmware Version: 2.2
Baseband Version: T959UVJL5
Kernel Version: 2.6.32.9
Build Number: Nero.v3
Description of Problem:
When I plug my phone into either or my two computers the following occurs - My phone recognizes that it is plugged in and begins charging; my computers do nothing.
When I was on Android 2.1 I could plug my phone into either of my two systems and my PCs would respond appropriately (ie. show the drive letters and let me access the device once I mounted the device).
Since the very first Android 2.2 install my computers act like nothing is happening. ADB doesn't see my phone, Odin is silent, and Windows doesn't show any drive letters nor does it even show that I am plugging in a USB device.
I have tried to correct this by changing the USB settings on the phone (Kies, Media Player, Mass storage, Ask on connection) and even trying to connect while in debug mode. Sadly, I never made a nandroid backup to take me back to the Android 2.1 install (idiot me took the plunge before reading up on that section).
I don't understand what would cause my phone to be treated as if it wasn't there. I've tried different USB ports, different MicroUSB cables, and even uninstalling/reinstalling the various device drivers for the phone.
I can get into download mode just fine, but what's the point if Odin can't see the phone since Windows thinks that nothing is there? Before you ask, yes, I tried going into download mode before starting Odin as well as after starting Odin; debug mode on and debug mode off. I've been trying all the combinations.
If anybody has any information beyond what is in the stickies, I would greatly appreciate it!
Do you see "USB connected" in notification bar on the phone? You can also turn on USB debugging mode in USB settings. If you see "USB connect" in pull down notification bar..tap on that and it will mount on your computer.
I experienced similar problem with.axura tool...phone well charge but doesn't pop out the mount notification. I power off both my phone and computer and it work again. I'm sure this won't on your scenario but just wanna inform you that it's not all hopeless...good luck
Yes. I have seen the mount USB bar. Bad news: even after it says mounted, the PCs react as if nothing has happened.
Sent from my SGH-T959 using XDA App
First of all, read this forum (last post is mine) http://forum.xda-developers.com/showthread.php?t=925393 - make sure you have kies or kies mini installed so that you have the correct drivers on your computer for your vibrant.
secondly, team whiskey has developed a fix for the mount issue your experiencing: http://forum.xda-developers.com/showthread.php?t=846384&highlight=mount+fix
they also have the mount problem fixed in the later nero roms... should not be an issue. please let me know if this helps!
in_dmand said:
First of all, read this forum (last post is mine) http://forum.xda-developers.com/showthread.php?t=925393 - make sure you have kies or kies mini installed so that you have the correct drivers on your computer for your vibrant.
secondly, team whiskey has developed a fix for the mount issue your experiencing: http://forum.xda-developers.com/showthread.php?t=846384&highlight=mount+fix
they also have the mount problem fixed in the later nero roms... should not be an issue. please let me know if this helps!
Click to expand...
Click to collapse
Okay, so I've tried all of the above to no effect except for the latest Nero rom...
Looks like I'll be trying the latest Nero (thank goodness for Dropbox).
Nope. Updating to the latest Nero [v5] didn't work.
Anyone else?
Nvm... gl with fixing it.
All~G1 said:
Nvm... gl with fixing it.
Click to expand...
Click to collapse
I think I'm going to have to throw it under a bus...
This same thing happened to me and to fix this problem all I did was install the drivers I got online, PM me your email and ill send you the drivers
I am almost certain that it is drivers issue more than your phone or any rom. You need to completely uninstall current drivers..all traces of em, reboot and install drivers from samsung website or there are some here in vibrant section also. It happened to me couple of times where one set of drivers stopped working for no reason and i had to try couple of different ones.
I had the same problem. Phone would charge but not connect. I solved it by getting a new usb cable. I just use the bad one for charging now
Sent from my SGH-T959 using XDA App
This is a driver problem. Your computer does not have the phone drivers and is confused on what to make of your phone so it finally decides that it is a charging device more or less and will not mount it, EVEN if you select mount from your phone options.
Please look on this forum or ask the guy who posted before for the Samsung USB drivers. Install them on your computer and then mounting the phone from the notification bar will work.
Hope that helps and feel free to ask again if you are stuck on the process.
I thought it was a driver issue as well until last week.
My coworker has the same model phone and is currently running 2.2.
He has his laptop (Windows XP) setup to handle his phone.
When he plugs his equipment in, everything works. When he plugs my phone in, same old story...
Even when trying different MicroUSB cables.
This is why I'm considering loading up a different/modified kernel.
Sent from my SGH-T959 using XDA App
Ok i have been looking EVERYWHERE and it seems like all the guides are outdated and may not work if i have android 2.2.1 on the phone already.
I have
PVT 32A
HBOOT-1.33.0013 (SAPP31000)
in the settings on the phone it says my baseband version is 62.50Sj.20.17U_2.22.28.25 which doesnt seem to match up with the different guides out there.
PLEASE somebody link me to a guide that still works nowadays with android 2.2.1!!!!
Thank you!!!!!
The old guide on the cyanogenmod site should work fine. An image is provided to downgrade to like Cupcake or something, then you can root it. I was able to follow the directions a few months back on my wife's old mytouch 3g with no issue.
Where are you running into a snag?
Sent from my HTC Sensation 4G using XDA App
Thanks for replying. Well to start, here it says.
wiki.cyanogenmod.com/wiki/HTC_Magic_(32A):_Rooting
About Screen
While booted go to Settings » About and look at the baseband version. You will see a long string with the last piece that looks like: 6.35.10.18 or 3.22.20.17 - that is the radio version
Except my baseband is something entirely different. I posted it in the original post.
Actually, if i just knew how to downgrade to cupcake for starters that would be great.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Help somebody???? Everything on the net doesnt match up with my phone for some reason. Like its all outdated.
Which mytouch 3g do you have?
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
injo503 said:
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=925182.
Yay!!! This appears as if it might work for me! Thanks so much!
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
injo503 said:
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
Click to expand...
Click to collapse
Yes, it could mess with it. Did you reboot your device before trying this? It is recommended that you reboot your device after every root attempt.
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
injo503 said:
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
Click to expand...
Click to collapse
When using Superoneclick, did you follow all of its instructions correctly (especially disabling and enabling USB debugginig many times)? See here: http://forum.xda-developers.com/showthread.php?t=803682 and read the "Read me" for 11/10/2011.
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
injo503 said:
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
Click to expand...
Click to collapse
Okay. Try this method instead: http://forum.xda-developers.com/showthread.php?p=4314039.
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
injo503 said:
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
Click to expand...
Click to collapse
You do need drivers for your device installed on your pc. Yes, they could be for that (but you still need your device specific drivers).
Another thing is im using a mini usb cord but the plug on the mytouch is shaped differently. But it fits anyways and works for charging and file transfers.
Where can i find device drivers for my mytouch 3g? I havent seen any anywhere.
Hello Everybody i just got my viewpad 7 2.2 froyo i want to root it ... when i open superoneclick and click root it stucks and doesn't respond
According to this thread "If there is no activity for more than 30 seconds and the terminal display is stuck at 'Running rageagainstthecage....' remove the USB plug momentarily and plug back in." Hope that helps. Good Luck!
hanmin said:
As mentioned above, the AGPS uses server information (via cellular network) to locate the GPS satellite for a quicker fix and hash conditions. For a 4KM tunnel, I'm sure that your phone would have lost both GPS and network signal.
Click to expand...
Click to collapse
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Sent from my CSL-MI410 using xda premium
i got the same problem...
It stucks at waiting for device... I've tried pluging it off and back in...
you guy`s try a different usb port i had a simuliar problem with sut restoring the stock rom and i switch port and it worked youy can always try
haree said:
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Click to expand...
Click to collapse
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
elister said:
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
Click to expand...
Click to collapse
first run setup when connect device then leave the syng prog runninggo to dos shell
enter viewpads cdrom letter here it is g:\ you have to check youre`s
the type adb shell
dont forget superuser on youre viewpad ask for permission grant it hope this wil work
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
elister said:
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
Click to expand...
Click to collapse
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Alleycatzero said:
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Click to expand...
Click to collapse
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
elister said:
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
Click to expand...
Click to collapse
it supposed to be easy with youre pad to don`t know what els then sorry
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
armando101 said:
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
Click to expand...
Click to collapse
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
elister said:
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
Click to expand...
Click to collapse
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
kwbr said:
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
Click to expand...
Click to collapse
Are you sure? Lakehousetech's guide to using Super One Click 1.7 does not mention syncusb.exe. Because of this, Im wondering if the rest fo the guide is correct, because even with my device rooted with Gingerbreak, the rest of the guide does not work.
http://forum.xda-developers.com/showthread.php?t=1015005
Hello guys, I'm new here. I'm also facing the same problem in rooting my VP7. Tried different versions of SOC, stuck up on "waiting for device" and SOC stops responding. Tried also GingerBreak, installed and click Root Device and waited for ages and nothing happens. Almost followed all the guides posted here in XDA.
What am I missing? I'm about to give up. Thanks in advance.
same problems....
I am actually in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail.
I first read the postings in forums and websites, downloaded the newest (and then the successively older) versions of SuperOneClick 2.2.3. and tried - nothing, its stuck every time before connecting to the device.
Tried different USB-ports, enabled always USB-debugging, tried it with SD-card in or out - nothing. Same result with older versions of SuperOneClick (even using the alternate ADB-parser in "Advanced") - always stuck at the same place before connecting to the device. But - Windows sees the tablet and the card, because the usual window opens (for deciding what to do with the data on the card). Copying pics or music to the card is no problem.
Then - I left the SOC-Road for Gingerbreak. Installed, SD-card removed, runnig forever (25 minutes was the longest I let it run) - nothing. No reboot, no stopping of that little wheel proving that the program is not stuck and runs.
Now, before downloading another potential program for rooting, I became member here at XDA, looking for help.
I run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year).
I would be glad if someone of the "gurus" here could help me, because I spent three days now and I still don't see the light at the end of the tunnel....
Gerd
boriflash1 said:
... in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail ... run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year) ... and I still don't see the light at the end of the tunnel....
Gerd
Click to expand...
Click to collapse
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.) Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection, recognize the device, attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable, sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted)
If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Letitride said:
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Click to expand...
Click to collapse
Dear Letitride, first of all thank you very much for trying to help. Let me answer your questions one by one.
My computer runs on Vista home, its a laptop and has all the official windows updates. Four USB-ports, all of them working (checked with my external hard drive). When plugging-in the Viewpad, the window with the options how to open the data on the SD-card immediately opens.
I do not know how to access the data on the Viewpad like you did, but I definitely have Froyo 2.2.2. and the last official update, official rom.
Letitride said:
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Click to expand...
Click to collapse
Sorry, I don't know anyone at the moment (as I am travelling) with another computer I could use. So I guess I have to stick with mine. But when I do a restart, all applications running before should be terminated anyway. I could also move all the data without any problem to and from the Viewpad's SD-card.
Letitride said:
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
Click to expand...
Click to collapse
Now you lost me. Which drive? Laptop drive? Where do I get the VPad7 apps, drivers, etc? I have to have them before copying them in any subfolder (subfolder of which folder by the way?). Same question for ADB, shell, busybox. Sorry for my stupidity, I am into Windows, but not into Android....And even in Windows I must confess that I almost did not run anything from command lines. Never needed to....
Letitride said:
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
Click to expand...
Click to collapse
I even have three cables and 4 ports and I interchanged already all of them.
Letitride said:
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.)
Click to expand...
Click to collapse
Already did. I tried them from 1.6 on upwards... No success.
Letitride said:
Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Click to expand...
Click to collapse
I turned of windows firewall, Avira and the Viewpads antivirus. No success
Letitride said:
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection
Click to expand...
Click to collapse
YES
Letitride said:
recognize the device,
Click to expand...
Click to collapse
Hmmm.,... it recognizes the SD-card, but not the device. That is also the problem when using SOC....it is stuck at ...looking for device....
Letitride said:
attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable,
Click to expand...
Click to collapse
DID, but it did not move of change anything when SOC is stuck.
Letitride said:
sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted) - If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Click to expand...
Click to collapse
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops working, the window gets white and then when I try to close it, it simply states that SOC has a problem in closing. On the second click, it closes.
I hope I was a specific as possible, excuse once again my ignorance concerning android. It definitely seems that my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Thanks again. I really appreciate your help.
Gerd
boriflash1 said:
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops ... gets white and ... simply states that SOC has a problem in closing. On the second click, it closes ... ignorance concerning android ... my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Gerd
Click to expand...
Click to collapse
Edited your details to try to keep it short - it read like there some of the device drivers might be missing or need to be installed.
My laptop was reformatted last month running Vista Business & from my notes, when the Vpad was 1st. connected, it recognized the new hardware (Qualcomm USB device) and proceed to install 3 drivers, enabled a virtual CD-ROM drive with additional setup files, and when it was done including a reboot, the laptop has 6 new hardware/device drivers - and both the new virtual CD-ROM and USB removable device available & working, with USB debugging enabled and once the USB drive was turned on (default is off)
Have you tried to go to Control Panel, click & uninstall all the related USB drivers, including a PC Tools apps auto-configured by the Vpad7 ?
Then, shutdown & reboot the laptop - reconnect the Vpad and let it re-install everything from the beginning. (also, do you have a spare mSD card, an older 8GB or even 4GB mSD would be useful ?)
As for the sub/folder - I was referring to creating to making a subfolder on your laptop's drive, and saving/moving all of the vpad7 related donwloads, SOC and custom Roms, etc. to this folder (and subfolders as necessary to keep it organized.) I put the adB and busybox files, etc. here too as downloaded - in order to run adB using the command prompt per instructions - this Android & linux based "stuff" is new to many of us, but to have fun is to allocate some time to learn them. There are links here on XDA on the basics & it's worthwhile reading.
Also, did the Vpad7 install PC Tools, which is used to sync. files between the laptop & the V?
I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
I'd be interested in knowing as well...
Sent from my DROID RAZR using xda app-developers app
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
seanzol said:
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
Click to expand...
Click to collapse
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
jeff_roey said:
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
Click to expand...
Click to collapse
Hi!
Take a look on others users problems they faced in eternityproject easyrootics.
You may face problems with other devices drivers like htc sync, kies, motocast... disable those and check you got adb working by typing
Code:
adb devices
I your root folder from windows terminal.
cheers
did you make sure you have the correct drivers installed? Not just plugging it in to USB and windows says drivers are installed.. that's not it. You have to make sure you install the correct 32 or 64 bit drivers (included in "Matt's Utility). Extract them, and double click to run the installation. Then try Matt's utility again.
I have only used M's U, not the other methods on both a 32 bit computer, and a 64 bit puter and haven't had any problems whatsoever. Good luck.
Edit: Just thought of this as I was re-reading the thread, try a different USB port. Some of my other USB stuff only works in the port it was installed in. Also, I'm sure you know, but to find out if you're 32 or 64 bit, go to "start" right click on "my computer", then properties. Install the drivers that are included in the extracted Matt's Utility 1.7 folder. Make sure USB debugging is enabled, USB mass storage on your phone. It'll re-boot 3-4 times during the rooting process.
jeff_roey said:
I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
Click to expand...
Click to collapse
Did you unzip Matt's utility into a new folder?
Go to my thread op and read the instructions
Cheers
Sent from my XT910 using xda premium
I had the same issue when I side loaded. Drivers were updated and all was well. Try plugging the phone in in charge only mode. I was complicating the process by trying to do it in fastboot. I was informed to just plug it in, hit 3 and let Matt's utility do it's thing. And it did.
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
newowner said:
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
Click to expand...
Click to collapse
Setting my USB mode to connect as a camera (PTP) did it!
I had the Moto Drivers from Matt's Utility 1.7 already installed (driver ver 5.7.0) and based on advice from other posts in this string, I went ahead and uninstalled them and reinstalled them just to be safe. Root attempts after doing that using the methods I discussed in my OP still were unsuccessful.
After seeing newowner's post, I went ahead and chose camera mode for the USB Computer Connection (settings -> storage -> press the menu key and choose Camera (PTP) and windows installed additional devices: USB Composite Device, DROID RAZR, and Mot Composite ADB Interface. I'm guessing the ADB Interface on was the one I was missing before.
Okay, I'm rooted and I'm heading back through this string with my bag O'Thanks to all of you.
Glad to assist.
Thanks for following up with your progress.
ICS is a little different!
nothing worked for me...tried camera mode tried media mode, tried different computers and reinstalling and uninstalling....bah.
I ended up doing a factory reset and everything was fine after. Boo...couldn't TB it beforehand though..
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
ultimate_reconx said:
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Did you have the Android drivers installed previously? I'm assuming that you're trying to install the drivers for the first time on that your computer and that you have USB Debugging enabled. I'll also be assuming you disabled driver verification, which can be a problem in some computers.
First you need to boot your phone normally, and plug it into the computer. Press Win+R to open the "Run" dialog and run "devmgmt.msc," which is the Device Manager. Look up the "Unknown Device" that is your phone and double click it. Click on the Event tab and check the Hardware ID in the drop-down box. It should look something like this (sorry mine is Android Composite ADB Interface because I've installed it already, but that's what it should look like in the end):
Now you have to make a new section in the driver inf. It should be in the google adt bundle and in the extras\google directory. The file name is android_winusb.inf. In the picture below my tablet is the iDeaUSA CT702. You need to add one of these sections in both the x86 and x64 section if you have a 64 bit computer. If not, just put it in the x86 section. The %USB stuff needs to match that in the Device Manager Hardware ID.
Now you should have a device called Android Composite ADB Interface or anything like that is fine.
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
ultimate_reconx said:
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you don't know where the driver is, then download a new one. I've uploaded the official Google USB driver to mediafire here: Mediafire - usb_driver.zip
You need to modify this driver, then when asked to select the inf file for driver installation choose the android_winusb.inf inside. After installation your phone should be recognized. Please tell me if there's any uncertainties you have.
Have you tried connecting the device with usb dev mode disabled? I know its strange but I've a few devices that use different drivers if the usb dev mode is enabled. I've also devices where I need to enable usb mass storage setting every time (settings menu or slide down notification). Also it never hurts to try a new cable, usb wires do tend to wear out and are very cheaply manufactured so they break inside with the slightest tug of the wire. I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
ultimate_reconx said:
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Cha1n5aW said:
I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
Click to expand...
Click to collapse
Good point. If you don't have developer mode usb debugging enabled, then there will be no "unknown device" as shown above in the device manager. Be more detailed about "no luck" please.