FIXED
Okay, I tested only nAa v10 and v11 kernels in combination with miniCM v2.1.8/2.1.9(currently) and sometimes when I restart my phone, the phone goes off, then on, and Purple LED starts, and screen is black (only backlight works) then I have to hard restart it (battery in-out), is this a hardware or kernel problem, and how can I fix it .I didn't have this problem before/after flashing other kernel's.
NOT FIXED
#2 - Camera problem
I've also got one more problem, since I've bought my phone, and now I mean all combinations of rom's 2.1, 2.2, 2.3, stock or custom, or even kernels, I've got a problem when I long press camera button, phone just freezes and restarts, this happens in 3 of 5 times. Once more, sorry for offtopic. Thanx in advance.
If you look at nAa kernel thread you'll see that the reboot loops occurs with everybody and it has not way to "fix". Its a bug that you have to live with it.
Tnx anyway..
Does someone now about my camera problem?
Related
Guys,
I have this exact problem with my Note; http://www.youtube.com/watch?v=dOy4pQOgvkM. The Note works as normal, but when the display times out, it wont wake up and all i get is the red, green pixels slowing turning into a white screen. I have to reboot by taking the battery out or Vol down+home+power to restart.
I've rooted the phone, unrooted, factory reset - still the same.
Any ideas (before i send it in for repair)??
You may have downgraded your device to get rooted, N so it may have older kernel.
Just update kernel N this will be solved.
That's so-called pixel salad, mentioned many times in Franco's kernel thread. It appears that many users (not all though) managed to get rid of it after flashing the latest franco test kernel.
You'll have to root your Note again and flash the kernel through CWM Recovery though, if you want to give it a shot that is.
You can download the kernel here:
http://forum.xda-developers.com/showpost.php?p=23850636&postcount=1691
phew!
Thanks guys, all sorted - couple of hours of reading threads, i've updated the kernel with Franco's, all back to normal!
Hello, im running on latest Nova HD.
My problem is that my phone shutdown by itself.
This is not SOD - i can turn it back on just by pressing the power button.
Any advices about this? Thank yoU!
Hello, just to add a question. At the moment I have Nova_HD 1.0.3 and the phone freezes and reboots when connected through USB. Anyone else has this problem? Usb-debug deactivated.
Thanks
EDIT: Just reinstalled with full wipe. working OK now..
Shutdown isssue too
Hello!
My biggest problem with O2x is signal loss when on GSM / WCDMA (auto mode) with official GB roms (v20l, v20q).
I routed my phone and installed Nova HD Rebuild 1.0.3. With Nova Kernel I had no wi-fi, with HP 2x and Harsh kernel, my phone is shutting down by itself, after a phone call, the screen remains off (black) and I have to remove the battery to use it again. With all the kernels I had huge battery drain (about 6-8 hours uptime with normal use). Always clean install, full wipe, dalvik cache, battery stats.
Now, I installed official, unrooted v20s Euro Open. I will test it and post my opinion about this rom.
martinesko36 said:
Hello, im running on latest Nova HD.
My problem is that my phone shutdown by itself.
This is not SOD - i can turn it back on just by pressing the power button.
Any advices about this? Thank yoU!
Click to expand...
Click to collapse
BeerFreek said:
Hello, just to add a question. At the moment I have Nova_HD 1.0.3 and the phone freezes and reboots when connected through USB. Anyone else has this problem? Usb-debug deactivated.
Thanks
EDIT: Just reinstalled with full wipe. working OK now..
Click to expand...
Click to collapse
You can try to put higher minimum frequency from 216 to 324 or flash latest Harsh kernel 3.0.34, but not before wiping cache and dalvik
I have noticed that the phone shuts down only when there's no radio signal for more than 5-10min. The phone keeps switching itself off unless I turn on air plane mode.
Ok, so i am on the miui.us rom by zackconsole and x8 master with the nAa-ics 2 kernel. I flashed the rom and the libhardware file and deleted some uneuseful apks. It worked fine for a couple of hours but then suddenly when I pressed the home button kinda like a red pictureframe appeared on the sides for about an half second and every time i pressed it it came up again and disappeared. I rebooted many times but it did not go away. I fullwiped and it worked but after a couple of hrs there it was again.
I know that the screen moves a little on certain freq on custom kernels but i reseted it to 600 Mhz and rebooted but it didnt work.
So what could it be? The kernel, the ROM? what should i do?
Plz help its so annoying.
I managed to take a screenshot:
settings -> developer options -> disable strict mode
Didn't work
try to flash the newest nAa ics kernel (v03)
ICS-03 kernel is recommended since its based on MiniCM9 3.0.2
I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??