Hi.
I know it's been talked about a thousand times alreay, I hate to open a new thread, but I really tried every option I've found to root my new GT540g
Z4root Androot and SuperOneClick, none works
I put my phone in "USB debug" but it seems like none of this programs are realizing that
I also tried with the root.bat (http://forum.xda-developers.com/showthread.php?t=803238) method, and nothing
When I connect my phone, if I start the LG Mobile Update program, it can see my phone
but when I ask adb to do the same, like with a simple "adb devices" it cannot find it
I'm on Win7 x64, and have already reinstalled the drivers a LOT of times, even switching between the oficial and some drivers I've seen on the forum
Please, help me
Is there an error message?
in adb it just says "device not found"
switch off the 'mass storage only' option if it is on
I've tried with both mass storage on and off
this is puzzling
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
try universal androot it works apparently
Doughnut said:
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
Click to expand...
Click to collapse
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Have you installed the adb drivers? Without them adb can't see the phone. Even if you put it in "Debug mode". You can download them with google's android sdk package.
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Mitalca said:
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Click to expand...
Click to collapse
good you sorted it, sounds like you had driver overload
JackG256 said:
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Click to expand...
Click to collapse
Easy, because its not to my expectations.
So I deem it unworthy, its a matter of opinion rather than fact, so probably pointless debating.
Someone has messaged me from this forum asking to buy it for £21, they're welcome to do so.
try this : http://www.4shared.com/file/p3TR1eih/autorootapp2sd.html
Hmm. I'm assuming you are on 2.1.
I happened to see people come across problems on Win7x64. I'd highly recommend you try it on WinXPx32.
z4root works perfect.
http://forum.xda-developers.com/showpost.php?p=9109591&postcount=1
I have tried both root.bat method and z4root. Both worked fine for me. However, I personally prefer root.bat.
Pretty much any rooting app that supports Rage Against The Cage exploit would work on GT540.
Use my information at your own risk!
And, like Mitalca suggested, you might want to try uninstalling all drivers and a clean reinstall to prevent driver conflicts.
In any case, more than the LG drivers, you'd need ADB drivers.
Mitalca said:
in adb it just says "device not found"
Click to expand...
Click to collapse
Try to remove sdcard or disable it from menu storage.
why don't you try a custom ROM such as LewaOS or SDSL... Just flash it and your phone would be rooted already, and it's much featureful and runs faster than the stock ROM
Glad to see your sorted
I would have said it works on Win 7 x64 because I use it
I also use ubuntu on the same pc, but thats besides the point.
Anyways, glad to see your sorted, and enjoy your phone!
Try to change rom
Try z4root for rooting your GT540. It works fine on our phone.
Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Jeez I love the vibrant but I'm so unbelievably annoyed. First I rooted my phone and flashed clockwork mod recovery in order to delete some bloatware, not that I needed the clockwork mod recovery right now but did it anyway. So after that my Vibrant lagged, my sync was broken and my market no longer worked, so I used Odin to get back to stock thanks to a good suggestion and now I am attempting to root again and I would prefer to root through ADB but hence here we go again more annoyances, for some reason Windows 7 does not recognize my device in debugging mode. I have installed the drivers and it says "drivers installed successfully and ready to use" yet when I go to device manager it says "no driver files installed" and does not recognize my device. My nexus one, Mytouch and G1 were SOOOO much easier to work with, never had a problem.
So can someone help me out? Why is windows 7 sucking the big one right now? I can obviously root by just putting the file in my root directory, booting in stock recovery and doing update.zip so that's really not the big deal, the big deal is, I WANT ADB, this is pissing me off. I can't do anything in ADB because my device is not listed / recognized
justanothergirl said:
Jeez I love the vibrant but I'm so unbelievably annoyed. First I rooted my phone and flashed clockwork mod recovery in order to delete some bloatware, not that I needed the clockwork mod recovery right now but did it anyway. So after that my Vibrant lagged, my sync was broken and my market no longer worked, so I used Odin to get back to stock thanks to a good suggestion and now I am attempting to root again and I would prefer to root through ADB but hence here we go again more annoyances, for some reason Windows 7 does not recognize my device in debugging mode. I have installed the drivers and it says "drivers installed successfully and ready to use" yet when I go to device manager it says "no driver files installed" and does not recognize my device. My nexus one, Mytouch and G1 were SOOOO much easier to work with, never had a problem.
So can someone help me out? Why is windows 7 sucking the big one right now? I can obviously root by just putting the file in my root directory, booting in stock recovery and doing update.zip so that's really not the big deal, the big deal is, I WANT ADB, this is pissing me off. I can't do anything in ADB because my device is not listed / recognized
Click to expand...
Click to collapse
That's why I am doing all my development work on a linux box Try removing the driver and cleaning the registry (I am not sure if Win 7 has such a thing) and re-install the drivers. Put the the phone in USB debug mode and connect to the PC.
Certain you installed the right ones? Seems like it took a few times before I found the ones that worked and gave the adb connection in device manager. Been a while, but pretty sure i had to download Kies and unzip the .exe to find the drivers. The final .exe is called "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (nice name..) and its version 1.3.750 and is about 18MB.
After that, worked like a charm
fearmonkey said:
Certain you installed the right ones? Seems like it took a few times before I found the ones that worked and gave the adb connection in device manager. Been a while, but pretty sure i had to download Kies and unzip the .exe to find the drivers. The final .exe is called "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (nice name..) and its version 1.3.750 and is about 18MB.
After that, worked like a charm
Click to expand...
Click to collapse
Yeah that's the one I installed. I have no idea why Windows 7 is being a super douche.
justanothergirl said:
Yeah that's the one I installed. I have no idea why Windows 7 is being a super douche.
Click to expand...
Click to collapse
Meh, i blame samsung on this one. Once i finally got it installed, seemed to do ok..
but it is slowly coming back to me now..yes.
So, rename/unzip that SAMSUNG*.exe file to a directory. Probably will ask to overwrite some files (why they are in there twice..no clue). Run the setup.exe. Boom!
I'd uninstall them and re-install to verify..but, I kinda like having adb around and I already wasted a couple hours trying to get it to work that first time..
That worked! Thanks a million! You rock <333
Problem 1: (trying to get fastboot to work)
I downloaded the latest SDk and used the drivers in there. When I goto "update" my Android ADB driver and point it to the the google usb driver, it tell me to go jump off a bridge.. Though I fail to see how that will make my driver install
Anyway that's where i'm stuck, i've tried replacing the .sys files and blew up my XP blue screen at boot which was awsome..
I'm trialing a Streak to replace my iPhone4, This seamed to be the only phone so far that really WOWed me, that was until I used it, with 1.6 it's no iPhone killer..
I am also a previous HTC Advantage user, so i like big phones...
Any Ideas? Maybe i need the old 1.6 SDK Drivers?
This is all to get FastBoot to work, so i can start installing roms.
Problem 2:
Is there anything that I need to be careful of having an ATT phone over an 02?
try dell's drivers.
I found that using XP I had to install the drivers multiple times for it to register the Android 1.0 or whatever.
I simply used the QDL Tool on my locked-to-contract AT&T Streak 1.6. Like I said, I had to install the ADB drivers multiple times (I think that is their name) for it to finally go through. And then on the 4th time or so, it all went smoothly and I'm now running the "official" 2.2
I did nothing special. Just ran the Tool, installed the drivers, if it failed, I installed the drivers again, and ran the Tool again. I think maybe 4th time of installing drivers was the trick. I don't know what I did differently on the last time, but it worked just fine.
subvecto said:
try dell's drivers.
Click to expand...
Click to collapse
Tried that as well, no dice...
stang393 said:
Tried that as well, no dice...
Click to expand...
Click to collapse
That is strange... I was able to get dell recognized by win7 only via drivers that was installed via dell PC sync software...
Sent from my Dell Streak using Tapatalk
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
My Evo gave me grief for a solid hour when I first got it. Followed the walkthrough here and one of the contingency plans worked like a charm.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Thanks, but it is not a driver problem as the drivers are installed correctly and ADB can see the phone connected.
I tried on 3 different PC's, replaced US cables. everything failed.
I think something is up with my unit which will be going back tomorrow.
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
So it worked fine before you rooted it?
Yes, SuperOneClick is using ADB to push the root files, so i assume ADB worked then.
I am also getting constant device reboots (random) so i think there is a hardware problem. i'll take it back tomorrow.
I had drivers installed, but the set of drivers PDAnet ended up installing for me fixed the issue. Till I get my paycheck, I won't be able to play with it
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
I am now on my 4th phone - so will be waiting for things to simmer down before I go back to modding again, but the other 3 have all had the same issue after using the superoneclick to root.
Once root is done all ADB access goes away. Something is amiss.
edit: More specifically my 4th atrix.
airbillion said:
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
Click to expand...
Click to collapse
I ended replacing the phone as I had other problems with it. Now a adb works fine even after root.
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
SNadler said:
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
Click to expand...
Click to collapse
It does not solve the problem.
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
airbillion said:
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
Click to expand...
Click to collapse
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
clubtech said:
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
Click to expand...
Click to collapse
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
airbillion said:
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
Click to expand...
Click to collapse
I tried restoring my device to factory default several times. It did not solve the ADB problem and not my random reboot problem (even with zero 3rd party apps installed).
I tried installing ADBWireless from the market - no go.
I googled and found a command to run via local terminal to force ADB to stay up - no go.
I finally came to a conclusion that a) I have bad hardware because my device was rebooting b) i can't fix the ADB problem without a full SBF file which we don't have.
Went to at&t, got it replaced. no more reboots. rooted with superoneclick and did not do the sideload fix from that app.
Then i manually edited the settings.db file to allow sideloading and been running fine ever since.
Clubtech,
Thanks for the file! It works for me!
Here is a post on the fix: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1
Can anyone explain this for a noob? i just want aRoot to work and the HDMI cable thing to work... the oneclickroot worked but nothing else will and i think it is because ADB is not recognized...
I finally did it. Didn't have to unlock, rollback the firmware, ADB, or anything too drastic. So happy.
I used this method here.
http://forum.xda-developers.com/showthread.php?t=1706588
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers. Can download it here if you're as incompetent as me (Under Utilities). Exit out Asus Sync in your system tray before attempting the method above. And I'm probably not the guy to ask for any help if you got problems or questions.
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
I installed OTA RootKeeper afterwards.
Thanks XDA. Thanks sparkym3.
I think you should give yourself more credit.
GJ
thanks man!
-Bang
supersoulfly said:
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers.
Click to expand...
Click to collapse
This works indeed, but you must stop ASUS sync if it's running. If you don't, the version of ADB packaged with ASUS Sync is different from the one in the zip file and you'll get a whole lot of lines with "adb server is out of date, daemon started successfully" which mess with the script.
Once I stopped the Sync thing from systray and verified in task manager, the script ran like a charm.
So, another TF300 with .29 WW rooted, thanks to the people involved in making this possible
all this confused me way too much but luckily for me i had help (well i say help he did it all via teamviewer lol) from thing o doom he is a star
I used this method too on my 29.WW,thx guys
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
jakelikescake123 said:
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
Click to expand...
Click to collapse
Ummmm.....I think I confirmed it, in the first post.
supersoulfly said:
Ummmm.....I think I confirmed it, in the first post.
Click to expand...
Click to collapse
im the idiot
thanks
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
lightiv said:
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
Click to expand...
Click to collapse
May not be the issue, but it's happened to me several times rooting & ROMing phones - plug the cable into a rear USB port that's on the motherboard. The USB ports on the front of the case don't always work for some reason. The front of my case has 6 ports and I can only get reliable phone connections on 2 of them. Down right squirrely!
ID10T Error on My Part
Turn out to be an ID10T error on my part. I had DroidExplorer running from when I rooted my cellphone. I finally ran across a post that made reference to it and killed the process. It took all of 30 seconds to root once I killed the process.