Related
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.
Hello all,
Im trying to flash a new recovery image, but none seem to be working. Im not sure if you're familiar with the file names, but Ive tried "recovery-clockwork-3.0.2.4-crespo.zip" and "3101-orange.img"(j_rodd's modification of koush's). I tried to go to the source but it seems koush's site is down right now.
The phone is unlocked, however when I select recovery from the bootloader the phone shows a package unboxing image and then an android next to an exclamation in a triangle. Regular boot is fine.
Thanks in advance.
you're doing this in bootloader, right?
You have to be in bootloader, open cmd on computer and flash through there.
You can find 3.1.0.1 here http://forum.xda-developers.com/showthread.php?t=988686
outamoney said:
Hello all,
Im trying to flash a new recovery image, but none seem to be working. Im not sure if you're familiar with the file names, but Ive tried "recovery-clockwork-3.0.2.4-crespo.zip" and "3101-orange.img"(j_rodd's modification of koush's). I tried to go to the source but it seems koush's site is down right now.
The phone is unlocked, however when I select recovery from the bootloader the phone shows a package unboxing image and then an android next to an exclamation in a triangle. Regular boot is fine.
Thanks in advance.
Click to expand...
Click to collapse
Are you on stock rom? if yes, then no matter how many times you flash the custom recovery(cwm or jrodd), once you reboot your phone and enter recovery, you'll always end up with stock recovery.( the image you are getting android next to triangle is that of the stock recovery)
what you should do is enter bootloader, fastboot flash ur recovery, and from there (without reboot) enter recovery directly. i would recommend you flash a custom rom.
I tried all the methods of rooting, but none of them is working. Can anyone help.
I had unlocked my bootloader successfully and when trying to push the custom recovery img it says booting but it hangs on a Google screen with a lock unlocked and fastmode status - okay written.
I tried the Toolkit on XDA also and the phone doesnt restarts after "booting into Android using an Insecure Boot Image" and same screen appears
I am running Android 4.0.4 and build IMM76D
amolnw said:
I tried all the methods of rooting, but none of them is working. Can anyone help.
I had unlocked my bootloader successfully and when trying to push the custom recovery img it says booting but it hangs on a Google screen with a lock unlocked and fastmode status - okay written.
I tried the Toolkit on XDA also and the phone doesnt restarts after "booting into Android using an Insecure Boot Image" and same screen appears
I am running Android 4.0.4 and build IMM76D
Click to expand...
Click to collapse
are u sure u are posting in the right section ? (title says Nexus S)
1. wrong forum
2. dont use toolkits
instead of the fastboot boot recovery recovery.img command, try fastboot flash recovery recovery.img
Worked
I tried this thread and I was able to go into custom recovery mode.
h*t*tp://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread
Strange it was not going by flashing CWM. Then I installed ROM manager and installed CWM from it. Bingo!!! Everything is cool now
Hi, I have a unlocked HTC One Mini S-ON, not sure if root is still there.
I had it loaded with One-Hybrid-Rom, which used to work fine.
Whenever the phone runs out of battery and I recharge it, after trying to reboot, I always get bootloader.
I have to reboot boatloader 100 times before I finally get the HTC screen and the Rom boots up.
Once the rom is loaded, the phone works fine.
Also, in bootloader, I can NOT enter recovery. When I select "Recovery", it gets back to the same bootloader screen.
So I tried flashing the recovery partition with all kinds of versions of twrp and cwm.
The phone is perfectly connected with adb, fastboot. I use fastboot flash firmware to try and flash the recovery, but it ALWAYS gives me the same error, it is able to send the file to the phone perfectly, but when it starts writing I get "IMAGE UPDATE ERROR".
I have tried literally everything to get the recovery partition working again, but all fails.
As I said, once the phone is booted up, it is working fine...
Is there a fix for this issue? It is just impossible to reboot the phone 100 times before the rom loads.
Thanks a lot guys.
feemanbe said:
Hi, I have a unlocked HTC One Mini S-ON, not sure if root is still there.
I had it loaded with One-Hybrid-Rom, which used to work fine.
Whenever the phone runs out of battery and I recharge it, after trying to reboot, I always get bootloader.
I have to reboot boatloader 100 times before I finally get the HTC screen and the Rom boots up.
Once the rom is loaded, the phone works fine.
Also, in bootloader, I can NOT enter recovery. When I select "Recovery", it gets back to the same bootloader screen.
So I tried flashing the recovery partition with all kinds of versions of twrp and cwm.
The phone is perfectly connected with adb, fastboot. I use fastboot flash firmware to try and flash the recovery, but it ALWAYS gives me the same error, it is able to send the file to the phone perfectly, but when it starts writing I get "IMAGE UPDATE ERROR".
I have tried literally everything to get the recovery partition working again, but all fails.
As I said, once the phone is booted up, it is working fine...
Is there a fix for this issue? It is just impossible to reboot the phone 100 times before the rom loads.
Thanks a lot guys.
Click to expand...
Click to collapse
No one?
No-one willing to help me on an unflashable recovery partition?
Sometimes phone boots into modded OS and runs perfectly, but mostly (99 out of 100 times) it just reboots to bootloader,
unable to enter recovery.
When flashing recovery (I tried all possible recoveries) via fastboot, it connects, but then I get "Failed, image update error"..;
I would really like to use this phone again...
It is S-ON, Unlocked, Hboot-2.21
Thanks.
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
t.holley.os said:
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
Click to expand...
Click to collapse
What do you want to do exactly? Restore stock recovery so that you can take the OTA? If you followed either one of the methods on that thread, you should already be stock, i don't get why you booted TWRP again.
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
t.holley.os said:
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
Click to expand...
Click to collapse
Just flash the stock recovery image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
t.holley.os said:
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
Click to expand...
Click to collapse
Press and hold power for 30 second, the device will try to boot but just keep holding the power. Then press and hold vol down and power. It doesn't boot into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
t.holley.os said:
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
Click to expand...
Click to collapse
FYI the TWRP boot loops are due to MTP bug that was never fully fixed from 2860. It's better than it used to be, but still an issue occasionally, especially if connected to power while you try to get in to TWRP.