Database Info

[Q] HELP!! Samsung Nexus S Crashed, Cant do anything

Hi
I have a Samsung Nexus S for past 5 months. I recently upgraded to the ICS. Last week, I was listening songs on my phone and all of a sudden out of nowhere the phone re-started.
After couple of minutes, saw a message on screen saying “encryption unsuccessful, you have lost all your data. This phone will now need to rebooted”.
Underneath this message, there was only 1 option of REBOOT NOW. I had to press the button since I had no other option.
After this the phone restarted but never went past the start up animation screen. After couple of days, I gave it another shot and after going past the welcome screen, it gave me the option to register the phone again. But as soon as that screen comes up, I get all these small messages saying, email has stopped, music has stopped, android process has stopped, calendar has stopped................ at this point the phone virtually hangs itself and I can’t do anything.
Can someone please advise what is wrong with my phone and how can I fix it?
Any help would be very much appreciated.

Try this, power the phone off, now press and hold the volume up & power botton at the same time, a menu should appear, now use the volume up/down buttons till "RECOVERY" is highlighted green, now press the power button, the phone will now reboot and in to recovery and show an android on the screen, at this point you need to press and hold the power button then press volume up briefly, a menu should appear, use the volume up/down buttons to highlight "wipe data/factory reset" and press the power button, now use the volume up/down buttons to highlight "Yes -- delete all user data" once this is done select "reboot system now", this process will wipe the phone and put it back to factory settings, it won't delete usb storage though so you may need erase usb storage once you're up and running again.

d.chatten said:
Try this, power the phone off, now press and hold the volume up & power botton at the same time, a menu should appear, now use the volume up/down buttons till "RECOVERY" is highlighted green, now press the power button, the phone will now reboot and in to recovery and show an android on the screen, at this point you need to press and hold the power button then press volume up briefly, a menu should appear, use the volume up/down buttons to highlight "wipe data/factory reset" and press the power button, now use the volume up/down buttons to highlight "Yes -- delete all user data" once this is done select "reboot system now", this process will wipe the phone and put it back to factory settings, it won't delete usb storage though so you may need erase usb storage once you're up and running again.
Click to expand...
Click to collapse
I would wipe cache while you're in there too.
Sent from my Nexus S using xda premium

i tried doing that. i cant get into recovery mode, when I press volume \up and power i get into that screen where it displays all the options such as recovery, bootloader etc etc. I select recovery (I dont see a android exclamation sign instead for a split second I see android and a triangle) and press volume down/up + power button, nothing happens. after some time it reboots and hangs itself at the animation screen..........any suggestions? your help is much appreciated.

puriaditya1234 said:
i tried doing that. i cant get into recovery mode, when I press volume \up and power i get into that screen where it displays all the options such as recovery, bootloader etc etc. I select recovery (I dont see a android exclamation sign instead for a split second I see android and a triangle) and press volume down/up + power button, nothing happens. after some time it reboots and hangs itself at the animation screen..........any suggestions? your help is much appreciated.
Click to expand...
Click to collapse
I think that you have to push clockworkmod recovery image like when you root your device.
Sent from my Nexus S using Tapatalk

is there any 'how to' guide to do that?

puriaditya1234 said:
is there any 'how to' guide to do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1007782
Check this thread.
Sent from my Nexus S using Tapatalk

yeah, try using clockwork recovery.
that's much more usfeul than the stock one

i tried doing clockwork recovery, I cant unlock the bootloader, i did all the steps ie installed android drivers, went to command prompt, typed the command, I can see the option of unlocking bootloader on android but when I select yes, it still says locked. I guess I will have to give up on this phone.

puriaditya1234 said:
i tried doing clockwork recovery, I cant unlock the bootloader, i did all the steps ie installed android drivers, went to command prompt, typed the command, I can see the option of unlocking bootloader on android but when I select yes, it still says locked. I guess I will have to give up on this phone.
Click to expand...
Click to collapse
Try using one click root v6 by shabbypenguin. That will work for you. Its what I used and its so easy. Just look for it here on xda
Sent from my Nexus S using xda premium

Cannot boot into recovery!

Hey guys! I just got a One X from AT&T bought on eBay, although I live in Europe.
I managed to unlock the bootloader by changing the CID to 1111111 etc. (how many 1's?) and it worked fine.
I then ran installed ClockworkMod Touch Recovery for the HTC One X through terminal and it was a success.
I rebooted by holding down the power and volume down, and attempted to boot into recovery. I got a white screen with the HTC logo, and red text underneath saying something like "do not use this without HTCs permission" or something of the sort. The phone then turned off.
NOW I'm trying to boot again into the bootloader (I think that's what it's called, but by turning it off and holding the volume down and power key) and it just doesn't work. I've tried a million times, with different variations of holding down the keys. What happens is the light on the touch keys at the bottom flashes a bunch of times, then it boots normally. Everything works on the phone otherwise.
I tried to do it via fastboot/terminal by issuing the command ./fastboot-mac reboot-bootloader but it just says "waiting for device..." even though it's connected.
Anyone had this problem and found a solution?

Recovery
Clockwork recovery is not supported on the evita. Download goo manager and you should be able TWRP from that. And then you can reboot into TWRP.

I think you flashed CWM for the international (Tegra3 quad core) One X. Install TWRP as previous poster recommended.

There is no version of CWM Touch Recovery that is supported for the AT&T One X. You flashed the international version. Fortunately, you can flash TWRP right over it inside Goo Manager.
Be thankful you didn't flash it inside ROM Manager or you could have bricked your phone. I've seen people do it in the past.

ansedve season
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?

in fastboot run this command "fastboot erase cache", then boot into recovery.

DvineLord said:
in fastboot run this command "fastboot erase cache", then boot into recovery.
Click to expand...
Click to collapse
Don't be too concerned with the blah blah in red writing about development version etc. on the boot screen - you get that boot screen when you unlock the bootloader.

mollysue said:
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
Click to expand...
Click to collapse
What did you do in recovery? Did you flash anything? Does the phone not boot up now?

Thanks guys for all your help. I guess know I technically know what to do to fix things, thanks to you. The only problem that after probably over 100 failed attempts I cannot boot into recovery. I tried all variations of holding the power and volume down button while restarting, rebooting, turning on/off or up/down sideways but it just boots normally every time.
This means I can't use fastboot etc. I guess unlocking the bootloader and voiding the warranty was for nothing
If you know another way to reboot into bootloader other than the hardware buttons method let me know!

Believe it or not, I think you are just performing the button presses incorrectly, if you can't access the bootloader. Bootloader is probably still intact, otherwise the phone would not be working at all.
1) In Settings>Power, make sure "fast boot" is not checked.
2) Then power the phone off fully, but holding the power button until the power menu comes up, and select "Power off". Wait a minute for the phone to power off completely.
3) Hold down the volume down rocker. DO NOT release it until I tell you to later.
4) Press the power button for 3 seconds, then release. DO NOT release the volume down rocker.
5) Once the white bootloader screen shows up, release the volume down rocker.
Alternately, you can do this:
a) With the phone powered on, hold the power button until the capacitive buttons flash (about 5 seconds).
b) The moment the screen goes black, hold down the volume down rocker, (again, DO NOT release it until the bootloader screen comes up) but release the power button.
The timing for this method is a little trickier, if you press the volume down rocker too late, it will boot normally (or safe mode), and too soon, and it just reduces the ringer volume and the phone stays on. But as long as you press and hold volume down the moment the screen goes black, it will work.
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
But also, I would still not recommend trying to boot into recovery until you have installed the TWRP recovery as mentioned previously on this thread, if you have not done so already. There is no CWM Touch Recovery for this phone, so I'm pretty certain you installed in improper recovery on the phone, and recovery will not function at all.

Alternatively, you can go into Goo Manager and select the "Reboot Recovery" option, which should get you into TWRP

Or from command prompt "adb reboot bootloader" so long as you open your prompt from your adb application folder.
Or alternatively skip the middle man: "adb reboot recovery"
I really think your problem lies with your button pressing -- follow instructions on the previous post and you should be home free.

Well I actually eventually managed it! I think the volume button was a bit stuck because it still takes a few tries to boot into bootloader, but eventually I managed it and am in the TWRP menu right now!
I did a little victory dance when it happened. Thanks again!

[Q] CM 10.1 Permanent Soft Brick?

Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!

Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium

DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.

phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.

DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?

phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.

It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2

Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops:

[Q] HOX stuck in bootloop with no access to bootloader

Ok.. I'm about to lose hope, please any creative ideas will be much appreciated..
I think i did a big mistake trying to update to the latest nightly release of CM 10.2 using the auto-update feature of cm 10.1...
The end result is a bootloop, gets up to the CM rotating animation for a few seconds and reboots.
on top of that:
unable to get into bootloader using pwr+vol up nor vol down
unable to access device using adb nor fastboot - shows no device connected
the PC does not recognize the device though there are drivers installed, the charging LED lights up but no PC activity
all of the solutions i've seen assume either the recover/bootloader is available or the phone is accessed via fastboot/adb.
in this case neither are correct....
for some time i wanted to upgrade to htc one but not yet....
please help

Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app

exad said:
Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.

You could try letting it drain completely. Then charge a bit and try again.
Is your phone plugged in while your trying? My phone will not enter bootloader while its plugged in.
Sent from my One X using xda app-developers app

spitfireatz said:
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.
Click to expand...
Click to collapse
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.

redpoint73 said:
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.
Click to expand...
Click to collapse
I wish it was the case,
when i try to go into hboot the device instead of going into another boot until animation cycle, goes into black screen boot cycle. which means most likely that the action (PWR+Vol) does have an effect otherwise it would have continued to go into same boot cycle through the CM animation..
besides there is a recovery installed, or at least was...
is there anyway to re-install the hboot part without the hboot/fastboot availability?

spitfireatz said:
is there anyway to re-install the hboot part without the hboot/fastboot availability?
Click to expand...
Click to collapse
If you are s-off, try running the RUU.

Loop boot without a root. Help needed.

Suddenly my phone (z710e) jumped into a loop boot.
It's not rooted, no custom stuff, no custom bootloader.
It loads fine, but after 1-2 seconds reboots.
I've already tried to unbrick it with no result, computer can't see my phone.
Help with an advice or a link or anything useful will be great!
Thanks!

S1R1N said:
Suddenly my phone (z710e) jumped into a loop boot.
It's not rooted, no custom stuff, no custom bootloader.
It loads fine, but after 1-2 seconds reboots.
I've already tried to unbrick it with no result, computer can't see my phone.
Help with an advice or a link or anything useful will be great!
Thanks!
Click to expand...
Click to collapse
If i remember correctly you can wipe cache from the stock recovery. Boot into hboot by holding down volume down and power. Use the volume buttons to highlight recovery and press power. Then you will see a little android or a red exclamation in a triangle. Press the volume buttons and power until options appear on the screen. If it gives you wipe cache, them wipe it. Other wipe options may/will remove your personal data so use caution and know the risks
Sent from my nexus 7 using Tapatalk

heavy_metal_man said:
If i remember correctly you can wipe cache from the stock recovery. Boot into hboot by holding down volume down and power. Use the volume buttons to highlight recovery and press power. Then you will see a little android or a red exclamation in a triangle. Press the volume buttons and power until options appear on the screen. If it gives you wipe cache, them wipe it. Other wipe options may/will remove your personal data so use caution and know the risks
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
unfortunately power+volume doesn't work.. it just boots as usual (

S1R1N said:
unfortunately power+volume doesn't work.. it just boots as usual (
Click to expand...
Click to collapse
did you remove first the battery and then put it back?

S1R1N said:
unfortunately power+volume doesn't work.. it just boots as usual (
Click to expand...
Click to collapse
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Edit: removed incorrect data.

heavy_metal_man said:
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. If it fails after 3 battery pulls then your device has fast boot enabled in its settings. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
it doesn't matter if you have fastboot enabled
you can still have access to the bootloader when removing battery and putting it back

heavy_metal_man said:
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Edit: removed incorrect data.
Click to expand...
Click to collapse
I've tried to remove battery and reboot before, nothing changed.
adb - no, did not used

Solution was - to disassemble it and assemble... After that phone booted normally. :victory:
Thank you all for your replies!