Sorry if this is a useless question but I have to ask. So my phone was working fine but then I installed the Faux 2.1.5 lv on my CM RC2. I followed all the steps before installing delete dalvik cache and cache and even restarting. Well it worked for a little while then it suddenly turned off. Now it wont respond to me pressing the power button. It also doesnt show the led lighting up while charging the phone. If theres a fix or suggestion please respond.
charlie5467 said:
Sorry if this is a useless question but I have to ask. So my phone was working fine but then I installed the Faux 2.1.5 lv on my CM RC2. I followed all the steps before installing delete dalvik cache and cache and even restarting. Well it worked for a little while then it suddenly turned off. Now it wont respond to me pressing the power button. It also doesnt show the led lighting up while charging the phone. If theres a fix or suggestion please respond.
Click to expand...
Click to collapse
Did you pull the battery then press the power button..
Yes I did. Do you think its bricked
Edit: I tried removing the battery right now again and for some reason it turned on. Any info and what i should do for it wont happen again. Thanks
Edit 2: WOW now my freakin wifi keeps saying error no matter what I do man am i getting frustrated
Try his stock voltage gingerbread kernel instead of the low voltage one
how about you just leave the Zinx Kernal?
i keep stock CM kernals and never have issues with them.
just enjoy CM7 how it comes out of the box.. haha or out of the .zip lol
Well I tried both of those kernals sv and the stock kernal of cm7 rc2 and TS still showed error after turning on wifi and Bluetooth doesn't even do anything when I try to turn it on. So I restored my nandroid backup of stock mytouch rom and it still has the same issues
make sure you start fresh.
WIPE EVERYTHING.
format wipe /system /data
i forgot what else is in there but wipe everything
and start from a fresh install.
Well I wiped everything including format boot and format system. Still same issues
Related
I was running CM7 7.02 from emmc with Dalingrin's 4/24/11 OC kernel, and was very happy with it. However, I got distracted by shiney... Rom manager gave me a pop up saying 7.03 was available, which it hadn't done in the past, so I figured, why not give it a shot?
I ran a full backup, installed the update, booted... and all my apps were gone. It was a fresh install instead of an install over my existing 7.02 like I would have gotten if I just booted from my CWM boot SD card and flashed. Well, crappy, but I have my backup, right? Still, might as well try the OC kernel and see how it runs real quick... oh, won't boot after the OC kernel. huh.
So I boot to recovery, and clear cache, and restore my backup.
Everything looks perfect. Back to my customized layouts... wait, where is my Honeycomb style bottom status bar? I'm back to the default look/feel. Ok, I can fix that... wait, why isn't my N button working? I've gone into ADW settings, selected several options for the "home button" functionality, rebooted, nothing works. I've got everything except a working N button. Why?
The only time it has worked is ONCE right after I installed a second home launcher, flashed 7.02 over 7.02, rebooted, and hit the button. It popped up and asked me which of the two launchers I wanted as default. After that, it hasn't responded.
Anyone have any idea what I did or what I can do to fix this? I'm fine if I have to format and start from scratch, I just would rather not since I'm stuck in an airport and waiting on a flight home, so I'd rather be reading/watching movies/playing music instead of tinkering... if it's something simple to fix, ya know?
That post just made me mental!
Sent from my Nexus S using XDA Premium App
I'm glad I could provide some amusement?
I ended up wiping data and system, installing 7.02, gapps, and 4/24/11, clearing cache and dalvik, then booting up and then refreshed my apps and data from Titanium. Everything worked great for a while and then the N button stopped again. No idea what happened. I've been working 16+ hour days for 7 days straight and can't think straight. On the up side, I was able to finish watching my movie on the flight home after my flight was delayed for 4 hours.
I need sleep. I also need to figure out why my button keeps dying. Works perfectly in CWM and to wake the device up, just not for it's intended purpose.
Had a similar problem with the N button not working with the 04/24 kernel. However it got working after a reboot...
One thing you could try is to use the 04/04 kernel instead. Might be a OC related issue.
Ok, this is a fun one...
I was up late last night (too late to be doing anything on my nook apparently) and I opened CWM to see if there was an update for it. I noticed it could check for updates to my ROM, so I found the new nightly (160) with it. I decided to install it to see if that would be an easier way then manually downloading and flashing. It cam up with options to wipe cache and such, and I did not realize until too late that the Data and Cache options were one in the same.
So I set it to do a backup, then wipe the data/cache, and dalvik cache. When it booted back up I had lost everything...obviously. So I rebooted into recovery, and restored my backup. Once finished, the screen went blank and did not come back on.
Now I get nothing, no response from the screen. Today I DID plug it into the usb on my work computer and it tried to install drivers so I think it may be on...
Anyone have any ideas?
Anybody?
I'm hopin it is on and that the battery will die...but I am not sure that will solve anything.
Any suggestions would be appreciated.
Go here and start again: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Make sure you use the latest version of CWR (3.2.0.1)
The problem is actually that I get no response from my screen. It does not turn on, flash like it's going to work, DO anything. That's what has me so worried
dna_d said:
The problem is actually that I get no response from my screen. It does not turn on, flash like it's going to work, DO anything. That's what has me so worried
Click to expand...
Click to collapse
It is fully charged and you get nothing with a bootable SD card installed? Have you tried this while still plugged in to the a/c current?
I do not know about being fully charged...but I HAVE tried it plugged into USB on my computer. Still nothing.
Ok, I got it on! Not sure if this was it but now it complained about low battery. I had previously plugged it in for a whole night and got nothin. I think I will use your previous link to just wipe it all and start from scratch.
-------------
Edit: I am back up and running, thanks for your advice!
After i installed the cyanogen mod my LED is permanently on, i tried also to reboot the phone, but nothing, it lasts on... how should i solve this problem? sorry for eventual errors but i'm new... ah the led is yellow
Re-download, do a factory reset, wipe system, for the hell of it wipe cache. Don't forget to back up your apps first. Flash. Report.
Settings - system - battery light
I should point out that I don't use CM. Haha. :thumbup:
Resolved
Ok thanx i solved it the battery light tanks for swift response
hi
ive changed my phone in developers options from delvik to ART and now if I turn it on it sats"upgrading android" does "optimization for few min and then touchwiz crashes and the whole UI dosent go on...therefor I cant reach the menu to undo the change...safe mode dosent come up niether...I have no idea whats wrong,,,
the device is unrooted with everything fresh new and no 3rd party apps(only from the playstore)...
help!!!!
liavo555 said:
hi
ive changed my phone in developers options from delvik to ART and now if I turn it on it sats"upgrading android" does "optimization for few min and then touchwiz crashes and the whole UI dosent go on...therefor I cant reach the menu to undo the change...safe mode dosent come up niether...I have no idea whats wrong,,,
the device is unrooted with everything fresh new and no 3rd party apps(only from the playstore)...
help!!!!
Click to expand...
Click to collapse
Have you tried rebooting the phone? Or wiped cache in recovery. Dalvik is imo still more stable and faster then ART atm.
gee2012 said:
Have you tried rebooting the phone? Or wiped cache in recovery. Dalvik is imo still more stable and faster then ART atm.
Click to expand...
Click to collapse
I have tried rebooting and safe mode...
then I wanted to try factory reset but excidently got into download mod insted...I tool the chance of a brick and took the battery out while in download mode(since I didnt have files to burn via odin) and the phone just turned on using delvik and didnt show any problem...so the issue is solved,,,I have no idea how and why but it is...
liavo555 said:
I have tried rebooting and safe mode...
then I wanted to try factory reset but excidently got into download mod insted...I tool the chance of a brick and took the battery out while in download mode(since I didnt have files to burn via odin) and the phone just turned on using delvik and didnt show any problem...so the issue is solved,,,I have no idea how and why but it is...
Click to expand...
Click to collapse
I had ill effects when switching myself, found that best way to test it was to switch it to ART right after a hard reset or flashing stock via odin. Im sure just wiping cache and dalvik would have fixed it, but i was returning the phone for USB port issues anyhow so i flashed back to stock. not sure if clearing the android files on the internal storage or the cache/dalvik being wiped fixed it, but it ran find after that with no FC's etc. As stated though, i havent really noticed much if any improvement. Still too soon in its infancy to probably see much from it yet lol.
Good luck!
Hi guys
i have a custom rom, nougat 7.1 installed and its been working fine. last night i installed an aftermarket battery replacement as the other wasnt holding a charge. after turning on by simply pressing the power switch it went straight to twrp recovery and kept doing so. this morning i cleared the cache and data to start again which was a bit of hassle and it then booted fine. however, i just restarted again and its in the same loop.
i have checked for any obvious obstruction under the rear case that could be pressing against the volume keys but there isnt anything.
any ideas?
cheers
Did you try to reflash everything, e.g. also the ROM?
AndDiSa said:
Did you try to reflash everything, e.g. also the ROM?
Click to expand...
Click to collapse
i didnt really want to do that unless i really had to. as i say, before the battery swap it was fine
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
AndDiSa said:
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
Click to expand...
Click to collapse
well, i just went to restart and was going to reinstall but it booted properly. i then did a restart and again it booted fine. i dont get it.