Hello. I ave ordered a Motorola Defy which should arrive in a couple of days from now. I'm pretty sure that it will be running on Android 2.1. So in all preparedness for the rooting, I have installed the Motorola Drivers and SuperOneClick V1.9.5(with driver pack).
So my question is, is all of this as simple as checking the USB debugging option, unmounting the SD card and clicking the root button. Sorry, I'm new to this stuff. Any help would be deeply appreciated.
-restart your phone while keeping the volume-up button pressed. This will get your phone into bootloader mode.
-Connect your phone to your computer via USB. Its bootloader drivers will get automatically installed.
-Restart the computer again and also restart your phone normally into Android this time.
-Connect your phone to your computer and let its normal drivers get automatically installed.
-Make sure USB debugging is DISABLED on your phone in Settings > Applications > Development.
-Launch SuperOneClick on your computer by right-clicking on it and selecting ‘Run as Administrator’.
-Click ‘Root’. It will say ‘Waiting for device…’
-Now ENABLE USB debugging on your phone in Settings > Applications > Development.
-Wait patiently till you see a prompt on your computer saying ‘Device is rooted’.
-Reboot your phone and you’re done!
All the best
What about the new version of SuperOneClick i.e. 1.9.5
I've read the same instructions on addictive tips. And they suggested an older version of SuperOneClick since it was written sometime ago. I've heard that there is an easier way of doing it with the newer versions of SuperOneClick. That's what I wanted to know.
I could not root my Defy with the newest version of superoneclick I used version SuperOneClickv1.5.5-ShortFuse the newest could not root my phone. You can try but if it does not work then use an older version.
You have to enable USB debugging and set usb connection to charge only, or else ADB cannot connect to your phone. Then press Root and wait till it says your phone is rooted.
Worked for me on my 2 Motorola android phones.
(owner of Milestone XT720 and Defy)
I use v1.7.0...and it works like a charm
Thanks
Thanks folks. I have a self of calmness in my mind now. I now have both the versions of SuperOneClick (1.7 and 1.9.5). I'll try it with 1.7 first. Can't wait to get my hands on the device tomorrow. Thanks again folks.
I've read that it is a must to unmount sd card. How do i do that?
Edit: Nevermind. Found it under settings>sd card
Help
gommers1978 said:
I could not root my Defy with the newest version of superoneclick I used version SuperOneClickv1.5.5-ShortFuse the newest could not root my phone. You can try but if it does not work then use an older version.
You have to enable USB debugging and set usb connection to charge only, or else ADB cannot connect to your phone. Then press Root and wait till it says your phone is rooted.
Worked for me on my 2 Motorola android phones.
(owner of Milestone XT720 and Defy)
Click to expand...
Click to collapse
When exactly did you root your device? And would the phone get bricked if it doesn't get rooted using newer versions of superoneclick?
chill man...it wont brick ur phone..yanta sav maga..estu yochasubeda(i hope u know kannada)
chethan316 said:
When exactly did you root your device? And would the phone get bricked if it doesn't get rooted using newer versions of superoneclick?
Click to expand...
Click to collapse
Dont worry dude! I am an adroid newbie too (Defy is my first android) and i managed to root it within 5 minutes in the first try itself. I also used 1.7 by the way.
arpith.fbi said:
chill man...it wont brick ur phone..yanta sav maga..estu yochasubeda(i hope u know kannada)
Click to expand...
Click to collapse
Hahaha You have no idea how hard I'm laughing right now. Nangu kannada barotthe maga
New rooting guide for for Defy
I can't post links so just go to tech journal com and search for root Motorola.
This just came out today, hope it helps. I'm going to try it and will report back.
Been looking for a while for something like this. It seems like there is nothing to it, at least going by other stuff I've seen.
Comments?
Football Fan said:
Dont worry dude! I am an adroid newbie too (Defy is my first android) and i managed to root it within 5 minutes in the first try itself. I also used 1.7 by the way.
Click to expand...
Click to collapse
How exactly did you do it with SuperOneClick 1.7?
arpith.fbi said:
-restart your phone while keeping the volume-up button pressed. This will get your phone into bootloader mode.
-Connect your phone to your computer via USB. Its bootloader drivers will get automatically installed.
-Restart the computer again and also restart your phone normally into Android this time.
-Connect your phone to your computer and let its normal drivers get automatically installed.
-Make sure USB debugging is DISABLED on your phone in Settings > Applications > Development.
-Launch SuperOneClick on your computer by right-clicking on it and selecting ‘Run as Administrator’.
-Click ‘Root’. It will say ‘Waiting for device…’
-Now ENABLE USB debugging on your phone in Settings > Applications > Development.
-Wait patiently till you see a prompt on your computer saying ‘Device is rooted’.
-Reboot your phone and you’re done!
All the best
Click to expand...
Click to collapse
Thanks so much. So this method worked for you with SuperOneClick 1.7 right? I just want to make sure that everything's alright when I'm doing it.
yup...follow the steps and it will be rooted..i used v1.7..my fone was rooted withing 2 mins
i dint go to bootloader before rooting it..just connected the phone via usb (n normal mode)and it installed all the necessary drivers..after tat restart ur comp...then ROOT it
tats all
chethan316 said:
When exactly did you root your device? And would the phone get bricked if it doesn't get rooted using newer versions of superoneclick?
Click to expand...
Click to collapse
I rooted my device 3 days ago (thats when i recieved my Defy) in all the phones ive rooted and all the rooting i ever did, i never bricked a phone.
No ive used the newest version and i did not work and no brick either.
For Android v2.1 I used 'z4root' without any problems. In v2.2.2 z4root don't work, then I use SOC 1.9.1 (for root) & 1.9.5 (for 'non market apps')
Related
Is there a way to root stock 2.2 that isn't unREVoked or z4root? I can't get unREVoked to work, just tells me to connect phone via usb and enable USB debugging. I have done this. Adb isn't working either, and z4root just sits at the screen for hours saying it's working. I just need a temp root for now, as I am having a usb problem where the phone reboots to 5 vibe whenever unplugged. I obviously want to get back to rooted, but just want to go one step at a time. Phone can read the SD, but my computer cannot recognize USB storage mode.
Is there a way to get this done?
Thanks,
dmeadows013
dmeadows013 said:
Is there a way to root stock 2.2 that isn't unREVoked or z4root? I can't get unREVoked to work, just tells me to connect phone via usb and enable USB debugging. I have done this. Adb isn't working either, and z4root just sits at the screen for hours saying it's working. I just need a temp root for now, as I am having a usb problem where the phone reboots to 5 vibe whenever unplugged. I obviously want to get back to rooted, but just want to go one step at a time. Phone can read the SD, but my computer cannot recognize USB storage mode.
Is there a way to get this done?
Thanks,
dmeadows013
Click to expand...
Click to collapse
Did you get the drivers for Windows and change USB connect to "charge only?" Not sure about how else to go about rooting to be honest.
Sent from my Droid Incredible running some random CM7 nightly.
SteveG12543 said:
Did you get the drivers for Windows and change USB connect to "charge only?" Not sure about how else to go about rooting to be honest.
Sent from my Droid Incredible running some random CM7 nightly.
Click to expand...
Click to collapse
I'm on mac
dmeadows013 said:
I'm on mac
Click to expand...
Click to collapse
Ahhh, fancy schmancy lol. I have very little experience with a Mac in general, and absolutely none with rooting on a Mac. Hopefully someone else could chime in and help ya out!
Sent from my Droid Incredible running some random CM7 nightly.
i think there's a video tutorial on how to root using mac os. its on youtube
jioleight said:
i think there's a video tutorial on how to root using mac os. its on youtube
Click to expand...
Click to collapse
This dude does it on a Mac: You Tube
It seems I couldn't find this phone in the list, maybe someone could help me root my device.
Or any links with regards to my phone on rooting is highly appreciated.
Phone Info:
Model : LG-E510
Android version: 2.3.4
Kernel version: 2.6.35.10-perf
[email protected] #1
Build number: GINGERBREAD
Software version: V10c-NOV-04-2011
Thanks!
bumping my post. thanks.
Ok. Bumping my post again.
Anyone please?
Hub Root
Hi,
I'm also an owner of LG Optimus HUB and I'm also intersted of phone rooting and flashing.
I have noticed that CyanogenMod have released a nigthly version of their ROM.
Thanks!
Just found your thread thru Google, because I wanted to see if there is already a LG Optimus Hub sub-forum here on XDA.
There is a same thread here with all the info you might need (my posts are relevant )!
Next time use the search function!
Hope I helped!
Thanks yani2000 for the link. I'll keep this thread up for any news or whatsoever regards to our device. Thanks again.
nothing's worked so far!
Well I started with superoneclick, it told me I didn't have any drivers and I chose the "force driver's option" before this the phone wasn't popping up when I hooked up the USB. It just show's on the phone "USB debugging connected". After that I tried running superoneclick and after starting the adb server it hangs up and dies. This is on win7 64bit with admin rights. I then downloaded the apk for gingerbreak and that just hung there for about 20+ minutes saying it would reboot if successful. After that I found a guide on how to install adb drivers, but after I run the "adb shell" command it tells me my device is not found. I uninstalled the drivers from my PC and i'm getting the same "device not found while trying to install adb drivers". Oh before uninstalling my forced drivers from superoneclick I tried unlockroot from unlockroot.com. It also said my device was not found. Not sure what the hell to do next! hope all this info helps you help me!
.
Thread moved. Would advise you to read forum rules and post in correct section.
just a stupid question, how can I go into Recovery Mode? I tried holding down Home key + Power button to no avail after shutting down the phone...
Recovery mode should be volume down+home key+power
But if you don't have a custom recovery on the phone all it will do is a factory reset.
trish43 said:
GUYS.. I need help with rooting my lg e510 optimus hub phone... any ideas..? please and thank you...
Click to expand...
Click to collapse
Did you try that tutorial I posted in that another thread?
Here is the link to the thread I'm talking about (also posted few posts up by me).
And here is the direct link to SuperOneClick ROOT Tutorial!
Please report back how it went in that other thread!
Thank you!
Thanks yani! My phone was successfully rooted!
SuperOneClick no longer requires alternate ADB
I just rooted my LG Hub (or E510f, or Univa) with SuperOneClick 2.3.3: only connecting the phone, USB debugging, no mounting SD. No alternate ADB. Just SuperOneClick.
djtreo said:
Thanks yani! My phone was successfully rooted!
Click to expand...
Click to collapse
Which method u followed to root hub
Esf files ?
How can I find esf folder in this device (E510-optimus Hub)?Root eksplorer is not find this folder.But imei is appear correct.
And How can I do imei backup? esf files is not to be root folder.thanks.
You should be careful with rom manager because it happened to me several times that I did a hard reset!
Sorry for my bad English
Retoño said:
I just rooted my LG Hub (or E510f, or Univa) with SuperOneClick 2.3.3: only connecting the phone, USB debugging, no mounting SD. No alternate ADB. Just SuperOneClick.
Click to expand...
Click to collapse
Likewise, it works!
did'nt work
Retoño said:
I just rooted my LG Hub (or E510f, or Univa) with SuperOneClick 2.3.3: only connecting the phone, USB debugging, no mounting SD. No alternate ADB. Just SuperOneClick.
Click to expand...
Click to collapse
it didnt work. when i tried to root my lg e510 with superoneclick it stopped responding after killing ADB. Can u recommend any other software for rooting?
Help please!
Installed GNex Toolkit v7.4
Selected phone model #14
Selected Option #1 and installed drivers
Selected Option #3 and successfully unlocked the Bootloader
Selected Option #4 to root and replied yes -
then phone booted into Android and I enabled USB Debugging -
messages from Toolkit are:
- <waiting for device>
- rebooting...
- finished. total time: 0.032s
- procedure will continue in 30 seconds
- Waiting for USB debugging to be enabled
At this point even though I enabled debugging the Toolkit just hangs here (waited 5 minutes at least) and nothing further happens with the phone - I believe I'm expecting another phone reboot?
If I go back to the Toolkit main menu under ADBMODE it has the device serial number followed by "offline" which I believe is the problem - phone is not getting 'online' in ADBMODE?
Thanks in advance for all replies.
Restart it?
I'm not sure how the toolkit works since I never used one..
biscuitownz said:
Restart it?
I'm not sure how the toolkit works since I never used one..
Click to expand...
Click to collapse
Restarting gets back to the same state.
If I try 'adb devices' directly it also shows the phone as offline.
Learn how to do it manually.
Its likely a driver problem. Usually is.
martonikaj said:
Learn how to do it manually.
Its likely a driver problem. Usually is.
Click to expand...
Click to collapse
Referenced thread talks about "return to stock" - I'm trying to go the other way - to install a custom ROM...
alanchase said:
Referenced thread talks about "return to stock" - I'm trying to go the other way - to install a custom ROM...
Click to expand...
Click to collapse
If your phone won't boot and you think you've messed something up, restore to stock and start over.
Then, while you're in there, flash CWM manually and push the ROM file and flash it via CWM interface.
martonikaj said:
If your phone won't boot and you think you've messed something up, restore to stock and start over.
Then, while you're in there, flash CWM manually and push the ROM file and flash it via CWM interface.
Click to expand...
Click to collapse
Phone boots fine - all this is new to me and these manual instructions often assume certain knowledge that I don't have, hence the appeal of the Toolkit option...
I recently sat my mother down and had her follow my guide on my phone.
She doesn't even know how to remove widgets from her screen...
And she did this without a problem.
Link in my sig.
I would agree with it being a driver issue...choose the install drivers option via the toolkit then retry
Sent from my Galaxy Nexus using xda premium
Xeckz said:
I would agree with it being a driver issue...choose the install drivers option via the toolkit then retry
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Already tried that - uninstalled and reinstalled the drivers and still it hangs during the root operation...
...and if Device Manager shows the phone without an " ! " then does that indicate the drivers are successfully installed?
Jubakuba said:
I recently sat my mother down and had her follow my guide on my phone.
She doesn't even know how to remove widgets from her screen...
And she did this without a problem.
Link in my sig.
Click to expand...
Click to collapse
Will look at your link - thanks.
Turns out it was a USB port issue - was using a front port - forgot that those sometimes can be less reliable than a rear port - switched to one of the rear USB ports and was able to proceed.
I had used "Galaxy Nexus Toolkit V7.7.0 to :
Unlock my BootLoader,
Root my phone
Rename Files Recovery
Flash Recovery (CWM Touch)
Install BusyBox on Phone
And now, i have install the rom JellyBean 4.1.1 with the Recovery Mode :
(I take the Rom here : http://forum.xda-developers.com/showthread.php?t=1737849)
After HAVING done all of this, i try to boot my phone, but he remained stuck on the loading screen (animation) ... even after 1 hours of waiting....
I had go back in recovery mode and I "Wipe" all the DATA, now there is no more operating system on my phone and i'm not able to install a new ROM and i can't even go thru my phone data via USB cauz my computer not recognize my Samsung Galaxy Nexus anymore...
Someone can help me I think I'm in big trouble right now...
This is the problem with toolkits. Things can go wrong and you don't know where it went wrong. See my signature for my thoughts.
As far as getting your phone working again. Follow efrants guide http://forum.xda-developers.com/showthread.php?t=1626895 it has all the info you need to get up and running.
Sent from my Nexus 7 using xda premium
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Also, can I ask you which recovery you have right now? Is it clockworkmod or stock?
Ok thanks i try this right now... Hope it will work, i'm freaking out at the moment...
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Epsilons said:
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Click to expand...
Click to collapse
Make sure you uninstall any unrelated drivers first. Then proceed with the driver installation.
Sent from my Nexus 7 using xda premium
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Epsilons said:
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Click to expand...
Click to collapse
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
I've been seeing issues with the toolkits and rooted my phone hours ago using adb, worked flawlessly except the drivers lol.
But after I got that resolved it worked, no jb issues and no other issues. Recovery stuck as well.
Sent from my Galaxy Nexus using Tapatalk 2
El Daddy said:
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Witch driver ? The SAMSUNG or the Universal Naked Driver
Epsilons said:
Witch driver ? The SAMSUNG or the Universal Naked Driver
Click to expand...
Click to collapse
They both should work fine (I got Samsung one installed and works flawlessly), but Naked Driver is better I believe
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Epsilons said:
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Click to expand...
Click to collapse
OK so it looks like you have the driver installed.
What is telling you to enable USB debugging mode?
Read the link I posted and flash the stock image via fastboot.
Sent from my Nexus 7 using xda premium
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Yes, I realize you can't do these things. I gave you the info to fix your problem in the second post.
You need to boot into the bootloader and flash the stock images with fastboot. I don't know how much clearer I can be.
Be patient with rooting, frustration will lead to mistakes.
Sent from my Galaxy Nexus using Tapatalk 2
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Ordinarily, I don't recommend tool kits either, but in this case you quite frankly seem like the kind of fella that needs one. SO HERE IT IS. This is a different toolkit than you used before. Be sure to select the correct device first off(because this works with ALL Nexus devices not just one), then do the part entitled "Initial Setup". Do the FULL DRIVER INSTALLATION. It may be that you don't need to, but it will not hurt so do it anyway. After that, click on the "won't boot up" checkbox under "Flash Stock + Unroot" button, then click the button. At all times, read and follow directions. I used this toolkit once, now I do things manually. But you seem incapable. Not intended to be insulting, just a statement of your technical aptitude. Not everyone can do this stuff. So if you have tried EVERYTHING above and been unable to complete any of it correctly, then try this. It isn't one-click and requires some amount of effort on your part. My 11 year old nephew did it though. Good luck.
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
As El Daddy said, you are not reading the instructions. Your fastboot driver IS installed properly if you see "Samsung Galaxy Nexus BootLoader Interface". Follow the instructions step-by-step. You do NOT need to see anything in "My Computer". It seems like you are panicking, and not reading...
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
kyokeun1234 said:
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Click to expand...
Click to collapse
And let's not scare the guy: you CANNOT "brick" your device using a toolkit. There is a big difference between not being able to boot because of a bad flash (not a brick), and a device that cannot boot at all (i.e., a brick).
It seems like people are using the term brick to mean a lot of things other than what it was meant to mean: "bricked" means that you cannot boot your device without JTAG, or sending it in for repair, i.e., it's as useful as a brick.
Ok thank you everyone, sorry about my patience tonight...
Now ma Samsung Galaxy Nexus is on Jelly Bean 4.1.1 with SuperUser and all the stuff and i'm happy
So thanks everyone.
I got it
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...