Related
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/
My nexus is stuck on the google boot loop since this morning, i am on stock firmware no root or no nothing, can someone suggest me how can i fix this issue. i have mac and does not have access to any windows machine so i will be greatful if the suggestions will be accordingly for mac
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Hopefully factory reset using recovery works as krunal1981 suggested. If it doesn't then you will have to use Odin or Heimdall for Mac and preform a full restore. If you have a warranty and the first doesn't work, take it back to Verizon and tell them that your phone isn't booting anymore and they'll replace it.
krunal1981 said:
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Click to expand...
Click to collapse
Thanks Much this solved all my problems with the phone as of now, wonder what caused the phone to go in that ever ending loop
Question: Did wiping from stock recovery also erase your internal storage (/sdcard) or not?
Anyway - I have had this problem too, and all I can say is: A full wipe fixes it but only temporarily. It will happen again most likely. I believe it is a hardware problem with the internal memory. Next time it happens you should seek a warranty replacement.
when i do this all i get is the droid robot with an exclamation mark. my phone seems to go crazy at moments just keeps power cycling and gets soooooo hot and verizon just keeps trying to give my refurbed ones doing the same thing
galaxy nexus stock
Yes.. resetting the phone from the stock recovery erases everything
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
when you get the android with an exclamation mark , press all the hardware buttons on your phone i.e volume up , volume down and the power button. this will take you to the stock recovery .
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
sphish said:
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
Click to expand...
Click to collapse
It's a hardware defect. The only permanent fix is a warranty replacement.
Fortunately the units with this defect seem to manifest it within the first few months so that the owner can figure it out and get a swap.
So, a bit more information here. I'll get to the result at the end.
I did the factory reset from recovery, that would allow the phone to boot and stay on for a few minutes, I found, after which it would go into boot loops again.
Once the phone was on, I had USB debugging on, and was looking at the phone files when I noticed that folders that were originally on the phone from before the wipe @ recovery would begin to appear, one by one. Complete with all the original files that I had before the factory reset. Once I noticed this, I performed a full wipe from the phone OS (Settings -> Backup & Reset -> Factory Data Reset).
This actually wiped everything, 100%. Made sure not to restore all apps from my google account, either, and guess what, more than 24 hours of not a single reboot. Heavy use for those 24 hours, as well. Been stressing the phone HARD.
Near as I can tell, there was some file or app that for whatever reason probably went rogue and was causing the phone to encounter something which I can only relate as being similar to a core dump/BSOD if you were on linux/windows. I don't study phone OS culture enough (I'm an auto service technician by trade) and haven't compiled a Linux box in over 10 years, so I'm a bit rusty on it, but it honestly doesn't surprise me that this is a definite possibility given all the different hardware configurations and all the different apps that are out there that are expected to work on everything.
So, there you have it, my experience, my fix, and what worked for me (so far). I'll keep everyone posted if I notice any random reboots or any future reboot loops.
I believe it's a hardware level defect with the eMMC. It keeps working fine again until it attempts to write some important file to that exact sector of the internal memory. Then it corrupts again and back to the boot loop.
When I had a defective unit, the longest it'd last before looping again was 20 days. Sometimes as few as five hours. If it spontaneously starts looping again - it's a hardware problem and there's no fix. You need a replacement.
Sent from my Galaxy Nexus using Tapatalk 2
So, here's an update on the situation with my phone.
The update, is that there is no situation. The phone is operating perfectly fine. Had it's OTA update to Jelly Bean a couple/few weeks back now, and is still running smoothly. Moderate to heavy data/wifi usage (past 10 days has seen 700mb wifi traffic, 1.2gb 3G/HSPA traffic) and phone hasn't been rebooted in over 300 hours.
I'll give periodic updates every month or so.
My girlfriend was using her tablet the other day to do a card swipe transaction at work. Suddenly Mid-transaction the tablet crashed and wouldn't turn on. I took it home and plugged it in. I finally got it to turn on into stock recovery mode however it had the Android icon laying down with his front panel open and a red exclamation point with "No Command" underneath. I proceeded to do a factory reset which succeeded however right before it reboot the "No Command" underneath the Android icon switched to "Error". The system rebooted, and initialized the first on procedures (connect to wifi, sign in to google, sign in to samsung, etc..) however it wont stay on for more than about 15 minutes without shutting off completely, or restarting itself and going into boot-loop. It wasn't holding a charge either so i replaced the battery but the all the symptoms remain except for not holding a charge. One other thing that it does... sometimes a triangle shaped part of the screen will blink black, or the screen will flicker back and forth from the home screen to the settings screen if i go into settings. Occasionally, buttons like "Submit" and "Cancel" (On the wifi password entry) will glitch out.
I was thinking of rooting it, installing custom recovery and a custom rom to see if it would fix it but thought i would ask what you all thought first.
62 views and no replies? Nobody else has experienced the No Command error? I replaced the battery.... the tablet was fine for a couple of days and now it just shut itself off again...
I never had any of these problems. If you're near a Best Buy try going in and talking to their Samsung rep. Our local ones here is SLC have a rep in every store that works specifically with Samsung. Good luck. Thats frusterating.
Epic Nightmare said:
My girlfriend was using her tablet the other day to do a card swipe transaction at work. Suddenly Mid-transaction the tablet crashed and wouldn't turn on. I took it home and plugged it in. I finally got it to turn on into stock recovery mode however it had the Android icon laying down with his front panel open and a red exclamation point with "No Command" underneath. I proceeded to do a factory reset which succeeded however right before it reboot the "No Command" underneath the Android icon switched to "Error". The system rebooted, and initialized the first on procedures (connect to wifi, sign in to google, sign in to samsung, etc..) however it wont stay on for more than about 15 minutes without shutting off completely, or restarting itself and going into boot-loop. It wasn't holding a charge either so i replaced the battery but the all the symptoms remain except for not holding a charge. One other thing that it does... sometimes a triangle shaped part of the screen will blink black, or the screen will flicker back and forth from the home screen to the settings screen if i go into settings. Occasionally, buttons like "Submit" and "Cancel" (On the wifi password entry) will glitch out.
I was thinking of rooting it, installing custom recovery and a custom rom to see if it would fix it but thought i would ask what you all thought first.
Click to expand...
Click to collapse
Android will corrupt itself if improperly shut down. Especially with battery drain, that is why there are warnings not to let the tablet run bellow a certain percentage.
Download Odin 3.07 if your android is below 4.4.2, if not Download 3.09
I prefer UK firmwares as they are more robust than US.
To go into firmware upload, you can hold the volume down while powering up and volume up once more to be in upload mode. Then connect to your pc. If you do not have drivers installed Odin will not work. Either install Kies and allow drivers to install or download them from Samsungs site.
Once you perform the update you should have a normally running device.
If you never updated to 4.4.2... stay away from it too many issues over what it is. You can root 4.2.2 and tweak its performance easier than dealing with 4.4.2's reboot and multitasking lag issues. Some say they are fixed with a factory reset after updating, but they still remain, just not as problematic.
As of right now the tablet is bricked. The screen wont turn on, it wont even respond to being charged. I took the back off of it to make sure all of the hardware was connected and replaced the battery. Now its a brick
Sent from my SM-P900 using XDA Free mobile app
gooberdude said:
Android will corrupt itself if improperly shut down. Especially with battery drain, that is why there are warnings not to let the tablet run bellow a certain percentage.
Download Odin 3.07 if your android is below 4.4.2, if not Download 3.09
I prefer UK firmwares as they are more robust than US.
To go into firmware upload, you can hold the volume down while powering up and volume up once more to be in upload mode. Then connect to your pc. If you do not have drivers installed Odin will not work. Either install Kies and allow drivers to install or download them from Samsungs site.
Once you perform the update you should have a normally running device.
If you never updated to 4.4.2... stay away from it too many issues over what it is. You can root 4.2.2 and tweak its performance easier than dealing with 4.4.2's reboot and multitasking lag issues. Some say they are fixed with a factory reset after updating, but they still remain, just not as problematic.
Click to expand...
Click to collapse
In case I do get download mode working where would i get these UK official roms from? Are they for the wi-fi version?
1st thing... Search for battery disconnect note 8.0. A few have done a reset of the battery and power on issues. It is a lot easier than an Apple tablet.
Below is the 4.2.2 UK version for the WiFi only GT-N5110.
http://www.samsungis.com/download/BTU-N5110XXCMK1
If you are able to flash... I recommend safe root and install exposed framework and wanam exposed to disable DVFS and add some custom features.
If you have 4.4.2 already, you wil need to flash 4.4.2.
http://www.samsungis.com/download/BTU-N5110XXDNE1
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem
So I feel like this is different from a typical bootloop (certainly different from ones I've had in the past). Any ideas short of factory reset would be very much appreciated. I just need it to load once more to do a Titanium Backup (and I guess I should install TWRP and do a nandroid backup)!
I've been using my Tab Pro for years now, rooted, works perfectly, and I always leave it on. I thought yesterday, perhaps this is a bad idea, I should turn it off every once in a while. But I wanted to play a game before I did. I click the game icon and then everything froze and it restarted itself.
It gets stuck at the SAMSUNG logo page. Sounds like a typical bootloop. After 20 minutes of waiting, nothing changes, so I hold down the power button and it restarts and actually loads to my home screen! Great! I swipe the screen lock, click on my game -- it restarts, rinse, repeat. Each time it restarts itself it stops at the SAMSUNG page, forcing a second manual reboot that fully loads, but doesn't go 10 seconds before restarting. I try to load different things each time and finally give up.
So I look some stuff up online. There's a suggestion to go into recovery (I could've sworn I had custom, but apparently not?) and "Wipe Cache/Partition." I look up that this is safe and do it (Sidenote: Power+Home+Vol Up only works around every 5th try or so. It glitches out every other time, there's a quick flash and a horizontal line and it restarts again). Now I restart and it worked! It loads and no reboot!
But now, a third of my apps/games have the android guy as an icon and even more of the real icons are all grayed out. I figure one more restart and it would come back. Now I'm back into my weird bootloop. I try wiping cache/partition again and again and it no longer works as a solution...
TL;DR - Tablet keeps restarting to SAMSUNG logo, requires 2nd manual restart. Home screen loads, but then restarts 10 seconds later. Clearing cache/partition made things worse. HALP!
EDIT: My current build is KOT49H.T520XXUANAE. I can't even find the stock ROM for this! Does it exist?
EDIT 2: After letting it charge for an hour (it was already 93%) I went back to it and it had loaded! But the home screen was blank save for the Google search and the Apps icon (which found no apps....). I was able to get into settings and attempted to click Application Manager and then it froze again.
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
hamstrman said:
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
Click to expand...
Click to collapse
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
starbright_ said:
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
Click to expand...
Click to collapse
I appreciate the response, but as I said, I'm looking for anything shy of factory reset. If I lose all of my apps and data and configuration, I might as well throw out the tablet and buy a new one.
Still trying to figure out the pattern. I got another attempt of it not restarting for 10 full minutes. The keyboard failing is annoying because it doesn't stop, but I can live with it if it means being able to backup my tablet with Titanium Backup. I only got 6 apps backed up before it froze, but I'll get through all of them eventually (I hope). It's just going to be incredibly frustrating.