Develop Bugs

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.

This is the hspa version.

svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!

This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..

I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.

svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!

I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.

Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.

I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

Desire not bricked but......

Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks

Are you using a custom rom of any kind, rooted etc. giving details like this helps people answer questions.
My advice is if you are useing a custom rom then backup your apps etc. then redownload the rom and flash it as new then recover your apps.

[Q] Screen Issues Lead To Bricked Device

I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery

[Q]Rogers Galaxy S3 constantly restarting even in recovery/download mode

So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.

Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.

There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.

Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.

Sleep/Wake problems [SOLVED]

So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.

msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel

powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.

So enjoy the fix if you ever run into the above issue.

Im fine with stock, but I miss the fun of trying new roms.