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.

One X in Bootloop

After canceling a flash of Sick Sense, my One x wont boot now. I would boot into bootloader and hit recovery and twrp splashscreen shows for a split second, then reboots to htc splashscreen, staying like that forever. What should I do? Fastboot install another recovery?

ethantarheels123 said:
After canceling a flash of Sick Sense, my One x wont boot now. I would boot into bootloader and hit recovery and twrp splashscreen shows for a split second, then reboots to htc splashscreen, staying like that forever. What should I do? Fastboot install another recovery?
Click to expand...
Click to collapse
Looks like you are unlocked ... so try to boot into "bootloader" and reflash recovery ...
If nothing helps ... relock bootloader and flash RUU ...

Boot into the bootloader
Flash TWRP again (must be TWRP as CWM does not have USB mount yet)
Boot into TWRP
Mount USB
Transfer your ROM of choice onto your phone
Unmount USB
Do a factory reset from TWRP
Flash the .zip
Reboot and hope for the best
If that doesn't work then you could just run the RUU from fastboot.

Yea I was out and about with no internet just my phone me and my laptop lol. What I ended up having to do was relock and ruu back to 1.85. Thanks for the help guys. Now I hope I can still reunlock lol
Sent from my HTC One X using XDA

What happened earlier was that, even though I was able to get and boot into cwm, the sd card got unmounted somehow so I couldn't flash or restore anything.
Sent from my HTC One X using XDA

AT&T HOX Stuck in Boot Loop after trying to flash a rom using Flash Image GUI
First of all thank you to everyone who is willing to help me out. I apologize if I missed the answer I'm looking for. Here is what's going on:
I successfully rooted my HTC One X (At&T) using TWRP a couple days ago. I created two backups in TWRP, one before rooting and one after. I then tried to install viperx 3.3.1 using Flash Image GUI from the playtstore and after the install finished I am not stuck in a boot loop on the screen that says "HTC quietly brilliant" and has the disclaimer written in red. I turned my phone off and rebooted holding the power button and volume down button and tried to do a restore of one my backups in TWRP. However I am still stuck in a boot loop. I tried restoring to the other backup also and still in a boot loop. I tried wiping the cache, Dalvik Cache, and System and then rebooting but same thing. I would appreciate any help at all. Thank you an advance for your time.

You have to flash the boot img of your backups...but just flash viper and flash the boot img

Whoa whoa whoa whoa... we don't have viper 3.3... he just released 3.2 today... sooooo it looks like you tried to flash the international version of viper
Sent from my evita using Tapatalk 2

[Q] HTC One S stuck in 'Entering recovery'

I unlocked the bootloader of My HTC One S with instructions from htcdev.com later I flashed it with latest touch CWM img file. The device is booting normally but when i am trying to go into recovery mode, it stuck in there showing 'Entering Recovery'. I cleared cache several times, tried to flash with twrp but same situation. If I just erase cache, it is still showing the same screen, tried stock recovery image also, still no luck. Please help :crying:

Mysticalsam said:
I unlocked the bootloader of My HTC One S with instructions from htcdev.com later I flashed it with latest touch CWM img file. The device is booting normally but when i am trying to go into recovery mode, it stuck in there showing 'Entering Recovery'. I cleared cache several times, tried to flash with twrp but same situation. If I just erase cache, it is still showing the same screen, tried stock recovery image also, still no luck. Please help :crying:
Click to expand...
Click to collapse
Have you tried to flash TWRP instead? How exactly are you trying to go to recovery? From the ROM power menu or by shutting phone down and starting up having vol-down pressed? Have you tried both methods?

Rapier said:
Have you tried to flash TWRP instead? How exactly are you trying to go to recovery? From the ROM power menu or by shutting phone down and starting up having vol-down pressed? Have you tried both methods?
Click to expand...
Click to collapse
By fastboot.

Go again in fastboot and flash TWRP recovery. See if you then can boot to recovery
Sent from nowhere over the air..

Rapier said:
Go again in fastboot and flash TWRP recovery. See if you then can boot to recovery
Sent from nowhere over the air..
Click to expand...
Click to collapse
I tried everything.
TERP, STOCK, CWM. erasing cache many times.... nothing works

Issue Fixed 'Entering Recovery'
Its been fixed. The problem was with the model. I was using S4 variants whereas my phone is S3. Thanks for your replies.

How did you do?
Mysticalsam said:
Its been fixed. The problem was with the model. I was using S4 variants whereas my phone is S3. Thanks for your replies.
Click to expand...
Click to collapse
I also have de S3 HTC One S. I can't pass through the step "Entering recovery..."
Thanks!

[Q] Phone won't boot to recovery

Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!

DaiMinzz said:
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
Click to expand...
Click to collapse
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!

stevekind said:
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
Click to expand...
Click to collapse
Still the same problem didn't work
Im sure everthing on the pc went ok, but my Oneplus has recovery bug

[Completed] [Q] HTC One M7 not entering recovery

HTC One M7 GSM Recovery Update Problems]​
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:

JacobHaze24 said:
HTC One M7 GSM Recovery Update Problems]​
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:
Click to expand...
Click to collapse
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.

enigmaamit said:
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.
Click to expand...
Click to collapse
yes I have already unlocked the bootloader through the htcdev site and adb never fails to write the recoveries its just only the TWRP and CWM recoveries i mentioned seem to work on my device i cant update to a newer one because it gets stuck on the "entering recovery" screen when i try to boot into recovery, im not quite sure why its happening
Okay I just tried what you said and the result is the same, I cant be the only one with this problem

JacobHaze24 said:
I cant be the only one with this problem
Click to expand...
Click to collapse
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!

enigmaamit said:
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!
Click to expand...
Click to collapse
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:

JacobHaze24 said:
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:
Click to expand...
Click to collapse
Glad you made it, and learnt some valuable skills along the way.
Thread closed.