Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...
He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.
Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...
As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.
Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.
Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!
Related
I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on. I pulled the batter out and then went to turn it back on, I would vibrate like it was going to start up and a few seconds it would go black and vibrate again. It did this over and over till I finaly tried a hard reset. I was able to get into the hard reset and it said that it compleated and I hit power up to boot. But then the screen got fuzzy and would not boot, so I pulled the battery again and now I can't get it to start at all! No power, nothing! Even with the power cord pluged in it doesn't do anything, not even light up showing that it's being charged!!
What should I do, or check?
Not knowing particulars I would double check the water intrusion labels and make sure they were both white still. Check your gold battery connectors and make sure those look good. Also check your charger and the USB plug to make sure that it is clean of debris and shiny.
Then I would charge the phone for 4 to 8 hours without attempting any boot ups just to make sure it was fully charged.
I have had 'wonky' issues with the phone being too low of a charge and not booting properly. Sorry I can't be of more help.
I will hook it up to a charge tonight and see if that does anything, but it was atleast at 60% eairlyer and as far as I know should be no reason that it should have discarged that quiclky. Also all the markers look just as they did out of the box. Thanks for the advice!
Your ROM might have gotten corrupted. Try a reflash by booting in bootloader mode.
How? It won't turn on?
wingman1487 said:
How? It won't turn on?
Click to expand...
Click to collapse
Try pulling out the battery (and no USB plugged in) then hold the volume down or up button (I don't remeber which) and hit the power button just once while holding the volume button and if you get to boot loader mode you can go from there. Otherwise I'm afraid you are out of luck.
So with no battery I can get to boot loader mode?
Anyways, in or out, nothing. How does my phone just brick itself? I didn't do anything to it!?
If you could do a hard reset, then you can get into bootloader. Just press and hold volume down and then soft reset. If you have to do, a hard reset first, then go into bootloader when the screen says to press volume up to boot up. Once in bootloader, either flash a rom of your sd card if you know how to or off the usb connection.
What radio do you have, and did you change radios recently? I'd recommend using what nrg says (1.14.25.05) with his rom.
I was able to do a hard reset and now nothing is happening. I cant get it to power up, can't get into boot loader, nothing. It is acting like it is bricked... but I haven't added new software, no new ROM... I just don't understand.
Just pull the battery and let it sit overnight. I've read that that can help.
Oh, yeah, what radio are you using? I ask because there was another poster with a similar problem on that rom. He was using a 1.12.xx.xx radio (I think .25.19), and it appeared to have issues with the included rilphone (1.14.25.05). If you haven't flashed a radio and are using a stock fuze radio, this could well be your problem.
Humm the radio was the most recnet one by HTC. The on that the Energy ROM flashes with stock (not the one he suggests, I never got to flashing that one onto the phone) I'll let it sit tongith and report back in the morning/afternoon.
wingman1487 said:
I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on..
Click to expand...
Click to collapse
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair
nolla said:
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair
Click to expand...
Click to collapse
Well, flash it back to stock and then have it repaired or replaced. You don't need the screen working on the phone to flash it.
To post an update, I pulled the battery and left it all night like that with no resolve. Right now I have my buddy (the one I bought the phone from) on the phone with cingular to see if there is anyway we can get them to replace the phone since it is only 2 months old or so.
Ok! Get an iPhone now
raydm said:
Ok! Get an iPhone now
Click to expand...
Click to collapse
HAHAHAHA Ya that is somthing that isn't going to happen.
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
I run any radio I like on my phone and I never got this issue. Sounds like a hardware issue and it just happened to match that the two persons flashed the same ROM without changing the radio to the recommended one because, frankly, I just flash any I want and I haven't gotten that problem yet (mind you I flash sometimes 5 times a day.)
ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
You're probably fine with that radio; you can always install the rilphone.dll for it.
This is the thread I was thinking of. Now that I re-read it, the OP didn't specify the rom, but since everyone is on NRG rom, I guess I just assumed that was what it was. Either way, the 1.12 radio seemed to not get along with the cooked in 1.14 rilphone. Or, it could've just been bad luck on the radio flash.
background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*
Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk
Did you try booting into recovery mode instead of odin?
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
if u can boot into cwm flash darkside
OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?
Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...
I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe
Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727
The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m
Can I just run this by you to see if there is anything you can add?
My wife’s phone started misbehaving recently it froze up and wouldn’t charge. On inspection I found it had had a little drink of water, only a very small splash but there was definitely some inside when I took the battery out to investigate. It was in her bag where a drink bottle spilled a little.
Anyway did all the usual stuff once I realised: stripped it out and put it in the airing cupboard overnight, still problems. With the remaining battery I managed to reload a clockwork backup I had on it and it seemed to start working, started charging and run for a while. It then froze. It seems the screen stops working but the vol and pwr buttons still function. Booting into recovery ALL functions work perfectly, I can run the tests (the lower screen buttons work) reload roms etc but as soon as I boot into the rom, mostly the screen refuses to work but sometimes it works for a minute or so (enough time to restore the user account after a factory reset). But after a while and always after the screen time out, nothing will work again, not even the power button. Needs a battery pull to allow it to run again.
Any ideas? I assume it is shagged. I was going to try a complete wipe and re install a new different rom. Any suggestions which one to try?
Thanks for any help.
Keith.
you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?
441Excelsior said:
you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?
Click to expand...
Click to collapse
No I am pretty sure it isn't fried. I know it is dodgy to pull the battery but since I recon the thing is buggered any way I have actually now done this dozens of times. The chip seems to be ok. How do I know for sure? I can mount and unmount the cache from within the revolutionary loader screen but it doesnt do anything or give any messages. Where would I see the error message?
I just loaded the new cm10 rom. It seems to work sort of ok running this though it did freeze once and the screen behaves funny. presses take a long time to register - like it is running really slowly and single taps usually respond as long pushed. I am going to try an old rom (3.5) with a full wipe and see if it is any better with this.
Thanks.
Also I had this error and also because of wather and the phone maked like yours. But....I put older recovery non touch clasic version of 4ext and after I recover a older backup and start working normal.... I think this you can do and don't cost nothing.
Sent from my HTC Desire S using Tapatalk 2
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys