My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Ruwin said:
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Click to expand...
Click to collapse
Strange... it's really hard way to resolve, but what about some logging on SDCARD? Problem is that it can be really huge file. And Murphy law... it definitely will not restart for many hours...
I just bought a class 6 sd card, i'm testing it, maybe it's the card that shuts down the phone... i'll post the result tomorrow.
Lol man , I have the V10B for romania . I can give it to you on messenger if you add me : zerobarat1 .
Cheers
I had void with gapps, gingerbread, kernel, a2sd, blink, tapps folders on sd. Then I flashed milk_os kernel. Everything was fine.
Then I created stage fright and hwacc folders for quadrant testing. Something happened my neocore score was only 9 fps (though quadrant was 1100). I deleted stage fright, hwacc and kernel folders. Phone was fine again. But was going to sleep of death after some time of non usage. Didn't reboot even from power button. Had to take put and reinsert battery.
So I created the kernel folder again and rebooted. Went into recovery again and applied milk_os kernel again and rebooted. Everything is fine now.
Something remotely similar happened to me a while ago. I found the phone turned off without any particular reason and it refused to power on until I removed and reinserted the battery. It had me worried, but fortunately this didn't happened again ever since.
My problem seems unsolved. I also found my phone dead two times again only in last 4 hours.
Guys any solution. I have void with a2sd enabled and with mik_os kernel 1.1
Did you have the same problem when you were on stock? It might be a physical fault rather than the rom. Also, I believe the latest void already have mik_os kernel 1.1? So there was no need to flash it again.
a2sd maybe? I read quite a lot of issues with that thing.
Miks kernel 1.1 has some scrolling bugs, flash 1.0 and maybe problems solved
I applied mik_os v 1.0. Now everything seems ok for last 16 hours. Will notice further.
Everything ok till now. May be it was something related to mik_ os 1.1.
With 1.0 problem seems to be fixed as of now.
Try dev kernel v3, it's enhanced version of mik's v1.0 kernel
Sorry to say, but this damn bug stroke again. I just found my phone dead, unwilling to reboot unless I took out the battery (which, by the way, was 94% full).
I'm using void #alpha with a2sd and mik_os kernel 1.0 and I don't have the sdcard unmount problem. I can't tell if this also happens on stock ROM since I don't intend to go back to stock ROM until LG rolls out the 2.3 version.
Waiting for some stock ROM user input, but my guess is that this is hardware related.
Any help?
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Hit the search button on phone and if search screen appears, type settings in it. If you are able to reach settings, you can do everything from there. Try playing with the search button on the phone.
If this does not help, you will have to do a factory reset. You can do a factory reset by the pressing the combo of home + vol down + power on buttons if you are on stock rom. If other rom, do via recovery.
winnie34 said:
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Click to expand...
Click to collapse
same here too .... (when the phone turn off the screen automatically...or auto suspend...is the same) i have the #echo and .... i have the random power off and... some times... it keeps on the boot loop when it supous to suspend... butn when i suspend the phone whit the power button ... the phone keeps working fine... i dont know what to do... XD
I got the class 6 SD and since then i had no problems with shutdown. Though at the time i'm writing, my O1 is at service. It seemed that the shutdowns are related to the sd, even if you don't get any unmount errors. My logs say that each time the phone shut down, it was trying to access a service from the sd memory, and, guess what, there was no sd! So it closed all the services.
could it be unmounting sd card?
After a long time of checking how to fix this, I, finally found it.
I had this error several times, and, I always tried to check where it was the error. I did a factory reset and, suddenly this error stopped. But I needed to know exactly by "doing what" this error appeared.
This error appears in one of this two:
- if you dissactivate the "rotation" in your phone.
- if you dissable bluetooth in your phone
One of those two. If I dissable this two, my phone, in about 1 hour, it suddenly shutdown. But inmmediatly if I enable this options, its stops to crash.
You can toogle this options with the "battery" widget in your phone.
I hope this will help you, as it helped me. Plz, tell all the ppl about, how to fix this.
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
rccr said:
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
Click to expand...
Click to collapse
Newbie too, and had the same problem, phone would boot into a low resolution mode (everything looked huge), followed by most applications and widgets crashing, I was lucky enough for the phone to forget the association with ADW Launcher and it allowed me to use the default home screen when launching it.
Now I'm in the process of repairing it using SEUS, need to charge up the phone before, is there's a way to fix this without having to lose everything? (Can't use the backup service)
rccr, try accessing safe mode, hold the menu key while it's booting.
Thanks!
Thanks! I have got to a post from xcyanogen forum, ways of recovering a 'killed device'. I was managed to flash back Sony Ericsson 2.1 using SEUS. Have installed back CyanogenMod6-v3.6, now everything working as before.
Help!!!!
Rccr can you please tell me the exact link?
You should never replace busybox on a custom rom or if ypy have xrec installed because they depend on their specific bysybox version!
Sent from my X10mini running on MiniCM 2.2.1 RC2 / aZuZu ZiG ZaG Alpha 0
After I restarted my Cell the boot animation keeps on replaying after the slight vibrate, same thing hapens for 10 mins then the mobile starts.
Its not normal
Can anyone help?
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
hirentherock555 said:
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
Click to expand...
Click to collapse
Found a partial solution after formatting the cell twice like a fool
Last night while playing Dangerous chambers 3D or somthing my cell got hanged.
Later it wouldnt restart or anything so had to pull out the battery.
After it started it went into loop mode.
I got worried
Formatted it once.
All ok later then again after some apps it went in loop mode.
Couldnt figure out which app was causing the prob.
Then today morning after some reasearch found out that:
In CM7 settings in settings menu> Tablet tweaks> disable lock screen> Tick
This is what i used to do to use an alternate lock screen.
After removing the check all is fine untill now.
Will update if anything happens next.
I also met this problem when trying to develop a CM7 ROM myself (from HPA CM7 BETA2). My problems are:
1. After building successfully, apps inside the output /system/app folder are bigger (in size, of course) than the original HPA ROM (ADWLauncher in HPA is 731.5K, and mine after building is 1M)
2. After flashing to DV, my phone hangs at the CM7 logo. It's OK to type "sudo adb devices" to see that my device is attached, but then any command other than that will receive "error: closed"
Guys, do you know what's the problem with my build?
I got some problem with this rom. My phone get white light when i open or install some app especially titanium backup though i have just installed it a moment ago. Then i try to replace battery icon my phone stuck in xperia logo. I have tried to install many time and it's the same. Plz help me!
''White light''
zombie064 said:
I got some problem with this rom. My phone get white light when i open or install some app especially titanium backup though i have just installed it a moment ago. Then i try to replace battery icon my phone stuck in xperia logo. I have tried to install many time and it's the same. Plz help me!
Click to expand...
Click to collapse
I had the same problem when I used X10S, unwanted reboots as WLOD (White Light Of Death). Typically, this occurs when you change the CPU frequency or an process/app is malfunctioning. I had that problem when I tried to open a large app - especially Settings.
Anyway, here's the solution: after flashing the ROM - flash over the latest Ferakernel (V3.6) http://forum.xda-developers.com/showpost.php?p=34222065&postcount=5378 After that, don't forget to install the libs and modules provided before rebooting... and clear cache and dalvik cache.
I hope this helps you. For me - it did the trick. :cyclops:
it's working! thank you
Hi, I have a strange problem with my Xerpia Z2..
After flashing a cyanogen mod to test it out.. it`s not possible for me to get a working generic Android system anymore.
The smartphone stuck in a caint of "bootloop" or, if it start android at last, it reboots after a short while automaticly.
The bootloop is like this:
Screen: Shows 10 sec. sony-logo -> than 2 sec. black screen -> than 5 sec. sony-logo -> than it starts from beginning..
The bootloop-lenght varied until it starts finally into android.. sometime it doesn`t come to that point, and it reboots for a very long period (until I get annoyed and shut it down)
I have trying the following things to solve that issue:
- Flashing several stockroms wirh flashtool (D6503_17.1.2.A.0.314_Generic DE.ftf / D6503_23.0.1.A.0.167_Customized DE.ftf)
- trying to reset the hole phone with the xperia "emma" tool
- trying to reset the hole phone with the pc companion software
.. in my opinion, the problem could be find in the bootloader/recovery.. I don`t think it`s a hardware issue, because cyanogen mod is still runs without problems. Maybe some cyanogen remains are still leftover in the bootloader, that don`t work with generic android versions.. that`s what I can imagine. (but i`m not an expert
I don`t get why flashing the phone doesn`t solve the issue., it almost seems that the flash process don`t touch the bootloader, to overwrite it with stock parameters (?) or does not fix that area which is responsible for that issue..
Phone status at this time:
Not root - not unlocked - no backup of TA - DRM Keys (The guy that I bought that phone from, saddly doesn`t do a backup /
Before you flash the stock rom, are you clearing the Dalvik cache?
Whenever I've been through instructions on flashing roms, that always seems to be a step, but I didn't see you mention doing that before flashing.
Lagamorph said:
Before you flash the stock rom, are you clearing the Dalvik cache?
Whenever I've been through instructions on flashing roms, that always seems to be a step, but I didn't see you mention doing that before flashing.
Click to expand...
Click to collapse
Hi, I did that.. the 3 checkboxes in Flashtool are always enabled (Wipe: Cache, APPLOG. Data)