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.

Odd behavior when upgrading to cm10.0.0 on HTC one s

I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?

OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.

Try TWRP...it will be better
Sent whit HTC ONE S

That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app

Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app

boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.

I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app

jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209

[Q] Phone won't boot into ROM or recovery--Possible hardware issue?

I've been having a bit of a hard time with a friend's Skyrocket tonight. I flashed CM9 for her before, and it seems to work well. In the past two to three weeks, though, she tells me that her phone's been randomly turning off. Tonight, I finally decided to install CM10 on the Skyrocket, thinking that this would fix the issue. I installed it through CWM like normal (I've flashed many a ROM, so I couldn't have messed up this process).
With everything installed, I reboot through CWM. The issue is, the phone just goes black. After pulling the battery and trying to boot again, I see the Samsung logo, followed by a black screen. The phone sort of pulsates for a bit at this point, giving me a short vibration here and there, before finally stopping. Attempting to get into recovery doesn't work either. I also, due to me not being used to the download mode feature (I personally have a Galaxy Nexus), accidentally tried to start it by holding the power and volume buttons (rather than holding volume and plugging the phone in, not touching power). The yellow triangle would show up very briefly, and then the phone shuts off.
When getting into download mode the proper way, I was able to get into Odin and flash CWM again. At this point, I should definitely be able to get into Recovery. But alas, I cannot... Same issues as before. At this point, it's revealed to me that, after the random shutoffs that my friend had been experiencing, she would sometimes also have trouble turning the phone back on. Noticing a trend?
I'd like to know what you guys think: Is this a software issue, or is it a hardware issue? For the former, what do you guys recommend so the phone could boot normally again? And for the latter, well... I don't suppose there are any easy hardware fixes I could try?

If you pull the battery and reinsert does the phone start on its own with no button pushes? If so... Stuck power button.
Sent from my SAMSUNG-SGH-I727 using xda premium

stoopendis said:
If you pull the battery and reinsert does the phone start on its own with no button pushes? If so... Stuck power button.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Nope, not at all. I need to press the power button for it to start.

It'd flash back to stock with Odin and then go from there.
Sent from my SGH-I727 using xda app-developers app

jd1639 said:
It'd flash back to stock with Odin and then go from there.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I'm embarrassed to say that I didn't try flashing to stock because I figured it would work, but somehow, it did. I still feel that there's something wrong with the power button, and I'll be doing some more testing, but for now, everything's okay. Thanks for your help.

I bet you can reflash cm10 and it'll work fine. Just do a factory reset and the wipes and you'll be fine.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Wipe ALL the things, then Odin back to stock and reinstall. I'd bet that solves it
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

[Q] Help Phone won't turn on after trying to flash liquidsmooth

Hi,
I rooted my phone today and everything worked fine, I then went to CWrecovery to flash the liquidsmooth rom I downloaded. I selected to reboot device after a successful install but now it won't turn on, no screen, led, etc. if I plug into computer I get a contection noise from my computer but thats it. Can't boot into download mode or recovery... What can I do to fix?
thanks

Did you unlock and flash a custom bootloader?

I think so. I rooted/unlocked bootloader.
Did this: http://forum.xda-developers.com/showthread.php?t=2046439&nocache=1
For Both Root and Unlocked Bootloader ***RECOMMENDED*** - Download SuperSU + Unlocked Bootloader to your SD Card
Then tried to flash LiquidSmooth from forum.

Ryukashin said:
I think so. I rooted/unlocked bootloader.
Did this: http://forum.xda-developers.com/showthread.php?t=2046439&nocache=1
For Both Root and Unlocked Bootloader ***RECOMMENDED*** - Download SuperSU + Unlocked Bootloader to your SD Card
Then tried to flash LiquidSmooth from forum.
Click to expand...
Click to collapse
Did you wipe data factory reset prior to flashing the rom?
Sent from my SCH-I535 using xda app-developers app

no i didn't

If you forgot to wipe the phone would still attempt to boot. It just might send you into a bootloop
Anthrax unreleased towchwiz

Yeah except I can't get it to boot at all. No response to turning on, pulled battery, waited 30 minutes, then tried to boot again. nothing. not even the LED. now if I leave the battery out and plug the phone in to the computer the LED turns on but that's it. At the computer end I get the sound for plugging in a USB device, however it doesn't do anything else and there were no drivers for the device: QHSUSB_DLOAD.
Is it hard bricked?

Try getting into recovery by holding volume up+home button +power button at the same time. Hold it for a few seconds and it should vibrate and one the Samsung logo comes on you could let go. At this point I would either try re flashing or restore your most recent backup download another rom and try again.
Sent from my SCH-I535 using xda premium

mikeman45 said:
Try getting into recovery by holding volume up+home button +power button at the same time. Hold it for a few seconds and it should vibrate and one the Samsung logo comes on you could let go. At this point I would either try re flashing or restore your most recent backup download another rom and try again.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Tried that, as well at the Vol Down+ home+ power. Neither worked, no vibrate or screen boot.

Take your battery out for at least 5 minutes than put on the charger for awhile (couple hours) than try again. If none of this works hero had a wire up on how to fix your soft brick phone that might help. If your bootloader wasn't unlocked I'm not sure what to do to fix that. I hope you get it going. I'll post that link if I find it.
EDIT : read this post. http://forum.xda-developers.com/showthread.php?p=30386309
Sent from my SCH-I535 using xda premium

mikeman45 said:
Take your battery out for at least 5 minutes than put on the charger for awhile (couple hours) than try again. If none of this works hero had a wire up on how to fix your soft brick phone that might help. If your bootloader wasn't unlocked I'm not sure what to do to fix that. I hope you get it going. I'll post that link if I find it.
EDIT : read this post. http://forum.xda-developers.com/showthread.php?p=30386309
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My friend had this happen (not rooted), she took it in to Verizon and they got it going by holding VOL UP and DOWN, and then POWER.
I'd never heard of this technique, but it worked for her.

Post the link and exact file name of the rom you flashed.
Sent from my SCH-I535 using xda app-developers app

I just had the same thing happen, cleanrom 5.6 and tried flashing perseus kernel when it failed, now i have this

mikeman45 said:
Take your battery out for at least 5 minutes than put on the charger for awhile (couple hours) than try again. If none of this works hero had a wire up on how to fix your soft brick phone that might help. If your bootloader wasn't unlocked I'm not sure what to do to fix that. I hope you get it going. I'll post that link if I find it.
EDIT : read this post. http://forum.xda-developers.com/showthread.php?p=30386309
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Will the liquidsmooth i9305 rom brick a i9300 device forever?

[Q&A] [CM 10.2]

This is the Q&A for the unofficial CM 10.2 for the SGS4G.
Sent from my SGH-T959V using xda premium

Is it just me or is fix permission missing from CWM.

So, apart from GPS not working, as far as you know everything basic is working well?
sent from me

getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
Yeo, it is. I didn't touch anything related to the recovery except the recovery fstab that I must update to b compatible w the new JB so idk if I have to do anything else to have that feature back or it was CWM by default then, I will find out bout it soon.
itzik2sh said:
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
Click to expand...
Click to collapse
You can say so
Sent from my SGH-T959V using Tapatalk 2

Damn... I thought there was a chance GPS would somehow be possible I'm starting to think its wishful thinking... Come on samsung
Sent from my SGH-T959V using Tapatalk 2

getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
I believe koush decided to throw away the fix permissions button in CWM because he said it was largely placebo effect and had no real purpose anymore.
Sent from my Nexus 4 using xda app-developers app

Thanks for all the solutions and answers that I have collected from users around here, I have been able to update the OP for the FAQ (post 3) in the main thread. So either a question is answered here or not, please also have a look over the FAQ @ post 3 in the dev thread to track down the answered common questions, thanks .
Sent from my SGH-T959V using Tapatalk 2

so do you know if external mics work on this Rom?

Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?

http://www.android.com/about/jelly-bean/

Vismis said:
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
Click to expand...
Click to collapse
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium

1234west said:
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?

Vismis said:
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Click to expand...
Click to collapse
Battery Pull. Hold Vol Up + Vol Down + Power. Whenever The Samsung Galaxy S 4G Splash Screen Comes On, Let Go Of The Power Button And Keep The Volume Buttons Held Down. Should Take You To Recovery
Sent from my SGH-T959V using xda premium

OMG YES!!! I have no idea what i did but i pressed the combo when i plugged it into my computer and it looped the battery screen twice then went straight into CWM recovery did not go through the splash screen like a normal CWM recovery start but whatever i got to remove the rom and flash the new Slim Rom . Anyone have any idea what could have caused this just so i know what to or what not to do in the future ?

Try using adb
Sent from my SGH-T999 using xda app-developers app

To get to CWM recovery on this ROM, simply download 'Quick Boot' application and use it to get to recovery. It works.
Apex launcher crashes as well. I think issue is ROM related. Also, ROM is very heavy, I couldn't find why.
Edit: ROM is snappier after using CM performance features and letting cache do its work.
sent from me

jeffreylin_ said:
That's not very helpful if you can't get past the CyanogenMod splash though.
Click to expand...
Click to collapse
I got through the splash screen on 1st try.
You should check if you worked according to ROM instructions.
I usually always format system as well as wipe everything twice before flashing any new ROM.
I was referring to :
1. the lack of recovery button on power menu.
2. The inability to use hardware keys to get to recovery after flashing this ROM.
Heimdall One-click (in download mode) and try again.

You're right - I missed that option in developer features - it's called 'advanced reboot options'.
I'd suggest you get to download mode - one click heimdall and reflash this ROM after dowble wiping dalvik, cache, and format system.

I've flashed numerous ROMS to my phone before but have never ran into a problem like this.
-I went back to stock
-flashed CM7, as recommended from the OP
-downloaded and flashed CM10.2 but it gets stuck around 75%
I've been on this thread, and the rom thread as well as waiting a bit, hoping to find a solution or it figures itself out. Nothing! Is it unsafe to pull my battery when its at 'Installing update' (75%) for an extended period of time?
Also, i am on CWM 5.0.2.8
Thanks

I flashed it from ICS (Ultragen) and had no problem.
You can try that as well.