I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
Related
Greetings fellow GNex owners and enthusiasts!
I've been trying to root my Galaxy Nexus unsuccessfully for the past week.
Here's what I've done so far:
1. I Unlocked the bootloader as per Droid-Life's instructions using an old method with the cmd prompt. (The complete How-To guide on their website) I installed the SDK on a windows 7 64-bit machine and went ahead with the process. This worked fine.
(*Note: My Gnex is stuck on 4.0.2 and it won't pull an update. I've tried the method of clearing the data from the framework app and resetting the clock to 1969 multiple times without success. probably 10-15 times.)
2. Since that I've tried uninstalling/reinstalling drivers, rebooting, and then rebooting some more. I've tried every available "noob-proof" method out there and i can't get it to work.
Tried Galaxy Nexus Tooklit v5.6
With and without the included drivers. tons of reboots and re-tries. root always fails.
Wugfresh's Toolkit 1.3
with and without the included drivers. tons of reboots and re-tries. root always fails.
Manually pushing CWM Recovery and SU to the phone with cmd promt via other tutorials floating around the internet, etc. Pushing CWM Recovery fails. Can't even get the temporary flash going to install SU
NOTHING works.
Is it because I unlocked the bootloader manually using an older method first?? I'm pretty sure I've been following the various instructions with each method accurately.
Can someone shed some light on me? I don't necessarily want to mess with kernels and custom ROMs. I just want to be able to wirelessly tether like I could with my OG and D2.
Thanks in advance,
Thanassi
Check my sig and try my method?
Haha.
But I'm guessing driver error.
The simplest method for getting drivers is to download and install pdanet on your PC. Then simply try again.
http://junefabrics.com/android/
I've had to root my phone 3 times and each time took 3 tries before it took. As mentioned before also make sure your drivers are good. And su files.
bow chicka wow wow.
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
shohratshankar said:
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
familyguy59 said:
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
Click to expand...
Click to collapse
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
shohratshankar said:
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
Click to expand...
Click to collapse
Yes. You don't need the SDK, as a matter of fact
The Rundll32 part, is a fact, when installing the drivers...
It has the following effect:
You have installed ADB drivers (no Rundll32). You are flashing away, and all of a sudden. BANG! Everything stoppen. Phone's bricked... Why? Windows thought it is being smart, and installed new drivers, whilst you were working. However, with the RunDll32 command, you can tell Windows, that YOU want to install the drivers manually, and check manually. Of course, you can turn this off, if you want. No prob. but I personally recommend leaving it off
It's saved many phones' lives ^^
so you are having trouble with the adb or fastboot drivers? is so i had this problem too and sometimes even have to reinstall those drivers after flashing a rom.
i had to manually install the drivers using device manager, just select the android device and go to update driver. Choose "Browse my computer for driver software" then pick "Let me pick from a list of device drivers on my computer" then choose Google in that list.
Error
familyguy59 said:
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
Click to expand...
Click to collapse
I get an error message with this application whenever I attempt to do something.
tried that
shohratshankar said:
I'm a noob too.
I followed the following method:
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
thanassi44 said:
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
GSM only??
efrant said:
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
Click to expand...
Click to collapse
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
thanassi44 said:
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
Click to expand...
Click to collapse
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
FINALLY! Have Root.
efrant said:
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your responses and suggestions. I finally got something to work. After some more driver swapping and rebooting, now on an XP machine, I got wugfresh's toolkit 1.3 to flash cwm recovery and I was able to install su. The program then ran an automated script to allow permanent flashing of cwm recovery. Got my titanium backup and from manager back, as well as wireless tether. Thank you all for your attention and patience!
Had such a hard time with this phone that I was beginning to have buyers remorse. Now its been set free.
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Sorry, but I've tested this program, over and over. I use it, myself. I never habe any problems...
But, I'm in the making, of a Youtube video. I'll post it, in my thread Then maybe you can see, what you did wrong
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Hang on... Did you install the scnd. file, within the ISO? If not, there's your problem...
Hey Guys,
New to the forum here and quite a noob on Android Systems. The GNex is my 1st smart phone and I've had it for 6 months now.
Wanting to root, unlock, and flash the new JB rom onto my phone and is using the ToolKit for the process.
-----------------------------------------------------------------------------------------------------------------------------------------
The original problem is now immaterial, what is bothering me now is installing drivers.....I cannot seem to find a way to properly install the proper drivers for my galaxy nexus. All my laptop would do is install the stock drivers upon connecting the phone to the laptop.
It doesn't matter what drivers im trying to install the condition is the same. I've so far tried out two ways, 1st is following the step by step instruction from efrant, 2nd is installing using the Galaxy Nexus ToolKit v7.0.
For a android noob like me I really have no idea what is going on here @@"
oh and what role does "USB debugging" play in installing drivers? when should it be ticked and when should it not???
----------------------------------------------------------------- below is my original question posted --------------------------------------
However during the 1st step where I need to select my firmware build, I realised the IMM76k build is listed under CDMA where my GNex has this build but is a GSM model.
How should I proceed?? Choose a similar build under GSM or choose the correct build but under CDMA instead??
thanks guys
I would root,unlock, and flash recovery via adb so incase something doesn't work you'll know what happened. Also if you want to use the toolkit just select the correct version under gsm and install the drivers. It should work
I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
actually I was going to do it your way by following through all the steps you have listed out. Like you have said somewhere its like learning math 1st before using a calculator.
However I found myself stuck at the very first part.....installing drivers....
Before yesterday I have not tried to install any driver myself. I guess the only driver that was ever installed to my PC is the one that automatically runs when you plug your phone into a computer for the first time.
When I was following your steps, I first went into device manager --> galaxy nexus --> details --> uninstall driver
and then I have no idea how to install the drivers that I have DL from following your steps. I remember in the instructions you said to plug in my GNex and I should be able to direct the PC to install whatever driver I want, but instead the PC just automatically installed the original drivers again...
So today I decided to give the toolkit a go. As you have seen the 1st problem I ran into was the mixed up variants.....(what does "build code" stand for anyways??)
And the second problem im having now is, again.....it wouldn't install the universal driver. Or at least it does not seem to have installed....
Well, now that I've got your attention D) I would like to follow your steps again if I can get pass the driver issue....I like the JB rom you have uploaded better anyways~~ fan of original stuff from Google!
thanks!!!
Just to mention, my purpose of doing all this is to get to JB faster, and maybe learn more about my device on the way.
My GNex is a GSM model, yakjuzs, build code is IMM76k (this is the odd part) if these information would help solving my problem.
I normally prefer stock google released ROMs.
@CloakedUltraling, installing the drivers is the only tricky part. You need to get to the point where you see something like "Android 1.0" in your device manager with a yellow exclamation point.
To get to that point, right click on anything you see related to Samsung or Android in device manager and click uninstall. Then go to View in the menu at the top and select show hidden devices, and uninstall anything related to Samsung or Android. Then reboot your PC, and once booted, plug your device (while it is booted into the bootloader) to your PC.
Now, you should see something like "Android 1.0". Right-click on that and select update driver, then follow the menu to manually install it, and navigate to the directory where you unzipped 1wayjonny's driver. This needs to be done TWICE: once when your device is booted into the bootloader, and once when it is booted normally.
i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??
CloakedUltraling said:
i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??
Click to expand...
Click to collapse
SDK is not required for you (unless you are developing... )
Drivers need to be installed before you can use adb and fastboot - one for each.
Sent from my Galaxy Nexus using Tapatalk 2
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
don't use windows..
Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles
chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Could you walk me through your fix?
Mods please delete double post sorry
ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.
I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave
if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium
Samsungs older drivers: uploaded.net/file/hdh0f1xd
Hello Everybody,
I habe a really big Problem with my GNex.
Today I Copied some Files over to my PC. For this I used for the first time "USB Mass Storage". Because I haven't seen some Files wich i can see under my Phone.
It worked really good. I unplugged my phone and to my things. Some minutes later i Heared the "Pling" from superuser. Then my phone was really slowly and need a bunch of time only to open the Launcher. So i deactivated Superuser. Deinstalled USB Mass Storage and MyMobiler.
After this i rebooted my Phone 2 times and the lag on my screen was gone. But now i'm unable to Access the Device under Android booted as MTP.
Even after reinstalling USB Mass Storage i'm unable to Access the Device via MTP or Mass Storage. My Windows PC and Android don't says anything. My Device is only Loading.
So i Unlocked my Bootloader with "BootUnlocker" and updated my System with offical Google Update 4.2 "fastboot update image-yakju-jop40d.zip" .
But i cann't access my Device now. Only fastboot is working.
So i'm unable to backup all my data and do an Factory Reset.
Have anyone out there an Suggestion how i can fix this Problem.
My Device:
Galaxy Nexus
Stock: 4.2
BL: Unlocked
Root: No Root (But with BL unlocked should this be the smallest problem.
Best regards and Thanks
Chris
P.s Sorrry for the really bad English
P.s.s Fastboot is working ... so it don't seems like an HW error
The nexus doesn't have use mass storage
Sent from my Galaxy Nexus using Tapatalk 2
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Chris302 said:
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Click to expand...
Click to collapse
have you tried a different usb chord?
simms22 said:
have you tried a different usb chord?
Click to expand...
Click to collapse
Yes i tried another USB-Cord.
Same thing -> Phone is Charging but not resposing over ADB.
And also i can't see it in the Explorer.
Same thing at my GF PC (Win Vista)
are you trying to use adb in the bootloader? if so, that will never work. ever.
Zepius said:
are you trying to use adb in the bootloader? if so, that will never work. ever.
Click to expand...
Click to collapse
No i'm using Fastboot when i was in BL to confirm that i have no HW error.
I try to ADB when i booted my Phone.
Or to access the My Device via Explorer
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
danger-rat said:
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
Click to expand...
Click to collapse
I Don't think hat There is my Problem, because under Windows i can Not even See my device it is not even recognized.
I can test driver uninstalling but i can not see my device under the device manager
:/ it seems like my android is f****ed up because root is also not working :/
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
danger-rat said:
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
Click to expand...
Click to collapse
I want to clear some things.
Don't think i want to shame you, i really thankfull for your help . Also it is the Best forum for Android Development and everything around it wo i have ever seen.
I was always on Stock. I updated the Offical 4.2 to 4.2 with an Stock image, it is now working again, i think the Update cleaned the Things up. Only Thing (shame me) i have forgotten to check after update is under-> settings -> storage -> Menu -> USB-Connection -> and check there "MTP".
So now my Device says connecting as "MTP" and my PC also recognize it again.
Before that my Device don't even say connecting as MTP.
I know that i will loose root when i update my Device -> but with my unlocked BL I just Booted to CWM and flashed Superuser.
Maybe (i hope) you are willing to help me again.
I am unable to update my SU binary and also i dont see a Message from Superuser, where i can allow Root access.
Even if i set under Settings -> Security -> Automated Answer -> "Allow"
I don't see the Message where i can say "allow" to Root access. I cannot even install SuperSU.
Have you any idea why it seems like i cannot access Root. For me it's seems like my app's don't recognize root.
When i Start SuperSu he says "Su-binary" must be updated" and next step is "Installation failed".
Have you any Idea where this came from?
But the good thing is at this point i'm abel again to access my Device via Explorer Thank you really really much for your Help You can't belive how glad i'm not to do a Factory reset and loose all my data.
Thank oyu for your great help
Chris
P.s. Root is working from Shell
Please read forum rules before posting
Questions and issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Chris302 said:
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Click to expand...
Click to collapse
Use SuperSu instead of Superuser.
Sent from my i9250
bk201doesntexist said:
Use SuperSu instead of Superuser.
Sent from my i9250
Click to expand...
Click to collapse
Sorry for the long delay.
I had no time to check this thread. And also my Email Notification hasen't worked.
So I hope you still look at this and can also suggest something.
I tried SuperSU but supersu says.
He need to install the Binaries.
After roundabout 15 seconds i get an Error message which says: "Installation failed".
My Super user tells me that the Binary is outdated.
And i get this Error Message in SuperSU even when i say "Answer every Permission Request with Allow".
I Even tried to remount the System as RW and the say update. But Both of them Seems to fail to install the Binary.
I flashed Superuser Through Temp Booted CWM.
Is their another Zip that i can try ?! or have i done something wrong while Flashing ?
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Chris302 said:
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Click to expand...
Click to collapse
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
bk201doesntexist said:
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
Click to expand...
Click to collapse
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
I recently reverted back to stock 4.2.1 (just to try it)
My Win7 computer was unable to see my phone when connected in MTP mode. Nothing showed in the computer at all, However when I selected PTP I could acess the DCIM folder.
In the end I couldn't be F**Ked with it so I pushed a custom rom to data/media/ and every thing was normal again.
I spoke to a friend who had the same issue I had, and he just enabled debugging (which a custom rom has enabled by default) to solve the issue.
Chris302 said:
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
I have not tried Superuser again since Chainfire released Supersu and all those issues rose with JB.
Chris302 said:
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
Click to expand...
Click to collapse
http://www.google.co.uk/search?q=xd...&sugexp=chrome,mod=0&sourceid=chrome&ie=UTF-8
would take you to:
http://forum.xda-developers.com/showthread.php?t=1538053
flash that
p.s: on the supersu thread says you need to be rooted... for us, of course, it's not quite true, rather we need unlocked bootloader and custom recovery.
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
doublewhamy said:
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
Click to expand...
Click to collapse
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Aerowinder said:
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Click to expand...
Click to collapse
I appreciate the assistance!