Database Info

[DONE] Fix for "Preparing Sim Card..." Error for CleanROM

Hey,
Starting this thread up as a place to figure out the "Preparing Sim Card" problem.
Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:
1. Clearing all cache (fastboot/recovery)
2. Clearing all data/force stopping problem apps (people/dialer/messaging)
3. RUUing back to stock
4. Flashing a new radio
5. Removing/Changing SIM cards
6. Trying dialer trick:
.....a. Go to Dialer (if you can't access it, clear the data in it first)
.....b. dial *#*#4636#*#*
.....c. Turn off the radio
.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.
.....e. Run a ping test to make sure everything's alright.
7. Used TWRP to clear system/flash new ROM
8. Tried another ROM with GSM Patch
CURRENT STATUS: WORKING!!!! =D
The answer to all your problems issss........
Well, it's multi-step
1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)
2. Make sure to unlock your bootloader again
3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)
4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]
5. NOW install TWRP
6. Install CleanMOD 4.1
7. SUCCESS!!!
Also, thanks to tehdef, who also tried this method:
Here is what I did to break my phone.
I had the following MODS.
-AOKP 6.1
-CWM
Decided I wanted to test something on CleanROM 4.1
- Flashed CR4.1 in CWM
Got stuck in Boot Cycle and CWM would not load
1. Locked Bootloader
2. Installed 1.85 Evita RUU
3. Unlocked Bootloader
4. Installed TWRP
5. Flashed AOKP 6.1
At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.
6. Rebooted to Bootloader
7. Reset to Factory while in AOKP
8. TWRP Loads
9. Reboot to System
My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.
NOTE: YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)
Thanks goes out to...
Scott for his awesome ROMs and his life lessons
kleeman7 for toughing it out and helping me through the entire thing
tehdef for helping me test out several of my theories
shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)
and thanks goes out to anyone I forgot to mention. XD
Now, back to more ROM flashing

scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?

redpoint73 said:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
Click to expand...
Click to collapse
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.

Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.

tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?
if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed

tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".

I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync

elsupermang said:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
Click to expand...
Click to collapse
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!
redpoint73 said:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
Click to expand...
Click to collapse
Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it

Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.

tehdef said:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
Click to expand...
Click to collapse
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens

Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X

Well, hopefully that's it.
---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.

kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything

jojojohnson7410 said:
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
Click to expand...
Click to collapse
Try flashing AOKP + GApps to see if the People vs Contact system is diff?

tehdef said:
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
Click to expand...
Click to collapse
That's a good idea, maybe once Scott reads his thread he will have some input for everyone.
Sent from my HTC One X

Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
...actually, tehdef, did you ever unlock your bootloader with the one-click without HTCDEV unlock at any point in time? This might help me out cause this might also be the problem. Thanks!

jojojohnson7410 said:
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
Click to expand...
Click to collapse
Clearing contacts seems to work. My list is now populating.
Attempted to send text. Prepairing SIM Card returns.
---------- Post added at 02:23 PM ---------- Previous post was at 02:12 PM ----------
Unfortunately the Android.acore process has stopped when I tried to sync my Gmail contacts after clearing everything.

I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?

Something is corrupt.
I want to put AOKP back on the phone, because I honestly think it's Sense related.

natediddydude said:
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Click to expand...
Click to collapse
lol at the shaking your phone really hard XD
Anyways, I have a theory:
there are two ways we COULD possibly fix this:
1. obtain a rom that has root. Get root explorer or somehow get into /data/data/com.android.providers.contacts/databases/ and delete .db-journal if its in there. Do this in conjunction with clearing out the data of all the affected apps and their sister apps (i.e. Contacts, Contacts Storage, Contacts Sync) and force stopping all of them. Can't test this cause bootloader refuses to unlock atm)
2.lock the bootloader, RUU to 1.82 (NOTE: NOT 1.85!) and try to unlock using this: http://forum.xda-developers.com/showthread.php?t=1734558. REMEMBER take out your SIM card! but maybe this might help not 100% sure if this is what caused it for me, so it's best to consider it too. Can't test this right now because I am stuck without a BL unlock and i can't get root on this firmware
*EDIT* ahahhahahah i lied. no sim card needed, so why would it rely on mobile data? ahh im such a silly person alright here goes!
i'll let you know when i get out of my pickle, but it might be a while. That, or i might just get pissed off enough to just go to the store and look like an idiot cause i really do feel like one right now and I need to get the phone working T_T
Keep checking back!

[Q] I need help.

I'm not a dev, but it's obvious to me something is wrong.
I re-flashed the eaglesblood ICS rom using clockworkmod recovery v.5.8.1.3 (touch version)
everything seemed okay.
until i started putting apps back on my phone with app backup and restore.
I was getting "process syystem has stopped responding" all over the place.
Then the phone crashed.
it keeps booting, only three apps seem to be running that show themselves in the taskbar, Groove IP, GV SMS integration, and Battery Notifier (Big Text)
It sits there, one one of the home screens, LW animating slowly as it will.. then the phone reboots for no reason.
I installed 4 or 5 different logcat apps but i can't make heads or tails of them
and adb logcat > logcat.txt just spits out this :
/sbin/sh: exec: line 1: logcat: not found
dmesg spits out the log i'm attaching.
Can anyone help me? If i can save the log from one of the logcat apps, will that help?
I'd rather not have to reflash and re-install apps AGAIN.

Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app

Barracuda1101 said:
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.

Eve_brea said:
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Click to expand...
Click to collapse
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..

Eve_brea said:
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Click to expand...
Click to collapse
*grumble* damn sun-downer phone. SO all night it was crashing.. So i finally got irritated when i went to bed, yanked the battery out and plopped it on my night-stand by my fan.
This morning i put the battery in, turn it on, and it seems stable.
What the heck?!

logs.
So... between all the log apps i've played with i have a bunch of logs.. if anyone could look them over and tell me if they see a problem, i'd appreciate it.

Re-download Rom+Gapps
Place on SD card
Re-nvflash cwm recovery 5.0.2.0
Wipe data/cache/davlk/battstats/format system
Install rom+gapps
Wipe cache/davlk/battstats
Fix permissions
Reboot
Using touch is sometimes buggy, 5.0.2.0 is most stable. Restoring apps/data is sometimes a messes things up.
Sent from my LG-P999 using xda app-developers app

[Q] BlackBean (BAKED) ROM - apps stopping

I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.

Did you full wipe before installing the rom? That means factory reset/data wipe.

polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?

volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.

volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S

anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?

volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app

Seriously at a loss for what has been happening with my phone.

Ive been having some issues pop up with my phone in the last few weeks. Sorry but be prepared for a lengthy post haha.
It all started in Dec with the OTA of JB. After than my Maps/Nav constantly force close. I am not the only one with this issue because looking at recent reviews of Maps in the Play store, a lot of GS3 users are experiencing it too.
I made this thread: http://forum.xda-developers.com/showthread.php?t=2115108 to try and see if there was a fix. Never solved the problem.
My friend was running the latest AOKP Milestone ROM and said his Maps/Nav worked fine. So I rooted, bootloader, recovery and flashed AOKP Milestone. Well Maps/Nav still didnt work. Found out my friend never installed the official OTA to JB and went from ICS to AOKP. So it only lead me further to believe that it was something with the update.
Figured I would wait it out till there was a fix, until I started having another issue. I use Handcent as my primary SMS app. All of the sudden one day my notification ringtone stops working. Was working fine then poof doesnt work. Tried redoing all the settings and got nothing. Uninstalled and reinstalled nothing. Cleared cache, uninstall/reinstall nothing.
So now with this problem persisting for a few days I got sick of it. Thought I should be able to flash an MD5 thru Odin back to ICS, get Maps/Nav working (along with txt tones) and then flash to AOKP. First I flashed I535VRALF2 and Maps/Nav worked fine, flashed AOKP and didnt work. So today I flashed I535VRALG1 and again Maps/Nav/Txt worked fine. Flashed back to AOKP and Maps/Nav didnt work, BUT txt tones did (for a while). Driving from home to work (15mins) somehow my txt tones stopped working again!
Between each flash I would factory reset/wipe cache/dav data ect. Not sure why these problems are being so persistent. Even on the last time back to ICS, I wiped everything in CWM and booted the phone AND did a factory reset from within the phone settings.
Anyone have any ideas? Did accepting the JB OTA just perma F me on Maps/Nav?

No ideas?

I don't run aokp but found this in the faq on rootz: "Fix permissions in CWMR.Uninstall maps updates/clear cache and data."
No idea if it will help but it won't hurt to try.
Sent from my SCH-I535 using xda app-developers app

Ya I tried that already and it didnt work
And Ive also tried running older versions of Maps as well with no results

Try doing a superwipe. Completely erases internal memory. I know some roms have the option, specifically synergy to my knowledge. It is also available as a zip. Just make sure everything on internal you want to save it backed up to external or a computer. A fresh wipe can do wonders.
Sent from my SCH-I535 using xda app-developers app

NZitney said:
Try doing a superwipe. Completely erases internal memory. I know some roms have the option, specifically synergy to my knowledge. It is also available as a zip. Just make sure everything on internal you want to save it backed up to external or a computer. A fresh wipe can do wonders.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did (I think haha). I installed a fresh MD5 thru Odin, then once my phone booted, I used the internal factory reset option to completely wipe the internal storage. Or is that not the same thing?

http://forum.xda-developers.com/showthread.php?t=2121347
Try running the mega wipe zip with the Rom on external sd. If you are restoring
Apps, do so without data first to see if everything works.
Sent from my SCH-I535 using xda app-developers app

NZitney said:
http://forum.xda-developers.com/showthread.php?t=2121347
Try running the mega wipe zip with the Rom on external sd. If you are restoring
Apps, do so without data first to see if everything works.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Will it work on the GS3? That thread is for the Note2
And im running the latest touch CWM and that thread is a bit confusing, it says:
Requirements: You need to have
1. TWRP Recovery installed
Quote:
How to use:
Just copy the required zip to your External SDcard and reboot into CWM recovery. Install the zip and you are good to go!
Click to expand...
Click to collapse
It says you have to have TWRP recovery but then says boot into CWM, so not sure what to think.

any more ideas?

Anyone else?

[Q] Constant app lock ups - even after reinstalling

Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.

Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.

Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks

Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.

ok i'll try installing beans again and using fix permissions afterwards.
Thanks

still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?

Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.

Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app

How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.

SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?

Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.

SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.

I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means

Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.

I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.