When a process becomes unresponsive I get, "unfortunately the process %1$s has stopped." The text & buttons will be squished (in Portrait). The %1$s will also appear in the Settings > App info pages. Force quitting a process will quit it but the system message will read "Just once." Any way I can fix this?
Secondly, Power Menu Reboot into Recover or Bootmenu only give me a regular reboot.
Any way fix this?
All began after flashing:
Quarx's CM10
CM10-20121018-NIGHTLY-mb526.zip
I'm on MB525 - Bayer
I tried re-flashing. Nothing different. Any suggestions would be appreciated.
--
While I'm here, has anyone got a PDroid patch for Quarx CM10? I've had no luck with Auto_Patcher (via Mac)
Related
I've been getting this recently with 3 GB roms and 2 kernels on E22 modem. It happens when I restore my apps+data using Titanium Backup and reboot. This is "user apps" only. I'm working on restoring in batches to troubleshoot, but there are way too many so I got a logcat as well.
Order of events:
Boot -> media scan -> delay of 60-120sec -> restart rom (does NOT show kernel or rom splash screens on restart)
------ loop
I can't seem to pinpoint the offending app. It's also possible that it may be too many of them, or too many on SD. It happens on battery power, on AC, and on USB with airplace mode on/off.
Any ideas how to solve this?
LOGCAT: http://quick99si.home.comcast.net/misc/logcat.txt
Oh, and the log was stopped as soon as I saw the screen turn off. There's definitely data in there from the subsequent restart.
Hi all,
I have to report a problem with 2nd Init installed and camera.
I Found that my camera showed a black screen instead of the preview but I could make pictures without problems, but no video.
After trying everything found on the web, the problem was still there. So I restored all my apps and data and I tried to uninstall 2ndinit....
The camera now is working!!!!
I can't even imagine the reason but seems that 2nd Init has some bugs on defy.
Anyone had this problem?
bye
Davide
The solution is simple, from bootmenu change boot method from bootmenu to normal. The black screen is due to messed up video driver.
Maybe I was not too clear... I'll try to explain better.
The problem at the camera IS DUE to defy 2ndInit not to video driver!
The only way I found to solve it is to remove 2ndInit. (tried 2 times)
I was just wondering about the connection between the problem and 2ndInit.
Thanks
Bye
pbjhon was right in the first place. The 2nd-init is actually causes the camera to stop working properly where you can not see any preview but taking picture is ok.
You need to set the boot menu(in 2nd-init) to normal booting instead of boot into 2nd-init. Installing 2nd-init in default will set the booting direct to 2nd-init menu which you must edit/change it yourself.
I have similar problem, happened just after install of bootmenu (0.6.1, no new ROM yet).
Please clarify - once I've selected the "Normal" boot option, to be the default one, - how could I enter bootmenu again ? - is this done by press on "volume-down" button, once the blue led is lit ?
simon45 said:
I have similar problem, happened just after install of bootmenu (0.6.1, no new ROM yet).
Please clarify - once I've selected the "Normal" boot option, to be the default one, - how could I enter bootmenu again ? - is this done by press on "volume-down" button, once the blue led is lit ?
Click to expand...
Click to collapse
Install latest bootmenu and CWM for better ROM management, http://forum.xda-developers.com/showthread.php?t=1356767.
Some custom roms will ask what kind of boot when you pressed reboot option, like CM7. You can disable/enable that option as well.
However in the ROM you use, if theres no option, then you can simply press Vol-down the moment blue led turns on.
For me, the no-camera issue was resolved by set the default boot, to "Normal".
I have also verified that I can re-select boot menu, using the volume-down press after blue Led lights up.
Thanks for the help.
I am running CM7.2 KANG ROM built by mrg666 on my NC. Sometimes I encountered that the NC stop responding and I have to press the power button key for an interval to force it off then reboot it again. I don't think that's SOD since I am not able to get it connected with USB ADB when it stops responding.
Is there anybody having a clue how does it happen or how to get the previous log to find out the root cause? Thanks.
Three things you can pull - logcat (useless if you have to reboot), kmesg, and dmesg.
Hi Everyone,
I just rooted my phone (and if your an Aussy you know what rooted means - basically it means that you have stuffed it). I was following the instructions on this page - Motorola Defy: Full Update Guide, and whilst doing so I made an error under the "Installing bootmenu & the ClockworkMod Recovery" section.
Now whilst I have the boot menu installed, none of the menu items within the boot menu actually work. Instead of seeing particular (desirable) activities on the phone I see messages along the lines of "Error in /system/bootmenu/script/xyz.sh" whenever I try any of the menu items. I have even selected the "[Uninstall Bootmenu]" option only to see the error "Error in /system/bootmenu/script/uninstall.sh"! Now I am really stuck as I cannot uninstall the boot menu and try again, and my phone simply won't boot to the ROM (CyanogenMod) that is installed.
Due to the fact that I cannot boot into the ROM / phone normally I am unable to run the ADB command from a prompt.
If anybody has any ideas on how I might be able to get around this stale mate they will be greatly appreciated.
Kind Regards,
David
Flash an sbf, root your phone, install the 2ndinit 2.3 apk(search with Google) and you shall have a working boot menu
Sent from my Nexus 7 using XDA Premium HD app
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom