So my girlfriend bought this phone today, and when the phone got all up and running it wanted to do a system update to kitkat, said it would take about ten mins so she does the update and 2 hours later it still wasnt running ( got stuck on a screen that says "Finishing boot" ) after two hours it was rebooted and would not get past the motorola screen, so we took it back and exchanged it, came home and started setting up the new one and its stuck at finishing booting, can someone give me some advice on this
also its starting to get hot
It has went into a Bootloop, I would reboot into recovery and clear the cache
Wherezz said:
It has went into a Bootloop, I would reboot into recovery and clear the cache
Click to expand...
Click to collapse
its 100% stock, how do I go about doing that?
With the phone turned off, Press and hold Volume down + Power button for about 3 seconds, Select Recovery, then select wipe/format/clear (dont remember how it says) cache.
It should fix this
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
So, did it work?
that did not work, now trying the factory option as I would assume it means factory reset
The factory reset must work for sure, but I told you to clean the cache because the factory reset deletes all the phone data
Sent from my SGH-I777 using Tapatalk
Yes but there was no option to clear the cache in the recovery options , factory reset kinda worked , it can receive calls however its stuck on whatever screen it displays can't go to the home screen either
Sent from my SPH-D710 using xda premium
Is the Verizon one? You must activate it before you can use it, there is a way to bypass the activation screen, http://youtu.be/qhphsyRFEy4
Sent from my SGH-I777 using Tapatalk
Idk what it was but the phone rang and it started working . it is Verizon and it was activated , it froze at the Motorola logo but it was weird cause it didn't start working ...... Very odd but no idea why that happened
Sent from my SPH-D710 using xda premium
Related
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
I'm running Liberty ROM on my droid 2. I went to flash back to my standard blur infested stock screen and the phone won't come out of boot logo (which I changed to a DroidLife logo for the heck of it). I can't get into recovery. Android with the triangel and exclamation point show up. Hard reset gives this error:
E:cant open /cache/recover/command
I can not for the life of me get it to come out of boot logo. Is this bricked, am I screwed what? I need to come across a solution fast as a phone is crucial to my work.
Did you try holding x while powering the device on, then hitting the search hard key to bring up the stock recovery? Then wipe data/factory reset and wipe cache.
Sent from my ADR6300 using XDA App
I did. I've tried every method I know. The E:cant open /cache/recover/command message means the phone can't get to the recovery. Its annoying because all I did was flash back to a backup I made 4 hours prior to all this happening. FML.
Wipe everything I think may be help.
hoshikoong said:
Wipe everything I think may be help.
Click to expand...
Click to collapse
The phone will not access the recovery files so a wipe is unsuccessful. I've tried 12 times now, even called VZ tech support.
UPDATE: I've sent the phone in for insurance replacement. Though I would like to know how to solve this problem in the future.
My phone got crazy yesterday:
i don't know exactly when it started but when i start my phone up it says Media Scanning.
Then it says media scanned and then it goes like showing on the screenshot attached for hours, even after restarting.
I am not rooted and on gingerbread 2.3.5
Thanks for any help!
I decided to restore the phone but when i want to do that it wants a samsung account password which i forgot.
I tried also hard reset with dialing *2767*3855#. phone tried to shut down but didnt do it can i restore another way?
I also saw a video on youtube for gs2 with said that i have to press vol up home and power when the phone is ON until it reboots to android system recovery. then do factory reset there.
But will it work on our phone without root ?
Please help my phone starts annoying me
Deadfreak said:
I decided to restore the phone but when i want to do that it wants a samsung account password which i forgot.
I tried also hard reset with dialing *2767*3855#. phone tried to shut down but didnt do it can i restore another way?
I also saw a video on youtube for gs2 with said that i have to press vol up home and power when the phone is ON until it reboots to android system recovery. then do factory reset there.
But will it work on our phone without root ?
Please help my phone starts annoying me
Click to expand...
Click to collapse
Yes buddy. You can reboot your phone to Stock recovery (as you said you are not rooted and i hope u have not installed CWM). Switch off ur phone and switch on. When samsung logo appears, just press menu key+Volume up button. It will boot into recovery mode. From there you can wipe data/Factory reset your phone.
thanks for this tipp helped me out but do you know why the media kept scanning
At my girlfriend it was a sign before her her microsd goes defective......
Sent from my GT-I9103 using xda app-developers app
Hi all,
Earlier this week my HTC One Mini got stuck in an unstoppable bootloop. I couldn't even access fastboot/recovery, as everytime I booted into HBOOT the device would restart itself.
Thanks largely to the troubleshooting threads and the assistance of a few *extremely* helpful xda members, I've now escaped the clutches of the bootloop and I can boot into tr1gg3r84's 4.3 stock ROM.
However, my issues haven't been entirely fixed. The phone appears to boot up with no problems but when I try and use it, it'll hang for a second before unexpectedly rebooting. This is happened a number of times - within settings, within Play Store and sometimes whilst on standby when I'm not even touching it.
On top of that, the phone won't power off (even after deactivating fast boot in Settings > Power). I have tried powering off normally and in HBOOT - the screen goes dark for about 5 seconds, and then powers on again.
I thought I was out of the woods once the bootloop was fixed, but I'm at my wit's end.
Procedure I followed with current ROM:
- Wiped system, data, cache, and dalvik (TWRP)
- Installed Stock2.12.401.1Deodex(tr1gg3r84).zip
- Installed SuperSU update
- Rebooted into recovery
- Rebooted into bootloader
- Flashed boot.img from zip
At this point I attempted to start recovery from HBOOT in order to wipe cache and dalvik again - I got the purple 'Entering Recovery...' text but then the screen went black and rebooted as normal. After the phone booted for the first time, I enabled USB debugging and used 'adb reboot recovery' to get back into TWRP and wipe cache & dalvik.
Can anybody help?
Try following this thread.....reflash the OTA
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2573479
I have the same thing
the only way i can power it down is through the bootloader menu. Pain in the ass but it is a solid work around.
Macko mia said:
Try following this thread.....reflash the OTA
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2573479
Click to expand...
Click to collapse
Thanks for the tip, I'll give it a try.
elmuziko said:
I have the same thing
the only way i can power it down is through the bootloader menu. Pain in the ass but it is a solid work around.
Click to expand...
Click to collapse
I did try that, but all I get is a black screen for 2~ seconds then the phone powers back on.
i am using this device frm 2 years now, approx 2 month back i had successfully updated it through wi-fi.. it was all working very good ...
last saturday in the evening it started acting vulnerably as in it started rebooting sometimes after 15 min sometimes 1 hr sometimes 30 mins, but after reboot it worked fine for sometime and then again re-boot....same thing continued on sunday ... in the evening on sunday i thought of taking backup as i doubted it will crash ... but i did not had kies so i started the downloading of it and kept the tab aside on a table but when i checked after 20 min i saw it stuck on samsung logo.... now when i pressed power button it reboots with samsung music and stucks on the samsung logo... can anyone please guide me help me ... i dont want to loose my data on it,,,,
The service centre guys are like ull loose ur data for sure... but i am having some hope that i wont... please guide/help..
Pinkesh Suratwala said:
i am using this device frm 2 years now, approx 2 month back i had successfully updated it through wi-fi.. it was all working very good ...
last saturday in the evening it started acting vulnerably as in it started rebooting sometimes after 15 min sometimes 1 hr sometimes 30 mins, but after reboot it worked fine for sometime and then again re-boot....same thing continued on sunday ... in the evening on sunday i thought of taking backup as i doubted it will crash ... but i did not had kies so i started the downloading of it and kept the tab aside on a table but when i checked after 20 min i saw it stuck on samsung logo.... now when i pressed power button it reboots with samsung music and stucks on the samsung logo... can anyone please guide me help me ... i dont want to loose my data on it,,,,
The service centre guys are like ull loose ur data for sure... but i am having some hope that i wont... please guide/help..
Click to expand...
Click to collapse
Already Tried to wipe data/ factory reset?
i have only wipe cache... not yet done the data/ factory reset...
Pinkesh Suratwala said:
i have only wipe cache... not yet done the data/ factory reset...
Click to expand...
Click to collapse
you must wipe data/factory reset and reflashing rom again
Are you on a custom ROM or the stock?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
I am completely new to this things also i have never flashed this device its all what comes by default.. it goes in recovery mode provided by default .when i press power + volume up key... goes into android (3e) recovery
Then, unfortunately, I agree with blue_drt. A reset is probably the wisest choice. Of course all your data will be gone, but at least you'll have working Tab. I would try just resetting first to see if that fixes it, but if it doesn't, then you'll definitely need to follow blue's advice and reflash the ROM.
Sent from my GT-P5113 using XDA Premium 4 mobile app