Related
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?
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?
Hello,
I have a very big problem with my Samsung Galaxy S3 I9300.
The problem started when my battery ran down very very fast. I can use my phone for no longer than maybe 6 hours, and that is in stand by. If I want to charge my phone till it's completely full it might take two days on the charger as well, even when my phone is off. I tried to reset my phone to factory defaults, but that didn't fix the problem. I even bought a new battery, hoping that would solve the problem, but even no luck with that. The phone also becomes hot in the bottom. Now I wanted to bring it back to the store for warrenty but there lies the next problem, my phone is rooted.
I know it is possible to unroot the phone, and it's nog too hard to do. But every time I connect my phone with USB to my computer, my computer doesn't recognize it. I get the next error message "USB device not recognized". I tried different cables, I tried on an other computer, but still I get the same error. I also tried the S3 of a friend on my computer and with his phone I do get a connection. So I know there is nothing wrong with the drivers on my computer or something like that. There must be something wrong with my phone.
Now the problems won't stop here because there is even a third problem. Like I said before I have rooted my phone, but I can't use SuperUser. When I start SuperUser it says "The SU Binary needs to be updated. Continue?". Then when I press continue I get the message "Installation failed !". I can't use CWM as well. I wanted to use Triangle Away before bringing it back for warrenty, but I can't use it because I can't use SuperUser.
If some one would have an idea to unroot my phone without using USB so I can bring it in for warrenty. Or find a way to get my USB port running again, I think that would fix my problems.
I spend a few hours trying to fix these problems, but now I've come to a point I don't know what to do anymore, I hope anyone of you is willing to help me. I'll be for ever gratefull.
Grtz Nathan...
Hi.
If i was you, i would try to install a official version, using Odin.
Also, my advice is not to use the original charger, Even chinese have better one´s...
Did you install Kies and drivers on your PC? Check that too.
Consider install leaked 4.2.2 version of Rom, since it uses Odin to do it.
I hope i gave at least some clues....
Mord0rr said:
Hi.
If i was you, i would try to install a official version, using Odin.
Also, my advice is not to use the original charger, Even chinese have better one´s...
Did you install Kies and drivers on your PC? Check that too.
Consider install leaked 4.2.2 version of Rom, since it uses Odin to do it.
I hope i gave at least some clues....
Click to expand...
Click to collapse
Thanks for your reply,
I forgot to mention that I have the official ROM installed, I only rooted it. But even if I would want to install a new ROM, my computer doesn't recognize my phone throug USB. So I can't install a ROM using Odin unless my USB port is running again.
I tried several chargers already, I don't think the problem lies in the charger because the battery drains very fast when it's of the charger.
I did install Kies and drivers, I even uninstalled them and reinstalled them again a couple of times. I even tried it on different computers. And the Galaxy S3 of a friend of mine does make a connection. So I don't think the problem lies there.
droogje said:
Thanks for your reply,
I forgot to mention that I have the official ROM installed, I only rooted it. But even if I would want to install a new ROM, my computer doesn't recognize my phone throug USB. So I can't install a ROM using Odin unless my USB port is running again.
I tried several chargers already, I don't think the problem lies in the charger because the battery drains very fast when it's of the charger.
I did install Kies and drivers, I even uninstalled them and reinstalled them again a couple of times. I even tried it on different computers. And the Galaxy S3 of a friend of mine does make a connection. So I don't think the problem lies there.
Click to expand...
Click to collapse
Hummm....
Did you try hard reset? Definitely without USB recognition, you can`t go to next stage....
In setup did you check optinos like USB debugging?
At this moment im out of options....maybe a poweruser can help you better:highfive:
Mord0rr said:
Hummm....
Did you try hard reset? Definitely without USB recognition, you can`t go to next stage....
In setup did you check optinos like USB debugging?
At this moment im out of options....maybe a poweruser can help you better:highfive:
Click to expand...
Click to collapse
What exactly do you mean with hard reset? If you mean powering on with home button and volume up button pushed, and then select "wipe data/factory reset". Then yes, I tried that.
In setup I did check USB debugging. The thing is, when I power on with home button and volume down button, I enter download mode. But even in download mode my computer does not recognize my phone. I'm not sure, but I think the computer should.
I'm really stuck here :crying:
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
jalt96 said:
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
Click to expand...
Click to collapse
Try with other port and USB cable.
Have you Degugging Android activated in Deceloppers options ?
the other day i tried for hours to get my phone recognised. what did it in the end was trying it on a different pc and it worked
KeTuRr74 said:
Try with other port and USB cable.
Have you Degugging Android activated in Deceloppers options ?
Click to expand...
Click to collapse
I have already tried with every port on my PC. I'm using the USB cable that actually came with the device and it is working when I plug in another phones.
And yes, I have activated USB debugging
sosolid4u09 said:
the other day i tried for hours to get my phone recognised. what did it in the end was trying it on a different pc and it worked
Click to expand...
Click to collapse
The thing is that my phone is the only one that do not get detected every single time I connect it. I have already connected one GT-I9100 and GT-S6790L and both get detected. I already tried on 3 different Virtual Machines with Windows XP, Ubuntu, Windows 8.1 but no luck.
As I said in the first post, I think it's a firmware problem since it appeared when I did the official update, which was this one:
Model GT-I9300
Model name GALAXY S III
Country Argentina
Version Android 4.3
Build date Wed, 05 Nov 2014 20:33:08 +0000
PDA I9300UBUGNK1
CSC I9300UVOUGNK1
MODEM I9300UBUGNK1
jalt96 said:
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
Click to expand...
Click to collapse
I can see your frustration Now a few things technically it is a misconception that you need root to flash a custom rom you can actually flash a custom recovery with Odin full wipe and then flash a custom rom from custom recovery (only thing is you will lose all your data because you need root to back up your data)
Now I know the above statement is not very helpful because as you said Odin doesn't detect it (but I thought I would mention it anyway )
The reason framaroot and towelroot, didn't work is because at the moment the only way to root S3 is with Odin.:crying:
You may have tried this but I will mention it anyway first uninstal Kies and all Samsung drivers from your computer ( kies can interfere with Odin) Then try installing these drivers here >> http://developer.samsung.com/techni...Lhp1GqlWRy92Q60CX6PP1mF!80806326?v=T000000117 << If you have tried this then sorry.
Also when you connect the phone go to Device manager in Windows and try to look for your device ( it may say unkown device) it should have a warning triangle right click on it select update driver software and then select browse from my computer and point to the drivers that you have downloaded see if that works.
Another thing to note is if you are using Windows 8 you need to disable Driver signature in start up options ( Google it) for Windows to recognize the drivers.
tallman43 said:
I can see your frustration Now a few things technically it is a misconception that you need root to flash a custom rom you can actually flash a custom recovery with Odin full wipe and then flash a custom rom from custom recovery (only thing is you will lose all your data because you need root to back up your data)
Now I know the above statement is not very helpful because as you said Odin doesn't detect it (but I thought I would mention it anyway )
The reason framaroot and towelroot, didn't work is because at the moment the only way to root S3 is with Odin.:crying:
You may have tried this but I will mention it anyway first uninstal Kies and all Samsung drivers from your computer ( kies can interfere with Odin) If you have tried this then sorry.
Also when you connect the phone go to Device manager in Windows and try to look for your device ( it may say unkown device) it should have a warning triangle right click on it select update driver software and then select browse from my computer and point to the drivers that you have downloaded see if that works.
Another thing to note is if you are using Windows 8 you need to disable Driver signature in start up options ( Google it) for Windows to recognize the drivers.
Click to expand...
Click to collapse
I already tried uninstalling Kies and Samsung drivers. Also I tried looking for device on Device Manager but it does not appear when I plugin my S3, but it does appear when I connect other devices like S2 or Galaxy Fame Lite. They appear as portable devices.
I'm using Windows 7 on my PC and have already tried with different OS over Virtual Machines and still doesn't work.
And thanks for that note, didn't know there was possible to flash a Custom Recovery without root, but I can't since ODIN doesn't detect device :crying:
Then it looks like you are running out of options I would use another computer not Virtual Machines
Okay I'll give it a try but as I said before, looks like an firmware issue, not computer's. Why would my computer detects two another Samsung devices but not mine (which used to work until last update)
Me, too!
I'm having a similar problem. Last week my GS3 stopped working, and I bought another one from Ebay with a cracked screen and swapped out motherboards. The phone seems to work as well as a stock Verizon phone on Jellybean would, but I can't get my Linux, Win 8, or Win XP computers to even recognize that it's attached. Different cables, each and every one of the USB ports, not even a blip. Device Manager in Windows doesn't even see it, and yes I got the developer options unlocked and have enabled USB debugging.
I've got the Samsung drivers installed, and tried to install the CWM device drivers from the SAMSUNG GALAXY S3 TOOLKIT V9, but there was an error and that didn't work, either.
USB connection issues are usually due to Windows conflicts, driver problems or the lead itself. If all these have been excluded then you have either a firmware issue in the bootloader, which is very uncommon, or a hardware problem. The usb port is easily worn/damaged/dirty also the motherboard might be the cause.
There is no silver bullet to cure, test each possible thoroughly.
boomboomer said:
USB connection issues are usually due to Windows conflicts, driver problems or the lead itself. If all these have been excluded then you have either a firmware issue in the bootloader, which is very uncommon, or a hardware problem. The usb port is easily worn/damaged/dirty also the motherboard might be the cause.
There is no silver bullet to cure, test each possible thoroughly.
Click to expand...
Click to collapse
I'm 100 percent sure that it is not due a Windows issue, I have already test every option. I have not considered the usb port to be damaged or worn, which could be possible but phone charges every time I connect it to computer. It just does not get detected as a device. But in order to assume it is a motherboard issue I will have to put away my feeling that the problem is caused by last OTA official update, since this problem started there.
If it is a firmware update issue, is it any option to flash another ROM?
Sent from my GT-I9300 using XDA Free mobile app
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
peter wagih said:
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
Click to expand...
Click to collapse
Sorry but the only option that works to root the S3 international is Odin no apps work at the moment:crying:
tallman43 said:
Sorry but the only option that works to root the S3 international is Odin no apps work at the moment:crying:
Click to expand...
Click to collapse
no man how is it ?? believe me it works try frameroot.apk
peter wagih said:
no man how is it ?? believe me it works try frameroot.apk
Click to expand...
Click to collapse
Not on I9300 international version on other variants yes. Believe me if it worked it would be all over the forums post a link showing who it as worked for thanks..
peter wagih said:
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
Click to expand...
Click to collapse
As I said on previous posts, I have already installed and reinstalled Samsung USB drivers and made a factory reset -one from config. option and another one from Android stock recovery 3e (since I cannot install any advanced recovery -or even root it- to flash a custom rom). Doing those factory reset did not downgrade my last firmware update (when all my problems started).
I also said on previous posts that I tried towelroot and framaroot with no success. As tallman43 says, seems like international version of S3 does not support those kind of one-click to root apps.
-----------------------------------------------------
So far the only options available (if my theory about latest firmware update is the problematic one) are:
● downgrade firmware: [Q] How? Odin is not working since my phone does not get detected;
● root my phone in order to install an advanced recovery and flash a new ROM: [Q] Any way of rooting phone without computer (apart from towelroot or framaroot because I have tried and do not work for me)? I read one XDA post from 2 years ago to root S3 via console apk but latest comments assumes that method stopped working.
● install an advanced recovery without odin or root: [Q] How?
● fix USB firmware issue: [Q] I have completely no idea how to do it. (Already played with *#7284# and *#0808# but did not get my phone detected)
Please I need help, this is really irritating me and I am running out of ideas
Sent from my GT-I9300 using XDA Free mobile app
I guess I have found out what the problem was. It was not firmware (as I thought). It was the micro USB port (as boomboomer said) which seems to not be firmly attached to the PCB. AC charging just seems to work okay, but not USB connections. I managed to figure it out by forcing the USB in a specific position to get it detected for 5 seconds, but then it disappeared.
Yeah, it was not as complex as I thought! I will try to replace that micro USB port as soon as possible, thanks everyone for your help!
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.