Database Info

[Q] [ISSUE] freezes while phone is in stand-by and while using apps

hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.

I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.

Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.

"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.

thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.

simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?

stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?

no, I'm using stock kernel and never flashed a custom kernel.

stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.

--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...

stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .

In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App

stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.

stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App

According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en

Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up

[Q] Nexus S ICS first load problems

HI
I rooted and installed ICS on my Nexus S. I rebooted it and its been trying to load for 20 minutes. I decided to pull the battery and reboot it again and again for the past 30 minutes I keep getting the loading screen graphics. Can you please help?
Thanks

adamniazi said:
HI
I rooted and installed ICS on my Nexus S. I rebooted it and its been trying to load for 20 minutes. I decided to pull the battery and reboot it again and again for the past 30 minutes I keep getting the loading screen graphics. Can you please help?
Thanks
Click to expand...
Click to collapse
Pull the battery connect ot pc via usb then press power n volume keys to reboot to recovery then wipe all and reflash or reinstall backup.
Sent from my GT-P7510 using Tapatalk

Did you wipe cache and dalvik cache? And do you have an unlocked bootloader?

Which image you used to install? Try the full OTA one for your phone model from the link in my sig.
Also do a full wipe before flashing.

Thanks, I went back into bootloader and I went to reset to factory specs but instead i think it cleaned my phone of my information and then when rebooted, went into ICS easily, Love the OS but I am not getting a wireless signal. I read one post where someone was running a gingerbread radio so now I am seeing how to do that

[Q] Can't get past boot logo

Hey guys,
First off I am the newbiest of the noobs. And I think I stumbled into bricking my asus tf101. I was wondering if you incredibly amazing developers would have a work around for me
I had rooted the TF101 a while back it worked everything was fine, I was frustrated with the poor video performance and thought maybe upgraded to jellybean may improve some speed issues with the tablet. So I ran off did some fast googling and found a forum that posted the nightlies. (Team EOS from this site)
I downloaded the first one (right to the tablet) booted into the root bootloader thing (yea im so noob I don't even know the proper wordage) and installed from that.
Now when it boots it sits at a 4 colored square logo that rotates a pules. each little piece glows (like it's loading) but it just sits there forever. i have waiting 10-15-30-45 minutes nothing.
I was wondering if there was a way I could download a new jellybean file on a SD card, and somehow install over with that?
Could really use the help and need it explained to me like im 2 ..
Really sorry to have to ask guys. Save me!

It's a very well discussed issue here and in the teameos thread.
Did you do a full cache, dalvik, system and factory reset of the device through recovery?
Which recovery are you using? (you probably need a newer one)
If you can still boot in recovery (you should) then wipe cache, dalvik, system, do a factory reset (does not wipe sdcard but you will lose all other data) and finally reflash the rom.
If you can't boot in recovery for whatever reason, you can use easyflasher to go back to stock then start over. Frederuco made an awesome post detailing the entire procedure on transformerforums.

[Q] [Help] Stuck on HTC boot screen, other issues in thread

(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start

splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.

irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?

bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.

Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.

Recovery and version?

bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0

Full wipe?

bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.

irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?

bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.

bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.

[Q] Phone stuck when turning on

Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.

SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.

bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?

SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.

SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.