I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.
Related
I have a problem with MIUI rom. Some days ago, my phone suddenly had FC, now, my phone run really slow and laggy... If I turn off the screen, my phone won't wake up, only four button in the bottom light up.
I wiped everything in CMW (system,data, and cache, also sd-card) but it doesn't work.
The fresh install had the same issues
I have this problem only with MIUI rom
any help
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
zandroid said:
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
Click to expand...
Click to collapse
i have tried from 1.8.5 to 1.9.2.
it's very weird
this guy has the same problem with me, maybe he can explain better than me
http://forums.miui.us/showthread.php?3740-Display-won-t-wake-from-sleep
Hey guys, I flashed 1.819 yesterday and everything was going great. The ROM ran smoothly and I was having no issues at all. When I woke up the next morning my display would not turn back on. Every time I tried to turn on the display the soft lights would light up but the display remained unresponsive. The phone still seemed functional as I could hear e-mail and sms notifications coming through.
When I rebooted my phone it was abnormally slow.. mounting the sd card and syncing seemed like it was taking forever and the launcher was very jittery.. if I let my display time out it would not come back on and I'd be forced to pull the battery and try again.
I performed a full wipe through clockwork recovery (everything, including wiping system,data, and cache in 'mounts and usb') and reinstalled 1.819. The fresh install had the same issues.. if I let my display time out I wouldn't be able to turn it back on. I thought I was having some wonky hardware issue but after flashing my previous sense rom and everything is working perfectly.. so I'm pretty much scratching my head here. My phone was kickass for one day and became allergic to MIUI overnight!
Click to expand...
Click to collapse
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
PacerguyDon said:
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
Click to expand...
Click to collapse
i have tried both
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
ttupa said:
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
Click to expand...
Click to collapse
immediately after the flash. I don't install any other apps
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
spiderj said:
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
Click to expand...
Click to collapse
Try different kernel
Sent from my Incredible 2 3D using XDA App
tenchu_712 said:
immediately after the flash. I don't install any other apps
Click to expand...
Click to collapse
tenchu, your signature says you are not English or American. Are you running the MIUI.us ROM on your incredible 2 in English - and not another language?
.....just a thought.
Hi,
So yesterday i was walking the dog listening to some music when my phone just died. I booted it back up again, listened some more and it died again. When this happened i was running version 1.2.0 of said mod, so i decided to try the latest.
Seems like i have this issue there aswell Everytime my phone goes into lock it shuts down. Anyone have an idea what can cause this? my phone is almost a year and a half.
Update: Removed my memorycard and no problems so far, will try to format it and let you know.
Update 2: Formatted SD-card, seems to be working again now.
Update 3: Nope, its back again. Any ideas?
Thanks to everyone for any help on this
Juji
Try installing the test version of 1.4 and do a full wipe before that.
You should also try and flash any other ROM (maybe even stock) to make sure it's a ROM issue and not some HW fault on your phone.
Do we have any chance to have a 2wcr kernel for this great ROM?
I have the same 1-2 times per day after calling with
Virtuous Quattro RC3
so maybe a bug in ICS ?
Have been running without any force shutdowns for over 24hours now, so it might have been temporary for me atleast.
I got no problems so far with ICS on DHD, flashing from 1.2.0 to 1.4.0 without full wipe. I think different phones get different issus with same ROM. Maybe the installed apps are a reason for that.
I had that bug, but I was running Gingerbread at the time. The problem worked itself out, around the same time I upgraded the SD card. That might be a cause, maybe re-seat the sd card? Might be loose or something along those lines.
I'm running 1.5.0 and mine keeps saying no network and keeps rebooting itself????
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.
Hi,
since a few weeks i've got a big problem, my phone freezes to the point where I have to hold the power button to restart it. this started happening when I was on Jellykat v6.7 but still persists after flashing stock rom.
Info:
Flashed latest bootloader
Problem persists on Jellykat and stock, with multiple and stock kernel.
Problem does not occur when running spotify in the background.
Right now I'm running stock rom (4.4.2 from sammy, flashed via odin) with stock kernel and latest bootloader.
When I restart it and check my battery stats I can see my wifi was still working when my phone did not respond, thus the device was on and I was recieving messages while the decive was not awake.
Weird thing is that it works properly when I let spotify play in the background, meaning it doesn't go into deep sleep (I think).:silly:
Right now my device works fine, but only because I have spotify playing the background 24/7 which isn't ideal in terms of battery life and such.
Any thoughts on it?
Thanks in advance!
Still no one? I guess i'll have to survive till I get the note 4 :silly:
Same here
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
silentkiller143 said:
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
Click to expand...
Click to collapse
It started on custom JellyKat ROM, weird thing is, yesterday it worked perfectly fine without spotify and today it's screwing me over again
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.