Database Info

[Q] [Help] Stock, unrooted, untouched 1920 Nexus S stuck in boot animation

Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!

You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App

Sent from my Nexus S using XDA App

Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?

OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App

Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App

brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila

The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.

You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium

So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App

Again the exclamation mark IS the stock recovery.

Urgent help - N8010 stuck in reboot loop

Hi GUys,
flashed my note using the CWM method successfully (well..) and after it randomly reboots at different stages, sometime at samsung logo, somtimes ater its fully loaded and running, sometimes on the galaxy note load up screen.
\ive tried wiping, reset, caches, re-rooting
also tried downloading stock and installing with odin, it removes root and same thing.
tried kies, but it says no updates available, on current firmware
it never reboots when in download mode, but dos sometimes when in recovery modes if that helps?
someone please help!!

Maybe its a hardware issue... if you've tweaked around with the software and symptoms don't seem to change, then you might wanna think about sending it in for repair or replacement.
Sent from my GT-N8013 using xda app-developers app

yeh i was thinking that, just hoping it wouldnt be the case
just flashing a custom rom now to see if maybe the stock i installed was corrupt
anywhere i can get previous stock roms from?

ok finally flashed stock 4.0.4 with odin and it seems stable.
Although one problem now -
There is no lockscreen and no boot options while pressing and holding the power button with addition to this while holding power button it directly switches off it slef without any prompt.
i found a thread for a 7000 with a fix but im not rooted and a bit scared to do it again so the command doesnt work in teminal
http://forum.xda-developers.com/showthread.php?t=1853165
Any help please guys?

Seems like your device is in factory mode.
That often happens when your EFS partition screwd up.
Check your Imei number.
Sent from my GT-N8000 using XDA Premium HD app

returned it for another one - turned out the power btto was faulty, hence the rebooting.

brieuwers said:
Seems like your device is in factory mode.
That often happens when your EFS partition screwd up.
Check your Imei number.
Sent from my GT-N8000 using XDA Premium HD app
Click to expand...
Click to collapse
I was going to start a New Topic but a search brought me to this post.....
Okay, I have an N8010 Wifi only model.
Where exactly does it list the IMEI number of the N8010?
Next, as the Wifi only N8010 does not have a Phone App how do you insert the *# Codes as in *#272 IMEI NUMBER*

Any post talking about an IMEI for the wifi only version is wrong... IMEI's are only for devices that have a phone modem, essentially 3G model only...

ultramag69 said:
Any post talking about an IMEI for the wifi only version is wrong... IMEI's are only for devices that have a phone modem, essentially 3G model only...
Click to expand...
Click to collapse
And with that it's also impossible to carry out any Samsung *# Codes

GT-N8010 stuck in bootloop, can't flash
Hey guys,
Today I was playing world at arms, and all of a sudden my tablet shut down and restarted.
Since then it is in a reboot loop, and doesn't respond to anything.
I run the latest official 4.4.2, which I rooted using the CF-Root method. It worked just fine for over a week, until this morning.
I tried to reflash the stock firware (from sammobile) without any luck. I tried to reflash the CF-Root without any luck.
It fails every time. I tried several versions of Odin (1.85, 3.07, and 3.09), but all of them failed.
I tried to reboot in recovery, but it doesn't work, the android robot appears, but then it restarts in the bootloop.
It goes up to the Samsung logo, before crasking again.
Sometimes I hear the music of World at arms playing before it crashes.
It seems real stuck, and I cannot think of anything else to do...
At the moment, I leave it in the loop until the battery dies off... And then I'll try charging it a bit and restart...
Any other suggestions?
Thanks,
J

Help wanted
Can anyone help me in this regard, my tablet is in Reboot loop.
---------- Post added at 01:41 PM ---------- Previous post was at 01:35 PM ----------
Please guide me if there is a solution to the problem, tablet's screen only shows the samsung logo and does not move ahead please suggest a solution if anyone can

hasanafzaal said:
Can anyone help me in this regard, my tablet is in Reboot loop.
---------- Post added at 01:41 PM ---------- Previous post was at 01:35 PM ----------
Please guide me if there is a solution to the problem, tablet's screen only shows the samsung logo and does not move ahead please suggest a solution if anyone can
Click to expand...
Click to collapse
Same with my Note .... stuck in boot loop... tried all but no luck
anyone to help?

Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update

Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!

I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app

wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse

beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:

error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse

beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??

mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.

beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!

This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse

I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...

Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app

I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse

So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..

Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app

I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.

Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse

Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?

update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.

There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.

Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.

Black Screen after I modify bootanimation

Hi,
I am using Nexus 5(rooted). I was trying to customize a boot animate myself. However, it shows nothing after I modified it.
For now, it will show only black screen after the White Google logo with unlock.
I don't know how to fix phone now, screen show nothing. System should be fine. the screen lock is working because I hear the screen lock sound, and I can unlock it. I have the original bootanimation.zip. I can get in the MTP drive when I connect it to my computer . However, I remember the USB debugging mode is off. Is there any way to fix it through computer? Bootloader is working on phone
Thanks

If you have custom recovery, boot into it and adb push
Bootanimation black is common if image is incorrect bit depth. Never heard of it making the rom black too. How long have you left it on for to check?
Sent from my Nexus 5 using Tapatalk

rootSU said:
If you have custom recovery, boot into it and adb push
Bootanimation black is common if image is incorrect bit depth. Never heard of it making the rom black too. How long have you left it on for to check?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
10 mins already =(
I did the system back up after I root the nexus 5. is this the custom recovery?
Would you mind tell me more how to do it? Thanks a lot. I just start to use android =(.
I can get in recovery mode, but there is nothing in "restore" section.

I tried to use "wipe" --> "advanced wipe" -->"system" to fix it on fastboot boarder. And, now it stucks at White Google logo. Not even get in to system now.. Help :crying:

chan1600 said:
I tried to use "wipe" --> "advanced wipe" -->"system" to fix it on fastboot boarder. And, now it stucks at White Google logo. Not even get in to system now.. Help :crying:
Click to expand...
Click to collapse
You have no OS now you wiped system, either push or sideload a custom rom or flash the stock image.

Ok. Fixed. Thank you for helping all =D
I downloaded the rom here and put it in USB
http://forum.xda-developers.com/showthread.php?t=2557523
and then mount it --> install--> install the rom =D done

chan1600 said:
Ok. Fixed.
I downloaded the rom here and put it in USB
http://forum.xda-developers.com/showthread.php?t=2557523
and then mount it --> install--> install the rom =D done
Click to expand...
Click to collapse
Oke, glad you fixed it :good:

Bit depth is important when making your own boot images. I don't know if it's changed since donut 1.6 but back then you could not compress the zip either or you would end up with a solid black animation.
If you use 7zip you set compression level to store
Sent from my Nexus 5 using xda app-developers app

how to recover from boot animation black i have samsung j7 ?
danarama said:
If you have custom recovery, boot into it and adb push
Bootanimation black is common if image is incorrect bit depth. Never heard of it making the rom black too. How long have you left it on for to check?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
whats the solution for boot animation black in samsumg ?

DPI changed and now HTC sensation xl wont show reselution

Hi, I followed one of the thread somewhere on this forum before and now my phone comes on to HTC white screen then doesnt show anything else but when you connected usb on pc it shows as Android connected but i cannot open it as its on auto charger mode only. Any help on getting the DPI resolution changing back somehow is greatly appreciated and yes my phone is rooted.

I suspect you modified your build.prop file. I hope you have already made a backup with twrp prior to this modification, correct? Restore system with system backup.
Sent from my C525c using Tapatalk