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.
Related
Hey, I've tried various methods of rooting my GSM Hero, and eventually found the method on this site entitled "VillainROM Roots 2.1 RUU for GSM Hero (Confirmed)". I got as far as trying to run runindos.bat, and this just returns the error as explained. If I run "adb devices" I get "List of devices attatched" and then just nothing after it. Strange.
Does it have anything to do with the fact that HTC Sync never picks up my phone?
Windows 7 64-bit
HTC GSM Hero
3 UK
Android 2.1
adb, drivers or usb debugging, check it
Sent from my HTC Hero using Tapatalk
USB Debugging is enabled, not sure how to check adb but what's the correct way to install the drivers? Is it by running the "SDK Manager" program in my SDK folder?
Moved to Q&A as not development.
Get the drivers via the sdk manager, and manually install them via device manager for the device.
Ahh, sorry about the wrong section. I assumed that Development would be things concerning roots.
SDK Manager only seems to let me install "SDK Platform Android X.X", I don't see any driver installations. Also, I'm not sure where it installs these to.
Edit:
Okay I tried to install "USB Driver" but Windows said that it was already up to date. Still not appearing in adb :/.
Hmmm. Search for drivers in dev forum, as I think I posted mine (or instructions to hack them) on one of the Froyd villain threads somewhere.
Also, I presume you have rebooted and tried adb right after reboot
Drivers for you
Thanks to you both, I'll try those later on today.
I'd rebooted both the PC and the phone and tried it. Nothing unfortunately. It just seems to be a big Windows 7 problem.
I use Win 7 without any problems.
Check out this epic guide by BTDAG,...
http://forum.xda-developers.com/showthread.php?t=776056
Good news and bad news. The drivers are now working, adb is working and runindos.bat is doing it's thing. Unfortunately, when it reboots the second time for recovery, there's just a red triangle with an exclamation mark in it.
I rebooted and got back to where I was, but how do I get the "Care Bear" boot screen? Am I supposed to have moved RA-Hero to my phone first or do I not need anything?
Thanks.
Hi Craig. I had to repeat process 4-5 times before it worked so make sure you have your new rom on SD for when it works. I had all same probs but it will get there. As pulser said on villain try changing directory to avoid echo. It seems to load a little more each time.
Sent from my living room.
Hmm, if the recovery thing with the phone in the background comes up, and has "apply:update.zip" as a selection, should I try that? I've tried a few times and that's usually what comes up, along with reboot phone and another couple of selections.
I've got it! Thanks very much for everything. I just kept doing it and it's working now. I got FroydVillain and I'm loving it! I never realized the Hero could be so smooth.
Also sorry for the double post, I'm used to auto-merging on formus.
Hello fellow android-users. I have a problem. A problem that I can not figure out. My problem is the fact that no matter what I do I can't root my optimus v. I have tried literally everything and still can not root it. On the phone I've tried all known versions of Visionary, Z4root, easyroot, and universal androot. On the computer I've tried SuperOneClick but it always gets stuck on "waiting for device". I have searched so many forums and cannot find a solution. I think I could root it from the computer if it weren't for these bland general drivers I get installed on my computer every time I install drivers then plug my phone into the computer via usb. I have tried plugging it in to 3 different computers and always get these drivers. I have also tried 2 different usb to micro-usb cables (thinking that the one that came with the optimus might be charge only).Down below I have attached the drivers that always come up and what I think I should get (I screenshooted this from a youtube video).And all the lg android,virgin mobile, and usb drivers I have installed in various orders and mixed and matched but still no good. Also I have never had the phone get a usb notification when I plug it in.And yes I have Usb debugging turned on on the optimus. Although I have tried taking it off just for the heck of it.
Thank you for your time and consideration.
P.S. All i want to do is root it so that I can remove the bloatware and overclock it a bit.
Additional Information: Yes this is also posted on android central but I'm posting it here in hopes that maybe you all can help.
Additional Additional Information:I have tried every driver in every combination for the optimus v with never any luck.I have also installed linux on my computer If I will need that.Is there anyway to root it manually from the device itself, because that appears to be the only way. Here is a link to the official thread:forum(dot)androidcentral(dot)com/showthread.php?p=889790
If you try to connect via adb shell, does it successfully get you a "$" or "#"? Or does it say device not found?
This may seem odd, but try turning the phone off and doing the procedure for permanent root. Some have reported that turning the phone off fixes connectivity issues.
i rooted mine 2.2.2 with gingerbreak, very easy, install root and bobs your uncle
Try Gingerbreak..........works all the time
I downloaded the Gingerbreak v.1.2 app and when I press root I get "rooting....... running exploit..... This may take a few minutes! Device will reboot on success!" and I wait and nothing ever happens. And if yall are talking about the gingerbreak exploit on superoneclick I can't even get my computer to recoqnize my phone the right way.I've never had the usb notification thing pop up on the phone.I have downloaded every single driver for the phone and have installed and uninstalled them soooooo many times with no success.And I have had usb debugging on and tried rebooting several times with no luck. All i want to do is gain root acess to remove bloatware and overclock a bit.
Try all 3 versions of gingerbreak
Alright I already tried v.1.2,and 1.1, but it won't hurt to try 1.0.
remove any antivirus tht u have installed and try again
Alright I'll try that and get back to you
I tried it and it made no difference.Thanks for the suggestion though.
your sureshot is to downgrade ur device to froyo2.2. and then perform the root
Did u enable usb debugging mode? oO
josinpaul: My device is already froyo.The optimus v comes with froyo and I have not touched the OS. Also, how I would I do that if no computer can even recognize the device? (Not trying to be a jerk, just wondering if you could change the OS without being connected to the computer.)
ccdreadcc: Yes I have usb debugging on.And yes I have tried rebooting while I had usb debugging on and while it was connected to the computer via usb with no different results.
Keep your memory card unmounted ,I think here is the problem.
Sent from my LG-P500 using XDA Premium App
If you mean go to settings in the phone and unmount it then I already did that and it didn't make a difference.If you mean don't mount the sdcard when the usb notification comes up on your phone, then I have no choice.I can't get my phone to even get that (the usb notification).It's charge only when I plug it up to my computer and I have installed all of the drivers and tried everything (and yes a million times, I have usb debugging turned on).That's the whole point! I can't get the drivers to recognize the phone.I have tried it on 3 computers with 2 different micro-usb cords with never any success.
I wonder if your phone really is in USB debuging mode despite what it says. Here is a program to verify that you have rooted your phone. Gingerbreak should work on all firmware/android versions. What android version are you on? Many of the methods do not work on 2.2.1 or 2.2.2. If you go to settings/about phone you should see what you are running.
PS When you did Gingerbreak, was the APK installed on the phone or the SD card? Gingerbreak is mentioned in a number of threads. Have you check this thread? http://forum.xda-developers.com/showthread.php?p=13086954
Verify your root with https://market.android.com/details?id=com.joeykrim.rootcheck
I am not rooted.That's what I'm trying to do.I checked my version and it is 2.2.1.And i have always tried running gingerbreak from my phone, but it just says "rooting" forever.
Upgrade to 2.2.2 and give it a shot?
Or jst try after a hard reset o)
How would I upgrade it to 2.2.2 if i can't connect it to my computer?
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
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?
Hi all,
I'm having some trouble with this, so I wanted to consolidate another thread into a main post. Here is my previous work. Any help would be appreciated or let me know if something doesn't make sense.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
Update 2 : working on it again today and couldn't get it to connect. Ignore what I said about it needs to be in PTP mode... it does not appear that way, but if you use a certain version of adb.exe floating around it will not connect. Look for one that is around 800KB... the one I'm using is 815,104 bytes. The other is around 500KB.
It also seems to be necessary to set adb.exe to "Run as Administrator" in compatibility mode (I also set run as XP SP3 for good luck). I have also been using an elevated cmd window, so hopefully this stuff is all legit
Yesterday the device did not actually fully get rooted so I started over. I am going to try running the "root" script line by line rather than the whole thing at once because it gets stuck somewhere and there is no indication of what happened.
Click to expand...
Click to collapse
Eh, I gave up... after two full days I'm confused about why I'm even doing it... Also, coming from an iPhone, this thing is already so open lol.