When I turn the phone off as soon as it vibrate before turning off it just freeze on the screen with the phone saying shutting down and I have to pull the battery out for it to finish turning off. Anyone know how to fix this or has experience this issue before? Just started happening today.
Are you rooted? What rom if so? What kernel? What recovery? What model phone?
Sent from my Nexus S 4G using XDA App
I'm rooted stock rom stock kernal stock recovery model # is GT-i9020T
It just sounds like something is running and doesn't want yo shut down. Got any less quality apps on it?
I would start uninstalling one at a time and trying to shut it down.
Sent from my Nexus S 4G using XDA App
I don't think is that I did a factory reset and data wipe thinking it would fix the problem but it didn't! Also now when I connect the phone to the computer it won't recognize it all just gives me a code 43 any solution for this? I had it working before so I know the drivers were install correct since I use fastboot and adb.
If that's the case it sounds like it may be a hardware issue. See if you could use your warranty for a replacement.
Sent from my Nexus S 4G using XDA App
I guess it is phone just die can't send to Samsung cause bootloader was unlock and the voids the warranty
Related
Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!
You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App
brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila
The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.
You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium
So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App
Again the exclamation mark IS the stock recovery.
Hey I'm in need of some serious help. My power button no longer works. It's as thought the phone thinks its constantly being held down. (Put battery in phone boots up by itself). I'm pretty comfortable with flashing roms etc and I need to get the bootloader locked for my warranty. I've tried multiple ways (I've done it in the past for friends). The 'fastboot oem lock' in fastboot via cmd doesnt work. It appears to be due to the power button being held down. It wont progress any further. It is not physically jammed (trust me ive tried fidgeting with it lemme tell you). I'm at a loss. Any ideas?
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Same thing happened to me and I sent it in for warranty with the bootloader unlocked. Samsung fixed it and no charge.
garu12 said:
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Click to expand...
Click to collapse
Dang. I hope u can fix it.
Sent from my Xoom using xda premium
Thanks for the replies. It's impossible to relock in this state! I did manage to unroot and install a stock rom so at least it's gonna look somewhat legit when I bring it in. Going to the Samsung repair center tomorrow (there is one not far from me so I dont need to send it). I'll let you know how it goes. Wish me luck!!
So I went in today to the Samsung repair center and 2 hours later my Nexus is good as new . Pretty classy of them. That's really good service. They didnt even question the unlocked bootloader and it was covered by the warranty. This makes me want to stick with Samsung. When my Nexus One power button died it took like 4 weeks to get it back
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
I have an entirely different issue but it involves me sending in my phone to samsung with an unlocked bootloader. My phone won't boot past the google screen and I can't relock the boot loader via adb. I've already sent the phone but didn't mention anything about it being rooted when I called customer service. Think there's a good chance they'll fix it no questions asked?
bradmikd said:
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
garu12 said:
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
Click to expand...
Click to collapse
or just adb reboot recovery
I installed ROM manager on my 2.3.6 gingerbread rooted SGM and clicked back up ROM. The device went totally dead and it wont show ANY signs of life whatsoever. So pressing any of the buttons combo wont work. The phone seems to be dead for real. I did manage to make Odin detect it even if the device seems to have no power and looks like its turned off. But it will not let Odin establish connection to it to flash a new OS on it.
Is there anything I can do? Have anyone solved this brick by now since is see a lot of people having this issue?
Can you pull the battery.
Sent from my MB855 using xda premium
Like how? I have pulled the battery out and put it back in with no result. Or did you mean to pull it out in a certain manner?
Ok, Does the battery charge when plugged in? Do you have another battery?
Sent from my MB855 using xda premium
No,the phone is totally dead. Like as if it would have no battery in. None of the button combos won't work on it. But if i press the emergency download mode button the Odin detects the device even if it seems dead,so the phone is alive i guess. But when i start Odin it starts the tread but get stuck on connecting.
All I know is basic trouble shooting,
I know Moto won't flash with out a good charged battery. Is there a forum for your phone here. Or try googling oden for info. Sorry i can't help more.
Good Luck
Sent from my MB855 using xda premium
As far as I have read so far my motherboard needs to be replaced. Tis is a ultra hard brick. People that got their galaxy mini bricked by ROM manager had to visit service center.. Hope they can't find out what happened. Thx for the replies!
Good reason to not use rom manager
Sent From Space Using My ICS Flavored Sensation
My phone is so hard bricked they couldn't fix it at customer service,they said they had to send it to another service,because it has a complex error. I keep my fingers crossed they can't find out what happened.
Got the phone back after 4 days,motherboard replaced,free of charge.
brick?
Hello.
i,ve installed rom manager and tried to make an backup of my rom.
my phone turned black and now its useless
anyone knows how to fix this ( galaxy mini gt s 5570 gbread 2.35 rooted)
i've tried to use odin but got no idea how to use it
anyone can help me?!!?
(phone has still 1 from the 2 years of warranty is this still valid or is it gone because of the root?)
It's hard bricked, you can do nothing, it's no use. Get it to service center saying that you dropped it and it wont turn on. dont say that you rooted your device. I've had this hardbrick too.
took it to the service center now waiting for them to fix it they said it could take several weeks.......
I was having really bad force close issues and I did a factory reset and it didn't make it better. They were system up and home force closes. They came up constantly so I couldn't even get into settings to turn on debugging mode to do any of the methods to go back to stock. I called and got a replacement but will T-Mobile know my phone was rooted and will they even care.?
Sent from my LG-D801 using Tapatalk
em2drvr03 said:
I was having really bad force close issues and I did a factory reset and it didn't make it better. They were system up and home force closes. They came up constantly so I couldn't even get into settings to turn on debugging mode to do any of the methods to go back to stock. I called and got a replacement but will T-Mobile know my phone was rooted and will they even care.?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Rooting does void your warranty and supposedly there is a root detection mechanism that they use that's on the stock ROM. I've only seen it mentioned but I don't know anything about it.
On the other hand people have sent in LG G2's for screen repair that are rooted and they've just received a new phone back. Since your problem is software and not hardware I imagine there could be extra grief in trying to repair a phone that's rooted since they will use different tools. I'd say it would depend on how they repair/replace your phone.
You can remove the ROOTED indication in download mode. See http://forum.xda-developers.com/showthread.php?t=2700992
diamond12 said:
You can remove the ROOTED indication in download mode. See http://forum.xda-developers.com/showthread.php?t=2700992
Click to expand...
Click to collapse
The problem is that bc of the fc's it won't me do anything on the phone. It's completely unresponsive.
Sent from my LG-D801 using Tapatalk
Have you tried a hardware factory reset using the poweron key sequence? (power+vol-, let go when LG logo comes up, press again immediately)
Also, maybe try to reflash 4.2.2 kdz.
Hey guys,
my brother owns a Nexus 5 (duh, otherwise why would i be here )
but anyways, his phone is just stuck at the boot screen. As in as soon as you try powering it on, it shows the Google sign but then it just continually restarts after that. I've tried entering the bootloader but as soon as I access it, it just forcibly reboots without me pressing anything. I'm kind of stuck here as I can't really do anything.
Does anyone have any clue what to do?
Edit: forgot to say he's full stock as in no root, no unlocked bootloader, no recovery etc.
Hi,
Keep the turned off for a bit and then try accessing the bootloader.. From there, go to the recovery and perform a factory reset.
If you can't access the bootloader or it keeps restarting again and again in bootloader, it might be a eMMC failure..
- Sent from an IceCold Hammerhead!
Could the power button be stuck?
Sent from my Nexus 5 using XDA Premium 4 mobile app
vin4yak said:
Hi,
Keep the turned off for a bit and then try accessing the bootloader.. From there, go to the recovery and perform a factory reset.
If you can't access the bootloader or it keeps restarting again and again in bootloader, it might be a eMMC failure..
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
I have certainly tried this. At the moment, im charging it. So let me get this straight, the only way around a dead eMMc chip would be
To RMA and request replacement?
korockinout13 said:
Could the power button be stuck?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have also considered this as well. Is there anyway to get around this? Or perhaps fix this even?
Perhaps its also worth to note that it will only do this when its connected to a charger but when disconnected, it wont even turn on (as in no google sign or bootloader)
Sent from my Nexus 5 using XDA Free mobile app
If it's stock, what happened to cause the situation?
Sent from my Nexus 5 using Tapatalk
Same here - phone was in my bag overnight and off this morning (battery full).
When I started it up it went into boot loop.
Stock ROM, no modifications whatsoever, 2 weeks old phone.
Anybody else?
072665995 said:
I have certainly tried this. At the moment, im charging it. So let me get this straight, the only way around a dead eMMc chip would be
To RMA and request replacement?
Click to expand...
Click to collapse
Yes. Motherboard needs to be replaced in the case of a dead eMMC.
fkoehn said:
Same here - phone was in my bag overnight and off this morning (battery full).
When I started it up it went into boot loop.
Stock ROM, no modifications whatsoever, 2 weeks old phone.
Anybody else?
Click to expand...
Click to collapse
Phones are not meant to be kept in the bag.. May be the bag hit somewhere and the phone took a brunt of it? Who knows??
Or it could also be a random failure..
Can you access the recovery? If so, try a factory reset from there and see whether it boots up?