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.
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
I have a big problem. My milestone xt720 has been stuck to m logo only. I tried different sbf's using rsdlite, I can only go to bootloader mode 80.89 but still the same. Before this happend I am using xt720mod.sbf with shenqi rom and I load movies and watch suddenly my phone rebooted and always stuck at shenqi bootanimation. I even try going to openrecovery but it stops at the mobile logo with indicator at the boron and I tried also booting to stock recovery and wipe and restore everything but it stills stop at boot animation. So I decided to reflash the sbf. Now I came up stuck at m logo.
Sent from my Nexus One using xda premium
What sbf did you flash
Sent from my XT720 using xda premium
Often when switching between sbfs that change the phones partitioning, the first boot doesn't work and I have to do a factory reset in stock recovery.
However, if have xt720mod.sbf don't forget you can reenter OpenRecovery via apply update.zip in stock recovery! (unless you deleted the files on your sdcard, but in that case just take out the sdcard and fix it on a PC)
I'm not sure which sbf you flashed. If you reflashed xt720mod.sbf remember it always gets stuck at (M) after a fresh flash--the ROM in xt720mod.sbf doesn't work --so every time you flash xt7210mod.sbf you must then go to stock recovery and apply update.zip to get into openrecovery and then install a working ROM.
mchlbenner said:
What sbf did you flash
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
I tried cincinati bell 2.1, korean 39r / 50r, central europe, singapore starhub which is the original. But after rsdlite finished the flashing process and rebooted the phone, it just stops at M or starhub logo. Nothing happens. I can't even go to stock recovery. Only i can switch to boatloader.
Sent from my Nexus One using xda premium
Mioze7Ae said:
Often when switching between sbfs that change the phones partitioning, the first boot doesn't work and I have to do a factory reset in stock recovery.
However, if have xt720mod.sbf don't forget you can reenter OpenRecovery via apply update.zip in stock recovery! (unless you deleted the files on your sdcard, but in that case just take out the sdcard and fix it on a PC)
I'm not sure which sbf you flashed. If you reflashed xt720mod.sbf remember it always gets stuck at (M) after a fresh flash--the ROM in xt720mod.sbf doesn't work --so every time you flash xt7210mod.sbf you must then go to stock recovery and apply update.zip to get into openrecovery and then install a working ROM.
Click to expand...
Click to collapse
I cant switch to stock recovery to run the update.zip which was i was doing before. I have not remove the openrecovery and update.zip on my sd. Its just that the phone stops a the M logo.
Sent from my Nexus One using xda premium
It sounds like you're doing all the right stuff to me.
I wonder if your camera and gallery buttons may be not working? Have you tried flashing the same sbf a few times in a row? That's what I'd try first. That might cause something like a factory reset. Also make sure your battery is fully charged. On the other hand, being able to switch between starhub and motorola logos demonstrates that RSD is actually doing something. I guess I'd maybe suspect weak button contact in either the camera or gallery key and I'd maybe try repeatedly to get into stock recovery by pulling the battery while holding the camera and gallery keys different ways...
I think the phone stops responding when stuck at M logo. This is what my phone experience..
-when the phone is off. When i plug it to charger i got no response from the phone that it is charging even i plugged it for 1hr. Totally no indicator. Btw i use universal charger to charge the battery.
-we know that if we flash the original phone sbf it should boot normally, which is the starhub sbf is my original. In my case after rsdlite flashing it reboots the phone and it just stay on the starhub logo until my battery drains out. The screen should flicker once indicating that the phone is booting and should load the bootanimation just like before. But it just stops at the logo.
I tried what you have said but still it stops in there. I tried flashing sbf's many times with full battery charge.
If only i can go to fastboot mode and try to scan if there are bad blocks on the nand.
Sent from my Nexus One using xda premium
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Wiltuz said:
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Hi there, sucks to hear what happened..
I believe you haven't put in enough research, ASUS has a publicly available unlocker for the 300T, why did you use a 3rd party root app?
Can you still boot Android? If you have root and your recovery partition is broken, there should still be a way to overwrite the recovery partition.
If not, this basically looks like a brick, unless you can hook up a debugger during the boot process somehow.
Someone with in-depth knowledge of this device might be able to help you out further, I'm just theorycrafting here.. Best of luck!
I would try using fastboot to reflash stock firmware, which you can download from the Asus website.
You could also try getting into APX mode and using nvflash to reflash it.
Sent from my Transformer Pad TF300T using xda app-developers app
So, I got my moto g a few days ago, and today I decided to unlock the bootloader.
The process went fine, but when it booted up to the startup screen, everything was forceclosing (systemui, etc)
I force shut it down. After that, it would show the boot animation, going to the rippling motorola logo, and then go to a black screen. I am currently flashing to stock using fastboot, I can use fastboot to flash an alternate recovery, but that seemed to do nothing. Stock recovery does not work.
I really hope there's a simple, idiot proof way to fix this.
Anyone know what it could be?
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
bobcat913 said:
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
I flashed TWRP, twrp works fine, but I need to transfer a ROM to the phone, using TWRP's sideload feature doesn't work, as my phone does not show up as a device, once in adb. In device manager, it shows up as "Android" and has no drivers, when trying to use the adb sideload feature in recovery.
I ended up fixing it after all, installing the easy universal adb/fastboot drivers, and then adb pushing the rom, and gapps