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 (wind mobile) can't factory reset! (jellybean)

Hi, first post here.
So I bought a Nexus S that was rooted and updated to Jellybean. It's an unlocked phone originally locked to Wind Mobile.
So it's been having issues with getting stuck on the google logo after reboot, so I decided to sell it. Problem is when I go to factory reset the phone it shows the reset bar but then that turns into a big triangle with an exclamation mark on it with a little android guy next to it. The phone gets stuck there. All I can do from there is remove the battery.
From there I tried going on bootloader using power and volume up (says unlocked btw), and from there I load recovery. On recovery there is an option to factory reset and I click on there, however it doesn't do it. This is what I says:
"--wiping data...
formatting /data...
E:format_volume: make_extf4fs failed on /dev/blo/ck/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete."
So I think the error might be accociated to the sd card because the Nexus S doesn't come with an sd card, it has built in memory? Also on recory when choose "mount sd card" it says"Error mounting /sdcard!".
So how do I go about fixing my problematic phone? I have a dude that wants to buy it but I can't even reset the damn thing, let alone fix the freezing at start up issue. I am also totally new to this.
Extra info: When the phone freezes at the google logo at start up I get passed that by using a blow dryer on the phone. That's the only way I start up the phone after the battery comes out. This is the gt-i9020t model.

Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!

gunner49 said:
Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!
Click to expand...
Click to collapse
I don't know if it's a custom recovery because the previous owner installed everything/rooted.
When I press power and vol. up, It looks identical to the uploaded picture's bootloader/recovery.

Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.

gunner49 said:
Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.
Click to expand...
Click to collapse
In advanced there is no option that worked.

*Solution*
Ok so for those having this problem this is what I dug up:
Internal SD card error causes the boot freeze/factory reset error. When you try mounting SD card it fails, this is also what makes me think it's a fault with the phone's internal SD card.
I do not know how to "fix" this fault, however I'll tell you what I did to get passed this issue.
1) Heating up the phone helps bypass the frozen screen. On Boot it goes to the google logo and freezes, but you can get passed this by heating up the phone (using a blow dryer) before hand and it's relatively successful.
2) I believe that before factory resetting the phone (whether using recovery or the actual reset option on settings), if you heat up the phone, it might work the same way it works when booting up.
I did not try 2) because I managed to "reset" my phone manually by uninstalling all apps, deleting all files/cache/photo's/accounts, and by clearing all app data. This works just as fine if you ask me.
Overall this solution has not been "fixed", I encourage people to find a real fix, but for now using the blow dryer and manually resetting is one way around the problem.

[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.

HELP!! CM12 not working!!

I downloaded TWRP 2.8.6.0 and installed it. Then I downloaded cm-12.1-20150405-UNOFFICIAL-xt897.zip ...put both on the SD card...went into TWRP, wiped the system, installed CM12.1 and it stayed at the boot logo for about 20 minutes. I rebooted, wiped again, and now I am stuck at the warning screen about the bootloader being unlocked....can't get into the phone OS at all....

Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).

arrrghhh said:
Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).
Click to expand...
Click to collapse
I didn't do a backup due to lack of space available.....plus i've had plenty of experience with flashing phones/ROMS....this one was supposed to be so easy.....but its proven to be very difficult.....I did flash another ROM on it and its at the loading screen......never seen a phone take so long to load.....sadly, I was wanting Lollipop and this one that I'm loading up now is KitKat......been loading for over 10 minutes now.......I have two of these phones, I guess I could do a backup of the other one and restore onto this phone....not sure if that will work......

Same problem here and I did restore a backup and it wouldn't boot either anymore

4218kris said:
Same problem here and I did restore a backup and it wouldn't boot either anymore
Click to expand...
Click to collapse
There's always RSDLite as a last resort.

My cousin flashed a nightly early this week and now it's stuck in a bootloop. I tried flashing latest recovery en formatting /repairing data and internal storage. But I always get an error on format DATA and trying to repair Internal Storage is not even an option.
Next I tried CM recovery. Nada, same effect. Flashing is possible, it even boots, but then it also loops.
Just flashed using RSD LITE 6.1.5 icw asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip. Still, this baby won't boot!
So unless someone comes with a fix... This baby is dead. Something very wrong with internal memory I guess.

I finally got it to boot, I do get the error on formatting data too but try a couple times and it seems to work. It always has an error the first try. I also flash the ROM with data and cache on ext4 then changed it after flash and after first boot it will factory reset the phone when changing from ext4 to f2fs. That's what I did and it worked for me.

Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.

Die Bruine said:
Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.
Click to expand...
Click to collapse
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app

palmbeach05 said:
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.

Die Bruine said:
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.
Click to expand...
Click to collapse
Ok, just checking. Did you wipe data and cache when doing that?
Sent from my SM-T320 using XDA Free mobile app

Yes I did. I would like to try 4218kris' suggestion. But without touch input that's not an option. Switched fronts to be sure, digitizer is ok. I'll leave this one for what it is. Still two users left in te family with XT897. When those break down I won't be replacig them.

Problem with BlissPop: Stuck at "BlissPop is starting..."

Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?

Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.

I don't have any SD card in my tablet though, thanks anyways.

Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk

Tried doing a format of system as well as data/cache/dalvik, still getting same result :/

Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk

When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.

any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works