Hello there everybody. I'm kind of new to modding my T-mobile G2.
I tried running the Pyromod 1.6 on my phone and I followed directions to the T. At first startup everything was running normally. On my previous rom (Villianrom) I used titanium backup to back up all my apps and some data. I was reinstalling my old apps using titanium and then I ran into some issues.
First, I kept getting force close issues with the android media process. I was also unable to download or update any of my apps via the android market.
Second, whenever I tried setting up a widget, I get even more force close issues with the media process and a couple others.
In an attempt to remedy this, I rebooted my phone and now its stuck on the startup of the mod. ( the blue hexagon beehive like flashing and graphic)
I'm not too sure if this is a brick or not and I'm currently just letting it run to see if time is what it needs to start up.
Any help or suggestions would be a great help and appreciated. =)
When it ran the first time it was a really cool mod so i'd like to keep it if possible.
Thanks!
if you can get into recovery i think you are ok, try to wipe cache/dalvik and run fix permissions
You're better off just wiping the phone, reflashing the ROM (and don't flash any other kernels on top of it), and then just select "restore apps with data" from Titanium's batch window.
Related
Hi, everyone; adding to the flood of questions...
I've been having some issues after a reboot lately:
- a couple of my apps will disappear. Namely Line Runner and the Merriam Webster Dictionary. I did some searching on this earlier and people who have had similar problems said it was due to the apps being installed on SD. I moved them to the phone, which seemed to solve the problem, but:
- rebooting also seems to make me lose my latest Google Search and Maps updates. The market will prompt me to update these. These apps are already on the phone, so no clue how to fix that one. But the most annoying thing is:
- after reboot, several of my game apps will force close when I try to open them. It seems like it's the more processor-intense ones: Pew Pew, Osmos, Anomaly, World of Goo. I thought maybe it was because of the undervolting/underclocking settings I have (from GideonX), but the apps work fine (running quite smoothly) after I install them, as long as I don't reboot. As soon as I reboot, if I try to open them again I get FC. If I uninstall then reinstall, they run fine again.
Any ideas? I'm running Juggernaut 4.1 with faux's 009u kernel and, as I said above, Gideon's script. I tried one reboot back to faux's stock clock/voltage settings, but I still got FCs on the apps. Granted, I didn't try it again or give it time to settle in or anything.
Any thoughts, folks? Thanks!
fix permissions? fresh wipe and install? clear cache? fiddle around
Ah, forgot to mention. Tried all of the above (fix permissions, clear cache, reflashed ROM, even recovered to my pre-custom ROM backup and reflashed from there).
I did some more testing on this, and I think I've narrowed down the problem. I flashed back to stock voltage/clock settings under faux's kernel, then reinstalled one of the apps I had issues with (Osmos). Upon reboot it still ran okay. So it seems I won't get force closes after reboot IF the app was installed under stock settings.
Does anyone know why undervolting and/or underclocking would cause apps to force close only after reboot?
EDIT:
Well, never mind. I did some more testing, and what I thought worked last time didn't work again. Must have just gotten lucky that time. Sigh.
Try wiping your phone with darksides super wipe and clean flash a rom. Check the md5 sums to make sure youre not installing a bad download
Sent from my SGH-T989 using Tapatalk
Oh, wow, didn't even know about the existence of that tool. Will definitely give that a try when I have some free time this weekend. Hopefully I can report back with positive news.
Thanks!
Don't want to count my chickens, but using super wipe seems to have done the trick so far! Using super wipe before flashing Jugg 5.0 seems to have gotten rid of my problem of FC apps.
Thanks again!
Hey guys,
I'm hoping someone can help me out. Lately, I've been experiencing a lot of FCing with my phone. It first started with Blazer 1.8 and seemed to carry over to FreeGS3's latest version even after a complete wipe. What happens is that, after the phone is in use for a while, when I try to open an app, the screen goes black, then FCs that app. Then any app I try to open will cause the same problem. No matter how many apps I try to open consecutively, I get an FC. I can only get my apps to open again if I click on Remove All in the Task Manager or reboot the phone. Then I'm good a little while until it happens again.
At first, I figured it was a ROM issue. I migrated over to FreeGS3 and I got the same exact thing happening. I figured it was perhaps something that carried over from restoring my apps with Titanium Backup. So I decided to clear everything again, (system, cache, dalvik) and start from scratch. No Titanium Backup, downloading each app at a time. Well, I downloaded some apps and started using my phone and BAMM! It happened again.
I tried everything, even fixing permissions in CWM and TWRP (I'm using TWRP now).
So I got Clark from FreeGS3 trying to help me out by sending him some Catlog of when the crashing starts. I'd post it here, but they're very long. One thing I can say, is that on this new clean install, the only Errors I'm getting in Catlog is MP-Decision and Sensors (accelHandler). Any idea what these are and how I can address these?
Please guys, help me out! I'd exchange the phone, but I don't believe it to be a hardware issue as I've downloaded some Stability and Stress Test apps on the PS and they all make it through alright.
Thanks in advance guys...
Appreciate the help fellas. =/
This is quite annoying
Every time I turn on my phone, all of the apps that start when my phone boots force close. I'm not able to send a text or even use the dialer. I'm able to browse my home screen, but when I try to run an app, either it will run for a bit and then force close, or it will close as soon as I open it. The battery I have is bad, which results in my phone turning off randomly, I know it's a bad battery because I've had this issue before and replacing the battery solved it.
Today I tried to use soundhound and while it was "listening" the phone decided to turn off. No surprise. However, when I rebooted it, none of my apps were able to run. I get the "Unfortunately, x has stopped working..." and am forced to close the app. I'm not able to do anything on my phone. I can still receive texts, I'm unable to respond to them. I should be getting a new battery in the mail any day now, and I'm hoping it will solve the issue.
I'm running cm9 beta 1. I've cleared the cache and the d-cache.
Could the battery be the cause of this? Any suggestions?
I'm gonna try to temp boot to EL29. Mobile ODIN doesn't work, am I able to use ODIN 1.85 on my computer instead? I would install the direct boot v3 file under the PDA option right?
EDIT: The apps seemed to have worked when under a temp boot of EL29. I'm gonna do a fresh install to see if that does the trick
I doubt its the battery. Maybe a corrupted install. Download files to pc if possible then xfer to phone. Verify md5 before flashing. You can get software from sourceforge if needed.
The fresh install did the trick. Still not sure how this happened, but whateva. I don't need a new phone
That's good sometimes you just get a bad flash or flash a mod that just messes things up. I have flashed things that worked perfectly for others and my phone got jacked. Its all part of the game. I keep a recent one click on my laptop just in case.
It sounds like when you installed your rom you forgot to wipe data/factory rest or when you restored app backups you installed data with system apps from a TWiz rom. When restoring backed up apps you can usually restore data for system apps from TWiz > TWiz or AOSP/CM > AOSP/CM as long as they are on the same build ie ICS > ICS or JB>JB etc. You can restore data for user apps safely regardless of rom they were backed up on. But the FC issue comes from incompatible system data it screws up the system process and causes apps to FC when it tries to load the data
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
hi all,
I have been running koodo v4 since I got my koodo s2x and would like to update it to v5. I am trying to follow the flash instruction down to the letter, i.e. using app2zip to back up all my user apps. However, I am having problems with app2zip: it simply doesn't finishes backing up! As an example, I just did the following:
1) rebooted S2X,
2) make sure nothing is running (checked using task manager,
3) run app2zip
4) checked all user apps (around 40+)
5) press the "GO!" button.
It has been about an hour and it is still "in process" backing up youtube.
anyone else has this problem running app2zip?
thanks in advance,
hi,
any help is very much appreciated!
You don't need to backup every single app, it's way too tedious on App2Zip. If you have Titanium backup, it can back up all user apps. Otherwise, uninstall all the junk you haven't used in a couple weeks. Then take a note of what apps you have left that aren't system apps. If any app requires data that you don't want to lose (ie; has complex settings you chose, or log-in, etc), back those apps up in App2Zip. Otherwise, you can just download the apps again from the google market when you flash your new ROM.
Reading your post again, if you are upgrading from v4 to v5, I'm fairly certain you can just dirty flash. Make a complete backup of your ROM in your recovery. Then, install the v5 zip, wipe cache/davlik cache and reboot. If you get errors, just restore the complete backup and flash it using the method in the above paragraph.
Yes, I know there are other threads out there from people having this same message. But I read through several of them, and they have having different issues.
The facts:
Samsung Galaxy Nexus, running ParanoidAndroid 2.99 beta6 (JB 4.2.1)
I had forgotten to re-flash the gapps after updating to the beta6, so I just tried flashing the newest gapps using GooManager (comes with PA I believe...)
Anyway, that was a bad idea apparently. Using GooManager. Now, whenever I boot up, I get that error in the title, and when I hit OK, I get the constant message "Setup Wizard has stopped working." I can't access my home screen, it's just black, and I've tried doing a factory reset, then reinstalling the ROM and gapps using TeamWin Recovery (what I normally use).
I am currently in the process of wiping my phone COMPLETELY, and then installing the system and such, hopefully fixing it. Just makes me sad that I didn't have a very recent backup =(
Assuming that doesn't work, does anyone have tips for me? Or an idea of what I SHOULD have done FIRST, after the problem occurred?
Harmonizeddeath said:
Yes, I know there are other threads out there from people having this same message. But I read through several of them, and they have having different issues.
The facts:
Samsung Galaxy Nexus, running ParanoidAndroid 2.99 beta6 (JB 4.2.1)
I had forgotten to re-flash the gapps after updating to the beta6, so I just tried flashing the newest gapps using GooManager (comes with PA I believe...)
Anyway, that was a bad idea apparently. Using GooManager. Now, whenever I boot up, I get that error in the title, and when I hit OK, I get the constant message "Setup Wizard has stopped working." I can't access my home screen, it's just black, and I've tried doing a factory reset, then reinstalling the ROM and gapps using TeamWin Recovery (what I normally use).
I am currently in the process of wiping my phone COMPLETELY, and then installing the system and such, hopefully fixing it. Just makes me sad that I didn't have a very recent backup =(
Assuming that doesn't work, does anyone have tips for me? Or an idea of what I SHOULD have done FIRST, after the problem occurred?
Click to expand...
Click to collapse
Sound like drama I would go with your initial plan and start over again with a clean wipe. But before doing that have you tried fixing permissions to see if that helps?
could you tell us which gapps you are flashing? also do you use Titanium Backup to restore all your apps?
I wasn't really able to use my phone, when it was "broken". Couldn't access anything on the home screen (as there seemed to be no home screen at all) and the "Setup Wizard" pop-up just kept coming. So, I did not try fixing permissions.
Ummm... I was/am using the most recent gapps from goo.im I believe. I was linked to the gapps download from the PA thread (http://forum.xda-developers.com/showthread.php?t=1619582). 4.2-2012 11 27
Anyway, it all works now. It took a few tries. I used the Galaxy Nexus Toolkit to flash stock ROMs (tried stock 4.2, but it got stuck on the Google boot screen [not animation] every time, so I settled on 4.0.4) and later flash TWRP so I could flash PA 2.99beta6 again. I did it properly this time, and all works well.
Sorry to bother the forums with this thread.
Oh! And I have NOT been using Titanium Backup. I tried using it, before I upgraded to PA 2.99 (required a format to go from the previous version), but it wouldn't back up anything properly. I eventually settled on using the GNex Toolkit (which also failed for me, but it was a fault on my part).
So to get my apps back, I've been doing it manually by going to the play store and going one-by-one to get the apps that were synced to my account. Really sucks losing all of my data =/
go to /system/app folder using root browser, and look for apks with incorrect permissions. All apk inside that folder should have 644 permission (owner read write, group read, and other read)
Or you could alternatively fix permissions from recovery or using other apps
i had this on stock 4.0.4 when i first got my phone.. flashed 4.1 and it fixed the issue
OP - I use mybackup pro from the app store to backup all my data/apps and videos etc. Simply backup then go into your phones system folder go into rerware folder and find your backup folder and drag it to your pc. Simply update your phone then just drop mybackup pros apk file to your phone again ..install..then drag your backup folder back into its rerware folder...if it doesnt have a rerware folder..do a little backup of your phone in stock and then you should see that rerware folder...anyway thats just the way i do it..works blissfully for me everytime!