Database Info

[Q] Nexus S stuck on google boot logo

Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!

I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??

brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions

Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?

lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.

Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom

any solution?
hi guys.i have the same issue.does anyone have a solution for this?

i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )

Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.

Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....

Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".

As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.

Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-

hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App

Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.

twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.

hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App

How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App

asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).

matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.

[q] help!!! Flashed clockwork recovery

Hi Everybody,
I unlocked a Samsung Nexus S 4g, managed to installed clockwork 3.0.2.4 and now when I reboot, it got stuck on the loading screen where it shows "google" and the and the padlock at the bottom. Please help me fix this.
This is my friend's phone. It seems that it does not recognize the sdcard.
Thank you for your help if you can provide any advice.
DUO

Have you ever taken the phone apart? I normally only see that when the NFC/"SIM" daughter board isn't connected. Also, can you boot into bootloader?
Duoxxx said:
Hi Everybody,
I unlocked a Samsung Nexus S 4g, managed to installed clockwork 3.0.2.4 and now when I reboot, it got stuck on the loading screen where it shows "google" and the and the padlock at the bottom. Please help me fix this.
This is my friend's phone. It seems that it does not recognize the sdcard.
Thank you for your help if you can provide any advice.
DUO
Click to expand...
Click to collapse

How did u root the phone? One click or manually? U prob didn't install recovery right.
Sent from my Nexus S 4G using XDA App

Boot into fastboot.
Download the recovery image again. Make sure it's the correct recovery for your NS model (don't use the NS4G recovery on the NS GSM). Flash it using fastboot.
Then go into recovery, do a full wipe and flash a ROM.

Idk why, but my friend had the same problem. He downloaded an older version of CWM recovery through ROM Manager, rebooted into recovery after and was able to install CWM 4.0.1.4 after. Idk if that will help but it worked for him
Sent from my Nexus S 4G using Tapatalk

Fixed it!!!!
Thank you guys for all your help. I had to unrooted and make sure it loads completely and do the whole process of rooting it again with the newest Clockwork recovery for the ns4g.
It took me a good couple of hours and bring my friend home mad at me, but she will be happy today when I get back her phone.
I wanted to thanks all of you for your help. I'm new to this forum but I appreciate your prompt response. I guess I'm going to stick around more often.
Thanks again

Duoxxx said:
Hi Everybody,
I unlocked a Samsung Nexus S 4g, managed to installed clockwork 3.0.2.4 and now when I reboot, it got stuck on the loading screen where it shows "google" and the and the padlock at the bottom. Please help me fix this.
This is my friend's phone. It seems that it does not recognize the sdcard.
Thank you for your help if you can provide any advice.
DUO
Click to expand...
Click to collapse
When you unlock your Phone, everything is wiped.
After you install recovery, you have to start your Phone by holding the Vol Up and Power button.
Go to recovery - mount your SDCard, copy the ROM that you want to flash and flash it.
You are not stuck on the Google Bootscreen - there is no ROM to boot from.

brainmaster said:
When you unlock your Phone, everything is wiped.
After you install recovery, you have to start your Phone by holding the Vol Up and Power button.
Go to recovery - mount your SDCard, copy the ROM that you want to flash and flash it.
You are not stuck on the Google Bootscreen - there is no ROM to boot from.
Click to expand...
Click to collapse
Thanks alot, it really got me worry but I was able to mount sd card and complete the whole process, now it is running the latest MIUI port for it.

I had a similar issue only that when I would click to flash the zip for clockwork in bootloader it said "file does not exist" I had to run a cmd prompt on my comp to install the clockwork mod.
Sent from my Nexus S 4G using XDA App

[Q] Cannot boot into recovery. Laggy phone as well.

I was just about to try updating from NScollab 1.0.39 to 1.0.40 and for some reason my nexus s refuses to boot into recovery. It doesn't seem to exist anymore. Im not sure if it is related or not but my phone became very laggy after my first failed attempt to boot into recovery. I tried fixing user permissions and rebooting many many times but it doesn't seem to help.

What does it do when u try to boot into recovery?
Sent from my HTC Sensation 4G using XDA App

It doesnt do anything. It just reboots into the bootloader.
Thank you for the quick reply
edit:
i tried flashing recovery again through rom manager and now whenever i try to boot into recovery it just hangs at the google logo with the unlocked padlock.

Hmmm
Do me a quick favor.
go here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and download the 4.0.0.2 recovery image and save it to some directory on ur computer
then follow these steps:
1. Open up command prompt/terminal and plug in phone to computer
2. Type "adb reboot bootloader"
3. It will take you to fastboot mode. Now type "fastboot erase recovery"
4. Then type fastboot "flash recovery ____.img"
( ____ is the name of the recovery img file)
5. Now it will flash and once it says "OKAY" then scroll down using volume down into recovery and see what happens
plz get back to me bout this!

IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?

i so hate rom manager! i cant believe that people still use it

shahravi94 said:
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
Click to expand...
Click to collapse
Since it works, you can wipe and flash ns collab lol
Sent from my HTC Sensation 4G using XDA App

Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.

Yeah prolly a ROM manager issue
Sent from my HTC Sensation 4G using XDA App

shahravi94 said:
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Click to expand...
Click to collapse
the recovery generally doesnt stick if flashing it through rom manager. flash it through fastboot and itll stick.

Hmm thanks for the advice! ill keep that in mind

[Q] RAZR HD XT 925 Boots into recovery by default

So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.

Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium

recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.

roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck

recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.

roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)

coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4

mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.

coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.

mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?

coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.

mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/

mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.

coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear

mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.

HTC Stuck in Recovery

Is there someone out there who can help? In tweeking with my phone, I some how got my HTC One S to only boot up in TeamWin Recovery Only. Dont have a clue where to go from here. Your help would be much appreciated, I wish there was a way to compensate you for your time/knowledge.

a10ciod said:
Is there someone out there who can help? In tweeking with my phone, I some how got my HTC One S to only boot up in TeamWin Recovery Only. Dont have a clue where to go from here. Your help would be much appreciated, I wish there was a way to compensate you for your time/knowledge.
Click to expand...
Click to collapse
Hook your phone to your computer via USB. Mount the USB drive in TWRP. Now you should be able to put a ROM into your phone then install it.
and keep reading because your problem is pretty vague.

Thank you for your reply. This all came as a result of trying to get the phone back to Factory as much as I could. Now every time I turn the phone on it just boots up in recovery. Ive never flashed a new Rom ever.
Sent from my SM-N900T using xda app-developers app

This happened to me once when I accidently flashed the recovery.img into my boot partition!
I meant to do "fastboot flash recovery recovery.img" but stupidly did "fastboot flash boot recovery.img".
This was using the AIO One S toolkit and I just accidently hit the wrong button. Everytime it'd boot it'd just go straight into a recovery. Try to reflash a proper kernel for your phone.
I'm assuming you didn't backup your partition.
If you're on a JB Sense4+ rom, go ahead and use the Bulletproof kernel and see if that works.