I'm running AOKPlay and I want to supercharge.
So I ran the script Zeppelinrox gave out for ics devices, then found the patch for my build's services jar. I flashed the zip and after an hour or so, it booted up to the lock screen. I unlocked and got force closes for com.android.phone. I tapped OK but they would keep coming. So I restored my nandroid. So what am I doing wrong? Or what else should I do to supercharge?
EDIT: I flashed Aokplay RC3 and FXP125. the new scripts and starter kit make it much easier to install. However at first it wouldn't boot up, so I cleaned caches through cwm. Then it booted up and I got com.android.phone force closes repeatedly. The instructions say fix emissions through the script to handle this problem. But how on earth am I going to get into Smanager and run the script if I can't even unlock my phone because the force closes keep coming every second?
Related
has anyone else run into this prob? i am running cm6 rc3 and everytime i use pandora it will run for awhile and then just lock up. black screen no button response nothing and i have to pull the battery. i already did a search in here but didnt see any thing so thought id just ask
Try to uninstall the app and then install it again. If that doesen't work go into rom manager and select the option "Fix Permissions", after it prompts you to reboot the phone, reboot the phone and use the app again. Please keep in mind that CM6 RC3 is not the final version of the rom and some bugs still need to be worked out.
I've been following the CM7 nightly builds on my Incredible with no issues at all, I love it.
The problem I've been having is my girlfriend has an incredible as well and wanted to try out CM7. Rooted her phone no problem, installed the free copy of ROM manager (I have the paid, was wondering if maybe thats where the issue was coming into play) and dropped the latest nightly onto her SD Card.
When I install the ROM manually through recovery (wiped both dalvik and cache first) the ROM gets to the CM7 logo and then just sticks there, looping the logo over and over.
I restore the backup of sense, then install the ROM via Rom Manager's "Install ROM from SD Card" option, choose to wipe data and cache and it installs and boots no problem..or so it seems at first.
Even after repeated attempts at installing there are a lot of random issues that I never ran into at all. Every time she'll have a few contacts missing, and the bigger issue - she can't launch Facebook or any apps that have Facebook (Tweetdeck etc) they just force close instantly. Many other apps seem to just force close at random as well.
I installed CM6.1 just to see if it had any similar issues but it went smooth. I've run out of ideas so any suggestions would be appreciated.
Once it boots up, go into rom manager and fix permissions.
Corallis said:
I've been following the CM7 nightly builds on my Incredible with no issues at all, I love it.
The problem I've been having is my girlfriend has an incredible as well and wanted to try out CM7. Rooted her phone no problem, installed the free copy of ROM manager (I have the paid, was wondering if maybe thats where the issue was coming into play) and dropped the latest nightly onto her SD Card.
When I install the ROM manually through recovery (wiped both dalvik and cache first) the ROM gets to the CM7 logo and then just sticks there, looping the logo over and over.
I restore the backup of sense, then install the ROM via Rom Manager's "Install ROM from SD Card" option, choose to wipe data and cache and it installs and boots no problem..or so it seems at first.
Even after repeated attempts at installing there are a lot of random issues that I never ran into at all. Every time she'll have a few contacts missing, and the bigger issue - she can't launch Facebook or any apps that have Facebook (Tweetdeck etc) they just force close instantly. Many other apps seem to just force close at random as well.
I installed CM6.1 just to see if it had any similar issues but it went smooth. I've run out of ideas so any suggestions would be appreciated.
Click to expand...
Click to collapse
First, how long did was the boot animation going for CM7? My first install of CM7 took anywhere between 5-10 minutes of the logo looping (shocked the mess out of me cuz I never sat so long for a load). Maybe giving another nightly a try and waiting out the initial boot will resolve all issues. Personally, I flash rom's manually and have had little to no issues.
Second, maybe this was a specific nightly issue. I was running nightly #31 then switched to #36 and both ran perfectly. Try reflashing the rom and wiping everything again. Also, if your contacts ARE NOT stored under her gmail account this may be the reason you observe missing contact. All her contacts linked to her gmail should instantly reinstall each time you flash a rom/nightly/etc.
Did this help?
Hi friends..
I have Xperia pro, bootloader unlocked, rooted.
I had downloaded cm-10-20130217-NIGHTLY-iyokan.zip from the cyanogenmod site.
I followed all the instructions given in the xda developers for CM10.
Everything went fine, now when the phone starts after the cyanogenmod window, an error Unfortunately trebuchet has stopped will be keeep on comin and it won't let me go to home screen. It wont switchoff too.I will have remove the battery and shutdown.
I have installed custom rom first time, i had wiped the cache, formated system, then wipe delvik cache.(as i saw in youtube video)
Please somebody help how to fix this bootloop.
can i try with another version of CM10(may be stable one).
Unhappy [Q] CM10 nightly error :Unfortunately trebuchet has stopped error. Xperia PR
Hi Trebuchet is the launcher that goes with cm10 it seems you have a problem with this opening:crying:You can do a few things obviously try to re-install but also you can install a new launcher.
If you get a copy of any launcher/home apk place this in your flashtool folder which is located windows/flashtool/custom/apps then connect your phone to computer you can do this while switched on wait for flashtool to connect to your phone might take a minute or two when it say's root access allowed then go to install apk installer (Thats the one with a arrow pointing to the right) follow instruction's and flashtool will install a new home/launcher for you (reboot).Once installed you may keep getting error message on the faulty trebuchet just uninstall that with a root explorer in system apps.
Of course you can alway's try to install cm10 again
Please check out {Pro/Mini/MiniPro}[ROM][KERNEL][LINARO][DEV][TWRP] - CM10/FXP extended. i tested this CM10 rom and it is quite stable. In addition, they have fixed Trebuchet.apk issue (i think).
All,
I did not heed the warning but flashed the Turbo script even though I did not have the required recovery. I was using 4ext. I am on the newest PAC rom, S-Off and now have clockwork recovery 5.0. Every since the Turbo flash I get the persistent system UI error when I boot up. When I click OK it pops back up. I have flashed Chilly's super wipe and did a fresh install. I let Play store download all apps and everything was fine after a reboot. Then I started fixing all of my settings, All was fine until i did a reboot. I need help please.
**EDIT**
I am trying everything I can, and may have found the culprit.... please hold, still testing
**EDIT**
Fixed, I will notify chilly. If you disable "Quick Settings" on PAC 4.2.2 you will get stuck with this error. Just be patient and re-enable it.
So in my infinite drunken wisdom I decided to root my Galaxy last night...
(First time I root a cellphone, I have rooted Kindles before)
I found a video online, followed directions and it was a breeze..
Until I decided it was not "custom" enough and I install CyanogedMod
Google was missing so I downloaded, boot phone and install from boot
Some APS installed, some did not...
When I reboot my phone there is a flashing window, I can't really tell what it says because it goes away before I can read it
---
I know I messed up something...
There is no keyboard now...
Unfortunately, Android keyboard (AOSP) has stopped
Appears when I try to use keyboard
How can I make it work?
Please help
go into recovery mode clear data/cache/dalvic. now reflash your rom with the gapps package clear cache/dalvik reboot
Yeah...
Is not working
Phone starts with "updating apps" # of 83
After the updating is done, cyro starts again... and I get the "Keyboard" is not working message
OK, i already did the whole process a couple of times...
I keep getting the same error, the keyboard
I think the problem is with cyanogen, i don't know how to uninstall/replace it
OK, i got it working
I had to install a different version of gapps
gapps-jb-20130301-signed
that version did it for me
thanks for your help, though