I was in a bootloop on my Nexus S. The phone was completely stock. It was never rooted and never ran any custom roms. I charged the battery, then turned on the phone and it went into a bootloop. I tried a battery pull, and nothing. So I finally decided to follow this tutorial and rooted the phone. Now the phone boots up and all is good again. Can anyone tell me what most likely would have caused this to begin with, and why rooting would have fixed it?
Corrupted file somewhere, likely in /data, otherwise maybe .android_secure. Unless its a battery related issue I'd put it down to this.
No idea what exactly it could've been and never heard of someone with the issue though. One of technologies mysteries in the end.
Harbb said:
Corrupted file somewhere, likely in /data, otherwise maybe .android_secure. Unless its a battery related issue I'd put it down to this.
No idea what exactly it could've been and never heard of someone with the issue though. One of technologies mysteries in the end.
Click to expand...
Click to collapse
Well I looks like it's mystery solved. I think it was a hardware problem, as it went back into bootloop at first, but now it's stuck on the Google logo. I can't even unlock the bootloader anymore. Each time I try fastboot oem unlock, it comes back as: Failed <remote: Erase Fail>. Everywhere I've searched for a solution, comes back as a hardware failure. The phone is only over a year old.
I've flashed my 2 galaxy s 4gs countless times and always kept this thing completely stock until I had to unlock and root this thing just to get it working. And now it seems it's totally bricked without even flashing a single rom with no more warranty left. Go figure.
More and more people getting that erase fail error. Speak to Samsung and let them know it seems to be a common problem with the nand chip they used. Plenty of others with the same issues, most lucky enough to get it fixed under warranty. Just maybe there is someone nice enough to help.
Related
Well, what the title says. It's becoming extremely annoying. Any suggestions?
what rom are you on?
I was on stock UCLA3, but when this problem occured I completely went back to stock. Still exists.
have you tried to do a 3e recovery factory restore?
I don't know what to do, honestly. I'm open to any suggestions! I'll look that up, thanks in advance.
Flash a custom rom with good kernel!
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
MAGiK9 said:
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
Click to expand...
Click to collapse
Yeah thats a bad thing, but they probably wont say anything. Don't mention anything about the counter
I started having the exact same issue this last weekend, took my phone into At&t warranty center, they replaced the battery and did a reflash back to factory rom. Still had the issue after that. The problem didn't start till after I took it out of my otter box and started taking the back off to pull the battery for rooting and flashing roms. Since i have put the phone back in the otter box case I have not had it restart on my yet. I am thinking it is a loose back cover and the battery is being knocked loose and then back in place hence the restarts. Just some of my observations from my own experiances with this same problem.
Ironically, mine has never happened until I took it out of the Otterbox Commuter case.
luckily i haven't had this issue, and i have removed it like 8-10 times before learning I didn't have to...
I took my phone to the att store so they could look at it.. I explained what was going on and the guy told me he was going to check the counter.. BUT he never did. He ordered me a new battery, and if that does not work they will send me a new phone. However, i'm going to get the new phone anyway.
Reboot issues and battery
Ok, same problem here, ICS leaked 4.0.3, Samsung Galaxy S2 skyrocket. Thought it was setcpu and/or busy box, not.. I notice that when I moved my phone in an odd manner it would reboot. Removed the battery cover and noted that there was play in where the battery sat, so much so that I was able to stick my finger nail into the separation, I don't know call it a half a cm. Any way, I took some note book paper, made a wedge so the battery was nice and tight... so far so good. Will let you know.
I'm not sure if this will be any help or not. My phone has done the same thing a couple of times and at least twice I've noticed that it was because I had the phone in my pocket and I was accidentally holding down the power button when I was bending over/squatting/etc. As for the other times it has restart on its own, I have no idea. It's been at least a month since those happened though.
Hi,
I wanted to update my Nexus S from SlimBean 4.2.1 1.0 to 1.1 this morning.
I didn't do a full wipe which basically ruined my OS so I wanted to back it all up, full wipe and start all over again.
I had big problems with backing up as Titanium Backup either crashed or was stuck at it's initializing SQLite stage.
The phone process and System UI were crashing all the time if that matters.
So I tried to back it up through CWM which first failed while backing up the data partition, but it worked the second time.
I turned the phone off and since then it's not doing anything anymore.
Won't turn on, doesn't show the charging animation when plugging it in.
I tried to recover it several times.
It doesn't show up in Windows' Device Manager and UnBrickableRessurrectorR40 doesn't see it.
Is there anything I can do?
Thanks a lot.
land.apfel
why don't you try to get it to download mode and flash via odin ?
I would do it that way if it was possible. The Nexus won't do anything. Neither fastboot, nor Download nor recovery nor anything else.
The only thing it does is getting hot when being connected to AC.
But I'll try to do the UnbrickableMod and see if it helps.
land.apfel
Did you make the hardware modification? I have to do it with mine to be recognized.
samcortez said:
Did you make the hardware modification? I have to do it with mine to be recognized.
Click to expand...
Click to collapse
hardware modification is so difficult so as to be impossible for most people. it seems to be the only solution though. i only just bought my nexus s (for $150) second hand .. flashed cwm 10 on it and it bricked a few days later when i swapped a battery. i have disassembled the phone but the modification required needs minute tools and expertise beyond my ability. any suggestions? sending it in to experts in the USA will cost me nearly $100 and I'm afraid the diagnosis might mean I will lose that as well.
Without the hardware modification you can trash your Nexus S right now, as the chance that you recover it for some reason is probably 0.01%.
For doing the hardware modification you really need to know what you're doing. If you don't, look out for someone you know and who would do it for you.
After you did the UnbrickableMod, the chance that you can recover your phone is about 60% (maybe).
If you can't recover the phone, you need to exchange the eMMC chip as well.
I found eMMC chips in China for $19, but you still need to assemble it.
This is where I'm stuck at the moment.
my phone is in same condition please someone solve this and share with us
If you haven't already applied the UnBrickableMod you should try that first.
If you have, I have no idea what to do.
land.apfel
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down. I thought it was because the rom was not stable enough so I flashed CM9. On CM9 the phone would shut off every five minutes it was that bad. I then installed Miktouch 0.7 and the shutdowns for the most part stopped. The phone will shut down now and again and it always shuts down after I use youtube for 10+ minutes or use the camera for several minutes.
I tried to revert to stock and see if that fixed anything but when I boot into the bootloader it looks for PG59IMG and says no image found and nothing happens. I got the PG59IMG from this thread: http://forum.xda-developers.com/showthread.php?t=1878329
Any help is appreciated.
I swear it sounds mechanical...maybe battery related. Just starting out of the blue like that and it being cross ROM and all. It should just flash that file automatically from hboot though. Are you sure you copied the file to the root of your SD card? Did you relock your bootloader with *fastboot oem lock* before running it? Sometimes it doesn't like it if the usb cable is still plugged in. (for some weird reason) If you're still S-On, did you flast the boot.img file thru adb with *fastboot flash boot boot.img* after flashing your ROM?
Oh yeah, you won't be able to flash that PG59IMG if it is newer than the hboot version listed in your bootloader right now. That is until you get S-Off with the wire trick.
Check some of that stuff out & get back to us.
I agree it sounds mechanical, most likely a bad battery.
I confronted similar behavior over the weekend and a testing with a new battery allowed me to point a finger at an older, aftermarket battery as causing the shutdowns.
Sorry for the delay in the reply - real life got in the way.
I thought it was also mechanical but the shut downs are MUCH less frequent in Miktouch than on ICS roms so I thought it may have to do partially with the software.
I'm S-off, used the revolutionary method years ago. Never issued the "fastboot oem lock" command and I've never done anything related to fastboot. The stock image was in the root of the sd card.
When the phone does shut down it doesn't matter if take out the battery or do anything else, I can't get the phone to start back up until 20 mins later or so. The phone will certainly shut down if I use the camera or use youtube so if there is a way I can grab a log or something that could help let me know
I've had very similar issues, since installing a CM 10 alpha, and now on 10.1. The first couple weeks when I first rooted/flashed CM 10 were fine, but then it started rebooting one day, and never has stopped. Stock battery, no reboots prior to that, S-On, flashed the boot.img for each rom, and it's doing this with both CM 10 and CM 10.1. Does that also sound like battery, since it's the stock battery which has always worked fine? Also, it seems heat/intensity related - if I'm playing a game, using GPS, or talking a long time, that's when it tends to happen, and then it tends to happen right at/near the lock screen for a while after that until it's cooled down (perhaps that screams battery, but since it always restarts fine/has power I would have guessed it had to do with the processor or kernel). Thanks in advance for any advice!
Could be the battery...
I agree with the other posters. I had the experience of lots of random reboots a while back when I was working my way through sverhagen's 9.1r3+ ROMs. But, it just turned out that my stock battery had given up the ghost. Swapping to one of the gold batteries fixed the problem. I tried the stock battery in the interim for a brief stint and switched back to the gold, as the stock battery still caused random reboots. So maybe its time for a battery refresher
Faizt20 said:
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down....
Click to expand...
Click to collapse
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
presin16 said:
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
Click to expand...
Click to collapse
Yeah....the little suckers are on a power trip I think.
i've been having some shut down issues for a while, on different ROMs so I don't think it's that. whenever i'm using it i don't have any issues (unless it's a known ROM thing, that's separate). even during the day when i'm not using it, it hasn't shut down or anything. the issue is that a lot of times when i wake up, i find that the phone has been shut down. i charge it overnight. so, my best guess is that i should stop doing that, maybe the battery is bad, it can't handle that for that long?
idk any ideas would be helpful. i'm considering buying a gold battery anyway
Did you try the new Battery ?
I was have random shutdown and lockup problems. The phone would lock with a blank screen and I'd have to pull the battery to get it back.
Am running SilverL's CM 10.1. I might be a coincidence, but I backed off on the aggressiveness of the CPU settings (in the performance menu) and the problem went away.
I'm currently running a min/max = 128/1242.
I'm trying not to post a new thread so I'll post my very similar problem.
I got this phone about a year ago. I put Miktouch on it and was experiencing random shut downs all the time. I believe I posted on here and I can't remember the responses. As the mytouch q kinda sucks and I want a solid phone. I gave it another attempt this time with CM 9.1.0. When I used the camera once it shut down and restarted I think. Then I got a solid few days before it started going wanky again. Today alone I've had like 5 restarts. From what I've searched around it seems the problem here is the battery? This is stock battery and I got the phone used off ebay. I think I used stock rom like a week before rooting and putting Miktouch on it.
edit: For some odd reason my background also changed. Charged the phone backup. It turned off again.
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
WeekendsR2Short said:
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
Click to expand...
Click to collapse
I know. I'm talking about two different phones in the same post. I bought this phone (Mytouch 4g Slide) last summer but shortly started having problems. As I didn't want to deal with it I went back to my slowly dying touchscreen on my G2. When that finally died (touchscreen) I just bought a mytouch q as I wanted a phone that worked. This was my first new phone in a long time.
I am NOT trying to install any roms for the MyTouch Q on the MT4GS or the other way around.
S-OFF should be off on the 4G slide. Pretty sure my mytouch Q is still rooted though. It sucked at running CM 9
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
WeekendsR2Short said:
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
Click to expand...
Click to collapse
Yeah, from what I read it could be a battery problem. Going to go with this Anker battery as its the only reliable battery I can find that doesn't cost an arm and a leg.
Anker Battery
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
demkantor said:
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a theory of whats causing it. If I extensively use the phone the battery warms up which gets to the point it shuts down. Thus if the battery is still too warm and I turn the phone on then it will just keep shutting down. Of course I can't do this until I'm home for the day as I'm out and about this weekend.
edit:
I used the Revolutionary way to turn s-off which is permanent.
I get random shut downs constantly. Usually atleast 3-4 times a day. It's pretty nerve racking. I honestly don't think it's the battery, I've experienced this issue on three different batteries and it happened on all of them. It's not ROM related either as I've tried probably 15 different ROMs (stock based, ICS, JB) and they all have this issue.
My buddy who has a Sensation also has this issue on his phone. Maybe it's a problem for that phone too since they are pretty similar?
We updated the phone to 4.4.3 her phone is a plain vainilla N5, locked and unrooted. when it finished, the phone restarted and it was like we turn on the phone for the first time. the welcome and initial setup screen appeared. Since I sideloaded mine(mine is working fine). I didnt know if this was normal or not.
After the phone started. Two little notification icons appeared on the top left of the screen which I have never seen before. I tried to take a screenshot, but there was an error telling me I couldnt take a screenshot
http://imgur.com/3psmPCi [1]
One of the icons says there's no much space left. So I look at the storage screen and now the phone only has 128Mb of total space available
http://imgur.com/ewJDeOA [2]
everything is missing, photos, apps, contacts, everything. I tried to do a factory reset, but the final button is not working. it doenst do anything.
I tried to start the recovery through the bootloader and I get the sick android screen.
http://i.imgur.com/AwEo5tk [3]
I dont know what to do. I dont know if should flash a stock image or something. But I dont know what's the deal with the flash drive total space.
Any else has run into this? Any ideas?
EDIT:
I tried unlocking the bootloader and installing a custom recovery. No luck. After rebooting to into the custom recovery. The phone locks the bootloader again and there's no custom recovery anymore.
Also, everytime I turn off and on the phone. The initial setup screen comes up every time.
The device locks the bootloader again after unlocking it? Sounds like the eMMC chip is busted.
Try to flash a factory image, if that doesn't work you are screwed
vin4yak said:
The device locks the bootloader again after unlocking it? Sounds like the eMMC chip is busted.
Click to expand...
Click to collapse
Is that replaceable? How did that happen?
Sent from my Nexus 5 using Tapatalk
elgranchuy said:
Is that replaceable? How did that happen?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You could try unlocking the bootloader again and see if it unlocks?? If not, the motherboard needs to be swapped. No idea how it happened, it's a random hardware failure very common with the Nexus 5. I've seen lots of devices with a busted eMMC chip. It's strange that you can still boot into your OS. May be the chip is partly damaged. Anyways, it needs to be replaced.
vin4yak said:
You could try unlocking the bootloader again and see if it unlocks?? If not, the motherboard needs to be swapped. No idea how it happened, it's a random hardware failure very common with the Nexus 5. I've seen lots of devices with a busted eMMC chip. It's strange that you can still boot into your OS. May be the chip is partly damaged. Anyways, it needs to be replaced.
Click to expand...
Click to collapse
What are my options then? A couple of months ago we had to replace the screen through a third-party. Should I do an RMA with Google/LG. How do I explain this situation to them? Would they notice that I replace the screen?
elgranchuy said:
What are my options then? A couple of months ago we had to replace the screen through a third-party. Should I do an RMA with Google/LG. How do I explain this situation to them? Would they notice that I replace the screen?
Click to expand...
Click to collapse
If you've bought the device from google play store, then contact google and explain them your situation. I'm not sure whether they will notice it or not. If they open up the device, they might notice it.
If you've bought it elsewhere then visit a LG Service center and let them take a look at the device.
As per warranty guidelines, any 3rd Party repairs performed on the device voids the warranty. So, there's a strong possibility that you/your gf might need to pay up.
Hey!
So, today my gf charged her OPO for 30 min, turned off. When she tried to turn it back on afterwards, the phone went into bootloader. She tried to restart it, but everytime it only restarts to bootlader. The first time there was also a picture of the android figure, but with an error message or sth like that, but she cannot remember exactly.
The phone is not rooted, stock firmware and stock bootloader, latest update of the official CM firmware (not oxygen OS).
We tried wiping cache only. No difference. We tried wiping all data. No difference.
Any other ideas?
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
zaoms said:
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
Click to expand...
Click to collapse
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Zigurat said:
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Click to expand...
Click to collapse
Wow good thinking back there. Most of users(including me) thinks software issue but you found it nice amd easily. Happy to know it is ok now.