Develop Bugs

Help! Power button broke and have to return to stock

So the other night, my power button literally stopped working. I called Verizon and requested another device to be sent to me, but now I have to return this thing to stock before I send it back. I've tried to Galaxy Nexus Root Toolkit by Wug, but my device won't show up. I can't get into bootloader mode because my power button won't work!!
Is there anything else I can do?

matt6906 said:
So the other night, my power button literally stopped working. I called Verizon and requested another device to be sent to me, but now I have to return this thing to stock before I send it back. I've tried to Galaxy Nexus Root Toolkit by Wug, but my device won't show up. I can't get into bootloader mode because my power button won't work!!
Is there anything else I can do?
Click to expand...
Click to collapse
Is your phone on? Just use adb's command "adb reboot bootloader". If your phone is off, I don't know how you can turn it on without a power button.
Sent from my Galaxy Nexus using xda premium

connect to your computer and use
Code:
adb reboot bootloader
when you finally need to power it off to send it in, just pull the battery.

adb won't recognize my device. =/ It's stuck off.

You shouldn't have to worry then because they won't be able to turn it on either. lol

[email protected] said:
You shouldn't have to worry then because they won't be able to turn it on either. lol
Click to expand...
Click to collapse
Lmao, now thats funny......and it makes sense
Sent from my Galaxy Nexus using xda premium

Do you get some sort of animation when it's plugged into the charger?

if its on
open terminal and type:
su
reboot bootloader
if its off use a usb jig to get into odin mode

[email protected] said:
You shouldn't have to worry then because they won't be able to turn it on either. lol
Click to expand...
Click to collapse
Uh.. Yeah they will. The physical power button isn't working but as they unscrew the Galaxy nexus they can trigger the mechanic to power the phone on. And then just replace the button and reflash it to stock and then resell the phone.
If they see that the device was already bootloader unlocked, don't be surprised to see additional charges on your next bill.
Sent from my Galaxy Nexus using xda premium

Have you tried the GN Toolkit: http://forum.xda-developers.com/showthread.php?t=1392310
If i remember correct, when the phone is ON, you can connect the phone, then reboot it with the GN toolkit to bootloader and install stock.
I think that could solve your problem

Take the battery out, plug the phone in, and then replace the battery. See if it will power up by itself.
Sent from my Xoom using Tapatalk

Things I have tried:
GN Rootkit (adb/fastboot won't recognize device)
Plugging phone into computer and restarting computer
Draining battery and allowing to charge in phone until enough juice to turn on automatically
Plugging phone in with no battery
Nothing will work. Never tried a USB jig. Guess I will order one and see if that helps. Never used one before but I guess a google search will help. Guess I'll call Verizon and ask them to extend my return period before they bill me for the device.

Tried the naked drivers?
http://forum.xda-developers.com/showthread.php?t=1379875

Usb jig will bring you to download mod ,then you have option to reboot(automatic phone turns on) ...befor you can flash stock rom and no more problems!
Sent from my GT-I9100 using XDA Premium App

i highly doubt they will send the verizon police to repossess the replacement for when the find the unlocked bootloader.

you can send it in rooted
I had Verizon replace my last phone with Asurion insurance because of a blown speaker. The phone was running Cyanogen. There was no problem.
To be clear:
1. The phone was CLEARLY running Cyanogen because it powered on, showed the CM7 boot animation, and worked perfectly
2. They never called me, hassled me, or anything. Just credited my account.
good luck

Got into Odin mode, but no options to reboot. Just says "Downloading... Do not turn off target !!" The only option displayed is "Start" but I'd have to use the power button to select it (can't do that lol). What can I do from Odin?

Well, pretty sure I just hard-bricked it, so whatever.
Downloaded this: i9250xx_itl41f_fl.zip
and ran it while the phone was connected to the computer in odin mode.
Was kind of distracted by gf and didn't verify that it was for CDMA. I guess its GSM only. Anyways, now the jig won't bring up Odin mode, and I have an imagine of a phone connected to a monitor with a yellow exclaimation triangle between the two.
Guess that's it.

Found a CMDA odin image. gonna try to flash this. didnt realize you needed Odin3 too, lol. Will let you guys know how it worked..

Image worked. Back to stock 4.0.2. I suppose that means it's unrooted. Used the GN Rootkit to relock bootloader. I don't know if stock recovery is installed or not, though. I tried to reboot into recovery using the rootkit, but i just got a red triangle. Any ideas?

[Q] Kindle Won't Turn On

So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?

philip1192 said:
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Click to expand...
Click to collapse
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again

Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

persano said:
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Click to expand...
Click to collapse
I'll try that and see if it'll help.
mindmajick said:
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is that a problem?

Other than voiding the warranty since you opened the device... And removed a battery not meant to be removed? Naaaah
You should NEVER have to pull the battery on ANY android device.
Edit: couple more things
1. As long as you are USING the device it won't charge on USB to PC. Always better to charge off a wall outlet. MUCH faster charging too.
2. NEVER flash a ROM if your battery is low.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.

philip1192 said:
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
Click to expand...
Click to collapse
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
How was it not actually unlocked?
Hopefully someone can...

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

soupmagnet said:
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
Click to expand...
Click to collapse
Well, they're lame. I like HTC better.
mindmajick said:
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'll see if I can make that work. If not, I guess I have an expensive paperweight on my hands...

[Q] Soft Brick / USB Brick / General Weirdness

Phone: VZW Galaxy Nexus, Rooted, TWRP Recovery, Lean Kernel
For the first (and last) time in my life I decided to dirty flash a ROM (4/16 build of Project Elite) to my phone (from an earlier build of PE). My phone apparently hated that. It has created an odd world of problems for my phone that I am hoping someone may be able to see a trend with and offer up some suggestions for escaping this odd world.
Here are my phone's symptoms:
(1) Earpiece on phone stopped working: During phone calls, I can only hear audio when using speakerphone. I was able to remedy this by getting the SoundAbout App from the Play store. This tool allows you to manually change how the audio is routed. My phone thinks a headphone is plugged in and tries to route the audio through the headphone jack. This app allows me to fix that problem.
(2) USB File Transfer Mode stopped working: When connecting my phone to the computer it will charge (sometimes, see #3) but my computer will not recognize it as a device. Consequently, adb (and wireless adb), fastboot and ODIN all will not connect to my phone because the phone is not recognized. I have uninstalled, updated and re-installed just about every driver set I can find for the Galaxy Nexus/ I know it is not a driver issue because my wife's Nexus connects to the CPU just fine.
(3) Phone Charging is Intermittent: I have trouble finding a trend with this one. If I toggle Fast Charge (Off or On), my phone will no longer charge. This is fixed by powering off the phone with the cable plugged in. At that point the white battery icon appears and the phone begins charging. If I power the phone back on, the phone will continue to charge but will not be recognized as a USB device.
Here is what I have tried over the past 2 days:
(1) Both GNEX Toolkits: With no USB connectivity, adb and fastboot are not options. This option becomes unavailable with no usb. Have tried both.
(2) ODIN: Phone is not recognized by ODIN tool.
(3) Cleaning USB/Headphone Ports: This produced some interesting black stuff, but no results.
(4) Clean Flash of PE 4/16 Build: Wipe data/cache/dalvik and re-flash. Same problem.
(5) Clean Flash of Stock Rooted Build: Wipe data/cache/dalvik and flash. Same problem.
(6) Mobile ODIN: Cannot locate the tar balls for a stock 4.2.2 factory flash. Have found the necessary files for 4.0.2, but these will not flash in Mobile ODIN. I have read that you have to be on the same android version as the ODIN tar files you are trying to flash. I think this is my best option at this point, but I cannot for the life of me figure out how to get Mobile ODIN to work.
As far as I can tell this is a software problem that is baked somewhere deep in the phone. Since the USB and headphone problem started at the same time, I do not believe it to be hardware. My theory is that somehow fast-charge is locked on (?) and my phone is locked to routing the audio to the headset. If I can find a way to completely wipe everything off and start fresh, I believe my problem will be solved.
Does anybody have any ideas what may be going on here and how I may be able to get this phone back to Stock?
tldr; no usb, no headset audio after dirty flash, how do i get back to stock??

In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus

bk201doesntexist said:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.

7ontheline said:
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
Click to expand...
Click to collapse
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?

bk201doesntexist said:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
Click to expand...
Click to collapse
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.

7ontheline said:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
Click to expand...
Click to collapse
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.
You've done this? Sure the USB port doesn't have a bent pin or something?
Sent from my Nexus

My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app

tdf666 said:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.
I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.

I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
Sent from my Galaxy Nexus using xda app-developers app

No Command in Recovery/PC Wont Recognize..Solved!!!!!!!!!!!

My verizon galaxy nexus is saying no command once i boot to recovery....Dont know whats going on...It charges when the phone is off, but once its powered on it doesnt charge nor does my pc recognize it...

Anyone seen this before?

1) do not bump your own thread 10 MINUTES after your post.
2) did you change any system files? what did you do before this happened?

Zepius said:
1) do not bump your own thread 10 MINUTES after your post.
2) did you change any system files? what did you do before this happened?
Click to expand...
Click to collapse
Didnt do anything to it...I just got it and its on verizon...When the phone is off it will charge once its on it doesnt charge and my pc cant see it....I go to recovery mode it says no command but i finally got it to recovery menu after holding the volume up +power for about 30seconds about to do a factory reset and see how it goes
Apologize for the bump so fast
Performed the factory reset in recovery mode and my PC is still not seeing the phone..I plug my other nexus in and my PC sees it immediately...

antawnm26 said:
Performed the factory reset in recovery mode and my PC is still not seeing the phone..I plug my other nexus in and my PC sees it immediately...
Click to expand...
Click to collapse
thats drivers. nothing more.

Zepius said:
thats drivers. nothing more.
Click to expand...
Click to collapse
Even though its the same phone?
Ok installed the drivers in the back to root guide.. I plugged my other verizon samsung galaxy nexus into my computer and it saw it, I plugged my new one in and it does not recognize it...Im confused as to what could be going on..The reason I got another one was because i got it for a pretty good deal since my first one has a cracked screen...
What could be going on with my new one that my pc wont see it? How could I get it rooted and flash a rom to see if this could fix it?

antawnm26 said:
Even though its the same phone?
Ok installed the drivers in the back to root guide.. I plugged my other verizon samsung galaxy nexus into my computer and it saw it, I plugged my new one in and it does not recognize it...Im confused as to what could be going on..The reason I got another one was because i got it for a pretty good deal since my first one has a cracked screen...
What could be going on with my new one that my pc wont see it? How could I get it rooted and flash a rom to see if this could fix it?
Click to expand...
Click to collapse
And another cable or computer? Does that make a diffrence?
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
And another cable or computer? Does that make a diffrence?
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
No go with different cable and computer...It shows that its charging to the pc,but it will not recognize it....when i put my sim card in it links up to verizon and shows 4g. Im wondering if whoever had it before may have flashed something and messed something up....Im wondering is there a way to upload a rom (verizon) and twrp to dropbox and download it and root it that way and see if that fix the issue...Is there anything in the stock rom that could be missing that could cause this issue?
been looking for a .tar file of cwm to upload to drop box and download it and flash it with mobile odin since my pc cant recognize my Nexus and then download su from drop box reboot to recovery and then flash a verizon rom and see if that fix the issue...Is that sounding like a good plan or not?

SOLVED!!!!!! I figured I would try and swap my usb parts out and that was the culprit....So, it would charge but not allow the pc to see it.....
Thanks for the advice guys

[Q] Galaxy Nexus: Android 4.3 Update phone not charging

Hi There
I recently updated to Android 4.3 and ever since then my phone isn't charging anymore. When I connect it to my PC it is connected as an "unknown device". At first it was charging when turned off, but know even that doesn't work.
I had clockworkmod installed, but since the update I only get the "No command." message and the standard Android system recovery.
I'd like to get my phone connected to my PC again somehow, so I can downgrade to 4.2.2 again.
Anyone has the same problem / suggestions on how to solve this?
Thanks!
Phone: Galaxy Nexus I9250 (maguro)
Lock state: unlocked
Bootloader: PRIMEMD04
Carrier: Swisscom

Hi, I've got the exact same problem on my Galaxy Nexus, and I can't find any solution yet, I've a couple of things that did not work at all.
Now I've got the charging anim on the screen when my phone is switched off but even then, it seems I can't get it charged more then 8%
Really don't know what to do here

External battery charger... Charge your battery and flash back to 4.2 until you can sort issue out?

DrRatek said:
Hi, I've got the exact same problem on my Galaxy Nexus, and I can't find any solution yet, I've a couple of things that did not work at all.
Now I've got the charging anim on the screen when my phone is switched off but even then, it seems I can't get it charged more then 8%
Really don't know what to do here
Click to expand...
Click to collapse
Same here after updating it worked normally for a week but now no charging . I have to charge it by turning of the phn with a high power charger
I am a noob don't know how to downgrade

Huehnerdieb said:
Hi There
I recently updated to Android 4.3 and ever since then my phone isn't charging anymore. When I connect it to my PC it is connected as an "unknown device". At first it was charging when turned off, but know even that doesn't work.
I had clockworkmod installed, but since the update I only get the "No command." message and the standard Android system recovery.
I'd like to get my phone connected to my PC again somehow, so I can downgrade to 4.2.2 again.
Anyone has the same problem / suggestions on how to solve this?
Thanks!
Phone: Galaxy Nexus I9250 (maguro)
Lock state: unlocked
Bootloader: PRIMEMD04
Carrier: Swisscom
Click to expand...
Click to collapse
Can you check if you still have root? If you still have root, you can flash another recovery using Mobile Odin.

rajuki said:
Can you check if you still have root? If you still have root, you can flash another recovery using Mobile Odin.
Click to expand...
Click to collapse
Hi rajuki
Well I thought so. But after I installted Mobile Odin it tells me I don't...
Thanks for the hint anyways.

NYYFan325 said:
External battery charger... Charge your battery and flash back to 4.2 until you can sort issue out?
Click to expand...
Click to collapse
Yeah I want to flash back to 4.2 or CM. The problem is I can't since my PC doesn't recognize my device. I tried different drivers but it just pops up as "unknown device" in the device manager.

Can anyone tell me how to downgrade i am a noob currently on stock 4.3
Sent from my Galaxy Nexus using xda app-developers app

After hours of flashing rooting unrooting it finally works but i really don't know how.
At first my phone wasnt anymore recognized by my PC, after playing around with checking unchecking debuging mode, and uninstalling drivers and installing drivers from the NEXUS ROOT TOOLKIT, it came back on my PC screen.
-first i downgraded to 4.2.2 (using nexus root tollkit), it did not change anything
-then got back on 4.3 with OTA, still same problem
-then tried unlocking rooting and flashing cyanmogen mod, still same problem
-Finally i flashed stock 4.3, unrooted and locked, and now everything works perfectly...I really dont know how but now its all good, also it looked like Avast and Nova launcher were not doing too well with 4.3 so i uninstalled them and really saw a difference afterwards
I hope this may help someone