• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ASOP on Hammerhead, yellow exclamation mark in control panel.

Codec

Android Enthusiast
Was trying to backup my ROM with clockwork recovery but it fails every time and I looked in control panel and noticed this, how do I fix it?
ASOPonhammerhead_zps419d267e.jpg
 
I also have this right now after unlocking bootloader and loading a recovery. Phone now isn't showing internal storage and I can't adb push or adb sideload as it says error: device not found

I hate this, what is going on? This was supposed to be easy / foolproof.
 
Yep.

It seems there is an important step that can't be avoided after unlocking the bootloader and before flashing a recovery, that is you must reboot the device to reestablish the file system, not go straight into flashing a recovery.

See the replies after this one for some explanation / further info: http://androidforums.com/nexus-5-all-things-root/791039-help-rooting.html#post6296257

Codec I suggest you flash the factory image and try again. I will soon.
 
Was trying to backup my ROM with clockwork recovery but it fails every time and I looked in control panel and noticed this, how do I fix it?
ASOPonhammerhead_zps419d267e.jpg

I wouldn't expect the above to be a problem for the recovery backup as I would assume it would be using your Samsung ABD drivers. The above is, I think, Windows looking for MTP drivers.
 
Install the Universal Naked Drivers and you'll be good to go.
I did that but why does it say Samsung Galaxy Nexus ADB interface? Wast trying to backup ROM again and clockwork is giving me an error saying error processing ROM manager script. Please verify that you are preforming the backup, restore or ROM installation from ROM manager v4.4.0.0 or higher.
 
I did that but why does it say Samsung Galaxy Nexus ADB interface? Wast trying to backup ROM again and clockwork is giving me an error saying error processing ROM manager script. Please verify that you are preforming the backup, restore or ROM installation from ROM manager v4.4.0.0 or higher.

That's fine. Mine does the same, but ADB works, which is all that matters to me. Not sure about the ROM Manager issue though. I install all of my recoveries via fastboot or through flashable zips.
 
I used WugFresh toolkit to root, you are referring SDK manager, I could never get that to launch, it just flashes the command prompt and then immediately closes.

do you mean when u attempt to open adb i can help you with that just reply and i will post steps close enough to help you you know what here


THIS ALL HAPPENS IN CMD
ok i assume you installed it to your C: or what ever so from here you will see the C:Users/(user name or close to this) now do the command cd.. until its just the C: showing or as far it will go now enter cd android-sdk[ENTER] then cd sdk [ENTER] then cd platform-tools [ENTER] then cd adb and that should launch adb
 
I used WugFresh toolkit to root, you are referring SDK manager, I could never get that to launch, it just flashes the command prompt and then immediately closes.

do you mean when u attempt to open adb i can help you with that just reply and i will post steps close enough to help you you know what here


THIS ALL HAPPENS IN CMD
ok i assume you installed it to your C: or what ever so from here you will see the C:Users/(user name or close to this) now do the command cd.. until its just the C: showing or as far it will go now enter cd android-sdk[ENTER] then cd sdk [ENTER] then cd platform-tools [ENTER] then cd adb and that should launch adb

What he's mentioning occurs because he doesn't have the Java JDK installed on his PC. Once that is done, you have to set a variable in the environment to detect JAVA_HOME.
 
Back
Top Bottom