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?
Related
Each time I try to root my streak I get the following error message off super one click
Ok
Pushing psneuter...
Error: closed
Failed
Sent from my Dell Streak using XDA App
I have the same problem
There are numerous threads in numerous forums about using SOC with the Streak.
Summary:
Drivers – make sure they are correct for your system.
Run SuperOneClick from an administrator account or as an administrator
Make sure your phone is in USB debugging mode
If you have an anti-virus app on your phone turn it off.
You may have to turn off your anti-virus on your computer.
You may need to go into settings on the phone and un-mount the SD card or physically remove it during the root process.
Try different ports on your computer. Most have better luck with a port directly on the mother board.
Less problems are reported with 32 bit systems and WinXP installs.
Shut down all other software, disconnect other devices from USB
Try different versions of SOC. I believe that I used 1.53, others report success with 1.55.
More detail here
marvin02 said:
There are numerous threads in numerous forums about using SOC with the Streak.
Summary:
Drivers - make sure they are correct for your system.
If you have an anti-virus app on your phone turn it off.
You may have to turn off your anti-virus on your computer.
You may need to go into settings on the phone and un-mount the SD card or physically remove it during the root process.
Try different ports on your computer. Most have better luck with a port directly on the mother board.
Less problems are reported with 32 bit systems and WinXP installs.
Try different versions of SOC. I believe that I used 1.53, others report success with 1.55.
Click to expand...
Click to collapse
I totally agree with the above post, 1.5.4 worked for me, just be diligent, took me a few tries to make it work, I closed all applications also to be sure, only SOC open. Just follow marvin's instruction and you'll be good.
I have expanded on the summary in the post above in this article. It's a collection of what I have seen posted in various forums.
jankec79 said:
I have the same problem
Click to expand...
Click to collapse
use z4root
Solved It for me.
Open oneclick 1.6.5 start root with phone unplugged and turned off. OneClick will say waiting for device.
Plugin phone and turn on. One click will see it during the boot phase and install it. Let it sit it may run 2 or three times through. It has worked every time for me.
Sent from my Dell Streak using XDA App
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hi
For some reason I am now getting a Driver Installation Failure error for my S3 when I plug it in to USB on Windows 7. The driver is SAMSUNG Mobile MTP Device, which fails after a long (3 minute or so) install attempt.
This means I can't access the Phone via USB for file tranfers etc, either Windows Explorer or Keis. Though I can use ODIN to Flash if I put the Phone in Debug Mode.
I have tried all sorts. Un-installing the Samsung Drivers, rebooting and reinstalling, and getting Kies to try a driver repair.
It wasn't like this when I started with the phone. Something changed - after I rooted it. I am currently on the Omega ROM 6.0 with standard kernel. For a while I was on 5.1 with Syloa 1.1 and then 1.26. I realized it was wrong when I couldn't copy Omega 6.0 ROM ZIP over to Flash.
I have searched and searched. This seems to have happened to other phones as well but be intermittent. A few other phone on XDA have reported this in the last couple of weeks (so maybe a Microsoft change to Windows 7?)
As a weird related issue sometimes when I plug the Phone into WIndows now I get two removable drives showing, which are "Samsung USB Gadgets" using a 2006 Microsoft Driver... They show as removable drives with no drive in them. Again all my tricks of disabling uninstalling, re-installing etc these seem to make no difference.
Anyway - any ideas / fixes help appreciated!!!
Cheers
So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.
Now again check in device manager after installation. It should look like the one in the attachment.
I've got the same issue; can't get the MTP drivers to work on my Win 7 machine or my work XP box. Both had the Galaxy nexus drivers on them previously (I think, came from ICS Captivate).
Are you sure USB debbuging is unchecked in settings?
If that's not the problem, you could try a different pc or os (a live ubunt cd for instance) to see whether it's the phone or the computer thats messed up.
Fresh windows 7 install and still nothing. Could the phone be messed up?
Have you tried a different USB port?
Yeah tried all the ports/cables I've got lying around. In safe mode it will install everything okay but Kies still won't connect. :/
Geoff.Costello said:
Hi
It wasn't like this when I started with the phone. Something changed - after I rooted it. I am currently on the Omega ROM 6.0 with standard kernel.
Click to expand...
Click to collapse
Same here!
I also have Omega ROM 6.0 but the problem started BEFORE Omega ROM.
Did you also back up your efs folder using SGS Toolkit 2.0?
I seem to have had the problem after flashing the "insecure image" which one has to do using the SGS Toolkit in order to backup efs.
Ive also uninstalled and reinstalled pretty much EVERYTHING, drivers, Kies, SGSToolkit etc...
I have 5 pc's at home. ALL of them cannot connect to my SGS3, and ALL could connect to my SGS2 a couple of days ago!
tx
Mark.
---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------
rohan999 said:
So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.
Click to expand...
Click to collapse
Thanks, but process does not work in this case. Not on 5 PC's in my house.
BTW Kies by WIFI seems to work, but it is obviously very limited...
Try this
This worked for me follow link
tomshardware.com/forum/242140-44-device-refuses-installed-please
rjnolberto83 said:
This worked for me follow link
tomshardware.com/forum/242140-44-device-refuses-installed-please[/url]
Click to expand...
Click to collapse
hi link does not work
it takes me to toms home page...
To fix the problem, follow the next steps:*1) Go to http://www.microsoft.com/en-us/download/details.aspx?id=19153
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
rjnolberto83 said:
To fix the problem, follow the next steps:*1) Go to microsoft.com/downloads/details.aspx?FamilyId=A2E73160-E862-4F19-BB26-C0CAFE798955&displaylang=en
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I've got the same issue and this did not work.
Reinstalling windows fixed my problem.
cure is to wipe phone, dalvik, re-flash rom
rjnolberto83 said:
To fix the problem, follow the next steps:*1) Go to microsoft.com/downloads/details.aspx?FamilyId=A2E73160-E862-4F19-BB26-C0CAFE798955&displaylang=en
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hi there
This may work in other situations, but I have found out what caused my MTP to start working again, and it is NOT the computer, it is the phone for 100% sure.
I had this issue on 5 PCs in my home, ALL of which worked fine with my SGS2.
I did a factory wipe, wiped dalvik, and re-installed Omega v6 rom, and it now works on all 5 computers.
I do not know why it started, but the thing I did before the problems started was to use SGSToolkit v2 to flash an "insecure image" so I could backup efs folder. I have a feeling it is related to this, but I do not know for sure, and the maker of that software says 20000 people have used his software without this issue, so it cannot be his software.
Anyhow, by reflashing omega, and wiping the phone, it now works.
Mark.
Worked for me too.. It was the phone.
Mark,
Thanks. I too had Omega 5.2.
I wanted to upgrade modems but found I couldn't connect via PC as I had lost Root.
I too downloaded Version 2.0 of the tool kit and downloaded the insecure kernel and flashed it.
After that I could not get any PC to recognise the phone.
I got Omega 6.0 on wirelessly
But connection problem remained.
So your full wipe worked. The phone is now behaving and connecting to any PC I try.
Thanks
Geoff
Possibly the USB cable?
I ran into this issue as well. When I connected my phone to my (Win7Prof64) computer, the OS recognized and downloaded the drivers and my phone's directory came right up. When I tried the same the next day - I received the "unknown device" message. After about an hour of troubleshooting I learned something interesting - I was using a different USB cable than the one I received with my phone. I connected the USB cable I got with the phone and everything automagically worked again. The USB cable must use another wire that "regular" USB cables don't? Here's a chat with Samsung support regarding the cable:
Gavin: Yes, the USB cable supplied with the device is Samsung recommend and is the Original. So, we request you to use the USB which is supplied with the device.
Doug: will i damage the device at all if i use a different cable to simply charge the device?
Gavin: No, it will not damage the device while charging.
Gavin: But, it can face some issues in connecting in mass storage mode.
Hope this helps!
Here's what I found about about my problem.
Samsung Galaxy S3 does not like USB 3.0 ports on my laptop.
Plugged the phone into the USB 2.0 port and it worked perfect.
Hope this helps out some of you!
The same device on Win7 OK, on XP not.
4 me it happen after Android upgrade to ICS 4.0.4 but only on XP PC. Win7 found new drivers online automatically.
May be XP is to old 4 ICS
One solution I found here: http://androidforums.com/4819200-post7.html however don't want to hard reset my device
Some body can try driver pack 4 all phones here: http://www.mobiledit.com/downloads.htm?show=14
I had this happen on occasion in the past and just now (moved to new laptop). What I have done that works for me is that you open up the details (where it says that it's installing your device click here for more details) and let it find/install all the drivers. Eventually it will fail with the MTP driver, KEEP that window open. Now unplug the usb cable FROM YOUR PC (don't ask me why but this works 100% from the phone side not always) and then plug in again. You'll see the MTP driver search start again and this time it should install.
FIX
1. Download and install the s3 Toolkit here: http://forum.xda-developers.com/showthread.php?t=1703488
2. Don't run it but browse to \Samsung Galaxy S3 ToolKit\drivers
3. Run USBDeview and uninstall everything with Samsung or i9300 in the description (right-mouse)
4. uninstall Kies and USB drivers.
5. Disconnect phone
6. Install \Samsung Galaxy S3 ToolKit\drivers\Samsung_USB_Driver.exe
7. Connect phone.
Tadah!
Solution
Here is the only solution that could resolve the problem for me after days and days of trials and errors.
Just go to device manager and manually install the driver after selecting it from the already available drivers.
over and done.
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
dsore1218 said:
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
Click to expand...
Click to collapse
I can't get mine to work either. Closest thing I've gotten is using omap4boot-for_optimus-v1.21
its different from some of the others, in that its a blue background and it doesnt actually list the p769. However, after selecting option 5, and following onscreen instructions, I was able to get my front capacitive buttons to light up, but nothing else. I can't enter S/W upgrade mode, I can't get LG recovery tool to recognise my phone, I am absolutely **** out of luck. I dont know if using omap4boot-for_optimus-v1.21 will help or hurt you, but im just explaining my experiences.
Have you installed the omap driver for fastboot?
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
I don't have Windows 8.1 so I'm not sure how to address the driver issue. I reer as wel.commend you uninstall the driver, both of them. The one under Android Phone in the device manager and the one called TI Boards in the device manager.
1. Uninstall all OMAP drives (Two of them)
2. Disconnect from the internet (to preventing Windows update from selecting its own driver.
3. Follow steps to fastboot. When connecting your phone have device manager open and right click the device that is flashing on and off (you will see the device manager refreshing and stuffs. It will dissappear after about two seconds but if you get the right click in and the option to install the driver, do it, point to the fastboot driver.
4. Disconnect phone after driver install and pull the battery.
5. Fastboot again, using option 1.
6. Quickly install same driver on the new device in device manager. Be quick.
7. Disconnect, Pull battery
8. Fastboot again
9. Flash ICS U and X
10. Make sure your LG drivers are installed.
11. Reboot PC.
12. Now you should be able to get into SW UPGRADE MODE with the plugging in of the USB
Should not lock up at 15%, make sure you have drivers installed for this.
13. Should work and reboot to home screen automatically.
14. If you really must, fastboot again and install JB U and X
dsore1218 said:
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
Click to expand...
Click to collapse
I've heard fastboot (and several other programs) aren't working on Windows 8. You need windows 7
Sent from my LGMS769 using XDA Premium 4 mobile app
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...